IEC 61158-4-13:2007

IEC 61158-4-13
Edition 1.0 2007-12
INTERNATIONAL
STANDARD
Industrial communication networks – Fieldbus specifications –
Part 4-13: Data-link layer protocol specification – Type 13 elements

All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form
or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from
either IEC or IEC's member National Committee in the country of the requester.
If you have any questions about IEC copyright or have an enquiry about obtaining additional rights to this publication,
please contact the address below or your local IEC member National Committee for further information.

IEC Central Office
3, rue de Varembé
CH-1211 Geneva 20
Switzerland
Email: inmail@iec.ch
Web: www.iec.ch
About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.

About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigenda or an amendment might have been published.
ƒ Catalogue of IEC publications: www.iec.ch/searchpub
The IEC on-line Catalogue enables you to search by a variety of criteria (reference number, text, technical committee,…).
It also gives information on projects, withdrawn and replaced publications.
ƒ IEC Just Published: www.iec.ch/online_news/justpub
Stay up to date on all new IEC publications. Just Published details twice a month all new publications released. Available
on-line and also by email.
ƒ Electropedia: www.electropedia.org
The world's leading online dictionary of electronic and electrical terms containing more than 20 000 terms and definitions
in English and French, with equivalent terms in additional languages. Also known as the International Electrotechnical
Vocabulary online.
ƒ Customer Service Centre: www.iec.ch/webstore/custserv
If you wish to give us your feedback on this publication or need further assistance, please visit the Customer Service
Centre FAQ or contact us:
Email: csc@iec.ch
Tel.: +41 22 919 02 11
Fax: +41 22 919 03 00
IEC 61158-4-13
Edition 1.0 2007-12
INTERNATIONAL
STANDARD
Industrial communication networks – Fieldbus specifications –
Part 4-13: Data-link layer protocol specification – Type 13 elements

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
XC
ICS 35.100.20; 25.040.40 ISBN 2-8318-9437-9

– 2 – 61158-4-13 © IEC:2007(E)
CONTENTS
FOREWORD.5
INTRODUCTION.7
1 Scope.8
1.1 General .8
1.2 Specifications.8
1.3 Procedures.8
1.4 Applicability.9
1.5 Conformance.9
2 Normative references .9
3 Terms, definitions, symbols and abbreviations.9
3.1 Reference model terms and definitions.9
3.2 Service convention terms and definitions.11
3.3 Data-link service terms and definitions .12
3.4 Symbols and abbreviations.17
3.5 Common conventions .18
3.6 Additional conventions .19
4 Overview of the DL-protocol .19
4.1 Overview .19
4.2 General description .19
4.3 Service assumed from the PhL .22
4.4 DLL architecture.23
4.5 Local parameters and variables.24
5 General structure and encoding of PhIDUs and DLPDU and related elements of
procedure.26
5.1 Overview .26
5.2 MA_PDU structure and encoding.26
5.3 Common MAC frame structure, encoding and elements of procedure .27
5.4 Invalid DLPDU.29
6 DLPDU-specific structure, encoding and elements of procedure .29
6.1 General .29
6.2 Overview .30
6.3 Start of synchronization (SoC).30
6.4 PollRequest (PReq).32
6.5 Poll response (PRes) .34
6.6 Start of asynchronous (SoA).38
6.7 Asynchronous send (ASnd) .41
7 DLE elements of procedure .45
7.1 Overall structure.45
7.2 Cycle state machine (CSM) .45
7.3 Isochronous transmission TX/RX control (ITC) .65
7.4 Asynchronous transmission TX/RX control (ATC) .69
7.5 Asynchronous slot scheduler (ASS).73
7.6 Exception signaling (ES) .75
7.7 NMT signaling (NS) .77
7.8 DLL management protocol.78
Bibliography.83

61158-4-13 © IEC:2007(E) – 3 –

