IEC 61158-6-19:2019

IEC 61158-6-19 ®
Edition 4.0 2019-06
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
Industrial communication networks – Fieldbus specifications –
Part 6-19: Application layer protocol specification – Type 19 elements

Réseaux de communication industriels – Spécifications des bus de terrain –
Partie 6-19: Spécification du protocole de la couche application – Éléments
de type 19
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é info@iec.ch
CH-1211 Geneva 20 www.iec.ch
Switzerland
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 corrigendum or an amendment might have been published.

IEC publications search - webstore.iec.ch/advsearchform Electropedia - www.electropedia.org
The advanced search enables to find IEC publications by a The world's leading online dictionary on electrotechnology,
variety of criteria (reference number, text, technical containing more than 22 000 terminological entries in English
committee,…). It also gives information on projects, replaced and French, with equivalent terms in 16 additional languages.
and withdrawn publications. Also known as the International Electrotechnical Vocabulary

(IEV) online.
IEC Just Published - webstore.iec.ch/justpublished
Stay up to date on all new IEC publications. Just Published IEC Glossary - std.iec.ch/glossary
details all new publications released. Available online and 67 000 electrotechnical terminology entries in English and
once a month by email. French extracted from the Terms and Definitions clause of
IEC publications issued since 2002. Some entries have been
IEC Customer Service Centre - webstore.iec.ch/csc collected from earlier publications of IEC TC 37, 77, 86 and
If you wish to give us your feedback on this publication or CISPR.

need further assistance, please contact the Customer Service

Centre: sales@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é.

Recherche de publications IEC - Electropedia - www.electropedia.org
webstore.iec.ch/advsearchform Le premier dictionnaire d'électrotechnologie en ligne au
La recherche avancée permet de trouver des publications IEC monde, avec plus de 22 000 articles terminologiques en
en utilisant différents critères (numéro de référence, texte, anglais et en français, ainsi que les termes équivalents dans
comité d’études,…). Elle donne aussi des informations sur les 16 langues additionnelles. Egalement appelé Vocabulaire
projets et les publications remplacées ou retirées. Electrotechnique International (IEV) en ligne.

IEC Just Published - webstore.iec.ch/justpublished Glossaire IEC - std.iec.ch/glossary
Restez informé sur les nouvelles publications IEC. Just 67 000 entrées terminologiques électrotechniques, en anglais
Published détaille les nouvelles publications parues. et en français, extraites des articles Termes et Définitions des
Disponible en ligne et une fois par mois par email. publications IEC parues depuis 2002. Plus certaines entrées
antérieures extraites des publications des CE 37, 77, 86 et
Service Clients - webstore.iec.ch/csc CISPR de l'IEC.

Si vous désirez nous donner des commentaires sur cette
publication ou si vous avez des questions contactez-nous:
sales@iec.ch.
IEC 61158-6-19 ®
Edition 4.0 2019-06
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
Industrial communication networks – Fieldbus specifications –

Part 6-19: Application layer protocol specification – Type 19 elements

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

Partie 6-19: Spécification du protocole de la couche application – Éléments

de type 19
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
INTERNATIONALE
ICS 25.040.40; 35.100.70; 35.110 ISBN 978-2-8322-9119-1

– 2 – IEC 61158-6-19:2019 © IEC 2019
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 Referenced terms and definitions . 9
3.1.1 ISO/IEC 7498-1 terms . 9
3.1.2 ISO/IEC 8822 terms . 9
3.1.3 ISO/IEC 9545 terms . 9
3.1.4 ISO/IEC 8824-1 terms . 9
3.1.5 Fieldbus Data Link Layer terms . 10
3.2 Additional terms and definitions . 10
3.3 Additional abbreviations and symbols . 11
3.4 Conventions . 12
4 Abstract syntax . 12
5 Transfer syntax . 12
5.1 Introduction . 12
5.2 RTC PDU merged abstract and transfer syntax . 12
6 Structure of FAL protocol state machines . 12
7 AP-context state machine . 14
7.1 Overview. 14
7.2 States . 14
7.2.1 Idle . 14
7.2.2 Running . 14
7.3 States, events and transitions . 15
8 FAL service protocol machine (FSPM) . 15
8.1 Overview. 15
8.2 MGT services . 15
8.2.1 Get network status . 15
8.2.2 Get device status . 15
8.2.3 Network status change report . 15
8.2.4 Device status change report . 15
8.2.5 Set device status . 15
8.2.6 Enable RTC . 15
8.2.7 Enable hot-plug . 16
8.2.8 Notify RTC . 16
8.2.9 Disable RTC . 16
8.2.10 Notify error . 16
8.3 IDN services . 16
8.3.1 Read . 16
8.3.2 Write. 16
8.4 CYCIDN services . 16
8.4.1 Read_cyclic . 16

