ISO/IEC ISP 11188-3:1996

INTERNATIONAL ISO/IEC
STANDARDIZED ISP
PROFILE 11188-3
First edition
1996-03-o 1
Information technology - International
Standardized Profile - Common upper
layer requirements -
Part 3:
Minimal OSI upper layer facilities
Technologies de I’informa tion - Profil normalis in temational -
Prescriptions communes pour la couche supbrieure -
Partie 3: Facilit& minima/es pour la couche supbieure OS/
Reference number
lSO/IEC ISP 11188-3:1996(E)
ISO/IEC ISP 11188-3 : 1996 (E)
Contents
Page
iV
.........................................................................................................................................................
Foreword
V
.......................................................................................................................................................
Introduction
1 Scope .
1.1 General .
...........................................................................................................
1.2 Position within the taxonomy
........................................................................................................................
2 Compliance and conformance
.........................................................
2.1 Profile or specification of a basic communications application
..............................................................................................
2.2 OS1 upper layer stack implementation
..............................................................................................................
2.3 Facilities, roles and options
.........................................................................................................
2.4 Relationship to base standards
2.4.1 ACSE .
2.4.2 Presentation layer .
....................................................................................................................
2.4.3 Session layer
...........................................................................................................................
2.5 Transport-provider
.....................................................................................................................................
3 Normative references
......................................................................
3.1 Identical Recommendations 1 International Standards
.......................... 5
3.2 Paired Recommendations 1 International Standards equivalent in technical content
.......................................................................................................................
3.3 Additional references
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 Definitions
.............................................................................................................
4.1 Reference model definitions
...................................................................................
4.1.1 Basic Reference Model definitions
4.1.2 Naming and addressing definitions .
........................................................................................................
4.2 Service conventions definitions
....................................................................................................................
4.3 Presentation definitions
...........................................................................................................................
4.4 Session definitions
..............................................................................................
4.5 Application layer structure definitions
.................................................................................................................
4.6 ACSE service definitions
.......................................................................................................
4.7 Taxonomy of profile definitions
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.8 Definitions of this part of ISOLIEC ISP 11188
5 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .*.
..................................................................................................................................................
6 Conventions
....................................................................................................................
6.1 Profile status indicators
...................................................................................................................
6.2 Definitions of variables
.................................................................................................................
6.3 Definition of mnemonics
7 Model .
..........................................................................................................................
7.1 Common elements
..................................................................................................................
7.2 Standalone applications
............................................................................................................
7.3 Platform-based applications
.......................................................................................................
7.3.1 Migrant applications
7.3.2 Kernel application .
0 ISOIIEC 1996
All rights reserved. Unless otherwise specified, 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 Offke l Case postale 56 l CH-1211 Genkve 20 l Switzerland
Printed in Switzerland
ii
ISO/IEC ISP 11188-3 : 1996 (E)
0 ISO/IEC
Annexes
mOS1 Requirements for ACSE facilities .
A
..............................................................................
B mOS1 requirements for Presentation layer facilities
.....................................................................................
mOS1 requirements for Session layer facilities
C
........................................................................................................
D Profile requirements list proforma
................................................................................
E Implementation conformance statement proforma
.............................................................................................................
F Minimal OSI object identifiers
..........................................................................................................................
G Minimal OS1 concepts
.............................................................................................................
H Implementation considerations
. . .
Ill
ISO/IEC ISP 11188-3 : 1996 (E) 0 ISO/IEC
Foreword
IS0 (the International Organization for Standardization) and IEC (the International Electrotechnical Commission)
form the specialized system for worldwide standardization. National bodies that are members of IS0 or IEC
participate in the development 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 or 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 JTCl.
In addition to developing International Standards, ISO/IEC JTCl has created a Special Group on Functional
Standardization for the elaboration of International Standardized Profiles.
An International Standardized Profile is an internationally agreed, harmonized document which identifies a
standard or group of standards, together with options and parameters, necessary to accomplish a function or set of
functions.
Draft International Standardized Profiles are circulated to national bodies for voting. Publication as an
International Standardized Profile requires approval by at least 75% of the national bodies casting a vote.
International Standardized Profile ISO/ISP 11188-3 was prepared with the collaboration of
Asia-Oceania Workshop (AOW);
European Workshop for Open Systems (EWOS);
Open Systems Environment Implementors’ Workshop (OIW).
ISO/IEC ISP 11188 consists of the following parts, under the general title Information technology - International
Standardized Profile - Common upper layer requirements:
Part I: Basic connection oriented requirements
Part 2: Basic connection oriented requirements for ROSE-based Profiles
Part 3: Mnimal OSI upper layer facilities
Annexes A, B, C , D, E and F form an integral part of this part of ISO/IEC ISP 11188. Annexes G and H are for
information only.
1V
ISO/IEC ISP 11188-3 : 1996 (E)
0 ISOKEC
Introduction
This part of ISO/IEC ISP 11188 is defmed within the context of Functional Standardization, in accordance with
the principles specified by ISO/IEC TR 10000, Framework and Taxonomy of International Standardized ProJiles.
The context of Functional Standardization is one part of the overall field of Lnformation Technology (IT)
standardization activities, covering base standards, profiles, and registration mechanisms. A profile defines a
combination of base standards that collectively perform a specific, well-defined IT function. Profiles standardize
the use of options and other variations in the base standards, and provide a basis for the development of uniform,
internationally recognized system tests.
A profile (e.g., an ISO/IEC ISP) or the specification of a basic communications application may reference this
part of ISO/IEC ISP 11188. In addition, a referencing ISP may specify further requirements on the protocols,
provided it does not contradict this part of ISO/IEC ISP 11188. A specification of an implementation may also
reference this part of ISO/IEC ISP 11188.
The purpose of ISO/IEC ISP 11188 is to provide common text for ISPs or other referencing specifications which
specify A-profiles. In addition to simplifying their drafting, it also facilitates the common implementation of the
protocols for use in different A-profile contexts.
This part of ISO/IEC 11188 specifies a profile of the minimal OS1 facilities supporting basic connection-oriented
communications applications. These facilities are comprised of a subset of the facilities defined by the ACSE,
Presentation, and Session service definitions.

