IEC 61158-5-7:2007

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

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
XH
ICS 35.100.70; 25.040.40 ISBN 2-8318-9455-7

– 2 – 61158-5-7 © IEC:2007(E)
CONTENTS
FOREWORD.1H7
INTRODUCTION.2H9
1 Scope.3H10
1.1 Overview .4H10
1.2 Specifications.5H11
1.3 Conformance.6H11
2 Normative references .7H11
3 Terms, definitions, symbols, abbreviations and conventions .8H12
3.1 ISO/IEC 7498-1 terms .9H12
3.2 ISO/IEC 8822 terms .10H12
3.3 ISO/IEC 9545 terms .11H12
3.4 ISO/IEC 8824 terms .12H12
3.5 Fieldbus data-link layer terms.13H12
3.6 Fieldbus application layer specific definitions .14H14
3.7 Abbreviations and symbols.15H21
3.8 Conventions .16H22
4 Concepts .17H26
5 Data type ASE.18H26
5.1 Overview .19H26
5.2 Formal definition of data type objects .20H26
5.3 FAL defined data types.21H26
6 Communication model specification.22H28
6.1 Concepts.23H28
6.2 ASEs.24H45
6.3 ARs .25H215
Bibliography.26H236

Figure 1 – Organisation of the ASEs and ARs.27H29
Figure 2 – Object model of the MPS ASE.28H49
Figure 3 – Time-out evaluation net.29H61
Figure 4 – Asynchronous promptness status evaluation net .30H65
Figure 5 – Synchronous promptness status evaluation net.31H66
Figure 6 – Punctual promptness status evaluation net .32H68
Figure 7 – Asynchronous refreshment status evaluation net.33H71
Figure 8 – Synchronous refreshment status evaluation net .34H72
Figure 9 – Punctual refreshment status evaluation net .35H74
Figure 10 – A_Readloc service procedure.36H77
Figure 11 – A_Writeloc service procedure.37H79
Figure 12 – A_Update service procedure .38H81
Figure 13 – A_Readfar service procedure .39H83
Figure 14 – A_Writefar service procedure .40H85
Figure 15 – A_Sent service procedure .41H86
Figure 16 – A_Received service procedure .42H87
Figure 17 – A_Read service procedure .43H89

61158-5-7 © IEC:2007(E) – 3 –
Figure 18 – A_Read service state machine .44H90
Figure 19 – A_Write service procedure .45H91
Figure 20 – A_Write service state machine .46H92
Figure 21 – Model of a resynchronised variable .47H95
Figure 22 – Principles for resynchronisation of a produced variable .48H96
Figure 23 – Resynchronisation mechanism state machine for a produced variable.49H98
Figure 24 – Asynchronous refreshment private mechanism evaluation net .50H99
Figure 25 – Asynchronous refreshment public mechanism evaluation net .51H100
Figure 26 – Synchronous refreshment private mechanism evaluation net.52H101
Figure 27 – Synchronous refreshment public mechanism evaluation net .53H102
Figure 28 – Punctual refreshment private mechanism evaluation net .54H103
Figure 29 – Punctual refreshment public mechanism evaluation net.55H104
Figure 30 – Principles for the resynchronisation of a consumed variable.56H105
Figure 31 – Resynchronisation mechanism state machine for consumed variable .57H107
Figure 32 – Asynchronous promptness public mechanism evaluation net.58H108
Figure 33 – Asynchronous promptness private mechanism evaluation net .59H109
Figure 34 – Synchronous promptness public mechanism evaluation net .60H110
Figure 35 – Synchronous promptness private mechanism evaluation net .61H111
Figure 36 – Punctual promptness public mechanism evaluation net .62H113
Figure 37 – Punctual promptness private mechanism evaluation net.63H114
Figure 38 – Spatial consistency list variables interchange mechanism .64H116
Figure 39 – Spatial consistency – consistency variable interchange mechanism .65H117
Figure 40 – Spatial consistency – list recovery mechanism .66H117
Figure 41 – Spatial consistency – validity of the spatial consistency status .67H118
Figure 42 – Object model of a variable list .68H118
Figure 43 – A_Readlist service procedure.69H124
Figure 44 – Consistency variable value evaluation net .70H130
Figure 45 – Consistency interchange timing diagram .71H131
Figure 46 – Recovery mechanism evaluation net .72H132
Figure 47 – Recovery interchange timing diagram.73H132
Figure 48 – Flowchart of the sub-MMS environment management state .74H138
Figure 49 – Domain management state chart .75H169
Figure 50 – Domain upload flowchart .76H171
Figure 51 – Domain download sequence diagram .77H172
Figure 52 – Domain upload sequence diagram .78H172
Figure 53 – Program invocation state chart.79H185
Figure 54 – A_Associate service procedure .80H224
Figure 55 – A_Release service procedure.81H227
Figure 56 – A_Abort service procedure .82H228
Figure 57 – A_Data service procedure .83H230
Figure 58 – A_Unidata service procedure .84H233
Figure 59 – Associated mode service state chart .85H234
Figure 60 – Non-associated mode service state chart .86H235

