IEC 61158-3-3:2014

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

Réseaux de communication industriels – Spécifications des bus de terrain –
Partie 3-3: Définition des services de la couche liaison de données – Éléments
de type 3
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 l'IEC ou du Comité national de l'IEC du pays du demandeur. Si vous avez des
questions sur le copyright de l'IEC 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 l'IEC 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.

IEC Catalogue - webstore.iec.ch/catalogue Electropedia - www.electropedia.org
The stand-alone application for consulting the entire The world's leading online dictionary of electronic and
bibliographical information on IEC International Standards, electrical terms containing more than 30 000 terms and
Technical Specifications, Technical Reports and other definitions in English and French, with equivalent terms in 14
documents. Available for PC, Mac OS, Android Tablets and additional languages. Also known as the International
iPad. Electrotechnical Vocabulary (IEV) online.

IEC publications search - www.iec.ch/searchpub IEC Glossary - std.iec.ch/glossary
The advanced search enables to find IEC publications by a More than 55 000 electrotechnical terminology entries in
variety of criteria (reference number, text, technical English and French extracted from the Terms and Definitions
committee,…). It also gives information on projects, replaced clause of IEC publications issued since 2002. Some entries
and withdrawn publications. have been collected from earlier publications of IEC TC 37,

77, 86 and CISPR.
IEC Just Published - webstore.iec.ch/justpublished
Stay up to date on all new IEC publications. Just Published IEC Customer Service Centre - webstore.iec.ch/csc
details all new publications released. Available online and If you wish to give us your feedback on this publication or
also once a month by email. need further assistance, please contact the Customer Service
Centre: csc@iec.ch.
A propos de l'IEC
La Commission Electrotechnique Internationale (IEC) 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 IEC
Le contenu technique des publications IEC est constamment revu. Veuillez vous assurer que vous possédez l’édition la
plus récente, un corrigendum ou amendement peut avoir été publié.

Catalogue IEC - webstore.iec.ch/catalogue Electropedia - www.electropedia.org
Application autonome pour consulter tous les renseignements
Le premier dictionnaire en ligne de termes électroniques et
bibliographiques sur les Normes internationales,
électriques. Il contient plus de 30 000 termes et définitions en
Spécifications techniques, Rapports techniques et autres
anglais et en français, ainsi que les termes équivalents dans
documents de l'IEC. Disponible pour PC, Mac OS, tablettes
14 langues additionnelles. Egalement appelé Vocabulaire
Android et iPad.
Electrotechnique International (IEV) en ligne.

Recherche de publications IEC - www.iec.ch/searchpub
Glossaire IEC - std.iec.ch/glossary
Plus de 55 000 entrées terminologiques électrotechniques, en
La recherche avancée permet de trouver des publications IEC
en utilisant différents critères (numéro de référence, texte, anglais et en français, extraites des articles Termes et
comité d’études,…). Elle donne aussi des informations sur les Définitions des publications IEC parues depuis 2002. Plus
projets et les publications remplacées ou retirées. certaines entrées antérieures extraites des publications des

CE 37, 77, 86 et CISPR de l'IEC.
IEC Just Published - webstore.iec.ch/justpublished

Service Clients - webstore.iec.ch/csc
Restez informé sur les nouvelles publications IEC. Just
Published détaille les nouvelles publications parues. Si vous désirez nous donner des commentaires sur cette
Disponible en ligne et aussi une fois par mois par email. publication ou si vous avez des questions contactez-nous:
csc@iec.ch.
IEC 61158-3-3 ®
Edition 2.0 2014-08
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
Industrial communication networks – Fieldbus specifications –

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

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

Partie 3-3: Définition des services de la couche liaison de données – Éléments

de type 3
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
PRICE CODE
INTERNATIONALE
CODE PRIX XB
ICS 25.040.40; 35.100.20; 35.110 ISBN 978-2-8322-1701-6

