ISO/IEC 10026-6:1995

Information technology — Open Systems Interconnection — Distributed Transaction Processing — Part 6: Unstructured Data Transfer

Provides a model for the transfer of application data for transaction processing applications whose application-specific protocol has not been standardized within the OSI environment.

Technologies de l'information — Interconnexion des systèmes ouverts (OSI) — Traitement transactionnel réparti — Partie 6: Transfert de données non structuré

General Information

• Status: Published
• Publication Date: 28-Jun-1995
• ICS: 35.100.70 - Application layer
• Technical Committee: ISO/IEC JTC 1 - Information technology
• Drafting Committee: ISO/IEC JTC 1 - Information technology
• Current Stage: 9093 - International Standard confirmed
• Completion Date: 28-Jun-2001

Standards Content (Sample)

INTERNATIONAL lSO/IEC
10026-6
STANDARD
First edition
1995-07-01
Information technology - Open Systems
- Distributed Transaction
Interconnection
Processing -
Part 6:
Unstructured Data Transfer
- lnterconnexion de syst&mes ouverts
Technologies de I’informa tion
- Traitemen t transactionnel rgparti -
mu
Partie 6: Transfert de don&es non structurb
Reference number
ISO/I EC 10026-6: 1995(E)

---------------------- Page: 1 ----------------------
ISO/IEClOO26=6:1995(E)
Foreword
IS0 (the International Organization for Standardization) and IEC (the Inter-
national 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 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 voting. Publication
as an International Standard requires approval by at least 75 % of the national
bodies casting a vote.
International Standard ISO/IEC 10026-6 was prepared by Joint Technical
Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 21, Open
systems interconnection, data management and open distributed processing.
ISO/IEC 10026 consists of the following parts, under the general title Information
technology - Open Systems Interconnection - Distributed Transaction
Processing:
- Part I: OSI TP Model
- Part 2: 0% TP Service
- Part 3: Protocol specification
- Part 4: Protocol Implementation Conformance Statement (PIGS) proforma
- Part 5: Application context proforma and guidelines when using OSI TP
- Part 6: Unstructured Data Transfer
Annex A forms an integral part of this part of ISO/IEC 10026. Annexes B and C
are for information only.
0 ISO/IEC 1995
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 Office l Case postale 56 0 W-121 1 @en&e 20 Q Switzerland
Printed in Switzerland
ii

---------------------- Page: 2 ----------------------
0 ISO/IEC
ISO/IEC10026=6:1995(E)
Introduction
ISO/IEC 10026 is one of a set of standards produced to facilitate the interconnection of computer systems. It is related to other
International Standards in the set as defined by the Reference Model for Open Systems Interconnection (IS0 7498). The Reference
Model subdivides the area of standardization for interconnection into a series of layers of specification, each of manageable size.
The aim of Open Systems Interconnection is to allow, with a minimum of technical agreement outside the interconnection
standards, the interconnection of computer systems
a) from different manufacturers;
b) under different management;
c) of different levels of complexity; and
d) of different technologies.
ISO/lEC 10026-1, -2 and -3 define the OS1 TP Model, OS1 TP Service and OS1 TP Protocol available within the Application
Layer of the OS1 Reference Model. ISO/IEC 10026-4 is the OS1 TP PICS and ISO/IEC 10026-5 defines the Application Context
Proforma and Guidelines When Using OS1 TP.
This part of ISO/IEC 10026 defines a model for unstructured data transfer within the OS1 TP environment. UDT operates within
the constraints specified for U-ASEs in ISO/IEC 10026. UDT is not suitable for use outside the OS1 TP environment.
0 . e
111

---------------------- Page: 3 ----------------------
This page intentionally left blank

