Presentation is loading. Please wait.

Presentation is loading. Please wait.

Doc.: IEEE 802.11-02/462r0 Submission July 2002 Bill McFarland, Atheros CommunicationsSlide 1 Backwards/Forwards Compatibility for 11h There will exist.

Published byClinton Barton Modified over 7 years ago

Similar presentations

Presentation on theme: "Doc.: IEEE 802.11-02/462r0 Submission July 2002 Bill McFarland, Atheros CommunicationsSlide 1 Backwards/Forwards Compatibility for 11h There will exist."— Presentation transcript:

1 doc.: IEEE 802.11-02/462r0 Submission July 2002 Bill McFarland, Atheros CommunicationsSlide 1 Backwards/Forwards Compatibility for 11h There will exist many legacy APs and STAs that do not implement 11h in domains that do not require DFS/TPC There will be some legacy APs and STAs that do not implement 11h, but operate in domains that require DFS/TPC (interim rules or non-11h DFS/TPC) Some users will want to enable 11h in domains that do not require DFS/TPC Need to consider all possible combinations of legacy and 11h devices

2 doc.: IEEE 802.11-02/462r0 Submission July 2002 Bill McFarland, Atheros CommunicationsSlide 2 Observation Currently, there is no way to distinguish a STA that does not have 11h capability from a STA that has 11h but has the MIB variable dot11SpectrumManagementRequired set to false However, it appears that in all cases the appropriate behavior is the same, so there is no need to make the distinction In addition, by requiring STAs that have 11h capability to turn it on before associating with a 11h enabled (I)BSS, an AP with 11h enabled can know that any STA associating with 11h disabled is a legacy device

3 doc.: IEEE 802.11-02/462r0 Submission July 2002 Bill McFarland, Atheros CommunicationsSlide 3 Complicated Cases In the upcoming table, an 11h capable STA disables 11h operation in order to associate with a BSS or IBSS with 11h disabled if “conditions are met” The conditions are intended to insure that a STA will not violate regulations

4 doc.: IEEE 802.11-02/462r0 Submission July 2002 Bill McFarland, Atheros CommunicationsSlide 4 “Conditions” An STA may disable 11h operation in order to associate with a (I)BSS that has 11h disabled if either of the following are met The STA can determine that it is in a regulatory domain that does not require DFS/TPC. Potential methods include: –The AP transmits an 11d country code –The user confirms location of the STA –The STA includes configuration information that establishes its legal region of operation The STA can insure that it will meet regulations even if 11h is not employed. Potential methods include: –Operating at a transmit power below the regulatory limit, including any mitigation factors –Independently detecting radars and ceasing operation on channels that contain radar signals

5 doc.: IEEE 802.11-02/462r0 Submission July 2002 Bill McFarland, Atheros CommunicationsSlide 5 Desired Behavior

6 doc.: IEEE 802.11-02/462r0 Submission July 2002 Bill McFarland, Atheros CommunicationsSlide 6 Proposed Change to Wording in Draft Change TPC procedures (11.5 draft 2.0) from: For the purposes of TPC, a STA with the boolean MIB attribute dot11SpectrumManagementRequired set equal to true shall not operate in a BSS or IBSS unless the Spectrum Management bit is set equal to 1 in the Capability Information field in Beacons and Probe Responses received from the BSS or IBSS. Similarly, an AP with the boolean MIB attribute dot11SpectrumManagementEnabled set equal to true shall not associate or reassociate a STA unless the Spectrum Management bit is set equal to 1 in the Capability Information field in Association and Reassociation Requests received from the STA To: For the purposes of TPC, a STA with the boolean MIB attribute dot11SpectrumManagementRequired set equal to true shall not operate in a BSS or an IBSS unless the Spectrum Management bit is set equal to 1 in the Capability Information field in Beacons and Probe Responses received from the BSS or IBSS unless the STA can determine that it is in a regulatory domain that does not require spectrum management, or can ensure that it will meet regulatory requirements even if spectrum management is not employed. Potential methods for determining the regulatory domain include receiving a country indication in the beacon, user confirmation, or configuration information within the device. Potential methods to ensure regulations are met even if spectrum management is not employed include using a transmit power that is below the legal maximum including any mitigation factor. Continued …

7 doc.: IEEE 802.11-02/462r0 Submission July 2002 Bill McFarland, Atheros CommunicationsSlide 7 Changes to Draft (Continued) For the purposes of TPC, a STA with the boolean MIB attribute dot11SpectrumManagementRequired set equal to false shall enable spectrum management before associating with a BSS or IBSS in which the Spectrum Management bit is set equal to 1 in the Capability Information field in Beacons and Probe Responses received from the BSS or IBSS Change TPC procedures (11.5 draft 2.0) from: Similarly, an AP with the boolean MIB attribute dot11SpectrumManagementEnabled set equal to true shall not associate or reassociate a STA unless the Spectrum Management bit is set equal to 1 in the Capability Information field in Association and Reassociation Requests received from the STA To: Because of the existence of legacy devices that do not support spectrum management but do meet regulatory requirements, APs may allow association of devices that do not have the Spectrum Management bit set equal to 1 in the Capability Information field in Association and Reassociation Requests received from the STA.

