Deb Barclay +1.630.690.2058 DLBarclay@alcatel-lucent

1. 3GPP2 All IP Emergency CallsSDO Emergency Services Coordination WorkshopWashington DC 10-12 April, 2007 Deb Barclay +1.630.690.2058DLBarclay@alcatel-lucent.com • Kirk Burroughs • +1.408.626.0515 • kirkb@qualcomm.com • QUALCOMM

2. Presentation Overview • 3GPP2 / 3GPP Alignment • Stage 1 – Requirements • Stage 2 – Architecture / Call Flows • Stage 3 – Protocol • Summary

3. 3GPP2 / 3GPP Alignment • 3GPP2’s IMS Core Network specifications are based on 3GPP’s IMS Core Network specifications • This is true in general and not just for emergency services • For emergency services, there are some differences, mainly due to access network differences • 3GPP2 covers IP-Based emergency calls originated from 3GPP2 associated wireless networks (HRPD and WLAN) whereas 3GPP also covers calls from ETSI TISPAN defined fixed broadband networks • How the Endpoint determines it is roaming • Broadcast MCC/MNC in 3GPP vs DHCP in 3GPP2 • How unauthorized endpoints get access to the network

4. Stage 1 - Requirements • S.R0115 All IP-Network Emergency Call Support • http://www.3gpp2.org/Public_html/specs/S.R0115-0%20v1.0_060914.pdf • S.R0115 (revision 1.1) recently updated to add support for the following: • Support for Non-authorized mobiles • Anonymous call support • A regional requirement (e.g. Japan: prefix 184 before emergency number 119)

5. Stage 2 – Architecture / Call Flows • X.P0049 “Multi-Media Domain (MMD) Emergency Call Support” • Draft is available in the projects folder: • ftp://ftp.3gpp2.org/TSGX/Projects - under the X.P0049 folder • Based on 3GPP’s Stage 2, TS 23.167 “IP based IP Multimedia Subsystem (IMS) emergency sessions; Stage 2” • Same architecture as 3GPP – when roaming, call is handled entirely in the visited network. • While X.P0049 is a Stage 2 specification for IMS Core Network, it will also contain annexes for HRPD/PDS and WLAN access network procedures • HRPD / PDS details in progress • WLAN work yet to begin

6. IMS Emergency Call Architecture • BGCF: Breakout Gateway Control Function • CSCF: Call Session Control Function • E-CSCF: Emergency CSCF • LRF: Location Routing Function • MGCF: Media Gateway Control Function • P-CSCF: Proxy CSCF • S-CSCF: Serving CSCF • SUPL: Secure User Plane Location • UE: User Endpoint • * LRF – Location may be obtained using OMA SUPL

7. Stage 3 Protocols • X.P0013-004 “All IP Core Network Multimedia Domain” • Based on 3GPP’s Stage 3, TS 24.229 “IMS call control based on SIP/SDP” • Will be part of X.P0013-004 Rev. C • Effort started Feb. 2007 • C.S0024 Rev. B - HRPD access network enhancements are complete: • Emergency call indicator in HRPD session request

8. HRPD / PDS Details • 3GPP2 allows a wide range of packet data options • Simple IP or Mobile IP • IPv4 or IPv6 • Different packet data scenarios • Scenario 1: Endpoint powers up (Non-Authorized Mobile) • Scenario 2: Endpoint already has a Simple IP (v4 or v6) session • Scenario 3: Endpoint already has a Mobile IPv4 session • Scenario 4: Endpoint already has a Mobile IPv6 session

9. Non-Authorized Mobile

10. Mobile IP Access

11. Summary • 3GPP and 3GPP2 solutions are mostly aligned except for the access network related differences elaborated in slide #3 • 3GPP2 would like to work cooperatively with other groups to achieve global solutions. • Thank you!

12. Acronyms • DHCP – Dynamic Host Configuration Protocol • HRPD – High Rate Packet Data (3GPP2 access technology) • IMS – IP Multimedia Subsystem • MCC/MNC – Mobile Country Code/Mobile Network Code • MMD – Multi-Media Domain – 3GPP2 architecture that includes the IMS Core Network plus Packet Data Subsystem • PDS – Packet Data Subsystem • WLAN – Wireless Local Area Network