deb barclay +1.630.690.2058 dlbarclay@alcatel-lucent
DESCRIPTION
3GPP2 All IP Emergency Calls SDO Emergency Services Coordination Workshop Washington DC 10-12 April, 2007. Deb Barclay +1.630.690.2058 [email protected]. Kirk Burroughs +1.408.626.0515 [email protected] QUALCOMM. Presentation Overview. 3GPP2 / 3GPP Alignment - PowerPoint PPT PresentationTRANSCRIPT
![Page 1: Deb Barclay +1.630.690.2058 DLBarclay@alcatel-lucent](https://reader030.vdocument.in/reader030/viewer/2022032709/56813253550346895d98d466/html5/thumbnails/1.jpg)
1
3GPP2 All IP Emergency CallsSDO Emergency Services Coordination Workshop
Washington DC 10-12 April, 2007
Kirk [email protected]
QUALCOMM
![Page 2: Deb Barclay +1.630.690.2058 DLBarclay@alcatel-lucent](https://reader030.vdocument.in/reader030/viewer/2022032709/56813253550346895d98d466/html5/thumbnails/2.jpg)
10 April 2007 2
Presentation Overview
– 3GPP2 / 3GPP Alignment
– Stage 1 – Requirements
– Stage 2 – Architecture / Call Flows
– Stage 3 – Protocol
– Summary
![Page 3: Deb Barclay +1.630.690.2058 DLBarclay@alcatel-lucent](https://reader030.vdocument.in/reader030/viewer/2022032709/56813253550346895d98d466/html5/thumbnails/3.jpg)
10 April 2007 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
![Page 4: Deb Barclay +1.630.690.2058 DLBarclay@alcatel-lucent](https://reader030.vdocument.in/reader030/viewer/2022032709/56813253550346895d98d466/html5/thumbnails/4.jpg)
10 April 2007 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)
![Page 5: Deb Barclay +1.630.690.2058 DLBarclay@alcatel-lucent](https://reader030.vdocument.in/reader030/viewer/2022032709/56813253550346895d98d466/html5/thumbnails/5.jpg)
10 April 2007 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
![Page 6: Deb Barclay +1.630.690.2058 DLBarclay@alcatel-lucent](https://reader030.vdocument.in/reader030/viewer/2022032709/56813253550346895d98d466/html5/thumbnails/6.jpg)
10 April 2007 6
IMS Emergency Call Architecture
BGCF: Breakout Gateway Control FunctionCSCF: Call Session Control FunctionE-CSCF: Emergency CSCFLRF: Location Routing FunctionMGCF: Media Gateway Control FunctionP-CSCF: Proxy CSCFS-CSCF: Serving CSCFSUPL: Secure User Plane LocationUE: User Endpoint* LRF – Location may be obtained using OMA
SUPL
Ml
to PSAP (via PSTNvia BGCF/
MGCF)
to PSAP or ECS via IP mutimedia
Network
UE P-CSCF E-CSCFGm Mw
Mi/Mg
Mm
S-CSCFMm/Mw
Mw
from PSAP
Le (e.g. E2)
from PSAP*LRF
![Page 7: Deb Barclay +1.630.690.2058 DLBarclay@alcatel-lucent](https://reader030.vdocument.in/reader030/viewer/2022032709/56813253550346895d98d466/html5/thumbnails/7.jpg)
10 April 2007 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
![Page 8: Deb Barclay +1.630.690.2058 DLBarclay@alcatel-lucent](https://reader030.vdocument.in/reader030/viewer/2022032709/56813253550346895d98d466/html5/thumbnails/8.jpg)
10 April 2007 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
![Page 9: Deb Barclay +1.630.690.2058 DLBarclay@alcatel-lucent](https://reader030.vdocument.in/reader030/viewer/2022032709/56813253550346895d98d466/html5/thumbnails/9.jpg)
10 April 2007 9
Non-Authorized Mobile
PDSN
Host Network
2. Request data connection(emergency)
3. A12: CHAP auth( emergency NAI)
4. A11: A10 connection
6. Get IP Addr
1. Session Negotiation
14: Authorize Session (CN IPaddr)
PCRFHRPD RAN AAA
16. Vocoded Speech
UE P/E-CSCF
8. Get P-CSCF Identity
10. Data(INVITE( SDP ))11. SIP: INVITE( SDP )
12. SIP: 180 Ringing(SDP)13. Data(180 Ringing(SDP))
15. SIP: Complete SIP session establishment
17. SIP session ends
18. Unauthorize CN - IPaddr
5. CHAP auth( emergency NAI)
9. Session Established
7. VoIP Bearer Path Established
![Page 10: Deb Barclay +1.630.690.2058 DLBarclay@alcatel-lucent](https://reader030.vdocument.in/reader030/viewer/2022032709/56813253550346895d98d466/html5/thumbnails/10.jpg)
10 April 2007 10
Mobile IP Access
PDSN
Visited Network
2. Request local IPaddr
PCRFHRPD RAN
AAA
UE P/E-CSCF
3. Return local IPadd
8. SIP: INVITE( SDP )
11. SIP: 180 Ringing(SDP)
12. SIP: Complete SIP session establishment
14. SIP session ends
PDSN PCRF IMS
Home Network
1. Existing HRPD MIP Session, local Carrier and local P-CSCF known to UE
4. SIP: REGISTER( ePUID)
5. SIP: REGISTER( ePUID)
6. SIP: 200 OK7. SIP: 200 OK
13. Vocoded Speech
9. SIP: INVITE( SDP )
10. SIP: 180 Ringing(SDP)
![Page 11: Deb Barclay +1.630.690.2058 DLBarclay@alcatel-lucent](https://reader030.vdocument.in/reader030/viewer/2022032709/56813253550346895d98d466/html5/thumbnails/11.jpg)
10 April 2007 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!
![Page 12: Deb Barclay +1.630.690.2058 DLBarclay@alcatel-lucent](https://reader030.vdocument.in/reader030/viewer/2022032709/56813253550346895d98d466/html5/thumbnails/12.jpg)
10 April 2007 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