ANSI INCITS ISO IEC 9804-1998 Information technology Open Systems Interconnection Service definition for the Commitment Concurrency and Recovery service element (Adopted by INCITS).pdf

1、B CReference numberISO/IEC 9804:1998(E)INTERNATIONALSTANDARDISO/IEC9804Third edition1998-12-01Information technology Open SystemsInterconnection Service definition for theCommitment, Concurrency and Recoveryservice elementTechnologies de linformation Interconnexion de systmes ouverts(OSI) Dfinition

2、du service pour llment dengagement, deconcomitance et de rtablissementAdopted by INCITS (InterNational Committee for Information Technology Standards) as an American National Standard.Date of ANSI Approval: 12/3/2002Published by American National Standards Institute,25 West 43rd Street, New York, Ne

3、w 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 National Standards Institute (ANSI), and Infor

4、mation 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 submitted to ITI, 1250 Eye Street NW,Washington

5、, DC 20005.Printed in the United States of AmericaISO/IEC 9804: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 photocopying and microfilm, without permission

6、 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 12.2 Paired Recommendations | International Standards equivalent in tech

7、nical content 23 Definitions 23.1 Reference Model definitions. 23.2 Service conventions definitions 33.3 Presentation service definitions 33.4 ACSE service definitions 33.5 Application Layer Structure definitions . 33.6 CCR service definitions 44 Abbreviations. 75 Conventions . 86 Concepts. 86.1 Use

8、 of CCR in a distributed application environment 86.2 CCR facilities 146.3 Heuristic decisions 167 Service definition. 167.1 C-INITIALIZE service . 177.2 C-BEGIN service 187.3 C-PREPARE service. 197.4 C-READY service 207.5 C-COMMIT service 207.6 C-ROLLBACK service. 217.7 C-NOCHANGE service 227.8 C-C

9、ANCEL service 237.9 C-RECOVER service . 237.10 C-P-ERROR service . 258 Sequencing information. 258.1 General 258.2 Events . 328.3 States. 328.4 Predicates 328.5 Interpretation of the state table . 32 ISO/IEC ISO/IEC 9804:1998(E)iii8.6 Completing the branch 328.7 Collisions and disruptive services .

10、339 Using CCR 339.1 General 339.2 Use of CCR with non-reference mapping . 339.3 Use of session synchronization and resynchronization services . 339.4 Use of CCR with session activities 339.5 Use of presentation services 33Annex A CCR service-user rules 34A.1 Introduction . 34A.2 Compliance 34A.3 CCR

11、 service primitive usage rules 34A.4 Atomic action data manipulation rules 37A.5 Bound data manipulation rules 38A.6 CCR service-user data transfer rules . 39Annex B Relationship of CCR to the Application Layer Structure 40B.1 CCR service-provider 40B.2 CCR service-user. 40B.3 Atomic action graph 40

12、Annex C CCR tutorial. 42C.1 Introduction . 42C.2 Strucutre of an atomic action tree 43C.3 CCR service-user information resources. 45C.4 Concurrency 47C.5 Recovery 48C.6 Time relations and sequence of service primitives 52C.7 Comments on implementation complexity 53C.8 Using the User Data parameter o

13、n CCR services53C.9 Optional use of C-PREPARE 59ISO/IEC 9804:1998(E) ISO/IECivForewordISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) formthe specialized system for worldwide standardization. National bodies that are members of ISO or

14、IEC participate in thedevelopment of International Standards through technical committees established by the respective organization to dealwith particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest.Other international organizations, gover

15、nmental and non-governmental, in liaison with ISO and IEC, also take part in thework.In the field of information technology, 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 bodie

16、s for voting. Publicationas an International Standard requires approval by at least 75 % of the national bodies casting a vote.International Standard ISO/IEC 9804 was prepared by Joint Technical Committee ISO/IEC JTC 1, Informationtechnology, Subcommittee SC 33, Distributed application services, in

17、collaboration with ITU-T. The identical text ispublished as ITU-T Recommendation X.851.This third edition cancels and replaces the second edition (ISO/IEC 9804:1994), which has been technically revised.Annexes A and B form an integral part of this International Standard. Annex C is for information o

18、nly.v)NTRODUCTIONThis Recommendation | International Standard is one of a set of Recommendations | International Standards produced tofacilitate the interconnection of information processing systems. It relates to other ITU-T Recommendations |International Standards in the set defined by the Referen

19、ce Model for Open Systems Interconnection (see ITU-TRec. X.200 | ISO/IEC 7498). The reference model subdivides the area of standardization for interconnection into a seriesof layers of specification, each of manageable size.The goal of Open Systems Interconnection is to allow, with a minimum of tech

