IEC 61158-5-13:2014

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

Réseaux de communication industriels – Spécifications des bus de terrain –
Partie 5-13: Définition des services de la couche application – Éléments
de type 13
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-13 ®
Edition 2.0 2014-08
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
Industrial communication networks – Fieldbus specifications –

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

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

Partie 5-13: Définition des services de la couche application – Éléments

de type 13
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
PRICE CODE
INTERNATIONALE
CODE PRIX XA
ICS 25.040.40; 35.100.70; 35.110 ISBN 978-2-8322-1738-2

– 2 – IEC 61158-5-13:2014 © IEC 2014
CONTENTS
FOREWORD . 4
INTRODUCTION . 6
1 Scope . 7
1.1 General . 7
1.2 Specifications . 8
1.3 Conformance . 8
2 Normative references . 8
3 Terms, definitions, symbols, abbreviations and conventions . 9
3.1 ISO/IEC 7498-1 terms . 10
3.2 ISO/IEC 8822 terms . 10
3.3 ISO/IEC 9545 terms . 10
3.4 Fieldbus application-layer specific definitions . 10
3.5 Abbreviations and symbols . 17
3.6 Conventions . 18
4 Concepts . 20
4.1 Common concepts . 20
4.2 Type specific concepts . 21
5 Data type ASE . 22
5.1 General . 22
5.2 Formal definition of data type objects . 22
5.3 FAL defined data types . 22
5.4 Data type ASE service specification . 28
6 Type 13 communication model specification . 28
6.1 ASEs . 28
6.2 ARs . 50
6.3 Summary of FAL classes . 57
6.4 Permitted FAL services by AREP role . 58
Bibliography . 59

Figure 1 – The ASEs of Type 13 . 22
Figure 2 – The AR ASE conveys APDUs between APs . 46

Table 1 – Overall structure of the OD . 21
Table 2 – Ident service . 31
Table 3 – Status service . 32
Table 4 – Sync service . 33
Table 5 – NMT-req-invite service . 34
Table 6 – NMT-state-command service . 35
Table 7 – NMT-info service . 36
Table 8 – SDO-write . 38
Table 9 – SDO-write-mult . 39
Table 10 – SDO-read . 41
Table 11 – SDO-read-mult . 42
Table 12 – SDO-abort . 43

Table 13 – PDO-transfer . 45
Table 14 – Conveyance of service primitives by AREP role . 47
Table 15 – Valid combinations of AREP roles involved in an AR . 47
Table 16 – FAL class summary . 57
Table 17 – Services by AREP role . 58

– 4 – IEC 61158-5-13:2014 © IEC 2014
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
INDUSTRIAL COMMUNICATION NETWORKS –
FIELDBUS SPECIFICATIONS –
Part 5-13: Application layer service definition –
Type 13 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-13 has been prepared by subcommittee 65C: Industrial
networks, of IEC technical committee 65: Industrial-process measurement, control and
automation.
This second edition cancels and replaces the first edition published in 2007. This edition
constitutes a technical revision. The main changes with respect to the previous edition are
listed below:
• addition of synchronization feature,
• corrections, and
• editorial improvements.
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 the parts of the IEC 61158 series, under the general title Industrial communication
networks – Fieldbus specifications, can be found on the IEC web site.
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.
– 6 – IEC 61158-5-13:2014 © IEC 2014
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.

INDUSTRIAL COMMUNICATION NETWORKS –
FIELDBUS SPECIFICATIONS –
Part 5-13: Application layer service definition –
Type 13 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 13 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
different Types of the 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
1) the FAL user at the boundary between the user and the Application Layer of the Fieldbus
Reference Model, and
2) 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 IEC 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

