EN 61158-5-13:2008

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Industrijska komunikacijska omrežja - Specifikacije za procesno vodilo - 5-13. del: Definicija opravil na aplikacijskem nivoju - Elementi tipa 13 (IEC 61158-5-13:2007)Industrielle Kommunikationsnetze - Feldbusse - Teil 5-13: Dienstfestlegungen des Application Layer (Anwendungsschicht) - Typ 13-ElementeRéseaux de communication industriels - Spécifications des bus de terrain - Partie 5-13: Définition des services des couches d'application - Eléments de type 13Industrial communication networks - Fieldbus specifications - Part 5-13: Application layer service definition - Type 13 elements35.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-13:2008SIST EN 61158-5-13:2008en,de01-julij-2008SIST EN 61158-5-13:2008SLOVENSKI
STANDARDSIST EN 61158-5:20041DGRPHãþD

EUROPEAN STANDARD EN 61158-5-13 NORME EUROPÉENNE
EUROPÄISCHE NORM March 2008
CENELEC European Committee for Electrotechnical Standardization Comité Européen de Normalisation Electrotechnique Europäisches Komitee für Elektrotechnische Normung
Central Secretariat: rue de Stassart 35, B - 1050 Brussels
© 2008 CENELEC -
All rights of exploitation in any form and by any means reserved worldwide for CENELEC members.
Ref. No. EN 61158-5-13:2008 E
ICS 35.100.70; 25.040.40 Partially supersedes EN 61158-5:2004
English version
Industrial communication networks -
Fieldbus specifications -
Part 5-13: Application layer service definition -
Type 13 elements (IEC 61158-5-13:2007)
Réseaux de communication industriels -
Spécifications des bus de terrain -
Partie 5-13: Définition des services
des couches d'application -
Eléments de type 13 (CEI 61158-5-13:2007)
Industrielle Kommunikationsnetze -
Feldbusse -
Teil 5-13: Dienstfestlegungen
des Application Layer (Anwendungsschicht) -
Typ 13-Elemente (IEC 61158-5-13:2007)
This European Standard was approved by CENELEC on 2008-02-01. 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 Central Secretariat 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 Central Secretariat has the same status as the official versions.
CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Cyprus, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and the United Kingdom.
- 2 -
Foreword The text of document 65C/475/FDIS, future edition 1 of IEC 61158-5-13, 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 was approved by CENELEC as EN 61158-5-13 on 2008-02-01. This and the other parts of the EN 61158-5 series supersede EN 61158-5:2004. With respect to EN 61158-5:2004 the following changes were made: – deletion of Type 6 fieldbus for lack of market relevance; – addition of new fieldbus types; – partition into multiple parts numbered 5-2, 5-3, …, 5-20. The following dates were fixed: – latest date by which the EN has to be implemented
at national level by publication of an identical
national standard or by endorsement
(dop)
2008-11-01 – latest date by which the national standards conflicting
with the EN have to be withdrawn
(dow)
2011-02-01 NOTE
Use of some of the associated protocol types is restricted by their intellectual-property-right holders. In all cases, the commitment to limited release of intellectual-property-rights made by the holders of those rights permits a particular data-link layer protocol type to be used with physical layer and application layer protocols in type combinations as specified explicitly in the EN 61784 series. Use of the various protocol types in other combinations may require permission from their respective intellectual-property-right holders. Annex ZA has been added by CENELEC. __________ Endorsement notice The text of the International Standard IEC 61158-5-13:2007 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 61158-3-13 NOTE
Harmonized as EN 61158-3-13:2008 (not modified). IEC 61158-4-13 NOTE
Harmonized as EN 61158-4-13:2008 (not modified). IEC 61158-6-13 NOTE
Harmonized as EN 61158-6-13:2008 (not modified). IEC 61784-2 NOTE
Harmonized as EN 61784-2:2008 (not modified). __________
- 3 - EN 61158-5-13:2008 Annex ZA
(normative)
Normative references to international publications with their corresponding European publications
The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.
NOTE
When an international publication has been modified by common modifications, indicated by (mod), the relevant EN/HD applies.
Publication Year Title EN/HD Year
IEC 60559 -1) Binary floating-point arithmetic
for microprocessor systems HD 592 S1 19912)
IEC/TR 61158-1 2007 Industrial communication networks -
Fieldbus specifications -
Part 1: Overview and guidance for the IEC 61158 and IEC 61784 series - -
ISO/IEC 7498-1 -1) Information technology - Open Systems Interconnection - Basic Reference Model:
The Basic Model EN ISO/IEC 7498-119952)
ISO/IEC 7498-3 -1) Information technology - Open Systems Interconnection - Basic Reference Model: Naming and addressing - -
ISO/IEC 8822 -1) Information technology - Open Systems Interconnection - Presentation service definition - -
ISO/IEC 9545 -1) Information technology - Open Systems Interconnection - Application Layer structure - -
ISO/IEC 10731 -1) Information technology - Open Systems Interconnection - Basic reference model - Conventions for the definition of OSI services- -
1) Undated reference. 2) Valid edition at date of issue. SIST EN 61158-5-13:2008

