Software Long Term Support Automotive Market Requirement › images › public › 2019 ›...

Software Long Term SupportAutomotive Market

Requirement

Fulup Ar FollCEO IoT.bzh

[email protected]

December 05th 2019Software Long Term Support Automotive Market Requirement 2/29

Table of contents

I. Who are we?

II. Supply market current conditions

III. Long Term Support (LTS) requirements

IV. IoT.bzh LTS proposal

V. Planning

VI. Conclusion

Who are we?I


About us

LORIENT➢ 29 engineers mostly dedicated to AGL➢ Our goal is to deploy AGL in cars, boats...

● https://iot.bzh/en/● http://github.com/iotbzh

https://iot.bzh/en/

http://github.com/iotbzh


1st contributor to AGL since 2016

References: Walt Miner (Linux Foundation)

AGL AMM 2017 https://sched.co/9KB6AGL AMM 2018 https://sched.co/DRAXAGL ALS 2019 https://sched.co/L8W3AGL AMM 2019 https://sched.co/VHQD

About 60% of contributions.

https://sched.co/9KB6

https://sched.co/DRAX

https://sched.co/L8W3

https://sched.co/VHQD

Supply market current conditions

II


Average vehicle age evolution ● The EU motor vehicle fleet is getting older year-on-year. Passenger cars are now on average 11.1 years

old, vans 11 years and heavy commercial vehicles 12 years (source ACEA, 11/06/2019)

● The average age of light vehicles in operation in the U.S. has risen again as consumers continue to hold onto cars and light trucks longer. Driven by technology and quality gains, the average age of light vehicles on U.S. roads is 11.8 years (source IHS Market 27/06/2019)

● IHS Market found that the number of older cars and light trucks is growing fast, with vehicles 16 years and older expected to grow 22% to 74 million from 2018 to 2023


Average smartphone age evolution

2016 2017 201820

21

22

23

24

25

26

27

Smartphone life cycles in months on the uptrend

USA

China

EU5

Years

Life

cyc

les

(mo

nth

s)

● Smartphone lifecycle is about 2 years in EU & US & 1,75 years in China

Automotive is not a “smartphone on wheels”


R&D investments● “Worldwide R&D spending among the world’s 1000 largest corporate R&D spenders increased

11.4% in 2018 to 782B$

● Technology cost rise will increase car-maker platforms lifecycles● A connected car platform only (IVI, cluster, telematics, cloud) now cost > 300M€


Cybersecurity reglementations

● The European Cybersecurity Act has been voted in June 2019 by EU parliament● ENISA will have authority upon national entities to establish European certifications including automotive

European Cybersecurity

Act vote

Long Term Support Requirements

III


OEM supply contract model S

uppl

ier n

omin

atio

n

[...]

End

of L

ife

Within the RFQ document, the

Suppliers receives information about

the forecast volumes (annual and total for the

vehicle life cycle) as well as the

requested capacity level

In the contract, the Supplier commits to setup the

volume/capacity indicated in RFQ with regard to the project

milestones

5 years is a typical duration that can be

extended to 7 years like for most popular cars (e.g.

average 7 years between each new Renault Clio

generation)

Example of contract term: “Over the 10 years which follow the end of mass-production, the

Supplier should supply parts in accordance with the requirements expressed by [the OEM]. This

10 years does not lead to a deadline, an ending-date or an authorization to cease the

supply a part.”S

tart

of P

rodu

ctio

n

End

of M

ass

Pro

duct

ion Project phase: 3 years Mass Production

phase: 5 to 7 years

RFQ

laun

ch

Aftersales phase: min 10 years

[...] [...]

Total: from 18 to 20 years


Context & requirements

● Existing systems

– Targeting mainly safety certification but not application security nor cybersecurity

– Not adapted to constantly evolving systems

– Not adapted to complex systems

– Not adapted to long term maintenance

● Requirements

– Reduce integration, maintenance costs and time-to-market

– More and more complex systems (>1000 components in a car, >1000 code changes per day, 100 millions lines of code in a car)

– Over-the-Air software update and cybersecurity...

– Very Long Term Support (security patches applied on systems over 10/15 years)

IoT.bzh proposal

Codename: Redpesk®

IV


R&D Funding

● 2018 bpifrance and Ademe “Innovation contest” ● Supported by the investment program “Avenir”

and the French Prime Minister Cabinet


What’s behind RedPesk® ● Automated CI plateform : builds and tests

● Multi-Boards : a dedicated board for every car model● Multi-Applications : depend on models, variants, years, …● Multi-Customers : OEMs, Tier1s, apps providers, ...● Multi-Systems : Linux(AGL/Android), RTOS(Zephyr, VxWorks), …

● Target very complex developments● Teams Developers, Sub Contrators, Management, Business Owner, …● Thousand of packages, Millions lines of code● Legal constrains (Licences, Ownership dependencies)● Cybersecurity/Certifications (code scanning)

