Doc.: IEEE 802.11-07/0025r1 Submission January 2007 Peng Mo, Huawei Technologies Co., Ltd.Slide 1 MAPID for User Plane Support Notice: This document has.

Slides:



Advertisements
Similar presentations
Doc.: IEEE /0866r1 Submission September 2005 Michael Montemurro, Chantry NetworksSlide 1 Mobility Domain Definition and Description Notice: This.
Advertisements

Doc.: IEEE /90r0 Submission Nov., 2012 NICTSlide b NICT Proposal IEEE P Wireless RANs Date: Authors: Notice: This document.
Doc.: IEEE /0930r0 Submission July 2006 Nancy Cam-Winget, Cisco Slide 1 Editor Updates since Jacksonville Notice: This document has been prepared.
Doc.: IEEE /1138r1 Submission November 2005 Cheng Hong, PanasonicSlide 1 Authorization Information in interworking Notice: This document has been.
Doc.: IEEE /1138r0 Submission November 2005 Cheng Hong, PanasonicSlide 1 Authorization Information in interworking Notice: This document has been.
Doc.: IEEE /0121r0 Submission January 2006 S. Bezzateev, A. Fomin, M. WongSlide 1 Broadcast Management Frame Protection Notice: This document.
Doc.: IEEE /0644r2 Submission May 2006 Päivi Ruuska, NokiaSlide 1 Measurement Pilot Transmission Information as optional information in Probe.
Doc.: IEEE /1219r2 Submission January, 2006 S. Ponnuswamy (Aruba Networks)Slide 1 Virtual AP Presentation Notice: This document has been prepared.
Doc.: IEEE /0072r0 Submission January 2009 Slide 1 Proxy ARP Issue for Direct Link Setup Notice: This document has been prepared to assist IEEE.
Doc.: IEEE /1936r0 Submission December 2006 Bruce Kraemer, Marvell Adrian Stephens, IntelSlide 1 TGn Proposed Draft Revision Notice Notice: This.
Doc.: IEEE /86r2 Submission March, 2010 Gabor BajkoSlide 1 Location Proxy Notice: This document has been prepared to assist IEEE It is.
Doc.: IEEE /0667r0 Submission July 2005 Mike Moreton, STMicroelectronicsSlide 1 Multiple Networks Notice: This document has been prepared to assist.
Doc.: IEEE /0028r0 Submission January 2005 Eleanor Hepworth, Siemens Roke ManorSlide 1 Definitions and Terminology Notice: This document has been.
Doc.: IEEE /1528r0 Submission 22 September 2006 Naveen Kakani, Nokia, IncSlide 1 TGn PSMP adhoc Group September Closing Report Notice: This document.
Doc.: IEEE /0460r1 Submission March 2006 Fujio Watanabe, DoCoMo USA LabsSlide 1 Japanese Emergency Call Regulation Notice: This document has been.
Doc.: IEEE /0136r0 Submission January 2007 Dave Stephenson, Cisco Systems, Inc.Slide 1 Input to Information Model Date: Notice:
Doc.: IEEE /1006r0 Submission September 2005 Andrew McDonald, Siemens Roke ManorSlide 1 Initial Network Selection Concept Notice: This document.
Doc.: IEEE /0215r1 Submission January 2006 Jesse Walker, Intel CorporationSlide 1 TGw Closing Report Notice: This document has been prepared to.
Doc.: IEEE /0652r1 Submission May 2007 Emily Qi, Intel CorporationSlide 1 TGv Redline D0.12 Insert and Deletion Notice: This document has been.
FBMS Termination Date: Name Compay Address Phone
[ Interim Meetings 2006] Date: Authors: July 2005
Multicast Scope Date: Authors: September 2006 Month Year
London TGu Motions Authors: January 2007 Date: Month Year
LB73 Noise and Location Categories
LB73 Noise and Location Categories
Waveform Generator Source Code
TGu Closing Report Date: Authors: November 2005
Attendance and Documentation for the March 2007 Plenary
3GPP Extended Date: Authors: July 2005 July 2005
Problem & Proposal for User Plane Support for QoS Mapping
Motion to accept Draft p 2.0
Solution to Transmit Updated QoS Map Set from AP to STA
On Coexistence Mechanisms
Solution to Transmit Updated QoS Map Set from AP to STA
TGu-changes-from-d0-02-to-d0-03
MAPID for User Plane Support
TGu Closing Report Date: Authors: July 2006 July 2006
On Coexistence Mechanisms
Reflector Tutorial Date: Authors: July 2006 Month Year
TGv Redline D0.07 Insert and Deletion
TGv Redline D0.06 Insert and Deletion
Proposal for User Plane Support for QoS Mapping
Congestion control timer
ADS Study Group Mid-week Report
TGu Timeline Date: Authors: July 2005 July 2005
TGu Timeline Date: Authors: July 2006 July 2006
TGu-changes-from-d0-01-to-d0-02
LB73 Noise and Location Categories
QoS map addition Date: Authors: May 2007 May 2007
MAPID for User Plane Support
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
3GPP2 Liaison Report Date: Authors: May 2006 May 2006
Beamforming and Link Adaptation Motions
Path Selection and Path Switch Mechanism
TGu Timeline Date: Authors: May 2006 May 2006
TGu-changes-from-d0-04-to-d0-05
TGu-changes-from-d0-03-to-d0-04
TGu Motions Date: Authors: May 2006 May 2006
Reserve Option Contradiction
New User Plane Requirement
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
Proposal for Diagnostic Alerts
Proposal for User Plane Support for QoS Mapping
Presentation transcript:

