SIST EN 61158-5-24:2015

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Industrijska komunikacijska omrežja - Specifikacije za procesna vodila - 5-24. del: Definicija opravil na aplikacijski ravni - Elementi tipa 24 (IEC 61158-5-24:2014)Industrielle Kommunikationsnetze - Feldbusse - Teil 5-24: Dienstfestlegungen des Application Layer (Anwendungsschicht) - Typ 24-Elemente (IEC 61158-5-24:2014)Réseaux de communication industriels - Spécifications des bus de terrain - Partie 5-24: Définition des services de la couche application - Éléments de type 24 (CEI 61158-5-24:2014)Industrial communication networks - Fieldbus specifications - Part 5-24: Application layer service definition - Type-24 elements (IEC 61158-5-24:2014)35.110OmreževanjeNetworking35.100.70Uporabniški slojApplication layer25.040.40Merjenje in krmiljenje industrijskih postopkovIndustrial process measurement and controlICS:Ta slovenski standard je istoveten z:EN 61158-5-24:2014SIST EN 61158-5-24:2015en,fr,de01-marec-2015SIST EN 61158-5-24:2015SLOVENSKI
STANDARD
EUROPEAN STANDARD NORME EUROPÉENNE EUROPÄISCHE NORM
EN 61158-5-24
October 2014 ICS 25.040.40; 35.100.70; 35.110
English Version
Industrial communication networks - Fieldbus specifications - Part 5-24: Application layer service definition - Type-24 elements (IEC 61158-5-24:2014)
Réseaux de communication industriels - Spécifications des bus de terrain - Partie 5-24: Définition des services de la couche application - Éléments de type 24 (CEI 61158-5-24:2014)
Industrielle Kommunikationsnetze - Feldbusse -
Teil 5-24: Dienstfestlegungen des Application Layer (Anwendungsschicht) - Typ 24-Elemente (IEC 61158-5-24:2014) This European Standard was approved by CENELEC on 2014-09-22. 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-5-24:2014 E SIST EN 61158-5-24:2015

The following dates are fixed: • latest date by which the document has to be implemented at national level by publication of an identical national standard or by endorsement (dop) 2015-06-22 • latest date by which the national standards conflicting with the document have to be withdrawn (dow) 2017-09-22
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-5-24: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. SIST EN 61158-5-24:2015

- 3 - EN 61158-5-24: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 2014
Industrial communication networks - Fieldbus specifications -
Part 1: Overview and guidance for the IEC 61158 and IEC 61784 series EN 61158-1 2014 IEC 61158-6-24 2014
Industrial communication networks - Fieldbus specifications -
Part 6-24: Application layer protocol specification - Type-24 Elements EN 61158-6-24 1) -
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 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 - -
1) To be published. SIST EN 61158-5-24:2015

