EN IEC 61158-5-26:2023
(Main)Industrial communication networks - Fieldbus specifications - Part 5-26: Application layer service definition - Type 26 elements
Industrial communication networks - Fieldbus specifications - Part 5-26: Application layer service definition - Type 26 elements
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 2 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 Type 2 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 Type 2 fieldbus application layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI application layer structure (ISO/IEC 9545). FAL services and protocols are provided by FAL application-entities (AE) contained within the application processes. The FAL AE is composed of a set of object-oriented application service elements (ASEs) and a layer management entity (LME) that manages the AE. The ASEs provide communication services that operate on a set of related application process object (APO) classes. One of the FAL ASEs is a management ASE that provides a common set of services for the management of the instances of FAL classes. Although these services specify, from the perspective of applications, how request and responses are issued and delivered, they do not include a specification of what the requesting and responding applications are to do with them. That is, the behavioral aspects of the applications are not specified; only a definition of what requests and responses they can send/receive is specified. This permits greater flexibility to the 318 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. 1.2 Specifications [...] 1.3 Conformance [...]
Industrielle Kommunikationsnetze - Feldbusse - Teil 5-26: Application layer service definition (Anwendungsschicht) - Type 26-Elemente
Réseaux de communication industriels - Spécifications des bus de terrain - Partie 5-26: Définition des services de la couche application - Eléments de type 26
L'IEC 61158-5-26:2023 fournit des éléments communs pour les communications de messagerie prioritaires et non prioritaires élémentaires entre les programmes d’application des environnements d’automatisation et le matériel spécifique au bus de terrain de type 26. Le terme "prioritaire" signale l’existence d’une fenêtre temporelle dans laquelle une ou plusieurs actions spécifiées doivent être réalisées, avec un niveau de certitude défini. Si les actions spécifiées ne sont pas réalisées dans la fenêtre temporelle, les demandes d’action risquent d’être rejetées, avec les risques que cela comporte pour les équipements, les installations et éventuellement la vie humaine. Le présent document définit de manière abstraite le service, visible par un observateur extérieur, assuré par la couche application de bus de terrain de type 26, en matière: de modèle abstrait visant à la définition des ressources d’application (objets) qui peuvent être manipulées par des utilisateurs utilisant un service FAL; d’événements et d’actions liés aux primitives du service; de paramètres associés à chaque événement et action de primitive, ainsi que de forme prise par ces paramètres; et d’interaction entre ces événements et ces actions, ainsi que de séquences valides desdits événements et actions.
Industrijska komunikacijska omrežja - Specifikacije za procesna vodila - 5-26. del: Definicija opravil na aplikacijski ravni - Elementi tipa 26 (IEC 61158-5-26:2023)
Aplikacijska raven procesnih vodil (FAL) uporabniškim programom omogoča dostop do komunikacijskega okolja procesnih vodil. Glede na to je mogoče aplikacijsko raven procesnih vodil šteti za »okno med ustreznimi aplikacijami«.
Ta del standarda IEC 61158 določa skupne elemente za osnovne časovno kritične in časovno nekritične sporočilne komunikacije med aplikacijami v avtomatizacijskem okolju ter material, specifičen za procesna vodila tipa 2. 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 mednarodni standard na abstrakten način določa na zunaj vidno opravilo, ki ga zagotavlja aplikacijska raven procesnih vodil tipa 2 v smislu:
a) abstraktnega modela za določanje aplikacijskih virov (objektov), ki ga lahko upravljajo uporabniki prek opravila aplikacijske ravni procesnih vodil,
b) primitivnih dejanj in dogodkov opravila;
c) parametrov, povezanih z vsakim primitivnim dejanjem in dogodkom, ter obliko, ki jo prevzamejo; in
d) medsebojne povezave med temi dejanji in dogodki ter njihovimi veljavnimi zaporedji.
Namen tega dokumenta je opredeliti opravila, ki se zagotavljajo za:
a) uporabnika aplikacijske ravni procesnih vodil na meji med uporabniško in aplikacijsko ravnjo referenčnega modela procesnega vodila, in
b) upravljanje sistemov na meji med aplikacijsko ravnjo in upravljanjem sistemov za referenčni model procesnega vodila.
Ta dokument določa strukturo in opravila aplikacijske ravni procesnih vodil tipa 2 v skladu z osnovnim referenčnim modelom OSI (ISO/IEC 7498-1) ter strukturo aplikacijske ravni OSI (ISO/IEC 9545).
Opravila in protokole aplikacijske ravni procesnih vodil zagotavljajo aplikacijski osebki (AE) aplikacijske ravni procesnih vodil znotraj aplikacijskih procesov. Aplikacijski osebek aplikacijske ravni procesnih vodil sestavljata sklop objektno usmerjenih aplikacijskih opravilnih elementov (ASE) in osebek za upravljanje ravni (LME), ki upravlja aplikacijski osebek. Aplikacijski opravilni elementi zagotavljajo komunikacijska opravila, ki delujejo na sklopu povezanih razredov objektov aplikacijskega procesa (APO). Med aplikacijske opravilne elemente aplikacijske ravni procesnih vodil spada aplikacijski opravilni element za upravljanje, ki zagotavlja skupen sklop opravil za upravljanje primerkov razredov aplikacijske ravni procesnih vodil.
Čeprav ta opravila določajo način izdajanja ter dostavljanja zahtev in odzivov z vidika aplikacij, ne zajemajo specifikacije v zvezi s tem, kako naj se nanje odzovejo aplikacije, ki te zahteve in odzive oddajajo. To pomeni, da vedenjski vidiki aplikacij niso opredeljeni; opredeljena je le definicija zahtev in odzivov, ki jih lahko pošiljajo/prejemajo. Tako se 318 uporabnikom aplikacijske ravni procesnih vodil omogoči večja prilagodljivost pri standardizaciji takega vedenja objektov. Poleg teh opravil so v tem dokumentu opredeljena tudi nekatera podporna opravila, da se omogoči dostop do aplikacijske ravni procesnih vodil za nadzorovanje nekaterih vidikov njenega delovanja.
General Information
Relations
Standards Content (Sample)
SLOVENSKI STANDARD
01-november-2023
Industrijska komunikacijska omrežja - Specifikacije za procesna vodila - 5-26. del:
Definicija opravil na aplikacijski ravni - Elementi tipa 26 (IEC 61158-5-26:2023)
Industrial communication networks - Fieldbus specifications - Part 5-26: Application layer
service definition - Type 26 elements (IEC 61158-5-26:2023)
Industrielle Kommunikationsnetze - Feldbusse - Teil 5-26: Application layer service
definition (Anwendungsschicht) - Type 26-Elemente (IEC 61158-5-26:2023)
Réseaux de communication industriels - Spécifications des bus de terrain - Partie 5-26:
Définition des services de la couche application - Eléments de type 26
(IEC 61158-5-26:2023)
Ta slovenski standard je istoveten z: EN IEC 61158-5-26:2023
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 IEC 61158-5-26
NORME EUROPÉENNE
EUROPÄISCHE NORM April 2023
ICS 25.040.40; 35.100.70; 35.110 Supersedes EN IEC 61158-5-26:2019
English Version
Industrial communication networks - Fieldbus specifications -
Part 5-26: Application layer service definition - Type 26 elements
(IEC 61158-5-26:2023)
Réseaux de communication industriels - Spécifications des Industrielle Kommunikationsnetze - Feldbusse - Teil 5-26:
bus de terrain - Partie 5-26: Définition des services de la Application layer service definition (Anwendungsschicht) -
couche application - Eléments de type 26 Type 26-Elemente
(IEC 61158-5-26:2023) (IEC 61158-5-26:2023)
This European Standard was approved by CENELEC on 2023-04-20. 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, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the
Netherlands, Norway, Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland,
Türkiye 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: Rue de la Science 23, B-1040 Brussels
© 2023 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members.
Ref. No. EN IEC 61158-5-26:2023 E
European foreword
The text of document 65C/1203/FDIS, future edition 2 of IEC 61158-5-26, 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 IEC 61158-5-
26:2023.
The following dates are fixed:
• latest date by which the document has to be implemented at national (dop) 2024-01-20
level by publication of an identical national standard or by endorsement
• latest date by which the national standards conflicting with the (dow) 2026-04-20
document have to be withdrawn
This document supersedes EN IEC 61158-5-26:2019 and all of its amendments and corrigenda (if
any).
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CENELEC shall not be held responsible for identifying any or all such patent rights.
Any feedback and questions on this document should be directed to the users’ national committee. A
complete listing of these bodies can be found on the CENELEC website.
Endorsement notice
The text of the International Standard IEC 61158-5-26:2023 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 standard indicated:
IEC 61784-1 (series) NOTE Approved as EN IEC 61784-1 (series)
IEC 61784-2 (series) NOTE Approved as EN IEC 61784-2 (series)
To be published. Stage at time of publication : FprEN 61784-1-X:2023.
To be published. Stage at time of publication : FprEN 61784-2-X:2023.
Annex ZA
(normative)
Normative references to international publications
with their corresponding European publications
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 1 Where 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.cencenelec.eu.
Publication Year Title EN/HD Year
IEC 61131-3 - Programmable controllers - Part 3: EN 61131-3 -
Programming languages
IEC 61158-1 2023 Industrial communication networks - EN 61158-1 2023
Fieldbus specifications - Part 1: Overview
and guidance for the IEC 61158 and IEC
61784 series
IEC 61158-6-26 2023 Industrial communication networks - EN IEC 61158-6-26 —
Fieldbus specifications - Part 6-26:
Application layer protocol specification -
Type 26 elements
IEC 61784-2-21 2023 Industrial networks - Profiles - Part 2-21: - -
Additional real-time fieldbus profiles based
on ISO/IEC/IEEE 8802-3 - CPF 21
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/IEEE 8802-3 - Standard for Ethernet - -
ISO/IEC 8822 - Information technology - Open Systems - -
Interconnection - Presentation service
definition
ISO/IEC 8824-1 - Information technology - Abstract Syntax - -
Notation One (ASN.1) - Part 1:
Specification of basic notation
ISO/IEC 9545 - Information technology - Open Systems - -
Interconnection - Application layer
structure
To be published. Stage at time of publication: FprEN IEC 61158-6-26:2023.
ISO/IEC 10731 - Information technology - Open Systems - -
Interconnection - Basic Reference Model -
Conventions for the definition of OSI
services
IEC 60559 - Floating-Point arithmetic HD 592 S1 -
IETF RFC 768 1980 User Datagram Protocol - -
IETF RFC 791 1981 Internet Protocol - -
IETF RFC 792 1981 Internet Control Message Protocol - -
IETF RFC 793 1981 Transmission Control Protocol - -
IETF RFC 796 2081 Address mappings - -
IETF RFC 826 1982 An Ethernet Address Resolution Protocol: - -
Or Converting Network Protocol Addresses
to 48.bit Ethernet Address for
Transmission on Ethernet Hardware
IETF RFC 894 1984 Standard for the Transmission of IP - -
Datagrams over Ethernet
IETF RFC 919 1984 Broadcasting Internet Datagrams - -
IETF RFC 922 1984 Broadcasting Internet datagrams in the - -
presence of subnets
IETF RFC 950 1985 Internet Standard Subnetting Procedure - -
IEC 61158-5-26 ®
Edition 2.0 2023-03
INTERNATIONAL
STANDARD
Industrial communication networks – Fieldbus specifications –
Part 5-26: Application layer service definition – Type 26 elements
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
ICS 25.040.40; 35.100.70; 35.110 ISBN 978-2-8322-6581-9
– 2 – IEC 61158-5-26:2023 © IEC 2023
CONTENTS
FOREWORD . 5
INTRODUCTION . 7
1 Scope . 8
1.1 General . 8
1.2 Specifications . 9
1.3 Conformance . 9
2 Normative references . 9
3 Terms, definitions, symbols, abbreviated terms and conventions . 11
3.1 Terms and definitions from other ISO/IEC standards . 11
3.1.1 Terms and definitions from ISO/IEC 7498-1 . 11
3.1.2 Terms and definitions from ISO/IEC 8822 . 11
3.1.3 Terms and definitions from ISO/IEC 9545 . 11
3.1.4 Terms and definitions from ISO/IEC 8824-1 . 12
3.2 Fieldbus application layer Type 26-specific definitions . 12
3.3 Abbreviated terms and symbols . 18
3.4 Conventions . 20
3.4.1 Overview . 20
3.4.2 General conventions . 20
3.4.3 Conventions for class definitions . 21
3.4.4 Conventions for service definitions . 22
4 Concepts . 23
5 Data type ASE . 23
5.1 Overview. 23
5.2 Formal definition of data type objects . 24
5.2.1 Data type class definitions . 24
5.2.2 Attributes . 25
5.3 FAL defined data types . 26
5.3.1 Fixed length types . 26
5.3.2 String types . 32
5.4 Data type ASE service specification . 33
6 Communication model specification . 33
6.1 General . 33
6.2 Protocol stack for Type 26 fieldbus . 33
6.3 Overview of Type 26 communication model . 34
6.4 Cyclic data communication service with Common-memory . 35
6.4.1 Overview . 35
6.4.2 Common–memory: allocation to each node . 36
6.4.3 Data sharing among nodes with the CM . 37
6.4.4 CM data type . 39
6.5 ASEs . 39
6.5.1 Overview of Type 26 ASEs . 39
6.5.2 Type 26 specific conventions for FAL service common parameters . 40
6.5.3 Cyclic-data ASE . 41
6.5.4 Message data ASE . 47
6.5.5 Load measurement ASE . 77
6.5.6 Network management ASE . 83
IEC 61158-5-26:2023 © IEC 2023 – 3 –
6.5.7 General purpose command server ASE . 97
6.5.8 AR ASE . 100
6.5.9 FAL ASE summary . 113
Bibliography . 116
Figure 1 – Protocol stack for Type 26 fieldbus . 34
Figure 2 – Unconfirmed Push-Publisher/Subscriber type interaction. 35
Figure 3 – Unconfirmed/Confirmed Client/Server type interaction. 35
Figure 4 – Common memory allocation . 37
Figure 5 – Data sharing with the CM . 38
Figure 6 – Node #01 for reception only . 38
Figure 7 – Node #01 without the CM . 39
Figure 8 − Data sharing among nodes with and without CM3 . 39
Figure 9 – The structure of ASEs for Type 26 FAL . 40
Figure 10 – Virtual-address-space for Byte block . 52
Figure 11 – Virtual-address-space for Word block . 54
Figure 12 – AR ASE internal architecture . 101
Figure 13 – Structure of IP address . 111
Table 1 – Write service parameters . 44
Table 2 – Send-CM service parameters . 45
Table 3 – Read service parameters . 45
Table 4 – Update memory service parameters . 46
Table 5 – Get- buffer service parameters . 47
Table 6 – Byte block read service parameters . 52
Table 7 – Byte block write service parameters . 53
Table 8 – Word block read service parameters . 54
Table 9 – Word block write service parameters . 55
Table 10 – Network parameter read service parameters . 56
Table 11 – Extended network parameter read service parameters . 57
Table 12 – Network parameter write service parameters . 58
Table 13 – Extended network parameter write service parameters . 59
Table 14 – Stop command service parameters . 60
Table 15 – Operation command service parameters . 60
Table 16 – profile read service parameters . 61
Table 17 – Transparent message service parameters . 63
Table 18 – Log data read service parameters . 64
Table 19 – Log data items . 64
Table 20 – Log data clear service parameters . 69
Table 21 – Message return service parameters . 70
Table 22 – Vendor specific message service parameters . 71
Table 23 – Set remote node configuration parameter service parameters . 72
Table 24 – Data elements and Node configuration parameters . 72
– 4 – IEC 61158-5-26:2023 © IEC 2023
Table 25 – Service parameters of Read remote participating node management
information parameter service . 73
Table 26 – Participating node management information parameters . 74
Table 27 – Read remote node management information parameter service parameters . 75
Table 28 – Node management information parameters . 76
Table 29 – Read remote node setting information parameter service parameters . 77
Table 30 – Node setting information parameters . 77
Table 31 – Start TK-holding-time measurement service parameters . 79
Table 32 – Terminate TK-holding-time measurement service parameters . 80
Table 33 – Token-holding-time measurement result . 81
Table 34 – Start GP_Comm sender log service parameters . 82
Table 35 – Terminate GP_Comm sender log service parameters . 82
Table 36 – GP_Comm sender log measurement result . 83
Table 37 – Service parameters for Set configuration parameter . 87
Table 38 – Configuration parameters . 87
Table 39 – Read node management information parameter service parameters . 88
Table 40 – Node management information parameters . 88
Table 41 – Service parameters for Read participating node mgt. information parameter . 89
Table 42 – Participating node management information parameters . 90
Table 43 – Service parameters for Read network management information parameter . 90
Table 44 – Network management information parameters . 91
Table 45 – Service parameters for Read message sequence number management
information . 91
Table 46 – Read message sequence number management information parameters . 92
Table 47 – Read node status service parameters . 92
Table 48 – Read node status parameters . 93
Table 49 – Upper layer operating condition matrix . 93
Table 50 – Reset node service parameters . 94
Table 51 – Set network address service parameters . 94
Table 52 – Register service parameters . 95
Table 53 – Event service parameters . 95
Table 54 – Activate/Deactivate measurement service parameters . 96
Table 55 – Get log data service parameters . 97
Table 56 – Send command service parameters . 100
Table 57 – CT send service parameters . 104
Table 58 – MT send service parameters . 106
Table 59 – CS send service parameters . 107
Table 60 – Notify state change service parameters . 108
Table 61 – Control measurement service parameters . 109
Table 62 – DLSAP assignments . 110
Table 63 – DLS Primitives and parameters . 112
Table 64 – Lower layer T-profile and the required standards . 113
Table 65 – Summary of FAL ASEs . 113
IEC 61158-5-26:2023 © IEC 2023 – 5 –
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
INDUSTRIAL COMMUNICATION NETWORKS –
FIELDBUS SPECIFICATIONS –
Part 5-26: Application layer service definition –
Type 26 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 the IEC 61784-1 series and the IEC 61784-2 series.
IEC 61158-5-26 has been prepared by subcommittee 65C: Industrial networks, of IEC technical
committee 65: Industrial-process measurement, control and automation. It is an International
Standard.
This second edition cancels and replaces the first edition published in 2019. This edition
constitutes a technical revision.
– 6 – IEC 61158-5-26:2023 © IEC 2023
This edition includes the following significant technical changes with respect to the previous
edition:
a) expand Common-memory-area as a new Common-memory-area-3 (CM3);
b) add new services with expansion of Common-memory-area:
– Extended-cyclic-data transfer service;
– Extended-participation-request service;
– Extended-network-parameter-read service;
– Extended-network-parameter-write service.
The text of this International Standard is based on the following documents:
Draft Report on voting
65C/1203/FDIS 65C/1244/RVD
Full information on the voting for its approval can be found in the report on voting indicated in
the above table.
The language used for the development of this International Standard is English.
This document was drafted in accordance with ISO/IEC Directives, Part 2, and developed in
accordance with ISO/IEC Directives, Part 1 and ISO/IEC Directives, IEC Supplement, available
at www.iec.ch/members_experts/refdocs. The main document types developed by IEC are
described in greater detail at www.iec.ch/publications.
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 document will remain unchanged until the
stability date indicated on the IEC web site under webstore.iec.ch in the data related to the
specific document. At this date, the document will be
• reconfirmed,
• withdrawn,
• replaced by a revised edition, or
• amended.
IEC 61158-5-26:2023 © IEC 2023 – 7 –
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 service is provided by the application protocol making use of the services
available from the data-link or other immediately lower layer. This document defines the
application service characteristics that fieldbus applications and/or system management can
exploit.
Throughout the set of fieldbus standards, the term "service" refers to the abstract capability
provided by one layer of the OSI Basic Reference Model to the layer immediately above. Thus,
the application layer service defined in this document is a conceptual architectural service,
independent of administrative and implementation divisions.
– 8 – IEC 61158-5-26:2023 © IEC 2023
INDUSTRIAL COMMUNICATION NETWORKS –
FIELDBUS SPECIFICATIONS –
Part 5-26: Application layer service definition –
Type 26 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 26 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 document defines in an abstract way the externally visible service provided by the Type26
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 document 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 document specifies the structure and services of the Type 26 fieldbus application layer, in
conformance with the OSI Basic Reference Model (see ISO/IEC 7498-1) and the OSI
Application Layer Structure (see 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.
IEC 61158-5-26:2023 © IEC 2023 – 9 –
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.
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.
This document can be used as the basis for formal Application Programming-Interfaces.
Nevertheless, it is not a formal programming interface, and any such interface will need to
address implementation issues not covered by this specification, including
a) the sizes and octet ordering of various multi-octet service parameters, and
b) the correlation of paired request and confirm, or indication and response, primitives.
1.3 Conformance
This document does not specify individual implementations or products, nor does it constrain
the implementations of application layer entities within industrial automation systems.
There is no conformance of equipment to this application layer service definition standard.
Instead, conformance is achieved through implementation of conforming application layer
protocols that fulfill the Type 26 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 the IEC 61784-1 series and the IEC 61784-2 series 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 61131-3, Programmable controllers – Part 3: Programming languages
IEC 61158-1:2023, Industrial communication networks – Fieldbus specifications – Part 1:
Overview and guidance for the IEC 61158 and IEC 61784 series
IEC 61158-6-26:2023, Industrial communication networks – Fieldbus specifications – Part 6-26:
Application layer protocol specification – Type 26 elements
IEC 61784-2-21:2023, Industrial networks – Profiles – Part 2-21: Additional real-time fieldbus
profiles based on ISO/IEC/IEEE 8802-3 – CPF 21
– 10 – IEC 61158-5-26:2023 © IEC 2023
ISO/IEC 646, Information technology – ISO 7-bit coded character set for information
interchange
ISO/IEC 7498-1, Information technology – Open Systems Interconnection – Basic Reference
Model – Part 1: The Basic Model
ISO/IEC/IEEE 8802-3, Telecommunications and exchange between information technology
systems − Requirements for local and metropolitan area networks − Part 3: Standard for
Ethernet
ISO/IEC 8822, Information technology – Open Systems Interconnection – Presentation service
definition
ISO/IEC 8824-1, Information Technology – Abstract Syntax Notation One (ASN-1) – Part 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
ISO/IEC 60559, Floating-Point arithmetic
IETF RFC 768, J. Postel, User Datagram Protocol, August 1980, available at https://www.rfc-
editor.org/info/rfc768 [viewed 2022-02-18]
IETF RFC 791, J. Postel, Internet Protocol, September 1981, available at https://www.rfc-
editor.org/info/rfc791 [viewed 2022-02-18]
IETF RFC 792, J. Postel, Internet Control Message Protocol, September 1981, available at
https://www.rfc-editor.org/info/rfc792 [viewed 2022-02-18]
IETF RFC 793, J. Postel, Transmission Control Protocol, September 1981, available at
https://www.rfc-editor.org/info/rfc793 [viewed 2022-02-18]
IETF RFC 796, J. Postel, Address mappings, September 1981, available at https://www.rfc-
editor.org/info/rfc796 [viewed 2022-02-18]
IETF RFC 826, D. Plummer, An Ethernet Address Resolution Protocol: Or Converting Network
Protocol Addresses to 48.bit Ethernet Address for Transmission on Ethernet Hardware,
November 1982, available at https://www.rfc-editor.org/info/rfc826 [viewed 2022-02-18]
IETF RFC 894, C. Hornig, A Standard for the Transmission of IP Datagrams over Ethernet, April
1984, available at https://www.rfc-editor.org/info/rfc894 [viewed 2022-02-18]
IETF RFC 919, J.C. Mogul, Broadcasting Internet Datagrams, October 1984, available at
https://www.rfc-editor.org/info/rfc919 [viewed 2022-02-18]
IETF RFC 922, J.C. Mogul, Broadcasting Internet datagrams in the presence of subnets,
October 1984, available at https://www.rfc-editor.org/info/rfc922 [viewed 2022-02-18]
IETF RFC 950, J.C. Mogul and J. Postel, Internet Standard Subnetting Procedure, August 1985,
available at https://www.rfc-editor.org/info/rfc950 [viewed 2022-02-18]
IEC 61158-5-26:2023 © IEC 2023 – 11 –
3 Terms, definitions, symbols, abbreviated terms and conventions
For the purposes of this document, the following terms, definitions, symbols, abbreviated terms
and conventions apply.
ISO and IEC maintain terminological databases for use in standardization at the following
addresses:
• IEC Electropedia: available at https://www.electropedia.org/
• ISO Online browsing platform: available at https://www.iso.org/obp
3.1 Terms and definitions from other ISO/IEC standards
3.1.1 Terms and definitions from ISO/IEC 7498-1
For the purposes of this document, the following terms and definitions given 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 Terms and definitions from ISO/IEC 8822
For the purposes of this document, the following terms and definitions given in ISO/IEC 8822
apply.
a) abstract syntax
b) presentation context
3.1.3 Terms and definitions from ISO/IEC 9545
For the purposes of this document, the following terms and definitions given 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
– 12 – IEC 61158-5-26:2023 © IEC 2023
3.1.4 Terms and definitions from ISO/IEC 8824-1
For the purposes of this document, the following terms and definitions given in ISO/IEC 8824-1
apply.
a) object identifier
b) type
c) value
d) simple type
e) structured type
f) tag
g) Boolean type
h) true
i) false
j) integer type
k) bitstring type
l) octetstring type
3.2 Fieldbus application layer Type 26-specific definitions
For the purposes of this document, the following terms and definitions apply.
3.2.1
application
function or data structure for which data is consumed or produced
3.2.2
application objects
multiple object classes that manage and provide a run time exchange of messages across the
network and within the network device
3.2.3
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 objects can 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.4
application process object class
class of application process objects defined in terms of the set of their network-accessible
attributes and services
3.2.5
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.
IEC 61158-5-26:2023 © IEC 2023 – 13 –
3.2.6
application relationship ASE
ASE used for establishing and terminating application relationship
3.2.7
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.8
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 can also affect the behavior of an object.
Attributes are divided into class a
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...