1

OMA Location Working Group Update

Mike LoushineSenior Scientist / Program ManagerEmerging Mobile Technologies Group

Telcordia Applied Research

May 11, 2010 Version 1.0

2

Outline

Disclaimer – This presentation is not an official OMA presentation.

SUPL 3.0 Status

3GPP LPP and OMA LPPe Status

3

Data Gateway: used for SUPL “traffic”

SMS Gateway: used for SUPL service initiation for network initiated SUPL applications

SET - SUPL Enabled TerminalSUPL Server - SUPL Location Platform (SLP)

OMA SUPL High-level Architecture

4

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

5

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.

6

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.

7

Submit Work Item Supported by 4

voting membercompanies

Submit WID to TP forReview and Approval

Rework definitions

TP assigns WID to WG

Define requirementsfrom use-cases

Generate use-cases Requirements WGreviews requirements

Create Architecturedocument

Create Enablerpackage

Submit CandidateEnabler

Working Group

Architecture

Security

Requirements

InterOp (IOP)

Public Comment

Create test plan Test Fest

Approved Specification

Approve

Approve

Working Group

Architecture

Security

Approve

Work Item Creation

Step 1

Requirements

Step 3

Detailed Technical

Work

Step 4

Validation & IOPStep 5

Assignment to WG

Step 2

SUPL 3.0 Status

RD approved for Candidate Status

Work continues on AD and TS

8

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)

9

LPP Version 1 and 2

UE

eNodeB

S1

eNodeB

S1

MME

E-SMLC

SLs

LTE-Uu

L1

MAC

RLC

PDCP

RRC

LPP

L1

MAC

RLC

PDCP

RRC Relay

L1

L2

IP

SCTP

S1-AP

L1

L2

IP

SCTP

S1-AP

NAS Relay

L1

L2

IP

SCTP

LCS-AP

L1

L2

IP

LCS-AP

LPP

UE eNode B MME LTE Uu S1-MME SLs

SCTP

E-SMLC

L1

MAC

RLC

PDCP

RRC

LPP1

L1

MAC

RLC

PDCP

RRC

L1

L2

IP

SCTP

S1-AP

L1

L2

IP

SCTP

S1-AP

NAS Relay

L1

L2

IP

SCTP

LCS-AP

L1

L2

IP

LCS-AP

LPP2

UE eNode B MME LTE Uu S1-MME SLs

SCTP

E-SMLC

LPP1 LPP2

Reference: 3GPP TS 36.305 V1.0.0 (2009-05)

10

OMA LPPe –Work Areas

AGNSS extensions High accuracy methods including

Precise Point Positioning and Real-Time Kinematics

Atmosphere models, etc. Radio Network-based positioning

extensions Radiomaps for cellular and non-

cellular 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)

SET to SET positioning extensions 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

11

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 high-

accuracy 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.

12

Submit Work Item Supported by 4

voting membercompanies

Submit WID to TP forReview and Approval

Rework definitions

TP assigns WID to WG

Define requirementsfrom use-cases

Generate use-cases Requirements WGreviews requirements

Create Architecturedocument

Create Enablerpackage

Submit CandidateEnabler

Working Group

Architecture

Security

Requirements

InterOp (IOP)

Public Comment

Create test plan Test Fest

Approved Specification

Approve

Approve

Working Group

Architecture

Security

Approve

Work Item Creation

Step 1

Requirements

Step 3

Detailed Technical

Work

Step 4

Validation & IOPStep 5

Assignment to WG

Step 2

LPPe Status

13

Questions? Comments?

Mike Loushine

Senior Scientist / Program Manager

mloushin@telcordia.com

Office: +1 (732) 758-5358

Mobile: +1 (732) 762-0242