1. The Fully Networked Car Geneva, 4-5 March 2009 1 The dot-car approach Arnaud de Meulemeester ATX Europe GmbH

2. The Fully Networked Car Geneva, 4-5 March 2009 2 The dot-car approach 1. What is dot-car? 2. The current status of dot-car 3. Possible enhancements 4. Next steps

3. The Fully Networked Car Geneva, 4-5 March 2009 3 What is dot-car o Dot-car (.car) is an initiative that ATX recommended to CVTA (Connected Vehicle Trade Association). o Give the vehicle access to the World Wide Web o Define rules and guidelines for compliance to enable the internet access in the car o New business models / customer offer / customer usage

4. The Fully Networked Car Geneva, 4-5 March 2009 4 What are dot-car goals? Dot-car initiative: Key factors for the OEM Time-to-market o Short time to market o Easy integration into the vehicle o Short development / deployment cycles o Default services for fast delivery Cost savings o Reduce maintenance costs o Standardization to achieve economy of scale o Reusability of existing components Driver o Easy to use o Ability to personalize o Meets expectations by enabling easy access to content Brand Customization o Customized access according to vehicle model, country and motorist o Compliance with OEM, Brand standards o Flexibility to cover new requirements o Factors in ergonomics

5. The Fully Networked Car Geneva, 4-5 March 2009 5 What are dot-car goals? Dot-car initiative: Key factors for the OEM Technology o Communication (roaming, IP based, services bandwidth dependent) o Standard Web technologies with enhancements o Customized for in-vehicle environment Safety o Promotes safer, hands-free, in-vehicle environment (simple human- machine interface) o Creates certification process to comply with definitions, guidelines for safe usage o Minimizes driver distraction Car-life cycle o Adapts embedded user interface to the lifecycle of the car Business model o Enables flexible customer offers and business models via services that can be loaded (and paid) on request applets, widgets, gadgets and plug-ins o Attracts high number of users o Attracts interested suppliers

6. The Fully Networked Car Geneva, 4-5 March 2009 6 Dot-car –Current Discussion Server Capabilities Content Type Compliance Class REQUEST Additional URL Parameters RESPONSE Meta Data Hidden Text Speech Style Sheet URL rewriting Device Information Driving Situation Location Brand Information Driver Profile Driver Behavior Browser Capabilities Bandwidth Analysis of the data provided Website based on the data provided in the request Generate response based on

7. The Fully Networked Car Geneva, 4-5 March 2009 7 Dot-car – connectivity enhancements GPRS EDGE UMTS HSDPA … WLAN Text2speech Voice command Voice recognition Dot-car browser … OEM specific interface Bandwidth I/O device driving situation Motor way type Traffic jam snow ice …

8. The Fully Networked Car Geneva, 4-5 March 2009 8 Dot-car – Update/Next Steps o Architectural workshop held on the 28th of October 2008 in Detroit o Attendees from BNSF, Booz Hamilton, Delphi, Continental, Intel, Navteq, SAE, TeleAtlas, QNX, … o Current activities Definition of special dot- car page attributes o Summary of dot-car page attribute proposal o Discussion of enhancements, modifications o Derive timeline for a global architecture o Discuss the results at the next connected car meeting

9. The Fully Networked Car Geneva, 4-5 March 2009 Backup – Open System Harmonization o At least 12 open-source initiatives in various stages of development globally o 14 organizations contacted to create a Harmonization Committee that would: 1.Familiarize all organizations with their initiatives objectives and domain 2.Create a common lexicon 3.Determine what boundary overlaps exist 4.Agree to share information as they progress (but cannot input unless you are members) 5.Determine a communication protocol between the groups 6.Work to leverage the efforts collectively o The first organizations have agreed to this effort in principle. Face-to-face meetings will follow mid-2009. o Paul Thorpe of OSS Nokalva will coordinate this effort for CVTA along with Scott McCormick, CVTA, and Tod Farrell, ATX.

10. The Fully Networked Car Geneva, 4-5 March 2009 Backup – Organizations Contacted Currently open: Nomadic device forum, http://www.aide- eu.org/for_nomadic.php http://www.aide- eu.org/for_nomadic.php ISO TC204 WG17 Nomadic Devices ISO TC204 WG16 CALM IETF Automotive Industry Requirements for NEMO Route Optimization ISO TC22 SC3 WG1 MVCI (Modular Vehicle Communication Interface, ISO 22900 JSR298, Telematics API (Java), (http://jcp.org/en/jsr/detail?id=298) AUTOSAR, PDU Router/Signal Gateway for CAN, LIN, Flexray Interfaces (http://www.autosar.org)http://www.autosar.org Agreed in principle: TIA TR48 ETRI Volpe (Ritter) JPO (Schagrin) Genivi SAE ITU-T SG16 VGP ad-hoc CVTA dot-car Initiative