EN 61158-6-9:2014

Industrial communication networks - Fieldbus specifications - Part 6-9: Application layer protocol specification - Type 9 elements

IEC 61158-6-9:2014 defines the protocol provided to define the wire-representation of the service primitives defined in IEC 61158-5-9, and define the externally visible behavior associated with their transfer. This standard specifies the protocol of the Type 9 fieldbus application layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI application layer structure (ISO/IEC 9545). This third edition cancels and replaces the second edition published in 2010 and constitutes a technical revision. The main changes are: - Correct Time-difference valid range; - Correct Table 3 state transition; - Include Transparent timeliness class in BNU AREP formal model.

Industrielle Kommunikationsnetze - Feldbusse - Teil 6-9: Protokollspezifikation des Application Layer (Anwendungsschicht) - Typ 9-Elemente

Réseaux de communication industriels - Spécifications des bus de terrain - Partie 6-9: Spécification du protocole de la couche application - Éléments de type 9

L'IEC 61158-6-9:2014 décrit le protocole mis en place pour définir la représentation filaire des primitives de service définies dans la CEI 61158-5-9 et définir le comportement visible de l'extérieur associé à leur transfert. La présente norme spécifie le protocole de la couche application de bus de terrain de Type 9, en conformité avec le modèle de référence de base OSI (ISO/CEI 7498-1) et la structure de la couche application OSI (ISO/CEI 9545). Cette troisième édition annule et remplace la deuxième édition parue en 2010. Elle constitue une révision technique. Les principales modifications sont: - Correction de la plage valide de Time-difference (écart du temps); - Correction des Passages d'états du Tableau 3; - Inclusion de la classe de ponctualité "Transparent" dans le modèle formel des points AREP BNU.

Industrijska komunikacijska omrežja - Specifikacije za procesna vodila - 6-9. del: Specifikacija protokola na aplikacijski ravni - Elementi tipa 9 (IEC 61158-6-9:2014)

Aplikacijski nivo procesnih vodil (FAL) omogoča uporabniškim programom dostop do komunikacijskega okolja procesnih vodil. Glede na to je mogoče aplikacijski nivo procesnih vodil obravnavati kot »okno med ustreznimi aplikacijami«.
Ta standard določa skupne elemente za osnovne časovno kritične in časovno nekritične sporočilne komunikacije med aplikacijami v avtomatizacijskem okolju in material, specifičen za procesna vodila tipa 9. Izraz »časovno kritičen« se uporablja za predstavitev prisotnosti časovnega okna, v okviru katerega se zahteva dokončanje enega ali več opredeljenih dejanj z določeno stopnjo gotovosti. Zaradi neuspešnega dokončanja opredeljenih dejanj v časovnem oknu je možna odpoved aplikacij, ki zahtevajo dejanja, pri čemer so ogroženi oprema, obrat in morda človeška življenja.
Ta standard na abstrakten način določa na zunaj vidno vedenje, ki ga zagotavlja aplikacijski nivo procesnih vodil tipa 9 v smislu
a) abstraktne sintakse, ki določa podatkovne enote protokola aplikacijskega nivoja, ki se prenašajo med aplikacijskimi osebki, ki komunicirajo,
a) prenosne sintakse, ki določa podatkovne enote protokola aplikacijskega nivoja, ki se prenašajo med aplikacijskimi osebki, ki komunicirajo,
c) stroja stanja aplikacijskega konteksta, ki opredeljuje vedenje aplikacijskega opravila, vidnega med aplikacijskimi osebki, ki komunicirajo, in
d) strojev stanja aplikacijskega razmerja, ki opredeljujejo komunikacijsko vedenje med aplikacijskimi osebki, ki komunicirajo.
Namen tega standarda je opredeliti protokol, ki se zagotavlja za
1) določitev žične predstavitve primitivov opravil iz standarda IEC 61158-5-9 in
2) določitev zunanje vidnega vedenja, povezanega z njihovim prenosom.
Ta standard določa protokol aplikacijskega nivoja procesnih vodil IEC tipa 9 v skladu z osnovnim referenčnim modelom OSI (ISO/IEC 7498-1) in strukturo aplikacijskega nivoja OSI (ISO/IEC 9545).