Figure 1 – Relationships of DLSAPs, DLSAP-addresses and group DL-addresses .14
Figure 2 – Slot communication network management.20
Figure 3 – Overall flow of data frames during one cycle .20
Figure 4 – Interaction of PhS primitives to DLE.22
Figure 5 – Data-link layer internal architecture.24
Figure 6 – Type 13 fieldbus DLPDU .27
Figure 7 – State transition diagram of the MNs CSM.51
Figure 8 – State transition diagram of MNs CSM at CSM_MS_NON_CYCLIC .53
Figure 9 – State transition diagram of MNs CSM at CSM_MS_CYCLIC.55
Figure 10 – State transition diagram of the CNs CSM .59
Figure 11 – State transition diagram of CNs CSM at CSM_CS_NON_CYCLIC .60
Figure 12 – State transition diagram of CNs CSM at CSM_CS_CYCLIC.61
Figure 13 – Multiple slot assignment.66
Figure 14 – State transition diagram of ITC.68
Figure 15 – State transition diagram of ATC .71
Figure 16 – State transition diagram of ASS .74
Figure 17 – State transition diagram of ES.76
Figure 18 – State transition diagram of NS.78
Figure 19 – State transition diagram of DLM .81

Table 1 – Data-link layer components .23
Table 2 – MAC multicast addresses .28
Table 3 – Message types .28
Table 4 – Node ID assignment .29
Table 5 – Structure of SoC DLPDU .30
Table 6 – Structure of SoC-Flag.31
Table 7 – Structure of PReq DLPDU .33
Table 8 – Structure of PReq-Flag.33
Table 9 – Structure of PRes DLPDU .35
Table 10 – Structure of PRes-Flag .36
Table 11 – Structure of SoA DLPDU .38
Table 12 – Structure of SoA-Flag.39
Table 13 – Definition of the RequestedServiceID in the SoA DLPDU.40
Table 14 – Structure of ASnd DLPDU .42
Table 15 – Definition of the ServiceID in the ASnd DLPDU .43
Table 16 – Structure of NMTRequest user data.44
Table 17 – Primitives exchanged between CSM and ITC .46
Table 18 – Parameters used with primitives exchanged between CSM and ITC .46
Table 19 – Primitives exchanged between CSM and ATC .47
Table 20 – Parameters used with primitives exchanged between CSM and ATC .47
Table 21 – Primitives exchanged between CSM and ASS .48
Table 22 – Parameters used with primitives exchanged between CSM and ASS .48

– 4 – 61158-4-13 © IEC:2007(E)
Table 23 – Primitives exchanged between CSM and ES .49
Table 24 – Parameters used with primitives exchanged between CSM and ES .49
Table 25 – Primitives exchanged between CSM and NS .49
Table 26 – Parameters used with primitives exchanged between CSM and NS .50
Table 27 – Primitives exchanged between CSM and DLM.50
Table 28 – Parameters used with primitives exchanged between CSM and DLM.50
Table 29 – Transitions of the MNs CSM .52
Table 30 – Transitions of MNs CSM at CSM_MS_NON_CYCLIC .53
Table 31 – Transitions of MNs CSM at CSM_MS_CYCLIC.56
Table 32 – Transitions of the CNs CSM .59
Table 33 – Transitions of CNs CSM at CSM_CS_NON_CYCLIC .60
Table 34 – Transitions of CNs CSM at CSM_CS_CYCLIC.62
Table 35 – CSM function table .63
Table 36 – Example of isochronous slot assignment .67
Table 37 – Primitives exchanged between ITC and DLS-user .67
Table 38 – Parameters used with primitives exchanged between ITC and DLS-user .67
Table 39 – Transitions of ITC.68
Table 40 – ITC function table .68
Table 41 – Primitives exchanged between ATC and DLS-user .69
Table 42 – Parameters used with primitives exchanged between ATC and DLS-user.70
Table 43 – Primitives exchanged between ATC and ES .70
Table 44 – Parameters used with primitives exchanged between ATC and ES .70
Table 45 – Transitions of ATC .71
Table 46 – ATC function table.73
Table 47 – Transitions of ASS .74
Table 48 – ASS function table.75
Table 49 – Primitives exchanged between ES and DLS-user .75
Table 50 – Parameters used with primitives exchanged between ES and DLS-user .75
Table 51 – Transitions of ES.76
Table 52 – Primitives exchanged between NS and DLS-user .77
Table 53 – Parameters used with primitives exchanged between NS and DLS-user .78
Table 54 – Transitions of NS.78
Table 55 – Primitives exchanged between DLM and DLS-user.79
Table 56 – Parameters used with primitives exchanged between DLM and DLS-user.80
Table 57 – Transitions of DLM .81
Table 58 – DLM function table .82

61158-4-13 © IEC:2007(E) – 5 –
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
INDUSTRIAL COMMUNICATION NETWORKS –
FIELDBUS SPECIFICATIONS –
Part 4-13: Data-link layer protocol specification – Type 13 elements

FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote
international co-operation on all questions concerning standardization in the electrical and electronic fields. To
this end and in addition to other activities, IEC publishes International Standards, Technical Specifications,
Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC
Publication(s)”). Their preparation is entrusted to technical committees; any IEC National Committee interested
in the subject dealt with may participate in this preparatory work. International, governmental and non-
governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely
with the International Organization for Standardization (ISO) in accordance with conditions determined by
agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all
interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence
between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in
the latter.
5) IEC provides no marking procedure to indicate its approval and cannot be rendered responsible for any
equipment declared to be in conformity with an IEC Publication.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees for any personal injury, property damage or
other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and
expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC
Publications.
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of
patent rights. IEC shall not be held responsible for identifying any or all such patent rights.
NOTE  Use of some of the associated protocol types is restricted by their intellectual-property-right holders. In all
cases, the commitment to limited release of intellectual-property-rights made by the holders of those rights permits
a particular data-link layer protocol type to be used with physical layer and application layer protocols in Type
combinations as specified explicitly in the IEC 61784 series. Use of the various protocol types in other
combinations may require permission from their respective intellectual-property-right holders.
International Standard IEC 61158-4-13 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-4 subseries cancel and replace
IEC 61158-4:2003. This edition of this part constitutes a technical addition, which also
replaces IEC/PAS 62408, published in 2005.
This edition of IEC 61158-4 includes the following significant changes from the previous
edition:
a) deletion of the former Type 6 fieldbus, and the placeholder for a Type 5 fieldbus data link
layer, for lack of market relevance;

– 6 – 61158-4-13 © IEC:2007(E)
b) addition of new types of fieldbuses;
c) division of this part into multiple parts numbered -4-1, -4-2, …, -4-19.
The text of this standard is based on the following documents:
FDIS Report on voting
65C/474/FDIS 65C/485/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-4 includes the following significant changes from the prior edition:
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.

61158-4-13 © IEC:2007(E) – 7 –
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 data-link protocol provides the data-link service by making use of the services available
from the physical 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 data-link
entities (DLEs) 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:
a) as a guide for implementors and designers;
b) for use in the testing and procurement of equipment;
c) as part of an agreement for the admittance of systems into the open systems environment;
d) 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.

– 8 – 61158-4-13 © IEC:2007(E)
INDUSTRIAL COMMUNICATION NETWORKS –
FIELDBUS SPECIFICATIONS –
Part 4-13: Data-link layer protocol specification – Type 13 elements

1 Scope
1.1 General
The data-link layer provides basic time-critical messaging communications between devices in
an automation environment.
This protocol provides communication opportunities to all participating data-link entities
a) in a synchronously-starting cyclic manner, according to a pre-established schedule, and
b) in a cyclic or acyclic asynchronous manner, as requested each cycle by each of those
data-link entities.
Thus this protocol can be characterized as one which provides cyclic and acyclic access
asynchronously but with a synchronous restart of each cycle.
1.2 Specifications
This standard specifies
a) procedures for the timely transfer of data and control information from one data-link user
entity to a peer user entity, and among the data-link entities forming the distributed data-
link service provider;
b) procedures for giving communications opportunities to all participating DL-entities,
sequentially and in a cyclic manner for deterministic and synchronized transfer at cyclic
intervals up to one millisecond;
c) procedures for giving communication opportunities available for time-critical data
transmission together with non-time-critical data transmission without prejudice to the
time-critical data transmission;
d) procedures for giving cyclic and acyclic communication opportunities for time-critical data
transmission with prioritized access;
e) procedures for giving communication opportunities based on standard ISO/ IEC 8802-3
medium access control, with provisions for nodes to be added or removed during normal
operation;
f) the structure of the fieldbus DLPDUs used for the transfer of data and control information
by the protocol of this standard, and their representation as physical interface data units.
1.3 Procedures
The procedures are defined in terms of
a) the interactions between peer DL-entities (DLEs) through the exchange of fieldbus
DLPDUs;
b) the interactions between a DL-service (DLS) provider and a DLS-user in the same system
through the exchange of DLS primitives;
c) the interactions between a DLS-provider and a Ph-service provider in the same system
through the exchange of Ph-service primitives.

