Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Юрий Швалик «Apple and Google are converting car into smartphone?»


Published on

LTS LoGeek Night Odessa

Published in: Software
  • Be the first to comment

  • Be the first to like this

Юрий Швалик «Apple and Google are converting car into smartphone?»

  1. 1. Apple and Google are converting car into smartphone?
  2. 2. Big announcements  Recently something important happened in the world of Automotive electronics  Google and Apple announced support of car Head Units into their operating systems  What does it mean for the Automotive industry - evolution or revolution?
  3. 3. How it works  Head Unit recognizes connected smartphone as soon as it’s plugged with USB cable  Phone locks it’s screen – user can’t operate his phone while connected to Head Unit  Access to certain applications is provided on the screen of Head Unit
  4. 4. Evolution of Head Units and mobile devices 1920s 1980s 1990s 2000s 2010s 2014s
  5. 5. Monolithic system VS applications Head Unit / Dashboard • Long development cycles • Proprietary tools & platforms • Software distribution is difficult • Reliability requirements are very high • Mid/Entry level cars? • Expensive Smart Devices • Vibrant development community • Proven distribution infrastructure • Lot’s of media content • Connectivity • Affordable • Short life-cycle
  6. 6. Why Google and Apple need it?  New “device” for applications  Application store has proven itself as very successful concept  Apple’s App Store has 1 Million apps  Google Play has 1.3 Million apps
  7. 7. Why automotive is nervous about it Closed system System open to mobile device
  8. 8. Apps Connectivity Technologies Miracast™
  9. 9. SDLP technology Middleware Open Source SDK  We’re providing an SDK to connect Head Unit and applications via SDLP  Just add Profile lib to you code and use it’s API  SDLP will make all the rest connectivity for you SDK Open Source Middleware  SDLP is not the App itself  Applications on mobile device and Head Unit are using SDLP to connect with each other  SDLP is located below in the system architecture  SDLP is Open Source  You can download Core Stack and SDK from Github repository  SDK for Android and Linux are available  Support of iOS, QNX and other systems is on the way SDLP
  10. 10. AllView demo stand  Set of growing use-cases that offer real value in the car  Designed for safety and differentiation by AUTOMOTIVE experts  Will work with Digital Dashboards, Head Units from entry-level to high-end
  11. 11. AllView demo applications - diagnostics Description  When planning the trip, driver wants to know how much oil the engine still has. One way to know it is to use dipstick. But much more advanced way is to run diagnostics application on a phone which will connect with HU and display this information in easy and understandable form  This is only one of the features that SDLP diagnostics application supports Usage  Mobile device can show the same information as HU does or even more detailed data which doesn’t make sense to present on display of HU  Support of OBDII and CAN connection from HU  Fuel level, Engine coolant level, Oil level, Tire pressure, wiper fluid…  Can be used by regular user or by service stations
  12. 12. AllView demo applications – driver workload Description  Workload management application changes amount of information which is available for the driver depending on the current road situation  Unlike other driver distraction algorithms – SDLP workload management utilize support of the passenger who’s very often together with driver  Depending on the workload level, some information is moved from HU to mobile device in hands of the passenger Usage  Passenger can assist in:  Navigating through the city when driver is to busy to look at navigation screen  Picking up calls  Finding POI and gas stations  Finding service station to assist with car repair
  13. 13. Example of GAL/CarPlay based solution  Smartphone application have 2 ways to interact with Head Unit  Screen sharing via GAL/CarPlay  Sending control signals through SDLP  First of all application have to pass certification to authorize itself as trusted source of data  Screen transfer initiation is done via control protocol  SDLP is also used to connect application with vehicle CAN data
  14. 14. Driver distraction
  15. 15. Security limitations
  16. 16. Security limitations Phone  Almost no limitations Car  Driver distraction  Show only what is important for the user at this moment  Disable animations when car is moving  Use special fonts  Only limited amount of text and graphics can be shows on screen at any moment  MISRA  CAN bus security  ISO standards  …
  17. 17. User response on bugs VS ~800$ ~150 000$
  18. 18. Niche market  For now Google and Apple don’t consider Automotive as their priority market  A lot of security limitations  Too few volumes, too high difficulty  GAL and CarPlay is not yet open for 3rd party developers  But! Nobody knows what’s coming next   Google have announced automotive alliance with big OEMs “to bringing the Android platform to cars”
  19. 19. Thank you! Yuriy Shvalik Program manager