Re: [802.19] comments on the 40MHz 11n/Bluetooth test plan
Title: Re: [802.19] comments on the 40MHz 11n/Bluetooth test plan
The current environment only allows 20 MHz 802.11 channels which can be easily handled by Bluetooth AFH devices. With the introduction of 40 MHz channels from one source, the picture is radically changed. Without protection, a large number of Bluetooth devices will no longer work well when 802.11n systems are deployed (future). Bluetooth specifications may get better, but there are still billions of existing Bluetooth devices out there that will be impacted. As more 802.11n systems are deployed and data rates increase because they can, even more interference results.
Simple corollary: Why is the 802.11n task group including detection of legacy 802.11 devices that don’t understand 802.11n beacons when determining when to allow 40 MHz operation, but doing nothing to detect existing Bluetooth devices?
Due to the large number of Bluetooth devices deployed, I would expect a good Bluetooth detection mechanism in 802.11n devices to have a positive indication most of the time. 40MHzIntollerant bit would be set most of the time making 40 MHz in 2.4 GHz a useless feature. The current 802.11n plan is to avoid current 802.11 systems until they are all replaced with 802.11n systems and then start using 40MHz channels at will regardless of whether they interfere with other 2.4 GHz users like Bluetooth. Just trying to create a fair environment for sharing of 2.4 GHz spectrum.
John
On 8/18/08 1:57 PM, "Craig Warren" <cwarren@xxxxxxxxxxxx> wrote:
I am getting confused because the discussions in the meetings we have been having all are doing speculation about future .11n scenarios. John are we divorcing the solution aspects developed by Bluetooth for some of these reasons, if so it seems rather one sided.
CW
From: John Barr [mailto:john.barr@xxxxxxxxxxxx]
Sent: Monday, August 18, 2008 11:51 AM
To: Craig Warren; STDS-802-19@xxxxxxxxxxxxxxxxx
Subject: Re: [802.19] comments on the 40MHz 11n/Bluetooth test plan
It is what is in the market now. Future versions may be better, but all of the legacy devices need to be considered as well. John
On 8/18/08 1:30 PM, "Craig Warren" <cwarren@xxxxxxxxxxxx> wrote:
The test plan looks like a great start. One thing I really want to make a point of ( I did not want to distract the current conversation at the end of the telecom) is that the headset depicted for SCO and A2DP combo is a MOT S9. This headset is a 2.0 I think that we should ensure that all testing be done with 2.0 BDR or 2.1 EDR/BDR headset versions. 2.1 will naturally be much better due to the much higher packet types used but older 1.1 A2DP headsets are available and should not be used. EDR 2.1 headsets are gaining market availability and this will greatly improve the performance of coexistence should testing be done with both Bluetooth versions?
Craig Warren
From: Shellhammer, Steve [mailto:sshellha@xxxxxxxxxxxx]
Sent: Monday, August 18, 2008 8:04 AM
To: STDS-802-19@xxxxxxxxxxxxxxxxx
Subject: [802.19] 40MHz 11n/Bluetooth Conference Call
All,
This is a reminder that we will be having a conference call Today at 1 PM EDT (10 AM PDT).
John Barr has uploaded his presentation, document 802.11-08/984r0.
Agenda
- Attendance
- Check to see if anyone is not familiar with the IEEE patent policy
-
- Presentation on 40 MHz 11n / Bluetooth Test Plan (John Barr)
- Updates from Last Week (Bruce Kraemer)
- New business
TO ATTEND THE AUDIO CONFERENCE:
1. Call +1 858-845-5000
2. After the greeting press 1 to attend meeting.
3. Enter Meeting ID 80219
4. Enter Meeting Password 80219 followed by the # sign.
5. Follow the remaining prompts for recording the callers name and joining the meeting.
For assistance, dial #0 at any time.
TAG conference call schedules are posted at http://ieee802.org/19/pub/calls.html.
Regards,
Steve
--
John R. Barr (John.Barr@xxxxxxxxxxxx)
Director, Standards Realization - <http://www.motorola.com>
Vice Chairman of the Board, Bluetooth SIG - <http://www.bluetooth.org>
(847) 576-8706 (office) +1-847-962-5407 (mobile) (847) 576-6758 (FAX)