8 doc.: IEEE 802.11-02/462r0 Submission July 2002 Bill McFarland, Atheros CommunicationsSlide 8 Proposed Change to Wording in Draft Change DFS procedures (11.6 draft 2.0) from: For the purposes of DFS, a STA with the boolean MIB attribute dot11SpectrumManagementRequired set equal to true shall not operate in a BSS or IBSS unless the Spectrum Management bit is set equal to 1 in the Capability Information field in Beacons and Probe Responses received from the BSS or IBSS. Similarly, an AP with the boolean MIB attribute dot11SpectrumManagementEnabled set equal to true shall not associate or reassociate a STA unless the Spectrum Management bit is set equal to 1 in the Capability Information field in Association and Reassociation Requests received from the STA To: For the purposes of DFS, a STA with the boolean MIB attribute dot11SpectrumManagementRequired set equal to true shall not operate in a BSS or an IBSS unless the Spectrum Management bit is set equal to 1 in the Capability Information field in Beacons and Probe Responses received from the BSS or IBSS unless the STA can determine that it is in a regulatory domain that does not require spectrum management, or can ensure that it will meet regulatory requirements even if spectrum management is not employed. Potential methods for determining the regulatory domain include receiving a country indication in the beacon, user confirmation, or configuration information within the device. Potential methods to ensure regulations are met even if spectrum management is not employed include independently detecting radar and ceasing operation on channels on which radar is detected. Continued …

9 doc.: IEEE 802.11-02/462r0 Submission July 2002 Bill McFarland, Atheros CommunicationsSlide 9 Changes to Draft (Continued) For the purposes of TPC, a STA with the boolean MIB attribute dot11SpectrumManagementRequired set equal to false shall enable spectrum management before associating with BSS or IBSS in which the Spectrum Management bit is set equal to 1 in the Capability Information field in Beacons and Probe Responses received from the BSS or IBSS Change DFS procedures (11.6 draft 2.0) from: Similarly, an AP with the boolean MIB attribute dot11SpectrumManagementEnabled set equal to true shall not associate or reassociate a STA unless the Spectrum Management bit is set equal to 1 in the Capability Information field in Association and Reassociation Requests received from the STA To: Because of the existence of legacy devices that do not support spectrum management but do meet regulatory requirements, APs may allow association of devices that do not have the Spectrum Management bit set equal to 1 in the Capability Information field in Association and Reassociation Requests received from the STA.

Download ppt "Doc.: IEEE 802.11-02/462r0 Submission July 2002 Bill McFarland, Atheros CommunicationsSlide 1 Backwards/Forwards Compatibility for 11h There will exist."

Similar presentations

Doc.: 11-03-0573r0-I Submission July 22, 2003 Paul Lambert, Airgo NetworksSlide 1 Enabling Encryption in Hotspots by Decoupling the Privacy Field from.

Doc.: r0-I Submission July 22, 2003 Paul Lambert, Airgo NetworksSlide 1 Enabling Encryption in Hotspots by Decoupling the Privacy Field from.
Doc.: IEEE 802.11-10/0528r0 Submission March 2010 Slide 1 Slot Time Synchronization for Coexistence of 5 MHz, 10 MHz and 20 MHz Systems Date: 2010-05-11.

Doc.: IEEE /0528r0 Submission March 2010 Slide 1 Slot Time Synchronization for Coexistence of 5 MHz, 10 MHz and 20 MHz Systems Date:
Doc.: IEEE 802.11-08/1468r0 Submission Dec 2008 Ashish Shukla, Marvell SemiconductorSlide 1 ERP Protection in IEEE 802.11s Mesh Network Date: 2008-12-12.

Doc.: IEEE /1468r0 Submission Dec 2008 Ashish Shukla, Marvell SemiconductorSlide 1 ERP Protection in IEEE s Mesh Network Date:
Submission doc.: IEEE 11-12/0281r0 March 2012 Jarkko Kneckt, NokiaSlide 1 Recommendations for association Date: 2012-03-05 Authors:

Submission doc.: IEEE 11-12/0281r0 March 2012 Jarkko Kneckt, NokiaSlide 1 Recommendations for association Date: Authors:
Doc.: IEEE 802.11-10/0256r0 Submission March 2010 Zhou Lan NICTSlide 1 Proposal of Synchronized Quiet Period for Incumbent User Detection Date: 2010-March.

Doc.: IEEE /0256r0 Submission March 2010 Zhou Lan NICTSlide 1 Proposal of Synchronized Quiet Period for Incumbent User Detection Date: 2010-March.
Doc.: IEEE 802.11-08/1101r3 Submission September 2008 John R. Barr, Motorola, Inc.Slide 1 Additional 40 MHz Scanning Proposal Date: 2008-09-09 Authors:

Doc.: IEEE /1101r3 Submission September 2008 John R. Barr, Motorola, Inc.Slide 1 Additional 40 MHz Scanning Proposal Date: Authors:
Doc: IEEE 802.11 - 99/257 Submission November 1999 PAGE 1 CHRIS ZEGELIN, Symbol Technologies Inc. INTERNATIONAL ROAMING A SIMPLE APPROACH FOR WORLD WIDE.

