September 2001 doc IEEE 802 15 01441 r

September 2001 doc. : IEEE 802. 15 -01/441 r 0 IEEE P 802. 15 Working Group for Wireless Personal Area Networks. TM Current Status of IEEE 802. 15. 2 WLAN/WPAN Coexistence Task Group Submission 1 Steve Shellhammer, Symbol Technologies

September 2001 doc. : IEEE 802. 15 -01/441 r 0 IEEE 802. 15. 2 Deliverables • Coexistence Model – Quantify the effect of the mutual interference of WLAN (e. g. 802. 11) and WPAN (e. g. Bluetooth) upon one another. • Coexistence Mechanisms – Mechanisms or techniques to facilitate coexistence of WLAN and WPAN devices. • Both to be documented in an IEEE Recommended Practice Submission 2 Steve Shellhammer, Symbol Technologies

September 2001 doc. : IEEE 802. 15 -01/441 r 0 Coexistence Model • The purpose of this Coexistence Model is: – To quantify the effect of the mutual interference under various scenarios. • WLAN in Laptop and Bluetooth in nearby PDA • WLAN and Bluetooth in the same Laptop – To demonstrate the effectiveness of the adopted Coexistence Mechanism. Submission 3 Steve Shellhammer, Symbol Technologies

September 2001 doc. : IEEE 802. 15 -01/441 r 0 Coexistence Model • The Coexistence Model consist of four sections, – Physical Layer Models of the 802. 11 b and 802. 15. 1 (Bluetooth) Radios – MAC Layer Models of both 802. 11 b and 802. 15. 1 (Bluetooth) – RF Channel Model of the Radio Channel – Data Traffic Models of the traffic over both 802. 11 and 802. 15. 1 (Bluetooth) networks. Submission 4 Steve Shellhammer, Symbol Technologies

September 2001 doc. : IEEE 802. 15 -01/441 r 0 Coexistence Mechanisms • Collaborative Mechanisms – Some form of communication exists between the WLAN and WPAN. – Use this link to provide fair sharing of medium (i. e. air waves) • Non-Collaborative Mechanisms – No communication between WLAN and WPAN exists. – Techniques to minimize the effects of the mutual interference Submission 5 Steve Shellhammer, Symbol Technologies

September 2001 doc. : IEEE 802. 15 -01/441 r 0 Coexistence Mechanisms • Collaborative Mechanism (Only one) – Selected a joint proposal from Mobilian, Symbol Technologies, and NIST. – Primarily a Coordinated Scheduling Mechanism. – To be used when IEEE 802. 11 b and Bluetooth are to be co-located in the same unit (e. g. laptop computer) Submission 6 Steve Shellhammer, Symbol Technologies

September 2001 doc. : IEEE 802. 15 -01/441 r 0 Collaborative Mechanism • The Collaborative Coexistence Mechanism relies on physical signals between the two radios within a common unit (e. g. laptop). • These physical signals are used to coordinate timing of the WLAN and WPAN transmissions to avoid interference. Submission 7 Steve Shellhammer, Symbol Technologies

September 2001 doc. : IEEE 802. 15 -01/441 r 0 Coexistence Mechanisms • Non-Collaborative (Multiple) – Bluetooth Packet Selection and Scheduling – Bluetooth Adaptive Frequency Hopping Submission 8 Steve Shellhammer, Symbol Technologies

September 2001 doc. : IEEE 802. 15 -01/441 r 0 Bluetooth Packet Selection & Scheduling • The this is a non-collaborative mechanism in which the Bluetooth devices independently detect the presence of 802. 11 b and determine which channels are utilized by 802. 11 b. • Then the Bluetooth piconet does not transmit when it hops into one of the channel occupied by 802. 11 b. Submission 9 Steve Shellhammer, Symbol Technologies

September 2001 doc. : IEEE 802. 15 -01/441 r 0 Adaptive Frequency Hopping • Just like the Bluetooth Packet Scheduling technique, the this is a non-collaborative mechanism in which the Bluetooth devices independently detect the presence of 802. 11 b and determine which channels are utilized by 802. 11 b. • In AFH the Bluetooth piconet remaps its hopping sequence to “hop around” the frequency band occupied by 802. 11 b Submission 10 Steve Shellhammer, Symbol Technologies

September 2001 doc. : IEEE 802. 15 -01/441 r 0 Draft Recommended Practice • Word documents of each of the various clauses we presented at the July meeting. • Revisions of the various clauses are being reviewed on conference calls, due the cancellation of the September meeting. • The Editor is starting to integrate the clauses together in Framemaker. Submission 11 Steve Shellhammer, Symbol Technologies

September 2001 doc. : IEEE 802. 15 -01/441 r 0 Adaptive Frequency Hopping • There is continuing detailed technical work being done on the Adaptive Frequency Hopping specification. • This work is being done in conference calls, where the team reviews documents distributed over the email reflector. Submission 12 Steve Shellhammer, Symbol Technologies

September 2001 doc. : IEEE 802. 15 -01/441 r 0 FCC NPRM • Under Current FCC ruled Adaptive Frequency Hopping is only allowed for low-power (< 1 mw) Bluetooth devices. • In May 2001 the FCC issued a Notice of Proposed Rule Making. • If this Rule Making issues then Adaptive Frequency Hopping will be allowed under high-power Bluetooth devices. Submission 13 Steve Shellhammer, Symbol Technologies

September 2001 doc. : IEEE 802. 15 -01/441 r 0 Donation from OPNET Corporation • The OPNET Corporation has donated three time-limited licenses of their Network analysis tool to several small companies to support the work of 802. 15. 2. • These tools will be used to model Adaptive Frequency Hopping in an 802. 11 b environment to model performance improvements. Submission 14 Steve Shellhammer, Symbol Technologies

September 2001 doc. : IEEE 802. 15 -01/441 r 0 Liaison with Bluetooth SIG • Currently both the IEEE 802. 15. 2 Coexistence Task Group and the Bluetooth SIG Coexistence Working Group are developing specifications for Adaptive Frequency Hopping. • In July the 802. 15 Chairman and the 802. 15. 2 Chairman sent a letter to the Bluetooth SIG General Manager and Board of Directors. 802. 15 -01/349 r 0. Submission 15 Steve Shellhammer, Symbol Technologies

September 2001 doc. : IEEE 802. 15 -01/441 r 0 Liaison with Bluetooth SIG • The letter requested that the Bluetooth SIG work with the IEEE 802. 15. 2 Task Group in agreeing on a common Adaptive Frequency Hopping specification. • The Bluetooth SIG agreed in principle to work together with the IEEE. Submission 16 Steve Shellhammer, Symbol Technologies

September 2001 doc. : IEEE 802. 15 -01/441 r 0 Liaison with Bluetooth SIG • However, the two organizations have been unable to exchange any technical information, due to Bluetooth SIG Intellectual Property rules. • We are currently at an impasse since the two organizations cannot exchange any technical information. Submission 17 Steve Shellhammer, Symbol Technologies