ANSI ISO IEC 9805-1-1998 Information technology Open Systems Interconnection Protocol for the Commitment Concurrency and Recovery service element Protocol specification (Adopted by.pdf

《ANSI ISO IEC 9805-1-1998 Information technology Open Systems Interconnection Protocol for the Commitment Concurrency and Recovery service element Protocol specification (Adopted by.pdf》由会员分享，可在线阅读，更多相关《ANSI ISO IEC 9805-1-1998 Information technology Open Systems Interconnection Protocol for the Commitment Concurrency and Recovery service element Protocol specification (Adopted by.pdf（62页珍藏版）》请在麦多课文档分享上搜索。

1、B CReference numberISO/IEC 9805-1:1998(E)INTERNATIONALSTANDARDISO/IEC9805-1Third edition1998-12-15Information technology Open SystemsInterconnection Protocol for theCommitment, Concurrency and Recoveryservice element: Protocol specificationTechnologies de linformation Interconnexion de systmes ouver

2、ts(OSI) Protocole pour llment de service dengagement, deconcomitance et de rtablissement: Spcification du protocoleAdopted by INCITS (InterNational Committee for Information Technology Standards) as an American National Standard.Date of ANSI Approval: 12/3/2002Published by American National Standard

3、s Institute,25 West 43rd Street, New York, New York 10036Copyright 2002 by Information Technology Industry Council (ITI).All rights reserved.These materials are subject to copyright claims of International Standardization Organization (ISO), InternationalElectrotechnical Commission (IEC), American N

4、ational Standards Institute (ANSI), and Information Technology Industry Council(ITI). Not for resale. No part of this publication may be reproduced in any form, including an electronic retrieval system, withoutthe prior written permission of ITI. All requests pertaining to this standard should be su

5、bmitted to ITI, 1250 Eye Street NW,Washington, DC 20005.Printed in the United States of AmericaISO/IEC 9805-1:1998(E) ISO/IEC 1998All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic ormechanical, including

6、 photocopying and microfilm, without permission in writing from the publisher.ISO/IEC Copyright Office Case postale 56 CH-1211 Genve 20 SwitzerlandPrinted in SwitzerlandiiContents Page1 Scope 12 Normative references . 12.1 Identical Recommendations | International Standards 13 Definitions 23.1 Refer

7、ence model definitions . 23.2 Naming and addressing definitions. 23.3 Service conventions definitions 33.4 Presentation service definitions 33.5 ACSE service definitions 33.6 Application Layer Structure definitions . 33.7 CCR service definitions 33.8 CCR protocol specification definitions. 54 Abbrev

8、iations. 54.1 Data units 54.2 Types of application-protocol-data-units 54.3 Other abbreviations. 55 Conventions . 66 Overview of the CCR protocol 66.1 Service support . 66.2 Constraints on ACSE services 66.3 Use of the presentation service . 76.4 Relationship to the session-service and the transport

9、-service. 76.5 Operation of the CCRPM . 86.6 Rules of extensibility 87 Elements of procedures 87.1 Initialization procedure. 97.2 Begin branch procedure 117.3 Prepare procedure. 147.4 Signal readiness procedure . 157.5 Order commitment 167.6 Rollback procedure. 187.7 No-change completion procedure.

10、207.8 Cancel procedure 227.9 Branch recovery procedure. 237.10 Order commitment and begin branch procedure 267.11 Error procedure. 278 CCRPM state table. 278.1 General 27 ISO/IEC ISO/IEC 9805-1:1998(E)iii8.2 Incoming events 288.3 Outgoing events. 288.4 Specific actions 298.5 Predicates. 298.6 Enable

11、ments 298.7 Variables 298.8 Notation. 298.9 Conventions. 308.10 Actions to be taken by the CCRPM. 308.11 Changes to atomic action data. 318.12 Changes to bound data 319 Reference mapping to the ACSE and presentation services . 429.1 Initialize. 429.2 Begin branch . 439.3 Prepare. 449.4 Signal readin

12、ess. 449.5 Order commitment 449.6 Rollback 459.7 No-change completion 459.8 Cancel 459.9 Branch recovery 459.10 Order commitment and begin branch procedure.4510 Concatenations and mappings 4610.1 Mapping precedence 4610.2 Allowable concatenations 4611 Precedence 4712 Conformance 4712.1 Statement req

13、uirements . 4712.2 Static conformance requirements 4812.3 Presentation transfer syntax. 4812.4 Bound data and atomic action data 4812.5 Dynamic conformance requirements. 48Annex A Definition of CCR data types 49A.1 Information object names 49A.2 Datatype definitions for CCR Protocol . 49Annex B Usin

14、g the CCR ASE in combination with other ASEs 53B.1 Introduction . 53B.2 Service primitives 53B.3 Conformance . 53B.4 CCR events 53B.5 Purge and flow control 54B.6 Delimitation of atomic actions 54B.7 Named mapping variations 54ISO/IEC 9805-1:1998(E) ISO/IECivForewordISO (the International Organizati

15、on for Standardization) and IEC (the International Electrotechnical Commission) formthe specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in thedevelopment of International Standards through technical committees established by the respective

16、 organization to dealwith particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest.Other international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in thework.In the field of information techno

17、logy, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. DraftInternational Standards adopted by the joint technical committee are circulated to national bodies for voting. Publicationas an International Standard requires approval by at least 75 % of the national bodies casting

18、 a vote.International Standard ISO/IEC 9805-1 was prepared by Joint Technical Committee ISO/IEC JTC 1, Informationtechnology, Subcommittee SC 33, Distributed application services, in collaboration with ITU-T. The identical text ispublished as ITU-T Recommendation X.852.This third edition cancels and

19、 replaces the second edition (ISO/IEC 9805-1:1994), which has been technically revised.ISO/IEC 9805 consists of the following parts, under the general title Information technology Open SystemsInterconnection Protocol for the Commitment, Concurrency and Recovery service element: Part 1: Protocol spec

20、ification Part 2: Protocol Implementation Conformance Statement (PICS) proformaAnnexes A and B form an integral part of this part of ISO/IEC 9805.v,QWURGXFWLRQThis Recommendation | International Standard is one of a set of Recommendations | International Standards produced tofacilitate the interconn

21、ection of information processing systems. It is related to other Recommendation | InternationalStandards in the set as defined by the Reference Model for Open Systems Interconnection (see ITU-T Rec. X.200 |ISO/IEC 7498-1). The Reference Model subdivides the area of standardization for interconnectio

22、n into a series of layersof specification, each of manageable size.The goal of Open Systems Interconnection is to allow, with a minimum of technical agreement outside theinterconnection standards, the interconnection of information processing systems: from different manufacturers; under different ma

23、nagements; of different levels of complexity; and of different technologies.This Recommendation | International Standard specifies the protocol for the application-service-element forCommitment, Concurrency, and Recovery (CCR). These services are intended to be applicable to a wide range ofapplicati

24、on-process communication requirements.This Recommendation | International Standard specifies CCR Protocol Version 2. The 1990 edition of ISO/IEC 9805specified CCR protocol Version 1. The 1993/1994 editions of this Recommendation | International Standard specifiedboth CCR protocol Version 1 and CCR p

25、rotocol Version 2, for the static commitment functional unit only.The CCR protocol specification consists of the following main components:a) the specification of the CCR APDUs using Abstract Syntax One (ASN.1, ITU-T Rec. X.680 |ISO/IEC 8824-1);b) the elements of procedure for issuing CCR service in

26、dication and confirm primitives to the CCRservice-user when CCR APDUs are received and for the sending of CCR APDUs when CCR servicerequest and indication primitives are received from the CCR service-user;c) the CCR protocol machine specified in terms of a state table; andd) the presentation service

