Is Auto The New Android?  

Dave Gruber

Director of Developer Programs

Black Duck Software

@black_duck_sw

2

In This Session We Will:

1. Explore the automotive opportunity

2. Auto initiatives currently underway

3. Compare and contrast the automotive platform with Android

4. Explore how you can prepare to participate

3

Automotive 101

4

“Information-based media content or programming that also includes entertainment content in an effort to enhance popularity with audiences and consumers.”

Glossary

Infotainment

IVI “In-Vehicle-Infotainment”

Headunit “the logical interface between the car and consumer space. Provides the user experience in the car.”

OEM “the automaker” (GM, BMW, Ford, etc.)

Tier 1 suppliers “companies that OEMs contract with to supply IVI units (Delphi, Alpine, etc)”

Tier 2 suppliers “HW/SW companies providing components to Tier-1s”

5

IVI HeadUnit – No Longer “Just a Car Radio”

6

Automotive Trends – Things are Changing

Value is shifting from manufacturing/assembly to Software– New “players” - IT and electronics companies

IVI Head Unit evolves as a multiuser, social and Cloud access platform

Balancing in-house development vs. strategic alliances with suppliers and competitors

Emerging “Always-ON” IVI integration with social net’s– Road hazards, Traffic conditions, Police / radar alerts– Internet, iPhone/iPad, Car-to-car communications

7

1. An insatiable customer appetite for functionality – Infotainment in the car has become important and a

differentiator in the car-buying decisions

2. Complexity and cost– Development and validation costs continue to spiral upward as

the amount of software required rockets

3. Aggressive competition from the consumer electronics

Industry Dynamics

8

Auto Customers are Frustrated!

Consumer Electronics IVI

• $hundreds• Latest

innovations

• $thousands• Out-of-date

immediately

vs.

9

Dev cycles

Why?

Lines of Code

Amount of SW

Complexity & Lack of standards

Life Cycle

consumer

auto

Year 1 Year 2 Year 3

consumer

auto

Year 1 Year 2 Yr. 10-30Year 3 Year 4

apps

Supply Chain Adds Complexity

Tier 1Supplier

OEM

Dealership

Tier 1Supplier

Tier 1Supplier

Dealership

Dealership

Dealership

Dealership

Dealership

Customer

Customer

Customer

Customer

Customer

Customer

Customer

Customer

Customer

Customer

Customer

Tier 3Supplier

Tier 2Supplier

Tier 2Supplier

Tier 2Supplier

Tier 2Supplier

Tier 2Supplier

Tier 2Supplier

Tier 3Supplier

Tier 3Supplier

Tier 3Supplier

Tier 3Supplier

Tier 3Supplier

Tier 3Supplier

Tier 3Supplier

Tier 3Supplier

Tier 2Supplier

Tier 2Supplier

11

Today’s needs: Speech recognition, touch screen, 3D graphics, heads-up display, gesture recognition, steering wheel controls, text to speech

Connectivity: SD Cards, USB, Bluetooth, WiFi connections, satellite radio

Soon: App stores, cloud services, social networking

Headunit Requirements

What’s the right balance? …for what stays in the portable consumer device

versus what goes in the head unit?

12

The head unit middleware must:

Communicate with portable consumer devices

Be a client for the cloud

Have the speed and reliability of an embedded device

Interface with auto-specific events

Provide the rich user functionality and ecosystem support of a PC

Avoid driver distraction through ease of use

A Closer Look at the Auto Platform

13

Legislation is growing in most states with mobile device restrictions– US national Highway Traffic and Safety Administration

Distractions cause accidents and death– Texting is on the top of the list!

IVI therefore needs to respond– Entering a GPS location – only when stopped

So what are the rules?– Studies are underway, best practices & guidelines will emerge

soon

Driver Distraction

14

No eye candy

Limit glances to 1-2 seconds (break down tasks into 2 second steps)

Ensure static positioning (predictable)

Limit menus

Short total task duration (10-15 seconds)

Limit/no reminder prompts

Driver MUST be able to pause at any time in the task (without further prompting)

Limiting Driver Distraction – The basics

15

What auto initiatives are underway?

16

Proprietary IVI platforms– Microsoft’s CE IVI platform– QNX CAR 2 IVI platform– Microltron IVI (primarily in Japan)

