IEC 61158-6-14:2010

IEC 61158-6-14 ®
Edition 2.0 2010-08
INTERNATIONAL
STANDARD
Industrial communication networks – Fieldbus specifications –
Part 6-14: Application layer protocol specification – Type 14 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: 0Hinmail@iec.ch
Web: 1Hwww.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: 2Hwww.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: 3Hwww.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: 4Hwww.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: 5Hwww.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: 6Hcsc@iec.ch
Tel.: +41 22 919 02 11
Fax: +41 22 919 03 00
IEC 61158-6-14 ®
Edition 2.0 2010-08
INTERNATIONAL
STANDARD
Industrial communication networks – Fieldbus specifications –
Part 6-14: Application layer protocol specification – Type 14 elements

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
XC
ICS 25.04.40; 35.100.70; 35.110 ISBN 978-2-88912-130-4
– 2 – 61158-6-14 © IEC:2010(E)
CONTENTS
FOREWORD.1H7
INTRODUCTION.2H9
1 Scope.3H10
1.1 General .4H10
1.2 Specifications.5H10
1.3 Conformance.6H11
2 Normative references .7H11
3 Terms, definitions, symbols, abbreviations and conventions .8H11
3.1 Referenced terms and definitions .9H11
3.2 Fieldbus application layer specific terms and definitions.10H13
3.3 Abbreviations and symbols.11H16
3.4 Conventions .12H17
4 Abstract syntax.13H18
4.1 Fixed format PDU description .14H18
4.2 Object definitions in FAL management ASE.15H26
4.3 Definition of objects used in Type 14 application access entity .16H33
5 Transfer syntax .17H36
5.1 Encodingof basic data types.18H36
5.2 Encoding of Type 14 APDU header .19H43
5.3 Encoding of FAL management entity service parameters.20H43
5.4 Encoding of AAE Services.21H49
6 Structure of FAL protocol state machines .22H55
7 AP-Context state machine .23H56
7.1 Primitives exchanged between ALU and ALE .24H56
7.2 Protocol state machine descriptions .25H56
7.3 State transitions .26H57
7.4 Function descriptions .27H63
8 FAL management state machines.28H63
8.1 Primitives .29H63
8.2 Protocol state machine descriptions .30H65
8.3 State transitions .31H65
8.4 Function descriptions .32H67
9 Application access entity protocol machine.33H71
9.1 Primitives .34H71
9.2 AAE state machine .35H73
9.3 Event ASE protocol machine .36H76
9.4 Domain ASE protocol machine .37H77
10 Application relationship state machine.38H81
10.1 Primitives .39H81
10.2 AREP state description.40H82
10.3 State transitions .41H83
10.4 Function descriptions .42H84
11 DLL mapping protocol machine .43H84
11.1 Concept .44H84
11.2 Primitives .45H84

61158-6-14 © IEC:2010(E) – 3 –
11.3 State description .46H85
11.4 State transitions .47H85
11.5 Function description .48H86
Bibliography.49H87

Figure 1 – State transition diagram .50H17
Figure 2 – Exchanged primitives of protocol state machine .51H56
Figure 3 – ACE protocol state machine .52H57
Figure 4 – FME protocol state machine.53H65
Figure 5 – AAE state transition diagrams .54H73
Figure 6 – Event ASE state transition diagrams .55H76
Figure 7 – Domain ASE state transition diagram .56H78
Figure 8 – AREP state transition diagrams.57H83
Figure 9 – ESME state transition.58H85

Table 1 – State machine description elements .59H18
Table 2 – Definition of Type 14 MOB header object .60H26
Table 3 – Definition of Type 14 device descriptor object .61H26
Table 4 – Definition of the time synchronization object.62H27
Table 5 – Definition of maximum response time object.63H28
Table 6 – Definition of the Type 14 communication scheduling management object .64H28
Table 7 – Definition of the device application information object .65H28
Table 8 – Definition of FB application information header.66H29
Table 9 – Definition of domain application information header.67H29
Table 10 – Definition of Type 14 link object header.68H30
Table 11 – Definition of Type 14 FRT link object header .69H30
Table 12 – Definition of FB application information object .70H31
Table 13 – Definition of Type 14 link object .71H31
Table 14 – Definition of Type 14 FRT link object.72H32
Table 15 – Definition of domain application information object .73H33
Table 16 – Definition of domain object .74H33
Table 17 – Definition of simple variable object .75H34
Table 18 – Definition of event object .76H34
Table 19 – Definition of Type 14 socket mapping object.77H35
Table 20 – Definition of Type 14 socket timer object .78H35
Table 21 – Definition of ErrorType object .79H36
Table 22 – Encoding of Boolean value TRUE.80H36
Table 23 – Encoding of Boolean value FALSE .81H36
Table 24 – Encoding of Unsigned8 data type .82H37
Table 25 – Encoding of Unsigned16 data type .83H37
Table 26 – Encoding of Unsigned32 data type .84H37
Table 27 – Encoding of Unsigned64 data type .85H38
Table 28 – Encoding of Int8 data type.86H38

