IEC 61158-5-2:2014

IEC 61158-5-2 ®
Edition 3.0 2014-08
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside
Industrial communication networks – Fieldbus specifications –
Part 5-2: Application layer service definition – Type 2 elements

Réseaux de communication industriels – Spécifications des bus de terrain –
Partie 5-2: Définition des services de la couche application – Eléments de type 2

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
either IEC or IEC's member National Committee in the country of the requester. If you have any questions about IEC
copyright or have an enquiry about obtaining additional rights to this publication, please contact the address below or

your local IEC member National Committee for further information.

Droits de reproduction réservés. Sauf indication contraire, aucune partie de cette publication ne peut être reproduite
ni utilisée sous quelque forme que ce soit et par aucun procédé, électronique ou mécanique, y compris la photocopie

et les microfilms, sans l'accord écrit de l'IEC ou du Comité national de l'IEC du pays du demandeur. Si vous avez des

questions sur le copyright de l'IEC ou si vous désirez obtenir des droits supplémentaires sur cette publication, utilisez
les coordonnées ci-après ou contactez le Comité national de l'IEC de votre pays de résidence.

IEC Central Office Tel.: +41 22 919 02 11
3, rue de Varembé Fax: +41 22 919 03 00
CH-1211 Geneva 20 info@iec.ch
Switzerland www.iec.ch
About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.

About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigenda or an amendment might have been published.

IEC Catalogue - webstore.iec.ch/catalogue Electropedia - www.electropedia.org
The stand-alone application for consulting the entire The world's leading online dictionary of electronic and
bibliographical information on IEC International Standards, electrical terms containing more than 30 000 terms and
Technical Specifications, Technical Reports and other definitions in English and French, with equivalent terms in 14
documents. Available for PC, Mac OS, Android Tablets and additional languages. Also known as the International
iPad. Electrotechnical Vocabulary (IEV) online.

IEC publications search - www.iec.ch/searchpub IEC Glossary - std.iec.ch/glossary
The advanced search enables to find IEC publications by a More than 55 000 electrotechnical terminology entries in
variety of criteria (reference number, text, technical English and French extracted from the Terms and Definitions
committee,…). It also gives information on projects, replaced clause of IEC publications issued since 2002. Some entries
and withdrawn publications. have been collected from earlier publications of IEC TC 37,

77, 86 and CISPR.
IEC Just Published - webstore.iec.ch/justpublished
Stay up to date on all new IEC publications. Just Published IEC Customer Service Centre - webstore.iec.ch/csc
details all new publications released. Available online and If you wish to give us your feedback on this publication or
also once a month by email. need further assistance, please contact the Customer Service
Centre: csc@iec.ch.
A propos de l'IEC
La Commission Electrotechnique Internationale (IEC) est la première organisation mondiale qui élabore et publie des
Normes internationales pour tout ce qui a trait à l'électricité, à l'électronique et aux technologies apparentées.

A propos des publications IEC
Le contenu technique des publications IEC est constamment revu. Veuillez vous assurer que vous possédez l’édition la
plus récente, un corrigendum ou amendement peut avoir été publié.

Catalogue IEC - webstore.iec.ch/catalogue Electropedia - www.electropedia.org
Application autonome pour consulter tous les renseignements
Le premier dictionnaire en ligne de termes électroniques et
bibliographiques sur les Normes internationales,
électriques. Il contient plus de 30 000 termes et définitions en
Spécifications techniques, Rapports techniques et autres
anglais et en français, ainsi que les termes équivalents dans
documents de l'IEC. Disponible pour PC, Mac OS, tablettes
14 langues additionnelles. Egalement appelé Vocabulaire
Android et iPad.
Electrotechnique International (IEV) en ligne.