Device connectivity – MirrorLink, Car Connectivity Consortium (CCC)– FORD’s OpenXC– Renault Connect

Open platform initiatives– Android is being explored and tested by a few OEMs– GENIVI is the largest, best organized

Certified GENIVI compliant implementations: Tizen, Mentor Graphics IVI, MontaVista IVI, Ubuntu Remix IVI and Wind River IVI

Platforms & Connectivity

17

The GENIVI Alliance is a non-profit industry alliance driving the broad adoption of an (IVI) open-source development platform

– Launched in March 2009

– Founded by BMW, Wind River, GM, PSA, Delphi, Magneti-Marelli, and Visteon

– Members-only consortium at this time, but it seems inevitable that it will open up

– Now 162 companies participating

– Linux is the foundation

– Basic building blocks are in place

GENIVI

18

GENIVI Alliance Ecosystem Members13 OEMs, 20 Tier-1s, 18 Silicon Cos, 100+ SW/Tech Cos

19

GENIVI was launched to serve three primary purposes:

1. Build critical mass/ecosystem

2. Establish the technical program/architecture

3. Implement a compliance program

supporting both open source & commercial

A Closer Look at GENIVI

20

GENIVI Targets Non-differentiating Layers

•Differentiation• Integration•Commercial and Proprietary solutions

• Implementation Competition

Automaker and Tier1 Supplier Domain

AppsOSV

Extensions Libs

HMI - Human Machine Interface

•Non-differentiating features•Consolidated Requirements

•Auto Specific Middleware•Validation/Compliance

Alliance Domain

Open Source Kernel

Open Source IVI Stack

21

GENIVI Solution StackAdopt – Adapt – Create

Hardware

Reference Apps

Reference HMI

GENIVI Reference

GENIVI Platform

GENIVI Code

80%open source

15%5%

GOAL: Cut IVI ProductDevelopment From 7+ yearsDown to <2!

15% adapted5% custom

22

IVI Implementation Model Comparison

Hardware Design

BIOS(Intel)

Boot Loader(GRUB)

Kernel (linux-2.6.21) BSP

GN

U l

ibc

-2.5

Au

toS

AR

Ab

str

ac

tio

n L

ay

er

Tra

ffic

In

fo M

an

ag

er

CE

De

vic

e M

an

ag

er

Pe

rsis

ten

ce

Ma

na

ge

r

Nu

an

ce

AS

R

Nu

an

ce

TT

S

X-O

rg

IEG

D D

riv

ers

IP S

tac

k v

6

Ne

two

rk M

an

ag

er

VM

OS

T D

isp

atc

he

r

SM

SC

Ne

t S

erv

ice

s

WE

B S

erv

er

Au

dio

Ma

na

ge

r

Pa

rro

t B

lue

too

th S

tac

k /

P

rofi

les

He

lix

Fra

me

wo

rk

A/V

Co

de

cs

Ev

olu

tio

n F

ram

ew

ork

Gra

ce

No

te C

DD

B

IPC (D-BUS)Socket LayerC/C++ API Bindings

Sh

ell

(b

as

h)

Pe

rl I

nte

rpre

ter

Py

tho

n I

nte

rpre

ter

Init

iali

sa

tio

n S

cri

pts

Ma

cro

me

dia

Fla

sh

Bro

ws

er

Co

re E

ng

ine

Te

lep

ho

ny

Co

re

SM

SC

ore

PIM

Co

reP

IMA

pp

SM

SA

pp

Te

lep

ho

ny

Ap

p

Bro

ws

er

Ap

p

XX

XC

ore

XX

XA

pp

Mu

ltim

ed

ia P

lay

er

Ap

pli

ca

tio

n

Oth

er

Ap

pli

ca

tio

ns

Na

vig

ati

on

En

gin

e

Adaptation Code MOST FBlocks

VMOST Client Library

HMI for Non Integrated

Applications

3D MAP

Engine

HMI Layer

XX

XC

ore

XX

XA

pp

XX

XC

ore

XX

XA

pp

Tier-1Plattform

CommercialPackage

OEMMis

c L

ibra

rie

s / C

om

po

ne

nts

Tier-1 Product

Code created by the 1st tier.

Licensed code from eco-system partners pre-integrated in the platform

Classic/Proprietary

Hardware Design

BIOS(Intel)

Boot Loader(GRUB)

Kernel (linux-2.6.21) BSP