IEC 61158-5-13Edition 1.0 2007-12INTERNATIONAL STANDARD
Industrial communication networks – Fieldbus specifications –
Part 5-13: Application layer service definition – Type 13 elements
INTERNATIONAL ELECTROTECHNICAL COMMISSION XAICS 35.100.70; 25.040.40 PRICE CODEISBN 2-8318-9461-1SIST EN 61158-5-13:2008

– 2 – 61158-5-13 © IEC:2007(E) CONTENTS FOREWORD.4 INTRODUCTION.6 1 Scope.7 1.1 Overview.7 1.2 Specifications.8 1.3 Conformance.8 2 Normative references.8 3 Terms, definitions, symbols, abbreviations and conventions.9 3.1 ISO/IEC 7498-1 terms.9 3.2 ISO/IEC 8822 terms.9 3.3 ISO/IEC 9545 terms.9 3.4 Fieldbus application-layer specific definitions.9 3.5 Abbreviations and symbols.16 3.6 Conventions.16 4 Concepts.19 4.1 Common concepts.19 4.2 Type specific concepts.19 5 Data type ASE.21 5.1 General.21 5.2 Formal definition of data type objects.21 5.3 FAL defined data types.21 5.4 Data type ASE service specification.26 6 Type 13 communication model specification.26 6.1 ASEs.26 6.2 ARs.47 6.3 Summary of FAL classes.54 6.4 Permitted FAL services by AREP role.55 Bibliography.56
Figure 1 – The ASEs of Type 13.20 Figure 2 – The AR ASE conveys APDUs between APs.43
Table 1 – Overall structure of the OD.20 Table 2 – Ident service.29 Table 3 – Status service.30 Table 4 – NMT-req-invite service.31 Table 5 – NMT-state-command service.32 Table 6 – NMT-info service.33 Table 7 – SDO-download.35 Table 8 – SDO-down-mult.36 Table 9 – SDO-upload.38 Table 10 – SDO-up-mult.39 Table 11 – SDO-abort.40 SIST EN 61158-5-13:2008

61158-5-13 © IEC:2007(E) – 3 –
Table 12 – PDO-transfer.42 Table 13 – Conveyance of service primitives by AREP role.44 Table 14 – Valid combinations of AREP roles involved in an AR.44 Table 15 – FAL class summary.54 Table 16 – Services by AREP role.55 SIST EN 61158-5-13:2008

