ANSI INCITS ISO IEC 10026-1-1998 Information technology Open Systems Interconnection Distributed Transaction Processing Part 1 OSI TP Model (Adopted by INCITS).pdf

《ANSI INCITS ISO IEC 10026-1-1998 Information technology Open Systems Interconnection Distributed Transaction Processing Part 1 OSI TP Model (Adopted by INCITS).pdf》由会员分享，可在线阅读，更多相关《ANSI INCITS ISO IEC 10026-1-1998 Information technology Open Systems Interconnection Distributed Transaction Processing Part 1 OSI TP Model (Adopted by INCITS).pdf（46页珍藏版）》请在麦多课文档分享上搜索。

1、B CReference numberISO/IEC 10026-1:1998(E)INTERNATIONALSTANDARDISO/IEC10026-1Second edition1998-10-15Information technology Open SystemsInterconnection Distributed TransactionProcessing Part 1:OSI TP ModelTechnologies de linformation Interconnexion de systmes ouverts(OSI) Traitement transactionnel r

2、parti Partie 1: Modle OSI TPAdopted by INCITS (InterNational Committee for Information Technology Standards) as an American National Standard.Date of ANSI Approval: 11/25/2002Published by American National Standards Institute,25 West 43rd Street, New York, New York 10036Copyright 2002 by Information

3、 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 Information Technology Industry Council(ITI).

4、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, DC 20005.Printed in the United States o

5、f AmericaISO/IEC 10026-1:1998(E) ISO/IEC 1998All rights reserved. Unless otherwise specified, no part of this publication may be reproducedor utilized in any form or by any means, electronic or mechanical, including photocopying andmicrofilm, without permission in writing from the publisher.ISO/IEC

6、Copyright Office Case postale 56 CH-1211 Genve 20 SwitzerlandPrinted in SwitzerlandiiContents.PageForewordivIntroduction .v1 Scope 12 Normative references . 13 Definitions . 23.1 Terms defined in other International Standards 23.2 Terms defined in ISO/IEC 10026 34 Abbreviations 85 Conventions 86 Req

7、uirements 86.1 Introduction 86.2 User requirements. 96.3 Modelling requirements . 96.4 OSI TP Service and Protocol requirements 107 Concepts of distributed TP . 107.1 Transaction 107.2 Distributed transaction. 107.3 Transaction data and coordination level 107.4 Tree relationships 117.5 Dialogue 117.

8、6 Dialogue tree . 127.7 Transaction branch 127.8 Transaction tree 137.9 Channel . 137.10 Handshake 137.11 Hinterland 138 Model of the OSI TP Service 148.1 Nature of the OSI TP Service148.2 Rules on dialogue trees. 158.3 Rules on transaction trees. 168.4 Naming 188.5 Data transfer 198.6 Coordination

9、of resources . 198.7 Recovery . 248.8 Concurrency control and deadlock 318.9 Security 31ISO/IEC ISO/IEC 10026-1:1998(E)iiiAnnexesA Relationship of the OSI TP Model to the Application Layer Structure . Erreur! SigB Tutorial on concurrency and deadlock control in OSI TP 34C Tutorial on the presumed ro

10、llback two-phase commit protocol. 35D Combinations of Commitment Optimisations 36E Summary of changes to the second edition 39TablesTable 1 - Permitted combinations of transaction data and coordination levels 11Table 2 - Update of log-damage record. 24Table 3 - Types of failures . 25Table 4 - Restor

11、ation of node state after atomic action data unavailability 30FiguresFigure 1 - Transaction hinterland of node A viewed from node B14Figure 2 - Transaction branches, dialogues, and application-associations . 18Figure 3 - Phases of recovery 29ISO/IEC 10026-1:1998(E)ISO/IECivForewordISO (the Internati

12、onal Organization for Standardization) and IEC (the InternationalElectrotechnical Commission) form the specialized system for worldwidestandardization. National bodies that are members of ISO or IEC participate in thedevelopment of International Standards through technical committees establishedby t

13、he respective organization to deal with particular fields of technical activity.ISO and IEC technical committees collaborate in fields of mutual interest. Otherinternational organizations, governmental and non-governmental, in liaison withISO and IEC, also take part in the work.In the field of infor

14、mation technology, ISO and IEC have established a jointtechnical committee, ISO/IEC JTC 1. Draft International Standards adopted bythe joint technical committee are circulated to national bodies for voting.Publication as an International Standard requires approval by at least 75 % of thenational bod

15、ies casting a vote.International Standard ISO/IEC 10026-1 was prepared by Joint TechnicalCommittee ISO/IEC JTC 1, Information technology, Subcommittee SC 21, Opensystems interconnection, data management and open distributed processing.This second edition cancels and replaces the first edition(ISO/IE

16、C 10026-1:1992), which has been technically revised. It also incorporatesTechnical Corrigendum 1:1996.This part of ISO/IEC 10026 is technically aligned with ITU-T RecommendationX.860, but is not published as identical text.ISO/IEC 10026 consists of the following parts, under the general title Inform

