Location Capability Negotiation

Slides:



Advertisements
Similar presentations
Doc.: IEEE /1672 STA Provided Location November 2006 Donghee Shim, et alSlide 1 STA Provided Location Notice: This document has been prepared.
Advertisements

Doc.: IEEE /0041r1 AP Location Capability January 2007 Donghee Shim et alSlide 1 AP Location Capability Notice: This document has been prepared.
FBMS Termination Date: Name Compay Address Phone
Beacon Measurement on Pilot Frames
LB84 General AdHoc Group Sept. Closing TGn Motions
LB84 General AdHoc Group Sept. Closing TGn Motions
[ Interim Meetings 2006] Date: Authors: July 2005
Resource Request/Response Discussion
IEEE White Space Radio Contribution Title
Emergency Call number support
London TGu Motions Authors: January 2007 Date: Month Year
LB73 Noise and Location Categories
LB73 Noise and Location Categories
Waveform Generator Source Code
TGu Closing Report Date: Authors: November 2005
TGp Closing Report Date: Authors: July 2007 Month Year
Attendance and Documentation for the March 2007 Plenary
[ Policies and Procedure Summary]
Miscellaneous Updates
Motion to accept Draft p 2.0
Protected SSIDs Date: Authors: March 2005 March 2005
[place presentation subject title text here]
Descriptive Language Usage in TGv
TGp Motions Date: Authors: November 2005 Month Year
TGp Closing Report Date: Authors: March 2006 Month Year
Emergency Call Motion Date: Authors: January 2006
TGp Closing Report Date: Authors: May 2007 Month Year
AP Location Capability
TGp Closing Report Date: Authors: March 2006 Month Year
Reflector Tutorial Date: Authors: July 2006 Month Year
CID#102 - Channel Allocation for P2P
TGv Redline D0.07 Insert and Deletion
TGv Redline D0.06 Insert and Deletion
TGu Closing Report Date: Authors: September 2005
ADS Study Group Mid-week Report
IEEE P Wireless RANs Date:
Protection Assurance Method
Attendance for November 2006
TGu-changes-from-d0-01-to-d0-02
LB73 Noise and Location Categories
Extended Channel Switch Announcements
TGy draft 2.0 with changebars from draft 1.0
TGv Redline D1.04-D1.0 Insert and Deletion
TGv Redline D0.10 Insert and Deletion
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
Redline of draft P802.11w D2.2 Date: Authors:
Document Motions Date: Authors: November 2005 November 2005
TGp Closing Report Date: Authors: March 2007 Month Year
Off-channel selection
TGu-changes-from-d0-02-to-d0-03
[ Policies and Procedure Summary]
Proposed changes to the v Draft
Beamforming and Link Adaptation Motions
Path Selection and Path Switch Mechanism
Limiting GAS State-1 Query Response Length
STA Location for emergency call support in SSPN interface
Motion to go to Letter Ballot
EC Motions – July 2005 Plenary
TGu-changes-from-d0-04-to-d0-05
Suggested comment resolution on ATIM window parameter
TGu-changes-from-d0-03-to-d0-04
TGu Motions Date: Authors: May 2006 May 2006
Non-AP STA Location Capability
Reserve Option Contradiction
Extended Channel Switch Announcements
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
TGr Proposed Draft Revision Notice
E911 Bits Date: Authors: May 2007 Month Year
Location Presentation
TGp Motions Date: Authors: January 2006 Month Year
Presentation transcript:

Location Capability Negotiation Month Year doc.: IEEE 802.11-yy/xxxxr0 November 2006 Location Capability Negotiation Authors: Date: 2006-11-08 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.kerry@philips.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 November 2006 Abstract This presentation provides a mechanism for the STA and the Network to negotiate location capability to position the STA. 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 determine next steps. Donghee Shim, et al John Doe, Some Company

Current Location Proposal November 2006 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’ November 2006 Current Location Proposal – cont’ Based on the normative texts in 802.11v draft, following can be deduced STA-assisted positioning is supported such that AP collects measurement data provided by the STA and calculates the location of STA Network-assisted positioning can be also supported such that STA can calculate its location based on measurement of time of arrival, however, it is not explicitly specified (timing measurement in the Probe Response message implicitly implies this capability) STA-based positioning seems to be not supported Various positioning technologies have been considered and would be considered, however, there is no specific handshake to negotiate the location capabilities of the STA and the Network to position the STA Determining the positioning method before exchanging positioning related frames would be better Donghee Shim, et al

November 2006 Thoughts There is no exact way of negotiation of positioning method between the STA and the AP Currently, STA-assisted positioning and STA-based positioning are supported However, there is no capability to indicate the capability of STA such as STA-assisted positioning supported, STA-based positioning supported, or both supported or preferred one (sometimes the STA can indicate STA-assisted positioning preferred or STA-based positioning preferred) or autonomous mode (e.g. autonomous GPS) Addition of capability parameters in location service parameters in the Presence Configuration Request frame can be considered Addition of location service parameters including capability parameters in the Presence Configuration Response can be considered to indicate positioning method desired by the AP Donghee Shim, et al

Location Capability Negotiation November 2006 Location Capability Negotiation STA can indicate its location capability AP STA Presence Configuration Request (…, Location Capability Parameters Element, …) STA capabilities is included in Location Capability Parameters Element Donghee Shim, et al

Location Capability Negotiation (cont’) November 2006 Location Capability Negotiation (cont’) AP can indicate its location capability AP STA Presence Configuration Response (…, Location Capability Parameters Element, …) AP capabilities is included in Location Capability Parameters Element Donghee Shim, et al

Location Capability Parameters Element November 2006 Location Capability Parameters Element Identifier Field Name 1 STA based only 2 STA assisted only 3 STA based preferred 4 STA assisted preferred 5 STA based and STA assisted 6 Autonomous GPS 7 - 254 Reserved 255 Vendor Specific Donghee Shim, et al

Proposal : Location Capability November 2006 Proposal : Location Capability Negotiation of Location Capability of STA and AP Provides available positioning capability of the STA and the AP to each other With Location Capability Parameters Element in Presence Configuration Request and Presence Configuration Response Upon receiving the STA’s location capabilities, the AP can indicate the determined positioning method to be used Donghee Shim, et al

November 2006 Motion Move to have authors draft normative text for potential inclusion into TGv draft Moved: Seconded: Donghee Shim, et al