This page intentionally left blank

INTERNATIONAL STANDARDIZED PROFILE @ISo/aX ISO/IEC ISP 11188-3 : 1996 (E)
Information technology-International Standardized Profile-Common upper
layer requirements-
Part 3:
Minimal OS1 upper layer facilities
1 Scope
This part of ISO/IEC ISP 11188 introduces the concept of the minimal set of OS1 upper layer facilities1 for basic
communications applications. A basic communications application simply requires the ability to open and close
connection-oriented communications with a peer and to send and receive messages with the peer. It is expected
that a large portion of potential OS1 applications will be basic communications applications.
11 . General
This part of ISO/IEC ISP 11188 specifies the minimal set of upper layer facilities
required for the support of basic
communications applications. The minimal OS1 facilities are referred to as mOS1.
This part of ISO/IEC ISP 11188 defines the mOS1 facilities in terms of identified
features of the upper layer PICS
proformas - the ACSE (ISO/IEC 8650.2), the Presentation layer (ISOLIEC 8823.2), and the Session layer
(ISWIEC 8327-2). The identified features of these PICS proformas are specified in annexes A, B, and C,
respectively.
This part of ISO/IEC ISP 11188 complies with the requirements stated in ISO/IEC ISP 11188-1, Basic connection
oriented requirements.
This part of ISO/IEC ISP 11188 may be referenced by two classes of entities: upper layer users and upper layer
providers.
mOSI users represent basic communications applications. mOS1 users may be profiles (such as
A-profiles identified in ISO/IEC TR 10000-2) or specifications of basic communications
applications that are not represented by a formal profile. An API specification is a special case of
the latter. The term referencing specification is used in this part of ISO/IEC ISP 11188 to
represent this set of mOS1 users.
mOS1 providers represent implementations of the upper layer facilities that provide (at a
minimum) the facilities defined in this part of ISO/IEC ISP 11188. The term referencing
implementation is used in this part of ISO/IEC ISP I1 188 to represent this set of mOS1
providers.
A referencing specification (a mOS1 user) may claim compliance2 to this part of ISO/IEC ISP 11188. It may do so
if the OS1 upper layer facilities that it requires can be expressed by the facilities of this part of ISO/IEC ISP 11188.
Subclause 2.1 summarizes the requirements for making such a statement. Annex D provides a proforma for a
profile requirements list (PRL) for a compliant application.
A referencing implementation (a mOS1 provider) may claim conformance3 to this part of ISO/IEC ISP 11188. It
may do so if the OS1 upper layer facilities that it provides include those expressed in this part of ISO/IEC ISP
11188. That is, an implementation may contain more upper layer facilities than those required to be conformant to
this part of ISO/IEC ISP 11188. However, they must contain at least those of this part of ISO/IEC ISP 11188.
er facilities considered in this part of ISOLEC ISP 11188 are ACSE, Presentation, and Session.
l The upper lay
2 Compliance deals with one specification referencing another specification.
3 Conformance deals with a physical implementation that references a particular specification.

