Download
ieee p802 15 working group for wireless personal area networks tm n.
Skip this Video
Loading SlideShow in 5 Seconds..
IEEE P802.15 Working Group for Wireless Personal Area Networks TM PowerPoint Presentation
Download Presentation
IEEE P802.15 Working Group for Wireless Personal Area Networks TM

IEEE P802.15 Working Group for Wireless Personal Area Networks TM

119 Vues Download Presentation
Télécharger la présentation

IEEE P802.15 Working Group for Wireless Personal Area Networks TM

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. IEEE P802.15 Working Group for Wireless Personal Area NetworksTM Current Status of IEEE 802.15.2 WLAN/WPAN Coexistence Task Group Steve Shellhammer, Symbol Technologies

  2. 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 Steve Shellhammer, Symbol Technologies

  3. 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. Steve Shellhammer, Symbol Technologies

  4. Coexistence Model • The Coexistence Model consist of four sections, • Physical Layer Models of the 802.11b and 802.15.1 (Bluetooth) Radios • MAC Layer Models of both 802.11b 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. Steve Shellhammer, Symbol Technologies

  5. 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 Steve Shellhammer, Symbol Technologies

  6. 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.11b and Bluetooth are to be co-located in the same unit (e.g. laptop computer) Steve Shellhammer, Symbol Technologies

  7. 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. Steve Shellhammer, Symbol Technologies

  8. Coexistence Mechanisms • Non-Collaborative (Multiple) • Bluetooth Packet Selection and Scheduling • Bluetooth Adaptive Frequency Hopping Steve Shellhammer, Symbol Technologies

  9. Bluetooth Packet Selection & Scheduling • The this is a non-collaborative mechanism in which the Bluetooth devices independently detect the presence of 802.11b and determine which channels are utilized by 802.11b. • Then the Bluetooth piconet does not transmit when it hops into one of the channel occupied by 802.11b. Steve Shellhammer, Symbol Technologies

  10. 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.11b and determine which channels are utilized by 802.11b. • In AFH the Bluetooth piconet remaps its hopping sequence to “hop around” the frequency band occupied by 802.11b Steve Shellhammer, Symbol Technologies

  11. 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. Steve Shellhammer, Symbol Technologies

  12. 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. Steve Shellhammer, Symbol Technologies

  13. 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. Steve Shellhammer, Symbol Technologies

  14. 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.11b environment to model performance improvements. Steve Shellhammer, Symbol Technologies

  15. 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/349r0. Steve Shellhammer, Symbol Technologies

  16. 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. Steve Shellhammer, Symbol Technologies

  17. 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. Steve Shellhammer, Symbol Technologies