ISO/IEC 9545:1994 Information technology - Open Systems Interconnection - Application Layer structure

ISO/IEC 9545:1994 Information technology — Open Systems Interconnection — Application Layer structure
https://www.iso.org/standard/17291.html

# 2   Normative references

## 2.1   Identical Recommendations | International Standards
ITU-T Recommendation X.200 (1994)1) | ISO/IEC 7498-1:1994, Information technology — Open Systems Interconnection | Basic Reference Model.
ITU-T  X.200 (1994)1) | ISO/IEC 7498-1:1994, Information technology — Open Systems Interconnection | Basic Reference Model.
ITU-T Recommendation X.210 (1993) | ISO/IEC 10731:1993, Information technology — Open Systems Interconnection — Conventions for the Definition of OSI services.
CCITT Recommendation X.660 (1992) | ISO/IEC 9834-1:1993, Information technology — Open Systems Interconnection — Procedures for the operation of OSI Registration Authorities: General Procedures.
## 2.2   Paired Recommendations | International Standards equivalent in technical content

CCITT Recommendation X.217 (1992), Service definition for the Association Control Service Element.
ISO 8649:1989, Information technology — Open Systems Interconnection — Service Definition for the Association Control Service Element.
CCITT Recommendation X.216 (1988), Presentation service definition for Open Systems Interconnection for CCITT applications.
ISO 8822:1988, Information processing systems — Open Systems Interconnection — Connection oriented presentation service definition.
CCITT Recommendation X.650 (1992), Open Systems Interconnection (OSI) Reference Model for naming and addressing.
ISO 7498-3:1989, Information processing systems — Open Systems Interconnection — Basic Reference Model: Naming and Addressing.


# 3   Definitions

## 3.1   For the purposes of this Recommendation | International Standard, the following terms as defined in ITU-T Rec. X.200 | ISO/IEC 7498-1 apply:

a) abstract syntax;
b) application-entity;
c) application-process;
d) application-process-invocation;
e) application-process-type;
f) (N)-address;
g) (N)-association;
h) (N)-entity;
i) (N)-entity-invocation;
j) (N)-entity-type;
k) (N)-function;
l) (N)-layer;
m) (N)-protocol;
n) (N)-protocol-control-information;
o) (N)-protocol-data-unit;
P) (N)-service-access-point;
q) presentation context;
r) real open system; and
s) transfer syntax.
## 3.2   For the purposes of this Recommendation | International Standard, the following terms as defined in CCITT Rec. X.650 | ISO 7498-3 apply:

a) AEI-identifier;
b) AE-qualifier;
c) AE-title;
d) AE-type-title;
e) AP-invocation-identifier;
f) application-association-identifier;
g) AP-title;
h) (N)-directory-function; and
i) (N)-protocol-addressing-information.
## 3.3   For the purposes of this Recommendation | International Standard, the following terms as defined in ITU-T Rec. X.210 | ISO/IEC 10731 apply:

a) deliver (primitive);
b) OSI-service;
c) OSI-service primitive;
d) OSI-service-user; and
e) submit (primitive).
## 3.4   For the purposes of this Recommendation | International Standard, the following definitions apply.
NOTE — The word "object" is used here in the general English sense.

## 3.4.1 AE-invocation
A specific utilization of part or all of the capabilities of a given application-entity in support of the communications requirements of an application-process-invocation.
Note 1 to entry: This is a specific use of the ASO-invocation concept.
## 3.4.2 AE-type
A description of a class of application-entities in terms of a set of capabilities defined for the Application Layer.
Note 1 to entry: This is a specific use of the ASO-type concept.
## 3.4.3 application-association, association
A cooperative relationship between two ASO-invocations which governs their bilateral use of the Presentation Service for communication of information and coordination of their joint operation.
Note 1 to entry: This is a specific use of the ASO-association concept.
## 3.4.4 application-association-identifier
A name that unambiguously identifies an application-association within the scope of the participating ASO-invocations.
## 3.4.5 application-context
A set of rules shared in common by two ASO-invocations in order to support an application-association.
Note 1 to entry: This is a specific use of the ASO-context concept.
## 3.4.6 application-context-definition
A specification of an application-context.
## 3.4.7 application-context- name
A name that unambiguously identifies an application-context-definition.
## 3.4.8 application-service-element
A set of application-functions that provides a capability for the interworking of application-entity-invocations for a specific purpose; application-service-elements are a component of application-service-objects.
Note 1 to entry: This definition refines the original definition of application-service-elements in ITU-T Rec. X.200 | ΙSΟ/IΕC 7498-1.
## 3.4.9 application-service-object
An active element within (or equivalent to the whole of) the application-entity embodying a set of capabilities defined for the Application Layer that corresponds to a specific ASO-type (without any extra capabilities being used).
Note 1 to entry: This is a specific use of the (N)-entity concept defined in ITU-T Rec. X.200 | ISO/IEC 7498-1.
## 3.4.10 ASE-invocation
A specific utilization of part or all of the capabilities of a given application-service-element.
## 3.4.11 ASE-type
A description of a class of application-service-elements in terms of a set of capabilities defined for the Application Layer.
## 3.4.12 ASO-association
A cooperative relationship among two or more ASO-invocations for the purpose of communication of information and the coordination of their joint operation.
Note 1 to entry: This is a specific use of the (N)-association concept.
## 3.4.13 ASO-association-identifier
A name that unambiguously identifies an ASO-association within the scope of the participating ASO-invocations.
## 3.4.14 ASO-context
A set of rules shared in common among ASO-invocations in order to support an ASO-association.
## 3.4.15 ASO-context-definition
A specification of an ASO-context.
## 3.4.16 ASO-invocation
A specific utilization of part or all of the capabilities of a given ASO (without extra capabilities being used).
Note 1 to entry: This is a specific use of the (N)-entity-invocation concept defined in ITU-T Rec. X.200 | ISO/IEC 7498-1.
## 3.4.17 ASOI-identifier
A name that unambiguously identifies an ASOI within the scope of the pair (parent invocation, ASO).
## 3.4.18 ASOI-tag
A name that unambiguously identifies an ASOI within the scope of the pair (API, ASO).
## 3.4.19 ASO-name
A name that unambiguously identifies an ASO within the scope of an AP.
## 3.4.20 ASO-qualifier
A name that unambiguously identifies an ASO within the scope of its parent.
Note 1 to entry: When the ASO is the AE, the parent of the ASO is the AP. In all other cases, the parent is the parent ASO.
## 3.4.21 ASO-title
A name that unambiguously identifies an ASO in the OSI environment.
## 3.4.22 ASO-type
A description of a class of ASOs in terms of a set of capabilities defined for the Application Layer.
Note 1 to entry: This is a specific use of the (N)-entity-type concepts defined in ITU-T Rec. X.200 | ISO/IEC 7498-1.
## 3.4.23 ASO-type-title
A name that unambiguously identifies an ASO-type in the OSI environment.
## 3.4.24 association control service element
An ASE that provides the exclusive means for establishing and terminating all application-associations.
Note 1 to entry: The functionality of this ASE is defined in CCITT Rec. X.217 | ISO/IEC 8649.
## 3.4.25 child ASO
An ASO is a child ASO of the ASO that immediately contains it.
## 3.4.26 control function
The component of an ASO that controls the interactions among the ASEs and/or ASOs within the containing ASO.
## 3.4.27 parent ASO
An ASO is a parent ASO to its immediately contained ASOs and ASEs.

