May 2007 doc IEEE 802 11 070667 r

May 2007 doc. : IEEE 802. 11 -07/0667 r 0 E 911 Bits Date: 2007 -05 -14 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: // ieee 802. 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@ok -brit. 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>. Submission 1 Thomson et al, Cisco Systems

May 2007 doc. : IEEE 802. 11 -07/0667 r 0 Abstract This presentation introduces a solution to the issue of advertising location service capability for e 911 Submission 2 Thomson et al, Cisco Systems

May 2007 doc. : IEEE 802. 11 -07/0667 r 0 Recap: The Problem • A method is required for a non-AP STA to determine that an AP provides location service for e 911 prior to association – This is required to reduce the delay finding a suitable AP to associate with for e 911 call • Currently an AP can advertise it supports location “capabilities” but may not provide location “service” at e 911 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 802. 11 emergency services to market sooner. Submission 3 Thomson et al, Cisco Systems

May 2007 doc. : IEEE 802. 11 -07/0667 r 0 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 + e 911 Location Service Bit in Capabilities IE • If an AP supports Basic Presence then the Presence bit is set • If an AP supports e 911 location service then the e 911 Location Service bit is set • Option #3 Use a separate Presence + e 911 -CIVIC Location Bit + e 911 -Geo Location Bit in Capabilities IE • If an AP supports e 911 CIVIC then it sets the e 911 -CIVIC Location Bit • If an AP supports e 911 Geo then it sets the e 911 -Geo Location Bit • Option #4: Use Presence Parameters IE and require an AP to set location format supported in the IE Submission 4 Thomson et al, Cisco Systems

May 2007 doc. : IEEE 802. 11 -07/0667 r 0 March Straw Polls • Should the TGv solve this problem of e 911 location advertisement? – Yes: 33 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 Submission 5 Thomson et al, Cisco Systems

May 2007 doc. : IEEE 802. 11 -07/0667 r 0 Solution • • • Add 2 new bits to Wireless Network Management Capabilities field Bit 7: E 911 CIVIC Location – – – Submission Bit 8: E 911 GEO Location – – The E 911 CIVIC bit is set to 0 and ignored when the Presence bit is set to 0. The E 911 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 7. 3. 2. 54. 9, and will provide it to the non -AP STA upon request. The E 911 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. – 6 The E 911 Geo bit is set to 0 and ignored when the Presence bit is set to 0. The E 911 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 7. 3. 2. 54. 9 and will provide it to the non-AP STA upon request. The E 911 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

May 2007 doc. : IEEE 802. 11 -07/0667 r 0 Motion • Move to include normative text in document 11 -07 -0298 -01 -000 v-normative-text-presence-e 911 clarification. doc into the TGv draft. Mover: Seconder: Result: Submission 7 Thomson et al, Cisco Systems