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