The dot-car approach

Document Sample
The dot-car approach Powered By Docstoc
					                          The dot-car approach   1




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




1. What is dot-car?
2. The current status of dot-car
3. Possible enhancements
4. Next steps



 The Fully Networked Car
 Geneva, 4-5 March 2009
                            What is dot-car                        3




                          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
The Fully Networked Car
Geneva, 4-5 March 2009
                             What are dot-car goals?                                                4




             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




   The Fully Networked Car
   Geneva, 4-5 March 2009
                          What are dot-car goals?                                                      5




          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




The Fully Networked Car
Geneva, 4-5 March 2009
                   Dot-car –Current Discussion                        6




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




      I/O device             driving situation   Bandwidth




    Text2speech              Motor way type       GPRS
   Voice command              Traffic jam         EDGE
  Voice recognition              snow             UMTS
  Dot-car browser                 ice             HSDPA
         …                         …                …
OEM specific interface                            WLAN



   The Fully Networked Car
   Geneva, 4-5 March 2009
                       Dot-car – Update/Next Steps             8




o Architectural workshop           o Summary of dot-car page
  held on the 28th of          attribute proposal
  October 2008 in Detroit o Discussion of
o Attendees from               enhancements,
  BNSF, Booz Hamilton,         modifications
  Delphi, Continental,
  Intel, Navteq, SAE,        o Derive timeline for a
  TeleAtlas, QNX, …            global architecture
o Current activities         o Discuss the results at the
  Definition of special dot-   next connected car
  car page attributes          meeting

   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.




    The Fully Networked Car
    Geneva, 4-5 March 2009
           Backup – Organizations Contacted


Agreed in principle:                  Currently open:

 •   TIA TR48                  • Nomadic device forum,
 •   ETRI                        http://www.aide-
                                 eu.org/for_nomadic.php
 •   Volpe (Ritter)            • ISO TC204 WG17 Nomadic Devices
 •   JPO (Schagrin)            • ISO TC204 WG16 CALM
 •   Genivi                    • IETF Automotive Industry
 •   SAE                         Requirements for NEMO Route
 •   ITU-T SG16 VGP ad-hoc       Optimization
 •   CVTA dot-car Initiative   • 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)




The Fully Networked Car
Geneva, 4-5 March 2009