delivering next generation...
TRANSCRIPT
Matt Jones Technical Lead for Future Infotainment, JLR Vice-President, GENIVI
Delivering Next Generation Infotainment
JLR: Key Facts
XK XJ XF
Range Rover RR Sport Evoque
Discovery 4 Freelander 2 Defender
JLR 2012 Line Up
Our PD Sites: Whitley
A former site for Whitley and Lancaster Bomber production
55 acres & 76,000m2 of office space
3000 employees
Home to Powertrain Engineering, Electrical Engineering and the Jaguar Design Studio
Our PD Sites: Gaydon
Converted from V-Bomber base in 1977
World-class R&D centre of the Automotive Industry
60 Km of Test Tracks
4500 people and rising
VR suite, climatic wind tunnels, rig test and engine test beds, electro-magnetic chamber
More Great Cars Faster…. ….in a Sustainable World
7
What’s happened previously?
8 8
Generations of Infotainment
• A collection of stand-along generations of infotainment system. • Proprietary hardware and software from individual suppliers. • Designed to deliver the initial feature set and stop.
• This has lead to the support of multiple, concurrent architectures
• Similar feature sets, different specifications, different Tier 1 vendors.
2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017Gen 1.0Gen 2.0Gen 2.1
9
What do vehicle buyers want?
10 10
Killer Features – Requested in 2011
• Multimodal HMI > HD Displays > Improved Voice Control
• Connected World > Telematics > Connected Navigation
(augmented offboard) > App Store
• Media Management – Online & Local • HD Audio / Video • Full Feature RSE
This is a fully featured home entertainment network…
11 11
Connected Navigation
• Latest maps available all of the time. > Just like Google Maps, but cached so available offline.
> Update strategy to just update differences.
• Linked POI from mobile devices and online accounts
• Support for future technologies: photo real maps.
12 12
App Stores
• There are hundreds of “App Stores” on the web. > iTunes App Store
> Google Apps
• Apps allow feature to be added by the user as soon as its available.
• Mindset change for system creation > The feature used to be: It should support email.
> Now it should be: It should support Apps, with some available to email…
13 13
Killer Features – Requested in 2014
Killer Features in 2014? WE HAVE NO IDEA!
• What is the next killer app on the smartphone?
14
What do automotive OEMs want?
15
Overall
16 16
Sell Cars…
• Easily deliver the features that customers want.
• A system that can be rapidly expanded.
• Ability to update software and add new features often.
17
Where does GENIVI feature?
2-Oct-12 Copyright © GENIVI Alliance 2011 (all x-wave images reproduced with permission from Visteon & 3M)
18
The GENIVI Charter: Mission, Purpose and Deliverables
Mission: • GENIVI is a non-profit industry alliance committed to driving the broad
adoption of an In-Vehicle Infotainment (IVI) reference platform. • GENIVI will accomplish this by aligning requirements, delivering reference
implementations, offering certification programs and fostering a vibrant open source IVI community
Purpose: • Ease IVI product integration • Enable open innovation and inheritance from adjacent industries Deliverables: • Aligned IVI requirements across a broad base of OEMs • Code that “satisfies” the requirements and “demonstrates” the compliance
statements • A compliance program against which commercial offerings can be certified
and ISVs can develop. 2-Oct-12 Copyright © GENIVI Alliance 2011 19
2-Oct-12 Copyright © GENIVI Alliance 2011 20
• 13 Automakers • 21 Tier1 Suppliers • 20 Silicon Suppliers • Major Software and
Service Suppliers
170 Members (and growing ):
2-Oct-12 Copyright © GENIVI Alliance 2011 21
Leadership - Officers
President
Graham Smethurst
Vice President
Matt Jones
Chairman
Doug Welk
Secretary
Kyle Walworth
Treasurer
Joel Hoffmann
Requirements Alignment Process
2-Oct-12 Copyright © GENIVI Alliance 2011 22
Lead OEM Contributes first
requirements
First requirements reviewed by other OEMs
Other OEMs contribute
requirements to fill gaps
Group agrees to aligned
requirements
Group determines
best functionality to
meet requirements
Group documents requirements and
matching components into a
compliance statement
EXPERT GROUP LED BY OEM
SUPPORTED BY TIER1
2-Oct-12 Copyright © GENIVI Alliance 2011 22
2-Oct-12 Copyright © GENIVI Alliance 2011 23 2-Oct-12 23
Audio Graphics Multimedia Speech
Connectivity
Package Management Security
System Infrastructure
Networking
External Access CE-device Positioning
Personal Information Management
OS kernel, drivers and libraries
IVI Implementation Model Comparison
2-Oct-12 Copyright © GENIVI Alliance 2011 24
Hardware Design
BIOS(Intel)
Boot Loader(GRUB)
Kernel (linux-2.6.21) BSP
GN
U li
bc-2
.5
Aut
oSA
RA
bstr
actio
n La
yer
Traf
fic In
fo M
anag
er
CE
Dev
ice
Man
ager
Per
sist
ence
Man
ager
Nua
nce
AS
R
Nua
nce
TTS
X-O
rg
IEG
D D
rive
rs
IP S
tack
v6
Net
wor
k M
anag
er
VM
OS
T D
ispa
tche
r
SM
SC
Net
Ser
vice
s
WE
B S
erve
r
Aud
io M
anag
er
Par
rot B
luet
ooth
Sta
ck /
Pro
files
Hel
ix F
ram
ewor
k
A/V
Cod
ecs
Evo
lutio
n Fr
amew
ork
Gra
ceN
ote
CD
DB
IPC (D-BUS)Socket LayerC/C++ API Bindings
She
ll (b
ash)
Per
l Int
erpr
eter
Pyt
hon
Inte
rpre
ter
Initi
alis
atio
n S
crip
ts
Mac
rom
edia
Fla
sh
Bro
wse
rC
ore
Eng
ine
Tele
phon
yC
ore
SM
SC
ore
PIM
Cor
eP
IMA
pp
SM
SA
pp
Tele
phon
yA
pp
Bro
wse
rA
pp
XX
XC
ore
XX
XA
pp
Mul
timed
ia P
laye
rA
pplic
atio
n
Oth
erA
pplic
atio
ns
Nav
igat
ion
Eng
ine
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
Mis
c Li
brar
ies
/ Com
pone
nts
Hardware Design
BIOS(Intel)
Boot Loader(GRUB)
Kernel (linux-2.6.21) BSP
GN
U li
bc-2
.5
Aut
oSA
RA
bstr
actio
n La
yer
Traf
fic In
fo M
anag
er
CE
Dev
ice
Man
ager
Pers
iste
nce
Man
ager
Nua
nce
ASR
Nua
nce
TTS
X-O
rg
IEG
D D
river
s
IP S
tack
v6
Net
wor
k M
anag
er
VMO
ST D
ispa
tche
r
SMSC
Net
Ser
vice
s
WEB
Ser
ver
Aud
io M
anag
er
Parr
ot B
luet
ooth
Sta
ck /
Prof
iles
Hel
ix F
ram
ewor
k
A/V
Cod
ecs
Evol
utio
n Fr
amew
ork
Gra
ceN
ote
CD
DB
IPC (D-BUS)Socket LayerC/C++ API Bindings
Shel
l (ba
sh)
Perl
Inte
rpre
ter
Pyth
on In
terp
rete
r
Initi
alis
atio
n Sc
ripts
Mac
rom
edia
Fla
sh
Bro
wse
rC
ore
Engi
ne
Tele
phon
yC
ore
SMS
Cor
e
PIM
Cor
ePI
MA
pp
SMS
App
Tele
phon
yA
pp
Bro
wse
rA
pp
XXX
Cor
eXX
XA
pp
Mul
timed
ia P
laye
rA
pplic
atio
n
Oth
erA
pplic
atio
ns
Nav
igat
ion
Engi
ne
Adaptation Code MOST FBlocks
VMOST Client Library
HMI for Non Integrated
Applications
3D MAP
Engine
HMI Layer
XXX
Cor
eXX
XA
pp
XXX
Cor
eXX
XA
pp
Mis
c Li
brar
ies
/ Com
pone
nts
Code created by the 1st tier.
Licensed code from eco-system partners pre-integrated in the platform
Open Source Kernel / Open Source Packages
Code created for automotive compliancy
User interface logic and graphics
Classic/Proprietary GENIVI/Open Source
GENIVI Compliance Program
• The new compliance program provides the necessary level of standardizations to allow developers to deliver implementations that will run on all GENIVI compliant distributions.
• As of January 2012, 9 Companies/Organizations have successfully completed the compliance program certification and now have registered GENIVI Compliant Products.
• Throughout 2012 and beyond numerous additional companies will be registering their products as well.
2-Oct-12 25 Copyright © GENIVI Alliance 2011
Asia OEMs
European OEMs
2-Oct-12
Copyright © GENIVI Alliance 2011 GENIVI is a trademark of the GENIVI
Alliance
26
Investigation Product Specification
Product Development
Product platform decision
Product nomination
Product SOP
OEM Adoption Progress
2-Oct-12 Copyright © GENIVI Alliance 2011 27 2-Oct-12 27
• OEM Production Launches • Continuous Build • GENIVI is hosting projects with
Linux Foundation
• GENIVI founders
Develop Alliance structure
2008
• Launch Alliance • Refine specs /
architecture • Delivery of GENIVI
v1.0 as source code.
2009
• Active recruitment of applications providers
• GENIVI next release • OEM product
commitments • Initiate compliance
program
2010
• Establish continuous build strategy
• Launch Compliance Program
• Broad adoption by OEMs
2011
2012 and Beyond
28
How is JLR moving forwards?
29
JLR: The Next Steps
• We have developments in progress on Linux in the IVI space • We are automotive, they still take a long time…
• We’re continuing to be heavily involved with GENIVI • We need a standardised IVI platform…
• JLR have joined the Linux Foundation • Working with and learning from the world’s largest collaborative coding
project…
30
JLR: Why AGL?
• JLR are participating in the Automotive Grade Linux
workgroup with the Linux Foundation • Complementary to GENIVI, in future we need Linux elsewhere in the vehicle…
• Shows real promise
• We need the Debian / Fedora of automotive:
• To enable experimentation
• To open up the community
• How can we let the community “hack” certain parts to add features
31
Conclusion
32 32
Partnerships / Community
• We’re creating partnerships & communities, rather than pure sourcing relationships.
• These are starting during the specification phase with engineering development partners.
• Not just at an OS level, but with individual applications
33 33
Roadmaps
• We’re buying-in to technology roadmaps: > Linux distribution > Software providers > Silicon suppliers > Network technologies
34 34
Open Source Software
• JLR are committed to Open Source Software: > It is our intention to push out any software that does not give JLR a
competitive advantage. > We have set up code scanning tools to check all licenses > We have driven down the ability to release code to the lowest possible
level… > Our code locker will automatically push Open Source licensed software to
an open website.
*This really scares our lawyers!