ISO/IEC ISP 11188-3 : 1996 (E) 0 ISO/IEX
Annex F assigns object identifi .er values for specific generic deftitions of application context, abstract
and transfer syntax.
12 . Position within the taxonomy
This part of ISO/IEC ISP 11188 does not specify a full A-profile, and therefore is not included in the taxonomy of
ISO/IEC TR 10000-2.
2 Compliance and conformance
21 . Profile or specification of a basic communications application
A specification may reference this part of ISO/IEC ISP 11188 to identify its upper layer requirements and may
claim compliance to this part of ISOKEC ISP 11188.
To be compliant, a referencing specification shall do the following:
require that all of the mandatory (“m”) features for this part of ISO/IEC ISP 11188 are also
mandatory for the referencing specification;
require that all of the out of scope (‘Ii”) features for this part of ISO/IEC ISP 11188 are also out
W
of scope for the referencing specification;
require that all of the optional (“0”) features for this part of ISO/IEC ISP 11188 are kept as
C)
optional, i.e., they are not redefined by the referencing specification;
require that all of the open (I’*“) features for this part of ISO/IEC ISP 11188 are kept as open or
are re-defined as mandatory (“m”), optional (“0”) or out of scope (“i”); and
comply with the requirements of ISO/IEC ISP 11188-l and not conflict with the requirements of
e)
this part of ISO/IEC ISP 11 188.4
NOTES
1 The meaning of the status indicators (see 6.1) when used by a referencing specification is given in table 1
column 3.
2 It is recommended that a referencing specification use the tables in annex D to specify its profile
requirements list.
A referencing specification may be compliant with this part of ISOLEC ISP 11188 by either of the following
ways:
It may repeat all of the specifications contained in this part of ISO/IEC ISP 11188. To claim
a)
compliance to this part of ISO/IEC ISP I1 188, a referencing specification shall assure that its
specification of the ACSE, Presentation, and Session features does not violate those in this part
of ISO/IEC ISP 11188.
It may claim compliance by reference to this part of ISOLIEC ISP 11188 instead of repeating the
b)
provisions of this part of ISO/IEC ISP 11188.
NOTE
It is recommended that a referencing specification claim compliance with this part of ISO/IEC ISP 11188 by
referencing it instead of repeating its provisions.
22 . OS1 upper layer stack implementation
An implementation may reference this part of ISO/IEC ISP 11188 to claim that it supports some or all of the
features specified herein. The referencing implementation may in fact support additional upper layer features-
without violating any of those in this part of ISO/IEC ISP 11188.
To be conformant, a referencing implementation shall do the following:
4 See clause 2 an dAn.nexBinISO/IECISP 11188-l.
0 ISO/IEC ISO/IEC ISP 11188-3 : 1996 (E)
support all of the mandatory (“m”) features in this part of ISO/IEC ISP 11188;
follow the guidelines for support of the out of scope (‘Ii”) features outlined in table 1;
b)
follow the guidelines for support of the optional (“0”) features outlined in table 1;
Cl
follow the guidelines for support of the open (“*“) features outlined in table 1; and
conform to the requirements of ISO/IEC ISP 11188-l.
NOTE - It is recommended that a referencing implementation use the tables in annex E to summarize its profile
implementation conformance statement.
2.3 Facilities, roles and options
This part of ISO/IEC ISP 11188 defines mOS1 compliance and conformance in terms of facilities, roles and
options. This part of ISO/IEC ISP 11188 has three facilities:
association establishment;
user data transfer; and
W
association release.
C)
Association establishment includes two optional facilities:
authentication; and
a)
application context negotiation.
b)
Each facility has roles (Initiator/Responder and Requester/Acceptor). Within this part of ISO/IEC ISP 11188, each
role (or an optional facility) is referenced by a variable (see 6.1). For example, the variable name used to describe
the capability to establish an association is establishment-initiator.
The referencing specification assigns each variable one of the following values:
mandatory (“m”)
optional (“0”)
out of scope (“i”)
The meanings of these values are defmed in table 1.
mOS1 compliance and conformance can be determined by specifying values (“ml’, ‘IO”, or ‘5”) for all of these
variables.
24 . Relationship to base standards
ACSE
2.4.1
This part of ISO/IEC ISP 11188 includes rules for incorporating the Kernel functional unit. Optionally, it also
includes the Authentication functional unit and Application Context Name Negotiation functional unit. This part
of ISO/IEC ISP 11188 allows the roles for association establishment and release identified in ISO/IEC 8650.
The required facilities of ACSE are specified in annex A. A default value for application context name is defmed
in annex F. The requirements expressed in ISO/IEC ISP 11188-l also apply to the ACSE aspects of this part of
ISO/IEx ISP 11188.
2.4.2 Presentation layer
This part of ISO/IEC ISP 11188 includes rules for incorporating the Presentation Kernel functional unit.
The required facilities of Presentation layer are specified in annex B. Default values for user abstract syntax name
and user transfer syntax name are defined in annex F. The requirements expressed in ISO/IEC ISP 11188-l also
apply to the Presentation layer aspects of this part of ISO/IEC ISP 11188.
2.4.3 Session layer
This part of ISO/IEC ISP 11188 includes rules for incorporating the Session Kernel and Duplex functional units.
0 ISO/IEC
ISO/IEC ISP 11188-3 : 1996 (E)
The required facilities of Session layer are specified in annex C. The requirements expressed in ISO/IEC ISP
11188-l also apply to the Session layer aspects of this part of ISO/IEC ISP 11188.
25 . Transport-provider
This part of ISO/IEC ISP 11188 does not address the lower four OS1 layers (Transport, Network, Link, and
Physical layers). They are outside of the scope of this part of ISO/IEC ISP 11188 (see also clause 7).
A transport-provider is needed to support the exchange of ACSE, Presentation, and Session PDUs for a conformant
mOS1 implementation. To meet this requirement, the transport-provider shall supply services equivalent to those
defined in the OS1 Transport layer service definition (ITU-T Rec. X.2 14 1 IS0 8072).
3 Normative references
The following documents contain provisions which, through reference in this text, constitute provisions of this
International Standardized Profile. At the time of publication, the editions indicated were valid. All documents are
subject to revision, and parties to agreements based on this International Standardized Profile are warned against
automatically applying any more recent editions of the documents listed below, since the nature of references made
by ISPs to these documents is that they may be specific to a particular edition. Members of IEC and IS0 maintain
registers of currently valid International Standards and ISPs, and ITU-T maintains published editions of its current
Recommendations.
31 . Identical Recommendations 1 International Standards
- KU-T Recommendation X.200 (1994) 1 ISO/IEC 7498-l : 1994, Infirmation technoEoeOpen
Systems Interconnection: Basic Reference Model.
- ITU-T Recommendation X.207 (1993) 1 ISO/IEC 9545 : 1994, Infirmation technoZoeOpen
Systems Interconnection-AAppZication layer structure.
- KU-T Recommendation X.210 (1993) 1 ISO/IEC 1073 1 : 1994, Information technology -Open
Systems Interconnection-Basic Reference Model -Conventions for the de$nition of OSI
services.
- KU-T Recommendation X.214 (1993) 1 ISO/IEC 8072 : 1994, Information technology -Open
Systems InterconnectiovTransport service dejnition.
- ITU-T Recommendation X.215 (1994) 1 ISO/IEC 8326 : 1996, Information technology -Open
Systems Interconnectioti Session service dejnition.
- ITU-T Recommendation X.216 (1994) I ISO/IEC 8822 : 1994, Information technolopopen
Systems InterconnectiowPresentation service de$nition.
- IT&T Recommendation X.217 (1995) I ISO/IEC 8649 : 1996, Information technology -Open
Systems InterconnectioeService deJinition for the Association Control Service Element.
- KU-T Recommendation X.225 (1995) 1 ISO/IEC 8327-l : 1996, Information technoloeopen
Systems Interconnection-Connection-oriented session protocol:
Protocol specification.
- IT&T Recommendation X.226 (1994) I ISO/IEC 8823-l : 1994, Information technology-open
Systems Interconnection-Connection-oriented presentation protocol: Protocol specification.
- KU-T Recommendation X.227 (1995) I ISO/IEC 8650-l : 5, Information technology -
Open Systems Interconnectio+Connection-oriented protocol for the Association Control
Service Element: Protocol specijcation.
- KU-T Recommendation X.245 (1995) I ISO/IEC 8327-2 : $ Information technology -
Interconnection-Connection-oriented session protocol : Protocol
Open Systems
Implementation Conformance Statement (PIGS) proforma.
5 To be published. (Revision of IS0 8650: 1988)
6 To be published.
ISO/IEC ISP 11188-3 : 1996 (E)
0 ISOKEC
- KU-T Recommendation X.246 (1994) I ISO/IEC 8823-2 : 1995, Information technolowopen
Systems Interconnection-Connection-oriented presentation protocol : Protocol Implementation
Conformance Statement (PICS) proforma.
- ITU-T Recommendation X.247 (1994) I ISO/IEC 8650-2 : 1995, Information technolo-Open
Systems InterconnectioeProtocol specification for the Association Control Service Element :
Protocol Implementation Conformance Statement (PICS) proforma .
- IT&T Recommendation X.690 (1994) ( ISO/IEC 8825-l : 1995, Information technolowASN. I
encoding rules: SpeciJcation of Basic Encoding Rules (BER), Canonical Encoding Rules (CER)
and Distinguished Encoding Rules (DER).
32 . Paired Recommendations 1 International Standards equivalent in technical content
- CCITT Recommendation X.650 (1992) Open Systems Interconnection (OSI’Reference model for
naming and addressing.
IS0 7498-3 : 1989, Information processing systems- Open Systems Interconnection-Basic
Reference Model-Part 3 : Naming and addressing.
33 Additional references
.
of International
- ISOIIEC TR 10000-l : 1995, Information technolog)r-Framework and taxonomy
Standardized ProJiles-Part I : General principles and documentation framework.
- ISOIIEC TR 10000-2 : 1995, Information technolovFramework and taxonomy of international
standardized proJles-Part 2 : Principles and Taxonomy for OSI profiles.
- ISO/IEC ISP 11188-l : 1995, Information technolovInternationa1 Standardized Profile-
Common upper layer requirements- Part I : Basic connection-oriented requirements.
4 Definitions
This part of ISO/IEC ISP 11188 makes use of the following definitions.
41 . Reference model dehitions
4.1.1 Basic Reference Model definitions
This part of ISO/IEC ISP 11188 is based on the concepts developed in ITU-T Rec. X.200 I ISO/IEC 7498-1. It
makes use of the following terms defined in them:
application-entity;
a>
Application layer;
b)
application-process;
C)
application-protocol-control-information;
d)
application-protocol-data-unit;
e)
application-service-element;
compliance;
g)
presentation-connection;
h)
Presentation layer;
.
presentation-service;
J)
session-connection;
k)
Session layer;
session-protocol;
m>
ISOlIEC ISP 11188-3 : 1996 (E) 0 ISO/IEC
session-service;
n)
Transport layer
0)
4.1.2 Naming and addressing definitions
This part of ISO/IEC ISP 11188 makes use of the following terms defined in IS0 7498-3:
application-process title;
a)
application-entity qualifier;
b)
application-entity title;
C)
application-process invocation-identifier;
d)
application-entity invocation-identifier; and
e)
presentation address.
Q
42 . Service conventions definitions
This part of ISO/IEE ISP 11188 makes use of the following terms defined in ITU-T Rec. X.210 1 ISO/IEC 1073 1:
primitive;
a)
request (primitive);
W
indication (primitive);
C)
response (primitive); and
d)
confirm (primitive).
e)
43 . Presentation definitions
This part of ISO/IEC ISP 1 I188 makes use of the following terms defined in ITU-T Rec. X.216 1 ISO/IEC 8822
and ITU-T Rec. X.226 1 ISO/IEC 8823-l:
abstract syntax;
a)
abstract syntax name;
b)
default context;
Cl
defined context set;
d)
tictional unit [Presentation];
e)
normal mode [Presentation];
presentation context;
fa
presentation data value; and
h)
presentation selector
44 . Session definitions
This part of ISOLEC ISP 11188 makes use of the following terms defined in ITU-T Rec. X.215 1 ISO/IEC 8326
and ITU-T Rec. X.225 1 ISO/IEC 8327-l:
session selector.
45 . Application layer structure definitions
This part of ISO/IEC ISP 11188 makes use of the following terms defined in ISO/IEC 9545:
application-context;
0 1s0/Il3c ISO/IEC ISP 11188-3 : 1996 (E)
application-entity invocation;
b)
control function; and
C)
application-service object.
d)
46 . ACSE service definitions
This part of ISO/IEC ISP 11188 makes use of the following terms defined in ITU-T Rec. X.217 1 ISOLTEC 8649
and ITU-T Rec. X.227 1 ISO/IEC 8650-l:
application-association; association;
a)
Association Control Service Element;
b)
requestor;
Cl
acceptor;
d)
association-initiator; and
e)
association-responder.
f)
47 . Taxonomy of profile definitions
This part of ISO/IEC ISP 11188 makes use of the following terms defined in ISO/IEC TR 10000-l:
A-Profile;
a)
profile requirements list;
b)
profile implementation conformance statement; and
c)
PICS Proforma.
48 . Definitions of this part of ISOlIEC ISP 11188
For the purposes of this part of ISO/IEC ISP 11188, the following definitions apply.
4.8.1 basic communications application: An application program that simply requires the ability to open and
close communications with a peer and to send and receive messages with that peer.
4.8.2 conformance: The referencing implementation supports an identified and consistent set of dynamic
conformance requirements specified in a set of related OS1 protocol, profile, abstract syntax, encoding rule and
information object specifications.7
4.8.3 mOS1 specification; mOSI stack specification: This specification that defines the minimal facilities of the
Session layer, Presentation layer, and ACSE.
4.8.4 mOS1 stack: An implementation that supports, at a minimum, the facilities defined in the mOS1 stack
specification.
4.8.5 mOS1 platform specification: The functional specification of a formal programmatic interface and a set of
supporting local services for the mOS1 stack specification.
4.8.6 mOS1 platform: An implementation of the mOS1 platform specification.
4.8.7 non-basic communications application: An application program ‘that requires the ability to support
functions other than those specified in the deftition a basic communications application.
4.8.8 platform: An implementation of an identified platform specification.
4.8.9 platform-based application: An application program that conforms to a platform specification.
7 This deftition may be removed at such a time when a definition of conformance is made available in the OS1 Reference
Model, or some other governing specification.
0 1s0/IEc
ISOlIEC ISP 11188-3 : 1996 (E)
4.8.10 PDV-processor: part of an implementation which wraps and unwraps the “PDV envelope” around the
syntax sent and received in the identified presentation context.
4.8.11 platform specification: The functional specification of a formal programmatic interface and a set of
supporting local services for an identified stack specification.
4.8.12 referencing implementation: A specification of an implementation which references mOS1 for defining its
upper layer requirements.
4.8.13 referencing specification: A specification of an ISO/IEC ISP or the specification of a basic
communications application which references mOS1 for defining its upper layer requirements.
4.8.14 specific basic communications application: an application that is not referenced by any ISP.
4.8.15 stack; stack implementation: An implementation of an identified stack specification
4.8.16 stack specification: The functional specification of a set of interrelated standards for the purpose of
providing a common service (set of facilities).
4.8.17 standalone application: Any application program which is not a platform-based application.
4.8.18 transport-provider: A provider of those transport services which are defined in ITU-T Rec. X.214 I
ISO/IEC 8072.
5 Abbreviations
The following abbreviations are used in this part of ISO/IEC ISP 11188.
ACSE Association Control Service Element
APDU application-protocol-data+.nit
API application programmatic interface
ASN. 1 Abstract Syntax Notation One
BCA basic communications application
International Telegraph and Telephone Consultative Committee
CCITT
Common Upper Layers Requirements
CULR
implementation conformance statement
ICS
lEC International Electrotechnical Commission
International Organization for Standardization
IS0
International Standardized Profile
ISP
International Telecommunications Union - Telecommunications Systems and Services
IT&T
minimal OS1 upper layer facilities
mOS1
OS1 Open Systems Interconnection
PDU protocoldata-unit
PDV presentation data value
protocol implementation conformance statement
PIGS
presentation-protocddata-unit
PPDU
profile requirements list
PRL
SPDU session-protocoldata4mit
TSDU transport~servicedatadata-unit

