IEC 61158-3-14:2010

IEC 61158-3-14 ®
Edition 2.0 2010-08
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
Industrial communication networks – Fieldbus specifications –
Part 3-14: Data-link layer service definition – Type 14 elements

Réseaux de communication industriels – Spécifications des bus de terrain –
Partie 3-14: Définition des services de couche liaison de données – Eléments
de Type 14
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form
or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from
either IEC or IEC's member National Committee in the country of the requester.
If you have any questions about IEC copyright or have an enquiry about obtaining additional rights to this publication,
please contact the address below or your local IEC member National Committee for further information.

Droits de reproduction réservés. Sauf indication contraire, aucune partie de cette publication ne peut être reproduite ni
utilisée sous quelque forme que ce soit et par aucun procédé, électronique ou mécanique, y compris la photocopie et les
microfilms, sans l'accord écrit de la CEI ou du Comité national de la CEI du pays du demandeur.
Si vous avez des questions sur le copyright de la CEI ou si vous désirez obtenir des droits supplémentaires sur cette
publication, utilisez les coordonnées ci-après ou contactez le Comité national de la CEI de votre pays de résidence.

IEC Central Office Tel.: +41 22 919 02 11
3, rue de Varembé Fax: +41 22 919 03 00
CH-1211 Geneva 20 info@iec.ch
Switzerland www.iec.ch
About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.

About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigenda or an amendment might have been published.

Useful links:
IEC publications search - www.iec.ch/searchpub Electropedia - www.electropedia.org
The advanced search enables you to find IEC publications The world's leading online dictionary of electronic and
by a variety of criteria (reference number, text, technical electrical terms containing more than 30 000 terms and
committee,…). definitions in English and French, with equivalent terms in
It also gives information on projects, replaced and additional languages. Also known as the International
withdrawn publications. Electrotechnical Vocabulary (IEV) on-line.

IEC Just Published - webstore.iec.ch/justpublished Customer Service Centre - webstore.iec.ch/csc
Stay up to date on all new IEC publications. Just Published If you wish to give us your feedback on this publication
details all new publications released. Available on-line and or need further assistance, please contact the
also once a month by email. Customer Service Centre: csc@iec.ch.

A propos de la CEI
La Commission Electrotechnique Internationale (CEI) est la première organisation mondiale qui élabore et publie des
Normes internationales pour tout ce qui a trait à l'électricité, à l'électronique et aux technologies apparentées.

A propos des publications CEI
Le contenu technique des publications de la CEI est constamment revu. Veuillez vous assurer que vous possédez
l’édition la plus récente, un corrigendum ou amendement peut avoir été publié.

Liens utiles:
Recherche de publications CEI - www.iec.ch/searchpub Electropedia - www.electropedia.org
La recherche avancée vous permet de trouver des Le premier dictionnaire en ligne au monde de termes
publications CEI en utilisant différents critères (numéro de électroniques et électriques. Il contient plus de 30 000
référence, texte, comité d’études,…). termes et définitions en anglais et en français, ainsi que
Elle donne aussi des informations sur les projets et les les termes équivalents dans les langues additionnelles.
publications remplacées ou retirées. Egalement appelé Vocabulaire Electrotechnique
International (VEI) en ligne.
Just Published CEI - webstore.iec.ch/justpublished
Service Clients - webstore.iec.ch/csc
Restez informé sur les nouvelles publications de la CEI.
Just Published détaille les nouvelles publications parues. Si vous désirez nous donner des commentaires sur
Disponible en ligne et aussi une fois par mois par email. cette publication ou si vous avez des questions
contactez-nous: csc@iec.ch.
IEC 61158-3-14 ®
Edition 2.0 2010-08
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
Industrial communication networks – Fieldbus specifications –

Part 3-14: Data-link layer service definition – Type 14 elements

Réseaux de communication industriels – Spécifications des bus de terrain –

Partie 3-14: Définition des services de couche liaison de données – Eléments

