IEEE P Working Group for Wireless Personal Area Networks (WPANs)

Slides:



Advertisements
Similar presentations
<month year> doc.: IEEE /271r0 September, 2000
Advertisements

doc.: IEEE <doc#>
Submission Title: [Add name of submission]
<month year> <doc.: IEEE doc> May 2015
doc.: IEEE <doc#>
June 2006 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Proposed Scenarios for Usage Model Document.
IEEE P Working Group for Wireless Personal Area Networks (WPANs)
doc.: IEEE <doc#>
IEEE P Working Group for Wireless Personal Area Networks (WPANs)
May 2001 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Adaptive Frequency Hopping Ad-hoc group update.
Submission Title: [WG-Treasurer’s Report July04]
doc.: IEEE <doc#>
doc.: IEEE <doc#>
March 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Toumaz response to TG6 Call for Applications]
<May,2009> doc.: IEEE <doc .....> <July 2009>
doc.: IEEE <doc#>
January 2007 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [TG3c Technical Requirement sub-group report]
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Resolution of CID 139] Date Submitted:
doc.: IEEE <doc#>
<month year> doc.: IEEE <xyz> January 2001
doc.: IEEE <doc#>
doc.: IEEE <doc#>
doc.: IEEE <doc#>
<month year> <doc.: IEEE doc> March 2015
<month year> doc.: IEEE < e>
July 2005 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [TG3c rate-range requirements: looking forward]
<month year> <doc.: IEEE doc> December 2015
<month year> <doc.: IEEE doc> March 2015
doc.: IEEE <doc#>
<month year> doc.: IEEE <xyz> November 2000
<month year> <doc.: IEEE doc> November 2015
doc.: IEEE <doc#>
doc.: IEEE /XXXr0 Sep 19, 2007 June 2009
Submission Title: [Frame and packet structure in ]
November 2006 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Simplified geometry for the usage model.
<month year> <doc.: IEEE doc> May 2015
<month year> <doc.: IEEE doc> May 2015
<month year>20 Jan 2006
<month year> doc.: IEEE <030158r0> January 2004
doc.: IEEE <doc#>
平成31年4月 doc.: IEEE /424r1 July 2008 doc.: IEEE c
doc.: IEEE <doc#>
Submission Title: [Preamble structures for 4a]
September 2000 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: TG3 Rank Order Voting Process Description.
<month year> <doc.: IEEE doc> December 2015
<month year> <doc.: IEEE doc> January 2016
<month year> <doc.: IEEE doc> March 2015
May 2018 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: z Comments on ax Coexistence Assurance.
doc.: IEEE <doc#>
doc.: IEEE <doc#1>
<month year> <doc.: IEEE doc> March 2015
January 2001 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Coexistence with (Bluetooth)
doc.: IEEE <doc#>
doc.: IEEE <doc#>
<month year> <doc.: IEEE doc> July 2015
<month year> doc.: IEEE <030158r0> <March 2003>
January 2000 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Study Group Summary and Motion for .15WG.
September 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Suggested TG3c PAR Changes] Date Submitted:
September 2009doc.: IEEE wng0
doc.: IEEE <doc#>
Mar 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Resolution for Comment 70 ] Date Submitted:
Mar 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Resolution for Comment 70 ] Date Submitted:
<month year> <doc.: IEEE doc> September 2015
January 2019 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Channel bandwidth observations] Date Submitted:
<month year> <doc.: IEEE doc> March 2015
Jan 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Call for THz Contributions Date Submitted: January.
July 2003 doc.: IEEE <03/242> July 2003
Submission Title: TG9ma Agenda for September Meeting
doc.: IEEE <doc#3>
Jan 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: TeraHertz Closing Report Date Submitted: January.
Presentation transcript:

IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) January 2001 IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Miscellaneous Coexistence Ideas Date Submitted: January 16, 2001 Source: Steve Shellhammer Company: Symbol Technology, Inc. Address: One Symbol Plaza, Holtsville NY 11742 Voice: (631) 738-4302, FAX: (631) 738-4618, E-Mail: shell@symbol.com Re: Submission of a Coexistence Mechanism in response to IEEE 802.15-00/009r4 Abstract: This is a submission to P802.15.2 of miscellaneous coexistence mechanism ideas Purpose: To present ideas to IEEE 802.15.2 to be considered as part of the Recommended Practice. Notice: This document has been prepared to assist the IEEE P802.15. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. Release: The contributor acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by P802.15. Steve Shellhammer, Symbol Technologies

IEEE P802.15 Working Group for Wireless Personal Area NetworksTM <month year> doc.: IEEE 802.15-<doc#> January 2001 IEEE P802.15 Working Group for Wireless Personal Area NetworksTM Miscellaneous Coexistence Ideas Steve Shellhammer, Symbol Technologies <author>, <company>

Purpose of This Submission January 2001 Purpose of This Submission This submission is not a standalone Coexistence Mechanism These are a combination of ideas that may be useful in combination with a coexistence mechanism It is not my intent for this submission to be voted on. TG2 can select any of these ideas to supplement a Coexistence Mechanism Steve Shellhammer, Symbol Technologies