ISO/IEC ISP 11188-3 : 1996 (E)
0 ISO/IEC
6 Conventions
61 Profile status indicators
.
This part of ISO/IEC ISP 11188 states mOS1 functionality by deftig rules for forming a mOS1 Profile
Requirements List (PRL) based on the PICS proformas of ACSE, Presentation, and Session. The rules for defining
a mOS1 PRL are contained in annexes A, B, and C. The rules are specified by a series of tables in each annex.
Each table in an annex refers to one identified table in the respective PICS Proforma. Each row in an annex table
refers to a row in the corresponding PICS Proforma table.
Annexes A, B, and C consist of rules that determine the status indicator for each entry in the ACSE, Presentation,
Session PICS Proformas. A status indicator defmes rules that a referencing application or a referencing
implementation must follow as it relates to the associated entry in annex A, B, or C. The Profile status indicators
used in this part of ISO/IEC ISP 11188 are presented in table 1.
The upper layer PICS proforma and consequently an upper layer PRL contain over 120 tables with almost 1000
entries (questions). For BCA applications, a large number of the PICS proforma entries do not apply-they are out
of scope (i). Others are obviously required-they are mandatory (m). Some are considered internal and left to the
discretion of the implementor-they are optional (0).
The remaining entries of annexes A, B, and C are determined by a referencing specification or a referencing
implementation. This is done by assigning status indicators (those defined in table 1) to mOS1 variables and open
parameters (see 2.3 and 6.2). An open parameter is a variable that is only referenced in one table entry. An open
parameter is assigned the profile status of “*‘I (see table 1).
An application PRL results when status identifiers are assigned to mOS1 variables and open parameters and they
are applied to annexes A, B, and C. Table 1 definitions apply to the resultant status identifiers of the application
PRL.
Column 2 of table 1 defmes rules for a referencing specification. They define how a referencing specification
shall view an entry in annexes A, or B, or C. It also defines the meaning of a status indicator when assigned to a
mOS1 variable or to an open parameter.
Column 3 of table 1 defines rules for a referencing implementation. define how a referencing
They
implementation shall view an entry in annexes A, or B, or C or that of an appli cations PRL.

