IEC 61158-6-2:2010

Industrial communication networks - Fieldbus specifications - Part 6-2: Application layer protocol specification - Type 2 elements

IEC 61158-6-2:2010 provides common elements for basic time-critical and non-time-critical messaging communications between application programs in an automation environment and material specific to Type 2 fieldbus. The term "time-critical" is used to represent the presence of a time-window, within which one or more specified actions are required to be completed with some defined level of certainty. Failure to complete specified actions within the time window risks failure of the applications requesting the actions, with attendant risk to equipment, plant and possibly human life. It specifies interactions between remote applications and defines the externally visible behavior provided by the Type 2 fieldbus application layer. This second edition cancels and replaces the first edition published in 2007 and constitutes a technical revision. The main changes with respect to the previous edition are:
- update of normative and bibliographic references;
- update of abbreviations;
- update list of service request/response PDUs (Time Sync and Parameter ASEs/objects);
- update of Time Sync ASE/object;
- new Parameter ASE/object;
- update/add object and services codes for Time Sync and Parameter ASEs;
- new QoS specification.
This bilingual version published in 2012-07 corresponds to the English version published in 2010-08.

Réseaux de communication industriels - Spécifications des bus de terrain - Partie 6-2: Spécification de protocole de la couche application - Eléments de Type 2

La IEC 61158-6-2:2010 fournit les éléments communs pour les communications de messagerie de base à temps critique et à temps non critique entre des programmes d'application dans un environnement d'automatisation et le matériau spécifique au bus de terrain de Type 2. Le terme "à temps critique" sert à représenter la présence d'une fenêtre temporelle, dans les limites de laquelle une ou plusieurs actions spécifiées sont tenues d'être parachevées avec un certain niveau défini de certitude. Le manquement à parachever les actions spécifiées dans les limites de la fenêtre temporelle risque d'entraîner la défaillance des applications qui demandent ces actions, avec le risque concomitant pour l'équipement, l'installation et éventuellement pour la vie humaine. Elle spécifie les interactions entre les applications distantes et définit le comportement visible de l'extérieur fourni par la couche application de bus de terrain de Type 2. Cette deuxième édition annule et remplace la première édition, parue en 2007. Elle constitue une révision technique. Les principales modifications par rapport à l'édition précédente sont:
- mise à jour des références normatives et bibliographiques;
- mise à jour des abréviations;
- liste de mise à jour pour les PDU de demande/réponse de service (ASE/objets Time Sync et Parameter);
- mise à jour d'ASE/objet Time Sync;
- nouvel ASE/objet Parameter;
- mise à jour/ajout de codes d'objet et de services pour les ASE Time Sync et Parameter;
- nouvelle spécification de QoS.
La présente version bilingue (2012-07) correspond à la version anglaise monolingue publiée en 2010-08.

General Information

• Status: Published
• Publication Date: 05-Aug-2010
• ICS: 25.040.40 - Industrial process measurement and control
• ICS: 35.100.70 - Application layer
• ICS: 35.110 - Networking
• Technical Committee: SC 65C - Industrial networks
• Drafting Committee: WG 9 - TC 65/SC 65C/WG 9
• Current Stage: DELPUB - Deleted Publication
• Completion Date: 19-Aug-2014

Standards Content (Sample)

IEC 61158-6-2
®
Edition 2.0 2010-08
INTERNATIONAL
STANDARD


Industrial communication networks – Fieldbus specifications –
Part 6-2: Application layer protocol specification – Type 2 elements



IEC 61158-6-2:2010(E)

---------------------- Page: 1 ----------------------
THIS PUBLICATION IS COPYRIGHT PROTECTED
Copyright © 2010 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
3, rue de Varembé
CH-1211 Geneva 20
Switzerland
Email: [e-mail]
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: [e-mail]
Tel.: [phone]
Fax: [phone]

---------------------- Page: 2 ----------------------
IEC 61158-6-2
®
Edition 2.0 2010-08
INTERNATIONAL
STANDARD


Industrial communication networks – Fieldbus specifications –
Part 6-2: Application layer protocol specification – Type 2 elements


INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
XH
ICS 25.04.40; 35.100.70; 35.110 ISBN 978-2-88912-118-2
® Registered trademark of the International Electrotechnical Commission