de Type 14
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
PRICE CODE
INTERNATIONALE
CODE PRIX S
ICS 25.04.40; 35.100.20; 35.110 ISBN 978-2-88912-854-9

– 2 – 61158-3-14  IEC:2010
CONTENTS
FOREWORD . 3
INTRODUCTION . 5
1 Scope . 6
1.1 Overview . 6
1.2 Specifications . 6
1.3 Conformance . 6
2 Normative references . 7
3 Terms, definitions, symbols, abbreviations and conventions . 7
3.1 Reference model terms and definitions . 7
3.2 Service convention terms and definitions . 9
3.3 Data-link service terms and definitions . 10
3.4 Symbols and abbreviations . 13
3.5 Common conventions . 15
4 DL service and concept . 16
4.1 General . 16
4.2 Services provided by the DLL . 17
5 DL-management services . 17
5.1 Overview . 17
5.2 Non-periodic data annunciation . 17
5.3 EndofNonPeriodicDataSendingAnnunciation service . 19
5.4 DL-management for FRT applications. 20
Bibliography . 22

Figure 1 – Relationships of DLSAPs, DLSAP-addresses and group DL-addresses . 11
Figure 2 – Communication model . 16
Figure 3 – Sequence of non-periodic data annunciation service and end of non-
periodic data annunciation service . 18

Table 1 – Non-periodic data annunciation primitives and parameters . 18
Table 2 – EndofNonPeriodicDataSending service primitives and parameters . 19
Table 3 – DL-management service primitives and parameters. 20

61158-3-14  IEC:2010 – 3 –
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
INDUSTRIAL COMMUNICATION NETWORKS –
FIELDBUS SPECIFICATIONS –
Part 3-14: Data-link layer service definition –
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 of their respective intellectual-property-right holders.
International Standard IEC 61158-3-14 has been prepared 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:
• Provide stability date for the publication;

– 4 – 61158-3-14  IEC:2010
• Update the edition of IEC 61588;
• Update the Normative references and Bibliography;
• Update the value of Protocol type in subclause 5.3.2;
• Correct the edit error;
• specification changes for CPF3;
• update of the requirements for all conformance classes;
• update of the requirements for all conformance services.
This bilingual version published in 2012-01 corresponds to the English version published in
2010-08.
The text of this standard is based on the following documents:
FDIS Report on voting
65C/604/FDIS 65C/618/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.
The French version has not been voted upon.
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-3-14  IEC:2010 – 5 –
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.
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 data-link layer service defined in this standard is a conceptual architectural service,
independent of administrative and implementation divisions.

– 6 – 61158-3-14  IEC:2010
INDUSTRIAL COMMUNICATION NETWORKS –
FIELDBUS SPECIFICATIONS –
Part 3-14: Data-link layer service definition –
Type 14 elements
1 Scope
1.1 Overview
This part of IEC 61158 provides common elements for basic time-critical messaging
communications between devices 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
14 fieldbus data-link layer in terms of
a) the primitive actions and events of the service;
b) the parameters associated with each primitive action and event, and the form which they
take; and
c) the interrelationship between these actions and events, and their valid sequences.
The purpose of this standard is to define the services provided to
• the Type 14 fieldbus application layer at the boundary between the application and data-
link layers of the fieldbus reference model, and
• systems management at the boundary between the data-link layer and systems
management of the fieldbus reference model.
1.2 Specifications
The principal objective of this standard is to specify the characteristics of conceptual data-link
layer services suitable for time-critical communications, and thus supplement the OSI Basic
Reference Model in guiding the development of data-link protocols for time-critical
communications. A secondary objective is to provide migration paths from previously-existing
industrial communications protocols.
This specification may be used as the basis for formal DL-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 do they constrain
the implementations of data-link entities within industrial automation systems.
There is no conformance of equipment to this data-link layer service definition standard.
Instead, conformance is achieved through implementation of the corresponding data-link
protocol that fulfills the Type 14 data-link layer services defined in this standard.