General Information

• Status: Published
• Publication Date: 23-Oct-2014
• Withdrawal Date: 22-Sep-2017
• ICS: 25.040.40 - Industrial process measurement and control
• ICS: 35.100.70 - Application layer
• ICS: 35.110 - Networking
• Technical Committee: CLC/TC 65X - Industrial-process measurement, control and automation
• Drafting Committee: IEC/SC 65C - IEC_SC_65C
• Current Stage: 6060 - Document made available - Publishing
• Start Date: 24-Oct-2014
• Completion Date: 24-Oct-2014
• Mandate: M/490 - Standardisation mandate to the European Standardisation Organisations (ESOs) to support European Smart Grid deployment
• Ref Project: SIST EN 61158-6-9:2015 - Industrial communication networks - Fieldbus specifications - Part 6-9: Application layer protocol specification - Type 9 elements (IEC 61158-6-9:2014)

Relations

• Replaces: EN 61158-6-9:2012 - Industrial communication networks - Fieldbus specifications - Part 6-9: Application layer protocol specification - Type 9 elements
• Effective Date: 07-Jun-2022
• Parent: EN 61158-6-2:2014 - Industrial communication networks - Fieldbus specifications - Part 6-2: Application layer protocol specification - Type 2 elements
• Effective Date: 07-Jun-2022
• Parent: EN 61158-6-2:2014 - Industrial communication networks - Fieldbus specifications - Part 6-2: Application layer protocol specification - Type 2 elements
• Effective Date: 23-Mar-2020

Overview

EN 61158-6-9:2014 (IEC 61158-6-9:2014) specifies the application layer protocol for Type 9 fieldbus elements used in industrial communication networks. It defines the wire representation of the service primitives from IEC 61158‑5‑9 and the externally visible behavior when those primitives are transferred. The standard aligns the Type 9 application layer with the OSI Basic Reference Model (ISO/IEC 7498‑1) and the OSI application layer structure (ISO/IEC 9545). This edition (3rd) updates the previous 2010 version with technical corrections such as time-difference range, a corrected state-transition table, and inclusion of a transparent timeliness class in the BNU AREP model.

Key topics and technical requirements

• Protocol syntax and encoding: Abstract syntax and transfer syntax definitions for FAL‑AR PDUs, data types (Integer, Floating Point, Visible String, Octet String, Date/Time types, Bit String, etc.), and user data definitions.
• Service primitive mapping: Wire-level representation of service primitives defined in IEC 61158‑5‑9, including identification insertion and coding rules.
• State machines and protocol machines: Formal specification of protocol behavior through machines such as:
  • VCR PM (Virtual Connection / VCR state machine)
  • FAL service protocol machine (FSPM)
  • Application relationship protocol machines (ARPMs) - QUU, QUB, BNU
  • DLL mapping protocol machine (DMPM)
• Interaction and mapping: Definitions of primitives and parameter sets exchanged between FSPM, ARPMs and the data-link layer; mapping rules for integration with lower OSI layers.
• Formal models and conformance: State tables, transition diagrams and functions to support conformance testing and implementation consistency.
• Encoding standards referenced: Use of ASN.1 notation and BER/CER/DER encoding rules (ISO/IEC 8824-1, 8825-1) for data representation.

Applications

• Implementing the Type 9 application layer protocol in field devices, gateways, PLCs and communication stacks for industrial automation.
• Developing interoperable fieldbus products that conform to EN 61158 and IEC 61158 series requirements.
• Creating test suites and conformance test plans for fieldbus application layer behavior, primitives and state transitions.
• Integrating Type 9 fieldbus services with data-link layer implementations and OSI-aligned protocol stacks.

Who should use this standard

• Device and protocol stack vendors implementing Type 9 fieldbus application layer.
• System integrators and control engineers deploying fieldbus-based industrial networks.
• Test laboratories and conformity assessment bodies validating protocol compliance.
• Standards developers and engineers mapping application-layer services to data-link layers.

Related standards

• IEC 61158-5-9 (Application layer service definition - Type 9 elements)
• IEC 61158 series (Parts 1, 3‑1, 4‑1)
• ISO/IEC 7498-1 (OSI Basic Reference Model), ISO/IEC 9545 (Application Layer structure)
• ISO/IEC 8824‑1, 8825‑1 (ASN.1 and encoding rules)