Recherche de publications IEC - www.iec.ch/searchpub
Glossaire IEC - std.iec.ch/glossary
Plus de 55 000 entrées terminologiques électrotechniques, en
La recherche avancée permet de trouver des publications IEC
en utilisant différents critères (numéro de référence, texte, anglais et en français, extraites des articles Termes et
comité d’études,…). Elle donne aussi des informations sur les Définitions des publications IEC parues depuis 2002. Plus
projets et les publications remplacées ou retirées. certaines entrées antérieures extraites des publications des

CE 37, 77, 86 et CISPR de l'IEC.
IEC Just Published - webstore.iec.ch/justpublished

Service Clients - webstore.iec.ch/csc
Restez informé sur les nouvelles publications IEC. Just
Published détaille les nouvelles publications parues. Si vous désirez nous donner des commentaires sur cette
Disponible en ligne et aussi une fois par mois par email. publication ou si vous avez des questions contactez-nous:
csc@iec.ch.
IEC 61158-5-2 ®
Edition 3.0 2014-08
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside
Industrial communication networks – Fieldbus specifications –

Part 5-2: Application layer service definition – Type 2 elements

Réseaux de communication industriels – Spécifications des bus de terrain –

Partie 5-2: Définition des services de la couche application – Eléments de type 2

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
PRICE CODE
INTERNATIONALE
CODE PRIX XH
ICS 25.040.40; 35.100.70; 35.110 ISBN 978-2-8322-1731-3

– 2 – IEC 61158-5-2:2014 © IEC 2014

CONTENTS
FOREWORD . 6

INTRODUCTION . 9

1 Scope . 10

1.1 General . 10

1.2 Specifications . 11

1.3 Conformance . 11

2 Normative references . 11

3 Terms, definitions, symbols, abbreviations and conventions . 13
3.1 ISO/IEC 7498-1 terms . 13
3.2 ISO/IEC 8822 terms . 13
3.3 ISO/IEC 9545 terms . 13
3.4 ISO/IEC 8824-1 terms . 13
3.5 Type 2 fieldbus data-link layer terms . 14
3.6 Type 2 fieldbus application-layer specific definitions. 14
3.7 Type 2 abbreviations and symbols . 22
3.8 Conventions . 23
4 Common concepts . 26
5 Data type ASE . 26
5.1 General . 26
5.2 Formal definition of data type objects . 26
5.3 FAL defined data types . 26
5.4 Data type ASE service specification . 36
6 Communication model specification . 36
6.1 Concepts . 36
6.2 ASEs . 45
6.3 ARs . 175
6.4 Summary of FAL classes . 206
6.5 Permitted FAL services by AR type . 206
Bibliography . 208

Figure 1 – Overview of ASEs and object classes . 38
Figure 2 – Addressing format using MAC, class, instance and attribute IDs . 39

Figure 3 – Identity object state transition diagram . 58
Figure 4 – Static Assembly state transition diagram . 63
Figure 5 – Dynamic Assembly state transition diagram . 64
Figure 6 – Typical timing relationships for acknowledged data production . 74
Figure 7 – Example of a COS system with two acking devices . 75
Figure 8 – Message flow in COS connection – one Connection object, one consumer . 75
Figure 9 – Message flow in COS connection – multiple consumers . 76
Figure 10 – Path Reconfiguration in a ring topology . 88
Figure 11 – CPF2 time synchronization offset clock model . 89
Figure 12 – CPF2 time synchronization system with offset clock model . 90
Figure 13 – CPF2 time synchronization group startup sequence . 93
Figure 14 – Parameter object state transition diagram . 99

Figure 15 – Example of Find_Next_Object_Instance service . 125

Figure 16 – Transmission trigger timer . 169

Figure 17 – Inactivity watchdog timer . 170

Figure 18 – Using tools for configuration . 171

Figure 19 – Production inhibit timer . 172

Figure 20 – Context of transport services within the connection model . 178

Figure 21 – Application–to–application view of data transfer . 178

Figure 22 – Data flow diagram for a link producer . 179

