BS ISO IEC 9805-1-1999 Information technology - Open systems interconnection - Protocol for the commitment concurrency and recovery service element - Protocol specificatio.pdf

1、BRITISH STANDARD BSISO/IEC 9805-1:1998 Information technology Open Systems Interconnection Protocol for the Commitment, Concurrency and Recovery service element Part 1: Protocol specification ICS 35.100.70BSISO/IEC9805-1:1998 This British Standard, having been prepared under the directionof the DISC

2、 Board, waspublished under the authorityof the Standards Committee and comes into effecton 15 February1999 BSI 06-1999 ISBN 0 580 32143 6 National foreword This British Standard reproduces verbatim ISO/IEC9805-1:1998 and implements it as the UK national standard. It supersedes BSISO/IEC9805-1:1994 w

3、hich is withdrawn. The UK participation in its preparation was entrusted to Technical Committee IST/6, Data communications, which has the responsibility to: aid enquirers to understand the text; present to the responsible international/European committee any enquiries on the interpretation, or propo

4、sals for change, and keep the UK interests informed; monitor related international and European developments and promulgate them in the UK. A list of organizations represented on this committee can be obtained on request to its secretary. Cross-references The British Standards which implement intern

5、ational or European publications referred to in this document may be found in the BSI Standards Catalogue under the section entitled “International Standards Correspondence Index”, or by using the “Find” facility of the BSI Standards Electronic Catalogue. A British Standard does not purport to inclu

6、de all the necessary provisions of a contract. Users of British Standards are responsible for their correct application. Compliance with a British Standard does not of itself confer immunity from legal obligations. Summary of pages This document comprises a front cover, an inside front cover, pages

7、i and ii, theISO/IECtitle page, pages ii to vi, pages 1to 52 and a back cover. This standard has been updated (see copyright date) and may have had amendments incorporated. This will be indicated in the amendment table on the inside front cover. Amendments issued since publication Amd. No. Date Comm

8、entsBSISO/IEC9805-1:1998 BSI 06-1999 i Contents Page National foreword Inside front cover Foreword v Text of ISO/IEC 9805-1 1ii blankBSISO/IEC9805-1:1998 ii BSI 06-1999 Contents Page Foreword v Introduction 1 1 Scope 1 2 Normative references 2 2.1 Identical Recommendations|International Standards 2

9、3 Definitions 3 3.1 Reference model definitions 3 3.2 Naming and addressing definitions 3 3.3 Service conventions definitions 3 3.4 Presentation service definitions 3 3.5 ACSE service definitions 3 3.6 Application Layer Structure definitions 4 3.7 CCR service definitions 4 3.8 CCR protocol specifica

10、tion definitions 5 4 Abbreviations 6 4.1 Data units 6 4.2 Types of application-protocol-data-units 6 4.3 Other abbreviations 6 5 Conventions 6 6 Overview of the CCR protocol 7 6.1 Service support 7 6.2 Constraints on ACSE services 7 6.3 Use of the presentation service 8 6.4 Relationship to the sessi

11、on-service and the transport-service 8 6.5 Operation of the CCRPM 8 6.6 Rules of extensibility 8 7 Elements of procedures 9 7.1 Initialization procedure 9 7.2 Begin branch procedure 11 7.3 Prepare procedure 14 7.4 Signal readiness procedure 15 7.5 Order commitment 16 7.6 Rollback procedure 18 7.7 No

12、-change completion procedure 20 7.8 Cancel procedure 22 7.9 Branch recovery procedure 23 7.10 Order commitment and begin branch procedure 26 7.11 Error procedure 27 8 CCRPM state table 27 8.1 General 27 8.2 Incoming events 28 8.3 Outgoing events 28 8.4 Specific actions 28 8.5 Predicates 28 8.6 Enabl

13、ements 28 8.7 Variables 28 8.8 Notation 29 8.9 Conventions 29 8.10 Actions to be taken by the CCRPM 29 8.11 Changes to atomic action data 30BSISO/IEC9805-1:1998 BSI 06-1999 iii Page 8.12 Changes to bound data 30 9 Reference mapping to the ACSE and presentation services 42 9.1 Initialize 42 9.2 Begin

14、 branch 43 9.3 Prepare 44 9.4 Signal readiness 44 9.5 Order commitment 44 9.6 Rollback 44 9.7 No-change completion 45 9.8 Cancel 45 9.9 Branch recovery 45 9.10 Order commitment and begin branch procedure 45 10 Concatenations and mappings 45 10.1 Mapping precedence 45 10.2 Allowable concatenations 46

