1. Venue Type and Name Assisted Network Selection
January 2007
July 2007
Venue Type and Name Assisted 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
Dave Stephenson, Cisco Systems
Stephenson et al

2. January 2007
July 2007
Abstract
This contribution describes a method for assisting the non-AP STA with network selection by providing venue type and name identification details.
This contribution builds upon Network Type Selection, 07/0759r1
There will be a straw poll at the end of this presentation.
Dave Stephenson, Cisco Systems
Stephenson et al

3. January 2007
July 2007
Overview
TGu’s focus on Network Selection has been with regard to SSPNs
Recently, TGu has begun to address Network Selection for networks which may not deploy an Advertising Server in the DS
Network Type based selection
Includes identifying networks by type: e.g. enterprise, free internet service, intranet only
This presentation explores other parameters which may be helpful to assist an end-user select the desired network
Dave Stephenson, Cisco Systems
Stephenson et al

4. HESSID Information Element with Venue Group/Type field added
January 2007
July 2007
HESSID Information Element with Venue Group/Type field added
Element ID
Length
HESSID
Network Type
Venue Group
Venue Type
Octets: 1 6
Venue Group Code
Venue Group Description
Unspecified 1
Assembly 2
Business 3
Educational 4
Factory and Industrial 5
Institutional 6
Mercantile 7
Residential 8
Storage 9
Utility and Miscellaneous 10
Vehicular 11
Outdoor
12 – 255
Reserved
Venue group descriptions taken from International Building Code
Venue types on next slide
Dave Stephenson, Cisco Systems
Stephenson et al

5. Venue Type Designation
January 2007
July 2007
Venue Type Designation
Dave Stephenson, Cisco Systems
Stephenson et al

6. GAS Native Query: Venue Name
January 2007
July 2007
GAS Native Query: Venue Name
Element ID
(0)
Length
Native Query Info
Octets: 1
Variable
Query Info
Info ID
Capability List
mSSID List 1
Emergency Public Network Access Information 2
Network Authentication Type 3
Venue Name 4
Reserved
Provides the venue name associated with the wireless network. The Venue Name IE may be used in cases where the SSID does not provide sufficient indication of the venue’s name.
Dave Stephenson, Cisco Systems
Stephenson et al

7. GAS Native Query: Venue Name (cont.)
January 2007
July 2007
GAS Native Query: Venue Name (cont.)
Info ID (4)
Length
Status Code
Venue Name
Octets: 1 2
variable
The Info ID field is equal to 4.
The Length field is the length of the Venue Name element and is equal to 2 plus the size of the venue name field.
The Status Code is a 2-octet field with values drawn from Table 23.
The Venue Name field is a UTF-8 formatted field containing the venue’s name and perhaps some related, descriptive text. The maximum length of this field is 256 octets. UTF-8 format shall be per RFC-3629.
Dave Stephenson, Cisco Systems
Stephenson et al

8. January 2007
July 2007
Benefits of Proposal
Many settings (e.g., downtown urban areas) have high numbers of available networks and venue type/name can assist in network selection
The venue type and name can be displayed by a connection manager’s UI on a terminal, thereby helping the user to confidently select the desired network
The venue name may be different than the network name (e.g., SSID = SSPN name while in a coffee shop)
Providing venue type also facilitates endpoint’s modifying their behavior based on where they are, e.g.:
Change alert to vibrate mode while in a movie theater
Look for advertisements while in a mercantile facility
Dave Stephenson, Cisco Systems
Stephenson et al

9. Feedback Questions Should venue type be simplified?
January 2007
July 2007
Feedback Questions
Should venue type be simplified?
Is it worthwhile to identify venue type so that terminals can modify their behavior based on where they are?
Dave Stephenson, Cisco Systems
Stephenson et al

10. January 2007
July 2007
Straw Poll
Is Task Group U supportive of 11-07/2219r0 and interested in having author draft normative text for inclusion into TGu draft?
Dave Stephenson, Cisco Systems
Stephenson et al