Trends for future in-vehicle communication Andreas Lock

Andreas LockRobert BOSCH GmbH

Trends for future in-vehicle communication

Powertrain Solutions | PS/NE-SC, AE-BE/EKE | 2020-09-22© Robert Bosch GmbH 2020. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of applications for industrial property rights.© Robert Bosch GmbH 2016. Alle Rechte vorbehalten, auch bzgl. jeder Verfügung, Verwertung, Reproduktion, Bearbeitung, Weitergabe sowie für den Fall von Schutzrechtsanmeldungen.

4

Trends for future in-vehicle communication

connected

car2car

electronic horizonsmartphone integration

eCall cloudfleet management

augmented realityservices

electrifiedplug-in

hybrid

battery

e-motorpower electronics

range

charging infrastructurefun-to-drive

eBike

eScooter

costs

automated

driver assistance

valet parking

emergency braking

redundancysensors

autopilot

highway-pilot

electric steering

legislation

Future Mobility: Electrified, Automated and Connected

Powertrain Solutions | PS/NE-SC, AE-BE/EKE | 2020-09-22© Robert Bosch GmbH 2020. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of applications for industrial property rights.

(R)Evolution of the E/E ArchitectureTrends for future in-vehicle communication

3

Performance ECUs e.g. (Cross-)Domain Control Unit, (Cross-)Domain Computer, Vehicle Control Computer

Optional ECUs (e.g. Central Gateway)typ. state of the art automotive ECUs (function specific)

Domain independent Zone ECUs Domain specific Zone ECUs (e.g. todays Door ECU)

Sensors/Actuators ECU = Electronic Control Unit

Distributed E/E Architecture

mainly encapsulated E/E architecture structure

(Cross) Domain Centralized E/E Architecture

to handle complexity of increasing cross domain

functionsTOM

ORR

OW

TOD

AY

Vehicle Centralized E/E Architecturedomain independent vehicle centralized

approach with central vehicle brain(s) and neural network (zones): Logical

centralization and physical distributionFUTU

RE V

ISIO

NVehicle Computer

Vehicle Cloud Computing

Domain Fusion

Domain Centralization

Integration

Modular

Trend

Vehicle volumes w/w

2025 2030

electrified

automated

connected


Function Repartitioning - Example: Function Split in PowertrainTrends for future in-vehicle communication

4

Benefits:• Encapsulation of HW variance of different powertrain types• Focus of OEM differentiation on Central CU

• Flexibility in the choice of powertrain actuators like internal combustion engine, gearbox, e-machine, …

• Chance for higher degree of standardization on Engine CU to „Smart Actuator CUs“.

Function Split in Powertrain is…… in field w/ some passenger car OEMs… state of the art for commercial vehicles… aligned with market trends… analyzed & proven in VIP demonstrator vehicles

CU = Control UnitECU = Engine Control Unit VIP = Vehicle Integration Platform

Modular extension/replacementdependent on PT type

SW-Adaption to equippedactuators & topology

ECUsmart Act.

Transm. CU

eAxle / InverterVIP / Central CU

Battery CU

High performance computing servers in combination w/ separation technologies allow a repartitioning of functions and a split of control loops and signal chains boosting requirements on IVN


PC and UAT systems have different configurations & capabilitiesTrends for future in-vehicle communication

5

Two Applications

Two Targets

Two Systems15+sensors

40+sensors


Requirements for future In-Vehicle Network (IVN)Trends for future in-vehicle communication

6

� High bandwidth, high throughput

� Complementary SerDes asymmetric high speed communicationfor end point devices (cameras, displays, sensors)

� Fill the gaps in embedded area (10BASE-T1S, CAN XL)� IVN homogenization towards Ethernet / IP but

� Coexistence with legacy automotive technologies

� Demand on QoS, network availability, security, … è Ethernet/TSN� Dynamic reconfiguration è Software Defined Networking (SDN)

� Cloud connectivity (quickly becoming a more integral part of E/E-A)

100Mb … Multi Gig Ethernet10MB .. 100Mb EthernetCAN, -FD/-XL, FLX, LIN, …

Distributed & new functions and split signal chains lead to increasing requirements for the IVN


Technology solution portfolioTrends for future in-vehicle communication

7

Powertrain

Body

Infotainment

Vehicle Motion& Safety

2010 2016 2020

Camera Systems

Diagnostics

Domain ECU Backbone

CAN FR

CAN

CAN

CAN

CAN

CAN

CAN

CAN

CAN

CAN CAN

FR FR

FR

CAN FD

CAN FD

100BASE-T1

100BASE-T1

100BASE-T1

100BASE-T1

100BASE-TX

100BASE-T1

OABR**

100BASE-TX

SerDes SerDes

OABR*MOST

Vehi

cle

Dom

ains

Spec

ific

Apps

CAN FD

CAN FD MOST

Analog SerDes

Possibility to be phased out

1000BASE-T1

1000BASE-T1