● Robust, highly available & adaptable ● (1000 changes/day) * (X boards) * (Y customers) * (Z apps)● Availability, Scalability ● Simulate of vehicle environments


General Building Mechanic


● A project is managed by a Team of Users

● A project is made of one or more applications sharing common constrains

● An application build result in one/many RPM packages

● A given project RPM packages are published in one/many repositories

Project A

App 1

App 2

Repository GG / ARM64

DistributionAGL by IoT Version GG

ARM64

DistributionAGL by IoT Version GG

Intel64Repository GG / Intel64

Build & Tests

Build & Tests

Managed by Car Maker Team 1 Managed by IoT.bzh Team

Very similar to well-known

IT Linux distributionsbut for

Embedded devices

Project & Applications


Global architecture

Red-Pesk - Backend Server

Build ServersBuild Servers

Build Servers Farm

Tests Manager

Red-Pesk Web UI

RPM repositories

Build Manager

User Management

Boards Management

RTM Board

RTM Board

DB +

files

Packages Provider

Web UI

RTM

Core

& APIs


C.I. workflow

The

icon

s use

d in

this

dia

gram

are

mad

e by

Fre

epik

from

ww

w.fl

atic

on.c

om

Agile Manager

Agile Developer

#1

Agile Developer

#2

Source Control Server

BuildUnit testVirtual Integration testReal Integration test

Checks out code

Commits changes

CI Server initiates a build

1

2

3

4a

4b

56

Build Passed

Build Failed

Users notification : Fail or Pass

https://www.freepik.com/home

http://www.flaticon.com/


Integration test example

The

icon

s use

d in

this

dia

gram

are

mad

e by

Fre

epik

from

ww

w.fl

atic

on.c

om

Start the target Boot with RedPesk ®

Powered imageGet the project to test, here: “ dnf install -y signal-composer”

Signal-composer integration tests

- Play CAN data from a file on the emulated BUS

- Simulate USB storage

- Etc.

Upload tests logs and results to the RedPesk infrastructure Stop the target

Signal-composer example

https://www.freepik.com/home

http://www.flaticon.com/


RTM infrastructure overall view

Client PC

WebUI

Iot.bzh Servers

VPN Client

Rackable Test Module n

µService RTM

RedPesk ® Backend

Iot.bzh Repositories

Cloud

VPN Tunnel

: 80

Internet access through client machine

Rackable Test Module 2 Rackable Test Module 1

Iot.bzh RedPesk ® Infrastructure

FIREW

ALL

ORVirtual Real


RTM: Real and Virtual Boards

LXC Hypervisor :

LXCLXC

LXCQEMU

ControllerQEMU AGL

VPN

Serve

r Routing Table

RTM API

IO

USB80

µService RTM

FIREW

ALL

Hardware RTM

VPN

Serve

r

µService RTM

Hardware RTMHardware RTMMaster Board

Iot.bzh RedPesk ® Infrastructure

FIREW

ALL

RTM

APIRouting

Table

Target BoardEth

CANUART

VideoAudio

V CC

Power supply & Monitoring

(A, W, °C)

..

..

Virtual Real

OR


V. Planning

PlanningV


Roadmap O

ctob

er 2

019

Nov

embe

r 201

9

Dec

embe

r 20

19

Janu

ary

2020

Febr

uary

202

0

Mar

ch 2

020

Apr

il 20

20

May

202

0

June

202

0

[...]

Dec

embe

r 202

0

Nov

embe

r 202

0

Janu

ary

2021

Febr

uary

202

1

First demos

First beta-

testers

Open to other testers

Qualification deployment

Production deployment

ConclusionVI


Conclusion

✔ RedPesk® is IoT.bzh’s response to:

Linux Industrial Embedded Long Term Support Issues✔ Sponsored by French subsidies

✔ Deployment schedule Q1 2021

✔ Market target automotive & marine first

Beta test opens Q1 2020, if interested contact [email protected]


Thank you for listening

Lorient Harbour, South Brittany, France

This

pic

ture

is a

n or

igin

al p

ictu

re ta

ken

by Ja

ck M

amel

et in

200

6. It

is u

nder

the

GNU

Fre

e D

ocum

enta

tion

Lice

nse

and

the

Crea

tive

Com

mon

s At

trib

utio

n.

LORIENT

Connected Boat Project IoT.bzh Test Boat

If you surf by, please visiting us.

https://www.gnu.org/licenses/fdl-1.3.fr.html

https://creativecommons.org/licenses/by-sa/3.0/deed.fr

Software Long Term Support Automotive Market Requirement › images › public › 2019 ›...

Documents

Transcript of Software Long Term Support Automotive Market Requirement › images › public › 2019 ›...