ISO/IEC 10026-5:1998

INTERNATIONAL ISOAEC
10026-5
STANDARD
First edition
1998-11-15
Information technology - Open Systems
Interconnection - Distributed Transaction
Processing -
Part 5:
Application context proforma and guidelines
when using OSI TP
Technologies de I’information - lnterconnexion de systkmes
owe& (OSI) - Traitement transactionnel @parti -
Partie 5: Proforme de contexte d’application et lignes directrices en
utilisa tion OS1 TP
Reference number
ISO/I EC 10026-5: 1998(E)

---------------------- Page: 1 ----------------------
ISOAEC 10026-5: 1998(E)
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 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-5 was prepared by Joint Technical
Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 21,
Open sys terns interconnection, data management and open distributed
processrng.
ISO/IEC 10026 consists of the following parts, under the general title
lnforma tion technology - Open Systems Interconnection - Distributed
Transaction Processing:
Part I: OSI TP Model
-
- Part 2: OSI TP Service
Part 3: Protocol specification
-
- Part 4: Protocol Implementation Conformance Statement (PICS)
pro forma
- Part 5: Application context proforma and guidelines when using
OSI TP
- Part 6: Unstructured Data Transfer
- Part 7: Message queueing
Annex A forms an integral part of this part of ISO/IEC 10026. Annex B is for
information only.
0 ISO/IEC 1998
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 l CH-1211 Gengve 20 l Switzerland
Printed in Switzerland
ii

---------------------- Page: 2 ----------------------
lSO/lEC 10026-5: 1998(E)
INTERNATIONAL STANDARD @ ISOAEC
Information technology - Open Systems
Interconnection - Distributed Transaction Processing -
Part 5:
Application context proforma and guidelines when using OS1 TP
ISO/IEC 10026 is one of a set of standards produced to fa-
cilitate the interconnection of computer systems. It is related
to other International Standards in the set as defined by the
3 Definitions
Reference Model for Open Systems Interconnection (IS0
The Reference Model subdivides the area of
7490).
For the purposes of this part of ISO/IEC 10026, the definitions
standardisation for interconnection into a series of layers of
specification, each of manageable size.
given in ISO/lEC 10026-l and the following definitions apply.
The goal of Open Systems Interconnection is to allow, with
a minimum of technical agreement outside the intercon- 3.1 Application Layer Structure definitions
nection standards, the interconnection of information proc-
essing systems:
This International Standard makes use of the following terms
defined in ISO/IEC 9545:
a) from different manufacturers;
b) under different management;
application-context-definition; and
a)
control-function.
Cl
c) of different levels of complexity; and,
d) of different technologies. 4 Abbreviations
ISO/IEC 10026 defines a Model, and Service, and specifies a
For the purposes of this part of ISO/IEC 10026, the abbrevi-
Communication Protocol within the Application Layer of the
ations given in ISO/lEC 10026-I and the following abbrevi-
OSI Reference Model.
ations apply.
1 Scope
FU Functional Unit
This part of lSO/IEC 10026 specifies requirements specific to
OSI TP that should be contained in an application context
5 Overview of the TP application context
definition, in addition to the general requirements for an ap-
plication context definition. It does not specify individual
proforma
implementations or products, nor does it constrain the im-
plementation of entities or interfaces within a computer
This part of ISO/IEC 10026 specifies what must be contained
system.
in an application context where use is made of the facilities
of OSI TP. Such an application context may define rules for
2 Normative references
the correct interaction of the various ASEs (ACSE, the
The following standards contain provisions which, through TP-ASE, possibly CCR, and one or more User-ASEs) con-
reference in this text, constitute provisions of this part of
trolled by the TP MACF and SACF, in addition to listing the
lSO/IEC lQ026. At the time of publication, the editions indicated
ASEs which are used. The remainder of this part of ISO/IEC
were valid. All standards are subject to revision, and parties to
10026 provides guidelines for the specification of such rules
agreements based on this part of lSO/IEC 10026 are encouraged
and options.
to investigate the possibility of applying the most recent editions of
the standards indicated below. Members of IEC and IS0 maintain
registers of currently valid International Standards.
IS0 9545:1993, information Processing Systems - Open Systems
Interconnection - Application Layer s true ture.
lSO/IEC 10026-I :I 998, information technology - Open Systems
/n terconnection - Distributed Transaction Processing - Part 1: OSI
TP Model.

