IEC 62734:2014 provides specifications in accordance with the OSI Basic Reference Model, ISO/IEC 7498-1, (e.g., PhL, DL, etc.). It is intended to provide reliable and secure wireless operation for non-critical monitoring, alerting, supervisory control, open loop control, and closed loop control applications. It defines a protocol suite, including system management, gateway considerations, and security specifications, for low-data-rate wireless connectivity with fixed, portable, and slowly-moving devices, often operating under severe energy and power constraints. The application focus is the performance needs of process automation monitoring and control where end-to-end communication latencies on the order of at least 100 ms can be tolerated.

PDF Catalog

PDF Pages	PDF Title
7	English CONTENTS
36	0 Introduction 0.1 General 0.2 Document structure 0.3 Potentially relevant patents
38	1 Scope 2 Normative references
39	3 Terms, definitions, abbreviated terms, acronyms, and conventions 3.1 Terms and definitions 3.1.1 (N)layer and other terms and definitions from the open systems interconnection Basic Reference Model
48	3.1.2 Other terms and definitions
66	3.1.3 Symbols for symmetric keys, and for asymmetric keys and certificates
67	3.1.4 Terms used to describe device behavior
68	3.2 Abbreviated terms and acronyms
74	3.3 Conventions 3.3.1 Service interfaces
75	3.3.2 Table cells 3.3.3 Italics
76	3.3.4 Bold face 3.3.5 Informal declarations of named constants 4 Overview 4.1 General 4.2 Interoperability and related issues
77	4.3 Quality of service 4.4 Worldwide applicability 4.5 Network architecture 4.5.1 Interfaces
78	4.5.2 Data structures
79	4.5.3 Network description Figures Figure 1 – Standard-compliant network
80	4.5.4 Generic protocol data unit construction Figure 2 – Typical single-layer PDU without fragmenting or blocking Figure 3 – Full multi-layer PDU structure used by this standard
81	4.5.5 Abstract data and concrete representations
83	4.6 Network characteristics 4.6.1 General 4.6.2 Scalability
84	4.6.3 Extensibility 4.6.4 Simple operation 4.6.5 Site-license-exempt operation 4.6.6 Robustness in the presence of interference, including from other wireless systems 4.6.7 Determinism and contention-free media access
85	4.6.8 Self-organizing networking with support for redundancy 4.6.9 Internet-protocol-compatible NL 4.6.10 Coexistence with other radio frequency systems
87	4.6.11 Time-slotted assigned-channel Dtransactions as the basis for communication
89	4.6.12 Robust and flexible security
90	4.6.13 System management 4.6.14 Application process using standard objects 4.6.15 Tunneling 5 System 5.1 General
91	5.2 Devices 5.2.1 General 5.2.2 Device interworkability 5.2.3 Profiles 5.2.4 Quality of service 5.2.5 Device worldwide applicability
92	5.2.6 Device description
93	Figure 4 – Physical devices versus roles
96	5.2.7 Device addressing 5.2.8 Device phases
97	Figure 5 – Notional representation of device phases
98	5.2.9 Device energy sources 5.3 Networks 5.3.1 General 5.3.2 Minimal network
99	5.3.3 Basic network topologies supported Figure 6 – Simple star topology
100	Figure 7 – Simple hub-and-spoke topology
101	Figure 8 – Mesh topology
102	5.3.4 Network configurations Figure 9 – Simple star-mesh topology
103	Figure 10 – Example where network and D-subnet overlap
104	Figure 11 – Example where network and Dsubnet differ
105	Figure 12 – Network with multiple gateways
106	Figure 13 – Basic network with backup gateway
107	5.3.5 Gateway, system manager, and security manager Figure 14 – Network with backbone
108	5.4 Protocol suite structure Figure 15 – Network with backbone – Device roles
109	5.5 Data flow 5.5.1 General Figure 16 – Reference model used by this standard
110	5.5.2 Native communications 5.5.3 Basic data flow Figure 17 – Basic data flow
111	5.5.4 Data flow between I/O devices 5.5.5 Data flow with legacy I/O device Figure 18 – Data flow between I/O devices
112	Figure 19 – Data flow with legacy I/O device
113	Figure 20 – Data flow with backbone-resident device
114	Figure 21 – Data flow between I/O devices via backbone subnet
115	5.5.6 Data flow with backbone 5.5.7 Data flow between I/O devices via backbone 5.5.8 Data flow to a standard-aware control system or device Figure 22 – Data flow to standard-aware control system
116	5.6 Time reference 5.6.1 General
117	5.6.2 Time synchronization 5.7 Firmware upgrades 5.8 Wireless backbones and other infrastructures 6 System management role 6.1 General 6.1.1 Overview
118	6.1.2 Components and architecture Figure 23 – Management architecture
119	6.1.3 Management functions 6.2 DMAP 6.2.1 General
120	6.2.2 Architecture of device management 6.2.3 Definition of management objects 6.2.4 Management objects in DMAP
121	Figure 24 – DMAP Tables Table 1 – Standard management object types in DMAP
122	6.2.5 Communications services provided to device management objects
123	6.2.6 Attributes of management objects Figure 25 – Example of management SAP flow through standard protocol suite
124	6.2.7 Definitions of management objects in DMAP Table 2 – Metadata_attribute data structure
126	Table 3 – Alert types for communication diagnostic category Table 4 – Alert types for security alert category Table 5 – Alert types for device diagnostic alert category Table 6 – Alert types for process alert category
128	Table 7 – ARMO attributes (1 of 3)
131	Table 8 – ARMO alerts
132	Table 9 – Alarm_Recovery method
133	6.2.8 Functions of device management and layer management
134	Table 10 – DMO attributes (1 of 8)
142	Table 11 – DMO alerts
143	6.3 System manager 6.3.1 General 6.3.2 System management architecture
144	6.3.3 Standard system management object types Figure 26 – System manager architecture concept
145	6.3.4 Security management Table 12 – System management object types
146	6.3.5 Addresses and address allocation
147	Table 13 – DSO attributes
148	Table 14 – Address_Translation_Row data structure Table 15 – Read_Address_Row method
150	6.3.6 Firmware upgrade Table 16 – Input argument usage for Read_Address_Row method Table 17 – Output argument usage for Read_Address_Row method
151	6.3.7 System performance monitoring
152	6.3.8 Device provisioning service 6.3.9 Device management services Table 18 – Attributes of SMO in system manager
154	Table 19 – Proxy_System_Manager_Join method
156	Table 20 – Proxy_System_Manager_Contract method
158	Table 21 – Effect of different join commands on attribute sets Table 22 – Attributes of DMSO in the system manager
159	Table 23 – System_Manager_Join method
161	6.3.10 System time services Table 24 – System_Manager_Contract method
165	6.3.11 System communication configuration Table 25 – Attributes of STSO in the system manager
166	Figure 27 – UAP-system manager interaction during contract establishment
168	Table 26 – Attributes of SCO in the system manager
169	Figure 28 – Contract-related interaction between DMO and SCO
172	Table 27 – SCO method for contract establishment, modification, or renewal (1 of 8)
180	Table 28 – Input argument usage for SCO methodfor contract establishment, modification, or renewal
181	Table 29 – Output argument usage for SCO methodfor contract establishment, modification, or renewal
182	Figure 29 – Contract source, destination, and intermediate devices
184	Table 30 – Contract_Data data structure (1 of 3)
188	Table 31 – New_Device_Contract_Response data structure (1 of 2)
191	Figure 30 – Contract establishment example
192	Figure 31 – Contract ID usage in source
194	Table 32 – SCO method for contract termination, deactivation and reactivation
195	Table 33 – DMO method to notify of contract termination
196	Figure 32 – Contract termination
197	Table 34 – DMO method to notify of contract modification
198	6.3.12 Redundancy management Figure 33 – Contract modification with immediate effect
199	6.3.13 System management protocols 6.3.14 Management policies and policy administration 6.3.15 Operational interaction with plant operations or maintenance personnel 7 Security 7.1 General
200	7.2 Security services 7.2.1 Overview Figure 34 – Examples of DPDU and TPDU scope
201	7.2.2 Keys
202	Figure 35 – Keys and associated lifetimes
204	Figure 36 – Key lifetimes
205	7.3 PDU security 7.3.1 General Table 35 – Security levels Table 36 – Structure of the security control field
206	7.3.2 DPDU security
207	Figure 37 – DPDU structure
208	Figure 38 – DLE and DLS processing for a Dtransaction initiator
210	Figure 39 – Received DPDUs – DLE and DSC
211	Table 37 – Sec.DpduPrep.Request elements
212	Table 38 – Sec.DpduPrep.Response elements Table 39 – Sec.DAckCheck.Request elements
213	Table 40 – Sec.DAckCheck.Response elements
214	Table 41 – Sec.DInitialCheck.Request elements
215	Table 42 – Sec.DInitialCheck.Response elements
216	Table 43 – Sec.DAckPrep.Request elements
217	Table 44 – Sec.DAckPrep.Response elements
218	Table 45 – Structure of the WISN DPDU nonce Table 46 – Structure of the 32bit truncated TAI time used in the Dnonce
221	7.3.3 TL security functionality
222	Figure 40 – TPDU structure and protected coverage
223	Figure 41 – TMIC parameters Table 47 – TSC pseudo-header structure
224	Figure 42 – TL and TSC interaction, outgoing TPDU
225	Figure 43 – TL and TSC interaction, incoming TPDU
226	Table 48 – Sec.TpduOutCheck.Request elements Table 49 – Sec.TpduOutCheck.Response elements
227	Table 50 – Sec.TpduSecure.Request elements
228	Table 51 – Sec. TpduSecure.Response elements
229	Table 52 – Sec.TpduInCheck.Request elements
230	Table 53 – Sec.TpduInCheck.Response elements
231	Table 54 – Sec.TpduVerify.Request elements
232	Table 55 – Sec.TpduVerify.Response elements Table 56 – Structure of TL security header
233	Table 57 – Structure of the TPDU nonce Table 58 – Structure of 32bit truncated nominal TAI time used in the Tnonce
237	7.4 Joining process 7.4.1 General 7.4.2 Prerequisites
238	7.4.3 Desired device end state and properties 7.4.4 Joining process steps common for symmetric-key and asymmetric-key approaches
241	7.4.5 Symmetric-key joining process
242	Figure 44 – Example: Overview of the symmetric-key joining process
243	Figure 45 – Example: Overview of the symmetric-key joining process of a backbone device
245	Table 59 – Proxy_Security_Sym_Join method
246	Table 60 – Security_Sym_Join method Table 61 – Security_Confirm method
247	Table 62 – Security_Sym_Join_Request data structure
248	Table 63 – Security_Sym_Join_Response data structure
249	Table 64 – Structure of compressed security level field
250	Table 65 – Master key security level Table 66 – Security_Sym_Confirm data structure
251	7.4.6 Asymmetric-key joining process
252	Table 67 – Implicit certificate format Table 68 – Usage_serial_number structure
253	Figure 46 – Asymmetric-key-authenticated key agreement scheme
256	Figure 47 – Example: Overview of the asymmetric-key joining process for a device with a DL
257	Figure 48 – Example: Overview of the asymmetric-key joining process of a backbone device
259	Table 69 – Proxy_Security_Pub_Join method
260	Table 70 – Security_Pub_Join method
261	Table 71 – Proxy_Security_Pub_Confirm method Table 72 – Security_Pub_Confirm method
262	Table 73 – Network_Information_Confirmation method
263	Table 74 – Format of asymmetric join request internal structure Table 75 – Format of the protocol control field
264	Table 76 – Format of asymmetric join response internal structure
265	Table 77 – Format of first join confirmation internal structure
266	Table 78 – Format of join confirmation response internal structure
267	7.4.7 Joining process and device lifetime failure recovery
268	Table 79 – Joining process and device lifetime state machine
269	7.5 Session establishment 7.5.1 General 7.5.2 Description Figure 49 – Device state transitions for joining process and device lifetime
270	Figure 50 – High-level example of session establishment
271	7.5.3 Application protocol data unit protection using the master key 7.5.4 Proxy security management object methods related to the session establishment Table 80 – Security_New_Session method
272	Table 81 – Security_New_Session_Request data structure
273	Table 82 – Security_New_Session_Response data structure
274	7.6 Key update 7.6.1 General 7.6.2 Description
275	7.6.3 Device security management object methods related to Tkey update Figure 51 – Key update protocol overview
276	Table 83 – New_Key method
277	Table 84 – Security_Key_and_Policies data structure
279	7.6.4 Failure recovery Table 85 – Security_Key_Update_Status data structure
280	Table 86 – Tkey and Dkey state transition
281	7.7 Functionality of the security manager role 7.7.1 Proxy security management object Figure 52 – Device key establishment and key update state transition Table 87 – Attributes of PSMO in the system manager
282	7.7.2 Authorization of network devices and generation or derivation of initial master keys 7.7.3 Interaction with device security management objects 7.7.4 Management of operational keys
283	7.8 Security policies 7.8.1 Definition of security policy 7.8.2 Policy extent
284	7.8.3 Unconstrained security policy choices 7.8.4 Policy structures Table 88 – Structure of policy field Table 89 – Key_Type
285	Table 90 – Key_Usage Table 91 – Granularity
286	7.9 Security functions available to the AL 7.9.1 Parameters on transport service requests that relate to security
287	7.9.2 Direct access to cryptographic primitives
288	7.9.3 Symmetric-key cryptography
289	7.10 Security statistics collection, threat detection, and reporting
290	7.11 DSMO functionality 7.11.1 General 7.11.2 DSMO attributes Table 92 – DSMO attributes
291	7.11.3 KeyDescriptor
292	Table 93 – KeyDescriptor
293	Table 94 – TkeyLookupData OctetString fields
294	Table 95 – Delete key method
295	Table 96 – Key_Policy_Update method
296	7.11.4 DSMO alerts
297	8 Physical layer 8.1 General Table 97 – DSMO alerts
298	8.2 Default physical layer 8.2.1 General requirements 8.2.2 Additional requirements of IEEE 802.15.4 Table 98 – Timing requirements
299	8.2.3 Exceptions to the IEEE 802.15.4 physical layer 9 Data-link layer 9.1 General 9.1.1 Overview
300	9.1.2 Coexistence strategies in the DL 9.1.3 Allocation of digital bandwidth
301	9.1.4 Structure of the DPDU 9.1.5 The DL and the IEEE 802.15.4 MAC Figure 53 – DL protocol suite and PhPDU/DPDU structure
302	9.1.6 Routes and graphs
304	Figure 54 – Graph routing example Table 99 – Graph table on ND20 Table 100 – Graph table on ND21
306	Figure 55 – Inbound and outbound graphs
309	9.1.7 Slotted-channel-hopping, slow-channel-hopping, and timeslots
310	Figure 56 – Slotted-channel-hopping
311	Figure 57 – Slow-channel-hopping Figure 58 – Hybrid operation
312	Figure 59 – Radio spectrum usage
314	Figure 60 – Predefined channel-hopping-pattern1
315	Figure 61 – Two groups of DLEs with different channel-hopping-pattern-offsets
316	Figure 62 – Interleaved channel-hopping-pattern1 with sixteen different channel-hopping-pattern-offsets
317	Figure 63 – Example timeslot allocation for slotted-channel-hopping
318	Figure 64 – Example timeslot allocation for slow-channel-hopping
319	Figure 65 – Hybrid mode with slotted-channel-hopping and slow-channel-hopping Figure 66 – Combining slow-channel-hopping and slotted-channel-hopping
320	9.1.8 Superframes Figure 67 – Example of a three-timeslot superframe and how it repeats Figure 68 – Superframes and links
321	Figure 69 – Multiple superframes with aligned timeslots
325	Figure 70 – Example superframe for slotted-channel-hopping
326	Figure 71 – Example superframe for slow-channel-hopping Figure 72 – Components of a slow-channel-hopping superframe
327	Figure 73 – Example configuration for avoiding collisions among routers
328	Figure 74 – Hybrid configuration
330	Figure 75 – Timeslot allocation and message queue
332	9.1.9 DL time keeping
333	Figure 76 – 250 ms alignment intervals
334	Figure 77 – Timeslot durations and timing
335	Table 101 – Approximating nominal timing with 32 KiHz clock
339	Figure 78 – Clock source acknowledges receipt of a Data DPDU
341	Figure 79 – Transaction timing attributes
342	Figure 80 – Dedicated and shared transaction timeslots
343	Figure 81 – Unicast transaction
346	Figure 82 – PDU wait time (PWT)
347	Figure 83 – Duocast support in the standard
348	Figure 84 – Duocast transaction
349	Figure 85 – Shared timeslots with active CSMA/CA
350	Figure 86 – Transaction during slow-channel-hopping periods
351	9.1.10 Dsubnet addressing
352	9.1.11 DL management service
353	Figure 87 – DL management SAP flow through standard protocol suite
354	9.1.12 Relationship between DLE and DSC
355	9.1.13 DLE neighbor discovery
358	9.1.14 Neighbor discovery and joining – DL considerations
361	Table 102 – DL_Config_Info structure
363	9.1.15 Radio link control and quality measurement
367	Table 103 – CountryCode
368	9.1.16 DLE roles and options 9.1.17 DLE energy considerations
369	9.2 DDSAP 9.2.1 General 9.2.2 DDData.request
370	Table 104 – DDData.request parameters
371	9.2.3 DDData.confirm 9.2.4 DDData.indication Table 105 – DDData.confirm parameters Table 106 – Value set for status parameter Table 107 – DDData.indication parameters
372	9.3 Data DPDUs and ACK/NAK DPDUs 9.3.1 General Figure 88 – PhPDU and DPDU structure
373	9.3.2 Octet and bit ordering
374	9.3.3 Media access control headers Table 108 – ExtDLUint, one-octet variant Table 109 – ExtDLUint, two-octet variant
375	Table 110 – Data DPDU MHR
377	Table 111 – Data DPDU DHDR Table 112 – Data DPDU DMXHR
378	Table 113 – DROUT structure, compressed variant
379	Table 114 – DROUT structure, uncompressed variant
380	Table 115 – DADDR structure
381	9.3.4 MAC acknowledgment DPDUs Figure 89 – Typical ACK/NAK DPDU layout Table 116 – ACK/NAK DPDU MHR
382	Table 117 – ACK/NAK DPDU DHR
383	Table 118 – ACK/NAK DPDU DHDR
384	9.3.5 DL auxiliary subheader Table 119 – Advertisement DAUX structure
385	Table 120 – Advertisement selections elements
386	Table 121 – Advertisement selections Table 122 – Advertisement time synchronization elements Table 123 – Advertisement time synchronization structure
388	Table 124 – Join superframe information subfields Table 125 – Join superframe information structure
389	Table 126 – Superframe derived from advertisement
390	Table 127 – Join information elements Table 128 – Join information structure
391	Table 129 – Defaults for links created from advertisements
392	Table 130 – dlmo.Neighbor entry created from advertisements Table 131 – dlmo.Graph entry created from advertisements
393	Table 132 – dlmo.Route entry created from advertisements
395	Table 133 – Solicitation header subfields
396	Table 134 – Solicitation header structure Table 135 – Solicitation DAUX fields Table 136 – Solicitation DAUX structure
398	Table 137 – Activate link DAUX fields Table 138 – Activate link DAUX structure Table 139 – Report received signal quality DAUX fields
399	9.4 DL management information base 9.4.1 General 9.4.2 DL management object attributes Table 140 – Report received signal quality DAUX structure Table 141 – DLMO attributes (1 of 7)
409	Table 142 – Dsubnet filter octets Table 143 – dlmo.TaiAdjust OctetString fields
410	Table 144 – dlmo.TaiAdjust OctetString structure Table 145 – dlmo.EnergyDesign OctetString fields Table 146 – dlmo.EnergyDesign OctetString structure
411	Table 147 – dlmo.DeviceCapability OctetString fields Table 148 – dlmo.DeviceCapability OctetString structure
413	Table 149 – dlmo.DiscoveryAlert fields Table 150 – dlmo.DiscoveryAlert structure
414	Table 151 – dlmo.Candidates OctetString fields
415	Table 152 – dlmo.Candidates structure
416	Table 153 – dlmo.SmoothFactors OctetString fields Table 154 – dlmo.SmoothFactors structure
417	Table 155 – dlmo.QueuePriority fields Table 156 – dlmo.QueuePriority structure
418	Table 157 – dlmo.ChannelDiag fields
419	9.4.3 DLMO attributes (indexed OctetStrings) Figure 90 – Relationship among DLMO indexed attributes Table 158 – dlmo.ChannelDiag structure
421	Table 159 – dlmo.Ch fields Table 160 – dlmo.Ch structure
424	Table 161 – Transaction receiver template fields Table 162 – Transaction receiver template structure
425	Table 163 – Transaction initiator template fields Table 164 – Transaction initiator template structure
426	Table 165 – Default transaction responder template, used during joining process Table 166 – Default transaction initiator template, used during joining process
427	Table 167 – Default transaction responder template, used during joining process
429	Table 168 – dlmo.Neighbor fields
430	Table 169 – dlmo.Neighbor structure
431	Table 170 – ExtendGraph fields Table 171 – ExtGraph structure
432	Table 172 – dlmo.NeighborDiagReset fields Table 173 – dlmo.NeighborDiagReset structure
433	Table 174 – dlmo.Superframe fields
434	Table 175 – dlmo.Superframe structure
438	Table 176 – dlmo.SuperframeIdle fields Table 177 – dlmo.SuperframeIdle structure
439	Table 178 – dlmo.Graph Table 179 – dlmo.Graph structure
440	Table 180 – dlmo.Link fields
441	Table 181 – dlmo.Link structure
442	Table 182 – dlmo.Link[ ].Type structure
443	Table 183 – Allowed dlmo.Link[ ].Type combinations
444	Table 184 – Values for dlmo.Link[ ].Schedule Table 185 – dlmo.Route fields
445	Table 186 – dlmo.Route structure
446	Table 187 – dlmo.NeighborDiag fields Table 188 – Diagnostic summary OctetString fields
447	Table 189 – Diagnostic summary OctetString structure Table 190 – Diagnostic ClockDetail OctetString fields
448	9.5 DLE methods 9.5.1 Method for synchronized cutover of DLE attributes 9.5.2 Methods to access indexed OctetString attributes Table 191 – Diagnostic ClockDetail OctetString structure
449	Table 192 – Read_Row method Table 193 – Write_Row method
450	9.6 DL alerts 9.6.1 DL_Connectivity alert Table 194 – Write_Row_Now method
451	Table 195 – dlmo.AlertPolicy fields Table 196 – dlmo.AlertPolicy OctetString structure
452	9.6.2 NeighborDiscovery alert Table 197 – DL_Connectivity alert Table 198 – DL_Connectivity alert OctetString
453	10 Network layer 10.1 General 10.2 NL functionality overview 10.2.1 General Table 199 – NeighborDiscovery alert
454	10.2.2 Addressing 10.2.3 Address translation Table 200 – Link-local address structure
455	Table 201 – Address translation table (ATT)
456	10.2.4 Network protocol data unit headers 10.2.5 Fragmentation and reassembly Figure 91 – Address translation process
458	Figure 92 – Fragmentation process
459	10.2.6 Routing Figure 93 – Reassembly process
460	Table 202 – Example of a routing table
461	Figure 94 – Processing of an NSDU received from a TLE
462	Figure 95 – Processing of a received NPDU
464	Figure 96 – Processing of a NPDU received by a NLE from the backbone
465	10.2.7 Routing examples Figure 97 – Delivery of a received NPDU at its final destination NLE
466	Figure 98 – Routing from a field device direct to a field-connected gatewaywithout backbone routing
467	Figure 99 – Protocol suite diagram for routing from a field device direct to a field-connected gateway without backbone routing
468	Figure 100 – Routing an NPDU from a field device to a gateway via a backbone router
469	Figure 101 – Protocol suite diagram for routing an APDU from a field device to a gateway via a backbone router
470	Figure 102 – Routing from a field device on one Dsubnet to another field device on a different Dsubnet
471	Figure 103 – Protocol suite diagram for routing from an I/O device on one Dsubnet to another I/O device on a different Dsubnet
472	Figure 104 – Example of routing over an Ethernet backbone network
473	10.3 NLE data services 10.3.1 General Figure 105 – Example of routing over a fieldbus backbone network
474	10.3.2 NData.request Table 203 – NData.request elements
475	10.3.3 NData.confirm 10.3.4 NData.indication Table 204 – NData.confirm elements
476	10.4 NL management object 10.4.1 NL management information base Table 205 – NData.indication elements
477	Table 206 – NLMO attributes (1 of 3)
480	10.4.2 Structured management information bases Table 207 – Contract table structure
481	10.4.3 NL management object methods Table 208 – Route table elements Table 209 – Address translation table structure
483	Table 210 – NLMO structured MIB manipulation methods
484	10.5 NPDU formats 10.5.1 General Table 211 – Alert to indicate dropped PDU/PDU error
485	Figure 106 – Distinguishing between NPDU header formats
486	10.5.2 Basic header format for NL Table 212 – Common header patterns Table 213 – Basic NL header format
487	10.5.3 Contract-enabled network header format
488	Table 214 – Contract-enabled NL header format Table 215 – 6LoWPAN_IPHC encoding format
489	10.5.4 Full header (IPv6) format Table 216 – IPv6 NL header format
490	Table 217 – Full NL header in the DL
491	10.5.5 Fragmentation header format Table 218 – NL header format for fragmented NPDUs Table 219 – Format of first fragment header
492	11 Transport layer 11.1 General Table 220 – Format of second and subsequent fragment headers
493	11.2 TLE reference model 11.3 Transport security entity 11.3.1 General 11.3.2 Securing the TL Figure 107 – TLE reference model
494	11.4 Transport data entity 11.4.1 General
495	11.4.2 UDP over IPv6 11.4.3 UDP header transmission and compression Figure 108 – UDP pseudo-header for IPv6
496	Table 221 – UDP header encoding
498	11.4.4 TSAPs and UDP ports
499	11.4.5 Good network citizenship 11.5 TPDU encoding 11.5.1 General 11.5.2 Header compression – User datagram protocol encoding Figure 109 – TPDU structure
500	Table 222 – UDP 6LoWPAN_NHC-for-UDP encoding octet Table 223 – Optimal UDP header encoding
501	11.5.3 TPDU security header 11.6 TL model 11.6.1 General 11.6.2 Data services Table 224 – UDP header encoding with checksum and compressed port numbers
502	Table 225 – TData.request elements
503	Table 226 – TData.confirm elements Table 227 – TData.confirm status codes
504	Table 228 – TData.indication elements
505	Table 229 – TLMO attributes (1 of 2)
507	Table 230 – TL management object methods – Reset Table 231 – TL management object methods – Halt
508	Table 232 – TL management object methods – PortRangeInfo Table 233 – TL management object methods – GetPortInfo
509	Table 234 – TL management object methods – GetNextPortInfo Table 235 – TL management object alert types – Illegal use of port
510	12 Application layer 12.1 General Table 236 – TL management object alert types – TPDU received on unregistered port Table 237 – TL management object alert types – TPDU does not match security policies
511	12.2 Energy considerations 12.3 Legacy control system considerations
512	12.4 Overview of object-oriented modeling 12.4.1 General 12.4.2 Object-to-object communication concept
513	12.4.3 AL structure 12.4.4 UAP structure Figure 110 – User application objects in a UAP
514	12.5 Object model
515	12.6 Object attribute model 12.6.1 General
516	12.6.2 Attributes of standard objects 12.6.3 Attribute classification
517	12.6.4 Attribute accessibility 12.7 Method model
518	12.8 Alert model 12.9 Alarm state model Table 238 – State table for alarm transitions
519	12.10 Event state model 12.10.1 General 12.10.2 State table and transitions Figure 111 – Alarm state model Table 239 – State table for event transitions
520	12.11 Alert reporting 12.11.1 General 12.11.2 Alert types Figure 112 – Event model
521	12.11.3 Alert report information
522	12.11.4 Alarm state recovery 12.12 Communication interaction model 12.12.1 General 12.12.2 Buffered unidirectional publication communication
523	12.12.3 Queued unidirectional communication 12.12.4 Queued bidirectional communication
524	Figure 113 – A successful example of multiple outstanding requests, with response concatenation
526	Figure 114 – An example of multiple outstanding unordered requests, with second write request initially unsuccessful
527	Figure 115 – An example of multiple outstanding ordered requests, with second write request initially unsuccessful
529	Figure 116 – Send window example 1, with current send window smaller than maximum send window Figure 117 – Send window example 2, with current send window the same size as maximum send window, and non-zero usable send window width
530	Figure 118 – Send window example 3, with current send window the same size as maximum send window, and usable send window width of zero
531	12.12.5 Communication service contract
532	12.13 AL addressing 12.13.1 General 12.13.2 Object addressing Figure 119 – General addressing model
533	12.13.3 Object attribute addressing 12.13.4 Object attribute addressing
535	12.13.5 Object method addressing 12.14 Management objects
536	12.15 User objects 12.15.1 General 12.15.2 Industry-independent objects
537	Table 240 – UAP management object attributes (1 of 2)
539	Figure 120 – UAP management object state diagram Table 241 – State table for UAP management object Table 242 – UAP management object methods
540	Table 243 – Alert-receiving object attributes
541	Figure 121 – Alert report reception state diagram Figure 122 – Alert-reporting example Table 244 – State table for handling an AlertReport reception
542	Table 245 – AlertReceiving object methods
543	Table 246 – UploadDownload object attributes (1 of 4)
548	Table 247 – UploadDownload object methods
549	Table 248 – UploadDownload object StartDownload method
550	Table 249 – UploadDownload object DownloadData method
552	Table 250 – UploadDownload object EndDownload method
553	Table 251 – UploadDownload object StartUpload method
554	Table 252 – UploadDownload object UploadData method
555	Table 253 – UploadDownload object EndUpload method
556	Table 254 – Download state table for unicast operation mode (1 of 2)
558	Figure 123 – UploadDownload object download state diagram Figure 124 – UploadDownload object upload state diagram
559	Table 255 – Upload state table for unicast operation mode (1 of 2)
561	Table 256 – Concentrator object attributes (1 of 2)
562	Table 257 – Concentrator object methods
563	Table 258 – Dispersion object attributes (1 of 2)
564	Table 259 – Dispersion object methods
565	Table 260 – Tunnel object attributes (1 of 3)
567	Table 261 – Tunnel object methods
568	Table 262 – Interface object attributes Table 263 – Interface object methods
569	12.16 Data types 12.16.1 Basic data types 12.16.2 Derived atomic data types 12.16.3 Industry-independent standard data structures
570	Table 264 – Data type: ObjectAttributeIndexAndSize
571	Table 265 – Data type: Communication association endpoint (1 of 2)
573	Table 266 – Data type: Communication contract data
574	Table 267 – Data type: Alert communication endpoint Table 268 – Data type: Tunnel endpoint
575	Table 269 – Data type: Alert report descriptor Table 270 – Data type: Process control alarm report descriptorfor analog with single reference condition
576	12.17 Application services provided by application sublayer 12.17.1 General Table 271 – Data type: ObjectIDandType Table 272 – Data type: UnscheduledCorrespondent
577	12.17.2 Publish/subscribe application communication model Table 273 – AL services
578	12.17.3 Scheduled periodic buffered communication
579	Figure 125 – Publish sequence of service primitives
581	Table 274 – Publish service
583	12.17.4 Client/server interactions
584	Figure 126 – Client/server model two-part interactions Figure 127 – Client/server model four-part interactions: Successful delivery
585	Figure 128 – Client/server model four-part interactions: Request delivery failure Figure 129 – Client/server model four-part interactions: Response delivery failure
587	Table 275 – Read service
592	Table 276 – Write service
596	Table 277 – Execute service
599	12.17.5 Unscheduled acyclic queued unidirectional messages (source/sink)
600	Figure 130 – AlertReport and AlertAcknowledge, delivery success Figure 131 – AlertReport, delivery failure
601	Figure 132 – AlertReport, acknowledgment failure
602	Table 278 – AlertReport service
605	Table 279 – AlertAcknowledge service
606	12.17.6 Client/server and source/sink commonalities
608	Figure 133 – Concatenated response for multiple outstanding write requests(no message loss)
609	Table 280 – Tunnel service
612	12.18 AL flow use of lower layer services 12.18.1 General 12.18.2 AL use of TDSAPs 12.18.3 Mapping AL service primitives to TL service primitives Table 281 – Application flow characteristics
613	12.19 AL management 12.19.1 General 12.19.2 Application sublayer handling of malformed application protocol data units Table 282 – AL service primitive to TL service primitive mapping
614	12.19.3 Application sublayer management object attributes Figure 134 – Management and handling of malformed APDUs received from device X
615	Table 283 – ASLMO attributes (1 of 2)
616	12.19.4 Application sublayer management object methods Table 284 – Application sublayer management object methods
617	12.19.5 Application sublayer management object alerts Table 285 – Reset method
618	12.19.6 DMAP services invoked by application sublayer Table 286 – ASLMO alerts
619	12.19.7 Process industries standard objects
621	Table 287 – Analog input object attributes
622	Table 288 – Analog input object methods
623	Table 289 – Analog input alerts
624	Table 290 – Analog output attributes (1 of 2)
625	Table 291 – Analog output object methods
626	Table 292 – Analog output alerts
627	Table 293 – Binary input object attributes
628	Table 294 – Binary input object methods Table 295 – Binary input alerts
629	Table 296 – Binary output attributes
630	12.19.8 Factory automation industries profile Table 297 – Binary output object methods Table 298 – Binary output alerts
631	12.20 Process control industry standard data structures 12.20.1 General 12.20.2 Status for analog information
632	12.20.3 Value and status for analog information 12.20.4 Value and status for binary information Table 299 – Status octet Table 300 – Data type: Process control value and status for analog value
633	12.20.5 Process control mode Table 301 – Data type: Process control value and status for binary value Table 302 – Data type: Process control mode Table 303 – Data type: Process control mode bitstring
634	12.20.6 Scaling 12.21 Additional tables 12.21.1 Process control profile standard objects Table 304 – Data type: Process control scaling Table 305 – Process control standard objects
635	12.21.2 Services 12.22 Coding 12.22.1 General 12.22.2 Coding rules for application protocol data units Table 306 – Services Table 307 – Application messaging format
636	Table 308 – Concatenated APDUs in a single TSDU Table 309 – Object addressing
637	Table 310 – Four-bit addressing mode APDU header construction Table 311 – Eight-bit addressing mode APDU header construction Table 312 – Sixteen-bit addressing mode APDU header construction
638	Table 313 – Inferred addressing use case example Table 314 – Inferred addressing mode APDU header construction
639	Table 315 – Six-bit attribute identifier, not indexed Table 316 – Six-bit attribute identifier, singly indexed, with 7bit index Table 317 – Six-bit attribute identifier, singly indexed, with 15bit index
640	Table 318 – Six-bit attribute identifier, doubly indexed, with two 7bit indices Table 319 – Six-bit attribute identifier, doubly indexed, with two 15bit indices Table 320 – Six-bit attribute identifier, doubly indexed, withfirst index seven bits long and second index fifteen bits long Table 321 – Six-bit attribute bit attribute identifier, doubly indexed, with first index fifteen bits long and second index seven bits long
641	Table 322 – Twelve-bit attribute identifier, not indexed Table 323 – Twelve-bit attribute identifier, singly indexed with 7bit index Table 324 – Twelve-bit attribute identifier, singly indexed with 15bit index Table 325 – Twelve-bit attribute identifier, doubly indexed with two 7bit indices
642	Table 326 – Twelve-bit attribute identifier, doubly indexed with two 15bit indices Table 327 – Twelve-bit attribute identifier, doubly indexedwith first index 7 bits long and second index 15 bits long Table 328 – Twelve-bit attribute identifier, doubly indexedwith the first index 15 bits long and the second index 7 bits long Table 329 – Twelve-bit attribute identifier, reserved form
643	Table 330 – Coding rules for read service request Table 331 – Coding rules for read service response with 7-bit size field Table 332 – Coding rules for read service response with 15-bit size field
644	Table 333 – Coding rules for write service request with 7bit size field Table 334 – Coding rules for write service request with 15bit size field Table 335 – Coding rules for write service response
645	Table 336 – Coding rules for execute service request with 7bit size field Table 337 – Coding rules for execute service request with 15bit size field Table 338 – Coding rules for execute service response with 7-bit size field
646	Table 339 – Coding rules for execute service response with 15-bit size field Table 340 – Coding rules for tunnel service request with 7-bit size field Table 341 – Coding rules for tunnel service request with 15-bit size field Table 342 – Coding rules for tunnel service response with 7-bit size field
647	Table 343 – Coding rules for tunnel service response with 15-bit size field Table 344 – Coding rules for AlertReport service with 7-bit associated-data size field Table 345 – Coding rules for AlertReport service with 15-bit associated-data size field
648	Table 346 – Coding rules for AlertAcknowledge service Table 347 – Coding rules for publish service for a native sequence of values Table 348 – Coding rules for publish service – non-native (for tunnel support) Table 349 – Coding rules for concatenate service
649	12.22.3 Coding of application data Table 350 – General coding rule for size-invariant application data Table 351 – General coding rule for size-varying application data of 0..255 octets
651	Table 352 – Coding rules for Unsigned8 Table 353 – Coding rules for Unsigned16
652	Table 354 – Coding rules for Unsigned32 Table 355 – Coding rules for Unsigned64
653	Table 356 – Coding rules for Unsigned128
654	Table 357 – Coding rules for single-precision float Table 358 – Coding rules for double-precision float
655	Table 359 – Coding rules for VisibleString Table 360 – Coding rules for OctetString
656	12.22.4 Time-related data types Table 361 – Coding rules for BitString
657	Table 362 – Coding rules for TAINetworkTime,and for TAITimeDifference when interpreted as a modulo difference Table 363 – Coding rules for TAITimeRounded
659	12.23 Syntax 12.23.1 Application protocol data unit
666	12.23.2 Alert reports and acknowledgments
668	12.23.3 Service feedback code
670	12.23.4 Read, write, and execute 12.23.5 Tunnel
671	12.23.6 End of contained module 12.24 Detailed coding examples (informative) 12.24.1 Read 12.24.2 Tunnel Table 364 – Coding example: Read request for a non-indexed attribute Table 365 – Coding example: Read response for a non-indexed attribute Table 366 – Coding example: Tunnel service request
672	13 Provisioning 13.1 General 13.2 Terms and definitions for devices with various roles or states
674	13.3 Provisioning procedures 13.4 Pre-installed symmetric keys
675	13.5 Provisioning using out-of-band mechanisms 13.6 Provisioning networks 13.6.1 General
676	13.6.2 Provisioning over-the-air using asymmetric cryptography Figure 135 – The provisioning network
677	13.6.3 Provisioning over-the-air using an open symmetric join key
678	13.7 State transition diagrams Figure 136 – State transition diagrams outlining provisioning steps during a device lifecycle
679	Table 367 – Factory default settings
681	Figure 137 – State transition diagram showing various paths to joining a secured network
682	13.8 Device management application protocol objects used during provisioning
683	Figure 138 – Provisioning objects and interactions
685	13.9 Management objects 13.9.1 Device provisioning object Table 368 – Device provisioning object (1 of 6)
690	13.9.2 Device provisioning object methods and alerts Table 369 – Reset_To_Default method
691	13.10 Device provisioning service object 13.10.1 Device provisioning service object attributes Table 370 – Write symmetric join key method
692	Table 371 – Device provisioning service object (1 of 4)
695	13.10.2 Device provisioning service object structured attributes
696	Table 372 – DPSOWhiteListTbl data structure (1 of 2)
697	13.10.3 Device provisioning service object methods
698	13.10.4 Device provisioning service object alerts Table 373 – Array manipulation table Table 374 – DPSO alert to indicate join by a device not on the WhiteList
699	13.10.5 Summary of attributes that can be provisioned 13.11 Provisioning functions (informative) 13.11.1 General Table 375 – DPSO alert to indicate inadequate device join capability
700	13.11.2 Examples of provisioning methods
703	Annexes Annex A (informative) User layer/application profiles A.1 Overview A.2 User layer A.3 Application profile
705	Annex B (normative) Communication role profiles B.1 Overview B.1.1 General B.1.2 Purpose B.1.3 System size B.1.4 Abbreviations and special symbols B.1.5 Role profiles
706	B.2 System B.3 System manager Table B.1 – Protocol layer device roles Table B.2 – Over-the-air upgrades
707	B.4 Security manager Table B.3 – Session support profiles
708	B.5 Physical layer B.6 Data-link layer B.6.1 General Table B.4 – Baseline profiles Table B.5 – PhL roles
709	B.6.2 Role profiles Table B.6 – DL required for listed roles
710	Table B.7 – Role profiles: General DLMO attributes Table B.8 – Role profiles: dlmo.Device_Capability
711	Table B.9 – Role profiles: dlmo.Ch (channel-hopping) Table B.10 – Role profiles: dlmo.TsTemplate Table B.11 – Role profiles: dlmo.Neighbor
712	Table B.12 – Role profiles: dlmo.NeighborDiag Table B.13 – Role profiles: dlmo.Superframe Table B.14 – Role profiles: dlmo.Graph
713	B.7 Network layer Table B.15 – Role profiles: dlmo.Link Table B.16 – Role profiles: dlmo.Route Table B.17 – Role profiles: dlmo.Queue_Priority
714	B.8 Transport layer B.9 Application layer Table B.18 – Routing table size Table B.19 – Address table size Table B.20 – Port support size Table B.21 – APs
715	B.10 Provisioning B.11 Gateway (informative) Table B.22 – Role profiles: I/O, routers, gateways, and backbone routers Table B.23 – Role profile: Gateway Table B.24 – Role profile: Gateway native access
716	Table B.25 – Role profile: Gateway interworkable tunnel mechanism
717	Annex C (informative) Background information C.1 Industrial needs C.2 Usage classes C.2.1 General
718	C.2.2 Class examples Table C.1 – Usage classes
719	C.2.3 Other uploading and downloading alarms (human or automated action) C.3 The Open Systems Interconnection Basic Reference Model C.3.1 Overview Figure C.1 – OSI Basic Reference Model
720	C.3.2 Application layer
721	C.3.3 Transport layer C.3.4 Network layer C.3.5 Data-link layer C.3.6 Physical layer
723	Annex D (normative) Configuration defaults D.1 General D.2 System management Table D.1 – System management configuration defaults
724	D.3 Security D.4 Data-link layer Table D.2 – Security configuration defaults
725	Table D.3 – DLE configuration defaults
726	D.5 Network layer D.6 Transport layer D.7 Application layer Table D.4 – NLE configuration defaults Table D.5 – TLE configuration defaults
727	Table D.6 – ALE configuration defaults
728	D.8 Provisioning
729	D.9 Gateway (informative) Table D.7 – Provisioning configuration defaults Table D.8 – Gateway configuration defaults
730	Annex E (informative) Use of backbone networks E.1 General E.2 Recommended characteristics E.3 Internet protocol backbones E.3.1 Methods of IPv6 protocol data unit transmission
731	E.3.2 Backbone router peer device discovery E.3.3 Security
733	Annex F (normative) Basic security concepts – Notation and representation F.1 Strings and string operations F.2 Integers, octets, and their representation F.3 Entities
734	Annex G (informative) Using certificate chains for over-the-air provisioning
735	Annex H (normative) Security building blocks H.1 Symmetric key cryptographic building blocks H.1.1 Overview H.1.2 Symmetric key domain parameters H.1.3 Block cipher H.1.4 Mode of operation H.1.5 Cryptographic hash function H.1.6 Keyed hash function for message authentication
736	H.1.7 Specialized keyed hash function for message authentication H.1.8 Challenge domain parameters H.2 Asymmetric-key cryptographic building blocks H.2.1 General H.2.2 Elliptic curve domain parameters H.2.3 Elliptic curve point representation H.2.4 Elliptic curve public-key pair H.3 Keying information H.3.1 General
737	H.3.2 Elliptic curve cryptography implicit certificates H.3.3 Elliptic curve cryptography manual certificates
738	H.3.4 Additional information H.4 Key agreement schemes H.4.1 Symmetric-key key agreement scheme H.4.2 Asymmetric-key key agreement scheme H.5 Keying information schemes H.5.1 Implicit certificate scheme
739	H.5.2 Manual certificate scheme H.6 Challenge domain parameter generation and validation H.6.1 Overview H.6.2 Challenge domain parameter generation H.6.3 Challenge domain parameter verification
740	H.7 Challenge validation primitive H.8 Secret key generation (SKG) primitive
741	H.9 Block-cipher-based cryptographic hash function
742	H.10 Elliptic curve cryptography manual certificate scheme H.10.1 Overview
743	H.10.2 Elliptic curve cryptography manual certificate generation transformation H.10.3 Elliptic curve cryptography manual certificate processing transformation
745	Annex I (informative) Definition templates I.1 Object type template I.2 Standard object attributes template Table I.1 – Table of standard object types
746	I.3 Standard object methods Table I.2 – Template for standard object attributes
747	I.4 Standard object alert reporting template Table I.3 – Template for standard object methods
748	I.5 Data structure definition Table I.4 – Template for standard object alert reporting
749	Table I.5 – Template for data structures
750	Annex J (informative) Operations on attributes J.1 Operations on attributes J.1.1 General J.1.2 Attribute classification J.1.3 Retrieving, setting, and resetting attributes
751	J.1.4 Retrieving and setting structured attributes Table J.1 – Scheduled_Write method template
752	Table J.2 – Read_Row method template Table J.3 – Write_Row method template
753	J.1.5 Resetting structured attribute values J.1.6 Deleting structured attribute values Table J.4 – Reset_Row method template
754	J.2 Synchronized cutover Table J.5 – Delete_Row method template
755	Annex K (normative) Standard object types
756	Table K.1 – Standard object types
758	Table K.2 – Standard object instances
760	Annex L (informative) Standard data types Table L.1 – Standard data types
762	Annex M (normative) Identification of tunneled legacy fieldbus protocols Table M.1 – Identification of tunneled legacy fieldbus protocols
763	Annex N (informative) Tunneling and native object mapping N.1 Overview N.2 Tunneling N.3 Foreign protocol application communication
764	N.4 Native object mapping N.5 Tunneling and native object mapping tradeoffs
765	Annex O (informative) Generic protocol translation O.1 Overview O.2 Publish Figure O.1 – Generic protocol translation publish diagram
766	O.3 Subscribe Figure O.2 – Generic protocol translation subscribe diagram
767	O.4 Client Figure O.3 – Generic protocol translation client/server transmission diagram
768	O.5 Server Figure O.4 – Generic protocol translation client/server reception diagram
769	Annex P (informative) Exemplary GIAP adaptations for this standard P.1 General P.2 Parameters P.3 Session P.4 Lease
770	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 P.12.1 General P.12.2 Native access
771	P.12.3 Foreign access P.13 Publish/subscribe P.13.1 General P.13.2 Native access
772	P.13.3 Foreign access P.14 Bulk transfer P.15 Alert
773	P.16 Gateway configuration P.17 Device configuration
774	Annex Q (informative) Exemplary GIAP adaptations for IEC 62591 Q.1 General Q.1.1 Overview Q.1.2 Reference Q.1.3 Addressing Q.1.4 Stack interface
775	Q.1.5 Tunneling Q.1.6 Entities Q.1.7 Delayed response Q.2 Parameters Q.3 Session
776	Q.4 Lease Q.5 Device list report Q.6 Topology report
777	Q.7 Schedule report Q.8 Device health report
778	Q.9 Neighbor health report Q.10 Network health report
779	Q.11 Time Q.12 Client/server
780	Q.13 Publish/subscribe Q.13.1 General Q.13.2 Lease establishment
781	Q.13.3 Buffering Q.14 Bulk transfer Q.15 Alert
782	Q.16 Gateway configuration Q.17 Device configuration
783	Annex R (informative) Host system interface to standard-compliant devices via a gateway R.1 Background R.1.1 Host system integration reference model R.1.2 Asset management tools R.1.3 Configuration tools Figure R.1 – Host integration reference model
784	R.1.4 Distributed control system R.1.5 Gateway R.2 Device application data integration with host systems R.2.1 General R.2.2 Native protocol integration via mapping R.2.3 Legacy device protocol integration via tunneling R.3 Host system configuration tool R.3.1 General R.3.2 Host configuration using electronic device description language
785	R.3.3 Host configuration using field device tool/device type manager Figure R.2 – Configuration using an electronic device definition
786	R.4 Field device/distributed control systems integration R.4.1 General R.4.2 Foundation Fieldbus High Speed Ethernet R.4.3 Modbus R.4.4 Open connectivity for industrial automation Figure R.3 – Configuration using FDT/DTM approach
787	R.5 Gateway R.5.1 General R.5.2 Devices supported R.5.3 Data subscription R.5.4 Data publication R.5.5 Client/server access R.5.6 Alerts reception R.6 Asset management application support R.6.1 General
788	R.6.2 Field device tool / device type manager R.6.3 HART R.6.4 OPC
789	Annex S (informative) Symmetric-key operation test vectors S.1 DPDU samples S.1.1 General S.1.2 DPDU with expected DMIC32 S.1.3 DPDU with expected ENC-DMIC32
790	S.2 TPDU samples S.2.1 General S.2.2 TPDU with expected ENC-TMIC-32: S.2.3 TPDU with expected TMIC-32:
792	Annex T (informative) Data-link and network headers for join requests T.1 Overview T.2 MAC header (MHR) T.3 DL header (DHR) Table T.1 – Sample MHR for join request
793	T.4 NL header Table T.2 – Sample DHR for join request Table T.3 – Network header for join messages
794	Annex U (informative) Gateway role U.1 General U.1.1 Overview
795	U.1.2 Notional gateway protocol suite diagrams for native devices and adapters U.1.3 Gateway scenarios
796	Figure U.1 – Gateway scenarios
797	U.1.4 Basic gateway model Figure U.2 – Basic gateway model
798	U.2 Notional GIAP U.2.1 Summary of interfaces and primitives
799	Table U.1 – Summary of notional gateway high-side interface examples
801	U.2.2 Sequence of primitives Figure U.3 – Internal sequence of primitives for session interface Figure U.4 – Internal sequence of primitives for lease management interface
802	Figure U.5 – Internal sequence of primitives for system report interfaces Figure U.6 – Internal sequence of primitives for time interface
803	Figure U.7 – Internal sequence of primitives forclient/server interface initiated from gateway to an adapter device Figure U.8 – Internal sequence of primitives forpublish interface initiated from gateway to an adapter device
804	Figure U.9 – Internal sequence of primitives for subscribe interface initiated from an adapter device Figure U.10 – Internal sequence of primitives forpublisher timer initiated from gateway to an adapter device Figure U.11 – Internal sequence of primitives forsubscriber timers initiated from an adapter device
805	Figure U.12 – Internal sequence of primitives for the bulk transfer interface Figure U.13 – Internal sequence of primitives for the alert subscription interface
806	U.2.3 Detailed description of parameters Figure U.14 – Internal sequence of primitives for the alert notification interface Figure U.15 – Internal sequence of primitives for gateway management interfaces
808	U.2.4 Detailed description of interfaces Table U.2 – Primitive G_Session parameter usage
810	Table U.3 – GS_Status for G_Session confirm
811	Table U.4 – Primitive G_Lease parameter usage
812	Table U.5 – GS_Lease_Type for G_Lease request
813	Table U.6 – GS_Status for G_Lease confirm
814	Table U.7 – Primitive G_Device_List_Report parameter usage
815	Table U.8 – GS_Status for G_Device_List_Report confirm Table U.9 – Primitive G_Topology_Report parameter usage
817	Table U.10 – Primitive G_Schedule_Report parameter usage
819	Table U.11 – Primitive G_Device_Health_Report parameter usage
820	Table U.12 – Primitive G_Neighbor_Health_Report parameter usage
822	Table U.13 – Primitive G_Network_Health_Report parameter usage
824	Table U.14 – Primitive G_Time parameter usage Table U.15 – GS_Status for G_Time confirm
825	Table U.16 – Primitive G_Client_Server parameter usage
826	Table U.17 – GS_Status for G_Client_Server confirm
828	Table U.18 – Primitive G_Publish parameter usage
829	Table U.19 – GS_Status for G_Publish confirm Table U.20 – Primitive G_Subscribe parameter usage
830	Table U.21 – GS_Status for G_Subscribe confirm Table U.22 – Primitive G_Publish_Timer parameter usage Table U.23 – Primitive G_Subscribe_Timer parameter usage
831	Table U.24 – Primitive G_Publish_Watchdog parameter usage
832	Table U.25 – Primitive G_Bulk_Open parameter usage
833	Table U.26 – GS_Status for G_Bulk_Open confirm Table U.27 – Primitive G_Bulk_Transfer parameter usage Table U.28 – GS_Status for G_Bulk_Transfer confirm
834	Table U.29 – Primitive G_Bulk_Close parameter usage
835	Table U.30 – Primitive G_Alert_Subscription parameter usage
836	Table U.31 – GS_Status for G_Alert_Subscription confirm Table U.32 – Primitive G_Alert_Notification parameter usage
837	Table U.33 – Primitive G_Read_Gateway_Configuration parameter usage
838	Table U.34 – GS_Attribute_Identifier values for G_Read_Gateway_Configuration request Table U.35 – Primitive G_Write_Gateway_Configuration parameter usage
839	Table U.36 – GS_Attribute_Identifier values for G_Write_Gateway_Configuration request Table U.37 – GS_Status for G_Write_Gateway_Configuration confirm
840	Table U.38 – Primitive G_Write_Device_Configuration parameter usage
841	Table U.39 – GS_Status for G_Write_Device_Configuration confirm Table U.40 – Primitive G_Read_Device_Configuration parameter usage
842	U.3 Example uses of WISN standard services and objects U.3.1 Tunneling Figure U.16 – Tunnel object model
843	Figure U.17 – Distributed tunnel endpoints
844	Figure U.18 – Multicast, broadcast, and one-to-many messaging
845	Figure U.19 – Tunnel object buffering
848	Figure U.20 – Publish/subscribe publisher CoSt flowchart Figure U.21 – Publish/subscribe publisher periodic flowchart
849	Figure U.22 – Publish/subscribe subscriber common periodic and CoSt flowchart
850	Figure U.23 – Network address mappings
851	Figure U.24 – Connection_Info usage in protocol translation
852	Figure U.25 – Transaction_Info usage in protocol translation
853	Figure U.26 – Interworkable tunneling mechanism overview diagram
855	U.3.2 Bulk transfer
856	U.3.3 Alerts Figure U.27 – Bulk transfer model
857	Figure U.28 – Alert model
858	U.3.4 Native publish/subscribe and client/server access Figure U.29 – Alert cascading
859	U.3.5 Time management Figure U.30 – Native publish/subscribe and client/server access
860	U.3.6 Security U.3.7 Configuration
861	U.3.8 Provisioning and joining Table U.41 – Example of gateway configuration management attributes
862	Annex V (informative) Compliance with ETSI EN 300 328 v1.8.1
866	Bibliography

Published By	Publication Date	Number of Pages
BSI	2015	872


PDF Format	Searchable	Printable	Preview Now

Status	Withdrawn
Title	Industrial networks. Wireless communication network and communication profiles. ISA 100.11a
Replaces	PD IEC/PAS 62734:2012
Publisher	BSI
Committee	GEL/65/3
Pages	872
Publication Date	2015-01-31
Withdrawn Date	2022-09-15
Replaced By	BS EN 62734:2015+A1:2019
ISBN	978 0 580 78132 2
Standard Number	BS EN 62734:2015
Identical National Standard Of	EN 62734:2015, IEC 62734:2014
Descriptors	Process control, Industrial, Communication networks, Interfaces (data processing), Fieldbus, Open systems interconnection, Computer networks, Radiocommunication, Data transmission, Bus networks, Communication procedures, Network layer (OSI), Data processing, Automatic control systems
ICS Codes	33.170 - Television and radio broadcasting

BS EN 62734:2015

PDF Catalog

Related products

BS EN 62734:2015+A1:2019