1. Location Presentation
Month Year
doc.: IEEE yy/xxxxr0
January, 2006
Location Presentation
Authors:
Date:
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
D. Stanley (Aruba Networks)
John Doe, Some Company

2. Month Year
doc.: IEEE yy/xxxxr0
January, 2006
Abstract
This location solution provides a mechanism for a STA to alert the network of its presence and to receive instructions from the network for providing further alerts. A location determination algorithm is not specified.
D. Stanley (Aruba Networks)
John Doe, Some Company

3. Goals Support a variety of end devices
January, 2006
Goals
Support a variety of end devices
Including devices that cannot calculate their own location
Support multiple location-calculation algorithms
Support multiple location based services
Support a secure mechanism for gathering and providing location data
Support an insecure mechanism reporting presence location
Interoperate with legacy clients
D. Stanley (Aruba Networks)

4. Location Applications
January, 2006
Location Applications
Applications and Services such as asset tracking, emergency services, management of equipment in the field require the ability to locate WLAN devices
Expect growth in all of these applications
As WLAN networks are installed, more and more applications will be added to leverage the deployed network
D. Stanley (Aruba Networks)

5. Approach Introduce the concept of “Presence”
January, 2006
Approach
Introduce the concept of “Presence”
“I am out here” (without defining “here”) rather than “Here I am”
Mechanism provided for exchange of location information, and timing measurements to support location determination methods
Define Presence Information Element
Transport presence information in 4 new Wireless Network Management Action Frames
Prior to association – Presence Notification and Presence Notification Response
Analogous to Probe Request and Probe Response
Not protected
After association – Presence Request and Presence Response
Protected using TGw mechanisms
D. Stanley (Aruba Networks)

6. Presence Parameters Information Element
January, 2006
Presence Parameters Information Element
Element ID
Information Element 1
Presence Reporting Parameters 2
Presence Reporting Channels 3
Timing measurements 4
Radio Information 5
Motion 6
Battery Information 7
Vendor Specific
8-255
Reserved
Elements are optional
D. Stanley (Aruba Networks)

7. Presence Reporting Parameters Element
January, 2006
Presence Reporting Parameters Element
Station-
ary
Interval
Stationary #
Frames
Per
Channel
In-Motion
In-Motion #
Inter
Frame
Triggered
Event
Indication
Data 2 1
Indicates time interval at which presence notification or present reports are to be sent
Separate rates for stationary and in-motion devices
Example: Stationary Interval of 30 minutes, send 5 frames per channel, with an interval of 100milliseconds between frames
Indicates whether the frame was sent due to a triggered event, or as a regularly scheduled event
D. Stanley (Aruba Networks)

8. Presence Reporting Channels Element
January, 2006
Presence Reporting Channels Element
Number of Channels
Channel 1
…Channel n 1
When included in the Beacon, indicates the list of channels on which the AP listens for presence frames
When included in the Presence Notification and Presence Request Frames, indicates the list of channels that the STA sends presence frames on
D. Stanley (Aruba Networks)

9. January, 2006
Beacon Frame Example AP
STA
Beacon ( Presence Parameters Element[ Presence Reporting Parmeters,
Presence Reporting Channels) ]
The combination of a Presence Reporting Parameters element and a Presence Reporting Channels Element broadcast in a beacon allow a device to discover the information required to bootstrap itself for presence reporting prior to association.
D. Stanley (Aruba Networks)

10. Timing Measurements Element
January, 2006
Timing Measurements Element
Timestamp Difference
Received
Timestamp 4 8
Timestamp Difference field contains the time difference in tenths of nanoseconds between the time that the corresponding Presence Notification or Presence Request frame was received from a STA and the time that the corresponding ACK frame was sent to the STA
Received Timestamp contains the time that the corresponding Presence Notification or Presence Request frame was received from a STA
Set to 0 if value not available or provided
Timing measurements element included in Presence Notification response and Presence Response frames.
D. Stanley (Aruba Networks)

11. Location Determination
January, 2006
Location Determination
Example -Time of arrival AP
STA
Unicast Presence Request Sent at T1, received at T2
ACK, sent at T3, Received at T4
Presence Response [ Timing Measurements Element with
Timestamp Difference = (T3-T2) ]
STA can then calculate [ (T4-T1) – (T3-T2)]/2
D. Stanley (Aruba Networks)

12. Radio Information Element
January, 2006
Radio Information Element
Transmit
Power
Antenna ID
Gain
Received RSNI
RCPI 1
The transmit power is the transmit power of the radio transmitting the presence frame.
The antenna gain is the antenna gain of the antenna over which the presence frame is transmitted.
The RSNI value is included in the Presence Notification Response and Presence Response Frames, and indicates the RSNI value for the corresponding received Presence Notification /Presence Request frame.
The RCPI value is included in the Presence Notification Response and Presence Response Frames, and includes the RCPI field, as defined in draft k.
D. Stanley (Aruba Networks)

13. Motion Element January, 2006
Indicator
Location
Configuration
Information
Velocity 1 16
The motion indicator indicates if the STA is stationary, in-motion, beginning or ending motion
Location Configuration Information is as defined in the k draft – longitude, latitude, altitude, azimuth
Velocity contains the speed of the STA, expressed in meters per second
D. Stanley (Aruba Networks)

14. Battery Information Element
January, 2006
Battery Information Element
Battery
Remaining
Age 1 2
Battery Remaining indicates the percentage of battery remaining
Battery Age indicates the calendar days of usage for the battery, specified in days
D. Stanley (Aruba Networks)

15. Presence Action Frames - 1
January, 2006
Presence Action Frames - 1 AP
STA
Presence Notification (Dialog Token, Response Requested, Presence Parameters Element)
Presence Notification can be sent prior to association, similar to probe request
Presence Notification Response (Dialog Token, Timestamp, Presence Parameters Element)
Presence Notification Response can be sent prior to association, similar to probe response
Sent if the Response Requested field is set
D. Stanley (Aruba Networks)

16. Presence Action Frames - 2
January, 2006
Presence Action Frames - 2 AP
STA
Presence Request (Dialog Token, Presence Parameters Element)
Presence Request action frame is sent after association
Presence Response (Dialog Token, Timestamp, Mgt Action Pending, Presence Parameters Element)
Presence Notification Response always sent in response to a Presence Request
The Management Action Pending field indicates that a management action is pending for the destination STA
D. Stanley (Aruba Networks)

17. January, 2006
Motion
Move to include the substantive text in document 06/0009r0 into the TGv draft
Moved:
Seconded:
D. Stanley (Aruba Networks)

18. January, 2006
References
D. Stanley (Aruba Networks)