QoS Resource Query Overview

Slides:



Advertisements
Similar presentations
LB84 General AdHoc Group Sept. Closing TGn Motions
Advertisements

LB84 General AdHoc Group Sept. Closing TGn Motions
[ Interim Meetings 2006] Date: Authors: July 2005
Resource Request/Response Discussion
Motions Date: Authors: January 2006
London TGu Motions Authors: January 2007 Date: Month Year
LB73 Noise and Location Categories
LB73 Noise and Location Categories
Waveform Generator Source Code
March 2014 Election Results
TGp Closing Report Date: Authors: July 2007 Month Year
Attendance and Documentation for the March 2007 Plenary
[ Policies and Procedure Summary]
Motion to accept Draft p 2.0
Protected SSIDs Date: Authors: March 2005 March 2005
QoS Resource Query Overview
3GPP liaison report July 2006
[place presentation subject title text here]
Motions Date: Authors: January 2006
Fast Transition Mobility (FTM) Domain
TGp Motions Date: Authors: November 2005 Month Year
Fast Transition Report
TGp Closing Report Date: Authors: March 2006 Month Year
TGu-changes-from-d0-02-to-d0-03
Contribution on Location Privacy
Quick Beacon Impacts on LB 92
TGp Closing Report Date: Authors: March 2006 Month Year
Reflector Tutorial Date: Authors: July 2006 Month Year
TGv Redline D0.07 Insert and Deletion
TGv Redline D0.06 Insert and Deletion
Managed BSS Channel Switch
Proposal for User Plane Support for QoS Mapping
ADS Study Group Mid-week Report
Proposal for Resolving Comments on Intra-Mesh Congestion Control
Selection Procedure Recommendation
TGu-changes-from-d0-01-to-d0-02
LB73 Noise and Location Categories
Extended Channel Switch Announcements
TGy draft 2.0 with changebars from draft 1.0
TGv Redline D0.10 Insert and Deletion
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
Redline of draft P802.11w D2.2 Date: Authors:
Document Motions Date: Authors: November 2005 November 2005
TGr Proposed Draft Revision Notice
Off-channel selection
TGu-changes-from-d0-02-to-d0-03
[ Policies and Procedure Summary]
March Opening Report Date: Authors: March 2011
May 2005 CAPWAP AHC Closing Report
TGu Motions Date: Authors: May 2006 May 2006
Liaison to TIA TR-41.4 from IEEE
Beamforming and Link Adaptation Motions
Path Selection and Path Switch Mechanism
Draft P802.11s D1.03 WordConversion
Limiting GAS State-1 Query Response Length
TGu-changes-from-d0-04-to-d0-05
Method for geting Link RCPI
Transition Nowhere Date: Authors: Sept 2005 Sept 2005
Use of More Data Field Date: Authors: Nov 2005 Month Year
Motion for request of assigned numbers
TGu-changes-from-d0-03-to-d0-04
TGu Motions Date: Authors: May 2006 May 2006
Reserve Option Contradiction
Beamforming and Link Adaptation Motions for LB 84 Comment Resolutions
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
Use of KCK for TGr Management Frame Protection
Use of KCK for TGr Management Frame Protection
TGr Proposed Draft Revision Notice
Proposal for User Plane Support for QoS Mapping
TGp Motions Date: Authors: January 2006 Month Year
Presentation transcript:

QoS Resource Query Overview May 2006 doc.: IEEE 802.11-06/0447r1 May 2006 QoS Resource Query Overview Date: 2006-05-16 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>. Steve Emeott, Motorola Steve Emeott, Motorola

May 2006 doc.: IEEE 802.11-06/0447r1 May 2006 Abstract This document is an overview of a proposed QoS resource query feature described in document 06/685r0. This proposal addresses comments 1195 and 1237 in LB82. Steve Emeott, Motorola Steve Emeott, Motorola

Components of the Proposal May 2006 Components of the Proposal QoS resource query is: A procedure permitting a STA to Determine whether a resource request is acceptable to a target AP prior to initiating a Fast BSS Transition with the target AP Obtain feedback from a target AP about its supported capabilities in the form of a response to a specific resource request simple query mechanism compatible with the resource request signaling already included in 802.11r. The proposal can be broken into the following components: resource control byte added to the RRIE, the byte having one field to enable query normative text for over the air and over the DS query exchanges using confirm and acknowledgement signaling normative text for AP and STA behaviors Steve Emeott, Motorola

Resource Control Byte in RRIE May 2006 Resource Control Byte in RRIE New Field Element ID Length Resource Control RRIE Identifier Count of RDIEs Octets: 1 Figure 80AI—RRIE information element Bit Meaning 0: Query When set, the RIC carries a QoS resource query. When clear, the RIC carries a reservation request. 1-7: Reserved Reserved Table T1—Resource Control field Steve Emeott, Motorola

May 2006 doc.: IEEE 802.11-06/0447r1 May 2006 Normative Text New clause 8A.4A (Fast BSS transition QoS resource query mechanism) added to Define normative procedures for Fast BSS transition QoS resource query mechanism, including Over-the-air query mechanism (8A.4A.1) Over-the-DS query mechanism (8A.4A.2) Small changes to clause 8A.7.2 (Creation and handling of a reservation request) Normative procedures for creation and handling of a reservation request augmented to include QoS resource query procedures at STA and AP New clause 8A.7.3 (Creation and handling of a QoS resource query request ) added to Define normative procedures for creation and handling of a QoS resource query request, including QoS resource query behaviors for STA QoS resource query behaviors for AP Steve Emeott, Motorola Steve Emeott, Motorola

May 2006 Pros The proposal adds a query feature to procedure already used to submit reservations (and otherwise defines no new signaling) A STA may use the query as a means to Learn whether the resource policies employed by the target AP permit the STA to make reservation using a specific TSPEC well in advance of a transition. This can be useful when a target AP supports admissions control but by policy does not accept certain TSPECs (perhaps an AC is requested for which admissions control is unsupported, or perhaps the RIC includes a HCCA TSPEC or requires an unusually high percentage of an APs resources, for example). Verify that PMK-R1 has been installed while at the same time learning the resource policies employed by the target AP Proposal defines STA and AP behaviors for implementing a query using the FT Action Confirm and FT Action Acknowledgement frames Steve Emeott, Motorola

Cons Adds an extra byte to the RRIE May 2006 Cons Adds an extra byte to the RRIE Adds a small amount to the complexity to the target AP to process the control byte Steve Emeott, Motorola

May 2006 Summary The query mechanism is simple because the signaling used for a query is for all intents and purposes equivalent to resource reservation. The query bit in the resource control byte prevents the target AP for actually reserving resources. Otherwise a query is the same as a resource request. Steve Emeott, Motorola

May 2006 Straw Poll Would you like normative text for this mechanism submitted for inclusion into the TGr draft? Yes: No: Steve Emeott, Motorola