IEC 61158-5-14:2007

IEC 61158-5-14
Edition 1.0 2007-12
INTERNATIONAL
STANDARD
Industrial communication networks – Fieldbus specifications –
Part 5-14: Application layer service definition – Type 14 elements

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.

IEC Central Office
3, rue de Varembé
CH-1211 Geneva 20
Switzerland
Email: inmail@iec.ch
Web: 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.
ƒ Catalogue of IEC publications: www.iec.ch/searchpub
The IEC on-line Catalogue enables you to search by a variety of criteria (reference number, text, technical committee,…).
It also gives information on projects, withdrawn and replaced publications.
ƒ IEC Just Published: www.iec.ch/online_news/justpub
Stay up to date on all new IEC publications. Just Published details twice a month all new publications released. Available
on-line and also by email.
ƒ Electropedia: www.electropedia.org
The world's leading online dictionary of electronic and electrical terms containing more than 20 000 terms and definitions
in English and French, with equivalent terms in additional languages. Also known as the International Electrotechnical
Vocabulary online.
ƒ Customer Service Centre: www.iec.ch/webstore/custserv
If you wish to give us your feedback on this publication or need further assistance, please visit the Customer Service
Centre FAQ or contact us:
Email: csc@iec.ch
Tel.: +41 22 919 02 11
Fax: +41 22 919 03 00
IEC 61158-5-14
Edition 1.0 2007-12
INTERNATIONAL
STANDARD
Industrial communication networks – Fieldbus specifications –
Part 5-14: Application layer service definition – Type 14 elements

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
XC
ICS 35.100.70; 25.040.40 ISBN 2-8318-9462-X

– 2 – 61158-5-14 © IEC:2007(E)

CONTENTS
FOREWORD.4

INTRODUCTION.6

1 Scope.7

1.1 Overview .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 .9
3.2 ISO/IEC 8822 terms .9
3.3 ISO/IEC 9545 terms .9
3.4 ISO/IEC 8824 terms .9
3.5 Fieldbus application-layer specific definitions .9
3.6 Abbreviations and symbols.12
3.7 Conventions .13
4 Concepts .16
5 Data type ASE.16
5.1 Overview .16
5.2 Formal definition of data type objects .16
5.3 FAL defined data types.17
5.4 Data type ASE service specification .37
6 Communication model specification.37
6.1 General .37
6.2 ASEs.38
6.3 Application relationship .82
6.4 Summary of application layer services.85
Bibliography.86

Figure 1 – Application layer entity.38
Figure 2 – Received message processing procedure .60
Figure 3 – AR ASE conveys APDUs between AP .82

Table 1 – Management object base .40
Table 2 – Access group assignment.52
Table 3 – Access rights assignment.53
Table 4 – Services for domain object .53
Table 5 – Service for report object .55
Table 6 – FAL management entity services.62
Table 7 – EM_DetectingDevice service parameters .63
Table 8 – EM_OnlineReply service parameters.64
Table 9 – EM_GetDeviceAttribute service parameters .65
Table 10 – EM_ActiveNotification service parameters .67
Table 11 – EM_ConfiguringDevice service primitives .69
Table 12 – EM_SetDefaultValue service parameter .71

61158-5-14 © IEC:2007(E) – 3 –

Table 13 – Parameters for domain download service .72

Table 14 – Parameters for domain upload service.74

Table 15 – EventRoport service parameters.76

Table 16 – AcknowledgeEventReport service parameters .77

Table 17 – ReportConditionChanging service parameters .78

Table 18 – Read service parameters.79

Table 19 – Write service parameters.80

Table 20 – VariableDistribute service parameters .81

Table 21 – Summary of application layer services.85

– 4 – 61158-5-14 © IEC:2007(E)

INTERNATIONAL ELECTROTECHNICAL COMMISSION

____________
INDUSTRIAL COMMUNICATION NETWORKS –

FIELDBUS SPECIFICATIONS –
Part 5-14: Application layer service definition – Type 14 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 provides no marking procedure to indicate its approval and cannot be rendered responsible for any
equipment declared to be in conformity with an IEC Publication.
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.
NOTE  Use of some of the associated protocol types is restricted by their 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 particular data-link layer protocol type to be used with physical layer and application layer protocols in type
combinations as specified explicitly in the IEC 61784 series. Use of the various protocol types in other
combinations may require permission of their respective intellectual-property-right holders.
International Standard IEC 61158-5-14 has been prepared by subcommittee 65C: Industrial
networks, of IEC technical committee 65: Industrial-process measurement, control and
automation.
This first edition and its companion parts of the IEC 61158-5 subseries cancel and replace
IEC 61158-5:2003. This edition of this part constitutes a technical addition. This part and its
Type 14 companion parts also cancel and replace IEC/PAS 62409, published in 2005.
This edition of IEC 61158-5 includes the following significant changes from the previous
edition:
61158-5-14 © IEC:2007(E) – 5 –