Keywords: EN 61158-6-9, IEC 61158-6-9, Type 9 fieldbus, application layer protocol, industrial communication networks, fieldbus standards, OSI application layer, protocol state machines, ASN.1 encoding.

Standards Content (Sample)

SLOVENSKI STANDARD
01-marec-2015
1DGRPHãþD
SIST EN 61158-6-9:2012
Industrijska komunikacijska omrežja - Specifikacije za procesna vodila - 6-9. del:
Specifikacija protokola na aplikacijski ravni - Elementi tipa 9 (IEC 61158-6-9:2014)
Industrial communication networks - Fieldbus specifications - Part 6-9: Application layer
protocol specification - Type 9 elements (IEC 61158-6-9:2014)
Industrielle Kommunikationsnetze - Feldbusse - Teil 6-9: Protokollspezifikation des
Application Layer (Anwendungsschicht) - Typ 9-Elemente (IEC 61158-6-9:2014)
Réseaux de communication industriels - Spécifications des bus de terrain - Partie 6-9:
Spécification du protocole de la couche application - Éléments de type 9 (CEI 61158-6-
9:2014)
Ta slovenski standard je istoveten z: EN 61158-6-9:2014
ICS:
25.040.40 Merjenje in krmiljenje Industrial process
industrijskih postopkov measurement and control
35.100.70 Uporabniški sloj Application layer
35.110 Omreževanje Networking
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN STANDARD EN 61158-6-9

NORME EUROPÉENNE
EUROPÄISCHE NORM
October 2014
ICS 25.040.40; 35.100.70; 35.110 Supersedes EN 61158-6-9:2012
English Version
Industrial communication networks - Fieldbus specifications -
Part 6-9: Application layer protocol specification - Type 9
elements
(IEC 61158-6-9:2014)
Réseaux de communication industriels - Spécifications des Industrielle Kommunikationsnetze - Feldbusse - Teil 6-9:
bus de terrain - Partie 6-9: Spécification du protocole de la Protokollspezifikation des Application Layer
couche application - Éléments de type 9 (Anwendungsschicht) - Typ 9-Elemente
(CEI 61158-6-9:2014) (IEC 61158-6-9:2014)
This European Standard was approved by CENELEC on 2014-09-23. CENELEC members are bound to comply with the CEN/CENELEC
Internal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration.
Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the CEN-CENELEC
Management Centre or to any CENELEC member.
This European Standard exists in three official versions (English, French, German). A version in any other language made by translation
under the responsibility of a CENELEC member into its own language and notified to the CEN-CENELEC Management Centre has the
same status as the official versions.
CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Croatia, Cyprus, the Czech Republic,
Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia,
Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland,
Turkey and the United Kingdom.

European Committee for Electrotechnical Standardization
Comité Européen de Normalisation Electrotechnique
Europäisches Komitee für Elektrotechnische Normung
CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels
© 2014 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members.
Ref. No. EN 61158-6-9:2014 E
Foreword
The text of document 65C/764/FDIS, future edition 3 of IEC 61158-6-9, prepared by SC 65C
"Industrial networks" of IEC/TC 65 "Industrial-process measurement, control and automation" was
submitted to the IEC-CENELEC parallel vote and approved by CENELEC as EN 61158-6-9:2014.
The following dates are fixed:
(dop) 2015-06-23
• latest date by which the document has to be implemented at
national level by publication of an identical national
standard or by endorsement
(dow) 2017-09-23
• latest date by which the national standards conflicting with
the document have to be withdrawn

This document supersedes EN 61158-6-9:2012.
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CENELEC [and/or CEN] shall not be held responsible for identifying any or all such
patent rights.
This document has been prepared under a mandate given to CENELEC by the European Commission
and the European Free Trade Association.
Endorsement notice
The text of the International Standard IEC 61158-6-9:2014 was approved by CENELEC as a
European Standard without any modification.
In the official version, for Bibliography, the following notes have to be added for the standards indicated:
IEC 61784-1 NOTE Harmonized as EN 61784-1.
IEC 61784-2 NOTE Harmonized as EN 61784-2.