IEC 61158-5-24 Edition 1.0 2014-08 INTERNATIONAL STANDARD NORME INTERNATIONALE Industrial communication networks – Fieldbus specifications –
Part 5-24: Application layer service definition – Type-24 elements
Réseaux de communication industriels – Spécifications des bus de terrain –
Partie 5-24: Définition des services de la couche application – Éléments
de type 24
INTERNATIONAL ELECTROTECHNICAL COMMISSION COMMISSION ELECTROTECHNIQUE INTERNATIONALE XD ICS 25.040.40; 35.100.70; 35.110 PRICE CODE CODE PRIX ISBN 978-2-8322-1744-3
– 2 – IEC 61158-5-24:2014 © IEC 2014 CONTENTS FOREWORD . 5 INTRODUCTION . 7 1 Scope . 8
General . 8 1.1 Specifications . 9 1.2 Conformance . 9 1.32 Normative references . 9 3 Terms, definitions, symbols, abbreviations, and conventions . 10
Referenced terms and definitions . 10 3.1 Additional terms and definitions . 10 3.2 Abbreviations and symbols . 15 3.3 Conventions . 17 3.44 Concepts . 19 5 Data type ASE . 20 6 Communication model specifications . 20
Type specific concepts . 20 6.1 Overview . 20 6.2 FSM ASE . 23 6.3 FAL ASEs. 29 6.4 FAL ARs . 70 6.5Bibliography . 95
Figure 1 – FAL ASE model of Type 24 . 22 Figure 2 – AR model for field device control service . 72 Figure 3 – AR model for message service . 72 Figure 4 – MSG ARs between each APs . 73
Table 1 – AP type definition . 21 Table 2 – Support list of service for each class of FSM ASE . 24 Table 3 – FSM-Reset . 25 Table 4 – FSM-GetStatus . 26 Table 5 – FSM-SetContext . 27 Table 6 – FSM-GetContext . 28 Table 7 – FSM-Start . 28 Table 8 – Support list of service for each class of FDC ASE . 29 Table 9 – FDC-Reset for master class . 33 Table 10 – FDC-Open for master class . 33 Table 11 – FDC-Enable for master class . 34 Table 12 – FDC-Connect for master class . 34 Table 13 – FDC-SyncSet for master class . 35 Table 14 – FDC-Disconnect for master class . 36 Table 15 – FDC-ResumeCycle for master class . 37 Table 16 – FDC-ComCycle for master class . 37 SIST EN 61158-5-24:2015

IEC 61158-5-24:2014 © IEC 2014 – 3 – Table 17 – FDC-Command for master class . 38 Table 18 – FDC-DataExchange for master class . 39 Table 19 – FDC-Reset for slave class . 42 Table 20 – FDC-Open for slave class . 43 Table 21 – FDC-Enable for slave class . 43 Table 22 – FDC-Connect for slave class . 44 Table 23 – FDC-SyncSet for slave class . 45 Table 24 – FDC-Disconnect for slave class . 46 Table 25 – FDC-ResumeCycle for slave class . 47 Table 26 – FDC-ComCycle for slave class . 47 Table 27 – FDC-Command for slave class . 48 Table 28 – FDC-Command for slave class . 49 Table 29 – FDC-Reset for monitor class . 51 Table 30 – FDC-Open for monitor class . 51 Table 31 – FDC-Enable for monitor class . 52 Table 32 – FDC-GetCMD for monitor class . 52 Table 33 – FDC-GetRSP for monitor class . 53 Table 34 – Support list of service for each class of Message ASE . 54 Table 35 – MSG-Reset for requester class . 56 Table 36 – MSG-Open for requester class . 57 Table 37 – MSG-Enable for requester class . 57 Table 38 – MSG-UserMessage for requester class . 58 Table 39 – MSG-OnewayMessage for requester class . 59 Table 40 – MSG-AbortTransaction for requester class . 61 Table 41 – MSG-Reset for responder class . 62 Table 42 – MSG-Open for responder class . 63 Table 43 – MSG-Enable for responder class . 63 Table 44 – MSG-UserMessage for responder class . 64 Table 45 – MSG-OnewayMessage for responder class . 65 Table 46 – MSG-AbortTransaction for responder class . 66 Table 47 – Support list of service for each class of Event Management ASE. 67 Table 48 – EVM-Reset . 68 Table 49 – EVM-Enable . 68 Table 50 – EVM-SyncEvent . 69 Table 51 – EVM-ReadNetClock . 69 Table 52 – Support list of service for each class of AR ASE . 70 Table 53 – AR-Reset for FDC Master AR class . 75 Table 54 – AR-Open for FDC Master AR class . 76 Table 55 – AR-Enable for FDC Master AR class . 76 Table 56 – AR-CycleEvent for FDC Master AR class. 77 Table 57 – AR-StartComCycle for FDC Master AR class . 77 Table 58 – AR-ResetCycle for FDC Master AR class . 78 Table 59 – AR-SendCommand for FDC Master AR class . 78 SIST EN 61158-5-24:2015

