doc.: IEEE /1021r0 Submission September, 2009 Gabor BajkoSlide 1 LCI and Location Formats 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 /1021r0 Submission September, 2009 Gabor BajkoSlide 2 Location Formats Open Geospatial Consortium (OGC) has created an XML grammar to describe geographical features, called GML RFC5491 defines an XML schema to be carried in IP based protocols (based on GML) –XML is verbose, and not feasible to be carried in link layers 3GPP defined a binary encoding of the shapes defined by OGC – 600.ziphttp:// 600.zip –Binary is a more compact encoding

doc.: IEEE /1021r0 Submission September, 2009 Gabor BajkoSlide 3 Location shapes Point Circle Ellipse Arc Band Polygon … and their equivalent 3D shapes

doc.: IEEE /1021r0 Submission September, 2009 Gabor BajkoSlide 4 Useful Location Shapes in Very common: –Point, to eg describe the location of a fixed STA (AP) –Circle, to eg describe the coverage of an AP –Arc Band, to eg describe the coverage of an AP with directed beam –possibly polygon ?

doc.: IEEE /1021r0 Submission September, 2009 Gabor BajkoSlide 5 LCI LCI has been copy-pasted from RFC3825 and azimuth appended to it RFC3825 uses a 9+25 bit fixed point number for WGS84 coordinates It can only be used to describe circles/ellipses with specific radiuses It can not be used to specify custom location boundaries: eg, it can not specify a location having latitude values [ to ], a full or partial arcband, a polygon, etc. See archive/web/geopriv/current/msg05482.html and related discussion for further detailshttp:// archive/web/geopriv/current/msg05482.html

doc.: IEEE /1021r0 Submission September, 2009 Gabor BajkoSlide 6 RFC3825 update (1) It was agreed in IETF to make an update of RFC3825, for a limited applicability: the update will provide a means to describe a location in a form of a rectangle, by mostly reusing the fields defined in RFC3825 point Uncertainty X Uncertainty Y

doc.: IEEE /1021r0 Submission September, 2009 Gabor BajkoSlide 7 RFC3825 update (2) The update will have a limited applicability –Won’t be able to describe a circle, ellipse, partial or full arcband (triangle), etc, which are very badly needed to describe a location: AP STA AP α

doc.: IEEE /1021r0 Submission September, 2009 Gabor BajkoSlide 8 Way forward LCI defined in k should not be incorporated into the base spec Location representation for should be redesigned Possibly reference the 3GPP document, which is the only binary format of geolocation representation in use across the industry –An LoA could be obtained from 3GPP The issue was discussed in TGv, but it is not in the scope of TGv Is there any formal procedure which on how to update a published spec?