---------------------- Page: 3 ----------------------
– 2 – 61158-6-2 © IEC:2010(E)
CONTENTS
FOREWORD.12
INTRODUCTION.14
1 Scope.15
1.1 General .15
1.2 Specifications.15
1.3 Conformance.16
2 Normative references .16
3 Terms, definitions, symbols, abbreviations and conventions .17
3.1 Terms and definitions from other ISO/IEC standards .17
3.2 Terms and definitions from IEC 61158-5-2.18
3.3 Additional terms and definitions.18
3.4 Abbreviations and symbols.24
3.5 Conventions .24
3.6 Conventions used in state machines .29
4 Abstract syntax.30
4.1 FAL PDU abstract syntax .30
4.2 Data abstract syntax specification .120
4.3 Encapsulation abstract syntax .124
5 Transfer syntax .138
5.1 Compact encoding.138
5.2 Data type reporting.145
6 Structure of FAL protocol state machines .150
7 AP-Context state machine .150
7.1 Overview .150
7.2 Connection object state machine.150
8 FAL service protocol machine (FSPM).160
8.1 General .160
8.2 Primitive definitions .160
8.3 Parameters of primitives.164
8.4 FSPM state machines.165
9 Application relationship protocol machines (ARPMs) . 166
9.1 General .166
9.2 Connection-less ARPM (UCMM).166
9.3 Connection-oriented ARPMs (transports).176
10 DLL mapping protocol machine 1 (DMPM 1) .247
10.1 General .247
10.2 Link producer .247
10.3 Link consumer.248
10.4 Primitive definitions .248
10.5 DMPM state machine .250
10.6 Data-link Layer service selection .251
11 DLL mapping protocol machine 2 (DMPM 2) .251
11.1 General .251
11.2 Mapping of UCMM PDUs.252
11.3 Mapping of transport class 0 and class 1 PDUs .257

---------------------- Page: 4 ----------------------
61158-6-2 © IEC:2010(E) – 3 –
11.4 Mapping of transport class 2 and class 3 PDU’s .258
11.5 Mapping of transport classes 4 to 6 .258
11.6 IGMP Usage.258
11.7 Quality of Service (QoS) for CP 2/2 messages .259
11.8 Management of an encapsulation session . 262
12 DLL mapping protocol machine 3 (DMPM 3) .263
Bibliography.264

Figure 1 – Attribute table format and terms .25
Figure 2 – Service request/response parameter.25
Figure 3 – Example of an STD .29
Figure 4 – Network connection parameters .49
Figure 5 – Time tick .51
Figure 6 – Connection establishment time-out .53
Figure 7 – Transport Class Trigger attribute.86
Figure 8 – CP2/3_initial_comm_characteristics attribute format .89
Figure 9 – Segment type.97
Figure 10 – Port segment.98
Figure 11 – Logical segment encoding.100
Figure 12 – Extended network segment .104
Figure 13 – Encapsulation message .124
Figure 14 – FixedLengthBitString compact encoding bit placement rules . 142
Figure 15 – Example compact encoding of a SWORD FixedLengthBitString.142
Figure 16 – Example compact encoding of a WORD FixedLengthBitString.142
Figure 17 – Example compact encoding of a DWORD FixedLengthBitString .143
Figure 18 – Example compact encoding of a LWORD FixedLengthBitString .143
Figure 19 – Example 2 of formal encoding of a structure type specification. 147
Figure 20 – Example of abbreviated encoding of a structure type specification . 148
Figure 21 – Example 1 of formal encoding of an array type specification . 148
Figure 22 – Example 2 of formal encoding of an array type specification . 149
Figure 23 – Example 1 of abbreviated encoding of an array type specification .149
Figure 24 – Example 2 of abbreviated encoding of an array type specification .150
Figure 25 – I/O Connection object state transition diagram . 151
Figure 26 –Bridged Connection object state transition diagram .155
Figure 27 – Explicit Messaging Connection object state transition diagram . 157
Figure 28 – State transition diagram of UCMM client . 169
Figure 29 – State transition diagram of high–end UCMM server. 170
Figure 30 – State transition diagram of low–end UCMM server . 172
Figure 31 – Sequence diagram for a UCMM with one outstanding message.174
Figure 32 – Sequence diagram for a UCMM with multiple outstanding messages.175
Figure 33 – TPDU buffer .176
Figure 34 – Data flow diagram using a client transport class 0 and server transport
class 0 .179
Figure 35 – Sequence diagram of data transfer using transport class 0. 179