15、 11 Precedence 46 12 Conformance 47 12.1 Statement requirements 47 12.2 Static conformance requirements 47 12.3 Presentation transfer syntax 47 12.4 Bound data and atomic action data 47 12.5 Dynamic conformance requirements 47 Annex A Definition of CCR data types 48 A.1 Information object names 48 A

16、.2 Datatype definitions for CCR Protocol 48 Annex B Using the CCR ASE in combination with other ASEs 51 B.1 Introduction 51 B.2 Service primitives 51 B.3 Conformance 51 B.4 CCR events 51 B.5 Purge and flow control 51 B.6 Delimitation of atomic actions 52 B.7 Named mapping variations 52 Figure 1 C-IN

17、ITIALIZE APDUs 9 Figure 2 C-BEGIN APDUs 12 Figure 3 C-PREPARE APDU 14 Figure 4 C-READY APDU 15 Figure 5 C-COMMIT APDUs 17 Figure 6 C-ROLLBACK APDUs 18 Figure 7 C-NOCHANGE APDUs 20 Figure 8 C-CANCEL APDU 22 Figure 9 C-RECOVER APDUs 23 Table 1 CCR services 7 Table 2 C-INITIALIZE-RI field 10 Table 3 C-

18、INITIALIZE-RC field 10 Table 4 C-BEGIN-RI field 12 Table 5 C-BEGIN-RC field 12 Table 6 Mapping of C-BEGIN req/ind parameters 13BSISO/IEC9805-1:1998 iv BSI 06-1999 Page Table 7 Mapping of C-BEGIN rsp/cnf parameter 14 Table 8 C-PREPARE-RI field 14 Table 9 Mapping of C-PREPARE req/ind parameter 15 Tabl

19、e 10 C-READY-RI field 15 Table 11 Mapping of C-READY req/ind parameter 16 Table 12 C-COMMIT-RI field 17 Table 13 C-COMMIT-RC field 17 Table 14 Mapping of C-COMMIT req/ind parameter 18 Table 15 Mapping of C-COMMIT rsp/cnf parameter 18 Table 16 C-ROLLBACK-RI field 18 Table 17 C-ROLLBACK-RC field 18 Ta

20、ble 18 Mapping of C-ROLLBACK req/ind parameters 19 Table 19 Mapping of C-ROLLBACK rsp parameter 19 Table 20 C-NOCHANGE-RI fields 20 Table 21 C-NOCHANGE-RC fields 20 Table 22 Mapping of C-NOCHANGE req/ind parameters 21 Table 23 Mapping of C-NOCHANGE rsp/cnf parameters 21 Table 24 C-CANCEL-RI field 22

21、 Table 25 Mapping of C-CANCEL req/ind parameters 23 Table 26 C-RECOVER-RI fields 24 Table 27 C-RECOVER-RC fields 24 Table 28 Mapping of C-RECOVER req/ind parameters 25 Table 29 Mapping of C-RECOVER rsp/cnf parameters 26 Table 30 CCRPM States 31 Table 31 Incoming events 32 Table 32 Actions 33 Table 3

22、3 Predicates 33 Table 34 Enablements 34 Table 35 Outgoing events 35 Table 36 CCRPM State Table Initialisation, idle and error 36 Table 37 CCRPM State Table Phase I 37 Table 38 CCRPM State Table After sending a ready signal 38 Table 39 CCRPM State Table After receiving a ready signal 39 Table 40 CCRP

23、M State Table After cancel or rollback 40 Table 41 CCRPM State Table After commit order 40 Table 42 CCRPM State Table No-change completion 41 Table 43 CCRPM State Table Completing recovery 42 Table 44 Mapping overview 43 Table 45 Mapping precedence 46BSISO/IEC9805-1:1998 BSI 06-1999 v Foreword ISO (

24、the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the development of International Standards through technical committees

25、 established by the respective organization to deal with 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 the work.

26、In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC1. Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as an International Standard requires approval by at least7

27、5% of the national bodies casting a vote. International Standard ISO/IEC9805-1 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC33, Distributed application services, in collaboration with ITU-T. The identical text is published as ITU-T Recommendation X.

28、852. This third edition cancels and replaces the second edition (ISO/IEC9805-1:1994), which has been technically revised. ISO/IEC 9805 consists of the following parts, under the general title Information technology Open Systems Interconnection Protocol for the Commitment, Concurrency and Recovery se

29、rvice element: Part 1: Protocol specification; Part 2: Protocol Implementation Conformance Statement (PICS) proforma. Annex A and Annex B form an integral part of this part of ISO/IEC9805.vi blankBSISO/IEC9805-1:1998 BSI 06-1999 1 Introduction This Recommendation|International Standard is one of a s

30、et of Recommendations|International Standards produced to facilitate the interconnection of information processing systems. It is related to other Recommendation|International Standards in the set as defined by the Reference Model for Open Systems Interconnection (see ITU-T Rec. X.200|ISO/IEC7498-1)

31、. The Reference Model subdivides the area of standardization for interconnection into a series of layers of specification, each of manageable size. The goal of Open Systems Interconnection is to allow, with a minimum of technical agreement outside the interconnection standards, the interconnection o

32、f information processing systems: This Recommendation|International Standard specifies the protocol for the application-service-element for Commitment, Concurrency, and Recovery (CCR). These services are intended to be applicable to a wide range of application-process communication requirements. Thi

33、s Recommendation|International Standard specifies CCR Protocol Version2. The1990 edition of ISO/IEC9805 specified CCR protocol Version1. The1993/1994 editions of this Recommendation|International Standard specified both CCR protocol Version1 and CCR protocol Version2, for the static commitment funct

34、ional 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/IEC8824-1); b) the elements of procedure for issuing CCR service indication and confirm primitives to the CCR servic