---------------------- Page: 4 ----------------------
INTERNATIONAL STANDARD 0 ISO/IEC
ISO/IEC 10026-6: 1995(E)
Information technology
- Open Systems Interconnection - Distributed Transaction
Processing -
Part 6:
Unstructured Data Transfer
1 Scope
ISO/IEC 10026-1:1992, Information technology - Open
Systems Interconnection - Distributed Transaction
Processing - Part I: OSI TP Model.
This part of ISO/IEC 10026 provides a model for the transfer
of application data for transaction processing applications
ISO/IEC 10026-2: 1992, Information technology - Open
whose application-specific protocol has not been standardized
Systems Interconnection - Distributed Transaction
within the OS1 environment.
Processing - Part 2: OS1 TP Service.
ISO/IEC 10026-3: 1992, Information technology - Open
2 Normative references
Systems Interconnection - Distributed Transaction
Processing - Part 3: Protocol specification.
The following standards contain provisions which, through
reference in this text, constitute provisions of this part of
ISO/IEC 1073 1: 1994, Information technology - Open
ISO/IEC 10026. At the time of publication, the editions
Systems Interconnection
- Basic Reference Model -
indicated were valid. All standards are subject to revision, and
Conventions for the definition of OSI services.
parties to agreements based on this part of ISO/IEC 10026 are
encouraged to investigate the possibility of applying the most
recent editions of the standards listed below. Members of IEC
and IS0 maintain registers of currently valid international
standards.
3 Definitions
ISO/IEC 9646- 1: 1994, Information technology - Open
For the purposes of this part of ISO/IEC 10026, the
Systems Interconnection - Conformance testing
definitions given in ISO/IEC 10026-l and the following
methodology andfiamework- Part 1: General concepts.
definition apply:
ISO/IEC 9646-2: 1994, Information technology - Open
3.1 non-OSI-standard: A specification not formally
Systems Interconnection - Conformance testing
approved by the recognized world-wide standardization bodies
methodology and framework - Part 2: Abstract Test Suite
for OSI.
specification.
ISO/IEC 9646-3: 1992, Information technology - Open
Conformance testing methodology
Systems Interconnection -
4 Abbreviations
Part 3: The Tree and Tabular Combined
and framework -
Notation (TTCN).
Abbreviations used in this part of ISO/IEC 10026 are defined
ISOIIEC 9646-4: 1994, Information technology - Open in ISO/IEC 10026-1, except the following:
Systems Interconnection - Conformance testing
methodology and framework - Part 4: Test realization.
UD Unstructured Data
UDT Unstructured Data Transfer
ISO/IEC 9646-5: 1994, Information technology - Open
Systems Interconnection - Conformance testing
methodology and framework - Part 5: Requirements on test
laboratories and clients for the conformance assessment
5 Conventions
process.
This part of ISO/IEC 10026 uses the conventions defined in
ISO/IEC 9834-l: 1993 Information technology - Open
ISO/IEC 1073 1.
Systems Interconnection - Procedures for the operation of
OSI Registration Authorities - Part 1: General procedures.

