Transcript Section 2: Section Title

Page 1
Non-Trusted User Plane Roaming
LBS Roaming Meeting, San Francisco
November 28, 2006
User Plane Defined
Page 2
•
•
•
•
•
•
•
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
Page 3
•
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
Page 4
•
•
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
Page 5
Network Initiated
Single
Fix
V1
√
(MSA)
Trusted
&
V2
√
MSA
Tracking
MS-Resident
MSB
Tracking
Single
Fix
MSA
Tracking
MSB
Tracking
√
√
√ (MSA)
√
√
√
MSA: MS-Assisted
MSB: MS-Based
V1/V2 Network Architecture
Page 6
MC
SMDPP
Apps
MSC / VLR /
HLR
IS-41
SMPP
Legacy PDE
L1
Wireless Network
MS-MPC
MS
L1
PDSN / IWF
H-MPC
MPC-MPC
E5'
IS-801
H/S-gpsOne
PDE
Apps
S-MPC
NI : V1 Non-Trusted
Page 7
LCS
Client
MPC
PDE
MS
MLP LIR
Service Authorization
a
GPOSREQ’
b
MT SMS (gpsOne Trigger, Notification, PDE Address, etc)
MO SMS (Consent, SID/NID, etc)
MO IS-801 Session
gposreq'
MLP LIR
c
d
e
f
g
NI : V2 Non-Trusted Single Fix
Page 8
LCS
Client
H/S MPC
PDE
MS
MLP LIR (QoS)
Service
Authorization
a
MT-SMS Positioning Request (CI, gpsOne Trigger, H-MPC ID, etc)
b
T3
SPPReq (CI, Network Initiated App, IMSI, SID, NID, etc)
GPOSREQ’ (gpsOne, IMSI, PDE Access Duration)
d
gposreq’ (position pending, ack)
T12
T7
SPPRes (PDE Address)
T16
MLP LIA (position)
e
f
T8
IS-801 exchange
T1
gposreq’ (position)
c
g
h
i
NI : V2 Non-Trusted Periodic
Page 9
LCS
Client
H/SMPC
PDE
MS
MLP TL Reporting Request (Interval, START_TIME, STOP_TIME)
a
Service Authorization
b
MT-SMS Positioning Request (CI, gpsOne Trigger, H-MPC ID, N Fixes, T Time Between)
c
T3
SPPReq (CI, Network Initiated App, IMSI, SID, NID, Duration, etc)
MLP TL Reporting Answer
d
e
GPOSREQ’ (gpsOne, IMSI, PDE Access Duration)
T7
gposreq’ (ack)
f
g
SPPRes (PDE Address)
h
IS-801 exchange (Download
needed assistance data)
gposreq’ (Session Info)
T16
i
j
Position Report (CI, Fix 1)
T14
l
MLP TL Report (Fix 1)
m
Position Report (CI, Fix 2)
T Interval 1
k
Position Report Response (CI, ack)
n
Position Report Response (CI, ack)
T14
o
MLP TL Report (Fix 2)
Additional IS-801 exchange
(Download needed assistance
data)
q
gposreq’ (Session Info)
r
Position Report (CI, Fix N)
s
Position Report Response (CI, ack)
T14
t
MLP TL Report (Fix N)
u
n T Intervals
p
NI : Trusted
Page 10
LCS
Client
PDE
MS
App
MS
MT SMS Trigger
a
MS API Request
b
MO IS-801 Session
c
MS API Response
d
Upload Position (SMS or IP)
e
MS Resident : V1 Non-Trusted
Page 11
MPC
PDE
MS
App
MS
MS API Request
MS-MPC Request
a
b
MS-MPC Response
c
GPOSREQ’
d
MO IS-801 Session
e
gposreq'
f
MS API Response
g
MS Resident : V2 Non-Trusted Single Fix / Periodic
Page 12
H/S MPC
PDE
MS
App
MS
MS API Request (N Fixes, T Time Between)
SPPReq (IMSI, App Type Ind, App ID, Duration, etc.)
b
GPOSREQ’ (IMSI, gpsOne, PDE Access Duration)
c
T7
gposreq' (ack)
d
SPPRes (gpsOne, PDE IP/Port#, etc.)
e
MO IS-801 Session
f
gposreq' (session info)
g
MS API Response (Fix 1)
T1
a
h
T16
Interval 1
MS API Response (Fix 2)
Additional MO IS801 sessions as
needed
MO IS-801 Session
gposreq' (session info)
i
j
N-2 Intervals
k
MS API Response (Fix N)
l
MS Resident : Trusted
Page 13
H/S MPC
PDE
MS
App
MS
MS API Request (N Fixes, T Time Between)
a
MO IS-801 Session
b
MS API Response (Fix 1)
gposreq' (unsolicited, session info)
Interval 1
c
d
MS API Response (Fix 2)
e
Additional MO IS-801
sessions as needed
MO IS-801 Session
gposreq' (unsolicited, session info)
f
g
N-2 Intervals
MS API Response (Fix N)
h
User Plane Roaming
• 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
Page 14
V1/V2 Roaming
Page 15
• 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
NI : V1 Non-Trusted
Page 16
LCS
Client
HMPC
HLR
SMPC
SPDE
MS
MLP LIR
a
Service
Authorization
b
LOCREQ
c
locreq
d
Roaming Request (NI, IMSI, gpsOne, SID/NID/etc)
e
T13
Ack (IMSI, gpsOne, PDE IP/Port#)
f
GPOSREQ’ (IMSI, gpsOne)
g
MT SMS (gpsOne, PDE IP/Port#, etc.)
T12
h
Permissions
Pop-up
Screen
T15
MO SMS (Consent, SID/NID, etc.)
i
j
T1
MO IS-801 Session
gposreq' (success, position)
Location Report (success, position)
MLP LIA
k
l
m
n
MS Resident : V1 Non-Trusted
Page 17
HMPC
SMPC
SPDE
MS
App
MS
MS API Request
SPPReq (MS-Res, PQoS, SID/NID/etc, IMSI, etc.)
a
b
Service
Authorization
c
Roaming Request (MS-Res, IMSI, gpsOne, SID/NID/etc)
T7
d
T13
Ack (IMSI, gpsOne, PDE IP/Port#)
e
SPPRes (gpsOne, PDE IP/Port#, etc)
f
GPOSREQ’ (IMSI, gpsOne)
T1
g
MO IS-801 Session
h
gposreq' (success, position)
i
MS API Response
Location Report (success, position)
j
k
NI : V2 Non-Trusted - Single fix
Page 18
LCS
Client
SMPC
HMPC
PDE
MS
MLP LIR (QoS)
Service
Authorization
a
MT-SMS Positioning Request (CI, gpsOne Trigger, H-MPC ID, etc)
b
T3
SPPReq (CI, Network Initiated App, IMSI, SID, NID, etc)
c
Roaming Request (NI, CI, IMSI, gpsOne, SID/NID/etc.)
d
GPOSREQ’ (gpsOne, IMSI, PDE Access Duration)
T13
gposreq’ (position pending, ack)
e
T7
Ack (CI, IMSI, gpsOne, PDE IP/Port)
f
g
SPPRes (PDE Address)
T1
T16
h
T8
IS-801 exchange
i
gposreq’ (position)
T12
j
Location Report (CI, Position)
k
MLP LIA (position)
l
NI : V2 Non-Trusted – Periodic Fix
Page 19
LCS
Client
SMPC
HMPC
PDE
MS
MLP TL Reporting Request (Interval, START_TIME, STOP_TIME)
a
Service Authorization
b
MT-SMS Positioning Request (CI, gpsOne Trigger, H-MPC ID, N Fixes, T Time Between)
c
T3
SPPReq (CI, Network Initiated App, IMSI, SID, NID, Duration, etc)
d
Roaming Request ( NI, CI, IMSI, gpsOne, STOP_TIME, SID/NID/etc.)
e
GPOSREQ’ (gpsOne, IMSI, PDE Access Duration)
T13
Ack (CI, IMSI, gpsOne, PDE IP/Port#)
f
gposreq’ (ack)
g
T7
MLP TL Reporting Answer
h
i
SPPRes (PDE Address)
j
IS-801 exchange (Download
needed assistance data)
k
gposreq’ (Session Info)
l
T16
Session Status Report (Session Info)
m
Position Report (CI, Fix 1)
o
MLP TL Report (Fix 1)
p
Position Report (CI, Fix 2)
T Interval 1
n
T14
Position Report Response (CI, ack)
q
Position Report Response (CI, ack)
T14
r
MLP TL Report (Fix 2)
Additional IS-801 exchange
(Download needed assistance
data)
gposreq’ (Session Info)
t
u
Session Status Report (Session Info)
v
Position Report (CI, Fix N)
Position Report Response (CI, ack)
MLP TL Report (Fix N)
w
T14
x
y
n T Intervals
s
MS Resident : V2 Non-Trusted
Page 20
HMPC
SMPC
PDE
MS
App
MS
MS API Request (N Fixes, T Time Between)
SPPReq (IMSI, App Type Ind, App ID, Duration, etc.)
b
Service
Authorization
c
Roaming Request (MSR, IMSI, gpsOne, SID/NID/etc.)
T13
a
d
GPOSREQ’ (IMSI, gpsOne, PDE Access Duration)
e
T7
gposreq' (ack)
f
Ack (IMSI, gpsOne. PDE IP/Port#)
g
SPPRes (gpsOne, PDE IP/Port#, etc.)
h
MO IS-801 Session
i
gposreq' (session info)
j
Session Status Report
k
T1
MS API Response (Fix 1)
T16
l
Interval 1
MS API Response (Fix 2)
MO IS-801 Session
(as needed)
n
gposreq' (session info)
Session Status Report
m
o
N-2 Intervals
p
MS API Response (Fix N)
q
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 21