– 2 – IEC 61158-3-3:2014 © IEC 2014
CONTENTS
FOREWORD . 5
INTRODUCTION . 7
1 Scope . 8
1.1 General . 8
1.2 Specifications . 8
1.3 Conformance . 9
2 Normative references . 9
3 Terms, definitions, symbols, abbreviations and conventions . 9
3.1 Reference model terms and definitions . 9
3.2 Service convention terms and definitions . 11
3.3 Common data-link service terms and definitions . 12
3.4 Additional Type 3 data-link specific definitions. 13
3.5 Common symbols and abbreviations . 15
3.6 Additional Type 3 symbols and abbreviations . 16
3.7 Common conventions . 18
3.8 Additional Type 3 conventions . 19
4 Connectionless-mode data-link service . 20
4.1 General . 20
4.2 Model of the connectionless-mode data-link service . 20
4.3 Sequence of primitives . 22
4.4 Detailed description of DL services. 25
5 DL-management Service . 44
5.1 General . 44
5.2 Facilities of the DLMS . 44
5.3 Services of the DL-management . 45
5.4 Overview of interactions . 46
5.5 Detailed specification of services and interactions . 48
Bibliography . 68

Figure 1 – Relationships of DLSAPs, DLSAP-addresses and group DL-addresses . 12
Figure 2 – SDA service . 23
Figure 3 – SDN service . 23
Figure 4 – SRD service . 23
Figure 5 – MSRD service . 24
Figure 6 – CS service . 24
Figure 7 – Reset, Set value, Get value, Ident (local), DLSAP status, DLSAP activate,
DLSAP activate responder, DLSAP activate subscriber and DLSAP deactivate services . 47
Figure 8 – Event service . 47
Figure 9 – Ident (remote) service . 48

Table 1 – Summary of DL services and primitives . 22
Table 2 – SDA data ack primitives and parameters . 26
Table 3 – Values of DL_status for the SDA data ack service . 28
Table 4 – SDN data primitives and parameters . 29

Table 5 – Values of DL_status for the SDN data service . 31
Table 6 – SRD data reply primitives and parameters . 32
Table 7 – Values of Update_status for the SRD data reply service . 33
Table 8 – Additional values of DL_status for the SRD data reply service . 34
Table 9 – SRD reply-update primitives and parameters . 34
Table 10 – Values of DL_status for the SRD reply-update service . 36
Table 11 – MSRD MCT data reply primitives and parameters . 37
Table 12 – MSRD DXM data reply primitive and parameters . 39
Table 13 – CS time event primitives and parameters . 41
Table 14 – Values of DL_status for the CS time event service . 42
Table 15 – CS clock value primitives and parameters . 42
Table 16 – Values of CS_status for the CS clock value service . 44
Table 17 – Values of DL_status for the CS clock value service . 44
Table 18 – Summary of DL-management services and primitives . 47
Table 19 – Reset primitives and parameters . 48
Table 20 – Values of DLM_status for the reset service . 48
Table 21 – Set value primitives and parameters . 49
Table 22 – Mandatory DLE-variables . 50
Table 23 – Optional DLE-variables . 50
Table 24 – Permissible values of mandatory DLE-variables . 51
Table 25 – Permissible values of optional DLE-variables . 51
Table 26 – Meaning of the values for the parameter isochronous_mode . 52
Table 27 – Default reaction times and operating parameters for a master station for
asynchronous transmission . 52
Table 28 – Default reaction times and operating parameters for a slave station with
asynchronous transmission . 52
Table 29 – Default reaction times and operating parameters for master stations for
coupling of synchronous and asynchronous transmission segments. 53
Table 30 – Default reaction times and operating parameter for slave stations for
coupling of synchronous and asynchronous transmission segments. 53
Table 31 – Values of DLM_status for the set value service . 53
Table 32 – Get value primitives and parameters . 54
Table 33 – Additional mandatory DLE-variables in master stations . 54
Table 34 – Permissible values of the additional DLE-variables in master stations . 55
Table 35 – Values of DLM_status for the get value service . 55
Table 36 – Event primitive and parameters . 55
Table 37 – Mandatory DLL events and fault types . 56
Table 38 – Permissible values of T . 56
SH
Table 39 – Ident primitives and parameters . 57
Table 40 – Ident_list for the ident service . 57
Table 41 – Values of DLM_status for the ident service (local) . 58
Table 42 – Values of DLM_status for the ident service (remote) . 58
Table 43 – DLSAP status primitives and parameters . 58
Table 44 – Values of DLM_status for the DLSAP status service . 59

