The Mobile Conduit: Delivery of Advanced Automotive Services through - - PowerPoint PPT Presentation
The Mobile Conduit: Delivery of Advanced Automotive Services through the Phone Jacek Serafiski Sen Murphy Zylia, Poland UCD, Ireland sean.murphy@iname.com jacek@zylia.pl http://zylia.pl Automotive Lunix Summit, Edinburgh 24.10.2013 Zylia
Jacek Serafiński Seán Murphy Zylia, Poland UCD, Ireland jacek@zylia.pl sean.murphy@iname.com http://zylia.pl
Automotive Lunix Summit, Edinburgh 24.10.2013
R&D consulting company with strong practical focus
Prototype development our primary activity
Expertise
Embedded systems Speech recognition systems Audio processing and coding Mobile-car integration
Work on mix of public- and private-funded projects Interested in leveraging expertise in embedded
Connected Car vision, concept, issues The role of mobile in the Connected Car Mobile-car integration technologies Carmesh Implementation work
Platform-specific experiences Demo applications
Conclusions
Automotive sector sees the connected car market as a big
Automotive applications market should reach US$ 1.2bn by
GSMA forecasts that:
More than 20% of vehicles sold worldwide in 2015 to include
More than 50% of vehicles sold worldwide in 2015 to be
Every new car to be connected in multiple ways by 2025.
Two main aspects to the Connected Car:
Integration with existing services (social networks,
Tailored automotive experience
Right data, right time Advanced Uis – mix of speech, in car controls, etc.
New data making new services possible
Driving behaviour analysis Eco-driving UBI – Usage-based Insurance Dashboard apps (Torque, Waze)
But it’s much more messy of course…
The expected lifetime of a car is 10 years thus the
Diversity in capabilities of different cars
There are problems to keep the car connected while
Privacy issues regarding usage of vehicular data Driver distraction issues for new services need to be
Application developers don’t know how to design for the
New user interfaces Present the right data at the right time
Power of mobile increasing at phenomenal rate
Increasing wireless interfaces’ capacity
OBU will not be able to compete with the mobile in terms of power,
connectivity or release cycles
Mobile already knows much about you
Home, work, apps, locations, etc.
Why not leverage Internet on the mobile?
Heterogeneous mobile world makes neat integration hard
Security issues - some car data and functionality needs to
Safety regulations, strict QA processes Auto manufacturers want to monetize automotive
want to have some control over the ecosystem
Natural solution leverages strength of different systems
OBU provides better integration with Car and driving
Mobile provides compute power and network connectivity
As in every marriage there are some tensions…
Some obvious touchpoints
Speech Navigation Control of the application store/service delivery
Need holistic view in which functionality split is clear
System design should allow some flexibility Standard communication protocols for orchestration
Car manufacturers will not be tied to single mobile
Solutions are not yet mature…
There are different approaches towards mobile-car
Basic integration – contacts, call support, no data connection Single in-house mobile app (e.g. Mercedes, Lexus) Mirroring solutions (e.g. MirrorLink, iOS 7) Application level solutions (Ford Applink, OnStar,
Applications run on the phone and connect wirelessly
Multiple applications connected to the car can run
Car provides UI components for mobile app
Mobile app is able to control the output components
Callbacks trigger mobile applications on input from car
Applications can access car data Open SDK for application developers for different
Started looking at it early this year Was the most open phone-car interaction solution
Ford are championing it and doing quite good
Although Mirrorlink has more industry support, developer
We like the vision of brains in phone and car
very compatible with SDL
Working with new platforms is challenging…
Experiences with SDL Experiences with Tizen IVI
We are working on three demonstration
Google Calendar integration Facebook integration OBDII data collection via RPi
Phone-car interaction protocol
Evolution of Ford’s Applink
Enables individual mobile applications to interact with car Being pushed (somewhat) within GENIVI consortium On Tizen IVI v3.0 roadmap SDL ‘richer’ view of mobile-car interaction than mirroring
iOS, MirrorLink
There is a quite well defined protocol right now
although it is somewhat missing an architecture
(iOS, Android)
SDL Javascript Library Web Sockets
WiFi or Bluetooth
iOS/Android libs to be included in SDL
understands SDL
Proxy running as OS process C++ implementation maintains communications with
phone and sends to browser
quite robust Browser based component Websockets interface to proxy Javascript library for
registering for notifications, message composition etc
mostly designed around
callbacks
cmake build process Did not compile out of the box on either Tizen or
Had some issues around Bluetooth and websockets SHA
Build generates binary which runs proxy and
chromium by default
HMI offers main automotive UI and emulates
System comprises of library and application Straightforward to build and deploy for Android Small issue with default settings for WiFi mode being
No discovery mechanism for WiFi
Control over in car display is very limited
Logic required on OBU side to know how to render
No real graphics support
Little navi integration
not possible to send POI to in car navi some TurnByTurn updates available, though
Features supported by protocol not yet implemented
vehicle data, application types/templates, file transfer
Application development and deployment process
We are using Tizen SDK 2.2 to build Web Application
HTML5-based UI components
Downloading Tizen IVI snapshot image from the
New revisions uploaded on monthly basis
Sign the application and upload to running Tizen IVI
Install and run applications
wrt-installer –i your_app.wgt wrt-launcher –l (to get the ID of the installed application) wrt-client –l your_app_ID
Android 4.3 SmartDeviceLink (from 24.04.2013 -
Tizen IVI 3.0-M2-Jul VMWare Player 5.0.2 build-1031769 WiFi for phone-car communication
Manual configuration
Basic application to provide GCal integration in car Can see next upcoming appointments and navigate
assuming location data in GCal event
Use in car controls to control application
(callbacks on button press, update UI)
SDL
Fetch locations from Facebook account
Show these locations relevant to current position Provide locations of friend’s check-ins, places tagge in,
FB-based user management (including authentication)
Architecture similar to the previous application Technologies used
Android Embedded browser REST API Facebook Graph API
Connection to ODBII interface
Mobile application connects to the RPi and stores the
OBDII to USB serial interface PyOBD library Raspberry Pi powered by car RPi as an access point
Connected Car will change how we use a car
Routing, eco-driving, looking for gas station, etc.
Mobile is the key part of the Connected Car
Mobile becomes context-aware
There is no single view of relationship between car
Development tools and platforms are still basic
Little understanding of how to develop for automotive
GENIVI is developing good technologies to make
Leveraging open in-car systems such as SDL Tizen IVI prototypes and applications Back-end for vehicular cloud-based services Vehicle-specific speech recognition systems Novel vehicular applications Over-the-air vehicle software updates In-vehicle (surround) audio coding Looking at EU-funded collaborations in the area
jacek@zylia.pl