0 1s0/IEc
ISO/IEC ISP 11188-3 : 1996 (E)
Table 1 - Profile status identifiers
Meaning when referenced by an implementation
Identifier Meaning when referenced by a
specification
The feature shall be required mandatory - The implementation shall support the
1 m mandatory -
for ‘support. The status of the feature shall feature, i.e. its syntax and procedures shall be
remain mandatory in a referencing implemented as specified in the base standard or in
specification (see note). ISO/IEC ISP 11188-l. However, it is not a requirement
that the feature shall be used in all instances of
communication unless mandated by the base standard
or stated otherwise in ISOLIEC ISP 11188-l. The
feature shall be the subject of an ISP conformance test
(see note).
optional - The implementation may decide either to
2 optional - The choice of whether this
feature is supported or it is not supported is support or to not support the feature.
made by the implementation. The status of
l Supporting the feature means that the feature shall
the feature shall remain optional in a
be handled as if it was mandatory.
referencing specification.
For sending, the capability is not used.
feature’s
For receiving an optional parameter, the syntax
shall be implemented and the parameter may be
- same as optional
that the status of the feature is mandatory,
referencing specification. be that the feature has not been implemented. The
uld be the subject of an ISP
of the feature shall remain out of scope in a ISP conformance test.
mentioned in a table. ntext where it i
feature is either
physically impossible, after some
conditions are evaluated. The status of the
feature shall remain not applicable in a
referencing specification.
conditionally supported - Support for the feature is
7 conditionally supported - Support for the
CM
further defmed by a condition (“n”) which is annexed to
feature is further defmed in this part of
ISO/IEC ISP 11188 by condition (‘In”) the table. Depending on the condition, when completing
annexed to the table. The value evaluated the associated PICS Proforma table, the answer for the
from the condition evaluates to one of the support column shall either be: the feature has been
following values defmed in this table: “m”; implemented; the feature has not been implemented; or
I’ ‘I. I’ l ‘I
1 , or “-“. not applicable.
0,
NOTE-The sypport of a feature can be conditional, depending on the support of a class of features to which it belongs, e.g. a
parameter in a PDU, a PDU in a firnctional unit.
0 ISO/IEC ISO/IEC ISP 11188-3 : 1996 (E)
62 . Definitions of variables
Variables are used in annexes A, B, and C as a method of specifying values for the ‘Profile status” column of
these tables. A variable (for the purpose of this part of ISO/IEC ISP 11188) is used as a simple replacement for
two or more table entries and/or in a IF/THEN/ELSE conditional statement to derive a table entry. A variable’s
name is always written in italics. The variables used are
Establishment-initiator - capability to establish an association or connection
Establishment-responder - capability to respond to an establishment initiation
Establishment-responder-reject - capability to reject an establishment initiation
Release-requestor - capability to release an association or connection
Release-acceptor - capability to accept a release request
Normal-data-requestor capability to request transfer
Normal-data-acceptor - capability to accept normal data transfer
Authentication - capability to perform authentication
Application-context-negotiation - capability to perform application context negotiation
Transport-expedited - capability to use transport expedited data for Session PDUs (this does not
include the Session ExpeditedData functional unit).
These variables reflect the roles and options identified in 2.3. The values these variables may take are I’m”, “o”,
and “i” as defined in table 1. Values for these variables may be assigned by a referencing specification in annex D
and by a referencing implementation in annex E.
63 . Definition of mnemonics
Mnemonics are used in annexes A, B, and C to facilitate the interpretation of conditional statements throughout
the PI&s of annexes A, B, and C. These mnemonics are introduced in column 4 of several tables in these annexes;
they are
A-CON-initiator (see A.2.1/1)
A-CON-responder (see A.2.1/2)
A-REL-requestor (see A.2.2/1)
A-REL-acceptor
(see A.2.212)
A-FU(A U) (see A.412)
A-FU(ACN) (see A.413)
P-DATA-requestor (see B.3.1.1.2/1)
P-DATA-acceptor (see B.3.1.1.2/2)
P-REL-requestor (see B.3.1.1.3/1)
P-REL-acceptor (see B.3.1.1.3/2)
P-REFUSE (see B.3.1.2/3)
S-EXP-T (see C.3.2/1)
These mnemonics are Boolean variables. They reflect whether the feature of the corresponding table entry is
supported or not. A mnemonic has the value TRUE if the corresponding feature is supported, otherwise FALSE.
0 ISO/IEC
ISO/IEC ISP 11188-3 : 1996 (E)
7 Model
This clause presents the mOS1 model and defines many of the terms used in this part of ISO/IEC ISP 11188. The
mOS1 model, as shown in figure 1, illustrates the mOS1 stack in three different environments which are detailed in
7.2 and 7.3. It can be viewed in two contexts: it can be viewed abstractly - where the various elements represent
abstract specifications; or it can be viewed concretely - where the elements represent those of an implementation.
Migrant Kernel
Basic Basic Communications Communications
Basic Communications
Basic Communications
Application Application Process Process
Application Process Application Process
(“stand-alone”) (“stand-alone”)
(“platform-based”) (“platform-based”)
[a mOSI API] [a mOSI API]
mOSI
ACSE ACSE
\ \
Presentation Presentation
Presentation mOSI
platform
---------
Session Session
Session
/
IS0 8072
Transport-provider
Figure I - mOSI model
71 . Common elements
There are common elements in all three environments shown in figure 1. They are:
- basic communications application
- PDV-processor
- mOSI stack
- transport services and
- transport provider
A basic communications application (BCA) simply requires the ability to open and close communications with a
peer and to send and receive messages with the peer. This part of ISO/IEC ISP 11188 addresses the requirements
of basic communications applications.
A stack represents a set of layered, interdependent communication standards (in the abstract sense) and their
implementation (in the concrete sense). The mOS1 stack represents the ACSE, Presentation, and Session
standards (protocol spe&ications) or their implementation with the features specified in this part of ISO/IEC ISP
11188.
NOTE - A stack does not necessarily represent a layered implementation of the layered standards. On the contrary,
it is recommended in annex H that the implementation of a mOS1 stack is one protocol engine, not three.
From the perspective of the Presentation protocol (ISO/IEC 8823-l), the syntax (encoded data) sent from one
application to its peer is a series of one or more presentation-data-values (PDV). The IS0 Presentation protocol
defines the encoding of the outer envelope around a PDV and the encoding for groups of PDVs (if any). The
0 ISO/IEC ISO/IEC ISP 11188-3 : 1996 (E)
actual contents of a PDV is a function of the mutually agreed upon abstract and transfer syntax of the PDV - its
presentation context. While ASN. 1 basic encoding rules can be used for encoding abstract and transfer syntax, it is
not the only choice.
The negotiation of the transfer syntax and the encoding/decoding of user information is considered in the OS1
model to be done by the Presentation layer. The Application layer is concerned only with abstract values, with no
defined encoding. Consequently, in a real system the boundary between Application layer and Presentation layer
cannot be precisely represented (since real systems are not abstract). In the implementation-oriented mOS1 model,
any necessary encoding/decoding of the transfer syntax sent between connected applications is outside the scope
of the mOS1 stack. The encoding produces presentation-data-values in the appropriate presentation context. The
Presentation protocol includes the specification
...