BS IEC 62601:2011:2014 Edition
$215.11
Industrial communication networks. Fieldbus specifications. WIA-PA communication network and communication profile
Published By | Publication Date | Number of Pages |
BSI | 2014 | 200 |
This International Standard specifies the system architecture and the communication protocol of Wireless networks for Industrial Automation – Process Automation (WIA-PA) built on IEEE STD 802.15.4-2006.
PDF Catalog
PDF Pages | PDF Title |
---|---|
4 | CONTENTS |
15 | FOREWORD |
17 | 1 Scope 2 Normative references 3 Terms, definitions and abbreviations 3.1 Terms and definitions |
21 | 3.2 Abbreviations |
23 | 4 Specification of data types 4.1 Representation of boolean type 4.2 Representation of unsigned integer type 4.3 Representation of octet type 4.4 Representation of floating point number type |
24 | 5 WIA-PA overview 5.1 Device types 5.2 Network topology |
25 | Figures Figure 1 – Example of WIA-PA physical topology (combination of star and mesh) Figure 2 – Example of WIA-PA physical topology (star-only) |
26 | 5.3 Protocol architecture Figure 3 – OSI basic reference model mapped to WIA-PA |
27 | 5.4 Interconnection 6 System management 6.1 General Figure 4 – The architecture of WIA-PA gateway |
28 | Figure 5 – DMAP in system management |
29 | 6.2 Framework of system management |
30 | 6.3 Joining process Figure 6 – Hybrid centralized and distributed system management scheme |
31 | Figure 7 – Joining process of routing device through the gateway device Figure 8 – Joining process of routing device through an online routing device |
32 | Figure 9 – Joining process of field device through a gateway device Figure 10 – Joining process of field device through a routing device |
33 | 6.4 Virtual Communication Relationship (VCR) Figure 11 – Long address structure of device Figure 12 – Short address structure of routing device Figure 13 – Short address structure of field device |
34 | Tables Table 1 – Protocol support for VCR |
35 | 6.5 Routing configuration and communication resource allocation |
36 | Figure 14 – An example of resource allocation |
37 | Figure 15 – Allocation process of routing device’s communication resources |
38 | 6.6 Aggregation and disaggregation Figure 16 – Allocation process of field device’s communication resources |
39 | Table 2 – Relations between VCR and aggregation function |
40 | Table 3 – Format of aggregated data followed by field device’s DAGO Table 4 – Format of aggregated packet followed by routing device’s PAGO |
42 | Figure 17 – Example of aggregation and disaggregation |
43 | Table 5 – DAGO class attributes Table 6 – DAGO instance attributes |
44 | Table 7 – MEM_STRUCT structure Table 8 – PAGO class attributes Table 9 – PAGO instance attributes Table 10 – DGO class attributes |
45 | 6.7 Performance monitoring Figure 18 – Process of path failure report Figure 19 – Device status report process of field device Table 11 – DGO instance attributes |
46 | 6.8 Leaving process Figure 20 – Device status report process of routing device Figure 21 – Process of channel condition report |
47 | Figure 22 – Active leaving process of routing device Figure 23 – Passive leaving process of routing device |
48 | Figure 24 – Active leaving process of field device (leaving from gateway device) Figure 25 – Active leaving process of field device (leaving from routing device) |
49 | 6.9 Management information base and services Figure 26 – Passive leaving process of field device (leaving from gateway device) Figure 27 – Passive leaving process of field device (leaving from routing device) |
50 | Table 12 – Unstructured attributes |
53 | Table 13 – Structured attributes |
54 | Table 14 – NLRoute_Struct structure Table 15 – Superframe_Struct structure |
55 | Table 16 – Link_Struct structure |
56 | Table 17 – Neighbor_Struct structure Table 18 – ChanCon_Struct structure |
57 | Table 19 – Device_struct structure |
59 | Table 20 – VCR_Struct structure |
60 | Table 21 – DevConRep_Struct structure Table 22 – Key_Struct structure |
61 | Table 23 – ObjList_Struct structure Table 24 – DMAP-MIB-GET.request parameters |
62 | Table 25 – DMAP-MIB-GET.confirm parameters |
63 | 7 Physical Layer Table 26 – DMAP-MIB-SET.request parameters Table 27 – DMAP-MIB-SET.confirm parameters |
64 | 8 Data link layer 8.1 General 8.2 Protocol stack 8.3 MAC overview and function extension Figure 28 – WIA-PA DLL protocol stack |
65 | Table 28 – MAC extended PIB attributes Table 29 – MAC extended command frame |
66 | Table 30 – MLME-KEEP-LIVE.confirm parameters Table 31 – MLME-KEEP-LIVE.indication parameters Table 32 – MLME-TIME-SYN.request parameters |
67 | Table 33 – MLME-TIME-SYN.confirm parameters Table 34 – MLME-TIME-SYN.indication parameters Table 35 – Beacon payload |
68 | 8.4 DLSL function description Table 36– Format of keep-alive command frame Table 37– Format of time synchronization command frame |
69 | Figure 29 – WIA-PA DLSL reference model |
70 | Figure 30 – WIA-PA superframe |
71 | Table 38 – Hopping mechanisms |
72 | Figure 31 – R1, R2 and R3 superframe structures Figure 32 – An example of long cycle data transmission |
74 | Figure 33 – DLSL state machine Table 39 – DLSL state transitions |
75 | 8.5 Data link sub-layer data services |
76 | Table 40 – DLDE-DATA.request parameters |
77 | Table 41 – DLDE-DATA.confirm parameters Table 42 – Status table |
78 | Figure 34 – Time sequence of data service Table 43 – DLDE-DATA.indication parameters |
79 | 8.6 Data link sub-layer management services Table 44 – DLME-DISCOVERY.request parameters |
80 | Table 45 – DLME- DISCOVERY.confirm parameters Table 46 – Network descriptor list |
81 | Figure 35 – Time sequence of network discovery Table 47 – DLME-JOIN.request parameters |
82 | Table 48 – DLME-JOIN.indication parameters Table 49 – DLME-JOIN.response parameters |
83 | Table 50 – DLME-JOIN.confirm parameters Table 51 – DLME-LEAVE.request parameters |
84 | Table 52 – DLME-LEAVE.indication parameters Table 53 – DLME-LEAVE.confirm parameters |
85 | Table 54 – DLME-CHANNEL-CONDITION.indication parameters Table 55 – DLME-NEIGHBOR-INFO.indication parameters |
86 | Table 56 – DLME-COMM-STATUS.indication parameters Table 57 – DLME -KEEP-LIVE.confirm parameters |
87 | Table 58 – DLME -KEEP-LIVE.indication parameters Table 59 – DLME-TIME-SYN.request parameters Table 60 – DLME -TIME-SYN.confirm parameters |
88 | 8.7 DLSL frame formats Figure 36 – General frame format Table 61 – DLME-TIME-SYN.indication parameters Table 62 – DLSL frame control filed |
89 | 9 Network layer 9.1 General 9.2 Protocol stack Figure 37 – WIA-PA network layer protocol stack Table 63 – Date frame format Table 64 – General command frame format Table 65 – DLSL command frame |
90 | 9.3 Function description Figure 38 – WIA-PA Network layer reference model |
91 | Table 66 – Example of a routing table |
92 | Figure 39 – Network layer state machine Table 67 – Network layer states Table 68– NL state transitions |
93 | 9.4 Network layer data services Table 69 – NLDE-DATA.request parameters |
94 | Table 70 – NLDE-DATA.confirm parameters Table 71 – NLDE-DATA.indication parameters |
95 | 9.5 Network layer management services Figure 40 – Time sequence of NL data services Table 72 – NLME-COMM-STATUS.request parameters |
96 | Table 73 – NLME-COMM-STATUS.indication parameters Table 74 – NLME-COMM-STATUS.confirm parameters |
97 | Table 75 – NLME-JOIN.request parameters |
98 | Table 76 – NLME-JOIN.indication parameters Table 77 – NLME-JOIN.response parameters |
99 | Table 78 – NLME-JOIN.confirm parameters |
100 | Figure 41 – Time sequence for field device joining through routing device |
101 | Figure 42 – One-hop joining process for routing device |
102 | Figure 43 – Multi-hop join process of routing device |
103 | Table 79 – NLME-LEAVE.request parameters Table 80 – NLME-LEAVE.indication parameters Table 81 – NLME-LEAVE.response parameters |
104 | Table 82 – NLME-LEAVE.confirm parameters |
105 | Figure 44 – Active leaving process of field device (leaving routing device) |
106 | Figure 45 – Passive leaving of field device |
107 | Figure 46 – Active leaving process of routing device |
108 | Figure 47 – Passive leaving process of routing device |
109 | Table 83 – NLME-RPT-CLRMEM.request parameters Table 84 – NLME-RPT-CLRMEM.confirm parameter |
110 | Figure 48 – Cluster member reporting process Table 85 – NLME-RPT-CLRMEM.response parameters |
111 | Table 86 – NLME-NEIGHBOR-INFO.request parameters |
112 | Figure 49 – Neighbor information reporting process Table 87 – NLME-NEIGHBOR-INFO.confirm parameter Table 88 – NLME-ADD_ROUTE.request parameters |
113 | Table 89 – NLME-ADD_ROUTE.confirm parameters |
114 | Figure 50 – Time sequence for route adding Table 90 – NLME-UPDATE_ROUTE.request parameters |
115 | Table 91 – NLME-UPDATE_ROUTE.confirm parameter |
116 | Figure 51 – Time sequence for route updating Table 92 – NLME-UPDATE_ROUTE.request parameters |
117 | Table 93 – NLME-DELETE_ROUTE.confirm parameters |
118 | Figure 52 – Time sequence for route deleting |
119 | Table 94 – NLME-ADD-LINK.request parameters |
120 | Table 95 – NLME-ADD-LINK.confirm parameters |
121 | Figure 53 – Adding a link originated from gateway device to routing device Figure 54 – Adding a link originated from routing device to field device |
122 | Table 96 – NLME-UPDATE-LINK.request parameters Table 97 – NLME-UPDATE-LINK.confirm parameters |
123 | Figure 55 – Updating a link originated by gateway device to routing device Figure 56 – Updating a link originated from routing device to field device |
124 | Table 98 – NLME-RELEASE-LINK.request parameters Table 99 – NLME-RELEASE-LINK.confirm parameters |
125 | Figure 57 – Releasing a link originated from gateway device to routing device |
126 | Figure 58 – Releasing a link originated from routing device to field device Table 100 – NLME-ADD-SFR.request parameters |
127 | Table 101 – NLME-ADD-SFR.confirm parameters |
128 | Figure 59 – Adding a superframe originated from gateway device to routing device Figure 60 – Adding a superframe originated from routing device to field device |
129 | Table 102 – NLME-UPDATA-SFR.request parameters Table 103 – NLME-UPDATE-SFR.confirm parameters |
130 | Figure 61 – Updating a superframe originated from gateway device to routing device Figure 62 – Updating a superframe originated from routing device to field device |
131 | Table 104 – NLME-RELEASE-SFR.request parameters Table 105 – NLME-RELEASE-SFR.confirm parameters |
132 | Figure 63 – Releasing a superframe originated from gateway device to routing device Figure 64 – Releasing a superframe originated from routing device to field device |
133 | Table 106 – NLME-AGG.indication parameters Table 107 – NLME-AGO-SEND.request parameters |
134 | Table 108 – NLME-DAG.indication parameter Table 109 – NLME- DEVICE -STATUS.request parameters |
135 | Figure 65 – Device status reporting process from field device to routing device Table 110 – NLME- DEVICE -STATUS.indication parameters Table 111 – NLME- DEVICE -STATUS.confirm parameter |
136 | Figure 66 – Device status reporting process from routing device to gateway device Table 112 – NLME-CHANNEL-CONDITION.request parameters |
137 | Figure 67 – Channel condition reporting process from field device to routing device Table 113 – NLME-CHANNEL-CONDITION.indication parameters Table 114 – NLME-CHANNEL-CONDITION.confirm parameter |
138 | Figure 68 – Channel condition reporting process from routing device to gateway device Table 115 – NLME-PATH_FAILURE.request parameters |
139 | Figure 69 – Failure path reporting process Table 116 – NLME-PATH_FAILURE.indication parameters Table 117 – NLME-PATH_FAILURE.confirm parameters |
140 | Table 118 – NLME-INFO_GET.request parameters |
141 | Table 119 – NLME-INFO_GET. indication parameters Table 120 – NLME-INFO_GET.response parameters |
142 | Table 121 – NLME-INFO_GET.response parameters |
143 | Table 122 – NLME-INFO_SET.request parameters Table 123 – NLME-INFO_SET.indication parameters |
144 | Table 124 – NLME-SET. response parameters |
145 | 9.6 Network layer packet formats Figure 70 – Network layer common packet format Table 125 – NLME-SET.confirm parameters Table 126– Control field format |
146 | Figure 71 – Network layer data packet format Figure 72 – Aggregated packet format |
147 | Figure 73 – Format of NL command packet |
148 | Table 127 – Network layer command packet |
149 | Table 128 – Execution results of commands Table 129 – Format of joining request packet Table 130 – Format of joining response packet |
150 | Table 131 – Format of communication status report request packet Table 132 – Format of leaving request packet Table 133 – Value of leaving reason |
151 | Table 134 – Format of leaving response packet Table 135 – Format of cluster member report request packet Table 136 – Format of cluster member report response packet |
152 | Table 137 – Format of neighbor information report request packet Table 138 – Format of route adding request packet Table 139 – Format of route adding response packet |
153 | Table 140 – Format of route update request packet Table 141 – Format of route update response packet Table 142 – Format of route deleting request packet |
154 | Table 143 – Format of route deleting response packet Table 144 – Format of link adding request packet Table 145 – Format of link adding response packet |
155 | Table 146 – Format of link update request packet Table 147 – Format of link update response packet |
156 | Table 148 – Format of link release request packet Table 149 – Format of link release response packet Table 150 – Format of superframe adding request packet |
157 | Table 151 – Format of superframe adding response packet Table 152 – Format of superframe update request packet Table 153 – Format of superframe update response packet |
158 | Table 154 – Format of superframe release request packet Table 155 – Format of superframe release response packet Table 156 – Format of device condition report request packet |
159 | Table 157 – Format of device condition information Table 158 – Format of channel condition report request packet Table 159 – Format of channel quality information |
160 | Table 160 – Format of path failure report request packet Table 161 – Format of attribute getting request packet |
161 | Table 162 – Format of attribute getting response packet Table 163 – Format of attribute setting request packet |
162 | 10 Application Layer 10.1 Overview Figure 74 – AL structure Table 164 – Format of attribute setting response packet |
163 | 10.2 UAP Figure 75 – User application process |
165 | Table 165 – Method definition Table 166 – Request format of READ Table 167 – Response format of READ method |
166 | Table 168 – Request format of WRITE method Table 169 – Response format of WRITE method |
167 | Table 170 – Format of PUBLISH method Table 171 – Format of REPORT method Table 172 – Format of REPORT ACK method |
168 | 10.3 Application sub-layer |
169 | Table 173 – ASLDE-DATA.request parameters Table 174 – ASLDE-DATA.confirm parameters |
170 | Table 175 – ASLDE-DATA.indication parameters Table 176 – ASLDE-AGG.request parameters |
171 | Figure 76 – C/S communication process Table 177 – ASLDE-DAG.indication parameters |
172 | Figure 77 – P/S communication process (disable aggregation function) |
173 | 10.4 Application sub-layer packet formats Figure 78 – P/S communication process (enable aggregation function) Figure 79 – R/S communication process |
174 | Figure 80– Application sub-layer general packet format Table 178 – Packet control field format Table 179 – Packet type subfield value |
175 | Figure 81 – ASL data packet format |
176 | Figure 82 – Acknowledgement packet format |
177 | 11 Security 11.1 General 11.2 Security management framework Figure 83 – Security management framework of WIA-PA network |
178 | 11.3 Secure communication protocol stack |
179 | Figure 84 – Security communication protocol stack Figure 85 – MPDU structure |
180 | Figure 86 – Security DLPDU structure Table 180 – Structure of DLSL security header |
181 | Figure 87 – Security APDU structure Table 181 – Structure of security control field in DLSL security header Table 182 – Structure of security material control field in DLSL security header |
182 | 11.4 Key management Table 183 – Structure of ASL security header field |
183 | Figure 88 – Key lifecycle |
184 | 11.5 Secure joining process Figure 89 – Secure joining process of WIA-PA device |
185 | Table 184 – DLME-SEC.request parameters Table 185 – DLME-SEC.indication parameters |
186 | Table 186 – DLME-SEC.response parameters Table 187 – DLME-SEC.confirm parameters |
187 | Figure 90 – Time sequence for field device joining (Field device to routing device) Figure 91 – Time sequence for field device joining (Routing device to gateway device) |
188 | Figure 92 – One-hop joining process for routing device Figure 93 – Multi-hop join process of routing device(new routing device to routing device) |
189 | 11.6 Secure transportation Figure 94 – Multi-hop join process of routing device (routing device to gateway device) |
191 | Annex A (informative) Security strategy for WIA-PA network |
192 | Table A.1 – Graded and layered security measures for WIA-PA network Table A.2 – Security levels of data packets |
193 | Annex B (informative) Format description for WIA-PA standard Figure B.1 – Time sequence diagram Table B.1 – Packet or frame format in octet(s) |
194 | Table B.2 – Subfield format in bit(s) |
195 | Annex C (informative) Example of UAO Table C.1 – AIO Class Attribute |
196 | Table C.2 – AIO Instance Attributes |
197 | Bibliography |