Figure 23 – Data flow diagram for a link consumer . 180
Figure 24 – Triggers . 181
Figure 25 – Binding transport instances to the producer and consumer of a transport
connection that does not have a reverse data path . 182
Figure 26 – Binding transport instances to the producers and consumers of a transport
connection that does have a reverse data path . 182
Figure 27 – Binding transport instances to the producer and consumers of a multipoint
connection when the transport connection does not have a reverse data path . 183
Figure 28 – Binding transport instances to the producers and consumers of a
multipoint connection when the transport connection does have reverse data paths . 183

Table 1 – Valid IANA MIB printer codes for character set selection . 35
Table 2 – Common elements . 42
Table 3 – ST language elements . 43
Table 4 – Type conversion operations. 43
Table 5 – Values of implementation-dependent parameters . 44
Table 6 – Extensions to IEC 61131-3:2003 . 45
Table 7 – Identity object state event matrix . 59
Table 8 – Static Assembly state event matrix . 64
Table 9 – Static Assembly instance attribute access . 64
Table 10 – Dynamic Assembly state event matrix . 65
Table 11 – Dynamic Assembly instance attribute access. 65
Table 12 – Message Router object Forward_Open parameters . 68
Table 13 – Acknowledge Handler object state event matrix . 71

Table 14 – Producing I/O application object state event matrix . 72
Table 15 – Profile identification . 85
Table 16 – Profile default settings and ranges . 85
Table 17 – Profile transports . 85
Table 18 – Default PTP clock settings . 86
Table 19 – Hand_Set clock quality management . 87
Table 20 – Path Reconfiguration Signalling message . 88
Table 21 – Parameter object state event matrix . 99
Table 22 – Status codes . 101
Table 23 – Get_Attribute_All service parameters . 104
Table 24 – Set_Attribute_All service parameters . 106
Table 25 – Get_Attribute_List service parameters . 108

– 4 – IEC 61158-5-2:2014 © IEC 2014

Table 26 – Set_Attribute_List service parameters . 110

Table 27 – Reset service parameters . 112

Table 28 – Start service parameters . 114

Table 29 – Stop service parameters . 116

Table 30 – Create service parameters . 117

Table 31 – Delete service parameters . 119

Table 32 – Get_Attribute_Single service parameters . 120

Table 33 – Set_Attribute_Single service parameters . 122

Table 34 – Find_Next_Object_Instance service parameters . 124
Table 35 – NOP service parameters . 126
Table 36 – Apply_Attributes service parameters . 127
Table 37 – Save service parameters . 129
Table 38 – Restore service parameters . 130
Table 39 – Get_Member service parameters . 132
Table 40 – Set_Member service parameters . 134
Table 41 – Insert_Member service parameters. 135
Table 42 – Remove_Member service parameters . 137
Table 43 – Group_Sync service parameters . 138
Table 44 – Add_AckData_Path service parameters . 140
Table 45 – Remove_AckData_Path service parameters . 141
Table 46 – Get_Enum_String service parameters . 142
Table 47 – Symbolic_Translation service parameters . 144
Table 48 – CM_Open service parameters . 152
Table 49 – CM_Close service parameters . 154
Table 50 – CM_ Unconnected_Send service parameters . 156
Table 51 – CM_Get_Connection_Data service parameters . 158
Table 52 – CM_Search_Connection_Data service parameters . 160
Table 53 – CM_Get_Connection_Data service parameters . 161
Table 54 – I/O Connection object attribute access . 166
Table 55 – Bridged Connection object attribute access . 166
Table 56 – Explicit messaging object attribute access . 167

Table 57 – Connection_Bind service parameters . 173
Table 58 – Service_Name service parameters . 174
Table 59 – How production trigger, transport class, and CM_RPI determine when data
is produced . 177
Table 60 – Transport classes . 188
Table 61 – UCMM_Create service parameters . 199
Table 62 – UCMM_Delete service parameters . 200
Table 63 – UCMM_Write service parameters . 200
Table 64 – UCMM_Abort service parameters . 202
Table 65 – TR_Write service parameters . 203
Table 66 – TR_Trigger service parameters . 203
Table 67 – TR_Packet_arrived service parameters . 204

