BS EN 62601:2016:2021 Edition
$256.21
Industrial networks. Wireless communication network and communication profiles. WIA-PA
Published By | Publication Date | Number of Pages |
BSI | 2021 | 230 |
This International Standard specifies the system architecture and the communication protocol of Wireless networks for Industrial Automation – Process Automation (WIA-PA) that is built on IEEE STD 802.15.4-2011.
PDF Catalog
PDF Pages | PDF Title |
---|---|
2 | undefined |
7 | English CONTENTS |
18 | FOREWORD |
20 | 1 Scope 2 Normative references 3 Terms, definitions and abbreviations 3.1 Terms and definitions |
24 | 3.2 Abbreviations |
26 | 4 Definition of data types |
27 | 5 WIA-PA overview 5.1 Device types 5.2 Network topology Tables Table 1 – Definition of data types |
28 | Figures Figure 1 – Example of WIA-PA physical topology (combination of star and mesh) Figure 2 – Example of WIA-PA physical topology (star-only) |
29 | 5.3 Protocol architecture Figure 3 – OSI basic reference model mapped to WIA-PA |
30 | 5.4 Interconnection Figure 4 – The architecture of WIA-PA gateway |
31 | 6 System management 6.1 General Figure 5 – DMAP in system management |
32 | 6.2 Framework of system management |
33 | 6.3 Joining process 6.3.1 Provisioning process Figure 6 – Hybrid centralized and distributed system management scheme |
34 | 6.3.2 Joining process of routing device Figure 7 – Joining process of routing device through the gateway device |
35 | 6.3.3 Joining process of field device Figure 8 – Joining process of routing device through an online routing device |
36 | 6.3.4 Addressing and address assignment Figure 9 – Joining process of field device through a gateway device Figure 10 – Joining process of field device through a routing device Figure 11 – Long address structure of device |
37 | 6.4 Virtual Communication Relationship (VCR) 6.4.1 Definition Figure 12 – Short address structure of routing device Figure 13 – Short address structure of field device |
38 | 6.4.2 Protocol support for VCR 6.4.3 VCR establishment Table 2 – Protocol support for VCR |
39 | 6.4.4 VCR release 6.5 Routing configuration and communication resource allocation 6.5.1 Routing configuration 6.5.2 Framework of communication resource allocation |
40 | 6.5.3 DLPDU priority and scheduling rules 6.5.4 Communication resource allocation to routing device Figure 14 – An example of resource allocation |
41 | Figure 15 – Allocation process of routing device’s communication resources |
42 | 6.5.5 Communication resource allocation to field device |
43 | Figure 16 – Allocation process of field device’s communication resources |
44 | 6.6 Aggregation and disaggregation 6.6.1 Aggregation Table 3 – Relations between VCR and aggregation function |
46 | 6.6.2 Disaggregation 6.6.3 An example of the two level aggregation process Table 4 – Format of aggregated data followed by field device’s DAGO Table 5 – Format of aggregated packet followed by routing device’s PAGO |
47 | Figure 17 – Example of aggregation and disaggregation |
48 | 6.6.4 Management of aggregation and disaggregation objects Table 6 – DAGO class attributes Table 7 – DAGO instance attributes |
49 | Table 8 – MEM_STRUCT structure Table 9 – PAGO class attributes Table 10 – PAGO instance attributes Table 11 – DGO class attributes |
50 | 6.7 Performance monitoring 6.7.1 Path failure report 6.7.2 Device status report Figure 18 – Process of path failure report Figure 19 – Device status report process of field device Table 12 – DGO instance attributes |
51 | 6.7.3 Channel condition report 6.8 Leaving process 6.8.1 General 6.8.2 Leaving process of routing device Figure 20 – Device status report process of routing device Figure 21 – Process of channel condition report |
52 | Figure 22 – Active leaving process of routing device Figure 23 – Passive leaving process of routing device |
53 | 6.8.3 Leaving process of field device Figure 24 – Active leaving process of field device (leaving from gateway device) Figure 25 – Active leaving process of field device (leaving from routing device) |
54 | 6.9 Management information base and services 6.9.1 Management information base Figure 26 – Passive leaving process of field device (leaving from gateway device) Figure 27 – Passive leaving process of field device (leaving from routing device) |
55 | Table 13 – Unstructured attributes (1 of 5) |
60 | Table 14 – Structured attributes |
61 | Table 15 – NLRoute_Struct structure Table 16 – Superframe_Struct structure |
62 | Table 17 – Link_Struct structure |
63 | Table 18 – Neighbour_Struct structure Table 19 – ChanCon_Struct structure |
64 | Table 20 – Device_struct structure (1 of 3) |
66 | Table 21 – VCR_Struct structure |
67 | Table 22 – DevConRep_Struct structure Table 23 – Key_Struct structure Table 24 – ObjList_Struct structure |
68 | 6.9.2 MIB services Table 25 – DMAP-MIB-GET.request parameters |
69 | Table 26 – DMAP-MIB-GET.confirm parameters Table 27 – DMAP-MIB-SET.request parameters |
70 | 7 Physical layer 7.1 General Table 28 – DMAP-MIB-SET.confirm parameters |
71 | 7.2 General requirements based on IEEE STD 802.15.4-2011 Table 29 – PHY protocol selection |
72 | 7.3 Additional requirements 7.3.1 General 7.3.2 Frequency allocations 7.3.3 Channel numbers and frequency assignments 7.3.4 Radio transceivers 7.3.5 Unspecified or improved required radio performance Table 30 – Frequency band and data rate Table 31 – Frequency assignments |
73 | 7.3.6 Transmit power 7.3.7 Output power control 7.3.8 Receiver sensitivity 7.3.9 PHY PIB attributes Table 32 – PHY PIB attributes (1 of 2) |
74 | 8 Data link layer 8.1 General 8.2 Protocol stack Figure 28 – WIA-PA DLL protocol stack |
75 | 8.3 MAC overview and function extension 8.3.1 MAC overview 8.3.2 General requirements based on IEEE STD 802.15.4-2011 |
76 | Table 33 – MAC protocol selection (1 of 2) |
78 | 8.3.3 MAC function extension Table 34 – MAC PIB attributes Table 35 – MAC extended PIB attributes |
79 | 8.4 DLSL function description 8.4.1 General Table 36 – Beacon payload Table 37 – Format of Capability Information field |
80 | 8.4.2 Coexistence 8.4.3 Timeslot communication Figure 29 – WIA-PA DLSL reference model |
81 | 8.4.4 WIA-PA superframe 8.4.5 Frequency hopping Figure 30 – WIA-PA superframe |
82 | Table 38 – Hopping mechanisms |
83 | 8.4.6 Transmission of long cycle data Figure 31 – R1, R2 and R3 superframe structures |
84 | 8.4.7 Retry strategy 8.4.8 Management service 8.4.9 Radio link quality and channel condition measurement Figure 32 – An example of long cycle data transmission |
85 | 8.4.10 Security 8.4.11 Country code 8.4.12 DLSL state machine |
86 | Figure 33 – DLSL state machine for device joining |
87 | Table 39 – DLSL state transitions for device joining |
88 | Figure 34 – DLSL state machine for in-network running Table 40 – DLSL state transitions for in-network running (1 of 3) |
91 | 8.5 Data link sub-layer data services 8.5.1 General 8.5.2 DLDE-DATA.request |
92 | 8.5.3 DLDE-DATA.confirm Table 41 – DLDE-DATA.request parameters |
93 | 8.5.4 DLDE-DATA.indication Table 42 – DLDE-DATA.confirm parameters Table 43 – Status table |
94 | 8.5.5 Time sequence of DLSL data service Figure 35 – Time sequence of data service Table 44 – DLDE-DATA.indication parameters |
95 | 8.6 Data link sub-layer management services 8.6.1 General 8.6.2 Network discovery services Table 45 – DLME-DISCOVERY.request parameters |
96 | Table 46 – DLME- DISCOVERY.confirm parameters Table 47 – Network descriptor list |
97 | 8.6.3 Device joining services Figure 36 – Time sequence of network discovery |
98 | Table 48 – DLME-JOIN.request parameters Table 49 – DLME-JOIN.indication parameters |
99 | 8.6.4 Device leaving services Table 50 – DLME-JOIN.response parameters Table 51 – DLME-JOIN.confirm parameters |
100 | Table 52 – DLME-LEAVE.request parameters Table 53 – DLME-LEAVE.indication parameters Table 54 – DLME-LEAVE.confirm parameters |
101 | 8.6.5 DLME-CHANNEL-CONDITION.indication 8.6.6 DLME-NEIGHBOUR-INFO.indication Table 55 – DLME-CHANNEL-CONDITION.indication parameters Table 56 – DLME-NEIGHBOUR-INFO.indication parameters |
102 | 8.6.7 DLME-COMM-STATUS.indication 8.6.8 Keep-alive services Table 57 – DLME-COMM-STATUS.indication parameters |
103 | 8.6.9 Time synchronization services Table 58 – DLME -KEEP-LIVE.confirm parameters Table 59 – DLME -KEEP-LIVE.indication parameters Table 60 – DLME-TIME-SYN.request parameters |
104 | 8.7 DLSL frame formats 8.7.1 General frame format Figure 37 – General frame format Table 61 – DLME -TIME-SYN.confirm parameters Table 62 – DLME-TIME-SYN.indication parameters |
105 | 8.7.2 Date frame format 8.7.3 Command frame format Table 63 – DLSL frame control field Table 64 – Date frame format Table 65 – General command frame format |
106 | Table 66 – DLSL command frame Table 67 – Format of keep-alive command frame |
107 | 9 Network layer 9.1 General 9.2 Protocol stack Figure 38 – WIA-PA network layer protocol stack Table 68 – Format of time synchronization command frame |
108 | 9.3 Function description 9.3.1 General 9.3.2 Addressing Figure 39 – WIA-PA network layer reference model |
109 | 9.3.3 Routing 9.3.4 Packet lifecycle management 9.3.5 Joining and leaving network of device Table 69 – Example of a routing table |
110 | 9.3.6 End-to-end network performance monitoring 9.3.7 Fragmentation and reassembly 9.3.8 Network layer state machine Figure 40 – Network layer state machine |
111 | Table 70 – NL state transitions (1 of 4) |
115 | 9.4 Network layer data services 9.4.1 General 9.4.2 NLDE-DATA.request |
116 | 9.4.3 NLDE-DATA.confirm 9.4.4 NLDE-DATA.indication Table 71 – NLDE-DATA.request parameters Table 72 – NLDE-DATA.confirm parameters |
117 | 9.4.5 Time sequence of NL data services 9.5 Network layer management services 9.5.1 General 9.5.2 Network communication status report services Figure 41 – Time sequence of NL data services Table 73 – NLDE-DATA.indication parameters |
118 | Table 74 – NLME-COMM-STATUS.request parameters |
119 | Table 75 – NLME-COMM-STATUS.indication parameters Table 76 – NLME-COMM-STATUS.confirm parameters |
120 | 9.5.3 Network joining services Table 77 – NLME-JOIN.request parameters |
121 | Table 78 – NLME-JOIN.indication parameters Table 79 – NLME-JOIN.response parameters |
122 | Table 80 – NLME-JOIN.confirm parameters |
123 | Figure 42 – Time sequence for field device joining through routing device |
124 | Figure 43 – One-hop joining process for routing device Figure 44 – Multi-hop join process of routing device |
125 | 9.5.4 Networkleaving services Table 81 – NLME-LEAVE.request parameters Table 82 – NLME-LEAVE.indication parameters |
126 | Table 83 – NLME-LEAVE.response parameters Table 84 – NLME-LEAVE.confirm parameters |
127 | Figure 45 – Active leaving process of field device (leaving routing device) Figure 46 – Passive leaving of field device |
128 | Figure 47 – Active leaving process of routing device Figure 48 – Passive leaving process of routing device |
129 | 9.5.5 Cluster member report services Table 85 – NLME-RPT-CLRMEM.request parameters Table 86 – NLME-RPT-CLRMEM.confirm parameter |
130 | Table 87 – NLME-RPT-CLRMEM.response parameters |
131 | 9.5.6 Neighbour information report services Figure 49 – Cluster member reporting process Table 88 – NLME-NEIGHBOUR-INFO.request parameters |
132 | Table 89 – NLME-NEIGHBOUR-INFO.confirm parameter |
133 | 9.5.7 Route allocation services Figure 50 – Neighbour information reporting process Table 90 – NLME-ADD_ROUTE.request parameters |
134 | Table 91 – NLME-ADD_ROUTE.confirm parameters |
135 | Figure 51 – Time sequence for route adding Table 92 – NLME-UPDATE_ROUTE.request parameters |
136 | Table 93 – NLME-UPDATE_ROUTE.confirm parameter |
137 | Figure 52 – Time sequence for route updating Table 94 – NLME-UPDATE_ROUTE.request parameters |
138 | Table 95 – NLME-DELETE_ROUTE.confirm parameters |
139 | 9.5.8 Communication resource allocation services Figure 53 – Time sequence for route deleting |
140 | Table 96 – NLME-ADD-LINK.request parameters |
141 | Table 97 – NLME-ADD-LINK.confirm parameters |
142 | Figure 54 – Adding a link originating from gateway device to routing device Figure 55 – Adding a link originating from routing device to field device |
143 | Table 98 – NLME-UPDATE-LINK.request parameters Table 99 – NLME-UPDATE-LINK.confirm parameters |
144 | Figure 56 – Updating a link originating by gateway device to routing device |
145 | Figure 57 – Updating a link originating from routing device to field device Table 100 – NLME-RELEASE-LINK.request parameters |
146 | Table 101 – NLME-RELEASE-LINK.confirm parameters |
147 | Figure 58 – Releasing a link originating from gateway device to routing device Figure 59 – Releasing a link originating from routing device to field device |
148 | Table 102 – NLME-ADD-SFR.request parameters Table 103 – NLME-ADD-SFR.confirm parameters |
149 | Figure 60 – Adding a superframe originating from gateway device to routing device Figure 61 – Adding a superframe originating from routing device to field device |
150 | Table 104 – NLME-UPDATA-SFR.request parameters Table 105 – NLME-UPDATE-SFR.confirm parameters |
151 | Figure 62 – Updating a superframe originating from gateway device to routing device |
152 | Figure 63 – Updating a superframe originating from routing device to field device Table 106 – NLME-RELEASE-SFR.request parameters |
153 | Table 107 – NLME-RELEASE-SFR.confirm parameters |
154 | Figure 64 – Releasing a superframe originating from gateway device to routing device Figure 65 – Releasing a superframe originating from routing device to field device |
155 | 9.5.9 Aggregation and disaggregation services Table 108 – NLME-AGG.indication parameters Table 109 – NLME-AGO-SEND.request parameters |
156 | 9.5.10 Device status report services Table 110 – NLME-DAG.indication parameter Table 111 – NLME-DEVICE -STATUS.request parameters |
157 | Figure 66 – Device status reporting process from field device to routing device Table 112 – NLME-DEVICE -STATUS.indication parameters Table 113 – NLME-DEVICE -STATUS.confirm parameter |
158 | 9.5.11 Channel condition report services Figure 67 – Device status reporting process from routing device to gateway device Table 114 – NLME-CHANNEL-CONDITION.request parameters |
159 | Figure 68 – Channel condition reporting process from field device to routing device Table 115 – NLME-CHANNEL-CONDITION.indication parameters Table 116 – NLME-CHANNEL-CONDITION.confirm parameter |
160 | 9.5.12 Failure path report services Figure 69 – Channel condition reporting process from routing device to gateway device Table 117 – NLME-PATH_FAILURE.request parameters |
161 | 9.5.13 Network attribute getting services Figure 70 – Failure path reporting process Table 118 – NLME-PATH_FAILURE.indication parameters Table 119 – NLME-PATH_FAILURE.confirm parameters |
162 | Table 120 – NLME-INFO_GET.request parameters |
163 | Table 121 – NLME-INFO_GET.indication parameters |
164 | Table 122 – NLME-INFO_GET.response parameters |
165 | 9.5.14 Network attribute setting services Table 123 – NLME-INFO_GET.confirm parameters |
166 | Table 124 – NLME-INFO_SET.request parameters Table 125 – NLME-INFO_SET.indication parameters |
167 | Table 126 – NLME-SET.response parameters |
168 | 9.6 Network layer packet formats 9.6.1 Common packet format Table 127 – NLME-SET.confirm parameters Table 128 – Network layer common packet format Table 129 – Control field format |
169 | 9.6.2 Data packet format Table 130 – Network layer data packet format |
170 | 9.6.3 Aggregated packet format 9.6.4 Command packet format Table 131 – Aggregated packet format |
171 | Table 132 – Format of NL command packet Table 133 – Network layer command packet |
172 | Table 134 – Execution results of commands Table 135 – Format of joining request packet |
173 | Table 136 – Format of joining response packet Table 137 – Format of communication status report request packet |
174 | Table 138 – Format of leaving request packet Table 139 – Value of Leaving reason Table 140 – Format of leaving response packet Table 141 – Format of cluster member report request packet |
175 | Table 142 – Format of cluster member report response packet Table 143 – Format of neighbour information report request packet |
176 | Table 144 – Format of route adding request packet Table 145 – Format of route adding response packet Table 146 – Format of route update request packet |
177 | Table 147 – Format of route update response packet Table 148 – Format of route deleting request packet Table 149 – Format of route deleting response packet |
178 | Table 150 – Format of link adding request packet Table 151 – Format of link adding response packet |
179 | Table 152 – Format of link update request packet Table 153 – Format of link update response packet |
180 | Table 154 – Format of link release request packet Table 155 – Format of link release response packet Table 156 – Format of superframe adding request packet |
181 | Table 157 – Format of superframe adding response packet Table 158 – Format of superframe update request packet |
182 | Table 159 – Format of superframe update response packet Table 160 – Format of superframe release request packet Table 161 – Format of superframe release response packet |
183 | Table 162 – Format of device condition report request packet Table 163 – Format of device condition information field |
184 | Table 164 – Format of channel condition report request packet Table 165 – Format of channel quality information field Table 166 – Format of path failure report request packet |
185 | Table 167 – Format of attribute getting request packet Table 168 – Format of attribute getting response packet |
186 | Table 169 – Format of attribute setting request packet Table 170 – Format of attribute setting response packet |
187 | 10 Application layer 10.1 Overview 10.1.1 General 10.1.2 AL structure 10.1.3 Functions of UAP Figure 71 – AL structure |
188 | 10.1.4 Functions of ASL 10.2 UAP 10.2.1 General 10.2.2 UAO Figure 72 – User application process |
189 | 10.2.3 Method definition |
190 | Table 171 – UAO method definition Table 172 – Request format of READ method Table 173 – Response format of READ method |
191 | Table 174 – Request format of WRITE method Table 175 – Response format of WRITE method |
192 | Table 176 – Format of PUBLISH method Table 177 – Format of REPORT method Table 178 – Format of REPORT ACK method |
193 | 10.3 Application sub-layer 10.3.1 General 10.3.2 Application sub-layer data entity |
194 | Table 179 – ASLDE-DATA.request parameters Table 180 – ASLDE-DATA.confirm parameters |
195 | Table 181 – ASLDE-DATA.indication parameters Table 182 – ASLDE-AGG.request parameters |
196 | Figure 73 – C/S communication process Table 183 – ASLDE-DAG.indication parameters |
197 | Figure 74 – P/S communication process (disable aggregation function) Figure 75 – P/S communication process (enable aggregation function) |
198 | 10.4 Application sub-layer packet formats 10.4.1 General 10.4.2 ASL general packet format Figure 76 – R/S communication process Table 184 – Application sub-layer general packet format |
199 | Table 185 – Packet control field format Table 186 – Packet type subfield value |
200 | 10.4.3 Packet formats Table 187 – ASL data packet format |
201 | 11 Security 11.1 General Table 188 – ASL acknowledgement packet format |
202 | 11.2 Security management framework Figure 77 – Security management framework of WIA-PA network |
203 | 11.3 Secure communication protocol stack 11.3.1 General |
204 | 11.3.2 Data link sub-layer security Figure 78 – Security communication protocol stack Table 189 – Format of security DLPDU |
205 | 11.3.3 Application sub-layer security Table 190 – Format of DLSL security header Table 191 – Structure of security control field in DLSL security header Table 192 – Structure of security material control field in DLSL security header |
206 | 11.4 Key management 11.4.1 Key type Table 193 – Security APDU structure Table 194 – Structure of ASL security header field |
207 | 11.4.2 Key distribution 11.4.3 Key update 11.4.4 Key status Figure 79 – Key lifecycle |
208 | 11.5 Secure joining process 11.5.1 Secure joining process of a new WIA-PA device Figure 80 – Secure joining process of WIA-PA device |
209 | 11.5.2 Device security material getting services Table 195 – DLME-SEC.request parameters Table 196 – DLME-SEC.indication parameters |
210 | Table 197 – DLME-SEC.response parameters |
211 | Table 198 – DLME-SEC.confirm parameters |
212 | Figure 81 – Time sequence for field device joining (field device to routing device) |
213 | Figure 82 – Time sequence for field device joining (routing device to gateway device) |
214 | Figure 83 – One-hop joining process for routing device |
215 | Figure 84 – Multi-hop join process of routing device(new routing device to routing device) |
216 | 11.6 Secure transportation 11.6.1 Process of secure transportation from field device to host configuration computer Figure 85 – Multi-hop join process of routing device (routing device to gateway device) |
217 | 11.6.2 Process of secure transportation from host configuration computer to field device |
218 | Annexes Annex A (informative) Security strategy for WIA-PA network Risk analysis for WIA-PA network A.2 Security principles for WIA-PA network A.3 Security objectives for WIA-PA network A.4 Graded and layered security system |
219 | Table A.1 – Graded and layered security measures for WIA-PA network Table A.2 – Security levels of data packets |
220 | Annex B (informative) Format description B.1 Time sequence diagram B.2 Packet or frame format Figure B.1 – Time sequence diagram Table B.1 – Packet or frame format in octet(s) |
221 | Table B.2 – Subfield format in bit(s) |
222 | Annex C (informative) Example of UAO C.1 General C.2 Analog input object C.2.1 Overview C.2.2 Class attribute of AIO C.2.3 Instance attribute of AIO Table C.1 – AIO class attribute |
223 | Table C.2 – AIO instance attributes |
224 | Annex D (informative) Country-specific and region-specific provisions |
225 | Annex E (informative) Regional modification for compliance with ETSI standards E.1 General E.2 Compliance with EN 300 440-2 E.3 Compliance with EN 300 328 Table E.1 – Applicable EN 300 440-2 requirements list Table E.2 – Applicable EN 300 328 requirements list |
226 | Table E.3 – Timeslot timing definitions and calculations |
227 | Bibliography |