100 likes | 187 Vues
Explore the current status, goals, and enhancements of the DOT-CAR initiative recommended by ATX to the Connected Vehicle Trade Association (CVTA). Discover the latest connectivity enhancements and future steps discussed in sessions and workshops. Backup details on open systems harmonization and organizations contacted are also provided.
E N D
The dot-car approach Arnaud de Meulemeester ATX Europe GmbH
The dot-car approach • What is dot-car? • The current status of dot-car • Possible enhancements • Next steps
What is dot-car • Dot-car (.car) is an initiative that ATX recommended to CVTA (Connected Vehicle Trade Association). • Give the vehicle access to the World Wide Web • Define rules and guidelines for compliance to enable the internet access in the car • New business models / customer offer / customer usage
Dot-car –Current Discussion • Device Information • Driving Situation • Location • Brand Information • Driver Profile • Driver Behavior • Browser Capabilities • Bandwidth • REQUEST • Additional URL Parameters • Analysis of the data provided • Generate • response • based on • RESPONSE • Meta Data • Hidden Text • Speech Style Sheet • URL rewriting • Server Capabilities • Content Type • Compliance Class • Website based on the data provided in the request
Dot-car – connectivity enhancements driving situation I/O device Bandwidth Motor way type Traffic jam snow ice … GPRS EDGE UMTS HSDPA … WLAN Text2speech Voice command Voice recognition Dot-car browser … OEM specific interface
Dot-car – Update/Next Steps • Architectural workshop held on the 28th of October 2008 in Detroit • Attendees fromBNSF, Booz Hamilton, Delphi, Continental, Intel, Navteq, SAE, TeleAtlas, QNX, … • Current activitiesDefinition of special dot-car page attributes • Summary of dot-car page attribute proposal • Discussion of enhancements, modifications • Derive timeline for a global architecture • Discuss the results at the next connected car meeting
Backup – Open System Harmonization • At least 12 open-source initiatives in various stages of development globally • 14 organizations contacted to create a Harmonization Committee that would: • Familiarize all organizations with their initiatives objectives and domain • Create a common lexicon • Determine what boundary overlaps exist • Agree to share information as they progress (but cannot input unless you are members) • Determine a communication protocol between the groups • Work to leverage the efforts collectively • The first organizations have agreed to this effort in principle. Face-to-face meetings will follow mid-2009. • Paul Thorpe of OSS Nokalva will coordinate this effort for CVTA along with Scott McCormick, CVTA, and Tod Farrell, ATX.
Backup – Organizations Contacted Currently open: • Nomadic device forum, 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) • Agreed in principle: • TIA TR48 • ETRI • Volpe (Ritter) • JPO (Schagrin) • Genivi • SAE • ITU-T SG16 VGP ad-hoc • CVTA dot-car Initiative