Table 68 – TR_Ack_received service parameters . 204

Table 69 – TR_Verify service parameters . 205

Table 70 – TR_Status_updated service parameters . 205

Table 71 – FAL class summary . 206

Table 72 – FAL services by AR type . 207

– 6 – IEC 61158-5-2:2014 © IEC 2014

INTERNATIONAL ELECTROTECHNICAL COMMISSION

____________
INDUSTRIAL COMMUNICATION NETWORKS –

FIELDBUS SPECIFICATIONS –
Part 5-2: Application layer service definition –

Type 2 elements
FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote
international co-operation on all questions concerning standardization in the electrical and electronic fields. To
this end and in addition to other activities, IEC publishes International Standards, Technical Specifications,
Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC
Publication(s)”). Their preparation is entrusted to technical committees; any IEC National Committee interested
in the subject dealt with may participate in this preparatory work. International, governmental and non-
governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely
with the International Organization for Standardization (ISO) in accordance with conditions determined by
agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all
interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence
between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in
the latter.
5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any
services carried out by independent certification bodies.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees for any personal injury, property damage or
other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and
expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC
Publications.
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of

patent rights. IEC shall not be held responsible for identifying any or all such patent rights.
Attention is drawn to the fact that the use of the associated protocol type is restricted by its
intellectual-property-right holders. In all cases, the commitment to limited release of
intellectual-property-rights made by the holders of those rights permits a layer protocol type to
be used with other layer protocols of the same type, or in other type combinations explicitly
authorized by its intellectual-property-right holders.
NOTE Combinations of protocol types are specified in IEC 61784-1 and IEC 61784-2.
International Standard IEC 61158-5-2 has been prepared by subcommittee 65C: Industrial
networks, of IEC technical committee 65: Industrial-process measurement, control and
automation.
This third edition cancels and replaces the second edition published in 2010. This edition

constitutes a technical revision.

The main changes with respect to the previous edition are listed below:

• Updates of definitions used by the Time Sync ASE;

• Corrections to numbering of services in 6.2;

• Addition of “member” and and object specific services in 6.2.1.2.1, 6.2.1.2.3, 6.2.1.3.1,
6.2.1.3.20 to 6.2.1.3.23, 6.2.1.3.28, and 6.5;

• Updates of Identity ASE in 6.2.1.2.2;

• Updates of Assembly ASE in 6.2.1.2.3;
• Updates of Message Router ASE in 6.2.1.2.4;
• Updates of Time Sync ASE in 6.2.1.2.6;
• Updates of FAL service status codes in 6.2.1.3.3;
• Miscellaneous clarifications of FAL services in 6.2.1.3.4 to 6.2.1.3.19;
• Updates of Connection Manager ASE in 6.2.2;
• Updates of Connection ASE in 6.2.3;
• Removal of obsolete transport classes 4 to 6 in 6.3.1, 6.3.3 and 6.4;
• Miscellaneous editorial corrections.
The text of this standard is based on the following documents:
FDIS Report on voting
65C/763/FDIS 65C/773/RVD
Full information on the voting for the approval of this standard can be found in the report on
voting indicated in the above table.
This publication has been drafted in accordance with ISO/IEC Directives, Part 2.
A list of all parts of the IEC 61158 series, published under the general title Industrial
communication networks – Fieldbus specifications, can be found on the IEC web site.

– 8 – IEC 61158-5-2:2014 © IEC 2014

The committee has decided that the contents of this publication will remain unchanged until

the stability date indicated on the IEC web site under "http://webstore.iec.ch" in the data

related to the specific publication. At this date, the publication will be

• reconfirmed,
• withdrawn,
• replaced by a revised edition, or