8.4.2 Write_cyclic . 16
8.4.3 Notify_cyclic . 16
9 Application relationship protocol machine (ARPM) . 16
9.1 Overview. 16
9.2 Master ARPM . 17
9.2.1 Overview . 17
9.2.2 State descriptions . 17
9.2.3 States, events and transitions . 18
9.3 Slave ARPM . 18
9.3.1 Overview . 18
9.3.2 State descriptions . 18
9.3.3 States, events and transitions . 19
9.4 Primitives received from the FSPM . 19
9.4.1 FSP-get network status. 19
9.4.2 FSP-get device status . 19
9.4.3 FSP-set device status . 19
9.4.4 FSP-enable RTC . 20
9.4.5 FSP-enable Hot-plug . 20
9.4.6 FSP-disable RTC . 20
9.4.7 FSP-read . 20
9.4.8 FSP-write . 20
9.4.9 FSP-read_cyclic . 20
9.4.10 FSP-write_cyclic . 20
9.5 Indications received from the DMPM . 21
9.5.1 ARP-network status change report. 21
9.5.2 ARP-device status change report . 21
9.5.3 ARP-notify RTC enabled . 21
9.5.4 ARP-notify RTC disabled . 21
9.5.5 ARP-notify_cyclic. 21
9.5.6 ARP-notify Error . 21
10 DLL mapping protocol machine (DMPM) . 21
10.1 Overview. 21
10.2 Primitives received from the ARPM . 22
10.3 Indications received from the DL . 22
Bibliography . 23

Figure 1 – Relationships among protocol machines and adjacent layers . 13
Figure 2 – APCSM state diagram . 14
Figure 3 – ARPM master AR state diagram . 17
Figure 4 – ARPM slave AR state diagram . 18

Table 1 – RTC PDU attribute format. 12
Table 2 – APCSM state-event table . 15
Table 3 – Master ARPM state-event table . 18
Table 4 – Slave ARPM state-event table . 19
Table 5 – ARPM to DL mapping . 22
Table 6 – DL to ARPM mapping . 22

– 4 – IEC 61158-6-19:2019 © IEC 2019
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 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-6-19 has been prepared by subcommittee 65C: Industrial
networks, of IEC technical committee 65: Industrial-process measurement, control and
automation.
This fourth edition cancels and replaces the third edition published in 2014. This edition
constitutes a technical revision.

This edition includes the following significant technical changes with respect to the previous
edition:
• improving the hotplug and redundancy features;
• improving the phase switching and the error handling;
• editorial improvements.
The text of this International Standard is based on the following documents:
FDIS Report on voting
65C/948/FDIS 65C/956/RVD
Full information on the voting for the approval of this International Standard can be found in
the report on voting indicated in the above table.
This publication has been drafted in accordance with ISO/IEC Directives, Part 2.
A list of all parts of the IEC 61158 series, published under the general title Industrial
communication networks – Fieldbus specifications, can be found on the IEC web site.
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-6-19:2019 © IEC 2019
INTRODUCTION
This document 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 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
document 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 document is concerned, in particular, with the communication and interworking of
sensors, effectors and other automation devices. By using this document together with other
standards positioned within the OSI or fieldbus reference models, otherwise incompatible
systems may work together in any combination.

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 part of IEC 61158 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 International Standard defines in an abstract way the externally visible service provided
by the different Types of 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 document is to define the services provided to:
a) the FAL user at the boundary between the user and the Application Layer of the Fieldbus
Reference Model, and
b) Systems Management at the boundary between the Application Layer and Systems
Management of the Fieldbus Reference Model.
This document 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
such object behavior. In addition to these services, some supporting services are also defined
in this document to provide access to the FAL to control certain aspects of its operation.

