1. 5th Emergency Service Coordination Workshop 3GPP Update www.3gpp.org Deb Barclay Alcatel-Lucent October 2008

2. 2 | 3GPP Update – 5 th SDO ES Workshop | Oct’08 3GPP Work/Study Items related to Emergency Services  Release 9 – target: Stage 1 – Dec’08, Stage 2 – June’09?, Stage 3 – Dec’09?  Support for IMS Emergency Calls over GPRS and EPS (TR 23.869)  EPS support for Control Plane Location Services (TR 23.891)  Single radio emergency call continuity (TR 23.870)  (con’t) Feasibility Study for IMS Emergency Call Enhancements (TR 23.868)  (con’t) Feasibility Study for dual radio emergency call continuity (TR 23.826)  Release 8 – Stage 1 and 2 complete, Stage 3 targeted for Dec’08  Circuit Switched Fallback (TS 23.272)  eCall (only applies to CS calls) (no Arch/Stage 2 required)  Earthquake and Tsunami Warning System – see Thurs. presentation  Feasibility Study for IMS Emergency Call Enhancements (TR 23.868)  Feasibility Study for dual radio emergency call continuity (TR 23.826)  3GPP2 cdma2000 Common IMS (TS 23.167)

3. 3 | 3GPP Update – 5 th SDO ES Workshop | Oct’08 Support for IMS Emergency Calls over GPRS and EPS - main functional components to support packet based emergency calls Access Location Service - Rel.7: IMS Support for Emergency Calls (TS 22.101, TS 23.167, TS 24.229) - Rel.9 IMS Extensions for IMS Emer study - Rel.9 DR-VCC for IMS Emer study - Rel.9 SR-VCC for IMS Emer - OMA Loc - SUPL 2.0 added initial support for LTE, SUPL 3.0 will have additional enhancements (Rel.8) - Rel.9 Control Plane Geolocation solution - Rel.9 Support for IMS Emergency Calls over GPRS and EPS - Rel.9 SR-VCCfor IMS Emergency Calls - Rel.8 Circuit Switched Fallback

4. 4 | 3GPP Update – 5 th SDO ES Workshop | Oct’08 Support for IMS Emergency Calls over GPRS and EPS - definitions  GPRS - General Packet Radio Service: the 3GPP common packet domain Core Network that is used for both the 2G GSM and 3G UMTS Radio Access Networks (RAN). The packet domain uses packet-mode techniques to transfer high- speed and low-speed mobile data and signalling in an efficient manner. See TS 23.060  EPS - Evolved Packet System: 4G; EPS is an evolution of GPRS characterized by higher-data-rate, lower-latency, packet-optimized system that supports multiple radio access technologies. The Evolved Packet System comprises the Evolved Packet Core (EPC) together with the evolved radio access network (E- UTRA and E-UTRAN). (This has also been referred to as LTE (Long Term Evolution)). See TS 23.401  The EPC also supports IP connectivity to non-3GPP access technologies including WiMAX and cdma2000 using IETF-based mobility management mechanisms. See TS 23.402

5. 5 | 3GPP Update – 5 th SDO ES Workshop | Oct’08 Support for IMS Emergency Calls over GPRS and EPS EPS Architecture: Roaming – Home routed traffic S6a HSS S8 S3 S1 - MME S10 UTRAN GERAN SGSN S11 Serving Gateway UE “ LTE - Uu ” - E-UTRAN S12 HPLMN VPLMN PCRF (2) Gx Rx SGi Operator’s IP Services (e.g. IMS, PSS, etc.) (3) PDN Gateway (1) S 1 - U S4 MME IMS Emergency Calls - Local Service - Not a subscription service (QoS, roaming) - Priority - Location - IP Addresses have traditionally been assigned from the home network (1) - Policy/Charging (PCRF) was controlled from the home network (2) - IMS in the home network provided consistent service even when roaming (3)

6. 6 | 3GPP Update – 5 th SDO ES Workshop | Oct’08 Support for IMS Emergency Calls over GPRS and EPS EPS Architecture: Roaming – Local Breakout with Visited Operator IP Services -EPC option allowing an IP address to be assigned from the visited network (1) - Policy/Charging coordinated between home and visited operators (2a, 2b) - IP Services may be obtained from the visited network (3)