61158-4-13 © IEC:2007(E) – 9 –
1.4 Applicability
These procedures are applicable to instances of communication between systems which
support time-critical communications services within the data-link layer of the OSI or fieldbus
reference models, and which require the ability to interconnect in an open systems
interconnection environment.
Profiles provide a simple multi-attribute means of summarizing an implementation’s
capabilities, and thus its applicability to various time-critical communications needs.
1.5 Conformance
This standard also specifies conformance requirements for systems implementing these
procedures. This standard does not contain tests to demonstrate compliance with such
requirements.
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 61158-3-13, Industrial communication networks – Fieldbus specifications – Part 3-13:
Data-link layer service definition – Type 13 elements
ISO/IEC 7498-1, Information technology – Open Systems Interconnection – Basic Reference
Model: The Basic Model
ISO/IEC 7498-3, Information technology – Open Systems Interconnection – Basic Reference
Model: Naming and addressing
ISO/IEC 8802-3:2000, 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
3 Terms, definitions, symbols and abbreviations
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:

– 10 – 61158-4-13 © IEC:2007(E)
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]
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]
61158-4-13 © IEC:2007(E) – 11 –
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

– 12 – 61158-4-13 © IEC:2007(E)
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
3.3 Data-link service terms and definitions
3.3.1
async-only CN
CN that is accessed only by polling
3.3.2
asynchronous period
second part of the Type 13 cycle, starting with a start of asynchronous (SoA) frame
3.3.3
basic Ethernet mode
mode that provides legacy Ethernet communication
3.3.4
continuous
communication class where isochronous communication takes place every cycle (the opposite
to multiplexed)
3.3.5
controlled node (CN)
network node without the ability to manage the SCNM mechanism
3.3.6
cycle state machine
state machine that controls the data-link layer cycle and is itself controlled by the NMT state
machine which determines the current operating mode
3.3.7
cycle time
time between two consecutive start of cyclic (SoC) frames
NOTE  The Cycle Time includes the time for data transmission and some idle time before the beginning of the next
cycle.
3.3.8
DLCEP-address
DL-address which designates either
a) one peer DL-connection-end-point, or

