+ All Categories
Home > Documents > In-Vehicle Infotainment (IVI) Control from Mobile · PDF filesoftware technologies to ......

In-Vehicle Infotainment (IVI) Control from Mobile · PDF filesoftware technologies to ......

Date post: 30-Mar-2018
Category:
Upload: phungdang
View: 221 times
Download: 1 times
Share this document with a friend
17
In-Vehicle Infotainment (IVI) Control from Mobile Devices
Transcript

In-Vehicle Infotainment (IVI) Control from Mobile Devices

What Our Customers Told Us

Top 5 most important software technologies to our customers in next 1-3 years: 1. RTOS 2. Open Source (Linux or

Android) 3. Connectivity 4. Security 5. Dynamic U/I

46% Anticipate changing OS in near future

74% Will also require an RTOS

43% Do not have a migration strategy or expertise in-house

73% Value sourcing Hardware, Software and related Services from same partner

81% Said they would see value if Avnet offered embedded software services

88% Interest in Open Source (Linux, Android, etc.)

33% Leverage partners for software services today

Ensure Quality with Software QA & Test Automation

Software QA, Test Design & Metrics, Test Automation, Functional & Performance Testing

Scale Globally with Internationalization

Global Product Enablement, Localization, Linguistic Verification & Functional Testing

Software Services

Speed Time to Market with Embedded Expertise

Platform Migration & Optimization --- Freescale, Xilinx, TI, Intel

Engage in Co-Creation with Avnet Embedded Software Services to:

Go Mobile with App and Cloud Services

App Design, Development, Porting & Testing --- iOS, Android, Linux, Windows Phone, QT

Get Embedded with OS Development

Image & Application Development, Training --- Windows Embedded, CE, Linux, Android, iOS

Why: The Connected Car Opportunity

> By year-end 2020, Gartner predicts that more than 80 percent of all new vehicles sold in mature automobile markets, such as the United States, will offer connected-vehicle functionality.

> A Business Insider report titled: “The Battle For The Connected Car: Google And Apple Want To Dominate Our Dashboards”, states:

• Within 5 years there will be over 60M connected-cars on the road globally

• Car-focused telecom, hardware and software services will drive some $51 billion in annual revenue by 2018.

• Americans spend an average of 1.2 hours a day traveling between locations

Google And Apple Want To Dominate Our Dashboards

> Google teamed up with Audi, GM, Honda, Hyundai and Nvidia to create the Open Automotive Alliance, a partnership that aims to bring the Android platform to cars starting in 2014.

• Google Bought Waze For $1B, Giving A Social Data Boost To Its Mapping Business

> Apple announced the Carplay technology in June 2013 which enables the Apple UI and control transfer from phone to IVI via USB

• Based on Apple Genevi announcement: First products coming to market in 2014 to include Volvo, Hyundai, Ferrari, Honda, Mercedes, Jaguar

• Symbio has partnered with Apple and Volvo over the last year to build the first commercially viable CarPlay implementation

What is Apple Carplay?

> Carplay is NOT an in-car system that runs iOS. It’s a system that integrates your iPhone apps with your car’s HMI, allowing you to control applications and your device.

> Introduced in iOS 7.1. Specifications available under NDA.

Voice Touch Knobs and controls

What: Features from Phone

Maps Messages

Phone Music

What: HMI Features

> UI to the HMI

• Full screen or Window mode

• Independent virtual screen

• Supports multiple resolutions

> Resources

• HMI handles HW resources

Microphone, audio input

Speakers, Audio output

Controls – Voice, Touch, Knobs

How: Principle Of Operation

iOS Device IVI / HMI System

UI stream

Audio input stream

HID event stream

Main and alternate audio stream

Virtual display HMI display

How: Architecture

Automotive HMI

Mfi Authentication

Audio: Decode Encode

Video: Decode

Resource management

User Input

Carplay API

Communication Plugin

Bonjour

iAP2 Client

Legend:

Customer specific

Symbio adaptation

Carplay implementation

iAP2 Authentication Metadata

Accessory data

Audio LPCM

Video H.264

Control A/V controls User actions

USB ( CDC / NCM )

iOS Device

Carplay adaptation

Platform support package

How: Symbio Connected Car

> Software module for Symbio Connected Car functionality to IVI systems • Currently available for Linux, WEC7

• Available 2nd half of 2014: Android, WEA7, WEC 2013, WES7, QNX

> Implementation contains • SCC functionality including Apple co-processor authentication

• Implementation of Bonjour service discovery

• iAP2 functionality

• Integration to platform video and audio processing

• Well defined interfaces and APIs to seamlessly integrate into existing IVI systems and other HMI products Audio and video resource management

HMI mode management

Steering wheel buttons, knobs and screen touch

How: Symbio Connected Car

> User interface is transferred as H.264 encoded video stream

• HW based decoding is mandatory

> Audio is transferred as linear PCM or compressed stream

• Main and alternative output to IVI loudspeakers

• Input from IVI microphone

> Touch and other user input (buttons, rotary encoders etc) are transferred as HID event stream

Future Connected Solutions

Connected Home

In-Flight Industrial Marine

Medical Retail

Demo

> Running Linux on i.MX6

iMX.6

Display

CarplayAuthen ca on

chip

I2C–USBOTG

LVDS(Data)

Control(GPIO)

I2C

I2C

OTG–USBadapter

Lightningcable

Symbio Connectivity Solution (SCS)

> Enable OEMs, Tier1s and accessory manufacturers to connect smartphones to car IVIs through Symbio’s Connected Car solution, starting with Apple devices and expanding to Android devices in 2nd half of 2014.

> SCS Solution includes:

• Licensed iAP2 and Digital iPOD out as a full solution

• HW/ SW adaptation

Performance optimization and UI adaptations to IVI systems

• Productization

• Validation

• Certification

• Maintenance

To Learn More

> MFI Program

• https://developer.apple.com/programs/mfi/

• https://mfi.apple.com/MFiWeb/getFAQ.action#2-1

> Avnet

• Please contact your local Avnet Rep, or

John Weber

[email protected]

> Symbio

• Wesley Wright

[email protected]

There are 2 types of Licenses: a Development License and a Manufacturing License. Companies that plan to develop/help develop, but not manufacture, MFi accessories are eligible for the MFi Development License. Companies that plan to manufacture MFi accessories AND own a high- volume manufacturing facility are eligible for the MFi Manufacturing License. The following tables describes the features of each license:


Recommended