– 4 – 61158-5-13 © IEC:2007(E) INTERNATIONAL ELECTROTECHNICAL COMMISSION ____________
INDUSTRIAL COMMUNICATION NETWORKS – FIELDBUS SPECIFICATIONS –
Part 5-13: Application layer service definition – Type 13 elements
FOREWORD 1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising all national electrotechnical committees (IEC National Committees). The object of IEC is to promote international co-operation on all questions concerning standardization in the electrical and electronic fields. To this end and in addition to other activities, IEC publishes International Standards, Technical Specifications, Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC Publication(s)”). Their preparation is entrusted to technical committees; any IEC National Committee interested in the subject dealt with may participate in this preparatory work. International, governmental and non-governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely with the International Organization for Standardization (ISO) in accordance with conditions determined by agreement between the two organizations. 2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international consensus of opinion on the relevant subjects since each technical committee has representation from all interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any misinterpretation by any end user. 4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications transparently to the maximum extent possible in their national and regional publications. Any divergence between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in the latter. 5) IEC provides no marking procedure to indicate its approval and cannot be rendered responsible for any equipment declared to be in conformity with an IEC Publication. 6) All users should ensure that they have the latest edition of this publication. 7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and members of its technical committees and IEC National Committees for any personal injury, property damage or other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC Publications.
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is indispensable for the correct application of this publication. 9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of patent rights. IEC shall not be held responsible for identifying any or all such patent rights. NOTE
Use of some of the associated protocol types is restricted by their intellectual-property-right holders. In all cases, the commitment to limited release of intellectual-property-rights made by the holders of those rights permits a particular data-link layer protocol type to be used with physical layer and application layer protocols in type combinations as specified explicitly in the IEC 61784 series. Use of the various protocol types in other combinations may require permission of their respective intellectual-property-right holders. International Standard IEC 61158-5-13 has been prepared by subcommittee 65C: Industrial networks, of IEC technical committee 65: Industrial-process measurement, control and automation. This first edition and its companion parts of the IEC 61158-6 subseries cancel and replace IEC 61158-5:2003. This edition of this part constitutes a technical addition. This part and its Type 13 companion parts also cancel and replace IEC/PAS 62408, published in 2005. This edition of IEC 61158-5 includes the following significant changes from the previous edition: a) deletion of the former Type 6 fieldbus for lack of market relevance; SIST EN 61158-5-13:2008

61158-5-13 © IEC:2007(E) – 5 –
b) addition of new types of fieldbuses; c) partition of part 5 of the third edition into multiple parts numbered -5-2, -5-3, … The text of this standard is based on the following documents: FDIS Report on voting 65C/475/FDIS 65C/486/RVD
Full information on the voting for the approval of this standard can be found in the report on voting indicated in the above table. This publication has been drafted in accordance with ISO/IEC Directives, Part 2. The committee has decided that the contents of this publication will remain unchanged until the maintenance result date indicated on the IEC web site under http://webstore.iec.ch in the data related to the specific publication. At this date, the publication will be: • reconfirmed; • withdrawn; • replaced by a revised edition, or • amended. NOTE
The revision of this standard will be synchronized with the other parts of the IEC 61158 series. The list of all the parts of the IEC 61158 series, under the general title Industrial communication networks – Fieldbus specifications, can be found on the IEC web site. SIST EN 61158-5-13:2008

– 6 – 61158-5-13 © IEC:2007(E) INTRODUCTION This part of IEC 61158 is one of a series produced to facilitate the interconnection of automation system components. It is related to other standards in the set as defined by the “three-layer” fieldbus reference model described in IEC/TR 61158-1. The application 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. SIST EN 61158-5-13:2008

61158-5-13 © IEC:2007(E) – 7 –
INDUSTRIAL COMMUNICATION NETWORKS – FIELDBUS SPECIFICATIONS –
Part 5-13: Application layer service definition – Type 13 elements
1 Scope 1.1 Overview 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 13 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 service provided by the different Types of the 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 standard is to define the services provided to 1) the FAL user at the boundary between the user and the Application Layer of the Fieldbus Reference Model, and 2) Systems Management at the boundary between the Application Layer and Systems Management of the Fieldbus Reference Model. This standard specifies the structure and services of the IEC fieldbus Application Layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498) and the OSI Application Layer Structure (ISO/IEC 9545). FAL services and protocols are provided by FAL application-entities (AE) contained within the application processes. The FAL AE is composed of a set of object-oriented Application Service Elements (ASEs) and a Layer Management Entity (LME) that manages the AE. The ASEs provide communication services that operate on a set of related application process object (APO) classes. One of the FAL ASEs is a management ASE that provides a common set of services for the management of the instances of FAL classes. Although these services specify, from the perspective of applications, how request and responses are issued and delivered, they do not include a specification of what the requesting and responding applications are to do with them. That is, the behavioral aspects of the applications are not specified; only a definition of what requests and responses they can send/receive is specified. This permits greater flexibility to the FAL users in standardizing such object behavior. In addition to these services, some supporting services are also defined in this standard to provide access to the FAL to control certain aspects of its operation. SIST EN 61158-5-13:2008

