SIST EN 61158-6-11:2008

SLOVENSKI STANDARD
01-julij-2008
1DGRPHãþD
SIST EN 61158-6:2004
Industrijska komunikacijska omrežja - Specifikacije za procesno vodilo - 6-11. del:
Specifikacija protokola na aplikacijskem nivoju - Elementi tipa 11 (IEC 61158-6-
11:2007)
Industrial communication networks - Fieldbus specifications - Part 6-11: Application layer
protocol specification - Type 11 elements
Industrielle Kommunikationsnetze - Feldbusse - Teil 6-11: Protokollspezifikation des
Application Layer (Anwendungsschicht) - Typ 11-Elemente
Réseaux de communication industriels - Spécifications des bus de terrain - Partie 6-11:
Spécification des services des couches d'application - Eléments de type 11
Ta slovenski standard je istoveten z: EN 61158-6-11:2008
ICS:
25.040.40 Merjenje in krmiljenje Industrial process
industrijskih postopkov measurement and control
35.100.70 Uporabniški sloj Application layer
35.110 Omreževanje Networking
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN STANDARD
EN 61158-6-11
NORME EUROPÉENNE
March 2008
EUROPÄISCHE NORM
ICS 35.100.70; 25.040.40 Partially supersedes EN 61158-6:2004

English version
Industrial communication networks -
Fieldbus specifications -
Part 6-11: Application layer protocol specification -
Type 11 elements
(IEC 61158-6-11:2007)
Réseaux de communication industriels -  Industrielle Kommunikationsnetze -
Spécifications des bus de terrain - Feldbusse -
Partie 6-11: Spécification des services Teil 6-11: Protokollspezifikation
des couches d'application - des Application Layer
Eléments de type 11 (Anwendungsschicht) -
(CEI 61158-6-11:2007) Typ 11-Elemente
(IEC 61158-6-11:2007)
This European Standard was approved by CENELEC on 2008-02-01. CENELEC members are bound to comply
with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European Standard
the status of a national standard without any alteration.

Up-to-date lists and bibliographical references concerning such national standards may be obtained on
application to the Central Secretariat or to any CENELEC member.

This European Standard exists in three official versions (English, French, German). A version in any other
language made by translation under the responsibility of a CENELEC member into its own language and notified
to the Central Secretariat has the same status as the official versions.

CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Cyprus, the
Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia,
Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain,
Sweden, Switzerland and the United Kingdom.

CENELEC
European Committee for Electrotechnical Standardization
Comité Européen de Normalisation Electrotechnique
Europäisches Komitee für Elektrotechnische Normung

Central Secretariat: rue de Stassart 35, B - 1050 Brussels