17、ationtechnology Open Systems Interconnection Distributed TransactionProcessing: Part 1: OSI TP Model Part 2: OSI TP Service Part 3: Protocol specification Part 4: Protocol Implementation Conformance Statement (PICS) proforma Part 5: Application context proforma and guidelines when using OSI TP Part

18、6: Unstructured Data TransferAnnex A forms an integral part of this part of ISO/IEC 10026. Annexes B to E arefor information only.ISO/IEC ISO/IEC 10026-1:1998(E)vIntroductionISO/IEC 10026 is one of a set of standards produced to facilitate theinterconnection of computer systems. It is related to oth

19、er International Standardsin the set as defined by the Reference Model for Open Systems Interconnection(ISO/IEC 7498-1). The Reference Model subdivides the area of standardizationfor interconnection into a series of layers of specification, each of manageablesize.The aim of Open Systems Interconnect

20、ion is to allow, with a minimum of technicalagreement outside the interconnection standards, the interconnection of computersystemsa) from different manufacturers;b) under different management;c) of different levels of complexity; and,d) of different technologies.ISO/IEC 10026 defines an OSI TP Mode

21、l, an OSI TP Service and specifies anOSI TP Protocol available within the Application Layer of the OSI ReferenceModel.The OSI TP Service is an Application Layer service. It is concerned withinformation which can be related as distributed transactions, which involve two ormore open systems.ISO/IEC 10

22、026 provides sufficient facilities to support transaction processing, andestablishes a framework for coordination across multiple OSI TP resources inseparate open systems.ISO/IEC 10026 does not specify the interface to local resources or accessfacilities that are provided within the local system. Ho

23、wever, future enhancementof the standard may deal with these issues.INTERNATIONAL STANDARD ISO/IEC ISO/IEC 10026-1:1998(E)1Information technology Open SystemsInterconnection Distributed Transaction Processing Part 1:OSI TP Model1 ScopeThis part of ISO/IEC 10026:a) provides a general introduction to

24、the concepts and mechanisms defined in ISO/IEC 10026;b) defines a model of distributed transaction processing;c) defines the requirements to be met by the OSI TP Service; andd) takes into consideration the need to coexist with other Application Service Elements, e.g. RDA(Remote Database Access), ROS

25、E (Remote Operations Service Element), and non-ROSEbased applications.This part of ISO/IEC 10026 makes sufficient provisions to allow the specification of transaction-modecommunications services and protocols that meet the properties of: atomicity, consistency, isolation, anddurability (the ACID pro

26、perties), as defined in ISO/IEC 9804.This part of ISO/IEC 10026 does not specify individual implementations or products, nor does it constrain theimplementation of entities or interfaces within a computer system.2 Normative referencesThe following standards contain provisions which, through referenc

27、e in this text, constitute provisions of thispart of ISO/IEC 10026. At the time of publication, the editions indicated were valid. All standards are subjectto revision, and parties to agreements based on this part of ISO/IEC 10026 are encouraged to investigate thepossibility of applying the most rec

28、ent editions of the standards indicated below. Members of IEC and ISOmaintain registers of currently valid International Standards.ISO/IEC 7498-1:1994, Information technology - Open Systems Interconnection - Basic Reference Model: TheBasic Model.ISO 7498-2:1989, Information processing systems - Open

29、 Systems Interconnection - Basic Reference Model- Part 2: Security Architecture.ISO/IEC 7498-3:1997, Information technology - Open Systems Interconnection - Basic Reference Model:Naming and addressing.ISO/IEC 8326:1996, Information technology - Open Systems Interconnection - Session service definiti

30、on.ISO/IEC 8649:1996, Information technology - Open Systems Interconnection - Service definition for theAssociation Control Service Element.ISO/IEC 8822:1994, Information technology - Open Systems Interconnection - Presentation servicedefinition.ISO/IEC 10026-1:1998(E)ISO/IEC2ISO/IEC 9545:1989, Info

31、rmation technology - Open Systems Interconnection - Application Layer structure.NOTE - this edition of ISO/IEC 10026 uses the terminology and modelling mechanisms of the first (1989) edition of theApplication Layer Structure (ISO/IEC 9545:1989).ISO/IEC 9579-1:1993, Information technology - Open Syst

32、ems Interconnection - Remote Database Access -Part 1: Generic Model, Service, and Protocol.ISO/IEC 9594-2:1995, Information technology - Open Systems Interconnection - The Directory: Models.ISO/IEC 9804:1997, Information technology - Open Systems Interconnection - Service definition for thecommitmen

33、t, concurrency and recovery service element.ISO/IEC 10026-2:1998, Information technology - Open Systems Interconnection - Distributed TransactionProcessing - Part 2: OSI TP Service.ISO/IEC 10026-3:1998, Information technology - Open Systems Interconnection - Distributed TransactionProcessing - Part

