Software Development for Next generation Infotainment and Telematics systems

1. Software Development for Next generation Infotainment and Telematics systems Renukaprasad Sharma – Wipro Technologies

2. Next generation Infotainment and Telematics Systems • New requirements and technologies for HMI development • Model based HMI development • Seamless integration with browsers with support for A/V streaming, Internet Radio, numerous browser plug-ins • Mobile Phone HMI Integration • Ubiquitous Connectivity • Connectivity to portable CE and storage devices, Mobile handsets, Internet, other Vehicles and Roadside Infrastructure Key trends in Next generation Systems • Adoption of Open Platforms for In-Vehicle Infotainment Systems • Primarily, adoption of Linux as the mainstream OS in IVI systems • Adoption of Open source components • Mobile Phone centric Telematics • New Telematics use cases that enable remote control / monitor of Vehicle using mobile phones

3. Challenges in meeting requirements of Next generation Systems Ubiquitous Connectivity Lifecycle mismatch between an In-vehicle Infotainment System and portable CE devices brought into the vehicle Though based on Bluetooth standards, phones from different OEMs behave very differently in many situations leading to interoperability issues Even though USB and Bluetooth are becoming de-facto standards, advent of new classes in USB and profiles in Bluetooth creates a situation where the in-vehicle system has to cope up with changing standards Adoption of Web technologies, which are primarily designed for Enterprise systems, into the embedded environment of the vehicle infotainment system and meet its stringent reliability, robustness and response time needs    Securing the In-vehicle platform from malicious attacks from external world that results from opening up the In-vehicle system to the external world

4. Challenges in meeting requirements of Next generation Systems New paradigm for HMI development • COTS tools for model based HMI development • While Model based HMI development is supposed to ease HMI development and HMI change processes, they bring in their own set of challenges • Runtime Engines - to provide cross platform interoperability are loosely coupled with native platform – so, performance not always optimum • Lack of interoperability in data formats of COTS tools – reuse is ruled out • Code generated by these tools are complex and so, debugging is not easy • Mobile Phone HMI integration • Challenge is to develop a technology that can • Interoperate across multiple phone models and multiple Infotainment systems • Render Phone Output (Audio, Video and Graphics) on to Infotainment Display without distortion and driver distraction • Browser integration • Create Browsers matching with the look-and-feel of rest of the HMI • Create special browser widgets that can securely interact with native code • Numerous plug-ins and technologies to create Rich Internet Apps – problem is which one to choose

5. Challenges in meeting requirements of Next generation Systems Mobile Phone Centric Telematics Using the Mobile Phone for • Remote Lock / Unlock of vehicle doors • Remote control the HVAC • Locate vehicle in a crowded parking lot by activating horn / audio beep • Check Fuel / Battery level and Tire pressure before a trip • Track vehicle • Receive alerts on Vehicle Intrusion • Remote Immobilizer activation Challenges • Needs Mobile Application (Client) and In-vehicle (Server) software development that can interoperate with multiple Vehicles and Phones • Poses a new security challenge as Mobile phones would have the access to the vehicle bus and critical parameters of the vehicle

6. Challenges in meeting requirements of Next generation Systems Adoption of Open Source Technologies Linux as the mainstream OS • Challenge is to meet the boot and start –up time requirements of 2 ~ 3 secs • Receiving CAN wake up message within 60 ms and respond to this message within 150 ms Open source middleware components • Can significantly speed up development, but, • Requires additional and careful design to prevent IP contamination (Mix of GPL,LGPL with Non-GPL proprietary software ) • Gets upgraded frequently by non-automotive open source communities and so requires extensive in-vehicle validation before a new release can be adopted • Business Models for Software providers and integrators not clear • Maintenance and ownership of Open source components to support long vehicle cycles not clear GENIVI Alliance is trying to address these issues • Wipro, as a Core Member of the alliance, is working actively with other alliance members to make Open IVI platform a success

7. Challenges in meeting requirements of Next generation Systems • Infotainment Systems for Emerging markets (India, China..) • Our study has revealed that retro-fitting products of European / US Market is not a long term, cost effective, scalable solution for the Indian market • Innovative product design and development is required to reduce cost as well as provide features / contents relevant to Indian consumers • Challenge is to build software that is highly configurable and scalable • Can scale from low end systems (No display but Voice prompts) to high end systems (TFT LCD display with full-fledged Speech Recognition and TTS) • Can have configurable Multiple Language support (Indian English, Hindi, regional languages) • Support varying levels of Integration depending on Mobile Phone capability of the user • Only Hands Free calling (using Bluetooth as well as wired solutions) , Hands Free calling with Music streaming, complete HMI integration with phone, etc

8. Overcoming Connectivity Challenges using Wipro’s Connectivity Framework

9. Connectivity Framework – Goals & Features Audio streaming BT phones, PMPs, external storage devices (USB MSD) V2V and V2I connectivity Features Camera connectivity Hands Free Telephony Traffic Information / incident updates Internet search Mobile Device Connectivity for Remote Access of Vehicle SMS / E-Mail download and readout, SMS / E-Mail create/send • Goals • Extend in-vehicle Infotainment platform by providing connectivity to external world in a secure manner • Ensure that this connectivity is future-proof through adoption of reusable components and scalable software framework pattern Multimedia content on demand

10. Connectivity Framework – Key features • Integrated and comprehensive connectivity solution • Not only connectivity for entertainment but also for Information and driving • Scalable, Configurable and OS independent architecture • Scalability achieved through loose coupling and componentization • Options for compile & run time switches to turn on / off any particular core service – telephony, media, navigation or a part of it, e.g., Embedded Phone support can be enabled/disabled by enabling / disabling the corresponding DP • SW upgrade over USB to support new device categories • Enables the solution to be re-targeted for smaller OSes – Threadx, VxWorks, Nucleus, etc • Same software code base can be reused for multiple product lines just by switching On / Off a particular device support or a feature resulting into cost optimization and enhanced reliability • Future proof • With device categorization, architecture focuses on core functionality of the connected device as perceived by the end user and abstracts the physical media of connectivity and device specific behaviour of the connected device • Componentized with well defined interfaces • This allows plug-and-play of components from multiple vendors with minimal effort for integration and ensuring interoperability

11. Conclusions • Our Mobile Phone centric, always connected lifestyle is leading to In-vehicle Infotainment and Telematics Systems that can no longer remain vehicle centric but has to adapt itself to technologies of Mobile Devices and the Web which evolve / change almost 3 ~4 times faster than traditional Auto Electronics • Integrating technologies that was not primarily designed for in-vehicle usage while not creating Driver Distraction is not an easy task • While Open Source technologies can enable new use cases for in-vehicle Infotainment Systems, it comes with its own challenges • All these call for a new paradigm for software development that thrives on short cycles and collaboration amongst competitors • A resilient software architecture that is designed from grounds-up to support change (easier said than done) can be an approach for mitigation of some of these problems

12. Thank You for your attention! Renukaprasad Sharma General Manager – Automotive Electronics renukaprasad.sharma@wipro.com www.wipro.com/automotiveelectronics