27、s (see ITU-T Rec. X.216 | ISO/IEC 8822) used for sending and receiving CCRAPDUs.The CCR protocol shares the presentation-service with other application-service-elements.The requirement to provide support for CCR together with other application-service-elements is satisfied by reference tothis Recomm

28、endation | International Standard.Annex A contains the definitions of the structure of the CCR APDUs.Annex B describes how the CCR can be used in combination with other ASEs that use the presentation service in a waythat is not compatible with the use of the presentation service by CCR as specified

29、in the body of this Recommendation |International Standard.ISO/IEC 9805-1:1998(E) ISO/IEC,62 ,( ( 1,17(51$7,21$/ 67$1$5ISO/IEC 9805-1 : 1998 (E)ITU-T Rec. X.852 (1997 E),78 7 5(b) C-INITIALIZE-RI APDU received by the accepting CCRPM;c) C-INITIALIZE response primitive from the acceptor; andd) C-INITI

30、ALIZE-RC APDU received by the CCRPM of the requestor.7DEOH ( ( 118VHU GDWD)RU WKH UHTXHVWLQJ ( b) C-BEGIN-RI APDU received by the accepting CCRPM;c) C-BEGIN response primitive from the acceptor; andd) C-BEGIN-RC APDU received by the requesting CCRPM.The events c) and d) are optional and may occur la