GN

U l

ibc

-2.5

Au

toS

AR

Ab

str

ac

tio

n L

ay

er

Tra

ffic

In

fo M

an

ag

er

CE

De

vic

e M

an

ag

er

Pe

rsis

ten

ce

Ma

na

ge

r

Nu

an

ce

AS

R

Nu

an

ce

TT

S

X-O

rg

IEG

D D

riv

ers

IP S

tac

k v

6

Ne

two

rk M

an

ag

er

VM

OS

T D

isp

atc

he

r

SM

SC

Ne

t S

erv

ice

s

WE

B S

erv

er

Au

dio

Ma

na

ge

r

Pa

rro

t B

lue

too

th S

tac

k /

P

rofi

les

He

lix

Fra

me

wo

rk

A/V

Co

de

cs

Ev

olu

tio

n F

ram

ew

ork

Gra

ce

No

te C

DD

B

IPC (D-BUS)Socket LayerC/C++ API Bindings

Sh

ell (

ba

sh

)

Pe

rl I

nte

rpre

ter

Py

tho

n I

nte

rpre

ter

Init

iali

sa

tio

n S

cri

pts

Ma

cro

me

dia

Fla

sh

Bro

ws

er

Co

re E

ng

ine

Te

lep

ho

ny

Co

re

SM

SC

ore

PIM

Co

reP

IMA

pp

SM

SA

pp

Tele

ph

on

yA

pp

Bro

ws

er

Ap

p

XX

XC

ore

XX

XA

pp

Mu

ltim

ed

ia P

lay

er

Ap

plic

ati

on

Oth

er

Ap

plic

ati

on

s

Na

vig

ati

on

En

gin

e

Adaptation Code MOST FBlocks

VMOST Client Library

HMI for Non Integrated

Applications

3D MAP

Engine

HMI Layer

XX

XC

ore

XX

XA

pp

XX

XC

ore

XX

XA

pp

Tier-1

CommercialPackage

OIPPackage

OpensourcePackage

OEMMis

c L

ibra

rie

s / C

om

po

ne

nts

Open Source Kernel / Open Source

Code created for automotive compliance

User interface logic and graphics

GENIVI/Open Source

User interface logic and graphics

23

Contrasting Android & Auto

24

Contrasting Auto & Android - Similarities

Mobile/Android Auto

Competition Apple vs. all Consumer elect vs. IVI

Collaboration Open Handset Alliance

GENIVI alliance

Leadership Google OEMs & Consortiums

Audience Highly diverse Highly diverse

External Interfaces

Cloud, auto, other Cloud, mobile

Function Utility, social & entertainment

Utility, social & entertainment

25

Contrasting Auto & Android - Differences

Mobile Android Auto

Operating environment

Connected or disconnected

Multi-state: parked, in-motion, engine running or not.

Apps & priorities

All apps = (limited priority)

IVI vs. core (core has priority)

Screens Generally small Mid-size

Connectivity >95% connected <50% connected

Usage restrictions

Almost none Distraction, in-motion

Supply Chain Well defined Broad & complex

HTML5 – Another Similarity

HMI layer converging - shaping up to be the UI approach of choice

Least/most common denominator

Will allow apps to be deployed on both CE & IVI

As an open standard, HTML5 avoids vendor lock-in

Leverage CSS to brand for different platforms

27

What the Auto Industry is Learning from Android

Letting mass innovation drive requirements accelerates platform evolution

Software is the differentiator

Aggressively leveraging open source can reduce complexity and lower costs

Leveling the playing field allows differentiation to occur higher up in the stack

28

Getting Involved Early with GENIVI

Members only BUT… supply chain is deep!

With 160+ companies involved, ecosystem is big

Companies outside of auto are involved

GENIVI has already declared that they want to recruit an ecosystem where open source developers can participate

“GENIVI's three tiered member program encourages companies of all sizes to participate, collaborate, and contribute to the success of our shared mission.”

http://www.genivi.org/

29

Final Thoughts

IVI is going to be big

Could be 2-5 years to get to a where Android is today

This is an opportunity worth watching closely

Early participants will have first-mover advantage

The auto industry needs help!!

Keep your eye on GENIVI

To learn more, read the OSS Revolutionizing Automotive Supply Chains Whitepaper

dgruber@blackducksoftware.com

@davegruber5