– 8 – 61158-5-13 © IEC:2007(E) 1.2 Specifications The principal objective of this standard is to specify the characteristics of conceptual application layer services suitable for time-critical communications, and thus supplement the OSI Basic Reference Model in guiding the development of application layer protocols for time-critical communications. A secondary objective is to provide migration paths from previously-existing industrial communications protocols. It is this latter objective which gives rise to the diversity of services standardized as the various Types of IEC 61158, and the corresponding protocols standardized in subparts of IEC 61158-6. 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. 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. There is no conformance of equipment to this application layer service definition standard. Instead, conformance is achieved through implementation of conforming application layer protocols that fulfill any given Type of application layer services as defined in this standard. 2 Normative references The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. IEC 60559, Binary floating-point arithmetic for microprocessor systems IEC/TR 61158-1 (Ed.2.0), Industrial communication networks – Fieldbus specifications – Part 1: Overview and guidance for the IEC 61158 and IEC 61784 series ISO/IEC 7498-1, Information technology – Open Systems Interconnection – Basic Reference Model – Part 1: The Basic Model ISO/IEC 7498-3, Information technology – Open Systems Interconnection – Basic Reference Model – Part 3: Naming and addressing ISO/IEC 8822, Information technology – Open Systems Interconnection – Presentation service definition 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 SIST EN 61158-5-13:2008

61158-5-13 © IEC:2007(E) – 9 –
3 Terms, definitions, symbols, abbreviations and conventions For the purposes of this document, the following terms, definitions, symbols, abbreviations and conventions apply 3.1 ISO/IEC 7498-1 terms 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.2 ISO/IEC 8822 terms a) abstract syntax b) presentation context 3.3 ISO/IEC 9545 terms 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.4 Fieldbus application-layer specific definitions For the purposes of this part of IEC 61158, the following terms and definitions apply. 3.4.1
application function or data structure for which data is consumed or produced 3.4.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.4.3
application process part of a distributed application on a network, which is located on one device and unambiguously addressed 3.4.4
application process identifier distinguishes multiple application processes used in a device SIST EN 61158-5-13:2008

– 10 – 61158-5-13 © IEC:2007(E) 3.4.5
application process object component of an application process that is identifiable and accessible through an FAL application relationship NOTE
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.4.6
application process object class class of application process objects defined in terms of the set of their network-accessible attributes and services 3.4.7
application relationship cooperative association between two or more application-entity-invocations for the purpose of exchange of information and coordination of their joint operation. This relationship is activated either by the exchange of application-protocol-data-units or as a result of preconfiguration activities 3.4.8
application relationship application service element application-service-element that provides the exclusive means for establishing and terminating all application relationships 3.4.9
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
Each application process involved in the application relationship maintains its own application relationship endpoint. 3.4.10
attribute description of an externally visible characteristic or feature of an object NOTE
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 behavior of an object. Attributes are divided into class attributes and instance attributes. 3.4.11
behavior indication of how an object responds to particular events 3.4.12
channel single physical or logical link of an input or output application object of a server to the process 3.4.13
class set of objects, all of which represent the same kind of system component NOTE
A class is a generalisation of an object; a template for defining variables and methods. All objects in a class are identical in form and behavior, but usually contain different data in their attributes. 3.4.14
class attributes attribute that is shared by all objects within the same class SIST EN 61158-5-13:2008