• amended.
IMPORTANT – The 'colour inside' logo on the cover page of this publication indicates
that it contains colours which are considered to be useful for the correct
understanding of its contents. Users should therefore print this document using a
colour printer.
INTRODUCTION
This part of IEC 61158 is one of a series produced to facilitate the interconnection of

automation system components. It is related to other standards in the set as defined by the

“three-layer” fieldbus reference model described in IEC 61158-1.

The application service is provided by the application protocol making use of the services

available from the data-link or other immediately lower layer. This standard defines the

application service characteristics that fieldbus applications and/or system management may

exploit.
Throughout the set of fieldbus standards, the term “service” refers to the abstract capability
provided by one layer of the OSI Basic Reference Model to the layer immediately above.
Thus, the application layer service defined in this standard is a conceptual architectural
service, independent of administrative and implementation divisions.

– 10 – IEC 61158-5-2:2014 © IEC 2014

INDUSTRIAL COMMUNICATION NETWORKS –

FIELDBUS SPECIFICATIONS –
Part 5-2: Application layer service definition –

Type 2 elements
1 Scope
1.1 General
The fieldbus application layer (FAL) provides user programs with a means to access the
fieldbus communication environment. In this respect, the FAL can be viewed as a “window
between corresponding application programs.”
This standard provides common elements for basic time-critical and non-time-critical
messaging communications between application programs in an automation environment and
material specific to Type 2 fieldbus. The term “time-critical” is used to represent the presence
of a time-window, within which one or more specified actions are required to be completed
with some defined level of certainty. Failure to complete specified actions within the time
window risks failure of the applications requesting the actions, with attendant risk to
equipment, plant and possibly human life.
This standard defines in an abstract way the externally visible service provided by the Type 2
fieldbus application layer in terms of
a) an abstract model for defining application resources (objects) capable of being
manipulated by users via the use of the FAL service,
b) the primitive actions and events of the service;
c) the parameters associated with each primitive action and event, and the form which they
take; and
d) the interrelationship between these actions and events, and their valid sequences.
The purpose of this standard is to define the services provided to
a) the FAL user at the boundary between the user and the application layer of the fieldbus
reference model, and
b) Systems Management at the boundary between the application layer and Systems

Management of the fieldbus reference model.
This standard specifies the structure and services of the Type 2 fieldbus application layer, in
conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI application
layer structure (ISO/IEC 9545).
FAL services and protocols are provided by FAL application-entities (AE) contained within the
application processes. The FAL AE is composed of a set of object-oriented application service
elements (ASEs) and a layer management entity (LME) that manages the AE. The ASEs
provide communication services that operate on a set of related application process object
(APO) classes. One of the FAL ASEs is a management ASE that provides a common set of
services for the management of the instances of FAL classes.
Although these services specify, from the perspective of applications, how request and
responses are issued and delivered, they do not include a specification of what the requesting
and responding applications are to do with them. That is, the behavioral aspects of the
applications are not specified; only a definition of what requests and responses they can

send/receive is specified. This permits greater flexibility to the FAL users in standardizing

such object behavior. In addition to these services, some supporting services are also defined

in this standard to provide access to the FAL to control certain aspects of its operation.

1.2 Specifications
The principal objective of this standard is to specify the characteristics of conceptual

application layer services suitable for time-critical communications, and thus supplement the

