CID#102 - Channel Allocation Month Year Month Year doc.: IEEE 802.11-yy/xxxxr0 doc.: IEEE 802.11-yy/xxxxr0 January 2008 CID#102 - Channel Allocation Authors: Date: 2008-01-14 Slide 1 Emily Qi (Intel Corp) et al Page 1 Emily Qi John Doe, Some Company

Month Year Month Year doc.: IEEE 802.11-yy/xxxxr0 doc.: IEEE 802.11-yy/xxxxr0 January 2008 Abstract This document provides an outline for channel allocation normative text proposal (08/0048r1) in support of the channel/frequency allocation for non-802.11-infrastructure networking (IBSS, Mesh, Bluetooth, etc...) or other uses. This presentation provides comment resolution for LB108 CID #102. Slide 2 Emily Qi (Intel Corp) et al Page 2 Emily Qi John Doe, Some Company

Agenda Motivation Proposed Solution Protocol Details January 2008 Agenda Motivation Proposed Solution Protocol Details Review the normative text, see 08/0048r1 Slide 3 Emily Qi (Intel Corp) et al

January 2008 Motivation In general, a non-802.11-infrastructure network (e.g. IBSS, one-hop Mesh, or Bluetooth) can co-exist with an infrastructure network The channel/frequency number that is selected by a non-802.11-infrastructure network is critical to the overall WiFi network performance Guidance from the infrastructure on channel/frequency allocation for non-802.11-infrastructure network can facilitate better network coexistence and improve overall network performance: Coordinated channel planning Reduce radio interference Balance traffic load Slide 4 Emily Qi (Intel Corp) et al

Usage Scenario: IBSS or one-hop Mesh January 2008 Usage Scenario: IBSS or one-hop Mesh Without the guidance from infrastructure, a non-AP STA may choose a non-ideal channel to start an IBSS or a mesh network Operation of the IBSS or the mesh network can interfere with the operation of infrastructure network Wired Infrastructure Channel 1 AP BSS = Basic Service Set Channel 11 AP STA STA STA STA STA STA STA IBSS or Mesh STA STA Emily Qi (Intel Corp) et al

Usage scenario: Bluetooth January 2008 Usage scenario: Bluetooth Before Channel 1 AP Problem: BT can interfere with 802.11 channels in use With guidance from the infrastructure it is possible to instruct the STA to use “safer” frequencies for use by BT. BT Frequency 802.11 BT Headset Dual Mode STA Channel/Frequency Separation After Channel 1 AP BT Frequency 802.11 BT Headset Dual Mode STA Emily Qi (Intel Corp) et al

Proposed Solution Introducing Channel Allocation IE January 2008 Proposed Solution Introducing Channel Allocation IE Provide recommended channel/frequency lists for different use cases Allow flexibility for multiple applications and extensibility for future use cases Non-AP STA can request channel allocation information with or without having to associate to the infrastructure network Upon the receipt of the Channel Allocation information, Non-AP STA should operate the corresponding network at the recommended channel/frequency lists. AP provides Channel Allocation information to the STA The AP provides a frequency list that either IT recommended or the network infrastructure examined based on the interference level, traffic load or supported regulatory classes. Slide 7 Emily Qi (Intel Corp) et al

Channel Allocation: Request and Response January 2008 Channel Allocation: Request and Response Define a capability bit in the Extended Capability IE: Channel Allocation Non-AP STA or AP can request or respond Channel Allocation information via Probe Request and Response frames Allow unassociated STA to request Channel Allocation information before initiating a non-802.11-infrasture network Non-AP STA or AP can request or respond Channel Allocation information via the Channel Allocation Request and Response frames – Public Action frame Allow associated STA to request Channel Allocation information in a protected manner Allow AP to update Channel Allocation information for both associated and unassociated STAs Slide 8 Emily Qi (Intel Corp) et al

Channel Allocation information Month Year doc.: IEEE 802.11-yy/xxxxr0 January 2008 Channel Allocation information Channel Allocation IE format : Element ID Length One or more Sub-elements Octets: 1 Variable Channel Allocation sub-element types and usages Sub-element ID Sub-element Type (Usages) 802.11 Non-infrastructure 1 Bluetooth 2 Zigbee 3 CSS 254 Unspecified Network 4-253, 255 Reserved One or more sub-elements to indicate channel/frequency numbers allocated for the corresponding use cases specified in the Sub-element ID field Sub-element ID is the only field included in the sub-element if the Channel Allocation IE is included in the request frames. Additional sub-element can be defined when more use cases are discovered Emily Qi (Intel Corp) et al Emily Qi

Examples of Channel Allocation Sub-elements Month Year doc.: IEEE 802.11-yy/xxxxr0 January 2008 Examples of Channel Allocation Sub-elements 802.11 Non-infrastructure Sub-element: Sub-element ID (0) Length (2n) <Regulatory class, Channel number> duplet List Octets: 1 2*n Bluetooth Sub-element: Sub-element ID (1) Length (2n) <Lower hopping Freq#, Upper hopping Freq# > duplet List Octets: 1 2*n Zigbee Sub-element: Sub-element ID (2) Length (n) Channel List Octets: 1 n Emily Qi (Intel Corp) et al Emily Qi

Channel Allocation Request/Response frames Month Year doc.: IEEE 802.11-yy/xxxxr0 January 2008 Channel Allocation Request/Response frames Channel Allocation Request: Category Action Dialog Token Request Reason Channel Allocation Element Supported Regulatory Element Octets: 1 variable Channel Allocation Response: Category Action Dialog Token Channel Allocation Element Octets: 1 variable AP can send a Channel Response frame in response to the Channel Allocation Request frame , or AP can also send an unsolicited Channel Allocation Response when AP needs to update Channel Allocation Information Emily Qi (Intel Corp) et al Slide 11 Emily Qi

Thank You! and Questions? Month Year doc.: IEEE 802.11-yy/xxxxr0 January 2008 Thank You! and Questions? Slide 12 Emily Qi (Intel Corp) et al Emily Qi