IEC 61158-5-4:2007

IEC 61158-5-4
Edition 1.0 2007-12
INTERNATIONAL
STANDARD
Industrial communication networks – Fieldbus specifications –
Part 5-4: Application layer service definition – Type 4 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-4
Edition 1.0 2007-12
INTERNATIONAL
STANDARD
Industrial communication networks – Fieldbus specifications –
Part 5-4: Application layer service definition – Type 4 elements

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
XB
ICS 25.040.40; 35.100.70 ISBN 2-8318-9446-8

– 2 – 61158-5-4 © IEC:2007(E)
CONTENTS
FOREWORD.4
INTRODUCTION.5
1 Scope.7
1.1 Overview .7
1.2 Specifications.8
1.3 Conformance.8
2 Normative references .8
3 Terms and definitions .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 ISO/IEC 8824 terms .9
3.5 Fieldbus data-link layer terms.10
3.6 Fieldbus application layer specific definitions .10
3.7 Abbreviations and symbols.15
3.8 Conventions .17
4 Concepts .20
4.1 Overview .20
4.2 Architectural relationships .20
4.3 Fieldbus Application Layer structure.22
4.4 Fieldbus Application Layer naming and addressing .34
4.5 Architecture summary.35
4.6 FAL service procedures.36
4.7 Common FAL attributes.37
4.8 Common FAL service parameters.37
4.9 APDU size.38
5 Type 4 communication model specification .38
5.1 Concepts.38
5.2 Variable ASE.45
5.3 Application relationship ASE .64
Bibliography.71

Figure 1 – Relationship to the OSI basic reference model.20
Figure 2 – Architectural positioning of the fieldbus Application Layer .21
Figure 3 – Client/server interactions .24
Figure 4 – Pull model interactions.25
Figure 5 – Push model interactions .25
Figure 6 – APOs services conveyed by the FAL.27
Figure 7 – Application entity structure.29
Figure 8 – Example FAL ASEs.30
Figure 9 – FAL management of objects.31
Figure 10 – ASE service conveyance.32
Figure 11 – Defined and established AREPs.34
Figure 12 – FAL architectural components .36

61158-5-4 © IEC:2007(E) – 3 –
Figure 13 – FAL AE .39
Figure 14 – Summary of the FAL architecture .42
Figure 15 – FAL service procedure overview.43
Figure 16 – Time sequence diagram for the confirmed services .44
Figure 17 – Time sequence diagram for unconfirmed services .45

Table 1 – REQUEST service parameters .60
Table 2 – RESPONSE service parameters.61
Table 3 – Error codes by source .62
Table 4 – Reserve REP service parameters.62
Table 5 – Free AREP service parameters .63
Table 6 – Get REP attribute service parameters .63
Table 7 – Set REP attribute service parameters.64
Table 8 – AR send service parameters .68
Table 9 – AR acknowledge service parameters.68
Table 10 – AR get attributes service parameters.69
Table 11 – AR set attributes service parameters .69

– 4 – 61158-5-4 © IEC:2007(E)
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
INDUSTRIAL COMMUNICATION NETWORKS –
FIELDBUS SPECIFICATIONS –
Part 5-4: Application layer service definition – Type 4 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-4 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 a technical revision. This part and its
Type 4 companion parts also cancel and replace IEC/PAS 62412, published in 2005.
This edition of IEC 61158-5 includes the following significant changes from the previous
edition:
61158-5-4 © IEC:2007(E) – 5 –
a) deletion of the former Type 6 fieldbus for lack of market relevance;
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.

– 6 – 61158-5-4 © 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.

61158-5-4 © IEC:2007(E) – 7 –
INDUSTRIAL COMMUNICATION NETWORKS –
FIELDBUS SPECIFICATIONS –
Part 5-4: Application layer service definition – Type 4 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 4 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 Type 4
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 Type 4 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

