July 2008 doc.: IEEE 802.11-08/1021r0 November 2008 Proposal to Add Optional non 802.11n Radio Scans for 40 MHz Operation in 2.4 GHz Authors: Date: 2008-10-21 Peter Loc & Kiran Luke Qian etc, Cisco

Abstract From LB136 CID 10025 Comment July 2008 September 2008 doc.: IEEE 802.11-08/1101r3 doc.: IEEE 802.11-08/1021r0 November 2008 Abstract From LB136 CID 10025 Comment The recommendation for the HT-STA not to transmit any 40 MHz mask PPDUs if it has knowledge of non-802.11 devices operating in the area does nothing to ensure that 802.11n devices with such knowledge will not interfere with non-802.11n devices. In fact, it inadvertently creates a class of 802.11 devices that knowingly interfere with non-802.11 devices. If a device has the capability to detect the presence of other non-802.11 devices, it should act upon such detection. The capability to detect non-802.11 devices operating in the same area should be an option in the standard to address concerns relating to coexistence with non 802.11 devices. Slide 2 Peter Loc & Kiran Page 2 Luke Qian etc, Cisco John R. Barr, Motorola, Inc.

From LB136 CID 10025 Proposed Resolution July 2008 September 2008 doc.: IEEE 802.11-08/1101r3 doc.: IEEE 802.11-08/1021r0 November 2008 From LB136 CID 10025 Proposed Resolution Proposed changes: 1) In subclause 7.32.57.5, use the reserved bit B3 of the Extended Capabilities field for the HT AP or HT STA to declare its support for non-802.11 radio scans. 2) In subclause 11.14.3.2, insert after line 12 , page 223: Before an AP or IDO STA that is capable of detecting non-802.11 radios (bit B3 of the Extended capabilities field is set to 1) starts a 20/40 MHz BSS, it shall perform overlapping BSS scans to search for non-802.11 radios. 3) In subclause 11.14.3.2, insert after line 65 , page 223, the following: An FC HT AP 2G4 that is capable of detecting non-802.11 radios shall keep the value of 20/40 Operation Permitted to FALSE if a presence of non-802.11 radio is detected. 4) Insert the following paragraph at the end of subclause 11.14.5, page 230, after line 13 An FC HT STA 2G4 that is associated with an FC HT AP 2G4 and is capable of performing non-802.11 radio scans (bit B3 of the Extended Capability field is set to 1) shall perform at least one non 802.11 radio scan every dot11BSSWidthTriggerScanInterval seconds., unless the FC HT STA 2G4 satisfies the conditions described in 11.14.6. Slide 3 Peter Loc & Kiran Page 3 Luke Qian etc, Cisco John R. Barr, Motorola, Inc.

Reasons for accepting the CID 10025 comment resolution as proposed July 2008 September 2008 doc.: IEEE 802.11-08/1101r3 doc.: IEEE 802.11-08/1021r0 November 2008 Reasons for accepting the CID 10025 comment resolution as proposed To remove the notion that the recommendation in the current IEEE802.11n Draft 7.0 creates a class of 802.11n devices that knowingly interfere with non 802.11 devices Results from new interference measurement tests (shown later in this submission) indicate that Bluetooth services (especially voice calls) are severely affected when a 40 MHz BSS is started or the BSS switches from 20 MHz to 40 MHz in 2.4 GHz Slide 4 Peter Loc & Kiran Page 4 Luke Qian etc, Cisco John R. Barr, Motorola, Inc.

Effects of 40 MHz operation in 2.4 GHz July 2008 doc.: IEEE 802.11-08/1021r0 November 2008 Effects of 40 MHz operation in 2.4 GHz Interference measurement tests so far indicated various degrees of interferences – See the following list of documents 11-08-0880-00-0vht-reponse-to-official-comments 11-08-1101-03-000n-additional-40-mhz-scanning-proposal 11-08-0992-00-000n-20-40-mhz-11n-interference-on-bluetooth 11-08-1140-00-000n-11n-40-mhz-and-bt-coexistence-test-results 11-08-0880-00-0vht-reponse-to-official-comment 19-08-0027-02-0000-ieee-802-11n-40-mhz-impact-on-bt-performance It is observed that results of most measurement tests were taken when Bluetooth devices have already adapted to a new hopping sequence to avoid interfering channels Slide 5 Peter Loc & Kiran Luke Qian etc, Cisco