---------------------- Page: 5 ----------------------
– 4 – 61158-6-2 © IEC:2010(E)
Figure 36 – Class 0 client STD .180
Figure 37 – Class 0 server STD .181
Figure 38 – Data flow diagram using client transport class 1 and server transport
class 1 .182
Figure 39 – Sequence diagram of data transfer using client transport class 1 and
server transport class 1 .183
Figure 40 – Class 1 client STD .185
Figure 41 – Class 1 server STD .186
Figure 42 – Data flow diagram using client transport class 2 and server transport
class 2 .188
Figure 43 – Diagram of data transfer using client transport class 2 and server transport
class 2 without returned data .189
Figure 44 – Sequence diagram of data transfer using client transport class 2 and
server transport class 2 with returned data .190
Figure 45 – Class 2 client STD .191
Figure 46 – Class 2 server STD .193
Figure 47 – Data flow diagram using client transport class 3 and server transport
class 3 .196
Figure 48 – Sequence diagram of data transfer using client transport class 3 and
server transport class 3 without returned data.197
Figure 49 – Sequence diagram of data transfer using client transport class 3 and
server transport class 3 with returned data .198
Figure 50 – Class 3 client STD .200
Figure 51 – Class 3 server STD .203
Figure 52 – Data flow diagram using transport classes 4 and 5.205
Figure 53 – Sequence diagram of message exchange using transport classes 4 and 5 . 206
Figure 54 – Sequence diagram of messages overwriting each other .207
Figure 55 – Sequence diagram of queued message exchange using transport classes
4 and 5 .208
Figure 56 – Sequence diagram of retries using transport classes 4 and 5 . 208
Figure 57 – Sequence diagram of idle traffic using transport classes 4 and 5. 209
Figure 58 – Classes 4 and 5 basic structure .210
Figure 59 – Class 6 basic structure.211
Figure 60 – Classes 4 to 6 general STD.212
Figure 61 – Class 4 sender STD .214
Figure 62 – Class 4 receiver STD .217
Figure 63 – Sequence diagram of three fragments using transport class 5. 220
Figure 64 – Sequence diagram of fragmentation with retries using transport class 5. 221
Figure 65 – Sequence diagram of two fragments using transport class 5 . 221
Figure 66 – Sequence diagram of aborted message using transport class 5 . 222
Figure 67 – Class 5 sender STD .223
Figure 68 – Class 5 receiver STD .226
Figure 69 – Data flow diagram for transport class 6 .231
Figure 70 – Sequence diagram of message exchange using transport class 6 . 233
Figure 71 – Sequence diagram of retries using transport class 6 . 233
Figure 72 – Sequence diagram of idle traffic using transport class 6 . 234

---------------------- Page: 6 ----------------------
61158-6-2 © IEC:2010(E) – 5 –
Figure 73 – Sequence diagram of request overwriting null .235
Figure 74 – Sequence diagram of response overwriting ACK of null. 235
Figure 75 – Sequence diagram of three fragments using transport class 6. 236
Figure 76 – Sequence diagram of fragmentation with retries using transport class 6. 237
Figure 77 – Sequence diagram of two fragments using transport class 6 . 237
Figure 78 – Sequence diagram of aborted fragmented sequence using transport
class 6 .238
Figure 79 – Class 6 client STD .239
Figure 80 – Class 6 server STD .242
Figure 81 – Data flow diagram for a link producer and consumer . 247
Figure 82 – State transition diagram for a link producer . 250
Figure 83 – State transition diagram for a link consumer. 251
Figure 84 – DS field in the IP header .261
Figure 85 – IEEE 802.1Q tagged frame.261

Table 1 – Get_Attribute_All response service rules .26
Table 2 – Example class level object/service specific response data of
Get_Attribute_All .26
Table 3 – Example Get_Attribute_All data array method .27
Table 4 – Set_Attribute_All request service rules .28
Table 5 – Example Set_Attribute_All attribute ordering method.28
Table 6 – Example Set_Attribute_All data array method.28
Table 7 – State event matrix format .30
Table 8 – Example state event matrix .30
Table 9 – UCMM_PDU header format .33
Table 10 – UCMM command codes.33
Table 11 – Transport class 0 header.34
Table 12 – Transport class 1 header.35
Table 13 – Transport class 2 header.35
Table 14 – Transport class 3 header.35
Table 15 – Classes 4 to 6 header format.35
Table 16 – Real-time data header – exclusive owner .36
Table 17 – Real-time data header– redundant owner .37
Table 18 – Forward_Open request format .39
Table 19 – Forward_Open_Good response format .40
Table 20 – Forward_Open_Bad response format .40
Table 21 – Large_Forward_Open request format .41
Table 22 – Large_Forward_Open_Good response format .42
Table 23 – Large_Forward_Open_Bad response format.42
Table 24 – Forward_Close request format .43
Table 25 – Forward_Close_Good response format.43
Table 26 – Forward_Close_Bad response format.44
Table 27 – Unconnected_Send request format.45
Table 28 – Unconnected_Send_Good response format.45