– 4 – IEC 61158-3-3:2014 © IEC 2014
Table 45 – DLSAP activate primitives and parameters . 60
Table 46 – DLSAP activate service_list . 60
Table 47 – DLSAP activate DLSDU_length_list (SDA, SDN, SRD, MSRD and CS) . 61
Table 48 – DLSDU lengths of SDA and SDN as used in the DLSAP activate service . 62
Table 49 – DLSDU lengths of SRD and MSRD as used in the (master station) DLSAP
activate service . 62
Table 50 – DLSDU lengths of CS as used in the DLSAP activate service . 62
Table 51 – Values of DLM_status for the DLSAP activate service . 62
Table 52 – DLSAP activate responder primitives and parameters . 63
Table 53 – DLSDU_length_list for the DLSAP activate responder service . 63
Table 54 – DLSDU length of SRD and MSRD as used in the DLSAP activate responder
service . 64
Table 55 – Values of DLM_status for the DLSAP activate responder service . 65
Table 56 – DLSAP activate subscriber primitives and parameters . 65
Table 57 – DLSDU_length_list for the DLSAP activate subscriber service . 66
Table 58 – DLSDU lengths of MSRD as used in the DLSAP activate subscriber service
(master and slave stations) . 66
Table 59 – Values of DLM_status for the DLSAP activate subscriber service . 66
Table 60 – DLSAP deactivate primitives and parameters . 67
Table 61 – Values of DLM_status for the DLSAP deactivate service . 67

INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
INDUSTRIAL COMMUNICATION NETWORKS –
FIELDBUS SPECIFICATIONS –
Part 3-3: Data-link layer service definition –
Type 3 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.
Attention is drawn to the fact that the use of the associated protocol type is restricted by its
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 layer protocol type to
be used with other layer protocols of the same type, or in other type combinations explicitly
authorized by its intellectual-property-right holders.
NOTE Combinations of protocol types are specified in IEC 61784-1 and IEC 61784-2.
International Standard IEC 61158-3-3 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:
– 6 – IEC 61158-3-3:2014 © IEC 2014
– Two notes in definitions modified.
The text of this standard is based on the following documents:
FDIS Report on voting
65C/759/FDIS 65C/769/RVD
Full information on the voting for the approval of this standard can be found in the report on
voting indicated in the above table.
This publication has been drafted in accordance with ISO/IEC Directives, Part 2.
The 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.
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.
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 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.

