1Qualcomm Proprietary NG eCall Solution for 3GPP2 AC GPP2 TSG-AC WG1 Teleconference January 12, 2016

2Qualcomm Proprietary Advantages −Robust solution – uses packet data services with error correction/retransmission −High data rates for packet vs. in-band modem (<560bps under best channel conditions) enables fast transmission of large amounts of data −Extensible – can easily add −Other data, e.g., vehicle diagnostics, medical/health, crash and surrounding environmental sensors, vehicle deceleration profile −Other media types, e.g., video telephony, video stream, telepresence, high-quality audio, text for disability access, text for language translation −Commercial services for automotive OEMs/general telematics and infotainment −Concurrent with voice – no interruption of voice conversations −Easily harmonized standard across other wireless and wireline interfaces Migration to All-IP networks (decommissioning circuit-switched networks) −MNOs are considering migrating to All-IP/packet-switched networks (e.g., LTE) −Need to plan in advance as average lifetime of vehicle: years Motivation for NG-eCall

3Qualcomm Proprietary 2012: instigated by the EC to provide a long term migration path for support of eCall with 4G : studied by ETSI who recommended a solution based on IMS as the successor to inband eCall [Ref 1] : developed by IETF Ecrit for use by 3GPP [Ref 4] −Current draft is in final stage of approval (awaiting IETF last call) −The solution is based on use of IMS and would convey MSD in the control plane as part of SIP signaling −The solution is extensible and can convey new types of data (e.g. new data related to a vehicle, vehicle cargo or passengers) and new control information (e.g. to enable a PSAP to remotely turn off a vehicle engine, honk a horn, flash headlights) 2015: WI approved by 3GPP as an addition to Release 14 for LTE access −The objective of the 3GPP WI [Ref 2] [Ref 3] is stated as follows: −The objective of this work item is to specify the system impacts for an eCall based on IMS emergency calls that will allow for enhanced eCall user experience and functionality, and for the long-term phase out of CS core and access networks. History Next Generation (NG) eCall for the EU

4Qualcomm Proprietary The solution defined by IETF is access agnostic and can be used with any IP based access It is also expected that the 3GPP solution will be transposable to 3GPP2 access types HPRD Access −Support of IMS emergency calls over HRPD is defined in 3GPP2 X.S0060 −This solution could be combined with IMS enhancements from 3GPP Rel-14 to enable NG eCall over HPRD eHRPD access −Support of IMS emergency calls over eHRPD is defined in 3GPP2 X.S0057-A −This solution could be combined with IMS enhancements from 3GPP Rel-14 to enable NG eCall over eHPRD 3GPP2 specific impacts −Access related impacts (e.g. to support eCall only mode) can be performed in 3GPP2 −Regional related impacts (e.g. to support different MSD content) can be performed in local SDOs Migration to LTE −An IMS based solution over HRPD or HRPD should be easy to migrate to LTE access 3GPP2 NG eCall in 3GPP2

5Qualcomm Proprietary IMS related protocols (e.g. SIP) for (2) and (3) can be the same as for 3GPP and IETF or a variant of this IVS to PSAP related interaction for (4) may need to differ from that in [Ref 4] – e.g. MSD content could differ IVS to access network interaction for (1) will differ from that for LTE for 3GPP but may support the same functions – e.g. “eCall only mode” Overview of NG eCall for 3GPP2 (1) High Level Architecture for direct access to PSAP

6Qualcomm Proprietary The TSP may be accessed in the same or in a similar manner to that for direct access to a PSAP From the perspective of the serving network, the eCall may be seen as a normal call or as an emergency call Normal call treatment would require some change to SIP eCall treatment – e.g. use of a Request URI that does not include “sos” The TSP to PSAP leg (5) could make use of a normal voice call or could employ NG interaction Overview of NG eCall for 3GPP2 (2) High Level Architecture for access to PSAP via a Third Party Service Provider (TSP)

7Qualcomm Proprietary eCall Establishment Procedure with direct PSAP Access (1) Flow Diagram