– 8 – 61158-5-4 © IEC:2007(E)
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, 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 the Type 2 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 61158-3-4, Industrial communication networks – Fieldbus specifications – Part 3-4: Data-
link layer service definition – Type 4 elements
IEC 61158-4-4, Industrial communication networks – Fieldbus specifications – Part 4-4: Data-
link layer protocol specification – Type 4 elements
IEC 61158-6-4, Industrial communication networks – Fieldbus specifications – Part 6-4:
Application layer protocol specification – Type 4 elements
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
61158-5-4 © IEC:2007(E) – 9 –
ISO/IEC 8824, Information technology – Open Systems Interconnection – Specification of
Abstract Syntax Notation One (ASN.1)
ISO/IEC 9545, Information technology – Open Systems Interconnection – Application Layer
structure
ISO/IEC 10646-1, Information technology – Universal Multiple-Octet Coded Character Set
(UCS) – Architecture and Basic Multilingual Plane
ISO/IEC 10731, Information technology – Open Systems Interconnection – Basic Reference
Model – Conventions for the definition of OSI services
3 Terms and definitions
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
For the purposes of this document, the following terms as defined in ISO/IEC 8822 apply:
a) abstract syntax
b) presentation context
3.3 ISO/IEC 9545 terms
For the purposes of this document, the following terms as defined in ISO/IEC 9545 apply:
a) application-association
b) application-context
c) application context name
d) application-entity-invocation
e) application-entity-type
f) application-process-invocation
g) application-process-type
h) application-service-element
i) application control service element
3.4 ISO/IEC 8824 terms
For the purposes of this document, the following terms as defined in ISO/IEC 8824 apply:

– 10 – 61158-5-4 © IEC:2007(E)
a) object identifier
b) type
3.5 Fieldbus data-link layer terms
For the purposes of this document, the following terms apply.
a) DL-Time
b) DL-Scheduling-policy
c) DLCEP
d) DLC
e) DLPDU
f) DLSDU
g) DLSAP
h) fixed tag
i) generic tag
j) link
k) network address
l) node address
m) node
n) tag
o) scheduled
p) unscheduled
3.6 Fieldbus application layer specific definitions
For the purposes of this standard, the following terms and definitions apply.
3.6.1
application
function or data structure for which data is consumed or produced
3.6.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.6.3
application process
part of a distributed application on a network, which is located on one device and
unambiguously addressed
3.6.4
application process identifier
distinguishes multiple application processes used in a device
3.6.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

61158-5-4 © IEC:2007(E) – 11 –
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.6.6
application process object class
a class of application process objects defined in terms of the set of their network-accessible
attributes and services
3.6.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.6.8
application relationship application service element
application-service-element that provides the exclusive means for establishing and
terminating all application relationships
3.6.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.6.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 behaviour of an object.
Attributes are divided into class attributes and instance attributes.
3.6.11
behaviour
indication of how an object responds to particular eventss
3.6.12
bit-no
designates the number of a bit in a bitstring or an octet
3.6.13
channel
single physical or logical link of an input or output application object of a server to the process
3.6.14
class
a 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 behaviour, but usually contain different data in their attributes.
3.6.15
class attributes
attribute that is shared by all objects within the same class
3.6.16
class code
unique identifier assigned to each object class

– 12 – 61158-5-4 © IEC:2007(E)
3.6.17
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.6.18
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.6.19
communication objects
components that manage and provide a run time exchange of messages across the network
EXAMPLES: Connection Manager object, Unconnected Message Manager (UCMM) object, and Message Router
object
3.6.20
connection
logical binding between application objects that may be within the same or different devices
NOTE 1 Connections may be either point-to-point or multipoint.
3.6.21
conveyance path
unidirectional flow of APDUs across an application relationship
3.6.22
dedicated AR
AR used directly by the FAL User
NOTE  On Dedicated ARs, only the FAL Header and the user data are transferred.
3.6.23
default DL-address
value 126 as an initial value for DL-address, which has to be changed (e.g. by assignment of
an DL-address via the fieldbus) before operation with a DP-master (class 1)
3.6.24
device
physical hardware connected to the link
NOTE  A device may contain more than one node.
3.6.25
dynamic AR
AR that requires the use of the AR establishment procedures to place it into an established
state
3.6.26
endpoint
one of the communicating entities involved in a connection
3.6.27
error
discrepancy between a computed, observed or measured value or condition and the specified
or theoretically correct value or condition