OSI Basic Reference Model in guiding the development of application layer protocols for time-
critical communications.
A secondary objective is to provide migration paths from previously-existing industrial
communications protocols. It is this latter objective which gives rise to the diversity of services
standardized as the various Types of IEC 61158, and the corresponding protocols
standardized in subparts of IEC 61158-6.
This specification may be used as the basis for formal application programming interfaces.
Nevertheless, it is not a formal programming interface, and any such interface will need to
address implementation issues not covered by this specification, including
a) the sizes and octet ordering of various multi-octet service parameters, and
b) the correlation of paired request and confirm, or indication and response, primitives.
1.3 Conformance
This standard does not specify individual implementations or products, nor does it constrain
the implementations of application layer entities within industrial automation systems.
There is no conformance of equipment to this application layer service definition standard.
Instead, conformance is achieved through implementation of conforming application layer
protocols that fulfill the Type 2 application layer services as defined in this standard.
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and
are indispensable for its application. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any
amendments) applies.
NOTE All parts of the IEC 61158 series, as well as IEC 61784-1 and IEC 61784-2 are maintained simultaneously.
Cross -references to these documents within the text therefore refer to the editions as dated in this list of
normative references.
IEC 61131-3:2003 , Programmable controllers – Part 3: Programming languages
IEC 61158-1:2014, Industrial communication networks – Fieldbus specifications – Part 1:
Overview and guidance for the IEC 61158 and IEC 61784 series
IEC 61158-3-2:2014, Industrial communication networks – Fieldbus specifications – Part 3-2:
Data-link layer service definition – Type 2 elements
IEC 61158-4-2:2014, Industrial communication networks – Fieldbus specifications – Part 4-2:
Data-link layer protocol specification – Type 2 elements
___________
A newer edition of this standard has been published, but only the cited edition applies.

– 12 – IEC 61158-5-2:2014 © IEC 2014

IEC 61158-6-2:2014, Industrial communication networks – Fieldbus specifications – Part 6-2:

Application layer protocol specification – Type 2 elements

IEC 61588:2009, Precision clock synchronization protocol for networked measurement and

control systems
IEC 61784-3-2, Industrial communications networks – Profiles – Part 3-2: Functional safety

fieldbuses – Additional specifications for CPF 2

ISO/IEC 646, Information technology – ISO 7–bit coded character set for information

interchange
ISO/IEC 7498-1, Information technology – Open Systems Interconnection – Basic Reference
Model: The Basic Model
ISO/IEC 8859-1, Information technology – 8-bit single-byte coded graphic character sets –
Part 1: Latin alphabet No. 1
ISO/IEC 9545, Information technology – Open Systems Interconnection – Application Layer
structure
ISO/IEC 10646, Information technology – Universal Coded Character Set (UCS)
ISO/IEC 10731, Information technology – Open Systems Interconnection – Basic Reference
Model – Conventions for the definition of OSI services
ISO/IEC/IEEE 60559, Information technology – Microprocessor Systems – Floating-Point
arithmetic
ISO 639-2, Codes for the representation of names of languages – Part 2: Alpha-3 code
ISO 8859-1 :1987, Information processing – 8-bit single-byte coded graphic character sets –
Part 1: Latin alphabet No. 1
ISO 8859-2 :1987, Information processing – 8-bit single-byte coded graphic character sets –
Part 2: Latin alphabet No. 2
ISO 8859-3 :1988, Information processing – 8-bit single-byte coded graphic character sets –
Part 3: Latin alphabet No. 3
ISO 8859-4 :1988, Information processing – 8-bit single-byte coded graphic character sets –
Part 4: Latin alphabet No. 4
ISO 8859-5 :1988, Information processing – 8-bit single-byte coded graphic character sets –
Part 5: Latin/Cyrillic alphabet
ISO 8859-6 :1987, Information processing – 8-bit single-byte coded graphic character sets –
Part 6: Latin/Arabic alphabet
ISO 8859-7 :1987, Information processing – 8-bit single-byte coded graphic character sets –
Part 7: Latin/Greek alphabet
___________
A newer edition of this standard has been published by ISO/IEC, but the cited edition is the one used in the
referenced IETF standards.
ISO 8859-8 :1988, Information processing – 8-bit single-byte coded graphic character sets –

Part 8: Latin/Hebrew alphabet
ISO 8859-9 :1989, Information processing – 8-bit single-byte coded graphic character sets –

Part 9: Latin alphabet No. 5
ISO 11898:1993 , Road vehicles – Interchange of digital information – Controller area