Severe interferences to existing Bluetooth service were observed when July 2008 doc.: IEEE 802.11-08/1021r0 November 2008 Interference Measurement Tests Focusing on BSS starting and switching to 40 MHz Severe interferences to existing Bluetooth service were observed when BSS started a 40 MHz operation BSS switched from 20 MHz to 40 MHz Slide 6 Peter Loc & Kiran Luke Qian etc, Cisco

Test Setup November 2008 July 2008 doc.: IEEE 802.11-08/1021r0 11n - AP ~10m Bluetooth Headset 11n - STA ~1m Bluetooth dongle Agilent Spectrum Analyser Peter Loc & Kiran Luke Qian etc, Cisco

Test setup (ctn) 11n Continuous Tx-Rx mode, Channel 5 July 2008 doc.: IEEE 802.11-08/1021r0 November 2008 Test setup (ctn) 11n Continuous Tx-Rx mode, Channel 5 Bandwidth switched at noted time-stamp Bluetooth Mustek Wireless Stereo Headset, MBT-A120 single tone sent from the laptop to headset through the dongle Peter Loc & Kiran Luke Qian etc, Cisco

Nominal Behaviour Top : on@40MHz  20MHz  40MHz July 2008 doc.: IEEE 802.11-08/1021r0 November 2008 Nominal Behaviour off 40MHz 20MHz 40MHz off 20MHz 40MHz 20MHz Start (11n off): 0s 11n-on : ~10s 11n-switch-BW : ~60s 11n-switch-BW : ~120s Top : on@40MHz  20MHz  40MHz Bottom : on@20MHz  40MHz  20MHz Peter Loc & Kiran Luke Qian etc, Cisco

Worst Case Top : on@40MHz  20MHz Bottom : on@20MHz  40MHz July 2008 doc.: IEEE 802.11-08/1021r0 November 2008 Worst Case off 40MHz 20MHz off 20MHz 40MHz Start (11n off) : 0s 11n-on : ~10s 11n-switch-BW : ~130s Top : on@40MHz  20MHz Bottom : on@20MHz  40MHz Peter Loc & Kiran Luke Qian etc, Cisco

AFH-Settling Times November 2008 Nominal Startup Transition Trial 1 July 2008 doc.: IEEE 802.11-08/1021r0 November 2008 AFH-Settling Times Nominal Startup Transition Trial 1 Trial 2 Trial 3 Average on@20MHz 25s 29s 24s 26s on@40MHz 33s 31s 40MHz->20MHz 0s 1ms? 20MHz->40MHz 10s 5s 6s 7s Worst Case Startup 62s Trials are all randomly started and are unrelated across the rows/columns ? : a blip was heard 86s Peter Loc & Kiran Luke Qian etc, Cisco

Explanation (AFH) November 2008 July 2008 doc.: IEEE 802.11-08/1021r0 11n-40MHz Bluetooth 11n-20MHz 40MHz(adapt) 20MHz(adapt) Peter Loc & Kiran Luke Qian etc, Cisco

Explanation (on a BW switch) July 2008 doc.: IEEE 802.11-08/1021r0 November 2008 Explanation (on a BW switch) 20MHz  40MHz 40MHz20MHz (needs time to adapt) (has no extra interference) (lower available Bandwidth) (extra Bandwidth) Peter Loc & Kiran Luke Qian etc, Cisco

Conclusions Bluetooth AFH-adaptation Time 11n Switch-on July 2008 doc.: IEEE 802.11-08/1021r0 November 2008 Conclusions Bluetooth AFH-adaptation Time 11n Switch-on Both 20MHz and 40MHz cause interferences to Bluetooth device 40MHz takes Bluetooth longer time to adapt Worst case can result in more than 1 minute disruption After AFH adapts, the effect of 11n is not perceived 11n Bandwidth-switch 40MHz  20MHz does not affect Bluetooth 20MHz  40MHz results in ~5-10s disruption Peter Loc & Kiran Luke Qian etc, Cisco

Proposal Accept the comment resolution as proposed by CID 10025 July 2008 doc.: IEEE 802.11-08/1021r0 November 2008 Proposal Accept the comment resolution as proposed by CID 10025 Accepting this resolution will surely alleviate concerns on coexistence between 40 MHz capable 802.11n devices and others that share the 2.4 GHz band. Peter Loc & Kiran Luke Qian etc, Cisco

Thank You Q&A November 2008 July 2008 doc.: IEEE 802.11-08/1021r0 Peter Loc & Kiran Luke Qian etc, Cisco