60 likes | 78 Views
ITU DFS/TPC Submission. WRC ’03 has discussions about 5GHz spectrum allocations on the agenda 802.11 would like to have international rules and allocations that are favorable to RLANs RLANs are secondary users in the band. Radar systems and satellites are primary.
E N D
ITU DFS/TPC Submission • WRC ’03 has discussions about 5GHz spectrum allocations on the agenda • 802.11 would like to have international rules and allocations that are favorable to RLANs • RLANs are secondary users in the band. Radar systems and satellites are primary. • In preparation for WRC, the ITU is already hearing papers and having discussions The negotiating has already begun! Bill McFarland, Atheros
802.11 Needs to Prove We Can Share with Radar/Satellite • ETSI/BRAN has already done simulations and submitted studies to ITU meetings – for HIPERLAN/2 • They have invited us to submit similar materials for 802.11a, with them in a single document This is an area in which we are completely aligned with ETSI/BRAN Bill McFarland, Atheros
Draft of ITU Submission Available for Review • Dave Skellern, Niels Erven, and I created a draft submission for 802.11a • It is available on the server in the submissions/regulatory/ as RR-01-026r0_ITU_DFS_Submission.doc • The ITU submission is a joint submission with ETSI/BRAN HIPERLAN/2 • We made the 802.11a sections as similar as possible to the HIPERLAN/2 sections that had already been created Bill McFarland, Atheros
What’s in it? • Overviews of 802.11a and HIPERLAN/2 (background reading for radar engineers) • A description of the DFS measurements and associated control frames for both systems (TGh) • Simulation results of radar detection and avoidance for HIPERLAN/2, done by ETSI/BRAN • A discussion of why 802.11a and HIPERLAN/2 will have similar radar avoidance performance • A recommended set of test signals and procedures to establish that an RLAN can avoid radar (created by BRAN) Many thanks to ETSI/BRAN! Bill McFarland, Atheros
Key Technical Aspects • We need to listen for radar pulses during any gaps in transmission, as well as at network startup • In order to detect the radar quickly enough, the channel must be clear ~20% of the time • Even when far overloaded, channel occupancy saturates at ~80% for DCF/eDCF • In PCF and HCF modes, the AP will need to insure that channel occupancy is <~80% • We have hooks that may be able to improve radar detection performance, but we are holding these in reserve • We want to match, not exceed or lag, HIPERLAN/2’s radar avoidance claims Bill McFarland, Atheros
What’s Next • Vic Hayes will sponsor the document through the regulatory group (and clean up the diagrams) • If you have comments on the document, send them to bill@atheros.com (Remember it is an overview not a specification!) • There will be a vote to submit the revised document to the ITU at the closing plenary Bill McFarland, Atheros