1 / 9

Control framework in 802.11v

doc: IEEE 802.11-05/xxx4r0. May 2005. Control framework in 802.11v. Joe Kwak, Marian Rudolf (InterDigital). Table of Contents. Motivation and proposed guiding principles for control framework with 802.11v Examples Dynamic Channel Selection Network-controlled Load Balancing

dardena
Download Presentation

Control framework in 802.11v

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. doc: IEEE 802.11-05/xxx4r0 May 2005 Control framework in 802.11v Joe Kwak, Marian Rudolf (InterDigital) Kwak, Rudolf

  2. Table of Contents • Motivation and proposed guiding principles for control framework with 802.11v • Examples • Dynamic Channel Selection • Network-controlled Load Balancing • Deferral management (e.g. Power/EDT control) • Management interfaces Kwak, Rudolf

  3. Motivation and guiding principles • The various Radio Resource Management functions that are proposed for 802.11v require signaling • Proposed guiding principles for defining 802.11v signaling • Aim at reusing the framework defined in earlier amendments • What was done in 802.11h TPC/DFS would be of particular interest to us here • Consider what is being done in current amendments (802.11r and 802.11k) • Make it simple and easy to implement • The following proposes examples using three fundamental radio resource management functionalities • Seamless channel switching (e.g. dynamic channel selection) • Network-controlled load balancing • Deferral management (e.g. Power/EDT control) Kwak, Rudolf

  4. Element ID Length Channel switch mode New channel number Channel switch count Element ID Length Channel switch mode New channel number Channel switch count Transaction ID Measurements Reason Example: Seamless channel switching • 802.11h already tackled this problem: DFS • “Channel Switch Announcement” IE can be attached to the Beacon or Probe response frame or sent in a dedicated action frame • Modified channel switch intention element format • Add a transaction ID to be able to pair with response • Possibility of appending measurements or reason code Kwak, Rudolf

  5. Example: Network-controlled Load Balancing • Load balancing can be split into decision phase and execution phase • Let 802.11v focus on decision and rely on 802.11r for the execution Kwak, Rudolf

  6. Example: Deferral Management • New IE’s and new action frames building on top of what exists in 802.11h and 802.11k with minimal modifications • New Deferral management IE’s • Deferral management capability • Supported CCA modes, Max/Min Tx power, Max/Min EDT • Deferral management reports and requests • CCA mode, EDT, Tx Power operational settings (or range) • Deferral management set command • Single IE could be used for both direct and indirect control modes • New Deferral management action frames • Deferral management request + reports • Deferral management set command Kwak, Rudolf

  7. Summary of what needs to be done • For each functionality, decide which management frames are needed: • Action frames (section 7.4) • Other management frames (section 7.2.3) • Add required new information fields in non-action management frames • Section 7.2.3 • Add new category in the action field for Radio Management • Section 7.3.1.11, Table 19a • Add new action frames (section 7.4.x) • Add new Radio Management Information Elements • Section 7.4.x for IEs strictly used by action frames • Section 7.2.3 for IEs if used by frames other than action frames • For the three examples mentioned before we estimate the need for • ~3-4 new 2-way or partial management action frame exchanges total • ~10 information fields or elements total Kwak, Rudolf

  8. Thoughts on the management interface with 11v… • Primarily, use MIB’s as baseline management interface for AP and STA • MIBs has always been the de-facto standard for IEEE 802 • Admitted, MIB’s have several major shortcomings • Admitted, many people are notoriously unhappy with SNMP… • But there is no clear-cut attractive alternative in sight today (XML ?) • Continue to assume MIB’s as simple baseline working assumption for 11v (too much work to rip apart the concrete now) • But in addition, is a simple MAC/SME management “API” or “SAP” a useful extension we could consider for 11v ? • In this context, look at what is currently proposed by, • 802.1 “Media Independent RF Management of Wireless 802 Networks” • 802.21 “Media Independent Handover” • Choose a selected set of few (3-4) key RF settings and RF performance metrics for setting/reporting through a new MAC/SME API/SAP in APs with 11v • Set Operating channel, Tx power/EDT/CCA, Network name, Disassociate MAC-address#N • Report Link quality, Throughput/Load, Inst. Data rate Kwak, Rudolf

  9. MAC/SME API/SAP • MAC API/SAP could be a quick and easy alternative to MIB’s for simple yet essential RF management tasks in 802.11 WLANs • Nothing needs to be standardized above L2 and for the DS • Removes the need to modify in SME itself, management agents (SNMP etc.) could be external Management Server or Application BLUE: can be proprietary RED: standardized Management Management Management Agent Agent Agent MAC API/SAP MAC API/SAP MAC API/SAP MIB MIB MIB SME SME SME MAC PHY MAC PHY MAC PHY AP3 AP2 AP1 Kwak, Rudolf

More Related