61158-3-14  IEC:2010 – 7 –
2 Normative references
The following referenced documents are indispensable for the application of this standard. For
dated references, only the edition cited applies. For undated references, the latest edition of
the referenced document (including any amendments) applies.
IEC 61588:2009, Precision clock synchronization protocol for networked measurement and
control system
ISO/IEC 7498-1, Information technology – Open Systems Interconnection – Basic Reference
Model – Basic Reference Model: The Basic Model
ISO/IEC 7498-3, Information technology – Open Systems Interconnection – Basic Reference
Model – Basic Reference Model: Naming and addressing
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 10731, Information technology – Open Systems Interconnection – Basic Reference
Model – Conventions for the definition of OSI services
IETF RFC 768, User Datagram Protocol, available at
IETF RFC 791, Internet protocol, available at
IETF RFC 793, Transmission Control Protocol, available at
3 Terms, definitions, symbols, abbreviations and conventions
For the purposes of this document, the following terms, definitions, symbols, abbreviations
and conventions apply.
3.1 Reference model terms and definitions
This standard is based in part on the concepts developed in ISO/IEC 7498-1 and
ISO/IEC 7498-3, and makes use of the following terms defined therein:
3.1.1 DL-address [ISO/IEC 7498-3]
3.1.2 DL-address-mapping [ISO/IEC 7498-1]
3.1.3 called-DL-address [ISO/IEC 7498-3]
3.1.4 calling-DL-address [ISO/IEC 7498-3]
3.1.5 centralized multi-end-point-connection [ISO/IEC 7498-1]
3.1.6 DL-connection [ISO/IEC 7498-1]
3.1.7 DL-connection-end-point [ISO/IEC 7498-1]
3.1.8 DL-connection-end-point-identifier [ISO/IEC 7498-1]
3.1.9 DL-connection-mode transmission [ISO/IEC 7498-1]

– 8 – 61158-3-14  IEC:2010
3.1.10 DL-connectionless-mode transmission [ISO/IEC 7498-1]
3.1.11 correspondent (N)-entities [ISO/IEC 7498-1]
correspondent DL-entities  (N=2)
correspondent Ph-entities  (N=1)
3.1.12 DL-duplex-transmission [ISO/IEC 7498-1]
3.1.13 (N)-entity [ISO/IEC 7498-1]
DL-entity  (N=2)
Ph-entity  (N=1)
3.1.14 DL-facility [ISO/IEC 7498-1]
3.1.15 flow control [ISO/IEC 7498-1]
3.1.16 (N)-layer [ISO/IEC 7498-1]
DL-layer  (N=2)
Ph-layer  (N=1)
3.1.17 layer-management [ISO/IEC 7498-1]
3.1.18 DL-local-view [ISO/IEC 7498-3]
3.1.19 DL-name [ISO/IEC 7498-3]
3.1.20 naming-(addressing)-domain [ISO/IEC 7498-3]
3.1.21 peer-entities [ISO/IEC 7498-1]
3.1.22 primitive name [ISO/IEC 7498-3]
3.1.23 DL-protocol [ISO/IEC 7498-1]
3.1.24 DL-protocol-connection-identifier [ISO/IEC 7498-1]
3.1.25 DL-protocol-data-unit [ISO/IEC 7498-1]
3.1.26 DL-relay [ISO/IEC 7498-1]
3.1.27 Reset [ISO/IEC 7498-1]
3.1.28 responding-DL-address [ISO/IEC 7498-3]
3.1.29 routing
[ISO/IEC 7498-1]
3.1.30 segmenting [ISO/IEC 7498-1]
3.1.31 (N)-service [ISO/IEC 7498-1]
DL-service  (N=2)
Ph-service  (N=1)
3.1.32 (N)-service-access-point [ISO/IEC 7498-1]
DL-service-access-point  (N=2)
Ph-service-access-point  (N=1)
3.1.33 DL-service-access-point-address [ISO/IEC 7498-3]
3.1.34 DL-service-connection-identifier [ISO/IEC 7498-1]
3.1.35 DL-service-data-unit [ISO/IEC 7498-1]
3.1.36 DL-simplex-transmission [ISO/IEC 7498-1]

