January 2003 doc IEEE 802 11 03080 r

January 2003 doc. : IEEE 802. 11 -03/080 r 0 A A Framework for RRM Simon Black, Mika Kasslin, Hasse Sinivaara (Nokia) simon. black@qosine. co. uk, mika. kasslin@nokia. com, hasse. sinivaara@nokia. com TGk January 2003 Submission 1 Black/Kasslin/Sinivaara, Nokia

January 2003 doc. : IEEE 802. 11 -03/080 r 0 A RRM Objectives • • RRM is about obtaining information and delivering it to the appropriate place Improved observation of AP and client performance and environment to facilitate • • Enhancing information provided to WLAN clients to: • • • Improved WLAN client performance though better network management Optimization of the overall system capacity – particularly in dense BSS environments Refinement of system installation/deployment – are new APs required? Are existing APs badly sited? Improved diagnosis of network management problems – audit trails, system alerts Managed link quality for Qo. S provision A flexible framework that can be adapted for new services Improve the AP selection process both when joining and when roaming Provide assisted handover support Information for assisted, or possibly autonomous network configuration during installation and expansion Submission 2 Black/Kasslin/Sinivaara, Nokia

January 2003 doc. : IEEE 802. 11 -03/080 r 0 A RRM Requirements 1 Capabilities, Measurements & Statistics • • It should be possible to identify an RRM capable AP, or STA It should be possible for a management entity to request that an Access Point make appropriate measurements to determine the radio environment – – • prior to MLME-START. request being issued while operating STAs should have the ability to make and report measurements on the radio environment – – • autonomously when requested via the AP It should be possible for a Network Management Entity to obtain configuration and statistics information – – Submission extend AP MIB for per-STA statistics and not global MAC statistics as already discussed in RRM SG/TGk it should be possible to generate management alerts for certain conditions 3 Black/Kasslin/Sinivaara, Nokia

January 2003 doc. : IEEE 802. 11 -03/080 r 0 A RRM Requirements 2 Improved BSS information • Information should be available to STAs to assist in making association decisions that result in – good service characteristics for the individual STA without affecting those experienced by other STAs in the ESS – efficient usage of the available resources. – likely to be particularly important if applications with Quality-of-Service (Qo. S) requirements are being supported – e. g. the provision of BSS load information Submission 4 Black/Kasslin/Sinivaara, Nokia

January 2003 doc. : IEEE 802. 11 -03/080 r 0 A RRM Requirements 3 Information to Streamline Roaming • Information should be available to STAs that assists in streamlining the roaming process – Overall objective to improve the user experience at handover through the provision of additional radio resource and system information – Transmitted by the AP – Information regarding other APs in the ESS (neighbourhood or colocated BSSs) and possibly the boundary of an ESS – This is just provision of information – the decision of when to scan for and join a given BSS is unchanged as an STA decision Submission 5 Black/Kasslin/Sinivaara, Nokia

January 2003 doc. : IEEE 802. 11 -03/080 r 0 A Six RRM Scenarios • • • AP MIB Related Configuration, Control, and Statistics AP Measurements Distribution of RRM Information to STAs STA Statistics Gathering RRM Commanded STA Actions STA Autonomous Action Submission 6 Black/Kasslin/Sinivaara, Nokia

January 2003 doc. : IEEE 802. 11 -03/080 r 0 A RRM Scenario A: AP MIB Related Configuration, Control, and Statistics DS Interface Access Point MIB Data Network Management Station Remote Management APME RRM Algorithms Submission AP MIB Remote RRM Algorithms Configuration{data} Control {data} MIB request 7 Black/Kasslin/Sinivaara, Nokia

January 2003 doc. : IEEE 802. 11 -03/080 r 0 A RRM Scenario B: AP Measurements Radio Interface Measurements DS Interface Access Point Measurement{data} Network Management Station Remote Management APME RRM Algorithms Submission Remote RRM Algorithms Measure request AP MIB 8 Black/Kasslin/Sinivaara, Nokia

January 2003 doc. : IEEE 802. 11 -03/080 r 0 A Scenario C: Distribution of RRM Information to STAs Radio Interface Info Request Station Access Point RRM Information{data] Station AP MIB Station Submission 9 Black/Kasslin/Sinivaara, Nokia

