Iec 61158 3 17 2007

IEC 61158 3 17 Edition 1 0 2007 12 INTERNATIONAL STANDARD Industrial communication networks – Fieldbus specifications – Part 3 17 Data link layer service definition – Type 17 elements IE C 6 11 58 3 1[.]

IEC 61158-3-17

Edition 1.0 2007-12

INTERNATIONAL

STANDARD

Industrial communication networks – Fieldbus specifications –

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

THIS PUBLICATION IS COPYRIGHT PROTECTED Copyright © 2007 IEC, Geneva, Switzerland

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

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: 2H 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: 3H 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: 4H 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: 5H 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: 6H csc@iec.ch

Tel.: +41 22 919 02 11

Fax: +41 22 919 03 00

IEC 61158-3-17

Edition 1.0 2007-12

INTERNATIONAL

STANDARD

Industrial communication networks – Fieldbus specifications –

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

Table 13 – DLM-EVENT primitive and parameters 114H29

INTERNATIONAL ELECTROTECHNICAL COMMISSION

INDUSTRIAL COMMUNICATION NETWORKS –

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

FOREWORD 1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising

all national electrotechnical committees (IEC National Committees) The object of IEC is to promote

international co-operation on all questions concerning standardization in the electrical and electronic fields To

this end and in addition to other activities, IEC publishes International Standards, Technical Specifications,

Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC

Publication(s)”) Their preparation is entrusted to technical committees; any IEC National Committee interested

in the subject dealt with may participate in this preparatory work International, governmental and

non-governmental organizations liaising with the IEC also participate in this preparation IEC collaborates closely

with the International Organization for Standardization (ISO) in accordance with conditions determined by

agreement between the two organizations

2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international

consensus of opinion on the relevant subjects since each technical committee has representation from all

interested IEC National Committees

3) IEC Publications have the form of recommendations for international use and are accepted by IEC National

Committees in that sense While all reasonable efforts are made to ensure that the technical content of IEC

Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any

misinterpretation by any end user

4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications

transparently to the maximum extent possible in their national and regional publications Any divergence

between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in

the latter

5) IEC provides no marking procedure to indicate its approval and cannot be rendered responsible for any

equipment declared to be in conformity with an IEC Publication

6) All users should ensure that they have the latest edition of this publication

7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and

members of its technical committees and IEC National Committees for any personal injury, property damage or

other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and

expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC

Publications

8) Attention is drawn to the Normative references cited in this publication Use of the referenced publications is

indispensable for the correct application of this publication

NOTE Use of some of the associated protocol types is restricted by their intellectual-property-right holders In all

cases, the commitment to limited release of intellectual-property-rights made by the holders of those rights permits

a particular data-link layer protocol type to be used with physical layer and application layer protocols in type

combinations as specified explicitly in the IEC 61784 series Use of the various protocol types in other

combinations may require permission of their respective intellectual-property-right holders

International Standard IEC 61158-3-17 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-3 subseries cancel and replace

IEC 61158-3:2003 This edition of this part constitutes a technical addition This part and its

Type 17 companion parts also replace IEC/PAS 62405, published in 2005

This edition includes the following significant changes with respect to 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;

b) addition of new types of fieldbuses;

c) division of this part into multiple parts numbered 3-1, 3-2, …, 3-19

This edition of this part constitutes an editorial revision

The text of this standard is based on the following documents:

FDIS Report on voting 65C/473/FDIS 65C/484/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 committee has decided that the contents of this publication will remain unchanged until

the maintenance result date indicated on the IEC web site under 57Hhttp://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

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

INDUSTRIAL COMMUNICATION NETWORKS –

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

1 Scope

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

17 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 17 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;

• 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

• Conformance

This standard does not specify individual implementations or products, nor does it 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 17 data-link layer services defined in this standard

2 Normative reference

The following referenced documents are indispensable for the application of this document

For dated references, only the edition cited applies For all other undated references, the

latest edition of the referenced document (including any amendments) applies

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 10731:1994, Information technology – Open Systems Interconnection – Basic

Reference Model – Conventions for the definition of OSI services

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

Internet Engineering Task Force (IETF), Request for Comments (RFC):

RFC 826 Ethernet Address Resolution Protocol

