1、Information processing systems - Text communication - Reliable Transfer - Part 2 : Protocol specification Systmes de traitement de Iinformation - Communication de texte - Transfert fiable - Partie 2 : Spcification du protocole Reference number ISO/IEC 9066-2 : 1989 (E) ISO/IEC 9066-2: 1989 (E) Conte
2、nts Page Foreword . iU Introduction . iv 1 Scope 1 2 Nortmative references . 1 3 Definitions 1 4 Abbreviations . 3 5 Conventions . 3 6 Overview of the protocol 3 7 Elements of procedure 5 8 Mapping to used services. 23 9 Abstract syntax definition of APDUs . 32 10 Conformance . 35 Annexes A RTPM Sta
3、te tables . 36 B Differences between this part of ISO/IEC 9066 and CCITT Recommendation X.410 . 1984 . 63 C Summary of assigned object identifier values . 64 0 ISO/IEC 1989 All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mecha
4、nical, including photocopying and microfilm, without permission in writing from the publisher. Printed in Switzerland ISO/IEC Copyright Office o Case postale 56 o CH-1211 Genve 20 0 Switzerland ISO/IEC 9066-2: 1989 (E) Foreword IS0 (the International Organization for Standardization) and IEC (the In
5、ternational Electrotechnical Commission) together form a system for worldwide standardization as a whole. National bodies that are members of IS0 or IEC participate in the develop- ment of International Standards through technical committees established by the respective organization to deal with pa
6、rticular fields of technical activity. IS0 and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in liaison with IS0 and IEC, also take part in the work. In the field of information technology, IS0 and IEC have es
7、tablished a joint technical committee, ISO/IEC JTC 1. Draft International Standards adopted by the joint technical committee are circulated to national bodies for approval before their accep- tance as International Standards. They are approved in accordance with procedures re- quiring at least 75 %
8、approval by the national bodies voting. International Standard ISO/IEC 9066-2 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology. iii -_- I 706b PT 2-87 I 4851703 0077828 0 r ISO/I EC 9066-2: 1989 (E) Introduction This part of ISO/IEC 9066 specifies the protocol for the
9、services provided by an application-service-element - the Reliable Transfer Service Element (RTSE) - to provide for the Reliable Transfer of application protocol data units (APDUs) between open systems. This part of ISO/IEC 9066 is one of a set of International Standards specifying the protocols for
10、 sets of application-service-elements commonly used by a number of applications. Reliable Transfer provides an application-independent mechanism to recover from communication and end-system failure minimizing the amount of retransmission. This part of ISO/IEC 9066 is technically aligned with CCITT R
11、ecommendation X.228. iv HUTERNATIONAL STANDARD IS0 / IEC 9066-2: 1989 (E) Information processing systems -Text Communication - Reliable Transfer - Part 2: Protocol specification 1 Scope This part of ISOIIEC 9066 specifies the protocol (abstract syntax) and procedures for the Reliable Transfer Servic
12、e Element services (ISO/IEC 9066- 1). The RTSE services are provided in conjunction with the Association Control Service Element (ACSE) services (IS0 8649) and the ACSE protocol (IS0 86501, and the presentation-service (IS0 8822). The RTSE procedures are defined in terms of a) the interactions betwe
13、en peer RTSE protocol machines through the use of ACSE and the presentation-service; b) the interactions between the RTSE protocol machine and its service-user. This part of ISOIIEC 9066 specifies conformance requirements for systems implementing these procedures. 2 Normative references The followin
14、g standards contain provisions which, through reference in this text, constitute provisions of this part of ISOfiEC 9066. At the time of publication, the editions were valid. All Standards are subject to revision, and parties to agreement based on this part of ISO/IEC 9066 are encouraged to investig
15、ate the possibility of applying the most recent editions of the standards listed below. Members of IS0 and IEC maintain Registers of currently valid International Standards. IS0 7498: 1984, Information processing systems - Open Systems Interconnection - Basic Reference Model. ISOTR 8509: 1987, Infor
16、mation processing systems - Open Systems Interconnection - Service Conuentions. IS0 8649: 1988, Information processing systems - Open Systems Interconnection - Service definition for the Association Control Service Element. IS0 8650: 1988, Information processing systems - Open Systems Interconnectio
17、n - Protocol specification for the Association Control Service Element. IS0 8822: 1988, Information processing systems - Open Systems Interconnection - Connection oriented presentation service definition. IS0 8824: 1987, Information processing systems - Open Systems Interconnection - Specification o
18、f Abstract Syntax Notation One (ASN.1). IS0 8825: 1987, Information processing systems - Open Systems Interconnection - Specification of basic encoding rules for Abstract Syntax Notation One (ASN.1). ISO/IEC 9066-1: 1989, Information processing systems - Text communication - Reliable Transfer -Part
19、1: Model and service definition, ISO/IEC 9072-1: 1989, Information processing systems - Text Conmunication - Remote Operations - Part 1: Model, notation and service definition. 3 Definitions 3.1 Reference model definitions This part of ISO/IEC 9066 is based on the concepts developed in IS0 7498 and
20、makes use of the following terms defined in it: a) Application Layer; b) application-process; c) application-entity; d) application-service-element; 1 3066 PT 2-87 4851903 0079830 9 I- -I - ISOAEC 9066-2: 1989 (E) application-protocol-data-unit; application-protocol-control-information presentation-
21、service; presenta tion-connec tion; session-service; session-connection; user-element ; two-way-alternate interaction; and transfer syntax. 3.2 Service conventions definitions This part of ISO/IEC 9066 makes use of the following terms defined in ISO/TR 8509: a) service-provider; b) service-user; c)
22、confirmed service; d) non-confirmed service; e) provider-initiated service; f) primitive; g) request (primitive); h) indication (primitive); i) response (primitive); and j) confirm (primitive). 3.3 Presentation service definitions This part of ISO/IEC 9066 makes use of the following terms defined in
23、 IS0 8822: a) abstract syntax; b) abstract syntax name; c) presentation context; and d) default context. 3.4 Association control definitions This part of ISO/IEC 9066 makes use of the following terms defined in IS0 8649: a) application-association; association; b) application context; c) d) X.410-19
24、84 mode. Association Control Service Element; and 3.5 RTSE service definitions This part of ISO/IEC 9066 makes use of the following terms defined in ISO/IEC 9066-1: a) ass oc ia t ion- i n i t ia t i n g - a p p 1 ic a t io n - e n t i t y ; association-initiator; b) association-responding-applicati
25、on-entity; association-responder ; c) sending-application-entity; sender; d) receiving-application-entity; receiver; e) requestor; f) acceptor; g) Reliable Transfer Service Element; h) RTSE-user; i) RTSE-provider; j) ACSE-provider; k) monologue interaction; 1) syntax-matching-services; m) Reliable T
26、ransfer; n) X.410-1984 mode; and o) normal mode. 3.6 Reliable Transfer protocol For the purpose of this part of ISO/IEC 9066 the following definitions apply: specification definitions 3.6.1 reliable-transfer-protocol-machine: The protocol machine for the Reliable Transfer Service Element specified i
27、n this part of ISO/IEC 9066. 3.6.2 requestingreliable-transfer-protocol- machine: The reliable-transfer-protocol-machine whose RTSE-user is the requestor of a particular Reliable Transfer Service Element service. 3.6.3 accepting-reliable-transfer-protocol- machine: The reliable-transfer-protocol-mac
28、hine whose RTSE-user is the acceptor for a particular Reliable Transfer Service Element service. 3.6.4 sending-reliable-transfer-protocol- machine: The reliable-transfer-protocol-machine whose RTSE-user is the sender. 2 9066 - 3.6.5 receiving-reliable-transfer-protocol- machine: The reliable-transfe
29、r-protocol-machine whose RTSE-user is the receiver. 3.6.6 ass o cia tion -in i ti a tin g - r e li ab 1 e - transfer-protocol-machine: The reliable- transfer-protocol-machine whose RTSE-user is the association-initiator. 3.6.7 association-responding-reliable- transfer-protocol-machine: The reliable-
30、 transfer-protocol-machine whose RTSE-user is the association-responder. 4 Abbreviations 4.1 Data units APDU appication-protocol-data-unit 4.2 Types of application-protocol-data- The following abbreviations have been given to the application-protocol-data-units defined in this part of TSO/IEC 9066.
31、RTAB RT-P-ABORT and RT-C-ABORT appIication-protocol-data-unit RTORQ RT-OPES-REQLEST application- protocol-data-unit RTOAC RT- OPE N -A C CE PT a p pl i c a t i o n - pro tocol-data-unit RTORJ RT-OPEN-REJECT application- protocol-data-unit RTTR RT-TRASSFER application-pro tocol- data-unit RTTP RT-TOK
32、EX-PLEASE application- protocol-data-unit units 4.3 Other abbreviations The following abbreviations are used in this part of ISO/IEC 9066. AE application-entity ACSE Association Control Service Element ASE application-service-element RTPM reliable-transfer-protocol-machine RT (or RTS) Reliable Trans
33、fer RTSE Reliable Transfer Service Element ISO/IEC 9066-2: 1989 (E) 5 Conventions This part of ISO/IEC 9066 employs a tabular presentation of its APDU fields. In clause 7, tables are presented for each RTSE APDU. Each field is summarized using the following notation: M presence is mandatory U T req
34、ind resp conf sp presence is a RTSE service-user option presence is a RTPM option source is related request primitive sink is related indication primitive source is related response primitive sink is related confirm primitive source or sink is the RTPM The structure of each RTSE APDU is specified in
35、 clause 9 using the abstract syntax notation of IS0 8824. 6 Overview of the protocol 6.1 Service provision The protocol specified in this part of ISO/IEC 9066 provides the services defined in ISOflEC 9066-1. These services are listed in table 1. Table 1 - RTSE service summary Service RT-OPES RT-CLOS
36、E RT-TURK-PLE ASE RT-TRANSFER RT-TURX-GIVE RT-P-ABORT RT- U- AB O RT Confirmed Confirmed Confirmed Non-confir med Non-confirmed Provider-initiated Non-confir med 6.2 Use of services 6.2.1 ACSE services The RTPM requires access to the A-ASSOCIATE, A-RELEASE, A-ABORT and A-P-ABORT services. This part
37、of ISODEC 9066 assumes that the RTPM is the sole user of these services. 3 ISOllEC 9066-2: 1989 (E) 6.2.2 Use of the Presentation-service The RTPM requires access to the P-ACTIVITY- START, P-DATA, P-MINOR-SYNCHRONIZE, P- ACTIVITY-END, P-ACTIVITY-INTERRUPT, P- ACTIVITY-DISCARD, P-U-EXCEPTION- REPORT,
38、 P-ACTIVITY-RESUME, P-P- EXCEPTION-REPORT, P-TOKEN-PLEASE and P-CONTROL-GIVE services. This part of ISO/IEC 9066 assumes that the RTPM is the sole user of the above services. The RTPM requires access to local syntax- matching-services provided by the presentation- service provider. This syntax-match
39、ing-service consists of a) An encoding service enabling the transformation from the local representation of an APDU value into an encoded-APDU-value of type OCTET STRING the value of which is the representation of the APDU value specified by the negotiated transfer syntax. b) A decoding service enab
40、ling the transformation from an encoded-APDU- value into the local representation of the APDU value. If X.410-1984 mode or simple encoding is used by the Presentation Layer, the APDU value is encoded as ASN.1 type ANY. If full encoding is used by the Presentation Layer, the APDU value is encoded as
41、ASN.l type EXTERNAL. (For X.410-1984 mode, single encoding and full encoding see IS0 8823). This part of ISO/IEC 9066 recognizes that the ACSE services require access to the P-COXXECT, P-RELEASE, P-U-ABORT and P-P-ABORT services. This part of ISO/IEC 9066 assumes that the ACSE and the RTPM are the s
42、ole users of any of the above, or of any other, presentation-services. use a single presentation context or multiple presentation contexts as a part of the presentation multiple defined context facility. The choice is determined by the use of the single presentation context parameter of the RT-OPEN
43、service as described in 8.1.1.1.3 and 8.1.1.1.4. 6.3 Model The reiiable-transfer-protocol-machine (RTPM) communicates with its service-user by means of primitives defined in ISO/IEC 9066-1. Each invocation of the RTPM controls a single application-association. The RTPM is driven by RTSE service requ
44、est and response primitives from its service-user, and by indication and confirm primitives from the ACSE services and the presentation-service. The RTPM, in turn, issues indication and confirm primitives to its service-user and request and response primitives on the used ACSE services or presentati
45、on-service. The reception of an RTSE service primitive, or of an ACSE service primitive, or of a presentation- service primitive, and the generation of dependent actions are considered to be indivisible. During the use of the RTSE services, the existence of both the association-initiating AE and the
46、 association-responding AE is presumed. How these AEs are created is beyond the scope of this part of ISO/IEC 9066 . During the use of the RTSE services, except RT-OPEPU, the existence of an application- association between the peer AEs is presumed. NOTE Each application-association may be identifie
47、d in an end system by an internal, implementation dependent mechanism so that the RTSE service-user, and the RTPM, and the ACSE service-provider can refer toit. During the lifetime of an application-association, the underlying presentation-connections either 4 7 Elements of procedure The association
48、-establishment procedure uses the RT-OPEN-REQUEST (RTORQ) APDU, the The RTSE protocol consists of the following RT-OPEN-ACCEPT (RTOAC) APDU, and the elements of procedure: RT-OPEN-REJECT (RTORJ) APDU. a) association-establishment b) association-release c) transfer d) turn-please e) turn-give f) erro
49、r reporting: fi) user-exception-report E?,) provider-exception-report gl) transfer-interrupt 82) transfer-discard 83) acsociation-abort g4 association-provider-abort hl) transfer-resumption (for recovery from gl, or after successful h3 from g3 or g4) h2) transfer-retry (for recovery from g2) h3) association-recovery (for recovery from g) error h) error recovery: g3 or g4 i) abort il) transfer-abort (recovery from gl or g2 i21 provider-abort (recovery from gl or g2 i3) user-abort. or g3 or g4 not possible) or g3 or g4 not possible) In the following subclauses, a summary of each