61158-3-14  IEC:2010 – 9 –
3.1.37 DL-subsystem [ISO/IEC 7498-1]
3.1.38 Systems-management [ISO/IEC 7498-1]
3.1.39 DLS-user-data [ISO/IEC 7498-1]
3.2 Service convention terms and definitions
This standard also makes use of the following terms defined in ISO/IEC 10731 as they apply
to the data-link layer:
3.2.1 acceptor
3.2.2 asymmetrical service
3.2.3 confirm (primitive);
requestor.deliver (primitive)
3.2.4 deliver (primitive)
3.2.5 DL-confirmed-facility
3.2.6 DL-facility
3.2.7 DL-local-view
3.2.8 DL-mandatory-facility
3.2.9 DL-non-confirmed-facility
3.2.10 DL-provider-initiated-facility
3.2.11 DL-provider-optional-facility
3.2.12 DL-service-primitive;
primitive
3.2.13 DL-service-provider
3.2.14 DL-service-user
3.2.15 DLS-user-optional-facility
3.2.16 indication (primitive);
acceptor.deliver (primitive)
3.2.17 multi-peer
3.2.18 request (primitive);
requestor.submit (primitive)
3.2.19 requestor
3.2.20 response (primitive);
acceptor.submit (primitive)
3.2.21 submit (primitive)
3.2.22 symmetrical service
– 10 – 61158-3-14  IEC:2010
3.3 Data-link service terms and definitions
3.3.1
communication macrocycle
set of basic cycles needed for a configured communication activity in a macro network
segment
3.3.2
communication phase
elapsed fraction of a cycle, measured from some fixed origin
3.3.3
communication scheduling
algorithms and operation for data transfers occurring in a deterministic and repeatable
manner
3.3.4
cyclic
repetitive in a regular manner
3.3.5
data DLPDU
DLPDU that carries a DLSDU from a local DLS-user to a remote DLS-user
3.3.6
destination FB Instance
FB instance that receives the specified parameters
3.3.7
DL-segment, link, local link
single DL-subnetwork in which any of the connected DLEs may communicate directly, without
any intervening DL-relaying, whenever all of those DLEs that are participating in an instance
of communication are simultaneously attentive to the DL-subnetwork during the period(s) of
attempted communication
3.3.8
DLSAP
distinctive point at which DL-services are provided by a single DL-entity to a single higher-
layer entity
NOTE This definition, derived from ISO/IEC 7498-1, is repeated here to facilitate understanding of the critical
distinction between DLSAPs and their DL-addresses.

61158-3-14  IEC:2010 – 11 –
NOTE 1 DLSAPs and PhSAPs are depicted as ovals spanning the boundary between two adjacent layers.
NOTE 2 DL-addresses are depicted as designating small gaps (points of access) in the DLL portion of a DLSAP.
NOTE 3 A single DL-entity may have multiple DLSAP-addresses and group DL-addresses associated with a
single DLSAP.
Figure 1 – Relationships of DLSAPs, DLSAP-addresses and group DL-addresses
3.3.9
DL(SAP)-address
either an individual DLSAP-address, designating a single DLSAP of a single DLS-user, or a
group DL-address potentially designating multiple DLSAPs, each of a single DLS-user
NOTE This terminology is chosen because ISO/IEC 7498-3 does not permit the use of the term DLSAP-address
to designate more than a single DLSAP at a single DLS-user.
3.3.10
(individual) DLSAP-address
DL-address that designates only one DLSAP within the extended link
NOTE A single DL-entity may have multiple DLSAP-addresses associated with a single DLSAP.
3.3.11
extended link
DL-subnetwork, consisting of the maximal set of links interconnected by DL-relays, sharing a
single DL-name (DL-address) space, in which any of the connected DL-entities may
communicate, one with another, either directly or with the assistance of one or more of those
intervening DL-relay entities
NOTE An extended link may be composed of just a single link.
3.3.12
FCS error
error that occurs when the computed frame check sequence value after reception of all the
octets in a DLPDU does not match the expected residual