a) deletion of the former Type 6 fieldbus for lack of market relevance;

b) addition of new types of fieldbuses;

c) partition of part 5 of the third edition into multiple parts numbered -5-2, -5-3, …

The text of this standard is based on the following documents:

FDIS Report on voting
65C/475/FDIS 65C/486/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.
The committee has decided that the contents of this publication will remain unchanged until
the maintenance result 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.
NOTE  The revision of this standard will be synchronized with the other parts of the IEC 61158 series.
The 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.

– 6 – 61158-5-14 © IEC:2007(E)

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/TR 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.

61158-5-14 © IEC:2007(E) – 7 –

INDUSTRIAL COMMUNICATION NETWORKS –

FIELDBUS SPECIFICATIONS –
Part 5-14: Application layer service definition – Type 14 elements

1 Scope
1.1 Overview
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 14 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
14 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 Type 14 fieldbus application layer, in

conformance with the OSI Basic Reference Model (ISO/IEC 7498) 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

– 8 – 61158-5-14 © IEC:2007(E)

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.
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 do they 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 14 application layer services as defined in this standard.
2 Normative references
The following referenced standards are indispensable for the application of this document. For
dated references, only the edition cited applies. For undated references, the latest edition of
the referenced standard (including any amendments) applies.
IEC 61131-3, Programmable controllers — Part 3: Programming languages
IEC/TR 61158-1 (Ed.2.0), Industrial communication networks – Fieldbus specifications –
Part 1: Overview and guidance for the IEC 61158 and IEC 61784 series

IEC 61588, Precision clock synchronization protocol for networked measurement and control
systems
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 7498-3, Information technology – Open Systems Interconnection – Basic Reference
Model – Part 3: Naming and addressing
ISO/IEC 8822, Information technology – Open Systems Interconnection – Presentation
service definition
61158-5-14 © IEC:2007(E) – 9 –

ISO/IEC 8824, Information Technology – Abstract Syntax notation One (ASN-1): Specification

of basic notation
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

3 Terms, definitions, symbols, abbreviations and conventions

For the purposes of this document, the following terms as defined in these publications 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 terms
a) object identifier
b) type
3.5 Fieldbus application-layer specific definitions
3.5.1
access control
control on the reading and writing of an object

– 10 – 61158-5-14 © IEC:2007(E)

3.5.2
access Path
association of a symbolic name with a variable for the purpose of open communication

3.5.3
communication macrocycle
set of basic cycles needed for a configured communication activity in a macro network

segment
3.5.4
communication scheduling
algorithms and operation for data transfers occurring in a deterministic and repeatable
manner
3.5.5
configuration (of a system or device)
step in system design: selecting functional units, assigning their locations and defining their
interconnections
3.5.6
cyclic
repetitive in a regular manner
3.5.7
destination FB Instance
FB instance that receives the specified parameters
3.5.8
domain
part of memory used to store code or data
3.5.9
domain download
operation to write data in a domain
3.5.10
domain upload
operation to read data from a domain
3.5.11
entity
particular thing, such as a person, place, process, object, concept, association, or event
3.5.12
bridge
DL-relay entity which performs synchronization between links (buses) and may perform
selective store-and-forward and routing functions to connect two micro network segments
3.5.13
identifier
16-bit word associated with a system variable
3.5.14
index
address of an object within an application process

61158-5-14 © IEC:2007(E) – 11 –

3.5.15
instance
actual physical occurrence of an object within a class that identifies one of many objects

within the same object class
3.5.16
instantiation
creation of an instance of a specified type

3.5.17
management information
network-visible information for the purpose of managing the field system
3.5.18
management information base
organized list of management information
3.5.19
mapping
set of values having defined correspondence with the quantities or values of another set
3.5.20
message filtering
decision on a message according to a special rule
3.5.21
micro segment
part of a network, where special scheduling is implemented
3.5.22
offset
number of octets from a specially designated position
3.5.23
phase
elapsed fraction of a cycle, measured from some fixed origin
3.5.24
process interface
data exchange and information mapping between physical process and application unit

