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

January 2007

Peng Mo, Huawei Technologies Co., Ltd.

Slide 1

doc.: IEEE 802.11-07/0025r1

Submission

MAPID for User Plane Support

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 <[email protected]> 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 <[email protected]>.

Date: 2007-01-08

Name Company Address Phone email Peng Mo Huawei [email protected]

Patrick Mo Huawei [email protected]

Authors:

January 2007


Slide 2

doc.: IEEE 802.11-07/0025r1

Submission

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.

January 2007


Slide 3

doc.: IEEE 802.11-07/0025r1

Submission

Agenda

• Background

• Problem Description

• Solution Statement

• Motion

January 2007


Slide 4

doc.: IEEE 802.11-07/0025r1

Submission

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.

January 2007


Slide 5

doc.: IEEE 802.11-07/0025r1

Submission

Background (Cont’d) –QoS Map Set element description

OrderSize (octets)

Description

1 1 Element ID. TBD

2 1 Length

3 2 DSCP exception element #1 (optional)


4+n-2 2 DSCP exception element #n (optional)

5+n-2 2 UP 0 DSCP Range element








January 2007


Slide 6

doc.: IEEE 802.11-07/0025r1

Submission

Background (Cont’d)

STA AP AAA ServerAAA Client

(Re-)Association Request

(Re-)Association Response

802.11i/ EAP Authentication

Access-Accept

(Keying info + tunnel)

Associate STA to VLAN per AAA

EAP-Success

4 way handshake

Action Frame (QoS Map Request)

Action Frame (QoS Map Configure)


• 802.11u provides the Action Frame (QoS Map Configure) and the procedure shown as below for the STA to get the QoS Map.

January 2007


Slide 7

doc.: IEEE 802.11-07/0025r1

Submission

Agenda

• Background



• Motion

January 2007


Slide 8

doc.: IEEE 802.11-07/0025r1

Submission

Problem DescriptionSTA AP AAA ServerAAA Client

(Re-)Association Request

(Re-)Association Response

802.11i/ EAP Authentication

Access-Accept

(Keying info + tunnel)

Associate STA to VLAN per AAA

EAP-Success

4 way handshake

Action Frame (QoS Map Request)



• “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?

January 2007


Slide 9

doc.: IEEE 802.11-07/0025r1

Submission

Agenda

• Background



• Motion

January 2007


Slide 10

doc.: IEEE 802.11-07/0025r1

Submission

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

January 2007


Slide 11

doc.: IEEE 802.11-07/0025r1

Submission

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

STA2 STA3STA4

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 #1QoS Map Set #1QoS Map Set #1

Solution Statement (Cont’d) – Broadcast Solution

January 2007


Slide 12

doc.: IEEE 802.11-07/0025r1

Submission

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.

OrderSize (octets)

Description

1 1 Element ID. TBD

2 1 Length

3 2 Map ID



5+n-2 2 DSCP exception element #n (optional)










January 2007


Slide 13

doc.: IEEE 802.11-07/0025r1

Submission


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.

January 2007


Slide 14

doc.: IEEE 802.11-07/0025r1

Submission


STA AP AAA Cl i ent AAA Server

(Re- )Associ at i on Request

(Re- )Associ at i on Response

(Keyi ng i nfo + tunnel )

Access-Accept

802. 11i / EAP Authenti cat i on

EAP-Success

Associ ate STA to VLAN per AAA

4 way handshake

QoS Map Request

QoS Map Confi gure(QoS Map Set(Map I D))

QoS Map Confi gure ( new QoS Map Set(Map I D))

Broadcast

modification to figure STA QoS Map determination sequence when broadcast is used

January 2007


Slide 15

doc.: IEEE 802.11-07/0025r1

Submission

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

January 2007


Slide 16

doc.: IEEE 802.11-07/0025r1

Submission

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.


January 2007


Slide 17

doc.: IEEE 802.11-07/0025r1

Submission

STA AP AAA Cl i ent AAA Server

(Re- )Associ at i on Request

(Re- )Associ at i on Response

(Keyi ng i nf o + tunnel )

Access-Accept

802. 11i / EAP Authenti cat i on

EAP-Success

Associ ate STA to VLAN per AAA

4 way handshake

QoS Map Request

QoS Map Confi gure(QoS Map Set, mul t i cast address)

QoS Map Confi gure(new QoS Map Set)

Mul t i castsend to the mul t i cast address

modification to figure STA QoS Map determination sequence when multicast is used


January 2007


Slide 18

doc.: IEEE 802.11-07/0025r1

Submission

• 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

January 2007


Slide 19

doc.: IEEE 802.11-07/0025r1

Submission

Agenda

• Background



• Motion

January 2007


Slide 20

doc.: IEEE 802.11-07/0025r1

Submission

Motion

• Move to accept the proposed changes (in red).

• Moved:

• Seconded:

• Result: (for-against-abstain)

Documents

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