– 12 – 61158-3-14  IEC:2010
3.3.13
frame
denigrated synonym for DLPDU
3.3.14
group DL-address
DL-address that potentially designates more than one DLSAP within the extended link. A
single DL-entity may have multiple group DL-addresses associated with a single DLSAP. A
single DL-entity also may have a single group DL-address associated with more than one
DLSAP
3.3.15
micro segment
part of a network where special scheduling is implemented
3.3.16
multipoint connection
connection from one node to many nodes
NOTE Multipoint connections allow data transfer from a single publisher to be received by many subscriber
nodes.
3.3.17
node
single DL-entity as it appears on one local link
3.3.18
offset
number of octets from a specially designated position
3.3.19
real-time
ability of a system to provide a required result in a bounded time
3.3.20
real-time communication
transfer of data in real-time
3.3.21
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.11.
3.3.22
receiving DLS-user
DL-service user that acts as a recipient of DLS-user-data
NOTE A DL-service user can be concurrently both a sending and receiving DLS-user.
3.3.23
schedule
temporal arrangement of a number of related operations
3.3.24
scheduling macrocycle
time interval to implement a specific schedule

61158-3-14  IEC:2010 – 13 –
3.3.25
sending DLS-user
DL-service user that acts as a source of DLS-user-data
3.3.26
time offset
time difference from a specially designated time
3.4 Symbols and abbreviations
.cnf Confirm primitive
.ind Indication primitive
.req Request primitive
.rsp Response primitive
ARP Address resolution protocol
Cnf Confirmation
CSMA/CD Carrier sense multiple access protocol with collision detection
DHCP Dynamic host configuration protocol
DL- Data-link layer (as a prefix)
DLC DL-connection
DLCEP DL-connection-end-point
DLE DL-entity (the local active instance of the data-link layer)
DLL DL-layer
DLPCI DL-protocol-control-information
DLPDU DL-protocol-data-unit
DLM DL-management
DLME DL-management entity (the local active instance of DL-management)
DLMS DL-management Service
DLS DL-service
DLSAP DL-service-access-point
DLSDU DL-service-data-unit
ECSME Type 14 communication scheduling management entity