- 3 - EN 61158-6-9:2014
Annex ZA
(normative)
Normative references to international publications
with their corresponding European publications
The following documents, in whole or in part, are normatively referenced in this document and are
indispensable for its application. For dated references, only the edition cited applies. For undated
references, the latest edition of the referenced document (including any amendments) applies.
NOTE 1 When an International Publication has been modified by common modifications, indicated by (mod),
the relevant EN/HD applies.
NOTE 2 Up-to-date information on the latest versions of the European Standards listed in this annex is
available here: www.cenelec.eu.

Publication Year Title EN/HD Year
IEC 61158-1 -  Industrial communication networks - EN 61158-1 -
Fieldbus specifications -
Part 1: Overview and guidance for the
IEC 61158 and IEC 61784 series
IEC 61158-3-1 -  Industrial communication networks - EN 61158-3-1 -
Fieldbus specifications -
Part 3-1: Data-link layer service definition -
Type 1 elements
IEC 61158-4-1 -  Industrial communication networks - EN 61158-4-1 -
Fieldbus specifications -
Part 4-1: Data-link layer protocol
specification - Type 1 elements
IEC 61158-5-5 -  Industrial communication networks - EN 61158-5-5 -
Fieldbus specifications -
Part 5-5: Application layer service
definition - Type 5 elements
IEC 61158-5-9 -  Industrial communication networks - EN 61158-5-9 -
Fieldbus specifications -
Part 5-9: Application layer service
definition - Type 9 elements
ISO/IEC 646 -  Information technology - ISO 7-bit coded - -
character set for information interchange
ISO/IEC 7498-1 -  Information technology - Open Systems - -
Interconnection - Basic Reference Model:
The Basic Model
ISO/IEC 8824-1 -  Information technology - Abstract Syntax - -
Notation One (ASN.1): Specification of
basic notation
Publication Year Title EN/HD Year
ISO/IEC 8825-1 -  Information technology - ASN.1 encoding - -
rules: Specification of Basic Encoding
Rules (BER), Canonical Encoding Rules
(CER) and Distinguished Encoding Rules
(DER)
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
ISO/IEC/IEEE 60559 -  Information technology - Microprocessor - -
Systems - Floating-Point arithmetic

IEC 61158-6-9 ®
Edition 3.0 2014-08
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
Industrial communication networks – Fieldbus specifications –

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

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

Partie 6-9: Spécification du protocole de la couche application – Eléments

de type 9
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
PRICE CODE
INTERNATIONALE
CODE PRIX XD
ICS 25.040.40; 35.100.70; 35.110 ISBN 978-2-8322-1760-3

– 2 – IEC 61158-6-9:2014 © IEC 2014
CONTENTS
FOREWORD . 5
INTRODUCTION . 7
1 Scope . 8
1.1 General . 8
1.2 Specifications . 8
1.3 Conformance . 9
2 Normative references . 9
3 Terms, definitions, symbols, abbreviations and conventions . 10
3.1 Terms and definitions from other ISO/IEC standards . 10
3.2 IEC 61158-1 terms . 11
3.3 Abbreviations and symbols . 14
3.4 Conventions . 15
3.5 Conventions used in state machines . 16
4 Abstract syntax . 17
4.1 FAL-AR PDU abstract syntax . 17
4.2 Abstract syntax of PDUBody . 19
4.3 Type definitions for ASEs . 22
4.4 Abstract syntax of data types . 27
5 Transfer syntax . 28
6 Structure of FAL protocol state machines . 39
7 AP-Context state machines . 40
7.1 VCR PM structure . 40
7.2 VCR PM state machine . 41
8 FAL service protocol machine (FSPM) . 53
8.1 General . 53
8.2 FSPM state tables . 53
8.3 Functions used by FSPM . 56
8.4 Parameters of FSPM/ARPM primitives . 56
9 Application relationship protocol machines (ARPMs) . 56
9.1 AREP mapping to data-link layer . 56
9.2 Application relationship protocol machines (ARPMs) . 66
9.3 AREP state machine primitive definitions . 82
9.4 AREP state machine functions . 83
10 DLL mapping protocol machine (DMPM) . 84
10.1 DMPM States . 84
10.2 DMPM state table . 85
10.3 Primitives exchanged between data-link layer and DMPM . 91
10.4 Functions used by DMPM . 93
Bibliography . 95

