Industry s Role in Accelerating the Roll-out of ecall A Tier 1 Supplier s Perspective

Transcription

1 Industry s Role in Accelerating the Roll-out of ecall A Tier 1 Supplier s Perspective Author: Brian Droessler, Continental Automotive Systems brian.droessler@us.contiautomotive.com February 14, 2007 B. Droessler Continental Automotive Systems Page 1 of 14

2 1.0 Introduction The European Commission s initiative of having a pan-european automatic crash notification system is a critical step in reducing overall traffic injuries and fatalities. This initiative, called ecall, is an attempt to reduce the roughly 41,000 fatalities and 1.7 million injuries happen each year on European roadways. With ecall, it is estimated that 2,500 lives may be saved. Furthermore, a May 2006 Eurobarameter consumer survey shows strong consumer demand for such a system with 62% of respondents stating they would like to have it in their next car. The benefits are clear. So, why has ecall not progressed as quickly as some had hoped? What needs to happen to achieve a timely introduction of ecall? The answers to these questions are unfortunately not simple. In this paper Continental Automotive Systems AG highlights the current market status and key issues to arrive at specific recommendation for how Industry can aid in a timely introduction of ecall. In addition, this paper presents results from one of the first end-to-end implementations of ecall that follows as closely as possible the April 2006 Final recommendations of the Driving Group ecall (DG ecall), a subgroup of the Driving Group Information Society (DG INFSO). 2.0 The Market The history of events surrounding the ecall initiative is long. The interested reader can refer to several sources of information for complete historical details. (See esafetyforum.com and sources cited in this paper.) In this section, we focus on the current status and the dynamics of what it will take to move forward. European Commission On November 23, 2006, the European Commission published Bringing ecall back on track Action Plan. This communication highlighted the good work accomplished thus far in creating specifications and planning for the implementation phases. However, several obstacles exist that are projected now to delay the roll-out of ecall. Despite these obstacles, the European Commission seems committed to first finding voluntary solutions to ecall implementation, consistent with DG INFSO recommendations. The European Commission s patience and resolve is evident in their proposal to work with Member States and Industry throughout The updated ecall implementation timelines published by the commission is: All key stakeholders should sign the Memorandum of Understanding (MoU) to ensure progress by end of 2006 Full specification of the ecall system and start of development by mid-2007 Full-scale field tests should be performed from the beginning of 2008 Member States should be ready with the upgrade of the Public Safety Answering Points (s) by September 2009 Introduction of ecall as standard option in all vehicles type-approved from 1st September 2010 onward B. Droessler Continental Automotive Systems Page 2 of 14

3 Member States In Nov-2006, only 7 out of 25 Member States and 2 out of 3 Associated States have signed the ecall MoU. The European Commission urged the remaining states to sign by the end of Member State commitments are absolutely essential in getting the necessary political and economic forces in place to move ecall ahead. It should be noted that part of securing Member State s commitment is the collaboration and standardization of protocols and implementation details to ensure that sufficient momentum exists behind a single pan-european solution. This further emphasizes the need for Industry collaboration. This will help the Commission as it works with Industry and Member States throughout s Much of the burden of ecall implementation appears to falling on the s. Situations vary by since some updates have already occurred with ecall requirements in mind. However, many s face the need to update or change their existing infrastructure and possibly organization. These updates require funding by Member States or private funds. Private funding has not been forthcoming. Without Member State s political and financial commitment to the ecall initiative, the local S will lack the funds to upgrade or change the infrastructure needed to accept ecalls. Without the updated systems in place, very few automobile manufactures or suppliers will introduce ecall compliant systems. Until this occurs only service provider assisted 112 and e112 emergency calling can exist. Automobile Manufacturers The European automobile manufacturers represented by ACEA (European Automobile Manufacturers Association) have been committed and engaged in ecall since the beginning. However, the manufacturers have difficulty installing ecall into vehicles until the Member States sign the MoU and updates have been made. Manufacturers also face the challenge of implanting, marketing and selling the in-vehicle system to consumers. The in-vehicle system increases the costs of the vehicle. Therefore, manufactures want an efficient, low-cost in-vehicle solution. Service Providers Existing Service Providers already see the value in ecall and have built businesses around this service. These service providers offer emergency calling as a core feature along with many other service. A pan- European ecall approach could be viewed to compete with the value already provided by these companies. However, the wide range of other services offered besides emergency calling positions service providers to be first to market in expanding the value of basic ecall. The Service Providers seek to balance ecall with the ability to offer other services and features to existing and future consumers. In the event of an emergency call, Service Providers still wish to be notified as part of the ecall service chain as they are today in order to offer additional services, such as insurance notification and consumer information. Cellular Carriers Cellular carriers desire an ecall solution that minimizes the potentially large investment in new or updated infrastructure across Europe and manages the impact on system capacity. Carriers wish to explore methods such as sleeping SIM which only use network capacity when needed for an ecall. These carriers are already making progress in supporting e112 and hope to use this as closely as possible in ecall implementation. B. Droessler Continental Automotive Systems Page 3 of 14