– 14 – 61158-3-14  IEC:2010
EM_ (as a prefix) Type 14 management
FIFO First-in first-out (queuing method)
FRT Fast Real-time
Ind Indication
IP Internet protocol
LLC Logical link control
LMP Link management protocol
MAC Medium access control
MAU Medium attachment unit
OSI Open Systems Interconnection
PAD Pad (bits)
PDU Protocol data unit
Ph- Physical layer (as a prefix)
PhE Ph-entity (the local active instance of the physical layer)
PhL Ph-layer
QoS Quality of service
Req Request
Rsp Response
RTE Real-time Ethernet
RT-Ethernet Real-time Ethernet
SAP Service access point
SDU Service data unit
SME System management entity
SNTP Simple network time protocol
TCP Transmission control protocol
UDP User datagram protocol
61158-3-14  IEC:2010 – 15 –
3.5 Common conventions
This standard uses the descriptive conventions given in ISO/IEC 10731.
The service model, service primitives, and time-sequence diagrams used are entirely abstract
descriptions; they do not represent a specification for implementation.
Service primitives, used to represent service user/service provider interactions (see
ISO/IEC 10731), convey parameters that indicate information available in the user/provider
interaction.
This standard uses a tabular format to describe the component parameters of the DLS
primitives. The parameters that apply to each group of DLS primitives are set out in tables
throughout the remainder of this standard. Each table consists of up to six columns,
containing the name of the service parameter, and a column each for those primitives and
parameter-transfer directions used by the DLS:
– the request primitive’s input parameters;
– the request primitive’s output parameters;
– the indication primitive’s output parameters;
– the response primitive’s input parameters; and
– the confirm primitive’s output parameters.
NOTE The request, indication, response and confirm primitives are also known as requestor.submit,
acceptor.deliver, acceptor.submit, and requestor.deliver primitives, respectively (see ISO/IEC 10731).
One parameter (or part of it) is listed in each row of each table. Under the appropriate service
primitive columns, a code is used to specify the type of usage of the parameter on the
primitive and parameter direction specified in the column:
M – parameter is mandatory for the primitive.
U – parameter is a User option, and may or may not be provided depending
on the dynamic usage of the DLS-user. When not provided, a default
value for the parameter is assumed.
C – parameter is conditional upon other parameters or upon the environment
of the DLS-user.
(blank) – parameter is never present.
Some entries are further qualified by items in brackets. These may be
a) a parameter-specific constraint
(=) indicates that the parameter is semantically equivalent to the parameter in the
service primitive to its immediate left in the table;
b) an indication that some note applies to the entry
(n) indicates that the following note n contains additional information pertaining to the
parameter and its use.
In any particular interface, not all parameters need be explicitly stated. Some may be
implicitly associated with the DLSAP at which the primitive is issued.

– 16 – 61158-3-14  IEC:2010
In the diagrams which illustrate these interfaces, dashed lines indicate cause-and-effect or
time-sequence relationships, and wavy lines indicate that events are roughly
contemporaneous.
4 DL service and concept
4.1 General
4.1.1 DLL architecture
The type 14 DLL is modeled in Figure 2 as an integrated data-link layer with UDP(TCP), IP,
MAC and LLC sublayers defined in ISO/IEC 8802-3 and an extension protocol defined in the
Type 14 parts of the IEC 61158 series, where
a) the Transfer Control Protocol (TCP) defined in RFC 793 is applied;
b) the User Datagram Protocol (UDP) defined in RFC 768 is applied;
c) the Internet Protocol (IP) defined in RFC 791 is applied;
d) the Logic Link Control (LLC) protocol defined in ISO/IEC 8802-3 is applied;
e) the Medium Access Control (MAC) layer protocol defined in ISO/IEC 8802-3 is applied.
Regular ISO/IEC 8802-3
Application layer
FRT applications
RT applications
based applications
RFC 768(UDP)/RFC 793 (TCP)
RFC 791 (IP)
Data link layer
DLL extension sublayer
LLC/MAC defined in ISO/IEC 8802-3
Physical layer
ISO/IEC 8802-3 PhL
Figure 2 – Communication model
Additionally, a DLL extension sublayer is defined as the Type 14 Communication Scheduling
Management Entity (ECSME) on ISO/IEC 8802-3 data-link protocol to manage the
deterministic communication and regular communication.
This ECSME provides the following functions:
• transparent data transferring between DLE and DLS_User specified in ISO/IEC 8802-3
without modifying the data;
• receiving DLS_User DATA from DLS_User and buffering them;
• transferring DLS_User DATA to DLE in configured order and priority. The DLE will send it
to Ethernet network using the protocols defined in ISO/IEC 8802-3;
• transferring decoded DLPDU from DLE to DLS_User.
ECSME supports two ways of communication scheduling:
• free competitive communication scheduling based on the CSMA/CD;
• deterministic communication based on the time-sharing scheduling policy defined later.
When the former scheduling is used, ECSME shall directly transfer the data between DLE and
DLS_User without any buffering or handling.

