IEC 61158-6-19:2007

IEC 61158-6-19
Edition 1.0 2007-12
INTERNATIONAL
STANDARD
Industrial communication networks – Fieldbus specifications –
Part 6-19: Application layer protocol specification – Type 19 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-6-19
Edition 1.0 2007-12
INTERNATIONAL
STANDARD
Industrial communication networks – Fieldbus specifications –
Part 6-19: Application layer protocol specification – Type 19 elements

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
U
ICS 35.100.70; 25.040.40 ISBN 2-8318-9497-2

– 2 – 61158-6-19 © IEC:2007(E)

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, abbreviations, symbols and conventions .9
3.1 Referenced terms and definitions .9
3.2 Additional terms and definitions.10
3.3 Additional abbreviations and symbols .11
3.4 Conventions .11
4 Abstract syntax.12
5 Transfer syntax.12
5.1 Introduction .12
5.2 RTC-MDT PDU merged abstract and transfer syntax .12
5.3 RTC-AT PDU merged abstract and transfer syntax .12
5.4 RTC-CC PDU merged abstract and transfer syntax .13
5.5 RTC-MDT PDU encoding.14
5.6 RTC-AT PDU encoding.14
5.7 RTC-CC PDU encoding .14
6 Structure of FAL protocol state machines .15
7 AP-context state machine .16
7.1 Overview .16
7.2 States.17
7.3 States, events and transitions.17
8 FAL service protocol machine (FSPM) .17
8.1 Overview .17
8.2 MGT services .18
8.3 IDN services.18
8.4 CYCIDN services.19
9 Application relationship protocol machine (ARPM) .19

9.1 Overview .19
9.2 Master ARPM .19
9.3 Slave ARPM .21
9.4 Primitives received from the FSPM.22
9.5 Indications received from the DMPM .23
10 DLL mapping protocol machine (DMPM) .24
10.1 Overview .24
10.2 Primitives received from the ARPM.24
10.3 Indications received from the DL .25
Bibliography.26

Figure 1 – Relationships among protocol machines and adjacent layers .15
Figure 2 – APCSM state diagram .16

61158-6-19 © IEC:2007(E) – 3 –

Figure 3 – ARPM master AR state diagram .20

Figure 4 – ARPM slave AR state diagram .21

Table 1 – RTC-MDT PDU attribute format .12

Table 2 – RTC-AT PDU attribute format .13

Table 3 – RTC-CC PDU attribute format.13

Table 4 – RTC-MDT PDU attribute encoding .14

Table 5 – RTC-AT PDU attribute encoding.14

Table 6 – RTC-CC PDU attribute encoding .15
Table 7 – APCSM state-event table .17
Table 8 – Master ARPM state-event table .20
Table 9 – Slave ARPM state-event table .22
Table 10 – ARPM to DL mapping .24
Table 11 – DL to ARPM mapping .25

– 4 – 61158-6-19 © IEC:2007(E)

INTERNATIONAL ELECTROTECHNICAL COMMISSION

____________
INDUSTRIAL COMMUNICATION NETWORKS –

FIELDBUS SPECIFICATIONS –
Part 6-19: Application layer protocol specification – Type 19 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 from their respective intellectual-property-right holders.
International Standard IEC 61158-6-19 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-6 subseries cancel and replace
IEC 61158-6:2003. This edition of this part constitutes a technical addition. This part and its
Type 19 companion parts also cancel and replace IEC/PAS 62410, published in 2005.
This edition of IEC 61158-6 includes the following significant changes from the previous
edition:
a) deletion of the former Type 6 fieldbus for lack of market relevance;
b) addition of new types of fieldbuses;

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

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

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

FDIS Report on voting
65C/476/FDIS 65C/487/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-6-19 © 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 protocol provides the application service by making use of the services

available from the data-link or other immediately lower layer. The primary aim of this standard

is to provide a set of rules for communication expressed in terms of the procedures to be

carried out by peer application entities (AEs) at the time of communication. These rules for

communication are intended to provide a sound basis for development in order to serve a

variety of purposes:
• as a guide for implementors and designers;
• for use in the testing and procurement of equipment;
• as part of an agreement for the admittance of systems into the open systems environment;
• as a refinement to the understanding of time-critical communications within OSI.
This standard is concerned, in particular, with the communication and interworking of sensors,
effectors and other automation devices. By using this standard together with other standards
positioned within the OSI or fieldbus reference models, otherwise incompatible systems may
work together in any combination.

61158-6-19 © IEC:2007(E) – 7 –

INDUSTRIAL COMMUNICATION NETWORKS –

FIELDBUS SPECIFICATIONS –
Part 6-19: Application layer protocol specification – Type 19 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 19 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 define in an abstract way the externally visible service provided by the different
Types of fieldbus Application Layer in terms of
• an abstract model for defining application resources (objects) capable of being
manipulated by users via the use of the FAL service,
• the primitive actions and events of the service;
• the parameters associated with each primitive action and event, and the form which they
take; and
• the interrelationship between these actions and events, and their valid sequences.
The purpose of this standard is to define the services provided to
• the FAL user at the boundary between the user and the Application Layer of the Fieldbus
Reference Model, and
• 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) 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-6-19 © 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, and the corresponding protocols
standardized in subparts of IEC 61158-6.
1.3 Conformance
This standard do 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 any given Type of application layer services as defined in this standard.
2 Normative references
The following referenced documents 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 document (including any amendments) applies.
IEC 61158-3-19, Industrial communication networks – Fieldbus specifications – Part 3-19:
Data-link layer service definition – Type 19 elements
IEC 61158-4-16, Industrial communication networks – Fieldbus specifications – Part 4-16:
Data-link layer protocol specification – Type 16 elements
IEC 61158-4-19, Industrial communication networks – Fieldbus specifications – Part 4-19:
Data-link layer protocol specification – Type 19 elements
IEC 61158-5-19, Industrial communication networks – Fieldbus specifications – Part 5-19:
Application layer service definition – Type 19 elements