61158-4-13 © IEC:2007(E) – 13 –
b) one multi-peer publisher DL-connection-end-point and implicitly the corresponding set of
subscriber DL-connection-end-points where each DL-connection-end-point exists within a
distinct DLSAP and is associated with a corresponding distinct DLSAP-address
3.3.9
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.10
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.
3.3.11
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.12
(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. (See Figure 1.)

– 14 – 61158-4-13 © IEC:2007(E)

DLS-user-entity
DLS-user-entity
DLS-users
DLSAP DLSAP DLSAP
DLSAP-
address DLSAP-
DLSAP-
group DL-
address
addresses
address
DL-layer
DL-entity
PhSA P PhSA P
Ph-layer
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.13
Type 13 fieldbus cycle
fixed time interval consecutively repeated which is organized by the MN
3.3.14
Type 13 fieldbus node ID
unique number within one Type 13 network used to addres a Type 13 fieldbus node
3.3.15
frame
denigrated synonym for DLPDU
3.3.16
isochronous data
data which is transmitted every cycle (or every nth cycle in case of multiplexed isochronous
data)
3.3.17
isochronous period
period within each cycle that offers deterministic operation through being reserved for the
exchange of (continuous or multiplexed) isochronous data

61158-4-13 © IEC:2007(E) – 15 –
3.3.18
legacy Ethernet
Ethernet as standardized in ISO/IEC 8802-3 (non-deterministic operation in non-time-critical
environments).
3.3.19
managing node
node that can manage the SCNM mechanism
3.3.20
multiplexed
communication class where cyclic communication takes place in such a way that m nodes are
served in s cycles (an alternative to continuous)
3.3.21
multiplexed timeslot
timeslot assigned to multiplexed isochronous data and shared among multiple nodes
3.3.22
multipoint connection
connection from one node to many nodes.
NOTE  Multipoint connection allows data transfer from a single publisher to many subscriber nodes.
3.3.23
multi-peer DLC
centralized multi-end-point DL-connection offering DL-duplex-transmission between a single
distinguished DLS-user known as the publisher or publishing DLS-user, and a set of peer but
undistinguished DLS-users known collectively as the subscribers or subscribing DLS-users,
where the publishing DLS-user can send to the subscribing DLS-users as a group (but not
individually), and the subscribing DLS-users can send to the publishing DLS-user (but not to
each other).
3.3.24
NetTime
clock time of the MN as distributed to all CNs within the SoC frame.
3.3.25
network management
management functions and services that perform network initialization, configuration and error
handling
3.3.26
node
single DL-entity as it appears on one local link
3.3.27
PollRequest
frame which is used in the isochronous part of a communications cycle
3.3.28
PollResponse
frame which is used in the isochronous part of a communications cycle to respond to a
PollRequest frame
– 16 – 61158-4-13 © IEC:2007(E)
3.3.29
process data object
object for isochronous data exchange between nodes
3.3.30
protocol
convention about the data formats, time sequences, and error correction in the data exchange
of communication systems
3.3.31
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.32
sending DLS-user
DL-service user that acts as a source of DLS-user-data
3.3.33
service data object
object for asynchronous data exchange between nodes
3.3.34
slot communication network management
mechanism which ensures that there are no collisions during physical network access of any
of the networked nodes, thus providing deterministic communication via legacy Ethernet

61158-4-13 © IEC:2007(E) – 17 –
3.4 Symbols and abbreviations
3.4.1 ASnd Asynchronous send (frame type)
3.4.2 CN Controlled node
3.4.3 DL- Data-link layer (as a prefix)
3.4.4 DLC DL-connection
3.4.5 DLCEP DL-connection-end-point
3.4.6 DLE DL-entity (the local active instance of the data-link layer)
3.4.7 DLL DL-layer
3.4.8 DLPCI DL-protocol-control-information
3.4.9 DLPDU DL-protocol-data-unit
3.4.10 DLM DL-management
3.4.11 DLME DL-management entity (the local active instance of
DL-management)
3.4.12 DLMS DL-management service
3.4.13 DLS DL-service
3.4.14 DLSAP DL-service-access-point
3.4.15 DLSDU DL-service-data-unit
3.4.16 FIFO First-in first-out (queuing method)
3.4.17 MN Managing node
3.4.18 NMT Network management
3.4.19 OSI Open systems interconnection
3.4.20 PDO Process data object
3.4.21 Ph- Physical layer (as a prefix)
3.4.22 PhE Ph-entity (the local active instance of the physical layer)
3.4.23 PhL Ph-layer
3.4.24 PReq PollRequest (frame type)
3.4.25 PRes PollResponse (frame type)
3.4.26 RTE Real time Ethernet
3.4.27 SCNM Slot communication network management
3.4.28 SDO Service data object
3.4.29 SoA Start of asynchronous (frame type)
3.4.30 SoC Start of cyclic (frame type)

– 18 – 61158-4-13 © IEC:2007(E)
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: mandatory for the primitive.
U Parameter: 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.
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.
61158-4-13 © IEC:2007(E) – 19 –
3.6 Additional conventions
In the diagrams which illustrate the DLS and DLM interfaces, dashed lines indicate cause-
and-effect or time-sequence relationships between actions at different stations, while solid
lines with arrows indicate cause-and-effect time-sequence relationships which occur within
the DLE-provider at a single station.
The following notation, a shortened form of the primitive classes defined in 3.5, is used in the
figures and tables.
req request primitive
ind
indication primitive
cnf confirm primitive (confirmation)
res Response primitive
4 Overview of the DL-protocol
4.1 Overview
A Type 13 fieldbus extends Ethernet according to the ISO/IEC 8802-3 standard with
mechanisms to transfer data with predictable timing and precise synchronizationto meet
timing demands typical for high-performance automation and motion applications. It does not
change basic principles of the Fast Ethernet Standard ISO/IEC 8802-3 but extends it towards
real-time Ethernet. Thus it is possible to leverage and continue to use any standard Ethernet
silicon, infrastructure component or test and measurement equipment like a network analyzer.
4.2 General description
4.2.1 General
Type 13 fieldbus provides mechanisms to achieve the following.
• Transmit time-critical data in precise isochronous cycles. Data exchange is based on a
publish/subscribe relationship.
• Synchronize networked nodes with high accuracy.
• Transmit less time-critical data asynchronously on request. Asynchronous data
communication can be used to transfer IP-based protocols like TCP or UDP and higher
layer protocols such as HTTP, FTP,…
Type 13 fieldbus manages the network traffic in a way that there are dedicated time-slots for
isochronous and asynchronous data (see Figure 2). It takes care that always only one
networked device gains access to the network media. Thus transmission of isochronous and
asynchronous data will never interfere and precise communication timing is guaranteed. The
mechanism is called slot communication network management (SCNM). SCNM is managed by
one particular networked device – the Managing Node (MN) – which includes the MN
functionality. All other nodes are cal
...