– 8 – IEC 61158-5-13:2014 © IEC 2014
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 any given Type of 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 61158-1:2014, Industrial communication networks – Fieldbus specifications – Part 1:
Overview and guidance for the IEC 61158 and IEC 61784 series
IEC 61158-3-13, Industrial communication networks – Fieldbus specifications – Part 3-13:
Data-link layer service definition – Type 13 elements
IEC 61158-4-13, Industrial communication networks – Fieldbus specifications – Part 4-13:
Data-link layer protocol specification – Type 13 elements
IEC 61158-6 (all parts), Industrial communication networks – Fieldbus specifications – Part 6:
Application layer protocol specification
IEC 61158-6-13, Industrial communication networks – Fieldbus specifications – Part 6-13:
Application layer protocol specification – Type 13 elements

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 – Part 1: The Basic Model
ISO/IEC 8822, Information technology – Open Systems Interconnection – Presentation
service definition
ISO/IEC 9545, Information technology – Open Systems Interconnection – Application Layer
structure
ISO/IEC 10731, Information technology – Open Systems Interconnection – Basic Reference
Model – Conventions for the definition of OSI services
IEEE 754, IEEE Standard for Floating-Point Arithmetic
3 Terms, definitions, symbols, abbreviations and conventions
For the purposes of this document, the following terms, definitions, symbols, abbreviations
and conventions apply
– 10 – IEC 61158-5-13:2014 © IEC 2014
3.1 ISO/IEC 7498-1 terms
3.1.1 application entity
3.1.2 application process
3.1.3 application protocol data unit
3.1.4 application service element
3.1.5 application entity invocation
3.1.6 application process invocation
3.1.7 application transaction
3.1.8 real open system
3.1.9 transfer syntax
3.2 ISO/IEC 8822 terms
3.2.1 abstract syntax
3.2.2 presentation context
3.3 ISO/IEC 9545 terms
3.3.1 application-association
3.3.2 application-context
3.3.3 application context name
3.3.4 application-entity-invocation
3.3.5 application-entity-type
3.3.6 application-process-invocation
3.3.7 application-process-type
3.3.8 application-service-element
3.3.9 application control service element
3.4 Fieldbus application-layer specific definitions
For the purposes of this part of IEC 61158, the following terms and definitions apply.
3.4.1
application
function or data structure for which data is consumed or produced
3.4.2
application objects
multiple object classes that manage and provide a run time exchange of messages across the
network and within the network device
3.4.3
application process
part of a distributed application on a network, which is located on one device and
unambiguously addressed
3.4.4
application process identifier
distinguishes multiple application processes used in a device

3.4.5
application process object
component of an application process that is identifiable and accessible through an FAL
application relationship
Note 1 to entry:  Application process object definitions are composed of a set of values for the attributes of their
class (see the definition for Application Process Object Class Definition). Application process object definitions
may be accessed remotely using the services of the FAL Object Management ASE. FAL Object Management
services can be used to load or update object definitions, to read object definitions, and to dynamically create and
delete application objects and their corresponding definitions.
3.4.6
application process object class
class of application process objects defined in terms of the set of their network-accessible
attributes and services
3.4.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.4.8
application relationship application service element
application-service-element that provides the exclusive means for establishing and
terminating all application relationships
3.4.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.4.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.4.11
behavior
indication of how an object responds to particular events
3.4.12
channel
single physical or logical link of an input or output application object of a server to the process
3.4.13
class
set of objects, all of which represent the same kind of system component
Note 1 to entry:  A class is a generalisation of an object; a template for defining variables and methods. All objects
in a class are identical in form and behavior, but usually contain different data in their attributes.

– 12 – IEC 61158-5-13:2014 © IEC 2014
3.4.14
class attributes
attribute that is shared by all objects within the same class
3.4.15
class code
unique identifier assigned to each object class
3.4.16
class specific service
service defined by a particular object class to perform a required function which is not
performed by a common service
Note 1 to entry:  A class specific object is unique to the object class which defines it.
3.4.17
client
a) object which uses the services of another (server) object to perform a task
b) initiator of a message to which a server reacts
3.4.18
controlled node
All nodes except one (this is the Managing Node) in a Type 13 network are of this type
3.4.19
connection
logical binding between application objects that may be within the same or different devices
Note 1 to entry: Connections may be either point-to-point or multipoint.
3.4.20
connection channel
description of a connection between a sink and a source of data items
3.4.21
connection path
an octet stream that defines the application object to which a connection instance applies
3.4.22
connection point
buffer which is represented as a subinstance of an Assembly object
3.4.23
consume
act of receiving data from a producer
3.4.24
consumer
node or sink that is receiving data from a producer
3.4.25
consuming application
application that consumes data
3.4.26
control commands
action invocations transferred from client to server to clear outputs, freeze inputs and/or
synchronise outputs
3.4.27
conveyance path
unidirectional flow of APDUs across an application relationship
3.4.28
cyclic
repetitive in a regular manner
3.4.29
data consistency
means for coherent transmission and access of the input- or output-data object between and
within client and server
3.4.30
device
physical hardware connected to the link
Note 1 to entry:  A device may contain more than one node.
3.4.31
device profile
a collection of device dependent information and functionality providing consistency between
similar devices of the same device type
3.4.32
diagnosis information
all data available at the server for maintenance purposes
3.4.33
end node
producing or consuming node
3.4.34
endpoint
one of the communicating entities involved in a connection
3.4.35
error
discrepancy between a computed, observed or measured value or condition and the specified
or theoretically correct value or condition
3.4.36
error class
general grouping for related error definitions and corresponding error codes
3.4.37
error code
identification of a specific type of error within an error class
3.4.38
event
an instance of a change of conditions
3.4.39
FIFO variable
a Variable Object class, composed of a set of homogeneously typed elements, where the first
written element is the first element that can be read

