Android for next IVI system

Transcription

1 Android for next IVI system

2 Agenda Wind River Introduction Market information Android IVI specifics Wind River best practice examples in automotive Wind River Automotive strategy overview beyond Andriod 2

3 WIND RIVER INTRODUCTION 3

4 Heritage Leadership 1981: Founded 1993: IPO 2009: Acquired 30+% Commercial Market Share Broadest Portfolio Scale 1,900 Employees 42,000 Developers Investment $100m Annual R&D Spend Rich History of M&A Commitment 95% Customer Satisfaction 20% Net Promoter Score 4

5 Industrial Aerospace and Defense Automotive Network Equipment Digital Living Mobile

6 Our Customers, Our Industries Aerospace and Defense Automotive Industrial and Medical Mobile and Consumer Network Equipment BAE Systems Boeing EADS GE Aviation General Dynamics Finmeccanica Harris Honeywell ITT L3 Communications Lockheed Martin MHI NASA NEC Northrop Grumman Raytheon Rockwell Collins Thales U.S. Navy Actia BMW Bosch/Blaupunkt Continental Clarion Daimler Delphi Fiat/Chrysler General Motors Harman Honda Hyundai Johnson Controls LGE Magneti Marelli Mitsubishi Mobis Nissan Pateo Volvo ABB Alstrom Transport Bombardier Transportation Bosch Rexroth Boston Scientific Carl Zeiss Draeger Medical Gambro Hitachi Medical Kuka Philips Medical Medtronic National Instruments Roche Schneider Electric Siemens Transportation St. Jude Medical TomoTherapy Varian Medical Systems Vestas Wind Systems Apple Datung Epson Ericsson Hewlett-Packard Iwatsu LG Electronics Motorola Philips Ricoh Samsung Sanyo Sony Thomson Toshiba Verizon 3Com Alcatel-Lucent Avaya EMC Ericsson Flextronics Hewlett-Packard Huawei Juniper LG Electronics Mitel Motorola NEC Nokia-Siemens Cisco Nortel Oki Tellabs UT Starcom ZTE

7 7

8 MARKET INFORMATION 8

9 In Vehicle Evolution Distraction Functionality Connectivity Safety Branding Customer Loyalty 9

10 The Future its more than just in the car! Source: Center for Automotive Research and Connected Vehicle Trade Association

11 Evolving Requirements Connectivity as Managed Network Node Telematic Services CE Devices Cloud Connectivity Safety & Security Connection security Application safety Policy management Optimization Cost Space, Wight, Power Hardware consolidation

12 Android & Linux in embedded Android gaining traction in embedded CAGR of 14,9% through 2013 for the Automotive segment Short-term impact on the Automotive market VDC Research, Android & Linux in the Embedded Systems Market, May

13 Market Trends Wide adoption of connected head units unit sales of connected navigation head units will make up for 80% of the total market in Western Europe by 2018 Open source is continuing to gain traction Choice is between GENIVI and Android Increased complexity and level of integration of OE head units Browser technology driving app development Mobile applications are illustration of network-connected cars Cloud connectivity gains more traction 13

14 Auto Challenges: Increase in Software Complexity Provide a comprehensive user experience Provide integration with user electronics Adapt to all new communication technologies Cope with the rising demand for services Which is the best way to meet these challenges? 14

15 ANDROID IVI SPECIFICS 15

16 Wind River and Android 5 years Wind River GPO directly with Google Contributed 100+ programs Contributed the enablement of several hundred Android SKUs 8 Android design centers worldwide Beijing, Seoul, Stockholm, Galati, Grenoble, San Diego, Beaverton, Kanata Customers span entire value chain Silicon, device manufacturers, operators, software vendor and integrators More than 300 attendees joined Wind River s 2011 Mobile Developer Conference in Korea Held inaugural China Mobile Summit in Partnered with IMC and Leadcore 16

17 Typical IVI Requirements No. Item Description R.01 Fastboot Early Camera: 2 Sec. Initial Screen: 8 Sec. Full Navigation + Voice Recognition: 20 Sec. R.02 3D Navigation 10 ~ 30 frames per second R.03 Multimedia HD (720p & 1280p) Video XSM / HD Radio R.04 Connectivity ipod & Android MirrorLink, DLNA, Miracast R.05 Telematics 3G / 4G LTE, Remote Management, Cloud Connectivity R.06 Internet Web Browser, Social Networking R.07 Car Network CAN / Ethernet AVB / WiFi Direct R.08 SW Framework HTML5 Web Runtime, App Store Firmware Management, Security Enhancement R.09 SW Architecture Scalability (High, Med, Low end device) Reusability (Different models, different OEMs, different CPU, etc) 17