<!--
(E)
5.3.5 An AE1 is an integral part of an AP-invocation. It supports those activities of an AP-invocation which require
communication within the OS1 environment. There may be Zero, one or more AEIs within an AP-invocation at a
particular Point in time: these AEIs may be, but need not be, of different AE-types.
5.3.6 Communication in the Application Layer takes place among two or more AEIs. These cooperating AEIs may
be of different AE-types. However, where different AE-types are involved, some correspondence and compatibility is
necessary among the behaviours described by the AE-types.
The lifetime of an AE1 is controlled by the AP-invocation which it represents in the OS1 environment. An
5.3.7
AP-invocation may have a longer lifetime than any or all of its AEIs.
54 . Application-service-objects
An application-service-object (ASO) is a composite component that is distinguished for the purpose of
5.4.1
structuring the Application Layer.
5.4.2 An AS0 is a configuration of various groups of application communication functions, each of which has been
separately distinguished for purposes of OS1 Service and protocol specification. The components of such a configuration
are ASEs, other ASOs, and a CF which determines the proper-Ges of the configuration. An AS0 is a composition of:
one or more ASEs and a CF; or
b) one or more ASOs and a CF; or
one or more ASEs and one or more ASOs and a CF.
The component ASOs tan, in turn, be decomposed in the same way. Component ASEs and ASOs may be of the Same or
different type.
5.4.3 An ASO-invocation (ASOI) represents a specific use of the capabilities of an ASO. The behaviour of an AS01
is characterised by:
the OSI-Service which it provides to its OSI-service-user( in conjunction with its peer(s);
b) the APCI contained in the APDUs it exchanges with its peer(s); and
the OSI-Service(s) which it uses.
An AS01 exhibits a communications behaviour within a range specified by its ASO-type. An AS01 includes state
information related to its communication behaviour.
5.4.4 An AE is itself an ASO. It is an AS0 which, in a particular configuration, is not contained by any other ASO.
An AE-type is the ASO-type for the AS0 which is equivalent to the AE. An AE1 is an AS01 of the AS0 which is
equivalent to the AE.
Within an AS01 there are other ASOIs and/or ASEIs which correspond to the ASOs and/or ASEs from which
5.4.5
the relevant AS0 is composed. At a particular Point in time there may be Zero, one or more ASOIs corresponding to a
particular ASO: the actual number is affected by factors including constraints imposed by the CF and by the
requirements of particular instances of communication.
5.4.6 The CF of an AS01 determines how its component ASEIs and ASOIs operate in combination so as to enable
the AS01 to provide a particular OSI-Service as a result of its operating in concert with peer ASOIs.
5.4.7 An ASO-type describes the communication capabilities of ASOs of a particular type. An ASO-type includes:
a definition of the OSI-Service provided by ASOIs of that type as a result of their Operation in concert
with peer ASOIs;
one or more references to component ASE-types and/or ASO-types that are partly or fully included;
a specification of the CF which determines how the component ASEIs and ASOIs of an AS01 of that type
operate in combination and make use of the Presentation Service and/or the OS1 Services provided by
other ASOs or ASEs so as to provide the OSI-Service that is particular to that ASO-type.
An ASO-type may be the subject of international standardization.
NOTE - The creation of appropriate ASO-types is dependent upon a variety of Systems requirements and constraints.
Some ASO-types will be the subject of international standardization; other ASO-types will be the subject of definition in more limited
communities of interest.
The state information modelled by an AS01 (including all its components) reflects the net effect of its
5.4.8
communications with other ASOIs. The existente of this state information provides a basis for modehing the co-
ordinated consecutive, and/or concurrent use of multiple ASO-associations.
NOTE - For example, this provides one possible method for modelling the continuation of an activity following the loss of
an application-association.
5.4.9 The lifetime of an AS01 is determined by the AE1 of which it is a part. An AE1 may have a longer lifetime
than any or all of its component ASOIs. The lifetime of an AS01 is not determined by the duration of the
ASO-associations in which it is a participant. Since an AE1 is an ASOI, at least one AS01 exists for the lifetime of
the AEI.
55 . Application-service-elements
5.5.1 An ASE is an indivisible component of an ASO. It is a combination of application communication functions
within an AS0 that is distinguished for purposes of OS1 Service and protocol specification.
5.5.2 An ASE-type describes the communication capabilities of ASEs of a particular type. An ASE-type specifies
the set of application-protocol-data-units (APDU) handled by the ASE and the procedures governing their use. This
constitutes the application-protocol among ASEs.
5.5.3 An ASE1 represents a specific use of the capabilities of an ASE. The behaviour of an ASE1 is characterized by:
the OSI-Service which it provides to its OSI-service- User(s), in conjunction with its peer(s);
b) the APCI it exchanges with its peer(s); and
its requirements for the use of the Presentation Service, AS0 Services, and ASE Services.
ASEs may occur as components of ASOs at any level of recursion in the Application Layer structure.
5.5.4
5.5.5 An ASE-type may be the subject of international standardization.
NOTE - The creation of appropriate ASE-types is dependent upon a variety of Systems requirements and constraints. Some
ASE-types will be the subject of international standardization; other ASE-types will be the subject of definition in more limited
communities of interest.
56 . Control functions
5.6.1 The specification of a CF is an integral part of an ASO-type. The CF of an AS01 provides the OSI-Service of
the AS01 through Coordination and use of:
a) OSI-Services of component ASOIs and ASEIs, and
b) supporting OSI-Services available to the AS01 which are external to the ASOI; these may be provided by
other ASOIs and/or by the OS1 Presentation Layer.
5.6.2 A CF provides functions of the following kinds:
mapping and Coordination between the OSI-Service provided by the AS01 and the OSI-Services provided
by the component ASOI(s) and ASEI(
b) mapping and Coordination between the supporting OSI-Services provided to the AS01 and the
OSI-Services required by the component ASOI(s) and ASEI(
any other control and Coordination functions that may be necessary to achieve the cooperative Operation
of the component invocations within the ASOI.
The characteristics of the mappings are determined by the properties of the OSI-Services involved: there need not be a
one-to-one mapping between OSI-Service primitives.
NOTE - For instance, a CF of an AS01 may generate a sequence of OSI-Service primitives as a consequence of the
invocation of a Single OSI-Service primitive of the ASOI.
5.6.3 The mapping between OSI-Service primitives of the AS01 and the OSI-Service primitives of the components,
requires the CF of an AS01 to accommodate:
a) Provision for the OSI-Service of the ASOI;
Coordination of the communications behaviour of the components of the AS01 so that they arc consistent
with the range of communications behaviours permitted for a particular ASO-association;
Coordination of communications behaviours on multiple (and possibly concurrent) ASO-associations.
5.6.4 A CF of an AS01 coordinates the use made of OSI-Services and presentation-Services by the components of
the AS01 for their exchange of APDUs with other ASOIs. The CF is required to provide a mapping that preserves the
properties of the Services used by the individual components, by taking into account the characteristics of the supporting
Services.
5.6.5 In mapping APDUs to and from OSI-Services and/or presentation Services, a CF may perform some of the
following functions:
concatenation and Separation of APDUs;
b) transformations of APDUs insofar as they are consistent with both the abstract Syntax that specifies their
generic structure and the shared state of the AEIs exchanging APDUs;
c) generation of APCI to coordinate interworking among its AS01 and ASOIs in other AEIs.
While an AS0 or ASE may be defined in terms of a particular mapping to a supporting Service, the CF of a parent AS0
tan modify the mapping to a different supporting Service as long as the behaviour of the Child AS0 is not affected. This
allows an AS0 or ASE requiring a particular supporting Service to be mapped to a different or equivalent supporting
Service without modifying the AS0 or ASE.
5.6.6 In Order to perform its various functions, the CF of an AS01 may maintain state information that relates to the
local Coordination of the activities of the components of the ASOI. In addition, the CF may maintain state information
that relates to the Coordination of the interactions of the component ASOIs and ASEIs with their peers in other AEIs.
57 . ASO-associations
5.7.1 An ASO-association is a cooperative relationship among two or more ASOIs; it is analogous to an
(N)-association. ASO-associations are formed among peer ASOIs in communicating AEIs. ASO-associations
are abstractions which exist among ASOIs which exchange APDUs. An AE1 that is participating in communications is
Party to at least one ASO-association.
An AS01 may have Zero, one or multiple ASO-associations at a particular Point in time. An AS01 may have
5.7.2
multiple ASO-associations to a Single peer ASOI. An AS01 may also have ASO-associations to multiple peer ASOIs;
these peer ASOIs may be in one AE1 or in different AEIs. Some ASOIs never have ASO-associations.
5.7.3 An AS01 may be a Partner in a number of ASO-associations consecutively or concurrently (or both). The
number of these ASO-associations may Change with time. In particular, there may be periods of time when an AS01 is
not a Party to any ASO-associations.
5.7.4 ASO-associations may be connection-mode or connectionless-mode communications. Within the Application
Layer, there are no architectural restrictions on mappings between connectionless-mode and connection-mode
ASO-associations.
5.7.5 Some ASO-associations are explicitly established. In other cases, there may be no explicit establishment.
Explicit ASO-association establishment occurs when ASOs exchange APDUs containing information relating to their
association (e.g. naming information and the context of the ASOs).
NOTE - The use of common procedures for explici t facilitate the re-use of ASO-
ASO-association establishment
maY tY Pes
as components of other ASO-types.
5.7.6 Coordination among ASO-associations may be local to a Single AE1 and not part of a cooperative relationship.
In such cases, the Coordination is only defined by the CFs within the AE1 and is not a part of the ASO-association.
The characteristics of an ASO-association are described by an ASO-context.
5.7.7
5.7.8 All ASO-associations that are not application-associations ultimately make use of underlying application-
associations (including connectionless data transfer) for communication. Several ASO-associations may make use of the
same application-association at the same time or different times, and any given ASO-association may make use of a
number of application-associations. Constraints on the use of application-associations by ASO-associations are part of
the ASO-type. The CF is responsible for coordinating the use of supporting ASO-associations by the AS01 components.
5.7.9 ASOIs participating in an ASO-association share a common structure. This common structure is either the
whole or subset of the structure of the communicating ASOIs. This is a property of the architecture and need not be
visible in any implementation.
5.7.10 ASOIs participating in an ASO-association may have different roles and need not be of the same ASO-type; as
a consequence they exhibit complementary rather than similar communication behaviours.
5.7.11 ASO-association-identifiers may be required to distinguish different ASO-associations within the same ASOI.
ASO-association identifiers are unambiguous within the scope of the participating ASOIs. The CF may create and/or
make use of these ASO-association-identifiers to coordinate the use of underlying ASO-associations by the AS01
components, including possibly exchanging them with peer-ASOIs in APCI.
58 . ASO-context
Communicating ASOIs must have shared knowledge, and follow a common set of rules that governs their
5.8.1
communication. Such a set of rules is called an ASO-context. An ASO-context describes the permissible collective
communications behaviour of the ASOIs that are Party to a particular ASO-association.
5.8.2 An ASO-context includes:
the enabled communications behaviour;
a set of rules and state information;
the number of ASOIs that may be party to this ASO-association;
the lifetime of the ASO-association and the ways in which it tan be established and terminated.
An ASO-association has only one ASO-context. The set of rules that make up the ASO-context may contain
5.8.3
rules for alteration of that set of rules. The set of rules may contain alternatives, together with rules for selecting among
these alternatives according to the requirements of the AP-invocations.
NOTE - The use of a rule to select among alternative rules within an ASO-context does not constitute an alteration of the
ASO-context. However, the use of a selection rule does Change the state information maintained by ASOIs with respect to an
ASO-association.
5.8.4 An ASO-context may contain shared rules that enable ASOIs to transfer information for multiple
ASO-association Coordination purposes.
When there is no explicit ASO-association establishment, the ASO-context is determined by other means, e.g.
5.8.5
Prior agreements, Systems management, or other application protocols.
5.8.6 The ASO-context that applies to an ASO-association may be negotiated during establishment in either of the
following ways:
by identifying a pre-existing ASO-tontext-definition; or
by transferring an actual description of the ASO-context.
In particular, a name may be used to identify a pre-existing ASO-tontext-definition.
NOTES
1 The predominant method of determining ASO-contexts is expected to be by reference to pre-existing ASO-context-
definitions.
2 The allocation of names to pre-existing ASO-tontext-definitions will be the subject of registration procedures as
described in clause 9 of this Application Layer Structure.
5.8.7 The communications behaviour of an AS01 over an ASO-association is constrained to be compatible with a
generic behaviour defined by the ASO-context in use.
An ASO-context is defined in such a manner as to ensure that the ASE types and/or AS0 types that it
5.8.8
references specify compatible use of supporting OSI-Services.
5.8.9 When an AS01 supports a number of concurrent ASO-associations, there is no architectural requirement that
each of these ASO-associations use the same ASO-context.
The ASO-context of a supporting ASO-association must accommodate the requirements of the ASO-contexts
5.8.10
of all the supported ASO-associations.
59 . AS0 naming
5.9.1 When a particular AS0 or AS01 needs to be identified for the purposes of communication, naming principles
defined by CCITT Rec. X.650 I ISO 7498-3, supplemented by additional qualifiers and identifiers, tan be used to name
the particular AS0 or ASOI. (See Table 1.)
There may be cases where identification remains unambiguous without assigning names to each element of the
ASO/ASOI structure. Such unnamed elements are effectively omitted from the naming structure.
An ASO-name unambiguously identifies an AS0 within the scope of an AP. An ASO-qualifier unambiguously
5.9.2
identifies an AS0 within the scope of its parent. An ASO-name is constructed as a sequence of one or more
ASO-qualifiers. The ASO-name of the AS0 that corresponds to the AE is the AE-qualifier.
5.9.3 Where ASOIs have to be identified, this is done by means of ASOI-identifiers that are unambiguous within the
scope of the pair (parent invocation, ASO). When qualified with the ASO-qualifier, an ASOI-identifier is used to
unambiguously identify an AS01 within the scope of its parent invocation. Thus, in the case where the AS01 is an AEI,
the ASOI-identifier is unambiguous within the scope of the pair (API, AE). In all other cases, the ASOI-identifier is
unambiguous within the scope (parent ASOI, ASO).
5.9.4 An ASOI-tag unambiguously identifies an AS01 within the scope of the API. An ASOI-tag is constructed as a
sequence of one or more occurrences of the pair (ASO-qualifier, ASOI-identifier). The ASOI-tag of the AS01 that
corresponds to the AE1 is the pair (AE-qualifier, AEI-identifier).
Table 1
IS UNAMBIGUOUSLY
ITEM IN THE SCOPE OF WHICH CONSISTS OF
IDENTIFIED BY
AS0 Parent ASO-qualifier
Sequence of
AS0 AP ASO-name
ASO-qualifiers
AP-title, sequence of ASO-
AS0 OS1 environment ASO-title
qualifiers
Parent-invocation Pair (ASO-qualifier,
ASOI
ASOI-identifier)
AS01 Pair (parent-invocation, AS01 identifier
ASO)
Sequence of pairs
AS01 AP-invocation ASOI-tag
(AS0 qualifier,
ASOI-identifier)
An ASO-title unambiguously identifies the AS0 within the OS1 environment. It consists of the AP-title
5.9.5
qualified by a sequence of ASO-qualifiers. If the AS0 is an AE, there will be only one ASO-qualifier in the sequence.
5.9.6 When ASO-types have to be identified, this is done by means of an ASO-type-title that is unambiguous in the
OS1 environment.
5.10 Application-associations
5.10.1 An application-association is a particular kind of ASO-association between two ASOIs which governs their
bilateral use of the Presentation Service for the communication of information and Coordination of their joint Operation.
NOTE - The lifetime of an ASO-association may be less than, equal to or greater than the lifetime of an application-
association.
5.10.2 An AS01 may support a number of application-associations consecutively or concurrently (or both), with one
or more other ASOIs.
5.10.3 An application-association-identifier may be associated with an application-association. This application-
association-identifier is unambiguous within the scope of the pair of associated ASOIs. It provides the means to identify
the related state information in each ASOI.
5.11 Application-context
5.11.1 An application-context is a particular kind of ASO-context. It describes the permissible collective
ications behaviour of the ASOIs that are party to a particular ASO-ssociation that is an application-association.
commun
5.11.2 An application-context is defined in such a manner as to ensure that the ASE-types and/or ASO-types that it
references specify compatible use of Presentation and ACSE Services.
5.12 Names and directory functions
### 5.12.1 As specified in CCITT Rec. X.650 I ISO 7498-3, application-directory-functions process presentation-
addresses, AE-titles, and application-protocol-addressing-information to provide mappings among these categories of
information. To accommodate the concept of the ASO, these functions may also include the processing of ASO-titles.
Thus, application-directory-functions provide mapping among categories of information including ASO-titles.
Conceptually, these functions are performed by the AE1 to derive the addressing information required.
### 5.12.2 
Information on these mappings may be held locally and made available for access by application-directory-
functions, or it may be held remotely. It is a local responsibility to retrieve the information and make it available to an
application-directory-function. If this information is stored remotely, OS1 protocols may be used to access that
information.
NOTE - It is not required that every AE-type contain an ASE-type that provides for retrieval of this remote information;
where necessary, local System management may obtain this capability from another AE1 or ASOI, even another AE1 or AS01 in
another AP-invocation.
### 5.12.3 
Application-directory-functions are application-functions that are modelled within the AE independent of any
particular ASEs or ASOs. Other such application-functions may support aspects of security activities, management
activities, etc.
### 5.12.4
 In CCITT Rec. X.650 I ISO 7498-3, several kinds of name are described in Order to enable the identification of