(available at <http://www.ietf.org/rfc/rfc0826.txt>)

3 Definitions

For the purposes of this document, the following terms and definitions apply

3.1 Terms and definitions

part of the RTE network consisting of one or two subnetwork(s)

NOTE Two subnetworks are required to compose a dual-redundant RTE network, and each end node in the

domain is connected to both of the subnetworks

3.1.2.3

domain master

station which performs diagnosis of routes to all other domains, distribution of network time to

nodes inside the domain, acquisition of absolute time from the network time master and

notification of status of the domain

bridge to which at least one router, external bridge or node non-compliant with this

specification, and to which at least one internal bridge or RTE station is connected

3.1.2.9

link

physical communication channel between two nodes

3.1.2.10

network time master

station which distributes network time to domain masters

3.1.2.11

non-redundant interface node

node which has a single interface port

3.1.2.12

non-redundant station

station that consists of a single end node

NOTE “non-redundant station” is synonymous with “end node”

3.1.2.13

path

logical communication channel between two nodes, which consists of one or two link(s)

3.1.2.14

redundant interface node

node with two interface ports one of which is connected to a primary network, while the other

is connected to a secondary network

3.1.2.15

redundant station

station that consists of a pair of end nodes

NOTE Each end node of a redundant station has the same station number, but has a different DL-address

part of a network that does not contain any routers A subnetwork consists of end nodes,

bridges and segments

NOTE Every end node included in a subnetwork has the same IP network address

3.2 Abbreviations and symbols

3.2.1 ISO/IEC 10731 abbreviations

OSI Open Systems Interconnection

3.2.2 Other abbreviations and symbols

ASS Acknowledged sequence of unitdata transfer service

AUS Acknowledged unitdata transfer service

cnf Confirmation primitive

DL- Data-link layer (as a prefix)

DLE DL-entity (the local active instance of the data-link layer)

FIFO First-in first-out (queuing method)

ind Indication primitive

IP Internet protocol

ISO International Organization for Standardization

PDU Protocol data unit

MSS Multipoint sequence of unitdata transfer service

MUS Multipoint unitdata transfer service

QoS Quality of service

req Request primitive

rsp Response primitive

SAP Service access point

SDU Service data unit

ToS Type of service

UUS Unacknowledged unitdata transfer service

3.3 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

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 Overview of the data-link layer service

4.1 General

The data-link service (DLS) provides transparent and reliable data transfer between

DLS-users It makes the way that supporting communication resources are utilized invisible to

DLS-users

In particular, the DLS provides the following

a) Independence from the underlying Physical Layer The DLS relieves DLS-users from all

direct concerns regarding which configuration is available (for example, direct connection,

or indirect connection through one or more bridges) and which physical facilities are used

(for example, which of a set of diverse physical paths)

b) Transparency of transferred information The DLS provides the transparent transfer of

DLS-user-data It does not restrict the content, format or coding of the information, nor

does it ever need to interpret the structure or meaning of that information It may, however,

restrict the amount of information that can be transferred as an indivisible unit

c) Reliable data transfer The DLS relieves the DLS-user from concerns regarding insertion

or corruption of data, or, if requested, loss, duplication or misordering of data, which can

occur In some cases of unrecovered errors in the data-link layer, duplication or loss of

DLSDUs can occur In cases where protection against misordering of data is not

employed, misordering can occur

d) Quality of Service (QoS) selection The DLS provides DLS-users with a means to request

and to agree upon a quality of service for the data transfer QoS is specified by means of

QoS parameters representing aspects such as mode of operation, transit delay, accuracy,

reliability, security and functional safety

e) Addressing The DLS allows the DLS-user to identify itself and to specify the DLSAPs

to/from which data are to be transferred

f) Scheduling The DLS allows the set of DLS-users to provide some guidance on internal

scheduling of the distributed DLS-provider This guidance supports the time-critical

aspects of the DLS, by permitting the DLS-user some degree of management over when

opportunities for communication will be granted to various DLEs for various

DLSAP-addresses

g) Common time sense The DLS can provide the DLS-user with a sense of time that is

common to all DLS-users on the network

h) Queues The DLS can provide the sending or receiving DLS-user with a FIFO queue,

where each queue item can hold a single DLSDU

4.2 Overview of network structure

Although the DLS conforms formally to the “three-layer” Fieldbus Reference Model, it actually

utilizes the transport layer service and the network layer service in addition to the data-link

layer service of the OSI Basic Reference Model The DLS of this specification is actually a

transport layer service in terms of the OSI Basic Reference Model Thus the network may

consist of one or more subnetworks interconnected to each other by the network layer relay

entities, known as routers

A network may be a redundant structure A redundant network consists of two independent

networks making dual-redundancy; they are referred to as the primary network and the

secondary network Consequently, dual-redundant independent logical communication

channels between two communication end nodes can be implemented This logical channel is

called a route

A pair of subnetworks comprising a dual-redundant network is called a domain

A subnetwork consists of one or more segments interconnected by DL-relay entities, known