© 2008 CENELEC - All rights of exploitation in any form and by any means reserved worldwide for CENELEC members.
Ref. No. EN 61158-6-11:2008 E
Foreword
The text of document 65C/476/FDIS, future edition 1 of IEC 61158-6-11, prepared by SC 65C, Industrial
networks, of IEC TC 65, Industrial-process measurement, control and automation, was submitted to the
IEC-CENELEC parallel vote and was approved by CENELEC as EN 61158-6-11 on 2008-02-01.
This and the other parts of the EN 61158-6 series supersede EN 61158-6:2004.
With respect to EN 61158-6:2004 the following changes were made:
– deletion of Type 6 fieldbus for lack of market relevance;
– addition of new fieldbus types;
– partition into multiple parts numbered 6-2, 6-3, …6-20.
The following dates were fixed:
– latest date by which the EN has to be implemented
at national level by publication of an identical
national standard or by endorsement (dop) 2008-11-01
– latest date by which the national standards conflicting
with the EN have to be withdrawn (dow) 2011-02-01
NOTE  Use of some of the associated protocol types is restricted by their intellectual-property-right holders. In all cases, the
commitment to limited release of intellectual-property-rights made by the holders of those rights permits a particular data-link layer
protocol type to be used with physical layer and application layer protocols in type combinations as specified explicitly in the
EN 61784 series. Use of the various protocol types in other combinations may require permission from their respective
intellectual-property-right holders.
IEC and CENELEC draw attention to the fact that it is claimed that compliance with this standard may involve the use of patents as
follows, where the [xx] notation indicates the holder of the patent right:
TOSHIBA has the patent applications listed below:
– US Publication Number 6711131 and its counterpart patents in other countries
– US Publication Number 5414813 and its counterpart patents in other countries
– US Publication Number 4930121 and its counterpart patents in other countries
IEC and CENELEC take no position concerning the evidence, validity and scope of these patent rights.
The holder of these patent rights has assured IEC that he is willing to negotiate licences under reasonable and non-discriminatory
terms and conditions with applicants throughout the world. In this respect, the statements of the holder of these patent rights are
registered with IEC. Information may be obtained from:
Toshiba Corporation
1-1, Shibaura 1-Chome
Minato-ku Tokyo 105-8001, Japan
Attention is drawn to the possibility that some of the elements of this standard may be the subject of patent rights other than those
identified above. IEC and CENELEC shall not be held responsible for identifying any or all such patent rights.
Annex ZA has been added by CENELEC.
__________
- 3 - EN 61158-6-11:2008
Endorsement notice
The text of the International Standard IEC 61158-6-11:2007 was approved by CENELEC as a European
Standard without any modification.
In the official version, for Bibliography, the following notes have to be added for the standards indicated:
IEC 61131-3 NOTE  Harmonized as EN 61131-3:2003 (not modified).
IEC 61158-4-11 NOTE  Harmonized as EN 61158-4-11:2008 (not modified).
ISO/IEC 9506-2 NOTE  Harmonized as EN 29506-2:1993 (not modified).
__________
Annex ZA
(normative)
Normative references to international publications
with their corresponding European publications

The following referenced documents are indispensable for the application of this document. For dated
references, only the edition cited applies. For undated references, the latest edition of the referenced
document (including any amendments) applies.

NOTE  When an international publication has been modified by common modifications, indicated by (mod), the relevant EN/HD
applies.
Publication Year Title EN/HD Year

1) 2)
IEC 60559 - Binary floating-point arithmetic for HD 592 S1 1991
microprocessor systems
1) 2)
IEC 61158-3-11 - Industrial communication networks - EN 61158-3-11 2008
Fieldbus specifications -
Part 3-11: Data-link layer service definition -
Type 11 elements
1) 2)
IEC 61158-5-11 - Industrial communication networks - EN 61158-5-11 2008
Fieldbus specifications -
Part 5-11: Application layer service definition -
Type 11 elements
1) 2)
IEC 61784-2 - Industrial communication networks - Profiles - EN 61784-2 2008
Part 2: Additional fieldbus profiles for real-time
networks based on ISO/IEC 8802-3

1) 2)
ISO/IEC 7498-1 - Information technology - Open Systems EN ISO/IEC 7498-1 1995
Interconnection - Basic Reference Model:
The Basic Model
1)
ISO/IEC 8822 - Information technology - Open Systems - -
Interconnection - Presentation service
definition
1)
ISO/IEC 8824-2 - Information technology - Abstract Syntax - -
Notation One (ASN.1): Information object
specification
1)
ISO/IEC 8825-1 - Information technology - ASN.1 encoding - -
rules: Specification of Basic Encoding Rules
(BER), Canonical Encoding Rules (CER) and
Distinguished Encoding Rules (DER)

1)
ISO/IEC 9545 - Information technology - Open Systems - -
Interconnection - Application Layer structure

1)
Undated reference.
2)
Valid edition at date of issue.

IEC 61158-6-11
Edition 1.0 2007-12
INTERNATIONAL
STANDARD
Industrial communication networks – Fieldbus specifications –
Part 6-11: Application layer protocol specification – Type 11 elements

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
V
ICS 35.100.70; 25.040.40 ISBN 2-8318-9486-7