– 14 – IEC 61158-5-13:2014 © IEC 2014
Note 1 to entry:  On the fieldbus only one, complete element can be transferred as a result of one service
invocation.
3.4.40
frame
denigrated synonym for DLPDU
3.4.41
group
a) general term for a collection of objects
Specific uses:
b) when describing an address, an address that identifies more than one entity
3.4.42
invocation
act of using a service or other resource of an application process
Note 1 to entry:  Each invocation represents a separate thread of control that may be described by its context.
Once the service completes, or use of the resource is released, the invocation ceases to exist. For service
invocations, a service that has been initiated but not yet completed is referred to as an outstanding service
invocation. Also for service invocations, an Invoke ID may be used to unambiguously identify the service invocation
and differentiate it from other outstanding service invocations.
3.4.43
index
address of an object within an application process
3.4.44
instance
the actual physical occurrence of an object within a class that identifies one of many objects
within the same object class
EXAMPLE California is an instance of the object class US-state.
Note 1 to entry:  The terms object, instance, and object instance are used to refer to a specific instance.
3.4.45
instance attributes
attribute that is unique to an object instance and not shared by the object class
3.4.46
instantiated
object that has been created in a device
3.4.47
logical device
a certain FAL class that abstracts a software component or a firmware component as an
autonomous self-contained facility of an automation device
3.4.48
manufacturer ID
identification of each product manufacturer by a unique number
3.4.49
management information
network-accessible information that supports managing the operation of the fieldbus system,
including the application layer
Note 1 to entry:  Managing includes functions such as controlling, monitoring, and diagnosing.

3.4.50
message router
object within a node that distributes messaging requests to appropriate application objects
3.4.51
managing node
One node of a type 13 network must act as a managing node.
3.4.52
multi-point connection
connection from one node to many
Note 1 to entry:  Multipoint connections allow messages from a single producer to be received by many consumer
nodes.
3.4.53
network
a set of nodes connected by some type of communication medium, including any intervening
repeaters, bridges, routers and lower-layer gateways
3.4.54
node
host of one AP, identified by a unique DLCEP-address
3.4.55
object
abstract representation of a particular component within a device, usually a collection of
related data (in the form of variables) and methods (procedures) for operating on that data
that have clearly defined interface and behavior
3.4.56
object dictionary
Collection of definitions. communication specific attributes and parameters, and application
dependent data
3.4.57
object specific service
service unique to the object class which defines it
3.4.58
originator
client responsible for establishing a connection path to the target
3.4.59
physical device
automation or other network device
3.4.60
point-to-point connection
connection that exists between exactly two application objects
3.4.61
pre-established AR endpoint
AR endpoint that is placed in an established state during configuration of the AEs that control
its endpoints
– 16 – IEC 61158-5-13:2014 © IEC 2014
3.4.62
process data
object(s) which are already pre-processed and transferred cyclically for the purpose of
information or further processing
3.4.63
produce
act of sending data to be received by a consumer
3.4.64
producer
node that is responsible for sending data
3.4.65
property
general term for descriptive information about an object
3.4.66
provider
source of a data connection
3.4.67
publisher
role of an AR endpoint that transmits APDUs onto the fieldbus for consumption by one or
more subscribers
Note 1 to entry:  A publisher may not be aware of the identity or the number of subscribers.
3.4.68
publishing manager
role of an AR endpoint in which it issues one or more confirmed service request APDUs to a
publisher to request the publisher to publish a specified object
Note 1 to entry:  Two types of publishing managers are defined by this standard, pull publishing managers and
push publishing managers, each of which is defined separately.
3.4.69
push publisher
type of publisher that publishes an object in an unconfirmed service request APDU
3.4.70
push publishing manager
type of publishing manager that requests that a specified object be published using an
unconfirmed service
3.4.71
push subscriber
type of subscriber that recognizes received unconfirmed service request APDUs as published
object data
3.4.72
server
a) role of an AREP in which it returns a confirmed service response APDU to the client that
initiated the request
b) object which provides services to another (client) object
3.4.73
service
operation or function than an object and/or object class performs upon request from another
object and/or object class
3.4.74
subscriber
role of an AREP in which it receives APDUs produced by a publisher
3.4.75
target
end-node to which a connection is established
3.5 Abbreviations and symbols
AE Application entity
AL Application layer
ALME Application layer management entity
ALP Application layer protocol
APO Application object
AP Application process
APDU Application protocol data unit
AR Application relationship
AREP Application relationship end point
ASCII American Standard Code for Information Interchange
ASE Application service element
BNB-PEC Buffered network-scheduled bi-directional pre-established connection
BNU-PEC Buffered network-scheduled uni-directional pre-established connection
CID Connection ID
CN Controlled node
Cnf Confirmation
DL- (as a prefix) data-link-
DLCEP Data-link connection end point
DLL Data-link layer
DLM Data-link-management
DLSAP Data-link service access point
DLSDU DL-service-data-unit
DNS Domain name service
FAL Fieldbus application layer
Ind Indication
IP Internet protocol (see RFC 791)
MN Managing node
NMT Network management
OD Object dictionary
PDO Process data object
PReq PollRequest (Type 13 frame type)
PRes PollRespons (Type 13 frame type)
QUB-CL Queued user-triggered bi-directional connectionless
QUB-COS Queued user-triggered bi-directional connection-oriented with
segmentation
QUU Queued user-triggered uni-directional