– 4 – 61158-6-14 © IEC:2010(E)
Table 29 – Encoding of Int16 data type.87H38
Table 30 – Encoding of Int32 data type.88H39
Table 31 – Encoding of Int64 data type.89H39
Table 32 – Encoding of Real type .90H39
Table 33 – Encoding of VisibleString data type .91H40
Table 34 – Encoding of OctetString data type .92H40
Table 35 – Encoding of BitString data type .93H40
Table 36 – Encoding of TimeOfDay data type .94H41
Table 37 – Encoding of BinaryDate data type .95H42
Table 38 – Encoding of PrecisionTimeDifference data type.96H42
Table 39 – Encoding of Type 14 application layer service message header .97H43
Table 40 – Encoding of EM_DetectingDevice request parameters.98H43
Table 41 – Encoding of EM_OnlineReply request parameters .99H44
Table 42 – Encoding of EM_GetDeviceAttribute request parameters.100H44
Table 43 – Encoding of EM_GetDeviceAttribute positive response parameters .101H44
Table 44 – Encoding of EM_GetDeviceAttribute negative response parameters .102H45
Table 45 – Encoding of EM_ActiveNotification request parameters .103H46
Table 46 – Encoding of EM_ConfiguringDevice request parameters.104H47
Table 47 – Encoding of EM_ConfiguringDevice positive response parameters .105H48
Table 48 – Encoding of EM_ConfiguringDevice negative response parameters.106H48
Table 49 – Encoding of EM_SetDefaultValue request parameters.107H48
Table 50 – Encoding of EM_SetDefaultValue positive response parameters .108H48
Table 51 – Encoding of clear device attribute service refuse packet.109H49
Table 52 – Encoding of DomainDownload request parameters.110H49
Table 53 – Encoding of domain download service response packet .111H49
Table 54 – Encoding of DomainDownload negative response parameters .112H49
Table 55 – Encoding of DomainUpload request parameters .113H50
Table 56 – Encoding of DomainUpload positive response parameters.114H50
Table 57 – Encoding of DomainUpload negative response parameters .115H50
Table 58 – Encoding of EventRoport request parameters.116H51
Table 59 – Encoding of EventRoportAcknowledge request parameters .117H51
Table 60 – Encoding of EventRoportAcknowledge positive response parameters.118H51
Table 61 – Encoding of EventRoportAcknowledge negative response parameters .119H51
Table 62 – Encoding of ReportConditionChanging request parameters .120H52
Table 63 – Encoding of ReportConditionChanging positive response parameters .121H52
Table 64 – Encoding of ReportConditionChanging negative response parameters .122H52
Table 65 – Encoding of Read request parameters.123H52
Table 66 – Encoding of Read positive response parameters .124H53
Table 67 – Encoding of Read negative response parameters .125H53
Table 68 – Encoding of Write request parameters.126H53
Table 69 – Encoding of Write positive response parameters .127H53
Table 70 – Encoding of Write negative response parameters .128H54
Table 71 – Encoding of VariableDistribute request parameters .129H54

