the evolution of infotainment apps as...

The Evolution of Infotainment

Apps as Differentiation Scott L. Linke, Automotive Architecture

QNX Software Systems

Freescale Technology Forum – Americas 09-Apr-2014 FTF-AUT-F0436

Connected car is a reality

Confidential Information of QNX Software Systems Limited

3

• Mobile experience changed expectations

– I want today’s app now… not next year…

• Ubiquitous access to “their” content

• Personalized and familiar experience

– Self-branding

– Ease of use

• Heterogeneous lifestyle and limited loyalty

– Apple users want Google, Amazon and Microsoft content

The consumer perspective

3


4

• How do I give the right “something” that makes “everyone” happy…

• “How do I maintain my brand…”

• “How do I keep up?”

The OEM perspective

4


5

Fragmented and heterogeneous…

• Standards based connectivity, but proprietary message set

– For example: Bluetooth Serial Port Profile with proprietary command & control

• Standard application environment, but proprietary APIs

• Mobile phones have unique tools and environments

• There is always some kind of proprietary fence to climb…


6

Who’s right ? What’s right ?

• It’s not about the phone… or mobile device

• It’s all about the apps that define “your” digital lifestyle

• Whoever can bring all of my apps from where ever they run… wins


7

Evolution of mobile device integration

Integration Technique

Examples

Smartphone Projection

MirrorLink, Apple CarPlay, Miracast, others…

App Integration Pandora Link, Aha Radio, OnStar RemoteLink, SYNC AppLink, BMW MINI Connected

Traditional Content Sharing

Bluetooth, USB, Wi-Fi, DLNA, Apple Made for iPod interfaces

Mobile compute power


8

Traditional content sharing

Head unit

Head unit is the master Mobile is slave

control

data

AVRCP A2DP

UMASS


9

App integration – client server model

Head unit

Head unit is client Mobile server

control & status

data

Client app

Server app

SPP CDC-NCM


10 Smartphone control – car as a peripheral

Service and app discovery

Authentication

Content

protection

Head unit display

Music, hands-free phone and voice recognition

off-load to phone

Video

P

R N D

Touch and hard button input

Auto sensors

Apple CarPlay

Audio

?

CDC-NCM


11 Car as a portal to “your” global digital lifestyle…

Service and app discovery

Authentication

Content

protection

Video

P

R N D

Touch and hard button input

Auto sensors

Audio

??

??

Music, hands-free phone and voice recognition

off-load to phone


12

What do I need…??


13

OpenGL ES

• Subset of OpenGL, for Embedded Systems

• Standard API, OpenGL ES 2.0

• Hardware accelerated in SoC

• Native support by operating system

• Focus on Embedded


14

Qt

• QML scripting with animations

• C++ with classic widget approach

• Support for Qt Creator deployment

• Support for almost any Operating System

5.1/5.2


15

• Used in Mobile and Automotive today

• Apps for cars

• Development possible by any web/app

experienced developer

• OS independent

HTML5


16

Web browser

Full Support for all HTML5 standards

• Audio/ video (through QNX multimedia technology)

• Geo-location

• Canvas

• WebSockets

• Offline applications

• Session storage

Enhanced browser

• High performance panning and scrolling

• Pixel-accurate zooming

• Physics-based scrolling and panning

• JavaScript JIT


17

Android

• Consumers want Android apps in the car

• Like all app environments

• must be automotive-hardened

• must offer levels of isolation from the rest of the system

• must be interoperable with rest of the system

• Still an emerging environment for automotive… but it cannot be

ignored.


18

Rendering from multiple input sources

• Audi TT Dashboard using multiple

technologies

– HTML5, OpenGL ES, Qt, video

• Mix and match graphical components to

create compelling user experience

• Required extensive graphics support to

formultiple rendering source s

– scaling, translation, rotation, alpha blending

• Final composition created a single unified

graphical interface from multiple

independent technologies

Composition example

Example with 4 UI technologies

• Background wallpaper: HTML5

• Video: From iPhone or iPod

• Navigation: OpenGL ES

• Control application: Qt5

• Transparently combine multiple off-screen

buffers onto the display

• Windows can be moved around, zoomed in /

out, rotated, or have transparency effects

applied without requiring the application to

redraw or even be aware

• Hardware and virtual layer support

• Full hardware acceleration

• Multi-modal input device support


19


20

Summary

• Role of mobile devices in the car is evolving

• Smart phone is becoming an automotive infotainment application platform

• Applications define the user’s lifestyle and they want “their” lifestyle in the car

• The ability to deliver the user’s lifestyle will be the key differentiator

• The Infotainment operating system must not only support but enable concurrent use of existing and emerging application technologies

© 2014 QNX Software Systems Limited. QNX, QNX CAR,

NEUTRINO, MOMENTICS, AVIAGE and other product

names are trademarks of Research in Motion Limited

doing business as BlackBerry, which are registered

and/or used in certain jurisdictions, and used under

license by QNX Software Systems Limited. The

information herein is for informational purposes only

and represents the current view of QSSL as of the date of

this presentation. Because QSS must respond to

changing market conditions, it should not be interpreted

to be a commitment on the part of QSSL, and QSSL

cannot guarantee the accuracy of any information

provided after the date of this presentation. QSSL

MAKES NO WARRANTIES, REPRESENTATIONS OR

CONDITIONS EXPRESS, IMPLIED OR STATUTORY, AS TO

THE INFORMATION IN THIS PRESENTATION.

Scott L. Linke Dir. Automotive Architecture

[email protected]

the evolution of infotainment apps as...

Documents