31、ter.( 13( andb) C-PREPARE-RI APDU received by the accepting CCRPM.( 15b) C-COMMIT-RI APDU received by the accepting CCRPM;c) C-COMMIT response primitive from the acceptor; andd) C-COMMIT-RC APDU received by the requesting CCRPM.( 8VH RI WKH ( 193UHUHTXLVLWH UHTXLUHPHQWVFor the requestor, the use of

32、this procedure requires either:a) no atomic action data for this branch are accessible in stable storage; orb) the CCR service-user has been ordered to rollback by its commit-superior.5ROOEDFN SURFHGXUHThis procedure is driven by the following events:a) C-ROLLBACK request primitive from the requesto

33、r;b) C-ROLLBACK-RI APDU received by the accepting CCRPM;c) C-ROLLBACK response primitive from the acceptor; andd) C-ROLLBACK-RC APDU received by the requesting CCRPM.( LVUXSWLYH HIIHFWVBecause the C-ROLLBACK service is mapped on the P-RESYNCHRONIZE service, CCR APDUs other than aC-ROLLBACK-RI from t

34、he association-initiator are discarded (by the underlying session service-provider). Thismapping guarantees that rollback takes precedence over all other allowed CCR protocol procedures.( 213UHUHTXLVLWH UHTXLUHPHQWVFor the requestor to issue the C-NOCHANGE request primitive: the requestor shall have

35、 no bound data for the atomic action.3URFHGXUH RSHUDWLRQThis procedure is driven by the following events:a) C-NOCHANGE request primitive from the requestor;b) C-NOCHANGE-RI APDU received by the accepting CCRPM;c) C-NOCHANGE response primitive from the acceptor; andd) C-NOCHANGE-RC APDU received by t

36、he requesting CCRPM.Events c) and d) are optional and may not occur if the Confirmation parameter on the C-NOCHANGErequest has the value “not-required”.( orb) the CCR service-user has been ordered to rollback.The cancel functional unit shall be selected on the association.Field name Presence Source

37、Sinkuser-data U req ind,62 ,( ( 233URFHGXUH RSHUDWLRQThis procedure is driven by the following events:a) C-CANCEL request primitive from the requestor;b) C-CANCEL-RI APDU received by the accepting CCRPM.b) C-RECOVER-RI APDU received by the accepting CCRPM;7DEOH & 5(&29(5 5, ILHOGV 7DEOH & 5(&29(5 5&

38、 ILHOGVField name Presence Source Sink Field name Presence Source Sinkatomic-action-identifier M req ind atomic-action-identifier M rsp cnfbranch-identifier M req ind branch-identifier M rsp cnfrecovery-state M req ind recovery-state M rsp cnfreversed-branch C req ind reversed-branch C rsp cnfuser-data U req ind user-data U rsp cnf