BS EN IEC 61158-6-2:2019
$215.11
Industrial communication networks. Fieldbus specifications – Application layer protocol specification. Type 2 elements
| Published By | Publication Date | Number of Pages |
| BSI | 2019 | 278 |
1.1 General
The Fieldbus Application Layer (FAL) provides user programs with a means to access the fieldbus communication environment. In this respect, the FAL can be viewed as a “window between corresponding application programs.”
This part of IEC 61158 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.
This International Standard specifies interactions between remote applications and defines the externally visible behavior provided by the Type 2 fieldbus application layer in terms of
-
the formal abstract syntax defining the application layer protocol data units conveyed between communicating application entities;
-
the transfer syntax defining encoding rules that are applied to the application layer protocol data units;
-
the application context state machine defining the application service behavior visible between communicating application entities;
-
the application relationship state machines defining the communication behavior visible between communicating application entities.
The purpose of this document is to define the protocol provided to
-
define the wire-representation of the service primitives defined in IEC 61158-5-2, and
-
define the externally visible behavior associated with their transfer.
This document specifies the protocol of the Type 2 fieldbus application layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI application layer structure (ISO/IEC 9545).
1.2 Specifications
The principal objective of this document is to specify the syntax and behavior of the application layer protocol that conveys the application layer services defined in IEC 61158-5-2.
A secondary objective is to provide migration paths from previously-existing industrial communications protocols.
1.3 Conformance
This document does not specify individual implementations or products, nor does it constrain the implementations of application layer entities within industrial automation systems. Conformance is achieved through implementation of this application layer protocol specification.
PDF Catalog
| PDF Pages | PDF Title |
|---|---|
| 2 | National foreword |
| 5 | Annex ZA(normative)Normative references to international publicationswith their corresponding European publications |
| 7 | CONTENTS |
| 19 | FOREWORD |
| 21 | INTRODUCTION |
| 22 | 1 Scope 1.1 General 1.2 Specifications |
| 23 | 1.3 Conformance 2 Normative references |
| 25 | 3 Terms, definitions, symbols, abbreviated terms and conventions 3.1 Terms and definitions from other ISO/IEC standards 3.1.1 Terms and definitions from ISO/IEC 74981 |
| 26 | 3.1.2 Terms and definitions from ISO/IEC 9545 3.1.3 Terms and definitions from ISO/IEC 88241 |
| 27 | 3.1.4 Terms and definitions from ISO/IEC 88251 3.2 Terms and definitions from IEC 6115852 3.3 Additional terms and definitions |
| 34 | 3.4 Abbreviated terms and symbols 3.5 Conventions 3.5.1 General concept |
| 35 | 3.5.2 Attribute specification 3.5.3 Common services Figures Figure 1 – Attribute table format and terms Figure 2 – Service request/response parameter |
| 36 | Tables Table 1 – Get_Attributes_All response service rules Table 2 – Example class level object/service specific response data of Get_Attributes_All |
| 37 | Table 3 – Example Get_Attributes_All data array method |
| 38 | Table 4 – Set_Attributes_All request service rules Table 5 – Example Set_Attributes_All attribute ordering method Table 6 – Example Set_Attributes_All data array method |
| 39 | 3.5.4 State machine conventions Figure 3 – Example of an STD |
| 40 | 4 Abstract syntax 4.1 FAL PDU abstract syntax 4.1.1 General Table 7 – State event matrix format Table 8 – Example state event matrix |
| 41 | 4.1.2 PDU structure |
| 43 | 4.1.3 UCMM_PDUs |
| 44 | Table 9 – UCMM_PDU header format Table 10 – UCMM command codes |
| 45 | 4.1.4 Transport_Headers Table 11 – Transport class 0 header Table 12 – Transport class 1 header Table 13 – Transport class 2 header Table 14 – Transport class 3 header |
| 46 | Table 15 – Real-time data header – exclusive owner Table 16 – Real-time data header– redundant owner |
| 48 | 4.1.5 CM_PDUs |
| 51 | Table 17 – Forward_Open request format Table 18 – Forward_Open_Good response format |
| 52 | Table 19 – Forward_Open_Bad response format |
| 53 | Table 20 – Large_Forward_Open request format Table 21 – Large_Forward_Open_Good response format |
| 54 | Table 22 – Large_Forward_Open_Bad response format |
| 55 | Table 23 – Forward_Close request format Table 24 – Forward_Close_Good response format |
| 56 | Table 25 – Forward_Close_Bad response format Table 26 – Unconnected_Send request format |
| 57 | Table 27 – Unconnected_Send_Good response format |
| 58 | Table 28 – Unconnected_Send_Bad response format |
| 59 | Table 29 – Unconnected_Send request format (modified) Table 30 – Unconnected_Send_Good response format (modified) |
| 60 | Table 31 – Unconnected_Send_Bad response format (modified) Table 32 – Get_Connection_Data request format Table 33 – Get_Connection_Data response format |
| 61 | Table 34 – Search_Connection_Data request format |
| 62 | 4.1.6 CM PDU components Table 35 – Get_Connection_Owner request format Table 36 – Get_Connection_Owner response format |
| 63 | Figure 4 – Network connection parameters |
| 65 | Table 37 – Time-out multiplier |
| 66 | Figure 5 – Priority/Tick_time bit definition Table 38 – Tick time units |
| 70 | Table 39 – Encoded application path ordering |
| 71 | 4.1.7 MR headers Table 40 – Transport class, trigger and Is_Server format Table 41 – MR_Request_Header format |
| 72 | 4.1.8 OM_Service_PDU Table 42 – MR_Response_Header format Table 43 – Structure of Get_Attributes_All_ResponsePDU body |
| 73 | Table 44 – Structure of Set_Attributes_All_RequestPDU body Table 45 – Structure of Get_Attribute_List_RequestPDU body Table 46 – Structure of Get_Attribute_List_ResponsePDU body Table 47 – Structure of Set_Attribute_List_RequestPDU body |
| 74 | Table 48 – Structure of Set_Attribute_List_ResponsePDU body Table 49 – Structure of Reset_RequestPDU body Table 50 – Structure of Reset_ResponsePDU body Table 51 – Structure of Start_RequestPDU body Table 52 – Structure of Start_ResponsePDU body |
| 75 | Table 53 – Structure of Stop_RequestPDU body Table 54 – Structure of Stop_ResponsePDU body Table 55 – Structure of Create_RequestPDU body Table 56 – Structure of Create_ResponsePDU body Table 57 – Structure of Delete_RequestPDU body Table 58 – Structure of Delete_ResponsePDU body |
| 76 | Table 59 – Structure of Get_Attribute_Single_ResponsePDU body Table 60 – Structure of Set_Attribute_Single_RequestPDU body Table 61 – Structure of Set_Attribute_Single_ResponsePDU body Table 62 – Structure of Find_Next_Object_Instance_RequestPDU body |
| 77 | Table 63 – Structure of Find_Next_Object_Instance_ResponsePDU body Table 64 – Structure of Apply_Attributes_RequestPDU body Table 65 – Structure of Apply_Attributes_ResponsePDU body Table 66 – Structure of Save_RequestPDU body Table 67 – Structure of Save_ResponsePDU body |
| 78 | Table 68 – Structure of Restore_RequestPDU body Table 69 – Structure of Restore_ResponsePDU body Table 70 – Structure of Get_Member_ResponsePDU body Table 71 – Structure of Set_Member_RequestPDU body Table 72 – Structure of Set_Member_ResponsePDU body |
| 79 | Table 73 – Structure of Insert_Member_RequestPDU body Table 74 – Structure of Insert_Member_ResponsePDU body Table 75 – Structure of Remove_Member_ResponsePDU body |
| 80 | Figure 6 – Member ID/EX description (WORD) Table 76 – Common structure of _Member_RequestPDU body (basic format) Table 77 – Common structure of _Member_ResponsePDU body (basic format) |
| 81 | Table 78 – Common structure of _Member_RequestPDU body (extended format) Table 79 – Common structure of _Member_ResponsePDU body (extended format) Table 80 – Extended Protocol ID |
| 82 | Table 81 – Structure of _Member_RequestPDU body (Multiple Sequential Members) Table 82 – Structure of _Member_ResponsePDU body (Multiple Sequential Members) |
| 83 | Table 83 – Structure of _Member_RequestPDU body (International String Selection) Table 84 – Structure of _Member_ResponsePDU body (International String Selection) Table 85 – Structure of Group_Sync_RequestPDU body Table 86 – Structure of Group_Sync_ResponsePDU body |
| 84 | Table 87 – Structure of Multiple_Service_Packet_RequestPDU body Table 88 – Structure of Multiple_Service_Packet_ResponsePDU body |
| 85 | Table 89 – Identity object class attributes Table 90 – Identity object instance attributes |
| 86 | Table 91 – Identity object bit definitions for status instance attribute |
| 87 | Table 92 – Default values for extended device status field (bits 4 to 7)of status instance attribute Table 93 – Identity object bit definitions for protection mode instance attribute Table 94 – Class level object/service specific response data of Get_Attributes_All |
| 88 | Table 95 – Instance level object/service specific response data of Get_Attributes_All Table 96 – Object-specific request parameter for Reset |
| 89 | Table 97 – Reset service parameter values Table 98 – Communication link attributes that shall be preserved Table 99 – Structure of Flash_LEDs_RequestPDU body |
| 90 | Table 100 – Message Router object class attributes Table 101 – Message Router object instance attributes Table 102 – Class level object/service specific response data of Get_Attributes_All |
| 91 | Table 103 – Instance level object/service specific response data of Get_Attributes_All Table 104 – Structure of Symbolic_Translation_RequestPDU body Table 105 – Structure of Symbolic_Translation_ResponsePDU body Table 106 – Object specific status for Symbolic_Translation service |
| 92 | Table 107 – Assembly object class attributes Table 108 – Assembly object instance attributes |
| 93 | Table 109 – Assembly Instance ID ranges Table 110 – Acknowledge Handler object class attributes |
| 94 | Table 111 – Acknowledge Handler object instance attributes Table 112 – Structure of Add_AckData_Path_RequestPDU body Table 113 – Structure of Remove_AckData_Path_RequestPDU body |
| 95 | Table 114 – Time Sync object class attributes Table 115 – Time Sync object instance attributes |
| 99 | Table 116 – ClockIdentity encoding for different network implementations Table 117 – ClockClass values Table 118 – TimeAccuracy values |
| 100 | Table 119 – TimePropertyFlags bit values Table 120 – TimeSource values |
| 101 | Table 121 – Types of Clock Table 122 – Network protocol to PortPhysicalAddressInfo mapping |
| 102 | Table 123 – Parameter object class attributes Table 124 – Parameter Class Descriptor bit values |
| 103 | Table 125 – Parameter object instance attributes |
| 104 | Table 126 – Semantics of Descriptor Instance attribute Table 127 – Descriptor Scaling bits usage |
| 105 | Table 128 – Minimum and Maximum Value semantics |
| 106 | Table 129 – Scaling Formula attributes Table 130 – Scaling links |
| 107 | Table 131 – Class level object/service specific response data of Get_Attributes_All Table 132 – Instance level object/service specific response dataof Get_Attributes_All (Parameter object stub) |
| 108 | Table 133 – Instance level object/service specific response dataof Get_Attributes_All (full Parameter object) |
| 109 | Table 134 – Structure of Get_Enum_String_RequestPDU body Table 135 – Structure of Get_Enum_String_ResponsePDU body Table 136 – Enumerated strings Type versus Parameter data type |
| 110 | Table 137 – Connection Manager object class attributes Table 138 – Connection Manager object instance attributes |
| 111 | Table 139 – Class level object/service specific response data of Get_Attributes_All Table 140 – Instance level object/service specific response data of Get_Attributes_All |
| 112 | Table 141 – Instance level object/service specific request data of Set_Attributes_All Table 142 – Connection object class attributes |
| 113 | Table 143 – Connection object instance attributes |
| 114 | Table 144 – Values assigned to the state attribute |
| 115 | Figure 7 – Transport Class Trigger attribute Table 145 – Values assigned to the instance_type attribute |
| 116 | Table 146 – Possible values within Direction Bit Table 147 – Possible values within Production Trigger Bits |
| 117 | Table 148 – Possible values within Transport Class Bits Table 149 – TransportClass_Trigger attribute values summary |
| 118 | Table 150 – Transport Class 0 client behavior summary Table 151 – Transport Class 1, 2 and 3 client behavior summary |
| 119 | Figure 8 – CP2/3_initial_comm_characteristics attribute format Table 152 – Values defined for the CP2/3_produced_connection_id attribute Table 153 – Values defined for the CP2/3_consumed_connection_id attribute |
| 120 | Table 154 – Values for the Initial Production Characteristics nibble |
| 121 | Table 155 – Values for the Initial Consumption Characteristics nibble |
| 124 | Table 156 – Values for the watchdog_timeout_action |
| 126 | Table 157 – Structure of Connection_Bind_RequestPDU body Table 158 – Object specific status for Connection_Bind service Table 159 – Structure of Producing_Application_Lookup_RequestPDU body |
| 127 | 4.1.9 Message and connection paths Table 160 – Structure of Producing_Application_Lookup_ResponsePDU body Table 161 – Producing_Application_Lookup Service status codes |
| 128 | Figure 9 – Segment type |
| 129 | Figure 10 – Port segment Table 162 – Possible port segment examples |
| 130 | Table 163 – TCP/IP link address examples |
| 131 | Figure 11 – Logical segment encoding Table 164 – Extended Logical Type |
| 133 | Table 165 – Electronic key segment format |
| 134 | Table 166 – Logical segments examples |
| 135 | Table 167 – Network segments |
| 137 | Figure 12 – Extended network segment Table 168 – Extended subtype definitions |
| 138 | Figure 13 – Symbolic segment encoding Table 169 – Symbolic segment examples |
| 139 | Table 170 – Data segment Table 171 – ANSI_Extended_Symbol segment |
| 142 | 4.1.10 Class, attribute and service codes Table 172 – Addressing categories Table 173 – Class code ID ranges |
| 143 | Table 174 – Attribute ID ranges Table 175 – Service code ranges |
| 144 | Table 176 – Class codes |
| 145 | Table 177 – Reserved class attributes for all object class definitions Table 178 – Common services list |
| 146 | Table 179 – Identity object specific services list Table 180 – Message Router object specific services list Table 181 – Acknowledge Handler object specific services list Table 182 – Parameter object specific services list |
| 147 | Table 183 – Services specific to Connection Manager Table 184 – Services specific to Connection object |
| 148 | 4.1.11 Error codes Table 185 – Device type numbering |
| 149 | Table 186 – Connection Manager service request error codes |
| 158 | Table 187 – General status codes |
| 160 | Table 188 – Extended status code for a general status of "Key Failure in path |
| 161 | Table 189 – Identity object status codes |
| 162 | 4.2 Data abstract syntax specification 4.2.1 Transport format specification 4.2.2 Abstract syntax notation |
| 163 | 4.2.3 Control network data specification |
| 165 | 4.2.4 Data type specification / dictionaries |
| 167 | 4.3 Encapsulation abstract syntax 4.3.1 Encapsulation protocol Figure 14 – Encapsulation message |
| 168 | Table 190 – Encapsulation header Table 191 – Encapsulation command codes |
| 170 | 4.3.2 Command descriptions Table 192 – Encapsulation status codes |
| 171 | Table 193 – Nop request encapsulation header Table 194 – RegisterSession request encapsulation header |
| 172 | Table 195 – RegisterSession request data portion Table 196 – RegisterSession reply encapsulation header |
| 173 | Table 197 – RegisterSession reply data portion (successful) Table 198 – UnRegisterSession request encapsulation header |
| 174 | Table 199 – ListServices request encapsulation header Table 200 – ListServices reply encapsulation header |
| 175 | Table 201 – ListServices reply data portion (successful) Table 202 – Communications capability flags |
| 176 | Table 203 – ListIdentity request encapsulation header |
| 177 | Table 204 – ListIdentity reply encapsulation header Table 205 – ListIdentity reply data portion (successful) |
| 178 | Table 206 – CPF 2 identity item |
| 179 | Table 207 – ListInterfaces request encapsulation header Table 208 – ListInterfaces reply encapsulation header |
| 180 | Table 209 – SendRRData request encapsulation header Table 210 – SendRRData request data portion |
| 181 | Table 211 – SendRRData reply encapsulation header Table 212 – SendUnitData request encapsulation header Table 213 – SendUnitData request data portion |
| 182 | 4.3.3 Common packet format Table 214 – Common packet format Table 215 – CPF item format Table 216 – Item Type ID numbers |
| 183 | Table 217 – Null address item Table 218 – Connected address item |
| 184 | Table 219 – Sequenced address item Table 220 – Unconnected data item Table 221 – Connected data item |
| 185 | Table 222 – Sockaddr info items |
| 186 | 5 Transfer syntax 5.1 Compact encoding 5.1.1 Encoding rules Table 223 – Usage of CPF items |
| 187 | 5.1.2 Encoding constraints 5.1.3 Examples Table 224 – BOOLEAN encoding Table 225 – Example compact encoding of a BOOL value Table 226 – Encoding of SignedInteger values Table 227 – Example compact encoding of a SignedInteger value |
| 188 | Table 228 – UnsignedInteger values Table 229 – Example compact encoding of an UnsignedInteger Table 230 – FixedLengthReal values Table 231 – Example compact encoding of a REAL value Table 232 – Example compact encoding of a LREAL value |
| 189 | Table 233 – FixedLengthReal values Table 234 – STRING value Table 235 – STRING2 value Table 236 – STRINGN value |
| 190 | Figure 15 – FixedLengthBitString compact encoding bit placement rules Table 237 – SHORT_STRING value Table 238 – Example compact encoding of a STRING value Table 239 – Example compact encoding of STRING2 value Table 240 – SHORT_STRING type |
| 191 | Figure 16 – Example compact encoding of a SWORD FixedLengthBitString Figure 17 – Example compact encoding of a WORD FixedLengthBitString Figure 18 – Example compact encoding of a DWORD FixedLengthBitString Figure 19 – Example compact encoding of a LWORD FixedLengthBitString |
| 192 | Table 241 – Example compact encoding of a single dimensional ARRAY Table 242 – Example compact encoding of a multidimensional ARRAY |
| 193 | 5.2 Data type reporting 5.2.1 Object data representation Table 243 – Example compact encoding of a STRUCTURE |
| 194 | 5.2.2 Elementary data type reporting Table 244 – Identification codes and descriptions of elementary data types |
| 195 | 5.2.3 Constructed data type reporting Table 245 – Identification codes and descriptions of constructed data types Table 246 – Formal structure encoding definition |
| 196 | Figure 20 – Example 1 of formal encoding of a structure type specification Figure 21 – Example 2 of formal encoding of a structure type specification Table 247 – Formal structure with handles encoding definition |
| 197 | Figure 22 – Example 3 of formal encoding of a handle structure type specification Figure 23 – Example 4 of formal encoding of a handle structure type specification Table 248 – Abbreviated structure encoding definition |
| 198 | Figure 24 – Example 5 of abbreviated encoding of a structure type specification Table 249 – Formal array encoding definition |
| 199 | Figure 25 – Example 1 of formal encoding of an array type specification Figure 26 – Example 2 of formal encoding of an array type specification |
| 200 | Figure 27 – Example 1 of abbreviated encoding of an array type specification Figure 28 – Example 2 of abbreviated encoding of an array type specification Table 250 – Abbreviated array encoding definition |
| 201 | 6 Structure of FAL protocol state machines 7 AP-Context state machine 7.1 Overview 7.2 Connection object state machine 7.2.1 I/O Connection instance behavior Figure 29 – I/O Connection object state transition diagram |
| 202 | Table 251 – I/O Connection state event matrix |
| 205 | 7.2.2 Bridged Connection instance behavior Figure 30 – Bridged Connection object state transition diagram Table 252 – Bridged Connection state event matrix |
| 206 | 7.2.3 Explicit Messaging Connection instance behavior |
| 207 | Figure 31 – Explicit Messaging Connection object state transition diagram Table 253 – Explicit Messaging Connection state event matrix |
| 209 | 8 FAL service protocol machine (FSPM) 8.1 General 8.2 Primitive definitions |
| 210 | Table 254 – Primitives issued by FAL user to FSPM Table 255 – Primitives issued by FAL user to FSPM |
| 213 | Table 256 – Primitives issued by FSPM to FAL user |
| 214 | 8.3 Parameters of primitives 8.4 FSPM state machines Table 257 – Parameters used with primitives exchanged between FAL user and FSPM |
| 215 | 9 Application relationship protocol machines (ARPMs) 9.1 General 9.2 Connection-less ARPM (UCMM) 9.2.1 General 9.2.2 Primitive definitions |
| 216 | 9.2.3 Parameters of primitives Table 258 – Primitives issued by FSPM to ARPM Table 259 – Primitives issued by ARPM to FSPM Table 260 – Parameters used with primitives exchanged between FSPM and ARPM |
| 217 | 9.2.4 UCMM state machines Figure 32 – State transition diagram of UCMM client9 Table 261 – UCMM client states |
| 218 | Table 262 – State event matrix of UCMM client |
| 219 | Figure 33 – State transition diagram of high–end UCMM server Table 263 – High-end UCMM server states |
| 220 | Table 264 – State event matrix of high-end UCMM server |
| 221 | Figure 34 – State transition diagram of low–end UCMM server Table 265 – Low-end UCMM server states |
| 222 | 9.2.5 Examples of UCMM sequences Table 266 – State event matrix of low–end UCMM server |
| 223 | Figure 35 – Sequence diagram for a UCMM with one outstanding message |
| 224 | 9.2.6 Management UCMM Figure 36 – Sequence diagram for a UCMM with multiple outstanding messages |
| 225 | 9.3 Connection-oriented ARPMs (transports) 9.3.1 Transport PDU buffer 9.3.2 Transport classes Figure 37 – TPDU buffer Table 267 – Notification |
| 226 | 9.3.3 Common primitive definitions Table 268 – Transport classes Table 269 – Primitives issued by FSPM to ARPM |
| 227 | 9.3.4 Parameters of common primitives 9.3.5 Transport state machines – class 0 Table 270 – Primitives issued by ARPM to FSPM Table 271 – Parameters used with primitives exchanged between FSPM and ARPM |
| 228 | Figure 38 – Data flow diagram using a client transport class 0 and server transport class 0 Figure 39 – Sequence diagram of data transfer using transport class 0 |
| 229 | Figure 40 – Class 0 client STD Table 272 – Class 0 transport client states Table 273 – Class 0 client SEM |
| 230 | Figure 41 – Class 0 server STD Table 274 – Class 0 transport server states Table 275 – Class 0 server SEM |
| 231 | 9.3.6 Transport state machines – class 1 Figure 42 – Data flow diagram using client transport class 1and server transport class 1 |
| 232 | Figure 43 – Sequence diagram of data transferusing client transport class 1 and server transport class 1 |
| 233 | Table 276 – Class 1 transport client states |
| 234 | Figure 44 – Class 1 client STD Table 277 – Class 1 client SEM |
| 235 | Figure 45 – Class 1 server STD Table 278 – Class 1 transport server states |
| 236 | 9.3.7 Transport state machines – class 2 Table 279 – Class 1 server SEM |
| 237 | Figure 46 – Data flow diagram using client transport class 2and server transport class 2 |
| 238 | Figure 47 – Diagram of data transfer using client transport class 2and server transport class 2 without returned data |
| 239 | Figure 48 – Sequence diagram of data transfer using client transport class 2and server transport class 2 with returned data |
| 240 | Figure 49 – Class 2 client STD Table 280 – Class 2 transport client states |
| 241 | Table 281 – Class 2 client SEM |
| 242 | Figure 50 – Class 2 server STD Table 282 – Class 2 transport server states |
| 243 | Table 283 – Class 2 server SEM |
| 244 | 9.3.8 Transport state machines – class 3 |
| 245 | Figure 51 – Data flow diagram using client transport class 3and server transport class 3 |
| 246 | Figure 52 – Sequence diagram of data transfer using client transport class 3 and server transport class 3 without returned data |
| 247 | Figure 53 – Sequence diagram of data transfer using client transportclass 3 and server transport class 3 with returned data |
| 248 | Table 284 – Class 3 transport client states |
| 249 | Figure 54 – Class 3 client STD Table 285 – Class 3 client SEM |
| 251 | Table 286 – Class 3 transport server states |
| 252 | Figure 55 – Class 3 server STD |
| 253 | Table 287 – Class 3 server SEM |
| 254 | 9.3.9 Transport state machines – classes 4, 5, 6 9.3.10 Transport state machines – class 4 9.3.11 Transport state machines – class 5 9.3.12 Transport state machines – class 6 10 DLL mapping protocol machine 1 (DMPM 1) 10.1 General Figure 56 – Data flow diagram for a link producer and consumer |
| 255 | 10.2 Link producer 10.3 Link consumer 10.4 Primitive definitions 10.4.1 Primitives exchanged between DMPM and ARPM 10.4.2 Parameters of ARPM/DMPM primitives Table 288 – Primitives issued by ARPM to DMPM Table 289 – Primitives issued by DMPM to ARPM |
| 256 | 10.4.3 Primitives exchanged between data-link layer and DMPM 10.4.4 Parameters of DMPM/Data-link Layer primitives Table 290 – Parameters used with primitives exchanged between ARPM and DMPM Table 291 – Primitives exchanged between data-link layer and DMPM Table 292 – Parameters used with primitives exchanged between DMPM and Data-link |
| 257 | 10.4.5 Network connection ID Table 293 – Selection of connection ID |
| 258 | 10.5 DMPM state machine 10.5.1 DMPM states Figure 57 – State transition diagram for a link producer Table 294 – Link producer states Table 295 – State event matrix of link producer |
| 259 | 10.5.2 Functions used by DMPM 10.6 Data-link Layer service selection 11 DLL mapping protocol machine 2 (DMPM 2) 11.1 General Figure 58 – State transition diagram for a link consumer Table 296 – Link consumer states Table 297 – State event matrix of link consumer |
| 260 | 11.2 Mapping of UCMM PDUs 11.2.1 General Table 298 – UCMM request |
| 261 | 11.2.2 Common requirements for Connection Manager PDU’s Table 299 – UCMM reply |
| 262 | Table 300 – Network Connection ID selection |
| 263 | 11.2.3 Forward_open PDU for class 2 and class 3 connections 11.2.4 Forward_open for class 0 and class 1 connections |
| 264 | Table 301 – Sockaddr Info usage |
| 267 | 11.2.5 Forward_close Table 302 – Example multicast assignments |
| 268 | 11.3 Mapping of transport class 0 and class 1 PDUs 11.3.1 Class 0 and class 1 PDUs 11.3.2 No dependency on TCP connections 11.3.3 Class 0 and class 1 packet ordering Table 303 – UDP data format for class 0 and class 1 |
| 269 | 11.3.4 Screening incoming connected data 11.4 Mapping of transport class 2 and class 3 PDU’s |
| 270 | 11.5 Mapping of transport classes 4 to 6 11.6 IGMP Usage 11.6.1 Background (informative) Table 304 – Transport class 2 and class 3 connected data |
| 271 | 11.6.2 IGMP Membership Report messages 11.6.3 IGMP Leave Group messages |
| 272 | 11.7 Quality of Service (QoS) for CP 2/2 messages 11.7.1 Overview 11.7.2 DSCP format |
| 273 | 11.7.3 IEEE 802.1D/IEEE 802.Q format 11.7.4 Mapping CPF 2 traffic to DSCP and IEEE 802.1D Figure 59 – DS field in the IP header Figure 60 – IEEE 802.1Q tagged frame Table 305 – Default DSCP and IEEE 802.1D mapping |
| 274 | 11.7.5 CP 2/2 usage of DSCP 11.7.6 CP 2/2 usage of IEEE 802.1D/IEEE 802.1Q 11.7.7 User considerations with IEEE 802.1D/IEEE 802.1Q |
| 275 | 11.8 Management of an encapsulation session 11.8.1 Phases of an encapsulation session 11.8.2 Establishing a session 11.8.3 Terminating a session 11.8.4 Maintaining a session |
| 276 | 11.8.5 TCP connection management 12 DLL mapping protocol machine 3 (DMPM 3) |
| 277 | Bibliography |