---------------------- Page: 5 ----------------------
ISO/IEC10026=6:1995(E)
0 ISO/IEC
6 Unstructured Data Transfer in OS1 TP
6.2.1 Using UDT with registered syntaxes
6.1 Purpose
The recommended approach is to register the application
This part of ISO/IEC 10026 defines two approaches for protocol’s abstract and transfer syntaxes, so that the resulting
transferring application data which allow non-OSI-standardized names may be used in transferring APDUs using Presentation
applications to operate in the OS1 TP environment. UDT, Services. (Normally, the P-Data service will be used to
thus, provides for the rapid migration of networked transfer APDUs, although other Presentation services may
transaction programs which were originally written for also be used, so long as this is done in a manner which will
operation in networks without facilities similar to those of not interfere with TP’s use of the Presentation Layer.)
the OS1 Application and Presentation Layers (i.e., for
interoperation between heterogeneous systems). Typically, it will also be necessary to specify an application
Annex B contains an application context
context name.
It should be emphasized that the second form of UDT proforma that may be completed to yield a complete
described in 6.2 (‘restricted UDT’) should only be used in application context definition, for registration under the
specialized circumstances, i.e., where there is a need to procedures of ISO/IEC 9834- 1.
exchange APDUs of existing applications in an OS1 TP
environment. Adopting this approach will prevent 6.2.2 Using UDT with a priori knowledge of
applications from exploiting the important features of the application syntax
Presentation Layer.
In the case where it is not convenient to register a non-OSI-
standardized application protocol’s syntaxes, it may be
6.2 Model for UDT possible to present application data values as sequences of
octets. In support of this approach, annex A provides generic
In order to transfer data between application programs abstract and transfer syntax names (together with an
(TPSUIs) in an OS1 TP environment, the applications must application context name) which can be used to support the
make use of the facilities of the Presentation Service. This mapping of any application protocol’s abstract and transfer
part of ISO/IEC 10026 does not define a service to offer syntax onto such a sequence of octets.
Presentation facilities to the application; rather it assumes
that the necessary elements of the Presentation Service will In other words, these generic abstract and transfer syntax
be made available to the application. names can be used to provide a means whereby APDUs may
be transferred without the need to register or more specifically
NOTE - In a real implementation, it is assumed that the API being
define the application protocol. It must be emphasized,
provided for application communication (e.g. for ‘peer-to-peer’
however, that adopting this approach requires that cooperating
operation) would include a service that would be mapped directly to
TPSUIs have a priori knowledge of the syntax, semantics,
the relevant Presentation Layer facilities.
and mapping of the APDUs; this is required if the TPSUIs are
to correctly generate and interpret both the syntax and
In order to make correct use of the Presentation Layer, the
semantics of the messages thus exchanged using the octet
application program must specify what abstract and transfer
string mapping described in annex A.
syntaxes are to be used. UDT assumes that cooperating
TPSUIs exchanging the APDUs of a non-standardized
protocol will have a priori knowledge of the syntax and
7 UDT ASE Specification
semantics of the protocol APDUs, thus enabling the TPSUIs
to correctly generate and interpret the data being exchanged.
7.1 Overview
The abstract and transfer syntaxes being used must be
registered with an OS1 registration authority operating under
The UDT ASE is an essentially null ASE that acts as the
the procedures of ISO/IEC 9834-l. The unambiguous names
User-ASE in the TP model when the application protocol
resulting from this registration are used to denote the
requires no additional protocol support from the User-ASE
application protocol’s syntaxes during Presentation
within the TPPM other than the specification of the mapping
negotiation.
to the Presentation service.
It is also necessary that the name of any application context
The UDT ASE has one service, UD-TRANSFER that models
being used be similarly registered. This registered application
the transmission of data between the TPSUIs on a TP
context name is used by ACSE; it implies the application
dialogue. The UD-TRANSFER service is subject to the
layer semantics and mappings of all the application protocols
constraints specified for the generic TP-DATA specified in
that may be used during that instance of communication,
ISO/IEC 10026-2 and 3. The service relates to a particular
including the one (or more) using the UDT approach.
dialogue.
UDT may be used in two ways as described below.