61158-5-13 © IEC:2007(E) – 11 –
3.4.15
class code unique identifier assigned to each object class 3.4.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
A class specific object is unique to the object class which defines it. 3.4.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 3.4.18
controlled node All nodes except one (this is the Managing Node) in a Type 13 network are of this type. 3.4.19
connection logical binding between application objects that may be within the same or different devices NOTE
Connections may be either point-to-point or multipoint. 3.4.20
connection channel description of a connection between a sink and a source of data items
3.4.21
connection path an octet stream that defines the application object to which a connection instance applies 3.4.22
connection point buffer which is represented as a subinstance of an Assembly object 3.4.23
consume act of receiving data from a producer 3.4.24
consumer node or sink that is receiving data from a producer 3.4.25
consuming application application that consumes data 3.4.26
control commands action invocations transferred from client to server to clear outputs, freeze inputs and/or synchronise outputs 3.4.27
conveyance path unidirectional flow of APDUs across an application relationship SIST EN 61158-5-13:2008

– 12 – 61158-5-13 © IEC:2007(E) 3.4.28
cyclic repetitive in a regular manner 3.4.29
data consistency means for coherent transmission and access of the input- or output-data object between and within client and server 3.4.30
device physical hardware connected to the link NOTE
A device may contain more than one node. 3.4.31
device profile a collection of device dependent information and functionality providing consistency between similar devices of the same device type 3.4.32
diagnosis information all data available at the server for maintenance purposes 3.4.33
end node producing or consuming node 3.4.34
endpoint one of the communicating entities involved in a connection 3.4.35
error discrepancy between a computed, observed or measured value or condition and the specified or theoretically correct value or condition 3.4.36
error class general grouping for related error definitions and corresponding error codes 3.4.37
error code identification of a specific type of error within an error class 3.4.38
event an instance of a change of conditions 3.4.39
FIFO variable a Variable Object class, composed of a set of homogeneously typed elements, where the first written element is the first element that can be read NOTE
On the fieldbus only one, complete element can be transferred as a result of one service invocation. 3.4.40
frame denigrated synonym for DLPDU SIST EN 61158-5-13:2008

61158-5-13 © IEC:2007(E) – 13 –
3.4.41
group a) a general term for a collection of objects.
Specific uses: b) when describing an address, an address that identifies more than one entity 3.4.42
invocation act of using a service or other resource of an application process NOTE
Each invocation represents a separate thread of control that may be described by its context. Once the service completes, or use of the resource is released, the invocation ceases to exist. For service invocations, a service that has been initiated but not yet completed is referred to as an outstanding service invocation. Also for service invocations, an Invoke ID may be used to unambiguously identify the service invocation and differentiate it from other outstanding service invocations. 3.4.43
index address of an object within an application process 3.4.44
instance the actual physical occurrence of an object within a class that identifies one of many objects within the same object class EXAMPLE
California is an instance of the object class US-state. NOTE
The terms object, instance, and object instance are used to refer to a specific instance. 3.4.45
instance attributes attribute that is unique to an object instance and not shared by the object class 3.4.46
instantiated object that has been created in a device 3.4.47
logical device a certain FAL class that abstracts a software component or a firmware component as an autonomous self-contained facility of an automation device 3.4.48
manufacturer ID identification of each product manufacturer by a unique number 3.4.49
management information network-accessible information that supports managing the operation of the fieldbus system, including the application layer NOTE
Managing includes functions such as controlling, monitoring, and diagnosing. 3.4.50
message router object within a node that distributes messaging requests to appropriate application objects 3.4.51
managing node One node of a type 13 network must act as a managing node. SIST EN 61158-5-13:2008