3.5.25
real-time
ability of a system to provide a required result in a bounded time
3.5.26
real-time communication
transfer of data in real-time
3.5.27
real-time Ethernet (RTE)
ISO/IEC 8802-3-based network that includes real-time communication
NOTE 1  Other communication can be supported, providing the real-time communication is not compromised.
NOTE 2  This definition is dedicated, but not limited, to ISO/IEC 8802-3. It could be applicable to other IEEE 802
specifications, for example IEEE 802.11.

– 12 – 61158-5-14 © IEC:2007(E)

3.5.28
schedule
temporal arrangement of a number of related operations

3.5.29
scheduling macrocycle
time interval to implement a specific schedule

3.5.30
source FB Instance
FB instance that sends a specific parameter

3.5.31
time offset
time difference from a specially designated time
3.6 Abbreviations and symbols
AAE Application Access Entity
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
API Application Process Identifier
AR Application Relationship
ARP Address Resolution Protocol
AREP
Application Relationship End Point
ASE Application Service Element
Cnf Confirmation
CR Communication Relationship
CREP Communication Relationship End Point
CSMA/CD Carrier Sense Multiple Access Protocol with Collision Detection
DD Device Description
DHCP Dynamic Host Configuration Protocol

DL- (as a prefix) Data Link-
DLCEP Data Link Connection End Point
DLL
Data Link Layer
DLE Data Link Entity
DLM Data Link-management
DLS Data Link Service
DLSAP Data Link Service Access Point
DLSDU
DL-service-data-unit
ECSME Type 14 communication scheduling management entity
Type 14 Ethernet for Plant Automation
EM_ (as a prefix) Type 14 Management
ESME Type 14 Socket Mapping Entity
FB Function Block
61158-5-14 © IEC:2007(E) – 13 –

FBAP Function Block Application Process

Ind Indication
IP Internet Protocol
LLC
Logical Link Control
LMP Link Management Protocol
MAC Medium Access Control
MAU Medium Attachment Unit
MOB Management Object Base
PAD Pad (bits)
PDU Protocol Data Unit
P/S Publisher/Subscriber
Req Request
Rsp Response
RTE Real-Time Ethernet
RT-Ethernet Real-Time Ethernet
SAP Service Access Point
SDU Service Data Unit
SME System Management Entity
SNTP
Simple Network Time Protocol
TCP Transmission Control Protocol
UDP User Datagram Protocol
3.7 Conventions
3.7.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 attributes are accessible from
instances of the class using the Object Management ASE services specified in Clause 5. The
service specification defines the services that are provided by the ASE.
3.7.2 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)

– 14 – 61158-5-14 © IEC:2007(E)

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
unique within the FAL ASE that will provide the services for this class. When qualified by
the identity of its FAL ASE, it unambiguously identifies the class within the scope of the
FAL. The value "NULL" indicates that the class cannot be instantiated. Class IDs between
1 and 255 are reserved by this standard to identify standardized classes. They have been
assigned to maintain compatibility with existing national standards. CLASS IDs between
256 and 2048 are allocated for identifying user defined classes.
(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" label indicates that the following entries are services defined for the
class.
a) An (m) in column 2 indicates that the service is mandatory for the class, while an (o)
indicates that it is optional. A (c) in this column indicates that the service is conditional.
When all services defined for a class are defined as optional, at least one has to be
selected when an instance of the class is defined.
b) The label "OpsService" designates an operational service (1).
c) The label "MgtService" designates an management service (2).

61158-5-14 © IEC:2007(E) – 15 –

d) The line number defines the sequence and the level of nesting of the line. Each

nesting level is identified by period. Nesting within the list of services is used to specify

services conditional on a constraint statement.

3.7.3 Conventions for service definitions

3.7.3.1 General
This standard uses the descriptive conventions given in ISO/IEC 10731.

The service model, service primitives, and time-sequence diagrams used are entirely abstract

descriptions; they do not represent a specification for implementation.

