page 1 non-trusted user plane roaming lbs roaming meeting, san francisco november 28, 2006...

Non-Trusted User Plane RoamingLBS Roaming Meeting, San

Francisco November 28, 2006

Non-Trusted User Plane RoamingLBS Roaming Meeting, San

Francisco November 28, 2006

User Plane Defined

• Service Level and Positioning Level messages carried over user data bearers• Mostly IP but also SMS

• Uses an “MPC” and a “PDE”, as well as IS-801-1, like the Control Plane

• Qualcomm published the first User Plane Specifications• Known as V1/V2

• The V1/V2 Specifications are available on the CDG website• www.cdg.org/technology/cdma_technology/tech_resources.asp

• V1/V2 have the goal of being a defacto standard• While there are now 3GPP2 and OMA standards for User Plane

solutions no CDMA products exist• User Plane solutions supports both MO and MT services

• User Plane solutions do not support voice services

User Plane History

• User Plane Architectures exist as a result of several issues with the Control Plane

• J-STD-036 only address E-911

• IS-881 / X.S0002 only supports network resident applications

• No support of self location• No signaling mechanism defined other than dialed digit analysis• Position can only be delivered to application server, not the MS• In other words MS resident applications are not explicitly supported• Complicates (disallows) support of BREW / JAVA

• No support of assistance data download• Disallows practical uses of the MS-Based mode of IS-801• For example, an MS simply downloading GPS Ephemeris and

Almanac data periodically for an application contained within the MS

User Plane Status

• Many carriers have launched User Plane solutions

• While not all of the deployed User Plane solutions exactly follow the V1/V2 Specs, all the deployed User Plane solutions can be classified as either Trusted or Non-Trusted

• Trusted and Non-Trusted are defined in the V1/V2 Specs

• Non-Trusted – MPC interaction required• A PDE is assigned

• Trusted – No MPC interaction required• Trusted applications may access the PDE directly

Trusted/V1/V2 Services

Network Initiated MS-Resident

Single Fix

MSA Tracking

MSB Tracking Single

Fix

MSA Tracking

MSB Tracking

V1√

(MSA) √ (MSA)

Trusted&V2

√ √ √ √ √ √

MSA: MS-Assisted

MSB: MS-Based

V1/V2 Network Architecture

MS-MPC

Wireless Network

PDSN / IWF

MSC / VLR /HLRApps

MS

S-MPCH/S-gpsOne

PDE

E5'IS-801

Legacy PDE

MC

MPC-MPC

L1

SMPP

SMDPP

IS-41

Apps

L1

H-MPC

NI : V1 Non-Trusted

MPC PDE MS

a

b

c

GPOSREQ’

MLP LIR

MO IS-801 Session

LCSClient

d

e

f

MT SMS (gpsOne Trigger, Notification, PDE Address, etc)

MO SMS (Consent, SID/NID, etc)

MLP LIR

g

gposreq'

Service Authorization

NI : V2 Non-Trusted Single Fix

LCSClient

MS

MLP LIR (QoS)

IS-801 exchange

H/S -MPC

PDE

a

c

b

d

e

f

g

h

i

ServiceAuthorization

gposreq’ (position)

SPPRes (PDE Address)

gposreq’ (position pending, ack)

GPOSREQ’ (gpsOne, IMSI, PDE Access Duration)

SPPReq (CI, Network Initiated App, IMSI, SID, NID, etc)

MT-SMS Positioning Request (CI, gpsOne Trigger, H-MPC ID, etc)

T3

T1

T16

T7

T12

MLP LIA (position)

T8

NI : V2 Non-Trusted Periodic

LCSClient

MS

MLP TL Reporting Request (Interval, START_TIME, STOP_TIME)

MT-SMS Positioning Request (CI, gpsOne Trigger, H-MPC ID, N Fixes, T Time Between)

IS-801 exchange (Downloadneeded assistance data)