– 4 – IEC 61158-5-24:2014 © IEC 2014 Table 60 – AR-Reset for FDC Slave AR class . 81 Table 61 – AR-Open for FDC Slave AR class . 81 Table 62 – AR-Enable for FDC Slave AR class . 82 Table 63 – AR-CycleEvent for FDC Slave AR class . 82 Table 64 – AR-StartComCycle for FDC Slave AR class . 83 Table 65 – AR-ResetCycle for FDC Slave AR class . 83 Table 66 – AR-SendCommand for FDC Slave AR class . 84 Table 67 – AR-Reset for FDC Monitor AR class . 86 Table 68 – AR-Open for FDC Monitor AR class . 86 Table 69 – AR-Enable for FDC Monitor AR class . 87 Table 70 – AR-GetCMD for FDC Monitor AR class . 88 Table 71 – AR-GetCMD for FDC Monitor AR class . 88 Table 72 – AR-Reset for Message AR class . 90 Table 73 – AR-Open for Message AR class . 91 Table 74 – AR-Enable for Message AR class . 92 Table 75 – AR-SendMessage for Message AR class . 92 Table 76 – AR-ReceiveMessage for Message AR class . 93 Table 77 – AR-AbortMessage for Message AR class . 94
IEC 61158-5-24:2014 © IEC 2014 – 5 – INTERNATIONAL ELECTROTECHNICAL COMMISSION ____________
INDUSTRIAL COMMUNICATION NETWORKS –
FIELDBUS SPECIFICATIONS –
Part 5-24: Application layer service definition –
Type-24 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-5-24 has been prepared by subcommittee 65C: Industrial networks, of IEC technical committee 65: Industrial-process measurement, control and automation.
– 6 – IEC 61158-5-24:2014 © IEC 2014 The text of this standard is based on the following documents: FDIS Report on voting 65C/763/FDIS 65C/773/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 the 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-5-24: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 service is provided by the application protocol making use of the services available from the data-link or other immediately lower layer. This standard defines the application service characteristics that fieldbus applications and/or system management may exploit. Throughout the set of fieldbus standards, the term “service” refers to the abstract capability provided by one layer of the OSI Basic Reference Model to the layer immediately above. Thus, the application layer service defined in this standard is a conceptual architectural service, independent of administrative and implementation divisions.
– 8 – IEC 61158-5-24:2014 © IEC 2014 INDUSTRIAL COMMUNICATION NETWORKS –
FIELDBUS SPECIFICATIONS –
Part 5-24: Application layer service definition –
Type-24 elements
1 Scope
General 1.1The 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 International 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 24 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 International Standard 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 International Standard specifies the structure and services of the 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). 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 SIST EN 61158-5-24:2015

IEC 61158-5-24:2014 © IEC 2014 – 9 – 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 International Standard to provide access to the FAL to control certain aspects of its operation.
Specifications 1.2The principal objective of this standard is to specify the characteristics of conceptual application layer services suitable for time-critical communications, and thus supplement the OSI Basic Reference Model in guiding the development of application layer protocols for time-critical communications. A secondary objective is to provide migration paths from previously-existing industrial communications protocols. It is this latter objective which gives rise to the diversity of services standardized as the various Types of IEC 61158, and the corresponding protocols standardized in subparts of IEC 61158-6. This specification may be used as the basis for formal Application Programming-Interfaces. Nevertheless, it is not a formal programming interface, and any such interface will need to address implementation issues not covered by this specification, including a) the sizes and octet ordering of various multi-octet service parameters, and b) the correlation of paired request and confirm, or indication and response, primitives.
Conformance 1.3This standard does not specify individual implementations or products, nor do they constrain the implementations of application layer entities within industrial automation systems. There is no conformance of equipment to this application layer service definition standard. Instead, conformance is achieved through implementation of conforming application layer protocols that fulfil any given Type of application layer services as defined in this part of IEC 61158. 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:2014, Industrial communication networks – Fieldbus specifications – Part 1: Overview and guidance for the IEC 61158 and IEC 61784 series IEC 61158-6-24:2014, Industrial communication networks – Fieldbus specifications –
Part 6-24: Application layer protocol specification – Type 24 elements ISO/IEC 7498-1, Information technology – Open Systems Interconnection – Basic Reference Model – Part 1: The Basic Model 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 SIST EN 61158-5-24:2015