– 2 – 61158-6-11 © IEC:2007(E)
CONTENTS
FOREWORD.4
INTRODUCTION.6
1 Scope.7
1.1 General .7
1.2 Specifications.8
1.3 Conformance.8
2 Normative references .8
3 Terms, definitions, symbols, abbreviations and conventions .9
3.1 Introduction .9
3.2 Terms and definitions from other ISO/IEC standards .9
3.3 Terms and definitions from IEC/TR 61158-1 .10
3.4 Other terms and definitions .10
3.5 Abbreviations and symbols.11
3.6 Conventions .12
4 FAL syntax description .13
4.1 Concept .13
4.2 General .14
4.3 FAL-AR PDU abstract syntax .14
4.4 Abstract syntax of PDU body.15
4.5 Data type .15
5 Transfer syntax .15
5.1 Overview and FAL header .15
5.2 Encoding rule .16
5.3 Encoding of structured types .18
6 FAL protocol state machines structures .18
6.1 Overview .18
7 FAL service protocol machine (FSPM).19
7.1 General .19
7.2 Primitives definitions .19
7.3 FSPM state tables .20
8 Application relationship protocol machine (ARPM).21
8.1 General .21
8.2 Primitive definitions .21
8.3 DLL mapping of BNU-PEC AREP class .22
8.4 BNU-PEC ARPM states machine.23
9 DLL mapping protocol machine (DMPM).25
9.1 Overview .25
9.2 Primitive definitions .26
9.3 DLL mapping protocol machine (DMPM).27
9.4 Data-link layer service selection .30
Bibliography.31

Figure 1 – RTE-TCnet communication profile.14
Figure 2 – APDU overview .16
Figure 3 – Relationship between FSPM, ARPM, DMPM and external physical CM .19

61158-6-11 © IEC:2007(E) – 3 –
Figure 4 – State transition diagram of FSPM.20
Figure 5 – State transition diagram of the BNU-PEC .23
Figure 6 – State transition diagram of DMPM.27

Table 1 – Conventions used for state machines .12
Table 2 – FAL header .16
Table 3 – Primitives issued by FAL user to FSPM .20
Table 4 – Primitives issued by FSPM to FAL user .20
Table 5 – FSPM state table – sender transactions .20
Table 6 – FSPM state table – receiver transactions .21
Table 7 – Function SelectArep .21
Table 8 – Primitives issued by FSPM to ARPM .22
Table 9 – Primitives issued by ARPM to FSPM .22
Table 10 – Parameters used with primitives exchanged between FSPM and ARPM .22
Table 11 – BNU-PEC state descriptions.23
Table 12 – BNU-PEC ARPM state table – sender transactions.24
Table 13 – BNU-PEC ARPM state table – receiver transactions.24
Table 14 – Function GetArepId ().25
Table 15 – Function BuildFAL-PDU.25
Table 16 – Function FAL_Pdu_Type .25
Table 17 – Primitives issued by ARPM to DMPM .26
Table 18 – Primitives issued by DMPM to ARPM .26
Table 19 – Parameters used with primitives exchanged between ARPM and DMPM .26
Table 20 – Primitives exchanged between data-link layer and DMPM .27
Table 21 – DMPM state descriptions.27
Table 22 – DMPM state table – sender transactions .28
Table 23 – DMPM state table – receiver transactions.29
Table 24 – Function PickArep .29
Table 25 – Function FindAREP .29

– 4 – 61158-6-11 © IEC:2007(E)
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
INDUSTRIAL COMMUNICATION NETWORKS –
FIELDBUS SPECIFICATIONS –
Part 6-11: Application layer protocol specification – Type 11 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.
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.
The International Electrotechnical Commission (IEC) draws attention to the fact that it is claimed that compliance
with this standard may involve the use of patents concerning as follows:
TOSHIBA has the patent applications listed below:
– US Publication Number 6711131 and its counterpart patents in other countries
– US Publication Number 5414813 and its counterpart patents in other countries
– US Publication Number 4930121 and its counterpart patents in other countries
IEC takes no position concerning the evidence, validity and scope of this patent right.
The holder of this patent right has assured the IEC that he is willing to negotiate licences under reasonable and
non-discriminatory terms and conditions with applicants throughout the world. In this respect, the statement of the
holder of this patent right is registered with IEC. Information may be obtained from:

