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