ISO/IEC 9072-2:1989

Information processing systems — Text communication — Remote Operations — Part 2: Protocol specification

This part of ISO/IEC 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 (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). The ROSE procedures are defined in terms of a) the interactions between peer ROSE protocol machines through 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.

Systèmes de traitement de l'information — Communication de texte — Opérations à distance — Partie 2: Spécification du protocole

La présente partie de l'ISO/CEI 9072 spécifie le protocole (syntaxe abstraite) et les procédures applicables à l'élément de service d'opérations distantes (partie 1 de cette Norme internationale). Les services ROSE sont fournis en liaison avec les services de l'élément de service de contrôle d'association (ACSE) (ISO 8649) et avec le protocole 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), ainsi qu'avec le service de présentation (ISO 8822). Les procédures ROSE sont définies sous la forme a) des interactions entre machines protocole ROSE homologues par l'emploi des services RTSE ou du service de présentation ; b) des interactions entre la machine protocole ROSE et son utilisateur de service. La présente partie de l'ISO/CEI 9072 spécifie les conditions de conformité applicables aux systèmes qui mettent en oeuvre ces procédures.

General Information

• Status: Withdrawn
• Publication Date: 08-Nov-1989
• Withdrawal Date: 08-Nov-1989
• ICS: 35.240.20 - IT applications in office work
• Technical Committee: ISO/IEC JTC 1 - Information technology
• Drafting Committee: ISO/IEC JTC 1 - Information technology
• Current Stage: 9599 - Withdrawal of International Standard
• Completion Date: 29-Jul-2020

Relations

• Revised: ISO/IEC 13712-1:1995 - Information technology — Remote Operations: Concepts, model and notation
• Effective Date: 15-Apr-2008

Standards Content (Sample)

INTERNATIONAL lSO/IEC
9072-2
STANDARD
First edition
1989-11-15
Information processing systems - Text
Remote Operations -
communication -
Part 2 :
Protocol specification
S ysthmes de traitement de l’information - Communication de texte - Ophations
a distance -
Partie 2 : Spkification du protocole
---
_-.-
-
-
-
=. -&
=
E
=
= =
= =
=
=
I
E
=
g
E
=
E
Reference number
=
s
s
s -
:@
ISO/IEC 9072-2 : 1989 (E)
ISOAEC 9072-2: 1989 (E)
Page
Contents
...
ill
Foreword .
iv
Introduction .
1 Scope .
2 Normative references .
3 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .*.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .*.*.
5 Conventions
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6 Overview of the protocol
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7 Elements of procedure
.....................................
8 Mapping to used services
.........................
9 Abstract syntax definition of APDUs
. .*.*.*.
10 Conformance
Annexes
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
A ROPM State tables
B Differences between this part of ISO/IEC 9072 and
. . . . . . . . . . . . . . . . . . . . . . . . . 27
CCITT Recommendation X.410 - 1984
. . . . . . . . . . . . . . . . . 28
C Summary of assigned object identifier values
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/lEC Copyright Office l Case postale 56 l CH-1211 Gen&ve 20 l Switzerland
Printed in Switzerland
ii
ISOAEC 9072-2: 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, ISOAEC 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-2 was prepared by Joint Technical
Committee ISO/IEC JTC 1, information technology.
. . .
III
This page intentionally left blank

