{"id":244183,"date":"2024-10-19T16:02:16","date_gmt":"2024-10-19T16:02:16","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bsi-pd-iec-pas-627342012\/"},"modified":"2024-10-25T11:01:00","modified_gmt":"2024-10-25T11:01:00","slug":"bsi-pd-iec-pas-627342012","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bsi-pd-iec-pas-627342012\/","title":{"rendered":"BSI PD IEC\/PAS 62734:2012"},"content":{"rendered":"
IEC\/PAS 62734:2012(E) defines the OSI layer specifications (e.g., PhL, DL, etc.), security specifications, and management (including network and device configuration) specifications for wireless devices serving application classes 1 through 5 and optionally class 0 for fixed, portable, and moving devices. It addresses the performance needs for periodic monitoring and process control where latencies on the order of 100 ms can be tolerated, with optional behavior for shorter latency.<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
4<\/td>\n | CONTENTS <\/td>\n<\/tr>\n | ||||||
26<\/td>\n | FOREWORD <\/td>\n<\/tr>\n | ||||||
28<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
30<\/td>\n | 1 Scope 2 Normative references <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | 3 Terms, definitions, abbreviated terms, acronyms and conventions 3.1 (N)-layer and other terms and definitions from the open systems interconnection basic reference model <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | 3.2 Other terms and definitions <\/td>\n<\/tr>\n | ||||||
51<\/td>\n | 3.3 Symbols <\/td>\n<\/tr>\n | ||||||
52<\/td>\n | 3.4 Abbreviated terms and acronyms <\/td>\n<\/tr>\n | ||||||
60<\/td>\n | 3.5 IEC service table conventions <\/td>\n<\/tr>\n | ||||||
61<\/td>\n | 4 Overview 4.1 General 4.2 Interoperability 4.3 Quality of service 4.4 Worldwide applicability <\/td>\n<\/tr>\n | ||||||
62<\/td>\n | 4.5 Network architecture <\/td>\n<\/tr>\n | ||||||
63<\/td>\n | Figures Figure 1 \u2013 Standard-compliant network <\/td>\n<\/tr>\n | ||||||
64<\/td>\n | 4.6 Network characteristics Figure 2 \u2013 Single protocol data unit Figure 3 \u2013 Full protocol data unit <\/td>\n<\/tr>\n | ||||||
69<\/td>\n | 5 Systems 5.1 General 5.2 Devices <\/td>\n<\/tr>\n | ||||||
71<\/td>\n | Figure 4 \u2013 Physical devices versus roles <\/td>\n<\/tr>\n | ||||||
75<\/td>\n | Figure 5 \u2013 Notional representation of device phases <\/td>\n<\/tr>\n | ||||||
76<\/td>\n | 5.3 Networks <\/td>\n<\/tr>\n | ||||||
77<\/td>\n | Figure 6 \u2013 Simple star topology <\/td>\n<\/tr>\n | ||||||
78<\/td>\n | Figure 7 \u2013 Simple hub-and-spoke topology <\/td>\n<\/tr>\n | ||||||
79<\/td>\n | Figure 8 \u2013 Mesh topology <\/td>\n<\/tr>\n | ||||||
80<\/td>\n | Figure 9 \u2013 Simple star-mesh topology <\/td>\n<\/tr>\n | ||||||
81<\/td>\n | Figure 10 \u2013 Network and DL subnet overlap <\/td>\n<\/tr>\n | ||||||
82<\/td>\n | Figure 11 \u2013 Network and DL subnet differ <\/td>\n<\/tr>\n | ||||||
83<\/td>\n | Figure 12 \u2013 Network with multiple gateways <\/td>\n<\/tr>\n | ||||||
84<\/td>\n | Figure 13 \u2013 Basic network with backup gateway <\/td>\n<\/tr>\n | ||||||
85<\/td>\n | Figure 14 \u2013 Network with backbone <\/td>\n<\/tr>\n | ||||||
86<\/td>\n | 5.4 Protocol suite structure Figure\u00a015 \u2013 Network with backbone \u2013 device roles <\/td>\n<\/tr>\n | ||||||
87<\/td>\n | 5.5 Data flow Figure 16 \u2013 Reference model <\/td>\n<\/tr>\n | ||||||
88<\/td>\n | Figure 17 \u2013 Basic data flow <\/td>\n<\/tr>\n | ||||||
89<\/td>\n | Figure 18 \u2013 Data flow between I\/O devices <\/td>\n<\/tr>\n | ||||||
90<\/td>\n | Figure 19 \u2013 Data flow with legacy I\/O device Figure 20 \u2013 Data flow with backbone <\/td>\n<\/tr>\n | ||||||
91<\/td>\n | Figure 21 \u2013 Data flow between I\/O devices via backbone <\/td>\n<\/tr>\n | ||||||
92<\/td>\n | 5.6 Time reference Figure 22 \u2013 Data flow to standard-aware control system <\/td>\n<\/tr>\n | ||||||
93<\/td>\n | 5.7 Firmware upgrades 5.8 Wireless backbones and other infrastructures <\/td>\n<\/tr>\n | ||||||
94<\/td>\n | 6 System management 6.1 General <\/td>\n<\/tr>\n | ||||||
95<\/td>\n | Figure 23 \u2013 Management architecture <\/td>\n<\/tr>\n | ||||||
96<\/td>\n | 6.2 Device management application process <\/td>\n<\/tr>\n | ||||||
98<\/td>\n | Figure 24 \u2013 DMAP <\/td>\n<\/tr>\n | ||||||
99<\/td>\n | Tables Table 1 \u2013 Standard management object types in DMAP <\/td>\n<\/tr>\n | ||||||
100<\/td>\n | Figure 25 \u2013 Example of management SAP flow through standard protocol suite <\/td>\n<\/tr>\n | ||||||
101<\/td>\n | Table 2 \u2013 Meta_Data_Attribute data structure <\/td>\n<\/tr>\n | ||||||
102<\/td>\n | Table 3 \u2013 Alert types for communication diagnostic category <\/td>\n<\/tr>\n | ||||||
103<\/td>\n | Table 4 \u2013 Alert types for security alert category Table 5 \u2013 Alert types for device diagnostic alert category Table 6 \u2013 Alert types for process alert category <\/td>\n<\/tr>\n | ||||||
105<\/td>\n | Table 7 \u2013 ARMO attributes <\/td>\n<\/tr>\n | ||||||
108<\/td>\n | Table 8 \u2013 ARMO alerts <\/td>\n<\/tr>\n | ||||||
109<\/td>\n | Table 9 \u2013 Alarm_Recovery method <\/td>\n<\/tr>\n | ||||||
112<\/td>\n | Table\u00a010 \u2013 DMO attributes <\/td>\n<\/tr>\n | ||||||
118<\/td>\n | Table 11 \u2013 DMO alerts <\/td>\n<\/tr>\n | ||||||
119<\/td>\n | 6.3 System manager <\/td>\n<\/tr>\n | ||||||
120<\/td>\n | Figure 26 \u2013 System manager architecture concept <\/td>\n<\/tr>\n | ||||||
121<\/td>\n | Table 12 \u2013 System management object types <\/td>\n<\/tr>\n | ||||||
123<\/td>\n | Table 13 \u2013 DSO attributes Table 14 \u2013 Address_Translation_Row data structure <\/td>\n<\/tr>\n | ||||||
124<\/td>\n | Table 15 \u2013 Read_Address_Row method <\/td>\n<\/tr>\n | ||||||
125<\/td>\n | Table 16 \u2013 Input argument usage Table 17 \u2013 Output argument usage <\/td>\n<\/tr>\n | ||||||
127<\/td>\n | Table 18 \u2013 Attributes of SMO in system manager <\/td>\n<\/tr>\n | ||||||
129<\/td>\n | Table 19 \u2013 Proxy_System_Manager_Join method <\/td>\n<\/tr>\n | ||||||
130<\/td>\n | Table 20 \u2013 Proxy_System_Manager_Contract method <\/td>\n<\/tr>\n | ||||||
131<\/td>\n | Table 21 \u2013 Effect of Different Join Commands on Attribute Sets <\/td>\n<\/tr>\n | ||||||
132<\/td>\n | Table 22 \u2013 Attributes of DMSO in system manager <\/td>\n<\/tr>\n | ||||||
133<\/td>\n | Table 23 \u2013 System_Manager_Join method <\/td>\n<\/tr>\n | ||||||
134<\/td>\n | Table 24 \u2013 System_Manager_Contract method <\/td>\n<\/tr>\n | ||||||
138<\/td>\n | Table 25 \u2013 Attributes of STSO in system manager <\/td>\n<\/tr>\n | ||||||
139<\/td>\n | Figure 27 \u2013 UAP-system manager interaction during contract establishment <\/td>\n<\/tr>\n | ||||||
141<\/td>\n | Figure 28 \u2013 Contract-related interaction between DMO and SCO Table 26 \u2013 Attributes of SCO in system manager <\/td>\n<\/tr>\n | ||||||
144<\/td>\n | Table 27 \u2013 SCO method for contract establishment, modification, or renewal <\/td>\n<\/tr>\n | ||||||
149<\/td>\n | Table 28 \u2013 Input argument usage <\/td>\n<\/tr>\n | ||||||
150<\/td>\n | Table 29 \u2013 Output argument usage <\/td>\n<\/tr>\n | ||||||
151<\/td>\n | Figure 29 \u2013 Contract source, destination, and intermediate devices <\/td>\n<\/tr>\n | ||||||
153<\/td>\n | Table 30 \u2013 Contract_Data data structure <\/td>\n<\/tr>\n | ||||||
156<\/td>\n | Table 31 \u2013 New_Device_Contract_Response data structure <\/td>\n<\/tr>\n | ||||||
159<\/td>\n | Figure 30 \u2013 Contract establishment example <\/td>\n<\/tr>\n | ||||||
160<\/td>\n | Figure 31 \u2013 Contract ID usage in source <\/td>\n<\/tr>\n | ||||||
162<\/td>\n | Table 32 \u2013 SCO method for contract termination, deactivation and reactivation Table 33 \u2013 DMO method to terminate contract <\/td>\n<\/tr>\n | ||||||
163<\/td>\n | Figure 32 \u2013 Contract termination <\/td>\n<\/tr>\n | ||||||
164<\/td>\n | Table 34 \u2013 DMO method to modify contract <\/td>\n<\/tr>\n | ||||||
165<\/td>\n | Figure 33 \u2013 Contract modification with immediate effect <\/td>\n<\/tr>\n | ||||||
166<\/td>\n | 7 Security 7.1 General <\/td>\n<\/tr>\n | ||||||
167<\/td>\n | 7.2 Security services Figure 34 \u2013 Examples of DPDU and TPDU scope <\/td>\n<\/tr>\n | ||||||
171<\/td>\n | 7.3 Frame security Table 35 \u2013 Security levels <\/td>\n<\/tr>\n | ||||||
172<\/td>\n | Table 36 \u2013 Structure of the security control field <\/td>\n<\/tr>\n | ||||||
173<\/td>\n | Figure 37 \u2013 DPDU structure <\/td>\n<\/tr>\n | ||||||
174<\/td>\n | Figure 38 \u2013 Outgoing messages \u2013 DL and security <\/td>\n<\/tr>\n | ||||||
176<\/td>\n | Figure 39 \u2013 Incoming messages- DL and security <\/td>\n<\/tr>\n | ||||||
177<\/td>\n | Table 37 \u2013 Sec.DpduPrep.Request elements <\/td>\n<\/tr>\n | ||||||
178<\/td>\n | Table 38 \u2013 Sec.DpduPrep.Response elements Table 39 \u2013 Sec.DLAckCheck.Request elements <\/td>\n<\/tr>\n | ||||||
179<\/td>\n | Table 40 \u2013 Sec. DLAckCheck.Response elements <\/td>\n<\/tr>\n | ||||||
180<\/td>\n | Table 41 \u2013 Sec.DpduCheck.Request elements <\/td>\n<\/tr>\n | ||||||
181<\/td>\n | Table 42 \u2013 Sec.DpduCheck.Response elements Table 43 \u2013 Sec.DLAckPrep.Request elements <\/td>\n<\/tr>\n | ||||||
182<\/td>\n | Table 44 \u2013 Sec.DLAckPrep.Response elements <\/td>\n<\/tr>\n | ||||||
183<\/td>\n | Table 45 \u2013 Structure of the WISN DPDU nonce Table 46 \u2013 Structure of the 32-bit truncated TAI time <\/td>\n<\/tr>\n | ||||||
187<\/td>\n | Figure 40 \u2013 TPDU structure and protected coverage <\/td>\n<\/tr>\n | ||||||
188<\/td>\n | Figure 41 \u2013 TMIC parameters Table 47 \u2013 TSS \u201cpseudo-header\u201d structure <\/td>\n<\/tr>\n | ||||||
189<\/td>\n | Figure 42 \u2013 Transport layer and security sub-layer interaction, outgoing TPDU <\/td>\n<\/tr>\n | ||||||
190<\/td>\n | Figure 43 \u2013 Transport layer and security sub-layer interaction, incoming TPDU <\/td>\n<\/tr>\n | ||||||
191<\/td>\n | Table 48 \u2013 Sec.TpduOutCheck.Request elements Table 49 \u2013 Sec.TpduOutCheck.Response elements <\/td>\n<\/tr>\n | ||||||
192<\/td>\n | Table 50 \u2013 Sec.TpduSecure.Request elements <\/td>\n<\/tr>\n | ||||||
193<\/td>\n | Table 51 \u2013 Sec. TpduSecure.Response elements <\/td>\n<\/tr>\n | ||||||
194<\/td>\n | Table 52 \u2013 Sec.TpduInCheck.Request elements <\/td>\n<\/tr>\n | ||||||
195<\/td>\n | Table 53 \u2013 Sec.TpduInCheck.Response elements Table 54 \u2013 Sec.TpduVerify.Request elements <\/td>\n<\/tr>\n | ||||||
196<\/td>\n | Table 55 \u2013 Sec.TpduVerify.Response elements <\/td>\n<\/tr>\n | ||||||
197<\/td>\n | Table 56 \u2013 Structure of TL security header <\/td>\n<\/tr>\n | ||||||
198<\/td>\n | Table 57 \u2013 Structure of the TPDU nonce Table 58 \u2013 Structure of 32-bit nominal TAI time <\/td>\n<\/tr>\n | ||||||
202<\/td>\n | 7.4 The join process <\/td>\n<\/tr>\n | ||||||
207<\/td>\n | Figure 44 \u2013 Example: Overview of the symmetric key join process Figure 45 \u2013 Example: Overview of the symmetric key join process of backbone device <\/td>\n<\/tr>\n | ||||||
209<\/td>\n | Table 59 \u2013 Proxy_Security_Sym_Join method <\/td>\n<\/tr>\n | ||||||
210<\/td>\n | Table 60 \u2013 Security_Sym_Join method Table 61 \u2013 Security_Confirm method <\/td>\n<\/tr>\n | ||||||
211<\/td>\n | Table 62 \u2013 Security_Sym_Join_Request data structure <\/td>\n<\/tr>\n | ||||||
212<\/td>\n | Table 63 \u2013 Security_Sym_Join_Response data structure <\/td>\n<\/tr>\n | ||||||
213<\/td>\n | Table 64 \u2013 Structure of compressed Security level field <\/td>\n<\/tr>\n | ||||||
214<\/td>\n | Table 65 \u2013 Master key security level Table 66 \u2013 Structure of KeyHardLifeSpan field <\/td>\n<\/tr>\n | ||||||
215<\/td>\n | Table 67 \u2013 Security_Sym_Confirm data structure <\/td>\n<\/tr>\n | ||||||
216<\/td>\n | Table 68 \u2013 Implicit certificate format <\/td>\n<\/tr>\n | ||||||
217<\/td>\n | Figure 46 \u2013 Asymmetric key-authenticated key agreement scheme Table 69 \u2013 Usage_Serial structure <\/td>\n<\/tr>\n | ||||||
220<\/td>\n | Figure 47 \u2013 Example: Overview of the asymmetric key join processfor a device with a data link layer <\/td>\n<\/tr>\n | ||||||
221<\/td>\n | Figure 48 \u2013 Example: Overview of the asymmetric key join processof a backbone device <\/td>\n<\/tr>\n | ||||||
222<\/td>\n | Table 70 \u2013 Proxy_Security_Pub_Join method Table 71 \u2013 Security_Pub_Join method <\/td>\n<\/tr>\n | ||||||
223<\/td>\n | Table 72 \u2013 Proxy_Security_Pub_Confirm method <\/td>\n<\/tr>\n | ||||||
224<\/td>\n | Table 73 \u2013 Security_Pub_Confirm method Table 74 \u2013 Network_Information_Confirmation method <\/td>\n<\/tr>\n | ||||||
225<\/td>\n | Table 75 \u2013 Format of asymmetric join request internal structure Table 76 \u2013 Format of the protocol control field <\/td>\n<\/tr>\n | ||||||
226<\/td>\n | Table 77 \u2013 Format of asymmetric join response internal structure <\/td>\n<\/tr>\n | ||||||
227<\/td>\n | Table 78 \u2013 Format of first join confirmation internal structure <\/td>\n<\/tr>\n | ||||||
228<\/td>\n | Table 79 \u2013 Format of join confirmation response internal structure <\/td>\n<\/tr>\n | ||||||
230<\/td>\n | Figure 49 \u2013 Device state transitions for join process and device lifetime Table 80 \u2013 Join process and device lifetime state machine <\/td>\n<\/tr>\n | ||||||
231<\/td>\n | 7.5 Session establishment Figure 50 \u2013 High-level example of session establishment <\/td>\n<\/tr>\n | ||||||
233<\/td>\n | Table 81 \u2013 Security_New_Session method <\/td>\n<\/tr>\n | ||||||
234<\/td>\n | Table 82 \u2013 Security_New_Session_Request data structure <\/td>\n<\/tr>\n | ||||||
236<\/td>\n | Table 83 \u2013 Security_New_Session_Response data structure <\/td>\n<\/tr>\n | ||||||
237<\/td>\n | 7.6 Key update Figure 51 \u2013 Key update protocol overview <\/td>\n<\/tr>\n | ||||||
238<\/td>\n | Table 84 \u2013 New_Key method <\/td>\n<\/tr>\n | ||||||
239<\/td>\n | Table 85 \u2013 Security_Key_and_Policies data structure <\/td>\n<\/tr>\n | ||||||
241<\/td>\n | Table 86 \u2013 Security_Key_Update_Status data structure <\/td>\n<\/tr>\n | ||||||
243<\/td>\n | Table 87 \u2013 Session and DL key state transition <\/td>\n<\/tr>\n | ||||||
244<\/td>\n | 7.7 Security manager functionality Figure 52 \u2013 Device session establishment and key update state transition Table 88 \u2013 Attributes of PSMO in the system manager <\/td>\n<\/tr>\n | ||||||
246<\/td>\n | 7.8 Security policies <\/td>\n<\/tr>\n | ||||||
247<\/td>\n | Table 89 \u2013 Structure of Policy field Table 90 \u2013 Key types Table 91 \u2013 Key usage <\/td>\n<\/tr>\n | ||||||
248<\/td>\n | Table 92 \u2013 Granularity <\/td>\n<\/tr>\n | ||||||
249<\/td>\n | 7.9 Security functions available to the application layer <\/td>\n<\/tr>\n | ||||||
252<\/td>\n | 7.10 Security statistics collection, threat detection, and reporting 7.11 Device security management object functionality <\/td>\n<\/tr>\n | ||||||
253<\/td>\n | Table 93 \u2013 Device security management object attributes <\/td>\n<\/tr>\n | ||||||
255<\/td>\n | Table 94 \u2013 KeyDescriptor (INFORMATIVE) <\/td>\n<\/tr>\n | ||||||
256<\/td>\n | Table 95 \u2013 TL KeyLookupData OctetString fields <\/td>\n<\/tr>\n | ||||||
257<\/td>\n | Table 96 \u2013 Delete key method <\/td>\n<\/tr>\n | ||||||
259<\/td>\n | Table 97 \u2013 Key_Policy_Update method <\/td>\n<\/tr>\n | ||||||
260<\/td>\n | 8 Physical layer 8.1 General Table 98 \u2013 DSMO Alerts <\/td>\n<\/tr>\n | ||||||
261<\/td>\n | 8.2 Default physical layer Table 99 \u2013 Timing requirements <\/td>\n<\/tr>\n | ||||||
262<\/td>\n | 9 Data link layer 9.1 General <\/td>\n<\/tr>\n | ||||||
264<\/td>\n | Figure 53 \u2013 DL protocol suite and PPDU\/DPDU structure <\/td>\n<\/tr>\n | ||||||
266<\/td>\n | Figure 54 \u2013 Graph routing example <\/td>\n<\/tr>\n | ||||||
267<\/td>\n | Table 100 \u2013 Graph table on ND20 Table 101 \u2013 Graph table on ND21 <\/td>\n<\/tr>\n | ||||||
268<\/td>\n | Figure\u00a055 \u2013 Inbound and outbound graphs <\/td>\n<\/tr>\n | ||||||
272<\/td>\n | Figure 56 \u2013 Slotted hopping Figure 57 \u2013 Slow hopping <\/td>\n<\/tr>\n | ||||||
273<\/td>\n | Figure 58 \u2013 Hybrid operation <\/td>\n<\/tr>\n | ||||||
274<\/td>\n | Figure 59 \u2013 Radio spectrum usage <\/td>\n<\/tr>\n | ||||||
276<\/td>\n | Figure 60 \u2013 Default hopping pattern 1 Figure 61 \u2013 Two groups of devices with different hopping pattern offsets <\/td>\n<\/tr>\n | ||||||
277<\/td>\n | Figure 62 \u2013 Interleaved hopping pattern 1 with 16 different hopping pattern offsets <\/td>\n<\/tr>\n | ||||||
278<\/td>\n | Figure 63 \u2013 Slotted hopping <\/td>\n<\/tr>\n | ||||||
279<\/td>\n | Figure 64 \u2013 Slow hopping <\/td>\n<\/tr>\n | ||||||
280<\/td>\n | Figure 65 \u2013 Hybrid mode with slotted and slow hopping Figure 66 \u2013 Combining slotted hopping and slow hopping <\/td>\n<\/tr>\n | ||||||
281<\/td>\n | Figure 67 \u2013 Example of a three-timeslot superframe Figure 68 \u2013 Superframes and links <\/td>\n<\/tr>\n | ||||||
282<\/td>\n | Figure 69 \u2013 Multiple superframes, with timeslots aligned <\/td>\n<\/tr>\n | ||||||
286<\/td>\n | Figure 70 \u2013 Slotted hopping <\/td>\n<\/tr>\n | ||||||
287<\/td>\n | Figure 71 \u2013 Slow hopping Figure 72 \u2013 Components of a slow hop <\/td>\n<\/tr>\n | ||||||
288<\/td>\n | Figure 73 \u2013 Avoiding collisions among routers <\/td>\n<\/tr>\n | ||||||
289<\/td>\n | Figure 74 \u2013 Hybrid configuration <\/td>\n<\/tr>\n | ||||||
291<\/td>\n | Figure 75 \u2013 Timeslot allocation and the message queue <\/td>\n<\/tr>\n | ||||||
294<\/td>\n | Figure 76 \u2013 250\u00a0ms alignment intervals <\/td>\n<\/tr>\n | ||||||
295<\/td>\n | Figure 77 \u2013 Timeslot durations and timing <\/td>\n<\/tr>\n | ||||||
296<\/td>\n | Table 102 \u2013 Approximating nominal timing with 32\u00a0kHz clock (INFORMATIVE) <\/td>\n<\/tr>\n | ||||||
300<\/td>\n | Figure 78 \u2013 Clock source acknowledges receipt of DPDU <\/td>\n<\/tr>\n | ||||||
302<\/td>\n | Figure 79 \u2013 Transaction timing attributes <\/td>\n<\/tr>\n | ||||||
303<\/td>\n | Figure 80 \u2013 Dedicated and shared transaction timeslots <\/td>\n<\/tr>\n | ||||||
304<\/td>\n | Figure 81 \u2013 Unicast transaction <\/td>\n<\/tr>\n | ||||||
306<\/td>\n | Figure 82 \u2013 PDU wait time (PWT) <\/td>\n<\/tr>\n | ||||||
307<\/td>\n | Figure 83 \u2013 Duocast support in the standard <\/td>\n<\/tr>\n | ||||||
308<\/td>\n | Figure 84 \u2013 Duocast transaction <\/td>\n<\/tr>\n | ||||||
309<\/td>\n | Figure 85 \u2013 Shared timeslots with CSMA-CA <\/td>\n<\/tr>\n | ||||||
310<\/td>\n | Figure 86 \u2013 Transaction during slow-hopping periods <\/td>\n<\/tr>\n | ||||||
313<\/td>\n | Figure 87 \u2013 DL management SAP flow through standard protocol suite <\/td>\n<\/tr>\n | ||||||
322<\/td>\n | Table 103 \u2013 DL_Config_Info structure <\/td>\n<\/tr>\n | ||||||
328<\/td>\n | 9.2 Data link layer data service access point <\/td>\n<\/tr>\n | ||||||
329<\/td>\n | Table 104 \u2013 DDData.request parameters <\/td>\n<\/tr>\n | ||||||
330<\/td>\n | Table 105 \u2013 DDData.confirm parameters Table 106 \u2013 Value set for status parameter <\/td>\n<\/tr>\n | ||||||
331<\/td>\n | 9.3 Data frames and acknowledgements Figure 88 \u2013 PPDU and DPDU structure Table 107 \u2013 DDData.indication parameters <\/td>\n<\/tr>\n | ||||||
333<\/td>\n | Table 108 \u2013 ExtDLUint, one-octet variant Table 109 \u2013 ExtDLUint, two-octet variant <\/td>\n<\/tr>\n | ||||||
334<\/td>\n | Table 110 \u2013 Data frame MHR <\/td>\n<\/tr>\n | ||||||
335<\/td>\n | Table 111 \u2013 DHDR frame control octet Table 112 \u2013 Data frame DMXHR <\/td>\n<\/tr>\n | ||||||
336<\/td>\n | Table 113 \u2013 DROUT structure, compressed variant <\/td>\n<\/tr>\n | ||||||
337<\/td>\n | Table 114 \u2013 DROUT structure, uncompressed variant <\/td>\n<\/tr>\n | ||||||
338<\/td>\n | Table 115 \u2013 DADDR structure <\/td>\n<\/tr>\n | ||||||
339<\/td>\n | Figure 89 \u2013 Typical acknowledgement frame layout Table 116 \u2013 Acknowledgement frame MHR <\/td>\n<\/tr>\n | ||||||
340<\/td>\n | Table 117 \u2013 Acknowledgement frame DHR <\/td>\n<\/tr>\n | ||||||
341<\/td>\n | Table 118 \u2013 DHR ACK\/NACK frame control <\/td>\n<\/tr>\n | ||||||
342<\/td>\n | Table 119 \u2013 Advertisement DAUX structure <\/td>\n<\/tr>\n | ||||||
343<\/td>\n | Table 120 \u2013 Advertisement selections elements Table 121 \u2013 Advertisement selections Table 122 \u2013 Advertisement time synchronization elements <\/td>\n<\/tr>\n | ||||||
344<\/td>\n | Table 123 \u2013 Advertisement time synchronization structure <\/td>\n<\/tr>\n | ||||||
345<\/td>\n | Table 124 \u2013 Join superframe information subfields Table 125 \u2013 Join superframe information structure <\/td>\n<\/tr>\n | ||||||
346<\/td>\n | Table 126 \u2013 Superframe derived from advertisement Table 127 \u2013 Join information elements <\/td>\n<\/tr>\n | ||||||
347<\/td>\n | Table 128 \u2013 Join information structure <\/td>\n<\/tr>\n | ||||||
348<\/td>\n | Table 129 \u2013 Defaults for links created from advertisements <\/td>\n<\/tr>\n | ||||||
349<\/td>\n | Table 130 \u2013 dlmo.Neighbor entry created from advertisements Table 131 \u2013 dlmo.Graph entry created from advertisements Table 132 \u2013 dlmo.Route entry created from advertisements <\/td>\n<\/tr>\n | ||||||
351<\/td>\n | Table 133 \u2013 Solicitation header subfields Table 134 \u2013 Solicitation header structure Table 135 \u2013 Solicitation DAUX fields <\/td>\n<\/tr>\n | ||||||
352<\/td>\n | Table 136 \u2013 Solicitation DAUX structure <\/td>\n<\/tr>\n | ||||||
353<\/td>\n | Table 137 \u2013 Activate link DAUX fields Table 138 \u2013 Activate link DAUX structure <\/td>\n<\/tr>\n | ||||||
354<\/td>\n | 9.4 Data link layer management information base Table 139 \u2013 Reporting received signal quality DAUX fields Table 140 \u2013 Report received signal quality DAUX structure <\/td>\n<\/tr>\n | ||||||
355<\/td>\n | Table 141 \u2013 DLMO attributes <\/td>\n<\/tr>\n | ||||||
363<\/td>\n | Table 142 \u2013 Subnet filter octets Table 143 \u2013 dlmo.TaiAdjust OctetString fields Table 144 \u2013 dlmo.TaiAdjust OctetString structure <\/td>\n<\/tr>\n | ||||||
364<\/td>\n | Table 145 \u2013 dlmo.EnergyDesign OctetString fields Table 146 \u2013 dlmo.EnergyDesign OctetString structure Table 147 \u2013 dlmo.DeviceCapability OctetString fields <\/td>\n<\/tr>\n | ||||||
365<\/td>\n | Table 148 \u2013 dlmo.DeviceCapability OctetString structure <\/td>\n<\/tr>\n | ||||||
366<\/td>\n | Table 149 \u2013 dlmo.DiscoveryAlert fields Table 150 \u2013 dlmo.DiscoveryAlert structure <\/td>\n<\/tr>\n | ||||||
367<\/td>\n | Table 151 \u2013 dlmo.Candidates OctetString fields <\/td>\n<\/tr>\n | ||||||
368<\/td>\n | Table 152 \u2013 dlmo.Candidates structure <\/td>\n<\/tr>\n | ||||||
369<\/td>\n | Table 153 \u2013 dlmo.SmoothFactors OctetString fields Table 154 \u2013 dlmo.SmoothFactors structure Table 155 \u2013 dlmo.QueuePriority fields <\/td>\n<\/tr>\n | ||||||
370<\/td>\n | Table 156 \u2013 dlmo.QueuePriority structure <\/td>\n<\/tr>\n | ||||||
371<\/td>\n | Table 157 \u2013 dlmo.ChannelDiag fields Table 158 \u2013 dlmo.ChannelDiag structure <\/td>\n<\/tr>\n | ||||||
372<\/td>\n | Figure 90 \u2013 Relationship among DLMO indexed attributes <\/td>\n<\/tr>\n | ||||||
373<\/td>\n | Table 159 \u2013 dlmo.Ch fields Table 160 \u2013 dlmo.Ch structure <\/td>\n<\/tr>\n | ||||||
376<\/td>\n | Table 161 \u2013 Receive template fields Table 162 \u2013 Receive template structure <\/td>\n<\/tr>\n | ||||||
377<\/td>\n | Table 163 \u2013 Transmit template fields Table 164 \u2013 Transmit template structure <\/td>\n<\/tr>\n | ||||||
378<\/td>\n | Table 165 \u2013 Default receive template Table 166 \u2013 Default transmit template Table 167 \u2013 Default receive template for scanning <\/td>\n<\/tr>\n | ||||||
380<\/td>\n | Table 168 \u2013 dlmo.Neighbor fields Table 169 \u2013 dlmo.Neighbor structure <\/td>\n<\/tr>\n | ||||||
382<\/td>\n | Table 170 \u2013 ExtendGraph fields Table 171 \u2013 ExtGraph structure Table 172 \u2013 dlmo.NeighborDiagReset fields <\/td>\n<\/tr>\n | ||||||
383<\/td>\n | Table 173 \u2013 dlmo.NeighborDiagReset structure <\/td>\n<\/tr>\n | ||||||
384<\/td>\n | Table 174 \u2013 dlmo.Superframe fields Table 175 \u2013 dlmo.Superframe structure <\/td>\n<\/tr>\n | ||||||
388<\/td>\n | Table 176 \u2013dlmo.SuperframeIdle fields Table 177 \u2013 dlmo.SuperframeIdle structure <\/td>\n<\/tr>\n | ||||||
389<\/td>\n | Table 178 \u2013 dlmo.Graph Table 179 \u2013 dlmo.Graph structure <\/td>\n<\/tr>\n | ||||||
390<\/td>\n | Table 180 \u2013 dlmo.Link fields <\/td>\n<\/tr>\n | ||||||
391<\/td>\n | Table 181 \u2013 dlmo.Link structure <\/td>\n<\/tr>\n | ||||||
392<\/td>\n | Table 182 \u2013 dlmo.Link[].Type structure <\/td>\n<\/tr>\n | ||||||
393<\/td>\n | Table 183 \u2013 Allowed dlmo.Link[].Type combinations <\/td>\n<\/tr>\n | ||||||
394<\/td>\n | Table 184 \u2013 Values for dlmo.Link[].Schedule Table 185 \u2013 dlmo.Route fields <\/td>\n<\/tr>\n | ||||||
395<\/td>\n | Table 186 \u2013 dlmo.Route structure <\/td>\n<\/tr>\n | ||||||
396<\/td>\n | Table 187 \u2013 dlmo.NeighborDiag fields Table 188 \u2013 Diagnostic Summary OctetString fields <\/td>\n<\/tr>\n | ||||||
397<\/td>\n | Table 189 \u2013 Diagnostic Summary OctetString structure Table 190 \u2013 Diagnostic ClockDetail OctetString fields <\/td>\n<\/tr>\n | ||||||
398<\/td>\n | 9.5 Data link layer methods Table 191 \u2013 Diagnostic ClockDetail OctetString structure <\/td>\n<\/tr>\n | ||||||
399<\/td>\n | Table 192 \u2013 Read_Row method Table 193 \u2013 Write_Row method <\/td>\n<\/tr>\n | ||||||
400<\/td>\n | 9.6 Data link layer alerts Table 194 \u2013 Write_Row_Now method <\/td>\n<\/tr>\n | ||||||
401<\/td>\n | Table 195 \u2013 dlmo.AlertPolicy fields Table 196 \u2013 dlmo.AlertPolicy OctetString structure <\/td>\n<\/tr>\n | ||||||
402<\/td>\n | Table 197 \u2013 DL_Connectivity alert Table 198 \u2013 DL_Connectivity alert OctetString <\/td>\n<\/tr>\n | ||||||
403<\/td>\n | 10 Network layer 10.1 General 10.2 Network layer functionality overview Table 199 \u2013 NeighborDiscovery alert <\/td>\n<\/tr>\n | ||||||
404<\/td>\n | Table 200 \u2013 Link local address structure <\/td>\n<\/tr>\n | ||||||
405<\/td>\n | Table 201 \u2013 Address translation table (ATT) <\/td>\n<\/tr>\n | ||||||
406<\/td>\n | Figure 91 \u2013 Address translation process <\/td>\n<\/tr>\n | ||||||
408<\/td>\n | Figure 92 \u2013 Fragmentation process <\/td>\n<\/tr>\n | ||||||
409<\/td>\n | Figure 93 \u2013 Reassembly process <\/td>\n<\/tr>\n | ||||||
410<\/td>\n | Table 202 \u2013 Example of a routing table <\/td>\n<\/tr>\n | ||||||
411<\/td>\n | Figure 94 \u2013 Processing of a NSDU received from the transport layer <\/td>\n<\/tr>\n | ||||||
412<\/td>\n | Figure 95 \u2013 Processing of an incoming NPDU <\/td>\n<\/tr>\n | ||||||
413<\/td>\n | Figure 96 \u2013 Processing of a NPDU received from the backbone <\/td>\n<\/tr>\n | ||||||
414<\/td>\n | Figure 97 \u2013 Delivery of an incoming NPDU at its final destination Figure 98 \u2013 Routing from a field device to a gateway on field \u2013 no backbone routing <\/td>\n<\/tr>\n | ||||||
415<\/td>\n | Figure 99 \u2013 Protocol suite diagram for routing from a field device to a gateway on field \u2013 no backbone routing <\/td>\n<\/tr>\n | ||||||
416<\/td>\n | Figure 100 \u2013 Routing a PDU from a field device to a gateway via a backbone router Figure 101 \u2013 Protocol suite diagram for routing a PDU from a field deviceto a gateway via a backbone router <\/td>\n<\/tr>\n | ||||||
418<\/td>\n | Figure 102 \u2013 Routing from a field device on one subnet to another field deviceon a different subnet <\/td>\n<\/tr>\n | ||||||
419<\/td>\n | Figure 103 \u2013 Protocol suite diagram for routing from an I\/O deviceon one subnet to another I\/O device on a different subnet <\/td>\n<\/tr>\n | ||||||
420<\/td>\n | Figure 104 \u2013 Routing over an Ethernet backbone network <\/td>\n<\/tr>\n | ||||||
421<\/td>\n | 10.3 Network layer data services Figure 105 \u2013 Routing over a fieldbus backbone network <\/td>\n<\/tr>\n | ||||||
422<\/td>\n | Table 203 \u2013 NData.request elements Table 204 \u2013 NData.confirm elements <\/td>\n<\/tr>\n | ||||||
423<\/td>\n | Table 205 \u2013 NData.indication elements <\/td>\n<\/tr>\n | ||||||
424<\/td>\n | 10.4 Network layer management object <\/td>\n<\/tr>\n | ||||||
425<\/td>\n | Table 206 \u2013 NLMO attributes <\/td>\n<\/tr>\n | ||||||
428<\/td>\n | Table 207 \u2013 Contract table structure <\/td>\n<\/tr>\n | ||||||
429<\/td>\n | Table 208 \u2013 Route table elements Table 209 \u2013 Address translation table structure <\/td>\n<\/tr>\n | ||||||
431<\/td>\n | Table 210 \u2013 NLMO structured MIB manipulation methods <\/td>\n<\/tr>\n | ||||||
432<\/td>\n | 10.5 Network layer protocol data unit formats Table 211 \u2013 Alert to indicate dropped PDU\/PDU error <\/td>\n<\/tr>\n | ||||||
433<\/td>\n | Figure 106 \u2013 Distinguishing between NPDU header formats Table 212 \u2013 Common header patterns <\/td>\n<\/tr>\n | ||||||
434<\/td>\n | Table 213 \u2013 Basic network layer header format <\/td>\n<\/tr>\n | ||||||
435<\/td>\n | Table 214 \u2013 Contract-enabled network layer header format <\/td>\n<\/tr>\n | ||||||
436<\/td>\n | Table 215 \u2013 6LoWPAN_IPHC encoding format <\/td>\n<\/tr>\n | ||||||
437<\/td>\n | Table 216 \u2013 IPv6 network layer header format <\/td>\n<\/tr>\n | ||||||
438<\/td>\n | Table 217 \u2013 Full network layer header in the DL Table 218 \u2013 Network layer header format for fragmented NPDUs <\/td>\n<\/tr>\n | ||||||
439<\/td>\n | 11 Transport layer 11.1 General Table 219 \u2013 First fragment header format Table 220 \u2013 Second and subsequent fragment header format <\/td>\n<\/tr>\n | ||||||
440<\/td>\n | 11.2 Transport layer reference model Figure 107 \u2013 Transport layer reference model <\/td>\n<\/tr>\n | ||||||
441<\/td>\n | 11.3 Transport security sub-layer 11.4 Transport data entity <\/td>\n<\/tr>\n | ||||||
442<\/td>\n | Figure 108 \u2013 UDP \u201cpseudo-header\u201d for IPv6 Table 221 \u2013 UDP header encoding <\/td>\n<\/tr>\n | ||||||
445<\/td>\n | 11.5 Transport layer protocol data unit encoding Figure 109 \u2013 Transport layer protocol data unit <\/td>\n<\/tr>\n | ||||||
446<\/td>\n | Table 222 \u2013 UDP LowPAN_NHC encoding Table 223 \u2013 Optimal UDP header encoding <\/td>\n<\/tr>\n | ||||||
447<\/td>\n | 11.6 Transport layer model Table 224 \u2013 UDP header encoding with checksum <\/td>\n<\/tr>\n | ||||||
448<\/td>\n | Table 225 \u2013 TData.request elements <\/td>\n<\/tr>\n | ||||||
449<\/td>\n | Table 226 \u2013 TData.confirm elements Table 227 \u2013 TData.confirm status codes <\/td>\n<\/tr>\n | ||||||
450<\/td>\n | Table 228 \u2013 TData.indication elements <\/td>\n<\/tr>\n | ||||||
452<\/td>\n | Table 229 \u2013 TLMO attributes <\/td>\n<\/tr>\n | ||||||
454<\/td>\n | Table 230 \u2013 Transport layer management object methods \u2013 Reset Table 231 \u2013 Transport layer management object methods \u2013 Halt <\/td>\n<\/tr>\n | ||||||
455<\/td>\n | Table 232 \u2013 Transport layer management object methods \u2013 PortRangeInfo Table 233 \u2013 Transport layer management object methods \u2013 GetPortInfo <\/td>\n<\/tr>\n | ||||||
456<\/td>\n | Table 234 \u2013 Transport layer management object methods \u2013 GetNextPortInfo Table 235 \u2013 Transport layer management object alert types \u2013 Illegal use of port <\/td>\n<\/tr>\n | ||||||
457<\/td>\n | 12 Application layer 12.1 General Table 236 \u2013 Transport layer management object alert types \u2013TPDU received on unregistered port Table 237 \u2013 Transport layer management object alert types \u2013TPDU does not match security policies <\/td>\n<\/tr>\n | ||||||
458<\/td>\n | 12.2 Energy considerations 12.3 Legacy control system considerations <\/td>\n<\/tr>\n | ||||||
459<\/td>\n | 12.4 Introduction to object-oriented modeling <\/td>\n<\/tr>\n | ||||||
460<\/td>\n | Figure 110 \u2013 User application objects in a user application process <\/td>\n<\/tr>\n | ||||||
461<\/td>\n | 12.5 Object model <\/td>\n<\/tr>\n | ||||||
462<\/td>\n | 12.6 Object attribute model <\/td>\n<\/tr>\n | ||||||
464<\/td>\n | 12.7 Method model <\/td>\n<\/tr>\n | ||||||
465<\/td>\n | 12.8 Alert model 12.9 Alarm state model Table 238 \u2013 State table for alarm transitions <\/td>\n<\/tr>\n | ||||||
466<\/td>\n | 12.10 Event state model Figure 111 \u2013 Alarm state model Table 239 \u2013 State table for event transitions <\/td>\n<\/tr>\n | ||||||
467<\/td>\n | 12.11 Alert reporting Figure 112 \u2013 Event model <\/td>\n<\/tr>\n | ||||||
469<\/td>\n | 12.12 Communication interaction model <\/td>\n<\/tr>\n | ||||||
472<\/td>\n | Figure 113 \u2013 A successful example of multiple outstanding requests,with response concatenation <\/td>\n<\/tr>\n | ||||||
473<\/td>\n | Figure 114 \u2013 An example of multiple outstanding unordered requests,with second write request initially unsuccessful <\/td>\n<\/tr>\n | ||||||
474<\/td>\n | Figure 115 \u2013 An example of multiple outstanding ordered requests,with second write request initially unsuccessful <\/td>\n<\/tr>\n | ||||||
476<\/td>\n | Figure 116 \u2013 Send window example 1, with current send window smallerthan maximum send window <\/td>\n<\/tr>\n | ||||||
477<\/td>\n | Figure 117 \u2013 Send window example 2, with current send window the same sizeas maximum send window, and non-zero usable send window width Figure 118 \u2013 Send window example 3, with current send window the same sizeas maximum send window, and usable send window width of zero (0) <\/td>\n<\/tr>\n | ||||||
479<\/td>\n | 12.13 Application layer addressing Figure 119 \u2013 General addressing model <\/td>\n<\/tr>\n | ||||||
482<\/td>\n | 12.14 Management objects 12.15 User objects <\/td>\n<\/tr>\n | ||||||
484<\/td>\n | Table 240 \u2013 UAP management object attributes <\/td>\n<\/tr>\n | ||||||
485<\/td>\n | Table 241 \u2013 State table for UAP management object <\/td>\n<\/tr>\n | ||||||
486<\/td>\n | Figure 120 \u2013 UAP management object state diagram Table 242 \u2013 UAP management object methods <\/td>\n<\/tr>\n | ||||||
487<\/td>\n | Table 243 \u2013 Alert receiving object attributes Table 244 \u2013 State table for handling an AlertReport reception <\/td>\n<\/tr>\n | ||||||
488<\/td>\n | Figure 121 \u2013 Alert report reception state diagram Figure 122 \u2013 Alert reporting example Table 245 \u2013 AlertReceiving object methods <\/td>\n<\/tr>\n | ||||||
490<\/td>\n | Table 246 \u2013 UploadDownload object attributes <\/td>\n<\/tr>\n | ||||||
494<\/td>\n | Table 247 \u2013 UploadDownload object methods <\/td>\n<\/tr>\n | ||||||
495<\/td>\n | Table 248 \u2013 UploadDownload object StartDownload method <\/td>\n<\/tr>\n | ||||||
496<\/td>\n | Table 249 \u2013 UploadDownload object DownloadData method <\/td>\n<\/tr>\n | ||||||
498<\/td>\n | Table 250 \u2013 UploadDownload object EndDownload method <\/td>\n<\/tr>\n | ||||||
499<\/td>\n | Table 251 \u2013 UploadDownload object StartUpload method <\/td>\n<\/tr>\n | ||||||
500<\/td>\n | Table 252 \u2013 UploadDownload object UploadData method <\/td>\n<\/tr>\n | ||||||
501<\/td>\n | Table 253 \u2013 UploadDownload object EndUpload method <\/td>\n<\/tr>\n | ||||||
503<\/td>\n | Table 254 \u2013 Download state table for unicast operation mode <\/td>\n<\/tr>\n | ||||||
504<\/td>\n | Figure 123 \u2013 Upload\/Download object download state diagram <\/td>\n<\/tr>\n | ||||||
505<\/td>\n | Table 255 \u2013 Upload state table for unicast operation mode <\/td>\n<\/tr>\n | ||||||
506<\/td>\n | Figure 124 \u2013 Upload\/Download object upload state diagram <\/td>\n<\/tr>\n | ||||||
508<\/td>\n | Table 256 \u2013 Concentrator object attributes <\/td>\n<\/tr>\n | ||||||
509<\/td>\n | Table 257 \u2013 Concentrator object methods <\/td>\n<\/tr>\n | ||||||
510<\/td>\n | Table 258 \u2013 Dispersion object attributes <\/td>\n<\/tr>\n | ||||||
511<\/td>\n | Table 259 \u2013 Dispersion object methods <\/td>\n<\/tr>\n | ||||||
512<\/td>\n | Table 260 \u2013 Tunnel object attributes <\/td>\n<\/tr>\n | ||||||
514<\/td>\n | Table 261 \u2013 Tunnel object methods <\/td>\n<\/tr>\n | ||||||
515<\/td>\n | 12.16 Data types Table 262 \u2013 Interface object attributes Table 263 \u2013 Interface object methods <\/td>\n<\/tr>\n | ||||||
516<\/td>\n | Table 264 \u2013 Data type: ObjectAttributeIndexAndSize <\/td>\n<\/tr>\n | ||||||
517<\/td>\n | Table 265 \u2013 Data type: Communication association endpoint <\/td>\n<\/tr>\n | ||||||
518<\/td>\n | Table 266 \u2013 Data type: Communication contract data <\/td>\n<\/tr>\n | ||||||
519<\/td>\n | Table 267 \u2013 Data type: Alert communication endpoint Table 268 \u2013 Data type: Tunnel endpoint <\/td>\n<\/tr>\n | ||||||
520<\/td>\n | Table 269 \u2013 Data type: Alert report descriptor Table 270 \u2013 Data type: Process control alarm report descriptor for analogwith single reference condition <\/td>\n<\/tr>\n | ||||||
521<\/td>\n | 12.17 Application services provided by application sub-layer Table 271 \u2013 Data type: ObjectIDandType Table 272 \u2013 Data type: Unscheduled correspondent <\/td>\n<\/tr>\n | ||||||
522<\/td>\n | Table 273 \u2013 AL services <\/td>\n<\/tr>\n | ||||||
524<\/td>\n | Figure 125 \u2013 Publish sequence of service primitives <\/td>\n<\/tr>\n | ||||||
526<\/td>\n | Table 274 \u2013 Publish service <\/td>\n<\/tr>\n | ||||||
529<\/td>\n | Figure 126 \u2013 Client\/server model two-part interactions <\/td>\n<\/tr>\n | ||||||
530<\/td>\n | Figure 127 \u2013 Client\/server model four-part interactions: Successful delivery Figure 128 \u2013 Client\/server model four-part interactions: Request delivery failure <\/td>\n<\/tr>\n | ||||||
531<\/td>\n | Figure 129 \u2013 Client\/server model four-part interactions: Response delivery failure <\/td>\n<\/tr>\n | ||||||
533<\/td>\n | Table 275 \u2013 Read service <\/td>\n<\/tr>\n | ||||||
537<\/td>\n | Table 276 \u2013 Write service <\/td>\n<\/tr>\n | ||||||
541<\/td>\n | Table 277 \u2013 Execute service <\/td>\n<\/tr>\n | ||||||
545<\/td>\n | Figure 130 \u2013 AlertReport and AlertAcknowledge, delivery success <\/td>\n<\/tr>\n | ||||||
546<\/td>\n | Figure 131 \u2013 AlertReport, delivery failure Figure 132 \u2013 Alert Report, acknowledgment failure <\/td>\n<\/tr>\n | ||||||
547<\/td>\n | Table 278 \u2013 AlertReport service <\/td>\n<\/tr>\n | ||||||
550<\/td>\n | Table 279 \u2013 AlertAcknowledge service <\/td>\n<\/tr>\n | ||||||
553<\/td>\n | Figure 133 \u2013 Concatenated response for multiple outstandingwrite requests (no message loss) <\/td>\n<\/tr>\n | ||||||
554<\/td>\n | Table 280 \u2013 Tunnel service <\/td>\n<\/tr>\n | ||||||
557<\/td>\n | 12.18 Application layer flow use to lower layer services Table 281 \u2013 Application flow characteristics <\/td>\n<\/tr>\n | ||||||
558<\/td>\n | 12.19 Application layer management Table 282 \u2013 Application service primitive to transport service primitive mapping <\/td>\n<\/tr>\n | ||||||
559<\/td>\n | Figure 134 \u2013 Management and handling of malformed APDUs received from device X <\/td>\n<\/tr>\n | ||||||
560<\/td>\n | Table 283 \u2013 ASLMO attributes <\/td>\n<\/tr>\n | ||||||
561<\/td>\n | Table 284 \u2013 Application sub-layer management object methods <\/td>\n<\/tr>\n | ||||||
562<\/td>\n | Table 285 \u2013Reset method <\/td>\n<\/tr>\n | ||||||
563<\/td>\n | Table 286 \u2013 ASLMO alerts <\/td>\n<\/tr>\n | ||||||
566<\/td>\n | Table 287 \u2013 Analog input object attributes <\/td>\n<\/tr>\n | ||||||
567<\/td>\n | Table 288 \u2013 Analog input object methods <\/td>\n<\/tr>\n | ||||||
568<\/td>\n | Table 289 \u2013 Analog input alerts <\/td>\n<\/tr>\n | ||||||
569<\/td>\n | Table 290 \u2013 Analog output attributes <\/td>\n<\/tr>\n | ||||||
570<\/td>\n | Table 291 \u2013 Analog output object methods <\/td>\n<\/tr>\n | ||||||
571<\/td>\n | Table 292 \u2013 Analog output alerts <\/td>\n<\/tr>\n | ||||||
573<\/td>\n | Table 293 \u2013 Binary input object attributes <\/td>\n<\/tr>\n | ||||||
574<\/td>\n | Table 294 \u2013 Binary input object methods Table 295 \u2013 Binary input alerts <\/td>\n<\/tr>\n | ||||||
575<\/td>\n | Table 296 \u2013 Binary output attributes <\/td>\n<\/tr>\n | ||||||
576<\/td>\n | Table 297 \u2013 Binary output object methods Table 298 \u2013 Binary output alerts <\/td>\n<\/tr>\n | ||||||
577<\/td>\n | 12.20 Process control industry standard data structures <\/td>\n<\/tr>\n | ||||||
578<\/td>\n | Table 299 \u2013 Status octet Table 300 \u2013 Data type: Process value and status for analog value <\/td>\n<\/tr>\n | ||||||
579<\/td>\n | Table 301 \u2013 Data type: Process value and status for binary value Table 302 \u2013 Data type: Process control mode <\/td>\n<\/tr>\n | ||||||
580<\/td>\n | 12.21 Additional tables Table 303 \u2013 Data type: Process control mode bitstring Table 304 \u2013 Data type: Process control scaling <\/td>\n<\/tr>\n | ||||||
581<\/td>\n | 12.22 Coding Table 305 \u2013 Process control standard objects Table 306 \u2013 Services <\/td>\n<\/tr>\n | ||||||
582<\/td>\n | Table 307 \u2013 Application messaging format Table 308 \u2013 Concatenated APDUs in a single TSDU Table 309 \u2013 Object addressing <\/td>\n<\/tr>\n | ||||||
583<\/td>\n | Table 310 \u2013 Four-bit addressing mode APDU header construction Table 311 \u2013 Eight-bit addressing mode APDU header construction Table 312 \u2013 Sixteen-bit addressing mode APDU header construction <\/td>\n<\/tr>\n | ||||||
584<\/td>\n | Table 313 \u2013 Inferred addressing use case example Table 314 \u2013 Inferred addressing mode APDU header construction <\/td>\n<\/tr>\n | ||||||
585<\/td>\n | Table 315 \u2013 Six-bit attribute identifier, not indexed Table 316 \u2013 Six-bit attribute identifier, singly indexed, with seven-bit index Table 317 \u2013 Six-bit attribute identifier, singly indexed, with fifteen-bit index Table 318 \u2013 Six-bit attribute identifier, doubly indexed, with two seven-bit indices <\/td>\n<\/tr>\n | ||||||
586<\/td>\n | Table 319 \u2013 Six-bit attribute identifier, doubly indexed, with two fifteen-bit indices Table 320 \u2013 Six-bit attribute identifier, doubly indexed,with first index seven-bits long and second index fifteen bits long Table 321 \u2013 Six-bit attribute bit attribute identifier, doubly indexed,with first index fifteen bits long and second index seven bits long Table 322 \u2013 Twelve-bit attribute identifier, not indexed <\/td>\n<\/tr>\n | ||||||
587<\/td>\n | Table 323 \u2013 Twelve-bit attribute identifier, singly indexed with seven-bit index Table 324 \u2013 Twelve-bit attribute identifier, singly indexed with fifteen bit identifier Table 325 \u2013 Twelve-bit attribute identifier, doubly indexed with two seven bit indices Table 326 \u2013 Twelve-bit attribute identifier, doubly indexed with two fifteen bit indices Table 327 \u2013 Twelve-bit attribute identifier, doubly indexed with first index seven-bits long and second index fifteen-bits long <\/td>\n<\/tr>\n | ||||||
588<\/td>\n | Table 328 \u2013 Twelve-bit attribute identifier, doubly indexed with the first index fifteen bits long and the second index seven bits long Table 329 \u2013 Twelve-bit attribute identifier, reserved form Table 330 \u2013 Coding rules for read service request Table 331 \u2013 Coding rules for read service response with seven bit length field <\/td>\n<\/tr>\n | ||||||
589<\/td>\n | Table 332 \u2013 Coding rules for read service response with fifteen-bit length field Table 333 \u2013 Coding rules for write service request with seven bit length field Table 334 \u2013 Coding rules for write service request with fifteen-bit length field Table 335 \u2013 Coding rules for write service response <\/td>\n<\/tr>\n | ||||||
590<\/td>\n | Table 336 \u2013 Coding rules for execute service request with seven-bit length field Table 337 \u2013 Coding rules for execute service request with fifteen-bit length field Table 338 \u2013 Coding rules for execute service response with 7-bit length field Table 339 \u2013 Coding rules for execute service response with 15-bit length field <\/td>\n<\/tr>\n | ||||||
591<\/td>\n | Table 340 \u2013 Coding rules for tunnel service request with seven-bit length field Table 341 \u2013 Coding rules for tunnel service request with fifteen-bit length field Table 342 \u2013 Coding rules for tunnel service response with seven-bit length field Table 343 \u2013 Coding rules for tunnel service response with fifteen-bit length field <\/td>\n<\/tr>\n | ||||||
592<\/td>\n | Table 344 \u2013 Coding rules for AlertReport service with seven bit length field Table 345 \u2013 Coding rules for AlertReport service with fifteen-bit length field Table 346 \u2013 Coding rules for AlertAcknowledge service <\/td>\n<\/tr>\n | ||||||
593<\/td>\n | Table 347 \u2013 Coding rules for publish service for a native sequence of values Table 348 \u2013 Coding rules for publish service \u2013 non-native (for tunnel support) Table 349 \u2013 Coding rules for concatenate service Table 350 \u2013 General coding rule for size-invariant application data <\/td>\n<\/tr>\n | ||||||
594<\/td>\n | Table 351 \u2013 Coding rules for application data of varying size Table 352 \u2013 Coding rules for Boolean data \u2013 true Table 353 \u2013 Coding rules for Boolean data \u2013 false <\/td>\n<\/tr>\n | ||||||
595<\/td>\n | Table 354 \u2013 Coding rules for Unsigned8 Table 355 \u2013 Coding rules for Unsigned16 <\/td>\n<\/tr>\n | ||||||
596<\/td>\n | Table 356 \u2013 Coding rules for Unsigned32 Table 357 \u2013 Coding rules for Unsigned64 <\/td>\n<\/tr>\n | ||||||
597<\/td>\n | Table 358 \u2013 Coding rules for Unsigned128 Table 359 \u2013 Coding rules for Float <\/td>\n<\/tr>\n | ||||||
598<\/td>\n | Table 360 \u2013 Coding rules for double-precision float Table 361 \u2013 Coding rules for VisibleString Table 362 \u2013 Coding rules for OctetString <\/td>\n<\/tr>\n | ||||||
599<\/td>\n | Table 363 \u2013 Coding rules for Bitstring Table 364 \u2013 Example of coding for Bitstring of size 8 <\/td>\n<\/tr>\n | ||||||
600<\/td>\n | Table 365 \u2013 Coding rules for TAITimeDifference Table 366 \u2013 Coding rules for TAINetworkTimeValue Table 367 \u2013 Coding rules for TAITimeRounded <\/td>\n<\/tr>\n | ||||||
602<\/td>\n | 12.23 Syntax <\/td>\n<\/tr>\n | ||||||
615<\/td>\n | 12.24 Detailed coding examples (INFORMATIVE) Table 368 \u2013 Coding example: Read request for a non-indexed attribute <\/td>\n<\/tr>\n | ||||||
616<\/td>\n | 13 Gateway 13.1 General Table 369 \u2013 Coding example: Read response (corresponding to request containedin the preceding table) Table 370 \u2013 Coding example: Tunnel service request <\/td>\n<\/tr>\n | ||||||
618<\/td>\n | Figure 135 \u2013 Gateway scenarios <\/td>\n<\/tr>\n | ||||||
619<\/td>\n | Figure 136 \u2013 Basic gateway model <\/td>\n<\/tr>\n | ||||||
620<\/td>\n | 13.2 Service access point <\/td>\n<\/tr>\n | ||||||
621<\/td>\n | Table 371 \u2013 Summary of gateway high side interface services <\/td>\n<\/tr>\n | ||||||
622<\/td>\n | Figure 137 \u2013 Sequence of primitives for session service Figure 138 \u2013 Sequence of primitives for lease management service <\/td>\n<\/tr>\n | ||||||
623<\/td>\n | Figure 139 \u2013 Sequence of primitives for system report services Figure 140 \u2013 Sequence of primitives for time service <\/td>\n<\/tr>\n | ||||||
624<\/td>\n | Figure 141 \u2013 Sequence of primitives for client\/server service initiated from gateway Figure 142 \u2013 Sequence of primitives for publish service initiated from gateway <\/td>\n<\/tr>\n | ||||||
625<\/td>\n | Figure 143 \u2013 Sequence of primitives for subscribe service initiated from device Figure 144 \u2013 Sequence of primitives for publisher timer initiated from gateway Figure 145 \u2013 Sequence of primitives for subscriber timers initiated from device <\/td>\n<\/tr>\n | ||||||
626<\/td>\n | Figure 146 \u2013 Sequence of primitives for the bulk transfer service Figure 147 \u2013 Sequence of primitives for the alert subscription service <\/td>\n<\/tr>\n | ||||||
627<\/td>\n | Figure 148 \u2013 Sequence of primitives for the alert notification service Figure 149 \u2013 Sequence of primitives for gateway management services <\/td>\n<\/tr>\n | ||||||
630<\/td>\n | Table 372 \u2013 Primitive G_Session parameter usage <\/td>\n<\/tr>\n | ||||||
631<\/td>\n | Table 373 \u2013 GS_Status for G_Session confirm <\/td>\n<\/tr>\n | ||||||
632<\/td>\n | Table 374 \u2013 Primitive G_Lease parameter usage <\/td>\n<\/tr>\n | ||||||
633<\/td>\n | Table 375 \u2013 GS_Lease_Type for G_Lease request <\/td>\n<\/tr>\n | ||||||
634<\/td>\n | Table 376 \u2013 GS_Status for G_Lease confirm <\/td>\n<\/tr>\n | ||||||
635<\/td>\n | Table 377 \u2013 Primitive G_Device_List_Report parameter usage <\/td>\n<\/tr>\n | ||||||
636<\/td>\n | Table 378 \u2013 GS_Status for G_Device_List_Report confirm Table 379 \u2013 Primitive G_Topology_Report parameter usage <\/td>\n<\/tr>\n | ||||||
637<\/td>\n | Table 380 \u2013 GS_Status for G_Topology_Report confirm <\/td>\n<\/tr>\n | ||||||
638<\/td>\n | Table 381 \u2013 Primitive G_Schedule_Report parameter usage <\/td>\n<\/tr>\n | ||||||
639<\/td>\n | Table 382 \u2013 GS_Status for G_Schedule_Report confirm <\/td>\n<\/tr>\n | ||||||
640<\/td>\n | Table 383 \u2013 Primitive G_Device_Health_Report parameter usage Table 384 \u2013 GS_Status for G_Device_Health_Report confirm <\/td>\n<\/tr>\n | ||||||
641<\/td>\n | Table 385 \u2013 Primitive G_Neighbor_Health_Report parameter usage <\/td>\n<\/tr>\n | ||||||
642<\/td>\n | Table 386 \u2013 GS_Status for G_Device_Health_Report confirm <\/td>\n<\/tr>\n | ||||||
643<\/td>\n | Table 387 \u2013 Primitive G_Network_Health_Report parameter usage <\/td>\n<\/tr>\n | ||||||
644<\/td>\n | Table 388 \u2013 GS_Status for G_Network_Health_Report confirm <\/td>\n<\/tr>\n | ||||||
645<\/td>\n | Table 389 \u2013 Primitive G_Time parameter usage Table 390 \u2013 GS_Status for G_Time confirm <\/td>\n<\/tr>\n | ||||||
646<\/td>\n | Table 391 \u2013 Primitive G_Client_Server parameter usage <\/td>\n<\/tr>\n | ||||||
647<\/td>\n | Table 392 \u2013 GS_Status for G_Client_Server confirm <\/td>\n<\/tr>\n | ||||||
649<\/td>\n | Table 393 \u2013 Primitive G_Publish parameter usage <\/td>\n<\/tr>\n | ||||||
650<\/td>\n | Table 394 \u2013 GS_Status for G_Publish confirm Table 395 \u2013 Primitive G_Subscribe parameter usage <\/td>\n<\/tr>\n | ||||||
651<\/td>\n | Table 396 \u2013 GS_Status for G_Subscribe confirm Table 397 \u2013 Primitive G_Publish_Timer parameter usage Table 398 \u2013 Primitive G_Subscribe_Timer parameter usage <\/td>\n<\/tr>\n | ||||||
652<\/td>\n | Table 399 \u2013 Primitive G_Publish_Watchdog parameter usage <\/td>\n<\/tr>\n | ||||||
653<\/td>\n | Table 400 \u2013 Primitive G_Bulk_Open parameter usage <\/td>\n<\/tr>\n | ||||||
654<\/td>\n | Table 401 \u2013 GS_Status for G_Bulk_Open confirm Table 402 \u2013 Primitive G_Bulk_Transfer parameter usage Table 403 \u2013 GS_Status for G_Bulk_Transfer confirm <\/td>\n<\/tr>\n | ||||||
655<\/td>\n | Table 404 \u2013 Primitive G_Bulk_Close parameter usage Table 405 \u2013 GS_Status for G_Bulk_Close confirm <\/td>\n<\/tr>\n | ||||||
656<\/td>\n | Table 406 \u2013 Primitive G_Alert_Subscription parameter usage <\/td>\n<\/tr>\n | ||||||
657<\/td>\n | Table 407 \u2013 GS_Status for G_Alert_Subscription confirm Table 408 \u2013 Primitive G_Alert_Notification parameter usage <\/td>\n<\/tr>\n | ||||||
658<\/td>\n | Table 409 \u2013 Primitive G_Read_Gateway_Configuration parameter usage <\/td>\n<\/tr>\n | ||||||
659<\/td>\n | Table 410 \u2013 GS_Attribute_Identifier values Table 411 \u2013 GS_Status for G_Read_Gateway_Configuration confirm Table 412 \u2013 Primitive G_Write_Gateway_Configuration parameter usage <\/td>\n<\/tr>\n | ||||||
660<\/td>\n | Table 413 \u2013 GS_Attribute_Identifier values Table 414 \u2013 GS_Status for G_Write_Gateway_Configuration confirm <\/td>\n<\/tr>\n | ||||||
661<\/td>\n | Table 415 \u2013 Primitive G_Write_Device_Configuration parameter usage <\/td>\n<\/tr>\n | ||||||
662<\/td>\n | Table 416 \u2013 GS_Status for G_Write_Device_Configuration confirm Table 417 \u2013 Primitive G_Read_Device_Configuration parameter usage <\/td>\n<\/tr>\n | ||||||
663<\/td>\n | 13.3 Protocol Figure 150 \u2013 Tunnel object model Table 418 \u2013 GS_Status for G_Read_Device_Configuration confirm <\/td>\n<\/tr>\n | ||||||
664<\/td>\n | Figure 151 \u2013 Distributed tunnel endpoints <\/td>\n<\/tr>\n | ||||||
665<\/td>\n | Figure 152 \u2013 Multicast, broadcast, and one-to-many messaging <\/td>\n<\/tr>\n | ||||||
666<\/td>\n | Figure 153 \u2013 Tunnel object buffering <\/td>\n<\/tr>\n | ||||||
669<\/td>\n | Figure 154 \u2013 Publish\/subscribe publisher CoSt flowchart Figure 155 \u2013 Publish\/subscribe publisher periodic flowchart <\/td>\n<\/tr>\n | ||||||
670<\/td>\n | Figure 156 \u2013 Publish\/subscribe subscriber common periodic and CoSt flowchart <\/td>\n<\/tr>\n | ||||||
671<\/td>\n | Figure 157 \u2013 Network address mappings <\/td>\n<\/tr>\n | ||||||
672<\/td>\n | Figure 158 \u2013 Connection_Info usage in protocol translation <\/td>\n<\/tr>\n | ||||||
673<\/td>\n | Figure 159 \u2013 Transaction_Info usage in protocol translation <\/td>\n<\/tr>\n | ||||||
674<\/td>\n | Figure 160 \u2013 Interoperable tunneling mechanism overview diagram <\/td>\n<\/tr>\n | ||||||
676<\/td>\n | Figure 161 \u2013 Bulk transfer model <\/td>\n<\/tr>\n | ||||||
677<\/td>\n | Figure 162 \u2013 Alert model <\/td>\n<\/tr>\n | ||||||
678<\/td>\n | Figure 163 \u2013 Alert cascading <\/td>\n<\/tr>\n | ||||||
679<\/td>\n | Figure 164 \u2013 Native P\/S and C\/S access <\/td>\n<\/tr>\n | ||||||
681<\/td>\n | Table 419 \u2013 UAP management object extended attributes <\/td>\n<\/tr>\n | ||||||
682<\/td>\n | 14 Provisioning 14.1 General 14.2 Terms and definitions <\/td>\n<\/tr>\n | ||||||
684<\/td>\n | 14.3 Provisioning procedures 14.4 Pre-installed symmetric keys <\/td>\n<\/tr>\n | ||||||
685<\/td>\n | 14.5 Provisioning using out-of-band mechanisms 14.6 Provisioning networks <\/td>\n<\/tr>\n | ||||||
686<\/td>\n | Figure 165 \u2013 The provisioning network <\/td>\n<\/tr>\n | ||||||
688<\/td>\n | 14.7 State transition diagrams Figure 166 \u2013 State transition diagrams outlining provisioning stepsduring a device life cycle <\/td>\n<\/tr>\n | ||||||
689<\/td>\n | Table 420 \u2013 Factory default settings <\/td>\n<\/tr>\n | ||||||
691<\/td>\n | Figure 167 \u2013 State transition diagram showing various pathsto joining a secured network <\/td>\n<\/tr>\n | ||||||
693<\/td>\n | 14.8 Device management application protocol objects for provisioning Figure 168 \u2013 Provisioning objects and interactions <\/td>\n<\/tr>\n | ||||||
694<\/td>\n | 14.9 Management objects <\/td>\n<\/tr>\n | ||||||
695<\/td>\n | Table 421 \u2013 Device provisioning object <\/td>\n<\/tr>\n | ||||||
699<\/td>\n | 14.10 Device provisioning service object Table 422 \u2013 Reset_To_Default method Table 423 \u2013 Write symmetric join key method <\/td>\n<\/tr>\n | ||||||
700<\/td>\n | Table 424 \u2013 Device provisioning service object <\/td>\n<\/tr>\n | ||||||
703<\/td>\n | Table 425 \u2013 DPSOWhiteListTbl data structure <\/td>\n<\/tr>\n | ||||||
705<\/td>\n | Table 426 \u2013 Array manipulation table Table 427 \u2013 DPSO alert to indicate join by a device not on the WhiteList <\/td>\n<\/tr>\n | ||||||
706<\/td>\n | 14.11 Provisioning functions (INFORMATIVE) Table 428 \u2013 DPSO alert to indicate inadequate device join capability <\/td>\n<\/tr>\n | ||||||
710<\/td>\n | Annex A (informative) Protocol implementation conformance statement proforma A.1 General <\/td>\n<\/tr>\n | ||||||
713<\/td>\n | A.2 System Table 429 \u2013 Field media type Table 430 \u2013 Protocol layer support <\/td>\n<\/tr>\n | ||||||
714<\/td>\n | Table 431 \u2013 Device PICS Table 432 \u2013 PICS for device implementing I\/O role Table 433 \u2013 PICS for device implementing router role Table 434 \u2013 PICS for backbone router <\/td>\n<\/tr>\n | ||||||
715<\/td>\n | Table 435 \u2013 PICS for gateway Table 436 \u2013 PICS for system manager Table 437 \u2013 PICS for provisioning device Table 438 \u2013 PICS for security manager Table 439 \u2013 PICS for device implementing system time source role <\/td>\n<\/tr>\n | ||||||
716<\/td>\n | A.3 System management Table 440 \u2013 System PICS <\/td>\n<\/tr>\n | ||||||
717<\/td>\n | Table 441 \u2013 Device PICS Table 442 \u2013 Router and backbone router PICS <\/td>\n<\/tr>\n | ||||||
718<\/td>\n | Table 443 \u2013 PICS for system time source <\/td>\n<\/tr>\n | ||||||
719<\/td>\n | Table 444 \u2013 PICS for system manager Table 445 \u2013 PICS for provisioning role <\/td>\n<\/tr>\n | ||||||
720<\/td>\n | A.4 Security manager Table 446 \u2013 Device PICS <\/td>\n<\/tr>\n | ||||||
721<\/td>\n | A.5 Physical layer Table 447 \u2013 PICS for provisioning role Table 448 \u2013 PICS for security manager <\/td>\n<\/tr>\n | ||||||
722<\/td>\n | Table 449 \u2013 PhL roles Table 450 \u2013 PhL frequency of operation Table 451 \u2013 PhL functions <\/td>\n<\/tr>\n | ||||||
723<\/td>\n | A.6 Data link layer Table 452 \u2013 PhL packet Table 453 \u2013 DL roles Table 454 \u2013 DL PICS for device implementing I\/O role Table 455 \u2013 DL PICS for device implementing router role <\/td>\n<\/tr>\n | ||||||
724<\/td>\n | A.7 Network layer Table 456 \u2013 DL PICS for device implementing backbone router role Table 457 \u2013 PICS for devices implementing I\/O role <\/td>\n<\/tr>\n | ||||||
725<\/td>\n | Table 458 \u2013 PICS for device implementing router role Table 459 \u2013 PICS for devices implementing backbone router role <\/td>\n<\/tr>\n | ||||||
726<\/td>\n | A.8 Transport layer Table 460 \u2013 PICS for device implementing I\/O role Table 461 \u2013 PICS for routing device Table 462 \u2013 PICS for backbone router <\/td>\n<\/tr>\n | ||||||
727<\/td>\n | A.9 Application layer Table 463 \u2013 AL implementation option Table 464 \u2013 PICS part 2: Optional industry-independent objects <\/td>\n<\/tr>\n | ||||||
728<\/td>\n | Table 465 \u2013 PICS part 2: Supported standard services for I\/O device role <\/td>\n<\/tr>\n | ||||||
729<\/td>\n | Table 466 \u2013 PICS part 2: Supported standard services for system manager role <\/td>\n<\/tr>\n | ||||||
730<\/td>\n | Table 467 \u2013 PICS part 2: Supported standard services for gateway rolewhen supporting native access <\/td>\n<\/tr>\n | ||||||
731<\/td>\n | Table 468 \u2013 PICS part 2: Supported standard services for gateway rolewhen supporting interoperable tunneling and for adapters <\/td>\n<\/tr>\n | ||||||
732<\/td>\n | Table 469 \u2013 PICS part 2: Supported standard services for routing device role <\/td>\n<\/tr>\n | ||||||
733<\/td>\n | Table 470 \u2013 PICS part 2: Supported standard services for backbone router role <\/td>\n<\/tr>\n | ||||||
734<\/td>\n | Table 471 \u2013 PICS part 2: Supported standard services for provisioning role Table 472 \u2013 PICS part 2: Supported standard services for system time source role Table 473 \u2013 Process control conformance: Supported objects <\/td>\n<\/tr>\n | ||||||
735<\/td>\n | A.10 Gateway Table 474 \u2013 Process control conformance: Supported alerts <\/td>\n<\/tr>\n | ||||||
736<\/td>\n | Table 475 \u2013 PICS: Gateway <\/td>\n<\/tr>\n | ||||||
737<\/td>\n | A.11 Provisioning <\/td>\n<\/tr>\n | ||||||
738<\/td>\n | Table 476 \u2013 PICS: I\/O devices, routing devices, gateways, and backbone routers Table 477 \u2013 PICS: Provisioning devices <\/td>\n<\/tr>\n | ||||||
739<\/td>\n | Annex B (normative) Role profiles B.1 General <\/td>\n<\/tr>\n | ||||||
740<\/td>\n | B.2 System B.3 System manager Table 478 \u2013 Protocol layer device roles Table 479 \u2013 Over-the-air upgrades <\/td>\n<\/tr>\n | ||||||
741<\/td>\n | B.4 Security manager Table 480 \u2013 Session support profiles Table 481 \u2013 Baseline profiles <\/td>\n<\/tr>\n | ||||||
742<\/td>\n | B.5 Physical layer B.6 Data link layer Table 482 \u2013 PhL roles Table 483 \u2013 DL required for listed roles <\/td>\n<\/tr>\n | ||||||
743<\/td>\n | Table 484 \u2013 Role profiles: General DLMO attributes <\/td>\n<\/tr>\n | ||||||
744<\/td>\n | Table 485 \u2013 Role profiles: dlmo.Device_Capability <\/td>\n<\/tr>\n | ||||||
745<\/td>\n | Table 486 \u2013 Role profiles: dlmo.Ch (channel hopping) Table 487 \u2013 Role profiles: dlmo.TsTemplate Table 488 \u2013 Role profiles: dlmo.Neighbor <\/td>\n<\/tr>\n | ||||||
746<\/td>\n | Table 489 \u2013 Role profiles: dlmo. NeighborDiag Table 490 \u2013 Role profiles: dlmo.Superframe Table 491 \u2013 Role profiles: dlmo.Graph <\/td>\n<\/tr>\n | ||||||
747<\/td>\n | B.7 Network layer Table 492 \u2013 Role profiles: dlmo.Link Table 493 \u2013 Role profiles: dlmo.Route Table 494 \u2013 Role profiles: dlmo.Queue_Priority Table 495 \u2013 Routing table size <\/td>\n<\/tr>\n | ||||||
748<\/td>\n | B.8 Transport layer B.9 Application layer B.10 Gateway Table 496 \u2013 Address table size Table 497 \u2013 Port support size Table 498 \u2013 APs Table 499 \u2013 Role profile: Gateway <\/td>\n<\/tr>\n | ||||||
749<\/td>\n | B.11 Provisioning Table 500 \u2013 Role profile: Gateway native access Table 501 \u2013 Role profile: Gateway interoperable tunnel mechanism Table 502 \u2013 Role profiles: I\/O, routers, gateways, and backbone routers <\/td>\n<\/tr>\n | ||||||
750<\/td>\n | Annex C (informative) Background information C.1 Industrial needs C.2 Usage classes <\/td>\n<\/tr>\n | ||||||
751<\/td>\n | Table 503 \u2013 Usage classes <\/td>\n<\/tr>\n | ||||||
752<\/td>\n | C.3 Other uploading and downloading- alarms (human or automated action) C.4 The open systems interconnection basic reference model <\/td>\n<\/tr>\n | ||||||
753<\/td>\n | Figure 169 \u2013 Basic reference model <\/td>\n<\/tr>\n | ||||||
756<\/td>\n | Annex D (normative) Configuration defaults D.1 General D.2 System management Table 504 \u2013 System management configuration defaults <\/td>\n<\/tr>\n | ||||||
757<\/td>\n | D.3 Security D.4 Data link layer Table 505 \u2013 Security configuration defaults <\/td>\n<\/tr>\n | ||||||
758<\/td>\n | D.5 Network layer Table 506 \u2013 DL configuration defaults <\/td>\n<\/tr>\n | ||||||
759<\/td>\n | D.6 Transport layer D.7 Application layer Table 507 \u2013 Network configuration defaults Table 508 \u2013 Transport configuration defaults <\/td>\n<\/tr>\n | ||||||
760<\/td>\n | Table 509 \u2013 Application configuration defaults <\/td>\n<\/tr>\n | ||||||
761<\/td>\n | D.8 Gateway D.9 Provisioning Table 510 \u2013 Gateway configuration defaults <\/td>\n<\/tr>\n | ||||||
762<\/td>\n | Table 511 \u2013 Provisioning configuration defaults <\/td>\n<\/tr>\n | ||||||
763<\/td>\n | Annex E (informative) Use of backbone networks E.1 General E.2 Recommended characteristics E.3 Internet protocol backbones <\/td>\n<\/tr>\n | ||||||
766<\/td>\n | Annex F (normative) Basic security concepts \u2013 Notation and representation F.1 Strings and string operations F.2 Integers, octets, and their representation F.3 Entities <\/td>\n<\/tr>\n | ||||||
767<\/td>\n | Annex G (informative) Using certificate chains for over-the-air provisioning <\/td>\n<\/tr>\n | ||||||
768<\/td>\n | Annex H (normative) Security building blocks H.1 Symmetric key cryptographic building blocks <\/td>\n<\/tr>\n | ||||||
769<\/td>\n | H.2 Asymmetric key cryptographic building blocks H.3 Keying information <\/td>\n<\/tr>\n | ||||||
771<\/td>\n | H.4 Key agreement schemes H.5 Keying information schemes <\/td>\n<\/tr>\n | ||||||
772<\/td>\n | H.6 Challenge domain parameter generation and validation <\/td>\n<\/tr>\n | ||||||
773<\/td>\n | H.7 Challenge validation primitive H.8 Secret key generation (SKG) primitive <\/td>\n<\/tr>\n | ||||||
774<\/td>\n | H.9 Block-cipher-based cryptographic hash function <\/td>\n<\/tr>\n | ||||||
775<\/td>\n | H.10 Elliptic curve cryptography manual certificate scheme <\/td>\n<\/tr>\n | ||||||
778<\/td>\n | Annex I (informative) Definition templates I.1 Object type template I.2 Standard object attributes template Table 512 \u2013 Table of standard object types <\/td>\n<\/tr>\n | ||||||
779<\/td>\n | I.3 Standard object methods Table 513 \u2013 Template for standard object attributes <\/td>\n<\/tr>\n | ||||||
780<\/td>\n | I.4 Standard object alert reporting template Table 514 \u2013 Template for standard object methods <\/td>\n<\/tr>\n | ||||||
781<\/td>\n | I.5 Data structure definition Table 515 \u2013 Template for standard object alert reporting <\/td>\n<\/tr>\n | ||||||
782<\/td>\n | Table 516 \u2013 Template for data structures <\/td>\n<\/tr>\n | ||||||
783<\/td>\n | Annex J (informative) Operations on attributes J.1 Operations on attributes Table 517 \u2013 Scheduled_Write method template <\/td>\n<\/tr>\n | ||||||
784<\/td>\n | Table 518 \u2013 Read_Row method template <\/td>\n<\/tr>\n | ||||||
785<\/td>\n | Table 519 \u2013 Write_Row method template Table 520 \u2013 Reset_Row method template <\/td>\n<\/tr>\n | ||||||
786<\/td>\n | J.2 Synchronized cutover Table 521 \u2013 Delete_Row method template <\/td>\n<\/tr>\n | ||||||
788<\/td>\n | Annex K (normative) Standard object types <\/td>\n<\/tr>\n | ||||||
790<\/td>\n | Table 522 \u2013 Standard object types <\/td>\n<\/tr>\n | ||||||
792<\/td>\n | Table 523 \u2013 Standard object instances <\/td>\n<\/tr>\n | ||||||
794<\/td>\n | Annex L (informative) Standard data types <\/td>\n<\/tr>\n | ||||||
795<\/td>\n | Table 524 \u2013 Standard data types <\/td>\n<\/tr>\n | ||||||
796<\/td>\n | Annex M (normative) Protocol identification values Table 525 \u2013 Protocol identification values <\/td>\n<\/tr>\n | ||||||
797<\/td>\n | Annex N (informative) Tunneling and native object mapping N.1 Overview N.2 Tunneling N.3 Foreign protocol application communication <\/td>\n<\/tr>\n | ||||||
798<\/td>\n | N.4 Native object mapping N.5 Tunneling and native object mapping tradeoffs <\/td>\n<\/tr>\n | ||||||
799<\/td>\n | Annex O (informative) Generic protocol translation O.1 Overview O.2 Publish Figure 170 \u2013 Generic protocol translation publish diagram <\/td>\n<\/tr>\n | ||||||
800<\/td>\n | O.3 Subscribe Figure 171 \u2013 Generic protocol translation subscribe diagram <\/td>\n<\/tr>\n | ||||||
801<\/td>\n | O.4 Client Figure 172 \u2013 Generic protocol translation client\/server transmission diagram <\/td>\n<\/tr>\n | ||||||
802<\/td>\n | O.5 Server Figure 173 \u2013 Generic protocol translation client\/server reception diagram <\/td>\n<\/tr>\n | ||||||
803<\/td>\n | Annex P (informative) Gateway service access point adaptations for this specification P.1 General P.2 Parameters P.3 Session P.4 Lease <\/td>\n<\/tr>\n | ||||||
804<\/td>\n | P.5 Device list report P.6 Topology report P.7 Schedule report P.8 Device health report P.9 Neighbor health report P.10 Network health report P.11 Time P.12 Client\/server <\/td>\n<\/tr>\n | ||||||
805<\/td>\n | P.13 Publish\/subscribe <\/td>\n<\/tr>\n | ||||||
806<\/td>\n | P.14 Bulk transfer <\/td>\n<\/tr>\n | ||||||
807<\/td>\n | P.15 Alert P.16 Gateway configuration P.17 Device configuration <\/td>\n<\/tr>\n | ||||||
808<\/td>\n | Annex Q (informative) Gateway service access point adaptations for WirelessHART\u00ae Q.1 General <\/td>\n<\/tr>\n | ||||||
809<\/td>\n | Q.2 Parameters Q.3 Session <\/td>\n<\/tr>\n | ||||||
810<\/td>\n | Q.4 Lease Q.5 Device list report <\/td>\n<\/tr>\n | ||||||
811<\/td>\n | Q.6 Topology report Q.7 Schedule report Q.8 Device health report <\/td>\n<\/tr>\n | ||||||
812<\/td>\n | Q.9 Neighbor health report Q.10 Network health report <\/td>\n<\/tr>\n | ||||||
813<\/td>\n | Q.11 Time Q.12 Client\/server <\/td>\n<\/tr>\n | ||||||
814<\/td>\n | Q.13 Publish\/subscribe <\/td>\n<\/tr>\n | ||||||
815<\/td>\n | Q.14 Bulk transfer Q.15 Alert <\/td>\n<\/tr>\n | ||||||
816<\/td>\n | Q.16 Gateway configuration Q.17 Device configuration <\/td>\n<\/tr>\n | ||||||
817<\/td>\n | Annex R (informative) Host system interface to standard-compliant devices via a gateway R.1 Background Figure 174 \u2013 Host integration reference model <\/td>\n<\/tr>\n | ||||||
818<\/td>\n | R.2 Device application data integration with host systems R.3 Host system configuration tool <\/td>\n<\/tr>\n | ||||||
819<\/td>\n | Figure 175 \u2013 Configuration using an electronic device definition <\/td>\n<\/tr>\n | ||||||
820<\/td>\n | R.4 Field device \/ distributed control systems integration Figure 176 \u2013 Configuration using FDT\/DTM approach <\/td>\n<\/tr>\n | ||||||
821<\/td>\n | R.5 Gateway R.6 Asset management application support <\/td>\n<\/tr>\n | ||||||
823<\/td>\n | Annex S (informative) Symmetric Key Operation Test Vectors S.1 DPDU samples <\/td>\n<\/tr>\n | ||||||
824<\/td>\n | S.2 TPDU samples <\/td>\n<\/tr>\n | ||||||
826<\/td>\n | Annex T (informative) Data link header and network header for join requests T.1 Overview T.2 MAC header (MHR) T.3 DL header (DHR) Table 526 \u2013 Sample MHR for join request Table 527 \u2013 Sample DHR for join request <\/td>\n<\/tr>\n | ||||||
827<\/td>\n | T.4 NL header Table 528 \u2013 Network header for join messages <\/td>\n<\/tr>\n | ||||||
828<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Industrial communication networks. Fieldbus specifications. Wireless systems for industrial automation: process control and related applications<\/b><\/p>\n |