4 Consumers From a consumer standpoint, it is important to note that there is strong public support for ecall. Two data points from the December 2006 Eurobarometer study make this point clear. 62% of respondents state they would like to have ecall in their next car. Although privacy concerns are important to consumers, the same survey also revealed that on average, 73% of respondents viewed sharing of location information as a minor or of no inconvenience when considering the usefulness of the ecall system. However, 51% of the respondents in the same Eurobarameter study stated the number one reason they would put off purchase of safety systems in general was because it is too expensive to buy. This data indicates consumers want improved safety, but only at reasonable prices when they purchase their vehicle. Summary Cleary, the remaining Member States must sign the MOU and support the ecall roll out politically and financially in order to move the updates forward. The European Commission has outlined several steps it will take throughout 2007 to accomplish this. However, this does not mean the burden of ecall rollout falls solely on the European Commission and Member States to move forward. The Automotive Industry and Tier 1 suppliers must do their part to further standardize, collaborate, and develop inexpensive and timely solutions in parallel. Continental Automotive Systems recognizes this need and in the section 3 presents the work it has done with industry and its recommendations for moving forward. B. Droessler Continental Automotive Systems Page 4 of 14

5 3.0 Continental Automotive Systems Viewpoints and Recommendations In light of these market dynamics, there is still much work for industry to do. Continental Automotive Systems sees 4 areas critical for industry to focus on in order to answer the question posed, What needs to happen to achieve a timely introduction of ecall? 1) Collaboration between industry players 2) Use of agreed upon open standards ETSI, Recommendations of the DG INFSO 3) Minimize overall costs across the value chain - in-vehicle, carrier, and solutions 4) Evolutionary view - solutions that are updateable and expandable 1) Collaboration Collaboration between industry players around a common solution is crucial to a pan-european launch of ecall. Member States and s need to see a clear consensus on the platforms, protocols and methods used to realize ecall. To this end, Continental Automotive Systems has collaborated with a major mobile network operator, Airbiquity, and Swissphone, to create a demo that as closely as possible follows the DG INFSO recommendations. This collaboration focuses initially on the basics of ecall. Technical accomplishments include crash detection, MSD creation, in-band modem transmissions, GSM network transmission, and receipt by a terminal with mapping ability. Section 4 details this effort, its challenges and results. This type of collaboration, around the heart of ecall, is needed to ensure a timely roll-out. Additional features and use cases are under development now such as UMTS, Bluetooth, and sleeping SIM based solutions. Future collaborations that include Full Set of Data (FSD), value added services, service providers, and other use cases are required next. 2) Open Standards The idea and even implementation of ecall-like systems is not new. OnStar, OnCall, Assist, PSA s IMA, and others are clearly successful market leaders in safety, security, and advanced convenience features. Even Industry efforts such as GST Rescue, Austria s ecall pilot, and Finland s ecall test center are clearly creating collaboration and example implementations Although these systems have shown technical feasibility and high levels of quality, they are individual solutions that differ in approach. There is certainly room to discuss how these existing solutions might be deemed to comply with the essence ecall. These systems may represent the best ways of implementing emergency calling long before agreement is reached for ecall. What Member States and s need to see in order to realize a pan-european approach in a timely manner is a consistent solution that adheres to agreed upon open standards put forth by such groups as ETSI and the DG INFSO. Two examples of work that has progressed in this area is the drive to standardize through ETSI the in-band modem transport method and the DG INFSO definition of the overall ecall process and Minimum Set of Data (MSD). Adhering to a unified and open solution will allow Member States, operators and others to be assured that their investment will be used by Industry. B. Droessler Continental Automotive Systems Page 5 of 14