18 Name Role Work Scope Semi. Vendor Wind River ISV BSP for App Processor Multimedia Graphics Requirement Analysis Software Architecture Design BSP/Middleware Enablement Applications Telematics ADAS Voice Recognition Navigation Reference Hardware Linux BSP OpenGL/OpenVG Media Codec Kernel Drivers create/modify/integrate IVI Framework create/modify Application create Software Integration ipod, Fast Boot, Test Automation, Firmware Management, Security Enhancement Telematics, ADAS, VR, Navigation IHV Device Drivers Device Drivers in Binary and/or Source Tier-1 OEM Systems Integration Device Manufacturing Car OEM Commercial Hardware Systems Integration Design / Product Validation System Specification Quality Assurance 18

19 Wind River offering for Andriod IVI IVI Software Architecture Design Fastboot Optimization Wind River ipod Solution Priority & Performance Optimization Multi-Window & Multi-Display Firmware Management (Software Update) 19

20 IVI SW Architecture Design 20

21 Android Fastboot Options Manual Optimization Fastboot Suspend to RAM Suspend to Flash WR Hyperboot Factory Snapshot Field Snapshot 21

22 Wind River Hyperboot Solution Hyperboot saves significant time during the Android device boot cycle. It offers four ways to reduce the boot time: Cold boot optimization: Optimizes the device start up after the power is turned on; power cycling clears memory and many internal settings Hibernation (warm boot): Reduces the time for a device to boot from zero power, where a previous system state is loaded and the system resumes from it Optimized driver I/O performance: Improves the boot speed by combining asynchronous I/O with compression for smaller image size and maximum throughput Android Package Manager optimization: Reduces the standard application scan to optimize the loading time * Performance gained from Hibernation feature, 22 vs. 5.5 sec, tested with i.mx6 on Jan