doc.: IEEE /0025r1 Submission January 2007 Peng Mo, Huawei Technologies Co., Ltd.Slide 1 MAPID for User Plane Support 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, 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 /0025r1 Submission January 2007 Peng Mo, Huawei Technologies Co., Ltd.Slide 2 Abstract This document indicates a problem in current u published draft [Draft-P802.11u-D0.02.pdf] and offers solutions to solve it. This document focuses on the QoS Mapping mechanism.

doc.: IEEE /0025r1 Submission January 2007 Peng Mo, Huawei Technologies Co., Ltd.Slide 3 Agenda Background Problem Description Solution Statement Motion

doc.: IEEE /0025r1 Submission January 2007 Peng Mo, Huawei Technologies Co., Ltd.Slide 4 Background In the interworking scenarios, the MAC layer QoS is not enough, because the external network may use a different QoS scheme u provides the solution with the QoS Map Set element, which defines the mapping from DSCP contained in a packets IP header to the user priority.

doc.: IEEE /0025r1 Submission January 2007 Peng Mo, Huawei Technologies Co., Ltd.Slide 5 Background (Cont’d) – QoS Map Set element description Order Size (octets) Description 11Element ID. TBD 21Length 32DSCP exception element #1 (optional) 42DSCP exception element #2 (optional) 4+n-22DSCP exception element #n (optional) 5+n-22UP 0 DSCP Range element 6+n-22UP 1 DSCP Range element 7+n-22UP 2 DSCP Range element 8+n-22UP 3 DSCP Range element 9+n-22UP 4 DSCP Range element 10+n-22UP 5 DSCP Range element 11+n-22UP 6 DSCP Range element 12+n-22UP 7 DSCP Range element

doc.: IEEE /0025r1 Submission January 2007 Peng Mo, Huawei Technologies Co., Ltd.Slide 6 Background (Cont’d) u provides the Action Frame (QoS Map Configure) and the procedure shown as below for the STA to get the QoS Map.

doc.: IEEE /0025r1 Submission January 2007 Peng Mo, Huawei Technologies Co., Ltd.Slide 7 Agenda Background Problem Description Solution Statement Motion

doc.: IEEE /0025r1 Submission January 2007 Peng Mo, Huawei Technologies Co., Ltd.Slide 8 Problem Description “When the AP has a change in the QoS Map information, it can also use the Action Frame to configure the QoS Map at the STA without solicitation (as shown in the broken line at the bottom of the figure). ” How to use the Action Frame to configure the QoS Map at the STA without solicitation? Unicast ? Broadcast ? Multicast?

doc.: IEEE /0025r1 Submission January 2007 Peng Mo, Huawei Technologies Co., Ltd.Slide 9 Agenda Background Problem Description Solution Statement Motion

doc.: IEEE /0025r1 Submission January 2007 Peng Mo, Huawei Technologies Co., Ltd.Slide 10 Unicast solution is one choice for the QoS Map Configure frame to configure the QoS Map at the STA. The destination address of the QoS Map Configure frame is the STA’s unicast MAC address when AP updates the QoS Map information. But unicast solution will bring two problems: 1. Unicast solution will bring more resource consumption, such as radio resources, state machines of AP. 2. Dialog Token in the unsolicited QoS Map Configure frame will make STA confused. Solution Statement (Cont’d) – Unicast Solution