---------------------- Page: 6 ----------------------
0 ISO/IEC
ISO/IEC 10026=6:1995(E)
On receipt, presentation data values received in a UDT
7.2 Primitives and their parameters
presentation context are mapped to the user data of a UD-
Transfer indication.
Primitive names:
UD-TRANSFER request
It is the responsibility of the specifications of the abstract
UD-TRANSFER indication
syntax, transfer syntax and application context (together) to
ensure that the user data on a single UD-Transfer indication
has the same value as the user data on the corresponding UD-
req ind
Transfer request.
/
User-data M M(=)
7.5 Collisions
Key:
M presence of the parameter is mandatory.
A collision of a UD-TRANSFER request and indication are
indicates that a parameter value is semantically
not treated as a collision but are each handled separately.
equal to the value of the parameter of the preceding
primitive in the table.
7.6 Disruption
7.2.1 User-data is a parameter that carries the non-OSI-
The UD-TRANSFER service does not disrupt any other
standardized protocol to be exchanged between cooperating
service. The UD-TRANSFER service is disrupted by any
peer TPSUIs.
service that disrupts the underlying service (i.e., P-DATA
service or which ever other service is used). If the UD-
7.3 Sequence of primitives TRANSFER service is used with OS1 TP as the actual
replacement for the ‘I?-DATA service, then the disruption and
purging rules given in ISO/IEC 10026-2 and -3 for the TP-
The sequence of primitives for the UD-TRANSFER service is
DATA service apply.
defined by the following time sequence diagram:
NOTES
UD-TRANSFER
rr 1. In particular, abort and resynchronization services may disrupt
request d
1 b
the UD-TRANSFER.
\
\
\
\
2. If the UD-TRANSFER service is mapped to another service,
\
\
\ such as TP-BEGIN-DIALOGUE or TP-ABORT, then the disruption
\
\ rules for that service apply.
UD-TRANSFER
\
\
b indication
8 Conformance
7.4 Procedures
To conform to this part of ISO/IEC 10026, a system shall
implement the procedures specified in clause 7 or, in the case
When a TPSUI wishes to transmit an APDU, it issues a UD-
of UDT with a priori knowledge of Application Syntax, the
Transfer request with the APDU as User-Data; this UD-
conformance statement in A.2.11 shall apply.
Transfer request is mapped directly to the user data of an
appropriate Presentation or TP service primitive, with the
APDU being mapped according to the transfer syntax being
used. The use made of Presentation services must be
consistent with OS1 TP’s use of these services, and is
constrained by the SACF and MACF rules of TP. The use of
Presentation may be more precisely determined by the
application context definition which is in use, or by bilateral
agreement.
The user data parameter of the UD-Transfer request (i.e., the
application data being transmitted) will be sent as one or
more presentation data values in the UDT presentation
context. These may or may not be concatenated according to
the SACF rules in force.

---------------------- Page: 7 ----------------------
ISO/IECl0026=6:1995(E)
0 ISO/IEC
Annex A
(normative)
Unstructured data transfer - Procedures, abstract and transfer
syntaxes, and application context for octet string mapping
This annex contains the procedures, abstract and transfer
syntax names, and a full application context which apply
(joint-iso-ccitt asn l( 1) basic-encoding( 1))
when a non-ISO-standardized application protocol is
transferred as the value of an octet string (with a bilateral is used as the transfer syntax name for the transfer syntax
agreement between communicating TPSUls). See 6.2.2. formed by taking an ordered sequence of octets (which is the
representation of a value of an abstract syntax identified by
the OBJECT IDENTIFIER in A.1.3, encoded in a manner
that is also known a priori to the communicating TPSUIs)
A.1 Procedures
as the value of an ASN.l type OCTET STRING and
encoding this according to the Basic Encoding Rules, with the
These procedures apply only when the application APDUs are
restriction that the primitive encoding shall be used. A single
transferred as a sequence of octets.
pdv shall be treated as a separate and complete value of the
type ASN.l OCTET STRING.
A.l.1 Receiving a UD-TRANSFER request
NOTE - The effect of this is that the sequence of octets passed
from the sending TPSUI is prefixed with the tag for OCTET
Upon receipt of a UD-TRANSFER request, the application
STRING and a length field, and is treated as the “single-ASN.l-
data contained in the user-data field is mapped to a single pdv
type” of the “presentation-data-values” CHOICE by the
(to ensure that all the application data is transmitted as a
presentation protocol.
whole) for transmission (using the transfer syntax defined in
A. 1.4) according to the mapping rules in A.2.8.1.4.
A.2 Application Context
NOTE - these procedures only apply to the UD-TRANSFER
service, not to other services defined in ISO/IEC 10026-3.
This clause contains the full application context for use when
application APDUs are transferred as a sequence of octets as
A.1.2 Receiving application data
defined by the procedures in this annex.
Upon receipt of a single presentation data value which is a
A.2.1 Application context name
presentation context for restricted UDT, a UD-Transfer
indication is generated whose user-data is mapped from the
received pdv. The OBJECT IDENTIFIER for this application context is
(iso( 1) standard(O) tp( 10026) udt(6) application-context(2))
A.l.3 Abstract syntax name
This application context supports the serial execution of bo
...