Pan European eCall webinar: Encouraging cooperation for successful deployment

1. Pan European eCall webinar: Encouraging cooperation for successful deployment Francesca Forestieri Director, mAutomotive, Connected Living Programme

2. GSMA Connected Living programme Vision 2020: To create a world where everything intelligently connects via mobile networks, delivering rich services to businesses and consumers in every aspect of their lives mEducation mHealth mAutomotive Service Awareness & Roaming Mission: To accelerate the development and adoption of operator led scalable and interoperable mobile solutions: Operator Leadership Board Sponsors KT, Telenor, Vodafone Smart Cities Demonstrator (Mobile World Capital) Programme Leadership Group AT&T, KT, Telenor, Vodafone Connected Experiences Campaign

3. Objectives for the Webinar • Objective: Stimulate Mobile Network Operator compliance with eCall • Update Operators on the status of eCall • Provide information on the obligation for Operators • Identify any common future action points • Foster inter-operator discussion on eCall compliance

4. What is eCall? • Public “eCall” is the future pan-European in-vehicle emergency call system, expected to be operational beginning in 2015. • Will automatically trigger an emergency call for severe accidents. • Creates a voice link to the closest Public Safety Answering Point (PSAP) and • Sends an emergency message (minimum set of data), including key information about the accident, such as: time, accurate location, driving direction and vehicle description. • Can also be activated manually. • Private Third Party emergency Call are proprietary value-add services (e.g., Volvo OnCall, GM OnStar, PSA, Fiat, BMW). These services are expected to continue to exist.

5. Regulatory Framework for eCall

6. Regulatory Framework for eCall

7. Member State Progress Reports • 19 Member States have communicated to the European Commission their evaluations of the readiness for eCall Deployment • 6 Member States indicated that the Commission Regulation for Operators was not sufficient to guarantee successful deployment of eCall, in particular: • Italy • Romania • Greece • Sweden • Slovakia • Czech Republic • Austria indicated that they were not sure if a regulation was necessary • Denmark Indicated that Operators were refusing to Implement the eCall Flag

8. Webinar Agenda

9. Thank you!Francesca Forestierifforestieri@gsm.org www.gsma.com

10. eCall webinar: standardisation status13th Sep 2012 Nick Sampson, ETSI MSG vice-chair

11. Contents • Overview of eCall standards • The eCall flag • eCall idle mode (“dormant SIM”) • Future of eCall transport solution • Implementation in MNOs • Summary

12. CEN: MSD (data)   3GPP: eCall idle mode 3GPP:eCall flag   = Standards approved or under final approval vote eCall Standardisation Status Pan-European eCall (112 + in-band modem)  CEN: Pan-European eCall operating requirements  CEN: High level application protocols  3GPP:In-band modem  3GPP:In-band modem

13.  = Standards approved or under final approval vote eCall Standardisation Status Third-party service (TPS)  CEN: TPS supporting eCall – Operating Requirements CEN: MSD (data) 

14. eCall flag (3GPP TS 24.008) • eCall uses normal voice call emergency (TS12) set-up message • The Emergency Category field is set to either • Manually initiated eCall • Automatically initiated eCall • This can be used by the MSC to route the eCall to a different number than normal emergency calls • E.g. specific eCall PSAP, specific modem/answering point, filtering point etc • Allows manually and automatically initiated eCalls to be differentiated • Routing requirement should be defined by national administrations • Note: the eCall flag is not sent beyond the MSC; the indication is based on the Called Number in the ISUP (or equivalent) signalling

15. eCall Dormant SIM - motivation • In-vehicle devices, by their nature, can generate significant volumes of mobility signalling • at switch-on/switch-off, change of location area, MSC etc • signalling is generated in both home and visited network • eCalls are made very rarely • Operators raised concern about the impact of this signalling

16. eCall Dormant SIM - standards • 3GPP (Release 8) has introduced an eCall-only mode: • An eCall-only UE (User Equipment) is in a dormant state (“eCall INACTIVE”) until an eCall, test call or reconfiguration call is made • The UE is ‘listening’ (a cell is selected), but network registration is not done until the call is made • No location update, periodic update etc • The UE shall continue mobility management procedures after an eCall call (or reconfiguration call) has terminated • to allow the Callback (or OTA reconfiguration) • for a period of 12 hours, then UE returns to “eCall INACTIVE” state • It shall be possible for the network operator to reconfigure (unrestrict) an eCall-only UE so that it can access subscribed services (and to restrict a previously unrestricted UE) • This is the reconfiguration call above