35、e-user when CCR APDUs are received and for the sending of CCR APDUs when CCR service request and indication primitives are received from the CCR service-user; c) the CCR protocol machine specified in terms of a state table; and d) the presentation services (see ITU-T Rec. X.216|ISO/IEC8822) used for

36、 sending and receiving CCR APDUs. 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 to this Recommendation|International Standard. Annex A con

37、tains 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 way that is not compatible with the use of the presentation service by CCR as specified in the body of this Recommendation|Internat

38、ional Standard. 1 Scope This Recommendation|International Standard is to be applied by reference from other specifications. This is done within such specifications by reference to the CCR services defined in ITU-T Rec. X.851|ISO/IEC9804. A reference to a CCR service invokes the procedures of this Re

39、commendation|International Standard to cause external effects. This Recommendation|International Standard specifies, in clause9, a use of the ACSE, Presentation and Session services to carry the CCR semantics. This “reference” mapping can be used whenever the use of these services does not conflict

40、with the user made by other ASEs or ASOs that are using the same association. Annex B defines how a different use of supporting services may be specified, for use where the reference mapping is inappropriate. This Recommendation|International Standard specifies the static and dynamic conformance req

41、uirements for systems implementing these procedures. It does not contain tests which can be used to demonstrate conformance. from different manufacturers; under different managements; of different levels of complexity; and of different technologies.BSISO/IEC9805-1:1998 2 BSI 06-1999 This edition of

42、this Recommendation|International Standard specifies CCR protocol Version2, which makes use of the Session Data Separation functional unit to protect data not belonging to the CCR atomic action. The1990 edition of ISO/IEC9805 specified CCR protocol Version1. The1993/1994 edition of this Recommendati

43、on|International Standard specified both CCR protocol Version1 and CCR protocol Version2, for the static commitment functional unit only. This International Standard specifies the protocol elements that support the following functional units: a) static commitment; b) dynamic commitment; c) read only

44、; d) one-phase commitment; e) cancel; and f) overlapped recovery. 2 Normative references The following Recommendations and International Standards contain provisions which, through reference in this text, constitute provisions of this Recommendation|International Standard. At the time of publication

45、, the editions indicated were valid. All Recommendations and Standards are subject to revision, and parties to agreements based on this Recommendation|International Standard are encouraged to investigate the possibility of applying the most recent edition of the Recommendations and Standards listed

46、below. Members of IEC and ISO maintain registers of currently valid International Standards. The Telecommunication Standardization Bureau of the ITU maintains a list of currently valid ITU-T Recommendations. 2.1 Identical Recommendations|International Standards ITU-T Recommendation X.200 (1994)|ISO/

47、IEC 7498-1:1994, Information technology Open Systems Interconnection Basic Reference Model: The Basic Model. ITU-T Recommendation X.207 (1993)|ISO/IEC9545:1994, Information technology Open Systems Interconnection Application layer structure. ITU-T Recommendation X.210 (1993)|ISO/IEC10731:1994, Infor

48、mation technology Open Systems Interconnection Basic Reference Model: Conventions for the definition of OSI services. ITU-T Recommendation X.215 (1995)|ISO/IEC8326:1996, Information technology Open Systems Interconnection Session service definition. ITU-T Recommendation X.216 (1994)|ISO/IEC8822:1994

49、, Information technology Open Systems Interconnection Presentation service definition. ITU-T Recommendation X.217 (1995)|ISO/IEC8649:1996, Information technology Open Systems Interconnection Service definition for the association control service element. ITU-T Recommendation X.227 (1995)|ISO/IEC8650-1:1996, Information technology Open Systems Interconnection Connection-oriented protocol f