Non-AP STA Location Capability Month Year doc.: IEEE 802.11-yy/xxxxr0 January 2007 Non-AP STA Location Capability Authors: Date: 2006-01-13 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@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>. Donghee Shim et al John Doe, Some Company

Month Year doc.: IEEE 802.11-yy/xxxxr0 January 2007 Abstract This presentation provides remaining issues for non-AP STA location capability for location/presence services No change on currently defined architectures and frames for location services support is required. No specific location determination mechanism is defined or required. At the end of the presentation, there will be a motion to include proposed normative text in the 11v draft. Donghee Shim et al John Doe, Some Company

Current Location Proposal January 2007 Current Location Proposal Presence Configuration Procedure Periodic exchange of frames for the purpose of collecting the necessary data to determine location by setting Presence Parameter information in Beacon, Probe Response or Presence Configuration Request A STA periodically transmits Presence Request frame AP collects data to position the STA Establishing a location service that periodically provides location estimation by setting Presence Parameter information in Beacon, Probe Response or Presence Configuration Request (1) AP periodically transmits Presence Response frame to provide location data to the STA Presence Request Procedure Advertise STA its Presence Request STA its own location to the AP Request AP location Provide data to AP for the purpose of locating the STA Presence Response Procedure The Presence Response frame, Beacon and Probe Response frames provide presence reporting parameters to the STA by AP A Presence Response frame may be sent to provide location information to a STA or exchange frames for location calculating purposes Donghee Shim et al

Current Location Proposal – cont’ January 2007 Current Location Proposal – cont’ Based on the normative texts in 802.11v draft, It is clearly stated that in the current 802.11v draft as “A Presence Request frame may be sent by a STA when the STA is not associated to an AP” in 11.15.4.1 Presence Request procedures.” However, the location descriptor to indicate non-AP STA location capability is only included in the Association / Reassociation request frames Donghee Shim et al

January 2007 Thoughts Current presence framework provides the mechanism to configure the STA to periodically transmit Presence Request or Response frames for the purpose of collecting data to locate the client or for the purpose providing location data. The association / reassociation frame can carry the location capability with Location Descriptor in the Presence Parameters The Presence Request frame can be sent without any association to the AP from the STA. However, current mechanism only allows the STA to include Location Descriptor in the Presence Parameters in the Presence Request frame to invoke Presence related procedures (to request its own location information or to provide data for the purpose of locating the STA) Then, Location Descriptor can be included in the Presence Request to indicate the location capability of the STA even if there is no specific presence/location related requests to be sent to the AP Also Location Descriptor can be added in the Presence Configuration Request to indicate the location capability of a STA In addition, Location Data can be included in the Presence Request and Presence Configuration Request to inform non AP STA’s location to the AP Donghee Shim et al

Non-AP STA Location Capability Proposal January 2007 Non-AP STA Location Capability Proposal Following texts are proposed to be added in the 11v draft to allow AP to send its location capability to the STAs in the Presence Request procedures, Presence Configuration procedures, Presence advertising procedures, respectively A non AP STA that supports presence capability may send an Association Request, Reassociation Request or Presence Request frame to provide its own location information and location capability. The non AP STA shall include a Location Descriptor element in Presence Parameters information element in an Association Request or Reassociation Request frame to provide its location capability. The location description value of 2 “CIVIC Preferred” or 3 “GEO Preferred” indicates that theSTA is capable of supporting both CIVIC and GEO formats, but prefers the indicated format. A non AP STA that supports presence capability may send an Presence Configuration Request frame to provide its own location information and location capability. The non AP STA shall include a Location Descriptor field in an Presence Configuration Request frame to provide its location capability. The location description value of 2 “CIVIC Preferred” or 3 “GEO Preferred” indicates that the STA is capable of supporting both CIVIC and GEO formats, but prefers the indicated format. The non AP STA shall indicate the location resolution it can support with location resolution descriptor element. (This kind of text is also proposed for AP location capability contribution, so we can say just ‘A STA’ instead of ‘A Non AP STA’). A STA may advertise its location information to a peer STA. Advertisement is accomplished by including a Presence Parameters information element in a Beacon, Association Request, Reassociation Request, Presence Request, Presence Configuration Request, Probe Response or Presence Response frame. For the case of a Presence Reponse frame the STA shall set the dialog token field to zero to indicate this frame is not in response to a corresponding Presence Request frame. To advertise, the STA shall include both the Location Descriptor and Location Data elements in the Presence Paramters information element. The STA shall define the Location Descriptor fields as follows. The Location Descriptor shall indicate Local. The Location Format Descriptor, Resolution Descriptor and Encoding Descriptor shall all be set to match the data contained in the Location Data element. Depending on the options defined in the Location Descriptor, the STA may also include the Location Source Identifier element. Donghee Shim et al

Non AP STA Location Capability in Presence Configuration Request January 2007 Non AP STA Location Capability in Presence Configuration Request STA can indicate its location capability AP STA Presence Configuration Request (…, Location Descriptor, Location Data…) Non AP STA’s location capabilities can be included in Location Descriptor field in the Presence Configuration Request frame Non AP STA’s location data can be included in Location Data field in the Presence Configuration Request frame Donghee Shim et al

Non AP STA Location Data in Presence Request January 2007 Non AP STA Location Data in Presence Request STA can indicate its location capability AP STA Presence Request (…, , Location Data…) Non AP STA’s location data can be included in Location Data field in the Presence Request frame Donghee Shim et al

Location Descriptor January 2007 CIVIC 1 GEO 2 CIVIC Preferred 3 Identifier Field Name CIVIC 1 GEO 2 CIVIC Preferred 3 GEO Preferred 4 Not Supported 5 Vendor Specific 6 - 15 Reserved Donghee Shim et al

Proposal : AP Location Capability January 2007 Proposal : AP Location Capability Location Capability of AP Proposes a normative text to allow non-AP STA to send its location capabilities to the STAs with Location Descriptor element in Presence Request or Presence Configuration Request frame Proposes to put the normative text in the proposal 11-07-xxxx-00-000v-normative-text-STA-location-capability based on the proposal in this presentation Donghee Shim et al

January 2007 Motion Move to include normative text in document 11-06-xxxx-00-000v-STA-location-capability changes to the 802.11v into the TGv draft. Mover: Seconder: Donghee Shim et al