20、nical agreement outside theinterconnection Recommendations and International Standards, the interconnection of information processing systems: from different manufacturers; under different managements; of different levels of complexity; and of different technologies.This Recommendation | Internation

21、al Standard recognizes that application-processes may wish to communicate witheach other for a wide variety of reasons. However, any communication requires certain services independent of thereasons for communication. The application-service-element defined in this Recommendation | International Sta

22、ndardprovides such services.This Recommendation | International Standard defines the facilities of the application-service-element for Commitment,Concurrency and Recovery (CCR). CCR provides services for a single association. A referencing specification usesthese services for starting and ending a s

23、pecific sequence of distributed application operations despite application orcommunication failure.This Recommendation | International Standard is referenced by a specification to apply CCR to its operation. CCRservices may be used with presentation services (see ITU-T Rec. X.216 | ISO/IEC 8822), or

24、 with other ApplicationLayer services. However, the use of CCR services is subject to the restrictions specified in clause 9. The use of CCRservices allows a referencing specification to define its activity as an atomic action. An atomic action may use manyassociations, possibly with different proto

25、cols on each association.Annex A describes the rules that shall be followed by a specification that references this Recommendation | InternationalStandard.Annex B presents the relationship of the CCR model and concepts to the Application Layer Structure (see ITU-TRec. X.207 | ISO/IEC 9545).Annex C i

26、s a tutorial to aid the understanding of the concepts and facilities of CCR. ISO/IEC ISO/IEC 9804:1998(E)3/ )%#G0 G0 G0 G0 %G9)45G134G02EC G08 G0 G0%G9 1).4%2.!4)/.!,G0G034!.$!2$ISO/IEC 9804 : 1998 (E)ITU-T Rec. X.851 (1997 E)45G134G0G02%#/-%.$!4)/.). association;b) application-entity;c) Application

27、 Layer;d) application-process;e) application-service-element;f) presentation-connection;g) presentation-service;h) session-connection;i) session-service.AMINGG0ANDG0ADDRESSINGG0DEFINITIONSThis Recommendation | International Standard makes use of the following terms defined in ITU-T Rec. X.650 |ISO/I

28、EC 7498-3: application-entity title2)._1)To be published.2)As defined in ITU-T Rec. X.650 | ISO 7498-3, an application-entity title is composed of an application-process title and anapplication-entity qualifier.)3/ )%#G0 G0 G0 G0 %G9)45G134G02EC G08 G0 G0%G9 33ERVICEG0CONVENTIONSG0DEFINITIONSThis Re

29、commendation | International Standard makes use of the following terms defined in ITU-T Rec. X.210 |ISO/IEC 10731:a) service-provider;b) service-user;c) confirmed service;d) non-confirmed service;e) provider-initiated service;f) primitive;g) request (primitive);h) indication (primitive);i) response

30、(primitive); andj) confirm (primitive).0RESENTATIONG0SERVICEG0DEFINITIONSThis Recommendation | International Standard makes use of the following terms defined in ITU-T Rec. X.216 |ISO/IEC 8822:a) abstract syntax;b) abstract syntax name;c) defined context set;d) functional unit presentation;e) presen

31、tation context; andf) presentation data value.!#3%G0SERVICEG0DEFINITIONSThis Recommendation | International Standard makes use of the following terms defined in ITU-T Rec. X.217 |ISO/IEC 8649:a) association-initiator;b) association-responder; andc) disrupt.!PPLICATIONG0,AYERG03TRUCTUREG0DEFINITIONST

32、his Recommendation | International Standard makes use of the following terms defined in ITU-T Rec. X.207 |ISO/IEC 9545:a) application-context;b) application-entity invocation;c) application-service-object;d) control function;e) multiple association control function;f) single association control func

33、tion;g) single association object.)3/ )%#G0 G0 G0 G0 %G94 )45G134G02EC G08 G0 G0%G9#2G0SERVICEG0DEFINITIONSACCEPTOR: The CCR service-user that receives the indication primitive for a particular CCR service. For aconfirmed service, it also issues the response primitive.APPLICATIONG0FAILURE: The failu

34、re of an application-entity invocation to meet its normal specification.ATOMICG0ACTION: A specific set of operations of a distributed application that may be characterized by theproperties of atomicity, consistency, isolation, and durability.ATOMICG0ACTIONG0BRANCH G0BRANCH: A relationship between tw

35、o CCR service-users representing an integral partof an atomic action. The relationship may survive both communication or application failure. It is begun by the use ofCCR services and later completed by either the use of CCR services or by an application or communication failure.ATOMICG0ACTIONG0BRAN