certain objects in the Application Layer. These kinds of name are:
application-association-identifier;
application-entity-invocation-identifier;
application-entity-title;
application-entity-type-title;
application-process-invocation-identifier;
application-process-title.
The ways in which they may be used in the Operation of application-directory-functions and the identification of specific
Application Layer objects are described in CCITT Rec. X.650 I ISO 7498-3.
### 5.12.5 Additionally, the following kinds of names for Application Layer objects are defined in this Application Layer
Structure and may be included as part of the Operation of application-directory-functions:
a) AE-qualifier;
b) ASO-association-identifier;
c) ASOI-identifier;
d) ASOI-tag;
e) ASO-name;
f) ASO-qualifier;
g) ASO-title; and
h) ASO-type-title.
# 6 Operation of application-entity-invocations
## 6.1 . Use of application-associations
### 6.1.1 
Capabilities for the establishment and termination of application-associations are contained in a specific ASE:
the ACSE. Application-associations tan only be established and terminated by use of ACSE.
### 6.1.2 
In an AS0 containing ACSE, it is the responsibility of the CF to coordinate the application-association needs
of the various ASEs and ASOs. It is the CF that makes use of ACSE to establish and terminate the application-
association.
### 6.1.3 
In establishing an application-association, the location of the peer AE is identified to the Presentation Service
by the presentation address of the peer AE. Additionally one or both of the following identifiers may be used for the
selection of a peer AEI:
a) AP-invocation-identifier;
b) AE-invocation-identifier.
An application-association identifier may also be used to identify the application-association.
### 6.1.4 
The termination of an application-association results from the action of the related ASOIs. ASOIs may take
such action in response to a failure in communications visible in the Presentation Service.
## 6.2 . Operation of ASO-invocations and ASE-invocations
### 6.2.1 
Direct access to the Presentation Service only occurs from the CF of the outermost AS01 (that is from the
AEI). The use of a Presentation Service by the CF of such an outermost AS01 is mapped 1: 1 to the actual Presentation
Service.
### 6.2.2 
The mapping of AS01 requirements for supporting Presentation Services onto the actual Presentation Service in
a Situation where the AS01 is in a deeply nested set of AS01 is dependent upon the combined actions of all the CFs on
the path between it and the actual Presentation Service. The resultant mapping may, but need not, be of a 1: 1 nature.
### 6.2.3 
When an AS01 contains ACSE invocations, that AS01 coordinates all communications activities on the ASO-
associations established by the ACSE invocations. An AS01 containing ACSE holds the state information for the
ASO-association. In addition, these ASO-associations tan be used by other ASOIs via the OSI-Services offered by the
AS01 containing the ACSE invocation.
Interaction with the supporting Service
## 6.3 
An AS01 may interact with supporting Services provided by the Presentation Layer or by other AS01 as
### 6.3.1
coordinated and possibly remapped by the CF of the parent ASOI.
### 6.3.2 
The communicating ASOIs use supporting Services to transfer APDUs among each other. The method of use
of supporting Services is prescribed by the rules of the ASO-context of an ASO-association.
The structure of the APDUs of an ASE is specified by at least one named abstract Syntax. To transfer these
### 6.3.3
APDUs among ASOIs using the supporting Services it is ultimately necessary to establish one or more presentation-
contexts for each abstract Syntax. Esch presentation-context specifies a pairing of a particular abstract Syntax with a
transfer Syntax. It is the responsibility of the control function to make sure that all the necessary presentation-contexts
are established.

