TGu Requirements Check

Slides:



Advertisements
Similar presentations
Proposal for SSPN Interface Cluster
Advertisements

Network Sharing Architecture
[ Interim Meetings 2006] Date: Authors: July 2005
Emergency Call number support
TGu/TGv Joint Session Date: Authors: July 2005 July 2005
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
Attendance and Documentation for the March 2007 Plenary
3GPP Extended Date: Authors: July 2005 July 2005
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
TGp Motions Date: Authors: November 2005 Month Year
TGp Closing Report Date: Authors: March 2006 Month Year
Emergency Call Motion Date: Authors: January 2006
TGu-changes-from-d0-02-to-d0-03
TGu Motions Date: Authors: September 2006 September 2006
TGu Requirements Change Motion
Proposal for User Plane Cluster
Proposed Changes to Requirements
JTC1 Ad Hoc Mid-week Report
TGu Closing Report Date: Authors: July 2006 July 2006
R8E4 and XML Date: January 12th 2006 Authors: January 2006
TGp Closing Report Date: Authors: March 2006 Month Year
Reflector Tutorial Date: Authors: July 2006 Month Year
TGv Redline D0.07 Insert and Deletion
TGu Timeline Date: Authors: January 2005 January 2005
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
ADS Study Group Mid-week Report
Protection Assurance Method
Authentication Cluster
TGu-changes-from-d0-01-to-d0-02
IEEE “ Requirements” Date: Authors:
Secure Network Selection
QoS in WLAN Interworking
Authentication Cluster
TGy draft 2.0 with changebars from draft 1.0
TGv Redline D0.10 Insert and Deletion
Proposed Changes to Requirements
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
Document Motions Date: Authors: November 2005 November 2005
Proposed Changes to Requirements
TGu-changes-from-d0-02-to-d0-03
3GPP2 Liaison Report Date: Authors: May 2006 May 2006
TGu Motions Date: Authors: May 2006 May 2006
STA Location for emergency call support in SSPN interface
Motion to go to Letter Ballot
TGu-changes-from-d0-04-to-d0-05
for video transmission, Status
Location Capability Negotiation
Transition Nowhere Date: Authors: Sept 2005 Sept 2005
Requirement Motions Date: Authors: July 2005 July 2005
TGu Closing Report Date: Authors: November 2006
TGu-changes-from-d0-03-to-d0-04
TGu Motions Date: Authors: May 2006 May 2006
MAC Anonymity Requirements Motion
New User Plane Requirement
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
TGu Motions Date: Authors: September 2006 September 2006
Proposal for User Plane Support for QoS Mapping
TGu Motions Date: Authors: March 2006 March 2006
TGp Motions Date: Authors: January 2006 Month Year
Presentation transcript:

TGu Requirements Check Month Year doc.: IEEE 802.11-yy/xxxxr0 November 2006 TGu Requirements Check Date: 2006-11-16 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>. Necati Canpolat, Intel Corporation John Doe, Some Company

Month Year doc.: IEEE 802.11-yy/xxxxr0 November 2006 Abstract This document provides verification on TGu requirements coverage in the confirmed proposals and identifies the open issues. Necati Canpolat, Intel Corporation John Doe, Some Company

Overview TGu has primarily 5 groups of requirements namely: Month Year doc.: IEEE 802.11-yy/xxxxr0 November 2006 Overview TGu has primarily 5 groups of requirements namely: Network Selection MIH Support Online Enrolment Emergency Call Support SSPN interfaces Each one of the above requirement has also sub entries. We have 5 confirmed proposals that overall cover the requirements however, some of the sub items have not been addressed. The purpose of this review is to highlight the ones that we need to address and bring a closure to them Necati Canpolat, Intel Corporation John Doe, Some Company

Network Selection Cluster Month Year doc.: IEEE 802.11-yy/xxxxr0 November 2006 Network Selection Cluster Reference Requirement Requirement Class R12N1 Define functionality by which a STA can determine whether its subscription to an SSPN would allow it to access a particular 802.11 AN before actually joining a BSS within that 802.11 AN. Proposals must describe their consideration of scalability. Required R12N2 The mechanism described in requirement R12N1 must allow a STA that has multiple credentials with an SSPN to select the correct credentials when authenticating with a Local Network. R12N3 Define functionality to support authentication with multiple SSPNs through a single AP. R12N4 Define functionality by which a STA can determine which interworking services are available before joining a BSS. R12N5 Functionality shall be provided by which APs can advertise (before connection) the charges that will be made for use of the network if connection is authorized based on an SSPN subscription. Not Required – Optional R12N6 Functionality shall be provided by which during the connection process a STA can be informed of the actual charges to be applied to this session. Not Required – Out of Scope R12N7 It should be possible to inform a STA about unbroadcasted SSIDs without causing the STA to probe for each preferred SSID. Not Required – Complete R12N8 Define functionality by which the STA is able to determine what online enrolment (also called online subscription) methods are supported by the local network. Optional Addressed NOT addressed Optional/out of scope Necati Canpolat, Intel Corporation John Doe, Some Company

SSPN Interface Cluster Month Year doc.: IEEE 802.11-yy/xxxxr0 November 2006 SSPN Interface Cluster Reference Requirement Requirement Class R12S1 Define the Authorization Information (originated from the SSPN) that shall be provided to the MAC and associated functionality. Required R12S2 Define how the information defined in R12S1 will be used. R12S3 Define functionality by which the information defined in R12S1 can be modified (by the SSPN). Not Required – Optional R12S4 Make accessible accounting information for transfer to the SSPN. This shall include information about accepted TSPECs, their duration, and about actual traffic flows. Not Required – Out of Scope Necati Canpolat, Intel Corporation John Doe, Some Company

MIH Support November 2006 Necati Canpolat, Intel Corporation Reference Requirement Requirement Class R12H1 Provide a mechanism to support Media Independent Handoff capability. Required Necati Canpolat, Intel Corporation

Emergency Call Support November 2006 Emergency Call Support Reference Requirement Requirement Class R12I1 Define IEEE 802.11TM functionality which would be required to support an Emergency Call (e.g. E911) service as part of an overall, multi-layer solution. Specifically: Capability Advertisement and Authentication issues Required R12I2 Define functionality by which Aps can provide information which will enable a STA to determine whether or not roaming to a candidate AP would require re-configuration (automatic or manual) of layer 3 networking. Not Required – Out of Scope Necati Canpolat, Intel Corporation

User Plane Cluster November 2006 Necati Canpolat, Intel Corporation Reference Requirement Requirement Class R12U1 Proposals shall allow a STA (subscription permitting) to access multiple Destination Networks at the same time. Not Required – Optional R12U2 Functionality shall be provided by which traffic destined for a particular Destination Network can be segregated from traffic destined for other Destination Networks. Not Required – Out of Scope R12U3 Provide mapping from external QoS information, e.g. DSCP, to 802.11 specific parameters. Required Necati Canpolat, Intel Corporation

Month Year doc.: IEEE 802.11-yy/xxxxr0 November 2006 Conclusion Overall all requirement clusters have been addressed by the confirmed proposals. Only item R12N8 has not been addressed by any proposal. TGu needs to finalize the decision on R12N8 requirement and move forward. Note: TGu has discussed the above mentioned issue and decided to make this requirement optional. It will also ask 802.21 to provide support for it since it aligns better with 802.21 scope. Necati Canpolat, Intel Corporation John Doe, Some Company

Feedback? November 2006 Month Year doc.: IEEE 802.11-yy/xxxxr0 Necati Canpolat, Intel Corporation John Doe, Some Company