doc.: IEEE /1065r3 Submission May 2006 Emily Qi et alSlide 1 Proposal for Load Balancing Notice: This document has been prepared to assist IEEE It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. Release: The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEEs name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEEs sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures, including the statement "IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE Working Group. If you have questions, contact the IEEE Patent Committee Administrator at. Date: Authors:

doc.: IEEE /1065r3 Submission May 2006 Emily Qi et alSlide 2 Abstract This document contains an outline of the normative text proposal for Load Balancing (doc#: 11-05/1064r5) in support of AP Load Balancing protocol to improve wireless network throughput and QoS effectiveness in accordance with REQ2030.

doc.: IEEE /1065r3 Submission May 2006 Emily Qi et alSlide 3 Agenda Design Goals Procedure and Usages Proposed Frame Formats Proposed Information Element

doc.: IEEE /1065r3 Submission May 2006 Emily Qi et alSlide 4 Design Goals Define a protocol to support AP and STA cooperative load balancing to improve wireless network throughput and QoS effectiveness for VoIP and Video stream Allow STA and AP to exchange the information needed to enable a network to manage BSS loads by –influencing STA roaming decisions, and –initiating STA handover to selected target BSS(s). The protocol can be extended to other Roaming Managements The provisions for Roaming Management and load balancing do not apply to an IBSS

doc.: IEEE /1065r3 Submission May 2006 Emily Qi et alSlide 5 Proposed Roaming Management Frames TGv Action Frames – Class 3 –Roaming Management Query Optional, non-AP STA AP –Roaming Management Request Mandatory, AP non-AP STA –Roaming Management Response Optional, non-AP STA AP Roaming Candidate List Entries comprise Neighbor Report IEs

doc.: IEEE /1065r3 Submission May 2006 Emily Qi et alSlide 6 Procedure and Usages APSTAx Roaming Management Query (optional) An AP may send a Roaming Management Request frame to any STA at any time, or respond to a Roaming Management Query frame from any STA Roaming Management Response (optional) Roaming Management Request Handover to new BSS Initiated Disassocation Timer (optional) STA considers network load balancing preferences, control level, exclusivity and evaluates current quality of roaming options. STA selects target BSS for the planned handover. Disassociation (optional) STA begins planned handover using TGr protocol or reassociation

doc.: IEEE /1065r3 Submission May 2006 Emily Qi et alSlide 7 Roaming Management Query If a STA wishes to solicit network information for roaming, the STA may send a Roaming Management Query frame to the serving AP Possible Roaming Query Reasons are: –Low throughput –Unacceptable delay/jitter –Loss of signal in current BSS (link going down), etc. CategoryActionDialog TokenRoaming Query Reason Octets:1111 Figure 2 Roaming Management Query frame body format

doc.: IEEE /1065r3 Submission May 2006 Emily Qi et alSlide 8 Roaming Management Request An AP can send a Roaming Management Request frame to any STA at any time, or respond to a Roaming Management Query frame from any STA Request mode: Control Level bit and Abridged bit –Disassociation Imminent bit: 1 = Disassociation Imminent ; 0 = Suggestion –Abridged bit: 1 = every BSSID under consideration by the receiving STA should be treated as if it were present in the Roaming Candidate List with a Preference value of 0; 0 = the sender of this frame has no recommendation. CategoryActionDialog Token Request mode Disassociation Timer (optional) Expiry Timer Roaming Candidate List Entries Octets 11111variable Figure 3 Roaming Management Request frame body format

doc.: IEEE /1065r3 Submission May 2006 Emily Qi et alSlide 9 Roaming Candidate List Entries Preference field valueDescription 0Barred AP, STA needs to stay away from this AP Relative values used to indicate the preferred ordering of BSSs, with 1 as the highest order of preference. Roaming Candidate List Entries contain one or more Neighbor Report elements In addition to the sub-elements that are defined in TGk, the following sub-elements are defined in TGv: –Roaming Candidate Preference to describes the network preferences for recommended target AP candidate to this STA –QBSS Available Admission Capacity and QBSS load for target AP candidate

doc.: IEEE /1065r3 Submission May 2006 Emily Qi et alSlide 10 Roaming Management Response A STA receiving a Roaming Management Request frame may respond with a Roaming Management Response frame Status Code: –Zero = will Roam to another AP; non-zero = Not Roam. Target BSSID –Shall be the target BSSID that STA decided to roam to if status code is 0. –Shall be Null if Status is non-zero CategoryActionDialog TokenStatus codeTarget BSSID (Optional) Octets:11116 Figure 5 Roaming Management Response frame body format

doc.: IEEE /1065r3 Submission May 2006 Emily Qi et alSlide 11 Feedback?

doc.: IEEE /1065r3 Submission May 2006 Emily Qi et alSlide 12 Motion Move to include normative text in document v-normative-text-proposal-load- balancing.doc into the TGv draft. Mover: Seconder: Results: