SubmissionKwak, Rudolf1 Control framework in v Joe Kwak, Marian Rudolf (InterDigital) doc: IEEE /xxx4r0 May 2005

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

doc: IEEE /xxx4r0May 2005 Submission Kwak, Rudolf 3 Motivation and guiding principles The various Radio Resource Management functions that are proposed for v require signaling Proposed guiding principles for defining v signaling Aim at reusing the framework defined in earlier amendments What was done in h TPC/DFS would be of particular interest to us here Consider what is being done in current amendments (802.11r and k) 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)

doc: IEEE /xxx4r0May 2005 Submission Kwak, Rudolf h 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 Example: Seamless channel switching Element IDLengthChannel switch mode New channel number Channel switch count Element IDLengthChannel switch mode New channel number Channel switch count Transaction ID MeasurementsReason

doc: IEEE /xxx4r0May 2005 Submission Kwak, Rudolf 5 Example: Network-controlled Load Balancing Load balancing can be split into decision phase and execution phase Let v focus on decision and rely on r for the execution

doc: IEEE /xxx4r0May 2005 Submission Kwak, Rudolf 6 Example: Deferral Management New IE’s and new action frames building on top of what exists in h and k 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

doc: IEEE /xxx4r0May 2005 Submission 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 Add new category in the action field for Radio Management Section , 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 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

doc: IEEE /xxx4r0May 2005 Submission 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, “Media Independent RF Management of Wireless 802 Networks” “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

doc: IEEE /xxx4r0May 2005 Submission Kwak, Rudolf 9 MAC/SME API/SAP Management Agent Management Agent Management Agent SME MACPHY SME MACPHY SME MACPHY MAC API/SAP AP1 AP2 AP3 Management Server or Application MIB BLUE: can be proprietary RED: standardized MAC API/SAP could be a quick and easy alternative to MIB’s for simple yet essential RF management tasks in 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