---------------------- Page: 7 ----------------------
– 6 – 61158-6-2 © IEC:2010(E)
Table 29 – Unconnected_Send_Bad response format .46
Table 30 – Get_Connection_Data request format.46
Table 31 – Get_Connection_Data response format .47
Table 32 – Search_Connection_Data request format .47
Table 33 – Get_Object_Owner request format .48
Table 34 – Forward_Open_Good response format .48
Table 35 – Time-out multiplier.51
Table 36 – Time tick units .51
Table 37 – Selection of connection ID.55
Table 38 – Transport class, trigger and Is_Server format .55
Table 39 – MR_Request_Header format .56
Table 40 – MR_Response_Header format.56
Table 41 – Structure of Get_Attribute_All_ResponsePDU body.57
Table 42 – Structure of Set_Attribute_All_RequestPDU body.57
Table 43 – Structure of Get_Attribute_List_RequestPDU body.57
Table 44 – Structure of Get_Attribute_List_ResponsePDU body .57
Table 45 – Structure of Set_Attribute_List_RequestPDU body .57
Table 46 – Structure of Set_Attribute_List_ResponsePDU body.58
Table 47 – Structure of Reset_RequestPDU body.58
Table 48 – Structure of Reset_ResponsePDU body .58
Table 49 – Structure of Start_RequestPDU body .58
Table 50 – Structure of Start_ResponsePDU body.58
Table 51 – Structure of Stop_RequestPDU body.59
Table 52 – Structure of Stop_ResponsePDU body .59
Table 53 – Structure of Create_RequestPDU body .59
Table 54 – Structure of Create_ResponsePDU body.59
Table 55 – Structure of Delete_RequestPDU body.59
Table 56 – Structure of Delete_ResponsePDU body .59
Table 57 – Structure of Get_Attribute_Single_ResponsePDU body .60
Table 58 – Structure of Set_Attribute_Single_RequestPDU body .60
Table 59 – Structure of Set_Attribute_Single_ResponsePDU body .60
Table 60 – Structure of Find_Next_Object_Instance_RequestPDU body .60
Table 61 – Structure of Find_Next_Object_Instance_ResponsePDU body .60
Table 62 – Structure of Apply_Attributes_RequestPDU body .61
Table 63 – Structure of Apply_Attributes_ResponsePDU body.61
Table 64 – Structure of Save_RequestPDU body .61
Table 65 – Structure of Save_ResponsePDU body .61
Table 66 – Structure of Restore_RequestPDU body.61
Table 67 – Structure of Restore_ResponsePDU body .61
Table 68 – Structure of Group_Sync_RequestPDU body.62
Table 69 – Structure of Group_Sync_ResponsePDU body .62
Table 70 – Identity object class attributes .62
Table 71 – Identity object instance attributes .62

---------------------- Page: 8 ----------------------
61158-6-2 © IEC:2010(E) – 7 –
Table 72 – Identity object bit definitions for status instance attribute.63
Table 73 – Bits 4 – 7 of status instance attribute.64
Table 74 – Class level object/service specific response data of Get_Attribute_All .64
Table 75 – Instance level object/service specific response data of Get_Attribute_All .65
Table 76 – Modified instance level object/service specific response data of
Get_Attribute_All .65
Table 77 – Object-specific parameter for Reset .66
Table 78 – Message Router object class attributes .66
Table 79 – Message Router object instance attributes .66
Table 80 – Class level object/service specific response data of Get_Attribute_All .67
Table 81 – Instance level object/service specific response data of Get_Attribute_All .67
Table 82 – Assembly object class attributes.
...

IEC 61158-6-2
®

Edition 2.0 2010-08
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE


Industrial communication networks – Fieldbus specifications –
Part 6-2: Application layer protocol specification – Type 2 elements