network (CAN) for high-speed communication

IETF RFC 1759, Printer MIB, available at

3 Terms, definitions, symbols, abbreviations and conventions
For the purposes of this document, the following terms, definitions, symbols, abbreviations
and conventions apply.
3.1 ISO/IEC 7498-1 terms
a) application entity
b) application process
c) application protocol data unit
d) application service element
e) application entity invocation
f) application process invocation
g) application transaction
h) real open system
i) transfer syntax
3.2 ISO/IEC 8822 terms
a) abstract syntax
b) presentation context
3.3 ISO/IEC 9545 terms
a) application-association
b) application-context
c) application context name
d) application-entity-invocation
e) application-entity-type
f) application-process-invocation
g) application-process-type
h) application-service-element
i) application control service element
3.4 ISO/IEC 8824-1 terms
a) object identifier
b) type
___________
A newer edition of this standard has been published, but only the cited edition applies.

– 14 – IEC 61158-5-2:2014 © IEC 2014

3.5 Type 2 fieldbus data-link layer terms

The following terms, defined in IEC 61158-3-2 and IEC 61158-4-2, apply.

a) DL-time
b) DL-scheduling-policy
c) DLCEP
d) DLC
e) DL-connection-oriented mode

f) DLPDU
g) DLSDU
h) DLSAP
i) fixed tag
j) generic tag
k) link
l) MAC ID
m) network address
n) node address
o) node
p) tag
q) scheduled
r) unscheduled
3.6 Type 2 fieldbus application-layer specific definitions
For the purposes of this document, the following terms and definitions apply.
3.6.1
allocate
take a resource from a common area and assign that resource for the exclusive use of a
specific entity
3.6.2
application
function or data structure for which data is consumed or produced

3.6.3
application objects
multiple object classes that manage and provide a run time exchange of messages across the
network and within the network device
3.6.4
application process
part of a distributed application on a network, which is located on one device and
unambiguously addressed
3.6.5
application process object
component of an application process that is identifiable and accessible through an FAL
application relationship
3.6.6
application process object class

class of application process objects defined in terms of the set of their network-accessible

attributes and services
3.6.7
application relationship
cooperative association between two or more application-entity-invocations for the purpose of

exchange of information and coordination of their joint operation

Note 1 to entry: This relationship is activated either by the exchange of application-protocol-data-units or as a
result of preconfiguration activities.

3.6.8
application relationship application service element
application-service-element that provides the exclusive means for establishing and
terminating all application relationships
3.6.9
application relationship endpoint
context and behavior of an application relationship as seen and maintained by one of the
application processes involved in the application relationship
Note 1 to entry: Each application process involved in the application relationship maintains its own application
relationship endpoint.
3.6.10
attribute
description of an externally visible characteristic or feature of an object
Note 1 to entry: The attributes of an object contain information about variable portions of an object. Typically, they
provide status information or govern the operation of an object. Attributes may also affect the behavior of an
object. Attributes are divided into class attributes and instance attributes.
3.6.11
behavior
indication of how an object responds to particular events
3.6.12
Best Master Clock Algorithm
BMCA
algorithm performed by each node to determine the clock that will become the master clock
on a subnet and the grandmaster clock for the domain

Note 1 to entry: The algorithm primarily compares priority1, clock quality, priority2, and source identity to determine
the best master among available candidates.
3.6.13
boundary clock
clock that has multiple Precision Time Protocol (PTP) ports in a domain and maintains the
timescale used in the domain
Note 1 to entry: It may serve as the source of time, i.e., be a master clock, and may synchronize to another clock,
i.e., be a slave clock.
[SOURCE: IEC 61588:2009, 3.1.3, modified – second sentence changed to a Note]

– 16 – IEC 61158-5-2:2014 © IEC 2014

3.6.14
class
set of objects, all of which represent the same kind of system component

Note 1 to entry: A class is a generalization of an object; a template for defining variables and methods. All objects

in a class are
...