1、INTERNATIONAL ISOIIEC STANDARD 9072-2 First edition 1989-11-15 Information processing systems - Text communication - Remote Operations - Part 2 : Protocol specification Systhes de traitement de linformation - Communication de texte - Oprations disfance - Partie 2 : SpBcification du protocole Referen
2、ce number ISO/IEC 9072-2 : 1989 (E) Contents Page Foreword . iii Introduction . iv 1 Scope 1 2 Normative references . 1 3 Definitions 2 4 Abbreviations . 3 5 Conventions . 3 6 Overview of the protocol 3 7 Elements of procedure 5 8 Mapping to used services . 12 9 Abstract syntax definition of APDUs .
3、 14 10 Conformance . 17 Annexes A ROPM State tables . 18 B Differences between this part of ISO/IEC 9072 and CCITT Recommendation X.410 . 1984 . 27 C Summary of assigned object identifier values . 28 O ISO/IEC 1989 All rights reserved. NO part of this publication may be reproduced or utilized in any
4、 form or by any means, electronic or mechanical, including photocopying and microfilm, without Permission in writing from the publisher. Printed in Switzerland ISO/IEC Copyright Office o Case postale 56 0 CH-1211 Geneve 20 Switzerland ISO/IEC 9072-2: 1989 (E) Foreword IS0 (the International Organiza
5、tion for Standardization) and IEC (the International 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 fechnical committees established by th
6、e respective organization to deal with particular 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 in
7、formation technology, IS0 and IEC have established 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 w
8、ith procedures re- quiring at least 75 % approval by the national bodies voting. International Standard ISO/IEC 9072-2 was prepared by Joint Technical Committee ISO/IEC JTC 1, lnformafion technology. iii ISOIIEC 9072-2: 1989 (E) Introduction This part of ISOIIEC 9072 specifies the protocol for the s
9、ervices provided by an application-service-element - the Remote Operations Service Element (ROSE) - to support interactive applications in a distributed open systems environment. This part of IS0 9072 is one of a set of International Standards defining sets of application-service-elements commonly u
10、sed by a number of applications. Interactions between entities of a distributed application are modeled as Remote Operations, and defined using a Remote Operations notation. A Remote Operation is requested by one entity; the other entity attempts to perform the Remote Operation and then reports the
11、outcome of the attempt. Remote Operations are supported by the ROSE. This part of ISO/IEC 9072 is technically aligned with CCITT Recommendation X.229. . INTERNATIONAL STANDARD IS0 / IEC 9072-2: 1989 (E) Information processing systems -Text communication - Remote Operations - Part 2: Protocol specifi
12、cation 1 Scape This part of ISOAEC 9072 specifies the protocol (abstract syntax) and procedures for the Remote Operation Service Element (part 1 of this International Standard). The ROSE services are provided in conjunction with the Association Control Service Element (ACSE) services (IS0 86491 and
13、the ACSE protocol (IS0 86501, optionally the Reliable Transfer Service Element RTSEI services (ISO/IEC 9066-1) and the RTSE protocol (ISOIIEC 9066-21, and the presentation- service (IS0 8822). The ROSE procedures are defined in terms of a) the interactions between peer ROSE protocol machines through
14、 the use of RTSE services or the presentation-service; b) the interactions between the ROSE protocol machine and its service-user. This part of ISO/IEC 9072 specifies conformance requirements for systems implementing these procedures. 2 Normative references The following standards contain provisions
15、 which, through reference in this text, constitute provisions of this part of ISOIIEC 9072. 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 9072 are encouraged to investigate the possibility of applyin
16、g the most recent editions of the standards listed below. Members of IS0 and IEC maintain Registers of currently valid International Standards. ISO/IEC 7498: 1984, Information processing systems - Open Systems Interconnection - Basic Reference Model. ISO/TR 8509: 1987, Information processing systems
17、 - Open Systems Interconnection - Service Conventions. IS0 8649: 1988, Informution processing systems - Open Systems Interconnection - Service definition for the Association Control Service Element. IS0 8650: 1988, Information processing systems - Open Systems Interconnection - Protocol specificatio
18、n for the Association Control Service Element. IS0 8822: 1988, Information processing systems - Open Systems Intercdnnection - Connection oriented presentation service definition. IS0 8824: 1987, Information processing systems - Open Systems Interconnection - Specification of Abstract Syntax Notatio
19、n One (ASN.1). IS0 8825: 1987, Informution processing systems - Open Systems Interconnection - Specification of basic encoding rules for Abstract Syntax Notation One(ASN.1). ISO/IEC 9066-1: 1989, Informa.tion processing systems - Text communication - Reliable Transfer - Part 1: Model and service def
20、inition. ISO/IEC 9066-2: 1989, Information processing systems - Text communication - Reliable Transfer - Part 2: Protocol specification. ISO/IEC 9072-1: 1989, Information processing systems - Text communication - Remote Operations - Part 1: Model, notation and service definition. ISO/IEC 9072-2: 198
21、9 (E) 3 Definitions 3.1 Reference Model definitions This part of ISO/IEC 9072 is based on the concepts developed in ISO/IEC 7498 and makes use of the following terms defined in it: a) Application Layer; b) application-process; c) application-entity; d) application-service-element; e) application-pro
22、tocol-data-unit; f) application-protocol-control-information; g) presentation-service; h) presentation-connection; i) session-service; j) session-connection; k) transfer syntax; and 1) user-element. 3.2 Service conventions definitions This part of ISO/IEC 9072 makes use of the following terms define
23、d in ISO/TR 8509: 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 (primitive); and j) confirm (primitive). 3.3 Presentation service definitions This part
24、of ISO/IEC 9072 makes use of the following terms defined in IS0 8822: a) abstract syntax; b) abstract syntax name; c) presentation context. 2 3.4 Association control definitions This part of ISO/IEC 9072 makes use of the following terms defined in IS0 8649: a) application-association; association; b
25、) application context; c) Association Control Service Element. 3.5 Reliable Transfer definitions This part of ISO/IEC 9072 makes use of the following terms defined in ISO/IEC 9066-1: a) Reliable Transfer Service Element. 3.6 ROSE service definitions This part of ISO/IEC 9072 makes use of the followi
26、ng terms defined in ISO/IEC 9072-1: association-initiating-application-entity; association-initiator; association-responding-application- entity; association-responder; invoking-application-entity; invoker; performing-application-entity; performer; requestor; acceptor; linked-operations; parent-oper
27、ation; child-operation; RO-notation; Remote Operation Service Element; ROSE-provider; ROSE-user; RTSE-user; Remote Operations. 3.7 Remote Operation prot specification definitions oco1 For the purpose of this part of ISO/IEC 9072 the following definitions apply: 3.7.1 remote-operation-protocol-.machi
28、ne: The protocol machine for the Remote Operation Service Element specified in this part of ISO/IEC 9072. ISOAEC 9072-2: 1989 (E) 5 Conventions This part of ISO/IEC 9072 employs a tabular presentation of its APDU fields. In clause 7, tables are presented for each ROSE APDU. Each field is summarized
29、using the following notation: M presence is mandatory u presence is a ROSE-user option req source is related request primitive ind sink is related indication primitive resp source is related response primitive 3.7.2 requesting-remote-operation- protocol-machine: The remote-operation- protocol-machin
30、e whose service-user is the requestor of a particular Remote Operation Service Element service. 3.7.3 accepting-remote-operation-protocol- machine: The remote-operation-protocol- machine whose service-user is the acceptor or a particular Remote Operation Service Element service. 4 Abbreviations 4.1
31、Data units conf sink is related confirm primitive APDU application-protocol-data-unit SP source or sink is the ROPM 4.2 Types of applcation-protocol-data- The structure of each ROSE APDU is specified in units clause 9 using the abstract syntax notation of The following abbreviations have been given
32、to ISOnEC 8824. the application-protocol-data-units defined in this part of ISOAEC 9072. 6 Overview of the protocol ROIV RO-EVOKE application-protocol- data-unit RORS RO-RESULT application-protocol- data-unit ROER RO-ERROR application-protocol-data- unit RORJ RO-REJECT application-protocol- data-uni
33、t 4.3 Other abbreviations The following abbreviations are used in this part of ISO/IEC 9072. AE Application Entity ACSE Association Control Service Element ASE Application Service Element R0 (or ROS) Remote Operations ROPM Remote Operations Protocol Machine ROSE Remote Operations Service Element RT
34、Reliable Transfer RTSE Reliable Transfer Service Element 6.1 Service provision The protocol specified in this part of ISO/IEC 9072 provides the ROSE services defined in ISO/IEC 9072-1. These services are listed in table 1. Table 1 - ROSE services summary Service Type RO-INVOKE Non-confirmed RO-RESCL
35、T ?ion-confirmed RO-ERROR Non-confirmed RO-REJECT-C Non-confirmed RO-REJECT-P Provider-initiated 6.2 Use of services The ROSE protocol specified in this part of ISO/IEC 9072 needs a transfer service to pass information in the form of ROSE APDUs between peer application-entities (AEs). Two transfer s
36、ervices may be used alternatively: a) the RTSE services, if the RTSE is included in the application-context, or b) the presentation-service, if the RTSE is not included in the application-context. 3 ISO/IEC9072-2: 1989 (E) In both cases an existing application-association, established and released b
37、y means of the ACSE services, is assumed. 6.2.1 Use of the RTSE services If the RTSE is included in the application-context, this part of ISOIIEC 9072 assumes that the ROPM is the sole user of the RT-TRANSFER service and the RT-TURN-GIVE service. The initiating AE may only request the release of the
38、 application-association by means of the RT- CLOSE service if it possesses the Turn. Therefore the RTSE-user and the ROPM are the user of the RT-TURN-PLEASE service. The ROPM is the user of the RT-U-ABORT and RT-P-ABORT services. 6.2.2 Use of the presentation-service If the RTSE is not included in t
39、he application-context, the ROPM is a user of the P- DATA service. 6.3 Model The remote-operation-protocol-machine (ROPM) communicates with its service-user by means of primitives defined in ISOAEC 9072-1. Each invocation of the ROPM controls a single application-association. The ROPM is driven by R
40、OSE service request primitives from its service-user, and by indication and confirm primitives of the RTSE services, or the presentation-service. The ROPM, in turn, issues indication primitives to its service-user, and request primitives on the used RTSE services, or the presentation-service. If the
41、 RTSE is included in the application-context, the RT- TRANSFER indication, RT-TRANSFER request and RT-TRANSFER confirm primitives are used. In the case of an application-context excluding RTSE, the presentation-service P-DATA request, and P-DATA indication primitives are used. In this case the trans
42、fer is not confirmed. The reception of a ROSE service primitive, or of a RTSE service or of a presentation-service primitive, and the generation of dependent actions are considered to be indivisible. During the exchange of APDUs, the existence of both, the association-initiating AE and the associati
43、on-responding AE is presumed. How these AEs are created is beyond the scope of this part of ISO/IEC 9072. During the execution of operations, the existence of an application-association between the peer AEs is presumed. How this application- association is established and released is beyond the scop
44、e of this part of ISO/IEC 9072 (see ISO/IEC 9072-1, IS0 8649, IS0 8650, ISO/IEC 9066-1 and ISO/IEC 9066-2). NOTE Each application-association may be identified in an end system by an internal, implementation dependent mechanism so that the ROSE service-user and the ROPM can refer to it. 4 7 Elements
45、 of procedure The ROSE protocol consists of the following elements of procedure: a) invocation b) return-result c) return-error d) user-reject e) provider-reject. In the following clauses, a summary of each of these elements of procedure is presented. This consists of a summary of the relevant APDLr
46、s, and a high-level overview of the relationship between the ROSE service primitives, the APDUs involved, and the transfer service that is used. The generic terms transfer service, transfer service-provider, transfer request, and transfer indication are used in the context of clause 7. Clause 8 desc
47、ribes how these generic service primitives are mapped either on to the RTSE services or the presentation-service. In clause 9 a detailed specification of the ROSE APDCs is given using the notation defined in IS0 8824. 7.1 Invocation 7.1.1 Purpose The invocation procedure is used by one AE (the invok
48、er) to request an operation to be performed by the other AE (the performer). 7.1.2 APDUs used The invocation procedure uses the RO-IXVOKE (ROIV) APDU. The fields of the ROIV APDC are listed in table 2. 7.1.3 Invocation procedure This procedure is driven by the following events: a) a RO-INVOKE reques
49、t primitive from the requestor ISOAEC 9072-2: 1989 (E) b) a ROIV APDU as user-data of a transfer indication primitive. 7.1.3.1 RO-INVOKE request primitive Table 2 - RON APDC fields Field name Source Sink sence Invoke-ID M req ind Linked-ID U req ind Operation-value M req ind Argument U req ind The requesting ROPM forms a ROIV APDU from the parameter values of the RO-INVOKE request primitive. It issues a transfer request primitive. The user-data parameter of the transfer request primitive contains the ROIV APDU. The requesting ROPM waits either for a transfer indication primitive fr
