1. Wireless Location Date: 2007-07-16 Authors: July 2007 Month Year
doc.: IEEE yy/xxxxr0
July 2007
Wireless Location
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, Cisco Systems
John Doe, Some Company

2. Month Year
doc.: IEEE yy/xxxxr0
July 2007
Abstract
This presentation introduces the requirements for presence technology to provide accurate wireless location and emergency services
The presentation shows how TGv is the only protocol that meets all requirements without significant modification
Thomson, Cisco Systems
John Doe, Some Company

3. 3 Important Presence Requirements
Month Year
doc.: IEEE yy/xxxxr0
July 2007
3 Important Presence Requirements
Capability Advertisement
The ability for the infrastructure and STAs to advertisement their capabilities
Location determination
The ability to control and manage location determination features of wireless devices
Location determination is necessary for reliable and accurate location to be distributed
Location distribution
The ability to distribute location information between wireless infrastructure and wireless STAs
Thomson, Cisco Systems
John Doe, Some Company

4. Capability Advertisement
Month Year
doc.: IEEE yy/xxxxr0
July 2007
Capability Advertisement
Requirement to provide unique capability exchange per STA
Not all STAs will require the same information format…etc
AP must respond to location requests if AP advertises capability
STAs advertise their location capabilities in Beacons, Probe Responses, (Re)Association Requests
Capability information includes
Format (CIVIC, Geo, Location by Reference…etc)
Encoding (Binary, XML…etc)
Resolution
Capable of providing
self-location
remote-location
Thomson, Cisco Systems
John Doe, Some Company

5. Location Determination Requires…
Month Year
doc.: IEEE yy/xxxxr0
July 2007
Location Determination Requires…
Reliable and timely communication of frames from a STA
STA frames must be detected close-in-time by multiple APs
Appropriate presence policy applied by APs for all associated STAs
Goal: To provide measurements necessary for high accuracy above “associated AP” accuracy
Thomson, Cisco Systems
John Doe, Some Company

6. Typical Location Determination Messages
Month Year
doc.: IEEE yy/xxxxr0
July 2007
Typical Location Determination Messages
Thomson, Cisco Systems
John Doe, Some Company

7. Floor Level Accuracy Requirement
Month Year
doc.: IEEE yy/xxxxr0
July 2007
Floor Level Accuracy Requirement
Determining correct floor is required for in-building presence and emergency services
Within buildings devices (e.g. phones) can associate to any AP on any floor
Depends on RF Coverage
Phone presence announcements seen on multiple floors
Location determination resolves appropriate floor based on all measurements
Thomson, Cisco Systems
John Doe, Some Company

8. Building Accuracy Requirement
Month Year
doc.: IEEE yy/xxxxr0
July 2007
Building Accuracy Requirement
Determining correct building is required for presence and emergency services
Across buildings: devices (phones) can associate to any AP in any building within RF coverage
Thomson, Cisco Systems
John Doe, Some Company

9. Location Determination Requirements
Month Year
doc.: IEEE yy/xxxxr0
July 2007
Location Determination Requirements
AP Responsibilities
Manages setup of STA presence messages for
Frequency
Stationary and In Motion parameters
Interframe Interval
Timing Measurements
Channel set
Channel Numbers and Regulatory Class
Policy administration
AP can ensure all STAs in BSS conform to presence reporting policies
Can disassociate STA if failure to comply
Additional measurements in 11k such as Measurement Request/Response help location determination
STA Responsibilities
Sends presence messages based on AP control
Presence Messages include:
Radio information including
Antenna gain, Transmit Power, Received RSNI, Antenna ID for Rx and Tx
Timing Measurements
Motion Indication
Thomson, Cisco Systems
John Doe, Some Company

10. Location Distribution Requirements
Month Year
doc.: IEEE yy/xxxxr0
July 2007
Location Distribution Requirements
Secure
Complies with privacy rules around location
Scalable
Enables network to provide accurate location for large number of clients
Timely
Enables network to provide location very close-in-time to emergency events or other location events
Specific
Enables network to provide location specific for a device in the format and options it requires
Thomson, Cisco Systems
John Doe, Some Company

11. Location Distribution: Request Based
Month Year
doc.: IEEE yy/xxxxr0
July 2007
Location Distribution: Request Based
Meets all requirements
Secure
Sent by either AP or non-AP STA in unicast frame with w encryption
Timely
Options for one-shot “On Demand” or event-based “subscription”
Specific
STA can request its own location with options
Format (CIVIC, Geo…etc)
Encoding (Binary, ASCII)
Resolution (AP, XY, Building…etc)
Accuracy Estimate
STA can request the AP’s location
STA can provide it’s own location if capable of self-determination
Scalable
Single message when required
Avoids continuous transmission of broadcasts or unicasts
Thomson, Cisco Systems
John Doe, Some Company

12. Location Distribution: Broadcast
Month Year
doc.: IEEE yy/xxxxr0
July 2007
Location Distribution: Broadcast
Sent by APs in beacon or probe response
Does not meet all requirements
Not secure
Can be seen by any non-associated STAs, security risk?
For general location distribution, privacy is required
For Emergency Services location distribution, no privacy may be acceptable
Not timely
Broadcast has to be scheduled very infrequently
Not scalable
No way of knowing which clients are using location or not
Adds load to the infrastructure to provide location when unclear who and what is using it
Wastes Over-The-Air bandwidth
Not specific
Broadcast relates to AP position not STAs
Thomson, Cisco Systems
John Doe, Some Company

13. TGv Meets Requirements
Month Year
doc.: IEEE yy/xxxxr0
July 2007
TGv Meets Requirements
Requirement
TGv
LLDP-MED1
Capability Advertisement
Provides per STA capability advertisement
None
Location Determination
Provides control and high accuracy
Location Distribution
Provides Secure, Timely, Scalable, Specific
Provides broadcast
1: ANSI/TIA-1057 LLDP-MED
Thomson, Cisco Systems
John Doe, Some Company

14. Month Year
doc.: IEEE yy/xxxxr0
July 2007
Final Thoughts
Location object format is common across TGv and other protocols
Wireless location requires a protocol that fits a dynamic physical environment
Supporting one protocol for location determination and another for distribution complicates the infrastructure and the client
Location requirements for wireless MAN systems are equally, if not more, challenging
Location security and privacy critical issues
TGv meets all requirements for wireless location and emergency services
Thomson, Cisco Systems
John Doe, Some Company

15. Backup July 2007 Month Year doc.: IEEE 802.11-yy/xxxxr0
Thomson, Cisco Systems
John Doe, Some Company

16. Presence Message Flow July 2007 Month Year doc.: IEEE 802.11-yy/xxxxr0
Thomson, Cisco Systems
John Doe, Some Company

17. On Demand Location Distribution
Month Year
doc.: IEEE yy/xxxxr0
July 2007
On Demand Location Distribution
Thomson, Cisco Systems
John Doe, Some Company

18. Subscription Location Distribution
Month Year
doc.: IEEE yy/xxxxr0
July 2007
Subscription Location Distribution
Thomson, Cisco Systems
John Doe, Some Company

19. Broadcast Location Distribution
Month Year
doc.: IEEE yy/xxxxr0
July 2007
Broadcast Location Distribution
Thomson, Cisco Systems
John Doe, Some Company

20. Wide Area Wireless Location
Month Year
doc.: IEEE yy/xxxxr0
July 2007
Wide Area Wireless Location
Wide area wireless AP location may be several miles from location of client
Using AP location inappropriate
Location determination must use ranging…etc.
Thomson, Cisco Systems
John Doe, Some Company