– 4 – 61158-5-7 © IEC:2007(E)
Table 1 – Binary time coding.87H27
Table 2 – Access protection.88H44
Table 3 – Binary time coding.89H60
Table 4 – Asynchronous promptness events and actions .90H65
Table 5 – Synchronous promptness events and actions .91H66
Table 6 – Punctual promptness events and actions.92H68
Table 7 – Asynchronous refreshment events and actions.93H71
Table 8 – Synchronous refreshment events and actions.94H72
Table 9 – Punctual refreshment events and actions .95H75
Table 10 – A_Readloc service parameters .96H76
Table 11 – A_Writeloc service parameters .97H78
Table 12 – A_Update service parameters .98H80
Table 13 – A_Readfar service parameters .99H82
Table 14 – A_Writefar service parameters .100H84
Table 15 – A_Sent service parameters .101H86
Table 16 – A_Received service parameters .102H87
Table 17 – A_Read service parameters .103H88
Table 18 – A_Write service parameters .104H90
Table 19 – Asynchronous refreshment private mechanism events and actions.105H99
Table 20 – Asynchronous refreshment public mechanism events and actions .106H100
Table 21 – Synchronous refreshment private mechanism events and actions.107H101
Table 22 – Synchronous refreshment public mechanism events and actions .108H102
Table 23 – Punctual refreshment private mechanism events and actions .109H104
Table 24 – Punctual refreshment public mechanism events and actions.110H105
Table 25 – Asynchronous promptness public mechanism events and actions.111H108
Table 26 – Asynchronous promptness private mechanism events and actions .112H109
Table 27 – Synchronous promptness public mechanism events and actions .113H110
Table 28 – Synchronous promptness privatemechanism events and actions .114H112
Table 29 – Punctual promptness public mechanism events and actions .115H113
Table 30 – Punctual promptness privatemechanism events and actions.116H114
Table 31 – A_Readlist service parameters .117H123
Table 32 – Confirmed initiate service parameters.118H143
Table 33 – Detailed structure of the extension calling parameter .119H144
Table 34 – Detailed structure of the init request detail parameter.120H145
Table 35 – Detailed structure of the extension called parameter .121H146
Table 36 – Detailed structure of the init request detail parameter.122H147
Table 37 – Conclude service parameter .123H148
Table 38 – Unconfirmed abort service parameters .124H150
Table 39 – Unconfirmed reject service parameters.125H151
Table 40 – Confirmed status service parameters .126H153
Table 41 – Unconfirmed unsollicited status service parameter .127H154
Table 42 – Confirmed identify service parameters.128H154