INTERNATIONAL STANDARD IS0 / IEC 9072-2: 1989 (E)
Information processing systems -Text communication -
Remote Operations - Part 2:
Protocol specification
ISO/IEC 7498: 1984, Inform&on processing
1 Scope
systems - Open Systems interconnection - Basic
Reference Model.
This part of ISO/IEC 9072 specifies the protocol
(abstract syntax) and procedures for the Remote
ISO/TR 8509: 1987, Information processing
Operation Service Element (part 1 of this
systems - Open Systems lnterconn.ection - Service
International Standard). The ROSE services are
Conventions.
provided in conjunction with the Association
Control Service Element (ACSE) services (IS0 IS0 8649: 1988, Information processing systems -
8649) and the ACSE protocol (IS0 8650), Open Systems Interconnection - Service definition
optionally the Reliable Transfer Service Element for the Association Control Service Element.
(RTSE) services (ISO/IEC 9066-l) and the RTSE
IS0 8650: 1988, Information processing systems -
protocol (ISO/IEC 9066-2), and the presentation-
Open Systems Interconnection - Protocol
service (IS0 8822 j.
specification for the Association Control Service
Element.
The ROSE procedures are defined in terms of
IS0 8822: 1988, Information processing systems -
a) the interactions between peer ROSE
Open Systems Interconnection - Connection
protocol machines through the use of
orientedbresentation service definition.
RTSE services or the presentation-service;
IS0 8824: 1987, Information processing systems -
b) the interactions between the ROSE
Open Systems Interconnection - Specification of
protocol machine and its service-user.
Abstract Syntax Notation One (ASN.1).
This part of ISO/IEC 9072 specifies conformance IS0 8825: 1987, Information processing systems -
requirements for systems implementing these Open Systems Interconnection - Specification of
basic encoding rules for Abstract Syntax Notation
procedures.
One (ASN.1).
Normative references
ISO/IEC 9066-l: 1989, Informa.tion processing
systems - Text communication - Reliable Transfer
The following standards contain provisions which,
- Part 1: Model and service definition. *,
through reference in this text, constitute
ISOIIEC 9066-2: 1989, Information processing
provisions of this part of ISO/IEC 9072. At the
systems - Text communication - Reliable Transfer
time of publication, the editions were valid. All
-Part 2: Protocol specification.
Standards are subject to revision, and parties to
agreement based on this part of ISO/IEC 9072 are
ISO/IEC 9072-l: 1989, Information processing
encouraged to investigate the possibility of
Text communication - Remote
systems -
applying the most recent editions of the standards
Part 1: Model, notation and service
Operations -
listed below. Members of IS0 and IEC maintain
definition.
Registers of currently valid International
Standards.
ISO/IEC 9072-2: 1989 (E)
34 . Association control definitions
3 Definitions
This part of ISO/IEC 9072 makes use of the
31 . Reference Model definitions
following terms defined in IS0 8649:
This part of ISO/IEC 9072 is based on the concepts
application-association; association;
a)
developed in ISO/IEC 7498 and makes use of the
b) application context;
following terms defined in it:
Association Control Service Element.
Application Layer; c)
a)
b) application-process;
3.5 Reliable Transfer definitions
application-entity;
c)
This part of ISO/IEC 9072 makes use of the
following terms defined in ISO/IEC 9066-l:
d) application-service-element;
Reliable Transfer Service Element.
application-protocol-data-unit; a)
e)
application-protocol-control-information;
f)
3.6 ROSE service definitions
g) presentation-service;
This part of ISO/IEC 9072 makes use of the
following terms defined in ISO/IEC 9072-l:
h) presentation-connection;
association-initiating-application-entity;
a)
session-service;
association-init.iator;
.
session-connection;
J)
b) association-responding-application-
k) transfer syntax; and
entity; association-responder;
user-element.
1)
invoking-application-entity; invoker;
cl
d) performing-application-entity; performer;
3.2 Service conventions definitions
requestor;
This part of ISO/IEC 9072 makes use of the 4
following terms defined in ISO/TR 8509:
f) acceptor;
service-provider;
a)
linked-operations;
g)
b) service-user;
h) parent-operation;
confirmed service;
c)
child-operation;
.
non-confirmed service;
d)
RO-notation;
J)
provider-initiated service;
Remote Operation Service Element;
k)
f) primitive;
ROSE-provider;
1)
request (primitive);
g)
m) ROSE-user;
h) indication (primitive);
RTSE-user;
d
response (primitive); and
Remote Operations.
0)
.
confirm (primitive).
J)
Remote Operation protocol
37 .
specification definitions
33 . Presentation service definitions
For the purpose of this part of ISO/IEC 9072 the
This part of ISO/IEC 9072 makes use of the
following definitions apply:
following terms defined in IS0 8822:
abstract syntax;
a)
3.7.1 remote-operation-protocol-machine:
The protocol machine for the Remote Operation
b) abstract syntax name;
Service Element specified in this part of ISO/IEC
presentation context.
cl
9072.
ISOAEC 9072-2: 1989 (E)
3.7.2 requesting-remote-operation- 5 Conventions
protocol-machine: The remote-operation-
protocol-machine whose service-user is the This part of ISO/IEC 9072 employs a tabular
presentation of its APDU fields. In clause 7, tables
requestor of a particular Remote Operation
are presented for each ROSE APDU. Each field is
Service Element service.
summarized using the following notation:
3.7.3 accepting-remote-operation-protocol-
M presence is mandatory
machine: The remote-operation-protocol-
U presence is a ROSE-user option
machine whose service-user is the acceptor for a
particular Remote Operation Service Element
source is related request primitive
req
service.
ind sink is related indication primitive
4 Abbreviations
source is related response primitive
resp
sink is related confirm primitive
41 . Data units conf
source or sink is the ROPM
APDU application-protocol-data-unit
SP
4.2 Types of application-protocol-data- The structure of each ROSE APDU is specified in
units clause 9 using the abstract syntax notation of
ISO/IEC 8824.
The following abbreviations have been given to
the application-protocol-data-units defined in this
6 Overview of the protocol
part of ISO/IEC 9072.
ROIV RO-INVOKE application-protocol- 61 . Service provision
data-unit
The protocol specified in this part of ISO/IEC 9072
RORS RO-RESULT application-protocol- provides the ROSE services defined in ISO/IEC
data-unit 9072-l. These services are listed in table 1.
RO-ERROR application-protocol-data-
ROER
unit
Table 1 - ROSE services summary
RO-REJECT application-protocol-
RORJ
data-unit
Service
Type
I I
43 . Other abbreviations
RO-IXVOKE Non-confirmed
The following abbreviations are used in this part
RO-RESULT LNon-confirmed
of ISO/IEC 9072.
RO-ERROR Non-confirmed
RO-REJECT-C’ Non-confirmed
AE Application Entity
RO-REJECT-P Provider-initiated
ACSE Association Control Service
Element
6.2 Use of services
ASE Application Service Element
The ROSE protocol specified in this part OI
RO (or ROS) Remote Operations
ISO/IEC 9072 needs a transfer service to pass
ROPM Remote Operations Protocol
information in the form of ROSE APDUs between
Machine
peer application-entities (AEs).
ROSE Remote Operations Service
Two transfer services may be used alternatively:
Element
a) the RTSE services, if the RTSE is
RT Reliable Transfer
included in the application-context, or
Reliable Transfer Service Element
RTSE
the presentation-service, if the RTSE is
b
not included in the application-context.
ISO/IEC 9072-2: 1989 (E)
issues indication primitives to its service-user,
In both cases an existing application-association,
and request primitives on the used RTSE services,
established and released by means of the ACSE
or the presentation-service. If the RTSE is
services, is assumed.
included in the application-context, the RT-
TRANSFER indication, RT-TRANSFER request
6.2.1 Use of the RTSE services
and RT-TRANSFER confirm primitives are used.
If the RTSE is included in the application-context,
In the case of an application-context excluding
this part of ISO/IEC 9072 assumes that the ROPAM
RTSE, the presentation-service P-DATA request,
is the sole user of the RT-TRANSFER service and
and P-DATA indication primitives are used. In
the RT-TURN-GIVE service.
this case the transfer is not confirmed.
The initiating AE may only request the release of
The reception of a ROSE service primitive, or of a
the application-association by means of the RT-
RTSE service or of a presentation-service
CLOSE service if it possesses the Turn. Therefore
primitive, and the generation of dependent
the RTSE-user and the ROPM are the user of the
actions are considered to be indivisible.
RT-TURN-PLEASE service.
During the exchange of APDUs, the existence of
The ROPM is the user of the RT-U-ABORT and
both, the association-initiating AE and the
RT-P-ABORT services.
association-responding AE is presumed. How
these AEs are created is beyond the scope of this
6.2.2 Use of the presentation-service
part of ISO/IEC 9072.
If the RTSE is not included in the
application-context, the ROPM is a user of the P- During the execution of operations, the existence
DATA service. of an application-association between the peer
How this application-
AEs is presumed.
63 . Model association is established and released is beyond
the scope of this part of ISO/IEC 9072 (see
The remote-operation-protocol-machine (ROPM)
ISO/IEC 9072-1, IS0 8649, IS0 8650, ISO/IEC
communicates with its service-user by means of
9066-l and ISO/IEC 9066-Z).
primitives defined in ISO/IEC 9072-L Each
invocation of the ROPM controls a single
NOTE Each application-association may be identified in an
application-association.
end system by an internal, implementation
dependent mechanism so that the ROSE service-user
The ROPM is driven by ROSE service request
and the ROPE can refer to it.
primitives from its service-user, and by indicatifm
and confirm primitives of the RTSE services, or
the presentation-service. The ROPM, in turn,
ISOAEC 9072-2: 1989 (E)
b) a ROIV APDU as user-data of a transfer
7 Elements of procedure
indication primitive.
The ROSE protocol consists of the following
7.1.3.1 RO-INVOKE request primitive
elements of procedure:
a) invocation
Table 2 - RON APDCr fields
b) return-result
return-error
d
Pre-
user-reject
d) Field name Source Sink
sence
prov ,ider-reject.
e)
Invoke-ID M ind
req
In the following clauses, a summary of each of
Linked-ID U ind
req
these elements of procedure is presented. This
Operation-value M ind
req
consists of a summary of the relevant APDUs, and
Argument U ind
req
a high-level overview of the re
...