1、INTERNATIONAL STANDARD ISOAEC 9072-l First edition 1989-11-15 Information processing systems - Text communication - Remote Operations - Part 1 : Model, notation and service definition Systkmes de traitement de /information - Communication de texte - Operations 3 distance - Partie 1 : Modkle, notatio
2、n et dhfinition du service Reference number ISO/IEC 9072-I : 1989 (E) ISOAEC 9072-I : 1989 (E) Contents Page Foreword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3、 . . . . . . . . . . . . . . . . . . . . . . . . 1v 1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 2 Normative references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 3 Definitions . . .
4、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 4 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 5 Conventions . 3 6 Remote Operations Model . 4 7 Overview of notation and service
5、8 8 Relationship with other ASEs and lower layer services 9 9 Remote Operations notation 10 10 Service definition 15 11 Mapping of notation on service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 12 Sequencing information . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6、. . . . . . . . . 23 Annexes A Notation supporting the specification of Application-service-elemnts and application-contexts . . . . . . . . 26 B Guidelines for application protocol designers on the use of ROSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
7、0 ISOllEC 1989 All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the publisher. ISO/IEC Copyright Office l Case postale 56 l Cl-121 1 Genkve 20
8、 l Switzerland Printed in Switzerland ii ISOAEC 9072-I : 1989 (E) Foreword IS0 (the International Organization 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
9、participate in the develop- ment of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity. IS0 and IEC technical committees collaborate in fields of mutual interest. Other international organizations, gove
10、rnmental 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 established a joint technical committee, ISO/IEC JTC 1. Draft International Standards adopted by the joint technical committee are circulated to national b
11、odies for approval before their accep- tance as International Standards. They are approved in accordance with procedures re- quiring at least 75 % approval by the national bodies voting. International Standard ISO/IEC 9072-l was prepared by Joint Technical Committee ISO/IEC JTC 1, lnformafion techno
12、logy. . . . III ISOAEC 9072-I : 1989 (E) Introduction This part of ISO/IEC 9072 defines a n vLablon and the services 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
13、 IS0 9072 is one of a set of International Standards defining sets of application-service-elements commonly used 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 Operatio
14、n is requested by one entity; the other entity attempts to perform the Remote Operation and then reports the outcome of the attempt. Remote Operations are supported by the ROSE. This part of ISO/IEC 9072 is technically aligned with CCITT Recommendation X.219. iv INTERNATIONAL STANDARD IS0 / IEC 9072
15、-l : 1989 (E) Information processing systems -Text communication - Remote Operations - Part 1: Model, notation and service definition 1 Scope This part of ISO/IEC 9072 defines emote Operation (RO-) notation for defining t- -3rvices provided to interactive applications. This part of ISO/IEC 9072 also
16、 defines the services provided by the Remote Operation Service Element (ROSE) services. The ROSE services are provided by the use of the ROSE protocol (part 2 of ISO/IEC 9072) in conjunction with the Association Control Service Element (ACSE) services (IS0 8649) and the ACSE protocol (IS0 86501, opt
17、ionally the Reliable Transfer Service Element (RTSE) services (ISO/IEC 9066-l) and the RTSE protocol USO/IEC 9066-21, and the presentation-service (IS0 8822). No requirement is made for conformance to this part of ISO/IEC 9072. 2 Normative references The following standards contain provisions which,
18、 through reference in this text, constitute provisions of this part of ISO/IEC 9072. At the time of publication, the editions were valid. All Standards ar.e subject to revision, and parties to agreement based on this part of ISO/IEC 9072 are encouraged to investigate the possibility of applying the
19、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. ISO/TR 8509: 1987, Information processing systems - Open Sy
20、stems Interconnection - Service Conventions. 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 Interconnection - Protocol specification for the
21、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 of Abstract Syntax Notation One (ASN
22、.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-l: 1989, Information processing systems - Text communication - Reliable Transfer - Part 1: Model and service definition. I
23、SO/IEC 9066-2: 1989, Znformation processing systems - Text communication - Reliable Transfer - Part 2: Protocol specification. ISO/IEC 9072-2: 1989, Information processing systems - Text communication - Remote Operations -Part 2: Protocol specification. 3 Definitions 3.1 Reference Model definitions
24、This part of ISO/IEC 9072 is based on the concepts developed in IS0 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-protocol-data-unit; f, application-protocol-control-informa
25、tion; d Presentation Layer; 1 ISOAEC 9072-l : 1989 (E) h) presentation-service; i) presentation-connection; j) session-service; k) session-connection 1) transfer syntax; and m) user-element. 3.2 Service conventions definitions This part of ISO/IEC 9072 makes use of the following terms defined in ISO
26、/TR 8509. a) b) c) 4 e) f) g) h) i) j) 3.3 service-provider; service-user; confirmed service; non-confirmed service; provider-initiated service; service-primitive; primitive; request (primitive); indication (primitive); response (primitive); and confirm (primitive). Presentation service definitions
27、This part of ISO/IEC 9072 makes use of the following terms defined in IS0 8822: a) abstract syntax; bl abstract syntax name; cl transfer syntax name; dl presentation context. 3.4 Association control definitions This part of ISO/IEC 9072 makes use of the following terms defined in IS0 8649: a) applic
28、ation-association; association; b) 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-l: a) Reliable Transfer Service Element. 3.6 ROSE definitions For the purpose of this p
29、art of ISO/IEC 9072 the following definitions apply: 3.6.1 association-initiating-application- entity; association-initiator: The application- entity that initiates the application-association. 3.6.2 association-responding-application- entity; association-responder: The application- entity that resp
30、onds to the initiation of an application-association by another AE. 3.6.3 invoking-application-entity; invoker: The application-entity that invokes the Remote Operation. 3.6.4 performing-application-entity; performer: The application-entity that performs a Remote Operation invoked by the other appli
31、cation-entity. 3.6.5 requestor: The part of an application- entity that issues a request primitive for a particular ROSE service. 3.6.6 acceptor: The part of an application- entity that receives the indication primitive for a particular ROSE service. 3.6.7 linked-operations: A set of operations form
32、ed by one parent-operation and one or more child-operations. 3.6.8 parent-operation: An operation during the execution of which the performer may invoke linked child-operations to be performed by the invoker of the parent-operation. 3.6.9 child-operation: An operation which might be invoked by the p
33、erformer of the linked parent-operation during the execution of the parent-operation, and which is performed by the invoker of the parent-operation. 2 ISO/IEC 9072-I : 1989 (E) 3.6.10 Remote Operations: (1) A concept and notation supporting the specification of interactive communication between appl
34、ication-entities. This includes the Remote Operation Service Element and the mapping of the notation onto the service primitives of used application-service-elements. (2) The set of bind-operations, unbind-operations and operations. 3.6.11 RO-notation: The notation lled for the specification of Remo
35、te Operations, dl d in this part of ISO/IEC 9072. 3.6.12 ACSE-user: The application-specific function that performs the mapping of the bind- operation and unbind-operation of the RO- notation onto ACSE. 3.6.13 Remote Operation Service Element: The application-service-element defined in this part of
36、ISO/IEC 9072. 3.6.14 ROSE-provider: The provider of the Remote Operations Service Element services. 3.6.15 ROSE-user: The application-specific function that performs the mapping of the operations and errors of the RO-notation onto ROSE. 3.6.16 RTSE-user: The application-specific function that perfor
37、ms the mapping of the bind- operation and unbind-operation of the RO- notation onto RTSE. 3.6.17 operation-interface: The interface within an application entity between the user element and the application service elements, defined as a set of application service element services (Remote Operations)
38、 available to the user element in RO-notation. 4 Abbreviations AE ACSE ASE APDU OS1 RO (or ROS) ROSE RT (or RTS) RTSE application-entity Association Control Service Element application-service-element application-protocol-data-unit Open Systems Interconnection Remote Operations Remote Operations Ser
39、vice Element Reliable Transfer Reliable Transfer Service Element 5 Conventions This part of ISO/IEC 9072 defines services for the ROSE following the descriptive conventions defined in ISO/TR 8509. In clause 10, the definition of each ROSE service includes a table that lists the parameters of its pri
40、mitives. For a given primitive, the presence of each parameter is described by one of the following values. blank not applicable M mandatory U user option C conditional 0 presence is an ROSE service-provider option In addition, the notation (=) indicates that a parameter value is semantically equal
41、to the value to its left in the table. 3 ISOAEC 9072-l : 1989 (E) 6 Remote Operations Model In the OS1 environment, communication between application processes is represented in terms of communication between a pair of application entities (AEs) using the presentation service. Communication between
42、some application- entities are inherently interactive. Typically, one entity requests that a particular operation be performed; the other entity attempts to perform the operation and then reports the outcome of the attempt. This clause introduces the concept of Remote Operations as a vehicle for sun
43、norting interactive applications, The generic structure of an operation is an elementary request/reply interaction. Operations are carried out within the context of an application-association. Figure 1 models this view. Operations invoked by one AE (the invoker) are performed by the other AE (the pe
44、rformer). Operations may be classified according to whether the performer of an operation is expected to report its outcome: - in case of success or failure (a result reply is returned if the operation is successful, an error reply is returned if the operation is unsuccessful); - in case of failure
45、only (no reply is returned if the operation is successful, an error reply is returned if the operation is unsuccessful); - in case of success only (a result reply is returned if the operation is successful, no reply is returned if the operation is unsuccessful); - or not at all (neither a result nor
46、 an error reply is returned, whether the operation was successful or not). Operations may also be classified according to two possible operation modes: synchronous, in which the invoker requires a reply from the performer before invoking another operation; and asynchronous, in which the invoker may
47、continue to invoke further operations without awaiting a reply. The following Operation Classes are defined: Operation Class 1: Synchronous, reporting success or failure (result or error). Operation Class 2: Asynchronous, reporting success or failure (result or error). Operation Class 3: Asynchronou
48、s, reporting failure (error) only, if any. Operation Class 4: Asynchronous, reporting success (result) only. Operation Class 5: Asynchronous, outcome not reported. The Operation Class of each operation has to be agreed between application entities (e.g. in an Application Protocol International Stand
49、ard). In some cases it is useful to group operations into a set of linked-operations which is formed by one parent-operation and one or more child- operations. The performer of the parent-operation may invoke none, one, or more child-operations i i I application-association I request AE c 1 A-1 reply I I Figure 1 - Remote Operations Model ISO/IEC 9072-l : 1989 (E) during the execution of the parent-operation. The invoker of the parent-operation is the performer of the child-operations. A child-operation may be a parent-operation of another set of linked- operations in a recursive manner.
