OMA Location Working Group Update Mike Loushine Senior Scientist / Program Manager Emerging Mobile Technologies Group Telcordia Applied Research May 11, 2010 Version 1.0 1 Outline Disclaimer – This presentation is not an official OMA presentation. SUPL 3.0 Status 3GPP LPP and OMA LPPe Status 2 OMA SUPL High-level Architecture Data Gateway: used for SUPL “traffic” SMS Gateway: used for SUPL service initiation for network initiated SUPL applications SET - SUPL Enabled Terminal SUPL Server - SUPL Location Platform (SLP) 3 SUPL 3.0 Objectives Evolve SUPL 2.0 in the following areas Location Support for LTE Improved Location for IP Emergency Calls Improved Location performance Triggered Location Enhancement Improved Indoor Location Accuracy SET to SET Location (Terminal to Terminal) Authentication Enhancements Privacy Enhancements Additional access networks Support for Extended Location Information 4 SUPL 3.0 Status Highlights of the Requirements (1) The protocol SHALL support IETF “Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO)” [RFC5139] Location info format. SUPL SHALL support SLP service discovery. SUPL SHALL support delivery of indoor context information from the SET to the H-SLP. SUPL SHALL support emergency location for unauthenticated SET. 5 SUPL 3.0 Status Highlights of the Requirements (2) SUPL SHALL support the conveyance of a location URI from the SET to the SLP. The SLP MAY use the location URI as an additional source of location information. SUPL SHALL support extended location information including, for instance, motion state (walking, running, driving, etc.) and SET orientation information. 6 SUPL 3.0 Status Working Group Create Architecture document Submit Work Item Supported by 4 voting member companies Work Item Creation Architecture Detailed Security Technical Work continues Create Enabler Work Working Group package Step 1 on AD and TS Rework definitions Architecture Submit Candidate Enabler Submit WID to TP for Review and Approval Assignment RD approved to WG for Step 4 Security Requirements Approve InterOp (IOP) Approve Candidate Status Step 2 Approve Public Comment TP assigns WID to WG Fest Validation &Test IOP Create test plan Generate use-cases Step 5 Requirements WG reviews requirements Requirements Step 3 Approved Specification Define requirements from use-cases 7 3GPP LPP – LTE Positioning Protocol Operates on a transaction basis between a target device and a server 3GPP Evolved Packet Solution Target Device – UE Server – MME OMA SUPL 2.0 Target Device – SUPL Enabled Terminal (SET) Server – SUPL Location Platform (SLP) Transaction Types Exchange of positioning capabilities Transfer of assistance data Transfer of location information (positioning measurements and/or position estimate) Reference: 3GPP TS 36.305 V1.0.0 (2009-05) 8 LPP Version 1 and 2 LPP Relay RRC S1-AP RRC E-SMLC S1 UE S1-AP LCS-AP LCS-AP PDCP PDCP SCTP SCTP SCTP SCTP RLC RLC IP IP IP IP MAC MAC L2 L2 L2 L2 L1 L1 L1 L1 L1 L1 SLs LPP NAS Relay LTE Uu UE S1-MME eNode B SLs MME E-SMLC MME eNodeB LTE-Uu LPP1 LPP1 LPP2 eNodeB LPP2 NAS Relay S1 RRC RRC S1-AP S1-AP LCS-AP LCS-AP PDCP PDCP SCTP SCTP SCTP SCTP RLC RLC IP IP IP IP MAC MAC L2 L2 L2 L2 L1 L1 L1 L1 L1 L1 LTE Uu UE Reference: 3GPP TS 36.305 V1.0.0 (2009-05) eNode B 9 S1-MME MME SLs E-SMLC OMA LPPe –Work Areas AGNSS extensions High accuracy methods including Precise Point Positioning and Real-Time Kinematics Atmosphere models, etc. SET to SET positioning extensions Radio Network-based positioning extensions Radiomaps for cellular and noncellular networks (coverage area models – collection and positioning) Fingerprinting methods (fingerprint collection and positioning) for cellular and non-cellular access types SET-based positioning, including: SET based OTDOA and SET based E-CID for LTE and other access types radio network assistance data over a broader geographic area Support of other access types (e.g. Wi-Fi) 10 Compliment (but not duplicate) service layer support in SUPL 3.0 Extension of existing terrestrial RF positioning methods to positioning of one SET by other SETs (e.g. a SET measures signals from another SET) A-GNSS support between SETs – e.g. SET to SET conveyance of assistance data LPP3 Status Highlights of the Requirements (in development) LPPe SHALL support fixed access types such as Cable, DSL, LAN, etc. LPPe SHALL support altitude assistance for improved availability and altitude performance. LPPe SHALL support measurements and assistance for highaccuracy relative positioning. LPPe SHALL support delivery of indoor context information to the UE. LPPe SHALL support delivery of indoor context information from the UE to an appropriate entity in the network. 11 LPPe Status Working Group Create Architecture document Submit Work Item Supported by 4 voting member companies Work Item Creation Architecture Detailed Security Technical Create Enabler Work Working Group package Step 1 Rework definitions Architecture Submit Candidate Enabler Submit WID to TP for Review and Approval Assignment to WG Step 4 Security Requirements Approve InterOp (IOP) Approve Step 2 Approve Public Comment TP assigns WID to WG Fest Validation &Test IOP Create test plan Generate use-cases Step 5 Requirements WG reviews requirements Requirements Step 3 Approved Specification Define requirements from use-cases 12 Questions? Comments? Mike Loushine Senior Scientist / Program Manager mloushin@telcordia.com Office: +1 (732) 758-5358 Mobile: +1 (732) 762-0242 13