7. 7 | 3GPP Update – 5 th SDO ES Workshop | Oct’08 Support for IMS Emergency Calls over GPRS and EPS (TS 23.869)  Ability to detect a request to provide bearer service for an IMS Emergency Call  Ability to provide access depending on local regulation  Must have valid subscription in an allowed area/location (normal service mode)  Access to UEs in limited service mode:  Must have an authenticated identity; may be in a restricted area/location  Access required regardless of subscription (i.e., SIMless allowed too)  Ability to provide bearer Quality of Service independent of subscription  IP Service Type? Reuse of Local IMS Service Type or new Emergency IMS?  Handover between 3GPP packet technologies (E-UTRAN UTRAN); handover to GERAN (GSM packet) will not be specified since SR-VCC to GSM CS will.  Handover between 3GPP E-UTRAN and non-3GPP packet technologies (e.g., cdma2000, WiMAX)  Ability to handover into a restricted area (what to do with non-emer bearers)

8. 8 | 3GPP Update – 5 th SDO ES Workshop | Oct’08 EPS/E-UTRAN Control Plane Location Architecture “B” TR 23.829 – EPS Control Plane Location Architecture Alternatives - TS 23.271 3GPP Control Plane Location Services - SMLC has been part of RAN – for UTRAN, it was associated with the RNC - EPS has a flatter RAN architecture; LS may be associated with MME and LS messages tunneled through the MME to RAN/UE

9. 9 | 3GPP Update – 5 th SDO ES Workshop | Oct’08 Single radio emergency call continuity (TR 23.870)  New Rel.9 work item  Dependent on DR-SRVCC study, Rel.8 SRVCC capability and Rel.9 EPS/GPRS IMS Emergency Call capability  Allows a single radio, multi-mode UE to handover from E-UTRAN to circuit mode voice. (i.e., the solution does not require UE with multiple radio access technologies (RATs) capability to simultaneously signal on two different RATs)  Includes EPS/E-UTRAN to legacy 3GPP CS (GSM/UTRAN) and EPS/E-UTRAN to legacy cdma2000 CS (1x)  RAT change and domain selection should be under network control (visited network when roaming).  Call must be anchored in IMS (at the VCC AS).  Work Item approved Sept’08  First 3GPP SA2 session Oct’08 where TR outline and scope were agreed.

10. 10 | 3GPP Update – 5 th SDO ES Workshop | Oct’08 Single radio emergency call continuity (con’t 2) SRVCC architecture for E-UTRAN to 3GPP2 1xCS -Architecture from TS 23.216 Rel.8 SRVCC; break before make call transfer; need to minimize the “break” - Support for emergency calls - If not authenticated, may not have subscriber data; can SRVCC be supported - How to convey emergency call context - Can SRVCC for emergency be supported inter-operator? - IMS VCC AS is the call anchor point, maintains the call context, interface point to LRF

11. 11 | 3GPP Update – 5 th SDO ES Workshop | Oct’08 Feasibility Study for dual radio emergency call continuity (TR 23.826)  Study started in Rel.8 and is continued in Rel.9  Consider support for dual radio, multi-mode UE to session continuity (handover) between IMS PS (e.g., WLAN) and 3GPP UTRAN/GSM CS  Make before break call transfer; can setup new domain while maintaining call in original domain  Call transfer typically provided from home IMS network. For emergency calls, must be controlled/anchored in visited network (i.e., need local call transfer identity; local anchor point in IMS).  Consider providing emergency priority/handling after call transfer.  Consider support for location continuity  Consider support for inter-operator session continuity  Consider support for session continuity of unauthorized UEs

12. 12 | 3GPP Update – 5 th SDO ES Workshop | Oct’08 Feasibility Study for IMS Emergency Call Enhancements (TR 23.868)  Study started in Rel.8 and is continued in Rel.9  The main goal is to extend the emergency call support to any access  De-couple the subscription of access network service and IMS network service  Emergency call with IP connectivity provided by access network A and IMS network B  Access network A can be any network, but IMS network B is either HPLMN or VPLMN that has got a roaming agreement with HPLMN  Outside the main goal also other enhancements are possible (e.g. reduction of complexity and performance improvement)  Study item to allow followup and alignment with IETF emergency call work (e.g. include HELD for location)  No commitment to normative specification changes at study phase  Any changes to normative specifications will require a 3GPP work item  Backwards compatibility with Rel-7 is required  This means Rel-7 and Rel-8 mobiles and networks can co-exist in the same system;  It does not mean Rel-8 must behave the same way as Rel-7 did;  Rel-8 design must take the existing Rel-7 into account