61158-3-14  IEC:2010 – 17 –
When the letter k) is used, the ECSME in each Type 14 device shall transfer DLS_User DATA
to DLE according to the pre-configured timing order and priority, the DLE shall process the
data and send it to PhL, so that the collision is avoided.
ECSME is the extension based on LLC defined in ISO/IEC 8802-3. For normal applications, it
transfers data between DLS_User and LLC without any changing. For FRT applications, it will
insert the optional DL-management tag in DLPDU to implement time-sharing scheduling policy.
ECSME does not alter the services provided by DLL to DLS_User defined in ISO/IEC 8802-3
as well as the interface between PhL and MAC. It only provides the transmission management
of the DLS_User data.
4.1.2 Transaction between DLL and PhL
The transactions between DLL and PhL defined in ISO/IEC 8802-3 are applied without any
changes.
4.2 Services provided by the DLL
The DLL provides connectionless data transfer services and connection-mode data transfer
services defined in ISO/IEC 8802-3, RFC 768, RFC 791 and RFC 793 protocols.
For time synchronization, the services defined in IEC 61588:2009 apply.
For deterministic communication, additional services for scheduling management are defined
based on ISO/IEC 8802-3.
5 DL-management services
5.1 Overview
This subclause defines the constraints on the sequence in which the primitives defined in this
clause may occur. The constraints determine the order in which primitives occur, but do not
fully specify when they may occur. Other aspects of actual system operation, such as PhL
problems affecting messages in transit, will affect the ability of a DLS-user or a DLS provider
to issue a primitive at any particular time.
5.2 Non-periodic data annunciation
5.2.1 General
This service is defined for a Type 14 device to broadcast all other devices if it has non-
periodic data to be sent at the non-periodic data transferring phase.
When a Type 14 device has non-periodic data (such as alert, alarm, domain download/upload)
to be sent, it shall broadcast the request primitive to all other nodes in the local micro-
segment.
The sequence of primitive of this service is shown in Figure 3.

– 18 – 61158-3-14  IEC:2010
Receiver
Sender
Request
Indication
DLPDU
Figure 3 – Sequence of non-periodic data annunciation service and end of non-periodic
data annunciation service
5.2.2 Primitives and parameters
Table 1 indicates the primitives and parameters of the non-periodic data annunciation service.
Table 1 – Non-periodic data annunciation primitives and parameters
Parameter name .req .ind
Argument
TYPE M M(=)
IP Header M M(=)
UDP Header M M(=)
NPMA_TAG M M(=)
PRI M M(=)
PAD M M(=)
CRC M M(=)
TYPE
Protocol type, the length of this field is two octets. Its value is 0x88CB.
IP Header
IP header, the length of this field is 20 octets referring to RFC 791, Internet Protocol (IP).
UDP Header
UDP header, the length of this field is 8 octets referring to RFC 768, User Datagram Protocol
(UDP).
NPMA_TAG
NonPeriodicDataAnnunciation PDU identifier, the length of this field is one octet. Its value is
0x20.
PRI
61158-3-14  IEC:2010 – 19 –
Priority, the length of this field is one octet, the value of this field indicates the priority of the
next non-periodic packet, if the value of this field is equal to 0xFF, it is illustrated that no non-
periodic packet needs to be transmitted.
PAD
Pad octets, the length of this field is 44 octets, all values of this field are set to 0x20.
CRC
Cyclic Redundancy Check value, the length is 4 octets.
5.3 EndofNonPeriodicDataSendingAnnunciation service
5.3.1 General
This service is defined for a Type 14 device to broadcast all other devices that the local non-
periodic data has been sent and other devices can have the chance to access the network at
the non-periodic data transferring phase.
The sequence of primitive of this service is shown in Figure 3.
5.3.2 Primitives and parameters
Table 2 indicates the primitives and parameters of the EndofNonPeriodicDataSending service.
Table 2 – EndofNonPeriodicDataSending service primitives and parameters
Parameter name .req .ind
Argument
TYPE M M(=)
IP Header M M(=)
UDP Header M M(=)
ENPMTA_TAG M M(=)
PRI M M(=)
PAD M M(=)
CRC M M(=)
TYPE
Protocol type, the length of this field is two octets. Its value is 0x88CB.
IP Header
IP header, the length of this field is 20 octets referring to RFC 791, Internet Protocol (IP).
UDP Header
UDP header, the length of this field is 8 octets referring to RFC 768, User Datagram Protocol
(UDP).
ENPMTA_TAG
– 20 – 61158-3-14  IEC:2010
EndofNonPeriodicDataSending PDU identifier, the length of this field is one octet. Its value is
0x21.
PRI
Priority, the length of this field is one octet, indicating the priority of the unsent non-periodic
packet. The value of 0xFF indicates that no non-periodic packet needs to be transmitted.
PAD
Pad octets, the length of this field is 44 octets, all values of this field are set to 0x20.
CRC
Cyclic Redundancy Check value, the length is 4 octets.
5.4 DL-management for FRT applications
5.4.1 General
For a Type 14 device which is used for FRT applications,
EndofNonperiodicdataSendingAnnunciation service can be omitted. “Non-periodic data
annunciation” can work by using an octet (PRI) in periodic packets instead of an independent
packet. In that case, the device which can send the Nonperiodicdata is managed by the
master device or other DL-management devices.
5.4.2 Primitives and parameters
Table 3 indicates the primitives and parameters of the DL-management service for FRT
applications.
Table 3 – DL-management service primitives and parameters
Parameter name .req .ind
Argument
PRI M M(=)
IND M M(=)
Reserved M M(=)
Timestamp M M(=)
PRI
Priority, the length of this field is one octet. The value of this field indicates the priority of the
next non-periodic packet, if the value of this field is equal to 0xFF, it means that no non-
periodic packet needs to be transmitted.
IND
Indicate, the length of this field is one octet. The value of this field indicates the device which
is allowed by the master device to send non-periodic packets.
Reserved
Reserved, the length of this field is two octets, all values of this field are set to 0x20. This
field is reserved.
61158-3-14  IEC:2010 – 21 –
Timestamp
Timestamp, the length of this field is eight octets. The value of this field indicates the
timestamp of last DL-management service is sent.