8Qualcomm Proprietary eCall Establishment Procedure with direct PSAP Access (2) Step Description 1)The IVS may optionally stay in eCall only mode in which there is no signaling with the AN 2)The IVS detects an emergency situation – e.g. from a sensor or user input 3)The IVS attaches to the AN – e.g. according to 3GPP2 X.S0060 for HRPD access or 3GPP2 X.S0057-A for eHRPD access 4)The IVS performs IMS emergency registration with the IMS in the serving network and with the HPLMN when roaming – this applies to eHRPD and to HRPD when roaming 5)The IVS sends a SIP INVITE to the IMS (P-CSCF) in the serving network carrying an emergency indication, eCall indication and the MSD 6)The serving network IMS (E-CSCF) forwards the SIP INVITE to the appropriate PSAP 7)The PSAP returns a SIP 200 OK to the IMS (E-CSCF) including a confirmation of MSD receipt 8)The IMS (P-CSCF) forwards the SIP 200 OK to the IVS 9)The remainder of call establishment occurs – mainly establishment of a voice media path

9Qualcomm Proprietary eCall MSD Request Procedure with direct PSAP Access (1) Flow Diagram

10Qualcomm Proprietary eCall MSD Request Procedure with direct PSAP Access (2) Step Description 1)The PSAP sends a request for updated MSD to the serving network IMS (e.g. the E-CSCF) 2)The serving network IMS (e.g. P-CSCF) forwards the request to the IVS 3)The IVS obtains updated MSD (e.g. new sensor readings, updated location) and returns to the serving network IMS (e.g. P-CSCF) 4)The serving network IMS (e.g. E-CSCF) forwards the updated MSD to the PSAP.

11Qualcomm Proprietary 3GPP2 Impacts Base NG eCall in 3GPP2 on common IMS support expected in 3GPP for Release 14 and on IETF standards Provide HRPD and eHRPD support for “eCall only mode” if needed −eCall only mode enables an IVS to avoid signaling with a serving network except to originate an eCall, originate a test or reconfiguration call to a home network number and, for a short time after either of these, receive an incoming call from a PSAP or the home network −Impacts can be restricted to the IVS (MS) and should not impact the network Modify the content of the MSD −NG eCall for the EU in 3GPP is expected to use MSD as defined by CEN in [Ref 6] −For other regions (e.g. China), different MSD content and formatting can be defined by regional SDOs Include any other data and control information (metadata) if needed using the IETF mechanisms defined in [Ref 4] and [Ref 5] The 3GPP2 impacts can be a small delta to the IETF and 3GPP solutions that could be completed during 2016 if agreed by 3GPP2 and regional SDOs

12Qualcomm Proprietary A 3GPP2 solution for NG eCall over HRDP and/or eHRPD can be based on IETF and 3GPP solutions with a small delta (e.g. to support eCall only mode and/or modified MSD) The solution can later be migrated to LTE access with minimal impact at the IMS level The solution avoids dependence on circuit switched access which may be phased out later The solution can provide improved performance (compared to an inband solution) including faster and more reliable MSD transfer and no interruption of voice communication The solution can be easily extended later to support other media and other data and control signaling Conclusions

13Qualcomm Proprietary ANAccess Network CENEuropean Committee for Standardization ECEuropean Commission eHRPDEvolved HRPD ETSIEuropean Telecommunications Standards Institute EUEuropean Union HRPDHigh Rate Packet Data IMSIP Multimedia Subsystem IVSIn Vehicle System LTELong Term Evolution MSDMinimum Set of Data NGNext Generation TSPThird Party Service Provider Abbreviations

14Qualcomm Proprietary [Ref 1] ETSI TR ( ): "eCall for VoIP“. [Ref 2] 3GPP SP , Work Item on “Evolution to and Interworking with eCall in IMS” (stage 1), June [Ref 3] 3GPP SP , Work item on “Evolution to and Interworking with eCall in IMS Stage 2”, December [Ref 4] IETF draft-ietf-ecrit-ecall-05, “Next-Generation Pan-European eCall”, November [Ref 5] IETF draft-ietf-ecrit-car-crash-05, “Next-Generation Vehicle-Initiated Emergency Calls”, November [Ref 6] EN 15722:2015 "Intelligent transport systems - ESafety - ECall minimum set of data". References