17. eCall dormant SIM – USIM configuration • The device implements the e-Call Only dormant state functionality • The USIM configuration determines whether the device behave as eCall-only device • the device reads the configuration information from the USIM • The eCall configuration is only specified for the USIM; It is not specified for the SIM (the SIM specification was frozen in 3GPP Release 4) • The USIM • indicates whether eCall is available, and if only eCalls are supported, or both eCalls and normal calls • stores test and reconfiguration numbers • USIM reconfiguration is needed to: • reconfigure an eCall-only capable UE to allow access to additional services • restrict an eCall-capable UE to allow access to eCall only

18. eCall dormant SIM - Implications and considerations • Will there be eCall-only devices? • Or, do operators require that there are eCall-only devices? • What will be the mechanism for controlling the eCall-only mode? • USIM, or proprietary? • If USIM, USIMs for eCall need to be configured correctly • If proprietary, how does operator ensure correct behaviour? • Need to define the reconfiguration process that is triggered by the reconfiguration call • who is involved, and with what role? • What happens if ignition is switched off after a reconfiguration call but before reconfiguration is complete? • depends on reconfiguration method

19. Future of eCall transport solution • Current eCall transport solution is specified for GSM and UMTS • ETSI MSG#29 (in March 2012) agreed a new work item on migration of eCall transport that will include the following: • Assessment of in-band modem solution in case of no use of CS bearers. • Study the adaptation of IMS emergency call and IMS Multimedia Emergency Service for supporting current and future service required by eCall. • Hybrid CS/IMS solution. • Migration recommendations • Target for MSG approval of the deliverable is 31/3/2013 • In addition, MSG#29 agreed a proposal for an ETSI Special Task Force (STF) on migration of eCall transport. • This has been approved by the ETSI Board, and is under evaluation by the European Commission

20. Implementation in MNOs • The eCall standards are just one part….. MNOs also need to consider: • SIM cards • Provisioning, reconfiguration, subscription management, relationship with SIM supplier and vehicle OEMs • HLR provisioning/capacity • Testing • Testing and certification of eCall devices? • Arrangements for periodic in-the-field testing? • Numbering resources – IMSI and MSISDN

21. Summary • eCall standards are complete • EC have issued recommendation to Member States to ensure MNOs implement the eCall flag by end 2014 • There are implementation aspects beside the standard itself • Is there benefit in MNOs discuss some of these aspects collectively?

22. eCall implementation – Ways and reasons to support Date : 13th September 2012 Final Version : 1.0 CONFIDENTIAL

23. Support of eCall at the MNO • The eCall flag • Necessary for all European MNO’s. • The eCall flag need to be implemented according to the specification to be able to transfer the eCall to the correct PSAP. • The eCall flag are 2 bits of the “emergency category”. • eCall flag needs to be implemented before member states can receive/route eCalls to a PSAP. • Dormant SIM • Applies only to MNO’s that issue SIM card embedded in eCall systems used in vehicles. • The Dormant SIM itself plus the update of them need to be supported. • Dormant SIM is a SIM that is able to tell the GSM terminal to activate dormant mode. • If a SIM is not dormant it will signal all the time when it moves and also when it is not moving through its “Location Updates” and “Periodic Location Updates”.

24. Why routing is necessary? Country- PSAP Setup variety

25. Coexistence of the eCall solutions Call back function support Dial 112 Dial XXX

26. Thank you! Andrea Sroczynski - Head of Global Automotive Sales Andrea.Sroczynski@telenor.com t: +49 2191 79 19 262 / m: +49 172 246 1379

27. eCall Deployment: Results from HeERO pilot Telecom Itala S.p.A /Service Platform Innovation- ITS & Logistics ETSI TC ITS Vice Chairman Marco Annoni

28. Outline • eCall needs and related requirements • Overview of the European Pilot (HeERO) • HeERO Italian Pilot • Topologic Model Alternatives • Routing Mechanisms • Status and Open Issues Telecom Italia S.p.A./Service Platform Innovation – ITS & Logistics Marco Annoni

29. eCall – Main EC Drivers & Requirements • Public Safety service • Additional features and value to the E112 deployment • Time reduction for rescue intervention • Provision of reliable data to increase rescue efficiency • Interoperable EU-wide service • Gradually deployable on all vehicles • Availability, Reliability and Testability • Long life-cycle (modular and upgradable solutions) • Free of charge for the end-user • Integrated with the extended ITS services ecosystem Marco Annoni, Telecom Italia S.p.A./Service Platform Innovation – ITS & Logistics