1000BASE-T1100BASE-TX

1000BASE-T1

1000BASE-T1

Analog

MOST

100BASE-T1

SOC = Service oriented Communication * = MIPI® A-PHY℠ / D-PHY℠ **OABR = Open Alliance BroadR-Reach

Cent

ral C

ompu

ter

Vehi

cle

Zone

BackbonePHY

100BASE-T1

1000BASE-T1

Multi Gig

Proprietary

BackboneLayer 2+

AVB

TSN

IPv4

IPv6

Seamless cloud integration

202x

100BASE-T1

1000BASE-T1

Multi Gig

CAN FD/XLECU

Sensor/Actuator

AVB

TSN

SOC

100BASE-T1

1000BASE-T1

Multi Gig

SoC

SOC

FlexRay

FlexRay

10BASE-T1S

10BASE-T1S

LIN

CAN FD/XL

AVB

TSN

LIN

SerDes*

SerDes *

M/NEE-Henkel | 2019-06-25© Robert Bosch GmbH 2019. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of applications for industrial property rights.

Bandwidth of Technologies in Automotive LandscapeTrends for future in-vehicle communication

8 1) with LVDS: A-PHY / D-PHY

LIN

bit/s1 Mbit/s

10 Mbit/s

100 Mbit/s

1 Gbit/s

10 Gbit/s

0,1 Mbit/s

CANFlexRay

3G - 5G

asymmetric

0,01 Mbit/s

symmetricVehicle2X (vehicle, cloud)

Vehicle Computer Net

Embedded Network

Sensor- / ECU-Bus SerDes1)

Camera, Radar, Lidar

Automotive Ethernet

Point2Point

switchable2)

unswitchable

2) direct communication between more than 2 ECUs possible


Hardware Acceleration (HWA) – a possible solution for future IVNTrends for future in-vehicle communication

9

Today´s solution with software Future solution with HWA Improvement

Throughput < 1 Gb/s (multi core) > 10 Gb/s > 10 x

Throughput in events/s < 200k > 10M 50 x

Jitter/Latency up to 1ms < 20µs 50 x

Multi-protocol Implemented in SW implemented in HW

Virtualization Available for Ethernet Generalized virtualization concept

Security DMA based SW offload encryption/authentication

In band encryption/authentication

Configuration Typically pre-build configuration Runtime configurable

0

500

1 000

1 500

2018 2020 2022 2024 2026

Data Volume (2018-22 RFQ, 23-27prediction)

Mb/s

Increasing factors:

- Automated

- Connected (e.g. FOTA)

- Electrified

- Shared

µP

Vehicle Computer/Central Gateway/Domain Control Unit/Zone

µC Ethernet Switch

CAN FR LINTechnical limitation* by SW approach

µP

Vehicle Computer/Central Gateway/Domain Control Unit/Zone

µC w/ HWA

CAN FR LIN

Throughput demand Today solution with software Future solution with HWA

Eth Eth

* single core


Security AspectsTrends for future in-vehicle communication

10

2

Integrity protection of critical in-vehicle signals and messages

In-vehicle network

1

ECU software and data integrity protection

Individual ECU

4

Vehicle firewall and security standards for external interfaces

Connected Vehicle

Protected and separated domains by E/E architecture and gateway

3

E/E-Architecture

ADAS = Advanced Driver Assistance System

BCM = Body Control ModuleECU = Electrical Control UnitGW = GatewayHU = Head UnitPT = Power Train

5

Network communication behavior is monitored and analyzed

Intrusion Detection Sys.

OBD Secure

Manufacturing

HU BCM……

Gateway

……

PT…

ADAS…

OBD

6

Secure generation and injection of cryptographic material

Secure Manufacturing

Ø Increasing communication bandwidth in future EE-architectures and the call for more and more Security Functionality in the car requires Hardware Acceleration for Firewall and Intrusion Detection System (IDS) functionality and efficient implementations of Security protocols (e.g. SecOC, MACsec).


SummaryTrends for future in-vehicle communication

11

� Automated, Connected , Electrified & Shared (ACES) drive … � … the significant growth of (cross domain) functions and system characteristics like safety and cyber security� … the functional centralization and hence introduction of vehicle integration platforms (central / zonal)

� … increasing interactions with the cloud, infrastructure and other mobile devices (C2X)

� Modern In-vehicle communication will provide� Higher bandwidth, QoS enforcement and management of dynamically changing communication requirements

� Integration of different bus technologies preserving investments in legacy communication� Excel in performance and security at competitive costs leveraging HW accelerators (e.g. EDE, HSM)

� Automotive industry will increasingly build on synergies between automotive and mobile device technologies (esp. MIPI® D-PHY℠, MIPI® A-PHY℠, MIPI® I3C℠)

� Specific automotive requirements might be introduced into MIPI-standards (e.g. longer reach, harsh environment, high temperature, reliability, safety, security)

Documents

Trends for future in-vehicle communication Andreas Lock