SPPReq (CI, Network Initiated App, IMSI, SID, NID, Duration, etc)

H/S-MPC

PDE

a

c

b

d

e

f

g

h

i

j

k

l

m

n

T In

terva

l 1n T

Inter

vals

o

Additional IS-801 exchange(Download needed assistance

data)q

p

r

s

t

u


MLP TL Report (Fix N)

Position Report (CI, Fix N)

gposreq’ (Session Info)

MLP TL Report (Fix 2)

Position Report (CI, Fix 2)





gposreq’ (ack)

Position Report Response (CI, ack)



T3

T7

T14

T14

T14

T16

MLP TL Reporting Answer


NI : Trusted

PDE MSMSApp

a

b

c

MS API Request

MO IS-801 Session

LCSClient

MS API Response

e

d

MT SMS Trigger

Upload Position (SMS or IP)

MS Resident : V1 Non-Trusted

PDE MSMSApp

a

b

c

MS API Request

MO IS-801 Session

MPC

d

e

MS-MPC Request

MS-MPC Response

MS API Response

f

GPOSREQ’

gposreq'

g

MS Resident : V2 Non-Trusted Single Fix / Periodic

aMS API Request (N Fixes, T Time Between)

H/S -MPC

PDE MSMSApp

SPPReq (IMSI, App Type Ind, App ID, Duration, etc.)

GPOSREQ’ (IMSI, gpsOne, PDE Access Duration)

gposreq' (ack)

