IP Connectivity for E911 in HRPD/PDS Networks Page 1 IP Connectivity for Emergency Calls in HRPD/PDS Networks 3GPP2 Meeting, 1/07 IP Connectivity for Emergency Calls in HRPD/PDS Networks 3GPP2 Meeting, 1/07

IP Connectivity for E911 in HRPD/PDS Networks Page 2 IP Connectivity for Emergency Calls in HRPD/PDS Networks QUALCOMM Inc. Notice: Contributors grant free, irrevocable license to 3GPP2 and its Organization Partners to incorporate text or other copyrightable material contained in the contribution and any modifications thereof in the creation of 3GPP2 publications; to copyright and sell in Organizational Partner’s name any Organizational Partner’s standards publication even though it may include portions of the contribution; and at the Organization Partner’s sole discretion to permit others to reproduce in whole or in part such contributions or the resulting Organizational Partner’s standards publication. Contributors are also willing to grant licenses under such contributor copyrights to third parties on reasonable, non-discriminatory terms and conditions for purpose of practicing an Organizational Partner’s standard which incorporates this contribution.This document has been prepared by the contributors to assist the development of specifications by 3GPP2. It is proposed to the Committee as a basis for discussion and is not to be construed as a binding proposal on the contributors. The contributors specifically reserves the right to amend or modify the material contained herein and nothing herein shall be construed as conferring or offering licenses or rights with respect to any intellectual property of the contributors other than provided in the copyright statement above.

IP Connectivity for E911 in HRPD/PDS Networks Page 3 Overview Briefly describe 3GPP’s solution on conditional Emergency Services IMS Registration Highlight a key difference between 3GPP and 3GPP2 on the issue of IMS to IP binding Discuss some issues for 3GPP2 Propose a 3GPP2 solution

IP Connectivity for E911 in HRPD/PDS Networks Page 4 3GPP Overview The only case when the UE should perform an additional emergency registration when it is already IMS registered is as follows: If the UE knows it is roaming outside the home network, but is connected to a GGSN and hence a P-CSCF, in the home network In this case, the UE has to perform the following steps: Obtain IP connectivity via a GGSN in the visited network Discover a P-CSCF in that network Perform another IMS registration with a *special* emergency Public URI –The *special* emergency URI is needed because of the limitation in IMS Rel 5/6/7, where for a given private id there can only be a single IMS registration

IP Connectivity for E911 in HRPD/PDS Networks Page 5 IMS/MMD Technical Differences Proxy-CSCF & PDSN/GGSN location In 3GPP IMS, the GGSN and P-CSCF are always co- located in the same network In 3GPP2 MMD, the PDSN and P-CSCF may be located in different networks –E.g., The PDSN may be in the visited and the P- CSCF may be in the home network

IP Connectivity for E911 in HRPD/PDS Networks Page 6 Technical Considerations for 3GPP2 In 3GPP2 networks the MS does not always know it is roaming A solution is proposed for MMD MMD Roaming is not yet defined When to use a P-CSCF in the home or visited is all TBD A multitude of IP options exist Simple IP vs. Mobile IP IPv4 vs. IPv6 L2TP

IP Connectivity for E911 in HRPD/PDS Networks Page 7 Proposed 3GPP2 Solution Mobile accesses HRPD/PDS network MS determines if it’s roaming via carrier-ID attribute (received via DHCP) Carrier ID = Mobile Country Code (MCC) + IMSI_11_12 (unique per operator) If the MS is not roaming, it accesses emergency services through its normal (home) P-CSCF registration If the MS is roaming but is using a local P-CSCF, it accesses emergency services through its visited network P-CSCF registration If the MS is roaming but the P-CSCF is in the home network then after an emergency call is dialed, the UE Obtains a SIPv6 address Registers via the local (visited) P-CSCF – For authorized mobiles anyway

IP Connectivity for E911 in HRPD/PDS Networks Page 8 Simple IPv6 Justification Mobile IPv4 and Mobile IPv6 are not appropriate for emergency access when roaming If HA is in the home network, then all packets are tunneled back to the home network HA assignment in the visited network may not be supported or authorized Simple IPv4 is not appropriate for emergency access when roaming If L2TP is used with the Simple IPv4 address, all packets will be routed to the home operator network MS is assigned with one Simple IPv4 address and is unaware of L2TP