1. Page 1 Non-Trusted User Plane Roaming LBS Roaming Meeting, San Francisco November 28, 2006 Non-Trusted User Plane Roaming LBS Roaming Meeting, San Francisco November 28, 2006

2. Page 2 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

3. Page 3 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

4. Page 4 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

5. Page 5 Trusted/V1/V2 Services Network InitiatedMS-Resident Single Fix MSA Tracking MSB Tracking Single Fix MSA Tracking MSB Tracking V1 √ (MSA) Trusted & V2 √√√√√√ MSA: MS-Assisted MSB: MS-Based

6. Page 6 V1/V2 Network Architecture

7. Page 7 NI : V1 Non-Trusted

8. Page 8 NI : V2 Non-Trusted Single Fix

9. Page 9 NI : V2 Non-Trusted Periodic

10. Page 10 NI : Trusted

11. Page 11 MS Resident : V1 Non-Trusted

12. Page 12 MS Resident : V2 Non-Trusted Single Fix / Periodic

13. Page 13 MS Resident : Trusted

14. Page 14 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

15. 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 V1/V2 Roaming

16. Page 16 NI : V1 Non-Trusted

17. Page 17 MS Resident : V1 Non-Trusted

18. Page 18 NI : V2 Non-Trusted - Single fix

19. Page 19 NI : V2 Non-Trusted – Periodic Fix

20. Page 20 MS Resident : V2 Non-Trusted

21. Page 21 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