## 6.4  Interaction with the Presentation Layer
### 6.4.1 
For the purpose of communication, an application-association makes use of a Single presentation-connection or
a Single use of the connectionless mode presentation-Service. Other ASO-associations make use of one or more
underlying ASO-associations.
### 6.4.2 An AE 
is attached to one or more presentation-service-access-Points in Order to make it addressable in the OS1
environment. An AE is named in the OS1 environment by its application-entity-title. The AE-title is associated with a
presentation-address for purposes of establishing communication with the AE. The relation of the AE-title and
presentation-address may be recorded in the OS1 Directory Facility.
### 6.4.3 
In requesting the establishment of a presentation-connection, an AE1 identifies to the presentation-Service, the
location of a peer AE by its presentation-address.
### 6.4.4 In addition, related AEIs 
may transfer AP-title and AE-title information during the establishment of an
application-association. This information identifies the peer AEs in a way that is independent of their presentation-
addresses.
### 6.4.5 The communicating AEIs 
use the presentation-Service to transfer APDUs among one other. The method of use of the presentation-Service is prescribed by the rules of the application-context of an application-association.
6.4.6 An application-association 
is bound to a Single presentation-connection. It does not span concurrent or consecutive supporting presentation-connections.
NOTE - In this way an application-association is a restricted use of the (N)-association concept. The general
(N)-association concept allows such spanning. An ASO-association, on the other hand, is not bound by this restriction.
## 6.5  Error recovery and ASO-association
## 6.5.1 The action 
to be taken in the event of errors that are visible within an ASO-association is prescribed by rules in
the ASO-context of the ASO-association. Following such errors, the ASO-association may be terminated or, in some
cases, communication may be resumed from a mutually acceptable Point.
ASO-association as part of the error
## 6.5.2 An ASO-association-identifier 
may be used to denote a particular procedures specified in an ASO-context.
recovery
# 7 Application Layer specifications
## 7.1  Categories of specification
The Operation of the Application Layer is described by the following kinds of specifications:
### 7.1.1
a) ASE-type definitions;
b) ASO-type definitions including CF specifications;
NOTE 1 - An AE-type defmition is a particular example of an ASO-type definition.
c) ASO-context definitions.
NOTE 2 - An application-tontext-definition is a special case of ASO-tontext-definition.
### 7.1.2 A Recommendation or International Standard 
which includes Application Layer functions within its scope may include combinations of one or more specifications from these categories. In addition it may reference one or more
specifications from these categories in other Recommendations and International Standards.
NOTE - This does not imply that all ASE- or ASO-types must be defined in such a way that they tan be referenced from
other Recommendations and International Standards. Nevertheless the feasibility of using particular Application Layer specifications
to support a variety of requirements is enhanced by structuring Standards documentation in a way that separates specifications of
different categories. For example, the publication of application-tontext-definitions as separate Standards may be useful in this
respect.

