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