January 2003 doc. : IEEE 802. 11 -03/080 r 0 A RRM Scenario D: STA Statistics Gathering Radio Interface Station DS Interface Access Point MIB Data Network Management Station MIB Data Remote Management Remote RRM Algorithms MIB request Submission MIB request 10 Black/Kasslin/Sinivaara, Nokia

January 2003 doc. : IEEE 802. 11 -03/080 r 0 A RRM Scenario E: RRM Commanded STA Actions Radio Interface Action Response DS Interface Access Point Action Response Network Management Station Remote Management SME RRM Algorithms Remote RRM Algorithms Action request Submission AP MIB APME RRM Algorithms Action request 11 Black/Kasslin/Sinivaara, Nokia

January 2003 doc. : IEEE 802. 11 -03/080 r 0 A RRM Scenario F: STA Autonomous Action Radio Interface DS Interface Access Point Information Network Management Station Remote Management SME RRM Algorithms [Action] Remote RRM Algorithms AP MIB APME RRM Algorithms Submission 12 Black/Kasslin/Sinivaara, Nokia

January 2003 doc. : IEEE 802. 11 -03/080 r 0 A Scope of RRM • In practice the protocol elements that are specified will be MAC and PHY extensions – most likely MLME and PLME services • The standard should deal with protocol and not decision-making or algorithms – for example a set of measurements may be defined but not any specific rule as to when these measurements should be made, or how the results should be used • Effectively the standard should provide a tool-kit for RRM Submission 13 Black/Kasslin/Sinivaara, Nokia

January 2003 doc. : IEEE 802. 11 -03/080 r 0 A IEEE 802. 11 h Layer Model SME Channel Switch Decision CHANNEL SWITCH Measurement Policy MREQUEST& MREPORT MEASURE MLME Channel Switch Timing Measurement Protocol Measurement Frames MAC Timing Protocol MLME Frames PLME Submission 14 Black/Kasslin/Sinivaara, Nokia

January 2003 doc. : IEEE 802. 11 -03/080 r 0 A Possible RRM Layer Management Model Higher Layer Protocols APME Measurement Policy TPC MIB GET/SET MEASURE Policy MREQUEST& MREPORT MLME TPC Measurement Protocol MIB Measurement Frames MAC Timing Beacon Process TPC Beacon Frames Measure Protocol MLME Frames PLME MIB Submission 15 Black/Kasslin/Sinivaara, Nokia

January 2003 doc. : IEEE 802. 11 -03/080 r 0 A Example Measurement MSC AP APME MLME STA SME Decision to request measurement from peer STA MLME-MREQUEST. req MLME-MREQUEST. cfm MEASUREMENT REQUEST FRAME MLME-MREQUEST. ind Decision to accept measurement request from peer STA MLMEMEASURE. req Measurement Process MLMEMEASURE. cfm Compile Measurement Report MLMEMREPORT. ind MLMEMREPORT. req MEASUREMENT REPORT FRAME Measurement Request Completed Submission 16 MLMEMREPORT. cfm Black/Kasslin/Sinivaara, Nokia

January 2003 doc. : IEEE 802. 11 -03/080 r 0 A RRM Protocol Elements • • Add a bit to the Capability Information fixed field to indicate RRM capability Use the Action management frame type as defined in the IEEE 802. 11 h draft – define a new Action category value defined for RRM • Extension of the AP MAC MIB – enhance for per-STA link statistics • Use the measurement request and measurement report elements and protocol as defined in the IEEE 802. 11 h draft – Define measurements to meet the requirements • RSSI, retry statistics, CCA busy fraction, noise floor, observed BSSs, non-IEEE 802. 11 signals – Consider cross-band measurements • Define a BSS load element – Review the QBSS load element in the IEEE 802. 11 e draft as a starting point • Define an ESS Information element – potential neighbour BSSs – indicate the boundary of the ESS Submission 17 Black/Kasslin/Sinivaara, Nokia

January 2003 doc. : IEEE 802. 11 -03/080 r 0 A A Framework for RRM Simon Black, Mika Kasslin, Hasse Sinivaara (Nokia) simon. black@qosine. co. uk, mika. kasslin@nokia. com, hasse. sinivaara@nokia. com TGk January 2003 Submission 18 Black/Kasslin/Sinivaara, Nokia