Réseaux de communication industriels – Spécifications des bus de terrain –
Partie 6-2: Spécification de protocole de la couche application – Eléments de
Type 2

IEC 61158-6-2:2010

---------------------- Page: 1 ----------------------
THIS PUBLICATION IS COPYRIGHT PROTECTED
Copyright © 2010 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.


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

IEC Central Office Tel.: [phone]
3, rue de Varembé Fax: [phone]
CH-1211 Geneva 20 [e-mail]
Switzerland www.iec.ch

About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.

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

Useful links:

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

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


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

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

Liens utiles:

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

---------------------- Page: 2 ----------------------
IEC 61158-6-2

®

Edition 2.0 2010-08




INTERNATIONAL



STANDARD




NORME



INTERNATIONALE











Industrial communication networks – Fieldbus specifications –

Part 6-2: Application layer protocol specification – Type 2 elements




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

Partie 6-2: Spécification de protocole de la couche application – Eléments de

Type 2















INTERNATIONAL

ELECTROTECHNICAL

COMMISSION


COMMISSION

ELECTROTECHNIQUE

PRICE CODE
INTERNATIONALE

XH
CODE PRIX


ICS 25.040.40; 35.100.70; 35.110 ISBN 978-2-83220-125-1



Warning! Make sure that you obtained this publication from an authorized distributor.

Attention! Veuillez vous assurer que vous avez obtenu cette publication via un distributeur agréé.

® Registered trademark of the International Electrotechnical Commission
Marque déposée de la Commission Electrotechnique Internationale

---------------------- Page: 3 ----------------------
– 2 – 61158-6-2  IEC:2010
CONTENTS
FOREWORD . 12
INTRODUCTION . 14
1 Scope . 15
1.1 General . 15
1.2 Specifications . 15
1.3 Conformance . 16
2 Normative references . 16
3 Terms, definitions, symbols, abbreviations and conventions . 17
3.1 Terms and definitions from other ISO/IEC standards . 17
3.2 Terms and definitions from IEC 61158-5-2. 18
3.3 Additional terms and definitions . 18
3.4 Abbreviations and symbols . 24
3.5 Conventions . 24
3.6 Conventions used in state machines . 29
4 Abstract syntax . 30
4.1 FAL PDU abstract syntax . 30
4.2 Data abstract syntax specification . 120
4.3 Encapsulation abstract syntax . 124
5 Transfer syntax . 138
5.1 Compact encoding . 138
5.2 Data type reporting . 145
6 Structure of FAL protocol state machines . 150
7 AP-Context state machine . 150
7.1 Overview . 150
7.2 Connection object state machine . 150
8 FAL service protocol machine (FSPM) . 160
8.1 General . 160
8.2 Primitive definitions . 160
8.3 Parameters of primitives . 164
8.4 FSPM state machines . 165
9 Application relationship protocol machines (ARPMs) . 166
9.1 General . 166
9.2 Connection-less ARPM (UCMM) . 166
9.3 Connection-oriented ARPMs (transports) . 176
10 DLL mapping protocol machine 1 (DMPM 1) . 247
10.1 General . 247
10.2 Link producer . 247
10.3 Link consumer . 248
10.4 Primitive definitions . 248
10.5 DMPM state machine . 250
10.6 Data-link Layer service selection . 251
11 DLL mapping protocol machine 2 (DMPM 2) . 251
11.1 General . 251
11.2 Mapping of UCMM PDUs . 252
11.3 Mapping of transport class 0 and class 1 PDUs . 257

---------------------- Page: 4 ----------------------
61158-6-2  IEC:2010 – 3 –
11.4 Mapping of transport class 2 and class 3 PDU’s . 258
11.5 Mapping of transport classes 4 to 6 . 258
11.6 IGMP Usage . 258
11.7 Quality of Service (QoS) for CP 2/2 messages . 259
11.8 Management of an encapsulation session . 262
12 DLL mapping protocol machine 3 (DMPM 3) . 263
Bibliography . 264

