MAPID for User Plane Support

Slides:



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

FBMS Termination Date: Name Compay Address Phone
LB84 General AdHoc Group Sept. Closing TGn Motions
[ Interim Meetings 2006] Date: Authors: July 2005
Multicast Scope Date: Authors: September 2006 Month Year
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
TGu Closing Report Date: Authors: November 2005
March 2014 Election Results
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
3GPP liaison report May 2006 May 2006 Date: Authors:
Motion to accept Draft p 2.0
Protected SSIDs Date: Authors: March 2005 March 2005
3GPP liaison report July 2006
[place presentation subject title text here]
Motions Date: Authors: January 2006
Solution to Transmit Updated QoS Map Set from AP to STA
Emergency Call Number Support
On Coexistence Mechanisms
Solution to Transmit Updated QoS Map Set from AP to STA
TGu-changes-from-d0-02-to-d0-03
CID 186, 206 and 211 resolution Date: Authors: January 2007
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
TGu Closing Report Date: Authors: September 2005
Solution for comment 32 Date: Authors: July, 2008
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 Timeline Date: Authors: November 2006 November 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
QoS in WLAN Interworking
TGy draft 2.0 with changebars from draft 1.0
TGv Redline D1.04-D1.0 Insert and Deletion
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:
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
May 2005 CAPWAP AHC Closing Report
TGu Motions Date: Authors: May 2006 May 2006
Beamforming and Link Adaptation Motions
CID 186, 206 and 211 resolution Date: Authors: January 2007
Unsynchronized Triggered Multicast Diagnostic Report
TGu Timeline Date: Authors: May 2006 May 2006
TGu-changes-from-d0-04-to-d0-05
Method for geting Link RCPI
TGu-changes-from-d0-03-to-d0-04
TGu Timeline Date: Authors: January 2005 January 2005
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
TGp Motions Date: Authors: January 2006 Month Year
Presentation transcript:

MAPID for User Plane Support January 2007 doc.: IEEE 802.11-07/0000r0 January 2007 MAPID for User Plane Support Date: 2007-01-08 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>. Peng Mo, Huawei Technologies Co., Ltd. Peng Mo, Huawei Technologies Co., Ltd.

January 2007 doc.: IEEE 802.11-07/0000r0 January 2007 Abstract This document indicates a problem in current 802.11u published draft [Draft-P802.11u-D0.02.pdf] and offers solutions to solve it. This document focuses on the QoS Mapping mechanism. Peng Mo, Huawei Technologies Co., Ltd. Peng Mo, Huawei Technologies Co., Ltd.

Agenda Background Problem Description Solution Statement Motion January 2007 doc.: IEEE 802.11-07/0000r0 January 2007 Agenda Background Problem Description Solution Statement Motion Peng Mo, Huawei Technologies Co., Ltd. Peng Mo, Huawei Technologies Co., Ltd.

January 2007 doc.: IEEE 802.11-07/0000r0 January 2007 Background In the interworking scenarios, the 802.11 MAC layer QoS is not enough, because the external network may use a different QoS scheme. 802.11u 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. For uplink: At the STA, there is a mapping from External QoS type (e.g. UMTS type via DSCP) to IEEE802 User Priority (in turn to EDCA ACs), or optionally to HCCA parameters. This will help the STA to construct correct QoS request to the QAP (e.g. ADDTS Request). At the AP, there is mapping from EDCA ACs to 802.1p when necessary. For downlink: At the AP, there is a mapping from 802.1p to EDCA ACs. QoS Mapping between DSCP and UP needs to be pre-configured at the AP for each directly connected SSPN. Peng Mo, Huawei Technologies Co., Ltd. Peng Mo, Huawei Technologies Co., Ltd.

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

January 2007 Background (Cont’d) 802.11u provides the Action Frame (QoS Map Configure) and the procedure shown as below for the STA to get the QoS Map. Peng Mo, Huawei Technologies Co., Ltd.

Agenda Background Problem Description Solution Statement Motion January 2007 doc.: IEEE 802.11-07/0000r0 January 2007 Agenda Background Problem Description Solution Statement Motion Peng Mo, Huawei Technologies Co., Ltd. Peng Mo, Huawei Technologies Co., Ltd.