## 7.2 Relationships among specifications
### 7.2.1 An ASO-tontext-definition 
may reference one or more ASO-types in Order to identify rules governing the
mutual interactions of peer ASOIs. Alternatively, ASO-types may reference ASO-tontext-definitions.
An ASO-type may reference other ASO-types. In addition, it may reference ASE-types and the Presentation
### 7.2.2 Service definition (CCITT Rec. X.216 I ISO 8822).
### 7.2.3 An ASE-type 
may make general reference to other ASE-types and/or ASO-types; in addition, it may reference the Presentation Service definition (CCITT Rec. X.216 I ISO 8822).
-->
# 参考資料
@kazuo_reve 自動車の故障診断に関連するプログラマーになりたての方が参照するとよさそうな情報
https://qiita.com/kazuo_reve/items/f773b320dcbf2ab316da

@kazuo_reve AUTOSARのClassic PlatformとAdaptive PlatformにおけるDiagnosticsの違いを整理
https://qiita.com/kazuo_reve/items/05c179d705c69286b94a

私のAdvent Calendar 2022 ーー はじめたきっかけ、1月のふりかえり、今後の展望
https://qiita.com/torifukukaiou/items/891db4e40a7f6194af56

## 自己参照
今、Calendar2021を書いている理由
https://qiita.com/kaizen_nagoya/items/dca73e903785bea2a106