Figure 1 – Attribute table format and terms . 25
Figure 2 – Service request/response parameter . 25
Figure 3 – Example of an STD . 29
Figure 4 – Network connection parameters . 49
Figure 5 – Time tick . 51
Figure 6 – Connection establishment time-out . 53
Figure 7 – Transport Class Trigger attribute . 86
Figure 8 – CP2/3_initial_comm_characteristics attribute format . 89
Figure 9 – Segment type . 97
Figure 10 – Port segment . 98
Figure 11 – Logical segment encoding . 100
Figure 12 – Extended network segment . 104
Figure 13 – Encapsulation message . 124
Figure 14 – FixedLengthBitString compact encoding bit placement rules . 142
Figure 15 – Example compact encoding of a SWORD FixedLengthBitString . 142
Figure 16 – Example compact encoding of a WORD FixedLengthBitString . 142
Figure 17 – Example compact encoding of a DWORD FixedLengthBitString . 143
Figure 18 – Example compact encoding of a LWORD FixedLengthBitString . 143
Figure 19 – Example 2 of formal encoding of a structure type specification . 147
Figure 20 – Example of abbreviated encoding of a structure type specification . 148
Figure 21 – Example 1 of formal encoding of an array type specification . 148
Figure 22 – Example 2 of formal encoding of an array type specification . 149
Figure 23 – Example 1 of abbreviated encoding of an array type specification . 149
Figure 24 – Example 2 of abbreviated encoding of an array type specification . 150
Figure 25 – I/O Connection object state transition diagram . 151
Figure 26 –Bridged Connection object state transition diagram . 155
Figure 27 – Explicit Messaging Connection object state transition diagram . 157
Figure 28 – State transition diagram of UCMM client . 169
Figure 29 – State transition diagram of high–end UCMM server . 170
Figure 30 – State transition diagram of low–end UCMM server . 172
Figure 31 – Sequence diagram for a UCMM with one outstanding message . 174
Figure 32 – Sequence diagram for a UCMM with multiple outstanding messages . 175
Figure 33 – TPDU buffer . 176
Figure 34 – Data flow diagram using a client transport class 0 and server transport
class 0 . 179
Figure 35 – Sequence diagram of data transfer using transport class 0. 179

---------------------- Page: 5 ----------------------
– 4 – 61158-6-2  IEC:2010
Figure 36 – Class 0 client STD . 180
Figure 37 – Class 0 server STD . 181
Figure 38 – Data flow diagram using client transport class 1 and server transport
class 1 . 182
Figure 39 – Sequence diagram of data transfer using client transport class 1 and
server transport class 1 . 183
Figure 40 – Class 1 client STD . 185
Figure 41 – Class 1 server STD . 186
Figure 42 – Data flow diagram using client transport class 2 and server transport
class 2 . 188
Figure 43 – Diagram of data transfer using client transport class 2 and server transport
class 2 without returned data . 189
Figure 44 – Sequence diagram of data transfer using client transport class 2 and
server transport class 2 with returned data . 190
Figure 45 – Class 2 client STD . 191
Figure 46 – Class 2 server STD . 193
Figure 47 – Data flow diagram using client transport class 3 and server transport
class 3 . 196
Figure 48 – Sequence diagram of data transfer using client transport class 3 and
server transport class 3 without returned data . 197
Figure 49 – Sequence diagram of data transfer using client transport class 3 and
server transport class 3 with returned data . 198
Figure 50 – Class 3 client STD . 200
Figure 51 – Class 3 server STD . 203
Figure 52 – Data flow diagram using transport classes 4 and 5 . 205
Figure 53 – Sequence diagram of message exchange using transport classes 4 and 5 . 206
Figure 54 – Sequence diagram of messages overwriting each other . 207
Figure 55 – Sequence diagram of queued message exchange using transport classes
4 and 5 . 208
Figure 56 – Sequence diagram of retries using transport classes 4 and 5 . 208
Figure 57 – Sequence diagram of idle traffic using transport classes 4 and 5 . 209
Figure 58 – Classes 4 and 5 basic structure . 210
Figure 59 – Class 6 basic structure . 211
Figure 60 – Classes 4 to 6 general STD . 212
Figure 61 – Class 4 sender STD . 214
Figure 62 – Class 4 receiver STD . 217
Figure 63 – Sequence diagram of three fragments using transport class 5 . 220
Figure 64 – Sequence diagram of fragmentation with retries using transport class 5 . 221
Figure 65 – Sequence diagram of two fragments using transport class 5 . 221
Figure 66 – Sequence diagram of aborted message using transport class 5 . 222
Figure 67 – Class 5 sender STD . 223
Figure 68 – Class 5 receiver STD . 226
Figure 69 – Data flow diagram for transport class 6 . 231
Figure 70 – Sequence diagram of message exchange using transport class 6 . 233
Figure 71 – Sequence diagram of retries using transport class 6 . 233
Figure 72 – Sequence diagram of idle traffic using transport class 6 . 234