– 10 – IEC 61158-5-24:2014 © IEC 2014 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.
Referenced terms and definitions 3.1 ISO/IEC 7498-1 terms 3.1.1For the purposes of this document, the following terms as defined in ISO/IEC 7498-1 apply: a) abstract syntax; b) application-entity; c) application process; d) application protocol data unit; e) application-process-invocation; f) (N)-facility; g) (N)-function; h) correspondent-(N)-entities; i) presentation context; j) real system; k) transfer syntax.
ISO/IEC 9545 terms 3.1.2For the purposes of this document, the following terms as defined in ISO/IEC 9545 apply: a) application-association; b) application-context; c) application-entity-invocation; d) application-entity-type; e) application-service-element.
ISO/IEC 8824-1 terms 3.1.3For the purposes of this document, the following terms as defined in ISO/IEC 8824-1 apply: a) object identifier.
Terms and definitions from ISO/IEC 10731 3.1.4For the purposes of this document, the following terms as defined in ISO/IEC 10731 apply: a) OSI-service-primitive; primitive; b) OSI-service-provider; provider; c) OSI-service-user; user.
Additional terms and definitions 3.2For the purposes of this document, the following terms and definitions apply. SIST EN 61158-5-24:2015

IEC 61158-5-24:2014 © IEC 2014 – 11 –
3.2.1alarm field device status to tell that the device has detected a fatal problem to be solved and cannot continue normal working, through the field device control (FDC) service of the type 24 fieldbus Note 1 to entry:
Any alarm statuses are latched and need some operation to be cleared them. Note 2 to entry:
Alarms may be classified into three groups; communication alarms, illegal-command-related ones, and application specific ones. But concrete definitions are dependent on implementation of each field devices.
3.2.2application process object network representation of a specific aspect of an application process (AP), which is modelled as a network accessible object contained within an AP or within another APO Note 1 to entry:
Refer IEC 61158-1, 9.3.4.
3.2.3application process context
AP context shared knowledge or a common set of rules, governing communication of FAL application entities (AEs) and describing the permissible collective communications behavior between the AEs that are party to a specific set of application relationships (ARs) Note 1 to entry:
Data within AP context can be specified by the user in advance, by the option selected while the user uses a field bus management (FSM) service to read out the facility of peer AP, by the automatic negotiation function that the FSM system handles, and so on. The method that is to be adopted depends on the specification of each implementation.
3.2.4application process type AP type description of a classification of application processes (APs) in terms of a set of capabilities for FAL of the type 24 fieldbus Note 1 to entry:
AP types are classified into three ones, C1 master AP, C2 master AP and slave AP, by their application roles in the fieldbus network. See 6.2.
3.2.5async command type of a command application protocol data unit (APDU) of the FDC service of the type 24 FAL, which can be issued any time after the previous transaction without consideration of synchronization with the communication cycle Note 1 to entry:
Definitions, which command should be async one or not, are dependent on an application. They may be provided as a registered set of commands and responses or a device profiles (see IEC 61158-6-24:2014, 4.4 and Annex A).
3.2.6asynchronous communication state or a way of communication for the FDC service of the type 24 FAL, in which a command can be issued any time after the previous transaction without consideration of synchronization with the communication cycle Note 1 to entry:
In this state, sync commands cannot be issued, but async commands can.
3.2.7attribute information or parameter contained in variable portions of an object Note 1 to entry:
Typically, they provide status information or govern the operation of an object. Attributes may also affect the behaviour of an object. SIST EN 61158-5-24:2015

