1 / 28

Location Services Standards Update

Location Services Standards Update. Kauai, USA December 2004. Kirk Burroughs QUALCOMM Inc. kirkb@qualcomm.com +1 408 626 0515. Disclaimer.

bernad
Download Presentation

Location Services Standards Update

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Location Services Standards Update Kauai, USA December 2004 Kirk Burroughs QUALCOMM Inc. kirkb@qualcomm.com +1 408 626 0515

  2. Disclaimer • Included in the following presentation is an overview of the 3GPP2 and OMA standards activities for Location Services. The overview is intended to be objective, however, it should be made clear that this presentation was prepared by QUALCOMM and not reviewed, approved, or endorsed in any way by either 3GPP2 or OMA and as such the overview should be considered a subjective overview provided by QUALCOMM.

  3. Outline • Control Plane Overview • User Plane Overview • 3GPP2 IP Based Location Services (X.P0024) • Overview • Network Reference Model • Call Flows • Open Issues • OMA LOC SUPL • Overview • Network Reference Model • Call Flows • Open Issues • Summary

  4. Control Plane Overview (1/2) • Network protocol is defined in J-STD-036 and PN-4747 / IS-881 / X.S0002 • J-STD-036 only addresses E-911 • PN-4747 / IS-881 / X.S0002 has some serious short comings • No support of self location • Position can only be delivered to application server, not the MS • In other words MS resident applications such as JAVA or BREW are not explicitly supported • No support of assistance data download • A MS can not simply download GPS assistance data • Disallows practical uses of the MS-Based mode of IS-801-1 and IS-801-A • Immediate services only • Periodic and triggered services not supported • No notification or verification mechanisms

  5. Control Plane Overview (2/2) • Positioning protocol and air interface are defined in IS-801-1 • IS-801-A was just recently published • IS-801-A states support for TCP, but is really dependent on X.P0024 • In addition to the service issues the Control Plane has additional issues • It is expensive and difficult to deploy • Its performance characteristics are inferior to the User Plane • It is only applicable to 1X networks • The Control Plane does have well defined roaming support • IS-41 based inter-MPC protocol via the L3 Interface • Bottom line = The Control Plane has and will most likely only see limited success; the User Plane appears to be the main vehicle for launching location services

  6. User Plane Overview • User Plane Pre-Standard Solutions • Original isolated solutions • KDDI, SKT, others have deployed unique User Plane solutions • Non-interoperable • No roaming - Although custom IWFs could be used • Qualcomm’s V1/V2 • China Unicom and Hutch-CAT have deployed V1/V2 • Other operators are now deploying V1/V2 • V1/V2 supports roaming • Many operators continue to create isolated User Plane solutions • Existing User Plane solutions have a security flaw in that they lack mutual authentication between the MS and the network • User Plane Standards • 3GPP2’s X.P0024 • OMA’s SUPL • Both standards expand support to include DO and IS-801-A

  7. 3GPP2 IP Based Location Services (X.P0024)

  8. Overview • Looks almost identical to Qualcomm’s V2, but addresses the security issues • X.P0024 is scheduled to be completed June 05 • Supports • MS-Initiated requests • WAP can be considered an MS-Initiated application • Network Initiated requests • Proxy / non-proxy solutions • A-GPS, Serving Cell, and Cached positioning • MS-Based / MS-Assisted positioning • Immediate / Periodic services • Triggered Events are for future releases • Roaming • Direct and Indirect • No immediate need for a Release 2.0

  9. Network Reference Model The figure above is not identical to the one contained in X.P0024 The NRM model shown in X.P0024 is in a state of flux as 3GPP2 decides on the best way to add a MC and a PPG to the NRM

  10. Network Reference Model • Positioning Server (PS) • Analogous to the MPC of J-STD-036 and PN-4747 / IS-881 / X.S0002 • Analogous to the SUPL Location Center of OMA • Position Determining Entity (PDE) • Analogous to the PDE of J-STD-036 and PN-4747 / IS-881 / X.S0002 • Analogous to the SUPL Positioning Center of OMA

  11. MS-Initiated Immediate – Home

  12. MS-Initiated Immediate – Roaming

  13. Network Initiated Immediate – Home

  14. Network Initiated Periodic 1/2 – Roaming

  15. Network Initiated Periodic 2/2 – Roaming

  16. Open Issues • Security details still being discussed • TSG-S is performing an overall analysis and this many take a few months • The most important aspect is the over the air interfaces • Two main approaches being suggested • TSL 1.0 vs TSL-PSK • Relationship with the OMA SUPL Spec is the underlying theme of most of the reaming discussions • The spec lacks forwards / backwards compatibility mechanisms and the current contributions addressing this issue are in limbo as the actual need for such mechanisms is being questioned • Although the protocol is fully specified (except for security and forwards / backwards compatibility ), there is a suggestion to map the protocol from its current encoding to ASN.1 in the name of “harmonization”

  17. OMA LOC SUPL

  18. Overview • Addresses 3GPP and 3GPP2 air interfaces • SUPL stated release date for Rel 1.0 is 1Q 2005 but this seems unlikely as it is less mature than X.P0024 • Supports • MS-Initiated Request • WAP can be considered an MS-Initiated Application • Network Initiated Request • Proxy / non-proxy solutions • A-GPS, Serving Cell, and Cached Positioning • MS-Based / MS-Assisted positioning • Immediate Services only • Periodic and Triggered Events are for future releases • Roaming Supported • Direct and Indirect • Rel 2.0 work will commence once Rel 1.0 is published

  19. Network Reference Model

  20. Network Reference Model • SUPL Location Platform (SLP) • Comprised of two core functional entities • SUPL Location Center (SLC) • Analogous to the MPC of J-STD-036 and PN-4747 / IS-881 / X.S0002 • Analogous to PS of X.P0024 • SUPL Positioning Center (SPC) • Analogous to the PDE of J-STD-036 and PN-4747 / IS-881 / X.S0002 • Analogous to the PDE of X.P0024

  21. MS-Initiated Immediate – Home

  22. MS-Initiated Immediate – Roaming

  23. Network Initiated Immediate – Home

  24. Network Initiated Immediate – Roaming

  25. Open Issues • Security details still being discussed • OMA SEC is performing an overall analysis and this should take a few months but OMA LOC has not adjusted its schedule accordingly • TLS based solutions are being discussed • The Network Initiated call flows require the network to be able to detect the capabilities of the SET, but this is not defined • QCOM is unaware of any real technical solution • Many protocol level details are missing • Qualcomm feels that after quite a long period of slow progress things are now being rushed • In general the spec is less mature than X.P0024 • Examples include RLP updates for SUPL, SUPL_INIT mappings, etc

  26. Summary (1/2) • In general the OMA and the 3GPP2 specs are functionally equivalent, but there are some key things to note • The OMA SUPL Network Initiated call flow is flawed in Qualcomm’s opinion • OMA SUPL is mandating alignment with other OMA specs such as MLP and RLP • OMA is phasing in support for periodic services and an the open interface between the PS / SLC and PDE / SPC • In theory OMA could develop a common spec but there are inherent differences between CMDA and GSM / WCMDA that translate into different requirements • Availability of AFLT, optimal data routing, and higher data rates • IS-801 and RRLP/RRC have some fundamental differences • Mobile originated sessions, session start / end flags, forwarding position estimates • Historically 3GPP and 3GPP2 have chosen different paths on issues such as transport, encoding, and security

  27. Summary (2/2) • There is some pressure to publish X.P0024 with no or limited forwards / backwards compatibly and to move all future User Plane activity into OMA, but QCOM feels that a 3GPP2 specification is best for the CMDA community • 3GPP2 has proved more capable of producing high quality work in a reasonable time frame • The majority of the OMA LOC members are pushing GSM / WCDMA agendas • X.P0024 is almost complete • A User Plane standard is essential for roaming • 3GPP2 needs to hear from the CDMA community that X.P0024 is needed and that it belongs in 3GPP2

  28. Acronyms • AAA – Authentication, Authorization, Accounting • IP – Internet Protocol • LBA – Location Based Application • LCS – Location Services • MLP – Mobile Location Protocol • MPC – Mobile Positioning Center • MS – Mobile Station • NI – Network Initiated • OMA – Open Mobile Alliance • OMA LOC – OMA Location (Working Group) • PDE – Position Determining Entity • PS – Positioning Server • RLP – Roaming Location Protocol • SET – SUPL Enabled Terminal • SLP – SUPL Location Platform • SUPL – Secure User Plane

More Related