6 The demonstration presented in this paper is one of the first to follow the DG INFSO recommendations as closely as possible. A comparison of these recommendations and demonstrator contents is found below. DG INFSO Recommendations Automatic trigger of ecall (airbag or user button input simulation) Automatic trigger of ecall (other crash scenarios) Anti-falsing Manual trigger mechanism Precise location Direction of travel MSD format as specified Call initiation time <20s Transport Protocol in-band or USSD options Voice call established to Receives acknowledgement from of receipt MNO GSM network Recognize 112 call and treat accordingly CLI data Best effort location MSD receive (in-band modem) Map visualization Voice call receive Voice Call connect Send acknowledgement to TCU Map accuracy Certification Formal certification procedures Other Functions Bluetooth connection using in-band modem UMTS connection Value Added Capabilities Information call Notify insurance carrier Tolling Demo Capabilities In-band Demo Capabilities Future/ Potential Capabilities Future or Potential Capabilities B. Droessler Continental Automotive Systems Page 6 of 14

7 3) Minimize Overall Costs Every party involved in ecall desires low cost solutions for their specific piece of the ecall value chain. If we look at what will make a timely introduction of ecall successful, the in-vehicle costs, carrier and update costs must be as inexpensive as possible. Minimizing In-Vehicle Costs The cost of the in-vehicle solution is a key factor affecting both consumers and automotive OEMs. If a voluntary approach is to be successful, the in-vehicle solution must be low cost or else consumers and OEMs will not choose to bear the costs. Consumer data suggests that costs are a significant reason why consumers do not choose a safety system. This requires Industry and the Commission to consider further the trade-offs of embedded and Bluetooth based approaches. Many discussions have already occurred that introduce the downsides of the Bluetooth based solutions. Most notably, crash survivability, availability, coverage, and battery condition are obstacles for the Bluetooth solution. The EG.1 and EG.2 Clarification Papers outline these issues. However, these discussions have also presented possible work around including user notification of a non-operable system. Because of the lower price point that a Bluetooth solution may offer, it is conceivable that Automotive OEMs will be more likely to adopt this solution voluntarily. In addition the use of the portable device s SIM avoids the SIM and registration issues foreseen with embedded solutions. Continental Automotive Systems views both solutions as technically viable and is prepared to work with Industry and the Commission to arrive at acceptable implementations. However, it is important to note Continental Automotive Systems suggested implementations include creating a dedicated ecall module to manage either the embedded or Bluetooth based solution. This approach ensures the best possible location (supplied by a local receiver augmented with vehicle dead reckoning) and management of the ecall priority relative to other possible tasks. The position, ecall detection, and MSD formulation are managed outside of the nomadic device, such that all that is needed from the nomadic device is a voice connection. All other functions are controlled outside the nomadic device, including the in-band modem function. The implementation suggested by Continental Automotive Systems for these solutions is outlined in Figure 1. DR Ecall Embedded DR Ecall Bluetooth Portable Phone Vehicle Bus Other I/O Vehicle Bus Other I/O Embedded Block diagram Bluetooth Block Diagram Figure 1 Minimizing Carrier Costs Many MSD transport mechanisms have been considered and analyzed to date. USSD (unstructured supplementary services data) and in-band modem were the top two candidates with the in-band modem B. Droessler Continental Automotive Systems Page 7 of 14