– 12 – IEC 61158-5-24:2014 © IEC 2014
3.2.8C1 master AP type that has master facilities for the FDC service of the type 24 FAL, or the device implementing that AP type Note 1 to entry:
Only one C1 master exists in a network of the type 24 fieldbus
3.2.9C2 master AP type that has only monitor facilities for the FDC service but requester facilities for message (MSG) service of the type 24 FAL, or the device implementing that AP type Note 1 to entry:
Less than two C2 masters can exist in a network of the type 24 fieldbus
3.2.10command PDU issued by a requester or a master to make a responder or a slave execute some functions
3.2.11communication transfer transmission – communication: process to exchange information in a formal manner between two or more devices, users, APs or entities – transfer: process to convey a PDU from a sender to a receiver – transmission: process to send out and propagate electrical signals or encoded data
3.2.12communication cycle period of repetitive activities synchronized with the transmission cycle while the connection establishing for the FDC protocol of the type 24 FAL Note 1 to entry:
Communication cycle may synchronize with a cycle multiplying the transmission cycle by a specified scaling factor.
3.2.13connection context or logical binding under specific conditions for the FDC protocol between a master object and a slave object for the type 24 FAL
3.2.14cyclic repetitive in a regular manner
3.2.15cyclic communication transmission mode in which request PDUs and response PDUs are exchanged repetitively in the scheduled time slots synchronized with a transmission cycle for the lower layer protocol of the type 24 fieldbus Note 1 to entry:
In the AL, the communication cycle arises from the transmission cycle in this mode.
3.2.16cycle scale counter counter to generate a communication cycle by means of scaling a primary cycle or a transmission cycle SIST EN 61158-5-24:2015

IEC 61158-5-24:2014 © IEC 2014 – 13 –
3.2.17device ID part of “device information” to identify the device for a specific product type or model of the type 24 fieldbus
3.2.18device information formatted and device-embedded information to characterize a device, which mainly consists of data for device model identification and device-profile specific parameters for the type 24 fieldbus
3.2.19device profile collection of device model-common information and functionality providing consistency between different device models among the same kind of devices
3.2.20dual transfer transfer mode for the FDC protocol of the type 24 FAL, in which a sender sends a same PDU twice a transaction and a receiver uses them to detect and recover a communication error such as data-corruption or data-loss in cyclic communication mode
3.2.21event driven communication transmission mode for the lower layer protocol of the type 24 fieldbus in which a transaction of command-response-exchanging arises as user’s demands Note 1 to entry:
Both the transmission cycle and the communication cycle don’t arise in this mode.
3.2.22error abnormal condition or malfunction for communication or any other activities
3.2.23field device control service FDC service time-critical communication service that handles a fixed length command data to control a field device and the corresponding feedback response data in a severe restriction on delay or jitter for the communication timing for the type 24 FAL
3.2.24field device control protocol
time-critical communication protocol that handles a fixed length command data to control a field device and the corresponding feedback response data in a severe restriction on delay or jitter for the communication timing for the type 24 FAL
3.2.25master class or its instance object of FDC application service element (ASE) who plays a role of a command requester for the type 24 FAL
3.2.26message service MSG service communication service that handles the variable length data and not required a severe restriction on response time SIST EN 61158-5-24:2015