Doc: IEEE /257 Submission November 1999 PAGE 1 CHRIS ZEGELIN, Symbol Technologies Inc. INTERNATIONAL ROAMING A SIMPLE APPROACH FOR WORLD WIDE.
Doc.: IEEE 802.11-07/2215r4 Submission August 2007 Ganesh Venkatesan, Intel CorporationSlide 1 Proposal –Radio Resource Measurement Capability Enabled.

Doc.: IEEE /2215r4 Submission August 2007 Ganesh Venkatesan, Intel CorporationSlide 1 Proposal –Radio Resource Measurement Capability Enabled.
Doc.: IEEE 802.11-07/2215r1 Submission July 2007 Ganesh Venkatesan, Intel CorporationSlide 1 Proposal – Supported Radio Resource Measurement Bitmask IE.

Doc.: IEEE /2215r1 Submission July 2007 Ganesh Venkatesan, Intel CorporationSlide 1 Proposal – Supported Radio Resource Measurement Bitmask IE.
Doc.: IEEE 802.11-00/270 Submission September 2000 McFarland, Chesson, Atheros CommunicationsSlide 1 DFS/TPC Proposal Greg Chesson, Bill.

Doc.: IEEE /270 Submission September 2000 McFarland, Chesson, Atheros CommunicationsSlide 1 DFS/TPC Proposal Greg Chesson, Bill.
Doc.: IEEE 802.11-02/392r0 Submission June 2002 Mike Moreton, Synad Technologies Ltd.Slide 1 IBSS TPC Issues Mike Moreton, Synad Technologies, Ltd.

Doc.: IEEE /392r0 Submission June 2002 Mike Moreton, Synad Technologies Ltd.Slide 1 IBSS TPC Issues Mike Moreton, Synad Technologies, Ltd.
Doc.:IEEE 802.11-11/1385r0 Submission Sep. 2011 Brian Hart, Cisco SystemsSlide 1 Making the Quiet Channel Element Work for 11a/11n Clients Date: 2011-09-30.

Doc.:IEEE /1385r0 Submission Sep Brian Hart, Cisco SystemsSlide 1 Making the Quiet Channel Element Work for 11a/11n Clients Date:
Doc.: IEEE 802.11-02/759r0 Submission November 2002 Bruce Kraemer, Intersil TK Tan, PhilipsSlide 1 Proposal to Amend 802.11a to address Japanese bands.

Doc.: IEEE /759r0 Submission November 2002 Bruce Kraemer, Intersil TK Tan, PhilipsSlide 1 Proposal to Amend a to address Japanese bands.
Doc.: IEEE 802.11-08/1468r1 Submission Jan 09 Ashish Shukla, Marvell SemiconductorSlide 1 ERP Protection in IEEE 802.11s Mesh Network Date: 2009-01-14.

Doc.: IEEE /1468r1 Submission Jan 09 Ashish Shukla, Marvell SemiconductorSlide 1 ERP Protection in IEEE s Mesh Network Date:
SubmissionJoe Kwak, InterDigital1 PHY measurements for interference reduction from 11h Joe Kwak, Marian Rudolf InterDigital doc: IEEE 802.11-03/537r0July.

SubmissionJoe Kwak, InterDigital1 PHY measurements for interference reduction from 11h Joe Kwak, Marian Rudolf InterDigital doc: IEEE /537r0July.
Submission doc.: IEEE 11-14/0977r3 August 2014 Donald Eastlake, HuaweiSlide 1 EPD, Mixed BSSes, and Group RAs Date: 2014-08-25 Authors:

Submission doc.: IEEE 11-14/0977r3 August 2014 Donald Eastlake, HuaweiSlide 1 EPD, Mixed BSSes, and Group RAs Date: Authors:
Doc.: IEEE 802.11-03/782r0 September 2003 Peter Ecclesine, Cisco SystemsSlide 1 802-11 Network Neighbors Peter Ecclesine, Cisco Systems.

Doc.: IEEE /782r0 September 2003 Peter Ecclesine, Cisco SystemsSlide Network Neighbors Peter Ecclesine, Cisco Systems.
Doc.: IEEE 802.11-08/1101r0 Submission September 2008 John R. Barr, Motorola, Inc.Slide 1 Additional 40 MHz Scanning Proposal Date: 2008-09-09 Authors:

Doc.: IEEE /1101r0 Submission September 2008 John R. Barr, Motorola, Inc.Slide 1 Additional 40 MHz Scanning Proposal Date: Authors:
Doc.: IEEE 802.11-13/1291r0 SubmissionSlide 1 Date: 2013-10-31 Presenter: Dynamic Bandwidth Control for 802.11aj (60GHz New Technique Proposal) KB Png.

Doc.: IEEE /1291r0 SubmissionSlide 1 Date: Presenter: Dynamic Bandwidth Control for aj (60GHz New Technique Proposal) KB Png.
FILS Reduced Neighbor Report

FILS Reduced Neighbor Report

Similar presentations

Ads by Google