doc.: IEEE /0763r1 Submission July, 2008 Hu JunlingSlide 1 Location Coordinates Inquiry 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, 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. Date: Authors:

doc.: IEEE /0763r1 Submission July, 2008 Hu JunlingSlide 2 Abstract For a navigation application, coordinates( longitude, latitude, altitude) information is more convenient than civic address( city,street, building, room…) information. This document proposes to add a measurement type of Measurement Request element for a STA requesting location coordinates of itself or remote target and its responding report.

doc.: IEEE /0763r1 Submission July, 2008 Hu JunlingSlide 3 Background (1/2) In p802.11v draft 3.0, Location Civic Request is used to request for civic address information and Location Identifier Request is used to request for an indirect reference in URI format for secure location inquiring. Two of above Requests belong to Measurement Request as a measurement type. Corresponding Report types have been defined for Measurement Report also. They are Location Civic Report and Location Identifier Report.

doc.: IEEE /0763r1 Submission July, 2008 Hu JunlingSlide 4 Background (2/2) The Location Civic Report element format is Location Accuracy X-estimate Location Accuracy Y-estimate Location Accuracy Z-estimate Civic Location –The Location Accuracy estimates relative to Civic Location. –The Civic Location is a readable text for geographical address. The Location Identifier Report element format is Public Identifier URI –The Public Identifier URI confirms the validity of the location estimate to an external agent when a STA forwards a location estimate to that agent.

doc.: IEEE /0763r1 Submission July, 2008 Hu JunlingSlide 5 Problem Civic address information( city, street, building, room…)is very good for emergency service, but it is not convenient for navigation service. For a WiFi handset with a function of navigation, what kind of data will it need for navigation function? Coordinates information(longitude, latitude, altitude), just as GPS system. The handset can get a civic location from the infrastructure and show it to user, but also it can get a civic location from the map in itself after it got a coordinates information. The civic location information of the map in the handset may be not so rich that the handset can indicate the location on the map according to received civic location.

doc.: IEEE /0763r1 Submission July, 2008 Hu JunlingSlide 6 A new measurement type of Location Coordinates Request/Report is proposed to be added to Measurement Request/Report. Following is a sample for Measurement Request. Proposition NameMeasurement Type Measurement Use …… Location Civic request11Radio Resource Measurement Location Identifier request12Radio Resource Measurement Location Coordinates request13Radio Resource Measurement Reserved … Table 7-29—Measurement Type definitions for measurement requests

doc.: IEEE /0763r1 Submission July, 2008 Hu JunlingSlide 7 Fields of Location Coordinates Request/Report The field format of Location Coordinates Request is same as Location Civic Request which is shown as follow. Location SubjectLocation Service Interval UnitsLocation Service Interval –The Location Subject indicates that a STA request local or remote location. The field format of Location Coordinates Report is similar as Location Civic Report which is shown as follow. Location Accuracy X-estimate Location Accuracy Y-estimate Location Accuracy Z-estimate LongitudeLatitudeAltitude –The definition of Location Accuracy parameters are same as Location Civic Report. –Longitude and latitude are signed long integer in 4 octets length with a unit of degree. The sign indicates the west / east of longitude or north / south of latitude. –Altitude is signed short integer in 2 octets length with a unit of 1 meter. Or, the altitude is 4 octets length with the unit 0.1 meter. The sign indicate higher or lower than sea level.

doc.: IEEE /0763r1 Submission July, 2008 Hu JunlingSlide 8 Straw Poll Do you think coordinates information is better for navigation service than civic information? -Yes -No -Don’t know