– 14 – 61158-5-13 © IEC:2007(E) 3.4.52
multipoint connection connection from one node to many NOTE
Multipoint connections allow messages from a single producer to be received by many consumer nodes. 3.4.53
network a set of nodes connected by some type of communication medium, including any intervening repeaters, bridges, routers and lower-layer gateways 3.4.54
node host of one AP, identified by a unique DLCEP-address. 3.4.55
object abstract representation of a particular component within a device, usually a collection of related data (in the form of variables) and methods (procedures) for operating on that data that have clearly defined interface and behavior 3.4.56
object dictionary Collection of definitions. communication specific attributes and parameters, and application dependent data 3.4.57
object specific service service unique to the object class which defines it 3.4.58
originator client responsible for establishing a connection path to the target 3.4.59
physical device automation or other network device 3.4.60
point-to-point connection connection that exists between exactly two application objects 3.4.61
pre-established AR endpoint AR endpoint that is placed in an established state during configuration of the AEs that control its endpoints 3.4.62
process data object(s) which are already pre-processed and transferred cyclically for the purpose of information or further processing 3.4.63
produce act of sending data to be received by a consumer 3.4.64
producer node that is responsible for sending data SIST EN 61158-5-13:2008

61158-5-13 © IEC:2007(E) – 15 –
3.4.65
property general term for descriptive information about an object 3.4.66
provider source of a data connection 3.4.67
publisher role of an AR endpoint that transmits APDUs onto the fieldbus for consumption by one or more subscribers NOTE
A publisher may not be aware of the identity or the number of subscribers. 3.4.68
publishing manager role of an AR endpoint in which it issues one or more confirmed service request APDUs to a publisher to request the publisher to publish a specified object. Two types of publishing managers are defined by this standard, pull publishing managers and push publishing managers, each of which is defined separately 3.4.69
push publisher type of publisher that publishes an object in an unconfirmed service request APDU 3.4.70
push publishing manager type of publishing manager that requests that a specified object be published using an unconfirmed service 3.4.71
push subscriber type of subscriber that recognizes received unconfirmed service request APDUs as published object data 3.4.72
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.4.73
service operation or function than an object and/or object class performs upon request from another object and/or object class 3.4.74
subscriber role of an AREP in which it receives APDUs produced by a publisher 3.4.75
target end-node to which a connection is established SIST EN 61158-5-13:2008

– 16 – 61158-5-13 © IEC:2007(E) 3.5 Abbreviations and symbols AE Application Entity AL Application Layer ALME Application Layer Management Entity ALP Application Layer Protocol APO Application Object AP Application Process APDU Application Protocol Data Unit AR Application Relationship AREP Application Relationship End Point ASCII American Standard Code for Information Interchange ASE Application Service Element CID Connection ID CN Controlled Node Cnf Confirmation DL- (as a prefix) data-link- 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 DNS Domain name Service FAL Fieldbus Application Layer Ind Indication MN Managing Node Req Request Rsp Response
3.6 Conventions 3.6.1 Overview The FAL is defined as a set of object-oriented ASEs. Each ASE is specified in a separate subclause. Each ASE specification is composed of two parts, its class specification, and its service specification. The class specification defines the attributes of the class. The access to these attributes is beyond the scope of this document except where specified. The service specification defines the services that are provided by the ASE. 3.6.2 General conventions This standard uses the descriptive conventions given in ISO/IEC 10731. 3.6.3 Conventions for class definitions Class definitions are described using templates. Each template consists of a list of attributes for the class. The general form of the template is shown below: SIST EN 61158-5-13:2008

