1. E911 Bits Date: 2007-05-14 Authors: May 2007 Month Year
doc.: IEEE yy/xxxxr0
May 2007
E911 Bits
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
Thomson et al, Cisco Systems
John Doe, Some Company

2. Month Year
doc.: IEEE yy/xxxxr0
May 2007
Abstract
This presentation introduces a solution to the issue of advertising location service capability for e911
Thomson et al, Cisco Systems
John Doe, Some Company

3. May 2007
Recap: The Problem
A method is required for a non-AP STA to determine that an AP provides location service for e911 prior to association
This is required to reduce the delay finding a suitable AP to associate with for e911 call
Currently an AP can advertise it supports location “capabilities” but may not provide location “service” at e911 call time
Some deployments will need civic location format (e.g., consumer, NENA) and some want geospatial format (e.g., carriers, cellular operators)
Regulatory requirements for location service are not defined yet, so we are trying to anticipate what regulators will require so we can bring emergency services to market sooner.
Thomson et al, Cisco Systems

4. Recap: Advertisement Options
May 2007
Recap: Advertisement Options
Option #1: Use the existing Presence bit in Capabilities IE
If an AP supports presence then it will require the administrator to define CIVIC and/or Geo address
Option #2: Use a separate Presence + e911 Location Service Bit in Capabilities IE
If an AP supports Basic Presence then the Presence bit is set
If an AP supports e911 location service then the e911 Location Service bit is set
Option #3 Use a separate Presence + e911-CIVIC Location Bit + e911-Geo Location Bit in Capabilities IE
If an AP supports e911 CIVIC then it sets the e911-CIVIC Location Bit
If an AP supports e911 Geo then it sets the e911-Geo Location Bit
Option #4: Use Presence Parameters IE and require an AP to set location format supported in the IE
Thomson et al, Cisco Systems

5. May 2007
March Straw Polls
Should the TGv solve this problem of e911 location advertisement?
Yes: No: 0
Which Option is preferred? (choose one category only)
Option #1: 0
Option #2: 3
Option #3: 17
Option #4: 7
Other/Don’t care: 4
Thomson et al, Cisco Systems

6. May 2007
Solution
Add 2 new bits to Wireless Network Management Capabilities field
Bit 7: E911 CIVIC Location
The E911 CIVIC bit is set to 0 and ignored when the Presence bit is set to 0.
The E911 CIVIC bit set to 1 indicates that the AP has its location defined in CIVIC format, as described by the Location Descriptor sub-element in , and will provide it to the non-AP STA upon request.
The E911 CIVIC bit set to 0 indicates that the AP does not have its location defined in CIVIC format or is not capable to provide CIVIC format location to the non-AP upon request.
Bit 8: E911 GEO Location
The E911 Geo bit is set to 0 and ignored when the Presence bit is set to 0.
The E911 Geo bit set to 1 indicates that the AP has its location defined in Geo format, as described by the Location Descriptor sub-element in and will provide it to the non-AP STA upon request.
The E911 Geo bit set to 0 indicates the AP does not have its location defined in Geo format or is not capable to provide Geo format location to the non-AP upon request
Thomson et al, Cisco Systems

7. May 2007
Motion
Move to include normative text in document v-normative-text-presence-e911-clarification.doc into the TGv draft.
Mover:
Seconder:
Result:
Thomson et al, Cisco Systems