1. Requirements for Network Selection
January 2005
doc.: IEEE /0029r0
January 2005
Requirements for Network Selection
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
Eleanor Hepworth, Siemens Roke Manor
Eleanor Hepworth, Siemens Roke Manor

2. January 2005
doc.: IEEE /0029r0
January 2005
Abstract
This presentation outlines some initial requirements associated with network selection for users presented with a choice of IEEE hotspots.
Eleanor Hepworth, Siemens Roke Manor
Eleanor Hepworth, Siemens Roke Manor

3. January 2005
The Problem
As WLAN hotspots proliferate, users are presented with more choice
Each choice potentially has different capabilities that will effect the user
How does the user decide which hotspot to attempt to authenticate with?
Need to base decision on more than just signal strength
Eleanor Hepworth, Siemens Roke Manor

4. The Problem (part II) PAWLAN presents some unique issues:
January 2005
The Problem (part II)
PAWLAN presents some unique issues:
Operators want to offer access to roamed users
Operators would like to offer new user sign up services
Operators want some degree of control over their users
Operators want to charge
From the user perspective, it is useful to discover information about operator policy up front
Need to support “Network Selection”
Eleanor Hepworth, Siemens Roke Manor

5. January 2005
Definitions
From :
The process by which a mobile terminal collects appropriate information and selects a L2 link (out of possibly many) for higher layer communication is called Network Selection.
Eleanor Hepworth, Siemens Roke Manor

6. Top-Level Requirements
January 2005
Top-Level Requirements
The user should be able to select the point of attachment based on information about the network characteristics.
This should be possible both in the case where the user already has an association with a network, and when they do not (i.e. pre-association).
The service provider should be able to advertise point of presence and service offerings to their users.
Eleanor Hepworth, Siemens Roke Manor

7. Scope In-scope: Out-of-scope: Unaffected: To-be-determined:
January 2005
Scope
In-scope:
transport of information to the user over IEEE technology
Out-of-scope:
definition of information transported
mechanisms to populate information in the hotspot
Unaffected: ?
To-be-determined:
relationship with with regard to information models and transport requirements
Eleanor Hepworth, Siemens Roke Manor

8. Transport Requirements
January 2005
Transport Requirements
Can also identify a number of desirable features for the transport solution:
Scalable; there are space constraints on some of the transport options
Backwards compatible; any mechanism must be backwards compatible with current networks
Security is not a requirement (or is it?)
Should these be specified in the requirements document, or are they part of the selection criteria?
Eleanor Hepworth, Siemens Roke Manor

9. January 2005
Conclusion
Initial thoughts on some more formal requirements for network selection
What are the next steps?
Eleanor Hepworth, Siemens Roke Manor