Current trends in open source and automotive
3 likes•2,227 views
The document discusses current trends in open source software for automotive in-vehicle infotainment (IVI) systems. It notes that the automotive industry is moving away from traditional closed source models towards more open source and common baselines in order to reduce costs, speed up development, and allow OEMs to differentiate through user experience and apps rather than software. The document introduces Tizen IVI as an open source platform for automotive IVI that aims to accelerate innovation, lower integration costs, enable security and differentiation through customization, and provide an application ecosystem. Key features of Tizen IVI are also summarized.
![Inflection Point #2
Win back the cockpit or concede to mobile
5
• Moral/Safety imperative!
– Reaching for a moving object increases crash/near-crash
risk by 8.8x, text messaging on cell phone = 23.2x
– Lack of tactile input = more time with eyes off road
• Needs to be compelling or phones win
• Device I already have / familiar / configured
• Service(s) I already pay for
• Already has my stuff on it
• Already has my connections on it
• IVI system adds complexity, both in cost and
manageability [OPPORTUNITY: Better sharing/syncing]
• IVI Can be Superior
• Works even when the phone doesn’t
• More adaptable/flexible inputs
• More and better data access](https://image.slidesharecdn.com/currenttrendsinopensourceandautomotive-140329071158-phpapp02/85/Current-trends-in-open-source-and-automotive-5-320.jpg)
Current trends in open source and automotive
- 1. Current Trends in Open Source and Automotive Brett Branch Tizen IVI Product Marketing Intel Open Source Technology Center
- 2. Agenda • Inflection Point #1 – Automotive Open Source? • What makes a good IVI platform? • Inflection Point #2 – win back the cockpit • Tizen IVI Overview • Tizen IVI Roadmap
- 3. Inflection Point #1 Automotive Open Source? 3 Automotive industry trending away from traditional closed source to open source and common baseline • Reduce cost • Over 100 Million lines of code in typical IVI platform in 2009 and rapidly going up as we integrate with more devices and services. Line of code cost $10-$100. Not sustainable. • Speed time to market, keep up with rapid changes • Focus on differentiation - on the top end of the stack: UX and Apps • Following mobile, i.e. Samsung S. Voice, etc. • GOOGLE Risk! But gain access to app/developer ecosystem and services • Security/Liability concerns
- 4. What makes a good IVI platform? Adaptive Navigation Staying Connected* Media Vehicle Information and Diagnostics Key Usage scenarios What end users care about Intuitive IVI pla'orms need to provide a great user experience appropriate for the car Performance Experience Connectivity Key Metrics Smooth Responsive Driver Assist / Autonomous Staying connected = email, texts, auto-‐responders and updates that allow the driver to be connected in a hands-‐free, vehicle appropriate manner Security Specific Favorite Apps What OEMs care about Cost Effective Development Updateable Stays Relevant Well Supported Speeds Time to Market
- 5. Inflection Point #2 Win back the cockpit or concede to mobile 5 • Moral/Safety imperative! – Reaching for a moving object increases crash/near-crash risk by 8.8x, text messaging on cell phone = 23.2x – Lack of tactile input = more time with eyes off road • Needs to be compelling or phones win • Device I already have / familiar / configured • Service(s) I already pay for • Already has my stuff on it • Already has my connections on it • IVI system adds complexity, both in cost and manageability [OPPORTUNITY: Better sharing/syncing] • IVI Can be Superior • Works even when the phone doesn’t • More adaptable/flexible inputs • More and better data access
- 6. Deliver the safe and smart driving experience WHEREVER YOU GO Intel Automotive Solution Division’s VISION
- 7. Opportunities! 7 • Improvements in all areas of the stack – Examples BT pairing and functionality, varying profiles capabilities mandatory and optional, etc. – More accurate Nav, including Dead Reckoning, etc. • New Applications and Services – ADAS applications – Traffic/Parking Management – Remote Diagnostics, Remote Vehicle Monitoring and Control (remote start, A/C, etc), and Assisted Service Scheduling – Dynamic Customized POIs based on profile – Socialization and Gameification of driving experiences – Auto-responders and alerts – …
- 8. What is Tizen™ for IVI? Tizen™ is an open source, standards-‐based soBware pla'orm supported by leading mobile operators, device manufacturers, and silicon suppliers Tizen is a trademark of the Linux FoundaFon. *Other names and brands may be claimed as the property of others. All products, computer systems, dates, and figures specified are preliminary based on current expectaFons and are subject to change without noFce. Tizen IVI is a open pla'orm designed specifically for the automoFve market to accelerate open innovaFon, facilitate differenFaFon, benefit from mobile and consumer advances, and enable common frameworks to lower the cost of soBware integraFon, and speed Fme to market of new services 8
- 9. Tizen In-Vehicle Infotainment • Creating an open extensible automotive platform • Active in W3C effort to define Automotive Web APIs • Jaguar Land Rover*, TOYOTA* and others promote Tizen solutions • Tizen IVI is the reference distribution for the Automotive Grade Linux project
- 10. Tizen™ IVI Features and Benefits Reduce so)ware integra1on costs by u1lizing standards-‐based Tizen IVI pla;orm Build with security • Small and fast boot • GENIVI* compliant • MulF-‐screen display • Audio zoning and mixing • Vehicle service data access • Web service access • Data protecFon • STT/TTS framework • SMACK domain security Ease to differen1ate by customizing the user experience for Tizen IVI • Customizable UX - User interface (UI) - Window manager - Input method • System se[ngs • Reference IVI applicaFons Mone1ze by selling services and apps integrated into Tizen IVI Deliver applica1on ecosystem based on HTML5 standards • New Tizen SDK supports IVI • Ease of applicaFon development, naFve and HTML5 Features Benefits 10
- 11. Apr May June July Aug Sep Oct Nov Dec Jan Feb Mar Apr May June July Aug Sep Tizen IVI 3.0 Roadmap 2013 2014 IVI 3.0-M1 IVI 3.0-M2 Func1onal Features • WebApps on Wayland • Small Footprint (<200MB) • Dialer App • Media Player • Based on Tizen 3.0 • Updated core components: Systemd, ofono, Bluez, Connman & more IVI 3.0M1 Func1onal Features • BT -‐ Serial Port Profile 1.1, AVRCP, A2DP, HFP 1.6, MAP • Web APIs (Vehicle Info, DLNA, Device, Speech) • Smack based Security w/ floor domain • Apps2App Comms • DLNA • Media Player w/BT and DLNA • Dialer App w/BT, TTS, STT • WebGL, Video and CSS HW accel • HW accel of Camera/Video streams • PIM • Genivi Layer Manager • Genivi Audio Manager • DiagnosFc Log and Trace • Tizen IVI SDK IVI 3.0M2 IVI 3.0 M3 IVI 3.0 M3 Func1onal Features • Intent to meet GENIVI Compliance w/ 6.0 (newer BlueZ) • AGL incremental requirements as defined by AGL and OEM/Tier1 customers • Smack 3 domain model • MulF-‐user • Crosswalk In Planning POR Recommended Pla'orms: Nexcom VTC-‐1010 Nexcom NDIS166, VTC7120 Features Under Considera1on • Yocto Support
- 12. Latest Preview - Tizen 3.0-M2-EOY 12 Based on a 3.12.4 Linux kernel with support for Intel® Atom™ E38xx processors formerly known as 'Bay Trail' Upgraded/Enhanced Features and ApplicaFons: • Tizen SDK for IVI (alpha release) • Smack Security Framework (under development, disabled by default) • Graphics – including new versions of Mesa, Wayland/Weston, and EFL. GL AcceleraFon fully supported for Wayland with YaGL soluFon • Enhanced AutomoFve Web API and updated AutomoFve Message Broker (AMB 0.10) • CSS HW AcceleraFon • GENIVI Components including: • Wayland shell implemenFng GENIVI Layer Manager API • GENIVI Audio Manager • Node Startup Controller • DiagnosFc, Log and Trace • Sample Apps: • Homescreen, GhostCluster, MediaPlayer, saythis, Se[ngs, Dialer For more informaFon about this release, please follow the link to the release notes. hsps://wiki.Fzen.org/wiki/IVI/IVI_January_15,_3.0-‐M2-‐EOY
- 13. Tizen IVI Development 13 • Requirement Inputs: • OEMs • Automotive Consortiums, AGL, GenIVI, etc. • Tizen.org bugs and feature requests • Development Contributions • Intel • OEMs • Tier1s • Community • Get Involved!! • Participation ensures that the solutions evolve the way you need… • Productize!! • Differentiation • Closed-source IP
- 14. Summary 14 • There is a huge demand and opportunity to provide automotive appropriate value added services in the car. • There is a huge desire to do a better job of integrating our mobile experiences in the car and “take back the cockpit” • Meeting these demands will require a common framework to build an experience and application ecosystem • Tizen IVI leverages the frameworks of adjacent market segments, and adds the necessary automotive specific frameworks to enable automotive appropriate solutions • Tizen IVI is guided and shaped by community participation
- 16. A few words about Consortia… 16 • Open Automotive Alliance – Google’s play in phases… • GENIVI, AGL and Tizen