IEC 61158-5-9:2007
(Main)Industrial communication networks - Fieldbus specifications - Part 5-9: Application layer service definition - Type 9 elements
Industrial communication networks - Fieldbus specifications - Part 5-9: Application layer service definition - Type 9 elements
IEC 61158-5-9:2007 defines the services provided to the FAL user at the boundary between the user and the Application Layer of the Fieldbus Reference Model, and SystemsManagement at the boundary between the Application Layer and Systems Management of the Fieldbus Reference Model. This standard specifies the structure and services of the Type 9 IEC fieldbus Application Layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498) and the OSI Application Layer Structure (ISO/IEC 9545). This first edition and its companion parts of the IEC 61158-5 subseries cancel and replace IEC 61158-5:2003. This edition of this part constitutes an editorial revision. This edition of IEC 61158-5 includes the following significant changes from the previous edition:
- deletion of the former Type 6 fieldbus for lack of market relevance;
- addition of new types of fieldbuses;
- partition of part 5 of the third edition into multiple parts numbered 5-2, 5-3,... This bilingual version (2014-12) corresponds to the monolingual English version, published in 2007-12.
Réseaux de communication industriels - Spécifications des bus de terrain - Partie 5-9: Définition des services des couches d'application - Eléments de type 9
L'IEC 61158-5-9:2007 vise à définir les services mis en place pour l'utilisateur de la FAL, à la frontière entre l'utilisateur et la couche Application du modèle de référence de bus de terrain, et la Gestion des systèmes, à la frontière entre la couche Application et la Gestion des systèmes selon le modèle de référence de bus de terrain. La présente norme spécifie la structure et les services de Type 9 de la couche application des bus de terrain de la CEI, en conformité avec le Modèle de référence de base de l'OSI (ISO/CEI 7498) et la Structure de la couche application de l'OSI (ISO/CEI 9545). Cette première édition et ses parties connexes de la sous-série CEI 61158-5 annulent et remplacent la CEI 61158-5:2003. Cette édition de la CEI 61158-5 comporte les modifications significatives suivantes par rapport à l'édition précédente:
- suppression de l'ancien bus de terrain de Type 6 à cause d'un manque d'adéquation avec le marché;
- ajout de nouveaux types de bus de terrain;
- partition de la partie 5 de la troisième édition en plusieurs parties numérotées 5-2, 5-3,... La présente version bilingue (2014-12) correspond à la version anglaise monolingue publiée en 2007-12.
General Information
Relations
Overview
IEC 61158-5-9:2007 - "Industrial communication networks – Fieldbus specifications – Part 5-9: Application layer service definition – Type 9 elements" - defines the Application Layer services and structures for the Type 9 IEC fieldbus. It specifies the services provided at the boundary between the Fieldbus Application Layer (FAL) and FAL users, and between the Application Layer and Systems Management. The standard is aligned with the OSI Basic Reference Model (ISO/IEC 7498) and the OSI Application Layer Structure (ISO/IEC 9545). This edition replaces earlier IEC 61158-5 publications and is an editorial revision reflecting changes in fieldbus Type categorization.
Key topics and requirements
The standard details the structure, services and conformance rules for Type 9 fieldbus Application Layer elements, including:
- Data types and ASE (Application Service Element) definitions - formal object and data type models and service behaviour.
- Communication model - abstract models for devices and virtual field devices (VFD), ASEs and ARs (Application Relations).
- Object Dictionary - structure for static and dynamic object lists and type summaries used by devices.
- Service sets - standardized services for reading/writing variables, information reports, event handling, unsolicted messages and buffered messaging.
- Download/Upload mechanisms - domain download/upload sequences, segment transfer and state machines for file/program transfer.
- Program invocation and lifecycle services - create/delete/start/stop/resume/reset/kill of program invocations and related state machines.
- Access control and membership - access groups, rights for variables, events, domains and program invocations.
- Protocol behaviour - state machines, error/reject/abort handling and operational states to ensure interoperable implementations.
- Conformance rules and normative references to OSI-related standards.
The document contains detailed tables, state diagrams and service parameter definitions to guide implementers.
Applications and who uses it
IEC 61158-5-9 is used by:
- Fieldbus stack developers implementing the Type 9 Application Layer.
- Device manufacturers (PLCs, I/O modules, HMIs, drives) seeking interoperability and conformance testing.
- System integrators and automation engineers designing distributed control and field-level communication systems.
- Certification and test laboratories verifying compliance with Fieldbus Reference Model requirements.
- Gateway and protocol-converter vendors implementing mapping between Type 9 and other fieldbus/industrial Ethernet protocols.
Practical uses include building interoperable field devices, implementing firmware for device services (read/write, events, program invocation, firmware/download), and ensuring consistent behaviour across multi-vendor automation systems.
Related standards
- IEC 61158 series (Fieldbus specifications)
- ISO/IEC 7498 (OSI Basic Reference Model)
- ISO/IEC 9545 (OSI Application Layer Structure)
- Other parts of IEC 61158-5 covering different fieldbus Types and ASE definitions
Keywords: IEC 61158-5-9, Type 9 fieldbus, application layer, fieldbus application services, industrial communication networks, Fieldbus Reference Model, OSI application layer.
Frequently Asked Questions
IEC 61158-5-9:2007 is a standard published by the International Electrotechnical Commission (IEC). Its full title is "Industrial communication networks - Fieldbus specifications - Part 5-9: Application layer service definition - Type 9 elements". This standard covers: IEC 61158-5-9:2007 defines the services provided to the FAL user at the boundary between the user and the Application Layer of the Fieldbus Reference Model, and SystemsManagement at the boundary between the Application Layer and Systems Management of the Fieldbus Reference Model. This standard specifies the structure and services of the Type 9 IEC fieldbus Application Layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498) and the OSI Application Layer Structure (ISO/IEC 9545). This first edition and its companion parts of the IEC 61158-5 subseries cancel and replace IEC 61158-5:2003. This edition of this part constitutes an editorial revision. This edition of IEC 61158-5 includes the following significant changes from the previous edition: - deletion of the former Type 6 fieldbus for lack of market relevance; - addition of new types of fieldbuses; - partition of part 5 of the third edition into multiple parts numbered 5-2, 5-3,... This bilingual version (2014-12) corresponds to the monolingual English version, published in 2007-12.
IEC 61158-5-9:2007 defines the services provided to the FAL user at the boundary between the user and the Application Layer of the Fieldbus Reference Model, and SystemsManagement at the boundary between the Application Layer and Systems Management of the Fieldbus Reference Model. This standard specifies the structure and services of the Type 9 IEC fieldbus Application Layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498) and the OSI Application Layer Structure (ISO/IEC 9545). This first edition and its companion parts of the IEC 61158-5 subseries cancel and replace IEC 61158-5:2003. This edition of this part constitutes an editorial revision. This edition of IEC 61158-5 includes the following significant changes from the previous edition: - deletion of the former Type 6 fieldbus for lack of market relevance; - addition of new types of fieldbuses; - partition of part 5 of the third edition into multiple parts numbered 5-2, 5-3,... This bilingual version (2014-12) corresponds to the monolingual English version, published in 2007-12.
IEC 61158-5-9:2007 is classified under the following ICS (International Classification for Standards) categories: 25.040.40 - Industrial process measurement and control; 35.100.70 - Application layer. The ICS classification helps identify the subject area and facilitates finding related standards.
IEC 61158-5-9:2007 has the following relationships with other standards: It is inter standard links to IEC 61158-5:2003/COR1:2004, IEC 61158-5:2003, IEC 61158-5-9:2014. Understanding these relationships helps ensure you are using the most current and applicable version of the standard.
You can purchase IEC 61158-5-9:2007 directly from iTeh Standards. The document is available in PDF format and is delivered instantly after payment. Add the standard to your cart and complete the secure checkout process. iTeh Standards is an authorized distributor of IEC standards.
Standards Content (Sample)
IEC 61158-5-9
Edition 1.0 2007-12
INTERNATIONAL
STANDARD
Industrial communication networks – Fieldbus specifications –
Part 5-9: Application layer service definition – Type 9 elements
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form
or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from
either IEC or IEC's member National Committee in the country of the requester.
If you have any questions about IEC copyright or have an enquiry about obtaining additional rights to this publication,
please contact the address below or your local IEC member National Committee for further information.
IEC Central Office
3, rue de Varembé
CH-1211 Geneva 20
Switzerland
Email: inmail@iec.ch
Web: www.iec.ch
About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.
About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigenda or an amendment might have been published.
ƒ Catalogue of IEC publications: www.iec.ch/searchpub
The IEC on-line Catalogue enables you to search by a variety of criteria (reference number, text, technical committee,…).
It also gives information on projects, withdrawn and replaced publications.
ƒ IEC Just Published: www.iec.ch/online_news/justpub
Stay up to date on all new IEC publications. Just Published details twice a month all new publications released. Available
on-line and also by email.
ƒ Electropedia: www.electropedia.org
The world's leading online dictionary of electronic and electrical terms containing more than 20 000 terms and definitions
in English and French, with equivalent terms in additional languages. Also known as the International Electrotechnical
Vocabulary online.
ƒ Customer Service Centre: www.iec.ch/webstore/custserv
If you wish to give us your feedback on this publication or need further assistance, please visit the Customer Service
Centre FAQ or contact us:
Email: csc@iec.ch
Tel.: +41 22 919 02 11
Fax: +41 22 919 03 00
IEC 61158-5-9
Edition 1.0 2007-12
INTERNATIONAL
STANDARD
Industrial communication networks – Fieldbus specifications –
Part 5-9: Application layer service definition – Type 9 elements
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
XE
ICS 35.100.70; 25.040.40 ISBN 2-8318-9457-3
– 2 – 61158-5-9 © IEC:2007(E)
CONTENTS
FOREWORD.5
INTRODUCTION.7
1 Scope.8
1.1 Overview .8
1.2 Specifications .9
1.3 Conformance.9
2 Normative references .9
3 Terms, definitions, symbols, abbreviations and conventions .10
3.1 ISO/IEC 7498-1 terms .10
3.2 ISO/IEC 8822 terms .10
3.3 ISO/IEC 9545 terms .10
3.4 ISO/IEC 8824 terms .10
3.5 IEC/TR 61158-1 terms.10
3.6 Type 9 fieldbus application-layer specific definitions.14
3.7 Abbreviations and symbols .14
3.8 Conventions .15
4 Concepts .18
5 Data type ASE.18
5.1 Overview .18
5.2 Formal definition of data type objects .20
5.3 FAL defined data types.22
5.4 Data type ASE service specification .25
5.5 Summary of data types.25
6 Communication model specification .26
6.1 Concepts .26
6.2 Common parameters .26
6.3 ASEs .26
6.4 ARs .114
6.5 Summary of classes .118
6.6 Permitted services by AREP role .118
Bibliography.120
Figure 1 – Data type class hierarchy .19
Figure 2 – VFD model .26
Figure 3 – Abstract model of an automation system (VFD) .27
Figure 4 – Source OD/remote OD .33
Figure 5 – Put OD state machine .46
Figure 6 – Transaction object state machine .52
Figure 7 – Context test of two features-supported with different bitstring length .60
Figure 8 – Overview of event .79
Figure 9 – Event state machine.85
Figure 10 – Domain genericdownload/download state machine (server).99
Figure 11 – Domain upload state machine (server) .101
61158-5-9 © IEC:2007(E) – 3 –
Figure 12 – State diagram.112
Table 1 – Data type summary .25
Table 2 – Logical status .28
Table 3 – Status.29
Table 4 – Unsolicited status .30
Table 5 – Identify .31
Table 6 – Structure of the object dictionary .34
Table 7 – Structure of the static list of types .34
Table 8 – Structure of the static object dictionary.34
Table 9 – Structure of the dynamic list of variable lists.35
Table 10 – Structure of the dynamic list of program invocations .35
Table 11 – Empty object dictionary .39
Table 12 – Get OD service parameters .42
Table 13 – Initiate put OD service parameters .44
Table 14 – Put OD service parameters.45
Table 15 – Terminate put OD service parameters .46
Table 16 – Put OD state transitions.48
Table 17 – Attribute FMS features supported .50
Table 18 – Transaction object state transitions .53
Table 19 – Initiate service parameters .54
Table 20 – Failure reasons .55
Table 21 – Abort service parameters.56
Table 22 – User abort reasons .57
Table 23 – APO ASE abort reasons .57
Table 24 – Reject service parameters .58
Table 25 – Reject APDU reasons.58
Table 26 – Compatibility of the local context to the remote context .59
Table 27 – Unconfirmed send service parameters.62
Table 28 – Confirmed send service parameters .63
Table 29 – AR-Abort service parameters.63
Table 30 – Compel service parameters .64
Table 31 – Get buffered message service parameters.65
Table 32 – AR-Status service parameters .66
Table 33 – Simple variable access group membership .67
Table 34 – Simple variable access rights membership .67
Table 35 – Array variable access group membership .69
Table 36 – Array variable access rights membership.70
Table 37 – Variable list access group membership.71
Table 38 – Variable list access rights membership .72
Table 39 – Read service parameters.74
Table 40 – Write service parameters.75
Table 41 – Information report service parameters .76
– 4 – 61158-5-9 © IEC:2007(E)
Table 42 – Define variable list service parameters .77
Table 43 – Delete variable list service parameters .78
Table 44 – Event access group membership .80
Table 45 – Event access rights membership .81
Table 46 – Event notification service parameters .82
Table 47 – Acknowledge event notification service parameters .83
Table 48 – Alter event condition monitoring service parameters .84
Table 49 – Event state transitions .85
Table 50 – Domain access group membership .86
Table 51 – Domain access rights membership .86
Table 52 – GenericInitiateDownloadSequence .88
Table 53 – GenericDownloadSegment .89
Table 54 – GenericTerminateDownloadSequence .90
Table 55 – InitiateDownloadSequence .91
Table 56 – DownloadSegment .92
Table 57 – TerminateDownloadSequence .93
Table 58 – RequestDomainDownload.94
Table 59 – InitiateUploadSequence.95
Table 60 – UploadSegment.96
Table 61 – TerminateUploadSequence .97
Table 62 – RequestDomainUpload.98
Table 63 – Domain genericDownload/download state machine (server) .99
Table 64 – Domain upload state machine (server) .101
Table 65 – Program invocation access group membership .103
Table 66 – Program invocation access group membership .103
Table 67 – Create program invocation service parameters .105
Table 68 – Delete program invocation service parameters .106
Table 69 – Start service parameters .107
Table 70 – Stop service parameters.108
Table 71 – Resume service parameters .109
Table 72 – Reset service parameters .110
Table 73 – Kill service parameters .111
Table 74 – Program invocation state machine .113
Table 75 – Class summary.118
Table 76 – Services by AREP role .118
61158-5-9 © IEC:2007(E) – 5 –
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
INDUSTRIAL COMMUNICATION NETWORKS –
FIELDBUS SPECIFICATIONS –
Part 5-9: Application layer service definition – Type 9 elements
FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote
international co-operation on all questions concerning standardization in the electrical and electronic fields. To
this end and in addition to other activities, IEC publishes International Standards, Technical Specifications,
Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC
Publication(s)”). Their preparation is entrusted to technical committees; any IEC National Committee interested
in the subject dealt with may participate in this preparatory work. International, governmental and non-
governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely
with the International Organization for Standardization (ISO) in accordance with conditions determined by
agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all
interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence
between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in
the latter.
5) IEC 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 from their respective intellectual-property-right holders.
International Standard IEC 61158-5-9 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-5 subseries cancel and replace
IEC 61158-5:2003. This edition of this part constitutes an editorial revision.
This edition of IEC 61158-5 includes the following significant changes from the previous
edition:
a) deletion of the former Type 6 fieldbus, and the former Type 1 fieldbus application layer, for
lack of market relevance;
– 6 – 61158-5-9 © IEC:2007(E)
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.
61158-5-9 © IEC:2007(E) – 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/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.
– 8 – 61158-5-9 © IEC:2007(E)
INDUSTRIAL COMMUNICATION NETWORKS –
FIELDBUS SPECIFICATIONS –
Part 5-9: Application layer service definition – Type 9 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 9 fieldbus. The term “time-critical” is used to represent the presence
of a time-window, within which one or more specified actions are required to be completed
with some defined level of certainty. Failure to complete specified actions within the time
window risks failure of the applications requesting the actions, with attendant risk to
equipment, plant and possibly human life.
This standard defines in an abstract way the externally visible 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
61158-5-9 © IEC:2007(E) – 9 –
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.
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.
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 the Type 9 application layer services as defined in this standard.
2 Normative references
The following referenced standards 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 standard (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 9545, Information technology – Open Systems Interconnection – Application Layer
structure
– 10 – 61158-5-9 © IEC:2007(E)
3 Terms, definitions, symbols, abbreviations and conventions
For the purposes of this document, the following terms as defined in these publications 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 ISO/IEC 8824 terms
a) object identifier
b) type
3.5 IEC/TR 61158-1 terms
The following IEC/TR 61158-1 terms apply.
3.5.1 application
function or data structure for which data is consumed or produced
3.5.2 application layer interoperability
capability of application entities to perform coordinated and cooperative operations using the
services of the FAL
61158-5-9 © IEC:2007(E) – 11 –
3.5.3 application object
object class that manages and provides the run time exchange of messages across the
network and within the network device
NOTE: Multiple types of application object classes may be defined
3.5.4 application process
part of a distributed application on a network, which is located on one device and
unambiguously addressed
3.5.5 application process identifier
distinguishes multiple application processes used in a device
3.5.6 application process object
component of an application process that is identifiable and accessible through an FAL
application relationship. Application process object definitions are composed of a set of
values for the attributes of their class.
3.5.7 application process object class
a class of application process objects defined in terms of the set of their network-accessible
attributes and services
3.5.8 application relationship
cooperative association between two or more application-entity-invocations for the purpose of
exchange of information and coordination of their joint operation. This relationship is activated
either by the exchange of application-protocol-data-units or as a result of preconfiguration
activities
3.5.9 application relationship application service element
application-service-element that provides the exclusive means for establishing and
terminating all application relationships
3.5.10 application relationship endpoint
context and behavior of an application relationship as seen and maintained by one of the
application processes involved in the application relationship. Each application process
involved in the application relationship maintains its own application relationship endpoint
3.5.11 attribute
description of an externally visible characteristic or feature of an object. The attributes of an
object contain information about variable portions of an object. Typically, they provide status
information or govern the operation of an object. Attributes may also affect the behaviour of
an object. Attributes are divided into class attributes and instance attributes
3.5.12 behaviour
indication of how the object responds to particular events. Its description includes the
relationship between attribute values and services
– 12 – 61158-5-9 © IEC:2007(E)
3.5.13 class
a set of objects, all of which represent the same kind of system component. A class is a
generalisation of the object; a template for defining variables and methods. All objects in a
class are identical in form and behaviour, but usually contain different data in their attributes
3.5.14 class attributes
an attribute that is shared by all objects within the same class
3.5.15 class code
a unique identifier assigned to each object class
3.5.16 class specific service
a service defined by a particular object class to perform a required function which is not
performed by a common service. A class specific object is unique to the object class which
defines it
3.5.17 client
a) an object which uses the services of another (server) object to perform a task
b) an initiator of a message to which a server reacts, such as the role of an AR endpoint in
which it issues confirmed service request APDUs to a single AR endpoint acting as a server
3.5.18 conveyance path
unidirectional flow of APDUs across an application relationship
3.5.19 cyclic
term used to describe events which repeat in a regular and repetitive manner
3.5.20 dedicated AR
AR used directly by the FAL User. On Dedicated ARs, only the FAL Header and the user data
are transferred
3.5.21 device
a physical hardware connection to the link. A device may contain more than one node
3.5.22 device profile
a collection of device dependent information and functionality providing consistency between
similar devices of the same device type
3.5.23 dynamic AR
AR that requires the use of the AR establishment procedures to place it into an established
state
3.5.24 endpoint
one of the communicating entities involved in a connection
61158-5-9 © IEC:2007(E) – 13 –
3.5.25 error
a discrepancy between a computed, observed or measured value or condition and the
specified or theoretically correct value or condition
3.5.26 error class
general grouping for error definitions. Error codes for specific errors are defined within an
error class
3.5.27 error code
identification of a specific type of error within an error class
3.5.28 FAL subnet
networks composed of one or more data link segments. They are permitted to contain
bridges, but not routers. FAL subnets are identified by a subset of the network address
3.5.29 logical device
specifies a certain FAL class that abstracts a software component or a firmware component
as an autonomous self-contained facility of an automation device
3.5.30 management information
network-accessible information that supports managing the operation of the fieldbus system,
including the application layer. Managing includes functions such as controlling, monitoring,
and diagnosing
3.5.31 network
a series of nodes connected by some type of communication medium. The connection paths
between any pair of nodes can include repeaters, routers and gateways
3.5.32 peer
role of an AR endpoint in which it is capable of acting as both client and server
3.5.33 pre-defined AR endpoint
AR endpoint that is defined locally within a device without use of the create service. Pre-
defined ARs that are not pre-established are established before being used
3.5.34 pre-established AR endpoint
AR endpoint that is placed in an established state during configuration of the AEs that control
its endpoints
3.5.35 publisher
role of an AR endpoint in which it transmits APDUs onto the fieldbus for consumption by one
or more subscribers. The publisher may not be aware of the identity or the number of
subscribers and it may publish its APDUs using a dedicated AR. Two types of publishers are
defined by this standard, Pull Publishers and Push Publishers, each of which is defined
separately
– 14 – 61158-5-9 © IEC:2007(E)
3.5.36 server
a) role of an AREP in which it returns a confirmed service response APDU to the client that
initiated the request
b) an object which provides services to another (client) object
3.5.37 service
operation or function than an object and/or object class performs upon request from another
object and/or object class. A set of common services is defined and provisions for the
definition of object-specific services are provided. Object-specific services are those which
are defined by a particular object class to perform a required function which is not performed
by a common service
3.5.38 subscriber
role of an AREP in which it receives APDUs produced by a publisher. Two types of
subscribers are defined by this standard, pull subscribers and push subscribers, each of
which is defined separately
3.6 Type 9 fieldbus application-layer specific definitions
There are no additional terms defined for this part.
3.7 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
API Application Process Identifier
AR Application Relationship
AREP Application Relationship End Point
ASCII American Standard Code for Information Interchange
ASE Application Service Element
Cnf Confirmation
DL- (as a prefix) Data Link-
DLC Data Link Connection
DLCEP Data Link Connection End Point
DLL Data Link Layer
DLM Data Link-management
DLSAP Data Link Service Access Point
DLSDU DL-service-data-unit
FAL Fieldbus Application Layer
61158-5-9 © IEC:2007(E) – 15 –
ID Identifier
IEC International Electrotechnical Commission
Ind Indication
LME Layer Management Entity
OSI Open Systems Interconnect
QoS Quality of Service
Req Request
Rsp Response
SAP Service Access Point
SDU Service Data Unit
SMIB System Management Information Base
SMK System Management Kernel
VFD Virtual Field Device
3.8 Conventions
3.8.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 attributes are accessible from
instances of the class using the Object Dictionary ASE services specified in Clause 6.3.2 of
this standard. The service specification defines the services that are provided by the ASE.
3.8.2 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:
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
– 16 – 61158-5-9 © IEC:2007(E)
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 unique within the FAL ASE that will provide the services for this class. When qualified
by the identity of its FAL ASE, it unambiguously identifies the class within the scope of
the FAL. The value "NULL" indicates that the class cannot be instantiated. Class IDs
between 1 and 255 are reserved by this standard to identify standardized classes. They
have been assigned to maintain compatibility with existing national standards. CLASS IDs
between 256 and 2048 are allocated for identifying user defined classes.
(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).
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 an management service (2).
61158-5-9 © IEC:2007(E) – 17 –
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.8.3 Conventions for service definitions
3.8.3.1 General
This standard uses the descriptive conventions given in ISO/IEC 10731.
The service model, service primitives, and time-sequence diagrams used are entirely abstract
descriptions; they do not represent a specification
...
IEC 61158-5-9 ®
Edition 1.0 2007-12
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
Industrial communication networks – Fieldbus specifications –
Part 5-9: Application layer service definition – Type 9 elements
Réseaux de communication industriels – Spécifications des bus de terrain –
Partie 5-9: Définition des services des couches d'application –
Éléments de Type 9
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form
or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from
either IEC or IEC's member National Committee in the country of the requester. If you have any questions about IEC
copyright or have an enquiry about obtaining additional rights to this publication, please contact the address below or
your local IEC member National Committee for further information.
Droits de reproduction réservés. Sauf indication contraire, aucune partie de cette publication ne peut être reproduite
ni utilisée sous quelque forme que ce soit et par aucun procédé, électronique ou mécanique, y compris la photocopie
et les microfilms, sans l'accord écrit de l'IEC ou du Comité national de l'IEC du pays du demandeur. Si vous avez des
questions sur le copyright de l'IEC ou si vous désirez obtenir des droits supplémentaires sur cette publication, utilisez
les coordonnées ci-après ou contactez le Comité national de l'IEC de votre pays de résidence.
IEC Central Office Tel.: +41 22 919 02 11
3, rue de Varembé Fax: +41 22 919 03 00
CH-1211 Geneva 20 info@iec.ch
Switzerland www.iec.ch
About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.
About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigenda or an amendment might have been published.
IEC Catalogue - webstore.iec.ch/catalogue Electropedia - www.electropedia.org
The stand-alone application for consulting the entire The world's leading online dictionary of electronic and
bibliographical information on IEC International Standards, electrical terms containing more than 30 000 terms and
Technical Specifications, Technical Reports and other definitions in English and French, with equivalent terms in 14
documents. Available for PC, Mac OS, Android Tablets and additional languages. Also known as the International
iPad. Electrotechnical Vocabulary (IEV) online.
IEC publications search - www.iec.ch/searchpub IEC Glossary - std.iec.ch/glossary
The advanced search enables to find IEC publications by a More than 55 000 electrotechnical terminology entries in
variety of criteria (reference number, text, technical English and French extracted from the Terms and Definitions
committee,…). It also gives information on projects, replaced clause of IEC publications issued since 2002. Some entries
and withdrawn publications. have been collected from earlier publications of IEC TC 37,
77, 86 and CISPR.
IEC Just Published - webstore.iec.ch/justpublished
Stay up to date on all new IEC publications. Just Published IEC Customer Service Centre - webstore.iec.ch/csc
details all new publications released. Available online and If you wish to give us your feedback on this publication or
also once a month by email. need further assistance, please contact the Customer Service
Centre: csc@iec.ch.
A propos de l'IEC
La Commission Electrotechnique Internationale (IEC) est la première organisation mondiale qui élabore et publie des
Normes internationales pour tout ce qui a trait à l'électricité, à l'électronique et aux technologies apparentées.
A propos des publications IEC
Le contenu technique des publications IEC est constamment revu. Veuillez vous assurer que vous possédez l’édition la
plus récente, un corrigendum ou amendement peut avoir été publié.
Catalogue IEC - webstore.iec.ch/catalogue Electropedia - www.electropedia.org
Application autonome pour consulter tous les renseignements
Le premier dictionnaire en ligne de termes électroniques et
bibliographiques sur les Normes internationales,
électriques. Il contient plus de 30 000 termes et définitions en
Spécifications techniques, Rapports techniques et autres
anglais et en français, ainsi que les termes équivalents dans
documents de l'IEC. Disponible pour PC, Mac OS, tablettes
14 langues additionnelles. Egalement appelé Vocabulaire
Android et iPad.
Electrotechnique International (IEV) en ligne.
Recherche de publications IEC - www.iec.ch/searchpub
Glossaire IEC - std.iec.ch/glossary
Plus de 55 000 entrées terminologiques électrotechniques, en
La recherche avancée permet de trouver des publications IEC
en utilisant différents critères (numéro de référence, texte, anglais et en français, extraites des articles Termes et
comité d’études,…). Elle donne aussi des informations sur les Définitions des publications IEC parues depuis 2002. Plus
projets et les publications remplacées ou retirées. certaines entrées antérieures extraites des publications des
CE 37, 77, 86 et CISPR de l'IEC.
IEC Just Published - webstore.iec.ch/justpublished
Service Clients - webstore.iec.ch/csc
Restez informé sur les nouvelles publications IEC. Just
Published détaille les nouvelles publications parues. Si vous désirez nous donner des commentaires sur cette
Disponible en ligne et aussi une fois par mois par email. publication ou si vous avez des questions contactez-nous:
csc@iec.ch.
IEC 61158-5-9 ®
Edition 1.0 2007-12
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
Industrial communication networks – Fieldbus specifications –
Part 5-9: Application layer service definition – Type 9 elements
Réseaux de communication industriels – Spécifications des bus de terrain –
Partie 5-9: Définition des services des couches d'application –
Éléments de Type 9
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
PRICE CODE
INTERNATIONALE
CODE PRIX XE
ICS 25.040.40; 35.100.70 ISBN 978-2-8322-1949-2
– 2 – IEC 61158-5-9:2007 © IEC 2007
CONTENTS
FOREWORD . 5
INTRODUCTION . 7
1 Scope . 8
1.1 Overview . 8
1.2 Specifications . 9
1.3 Conformance . 9
2 Normative references . 9
3 Terms, definitions, symbols, abbreviations and conventions . 10
3.1 ISO/IEC 7498-1 terms . 10
3.2 ISO/IEC 8822 terms . 10
3.3 ISO/IEC 9545 terms . 10
3.4 ISO/IEC 8824 terms . 10
3.5 IEC/TR 61158-1 terms . 10
3.6 Type 9 fieldbus application-layer specific definitions. 14
3.7 Abbreviations and symbols . 14
3.8 Conventions . 15
4 Concepts . 18
5 Data type ASE . 18
5.1 Overview . 18
5.2 Formal definition of data type objects . 20
5.3 FAL defined data types . 22
5.4 Data type ASE service specification . 25
5.5 Summary of data types . 25
6 Communication model specification . 26
6.1 Concepts . 26
6.2 Common parameters . 26
6.3 ASEs . 26
6.4 ARs . 114
6.5 Summary of classes . 118
6.6 Permitted services by AREP role . 118
Bibliography . 120
Figure 1 – Data type class hierarchy . 19
Figure 2 – VFD model . 26
Figure 3 – Abstract model of an automation system (VFD) . 27
Figure 4 – Source OD/remote OD . 33
Figure 5 – Put OD state machine . 46
Figure 6 – Transaction object state machine . 52
Figure 7 – Context test of two features-supported with different bitstring length . 60
Figure 8 – Overview of event . 79
Figure 9 – Event state machine . 85
Figure 10 – Domain genericdownload/download state machine (server) . 99
Figure 11 – Domain upload state machine (server) . 101
Figure 12 – State diagram. 112
Table 1 – Data type summary . 25
Table 2 – Logical status . 28
Table 3 – Status . 29
Table 4 – Unsolicited status . 30
Table 5 – Identify . 31
Table 6 – Structure of the object dictionary . 34
Table 7 – Structure of the static list of types . 34
Table 8 – Structure of the static object dictionary . 34
Table 9 – Structure of the dynamic list of variable lists . 35
Table 10 – Structure of the dynamic list of program invocations . 35
Table 11 – Empty object dictionary . 39
Table 12 – Get OD service parameters . 42
Table 13 – Initiate put OD service parameters . 44
Table 14 – Put OD service parameters . 45
Table 15 – Terminate put OD service parameters . 46
Table 16 – Put OD state transitions . 48
Table 17 – Attribute FMS features supported . 50
Table 18 – Transaction object state transitions . 53
Table 19 – Initiate service parameters . 54
Table 20 – Failure reasons . 55
Table 21 – Abort service parameters . 56
Table 22 – User abort reasons . 57
Table 23 – APO ASE abort reasons . 57
Table 24 – Reject service parameters . 58
Table 25 – Reject APDU reasons . 58
Table 26 – Compatibility of the local context to the remote context . 59
Table 27 – Unconfirmed send service parameters . 62
Table 28 – Confirmed send service parameters . 63
Table 29 – AR-Abort service parameters . 63
Table 30 – Compel service parameters . 64
Table 31 – Get buffered message service parameters. 65
Table 32 – AR-Status service parameters . 66
Table 33 – Simple variable access group membership . 67
Table 34 – Simple variable access rights membership . 67
Table 35 – Array variable access group membership . 69
Table 36 – Array variable access rights membership . 70
Table 37 – Variable list access group membership . 71
Table 38 – Variable list access rights membership . 72
Table 39 – Read service parameters . 74
Table 40 – Write service parameters . 75
Table 41 – Information report service parameters . 76
Table 42 – Define variable list service parameters . 77
– 4 – IEC 61158-5-9:2007 © IEC 2007
Table 43 – Delete variable list service parameters . 78
Table 44 – Event access group membership . 80
Table 45 – Event access rights membership . 81
Table 46 – Event notification service parameters . 82
Table 47 – Acknowledge event notification service parameters . 83
Table 48 – Alter event condition monitoring service parameters . 84
Table 49 – Event state transitions . 85
Table 50 – Domain access group membership . 86
Table 51 – Domain access rights membership . 86
Table 52 – GenericInitiateDownloadSequence . 88
Table 53 – GenericDownloadSegment . 89
Table 54 – GenericTerminateDownloadSequence . 90
Table 55 – InitiateDownloadSequence . 91
Table 56 – DownloadSegment . 92
Table 57 – TerminateDownloadSequence . 93
Table 58 – RequestDomainDownload . 94
Table 59 – InitiateUploadSequence . 95
Table 60 – UploadSegment . 96
Table 61 – TerminateUploadSequence . 97
Table 62 – RequestDomainUpload . 98
Table 63 – Domain genericDownload/download state machine (server) . 99
Table 64 – Domain upload state machine (server) . 101
Table 65 – Program invocation access group membership . 103
Table 66 – Program invocation access group membership . 103
Table 67 – Create program invocation service parameters . 105
Table 68 – Delete program invocation service parameters . 106
Table 69 – Start service parameters . 107
Table 70 – Stop service parameters . 108
Table 71 – Resume service parameters . 109
Table 72 – Reset service parameters . 110
Table 73 – Kill service parameters . 111
Table 74 – Program invocation state machine . 113
Table 75 – Class summary . 118
Table 76 – Services by AREP role . 118
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
INDUSTRIAL COMMUNICATION NETWORKS –
FIELDBUS SPECIFICATIONS –
Part 5-9: Application layer service definition – Type 9 elements
FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote
international co-operation on all questions concerning standardization in the electrical and electronic fields. To
this end and in addition to other activities, IEC publishes International Standards, Technical Specifications,
Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC
Publication(s)”). Their preparation is entrusted to technical committees; any IEC National Committee interested
in the subject dealt with may participate in this preparatory work. International, governmental and non-
governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely
with the International Organization for Standardization (ISO) in accordance with conditions determined by
agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all
interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence
between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in
the latter.
5) IEC 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 from their respective intellectual-property-right holders.
International Standard IEC 61158-5-9 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-5 subseries cancel and replace
IEC 61158-5:2003. This edition of this part constitutes an editorial revision.
This edition of IEC 61158-5 includes the following significant changes from the previous
edition:
a) deletion of the former Type 6 fieldbus, and the former Type 1 fieldbus application layer,
for lack of market relevance;
b) addition of new types of fieldbuses;
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.
– 8 – IEC 61158-5-9:2007 © IEC 2007
INDUSTRIAL COMMUNICATION NETWORKS –
FIELDBUS SPECIFICATIONS –
Part 5-9: Application layer service definition – Type 9 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 9 fieldbus. The term “time-critical” is used to represent the presence
of a time-window, within which one or more specified actions are required to be completed
with some defined level of certainty. Failure to complete specified actions within the time
window risks failure of the applications requesting the actions, with attendant risk to
equipment, plant and possibly human life.
This standard defines in an abstract way the externally visible 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.
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.
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 the Type 9 application layer services as defined in this standard.
2 Normative references
The following referenced standards 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 standard (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 9545, Information technology – Open Systems Interconnection – Application Layer
structure
– 10 – IEC 61158-5-9:2007 © IEC 2007
3 Terms, definitions, symbols, abbreviations and conventions
For the purposes of this document, the following terms as defined in these publications 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 ISO/IEC 8824 terms
a) object identifier
b) type
3.5 IEC/TR 61158-1 terms
The following IEC/TR 61158-1 terms apply.
3.5.1 application
function or data structure for which data is consumed or produced
3.5.2 application layer interoperability
capability of application entities to perform coordinated and cooperative operations using the
services of the FAL
3.5.3 application object
object class that manages and provides the run time exchange of messages across the
network and within the network device
NOTE: Multiple types of application object classes may be defined
3.5.4 application process
part of a distributed application on a network, which is located on one device and
unambiguously addressed
3.5.5 application process identifier
distinguishes multiple application processes used in a device
3.5.6 application process object
component of an application process that is identifiable and accessible through an FAL
application relationship. Application process object definitions are composed of a set of
values for the attributes of their class.
3.5.7 application process object class
a class of application process objects defined in terms of the set of their network-accessible
attributes and services
3.5.8 application relationship
cooperative association between two or more application-entity-invocations for the purpose of
exchange of information and coordination of their joint operation. This relationship is activated
either by the exchange of application-protocol-data-units or as a result of preconfiguration
activities
3.5.9 application relationship application service element
application-service-element that provides the exclusive means for establishing and
terminating all application relationships
3.5.10 application relationship endpoint
context and behavior of an application relationship as seen and maintained by one of the
application processes involved in the application relationship. Each application process
involved in the application relationship maintains its own application relationship endpoint
3.5.11 attribute
description of an externally visible characteristic or feature of an object. The attributes of an
object contain information about variable portions of an object. Typically, they provide status
information or govern the operation of an object. Attributes may also affect the behaviour of
an object. Attributes are divided into class attributes and instance attributes
3.5.12 behaviour
indication of how the object responds to particular events. Its description includes the
relationship between attribute values and services
– 12 – IEC 61158-5-9:2007 © IEC 2007
3.5.13 class
a set of objects, all of which represent the same kind of system component. A class is a
generalisation of the object; a template for defining variables and methods. All objects in a
class are identical in form and behaviour, but usually contain different data in their attributes
3.5.14 class attributes
an attribute that is shared by all objects within the same class
3.5.15 class code
a unique identifier assigned to each object class
3.5.16 class specific service
a service defined by a particular object class to perform a required function which is not
performed by a common service. A class specific object is unique to the object class which
defines it
3.5.17 client
a) an object which uses the services of another (server) object to perform a task
b) an initiator of a message to which a server reacts, such as the role of an AR endpoint in
which it issues confirmed service request APDUs to a single AR endpoint acting as a
server
3.5.18 conveyance path
unidirectional flow of APDUs across an application relationship
3.5.19 cyclic
term used to describe events which repeat in a regular and repetitive manner
3.5.20 dedicated AR
AR used directly by the FAL User. On Dedicated ARs, only the FAL Header and the user data
are transferred
3.5.21 device
a physical hardware connection to the link. A device may contain more than one node
3.5.22 device profile
a collection of device dependent information and functionality providing consistency between
similar devices of the same device type
3.5.23 dynamic AR
AR that requires the use of the AR establishment procedures to place it into an established
state
3.5.24 endpoint
one of the communicating entities involved in a connection
3.5.25 error
a discrepancy between a computed, observed or measured value or condition and the
specified or theoretically correct value or condition
3.5.26 error class
general grouping for error definitions. Error codes for specific errors are defined within an
error class
3.5.27 error code
identification of a specific type of error within an error class
3.5.28 FAL subnet
networks composed of one or more data link segments. They are permitted to contain
bridges, but not routers. FAL subnets are identified by a subset of the network address
3.5.29 logical device
specifies a certain FAL class that abstracts a software component or a firmware component
as an autonomous self-contained facility of an automation device
3.5.30 management information
network-accessible information that supports managing the operation of the fieldbus system,
including the application layer. Managing includes functions such as controlling, monitoring,
and diagnosing
3.5.31 network
a series of nodes connected by some type of communication medium. The connection paths
between any pair of nodes can include repeaters, routers and gateways
3.5.32 peer
role of an AR endpoint in which it is capable of acting as both client and server
3.5.33 pre-defined AR endpoint
AR endpoint that is defined locally within a device without use of the create service. Pre-
defined ARs that are not pre-established are established before being used
3.5.34 pre-established AR endpoint
AR endpoint that is placed in an established state during configuration of the AEs that control
its endpoints
3.5.35 publisher
role of an AR endpoint in which it transmits APDUs onto the fieldbus for consumption by one
or more subscribers. The publisher may not be aware of the identity or the number of
subscribers and it may publish its APDUs using a dedicated AR. Two types of publishers are
defined by this standard, Pull Publishers and Push Publishers, each of which is defined
separately
– 14 – IEC 61158-5-9:2007 © IEC 2007
3.5.36 server
a) role of an AREP in which it returns a confirmed service response APDU to the client that
initiated the request
b) an object which provides services to another (client) object
3.5.37 service
operation or function than an object and/or object class performs upon request from another
object and/or object class. A set of common services is defined and provisions for the
definition of object-specific services are provided. Object-specific services are those which
are defined by a particular object class to perform a required function which is not performed
by a common service
3.5.38 subscriber
role of an AREP in which it receives APDUs produced by a publisher. Two types of
subscribers are defined by this standard, pull subscribers and push subscribers, each of
which is defined separately
3.6 Type 9 fieldbus application-layer specific definitions
There are no additional terms defined for this part.
3.7 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
API Application Process Identifier
AR Application Relationship
AREP Application Relationship End Point
ASCII American Standard Code for Information Interchange
ASE Application Service Element
Cnf Confirmation
DL- (as a prefix) Data Link-
DLC Data Link Connection
DLCEP Data Link Connection End Point
DLL Data Link Layer
DLM Data Link-management
DLSAP Data Link Service Access Point
DLSDU DL-service-data-unit
FAL Fieldbus Application Layer
ID Identifier
IEC International Electrotechnical Commission
Ind Indication
LME Layer Management Entity
OSI Open Systems Interconnect
QoS Quality of Service
Req Request
Rsp Response
SAP Service Access Point
SDU Service Data Unit
SMIB System Management Information Base
SMK System Management Kernel
VFD Virtual Field Device
3.8 Conventions
3.8.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 attributes are accessible from
instances of the class using the Object Dictionary ASE services specified in 6.3.2 of this
standard. The service specification defines the services that are provided by the ASE.
3.8.2 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:
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
– 16 – IEC 61158-5-9:2007 © IEC 2007
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 unique within the FAL ASE that will provide the services for this class. When qualified
by the identity of its FAL ASE, it unambiguously identifies the class within the scope of
the FAL. The value "NULL"
...
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...