IEEE 802.15.3-2003
$167.38
IEEE Standard for Information technology– Local and metropolitan area networks– Specific requirements– Part 15.3: Wireless Medium Access Control (MAC) and Physical Layer (PHY) Specifications for High Rate Wireless Personal Area Networks (WPAN)
Published By | Publication Date | Number of Pages |
IEEE | 2003 | 324 |
New IEEE Standard – Superseded. The protocol and compatible interconnection of data and multimedia communication equipment via 2.4 GHz radio transmissions in a Wireless Personal Area Network (WPAN) using low power and multiple modulation formats to support scalable data rates is defined in this standard. The Medium Access Control (MAC) sublayer protocol supports both isochronous and asynchronous data types
PDF Catalog
PDF Pages | PDF Title |
---|---|
1 | Cover Page CONTENTS |
2 | Title Page |
4 | Introduction |
5 | Participants |
10 | 1. Overview 1.1 Scope |
11 | 1.2 Purpose 2. References |
12 | 3. Definitions |
14 | 4. Acronyms and abbreviations |
17 | 5. General description 5.1 What is a piconet? 5.2 Components of an 802.15.3 piconet 5.3 Overview of MAC functionality |
18 | 5.3.1 Coordination 5.3.1.1 Starting a piconet 5.3.1.2 Handing over control of the piconet 5.3.1.3 Creating a child piconet |
19 | 5.3.1.4 Creating a neighbor piconet 5.3.2 Ending a piconet 5.3.2.1 Ending a piconet with a dependent piconet involved |
20 | 5.3.3 Association and disassociation 5.3.4 Security overview 5.3.5 The 802.15.3 superframe |
21 | 5.3.6 Channel time management |
22 | 5.3.7 Data communications between DEVs 5.3.8 Information discovery in the piconet |
23 | 5.3.9 Dynamic channel selection 5.3.10 Power management |
24 | 5.3.11 Controlling transmit power in the piconet 5.4 Characteristics of the 2.4 GHz PHY 5.4.1 General characteristics |
25 | 5.4.2 Coexistence and interoperability 6. Layer management 6.1 Overview of management model |
27 | 6.2 Generic management primitives |
28 | 6.2.1 MLME-GET.request and PLME-GET.request 6.2.1.1 When generated 6.2.1.2 Effect of receipt 6.2.2 MLME-GET.confirm and PLME-GET.confirm 6.2.2.1 When generated 6.2.2.2 Effect of receipt |
29 | 6.2.3 MLME-SET.request and PLME-SET.request 6.2.3.1 When generated 6.2.3.2 Effect of receipt 6.2.4 MLME-SET.confirm and PLME-SET.confirm 6.2.4.1 When generated 6.2.4.2 Effect of receipt |
30 | 6.3 MLME SAP interface |
31 | 6.3.1 Reset 6.3.1.1 MLME-RESET.request |
32 | 6.3.2 Scan 6.3.2.1 MLME-SCAN.request |
34 | 6.3.2.2 MLME-SCAN.confirm |
35 | 6.3.3 Start |
36 | 6.3.3.1 MLME-START.request 6.3.3.2 MLME-START.confirm |
37 | 6.3.3.3 MLME-START-DEPENDENT.request 6.3.3.4 MLME-START-DEPENDENT.confirm |
38 | 6.3.4 Synchronization 6.3.4.1 MLME-SYNCH.request |
39 | 6.3.4.2 MLME-SYNCH.confirm 6.3.4.3 MLME-ATP-EXPIRED.indication 6.3.5 Association |
41 | 6.3.5.1 MLME-ASSOCIATE.request |
42 | 6.3.5.2 MLME-ASSOCIATE.indication |
43 | 6.3.5.3 MLME-ASSOCIATE.response 6.3.5.4 MLME-ASSOCIATE.confirm |
44 | 6.3.5.5 MLME-DEV-ASSOCIATION-INFO.indication 6.3.6 Disassociation |
45 | 6.3.6.1 MLME-DISASSOCIATE.request 6.3.6.2 MLME-DISASSOCIATE.indication |
46 | 6.3.6.3 MLME-DISASSOCIATE.confirm 6.3.7 Key request |
47 | 6.3.7.1 MLME-REQUEST-KEY.request 6.3.7.2 MLME-REQUEST-KEY.indication |
48 | 6.3.7.3 MLME-REQUEST-KEY.response 6.3.7.4 MLME-REQUEST-KEY.confirm |
49 | 6.3.8 Key distribution 6.3.8.1 MLME-DISTRIBUTE-KEY.request |
50 | 6.3.8.2 MLME-DISTRIBUTE-KEY.indication 6.3.8.3 MLME-DISTRIBUTE-KEY.response |
51 | 6.3.8.4 MLME-DISTRIBUTE-KEY.confirm 6.3.9 Security management 6.3.9.1 MLME-MEMBERSHIP-UPDATE.request |
53 | 6.3.9.2 MLME-SECURITY-ERROR.indication 6.3.9.3 MLME-SECURITY-MESSAGE.request |
54 | 6.3.9.4 MLME-SECURITY-MESSAGE.indication 6.3.9.5 MLME-SECURITY-MESSAGE.confirm 6.3.10 PNC handover |
55 | 6.3.10.1 MLME-PNC-HANDOVER.request |
56 | 6.3.10.2 MLME-PNC-HANDOVER.indication 6.3.10.3 MLME-PNC-HANDOVER.response |
57 | 6.3.10.4 MLME-PNC-HANDOVER.confirm 6.3.10.5 MLME-NEW-PNC.indication 6.3.11 PNC requesting information |
58 | 6.3.11.1 MLME-PNC-INFO.request |
59 | 6.3.11.2 MLME-PNC-INFO.indication 6.3.11.3 MLME-PNC-INFO.response |
60 | 6.3.11.4 MLME-PNC-INFO.confirm 6.3.12 Security information retrieval 6.3.12.1 MLME-SECURITY-INFO.request |
61 | 6.3.12.2 MLME-SECURITY-INFO.indication |
62 | 6.3.12.3 MLME-SECURITY-INFO.response 6.3.12.4 MLME-SECURITY-INFO.confirm 6.3.13 ASIE management |
63 | 6.3.13.1 MLME-CREATE-ASIE.request |
64 | 6.3.13.2 MLME-CREATE-ASIE.confirm |
65 | 6.3.13.3 MLME-RECEIVE-ASIE.indication 6.3.14 Peer information retrieval |
66 | 6.3.14.1 MLME-PROBE.request 6.3.14.2 MLME-PROBE.indication |
67 | 6.3.14.3 MLME-PROBE.response 6.3.14.4 MLME-PROBE.confirm 6.3.15 Information announcement to peers |
68 | 6.3.15.1 MLME-ANNOUNCE.request 6.3.15.2 MLME-ANNOUNCE.indication |
69 | 6.3.15.3 MLME-ANNOUNCE.confirm 6.3.16 Piconet services 6.3.16.1 MLME-PICONET-SERVICES.indication |
70 | 6.3.16.2 MLME-PICONET-SERVICES.response |
71 | 6.3.16.3 MLME-PICONET-SERVICES.confirm 6.3.17 Stream management 6.3.17.1 MLME-CREATE-STREAM.request |
73 | 6.3.17.2 MLME-CREATE-STREAM.confirm |
74 | 6.3.17.3 MLME-MODIFY-STREAM.request 6.3.17.4 MLME-MODIFY-STREAM.confirm |
75 | 6.3.17.5 MLME-TERMINATE-STREAM.request 6.3.17.6 MLME-TERMINATE-STREAM.indication |
76 | 6.3.17.7 MLME-TERMINATE-STREAM.confirm 6.3.17.8 MLME-MULTICAST-RX-SETUP.request |
77 | 6.3.18 Channel status request |
78 | 6.3.18.1 MLME-CHANNEL-STATUS.request 6.3.18.2 MLME-CHANNEL-STATUS.indication |
79 | 6.3.18.3 MLME-CHANNEL-STATUS.response 6.3.18.4 MLME-CHANNEL-STATUS.confirm |
80 | 6.3.19 Remote scan 6.3.19.1 MLME-REMOTE-SCAN.request |
81 | 6.3.19.2 MLME-REMOTE-SCAN.indication |
82 | 6.3.19.3 MLME-REMOTE-SCAN.response 6.3.19.4 MLME-REMOTE-SCAN.confirm |
83 | 6.3.20 Piconet parameter change 6.3.20.1 MLME-PICONET-PARM-CHANGE.request |
84 | 6.3.20.2 MLME-PICONET-PARM-CHANGE.confirm 6.3.21 Power change |
85 | 6.3.21.1 MLME-TX-POWER-CHANGE.request 6.3.21.2 MLME-TX-POWER-CHANGE.indication |
86 | 6.3.21.3 MLME-TX-POWER-CHANGE.confirm 6.3.22 Power management operation 6.3.22.1 MLME-PS-SET-INFORMATION.request |
88 | 6.3.22.2 MLME-PS-SET-INFORMATION.confirm 6.3.22.3 MLME-SPS-CONFIGURE.request |
89 | 6.3.22.4 MLME-SPS-CONFIGURE.confirm 6.3.22.5 MLME-PM-MODE-CHANGE.request |
90 | 6.3.22.6 MLME-PM-MODE-CHANGE.confirm 6.3.22.7 MLME-PM-MODE-ACTIVE.indication 6.4 PLME SAP interface |
91 | 6.4.1 PLME-RESET.request 6.4.1.1 When generated 6.4.1.2 Effect of receipt |
92 | 6.4.2 PLME-RESET.confirm 6.4.2.1 When generated 6.4.2.2 Effect of receipt 6.4.3 PLME-TESTMODE.request 6.4.3.1 When generated 6.4.3.2 Effect of receipt 6.4.4 PLME-TESTMODE.confirm 6.4.4.1 When generated |
93 | 6.4.4.2 Effect of receipt 6.4.5 PLME-TESTOUTPUT.request 6.4.5.1 When generated 6.4.5.2 Effect of receipt 6.5 MAC management 6.5.1 MAC PIB PNC group 6.5.2 MAC PIB characteristic group |
96 | 6.6 MAC SAP |
97 | 6.6.1 MAC-ASYNC-DATA.request 6.6.1.1 When generated 6.6.1.2 Effect of receipt |
98 | 6.6.2 MAC-ASYNC-DATA.confirm 6.6.2.1 When generated 6.6.2.2 Effect of receipt 6.6.3 MAC-ASYNC-DATA.indication 6.6.3.1 When generated 6.6.3.2 Effect of receipt |
99 | 6.6.4 MAC-ISOCH-DATA.request 6.6.4.1 When generated 6.6.4.2 Effect of receipt 6.6.5 MAC-ISOCH-DATA.confirm 6.6.5.1 When generated 6.6.5.2 Effect of receipt |
100 | 6.6.6 MAC-ISOCH-DATA.indication 6.6.6.1 When generated 6.6.6.2 Effect of receipt 6.7 Physical layer (PHY) service specification |
102 | 6.7.1 Transferring PHY data 6.7.1.1 PHY-DATA.request 6.7.1.2 PHY-DATA.indication 6.7.1.3 PHY-DATA.confirm |
103 | 6.7.2 Controlling PHY transmission 6.7.2.1 PHY-TX-START.request 6.7.2.2 PHY-TX-START.confirm |
104 | 6.7.2.3 PHY-TX-END.request 6.7.2.4 PHY-TX-END.confirm 6.7.3 PHY CCA functions 6.7.3.1 PHY-CCA-START.request |
105 | 6.7.3.2 PHY-CCA-START.confirm 6.7.3.3 PHY-CCA-END.request 6.7.3.4 PHY-CCA-END.confirm |
106 | 6.7.3.5 PHY-CCA.indication 6.7.4 Controlling the PHY receiver 6.7.4.1 PHY-RX-START.request 6.7.4.2 PHY-RX-START.confirm |
107 | 6.7.4.3 PHY-RX-START.indication 6.7.4.4 PHY-RX-END.request |
108 | 6.7.4.5 PHY-RX-END.confirm 6.7.4.6 PHY-RX-END.indication |
109 | 6.7.5 Controlling the PHY power usage 6.7.5.1 PHY-PM.request 6.7.5.2 PHY-PM.confirm 7. MAC frame formats |
110 | 7.1 Frame format conventions |
111 | 7.2 General frame format |
112 | 7.2.1 Frame control |
113 | 7.2.1.1 Protocol version 7.2.1.2 Frame type 7.2.1.3 SEC 7.2.1.4 ACK policy 7.2.1.5 Retry |
114 | 7.2.1.6 More data 7.2.2 Piconet ID (PNID) 7.2.3 SrcID and DestID |
115 | 7.2.4 Fragmentation control 7.2.4.1 MSDU number 7.2.4.2 Fragment number 7.2.4.3 Last fragment number 7.2.5 Stream index 7.2.6 MAC header validation |
116 | 7.2.7 MAC frame body 7.2.7.1 Frame payload 7.2.7.2 Secure session ID (SECID) 7.2.7.3 Secure frame counter (SFC) 7.2.7.4 Secure payload 7.2.7.5 Integrity code 7.2.7.6 FCS |
117 | 7.3 Format of individual frame types 7.3.1 Beacon frame 7.3.1.1 Non-secure beacon frame |
119 | 7.3.1.2 Secure beacon frame |
120 | 7.3.2 Acknowledgement frames 7.3.2.1 Immediate ACK (Imm-ACK) frame 7.3.2.2 Delayed ACK (Dly-ACK) frame |
122 | 7.3.3 Command frame 7.3.3.1 Non-secure command frame |
123 | 7.3.3.2 Secure command frame |
124 | 7.3.4 Data frame 7.3.4.1 Non-secure data frame 7.3.4.2 Secure data frame |
125 | 7.4 Information elements |
126 | 7.4.1 Channel time allocation |
127 | 7.4.2 BSID 7.4.3 Parent piconet 7.4.4 DEV association |
128 | 7.4.5 PNC shutdown 7.4.6 Piconet parameter change |
129 | 7.4.7 Application specific |
130 | 7.4.8 Pending channel time map (PCTM) 7.4.9 PNC handover 7.4.10 CTA status |
131 | 7.4.11 Capability |
133 | 7.4.12 Transmit power parameters 7.4.13 PS status |
134 | 7.4.14 Continued wake beacon (CWB) 7.4.15 Overlapping PNID 7.4.16 Piconet services |
135 | 7.4.17 Vendor specific 7.5 MAC command types |
137 | 7.5.1 Association and disassociation commands 7.5.1.1 Association request |
138 | 7.5.1.2 Association response 7.5.1.3 Disassociation request |
139 | 7.5.2 Security commands 7.5.2.1 Request key 7.5.2.2 Request key response 7.5.2.3 Distribute key request |
140 | 7.5.2.4 Distribute key response 7.5.3 PNC handover commands 7.5.3.1 PNC handover request |
141 | 7.5.3.2 PNC handover response 7.5.3.3 PNC handover information 7.5.4 Information request commands |
142 | 7.5.4.1 PNC information request 7.5.4.2 PNC information |
143 | 7.5.4.3 Security information request 7.5.4.4 Security information |
144 | 7.5.4.5 Probe request |
145 | 7.5.4.6 Probe response |
146 | 7.5.5 Information announcement commands 7.5.5.1 Piconet services |
147 | 7.5.5.2 Announce 7.5.6 Channel time allocation request, modification, and termination commands |
148 | 7.5.6.1 Channel time request |
150 | 7.5.6.2 Channel time response |
151 | 7.5.7 Channel status commands 7.5.7.1 Channel status request 7.5.7.2 Channel status response |
152 | 7.5.7.3 Remote scan request 7.5.7.4 Remote scan response |
154 | 7.5.7.5 Transmit power change 7.5.8 Power management commands 7.5.8.1 PS set information request 7.5.8.2 PS set information response |
155 | 7.5.8.3 SPS configuration request |
156 | 7.5.8.4 SPS configuration response |
157 | 7.5.8.5 PM mode change 7.5.9 Special commands 7.5.9.1 Security message |
158 | 7.5.9.2 Vendor specific 8. MAC functional description 8.1 Introduction |
159 | 8.2 Starting, maintaining and stopping piconets 8.2.1 Scanning through channels |
160 | 8.2.2 Starting a piconet |
161 | 8.2.3 PNC handover |
164 | 8.2.4 Dependent PNC handover |
167 | 8.2.5 Child piconet |
170 | 8.2.6 Neighbor piconet |
172 | 8.2.7 Stopping piconet operations 8.2.7.1 Stopping an independent or parent piconet 8.2.7.2 Parent PNC stopping a dependent piconet |
173 | 8.2.7.3 Dependent PNC termination of a dependent piconet 8.2.8 Non-PNC capable DEVs 8.3 Association and disassociation with a piconet 8.3.1 Association |
175 | 8.3.2 Piconet services |
177 | 8.3.3 Broadcasting piconet information 8.3.4 Disassociation |
178 | 8.4 Channel access |
179 | 8.4.1 Interframe space (IFS) 8.4.2 Contention based channel access |
180 | 8.4.3 Channel time allocation period channel access |
181 | 8.4.3.1 Channel time allocations (CTA) |
182 | 8.4.3.2 Channel time allocation (CTA) and channel time usage |
183 | 8.4.3.3 Management CTAs |
184 | 8.4.3.4 Slotted aloha access for open and association MCTAs 8.4.3.5 Allocation of MCTAs |
185 | 8.4.3.6 Guard time |
187 | 8.4.3.7 Calculating channel time requests |
188 | 8.5 Channel time management |
189 | 8.5.1 Isochronous stream management 8.5.1.1 Isochronous stream creation |
192 | 8.5.1.2 Isochronous stream modification |
195 | 8.5.1.3 Isochronous stream termination |
197 | 8.5.2 Asynchronous channel time reservation and termination 8.5.2.1 Asynchronous channel time reservation |
199 | 8.5.2.2 Asynchronous channel time termination |
200 | 8.6 Synchronization 8.6.1 Time accuracy 8.6.2 Beacon generation |
201 | 8.6.3 Beacon reception 8.6.4 Beacon information announcement |
202 | 8.6.5 Acquiring synchronization 8.7 Fragmentation and defragmentation |
203 | 8.8 Acknowledgement and retransmission 8.8.1 No-ACK 8.8.2 Immediate ACK 8.8.3 Delayed acknowledgement |
205 | 8.8.4 Retransmissions 8.8.5 Duplicate detection 8.9 Peer discovery |
206 | 8.9.1 PNC information request 8.9.2 Probe request and response |
207 | 8.9.3 Announce |
208 | 8.9.4 Channel status request |
209 | 8.9.5 Remote scan |
210 | 8.9.6 PNC channel scanning |
211 | 8.10 Changing piconet parameters 8.10.1 Moving beacon |
212 | 8.10.2 Changing superframe duration 8.10.3 Setting the PNID or BSID |
213 | 8.10.4 Maintaining synchronization in dependent piconets 8.11 Interference mitigation |
214 | 8.11.1 Dynamic channel selection |
215 | 8.11.2 Transmit power control |
216 | 8.11.2.1 Maximum transmitter power for the CAP, beacon and directed MCTAs 8.11.2.2 Adjustable transmitter power in a CTA 8.12 Multi-rate support |
217 | 8.13 Power management |
218 | 8.13.1 Piconet synchronized power save (PSPS) mode |
219 | 8.13.2 Device synchronized power save (DSPS) mode 8.13.2.1 Creation, use and management of DSPS sets |
220 | 8.13.2.2 Changing DSPS mode and operation |
221 | 8.13.2.3 CTA timing in DSPS mode |
223 | 8.13.3 Asynchronous power save (APS) mode |
224 | 8.13.4 Message sequence charts for power save modes |
228 | 8.14 ASIE operation |
229 | 8.15 MAC sublayer parameters |
230 | 9. Security 9.1 Security mechanisms 9.1.1 Security membership and key establishment 9.1.2 Key transport 9.1.3 Data encryption 9.1.4 Data integrity 9.1.5 Beacon integrity protection |
231 | 9.1.6 Command integrity protection 9.1.7 Freshness protection 9.2 Security modes 9.2.1 Security mode 0 9.2.2 Security mode 1 9.3 Security support |
232 | 9.3.1 PNC handover 9.3.2 Changes in the piconet group data key 9.3.3 Joining a secure piconet 9.3.4 Membership update |
233 | 9.3.5 Secure frame generation |
234 | 9.3.6 Secure frame reception |
235 | 9.3.7 Selecting the SECID for a new key 9.3.8 Key selection |
238 | 9.4 Protocol details |
239 | 9.4.1 Security information request and distribution |
240 | 9.4.2 Key distribution protocol |
241 | 9.4.3 Key request protocol |
242 | 10. Security specifications 10.1 Modes for security 10.2 Symmetric cryptography building blocks 10.2.1 Security interfaces 10.2.2 CTR + CBC-MAC (CCM) combined encryption and data authentication 10.2.3 CCM parameters |
243 | 10.2.4 Nonce value 10.2.5 AES encryption 10.3 Symmetric cryptography implementation 10.3.1 Symmetric cryptography data formats |
244 | 10.3.2 Symmetric cryptographic operations |
245 | 10.4 CCM mode |
246 | 10.4.1 Inputs 10.4.2 Data authentication |
249 | 10.4.3 Encryption 10.4.4 Output |
250 | 10.4.5 Decryption 10.4.6 Restrictions 10.4.7 List of symbols |
251 | 11. PHY specification for the 2.4 GHz band 11.1 Overview of the 2.4 GHz PHY |
252 | 11.2 General requirements 11.2.1 Operating frequency range 11.2.2 RF power measurements 11.2.3 Channel assignments 11.2.4 Scanning channels |
253 | 11.2.5 Unwanted emissions 11.2.6 Operating temperature range 11.2.7 PHY layer timing 11.2.7.1 Interframe space |
254 | 11.2.7.2 Receive-to-transmit turnaround time 11.2.7.3 Transmit-to-receive turnaround time 11.2.7.4 Time between successive transmissions 11.2.7.5 Channel switch time 11.2.8 Data size restrictions 11.2.8.1 Maximum frame length 11.2.8.2 Maximum transfer unit size 11.2.8.3 Minimum fragment size |
255 | 11.2.9 Header check sequence |
256 | 11.2.10 Channel access methods |
257 | 11.3 Modulation and coding 11.3.1 Base data rate 11.3.2 Signal constellations |
258 | 11.3.3 DQPSK modulation |
259 | 11.3.4 QPSK and 16/32/64-QAM with trellis coding |
267 | 11.4 PHY frame format 11.4.1 Frame format |
269 | 11.4.2 PHY preamble |
271 | 11.4.3 Header modulation 11.4.4 Scrambling |
272 | 11.4.5 PHY header 11.4.6 Stuff bits |
273 | 11.4.7 Tail symbols |
276 | 11.5 Transmitter specifications 11.5.1 Error vector magnitude definition |
277 | 11.5.2 EVM calculated values 11.5.3 Transmit PSD mask |
278 | 11.5.4 Transmit center frequency tolerance 11.5.5 Symbol rate |
279 | 11.5.6 Clock synchronization 11.5.7 Transmit power-on and power-down ramp 11.5.8 RF carrier suppression 11.5.9 Transmit power |
280 | 11.6 Receiver specifications 11.6.1 Error rate criterion 11.6.2 Receiver sensitivity 11.6.3 Receiver maximum input level 11.6.4 Receiver jamming resistance |
281 | 11.6.5 Receiver CCA performance |
282 | 11.6.6 Receiver RSSI 11.6.7 Link quality indication 11.7 PHY management |
286 | Annex A (normative) Frame convergence sublayer A.1 Generic convergence layer |
287 | A.1.1 FCSL PDU classification |
288 | A.1.2 IEEE 802.2 FCSL A.1.2.1 IEEE 802.2 FCSL QoS support |
289 | A.1.2.2 Data entity inter-relationships |
290 | A.2 802.2 FCSL SAP A.2.1 MA-UNITDATA.request |
291 | A.2.1.1 When generated A.2.1.2 Effect of receipt A.2.2 MA-UNITDATA.indication |
292 | A.2.2.1 When generated A.2.2.2 Effect of receipt A.2.3 MA-UNITDATA-STATUS.indication |
293 | A.2.3.1 When generated A.2.3.2 Effect of receipt |
294 | Annex B (informative) Security considerations B.1 Background assumptions B.1.1 Physical assumptions B.1.2 Network assumptions |
295 | B.1.3 Attack model assumptions B.1.4 Security key lifecycle issues B.1.4.1 Key lifecycle B.1.4.2 Membership lifecycle B.1.4.3 Group membership change rekey B.2 Claimed security services B.2.1 Beacon protection protocol |
296 | B.2.2 Distribute key protocol B.2.3 Key request protocol |
297 | B.2.4 Data protection protocol |
298 | Annex C (informative) Coexistence, interoperability, and interference C.1 Interoperability C.1.1 Interoperability with 802.11 DSSS and 802.11b |
299 | C.1.2 802.11 FHSS and 802.15.1 C.2 Coexistence C.2.1 Coexistence with 802.11b |
300 | C.2.1.1 Passive scanning C.2.1.2 Dynamic channel selection C.2.1.3 The ability to request channel quality information C.2.1.4 Link quality and RSSI C.2.1.5 Channel plan that minimizes channel overlap |
301 | C.2.1.6 Lower transmit power C.2.1.7 Transmit power control C.2.1.8 Neighbor piconet capability |
302 | C.2.2 Coexistence with 802.15.1 and 802.11 FHSS C.2.2.1 PHY colloaborative coexistence enhancements C.2.2.2 MAC coexistence via collaboration |
303 | C.2.2.3 Other techniques C.3 Coexistence performance C.3.1 Allowed operation C.3.2 Assumptions for coexistence calculations |
305 | C.3.3 Peformance impact on 802.15.3 piconets |
306 | C.3.3.1 802.11b overlapping with 802.15.3 |
310 | C.3.3.2 802.15.1 and 802.11 FHSS overlapping with 802.15.3 |
311 | C.4 Notes on the calculations |
312 | Annex D (normative) Protocol implementation conformance statement (PICS) proforma D.1 Introduction D.1.1 Scope D.1.2 Purpose D.2 Abbreviations and special symbols |
313 | D.3 Instructions for completing the PICS proforma D.4 Identification of the implementation |
314 | D.5 Identification of the protocol |
315 | D.6 Global statement of conformance D.7 PICS proforma-IEEE Std. 802.15.3-2003 D.7.1 Major roles for IEEE 802.15.3 DEVs |
316 | D.7.2 PHY functions |
317 | D.7.3 Major capabilities for the MAC sublayer D.7.3.1 MAC frames |
319 | D.7.3.2 MAC sublayer functions |
322 | D.7.4 Security support |
323 | Annex E (informative) Bibliography |