Proposal for Load Balancing Month Year November 2005 March 2006 Proposal for Load Balancing Date:2006-03-04 Authors: Notice: This document has been prepared to assist IEEE 802.11. 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 IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s 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 802.11. Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures <http:// ieee802.org/guides/bylaws/sb-bylaws.pdf>, 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 <stuart.kerry@philips.com> 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 802.11 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at <patcom@ieee.org>. Emily Qi et al Emily Qi et al

Month Year November 2005 March 2006 Abstract This document contains an outline of the normative text proposal for Load Balancing (doc#: 11-05/1064r2) in support of AP Load Balancing protocol to improve wireless network throughput and QoS effectiveness in accordance with REQ2030. Emily Qi et al Emily Qi et al

Agenda Design Goals Procedure and Usages Proposed Frame Formats Month Year November 2005 March 2006 Agenda Design Goals Procedure and Usages Proposed Frame Formats Proposed Information Element Emily Qi et al Emily Qi et al

March 2006 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 Emily Qi et al

Proposed Roaming Management Frames March 2006 Proposed Roaming Management Frames Roaming Candidate List IE 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 Reassociation Response and Admission Control Response The Roaming Candidate List element may be present if dot11WirelessNetworkManagementEnabled is true Emily Qi et al

Roaming Management Query Roaming Management Response March 2006 Procedure and Usages AP STAx 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 Roaming Management Request Handover to new BSS Initiated Disassocation Timer 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 STA begins planned handover using TGr protocol or reassociation Emily Qi et al

Roaming Management Query March 2006 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. Category Action Dialog Token Roaming Query Reason Octets: 1 Figure 2— Roaming Management Query frame body format Emily Qi et al

Roaming Management Request March 2006 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 Exclusivity bit Disassociation Imminent bit: 1 = Disassociation Imminent ; 0 = Suggestion Exclusivity bit: 1 = STA shall select a target AP only from the Roaming Candidate List ; 0 = STA may select a target AP not present in the Roaming Candidate List. Category Action Dialog Token Request mode Disassociation Timer (optional) Roaming Candidate List Neighbor Report element Octets 1 variable Figure 3 —Roaming Management Request frame body format Emily Qi et al

Proposed Roaming Candidate IE March 2006 Proposed Roaming Candidate IE EID Length BSSID Preference Expiry Timer Load Sub-element List Octets: 1 6 Figure 3 - Roaming Candidate element format Load Sub-elements Sub-element ID General Load QBSS Available Admission Capacity 1 QBSS Available Admission Capacity for UP 4 Traffic 2 QBSS Available Admission Capacity for UP 5 Traffic 3 QBSS Available Admission Capacity for UP 6 Traffic 4 QBSS Available Admission Capacity for UP 7 Traffic 5 Reserved 6-255 Preference field value Description Barred AP, STA needs to stay away from this AP. 1-255 Relative values used to indicate network does recommended this BSS for roaming Emily Qi et al

Roaming Management Response March 2006 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 Category Action Dialog Token Status code Target BSSID (Optional) Octets: 1 6 Figure 5 Roaming Management Response frame body format Emily Qi et al

March 2006 Feedback? Emily Qi et al

Month Year November 2005 March 2006 Motion Move to include normative text in document 11-05-1064-02-000v-normative-text-proposal-load-balancing.doc into the TGv draft. Mover: Seconder: Results: Emily Qi et al Emily Qi et al