Figure 1 – Insertion of identification information in the FMS PDU . 29
Figure 2 – Identification . 30
Figure 3 – Coding with identification . 31
Figure 4 – Coding without identification . 31
Figure 5 – Representation of the value true . 31

IEC 61158-6-9:2014 © IEC 2014 – 3 –
Figure 6 – Representation of the value false . 31
Figure 7 – Coding of data of data type Integer16 . 32
Figure 8 – Coding of data of data type Unsigned16 . 32
Figure 9 – Coding of data of data type Floating Point . 33
Figure 10 – Coding of data of data type Visible String . 33
Figure 11 – Coding of data of data type Octet String . 34
Figure 12 – Coding of data of type Date . 34
Figure 13 – Coding of data of data type Time-of-day . 35
Figure 14 – Coding of data of data type Time-difference . 36
Figure 15 – Coding of data of data type Bit String . 36
Figure 16 – Coding of data of data type Time-value . 37
Figure 17 – Coding of data of user data definitions with identifier. 37
Figure 18 – Coding of data of user data definitions without identifier . 37
Figure 19 – Coding of ID info for a SEQUENCE . 38
Figure 20 – Relationships among protocol machines and adjacent layers . 39
Figure 21 – Relationships among protocol machines and adjacent layers . 40
Figure 22 – VCR state machine . 41
Figure 23 – State transition diagram of FSPM . 53
Figure 24 – State transition diagram of the QUU ARPM . 67
Figure 25 – State transition diagram of QUB ARPM . 69
Figure 26 – State transition diagram of the BNU ARPM . 77
Figure 27 – State transition diagram of DMPM . 85

Table 1 – Conventions used for state machines . 16
Table 2 – Coding for Date type . 34
Table 3 – AP-VCR state machine transactions . 42
Table 4 – Primitives issued by FAL-User to VCR PM . 51
Table 5 – Primitives issued by VCR PM to FAL-User . 51
Table 6 – Primitives issued by VCR PM to FSPM . 52
Table 7 – Primitives issued by FSPM to VCR PM . 52
Table 8 – FSPM state table – sender transactions . 54
Table 9 – FSPM state table – receiver transactions . 55
Table 10 – Function SelectArep() . 56
Table 11 – Parameters used with primitives exchanged between FSPM and ARPM . 56
Table 12 – QUU ARPM states . 67
Table 13 – QUU ARPM state table – sender transactions . 67
Table 14 – QUU ARPM state table – receiver transactions . 68
Table 15 – QUB ARPM states . 68
Table 16 – QUB ARPM state table – sender transactions . 69
Table 17 – QUB ARPM state table – receiver transactions . 71
Table 18 – BNU ARPM states . 77
Table 19 – BNU ARPM state table – sender transactions . 78
Table 20 – BNU ARPM state table – receiver transactions . 79

– 4 – IEC 61158-6-9:2014 © IEC 2014
Table 21 – Primitives issued from ARPM to DMPM . 82
Table 22 – Primitives issued by DMPM to ARPM . 82
Table 23 – Parameters used with primitives exchanged between ARPM and DMPM . 82
Table 24 – Function GetArepId() . 83
Table 25 – Function BuildFAS-PDU . 84
Table 26 – Function FAS_Pdu_Type . 84
Table 27 – Function AbortIdentifier . 84
Table 28 – Function AbortReason . 84
Table 29 – Function AbortDetail . 84
Table 30 – DMPM state descriptions . 85
Table 31 – DMPM state table – sender transactions . 85
Table 32 – DMPM state table – receiver transactions . 88
Table 33 – Primitives exchanged between data-link layer and DMPM . 91
Table 34 – Function PickArep . 93
Table 35 – Function FindAREP . 93
Table 36 – Function LocateQubArep . 94
Table 37 – Function SetIdentifier() . 94

IEC 61158-6-9:2014 © IEC 2014 – 5 –
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
INDUSTRIAL COMMUNICATION NETWORKS –
FIELDBUS SPECIFICATIONS –
Part 6-9: Application layer protocol specification –
Type 9 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-9 has been prepared by subcommittee 65C: Industrial
networks, of IEC technical committee 65: Industrial-process measurement, control and
automation.
This third edition cancels and replaces the second edition published in 2010. This edition
constitutes a technical revision. The main change with respect to the previous edition is listed
below:
– 6 – IEC 61158-6-9:2014 © IEC 2014
• Correct Time-difference valid range
• Correct Table 3 state transition
• Include Transparent timeliness class in BNU AREP formal model
The text of this standard is based on the following documents:
FDIS Report on voting
65C/764/FDIS 65C/774/RVD
Full information on the voting for the approval of this standard can be found in the report on
voting indicated in the above table.
This publication has been drafted in accordance with ISO/IEC Directives, Part 2.
A list of all parts of the IEC 61158 series, published under the general title Industrial
communication networks – Fieldbus specifications, can be found on the IEC web site.
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.
IEC 61158-6-9:2014 © IEC 2014 – 7 –
INTRODUCTION
This part of IEC 61158 is one of a series produced to facilitate the interconnection of
automation system components. It is related to other standards in the set as defined by the
“three-layer” fieldbus reference model described in IEC 61158-1.
The application 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.

– 8 – IEC 61158-6-9:2014 © IEC 2014
INDUSTRIAL COMMUNICATION NETWORKS –
FIELDBUS SPECIFICATIONS –
Part 6-9: Application layer protocol specification –
Type 9 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 9 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 behavior provided by the Type
9 fieldbus Application Layer in terms of
a) the abstract syntax defining the application layer protocol data units conveyed between
communicating application entities,
b) the transfer syntax defining the application layer protocol data units conveyed between
communicating application entities,
c) the application context state machine defining the application service behavior visible
between communicating application entities; and
d) the application relationship state machines defining the communication behavior visible
between communicating application entities; and.
The purpose of this standard is to define the protocol provided to
1) define the wire-representation of the service primitives defined in IEC 61158-5-9, and
2) define the externally visible behavior associated with their transfer.
This standard specifies the protocol of the Type 9 IEC fieldbus application layer, in
conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI Application
Layer Structure (ISO/IEC 9545).
1.2 Specifications
The principal objective of this standard is to specify the syntax and behavior of the application
layer protocol that conveys the application layer services defined in IEC 61158-5-9.
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
protocols standardized in IEC 61158-6.