61158-5-13 © IEC:2007(E) – 17 –
FAL ASE:
ASE name CLASS:
Class name CLASS ID:
# PARENT CLASS: Parent class name ATTRIBUTES: 1 (o) Key Attribute: numeric identifier 2 (o) Key Attribute: name 3 (m) Attribute: attribute name(values) 4 (m) Attribute: attribute name(values) 4.1 (s) Attribute: attribute name(values) 4.2 (s) Attribute: attribute name(values) 4.3 (s) Attribute: attribute name(values) 5.
(c) Constraint: constraint expression 5.1 (m) Attribute: attribute name(values) 5.2 (o) Attribute: attribute name(values) 6 (m) Attribute: attribute name(values) 6.1 (s) Attribute: attribute name(values) 6.2 (s) Attribute: attribute name(values) SERVICES: 1 (o) OpsService: service name 2
(c) Constraint: constraint expression 2.1 (o) OpsService: service name 3 (m) MgtService: service name
(1) The "FAL ASE:" entry is the name of the FAL ASE that provides the services for the class being specified. (2) The "CLASS:" entry is the name of the class being specified. All objects defined using this template will be an instance of this class. The class may be specified by this standard, or by a user of this standard. (3) The "CLASS ID:" entry is a number that identifies the class being specified. This number is not used for Type 13 elements. (4) The "PARENT CLASS:" entry is the name of the parent class for the class being specified. All attributes defined for the parent class and inherited by it are inherited for the class being defined, and therefore do not have to be redefined in the template for this class. NOTE
The parent-class "TOP" indicates that the class being defined is an initial class definition. The parent class TOP is used as a starting point from which all other classes are defined. The use of TOP is reserved for classes defined by this standard.
(5) The "ATTRIBUTES" label indicate that the following entries are attributes defined for the class. a) Each of the attribute entries contains a line number in column 1, a mandatory (m) / optional (o) / conditional (c) / selector (s) indicator in column 2, an attribute type label in column 3, a name or a conditional expression in column 4, and optionally a list of enumerated values in column 5. In the column following the list of values, the default value for the attribute may be specified. b) Objects are normally identified by a numeric identifier or by an object name, or by both. In the class templates, these key attributes are defined under the key attribute. c) The line number defines the sequence and the level of nesting of the line. Each nesting level is identified by period. Nesting is used to specify i) fields of a structured attribute (4.1, 4.2, 4.3), ii) attributes conditional on a constraint statement (5). Attributes may be mandatory (5.1) or optional (5.2) if the constraint is true. Not all optional attributes require constraint statements as does the attribute defined in (5.2). SIST EN 61158-5-13:2008

– 18 – 61158-5-13 © IEC:2007(E) iii) the selection fields of a choice type attribute (6.1 and 6.2). (6) The "SERVICES" label indicates that the following entries are services defined for the class. a) An (m) in column 2 indicates that the service is mandatory for the class, while an (o) indicates that it is optional. A (c) in this column indicates that the service is conditional. When all services defined for a class are defined as optional, at least one has to be selected when an instance of the class is defined. b) The label "OpsService" designates an operational service (1). c) The label "MgtService" designates a management service (2). d) The line number defines the sequence and the level of nesting of the line. Each nesting level is identified by period. Nesting within the list of services is used to specify services conditional on a constraint statement. 3.6.4 Conventions for service definitions 3.6.4.1 General The service model, service primitives, and time-sequence diagrams used are entirely abstract descriptions; they do not represent a specification for implementation. 3.6.4.2 Service parameters Service primitives are used to represent service user/service provider interactions (ISO/IEC 10731). They convey parameters which indicate information available in the user/provider interaction. In any particular interface, not all parameters need be explicitly stated. The service specifications of this standard uses a tabular format to describe the component parameters of the ASE service primitives. The parameters which apply to each group of service primitives are set out in tables. Each table consists of up to five columns for the 1) parameter name, 2) request primitive, 3) indication primitive, 4) response primitive, and 5) confirm primitive. One parameter (or component of it) is listed in each row of each table. Under the appropriate service primitive columns, a code is used to specify the type of usage of the parameter on the primitive specified in the column: M parameter is mandatory for the primitive U parameter is a User option, and may or may not be provided depending on dynamic usage of the service user. When not provided, a default value for the parameter is assumed. C parameter is conditional upon other parameters or upon the environment of the service user. — (blank) parameter is never present. S parameter is a selected item. Some entries are further qualified by items in brackets. These may be a) a parameter-specific constraint: “(=)” indicates that the parameter is semantically equivalent to the parameter in the service primitive to its immediate left in the table. b) an indication that some note applies to the entry: SIST EN 61158-5-13:2008

61158-5-13 © IEC:2007(E) – 19 –
“(n)” indicates that the following note "n" contains additional information pertaining to the parameter and its use. Service procedures The procedures are defined in terms of • the interactions between application entities through the exchange of fieldbus Application Protocol Data Units, and • the interactions between an application layer service provider and
...