– 8 – IEC 61158-3-3:2014 © IEC 2014
INDUSTRIAL COMMUNICATION NETWORKS –
FIELDBUS SPECIFICATIONS –
Part 3-3: Data-link layer service definition –
Type 3 elements
1 Scope
1.1 General
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 3
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 3 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 1 data-link layer services defined in this standard.
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and
are indispensable for its application. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any
amendments) applies.
NOTE All parts of the IEC 61158 series, as well as IEC 61784-1 and IEC 61784-2 are maintained simultaneously.
Cross-references to these documents within the text therefore refer to the editions as dated in this list of normative
references.
IEC 61158-1, Industrial communication networks – Fieldbus specifications – Part 1: Overview
and guidance for the IEC 61158 and IEC 61784 series
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: Naming and addressing
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, 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 [7498-3]
3.1.2 DL-address-mapping [7498-1]
3.1.3 called-DL-address [7498-3]
3.1.4 calling-DL-address [7498-3]
3.1.5 centralized multi-end-point-connection [7498-1]
3.1.6 DL-connection [7498-1]
– 10 – IEC 61158-3-3:2014 © IEC 2014
3.1.7 DL-connection-end-point [7498-1]
3.1.8 DL-connection-end-point-identifier [7498-1]
3.1.9 DL-connection-mode transmission [7498-1]
3.1.10 DL-connectionless-mode transmission [7498-1]
3.1.11 correspondent (N)-entities [7498-1]
correspondent DL-entities  (N=2)
correspondent Ph-entities  (N=1)
3.1.12 DL-duplex-transmission [7498-1]
3.1.13 (N)-entity [7498-1]
DL-entity  (N=2)
Ph-entity  (N=1)
3.1.14 DL-facility [7498-1]
3.1.15 flow control [7498-1]
3.1.16 (N)-layer [7498-1]
DL-layer  (N=2)
Ph-layer  (N=1)
3.1.17 layer-management [7498-1]
3.1.18 DL-local-view [7498-3]
3.1.19 DL-name [7498-3]
3.1.20 naming-(addressing)-domain [7498-3]
3.1.21 peer-entities [7498-1]
3.1.22 primitive name [7498-3]
3.1.23 DL-protocol [7498-1]
3.1.24 DL-protocol-connection-identifier [7498-1]
3.1.25 DL-protocol-data-unit [7498-1]
3.1.26 DL-relay
[7498-1]
3.1.27 reset [7498-1]
3.1.28 responding-DL-address [7498-3]
3.1.29 routing [7498-1]
3.1.30 segmenting [7498-1]
3.1.31 (N)-service [7498-1]
DL-service  (N=2)
Ph-service  (N=1)
3.1.32 (N)-service-access-point [7498-1]
DL-service-access-point  (N=2)
Ph-service-access-point  (N=1)
3.1.33 DL-service-access-point-address [7498-3]