---------------------- Page: 3 ----------------------
@ ISOAEC
lSO/lEC 10026-5: 1998(E)
If any other application contexts are referenced as part of this
6 TP application context contents
context they shall be iisted, along with their Object identifier
names.
This clause contains guidelines for defining an application
context which contains OSI TP, together with general guide-
This list will include application contexts that will be used on
lines which would apply to any application context. (These
other associations if there are dialogue trees within which
general guidelines are included for completeness, and ap-
this association and one of the other associations are adja-
pear in italics.) An application context proforma is contained
cent at either end of this association. Other application
in annex A; this annex includes information which always
contexts need only be included if the semantic-exchanges
appears in the definition of an application context which
under this application context require the use of the other
contains OSI TP. The subclauses in this clause correspond
application contexts.
to clauses which would be included in an application context
definition (as listed in annex A).
6.5 Component ASEs
Such an application context definition always includes the
This section lists the ASEs required for the application con-
information described in 6.1, 6.2, 6.3, 6.5, 6.9 and 6.11 of this
text being defined. For each ASE in the application context,
clause. Information described in the other subclauses (6.4,
include subclauses as folio ws:
6.6-6.8, 6.10, 6.12) should be included when necessary.
OSI TP does not state where the modules responsible for 6.5.n name
maintaining the MACF rules for User-ASEs (if there are such
6.5.n.l reference (eg /SO//EC standard number)
rules) are located. The understanding here is that the MACF 6.5.n.2 version number
rules for User-ASEs are implemented inside the TPSUI
6.5.n.3 brief description
(which for this purpose is subdivided into a User-MACF and
a multiple association service user invocation (MASUI),
with a value ‘n’ for each specific ASE.
which is the receiver of the genuine multiple association
service).
In addition to the two mandatory ASEs (TP-ASE and ACSE),
other ASEs (eg CCR), and the User-ASEs incorporated in the
Application specific control functions which include OSI TP
application context are to be listed.
are constrained by the very strict control which OSI TP ex-
ercises on the PSAPs (choosing presentation services; clos-
Note - At least one U ser-A SE will always be required, unless the
ing, opening PSAPs; etc).
context on ly applies to a TP Channel.
6.1 Application context name 6.6 Use of other related ASEs
A globally unambiguous name of ASN.1 datatype OBJECT
if the application context requires the knowledge of the use
IDENTIFIER which identifies the application context defi-
of other ASEs on other associations in the AEis at one or both
nition. ends of the association, this clause iis ts them.
An application context name has to be registered to ensure This will include ASEs whose services will be invoked on
that the name is unambiguous, in accordance with /SO//EC
other associations to support the semantics of the ex-
7498-3. This registration may be done by recording the de-
changes on the association using this application context.
finition and the allocated name in a Standard. Alternatively,
For an application context which contains OSI TP, these other
a name may be obtained by applying to a Registration Au-
associations may include those supporting dialogues of a
thority that has the authority to assign application context
dialogue tree, one of whose dialogues is supported by an
names in accordance with the procedures of /SO//EC 9834-7.
association with this application context.
- Obtaining an appropriate object identifier requires using the
Note
rules of /SO//EC 9834- 1, Registration Authorities, and IS0 8805, Basic Note - In a particular instance, a real system using this application
Encoding Rules. If this application context is to be standardised context may use on other dialogues of the dialogue tree ASEs that
internationally or nationally, then its name should be taken from the are not listed here. ASEs are only listed here if the semantics of
registration authority for the international or national name space. exchanges under this application context necessarily require the
If it is to be a private name, it can be taken from a private name use of the ASE on another association.
space, but still following the basic rules of object identifiers.
6.7 Persistent application context rules
6.2 Purpose and scope
This section defines any additional rules to be enforced by
this application context, that supplement and impose re-
A brief outline of the purpose
of the appiica tion con text, to-
strictions in addition to those specified in the referenced base
ge ther with a brief scope state lmen t.
standards, concerning information that has a lifetime that is
greater than that of an association.
6.3 Referenced standards
The OSI TP SACF procedures defined in clause IO of iSO/iEC
A list of those standards which are referenced
by the appii-
10026-3 relating to association establishment and release
cation context being defined.
should be noted.
6.4 Referenced application contexts
6.8 Control function (SACF/MACF) rules
2

---------------------- Page: 4 ----------------------
ISOAEC 10026=5:1998(E)
@ ISO/IEC
6.8.1 objectives/summary
6.10 Error handling
6.8.2 temporal ordering rules
6.8.3 concatenation rules
This section defines what action should be taken (for exam-
6.8.4 mapping rules
pie, to abort the association) if the rules and constraints of the
6.8.5 references to base standard rules
application context are violated. Unless special error handi-
6.8.6 other rules
ing facilities are available, the following text may be suffi-
cien t:
This section defines rules to be enforced by the control
functions in support of this application context, that supple- “For this application context, if the rules and constraints of
ment and impose restrictions additional to those specified in the application context are violated, an A-Abort request
the base standards. (A reference to the base standards’ rules shall be issued.”
should be included.)
In an application context which contains OSI TP, consider-
It is important to note that the application context definition ation should be given to rolling back the transaction, abort-
specifies, where necessary, how the events of the component ing the association, aborting the dialogue, and/or invoking
ASEs are to be ordered. Any other invocation dependencies the TP-U-Error service primitive.
between the ASEs are specified. The control function rules
may need to specify where a state transition by one ASE re-
6.11 Conformance
guiles other ASEs to change state also.
This clause specifies ail rules which must be followed by an
in addition, the use of several ASEs together on an associ-
implementation in order to be conformant to this application
ation, or the sequential use of different ASEs on an associ-
context. As most standards and ASEs a/ready contain their
ation should be described in this clause.
own conformance requirements, referencing these require-
ments with the following text will often be sufficient for the
For an application context which contains OSI TP, a dis-
application contexrs conformance clause:
tinction must be made between rules relating to the SACF
and MACF. (SACF and MACF rules for OSI TP are defined in
“A conformant implementation shall exhibit external
clauses 10 and 11 of lSO/IEC 10026-3.) In particular, this
behaviour which conforms to the requirements implied by
clause must specify which User-ASE services, if any, replace
or stated in the other clauses of this application context
TP-Data for each state in which the invocation or reception
definition.”
of TP-Data is a valid event.
Note - The concept of conformance to an application context defi-
6.9 Optional features nition is somewhat new, and is subject to further work by the
JTCl /SC21 /WGl Conformance Rapporteur Group; this standard may
therefore change accordingly.
The rules and restrictions on the selection of any optional
features of each component ASE should be stated. in par-
63 2 Collision handling
ticular, for each referenced standard, the required functional
units and options must be specified, noting dependencies
Any additional rules concerned with the prevention and re-
between individual ASEs; it should be noted whether a par-
solution of the collision of services (eg A-Release and P-
ticular functional unit or option is mandatory, is not sup-
Resynchronise) should be specified in this clause. Unless
ported, or may optionally be provided. A brief rationale for
special collision handling is necessary, the following text
their selection may be given.
may be sufficient:
Note - No rules specified in the base standard shail be subject to
relaxation.
“No additional collision handling rules beyond those of
WMEC 10026-3 are required.”

---------------------- Page: 5 ----------------------
0 ISOAEC
lSO/lEC 100264:1998(E)
Annex A
(normative)
Application context proforma when using QSI TP
This annex provides a proforma for an application context
which contains TP, and includes text which must always be A.51 Association Control Service Element (ACSE)
included in the definition of such an application context.
A.51 .I Reference
In this annex, text in italics (except for the references in
clause A.3) is provided for guidance only, and should not be
IS0 8650: 1988 and IS0 8650 Technical Corrigendum I : 1991.
included in any application context definition.
A.&l .2 Version number
A.1 Application context name
Version . . . of the Association Control protocol shall be used.
OBJECT IDENTIFIER name for this application context is
The
. . . . . .
A.5.1.3 Brief description
A.2 Purpose and scope
The Associ ation Control protocol is used to establish and
rele ase the association.
A.3 Referenced standards
A-5.2 Distributed Transaction Processing ASE (TP-ASE)
application context definitio In references in whole or in
This
the following specifications:
part
A.5.2.1 Reference
IS0 8650: 1988, Information Processing Systems - Open
lSO/IEC 10026-3: 1992 clause 9.
Sys terns Interconnection - Protocol specification for the As-
sociation Control Service Element.
A-5.2.2 Version number
IS0 865OXor.l: 1991, Information Processing Systems -
Version . . . of the OSI TP protocol shall be used.
Open Systems Interconnection - Protocol specification for the
Association Control Service Element - Technica/
Corrigendum 1. A-5.2.3 Brief description
ISO/IEC 9805: 1990, Information Processing Systems - Open
A TP-ASE provides for TP APDU generation and reception.
Sys terns Interconnection - Protocol specification for the
Commitment, Concurrency and Recovery Service Element.
A.53 Commitment, Concurrency, and Recovery (CCR)
ASE
ISO/iEC 9805/Amd.2, Information Processing Systems - Open
Systems Interconnection - Protocol specification for the
A.5.3.1 Reference
Commitment, Concurrency and Recovery Service Element -
Amendment 2: Session Mapping Changes.
ISO/IEC 9805: 1990 etc.
ISO/IEC 10026-3: 1992, Information Processing Systems -
Open Systems Interconnection - Distributed Transaction
A.5.3.2 Version number
Processing - Part 3: Protocol Specification.
Version . . . of the CCR protocol shall be used.
A.4 Referenced application contexts
A.5.3.3 Brief description
A.5 Component ASEs
CCR provides two phase commitment facilities for OSI TP.
The foIlowing ASEs shall be contained in any OSI 7-P appli-
Note - Clause A.5.3, which provides a reference to the CC!? protocol,
cation context:
need only be included if the TP commit FU is to be used.
ACSE
TP-ASE Additional ASEs must be included, as follows:
Sample text for these two ASEs, and also for CCR, is pro-
A.5.n Additional component ASEs
vided below. Other ASEs should be listed as required.
4

---------------------- Page: 6 ----------------------
ISOAEC 10026=5:1998(E)
@ ISOAEC
A.5.n.l reference
A.5.n.2 version number
A.1 0 Error handling
A.5.n.3 brief description
have been spcified,
Unless special error handling facilities
with a value 91 for each specific ME.
the following text may be sufficient:
A.6 Use of other related ASEs
H For this application context, if the rules and constraints of
the application context are violated, an A-ABORT request
A.7 Persistent application context rules shall be issued.”
A.1 1 Conformance
A.8 Control function rules
Unless special conformance require ments are necessary, the
8.8.1 SACF rules
following text may be sufficient:
A.8.1.1 objectives/summary
A.8.1.2 temporal ordering rules “A conformant implementation shall exhibit external
A.8.1.3 concatenation rules behaviour which conforms to the requirements implied by
A.8.1.4 mapping ruies or stated in th
...