23 WR ipod Architecture Overview (1/3) ipod Media Player Application ipod Da Media P (Clien 23 Serial device iap USB stack USB or Serial Bluetooth stack ipod Daemon Synchronous 2/ Asynchronous Media Player (Client) Sync/Async Client APIs over Socket Built-in iap * (process) Handler ipod Daemon 2 (Server) Serial or I2C or TCP libwrsipod (client dynamic lib) WR ipod Daemon Provides ipod Service business logic Manage interactions with Apple devices and Auth. Chip 14 Client APIs Provides Client APIs to access ipod Daemon Socket based communication 2011 Wind River. All Rights Reserved. iap USB or Serial Static link Sync/Async Client WR iap Handler (static lib) ipod Da (Ser Provides Serial lingoes or I2C or implementation iap Handler on uc OrAuthentication Chip CP Hypervisor Partition Or (Optional) Serial / I2C PCM data Alsa device * Built-in iap Handler is default

24 WR ipod Overview (2/3) WR ipod Solution Supports Serial, USB and Bluetooth link with Apple device Provides a standalone solution Not assuming any Multimedia Framework PCM streaming over Alsa device Client library can be used by any kind of client (command line, Qt, ) Can be integrated in any standard Linux distribution Optimal design with 300KB or less size of the solution Provides both synchronous and asynchronous APIs While asynchronous APIs are recommended, synchronous APIs could be used for a rapid POC development Can be extended by WR to support new lingoes Thread-safe client library Is pre-certified through ATS pre-certification 24

25 WR ipod Architecture Overview (3/3) Dependencies libevent libusb Licenses ipod daemon is Wind River proprietary iap handler is Wind River proprietary libevent is covered by a 3-clause BSD License libusb is covered by LPGP

26 Priority & Performance Management Timings & Performances Requirement Example Rear View Camera (2sec) MMI OFF to ON (Welcome screen) (8sec) Transition between different HMI states (100msec) CAN initialization after CAN WakeUp (300ms) USB link with TCU initialization after CAN WakeUp (4sec) USB communication with CD Drive after CAN WakeUp (4sec) Maximum delay between the reception of a user command through CAN-M and user feedback (visual or auditive) of the action (100ms) Maximum delay between the reception of a CAN command (e.g. ADAS command) and execution of the action (100ms) 26

27 Multi-Windows / Multi-Display 27

28 Firmware Management Solution Firmware Management extends the AOSP solution to provide a semi-automated or fully automated update mechanism tailored to a particular Android implementation or device Security that allows only authorized and signed update packages to access the device Several different update methods are available: Typical developer methods: Manual key presses, Android Debug Bridge (ADB), and Secure Digital (SD) cards or ISB thumbsticks Typical end-user manual methods: System Updates in the Settings menu, pointing the browser at the desired build Typical operator fully or semi-automated methods: Firmware-over-the-air (FOTA), with or without user confirmation 28

29 BEST PRACTICE EXAMPLES 29

30 Android in IVI for Malaysia Device Name Android based IVI Project Period 2010 ~ Device Type CPU Android Froyo & GingerBread based IVI System Freescale i.mx Series Development details Complete Software development and integration (including Software for Factory and Service Centers diagnostics) Porting Android onto customer s hardware Android adaptation for In Car integration (Android customization (with large button, redefined positions, ), multi-sources support in Media and Video players (SD, USB, Bluetooth, Aux, ipod/iphone), FM Radio Application, specific Bluetooth management for user contacts, specific Audio manager, Made For ipod/iphone, specific Power manager, ) Productization Wind River. All Rights Reserved.

31 Android in IVI for Major Car Maker Device Name Android based IVI System Project Period 2011 ~ Device Type CPU Android based IVI System FREESCALE i.mx Series High Level Design Software Integration Development details Android Framework Customization for IVI system (Bluetooth, HMI Widget, Audio Flinger, etc.) Kernel/BSP Customization for IVI system Automotive Specific Middleware Implementation (MICOM Interface, Mode Manager, Radio, DMB, CDP, etc.) Kernel/Middleware test-automation by using Wind River FAST Wind River. All Rights Reserved.

32 Automotive with GENIVI with Device Name Magneti Marelli Lupinus platform Project Period 2010 ~ Device Type CPU GENIVI based IVI system ARM Cortex-A9 CPU Development details Wind River. All Rights Reserved.

33 Wind River in Automotive with VxWorks Car Infotainment Market Wind River. All Rights Reserved.

34 Pictures of Mobile Devices Wind River. All Rights Reserved.

35 WIND RIVER AUTOMOTIVE STRATEGY 35

36 Automotive in Wind River Active in automotive market since mid 90s Automotive vertical market structure since 2007 Genivi founding member Dedicated automotive resources Worldwide support structure Compiler, Test, Development Tool and Platform business RTOS and open source sw solutions for consumer and B2B products Professional Services certified CMMI 3

37 Wind River Automotive Open Source Strategy Open Source Alignment Software Integration Wind River Automotive Products Generic Wind River Products Wind River. All Rights Reserved.

38 Wind River Auto Strategic Focus Areas SW Integration System Infrastructure Multi Media Connectivity Wind River. All Rights Reserved.

39 Platform for Infotainment (PFI)

40 GENIVI Alignment

41 Wind River PFI 4.0 & 5.0 EA PFI 4.0 GenIVI 2.0 compliant PFI 5.0 GenIVI 3.0 compliant Yocto based distribution Aligned with Wind River Linux Comes with Wind River Linux Tool support

42 The Yocto Project A common build system and collaboratively developed technologies representing the best tools and methods for building a Linux-based system Improved cross-platform compatibility and component interoperability Increased portability of software and middleware and decreased costs of their extensibility and maintenance Increased reuse and collaboration between commercial and open source communities 42

43 WR Commitment to the Yocto Project Founding member of the Yocto Project Gold member of the Yocto Project Advisory Board Active contributor to the Yocto Project Holds four out of eight maintainer and technical lead positions Dedicated four employees investing almost 100 months for the past two years Contributed over 1550 total code commits more than 26,806 lines of code and counting 43

44 Adopting the Yocto Project Wind River Linux is based on the Yocto Project open source development infrastructure Wind River Linux has achieved Yocto Project Compatible registration Wind River Linux will work with any Yocto Project Compatible BSP, software, or middleware 44

45 Wind River Automotive Portfolio SW Platforms Automotive-driven roadmap GENIVI compliant WR Linux kernel user space Android IVI CE industry alignment Ready for connected services Link to AUTOSAR Support of multiple si partners Automotive Solutions Development Platforms Automotive IP Customization Services Software Integration Automotive Services SW Project Management Hardware Enablement Optimization Support & Maintenance Technologies and ISVs Wind River Apps (Apple integration, USB, etc.) Wind River ISVs: Wind River Tools FAST Workbench w/ Qt plug-in Dedicated for various product segments CMMI level 3 certified Customer satisfaction Simics Hypervisor support 45

46 Let us help you solve your challenges! Check out the demo stations in the lobby to see many of these live products today Take a copy of the printed materials for more details Contact Wind River Account Manager with any questions Account Manager, WIND RIVER Shenzhen BRANCH Feng Weijiang( 冯伟江 ) Office: x 205 Weijiang.feng@windriver.com More info available on our China website: 46

47