61158-6-14 © IEC:2010(E) – 5 –
Table 72 – Encoding of FRTRead request parameters .130H54
Table 73 – Encoding of FRTRead positive response parameters.131H54
Table 74 – Encoding of FRTRead negative response parameters .132H54
Table 75 – Encoding of FRTWrite request parameters .133H55
Table 76 – Encoding of FRTWrite positive response parameters.134H55
Table 77 – Encoding of FRTWrite negative response parameters .135H55
Table 78 – Encoding of FRTVariableDistribute request parameters.136H55
Table 79 – Primitives delivered by ALU to ALE .137H56
Table 80 – Primitives delivered by ALE to ALU .138H56
Table 81 – ACE state descriptions .139H57
Table 82 – ACE state transitions (sender).140H57
Table 83 – ACE state transitions (receiver) .141H60
Table 84 – APServiceType() descriptions.142H63
Table 85 – Primitives delivered by application layer user to FME .143H63
Table 86 – Primitives delivered by FME to application layer user .144H64
Table 87 – Primitive parameters exchanged between FME and application layer user .145H64
Table 88 – Primitives delivered by FME to ESME.146H64
Table 89 – Primitives delivered by ESME to FME.147H64
Table 90 – Primitives parameters exchanged between FME and ESME .148H65
Table 91 – State transitions of Type 14 FME.149H66
Table 92 – RcvNewIpAddress() descriptions .150H68
Table 93 – Attribute_Set() descriptions .151H68
Table 94 – RestoreDefaults() descriptions .152H68
Table 95 – NewAddress() descriptions.153H68
Table 96 – Restart_Type 14RepeatTimer() descriptions.154H68
Table 97 – Clear_DuplicatePdTagFlag() descriptions.155H69
Table 98 – Type 14RepeatTimerExpire() descriptions .156H69
Table 99 – Send_EM_ReqRspMessage() descriptions .157H69
Table 100 – Send_EM_CommonErrorRsp() descriptions.158H69
Table 101 – SntpSyncLost() descriptions .159H70
Table 102 – IPAddressCollision() descriptions .160H70
Table 103 – RecvMsg() descriptions .161H70
Table 104 – QueryMatch() descriptions.162H70
Table 105 – MessageIDMatch() descriptions.163H70
Table 106 – DevId_Match() descriptions .164H71
Table 107 – PdTag_Match() descriptions .165H71
Table 108 – Set_Attribute_Data() descriptions .166H71
Table 109 – Set_DuplicatePdTagFlag() descriptions .167H71
Table 110 – Primitives issued by ALU to AAE .168H72
Table 111 – Primitives issued by AAE to ALU .169H72
Table 112 – Primitives parameters exchanged between AAE and ALU.170H72
Table 113 – Primitives issued by AAE to ESME .171H72
Table 114 – Primitives issued by ESME to AAE .172H73

– 6 – 61158-6-14 © IEC:2010(E)
Table 115 – Primitive parameters exchanged between AAE and ESME .173H73
Table 116 – AAE state descriptions .174H73
Table 117 – AAE state transitions (sender) .175H74
Table 118 – AAE state transitions (receiver) .176H75
Table 119 – ServiceType() descriptions .177H75
Table 120 – State value of event management.178H76
Table 121 – Event ASE state transition table .179H77
Table 122 – Domain state value.180H77
Table 123 – Domain ASE state transition table .181H78
Table 124 – Domain_DownloadSucceed() description.182H80
Table 125 – Domain_WriteBuffer() description .183H81
Table 126 – IncreamentInvokeDomainCounter() description .184H81
Table 127 – DecreamentInvokeDomainCounter() description .185H81
Table 128 – Primitives issued by FME(or AAE) to AREP.186H81
Table 129 – Primitives issued by AREP to FME(or AAE).187H82
Table 130 – Primitives parameters exchanged between AREP and FME(or AAE) .188H82
Table 131 – Primitives issued by AREP to ESME.189H82
Table 132 – Primitives issued by ESME to AREP.190H82
Table 133 – Primitive parameters exchanged between AREP and ESME .191H82
Table 134 – AREP state descriptions .192H83
Table 135 – AREP state transitions.193H83
Table 136 – AREPType() descriptions.194H84
Table 137 – ServiceType() descriptions .195H84
Table 138 – The primitives exchanged between transport layer and ESME .196H85
Table 139 – Primitives parameters exchanged between Transport Layer and ESME .197H85
Table 140 – ESME state description .198H85
Table 141 – ECFME state transitions .199H86
Table 142 – ServiceType()description .200H86

61158-6-14 © IEC:2010(E) – 7 –
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
INDUSTRIAL COMMUNICATION NETWORKS –
FIELDBUS SPECIFICATIONS –
Part 6-14: Application layer protocol specification –
Type 14 elements
FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote
international co-operation on all questions concerning standardization in the electrical and electronic fields. To
this end and in addition to other activities, IEC publishes International Standards, Technical Specifications,
Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC
Publication(s)”). Their preparation is entrusted to technical committees; any IEC National Committee interested
in the subject dealt with may participate in this preparatory work. International, governmental and non-
governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely
with the International Organization for Standardization (ISO) in accordance with conditions determined by
agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all
interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence
between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in
the latter.
5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any
services carried out by independent certification bodies.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees for any personal injury, property damage or
other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and
expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC
Publications.
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of
patent rights. IEC shall not be held responsible for identifying any or all such patent rights.
NOTE 1 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 profile parts. Use of the various protocol types in other
combinations may require permission from their respective intellectual-property-right holders.
International Standard IEC 61158-6-14 has been prred by subcommittee 65C: Industrial
networks, of IEC technical committee 65: Industrial-process measurement, control and
automation.
This second edition cancels and replaces the first edition published in 2007. This edition
constitutes a technical revision.
The main changes with respect to the previous edition are listed below:
• update the Normative references and Bibliography;
• corrections of editorial errors;