– 8 – IEC 61158-6-19:2019 © IEC 2019
1.2 Specifications
The principal objective of this document 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 document 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 any given Type of application layer services as defined in this document.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their
content constitutes requirements 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.
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-3-19:2019, Industrial communication networks – Fieldbus specifications –
Part 3-19: Data-link layer service definition – Type 19 elements
IEC 61158-4-19:2019, Industrial communication networks – Fieldbus specifications –
Part 4-19: Data-link layer protocol specification – Type 19 elements
IEC 61158-5-19:2019, Industrial communication networks – Fieldbus specifications –
Part 5-19: Application layer service definition – Type 19 elements
ISO/IEC 7498-1, Information technology – Open Systems Interconnection – Basic Reference
Model: The Basic Model
ISO/IEC 8822, Information technology – Open Systems Interconnection – Presentation
service definition
ISO/IEC 8824-1, 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, definitions, symbols, abbreviations
and conventions apply.
ISO and IEC maintain terminological databases for use in standardization at the following
addresses:
• IEC Electropedia: available at http://www.electropedia.org/
• ISO Online browsing platform: available at http://www.iso.org/obp
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:
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.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-1 terms
For the purposes of this document, the following terms as defined in ISO/IEC 8824-1 apply:
a) object identifier
b) type
– 10 – IEC 61158-6-19:2019 © IEC 2019
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
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)
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
slave in the communication network, (e.g., a power drive system as defined in the IEC 61800,
I/O stations as defined in the IEC 61131).

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
3.2.8
little endian
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
IPG inter packet gap
IPOSYNC synchronization for PDS interpolator
MDT master data telegram
PDS power drive system
RTC real-time channel
SERCOS serial real-time communication system interface

– 12 – IEC 61158-6-19:2019 © IEC 2019
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 document.
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. The service specification defines the services that are provided
by the ASE.
This document uses the descriptive conventions given in ISO/IEC 10731.
4 Abstract syntax
The abstract syntax and the transfer syntax are merged into a fixed format that is defined in
Clause 5.
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 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 PDU attribute format
Attribute Format Size (bits)
Connection control word 2 Octets, bit mapped 16
Reserved for DLL 16 Bit 16
Configurable part of data record with connection data List of 2, 4 or 8 Octets
Operation data IDN 1 2, 4 or 8 Octets
Operation data IDN 2 2, 4 or 8 Octets
… …
Configured data IDN n 2, 4 or 8 Octets
Number and length of operation data k shall be configured in S-0-1050.x.06 (Configuration List) or by the
selected standard telegram S-0-0015 (Telegram type).

6 Structure of FAL protocol state machines
Clause 6 specifies the interface to FAL services and the protocol machines.
The behavior of the FAL is described by three integrated protocol machines. Specific sets of
these protocol machines are defined for different AREP types. The three protocol machines
are: FAL Service Protocol Machine (FSPM), the Application Relationship Protocol Machine

(ARPM), and the Data Link Layer Mapping Protocol Machine (DMPM). The relationships
among these protocol machines as well as primitives exchanged among them are depicted in
Figure 1.
AP _Context
FA L Se rvice R eq/Rsp P rimiti ves
FAL Se rvice Ind/Cnf P rimiti ves
FSP M
FSP M Req /Rsp P rimiti ves FSP M In d/Cnf P rimiti ves
#n ARPM
#1 ARPM
A RPM Req/Rsp P rimi tives A RPM In d/Cnf P rimi tives
DMPM
DL Req/Rsp Primitive s
DL Ind/ Cnf P rimitive s
Dat a Link La yer
Figure 1 – Relationships among protocol machines and adjacent layers
The FSPM describes the service interface between the AP-Context and a particular AREP.
The FSPM is common to all the AREP classes and does not have any state changes. The
FSPM is responsible for the following activities:
a) to accept service primitives from the FAL service user and convert them into FAL internal
primitives;
b) to select an appropriate ARPM state machine based on the AREP Identifier parameter
supplied by the AP-Context and send FAL internal primitives to the selected ARPM;
c) to accept FAL internal primitives from the ARPM and convert them into service primitives
for the AP-Context;
d) to deliver the FAL service primitives to the AP-Context based on the AREP Identifier
parameter associated with the primitives.
The ARPM describes the establishment and release of an AR and exchange of FAL-PDUs
with a remote ARPM(s). The ARPM is responsible for the following activities:
a) to accept FAL internal primitives from the FSPM and create and send other FAL internal
primitives to either the FSPM or the DMPM, based on the AREP and primitive types;
b) to accept FAL internal primitives from the DMPM and send them to the FSPM as a form of
FAL internal primitives;
c) if the primitives are for the Establish or Abort service, it shall try to establish or release the
specified AR.
– 14 – IEC 61158-6-19:2019 © IEC 2019
The DMPM describes the mapping between the FAL and the DLL. It is common to all the
AREP types and does not have any state changes. The DMPM is responsible for the following
activities:
a) to accept FAL internal primitives from the ARPM, prepare DLL service primitives, and
send them to the DLL;
b) to receive DLL indication or confirmation primitives from the DLL and send them to the
ARPM in a form of FAL internal primitives.
7 AP-context state machine
7.1 Overview
The AP-Context State Machine (APCSM) manages the behavioral states, transitions and
interactions of all the objects contained in an implementation of the Type 19 FAL. As shown
in Figure 2, there are three states. Event notifications are delivered to the APCSM from the
FAL Services Protocol Machine (FSPM) or the AR Protocol Machine (ARPM) as specified.
These event notifications, identified in Figure 2, result in state transitions.
The APCSM is initiated in the Idle state.
Establish
Idle Running
Release
Figure 2 – APCSM state diagram
7.2 States
7.2.1 Idle
7.2.1.1 Behavior
The FAL is not connected to the network. The only behavior associated with the Idle state is
a determination of errors or other fault conditions that are specified as preventing the
transition to the Running state. If there are no such preventative conditions, an automatic
invocation of the Establish primitive is self generated by the APCSM.
7.2.1.2 Events
Establish – Connects the FAL to the network. Upon successful completion, the APCSM
transitions to the Running state.
7.2.2 Running
7.2.2.1 Behavior
The FAL is connected to the network. The Master type device is able to perform the behavior
associated with communicating to the Slaves to which it is connected. Slave type devices are
able to perform the behavior associated responding to the Master to which it is connected.
7.2.2.2 Events
Release – Disconnects the FAL from the network. Upon successful completion, the APCSM
transitions to the Idle state.