– 18 – IEC 61158-5-13:2014 © IEC 2014
Req Request
RPDO Receive process data object
Rsp Response
SDO Service data object
TPDO Transmit process data object

3.6 Conventions
3.6.1 Overview
The FAL is defined as a set of object-oriented ASEs. Each ASE is specified in a separate
subclause. Each ASE specification is composed of two parts, its class specification, and its
service specification.
The class specification defines the attributes of the class. The access to these attributes is
beyond the scope of this document except where specified. The service specification defines
the services that are provided by the ASE.
3.6.2 General conventions
This standard uses the descriptive conventions given in ISO/IEC 10731.
3.6.3 Conventions for class definitions
Class definitions are described using templates. Each template consists of a list of attributes
for the class. The general form of the template is shown below:
FAL ASE: ASE name
CLASS:  Class name
CLASS ID: #
PARENT CLASS: Parent class name
ATTRIBUTES:
1 (o) Key Attribute: numeric identifier
2 (o) Key Attribute: name
3 (m) Attribute: attribute name(values)
4 (m) Attribute: attribute name(values)
4.1 (s) Attribute: attribute name(values)
4.2 (s) Attribute: attribute name(values)
4.3 (s) Attribute: attribute name(values)
5. (c) Constraint: constraint expression
5.1 (m) Attribute: attribute name(values)
5.2 (o) Attribute: attribute name(values)
6 (m) Attribute: attribute name(values)
6.1 (s) Attribute: attribute name(values)
6.2 (s) Attribute: attribute name(values)
SERVICES:
1 (o) OpsService: service name
2 (c) Constraint: constraint expression
2.1 (o) OpsService: service name
3 (m) MgtService: service name

(1) The "FAL ASE:" entry is the name of the FAL ASE that provides the services for the class
being specified.
(2) The "CLASS:" entry is the name of the class being specified. All objects defined using this
template will be an instance of this class. The class may be specified by this standard, or
by a user of this standard.
(3) The "CLASS ID:" entry is a number that identifies the class being specified. This number is
not used for Type 13 elements.
(4) The "PARENT CLASS:" entry is the name of the parent class for the class being specified.
All attributes defined for the parent class and inherited by it are inherited for the class
being defined, and therefore do not have to be redefined in the template for this class.
NOTE The parent-class "TOP" indicates that the class being defined is an initial class definition. The parent class
TOP is used as a starting point from which all other classes are defined. The use of TOP is reserved for classes
defined by this standard.
(5) The "ATTRIBUTES" label indicate that the following entries are attributes defined for the
class.
a) Each of the attribute entries contains a line number in column 1, a mandatory (m) /
optional (o) / conditional (c) / selector (s) indicator in column 2, an attribute type label
in column 3, a name or a conditional expression in column 4, and optionally a list of
enumerated values in column 5. In the column following the list of values, the default
value for the attribute may be specified.
b) Objects are normally identified by a numeric identifier or by an object name, or by
both. In the class templates, these key attributes are defined under the key attribute.
c) The line number defines the sequence and the level of nesting of the line. Each
nesting level is identified by period. Nesting is used to specify
i) fields of a structured attribute (4.1, 4.2, 4.3),
ii) attributes conditional on a constraint statement (5). Attributes may be mandatory
(5.1) or optional (5.2) if the constraint is true. Not all optional attributes require
constraint statements as does the attribute defined in (5.2).
iii) the selection fields of a choice type attribute (6.1 and 6.2).
(6) The "SERVICES" la
...