Download presentation
Presentation is loading. Please wait.
1
TAP/JIT Resource Pre-allocation
March 2005 doc.: IEEE /0210r0 March 2005 TAP/JIT Resource Pre-allocation Date: Authors: 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 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 Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures < 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 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 Edney (Nokia), Kumar (Cisco) Edney (Nokia), Kumar (Cisco)
2
March 2005 doc.: IEEE /0210r0 March 2005 Abstract Outcome of merger proposals between JIT and TAP in area of communicating resources requirements. Edney (Nokia), Kumar (Cisco) Edney (Nokia), Kumar (Cisco)
3
March 2005 Purpose and Scope This submission describes a mechanism for the STA and AP to discuss QOS* resource allocation requirements prior to transition In this submission we describe messages exchange mechanisms but medium is not discussed (e.g. over DS vs. using auth MAC frames) Message protection issues depend on the medium. “Over DS” communication has inherent protection for wireless hop. Using “auth frames” (original TAP) has protections built in * and other resources in future Edney (Nokia), Kumar (Cisco)
4
Types of AP / STA communications supported
March 2005 Types of AP / STA communications supported STA Query: STA asks AP to assess whether it could provide certain resources STA Pre-allocate: STA asks AP to allocate resources and hold them pending an association STA Associate: STA requests new resources as part of an association attempt. Edney (Nokia), Kumar (Cisco)
5
STA Query STA makes query to AP and provides list of desired resources
March 2005 STA Query STA makes query to AP and provides list of desired resources AP checks current loading and responds one of: Yes : Resources are available now No : Resources are not available; AP may suggest alternate set that it can accept or... Come-back-later: AP asks STA to query for a Yes/Noresponse after specified time. No commitment by AP to reserve resources AP may (optionally) remember query for limited time (informed to STA) Allows STA to simplify request on association by referencing query Allows AP to anticipate possible resource requirements Edney (Nokia), Kumar (Cisco)
6
STA Reservation STA informs AP of resource requirements
March 2005 STA Reservation STA informs AP of resource requirements AP may respond one of: Yes, resources reserved for limited time (informed to STA) No, resource request is rejected; AP may inform STA of possible alternative. STA may then revise and issue new reservation request Come back later Edney (Nokia), Kumar (Cisco)
7
March 2005 STA Associate STA can include a list of required resources with association request – no prior reservation or query required If AP is holding reserved resources and STA provides new set with association, AP would do adjustments. If AP cannot meet request it responds one of: Reject association (STA can try different AP) Reject association with suggested resources (STA can retry association request) Edney (Nokia), Kumar (Cisco)
8
March 2005 Message format Resource requests provided in message “Resource Information Container (RIC)” RIC has various features including: Grouping of related resources Indication of mandatory or optional resources Support for desired and alternate resource requests Index structure to optimize references to reserved resources Edney (Nokia), Kumar (Cisco)
9
Example Scenario STA is in a g711 voice call
March 2005 Example Scenario STA is in a g711 voice call STA decides to roam, chooses an AP to query before it associates. STA sends a TSPEC ( in RIC ) for g711 in the query. Query gets rejected, “NO”; query suggests g729 codec STA switches to g729 codec, associates with a g729 codec in the association Edney (Nokia), Kumar (Cisco)
10
March 2005 References r-jit-2-phase-association-proposal-text.doc r-transition-acceleration-protocol-draft-text.doc Edney (Nokia), Kumar (Cisco)
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.