61158-6-11 © IEC:2007(E) – 5 –
Toshiba Corporation
1-1, Shibaura 1-Chome
Minato-ku Tokyo 105-8001, Japan
Attention is drawn to the possibility that some of the elements of this International Standard may be the subject of
patent rights other than those identified above. IEC shall not be held responsible for identifying any or all such
patent rights.
International standard IEC 61158-6-11 has been prepared by subcommittee 65C: Industrial
networks, of IEC technical committee 65: Industrial-process measurement, control and
automation.
This first edition and its companion parts of the IEC 61158-6 subseries cancel and replace
IEC 61158-6:2003. This edition of this part constitutes a technical addition. This part and its
Type 11 companion parts also cancel and replace IEC/PAS 62406, published in 2005.
The text of this standard is based on the following documents:
FDIS Report on voting
65C/476/FDIS 65C/487/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 edition of IEC 61158-6 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 6 of the third edition into multiple parts numbered -6-2, -6-3, …
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-6-11 © 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 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.

61158-6-11 © IEC:2007(E) – 7 –
INDUSTRIAL COMMUNICATION NETWORKS –
FIELDBUS SPECIFICATIONS –
Part 6-11: Application layer protocol specification – Type 11 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 11 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 behavior provided by the
different Types of the fieldbus Application Layer in terms of
a) the abstract syntax defining the application layer protocol data units conveyed between
communicating application entities,
b) the transfer syntax defining the application layer protocol data units conveyed between
communicating application entities,
c) the application context state machine defining the application service behavior visible
between communicating application entities; and
d) the application relationship state machines defining the communication behavior visible
between communicating application entities; and.
The purpose of this standard is to define the protocol provided to
1) define the wire-representation of the service primitives defined in IEC 61158-5-11, and
2) define the externally visible behavior associated with their transfer.
This standard specify the protocol 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

– 8 – 61158-6-11 © 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 syntax and behavior of the application
layer protocol that conveys the application layer services defined in IEC 61158-5-11.
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 parts of the IEC 61158-6 series.
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 the application layer service definition standard.
Instead, 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-11, Industrial communication networks – Fieldbus specifications – Part 3-11:
Data-link layer service definition – Type 11 elements
IEC 61158-5-11, Industrial communication networks – Fieldbus specifications – Part 5-11:
Application layer service definition – Type 11 elements
IEC 61784-2, Industrial communication networks – Profiles – Part 2: Additional fieldbus
profiles for real-time networks based on ISO/IEC 8802-3
ISO/IEC 7498-1, Information technology – Open Systems Interconnection – Basic Reference
Model — Part 1: The Basic Model
ISO/IEC 8822, Information technology – Open Systems Interconnection – Presentation
service definition
ISO/IEC 8824, Information technology – Open Systems Interconnection – Specification of
Abstract Syntax Notation One (ASN.1)
ISO/IEC 8825, Information technology – ASN.1 encoding rules: Specification of Basic
Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules
(DER)
ISO/IEC 9545, Information technology – Open Systems Interconnection – Application Layer
structure
61158-6-11 © IEC:2007(E) – 9 –
3 Terms, definitions, symbols, abbreviations and conventions
3.1 Introduction
For the purposes of this documents, the followings apply.
3.2 Terms and definitions from other ISO/IEC standards
3.2.1 Terms and definitions from ISO/IEC 7498-1
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.2 Terms and definitions from ISO/IEC 8822
a) abstract syntax
b) presentation context
3.2.3 Terms and definitions from ISO/IEC 9545
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.2.4 Terms and definitions from ISO/IEC 8824
a) object identifier
b) type
c) value
d) simple type
e) structured type
f) component type
g) tag
h) Boolean type
i) true
j) false
k) integer type
l) bitstring type
m) octetstring type
n) null type
o) sequence type
p) sequence of type
q) choice type
r) tagged type
s) any type
t) module
u) production
– 10 – 61158-6-11 © IEC:2007(E)
3.2.5 Terms and definitions from ISO/IEC 8825
a) encoding (of a data value)
b) data value
c) identifier octets (the singular form is used in this standard)
d) length octet(s) (both singular and plural forms are used in this standard)
e) contents octets
3.3 Terms and definitions from IEC/TR 61158-1
a) application relationship
b) conveyance path
c) client
d) dedicated AR
e) dynamic AR
f) error class
g) error code
h) name
i) numeric identifier
j) peer
k) pre-defined AR endpoint
l) pre-established AR endpoint
m) publisher
n) subscriber
o) server
3.4 Other terms and definitions
NOTE The following definitions may apply to all the types except if the same item is used with different definitions
in a specific type. In this case the latter has precedence.
The following terms and definitions are used in this series of standards.
3.4.1
called
service user or a service provider that receives an indication primitive or a request APDU
3.4.2
calling
service user or a service provider that initiates a request primitive or a request APDU
3.4.3
common memory
virtual common memory over the Type 11 fieldbus, which is shared with the nodes
participating in the Type 11 fieldbus and is primarily used for the real-time communications by
the TCC data service
3.4.4
interoperability
capability of User Layer entities to perform coordinated and cooperative operations using the
services of the FAL
3.4.5
management information
network accessible information that supports the management of the Fieldbus environment
3.4.6
receiving
service user that receives a confirmed primitive or an unconfirmed primitive, or a service
provider that receives a confirmed APDU or an unconfirmed APDU