January 2007 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? Peng Mo, Huawei Technologies Co., Ltd.

Agenda Background Problem Description Solution Statement Motion January 2007 doc.: IEEE 802.11-07/0000r0 January 2007 Agenda Background Problem Description Solution Statement Motion Peng Mo, Huawei Technologies Co., Ltd. Peng Mo, Huawei Technologies Co., Ltd.

Solution Statement (Cont’d) – Unicast Solution January 2007 Solution Statement (Cont’d) – Unicast Solution 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 waste radio resource, because AP have to inform STAs of the QoS Map information one bye one. If unicast solution is chosen, the following conditions should be fulfilled: – AP should maintain a mapping list to associate the QoS Map information with STAs, such as QoS MAP1 《-》 STA1/STA4/STA5, QoS MAP2《-》STA2/STA3/STA6. – Modify the description of the Non-APQSTAAddress in section 10.3.32.4.1 to “The specified non-AP QSTA MAC address could be the STA’s MAC address.” Peng Mo, Huawei Technologies Co., Ltd.

Solution Statement (Cont’d) – Broadcast Solution January 2007 Solution Statement (Cont’d) – Broadcast Solution 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 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 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. WLAN AP QoS Map Set #1 QoS Map Set #1 QoS Map Set #1 QoS Map Set #1 STA1 STA4 STA2 STA3 Peng Mo, Huawei Technologies Co., Ltd.

Solution Statement (Cont’d) – Broadcast Solution January 2007 doc.: IEEE 802.11-07/0000r0 January 2007 Solution Statement (Cont’d) – Broadcast Solution 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 1 Element ID. TBD 2 Length 3 Map ID 4 DSCP exception element #1 (optional) 5 DSCP exception element #2 (optional) 5+n-2 DSCP exception element #n (optional) 6+n-2 UP 0 DSCP Range element 7+n-2 UP 1 DSCP Range element 8+n-2 UP 2 DSCP Range element 9+n-2 UP 3 DSCP Range element 10+n-2 UP 4 DSCP Range element 11+n-2 UP 5 DSCP Range element 12+n-2 UP 6 DSCP Range element 13+n-2 UP 7 DSCP Range element Peng Mo, Huawei Technologies Co., Ltd. Peng Mo, Huawei Technologies Co., Ltd.

Solution Statement (Cont’d) – Broadcast Solution January 2007 doc.: IEEE 802.11-07/0000r0 January 2007 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. Peng Mo, Huawei Technologies Co., Ltd. Peng Mo, Huawei Technologies Co., Ltd.

Solution Statement (Cont’d) – Broadcast Solution January 2007 Solution Statement (Cont’d) – Broadcast Solution modification to figure STA QoS Map determination sequence when broadcast is used Peng Mo, Huawei Technologies Co., Ltd.

Solution Statement (Cont’d) – Multicast Solution January 2007 Solution Statement (Cont’d) – Multicast Solution 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. Peng Mo, Huawei Technologies Co., Ltd.

Solution Statement (Cont’d) – Multicast Solution January 2007 Solution Statement (Cont’d) – Multicast Solution 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. Peng Mo, Huawei Technologies Co., Ltd.

Solution Statement (Cont’d) – Multicast Solution January 2007 Solution Statement (Cont’d) – Multicast Solution modification to figure STA QoS Map determination sequence when multicast is used Peng Mo, Huawei Technologies Co., Ltd.

Solution Statement (Cont’d) – Proposal January 2007 Solution Statement (Cont’d) – Proposal 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. Peng Mo, Huawei Technologies Co., Ltd.

Agenda Background Problem Description Solution Statement Motion January 2007 doc.: IEEE 802.11-07/0000r0 January 2007 Agenda Background Problem Description Solution Statement Motion Peng Mo, Huawei Technologies Co., Ltd. Peng Mo, Huawei Technologies Co., Ltd.

Motion Move to accept the proposed changes (in red). Moved: Seconded: January 2007 doc.: IEEE 802.11-07/0000r0 January 2007 Motion Move to accept the proposed changes (in red). Moved: Seconded: Result: (for-against-abstain) Peng Mo, Huawei Technologies Co., Ltd. Peng Mo, Huawei Technologies Co., Ltd.