IEC 61158-6-9:2014 © IEC 2014 – 9 –
1.3 Conformance
This standard does not specify individual implementations or products, nor does it constrain
the implementations of application layer entities within industrial automation systems.
Conformance is achieved through implementation of this application layer protocol
specification.
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and
are indispensable for its application. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any
amendments) applies.
NOTE All parts of the IEC 61158 series, as well as IEC 61784-1 and IEC 61784-2 are maintained simultaneously.
Cross-references to these documents within the text therefore refer to the editions as dated in this list of normative
references.
IEC 61158-1, Industrial communication networks – Fieldbus specifications – Part 1: Overview
and guidance for the IEC 61158 and IEC 61784 series
IEC 61158-3-1, Industrial communication networks – Fieldbus specifications – Part 3-1: Data-
link layer service definition – Type 1 elements
IEC 61158-4-1, Industrial communication networks – Fieldbus specifications – Part 4-1: Data-
link layer protocol specification – Type 1 elements
IEC 61158-5-5, Industrial communication networks – Fieldbus specifications – Part 5-5:
Application layer service definition – Type 5 elements
IEC 61158-5-9, Industrial communication networks – Fieldbus specifications – Part 5-9:
Application layer service definition – Type 9 elements
ISO/IEC 646, Information technology – ISO 7-bit coded character set for information
interchange
ISO/IEC 7498-1, Information technology – Open Systems Interconnection – Basic Reference
Model: The Basic Model
ISO/IEC 8824-1, Information technology – Abstract Syntax Notation One (ASN.1):
Specification of basic notation
ISO/IEC 8825-1, Information technology – ASN.1 encoding rules: Specification of Basic
Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules
(DER)
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
ISO/IEC/IEEE 60559, Information technology – Microprocessor Systems – Floating-Point
arithmetic
– 10 – IEC 61158-6-9:2014 © IEC 2014
3 Terms, definitions, symbols, abbreviations and conventions
For the purposes of this document, the following terms, definitions, symbols, abbreviations
and conventions apply.
3.1 Terms and definitions from other ISO/IEC standards
3.1.1 Terms and definitions from ISO/IEC 7498-1
a) abstract syntax
b) application entity
c) application process
d) application protocol data unit
e) application service element
f) application entity invocation
g) application process invocation
h) application transaction
i) presentation context
j) real open system
k) transfer syntax
3.1.2 Terms and definitions from ISO/IEC 9545
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.3 Terms and definitions from ISO/IEC 8824-1
a) object identifier
b) type
c) value
d) simple type
e) structured type
f) component type
g) tag
h) Boolean type
i) true
j) false
k) integer type
l) bitstring type
m) octetstring type
n) null type
o) sequence type
p) sequence of type
q) choice type
r) tagged type
s) any type
t) module
u) production
3.1.4 Terms and definitions from ISO/IEC 8825-1
a) encoding (of a data value)
b) data value
c) identifier octets (the singular form is used in this standard)
d) length octet(s) (both singular and plural forms are used in this standard)
e) contents octets
IEC 61158-6-9:2014 © IEC 2014 – 11 –
3.2 IEC 61158-1 terms
For the purposes of the present document, the following IEC 61158-1 terms apply.
3.2.1
application
function or data structure for which data is consumed or produced
3.2.2
application layer interoperability
capability of application entities to perform coordinated and cooperative operations using the
services of the FAL
3.2.3
application object
object class that manages and provides the run time exchange of messages across the
network and within the network device
Note 1 to entry:  Multiple types of application object classes may be defined.
3.2.4
application process
part of a distributed application on a network, which is located on one device and
unambiguously addressed
3.2.5
application process identifier
distinguishes multiple application processes used in a device
3.2.6
application process object
component of an application process that is identifiable and accessible through an FAL
application relationship
Note 1 to entry:  Application process object definitions are composed of a set of values for the attributes of their
class (see the definition for Application Process Object Class Definition). Application process object definitions
may be accessed remotely using the services of the FAL Object Management ASE. FAL Object Management
services can be used to load or update object definitions, to read object definitions, and to dynamically create and
delete application objects and their corresponding definitions.
3.2.7
application process object class
class of application process objects defined in terms of the set of their network-accessible
attributes and services
3.2.8
application relationship
cooperative association between two or more application-entity-invocations for the purpose of
exchange of information and coordination of their joint operation
Note 1 to entry:  This relationship is activated either by the exchange of application-protocol-data-units or as a
result of preconfiguration activities.
3.2.9
application relationship application service element
application-service-element that provides the exclusive means for establishing and
terminating all application relationships

– 12 – IEC 61158-6-9:2014 © IEC 2014
3.2.10
application relationship endpoint
context and behavior of an application relationship as seen and maintained by one of the
application processes involved in the application relationship
Note 1 to entry:  Each application process involved in the application relationship maintains its own application
relationship endpoint.
3.2.11
attribute
description of an externally visible characteristic or feature of an object
Note 1 to entry:  The attributes of an object contain information about variable portions of an object. Typically,
they provide status information or govern the operation of an object. Attributes may also affect the behaviour of an
object. Attributes are divided into class attributes and instance attributes.
3.2.12
behaviour
indication of how the object responds to particular events
Note 1 to entry:  Its description includes the relationship between attribute values and services.
3.2.13
class
set of objects, all of which represent the same kind of system component
Note 1 to entry:  A class is a generalisation of the object; a template for defining variables and methods. All
objects in a class are identical in form and behaviour, but usually contain different data in their attributes.
3.2.14
class attributes
attribute that is shared by all objects within the same class
3.2.15
class code
unique identifier assigned to each object class
3.2.16
class specific service
service defined by a particular object class to perform a required function which is not
performed by a common service
Note 1 to entry:  A class specific object is unique to the object class which defines it.
3.2.17
client
(a) object which uses the services of another (server) object to perform a task
(b) initiator of a message to which a server reacts, such as the role of an AR endpoint in
which it issues confirmed service request APDUs to a single AR endpoint acting as a
server
3.2.18
conveyance path
unidirectional flow of APDUs across an application relationship
3.2.19
cyclic
events which repeat in a regular and repetitive manner