8 recently becoming the sole option under consideration by 3GPP and ETSI. When considering what will aid a timely ecall implementation, minimizing the magnitude and costs of changes to the Mobile Network Operators (MNO) is critical. In this respect, the in-band modem technology offers a clear advantage. Because the in-band technology uses the voice channel, no updates are needed by the MNO. Going forward, UMTS will replace GSM networks. Knowing this will occur, it should be factored into the decisions being made now. Again, the in-band modem is ideally suited for this situation as the voice channel is always available despite the network changes. This is an important advantage, especially during the mobile network transition periods likely to occur during the life of the vehicle. Minimizing Costs The implementation costs at the are currently a roadblock to e112 and ecall implementation. Although some updates are needed, the cost of an in-band modem solution at the s is not projected to be substantial. The technology exists today and is currently in use in other applications. 4) Evolutionary View Continental Automotive Systems feels it is important to take an evolutionary and long term view to ecall if a timely approach is to be found. To move quickly, Continental Automotive Systems believes that Generation 1 of the ecall system should quickly and closely follow the DG INFSO recommendations to create a common, standard approach across Europe. This may involve both embedded or Bluetooth based approaches as negotiated between Automotive Manufacturers and the Commission. It will also be accelerated by use of the in-band modem technology once standardized to aid adoption and implementation by Member States and s. For those Automotive Manufacturers choosing to take a more proactive leadership position, Continental Automotive Systems suggests an additional option for initial roll-out in Figure 2. This solution would implement emergency calling using an existing call center/service provider or a direct 112 call. Additionally, the solution would build in the capability to comply with the current ecall implementations but not activate these features until a later date. For example, functions such as in-band modem, MSD creation, etc. would reside in the product and be updatable via reflash or wireless update, but the launched product would use existing telematics call centers or e112 connection until ecall was finalized. Upon final agreement on ecall implementation and readiness, the module could then be updated and/or activated to comply with ecall. - Early launch based on existing telematics service provider Vehicle Bus Telematics Services Other I/O Embedded ecall MSD formulation In-band Modem MNO services e112 Service Provider In-band modem - Build in ecall Capability - Activate/update in future Figure 2 Protect-for ecall Architecture B. Droessler Continental Automotive Systems Page 8 of 14

9 Any initial system will undoubtedly evolve due to changes in technology and use cases. Generation 1 systems will focus on ecall basics. Generation 1 and 2 systems implementations should consider making provisions for the Full Set of Data, value added service and third party service providers. Generation 3 of the system will need to be updatable, expandable, and modular. Doing so will allow additional services and functions built around ecall to enhance the business case. Care should be taken to balance timely roll-out of Generation 1 and making provisions for these extended services. Continental Automotive Systems foresees that several in-vehicle implementations will exist simultaneously and evolve over time. Potential scenarios are highlighted in Figure 3. Continental Automotive Systems can assist the Automotive Manufacturers in navigating through these options. Embedded Systems Bluetooth Systems Generation 1 Basic Functions - ecall ecall Embedded ecall Bluetooth Generation 2 Value Added - Modular Bluetooth WiFi Entertainment Value Added Services ecall Embedded Bluetooth WiFi Entertainment Value Added Services ecall Generation 3 Integration - Expandable Bluetooth WiFi Entertainment Value Added Services ecall Embedded Bluetooth WiFi Entertainment Value Added Services ecall Embedded Figure 3 - Potential ecall in-vehicle solution evolution B. Droessler Continental Automotive Systems Page 9 of 14

10 4.0 ecall Demo Overview Continental Automotive Systems worked in collaboration with Industry partners to implement an ecall demo that follows the DG INFSO recommendations. This demo system represents a potential generation 1 system to speed along ecall and in the future will explore technologies that minimize overall costs to the value chain. The overall structure of the demonstration architecture is highlighted in Figure 4. The demonstrator contains the major elements recommended by the DG INFSO implemented in a bench test environment. A system flowchart can be found in Figure 5. For ease of demonstration the crash event is simulated by triggering of a manual button. This same input could also detect an airbag signal or physical button press as needed. Upon detection the crash event, the ecall processor gathers location information, calculates current heading from historic locations and formulates the Minimum Set of Data (MSD). The system then initiates a 112 call via the embedded Net Access Device (). The Mobile Network Operator (MNO) detects and processes the 112 call. This call is then routed to the. Once a voice connection is established, the invehicle system uses the in-band modem to send the MSD to the. The uses a receiving in-band modem to extract the MSD. The MSD information is then displayed to the operator along with visualization on a map of the incident location. The then sends an automatics acknowledgement to the in-vehicle system upon successful receipt of the MSD. A voice connection is then established between the in-vehicle system and the. Vehicle Bus Ecall MSD formulation In-band Modem Embedded Bluetooth Other I/O Portable Phone MNO In-band modem Figure 4 ecall Demonstrator Overview In-Vehicle System (IVS) Mobile Network Operator Monitor for trigger event Initiate emergency call Formulate MSD Transmit MSD to MNO/ MNO detects 112 call and routes to receives and decodes MSD acks receipt and maps location Figure 5 ecall Demonstrator Flowchart In implementing the demonstrator system, the Industry partners worked collaboratively within a 4 month timeline to realize this system and associated studies described below. This demonstrator not only highlights the Industry collaboration needed to jump start ecall but also shows the ease of implementation for the value chain using existing components. This was accomplished through adhering to the DG INFSO recommendations which allowed the leverage of many existing components from each player in the value chain. B. Droessler Continental Automotive Systems Page 10 of 14