3.1.34 DL-service-connection-identifier [7498-1]
3.1.35 DL-service-data-unit [7498-1]
3.1.36 DL-simplex-transmission [7498-1]
3.1.37 DL-subsystem [7498-1]
3.1.38 systems-management [7498-1]
3.1.39 DLS-user-data [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
– 12 – IEC 61158-3-3:2014 © IEC 2014
3.3 Common data-link service terms and definitions
For the purposes of this document, the following terms and definitions apply.
NOTE Many definitions are common to more than one protocol Type; they are not necessarily used by all protocol
Types.
3.3.1
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.2
DLSAP
distinctive point at which DL-services are provided by a single DL-entity to a single higher-
layer entity
Note 1 to entry: This definition, derived from ISO/IEC 7498-1, is repeated here to facilitate understanding of the
critical distinction between DLSAPs and their DL-addresses.

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.3
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 1 to entry: 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.4
(individual) DLSAP-address
DL-address that designates only one DLSAP within the extended link
Note 1 to entry: A single DL-entity may have multiple DLSAP-addresses associated with a single DLSAP.
3.3.5
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 1 to entry: An extended link may be composed of just a single link.
3.3.6
frame
denigrated synonym for DLPDU
3.3.7
group DL-address
DL-address that potentially designates more than one DLSAP within the extended link
Note 1 to entry: A single DL-entity can have multiple group DL-addresses associated with a single DLSAP.
Note 2 to entry: A single DL-entity also can have a single group DL-address associated with more than one
DLSAP.
3.3.8
node
single DL-entity as it appears on one local link
3.3.9
receiving DLS-user
DL-service user that acts as a recipient of DLS-user-data
Note 1 to entry: A DL-service user can be concurrently both a sending and receiving DLS-user.
3.3.10
sending DLS-user
DL-service user that acts as a source of DLS-user-data
3.4 Additional Type 3 data-link specific definitions
For the purposes of this document, the following terms and definitions apply.
3.4.1
acknowledgement DLPDU
reply DLPDU that contains no DLSDU
3.4.2
bit time
time to transmit one bit
– 14 – IEC 61158-3-3:2014 © IEC 2014
3.4.3
clock synchronization
represents a sequence of interactions to synchronize the clocks of all time receivers by a time
master
3.4.4
controller_type
hardware class of the communications entity
3.4.5
data DLPDU
DLPDU that carries a DLSDU from a local DLS-user to a remote DLS-user
3.4.6
DL_status, DLM_status
status that specifies the result of the execution of the associated request
3.4.7
GAP
range of station (DLE) DL-addresses from this station (TS) to its successor (NS) in the logical
token ring, excluding stations above HSA
3.4.8
isochronous mode
special operational mode that implies both a constant (isochronous) cycle with a fixed
schedule of high and low priority messages, and the synchronization of the DLS-users with
this constant (isochronous) cycle
3.4.9
local DLE
DLE in a current master station that initiates the current transaction
3.4.10
local DLS-user
DLS-user that initiates the current service
3.4.11
publisher
transmitter of messages for consumption by subscribers
3.4.12
region/segment address
address extension that identifies a particular fieldbus subnetwork
Note 1 to entry: This supports DL-routing between fieldbuses.
3.4.13
remote DLE
addressed DLE of a service request (that is, the intended receiving DLE of any resulting
request DLPDU)
3.4.14
remote DLS-user
addressed DLS-user of a service request (that is, the intended receiver of any resulting
indication primitive)
3.4.15
reply DLPDU
DLPDU transmitted from a remote DLE to the initiating (local) DLE, and possibly other DLEs
Note 1 to entry: When the remote DLE is a Publisher, the reply DLPDU also can be sent to several remote DLEs.
3.4.16
request DLPDU
DLPDU that carries either a request for data or a DLSDU or both from a local DLS-user to a
remote DLS-user
3.4.17
response DLPDU
reply DLPDU that carries a DLSDU from a remote DLS-user to local DLS-user
3.4.18
station
master or slave device containing a DLE
3.4.19
subscriber
receiver of messages produced by a publisher
3.4.20
time event
message that represents a trigger for a moment of time
3.4.21
time master
device which is able to send clock synchronization messages
Note 1 to entry: Link devices have time master functionality.
3.4.22
time receiver
fieldbus device able to be time synchronized by a time master
3.4.23
token passing
medium access method, in which the right to transmit is passed from master station to master
station in a logical ring
3.5 Common symbols and abbreviations
NOTE Many symbols and abbreviations are common to more than one protocol Type; they are not necessarily
used by all protocol Types.
3.5.1 DL- data-link layer (as a prefix)
3.5.2 DLC DL-connection
3.5.3 DLCEP DL-connection-end-point
3.5.4 DLE DL-entity (the local active instance of the data-link layer)
3.5.5 DLL DL-layer
3.5.6 DLPCI DL-protocol-control-information

– 16 – IEC 61158-3-3:2014 © IEC 2014
3.5.7 DLPDU DL-protocol-data-unit
3.5.8 DLM DL-management
3.5.9 DLME DL-management Entity (the local active instance of
DL-management)
3.5.10 DLMS DL-management Service
3.5.11 DLS DL-service
3.5.12 DLSAP DL-service-access-point
3.5.13 DLSDU DL-service-data-unit
3.5.14 FIFO first-in first-out (queuing method)
3.5.15 OSI open systems interconnection
3.5.16 Ph- physical layer (as a prefix)
3.5.17 PhE Ph-entity (the local active instance of the physical layer)
3.5.18 PhL Ph-layer
3.5.19 QoS quality of service
3.6 Additional Type 3 symbols and abbreviations
3.6.1 ACK acknowledge(ment) DLPDU
3.6.2 cnf confirm primitive
3.6.3 CS clock synchronization
3.6.4 DA destination address of a DLPDU
3.6.5 DAE destination address extension(s) of a DLPDU which conveys
D_SAP_index or destination region/segment address or both
3.6.6 DS DL/DLM_status: Disconnected station, local DL-entity not in logical
token ring or disconnected from line
3.6.7 D_SAP destination service access point, the DLSAP which identifies the
remote DLS-user.
3.6.8 D_SAP_index destination service access point index, that component of a DLSAP-
address which designates a DLSAP and remote DLS-user within the
remote DLE
3.6.9 DXM data exchange multicast
3.6.10 EXT address extension bit of a DLPDU
3.6.11 FC frame control (DLPDU type) field of a DLPDU
3.6.12 G
GAP update factor, the number of token cycles between GAP
maintenance (update) cycles
3.6.13 HSA
highest station address installed (configured) on this fieldbus
3.6.14 ind indication primitive
3.6.15 IsoM
isochronous mode
3.6.16 LMS list of master stations
3.6.17 LR DL/DLM_status: Local resource not available or not sufficient
3.6.18 LS DL/DLM_status: Local service not activated at DLSAP or local
DLSAP not activated
3.6.19 MSRD send and request data with multicast reply (DL-service)
3.6.20 NA DL/DLM_status: No acknowledgement/response
3.6.21 NIL locally existing value, but not fixed
3.6.22 NO DL/DLM_status: Not ok
3.6.23 NR DL/DLM_status: No response, DL/DLM-data acknowledgement
negative and send data ok
3.6.24 NS Next station, the station to which this Master will pass the token
3.6.25 OK DL/DLM_status: Service finished according to the rules
3.6.26 RDH DL/DLM_status: Response DL-data high and no resource for send
data
3.6.27 RDL DL/DLM_status: Response DL/DLM-data low and no resource for
send data
3.6.28 req request primitive
3.6.29 RR DL/DLM_status: No resource for send data and no response
DL-data available (acknowledgement negative)
3.6.30 RS DL/DLM_status: No service or no remote address activated at
remote-service-access-point (acknowledgement negative)
3.6.31 SA source address of a DLPDU
3.6.32 SAE source address extension(s) of a DLPDU, which conveys
S_SAP_index or source region/segment address or both
3.6.33 SC single character acknowledge DLPDU
3.6.34 SDA send data with acknowledge (DL-service)
3.6.35 SDN send data with no acknowledge (DL-service)
3.6.36 SRD
send and request data with reply (DL-service)
3.6.37 S_SAP source service access point, the DLSAP associated with the
initiates local DLS-user
3.6.38 S_SAP_index source service access point index, a component of a DLSAP-
address which designates that DLSAP within the DLE at which the
transaction is being initiated
3.6.39 SYN
synchronizing bits of a DLPDU (period of IDLE), which guarantees
the specified DLPDU integrity and facilitates receiver
synchronization
3.6.40 SYNCHT synchronization telegram, indicates the start of a new cycle in IsoM
3.6.41 tBIT
bit time, DL-symbol period, the time to transmit one bit on the
fieldbus: 1/(data signaling rate in bit/s)

– 18 – IEC 61158-3-3:2014 © IEC 2014
3.6.42 TCSI clock synchronization interval time
3.6.43 TCT Isochronous cycle time, the requested duration for one cycle in
IsoM
3.6.44 TQUI quiet time, transmitter fall time (line state uncertain time) or
repeater switch time or both. The time a transmitting station needs
to wait after the end of a DLPDU before enabling its receiver.
3.6.45 TRDY ready time, the time after which the transmitting master will expect
a reply DLPDU
3.6.46 TRR real rotation time, the time between the last successive receptions
of the token by the observing master station
3.6.47 TS This Station
3.6.48 TSDI station delay of initiator, the time a master station will wait before
sending successive DLPDUs
3.6.49 TSDR station delay of responder, the actual time a responder needs to
generate a reply DLPDU
3.6.50 TSET setup time, the time between an event (e.g. interrupt SYN timer
expired) and the necessary reaction (e.g. enabling a receiver)
3.6.51 TSH time shift, the time a real isochronous cycle deviates from the
requested duration for one cycle in IsoM
3.6.52 TSL slot time, the maximum time a master station waits for a reply
DLPDU
3.6.53 TSYN synchronization time, the period of IDLE before the beginning of a
DLPDU after which a station enables its receiver; the required
minimum inter-DLPDU idle period to guarantee DLPDU integrity and
a valid DLPDU
3.6.54 TSYNI synchronization interval time, the maximum time that a receiving
station waits for the required inter-DLPDU idle period, of duration
TSYN, to occur before it detects a bus fault
3.6.55 TTR Target rotation time, the anticipated time for one token cycle,
including allowances for high and low priority transactions, errors
and GAP maintenance
3.6.56 UE DL/DLM_status: Negative acknowledgement, remote user interface
error
3.7 Commo
...