---------------------- Page: 6 ----------------------
61158-6-2  IEC:2010 – 5 –
Figure 73 – Sequence diagram of request overwriting null . 235
Figure 74 – Sequence diagram of response overwriting ACK of null . 235
Figure 75 – Sequence diagram of three fragments using transport class 6 . 236
Figure 76 – Sequence diagram of fragmentation with retries using transport class 6 . 237
Figure 77 – Sequence diagram of two fragments using transport class 6 . 237
Figure 78 – Sequence diagram of aborted fragmented sequence using transport
class 6 . 238
Figure 79 – Class 6 client STD . 239
Figure 80 – Class 6 server STD . 242
Figure 81 – Data flow diagram for a link producer and consumer . 247
Figure 82 – State transition diagram for a link producer . 250
Figure 83 – State transition diagram for a link consumer . 251
Figure 84 – DS field in the IP header . 261
Figure 85 – IEEE 802.1Q tagged frame . 261

Table 1 – Get_Attribute_All response service rules . 26
Table 2 – Example class level object/service specific response data of
Get_Attribute_All . 26
Table 3 – Example Get_Attribute_All data array method . 27
Table 4 – Set_Attribute_All request service rules . 28
Table 5 – Example Set_Attribute_All attribute ordering method . 28
Table 6 – Example Set_Attribute_All data array method . 28
Table 7 – State event matrix format . 30
Table 8 – Example state event matrix . 30
Table 9 – UCMM_PDU header format . 33
Table 10 – UCMM command codes . 33
Table 11 – Transport class 0 header . 34
Table 12 – Transport class 1 header . 35
Table 13 – Transport class 2 header . 35
Table 14 – Transport class 3 header . 35
Table 15 – Classes 4 to 6 header format . 35
Table 16 – Real-time data header – exclusive owner . 36
Table 17 – Real-time data header– redundant owner . 37
Table 18 – Forward_Open request format . 39
Table 19 – Forward_Open_Good response format . 40
Table 20 – Forward_Open_Bad response format . 40
Table 21 – Large_Forward_Open request format . 41
Table 22 – Large_Forward_Open_Good response format . 42
Table 23 – Large_Forward_Open_Bad response format . 42
Table 24 – Forward_Close request format . 43
Table 25 – Forward_Close_Good response format . 43
Table 26 – Forward_Close_Bad response format . 44
Table 27 – Unconnected_Send request format . 45
Table 28 – Unconnected_Send_Good response format . 45

---------------------- Page: 7 ----------------------
– 6 – 61158-6-2  IEC:2010
Table 29 – Unconnected_Send_Bad response format . 46
Table 30 – Get_Connection_Data request format . 46
Table 31 – Get_Connection_Data response format . 47
Table 32 – Search_Connection_Data request format . 47
Table 33 – Get_Object_Owner request format . 48
Table 34 – Forward_Open_Good response format . 48
Table 35 – Time-out multiplier . 51
Table 36 – Time tick units . 51
Table 37 – Selection of connection ID . 55
Table 38 – Transport class, trigger and Is_Server format . 55
Table 39 – MR_Request_Header format . 56
Table 40 – MR_Response_Header format . 56
Table 41 – Structure of Get_Attribute_All_ResponsePDU body . 57
Table 42 – Structure of Set_Attribute_All_RequestPDU body . 57
Table 43 – Structure of Get_Attribute_List_RequestPDU body . 57
Table 44 – Structure of Get_Attribute_List_ResponsePDU body . 57
Table 45 – Structure of Set_Attribute_List_RequestPDU body . 57
Table 46 – Structure of Set_Attribute_List_ResponsePDU body . 58
Table 47 – Structure of Reset_RequestPDU body . 58
Table 48 – Structure of Reset_ResponsePDU body . 58
Table 49 – Structure of Start_RequestPDU body . 58
Table 50 – Structure of Start_ResponsePDU body . 58
Table 51 – Structure of Stop_RequestPDU body . 59
Table 52 – Structure of Stop_ResponsePDU body . 59
Table 53 – Structure of Create_RequestPDU body . 59
Table 54 – Structure of Create_ResponsePDU body . 59
Table 55 – Structure of Delete_RequestPDU body . 59
Table 56 – S
...