61158-5-4 © IEC:2007(E) – 13 –
3.6.28
error class
general grouping for related error definitions and corresponding error codes
3.6.29
error code
identification of a specific type of error within an error class
3.6.30
event
an instance of a change of conditions
3.6.31
FAL subnet
subnetworks composed of one or more data link segments, identified by a subset of the
network address
NOTE  FAL subnets are permitted to contain bridges but not routers.
3.6.32
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.6.33
frame
denigrated synonym for DLPDU
3.6.34
interface
a) shared boundary between two functional units, defined by functional characteristics, signal
characteristics, or other characteristics as appropriate
b) collection of FAL class attributes and services that represents a specific view on the FAL
class
3.6.35
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.6.36
index
address of an object within an application process
3.6.37
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 state.
NOTE  The terms object, instance, and object instance are used to refer to a specific instance.
3.6.38
instance attributes
attribute that is unique to an object instance and not shared by the object class

– 14 – 61158-5-4 © IEC:2007(E)
3.6.39
instantiated
object that has been created in a device
3.6.40
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.6.41
manufacturer ID
identification of each product manufacturer by a unique number
3.6.42
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.6.43
member
piece of an attribute that is structured as an element of an array
3.6.44
method
a synonym for an operational service which is provided by the server ASE and
invoked by a client
3.6.45
module
hardware or logical component of a physical device
3.6.46
network
a set of nodes connected by some type of communication medium, including any intervening
repeaters, bridges, routers and lower-layer gateways
3.6.47
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 behaviour
3.6.48
object specific service
service unique to the object class which defines it
3.6.49
peer
role of an AR endpoint in which it is capable of acting as both client and server
3.6.50
physical device
an automation or other network device

61158-5-4 © IEC:2007(E) – 15 –
3.6.51
property
a general term for descriptive information about an object
3.6.52
provider
source of a data connection
3.6.53
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 and it may publish its APDUs
using a dedicated AR.
3.6.54
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.6.55
pull subscriber
type of subscriber that recognizes received confirmed service response APDUs as published
object data
3.6.56
resource
a processing or information capability of a subsystem
3.6.57
route endpoint
object container containing Variable Objects of a variable class
3.6.58
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.6.59
service
operation or function than an object and/or object class performs upon request from another
object and/or object class
3.6.60
subscriber
role of an AREP in which it receives APDUs produced by a publisher
3.7 Abbreviations and symbols
AE Application Entity
AL Application Layer
ALME Application Layer Management Entity
ALP Application Layer Protocol
APO Application Object
– 16 – 61158-5-4 © IEC:2007(E)
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
CR Communication Relationship
CREP Communication Relationship End Point
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
DNS Domain Name Service
DP Decentralised Peripherals
FAL Fieldbus Application Layer
FIFO First In First Out
HMI Human-Machine Interface
ID Identifier
IDL Interface Definition Language
IEC International Electrotechnical Commission
Ind Indication
IP Internet Protocol
ISO International Organization for Standardization
LDev Logical Device
LME Layer Management Entity
OSI Open Systems Interconnect
PDev Physical Device
PDU Protocol Data Unit
PL Physical Layer
QoS Quality of Service
REP Route Endpoint
Req Request
Rsp Response
RT Runtime
SAP Service Access Point
SCL Security Level
SDU Service Data Unit
SEM State event matrix
61158-5-4 © IEC:2007(E) – 17 –
SMIB System Management Information Base
SMK System Management Kernel
STD State transition diagram, used to describe object behaviour
VAO Variable Object
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 Management ASE services specified in Clause 5 of
this standard. The service specification defines the services that are provided by the ASE.
3.8.2 General conventions
This standard uses the descriptive conventions given in ISO/IEC 10731.
3.8.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:
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.

– 18 – 61158-5-4 © IEC:2007(E)
(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).
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.

61158-5-4 © IEC:2007(E) – 19 –
3.8.4 Conventions for service definitions
3.8.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.8.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:
“(n)” indicates that the following note "n" contains additional information pertaining to
the parameter and its use.
3.8.4.3 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 an application layer
service user in the same system through the invocation of application layer service
p
...