1 / 15

IP-based Location Services December 16, 2002

IP-based Location Services December 16, 2002. Outline. Location Services Requirements Position Determination/Position Disclosure Application Types User Plane Architecture Standards Status Roaming. LCS Requirements.

iren
Download Presentation

IP-based Location Services December 16, 2002

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. IP-based Location ServicesDecember 16, 2002

  2. Outline • Location Services Requirements • Position Determination/Position Disclosure • Application Types • User Plane Architecture • Standards Status • Roaming.

  3. LCS Requirements • Position Determination: Protocols and mechanisms to determine a position estimate of a mobile • IS-801 addresses protocol portion of this requirement • May or may not require specific service aspects, e.g. mechanisms for supporting authentication and authorization. • Position Disclosure (Usage): Protocols and mechanisms for requesting and delivering the target MS position information • Service Aspects: May include none, some or all of the following functions: • Authentication of User and/or Network Servers • Authorization (to use service(s)) • Accounting (for rights purchased, services used) • Notification/Verification (of user when network server seeks position and is not currently pre-authorized) • Location privacy, may include “fogging” (user can specify accuracy of location provided to network) • Security.

  4. Service Infrastructure Portal & Gateway (WAP) CDMA Packet Data Network Handset Web (Content) Server PDSN Web (Content) Server PDSN Carrier IP Network Router RADIUS PDE Internet LCS Server (Authorization & Billing)

  5. Application Type Examples • BREW / Java • Wide variety of possible applications. • The application may have all of its content stored locally, e.g. a navigation application with preloaded maps, or may be the client of a network application, e.g. a buddy finder service • SMS • Refers to simple preloaded text-based applications that use SMS as the transport mechanism • Example -- an ATM finder (single query to a network database followed by a single response) • WAP • Variety of applications that all use a client at the handset (the WAP browser) to display content generated at the network • Example -- mapping applications, driving direction lookup • Other network applications • Variety of applications that do not have a dedicated client at the handset • Example -- Phone finder, Location Sensitive Ads • Note: All network applications could be implemented with a dedicated client at the handset.

  6. Position Disclosure Options • Flexible architecture supports multiple options for each application type • Generally, main options are: • A: MS API is the access point for the application • B: LCS Server is the access point for the application

  7. System Architecture (1/4) • LCS Client • Entity seeking location information of target MS • MS – Mobile Station • Direct access point for selected application types • Application end-point for MS-PDE (IS-801) protocol • Contains LCS engine which determines or assists in position determination • PDE – Position Determination Entity • Determines position of a target MS based on PQoS requirements • Application end-point for MS-PDE (IS-801) protocol • Access point for BS Almanac information • LCS Server • Manages user/application service aspects for selected application types • Application end-point for MS-LCS Server protocol • Application end-point for L1 interface (e.g. LIF.)

  8. Position disclosure and position determination are independent The application requests a position from the MS or LCS Server (depending on carrier requirements) without requiring knowledge of the underlying technology Position determination may provide positions to the MS which, in turn, can be shared with the LCS Server Position Disclosure: Full range of applications can be supported, including BREW, WAP, SMS, Java Carrier selects which application types may access the MS directly Carrier selects which applications must instead access positioning data via the LCS Server. System Architecture (2/4)

  9. Position Determination: Both MS-Assisted and MS-Based positioning methods can be supported Upon direct invocation, based on the Quality of Service, the LCS engine chooses the appropriate positioning method Upon indirect invocation, the LCS Server may choose alternate positioning method, e.g. cell-ID, or defer the decision to the LCS engine in the handset Positioning specific application layer MS-PDE protocol and messaging is based on IS-801 standard TCP/IP transport mechanism used as opposed to Data Burst Messaging in IS-801. System Architecture (3/4)

  10. System Architecture (4/4)

  11. Example BREW Call Flow (MO, Option A) Note: steps a and c are API calls

  12. Example BREW Call Flow (MT, Option A) Note: steps b and d are API calls; step a may be a SMS message

  13. Example WAP Call Flow (MT, Option B) Note: steps d and f are API calls; step c may be a SMS message

  14. Roaming Support • MS discovers IP address for LCS Server (or PDE) via DNS query • MS communicates with PDE over IP • Serving LCS Server communicates with Home LCS Server for service authorization • LCS clients may be in visited or home networks (ex., location-specific advertisement) • Requires standards to be supported by roaming partners • Position determination must be performed by local PDE • PDE needs access to BS Almanac elements.

  15. Standards Status • 3GPP2 developed stage 1 requirements in S.P0066 • Stage 2/3 work about to start • Will re-use IS-801 for CDMA positioning protocol • Some concepts from PN-4747 for network signaling. • Good opportunity for feedback from carriers.

More Related