30. HeERO (Harmonised eCall European Pilot) Start date: 01/01/2011 Duration: 36 months Total budget: 10M EC contribution: 5M Coordinator: ERTICO 40 partners – 9 Member and Associated States Marco Annoni, Telecom Italia S.p.A./Service Platform Innovation – ITS & Logistics

31. eCall Public Service - Functional Architecture Marco Annoni, Telecom Italia S.p.A./Service Platform Innovation – ITS & Logistics

32. HeERO – Italy Pilot : Objectives and Expectations • Establish a multi-sector national Working Group able to develop a common vision and a realistic roadmap for the deployment of the eCall in Italy • Jointly assess and test the technological solutions in a realistic environment and identify the possible issues • Collect usability/operational experience from all actors involved in the pilot • National Government (Ministry Counsil Pres.  Min. Interiors, Min. Transp) • Vehicle Maker (CRF  FIAT) • Fixed & Mobile Network Operator (Telecom Italia) • Telematic Provider (Magneti Marelli) • PSAP Operator (AREU  Reg. Lombardia) • Driver’s National Association (ACI) • Analyze the possibility to enable commercial value added services by means the same eCall in-vehicle system • Increase the public awareness about eCall • Identify the national-specific process issues Marco Annoni, Telecom Italia S.p.A./Service Platform Innovation – ITS & Logistics

33. HeERO – Italy Pilot : the eCall Roadmap Marco Annoni, Telecom Italia S.p.A./Service Platform Innovation – ITS & Logistics

34. eCall Deployment on top of the legacy infrastructure • The actual end-to-end network topology is more complex than in the theoretical architecture • In most EU countries eCall network infrastructure extends the legacy infrastructure for public E112 service • Most of EU Member States currently adopt a topology consisting of a network of several PSAPs geographically distributed over the country (typically at either regional or provincial level) • When a legacy infrastructure exists, each PSAP is typically specialized (e.g. police, fire brigade, emergency rescue) and operated by a different body • Different roadmaps exists for the actual deployment depending of the PSAP model adopted at national level Marco Annoni, Telecom Italia S.p.A./Service Platform Innovation – ITS & Logistics

35. Current PSAPs network topology • Topology to be replicated in each district/province/region • eCall routed to one of the local emergency service  all of them should be upgraded to become able to manage the eCall • Coordination/interaction is needed among different emergency services PLMN domain PSTN domain or or Marco Annoni, Telecom Italia S.p.A./Service Platform Innovation – ITS & Logistics

36. 1° and 2° Level PSAPs network topology • Topology to be replicated in each district/province/region • eCall routed to the designated 1° level PSAP able to process the incoming eCall • Specialised PSAPs at 2° level PLMN domain PSTN domain Marco Annoni, Telecom Italia S.p.A./Service Platform Innovation – ITS & Logistics

37. MSC MNO A MSC MNO B MSC MNO C eCall Processing eCall PSAP Region 1 Region1 National PSTN Domain Loc Req (OpID+CLI) Loc Req (OpID+CLI) eCall discr. + MSD + Voice MSD+Voice +OpID+CLI eCall PSAP Region 2 Region2 Marco Annoni, Telecom Italia S.p.A./Service Platform Innovation – ITS & Logistics

38. Multi-MNO Routing mechanisms over PSTN • Requirements • Once fully deployed at national level, the eCall processing has to be MNO-independent in terms of routing through the fixed PSTN. • Service must be supported in international roaming conditions • No realistic possibility to modify the SS7/ISUP (ISDN User Part) signalling • Routing solution proposed in Italy • performed by means of a dedicated RgN in the Called Party Number field agreed at national level among the MNO and the involved ministries. Marco Annoni, Telecom Italia S.p.A./Service Platform Innovation – ITS & Logistics

39. CED INTERFORZE 112 NUE OC eCall routing scheme Mobile Op. 1 PSAP 112 Europeanupgraded for e-Call 112 RgN1+11x+9+OP_ID User e-Call (Man) e-Call (Aut) RgN2+112+Y+OP_ID Mobile Op. 2 112 + OP_ID Mobile Network Location RgN1 + ..... 112 User e-Call (Man) RgN2 + ..... 112_e-Call (Aut)+OP_ID e-Call (Aut) ISDN 112_e-Call (Man.)+OP_ID eCall Process RgN2+112+Y+OP_ID Mobile Op. 3 RgN1+11x+9+OP_ID 112 User e-Call (Man) PdI ISUP e-Call (Aut) In-Band MODEM Marco Annoni, Telecom Italia S.p.A./Service Platform Innovation – ITS & Logistics