ISO/IEC 10731, Information technology – Open Systems Interconnection – Basic Reference
Model – Conventions for the definition of OSI services
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 8824, Information technology – Open Systems Interconnection – Specification of
Abstract Syntax Notation One (ASN.1)

61158-6-19 © IEC:2007(E) – 9 –

3 Terms, definitions, abbreviations, symbols and conventions

3.1 Referenced terms and definitions

3.1.1 ISO/IEC 7498-1 terms
For the purposes of this document, the following terms as defined in ISO/IEC 7498-1 apply:

d) application entity
e) application process
f) application protocol data unit

g) application service element
h) application entity invocation
i) application process invocation
j) application transaction
k) real open system
l) transfer syntax
3.1.2 ISO/IEC 8822 terms
For the purposes of this document, the following terms as defined in ISO/IEC 8822 apply:
a) abstract syntax
b) presentation context
3.1.3 ISO/IEC 9545 terms
For the purposes of this document, the following terms as defined in ISO/IEC 9545 apply:
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.1.4 ISO/IEC 8824 terms
For the purposes of this document, the following terms as defined in ISO/IEC 8824 apply:
a) object identifier
b) type
3.1.5 Fieldbus Data Link Layer terms
For the purposes of this document, the following terms as defined in IEC 61158-3-19 and
IEC 61158-4-19 apply.
a) DL-Time
b) DL-Scheduling-policy
c) DLCEP
– 10 – 61158-6-19 © IEC:2007(E)

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.2 Additional terms and definitions
For the purposes of this document, the following terms and definitions apply.
3.2.1
communication cycle
fixed time period between two master synchronization telegrams in which real-time telegrams
are transmitted in the RT channel and non real-time telegrams are transmitted in the IP
channel
3.2.2
control unit
control device (e.g., a PLC as specified in the IEC 61131 standard family)
3.2.3
control word
two adjacent octets inside the master data telegram containing commands for the addressed
device
3.2.4
cycle time
duration of a communication cycle
3.2.5
device
a slave in the communication network, (e.g., a power drive system as defined in the IEC
61800 standard family, I/O stations as defined in the IEC 61131 standard family).
3.2.6
device status
four adjacent octets inside the acknowledge telegram containing status information for each
device
3.2.7
identification number (IDN)
designation of operating data under which a data block is preserved with its attribute, name,
unit, minimum and maximum input values, and the data

61158-6-19 © IEC:2007(E) – 11 –

3.2.8
little endian
describes a model of memory organisation which stores the least significant octet at the

lowest address, or for transfer, which transfers the lowest order octet first

3.2.9
master data telegram (MDT)
telegram, in which the master inserts its data

3.2.10
protocol
convention about the data formats, time sequences, and error correction in the data exchange
of communication systems
3.2.11
slave
node, which is assigned the right to transmit by the master
3.2.12
status word
two adjacent octets inside the acknowledge telegram containing status information of a device
3.2.13
S-0-nnnn
designation of IDNs
3.3 Additional abbreviations and symbols
AT acknowledge telegram
CC cross communication between participants
IDLE inter packet gap (see IPG)
IDN identification number
IPOSYNC synchronization for PDS interpolator
MDT master data telegram
RTC real-time channel
SERCOS serial real-time communication system interface
3.4 Conventions
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 three parts: its class definitions, its

services, and its protocol specification. The first two are contained in IEC 61158-5-19. The
protocol specification for each of the ASEs is defined in this standard.
The class definitions define the attributes of the classes supported by each ASE. The
attributes are accessible from instances of the class using the Management ASE services
specified in IEC 61158-5-19 standard. The service specification defines the services that are
provided by the ASE.
This standard uses the descriptive conventions given in ISO/IEC 10731.

– 12 – 61158-6-19 © IEC:2007(E)

4 Abstract syntax
The abstract syntax and the transfer syntax are merged into a fixed format that is defined in

the the next clause.
5 Transfer syntax
5.1 Introduction
Type 19 transfer syntax shall be bit-coded, and therefore does not comply with usual data

type specifications such as integer32 and alike.
The octet encoding shall use little endian.
5.2 RTC-MDT PDU merged abstract and transfer syntax
The merged abstract and transfer syntax for attributes belonging to this class is described in
Table 1.
Table 1 – RTC-MDT PDU attribute format
Attribute Format Size (bits)
Control word 4 Octets, bit mapped 32
Reserved field (for future extension) 12 Bits 12
Reserved field (for DLL) 4 Bits 4
Reserved field (for application profile) 5 Bits 5

IPOSYNC: Control unit synchronization bit 1 Bit 1
Reserved field (for application profile) 2 Bits 2
Real-time control bit 2 1 Bit 1
Real-time control bit 1 1 Bit 1
Reserved field (for DLL) 6 Bits 6
Configurable part of data record List of 2, 4 or 8 Octets
Configured cyclic command value 1 2, 4 or 8 Octets
Configured cyclic command value 2 2, 4 or 8 Octets
… …
Configur
...