61158-5-7 © IEC:2007(E) – 5 –
Table 43 – Confirmed get name list service paramaters .129H155
Table 44 – Access group attribute description for domain object .130H158
Table 45 – Access rights attribute description for domain object .131H158
Table 46 – Confirmed delete domain service parameters .132H159
Table 47 – Confirmed initate download sequence service parameters.133H160
Table 48 – Confirmed download segment service parameters.134H161
Table 49 – Confirmed terminate download sequence service parameters.135H162
Table 50 – Confirmed initiate upload sequence service parameters .136H164
Table 51 – Confirmed upload segment service parameters .137H165
Table 52 – Confirmed terminate upload sequence service parameters .138H166
Table 53 – Confirmed get domain attributes service parameters .139H167
Table 54 – Access group attribute details for program invocation object .140H174
Table 55 – Access rights attribute details for program invocation object.141H175
Table 56 – Confirmed create program invocation service parameters.142H176
Table 57 – Confirmed delete program invocation service parameters.143H178
Table 58 – Confirmed start service parameters .144H179
Table 59 – Confirmed stop service parameters .145H180
Table 60 – Confirmed resume service parameters .146H181
Table 61 – Confirmed reset service parameters .147H182
Table 62 – Confirmed kill service parameters.148H183
Table 63 – Access group attribute details for variable object.149H187
Table 64 – Access rights attribute details for variable object .150H188
Table 65 – Access group attribute details for variable list object .151H189
Table 66 – Access right attribute details for variable list objects .152H189
Table 67 – Confirmed read service parameters .153H190
Table 68 – Confirmed write service parameters .154H192
Table 69 – Unconfirmed information report service parameters.155H193
Table 70 – Confirmed define variable-list service parameters .156H194
Table 71 – Confirmed delete variable-list service parameters .157H196
Table 72 – Confirmed get variable access attributes service parameters .158H197
Table 73 – Confirmed get variable-list attributes service parameters.159H198
Table 74 – Data type specification .160H200
Table 75 – Variable access specification .161H201
Table 76 – Variable access description attribute details .162H201
Table 77 – Path selection parameters .163H202
Table 78 – Access group attribute detail for event object .164H205
Table 79 – Access rights attribute details for event object.165H206
Table 80 – Unconfirmed event notification service parameters.166H207
Table 81 – Event type parameter details .167H207
Table 82 – Confirmed acknowledged event notification service parameter .168H209
Table 83 – Confirmed alter event condition monitoring service parameters .169H210
Table 84 – Confirmed get alarm summary service parameters .170H212
Table 85 – Confirmed get event condition attributes service parameters .171H214

– 6 – 61158-5-7 © IEC:2007(E)
Table 86 – Classification of service quality parameters .172H217
Table 87 – Identification parameters .173H221
Table 88 – List of MCS AR ASE services .174H222
Table 89 – A_Associate service parameters.175H222
Table 90 – A_Release service parameters .176H227
Table 91 – A_Abort service parameters .177H228
Table 92 – A_Data service parameters .178H229
Table 93 – A_Unidata service parameters.179H230

61158-5-7 © IEC:2007(E) – 7 –
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
INDUSTRIAL COMMUNICATION NETWORKS –
FIELDBUS SPECIFICATIONS –
Part 5-7: Application Layer Service definition – Type 7 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-7 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 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, …

– 8 – 61158-5-7 © IEC:2007(E)
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 0Hhttp://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-7 © IEC:2007(E) – 9 –
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.

– 10 – 61158-5-7 © IEC:2007(E)
INDUSTRIAL COMMUNICATION NETWORKS –
FIELDBUS SPECIFICATIONS –
Part 5-7: Application Layer Service definition – Type 7 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. 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 7
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.