SPPRes (gpsOne, PDE IP/Port#, etc.)

MO IS-801 Session

gposreq' (session info)

MS API Response (Fix 1)

MS API Response (Fix 2)Additional MO IS-801 sessions as

neededMO IS-801 Session


MS API Response (Fix N)

b

c

d

e

g

f

h

j

k

i

l

N-2 Intervals

Interval 1T1

T7

T16

MS Resident : Trusted


H/S -MPC

PDE MSMSApp

MO IS-801 Session



Additional MO IS-801sessions as needed

MO IS-801 Session

b

c

d

e

g

f

h

Interval 1

N-2 IntervalsMS API Response (Fix N)

gposreq' (unsolicited, session info)

gposreq' (unsolicited, session info)

• User Plane solutions have independent coverage areas from the underlying cellular network so as such it is possible to have a User Plane solution provide global coverage

• Packet data roaming and SMS roaming must be enabled

• The home network must have a global Base Station Almanac (BSA) and a global GPS Reference Network

• Requires sharing of BSAs, perhaps via a third party

• In such cases the home based call flows just presented apply

User Plane Roaming

• V1/V2 assume that a global BSA and global WARN are not available and describe how the home and serving system interact to allocate a serving PDE

• The LCS Client, MS, and PDE are unchanged• The MPC needs to support a new interface

• Fully specified in V1/V2• Analogous to the L3 Interface

• For the V1 NI call flows, the MPC also needs to support an IS-41 interface

• The H-MPC needs to obtain the S-MPC information as such data is contained in the MT SMS trigger

• This was a bug in V1 that was corrected in V2• V1/V2 only fully describe roaming in the context of Non-Trusted• For Trusted roaming a simple DNS approach is briefly described in

V1/V2• Subsequent material has been made available that expands on the

range of options available to enable trusted roaming• This will be discussed in a separate presentation

V1/V2 Roaming

NI : V1 Non-Trusted

SMPC SPDE MS

a

b

c

LCSClient

d

e

f

g

h

PermissionsPop-upScreen

i

j


l

k

HMPC

m

GPOSREQ’ (IMSI, gpsOne)

MO IS-801 Session

gposreq' (success, position)

T12

T13

T1

Roaming Request (NI, IMSI, gpsOne, SID/NID/etc)

T15

MT SMS (gpsOne, PDE IP/Port#, etc.)

MO SMS (Consent, SID/NID, etc.)

MLP LIA

Ack (IMSI, gpsOne, PDE IP/Port#)

MLP LIR

n

HLR

LOCREQ

locreq

Location Report (success, position)


SMPC SPDE MS

a

b

c

d

e

f

g

h

i

j


k

HMPC

GPOSREQ’ (IMSI, gpsOne)

MO IS-801 Session

gposreq' (success, position)

Ack (IMSI, gpsOne, PDE IP/Port#)

T13

T1

T7Roaming Request (MS-Res, IMSI, gpsOne, SID/NID/etc)

SPPReq (MS-Res, PQoS, SID/NID/etc, IMSI, etc.)

Location Report (success, position)

MSApp

MS API Request

SPPRes (gpsOne, PDE IP/Port#, etc)

MS API Response

NI : V2 Non-Trusted - Single fix

LCSClient

MS

MLP LIR (QoS)

MT-SMS Positioning Request (CI, gpsOne Trigger, H-MPC ID, etc)

IS-801 exchange

SPPReq (CI, Network Initiated App, IMSI, SID, NID, etc)

HMPC PDE

a

c

b

d

e

f

g

h

i

j

SMPC

Roaming Request (NI, CI, IMSI, gpsOne, SID/NID/etc.)

k

lMLP LIA (position)

Location Report (CI, Position)

gposreq’ (position)


gposreq’ (position pending, ack)



Ack (CI, IMSI, gpsOne, PDE IP/Port)

T12

T3

T13

T1

T16

T7

T8

NI : V2 Non-Trusted – Periodic Fix

MLP TL Reporting Request (Interval, START_TIME, STOP_TIME)

MT-SMS Positioning Request (CI, gpsOne Trigger, H-MPC ID, N Fixes, T Time Between)

IS-801 exchange (Downloadneeded assistance data)

SPPReq (CI, Network Initiated App, IMSI, SID, NID, Duration, etc)

a

c

b

d

e

f

g

h

i

j

Roaming Request ( NI, CI, IMSI, gpsOne, STOP_TIME, SID/NID/etc.)

k

l

m

n

T In

terv

al 1

n T

Inte

rvals

o

Additional IS-801 exchange(Download needed assistance

data)

p

q

r

s

t

u

v

w

y

x


LCSClient

HMPC SMPC PDE MS

MLP TL Report (Fix N)

Position Report (CI, Fix N)








gposreq’ (ack)





MLP TL Reporting Answer

Ack (CI, IMSI, gpsOne, PDE IP/Port#)

T3

T7

T13

T14

T14

T14

T16

Session Status Report (Session Info)

Session Status Report (Session Info)


HMPC SMPC PDE MSMS App


SPPReq (IMSI, App Type Ind, App ID, Duration, etc.)

SPPRes (gpsOne, PDE IP/Port#, etc.)

MO IS-801 Session

gposreq' (ack)


Session Status Report



Interval 1

MO IS-801 Session (as needed)

N-2 Intervals

b

c

d

e

g

f

h

i

j

k

l

m

n

o

p

q

GPOSREQ’ (IMSI, gpsOne, PDE Access Duration)

Ack (IMSI, gpsOne. PDE IP/Port#)

T13T7

T1 T16

Roaming Request (MSR, IMSI, gpsOne, SID/NID/etc.)


Session Status Report

MS API Response (Fix N)


User Plane Remarks

•As it is clear that there will be multiple versions of User Plane solutions, some based on V1/V2 and some not, and that both the Trusted and Non-Trusted options will also exist, it is important to determine the best way to interconnect these disparate solutions

• This is a main focus of this LBS Roaming Summit

• More detailed discussion to follow

page 1 non-trusted user plane roaming lbs roaming meeting, san francisco november 28, 2006...

Documents

user plane roaming slide

ms slide

user plane specifications

user plane status

v1 nontrusted slide

deployed user plane

trusted applications

msbased slide