3.7.3.2 Service parameters
Service primitives are used to represent service user/service provider interactions (ISO/IEC
10731). They convey parameters which indicate information available in the user/provider
interaction.
NOTE 1  See the note under 3.7.3.3 relative to the non-inclusion of service parameters that are appropriate to a
protocol specification or programming interface specification or implementation specification, but not to an abstract
service definition.
This standard uses a tabular format to describe the component parameters of the service
primitives. The parameters that apply to each group of service primitives are set out in tables
throughout the remainder of this standard. Each table consists of up to six columns: a column
for the name of the service parameter, and a column each for those primitives and parameter-
transfer directions used by the service. The possible six columns are:
1) the parameter name;
2) the request primitive’s input parameters;
3) the request primitive’s output parameters;
NOTE 2  This is a seldom-used capability. Unless otherwise specified, request primitive parameters are input
parameters.
4) the indication primitive’s output parameters;
5) the response primitive’s input parameters; and
6) the confirm primitive’s output parameters.
NOTE 3  The request, indication, response and confirm primitives are also known as requestor.submit,
acceptor.deliver, acceptor.submit, and requestor.deliver primitives, respectively (see ISO/IEC 10731).
The service specifications of this standard uses a tabular format to describe the component
parameters of the ASE service primitives. The parameters which apply to each group of
service primitives are set out in tables. Each table consists of up to five columns for the

1) Parameter name,
2) request primitive,
3) indication primitive,
4) response primitive, and
5) confirm primitive.
One parameter (or component of it) is listed in each row of each table. Under the appropriate
service primitive columns, a code is used to specify the type of usage of the parameter on the
primitive specified in the column:
M parameter is mandatory for the primitive
U parameter is a User option, and may or may not be provided depending on dynamic
usage of the service user. When not provided, a default value for the parameter is
assumed.
– 16 – 61158-5-14 © IEC:2007(E)

C parameter is conditional upon other parameters or upon the environment of the service

user.
— (blank) parameter is never present.

S parameter is a selected item.

Some entries are further qualified by items in brackets. These may be

a) a parameter-specific constraint:

“(=)” indicates that the parameter is semantically equivalent to the parameter in the

service primitive to its immediate left in the table.

b) an indication that some note applies to the entry:
“(n)” indicates that the following note "n" contains additional information pertaining to
the parameter and its use.
3.7.3.3 Service procedures
The procedures are defined in terms of
• the interactions between application entities through the exchange of fieldbus Application
Protocol Data Units, and
• the interactions between an application layer service provider and an application layer
service user in the same system through the invocation of application layer service
primitives.
These procedures are applicable to instances of communication between systems which
support time-constrained communications services within the fieldbus application layer.
NOTE  The IEC 61158-5 subseries of standards define sets of abstract services. They are neither protocol
specifications nor implementation specifications nor concrete programming interface specifications. Therefore there
are restrictions on the extent to which service procedures can be mandated in the parts of IEC 61158-5 subseries.
Protocol aspects that can vary among different protocol specifications or different implementations that instantiate
the same abstract services are unsuitable for inclusion in these service definitions, except at the level of
abstraction that is necessarily common to all such expressions.
For example, the means by which service providers pair request and reply PDUs is appropriate for specification in
an IEC 61158-6 protocol specification standard but not in an IEC 61158-5 subseries abstract service definition
standard. Similarly, local implementation methods by which a service provider or service user pairs request and
confirm primitives, or indication and response primitives, is appropriate for an implementation specification or for a
programming interface specification, but not for an abstract service standard or for a protocol standard, except at a
level of abstraction that is necessarily common to all embodiments of the specifying standard. In all cases, the
abstract definition is not permitted to over-specify the more concrete instantiating realization.
Further information on the conceptual service procedures of an implementation of a protocol that realizes the
services of one of the IEC 61158-5 subseries abstract service definitions can be found in IEC/TR 61158-1:2007,
9.6.
4 Concepts
The common concepts and templates used to describe the application layer service in this
standard are detailed in IEC/TR 61158-1, Clause 9.
5 Data type ASE
5.1 Overview
An overview of the data type ASE and the relationships between data types is provided in
IEC/TR 61158-1, 10.1.
5.2 Formal definition of data type objects
The template used to describe the data type class in this clause is detailed in IEC/TR 61158-1,
10.2. This includes the specific ASE structure and the definition of its attributes.

61158-5-14 © IEC:2007(E) – 17 –

5.3 FAL defined data types
5.3.1 Fixed length types
5.3.1.1 Boolean types
5.3.1.1.1 Boolean
CLASS:  Data type
ATTRIBUTES:
1 Data type Numeric Identifier = 1

2 Data type Name = Boolean
3 Format = FIXED LENGTH
4.1 Octet Length = 1
This data type expresses a Boolean data type with the values TRUE and FALSE.
5.3.1.1.2 BOOL
This IEC 61131-3 type is the same as Boolean.
5.3.1.1.3 VT_BOOLEAN
CLASS: Data type
ATTRIBUTES:
2 Data type Name = VT_BOOLEAN
4 Format  = FIXED LENGTH
4.1 Octet Length  = 2
This data type expresses a Boolean data type with the values TRUE (-1) and FALSE (0) (see
Interger16).
5.3.1.2 Bitstring types
5.3.1.2.1 BitString8
CLASS:  Data type
ATTRIBUTES:
1 Data type Numeric Identifier = 22
2 Data type Name = Bitstring8
3 Format = FIXED LENGTH
5.1 Octet Length = 1
This type contains 1 element of type BitString.

