1. Proposal for User Plane Cluster
January 2006
doc.: IEEE /1xxxr0
January 2006
Proposal for User Plane Cluster
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
Hong Cheng, Panasonic
Hong Cheng, Panasonic

2. January 2006
doc.: IEEE /1xxxr0
January 2006
Abstract
This document contains initial proposals to cover the User Plane Cluster of technical requirements of TGu.
Hong Cheng, Panasonic
Hong Cheng, Panasonic

3. January 2006
doc.: IEEE /1xxxr0
January 2006
WiNOT consortium
This presentation is made on behalf of the WiNOT (Wireless NetwOrking Technology), comprising:
Intel
Nokia
Siemens
Panasonic
STMicroeletronics
BenQ
Cingular
T-Mobile
Hong Cheng, Panasonic
Hong Cheng, Panasonic

4. User Plane Cluster Required: Optional: Out of scope:
January 2006
User Plane Cluster
Required:
R8U3: Provide mapping from external QoS information, e.g. DSCP, to IEEE specific parameters
Optional:
R8U1: Proposals shall allow a STA (subscription permitting) to access multiple Destination Networks at the same time
Out of scope:
R8U2: Functionality shall be provided by which traffic destined for a particular Destination Network can be segregated from traffic destined for other Destination Networks
Hong Cheng, Panasonic

5. Proposal for R8U3 (Required)
January 2006
Proposal for R8U3 (Required)
IEEE802.11e control parameters would not be understood by the entity outside of MAC. Therefore, QoS requirements from application or SSPN would not be in the 11e format.
This could be also showing how the authorization information could be used by the MAC, as stated by R8S3
At the same time, local AN also needs to adjust the parameters according to network status.
Certain guideline on how a mapping could be done is necessary to result in a consistent interworking experience
For prioritized control
Mapping from 802.1p type of priority to AC types
Mapping of DSCP code points to AC types
Mapping of the stream direction information
Mapping of service type to whether certain acknowledge type should be used
For parameterized type of control
Mapping of SDP type of requirements to the TSPEC parameters
Mapping of Integrated Service parameters to TSPEC
e.g. reference to RFC2815
Hong Cheng, Panasonic

6. Proposal for R8U1 (Optional)
January 2006
Proposal for R8U1 (Optional)
L2 support is necessary for traffic segregation since L3 solution may not be reliable
L3 address spoofing
a local L3 address is not bound to the user identity
L2 has a better control of the data flow since it could be done at the first point of contact
Anything beyond the AP is already network side
Two type of methods
Terminal based VLAN. This requires VLAN tags to be signaled to the STA by AP MAC (could be part of the authorization information). This requires the STA to fully corporate with the network side control. However, can the STA be trusted? (It should comply. Otherwise it may risk lost service guarantee)
Network side filtering. This means the AP will need to filter out the traffic into correct VLAN or some tunnel accordingly. It requires the STA to signal the filter information to the AP MAC. It could be part of the TSPEC Filter information. However, this means the TSPEC Filter Information should be passed as part of the authorization process.
Hong Cheng, Panasonic

7. Proposal for R8U2 (Out of scope)
January 2006
Proposal for R8U2 (Out of scope)
No proposal
Hong Cheng, Panasonic

8. References 11-05-0822-08-000u-suggested-tgu-requirements January 2006
Hong Cheng, Panasonic