36、CHG0IDENTIFIER G0BRANCHG0IDENTIFIER: A value assigned by the atomic action branch-initiatorthat uniquely identifies a branch within the scope of the atomic action.ATOMICG0ACTIONG0DATA: State and control information about an atomic action and its branches. Atomic action datarequired for recovery pers

37、ists if an application or communication failure occurs.ATOMICG0 ACTIONG0 GRAPH: A connected graph consisting of CCR service-users as nodes and atomic actionbranches as arcs that represents the structure of an atomic action.ATOMICG0ACTIONG0IDENTIFIER: A value assigned by the atomic action owner that

38、uniquely identifies an atomicaction within the OSI environment. (The value is first used in a CCR service by the atomic action initiator. However, theinitiator may have received the value from another source via a mechanism that is not visible in CCR services).ATOMICG0ACTIONG0INITIATOR: The begin-tr

39、ee root.ATOMICG0ACTIONG0OWNER: The CCR service-user that established the atomic action identifier.ATOMICITY: A property of a set of related operations such that the operations are either all performed, or noneof them are performed.BEGING13TREE G0ATOMICG0ACTIONG0BEGING13TREE: An atomic action graph t

40、hat has been formed into a rooted tree wherethe direction of an arc is from the CCR service-user that initiates the atomic action branch.BOUNDG0DATA: Data that are accessed and manipulated by a CCR service-user as part of an atomic action. Theirstate is bound by the rules of CCR. Bound data survive

41、application and communication failures and exist beyond theatomic action branch.BRANCHG13INITIATOR G0ATOMICG0ACTIONG0BRANCHG13INITIATOR: The CCR service-user that begins a specific branch.BRANCHG13RESPONDER G0ATOMICG0ACTIONG0BRANCHG13RESPONDER: On a specific branch, the CCR service-user that didnot

42、initiate the branch.COMMITG13TREE G0ATOMICG0ACTIONG0COMMITG13TREE: An atomic action graph that has been formed into a rooted tree inwhich the direction of an arc is from the CCR service-user (the commit-superior) that may order commitment to the peer(the commit-subordinate).#2G0SERVICEG13PROVIDER: T

43、wo peer CCR application-service-elements involved in the same atomic actionbranch.#2G0SERVICEG13USER: That part of an application-entity invocation that makes use of CCR services to coordinateone or more branches of an atomic action graph.COMMITG0COORDINATOR: A CCR service-user that receives ready s

44、ignals from all of its neighbours.COMMITG13DECIDER: A CCR service-user that orders commitment to (usually, all of) its neighbours, withouthaving received an order of commitment. It is the root of the commit-tree (In certain cases, one of two roots).COMMITMENTG0OFG0ANG0ATOMICG0ACTIONG0BRANCH G0COMMIT

45、MENT: Completion of an atomic action branch with therelease of bound data in the final state.COMMITG13SUBORDINATE: (With reference to a branch.) The CCR service-user that sends a ready signal to itsneighbour; (with reference to a particular CCR service-user) another CCR service-user from whom a read

46、y signal hasbeen received on any branch (there may be several commit-subordinates for one CCR service-user).)3/ )%#G0 G0 G0 G0 %G9)45G134G02EC G08 G0 G0%G9 5COMMITG13SUPERIOR: (With reference to a branch.) The CCR service-user that receives a ready signal from itsneighbour; (with reference to a part

47、icular CCR service-user) another CCR service-user to whom a ready signal has beensent (CCR ensures there can be at most one).COMMUNICATIONG0FAILURE: The unexpected release of the supporting association.COMPENSATINGG0ACTION: Operations used to re-establish either the initial or the final state from a

48、 mixed situationthat was brought about by a conflict between heuristic decision(s) and the decision of the commit coordinator.CONCURRENCYG0CONTROL: A real open system mechanism that coordinates modifications to bound data used byconcurrent atomic actions so the isolation property of the atomic actio

49、n is guaranteed.CONFIRMATIONG0 OFG0 COMMITMENT: A statement from a commit-subordinate to the commit-superior that thecommit-subordinate has completed local commitment procedures.CONTINUINGG0TWOG13PHASEG0BRANCH G0CONTINUINGG0TWOG13PHASEG0NEIGHBOUR: A branch/neighbour in an atomic actionexcept anyi) which have been rolled back (by C-ROLLBACK request or indication); orii) which the CCR service-user has determined will be rolled-back, but has not done so; oriii) on which C-NOCHANGE indication has been received.NOTE