13. 13 | 3GPP Update – 5 th SDO ES Workshop | Oct’08 Common IMS – 3GPP2 cdma2000 Emerergency Services (TS 23.167)  Common IMS workshop held January 2008 where most of the 3GPP2 IMS capabilities were proposed to bring into 3GPP under the Common IMS program, including Emergency Call support  TS 23.167 was updated to include cdma2000 (HRPD)  Since IMS is somewhat “access technology agnostic”, minimal updates were required  Terminology in TS was generalized (e.g., GMLC changed to “Location Server”) and HRPD was added to supported access techologies.  References added for 3GPP2:  air interface procedures  emergency call packet network procedures  CS emergency call procedures  Annex created for cdma2000 (HRPD) access specific procedures

14. 14 | 3GPP Update – 5 th SDO ES Workshop | Oct’08 Circuit Switched Fallback (TS 23.272)  Release 8 – general capability for a UE operating in E-UTRAN/packet mode to be redirected to circuit mode for services  Used by packet data only E-UTRAN UEs in order to receive services such as voice, sms  Can be used by Voice over IMS UEs to originate emergency calls

15. 15 | 3GPP Update – 5 th SDO ES Workshop | Oct’08 eCall (figure source unknown)

16. 16 | 3GPP Update – 5 th SDO ES Workshop | Oct’08 eCall (con’t 2)  Stage 1 – TS 22.101 “3GPP Service Aspects”  eCall - A manually or automatically initiated CS emergency call, from a vehicle, supplemented with a minimum set of emergency related data (MSD), as defined under the EU Commission’s eSafety initiative. Allows the transfer of inband data during an emergency call  MSD: The Minimum Set of Data forming the data component of an eCall sent from a vehicle to a Public Safety Answering Point. The MSD has a maximum size of 140 bytes, is defined by the public safety authorities and includes, for example, vehicle identity, location information and time-stamp.  An eCall may be initiated automatically, for example due to a vehicle collision, or manually by the vehicle occupants (manual/auto is indicated in the call setup message)  The MSD should typically be made available to the PSAP within 4 seconds measured from the time when end to end connection with the PSAP is established

17. 17 | 3GPP Update – 5 th SDO ES Workshop | Oct’08 eCall (con’t 3)  The Manual/Automatic eCall indicator in the emergency call setup may be used to filter or route eCalls to dedicated PSAP operators.  A call progress indication shall be provided to the user while the MSD transmission is in progress.  Both the voice and data components of the emergency call shall be routed to the same PSAP or designated emergency call centre.  Should the PSAP request additional data then this may be possible during the established emergency call.  The realisation of the transfer of data during an emergency call shall minimise changes to the originating and transit networks.  The transmission of the data shall be acknowledged and if necessary data shall be retransmitted.  eCall-only mode UEs shall contain an USIM application

18. 18 | 3GPP Update – 5 th SDO ES Workshop | Oct’08 eCall (con’t 4)  3GPP SA4 has selected a solution for the in band modem based on an evaluation between three candidate solutions, evaluated by an independent test company that measured the performance against some criteria defined in 3GPP SA4.  The key Technical Specifications for eCall data transfer is expected to be approved in December 2008. These TSs are TS 26.267 "eCall Data Transfer - in-band modem solution; General Description" and TS 26.268 "eCall Data Transfer - in-band modem solution; ANSI-C Reference Code".  The two additional specifications, TS 26.269 "eCall Data Transfer - in-band modem solution; Conformance testing" and TR 26.969 "eCall Data Transfer - in-band modem solution; Characterisation Report", are expected to be finalised by June, 2009.

19. 19 | 3GPP Update – 5 th SDO ES Workshop | Oct’08 Backup

20. 20 | 3GPP Update – 5 th SDO ES Workshop | Oct’08 IMS Emergency Services Architecture (TS 23.167) Ml to PSAP ( via PSTN v ia BGCF / MGCF ) to PSAP or ECS via IP mutimedia Network UE P - CSCF E - Gm Mw Mi / Mg Mm S - CSCF Mm / M w Mw from PSAP Le ( e. g. E 2 ) from PSAP LRF Note : LRF = Location / Routing Function : may have GMLC / SUPL within