IEC 61158-6-9:2014 © IEC 2014 – 13 –
3.2.20
dedicated AR
AR used directly by the FAL User
Note 1 to entry:  On Dedicated ARs, only the FAL Header and the user data are transferred
3.2.21
device
physical hardware connection to the link
Note 1 to entry:  A device may contain more than one node.
3.2.22
device profile
collection of device dependent information and functionality providing consistency between
similar devices of the same device type
3.2.23
dynamic AR
AR that requires the use of the AR establishment procedures to place it into an established
state
3.2.24
endpoint
one of the communicating entities involved in a connection
3.2.25
error
discrepancy between a computed, observed or measured value or condition and the specified
or theoretically correct value or condition
3.2.26
error class
general grouping for error definitions
Note 1 to entry:  Error codes for specific errors are defined within an error class.
3.2.27
error code
identification of a specific type of error within an error class
3.2.28
FAL subnet
networks composed of one or more data link segments
Note 1 to entry: They are permitted to contain bridges, but not routers FAL subnets are identified by a subset of the
network address.
3.2.29
logical device
specifies a certain FAL class that abstracts a software component or a firmware component
as an autonomous self-contained facility of an automation device
3.2.30
management information
network-accessible information that supports managing the operation of the fieldbus system,
including the application layer
Note 1 to entry:  Managing includes functions such as controlling, monitoring, and diagnosing.

– 14 – IEC 61158-6-9:2014 © IEC 2014
3.2.31
network
series of nodes connected by some type of communication medium
Note 1 to entry:  The connection paths between any pair of nodes can include repeaters, routers and gateways.
3.2.32
peer
role of an AR endpoint in which it is capable of acting as both client and server
3.2.33
pre-defined AR endpoint
AR endpoint that is defined locally within a device without use of the create service
Note 1 to entry:  Pre-defined ARs that are not pre-established are established before being used.
3.2.34
pre-established AR endpoint
AR endpoint that is placed in an established state during configuration of the AEs that control
its endpoints
3.2.35
publisher
role of an AR endpoint in which it transmits APDUs onto the fieldbus for consumption by one
or more subscribers
Note 1 to entry:  The publisher may not be aware of the identity or the number of subscribers and it may publish its
APDUs using a dedicated AR. Two types of publishers are defined by this standard, Pull Publishers and Push
Publishers, each of which is defined separately.
3.2.36
server
a) role of an AREP in which it returns a confirmed service response APDU to the client that
initiated the request
b) object which provides services to another (client) object
3.2.37
service
operation or function than an object and/or object class performs upon request from another
object and/or object class
Note 1 to entry:  A set of common services is defined and provisions for the definition of object-specific services
are provided. Object-specific services are those which are defined by a particular object class to perform a
required function which is not performed by a common service.
3.2.38
subscriber
role of an AREP in which it receives APDUs produced by a publisher
Note 1 to entry:  Two types of subscribers are defined by this standard, pull subscribers and push subscribers,
each of which is defined separately.
3.3 Abbreviations and symbols
AE Application Entity
AL Application Layer
ALME Application Layer Management Entity
ALP Application Layer Protocol
APO Application Object
IEC 61158-6-9:2014 © IEC 2014 – 15 –
AP Application Process
APDU Application Protocol Data Unit
API Application Process Identifier
AR Application Relationship
AREP Application Relationship End Point
ASCII American Standard Code for Information Interchange
ASE Application service Element
Cnf Confirmation
DL- (as a prefix) data-link-
DLC Data-link Connection
DLCEP Data-link Connection End Point
DLL Data-link layer
DLM Data-link-management
DLSAP Data-link service Access Point
DLSDU DL-service-data-unit
FAL Fieldbus Application Layer
ID Identifier
IEC International Electrotechnical Commission
Ind Indication
LME Layer Management Entity
OSI Open Systems Interconnect
QoS Quality of service
Req Request
Rsp Response
SAP Service Access Point
SDU Service Data Unit
SMIB System Management Information Base
SMK System Management Kernel
VFD Virtual Field Devic
...