80 likes | 199 Views
Status of VoIP Emergency Services Support in 3GPP2. QUALCOMM, 8 September 2006. Summary of Current Status. Requirements (stage 1) Latest version is 3GPP2 S.P0115-0 Version 0.4 ( S.P0115 ) Produced by 3GPP2 TSG-S with input from TSG-X
E N D
Status of VoIP Emergency Services Support in 3GPP2 QUALCOMM, 8 September 2006
Summary of Current Status • Requirements (stage 1) • Latest version is 3GPP2 S.P0115-0 Version 0.4 (S.P0115) • Produced by 3GPP2 TSG-S with input from TSG-X • Now undergoing V&V with approval expected in the September Xian meeting • Design (stage 2) • Most impacts (e.g. MMD) will concern TSG-X • Some impacts (e.g. HRPD, WLAN) will concern TSG-C • Work has not yet started formally although interested companies have been discussing informally • Signaling (stage 3) • Expected to start some time after the Design starts but possibly before it is complete Note: TSG-S cover Services and Systems Aspects; TSG-C cover the cdma2000 radio interface; TSG-X cover the Core Network
Within Requirements - 1 • PSTN capable PSAPs • IP capable radio interfaces • HRPD (cdma2000-EvDO) • cdma2000-1x • WLAN • Authorized UEs • implies home network subscription and roaming agreement • Voice calls • Support for roaming and non-roaming scenarios • Note that serving and home systems are assumed to be cdma2000 • Routing to a PSAP based on the caller’s location and the required PSAP (e.g. fire, police, ambulance etc.)
Within Requirements - 2 • PSAP callback based on a TEL URI • Inclusion of UE location (cell/sector, civil or geographic) in an emergency call request when available • Provision of accurate initial UE location to a PSAP • Provision of accurate updated UE location to a PSAP during the call • Support handoff between access technologies (same or different) whenever handoff is supported for non-emergency calls • Accurate updated UE location following a handoff • Call Detail Records • Restriction of any supplementary service (e.g. Call Waiting) which would place an emergency call on hold • Priority of emergency calls over other services
Within Requirements - 3 • A UE SHOULD be able to detect an emergency call • Support for local emergency numbers and addresses (TEL URI, SIP URI) • Call control signaling and bearer MAY be handled in the serving network without routing through the home network • Minimizing call setup delay has high priority • Additional essential capabilities (e.g. voice call continuity) may affect the preference for visited versus home network support
Excluded from Requirements • IP (SIP) capable PSAPs • Additional media (e.g. text messages, pictures, video) • Calls from unauthorized UEs (e.g. no UIM) • Note that some of these items may be supported in a later phase
Design Expectations • Likely to maximize use of existing 3GPP2 capabilities – MMD (IMS), HRPD, WLAN, LCS • Based on (e.g.) experience in 3GPP and solutions from NENA, impacts to MMD, HRPD, WLAN, LCS can be expected • New servers likely to be added to the serving network – e.g. specialized SIP server (CSCF or AS) for emergency calls, separate location and routing server(s) • Reference to or inclusion of IETF and NENA capabilities (e.g. Geopriv pidf-lo, LoST, NENA i2)
Design Questions • IP Access • Simple IP versus Mobile IP • For MIP, Home Agent in the home network or allowed in the visited network • IPv4 versus IPv6 • Which combinations should be supported? • Registration in the home network via the serving network (e.g. serving network P-CSCF) or not • Call establishment exclusively via the visited network versus via the home network (and visited network) • Suitable procedures for obtaining an interim location for routing and a more accurate location for PSAP delivery • Support of handoff and voice call continuity (VCC) • Applicability of ongoing solutions in 3GPP, NENA, IETF