as bridges The topology of a subnetwork may be a tree, a ring or a mesh consisting of

segments interconnected by bridges

A segment consists of one or more DLEs, all of which are connected directly (i.e., without

intervening DL-relay entities) to a single shared logical communication channel, which is

called a link

A path (logical communication channel) consists of one or two physically independent and

logically parallel real communication channels, which are called links

4.3 Overview of addressing

domain number

numeric identifier that indicates a domain Two subnetworks comprising a dual-redundant

domain have an identical domain number

station number

numeric identifier that indicates a RTE station Two end nodes comprising a dual-redundant

station have an identical station number

TSAP address

DL-entity actually provides transport layer services, so DLS is provided at TSAPs TSAP is

identified by a set of TSAP-address (IP-address) and TSAP-identifier (UDP port number)

IP address

unique address for each end node An IP address consists of a network address portion and a

host address portion The network address is assigned according to the domain number, while

the host address is assigned based on the station number Each end node of a

dual-redundant station has a different host address

MAC address

MAC address is a unique address for an end node defined in ISO/IEC 8802-3 The destination

MAC address is resolved by the mechanism defined in RFC 826 from the destination IP

address

4.4 Types of data-link service

There are three types of DLS as follows:

a) a DLSAP management service;

b) a connectionless-mode data transfer service;

c) a DL-management service

5 DLSAP management service

5.1 Overview

This clause provides a conceptual definition of the services provided by the DLS-provider to

the DLS-user(s) This clause does not constrain the actual implementations of the interactions

at the DLS-provider to the DLS-user interface

5.2 Facilities of the DLSAP management service

The DLS provides the following facilities to the DLS-user:

a) a means for creating and deleting a FIFO queue of specified depth;

b) a means for assigning a DLSAP-address to the DLSAP;

c) a means for binding previously created FIFO queues to each potential direction of

connectionless data transfer at the specified DLSAP;

d) a means for specifying QoS parameters of the specified DLSAP;

e) a means for releasing resources used previously for the DLSAP

5.3 Model of the DLSAP management service

This standard uses the abstract model for a layer service defined in ISO/IEC 10731, Clause 5

The model defines interactions between the DLS-user and the DLS-provider that take place at

a DLSAP Information is passed between the DLS-user and the DLS-provider by DLS

primitives that convey parameters

The DLSAP management primitives are used to provide a local service between a DLS-user

and the local DLE Remote DLEs and remote DLS-users are not involved direct, so there is no

need for the other primitives of ISO/IEC 10731 Therefore the DLSAP management services

are provided by request primitives with input and output parameters

5.4 Sequence of primitives at one DLSAP

Table 1 is a summary of the DLSAP management primitives and parameters The major

sequence of primitives at a single DLE is shown in 116HFigure 1

Table 1 – Summary of DLSAP management primitives and parameters

queue creation DL-CREATE request (in Queue DLS-user-identifier,

Maximum DLSDU size, Maximum queue depth,

out Status,

Queue DL-identifier) queue deletion DL-DELETE request (in Queue DL-identifier,

out Status)

DLSAP activation DL-BIND request (in DLSAP-address DLS-user-identifier,

Sending queue DL-identifier Receiving queue DL-identifier, QoS parameters,

out Status,

DLSAP-address DL-identifier) DLSAP deactivation DL-UNBIND request (in DLSAP-address DL-identifier

out Status)

Figure 1 – Sequence of primitives for the DLSAP management DLS

5.5 Create

5.5.1 Function

The create queue DLS primitive may be used to create a limited-depth FIFO queue for later

constrained association with a DLSAP The resulting FIFO queue initially will be empty

5.5.2 Types of parameter

Table 2 lists the primitive and parameters of the create queue DLS

Table 2 – DLSAP-management C REATE primitive and parameters

DL-CREATE Request

Queue DLS-user-identifier M Maximum DLSDU size M Maximum queue depth M

Queue DL-identifier C

5.5.2.1 Queue DLS-user-identifier

This parameter specifies a means of referring to the queue in output parameters of other local

DLS primitives that convey the name of the queue from the local DLE to the local DLS-user

The naming-domain of the queue DLS-user-identifier is the DLS-user’s local-view

5.5.2.2 Maximum DLSDU size

This parameter specifies an upper bound on the size (in octets) of DLSDUs that can be put

into the queue

5.5.2.3 Maximum queue depth

This parameter specifies the maximum number of items in the associated queue

DL-CREATE request

DL-BIND request

DL-UNITDATA request

DL-UNITDATA indication

or

DL-UNBIND request DL-DELETE request