5.3.1.2.2 OCTET
This IEC 61131-3 type is the same as Bitstring8.
5.3.1.2.3 BitString16
CLASS:  Data type
ATTRIBUTES:
1 Data type Numeric Identifier = 23
2 Data type Name = Bitstring16
3 Format = FIXED LENGTH
5.1 Octet Length = 2
5.3.1.2.4 WORD
This IEC 61131-3 type is the same as Bitstring16.

– 18 – 61158-5-14 © IEC:2007(E)

5.3.1.2.5 BitString32
CLASS:  Data type
ATTRIBUTES:
1 Data type Numeric Identifier = 24

2 Data type Name = Bitstring32

3 Format = FIXED LENGTH
5.1 Octet Length = 4
5.3.1.2.6 DWORD
This IEC 61131-3 type is the same as Bitstring32.

5.3.1.2.7 BitString64
CLASS:  Data type
ATTRIBUTES:
1 Data type Numeric Identifier = 57
2 Data type Name = Bitstring64
3 Format = FIXED LENGTH
5.1 Octet Length = 8
5.3.1.2.8 LWORD
This IEC 61131-3 type is the same as Bitstring64.
5.3.1.3 Date types
5.3.1.3.1 BinaryDate
CLASS:  Data type
ATTRIBUTES:
1 Data type Numeric Identifier = 11
2 Data type Name = BinaryDate
3 Format = FIXED LENGTH
4.1 Octet Length = 7
This data type is composed of six elements of unsigned values and expresses calendar date
and time. The first element is an Unsigned16 data type and gives the fraction of a minute in
milliseconds. The second element is an Unsigned8 data type and gives the fraction of an hour
in minutes. The third element is an Unsigned8 data type and gives the fraction of a day in
hours. The fourth element is an Unsigned8 data type. Its upper three (3) bits give the day of
the week and its lower five (5) bits give the day of the month. The fifth element is an

Unsigned8 data type and gives the month. The last element is Unsigned8 data type and gives
the year.
5.3.1.3.2 BinaryDate2000
CLASS:  Data type
ATTRIBUTES:
1 Data type Numeric Identifier = 51
2 Data type Name = BinaryDate2000
3 Format = FIXED LENGTH
4.1 Octet Length = 8
This data type is composed of six elements of unsigned values and expresses calendar date
and time. The first element is an Unsigned16 data type and gives the fraction of a minute in
milliseconds. The second element is an Unsigned8 data type and gives the fraction of an hour
in minutes. The third element is an Unsigned8 data type and gives the fraction of a day in
hours. The fourth element is an Unsigned8 data type. Its upper three (3) bits give the day of

61158-5-14 © IEC:2007(E) – 19 –

the week and its lower five (5) bits give the day of the month. The fifth element is an

Unsigned8 data type and gives the month. The last element is Unsigned16 data type and

gives the year.
5.3.1.3.3 Date
CLASS:  Data type
ATTRIBUTES:
1 Data type Numeric Identifier = 50

2 Data type Name = Date
3 Format = FIXED LENGTH
4.1 Octet Length = 7
This data type is composed of six elements of unsigned values and expresses calendar date
and time. The first element is an Unsigned16 data type and gives the fraction of a minute in
milliseconds. The second element is an Unsigned8 data type and gives the fraction of an hour
in minutes. The third element is an Unsigned8 data type and gives the fraction of a day in
hours with the most significant bit indicating Standard Time or Daylight Saving Time. The
fourth element is an Unsigned8 data type. Its upper three (3) bits give the day of the week
and its lower five (5) bits give the day of the month. The fifth element is an Unsigned8 data
type and gives the month. The last element is Unsigned8 data type and gives the year. The
values 0 … 50 correspond to the years 2000 to 2050, the values 51 … 99 correspond to the
years 1951 to 1999.
5.3.1.3.4 DATE
CLASS:  Data type
ATTRIBUTES:
1 Data type Numeric Identifier = not used
2 Data type Name = DATE
3 Format = FIXED LENGTH
4.1 Octet Length = 2
This IEC 61131-3 type is a binary number. The most significant bit of the mos
...