doc.: IEEE /0025r1 Submission January 2007 Peng Mo, Huawei Technologies Co., Ltd.Slide 11 Broadcast solution is one choice for the QoS Map Configure frame to configure the QoS Map at the STA The destination address of the QoS Map Configure frame is the broadcast address when AP updates the QoS Map information. AP may serve STAs from different SSPNs, different QoS Map information for different SSPNs should be maintained by the same AP. So there should be a flag to distinguish the different QoS Map information. SSPN a WLAN AP STA1 STA2STA3 STA4 SSPN b STA 1,2 are subscribers of SSPN a. STA 3,4 are subscribers of SSPN b. QoS Map Set #1 is associated with SSPN a. QoS Map Set #2 is associated with SSPN b. QoS Map Set #1 QoS Map Set #1 has changed, AP needs to inform STA 1,2 of the new QoS Map Set, but STA 3,4 also receives the QoS Map Set because of the broadcast frame. QoS Map Set #1 Solution Statement (Cont’d) – Broadcast Solution

doc.: IEEE /0025r1 Submission January 2007 Peng Mo, Huawei Technologies Co., Ltd.Slide 12 If broadcast solution is chosen, we propose that adding a Map ID in the QoS Map Set (Figure u-17) to identify the QoS Map Set. Order Size (octets) Description 11Element ID. TBD 21Length 32Map ID 42DSCP exception element #1 (optional) 52DSCP exception element #2 (optional) 5+n-22DSCP exception element #n (optional) 6+n-22UP 0 DSCP Range element 7+n-22UP 1 DSCP Range element 8+n-22UP 2 DSCP Range element 9+n-22UP 3 DSCP Range element 10+n-22UP 4 DSCP Range element 11+n-22UP 5 DSCP Range element 12+n-22UP 6 DSCP Range element 13+n-22UP 7 DSCP Range element Solution Statement (Cont’d) – Broadcast Solution

doc.: IEEE /0025r1 Submission January 2007 Peng Mo, Huawei Technologies Co., Ltd.Slide 13 Solution Statement (Cont’d) – Broadcast Solution Add the following text after Figure u-17: The Map ID is maintained by AP and returned in the QoS Map Set element of the QoS Map Configure frame. One QoS Map Set is identified by one Map ID. Change the last paragraph of the clause P.2.1 as shown below: When the AP has a change in the QoS Map information, it can also use the Action Frame to configure the QoS Map at the STA without solicitation (as shown in the broken line at the bottom of the sequence). The STA should update the QoS Map information based on the Map ID.

doc.: IEEE /0025r1 Submission January 2007 Peng Mo, Huawei Technologies Co., Ltd.Slide 14 Solution Statement (Cont’d) – Broadcast Solution modification to figure STA QoS Map determination sequence when broadcast is used

doc.: IEEE /0025r1 Submission January 2007 Peng Mo, Huawei Technologies Co., Ltd.Slide 15 Multicast solution is one choice for the QoS Map Configure frame to configure the QoS Map at the STA. The destination address of QoS Map Configure frame is a multicast address when AP updates the QoS Map information. One multicast address should be allocated for One QoS Map Set by AP, and different QoS Map Sets should have different multicast addresses. AP should inform the STA of the multicast address, and the STA should join the multicast group. Solution Statement (Cont’d) – Multicast Solution

doc.: IEEE /0025r1 Submission January 2007 Peng Mo, Huawei Technologies Co., Ltd.Slide 16 If multicast solution is chosen, the following conditions should be fulfilled: – When the STA sends a unicast QoS Map Request frame to request the QoS Map information, AP should reply with a unicast QoS Map Configure frame with the QoS Map Set and a multicast address. The STA should get the multicast address from the QoS Map Configure frame and join the multicast group. – When AP has any change in the QoS Map information, the destination address of QoS Map Configure frame should be a multicast address. All STAs of the multicast group should process the QoS Map Configure frame. Solution Statement (Cont’d) – Multicast Solution

doc.: IEEE /0025r1 Submission January 2007 Peng Mo, Huawei Technologies Co., Ltd.Slide 17 modification to figure STA QoS Map determination sequence when multicast is used Solution Statement (Cont’d) – Multicast Solution

doc.: IEEE /0025r1 Submission January 2007 Peng Mo, Huawei Technologies Co., Ltd.Slide 18 Broadcast and multicast solution are both good choices, we propose using the broadcast solution because it results in the least changes to the current draft. Solution Statement (Cont’d) – Proposal

doc.: IEEE /0025r1 Submission January 2007 Peng Mo, Huawei Technologies Co., Ltd.Slide 19 Agenda Background Problem Description Solution Statement Motion

doc.: IEEE /0025r1 Submission January 2007 Peng Mo, Huawei Technologies Co., Ltd.Slide 20 Motion Move to accept the proposed changes (in red). Moved: Seconded: Result: (for-against-abstain)