34、3: Protocol specification.ISO/IEC 10026-4:1995, Information technology - Open Systems Interconnection - Distributed TransactionProcessing: Protocol Implementation Conformance Statement (PICS) proforma.ISO/IEC 10731:1994, Information technology - Open Systems Interconnection - Basic Reference Model -

35、Conventions for the definition of OSI services.ISO/IEC 13712-1:1995, Information technology - Remote Operations: Concepts, model and notation.3 DefinitionsFor the purposes of ISO/IEC 10026, the following definitions apply.3.1 Terms defined in other International Standards3.1.1 ISO/IEC 10026 makes us

36、e of the following terms defined in ISO/IEC 7498-1:a) application-entity;b) application-process;c) application-protocol-data-unit;d) concatenation;e) open system;f) presentation-service;g) presentation-service-access-point;h) presentation-service-data-unit;i) real open system; andj) separation.3.1.2

37、 ISO/IEC 10026 makes use of the following terms defined in ISO 7498-2:a) access control;b) audit;c) authentication;d) confidentiality;e) integrity; andf) non-repudiation.3.1.3 ISO/IEC 10026 makes use of the following terms defined in ISO/IEC 7498-3:a) application-process-invocation-identifier;b) app

38、lication-process-title;c) application-entity-invocation-identifier;ISO/IEC ISO/IEC 10026-1:1998(E)3d) application-entity-qualifier; ande) application-entity-title.3.1.4 ISO/IEC 10026 makes use of the following term defined in ISO/IEC 8326:quality-of-service3.1.5 ISO/IEC 10026 makes use of the follow

39、ing terms defined in ISO/IEC 10731:a) request;b) indication;c) response;d) confirm;e) service primitive; primitive;f) service-provider; andg) service-user.3.1.6 ISO/IEC 10026 makes use of the following terms defined in ISO/IEC 9545:a) application-association; association;b) application-context;c) ap

40、plication-context-name;d) application-entity-invocation;e) application-process-invocation;f) application-service-element;g) association control service element;h) multiple association control function;i) single association control function; andj) single association object.3.1.7 ISO/IEC 10026 makes u

41、se of the following terms defined in ISO/IEC 9594-2:a) Directory Information Tree;b) Directory entry; entry;c) distinguished name;d) object class; ande) relative distinguished name.3.1.8 ISO/IEC 10026 makes use of the following terms defined in ISO/IEC 9804:a) atomic action data;b) atomicity;c) boun

42、d data;d) consistency;e) durability;f) final state;g) heuristic decision;h) initial state; andi) isolation.3.2 Terms defined in ISO/IEC 100263.2.1 application-supported distributed transaction: A transaction where the user of the OSI TP Serviceis responsible for the maintenance of the ACID propertie

43、s.ISO/IEC 10026-1:1998(E)ISO/IEC43.2.2 chained sequence: A sequence of related contiguous (provider-supported) transaction branches, onthe same dialogue, that are aimed at achieving a common goal.3.2.3 Channel Protocol Machine; CPM: The part of an AEI involved in OSI TP that establishes andterminate

44、s TP channels.3.2.4 channel; Transaction Processing channel: A relationship over an association between two AEIs tofacilitate Transaction Processing Service Provider (TPSP) recovery activity. Channels are not visible to theTPSUIs.3.2.5 commit master: The neighbour to which a node has sent a ready si

45、gnal.NOTE - with the static commitment procedures, the commit master will be the dialogue superior.3.2.6 commit slave: A neighbour from which a ready signal has been received.NOTE - CCR uses the term “commit subordinate“; TP uses the term “commit slave“ to avoid confusion with dialoguesubordinate.NO

46、TE - with the static commitment procedures, a commit slave will be a dialogue subordinate.NOTE - the terms commit master and commit slave do not apply when a read-only signal or early-exit signal or one-phase signal is sent.3.2.7 commitment; transaction commitment: Completion of a transaction with t

47、he release of transactiondata in the final state.NOTE - commitment requires two-phase commitment procedures if bound data are affected; one-phase commitmentprocedures may be used if bound data are not affected; see section 8.6.1 for two-phase commitment procedures and8.6.4 for one-phase commitment p

48、rocedures.NOTE - the terms “commitment“ and “rollback“ have a different scope from that defined in ISO/IEC 9804. ISO/IEC10026 is concerned with the commitment and rollback of a complete transaction, whereas ISO/IEC 9804 refers to thecommitment and rollback of a single atomic action branch.3.2.8 comm

49、itment coordinator: A TPPM involved in a distributed transaction that arbitrates the finaloutcome of the transaction.NOTE - With the static two-phase commitment procedures, the commitment coordinator will be at the root of thetransaction tree. If the static one-phase commitment procedures are in use in the transaction tree, the commitmentcoordinator will either be a leaf node or an intermediate node. With the dynamic two-phase commitment procedures,the position of the commitment coordinator may be predetermined or may be determined dynamically.3.2.