Page 1 Control Plane Roaming LBS Roaming Meeting, Denver January 18, 2007 Control Plane Roaming LBS Roaming Meeting, Denver January 18, 2007

Page 2 Control Plane Roaming Update A few CP deployments out there, with a few more on the way Growing number of Control Plane enabled mobiles Control Plane roaming is important and seems straightforward It was agreed at previous LBS Roaming Summits that an RLP variant would be used as the protocol between Control Plane MPCs as opposed to IS-41 based ISPOSREQ / isposreq as defined in IS-881 Openwave has defined such a variant and is in the process of releasing the spec to the CDG IRT and this group A review of the Openwave spec is required and potential enhancements and standardization efforts need to be considered The RSP / CRX issues (no access to true serving system information) still need to be resolved

Page 3 IS-881 Roaming Call Flow

Page 4 Expected Control Plane Roaming Architecture RSP Home Operator Visited Operator MSC/VLR H-MPC HLR IS-41 Signaling HLR H-MPC V-MPC IP Network (L3) IP Network (L3) V-PDE LCS Client IP Traffic

Page 5 RSP Issue Most operators prefer to use RSP for roaming RSP provide peering point for SS7/IS-41 exchange between operators RSP provides intermediary HLR function During registration, home operator receives generic MSCID provided by RSP Home operator won’t be able to map generic MSCID to correct V-MPC for L3 interface Also the message used on the L3 interface to invoke the V-MPC needs to pass the serving MSCID to allow the V-MPC to execute local IS-881 procedures (e.g., invoke the serving MSC)

Page 6 RSP Issue Illustrated MS registers and RSP replaces MSC/VLR MSCID with generic RSP MSCID LCS Client queries H-MPC for roaming MS H-MPC uses LOCREQ/SMSREQ to receive MSCID (RSP HLR) from HLR H-MPC needs to map MSCID (RSP HLR) to the IP address of V-MPC Because MSCID is generic RSP MSCID, the H-MPC doesn’t know where the V-MPC is RSP Home Operator Visited Operator MSC/VLR H-MPC HLR IS-41 Signaling HLR H-MPC V-MPC IP Network (L3) IP Network (L3) V-PDE LCS Client IP Traffic MSCID = RSP HLR MSCID = MSC/VLR RSP HLR = ?

Page 7 RSP Issue Solution #1 MS Registers and RSP provides the serving MSCID to home operator LCS Client queries H-MPC for roaming MS H-MPC uses LOCREQ/SMSREQ to receive serving MSCID from HLR H-MPC maps serving MSCID to the IP address of V-MPC H-MPC performs L3 transaction with V-MPC (passing serving MSCID) RSP Home Operator Visited Operator MSC/VLR H-MPC HLR IS-41 Signaling HLR H-MPC V-MPC IP Network (L3) IP Network (L3) V-PDE LCS Client IP Traffic MSCID = MSC/VLR Visited Op =

Page 8 IP Network (L3) IP Network (L3) RSP Issue Solution #2 MS registers and RSP replaces MSC/VLR MSCID with generic RSP MSCID LCS Client queries H-MPC for roaming MS H-MPC uses LOCREQ/SMSREQ to receive serving MSCID (that of the RSP) from HLR H-MPC always creates IP connection (L3) with RSP RSP maps MS IMSI in L3 messaging to V-MPC IP Address RSP connects to V-MPC (passing serving MSCID) and provides response to H-MPC RSP Home Operator Visited Operator MSC/VLR H-MPC HLR IS-41 Signaling HLR H-MPC V-MPCV-PDE LCS Client IP Traffic MSCID = RSP HLR MSCID = MSC/VLR IMSI maps to V-MPC

Page 9 Next Steps Review and discuss Openwave’s RLP solution Gap Analysis of RLP for IS-881 support –Openwave’s changes and perhaps further enhancements Drive changes through OMA Review and discuss the RSP / CRX Issues