– 8 – 61158-6-14 © IEC:2010(E)
• specification changes for CPF3;
• update of the requirements for all conformance classes;
• update of the requirements for all conformance services.
The text of this standard is based on the following documents:
FDIS Report on voting
65C/607/FDIS 65C/621/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.
A list of all parts of the IEC 61158 series, published under the general title Industrial
communication networks – Fieldbus specifications, can be found on the IEC web site.
The committee has decided that the contents of this publication will remain unchanged until
the stability date indicated on the IEC web site under "http://webstore.iec.ch" in the data
related to the specific publication. At this date, the publication will be:
• reconfirmed;
• withdrawn;
• replaced by a revised edition, or
• amended.
NOTE 2 The revision of this standard will be synchronized with the other parts of the IEC 61158 series.

61158-6-14 © IEC:2010(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 protocol provides the application service by making use of the services
available from the data-link or other immediately lower layer. The primary aim of this standard
is to provide a set of rules for communication expressed in terms of the procedures to be
carried out by peer application entities (AEs) at the time of communication. These rules for
communication are intended to provide a sound basis for development in order to serve a
variety of purposes:
• as a guide for implementors and designers;
• for use in the testing and procurement of equipment;
• as part of an agreement for the admittance of systems into the open systems environment;
• as a refinement to the understanding of time-critical communications within OSI.
This standard is concerned, in particular, with the communication and interworking of sensors,
effectors and other automation devices. By using this standard together with other standards
positioned within the OSI or fieldbus reference models, otherwise incompatible systems may
work together in any combination.

– 10 – 61158-6-14 © IEC:2010(E)
INDUSTRIAL COMMUNICATION NETWORKS –
FIELDBUS SPECIFICATIONS –
Part 6-14: Application layer protocol specification –
Type 14 elements
1 Scope
1.1 General
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 14 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 specifies interactions between remote applications and defines the externally
visible behavior provided by the Type 14 fieldbus application layer in terms of
a) the formal abstract syntax defining the application layer protocol data units conveyed
between communicating application entities;
b) the transfer syntax defining encoding rules that are applied to the application layer
protocol data units;
c) the application context state machine defining the application service behavior visible
between communicating application entities;
d) the application relationship state machines defining the communication behavior visible
between communicating application entities.
The purpose of this standard is to define the protocol provided to
a) define the wire-representation of the service primitives defined in IEC 61158-5-14, and
b) define the externally visible behavior associated with their transfer.
This standard specifies the protocol of the Type 14 fieldbus application layer, in conformance
with the OSI Basic Reference Model (ISO/IEC 7498) and the OSI application layer structure
(ISO/IEC 9545).
1.2 Specifications
The principal objective of this standard is to specify the syntax and behavior of the application
layer protocol that conveys the application layer services defined in IEC 61158-5-14.
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
protocols standardized in the IEC 61158-6 series.