ISO Road vehicles Diagnostics 規格調査中　100規格、100記事をめざして。
https://qiita.com/kaizen_nagoya/items/51e29d318585a4219985

ISO Diagnostics 文献（Normative Reference and Bibliography）集め
https://qiita.com/kaizen_nagoya/items/535a0144a343df2c99df

ISO Diagnostics 用語定義(Terms and Definition)と短縮名(short name)集め
https://qiita.com/kaizen_nagoya/items/83cae62d1cb528c3c816

ISO/IEC OSIに学ぶ
https://qiita.com/kaizen_nagoya/items/89562c52f37d6bf0a80d

ISO 14229-1:2020 Road vehicles — Unified diagnostic services (UDS) — Part 1: Application layer
https://qiita.com/kaizen_nagoya/items/3231d9fea536d1b9b1f7

国際規格のNormative Reference
https://qiita.com/kaizen_nagoya/items/b94b6055997119ac2d9a

@kazuo_reveさんの「自動車の故障診断に関連するプログラマーになりたての方が参照するとよさそうな情報」の読み方
https://qiita.com/kaizen_nagoya/items/0c6b8373f93ce52def33

@kazuo_reve「AUTOSARのClassic PlatformとAdaptive PlatformにおけるDiagnosticsの違いを整理」で慌てて
https://qiita.com/kaizen_nagoya/items/d3ff6aba9b7402e8bde8

<この項は書きかけです。順次追記します。>
This article is not completed. I will add some words and/or centences in order.
Este artículo no está completo. Agregaré algunas palabras en orden.

## 知人資料
' @kazuo_reve 私が効果を確認した「小川メソッド」
https://qiita.com/kazuo_reve/items/a3ea1d9171deeccc04da

' @kazuo_reve 新人の方によく展開している有益な情報
https://qiita.com/kazuo_reve/items/d1a3f0ee48e24bba38f1

' @kazuo_reve Vモデルについて勘違いしていたと思ったこと
https://qiita.com/kazuo_reve/items/46fddb094563bd9b2e1e

## 自己記事一覧
Qiitaで逆リンクを表示しなくなったような気がする。時々、スマフォで表示するとあらわることがあり、完全に削除したのではなさそう。2024年４月以降、せっせとリンクリストを作り、統計を取って確率を説明しようとしている。2025年２月末を目標にしていた。

一覧の一覧( The directory of directories of mine.) Qiita(100)
https://qiita.com/kaizen_nagoya/items/7eb0e006543886138f39

仮説（0）一覧（目標100現在40）
https://qiita.com/kaizen_nagoya/items/f000506fe1837b3590df

Qiita(0)Qiita関連記事一覧（自分）
https://qiita.com/kaizen_nagoya/items/58db5fbf036b28e9dfa6

Error一覧 error(0)
https://qiita.com/kaizen_nagoya/items/48b6cbc8d68eae2c42b8

C++ Support(0)　
https://qiita.com/kaizen_nagoya/items/8720d26f762369a80514

Coding(0) Rules, C, Secure, MISRA and so on
https://qiita.com/kaizen_nagoya/items/400725644a8a0e90fbb0

Ethernet 記事一覧　Ethernet(0)
https://qiita.com/kaizen_nagoya/items/88d35e99f74aefc98794

Wireshark 一覧 wireshark(0)、Ethernet(48) 
https://qiita.com/kaizen_nagoya/items/fbed841f61875c4731d0

線網（Wi-Fi）空中線(antenna)(0) 記事一覧(118/300目標)
https://qiita.com/kaizen_nagoya/items/5e5464ac2b24bd4cd001

なぜdockerで機械学習するか 書籍・ソース一覧作成中 (目標100)
https://qiita.com/kaizen_nagoya/items/ddd12477544bf5ba85e2

プログラムちょい替え（0）一覧:4件
https://qiita.com/kaizen_nagoya/items/296d87ef4bfd516bc394

言語処理100本ノックをdockerで。python覚えるのに最適。:10+12
https://qiita.com/kaizen_nagoya/items/7e7eb7c543e0c18438c4

Python(0)記事をまとめたい。
https://qiita.com/kaizen_nagoya/items/088c57d70ab6904ebb53

安全（0）安全工学シンポジウムに向けて: 21
https://qiita.com/kaizen_nagoya/items/c5d78f3def8195cb2409

プログラマによる、プログラマのための、統計(0)と確率のプログラミングとその後
https://qiita.com/kaizen_nagoya/items/6e9897eb641268766909