7.3 States, events and transitions
The combination of all states events and possible transitions is shown in Table 2.
Table 2 – APCSM state-event table
Current Event Action Next
State State
Initiate the methods specified
Idle Establish Running
for the Running state
Idle Release Return an error Running
Running Establish Return an error Running
Running Release Initiate the methods specified Idle
for the Idle state
8 FAL service protocol machine (FSPM)
8.1 Overview
The FSPM provides the interface to the FAL user in the form of service handlers which
convert service parameters into APDUs and process service requests from the FAL user or
convert APDUs into service parameters and deliver service indications to the FAL user.
The FSPM operates in a single state with events defined by the receipt of service primitives.
8.2 MGT services
8.2.1 Get network status
Upon receipt of a Get Network Status service request from the FAL user, the FSPM prepares
and delivers an appropriately encoded FSP-get network status primitive to the ARPM.
8.2.2 Get device status
Upon receipt of a Get Device Status service request from the FAL user, the FSPM prepares
and delivers an appropriately encoded FSP-get device status primitive to the ARPM.
8.2.3 Network status change report
Upon receipt of an FSP-network status change indication from the ARPM, the FSPM prepares
and delivers an appropriately encoded network status change indication to the FAL user.
8.2.4 Device status change report
Upon receipt of an FSP-device status change indication from the ARPM, the FSPM prepares
and delivers an appropriately encoded device status change indication to the FAL user.
8.2.5 Set device status
Upon receipt of a Set Device Status service request from the FAL user, the FSPM prepares
and delivers an appropriately encoded FSP-set device status primitive to the ARPM.
8.2.6 Enable RTC
Upon receipt of an Enable RTC service request from the FAL user, the FSPM prepares and
delivers an appropriately encoded FSP-enable RTC primitive to the ARPM.

– 16 – IEC 61158-6-19:2019 © IEC 2019
8.2.7 Enable hot-plug
Upon receipt of an Enable Hot-plug service request from the FAL user, the FSPM prepares
and delivers an appropriately encoded FSP-enable hot-plug primitive to the ARPM.
8.2.8 Notify RTC
Upon receipt of an FSP-notify RTC indication from the ARPM, the FSPM prepares and
delivers an appropriately encoded notify RTC change indication to the FAL user.
8.2.9 Disable RTC
Upon receipt of a Disable RTC service request from the FAL user, the FSPM prepares and
delivers an appropriately encoded FSP-disable RTC primitive to the ARPM.
8.2.10 Notify error
Upon receipt of an FSP-notify error indication from the ARPM, the FSPM prepares and
delivers an appropriately encoded notify error indication to the FAL user.
8.3 IDN services
8.3.1 Read
Upon receipt of a Read service request from the FAL user, if the ARPM is not in the Running
state, an error is returned to the FAL user, otherwise the FSPM prepares and delivers an
appropriately encoded FSP-read primitive to the ARPM.
8.3.2 Write
Upon receipt of a Write service request from the FAL user, if the ARPM is not in the Running
state, an error is returned to the FAL user, otherwise the FSPM prepares and delivers an
appropriately encoded FSP-write primitive to the ARPM.
8.4 CYCIDN services
8.4.1 Read_cyclic
Upon receipt of a Read_cyclic service request from the FAL user, the FSPM prepares and
delivers an appropriately encoded FSP-read cyclic primitive to th
...