61158-6-14 © IEC:2010(E) – 11 –
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.
Conformance is achieved through implementation of this application layer protocol
specification.
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-14, Industrial communication networks – Fieldbus specifications – Part 3-14:
Data-link layer service definition – Type 14 elements
IEC 61158-4-14, Industrial communication networks – Fieldbus specifications – Part 4-14:
Data-link layer protocol specification – Type 14 elements
IEC 61158-5-14, Industrial communication networks – Fieldbus specifications – Part 5-14:
Application layer service definition – Type 14 elements
ISO/IEC 7498-1, Information technology – Open Systems Interconnection – Basic Reference
Model – Part 1: The Basic Model
ISO/IEC 8802-3, Information technology – Telecommunications and information exchange
between systems – Local and metropolitan area networks – Specific requirements – Part 3:
Carrier sense multiple access with collision detection (CSMA/CD) access method and
physical layer specifications
ISO/IEC 8822, Information technology – Open Systems Interconnection – Presentation
service definition
ISO/IEC 8824-1, Information technology – Abstract Syntax Notation One (ASN.1):
Specification of basic notation
ISO/IEC 9545, Information technology – Open Systems Interconnection – Application Layer
structure
ISO/IEC 10731, Information technology – Open Systems Interconnection – Basic Reference
Model – Conventions for the definition of OSI services
3 Terms, definitions, symbols, abbreviations and conventions
For the purposes of this document, the following terms and definitions apply.
3.1 Referenced terms and definitions
3.1.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
– 12 – 61158-6-14 © IEC:2010(E)
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.1.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.1.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.1.4 ISO/IEC 8824 terms
For the purposes of this document, the following terms as defined in ISO/IEC 8824 apply:
a) object identifier
b) type
3.1.5 Fieldbus data-link Layer terms
For the purposes of this document, the following terms as defined in IEC 61158-3-14 and
IEC 61158-4-14 apply.
a) DL-Time
b) DL-Scheduling-policy
c) DLCEP
d) DLC
e) DL-connection-oriented mode
f) DLPDU
g) DLSDU
h) DLSAP
i) link
j) network address
k) node address
61158-6-14 © IEC:2010(E) – 13 –
l) node
m) scheduled
3.2 Fieldbus application layer specific terms and definitions
3.2.1
access control
control on the reading and writing of an object
3.2.2
access Path
association of a symbolic name with a variable for the purpose of open communication
3.2.3
communication macrocycle
set of basic cycles needed for a configured communication activity in a macro network
segment
3.2.4
communication scheduling
algorithms and operation for data transfers occurring in a deterministic and repeatable
manner
3.2.5
configuration (of a system or device)
step in system design: selecting functional units, assigning their locations and defining their
interconnections.
3.2.6
cyclic
repetitive in a regular manner
3.2.7
destination FB Instance
FB instance that receives the specified parameters
3.2.8
domain
part of memory used to store code or data
3.2.9
domain download
operation to write data in a domain
3.2.10
domain upload
operation to read data from a domain
3.2.11
entity
particular thing, such as a person, place, process, object, concept, association, or event
3.2.12
Type 14 bridge
DL-relay entity which performs synchronization between links (buses) and may perform
selective store-and-forward and routing functions to connect two micro network segments

– 14 – 61158-6-14 © IEC:2010(E)
3.2.13
identifier
16-bit word associated with a system variable
3.2.14
index
address of an object within an application process
3.2.15
instance
actual physical occurrence of an object within a class that identifies one of many objects
within the same object class
3.2.16
instantiation
creation of an instance of a specified type.
3.2.17
management information
network-visible information for the purpose of managing the field system.
3.2.18
management information base
organized list of management information
3.2.19
mapping
set of values having defined correspondence with the quantities or values of another set.
3.2.20
member
piece of an attribute that is structured as an element of an array
3.2.21
message filtering
decision on a message according to a special rule.
3.2.22
micro segment
part of a network, where special scheduling is implemented.
3.2.23
offset
number of octets from a specially designated position.
3.2.24
phase
elapsed fraction of a cycle, measured from some fixed origin
3.2.25
process interface
data exchange and information mapping between physical process and application unit
3.2.26
real-time
ability of a system to provide a required result in a bounded time

61158-6-14 © IEC:2010(E) – 15 –
3.2.27
real-time communication
transfer of data in real-time.
3.2.28
Real-Time Ethernet
RTE
ISO/IEC 8802-3-based network that includes real-time communication
NOTE 1 Other communication can be supported, providing the real-time communication is not compromised.
NOTE 2 This definition is dedicated, but not limited, to ISO/IEC 8802-3. It could be applicable to other IEEE 802
specifications, for example IEEE 802.1Q.
3.2.29
schedule
temporal arrangement of a number of related operations.
3.2.30
scheduling macrocycle
time interval to implement a specific schedule.
3.2.31
source FB Instance
FB instance that sends a specific parameter
3.2.32
time offset
time difference from a specially designated time

– 16 – 61158-6-14 © IEC:2010(E)
3.3 Abbreviations and symbols
Application Access Entity
AAE
Application Entity
AE
Application Layer
AL
Application Layer Entity
ALE
Application Layer Protocol
ALP
Application Object
APO
Application Process
AP
Application Protocol Data Unit
APDU
Application Process Identifier
API
Application Relationship
AR
Address Resolution Protocol
ARP
Application Relationship End Point
AREP
Application Service Element
ASE
Confirmation
Cnf
Communication Relationship
CR
Communication Relationship End Point
...