ESW07 Location Formats: Convergence Now or Not at all?

1. ESW07Location Formats:Convergence Now or Not at all? James Winterbottom Andrew Corporation ESW07 10-12 April 2007

2. Required Result • Ultimately location is required by an application. Current applications include: • Routing • Dispatch • Billing • Locations can be expressed in geodetic terms or in terms of a civic address • Ultimately applications seem to receive XML formatted data: • PIDF-LO • GML • MLP

3. Geodetic locations • Binary intermediary formats: • 3GPP Geographical Area Description (GAD) TS-23.032 • RC-3825 and LLDP-MED LCI point representation. • XML representations • GML :- Geoshape profile, other profile • OMA-MLP (based on early GML)

4. Civic Representations • Revised Civic for PIDF-LO • MSAG • Requires validation if it is going to be used for routing purposes. • How is this achieved? • Is it needed for dispatch?

5. Required Shape Types • GAD currently supports: • Point (2d and 3d) • Ellipse • Ellipsoid • Ellipsoid Arc (Arc Band) • Circle • Polygon • MLP supports all of these. • Geoshape supports all these + • Prism (an extruded polygon) • Sphere • The NENA E2 interface only supports • Point (2d and 3d) • Circle • Sphere

6. Velocity and Direction • These can be represented in GML • GAD supports encoding of these attributes also. • Are they Required? • When are they used?

7. Identity and Usage Rules • IETF PIDF-LO is a container that provides a linkage between identity, location and a right to use location. • Right of access is determined directly by the Target • MLP is a protocol that includes data types. Location is requested for a device. The identity of the device is necessary for the location request. • Right of access is determined indirectly through a PPR

8. Precision Requirements • How accurate does data need to be? • For routing • For dispatch • When is an area required over a point?