july 2014 masashige mizuyama cto of automotive
play

July 2014 Masashige Mizuyama CTO of Automotive Infotainment Business - PowerPoint PPT Presentation

July 2014 Masashige Mizuyama CTO of Automotive Infotainment Business Division, Panasonic Corp. About Myself CTO of Automotive Infotainment Business since April 2013 Architect, Director of mobile phone development ~March 2013 2005.6


  1. July 2014 Masashige Mizuyama CTO of Automotive Infotainment Business Division, Panasonic Corp.

  2. About Myself • CTO of Automotive Infotainment Business since April 2013 • Architect, Director of mobile phone development ~March 2013 2005.6 Int’l Tech. Conference CELF, Yokohama 2006.4 Embedded Linux Conference, San Jose

  3. Today’s Agenda • Current status of IVI • Lessons Learned from Mobile phone experience • Challenge for Open Source

  4. Situation is … - The new reference in end user’s mind: Smartphone - IT/Cloud Speed of evolution, Software Explosion - IVI is spreading over the Cockpit - High Reliability is a must for Safety Robust, Speedy and Stable, Efficient Reliable Development System (Conflict)

  5. IVI is Expanding Cloud Infotainment System Services Multi Media Apps (Music, Navi) HMI Platform IVI System

  6. IVI is Expanding Cloud Infotainment System Services Multi- Media Apps (Music, Navi) HMI Platform IVI System Cockpit becomes “eCockpit”

  7. Our challenge in IVI Architecture • Both Efficiency and Safety should be required. Partitioning IT World Current Function APL APL APL IVI Safety HLOS Driving Assist

  8. Options for Partitioning Function Options Cost ASIL Architecture Integrity ○ Separated × × ① MM Meter HUD Units ECU ECU ECU ○ Dedicated △ △ ② MM HUD Meter Multi-Core ECU CPU CPU CPU ○ ○ Hypervisor △ ③ MM HUD Meter ECU CPU Linux RTOS ○ ◎ ? Linux MM HUD ④ Meter ECU CPU Linux

  9. Issue still remains Even if we partition the software on the CPU, How about the other shared resources? Cloud ASIL X Services Rich Apps Safety LCD DMAC CPU Ctrl. L2$ Internal BUS Memory GPU IF SoC

  10. Exploding Growth of Applications • History of Mobile phone 600 Software code size (MB) 500 400 RTOS  Linux  Android 300 200 100 0 1990 1995 2000 2005 2010 2015 Graphic menu i-mode Phone Java Video-phone Camera EC GPS (Reference: Based on Panasonic Products )

  11. Races for Ecosystem Esteemo 2006/11 2007/1 2008/7 merged 2006/10 2005/11 Lips 2007/7 2010/2 2005/11 Maemo 2011/9

  12. History says… Global market share held by the leading smartphone operating systems in sales to end users from 1st quarter 2009 to 4th quarter 2013 90 80 70 Share of global sales to end users in % 60 50 40 30 20 10 0 Q1 '09 Q2 '09 Q3 '09 Q1 '10 Q2 '10 Q3 '10 Q4 '10 Q1 '11 Q2 '11 Q3 '11 Q4 '11 Q1 '12 Q2 '12 Q3 '12 Q4 '12 Q1 '13 Q2 '13 Q3 '13 Q4 '13 Android iOS Microsoft RIM Bada* Symbian (Reference: The Statistics Portal http://www.statista.com/statistics/266136/global-market-share-held-by-smartphone-operating-systems/ )

  13. Infotainment looks like… Infotainment System Smartphone Touch interface GPS Modem CAN Movie Music Voice FOTA Call Graphics Sound Dead Reckoning SMS Voice Recognition … … …

  14. Shifting Gear to IT Speed IVI can no longer be developed by a single company. Can Open Innovation Open Source Development be the remedy? To Use Existing Open Source Software To Grow YOUR Assets in Open Source Proj.

  15. Does Open Source Work for Automotive? Successful Open Source Projects: Their Own HW to Enjoy Improvements Source Code First Simple Objective --- Solving Single Problem Area

  16. Automotive Specific Area – Open Source? Co-development among stakeholder companies Area for Automotive Specific Competition GUI Web CODECs … Toolkit Runtime OS Kernel & Common Libs. Closed Device Drivers Mainstream Open Source Development By developer’s community

  17. Automotive Specific Area – Collaboration? Core part of unique value of your product Important pieces for whole system to work.

  18. Still, Why Open for “Joint Development” ? Closed Party, Closed Project Commitment for quality, schedule Project reliability No Free Riders Open Source Project More Chance to have various partners Many eyes & hands for Quality, Schedule Motivation!

  19. Path to the “Off-the-Shelf” Platform Specification Specification Specification System Integrator, BSP Supplier, Total Solution Vendor Product Product Product Usable In Every Stage

  20. Conclusion Now, Standard in End User’s Mind is Smartphone. Our Progress Is Too Slow in Most Cases. If IVI Ecosystem doesn’t Get Working in 3-4 Years, Smartphone, Dongle or Arbitrary Extension Unit (or Some Other Ecosystem) will do it. Speed is Critical. Let’s Implement the Source Code and Make It Work!

  21. Thank You !!

  22. Appendix: References of images in this presentation http://pixabay.com/ja/%E8%BB%8A-%E3%83%9F%E3%83%A8%E3%83%BC%E6%A9%8B- %E3%83%90%E3%83%83%E3%82%AF%E3%83%9F%E3%83%A9%E3%83%BC-172876/ http://pixabay.com/ja/%E3%83%9F%E3%83%A9%E3%83%BC-%E8%BB%8A-%E3%82%AC%E3%83%A9%E3%82%B9- %E3%83%AA%E3%82%A2%E3%83%93%E3%83%A5%E3%83%BC-%E3%83%9F%E3%83%A9%E3%83%BC- %E9%A7%86%E5%8B%95-71418/ http://pixabay.com/ja/%E3%82%B9%E3%83%94%E3%83%BC%E3%83%89-%E3%82%B9%E3%83%94%E3%83%BC%E3%83%89- %E3%82%BB%E3%83%B3%E3%82%B5%E3%83%BC-%E3%83%80%E3%83%83%E3%82%B7%E3%83%A5- %E3%83%9C%E3%83%BC%E3%83%89-%E7%B6%99%E6%89%8B- %E3%82%BF%E3%82%B3%E3%83%A1%E3%83%BC%E3%82%BF-253650/ http://news.panasonic.net/images/01ELUGAWATER.jpg http://panasonic.jp/car/navi/products/Lseries/PRD/design/index.html#01

Recommend


More recommend