Preferred 802.11b Data Rate There are four data rates in 802.11b January 2001 Preferred 802.11b Data Rate There are four data rates in 802.11b 1, 2, 5.5 and 11 Mbps The higher the data rate the lower processing gain This implies lower data rate is better The higher the data rate the shorter the duration of the packet This implies higher data rate is better Steve Shellhammer, Symbol Technologies

Preferred 802.11b Data Rate These two observations are in opposition January 2001 Preferred 802.11b Data Rate These two observations are in opposition It has been observed that the benefits of having shorter packets more than offsets the decrease in processing gain, by going to higher rates IT IS BEST TO USE THE HIGHEST DATA RATE IN 802.11B Steve Shellhammer, Symbol Technologies

January 2001 Data Rate Scaling in 802.11b IEEE 802.11b allows for automatic data rate scaling How data rate scaling is implemented is not specified in the IEEE Standard The intent of automatic data rate scaling is to increase the range of the network at the expense of data rate Detect edge-of-range and then rate scale Steve Shellhammer, Symbol Technologies

January 2001 Data Rate Scaling in 802.11b Since the rate scaling algorithm is not in the standard we cannot make too broad a statement about the effect of interference It is possible for Bluetooth interference to fool the rate scaling algorithm to believe it needs to decrease the data rate. Steve Shellhammer, Symbol Technologies

January 2001 Data Rate Scaling in 802.11b If Bluetooth interference causes the rate scaling algorithm to decrease the 802.11b data rate. Since decreasing the data rate increases the effect of interference, we have Positive Feedback, resulting in a quick drop to 1 Mbps. Steve Shellhammer, Symbol Technologies

January 2001 Data Rate Scaling in 802.11b IF THE DATA RATE SCALING ALGORITHM IS FOOLED BY BLUETOOTH INTERFERENCE THEN DISABLE IT AND FIX THE DATA RATE AS HIGH AS POSSIBLE Steve Shellhammer, Symbol Technologies

January 2001 Bluetooth SCO Link The Bluetooth SCO Link is a periodic transmission every six Bluetooth slots 2 out of 6 slots used (No FEC) 4 out of 6 slots used (2/3-rate FEC) 6 out of 6 slots used (1/3-rate FEC) The SCO packets do not include a CRC and retransmission is not included. Steve Shellhammer, Symbol Technologies

January 2001 Bluetooth SCO Link The SCO Link, as an interferer, represents periodic interference with a short period (3.75 ms). If the Bluetooth power level at the 802.11 receiver is too high, then this periodic interferer is potentially a worse interferer than an ACL Link. Steve Shellhammer, Symbol Technologies

January 2001 Bluetooth SCO Link The SCO Link is more susceptible to 802.11 interference than an ACL Link Under interference it is more likely to cause full packet errors, not a few bit errors The FEC does very little to mitigate the effect of interference The SCO link does not support Packet Retransmission, which is what is needed in an interference environment Steve Shellhammer, Symbol Technologies

Bluetooth SCO Link THE SCO LINK IS WEAK IN AN INTERFERENCE ENVIRONMENT January 2001 Bluetooth SCO Link THE SCO LINK IS WEAK IN AN INTERFERENCE ENVIRONMENT RECOMMENDATION: ELIMINATE 1/2-RATE AND 1/3-RATE FEC REPLACE IT WITH A NEW SCO LINK WITH UP TO TWO RETRANSMISSIONS NEED TO ADD CRC TO SCO Steve Shellhammer, Symbol Technologies

Look-Ahead CCA in Bluetooth January 2001 Look-Ahead CCA in Bluetooth Currently Bluetooth does not include Clear Channel Assessment To make CCA useful in Bluetooth it would need to detect other wireless systems, not just Bluetooth devices Use Receive Signal Strength Indicator to detect other wireless systems Steve Shellhammer, Symbol Technologies

Look-Ahead CCA in Bluetooth January 2001 Look-Ahead CCA in Bluetooth Since for ACL Link the Slaves can only transmit if the Master sent a packet in the previous slot For ACL link you could add CCA only to the Master and have it check the current and next frequency. Look ahead one frequency. Steve Shellhammer, Symbol Technologies

Look-Ahead CCA in Bluetooth January 2001 Look-Ahead CCA in Bluetooth Bluetooth allocates about 220 s for the frequency synthesizer to tune to the next frequency. This is quite long and it is possible to design a synthesizer that tunes to a different frequency faster at a reasonable cost. So look ahead to the next frequency and check for a clear channel. Steve Shellhammer, Symbol Technologies

Look-Ahead CCA in Bluetooth January 2001 Look-Ahead CCA in Bluetooth Tune to fn Transmission Time BT 220 ms 405 ms BT with CCA Tune to fn+1 CCA Tune to fn 80 ms 60 ms 80 ms Steve Shellhammer, Symbol Technologies

January 2001 Summary Presented several observations about Bluetooth and 802.11 Coexistence Impact of 802.11b Data Rates Impact of 802.11b Rate Scaling Algorithm Weakness of the Bluetooth SCO Link Look-ahead CCA in Bluetooth Steve Shellhammer, Symbol Technologies