– 22 – 61158-3-14  IEC:2010
Bibliography
IEC/TR 61158-1, Industrial communication networks – Fieldbus specifications – Part 1:
Overview and guidance for the IEC 61158 and IEC 61784 series
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
IEC 61158-6-14, Industrial communication networks – Fieldbus specifications – Part 6-14:
Application layer protocol specification – Type 14 elements
ISO/IEC 646, Information technology – ISO 7-bit coded character set for information
interchange
ISO/IEC 2375, Information technology – Procedure for registration of escape sequences and
coded character sets
ISO/IEC 8824-1, Information technology – Abstract Syntax Notation One (ASN.1):
Specification of basic notation
IETF RFC 792, Internet Control Message Protocol, available at
IETF RFC 826, An Ethernet Address Resolution Protocol, available at
IETF RFC 919, Broadcasting Internet Datagrams, available at
IETF RFC 922, Broadcasting Internet Datagrams In the Presence of Subnets, available at

IETF RFC 959, File Transfer Protocol (FTP), available at
IETF RFC 1112, Host Extensions for IP Multicasting, available at
IETF RFC 1157, A Simple Network Management Protocol (SNMP, available at
)
IETF RFC 1533, DHCP Options and BOOTP Vendor Extensions, available at

IETF RFC 1541, Dynamic Host Configuration Protocol (DHCP), available at

IETF RFC 2030, Simple Network Time Protocol (SNTP) Version 4 for IPv4, IPv6 and OSI,
available at

____________
– 24 – 61158-3-14  CEI:2010
SOMMAIRE
AVANT-PROPOS . 25
INTRODUCTION . 27
1 Domaine d'application . 28
1.1 Vue d'ensemble . 28
1.2 Spécifications . 28
1.3 Conformité . 29
2 Références normatives . 29
3 Termes, définitions, symboles, abréviations et conventions .
...