11 For example, Continental was able to use its long history in Telematics to bring together hardware and integrate software for ecall processing, location, in-band modem,, and Bluetooth technologies. Airbiquity was able to quickly port an existing in-vehicle modem implementation. In addition, Airbiquity utilized an existing land side modem to connect to the terminal. A mobile network partner was able to use their existing GSM network unchanged. Swissphone was able to leverage existing capabilities to receive the MSD and process the data to identify all transmitted data including vehicle identification number and accident position. From quantitative standpoint, the demonstrator system performed exactly as expected. It is important to note that the initial system is not yet optimized for efficiency or lowest latency. However, even without the optimizations expected for a series production product, the time delay from event trigger to detection and visualization of the map location was near the DG INFSO recommendation of 34 seconds. With optimization it is believed that this time will be reduced. In addition to evaluating the basic ecall implementation using embedded and GSM network, the demonstrator is easily expanded to accommodate other technologies. Continental will next evaluate Bluetooth based transmissions, transmissions of in-band modem over UMTS, sleeping SIM and value added services implementations to compare them to baseline scenarios. B. Droessler Continental Automotive Systems Page 11 of 14

12 5.0 Conclusion Continental Automotive Systems commends the efforts of the Commission, Industry, and Member States thus far in the progress towards implementing ecall. Although more work is required, significant progress has been made in reaching clarity on the methods and standards needed for ecall. Continental Automotive Systems stands ready to help Industry, the Commission and Member States solve the remaining issues in order to bring ecall back on track and find a timely introduction to ecall. To achieve this, Continental Automotive Systems has recommended Industry focus on 4 key areas. Collaboration between industry players o The ecall demonstrator presented in this paper is an example of the collaboration needed between Industry players to help accelerate ecall. o Continental Automotive Systems invites the Commission, Member States and other Industry partners to help enhance the ecall demonstrator project. o The next collaboration must include working with existing service providers and call centers to establish a means for these partners to continue to offer and expand the value add they bring. Follow the recommendations of the DG INFSO, ETSI and other standards bodies o To ensure a consistent pan-european implementation, the DG INFSO recommendations need to become the standard for implementation. This will help Member States, s, and Industry focus on a single method across Europe. o Using existing expertise, the demo system was constructed in a short amount of time using the DG INFSO recommendations. Minimize overall costs across the value chain o Every player in the value chain seeks lowest possible costs. o In-band modem technology represents an efficient method to minimize costs across the value chain and accommodate future changes in carrier s network technology. o Bluetooth and embedded solutions are both technically viable. Bluetooth solutions, if implemented correctly, offer potential in-vehicle hardware cost savings. o Industry needs to work to balance the costs of these solutions with the benefits and reliability. Evolutionary view - solutions that are updateable and expandable o To ensure a timely roll-out, a generation 1 ecall system may have to make some trade-offs. o Over time, multiple solutions will likely exist simultaneously that will evolve. o Continental Automotive Systems is ready support automobile manufacturers with unique solutions that allow early introduction of emergency calling while protecting for ecall implementation. With these activities, Continental Automotive Systems believes that Industry can help the Commission and Member States move forward with ecall. B. Droessler Continental Automotive Systems Page 12 of 14

13 Sources November 23, 2006, Bringing ecall back on track Action Plan (3 rd esafety Communication) from the Commission of the European Communities April 2006, Version 2.0, Recommendations of the DG ecall for the introduction of the pan- European ecall December 2006, Use of Intelligent Systems in Vehicle, Special Eurobarometer report B. Droessler Continental Automotive Systems Page 13 of 14

14 Appendix A State Flow Diagrams Driver Ecall App Airbiquity modem Airbiquity server Airbag signal or Ecall button MNO Start voice call Go into carrier detect mode Start voice call Send carrier Switch to data mode Request MSD send MSD send MSD message send MSD Switch to voice or carrier detect mode respectively Switch to voice mode process MSD Switch to carrier detect mode Voice call finished voice call end voice call Ecall app idle Modem idle mode B. Droessler Continental Automotive Systems Page 14 of 14