ISO/IEC 9072-1:1989
(Main)Information processing systems — Text communication — Remote Operations — Part 1: Model, notation and service definition
Information processing systems — Text communication — Remote Operations — Part 1: Model, notation and service definition
This part of ISO/IEC 9072 defines a Remote Operation (RO-) notation for defining the services provided to interactive applications. This part of ISO/IEC 9072 also 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 (ISO 8649) and the ACSE protocol (ISO 8650), optionally the Reliable Transfer Service Element (RTSE) services (ISO/IEC 9066-1) and the RTSE protocol (ISO/IEC 9066-2), and the presentation-service (ISO 8822). No requirement is made for conformance to this part of ISO/IEC 9072.
Systèmes de traitement de l'information — Communication de texte — Opérations à distance — Partie 1: Modèle, notation et définition du service
La présente partie de l'ISO/CEI 9072 définit une notation d'opération distante (RO) pour définir les services fournis à des applications interactives. Cette partie de l'ISO/CEI 9072 définit encore les services fournis par les services de l'élément de service d'opérations distantes (ROSE) (partie 2 de l'ISO/CEI 9072) en liaison avec les services de l'élément de service de contrôle d'association (ACSE) (ISO 8649) et avec le contrôle ACSE (ISO 8650), optionnellement avec les services de l'élément de service de transfert fiable (RTSE) (ISO/CEI 9066-1) et avec le protocole RTSE (ISO/CEI 9066-2) et avec le service de présentation (ISO 8822). Aucune condition n'est spécifiée en ce qui concerne la conformité à la présente partie de l'ISO/CEI 9072.
General Information
Relations
Standards Content (Sample)
INTERNATIONAL lSO/lEC
9072-I
STANDARD
First edition
1989-l l-15
Information processing systems - Text
communication - Remote Operations -
Part 1 :
Model, notation and service definition
S yst&mes de traitemen t de l’information - Communication de texte - Opbrations
;i distance -
Partie I : Modkle, notation et d6 finition du service
Reference number
ISO/IEC 9072-l : 1989 (E)
ISOAEC 9072-l: 1989 (E)
Page
Contents
...
ill
Foreword .
iv
Introduction .
1 Scope .
. . . . .*.*.*.
9 Y Normative references
3 Definitions .
4 Abbreviations .
5 Conventions .
.....................................
6 Remote Operations Model
..............................
7 Overview of notation and service
........ 9
8 Relationship with other ASEs and lower layer services
..................................
9 Remote Operations notation
............................................
10 Service definition
Mapping of notation on service .
12 Sequencing information .
Annexes
A Notation supporting the specification of
. . . . . . . . 26
Application-service-elemnts and application-contexts
Guidelines for application protocol designers
B
on the use of ROSE . . . . . . . . . . . . . . . . . .*.
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 mechanical, including photocopying and microfilm, without permission in
writing from the publisher.
ISO/IEC Copyright Office l Case postale 56 l CH-1211 Geneve 20 l Switzerland
Printed in Switzerland
ii
lSO/IEC 90724 : 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 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, 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 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 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, information technology.
. . .
III
ISOAEC 9072-l : 1989 (E)
Introduction
This part of ISO/IEC 9072 defines a notation 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 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 Operation 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.
ISO/IEC9072-1: 1989(E)
INTERNATIONAL STANDARD
Information processing systems -Text communication -
Remote Operations - Part 1:
Model, notation and service definition
IS0 8650: 1988, Information processing systems -
1 scope
Open Systems Interconnection - Protocol
specification for the Association Control Service
This part of ISO/IEC 9072 defines a Remote
Element.
Operation (RO-) notation for defining the services
provided to interactive applications. This part of
IS0 8822: 1988, rnformation processing systems -
ISO/IEC 9072 also defines the services provided
Open Systems interconnection - Connection
by the Remote Operation Service Element (ROSE)
oriented presentation service definition.
services. The ROSE services are provided by the
IS0 8824: 1987, Information processing systems -
use of the ROSE protocol (part 2 of ISO/IEC 9072)
Open Systems Interconnection - Specification of
in conjunction with the Association Control
Abstract Syntax Notation One (ASN.1).
Service Element (ACSE) services (IS0 8649) and
the ACSE protocol (IS0 8650), optionally the
IS0 8825: 1987, Information processing systems -
Reliable Transfer Service Element (RTSE)
Open Systems Interconnection - Specification of
services (ISO/IEC 9066-l) and the RTSE protocol
basic encoding rules for Abstract Syntax Notation
(ISO/IEC 9066-2), and the presentation-service
One (ASN.1).
(IS0 8822).
ISO/IEC 9066-l: 1989, Information processing
systems - Text communication - Reliable Transfer
No requirement is made for conformance to this
- Part 1: Model and service definition.
part of ISO/IEC 9072.
ISO/IEC 9066-2: 1989, Information processing
Normative references
systems - Text communica.tion - Reliable Transfer
- Part 2: Protocol specificatton.
The following standards contain provisions which,
through reference in this text, constitute ISO/IEC 9072-2: 1989, Information processing
provisions of this part of ISO/IEC 9072. At the systems - Text communication - Remote
time of publication, the editions were valid. All Operations -Part 2: Protocol specification.
Standards are subject to revision, and parties to
agreement based on this part of ISO/IEC 9072 are 3 Definitions
encouraged to investigate the possibility of
applying the most recent editions of the standards 31 . Reference Model definitions
listed below. Members of IS0 and IEC maintain
This part of ISO/IEC 9072 is based on the concepts
Registers of currently valid International
developed in IS0 7498 and makes use of the
Standards.
following terms defined in it:
IS0 7498: 1984, Information processing systems -
Application Layer;
a)
Open Systems Interconnection - Basic Reference
b) application-process;
Model.
application-entity;
ISO/TR 8509: 1987, Information processing 4
systems - Open Systems interconnection - Service
d) application-service-element;
Conventions.
application-protocol-data-unit;
e>
IS0 8649: 1988, Information processing systems -
application-protocol-control-information;
Open Systems Interconnection - Service definition f)
for the Association Control Service Element.
Presentation Layer;
g)
ISOAEC 9072-l : 1989 (E)
presentation-service; 35 . Reliable Transfer definitions
h)
presentation-connection; This part of ISO/IEC 9072 makes use of the
i>
. following terms defined in ISO/IEC 9066-l:
session-service;
J)
Reliable Transfer Service Element
a)
k) session-connection
transfer syntax; and 36 . ROSE definitions
1)
user-element.
m)
For the purpose of this part of ISO/IEC 9072 the
following definitions apply:
3.2 Service conventions definitions
3.6.1 association-initiating-application-
This part of ISO/IEC 9072 makes use of the
entity; association-initiator: The application-
following terms defined in ISO/TR 8509:
entity that initiates the application-association.
service-provider;
a)
service-user; 3.6.2 association-responding-application-
b)
entity; association-responder: The application-
confirmed service;
entity that responds to the initiation of an
non-confirmed service; application-association by another AE.
d)
provider-initiated service;
3.6.3 invoking-application-entity; invoker:
service-primitive; primitive; The application-entity that invokes the Remote
fl
Operation.
request (primitive);
g)
indication (primitive); 3.6.4 performing-application-entity;
h)
performer: The application-entity that performs
response (primitive); and
i)
a Remote Operation invoked by the other
.
confirm (primitive). application-entity.
J)
Presentation service definitions 3.6.5 requestor: The part of an application-
33 .
entity that issues a request primitive for a
This part of ISO/IEC 9072 makes use of the
particular ROSE service.
following terms defined in IS0 8822:
3.6.6 acceptor: The part of an application-
a) abstract syntax;
entity that receives the indication primitive for a
abstract syntax name;
b)
particular ROSE service.
transfer syntax name;
C)
3.6.7 linked-operations: A set of operat’ions
presentation context.
d)
formed by one parent-operation and one or more
child-operations.
. Association control definitions
This part of ISO/IEC 9072 makes use of the 3.6.8 parent-operation: An operation during
following terms defined in IS0 8649: the execution of which the performer may invoke
linked child-operations to be performed by the
application-associ .ation; association;
a)
invoker of the parent-operation.
application context;
b)
3.6.9 child-operation: An operation which
Association Control Service Element.
c)
might be invoked by the performer of the linked
parent-operation during the execution of the
parent-operation, and which is performed by the
invoker of the parent-operation.
ISO/lEC 90724 : 1989 (E)
3.6.10 Remote Operations: services (Remote Operations) available to the user
element in RO-notation.
(1) A concept and notation supporting the
specification of interactive communication 4 Abbreviations
between application-entities. This includes the
Remote Operation Service Element and the AE application-entity
mapping of the notation onto the service
ACSE Association Control Service
primitives of used application-service-elements.
Element
(2) The set of b’ in d -operations, unbind-operations ASE application-service-element
and operations.
APDU application-protocol-data-unit
3.6.11 RO-notation: The notation used for the OS1 Open Systems Interconnection
specification of Remote Operations, defined in this
RO (or ROS) Remote Operations
part of ISO/IEC 90’72.
ROSE Remote Operations Service
3.6.12 ACSE-user: The application-specific Element
function that performs the mapping of the bind-
RT (or RTS) Reliable Transfer
operation and unbind-operation of the RO-
Reliable Transfer Service Element
notation onto ACSE. RTSE
A l
3.6.13 Remote Operation Service Element: 5 Conventions
The application-service-element defined in this
part of ISO/IEC 9072. This part of ISO/IEC 9072 defines services for the
ROSE following the descriptive conventions
3.6.14 ROSE-provider: The provider of the defined in ISO/TR 8509. In clause 10, the
Remote Operations Service Element set-vices. definition of each ROSE service includes a table
that lists the parameters of its primitives. For a
3.6.15 ROSE-user: The application-specific given primitive, the presence of each parameter is
function that performs the mapping of the described by one of the following values.
operations and errors of the RO-notation onto
blank not applicable
ROSE.
NI mandatory
3.6.16 RTSE-user: The application-specific
U user option
function that performs the mapping of the bind-
operation and unbind-operation of the RO- C conditional
notation onto RTSE.
presence is an ROSE service-provider
option
3.6.1’7 operation-interface: The interface
within an application entity between the user
In addition, the notation (=) indicates that a
element and the application service elements,
parameter value is semantically equal to the
defined as a set of application service element
value to its left in the table.
ISOAEC 9072-l : 1989 (E)
6 Remote Operations Model reply is returned if the operation is
unsuccessful);
In the OS1 environment, communication between
- or not at all (neither a result nor an error
application processes is represented in terms of
reply is returned, whether the operation
communication between a pair of application
was successful or not).
entities (AEs) using the presentation service.
Communication between some application-
Operations may also be classified according to two
entities are inherently interactive. Typically, one
possible operation modes: synchronous, in which
entity requests that a particular operation be
the invoker requires a reply from the performer
performed; the other entity attempts to perform
before invoking another operation; and
the operation and then reports the outcome of the
asynchronous, in which the invoker may continue
attempt. This clause introduces the concept of
to invoke further operations without awaiting a
Remote Operations as a vehicle for supporting
reply.
interactive applications.
The following Operation Classes are defined:
The generic structure of an operation is an
elementary request/reply interaction. Operations Operation Class 1: Synchronous, reporting
are carried out within the context of an success or failure (result or error).
application-association.
Operation Class 2: Asynchronous, reporting
success or failure (result or error).
Figure 1 models this view.
Operation Class 3: Asynchronous, reporting
Operations invoked by one AE (the invoker) are failure (error) only, if any.
performed by the other AE (the performer).
Operation Class 4: Asynchronous, reporting
Operations may be classified according to whether
success (result) only.
the performer of an operation is expected to report
its outcome: Operation Class 5: Asynchronous, outcome
not reported.
- in case of success or failure (a result reply
is returned if the operation is successful,
The Operation Class of each operation has to be
an error reply is returned if the operation
agreed between application entities (e.g. in an
is unsuccessful);
Application Protocol International Standard).
- in case of failure only (no reply is returned
if the operation is successful, an error In some cases it is useful to group operations into
reply is returned if the operation is a set of linked-operation
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.