1、January, 2001,Tod Sizer, Lucent Technologies / Bell Laboratories,Slide 1,Bluetooth SIG Coexistence Working Group,Liaison Report,January, 2001,Tod Sizer, Lucent Technologies / Bell Laboratories,Slide 2,Bluetooth SIG Coexistence Working Group,Coexistence Working Group Charter IEEE/Bluetooth SIG Coordi
2、nation Live Testing Finalizing simulations Adaptive Hopping,January, 2001,Tod Sizer, Lucent Technologies / Bell Laboratories,Slide 3,Coexistence Working Group Charter,Work within the Bluetooth community as well as with cross industry groups (e.g. IEEE) to quantify the detrimental effects which Bluet
3、ooth and other wireless products will have on the performance of both. This information will be imperative for members of the Bluetooth community to advise their customers of the realistic performance one can expect in different environments as well a build products which span between Bluetooth and
4、other wireless products. In addition, it will be used to disseminate SIG sponsored information on issues of coexistence to regulatory bodies. Develop methods of Bluetooth operation that will be used to improve coexistence between systems in the shared radio band. These will be issued as Best Practic
5、es white papers, improvements to the Bluetooth specifications, or formal profiles as necessary. To work closely with the Radio 2.0 Working Group to evaluate coexistence issues in new proposed radio designs.,January, 2001,Tod Sizer, Lucent Technologies / Bell Laboratories,Slide 4,IEEE 802.15 TG2/ Blu
6、etooth SIG Coexistence Working Group Coordination,Would like to work with the IEEE on how best to work together and avoid duplication of efforts. MAC layer simulations Comparison of live and simulation results Steve Shellhammer and Tod Sizer are currently acting as liaisons between the two groups.,J
7、anuary, 2001,Tod Sizer, Lucent Technologies / Bell Laboratories,Slide 5,Live Testing,Started to perform quantitative studies of Coexistence of Bluetooth with other interferers. Emphasis is on quantitative packet error rate performance in specific interference scenarios. Bluetooth v.s. Bluetooth Blue
8、tooth v.s. 802.11b Bluetooth v.s. 2.4 GHz DECT Cordless Phones,January, 2001,Tod Sizer, Lucent Technologies / Bell Laboratories,Slide 6,Live Testing,Because of some limitations in the equipment to this point several of the experiments could not be completed. Hope to report the complete results at th
9、e next IEEE meeting. Additional interferers to test are: HomeRF Microwave Ovens Other 2.4 GHz Cordless products. Suggestions as to interferers we should address beyond these?,January, 2001,Tod Sizer, Lucent Technologies / Bell Laboratories,Slide 7,Finalizing Simulations,Packet Error Rate simulations
10、 have been performed for: Bluetooth 802.11b HomeRF WBFH DECT (in progress) Microwave Ovens (in progress) Results were presented at the Tampa meeting. Now looking to compare these simulations with live testing and develop White Paper to aid deployment of Bluetooth.,January, 2001,Tod Sizer, Lucent Tec
11、hnologies / Bell Laboratories,Slide 8,Adaptive Hopping to Avoid Interference,When no interference is detected, hop over the entire frequency band. When interference is detected at a level which will cause packet errors to Bluetooth, actively avoid these frequency hop locations. This technique is cur
12、rently legal for Type 3 Bluetooth units.,January, 2001,Tod Sizer, Lucent Technologies / Bell Laboratories,Slide 9,Adaptive Hopping to Avoid Interference,The use of intelligence to avoid interference is legal at all powers, however, the required number of hop locations must be maintained. The Coexist
13、ence Working Group feels that adaptive hopping shows great promise in improving the performance of Bluetooth as a Coexistence Mechanism.,January, 2001,Tod Sizer, Lucent Technologies / Bell Laboratories,Slide 10,Adaptive Hopping,Continuing to have discussions on defining the details surrounding Adaptive Hopping. Apprised the FCC as to our thoughts on this issue. Obtained FCC support to continue to work towards consensus on this issue. Would welcome any thoughts and suggestions on this issue from the IEEE 802.15.2 group.,