40. eCall routing scheme In order to route the eCall to the designated PSAP some additional parameter would be needed in the ISUP, but this is not feasible  the proper routing is achieved by means of a dedicated format of the Called Party Number field The format adopted to deliver the 112 emergency calls (E112 service) was : C97 0XYZ 11x 9 OP_ID With a similar mechanism, the following routing number has been proposed and agreed for the Italian routing of the ecall: CXX 0XYZ 112 Y OP_ID CXX = RgN; XX=96 is the value that has been proposed and accepted 0XYZ = origin district of the incoming eCall 112 = unified number for the eCall Y = type of e Call : Y=0 automatic eCall; Y=1 manual eCall OP_ID = Operator ID : code of the mobile network Marco Annoni, Telecom Italia S.p.A./Service Platform Innovation – ITS & Logistics

41. eCall status and open issues • Process • eCall service deployment in Italy requires some reorganization of thesafety/emergency management process at national level. • Fragmented deployment need to build on top of legacy infrastructure to save costs of the infrastructure deployment/adaptation • Technical • The current standards for the PLMN enable an adequate initial deployment. Qualification tests of the new mobile network features have been successfully completed by TI and the deployment in the Pilot area (Varese) is on-going • Impacts on signaling processing and routing in PSTN requested the adoption of a custom solutions at national level • Scalability and future technology compliance need to beachieved (through continuous standard evolution) • Costs & Business Models • Models to support national deployment & operational costs to be exploited • Integration with other ITS public utility and/or commercial services Marco Annoni, Telecom Italia S.p.A./Service Platform Innovation – ITS & Logistics

42. Conclusions • eCall is entering pre-operational phase • From a mobile/fixed telco operator perspective technology is mature but the end-to-end system will have to be able to support modular evolution and upgrades • TI started evaluating the needed network upgrades (e.g. eCall discriminator) as soon as the required features has been made available by network technology vendors • FNO’s need country specific solutions regulated by national government for properly routing the eCall coming from different MNO’s to the designated PSAP • HeERO Pilot Project is prooving a suitable tool for assessing the technical and deployment issues in a realistic environment with the involvement of all needed stakeholders • Initial deployment costs in the infrastructure (PSAPs and telco mobile and fixed networks)  need to guarantee significant level of adoption and service availability from day one • Need of suitable models for making initial deployment and daily operation economically sustainable for all involved parties Marco Annoni, Telecom Italia S.p.A./Service Platform Innovation – ITS & Logistics

43. THANKS ! Marco Annoni Telecom Italia S.p.A. Service Platforms Innovation – ITS & Logistics Vice-Chairman ETSI TC IS marco.annoni@telecomitalia.it Marco Annoni, Telecom Italia S.p.A./Service Platform Innovation – ITS & Logistics

45. Automotive: A connected future Importance of an embedded eCall solution Vodafone Global Enterprise Cyrille Ravier Business Development Manager M2M/Automotive

46. Agenda Introduction Mandates recommendembedded Embedded – Advantages & Disadvantages Remove barriersofembeddedhardwarecosts The opportunitieswithembedded 46

47. Introduction • All new “type approved” cars in the EU from 2015/latest early 2016 • All member states to draw up detailed rules for public mobile network operators. • All mobile network operators in Europe to: • Support of the eCall like any 112 call • Implement the eCall discriminator (by 31 December 2014) • This regulation, which will change the landscape in the EU, will result in wide-scale usage of connected vehicles 47

48. Mandates recommendembeddedeCall • A growing number of telematics mandates (EU, Russia, Brazil). All of these mandates are expected to require (or strongly recommend) embedded telematics • Note. “Although the EU’s mandate technically does not specify what type of connectivity should be used for eCall, the EC has already strongly spoken out against non-embedded systems such as Bluetooth-based eCall. The EC has highlighted concerns that the reliability of Bluetooth-based solutions would be compromised during a crash, or that the driver may not have connected the smartphone to the car before the crash.” 48

49. Embedded – Advantages & Disadvantages The eCallregulation will helptoremovethisbarrier Embedded gives the best performance for safety (E-Call) Itisthepreferred route oflegislators

50. Regulation to help to reduce hardware costs all cars being equipped with embedded Telematics Communication Units Short-term vision: volumes = reduce the cost of fitting embedded Hardware even in markets without legislation. Mid-term vision: more connected services Source : WirelessCar 50