61158-6-11 © IEC:2007(E) – 11 –
3.4.7
resource
resource is a processing or information capability of a subsystem
3.4.8
sending
service user that sends a confirmed primitive or an unconfirmed primitive, or a service
provider that sends a confirmed APDU or an unconfirmed APDU
3.5 Abbreviations and symbols
AE Application Entity
AE-I Application Entity Invocation
AL Application Layer
AP Application Process
Ap_ Prefix for Data types defined for AP ASE
Ar_ Prefix for Data types defined for AR ASE
APDU Application Protocol Data Unit
AR Application Relationship
AREP Application Relationship End Point
ASE Application Service Element
ASN.1 Abstract Syntax Notation One
BCD Binary Coded Decimal
BER Basic Encoding Rule
BNU-PEC Buffered Network-Scheduled Uni-directional Pre-Established Connection
CM Common Memory
cnf confirmation primitive
Dl_ Prefix for Data types defined for data-link layer types
DL Data-link
DLC Data-link Connection
DLCEP Data-link Connection End Point
DLPDU Data-link Protocol Data Unit
DLSAP Data-link Service Access Point
DLSDU Data-link Service Data Unit
Dt_ Prefix for Data types defined for Data type ASE
Err Error (used to indicate an APDU type)
Er_ Prefix for Error types defined
Ev_ Prefix for Data types defined for Event ASE
FAL Fieldbus Application Layer
Fi_ Prefix for Data types defined for Function Invocation ASE
FIFO First In First Out
Gn_ Prefix for Data types defined for general use
ID Identifier
IEC International Electrotechnical Commission
in input primitive
ind indication primitive
ISO International Organization for Standardization
LAS Link Active Scheduler
Lr_ Prefix for Data types defined for Load Region ASE
lsb least significant bit
Mn_ Prefix for Data types defined for Management ASE
msb most significant bit
out output primitive
OSI Open Systems Interconnection
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statement
QoS Quality Of Service
Req Request (used to indicate an APDU type)
req request primitive
Rsp Response (used to indicate an APDU type)
rsp response primitive
– 12 – 61158-6-11 © IEC:2007(E)
SAP Service Access Point
SDU Service Data Unit
TCC Time-critical cyclic
ToS Type Of Service
Vr_ Prefix for Data types defined for Variable ASE

3.6 Conventions
3.6.1 Conventions for class definitions
The data-link layer mapping definitions are described using templates. Each template consists
of a list of attributes for the class. The general form of the template is defined in IEC 61158-5.
3.6.2 Abstract syntax conventions
When the "optionalParametersMap" parameter is used, a bit number which corresponds to
each OPTIONAL or DEFAULT production is given as a comment.
3.6.3 Conventions used in state machines
The state machines are described in Table 1.
Table 1 – Conventions used for state machines
Event
# Current state / condition Next state
=> action
Name of this The current Events or conditions that trigger this state transaction. The next state after the
transition state to which actions in this transition
=>
this state is taken
The actions that are taken when the above events or conditions are
transition
met. The actions are always indented below events or conditions
applies
The conventions used in the state machines are as follows:
:= Value of an item on the left is replaced by value of an item on the right. If an item on the right is a parameter, it
comes from the primitive shown as an input event.
xxx A parameter name.
Example:
Identifier := reason
means value of a 'reason' parameter is assigned to a parameter called 'Identifier.'
"xxx" Indicates fixed value.
Example:
Identifier := "abc"
means value "abc" is assigned to a parameter named 'Identifier.'
= A logical condition to indicate an item on the left is equal to an item on the right.
< A logical condition to indicate an item on the left is less than the item on the right.
> A logical condition to indicate an item on the left is greater than the item on the right.
<> A logical condition to indicate an item on the left is not equal to an item on the right.
&& Logical "AND"
|| Logical "OR"
This construct allows the execution of a sequence of actions in a loop within one transition.
The loop is executed for all values from start_value to end_value.