61158-5-7 © IEC:2007(E) – 11 –
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 7 application layer services as defined in this standard.
2 Normative references
The following referenced documents are indispensable for the application of this document.
For dated references, only the edition cited applies. For undated references, the latest edition
of the referenced document (including any amendments) applies.
IEC 60559, Binary Floating-point Arithmetic for Microprocessor Systems
IEC/TR 61158-1 (Ed.2.0), Industrial communication networks – Fieldbus specifications – Part
1: Overview and guidance for the IEC 61158 and IEC 61784 series
IEC 61158-3-7, Industrial communication networks – Fieldbus specifications – Part 3-7: Data-
link layer service definition – Type 7 elements
IEC 61158-4-7, Industrial communication networks – Fieldbus specifications – Part 4-7: Data-
link layer protocol specification – Type 7 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
ISO/IEC 8824, Information Technology – Abstract Syntax notation One (ASN-1): Specification
of basic notation
– 12 – 61158-5-7 © IEC:2007(E)
ISO/IEC 9545, Information technology – Open Systems Interconnection – Application Layer
structure
ISO/IEC 10731, Information technology – Open Systems Interconnection – Basic Reference
Model – Conventions for the definition of OSI services
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
For the purposes of this document, the following terms as defined in ISO/IEC 7498-1 apply:
a) application entity
b) application process
c) application protocol data unit
d) application service element
e) application entity invocation
f) application process invocation
g) application transaction
h) real open system
i) transfer syntax
3.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 Fieldbus data-link layer terms
The following terms as defined in IEC 61158-3-7 and IEC 61158-4-7 apply.
a) acknowledgement response DLPDU
b) basic cycle
c) basic transaction
61158-5-7 © IEC:2007(E) – 13 –
d) bus-arbitrator (BA)
e) control field
f) destination address
e) DL-segment, loca l link
g) DLCEP-identifier
h) DLCEP-iedentifier DLPDU
i) end of message transaction indication DLPDU
j) identified variable (or simply « variable »)
k) invalid DLCEP-identifier
l) macrocycle
m) message DLPDU identifier
n) message response DLPDU
o) periodic scanning of variables
p) published identified varaible
q) request response DLPDU
r) source address
s) subscribed identified variable
t) triggered message scanning
u) triggered periodic scanning of messages
w) triggered periodic scanning of variables
x) triggered scanning of variables
y) turnaround time
z) variable response DLPDU
The following symbols and abbreviations as defined in IEC 61158-3-7 and IEC 61158-4-7
apply.
a) BA
b) B_Dat_cons
c) B_Dat_Prod
d) B_Req1/2
e) ID_DAT
f) ID_MSG
g) ID_RQ1/2
h) PRT
i) Q_IDMSG
j) Q_IDRQ1/2
k) Q_Msg_Aper
l) Q_Req1/2
m) Q_RPRQ
n) RQ_Inhibit
o) RP_ACK
p) RP_DAT
q) RP_DAT_MSG
– 14 – 61158-5-7 © IEC:2007(E)
r) RP_DAT_RQ1/2
s) RP_DAT_RQ1/2_MSG
t) RP_MSG_ACK
u) RP_MSG_NOACK
v) RP_NAK
w) RP_END
x) STT
y) TI
3.6 Fieldbus application layer specific definitions
For the purposes of this standard, the following terms and definitions apply.
3.6.1
access protection
limitation of the usage of an application object to one client
3.6.2
active connection control object
instance of a certain FAL class that abstracts the interconnection facility (as Consumer and
Provider) of an automation device
3.6.3
address assignment table
mapping of the client's internal I/O-Data object storage to the decentralised input and output
data objects
3.6.4
allocate
take a resource from a common area and assign that resource for the exclusive use of a
specific entity
3.6.5
application
function or data structure for which data is consumed or produced
3.6.6
application layer interoperability
capability of application entities to perform coordinated and cooperative operations using the
services of the FAL
3.6.7
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.8
application process
part of a distributed application on a network, which is located on one device and
unambiguously addressed
3.6.9
application process identifier
distinguishes multiple application processes used in a device

61158-5-7 © IEC:2007(E) – 15 –
3.6.10
application process object
component of an application process that is identifiable and accessible through an FAL
application relationship
NOTE  Application process object definitions are composed of a set of values for the attributes of their class (see
the definition for Application Process Object Class Definition). Application process object definitions may be
accessed remotely using the services of the FAL Object Management ASE. FAL Object Management services can
be used to load or update object definitions, to read object definitions, and to dynamically create and delete
application objects and their corresponding definitions.
3.6.11
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.12
application relationship
cooperative association between two or more application-entity-invocations for the purpose of
exchange of information and coordination of their joint operation
NOTE  This relationship is activated either by the exchange of application-protocol-data-units or as a result of
preconfiguration activities.
3.6.13
application relationship application service element
application-service-element that provides the exclusive means for establishing and
terminating all application relationships
3.6.14
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.15
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.16
behaviour
indication of how an object responds to particular eventss
3.6.17
bit-no
designates the number of a bit in a bitstring or an octet
3.6.18
channel
single physical or logical link of an input or output application object of a server to the process
3.6.19
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.

– 16 – 61158-5-7 © IEC:2007(E)
3.6.20
class attributes
attribute that is shared by all objects within the same class
3.6.21
class code
unique identifier assigned to each object class
3.6.22
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.23
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.24
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.25
configuration identifier
representation of a portion of I/O Data of a single input- and/or output-module of a server
3.6.26
connection
logical binding between application objects that may be within the same or different devices
NOTE 1 Connections may be
...