転職(0)一覧
https://qiita.com/kaizen_nagoya/items/f77520d378d33451d6fe

技術士(0)一覧
https://qiita.com/kaizen_nagoya/items/ce4ccf4eb9c5600b89ea

Reserchmap(0) 一覧
https://qiita.com/kaizen_nagoya/items/506c79e562f406c4257e

物理記事　上位100
https://qiita.com/kaizen_nagoya/items/66e90fe31fbe3facc6ff

量子(0) 計算機, 量子力学 
https://qiita.com/kaizen_nagoya/items/1cd954cb0eed92879fd4

数学関連記事１００
https://qiita.com/kaizen_nagoya/items/d8dadb49a6397e854c6d

coq(0) 一覧
https://qiita.com/kaizen_nagoya/items/d22f9995cf2173bc3b13

統計(0)一覧
https://qiita.com/kaizen_nagoya/items/80d3b221807e53e88aba

図(0) state, sequence and timing. UML and お絵描き 
https://qiita.com/kaizen_nagoya/items/60440a882146aeee9e8f

色(0) 記事100書く切り口 
https://qiita.com/kaizen_nagoya/items/22331c0335ed34326b9b

品質一覧 
https://qiita.com/kaizen_nagoya/items/2b99b8e9db6d94b2e971

言語・文学記事　１００
https://qiita.com/kaizen_nagoya/items/42d58d5ef7fb53c407d6

医工連携関連記事一覧
https://qiita.com/kaizen_nagoya/items/6ab51c12ba51bc260a82

水の資料集(0)　方針と成果
https://qiita.com/kaizen_nagoya/items/f5dbb30087ea732b52aa

自動車　記事　１００
https://qiita.com/kaizen_nagoya/items/f7f0b9ab36569ad409c5

通信記事１００
https://qiita.com/kaizen_nagoya/items/1d67de5e1cd207b05ef7

日本語（０）一欄
https://qiita.com/kaizen_nagoya/items/7498dcfa3a9ba7fd1e68

英語(0) 一覧
https://qiita.com/kaizen_nagoya/items/680e3f5cbf9430486c7d

音楽　一覧(0) 
https://qiita.com/kaizen_nagoya/items/b6e5f42bbfe3bbe40f5d

「@kazuo_reve 新人の方によく展開している有益な情報」確認一覧 
https://qiita.com/kaizen_nagoya/items/b9380888d1e5a042646b

鉄道（０）鉄道のシステム考察はてっちゃんがてつだってくれる
https://qiita.com/kaizen_nagoya/items/faa4ea03d91d901a618a

OSEK OS設計の基礎　OSEK(100)
https://qiita.com/kaizen_nagoya/items/7528a22a14242d2d58a3

coding (101) 一覧を作成し始めた。omake:最近のQiitaで表示しない5つの事象
https://qiita.com/kaizen_nagoya/items/20667f09f19598aedb68

官公庁・学校・公的団体（NPOを含む）システムの課題、官（０）
https://qiita.com/kaizen_nagoya/items/04ee6eaf7ec13d3af4c3

「はじめての」シリーズ　 ベクタージャパン　
https://qiita.com/kaizen_nagoya/items/2e41634f6e21a3cf74eb

AUTOSAR(0)Qiita記事一覧, OSEK(75)
https://qiita.com/kaizen_nagoya/items/89c07961b59a8754c869

プログラマが知っていると良い「公序良俗」
https://qiita.com/kaizen_nagoya/items/9fe7c0dfac2fbd77a945

LaTeX(0) 一覧　
https://qiita.com/kaizen_nagoya/items/e3f7dafacab58c499792

自動制御、制御工学一覧（０）
https://qiita.com/kaizen_nagoya/items/7767a4e19a6ae1479e6b

Rust(0) 一覧　
https://qiita.com/kaizen_nagoya/items/5e8bb080ba6ca0281927

programの本質は計画だ。programは設計だ。
https://qiita.com/kaizen_nagoya/items/c8545a769c246a458c27

登壇直後版 色使い(JIS安全色) Qiita Engineer Festa 2023〜私しか得しないニッチな技術でLT〜 スライド編 0.15
https://qiita.com/kaizen_nagoya/items/f0d3070d839f4f735b2b

プログラマが知っていると良い「公序良俗」
https://qiita.com/kaizen_nagoya/items/9fe7c0dfac2fbd77a945

逆も真：社会人が最初に確かめるとよいこと。OSEK(69)、Ethernet(59)
https://qiita.com/kaizen_nagoya/items/39afe4a728a31b903ddc

統計の嘘。仮説（127）
https://qiita.com/kaizen_nagoya/items/63b48ecf258a3471c51b

自分の言葉だけで論理展開できるのが天才なら、文章の引用だけで論理展開できるのが秀才だ。仮説（136）
https://qiita.com/kaizen_nagoya/items/97cf07b9e24f860624dd

参考文献駆動執筆(references driven writing)・デンソークリエイト編
https://qiita.com/kaizen_nagoya/items/b27b3f58b8bf265a5cd1

「何を」よりも「誰を」。１０年後のために今見習いたい人たち
https://qiita.com/kaizen_nagoya/items/8045978b16eb49d572b2

Qiitaの記事に３段階または５段階で到達するための方法
https://qiita.com/kaizen_nagoya/items/6e9298296852325adc5e

出力(output)と呼ばないで。これは状態(state)です。
https://qiita.com/kaizen_nagoya/items/80b8b5913b2748867840

祝休日・謹賀新年 2025年の目標
https://qiita.com/kaizen_nagoya/items/dfa34827932f99c59bbc

Qiita 1年間をまとめた「振り返りページ」＠2024
https://qiita.com/kaizen_nagoya/items/ed6be239119c99b15828

2024 参加・主催Calendarと投稿記事一覧 Qiita(248)
https://qiita.com/kaizen_nagoya/items/d80b8fbac2496df7827f

主催Calendar2024分析 Qiita(254)
https://qiita.com/kaizen_nagoya/items/15807336d583076f70bc

Calendar 統計
https://qiita.com/kaizen_nagoya/items/e315558dcea8ee3fe43e

LLM 関連 Calendar 2024 
https://qiita.com/kaizen_nagoya/items/c36033cf66862d5496fa