61158-6-11 © IEC:2007(E) – 13 –
Example:
for (Identifier := start_value to end_value)
actions
endfor
This construct allows the execution of alternative actions depending on some condition (which
might be the value of some identifier or the outcome of a previous action) within one transition.
Example:
If (condition)
actions
else
actions
endif
Readers are strongly recommended to refer to the subclauses for the AREP attribute
definitions, the local functions, and the FAL-PDU definitions to understand protocol machines.
It is assumed that readers have sufficient knowledge of these definitions, and they are used
without further explanations.
4 FAL syntax description
4.1 Concept
This standard specifies the Application layer protocol of the Type 11 essential for the
ISO/IEC 8802-3-based Time-critical control network (TCnet), which is one of the
communication networks for the Real-Time Ethernet(RTE) defined in IEC 61784-2 and is
referred to as RTE-TCnet hereafter.
This standard meets the industrial automation market objective of providing predictable time
deterministic and reliable time-critical data transfer and means, which allow co-existence with
non-time-critical data transfer over the ISO/IEC 8802-3 series communications medium, for
support of cooperation and synchronization between automation processes on field devices in
a real-time application system. 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.
This standard specifies the part of the protocol set of the RTE-TCnet communication profile
and/or of one or more communication profiles related to a common family of the RTE-TCnet.
The RTE-TCnet communication profile, shown in Figure 1 as one of the profile sets, is based
on the 7 layer OSI Basic Reference model. For regular ISO/IEC 8802-3 based applications the
upper layers mapped over the data-link layer is in the ordinary way; on the other hand, for
time-critical applications with Common Memory running in parallel, the specific application
layer for RTE-TCnet is specified. The data-link layer for RTE-TCnet has the extension, but is
compliant to the ISO/IEC 8802-3 MAC protocol in order to provide both services for time-
critical communications and common memory applications respectively.

– 14 – 61158-6-11 © IEC:2007(E)
Time-critical applications
Regular ISO/IEC 8802-3-based
with common memory
applications
TELNET, FTP, HTTP Common memory
Application layer
OPC XML-DA etc
Transport layer RFC 768(UDP)
RFC 793 (TCP)
null
Network layer
RFC 791 (IP)
ISO/IEC 8802-3
Data Link layer
Specific scheduling extension
Physical layer
ISO/IEC 8802-3 (Redundant)
Figure 1 – RTE-TCnet communication profile
This standard specifies the data-link protocol as the essential parts of the RTE-TCnet profile,
which are the extension part of the ISO/IEC 8802-3 based data-link layer and the Application
layer exploiting the services of the data-link layer immediately below, in terms of the “three-
layer” Fieldbus Reference Model which is based in part on the OSI Basic Reference Model.
Other part of the RTE-TCnet profile is not in the scope of this document.
4.1.1 Field of applications
In industrial control systems, several kinds of field devices such as drives, sensors and
actuators, programmable controllers, distributed control systems and human-machine
interface devices are required to be connected with control networks. The process control
data and the state data is transferred among these field devices in the system and the
communications between these field devices requires simplicity in application programming
and to be executed with adequate response time. In most industrial automation systems such
as food, water, sewage, paper and steel, including a rolling mill, the control network is
required to provide time-critical response capability for their application, as required in
ISO/TR 13283 for time-critical communications architectures.
Plant production may be compromised due to errors, which could be introduced to the control
system if the network does not provide a time-critical response. Therefore the following
characteristics are required for a time-critical control network.
– A deterministic response time between the control device nodes.
– Ability to share process data seamlessly across the control system.
The RTE-TCnet is applicable to such industrial
...