– 14 – IEC 61158-5-24:2014 © IEC 2014
3.2.27monitor class or its instance object of FDC ASE who plays a role of a watcher or subscriber of commands and response between other communication nodes for the type 24 FAL
3.2.28monitor slave variant of slave AP type who has both slave class and monitor class for FDC ASE of the type 24 FAL
3.2.29network clock synchronized and periodically running counter that each nodes in a same network have, which becomes an oscillation source of the transmission cycle
3.2.30protocol machine state machine that realizes the protocol as the main function of the entity in each layer
3.2.31requester
class or its instance object of MSG ASE who plays a role of a command requester or sender for the type 24 FAL
3.2.32responder class or its instance object of MSG ASE who plays a role of a command responder or receiver for the type 24 FAL
3.2.33response PDU issued by a responder or a slave to inform a result or some status for the received command to a requester or a master
3.2.34service operation or process that an object performs upon request from another object
3.2.35single transfer normal transfer mode for the FDC protocol of the type 24 FAL in which a sender sends a same PDU once a transaction
3.2.36slave AP AP type that has slave facilities for the FDC service of the type 24 FAL, or the device implementing that AP type
3.2.37Slave FDC slave class or its instance object of FDC ASE who plays a role of a responder for the type 24 FAL
3.2.38state machine logical automatic machine or automaton that has a finite number of states and handles state transition fired by an event as a trigger SIST EN 61158-5-24:2015

IEC 61158-5-24:2014 © IEC 2014 – 15 –
3.2.39sync command type of command or APDU of the FDC service of the type 24 FAL, which is issued at the synchronized timing with every communication cycle Note 1 to entry:
Definitions which command should be sync one or not are dependent on an application. They may be provided as a registered set of commands and responses or a device profiles (see IEC 61158-6-24, 4.4 and Annex A).
3.2.40synchronous communication state or a way of communication for the FDC service of the type 24 FAL, in which a command is issued at the synchronized timing with every communication cycle Note 1 to entry:
In this state, both sync commands and async ones can be issued. Note 2 to entry:
In this state, an out-of-synchronization error of APs shall be detected by measures of the watchdog counter.
3.2.41transmission cycle period of repetitive activities for the lower layers of the type 24 fieldbus, which of all the slave devices are synchronized with that of a C1 master device by the lower layer protocol
3.2.42transmission mode state or a way of transmission for the lower layer protocol of the type 24 fieldbus; cyclic mode, event driven mode
3.2.43virtual memory space large data block of APOs for the type 24 FAL which can be read and write with pseudo-memory-addresses to provide consistency between different device models Note 1 to entry:
The virtual memory space includes the device information and other vender specific area. See IEC 61158-6-24, Annex B.
3.2.44warning field device status to tell that the device has detected a slight or passing problem but still working normally through the field device control (FDC) service of the type 24 fieldbus Note 1 to entry:
Any warning statuses are latched and need to be operated to clear them. Note 2 to entry:
Warnings are classified into three groups, communication warnings, illegal-command-related ones, and application specific ones. But concrete definitions are dependent on implementation of each field devices.
Abbreviations and symbols 3.3For the purposes of this document, the following abbreviations and symbols apply. AE Application Entity AL Application Layer A-, AL- Application layer (as a prefix) AP Application Process APDU Application Protocol Data Unit API Application Process Invocation APO Application Process Object APC Application Process Context (as prefix of a protocol for type 24 fieldbus) APC SM Application Process Context State Machine (for type 24 fieldbus) AR Application Relationship SIST EN 61158-5-24:2015

– 16 – IEC 61158-5-24:2014 © IEC 2014 AR ASE Application Relationship Application Service Element AREP Application Relationship End Point ARPM Application Relationship Protocol Machine
(for type 24 fieldbus) ARPM-FDCM ARPM for Field Device Control service Master (for type 24 fieldbus) ARPM-FDCMN ARPM for Field Device Control service Monitor (for type 24 fieldbus) ARPM-FDCS ARPM for Filed Device Control service Slave (for type 24 fieldbus) ARPM-MSG ARPM for Message service (for type 24 fieldbus) ASCII American Standard code for Information Interchange ASE Application Service Element ASN.1 Abstract Syntax Notation One Cnf Confirm primitive DL Data-link-layer DL- (as a prefix) Data Link- DLL Data Link Layer DLM Data Link-management DLPDU Data Link-Protocol Data Unit DLSAP Data Link Servic
...