Large Language Model Related Calendar 
https://qiita.com/kaizen_nagoya/items/3beb0bc3fb71e3ae6d66

博士論文 Calendar 2024 を開催します。 
https://qiita.com/kaizen_nagoya/items/51601357efbcaf1057d0

博士論文(0)関連記事一覧
https://qiita.com/kaizen_nagoya/items/8f223a760e607b705e78

coding (101) 一覧を作成し始めた。omake:最近のQiitaで表示しない5つの事象
https://qiita.com/kaizen_nagoya/items/20667f09f19598aedb68

あなたは「勘違いまとめ」から、勘違いだと言っていることが勘違いだといくつ見つけられますか。人間の間違い(human error(125))の種類と対策
https://qiita.com/kaizen_nagoya/items/ae391b77fffb098b8fb4

プログラマの「プログラムが書ける」思い込みは強みだ。３つの理由。仮説（168）統計と確率(17) , OSEK(79)
https://qiita.com/kaizen_nagoya/items/bc5dd86e414de402ec29

出力(output)と呼ばないで。これは状態(state)です。
https://qiita.com/kaizen_nagoya/items/80b8b5913b2748867840

これからの情報伝達手段の在り方について考えてみよう。炎上と便乗。
https://qiita.com/kaizen_nagoya/items/71a09077ac195214f0db

ISO/IEC JTC1 SC7 Software and System Engineering
https://qiita.com/kaizen_nagoya/items/48b43f0f6976a078d907

アクセシビリティの知見を発信しよう！（再び）
https://qiita.com/kaizen_nagoya/items/03457eb9ee74105ee618

統計論及確率論輪講（再び）
https://qiita.com/kaizen_nagoya/items/590874ccfca988e85ea3

読者の心をグッと惹き寄せる7つの魔法
https://qiita.com/kaizen_nagoya/items/b1b5e89bd5c0a211d862

「@kazuo_reve 新人の方によく展開している有益な情報」確認一覧
https://qiita.com/kaizen_nagoya/items/b9380888d1e5a042646b

ソースコードで議論しよう。日本語で議論するの止めましょう（あるプログラミング技術の議論報告）
https://qiita.com/kaizen_nagoya/items/8b9811c80f3338c6c0b0

脳内コンパイラの3つの危険
https://qiita.com/kaizen_nagoya/items/7025cf2d7bd9f276e382

心理学の本を読むよりはコンパイラ書いた方がよくね。仮説（34）
https://qiita.com/kaizen_nagoya/items/fa715732cc148e48880e

NASAを超えるつもりがあれば読んでください。
https://qiita.com/kaizen_nagoya/items/e81669f9cb53109157f6

データサイエンティストの気づき!「勉強して仕事に役立てない人。大嫌い!!」『それ自分かも?』ってなった!!! 
https://qiita.com/kaizen_nagoya/items/d85830d58d8dd7f71d07

「ぼくの好きな先生」「人がやらないことをやれ」プログラマになるまで。仮説（37）　
https://qiita.com/kaizen_nagoya/items/53e4bded9fe5f724b3c4

なぜ経済学徒を辞め、計算機屋になったか（経済学部入学前・入学後・卒業後対応） 転職(1)  
https://qiita.com/kaizen_nagoya/items/06335a1d24c099733f64    

プログラミング言語教育のXYZ。 仮説（52） 
https://qiita.com/kaizen_nagoya/items/1950c5810fb5c0b07be4

【24卒向け】9ヶ月後に年収１０００万円を目指す。二つの関門と三つの道。
https://qiita.com/kaizen_nagoya/items/fb5bff147193f726ad25

「【25卒向け】Qiita Career Meetup for STUDENT」予習の勧め
https://qiita.com/kaizen_nagoya/items/00eadb8a6e738cb6336f

大学入試不合格でも筆記試験のない大学に入って卒業できる。卒業しなくても博士になれる。
https://qiita.com/kaizen_nagoya/items/74adec99f396d64b5fd5

全世界の不登校の子供たち「博士論文」を書こう。世界子供博士論文遠隔実践中心 安全(99)
https://qiita.com/kaizen_nagoya/items/912d69032c012bcc84f2

日本のプログラマが世界で戦える16分野。仮説(53),統計と確率(25) 転職(32)、Ethernet(58)
https://qiita.com/kaizen_nagoya/items/a7e634a996cdd02bc53b

小川メソッド　覚え（書きかけ）
https://qiita.com/kaizen_nagoya/items/3593d72eca551742df68

DoCAP（ドゥーキャップ）って何ですか？
https://qiita.com/kaizen_nagoya/items/47e0e6509ab792c43327

views 20,000越え自己記事一覧
https://qiita.com/kaizen_nagoya/items/58e8bd6450957cdecd81

Views１万越え、もうすぐ１万記事一覧 最近いいねをいただいた213記事
https://qiita.com/kaizen_nagoya/items/d2b805717a92459ce853

amazon 殿堂入りNo1レビュアになるまで。仮説(102)
https://qiita.com/kaizen_nagoya/items/83259d18921ce75a91f4

100以上いいねをいただいた記事16選
https://qiita.com/kaizen_nagoya/items/f8d958d9084ffbd15d2a

水道局10年(1976,4-1986,3)を振り返る
https://qiita.com/kaizen_nagoya/items/707fcf6fae230dd349bf

小川清最終講義、最終講義（再）計画, Ethernet(100) 英語(100) 安全(100)
https://qiita.com/kaizen_nagoya/items/e2df642e3951e35e6a53

＜この記事は個人の過去の経験に基づく個人の感想です。現在所属する組織、業務とは関係がありません。＞
This article is an individual impression based on my individual experience. It has nothing to do with the organization or business to which I currently belong.
Este artículo es una impresión personal basada en mi experiencia personal. No tiene nada que ver con la organización o empresa a la que pertenezco actualmente.
### 文書履歴(document history)
ver. 0.01 初稿 20220212
### 最後までおよみいただきありがとうございました。
いいね　💚、フォローをお願いします。
#### Thank you very much for reading to the last sentence.
Please press the like icon 💚　and follow me for your happy life.
#### Muchas gracias por leer hasta la última oración.
Por favor, haz clic en el ícono Me gusta 💚 y sígueme para tener una vida feliz.