#636

CAR
IT
The Software-Defined Vehicle
Enabling the Updatable Car
Car IT
TABLE OF CONTENTS

Executive Summary

Defining the Software-defined Vehicle Business, technology, and supply chain

Core technologies

Global OEM activities As OEMs integrate more software-defined solutions into their vehicles, there is the potential for
future vehicle architecture to be defined by the software it uses, and the platforms adopted from
OEM impacts
its ecosystem. The end goal is a Software-Defined Vehicle - a car that leverages software to
Supply chain impacts and activities reduce the cost of development, boost performance, and enhance the in-vehicle user experience.

SBD Automotive’s Car IT Team has created The Software-Defined Vehicle report to support OEMs
RELATED SBD REPORTS and suppliers. It identifies the Software-Defined Vehicle and outlines how OEMs can utilize
platforms and services to build cars that can be continually updated, and progressively
629 – Automotive Operating Systems
maintained, by cross-platform software.
SBD's Car IT Team comprehensively profile the
modern infotainment ecosystems from the ground
up: system on chip (SoC) & silicon vendors,
automotive tier 1s, operating systems, and the
various ecosystems surrounding infotainment
supporting digitally-oriented consumer experiences.

632 – Intelligent Cockpits

COVERAGE FREQUENCY PUBLICATION FORMAT PAGES
The Intelligent Cockpits report assesses the key
attributes of intelligent, continuously interactive
vehicle cockpits to create a picture of how
technologies, with a broad range of primary uses, 1
can be joined to enable these new vehicle-focused
NA EUROPE ANNUALLY QUARTERLY ONE-OFF PD F POWERPOINT EXCEL ONLINE 170+
user experiences. ​ CHINA
 #636/The Software-Defined Vehicle

Key features & benefits This research supports Do I have access?

> Defines the SDV: > Global OEM activities &
Understand the Software- impacts: How Software-
Defined Vehicle, the KPIs, Defined Vehicles are changing
high-level architecture OEM businesses, as well as
and patterns, and the key their partnerships, PRODUCT PLANNERS C-SUITE
technology domains. investments, platforms and
organizations.

> Core technologies: > Supply chain activities and

Go in-depth on the impacts: How tier 1s, tier 2s
hardware and software and service providers Portal access
powering the Software- support the Software- MARKETING E N G I N E ER S
Defined Vehicle. Defined Vehicle.

Request a quote for

The Software-Defined Vehicle
July 2021 CON636-21
THE SOFTWARE-DEFINED VEHICLE
Enabling the updatable Car - Business, technology, & supply chain
 Contents Page
Introduction ≫ → Daimler ▪ Tier 2 Hardware Impacts → Tata Elxsi

→ Ford ▪ Tier 2 Software & Cloud Suppliers → Vector

→ Geely (Volvo) ▪ Tier 1 Suppliers & Technologies: → Wind River

Executive Summary ≫
→ General Motors → AISIN ▪ Open Source & Alliances:

→ Honda → Aptiv → Apollo

The Software-Defined Vehicle ≫ → Hyundai → Bosch → ASIMI

→ Jaguar Land Rover → Continental → Automotive Grade Linux

▪ Overview and KPIs
→ Mazda → DENSO → AUTOSAR
▪ High-level architecture & patterns
→ Renault-Nissan-Mitsubishi Alliance → Faurecia → Autoware
▪ Key technology domains
→ Stellantis → HARMAN → GENIVI

→ Tesla → Hyundai Mobis → SENSORIS

Core Technologies ≫ → Toyota → Lear Corporation → Yocto Project

▪ Overview → Volkswagen Group → LG Electronics ▪ Tier 2 Hardware Landscape

▪ Hardware → EV Startup Landscape → Marelli ▪ System Integration Landscape

▪ E/E & Networking → Mitsubishi Electric Contact Us ≫

▪ Operating Systems OEM Impacts ≫ → Panasonic

▪ Middleware & Communications ▪ Overview → Pioneer

▪ ADAS ▪ Business & KPI Impacts → Sumitomo Electric
▪ Connectivity & IVI ▪ Organizational Impacts → Valeo

▪ Cloud & Edge Computing ▪ Technology Impacts → ZF

▪ DevOps and OTA Software Updates ▪ Supply Chain Impacts ▪ Tier 2 Software & Cloud:

▪ Market Segmentation Impacts → Amazon (AWS, Zoox)

Global OEM Activities ≫ → BlackBerry

Overview and Timeline → Excelfore

▪ Supply Chain Impacts &
▪ Software-Defined Vehicle Maturity Index Activities ≫ → Google (Android, Waymo)

▪ OEM Groups: ▪ Supply Chain Overview → GuardKnox

→ BMW ▪ Tier 1 Impacts → Microsoft

Introduction
 Executive Summary

SDV Levels to Principles

E/E Patterns User Experience Updatability Connectivity S/W Architecture

1.0
Zonal Personalized Vehicle Software Updates 5G with Edge Edge Container Runtime

Vehicle Functional Domains Connected IVI Firmware Updates Multi-Channel

Service-Oriented
Architecture
Functional Bandwidth Smartphone Integration Phone App Updates 4G Cockpit S/W Apps
Functional
Multi-CAN Static IVI No Updates None or eCall Only Tightly Coupled

2.0
Zonal Personalized Vehicle Software Updates 5G with Edge Edge Container Runtime

Vehicle Functional Domains Connected IVI Firmware Updates Multi-Channel

Service-Oriented
Architecture
Functional Bandwidth Smartphone Integration Phone App Updates 4G Cockpit S/W Apps
Digital
Multi-CAN Static IVI No Updates None or eCall Only Tightly Coupled

3.0
Zonal Personalized Vehicle Software Updates 5G with Edge Edge Container Runtime

Vehicle Functional Domains Connected IVI Firmware Updates Multi-Channel

Service-Oriented
Architecture
Functional Bandwidth Smartphone Projection Phone App Updates 4G Cockpit S/W Apps
Updateable
Multi-CAN Static IVI No Updates None or eCall Only Tightly Coupled

4.0
Zonal Personalized Vehicle Software Updates 5G with Edge Edge Container Runtime

Vehicle Functional Domains Connected IVI Firmware Updates Multi-Channel

Service-Oriented
Architecture
Functional Bandwidth Smartphone Projection Phone App Updates 4G Cockpit S/W Apps
Software-Defined
Multi-CAN Static IVI No Updates None or eCall Only Tightly Coupled

6
6
Example slides
from the report
Please note: These slides are taken from the pre-release
report and may be updated before the final release
 Software-Defined Vehicle

The Software-Defined Vehicle abstracts hardware from software

Automakers do not manufacture their own silicon. Design Principle Impact
For any given computing module in a vehicle, a
hardware platform is sourced from a vendor that Tight Coupling Software developed as monolith,
specializes in system-on-chip components. unseparated from other functions
Updating is difficult due to
dependencies between
Software or services provided by the
components.
Many system-on-chip components have system component.
services, platforms, or APIs which are unique to
that component or manufacturer. When software Higher costs from
is written on these services, that software Hardware Hardware drivers & system services hardware complexity and
are unique to the system. fragmentation with
becomes “tightly coupled” with the hardware –
unique software for each.
that is, the software will only run on that specific
hardware platform.
Software can be updated
As automotive computing platforms become more Software developed as independent
or added more easily due
applications based on function or
capable, the introduction of hardware abstraction service.
to separation of functions
layers provides, on one side, support for by application.
hardware-specific system services, while on the
other side, these services are exposed as Loose Coupling Software can be
APIs & middleware added which
homogenous interfaces. provide hardware-agnostic developed independently
Application Application interfaces for interacting with of the specific hardware
hardware services or messaging while applications can
Software developers can then “loosely couple” Middleware & APIs with other applications. apply service-oriented
their software as applications, leveraging the architecture.
abstraction layer and other services to isolate Hardware Abstraction Layer
functionality as services while being portable to An abstraction layer provides
any hardware which supports the same Hardware services which map hardware- Reduction or elimination
abstraction layer. specific services, functions and data of hardware
to hardware-agnostic services, fragmentation due to
functions and data defined in the software incompatibility.
The transition from tight coupling to loose higher-level.
8 coupling is the ethos of the software-defined
vehicle.
8
 Software-Defined Vehicle

High-performance computers are the key to abstraction

• Applications & containers leverage services on the GPOS to
High-Performance Computer (HPC) run portable software integrated with the hardware
abstraction services offered by the GPOS or other
middleware.
Applications Containers

Real-Time • Multiple CPU clusters alongside sizable memory availability

Operating General Purpose allows for simultaneous execution of real-time and general
System (RTOS) Operating System (GPOS) purpose operating systems. The RTOS provides
deterministic computing for safety-critical functions, while
the GPOS allows deployment of more general services,
Type 1 Hypervisor features, and data processing applications.

• Type 1 hypervisor provides hardware-optimized

Non-Volatile Ethernet
virtualization services, ensuring safe operation of the RTOS
Memory
alongside GPOS guest OS(es).
CAN
Volatile
Memory
• HPCs provide a variety of physical interfaces to integrate
FlexRay both with CAN, LIN, and FlexRay sub-networks whilst
allowing for high-bandwidth communication with other
Graphics USB components via Ethernet, USB, and PCIe.
Processing
CPU Cluster for CPU Cluster for
CPU Cluster for CPU Cluster for Unit • GPUs power the processing of camera & radar data for
RTOS RTOS
RTOS GPOS (AV & IVI) PCIe ADAS/AV applications as well as power rendering for digital
cockpit interfaces.

• CPU clusters ensure redundant processing for both RTOS

and GPOS applications with separate contexts for
Connectivity deterministic and non-deterministic operations.
Infotainment/
Additional Zonal HPC(s)* Service or Smart
Digital Cockpit HPC • Multiple HPCs may be deployed to provide high availability,
Antenna
9 optimized, redundant AV services and/or specialized digital
cockpit applications.
* In zonally configured E/E architectures 9
 Core Technologies

SDVs create long-term scalability for ADAS & AV functionality

➢ Higher levels of automation create significant new hardware and software requirements for vehicles, requiring cutting edge technologies to provide the relevant input,
quickly and reliably process input data, and improve the performance of the system over time through integration with the cloud & other autonomous vehicles
➢ The operational requirements of higher levels of autonomy mandates the need to move from a strict fail-safe to a more fail-operational strategy: fault detection and
reaction needs to be controlled by independent hardware, resulting in unique AV software architecture requirements
➢ The goal of the implemented redundancies is to allow the driver (for SAE L3) to take over the driving task when required but also be able to implement a minimum risk
manoeuvre if absolutely necessary
➢ Dedicated high-performance computer systems are required to deliver real-time sensor data processing, sensor fusion and trajectory planning with the broader numbers &
types of sensors in highly autonomous vehicles, and this software requires significant integration with the cloud to be able to improve & update over time
ADAS Domain Requirements for Software-Defined Vehicles Trend
Requirement Design Impact Volume brands Leader
➢AV/ADAS controllers must be able to support Hardware & software redundancy, e.g. multiple sensing Premium brands Leader
the highest levels of safety assurance at any modalities, independent power supplies, lockstep
level of autonomy mechanisms, consensus-driven AI, etc. EV Startups

Both the hardware & software of the AV operational 1 2 3 4

➢AV/ADAS controllers must provide the highest
domain must be secured by design, leveraging best-in- Partial Redundant
levels of cybersecurity protection in the vehicle
class countermeasures to both defend and react to Distributed consolidation Consolidated HPC
to prevent threats to driver/passenger safety basic ADAS of ADAS ADA/AV ADAS/AV
security and safety threats
ECUs domain domain controllers
The vehicle should integrate reliable access to high-
➢AV/ADAS controllers must be able to support
speed, low-latency, low-cost data networks for OTA, and Relationship with other layers
new and enhanced functionality over its lifetime
the domain hardware should be considered with a multi-
through software & configuration updates
year lifespan (or mid-cycle upgrade) strategy OTA AV S/W Updates Configurations

➢AV/ADAS controllers must be able to support ADAS/AV high-performance computers should allow for Cloud & Edge Data Processing V2X Local/Maps
dynamic, localized applications to support data edge-oriented application runtimes which can be used to ADAS/AV Domain
processing & functional validation rapidly develop & deploy data cost-efficient functions
Middleware Application Runtime Service Integration
➢AV/ADAS controllers must be capable of High-performance computers used for AV/ADAS systems
ingesting & processing high-bandwidth camera should be equipped with specialized graphics processing OS/Hardware RTOS GPOS (Apps) GPU Acceleration
inputs in real-time and artificial intelligence capabilities E/E Gigabit Ethernet

Middleware and Connectivity & Cloud & Edge

Hardware E/E Architecture Operating System ADAS DevOps & OTA
10 Communications Infotainment Computing

10
 OEM Activities

Ford has jumped from laggard to near-leader in software in 5 years

OEM General Jaguar Land Renault-Nissan-
BMW Daimler Ford GAC Geely/Volvo HiPhi Honda Hyundai Leading Ideal Mazda NIO SAIC Stellantis Tesla Toyota Volkswagen Xpeng
Group Motors Rover Mitsubishi

Key Messages SDV Maturity Index

➢ Ford has completely overhauled its infotainment and E/E
platforms as it shifts its portfolio to include a high EV mix 1.0 2.0 3.0 4.0
➢ Most ECUs updateable ➢ Android Automotive
➢ Ford is the first manufacturer to offer over-the-air software Key Achievements: ➢ In-house cloud s/w Roadmap: ➢ Adaptive AUTOSAR
updates for almost all ECUs in its F-150 truck series ➢ Google data partnership ➢ Some level of ECU consolidation

➢ Ford’s cloud strategy, centered around Ford Smart Mobility, pairs Functional Digital Updateable Software-Defined
with its new FNV E/E to create a strong volume OEM technology
stack, which also includes co-investments with Volkswagen

Business Model/Supply Chain Insights Technology & Platform Insights In Market Announced R&D

As Ford targets 40% of its sales by 2030 to be EVs, it has

rapidly evolved its technology development strategy to OTA Updates via “Power Up” OTA Software
EV shift offer significant in-house capability. Connectivity Embedded 4G Updates for Full Vehicle
underpins tech
strategy Ford Smart Mobility manages cloud & MaaS development,
while product engineering manages in-vehicle software OTA Live Mapping Google Services
development Infotainment SYNC 4 SYNC (2023)
BlackBerry QNX Android Automotive OS
Organization Insights OEM Subsidiary Supplier

Driver Mobileye DAT Adaptive

✓ Ford Smart Mobility acts ADAS ArgoAI
Ford Motor Company as a subsidiary and
Assist AUTOSAR Classic 2.X AUTOSAR*

manages its cloud

portfolio No Middleware Adaptive AUTOSAR (projected)
✓ Team Upshift is a co- OS &
Smart Mobility staffed team from Ford Middleware Linux AUTOSAR
Classic (Yocto) Classic AUTOSAR
BlackBerry QNX Classic AUTOSAR Android OS
LLC Team
& Google using Google’s
cloud platform for data
Upshift Single Gateway Fully Networked Vehicle (FNV-2)
analytics & services E/E Multi-CAN, ADAS Flexray TBD
(Google/ ✓ Ford’s in-vehicle
Ford) software engineering is
Autonomic Ford primarily managed in-
LLC Pass house via product SYNC 4 IVI Controller Microcontroller
Product Eng. Hardware No Data Available
engineering (2x power of SYNC 3) ECUs
11
* Based on analysis of open job postings 11
 Supply Chain

The biggest suppliers are adopting the Tier 0.5 model

While other, specialized companies have existed throughout the automotive hardware & software supply chain, Tier 1s have traditionally acted as the central hub for aggregating supplied products and
technologies into a usable component. Some of the biggest Tier 1s are now evolving their business model to act more like a “partner” to OEMs – a Tier 0.5 – while other specialized suppliers and OEMs
themselves replace or augment services traditionally provided by Tier 1s for highly differentiating components and associated software.

Specialized
The Tier 1 Model Suppliers
Description Example
The traditional supplier model relies on Tier 1 Design
suppliers to manage the entire lifecycle of the high
tech component which it is manufacturing for the Complete vehicle
OEM. White-Label
design, development
OEM
& manufacturing

OEM Supplier
Engineering Custom design &
Develop Management manufacturing for
Update
Services specialized hardware

Low-Cost Commodity hardware

Design Supplier manufacturing

Supplier
Suppler builds both
Manufacture
Vertically automotive
Integrated components &
Supplier underlying
silicon/SoC

Update Develop
Contract
Software
Supplier The Tier 0.5 Model Engineering
development &
engineering
When designing and building highly differentiating components, Services
resources
OEMs will source partners – Tier 0.5s – rather that just
“suppliers” to facilitate co-creation.
--- Non-differentiating
Software
The Tier 0.5 model also gives rise to specialists along the supply software that
Manufacture chain, provided either by the supplier or selected by the OEM to
Products &
accelerates time to
Platforms
work in cooperation. market
12
12
 Supply Chain ⅼ Tier 1s ⅼ

Bosch is well-positioned as full-stack SDV technology supplier

Hitachi Hyundai Mitsubishi Sumitomo
Tier 1 AISIN Aptiv Bosch Continental DENSO Faurecia Foxconn HARMAN Lear LG Electronics Magna Marelli Panasonic Valeo Veoneer ZF
Astemo Mobis Electric Electric

Key Messages Strategic Direction

Bosch is a titan in the race for the software-defined vehicle, offering
both products and services in the vehicle and in the cloud to enable Products & Services Technology Domains
development & integration of new E/E and software Infotainment &
Cloud SaaS
Connectivity
While Bosch offers a wide variety of automotive solutions, its
strategic direction is clearly aligned to CASE and SDV, as evidenced
by the consolidation of its 17,000 in-vehicle software and platform
experts into its Cross-Domain Computing Solutions organization Component System Non-Software Autonomous
Manufacturing Integration
News & Insights Domains Driving

Headline Insight
Bosch’s integration of its OTA & in-vehicle software solutions with
Bosch/Microsoft SDV
Microsoft’s suite of Azure development, hosting, and deployment tools
Platform In-Vehicle
foreshadows the future of software deployment for SDVs Development Electrification Shared Mobility
Software
Tools
Bosch is establishing itself as a leader in software-defined vehicle Products
Bosch wins orders
computing technology through multiple orders for billions of euros IoT Cloud offers cross-vertical Bosch offers full-stack
worth billions for Infotainment &
worth of vehicle computers which underscores Bosch’s vertically Cloud SaaS device management services; infotainment & connectivity
vehicle computers
integrated SDV value proposition to OEMs Connectivity
plus partnership with Microsoft hardware & software solutions
SDV Strengths & Weaknesses The foundation of Bosch’s Extensive components,
System Autonomous
Strengths Weaknesses overall automotive footprint & platforms, and investments
Integration Driving
offering for AV/ADAS
Consolidated Organization – Mirroring its Automotive Insider – Bosch is a stalwart
customers, Bosch has consolidated its in- of the automotive industry, but this can ETAS, Escrypt, and Bosch all
Bosch Connected Mobility
vehicle computing and software expertise work against them in the SDV domain, Development offer a fragmented portfolio of
Shared Mobility offers some MaaS-centric
into a single organization – Cross-Domain where many OEMs are looking to the Tools tools, but not specifically SDV-
solutions, but not core focus
Computing Solutions – which gives Bosch semiconductor and consumer electronics oriented
a global, scalable organizational platform industries to help modernize and
In-Vehicle Bosch’s portfolio is less product- Bosch provides solutions in all
from which to build SDV-oriented accelerate their processes and platforms
Software centric, but some AUTOSAR- Electrification powertrain sectors, as well as
products and services
Too Big? – Bosch’s significant engineering Products related products BEV drive systems
Embedded Security – Bosch’s key footprint and experience define its SDV
software subsidiaries (ETAS and Escrypt) value proposition, but this can also lead to Offered for all major software- Bosch offers a wide variety of
offer an embedded development and a more expensive portfolio of products Component driven components, including Non-Software vehicle components
cybersecurity pedigree that enhances the and services which may not be as Manufacturing digital cockpit, HPCs and E/E, Domains throughout almost every
13 Bosch’s credibility in providing competitive as modular, ”slimmer” zonal controllers, ADAS, etc. domain in the vehicle
“automotive-grade” SDV-oriented services solutions from specialists
13
 Supply Chain ⅼ Open Source and Standards ⅼ

AUTOSAR Adaptive Platform early leader for SOA, ADAS software

Organization Apollo ASIMI AGL AUTOSAR Autoware GENIVI SENSORIS Yocto Project

Maturity
Key Messages Exploratory Incubation First Output Limited Adoption Widespread Adoption
➢ AUTOSAR is a long-standing industry alliance focused on the development of open Organization Type
standards for ECUs and in-vehicle software applications, from which suppliers can
develop software which implements the standard, and OEMs (or suppliers) can Alliance Consortium Foundation Undefined
develop application software which is guaranteed to run on AUTOSAR-compliant
solutions Output(s)
➢ AUTOSAR Classic is a full RTOS specification for microcontroller ECUs, while Name Type Description
AUTOSAR’s other main output – Adaptive Platform – is a novel application
middleware standard intended for high-performance computers Standard for Classic, including basic software (BSW) and
Classic Platform Standard runtime environment (RTE)
News & Insights Standard for implementing the Adaptive Runtime for
Adaptive Platform Standard Applications (ARA), which contains a variety of components
Headline Insight for managing embedded software applications
AUTOSAR continues to iterate on both Classic and Standard for shared components between Classic and
AUTOSAR release R20- Adaptive standards to ensure viability in modern vehicle Foundation Standard Adaptive to ensure interoperability between the platforms
11 published software architectures. Adaptive is still relatively young
but sufficiently mature for usage in production Acceptance Tests for Specification of tests which verify compliance with AUTOSAR
Specification
Classic Platform Classic standards
Members/Contributors
Specification of domain-specific interfaces i.e. powertrain,
Application Interfaces Specification body and comfort, chassis, etc.

Core Partners
Strengths Weaknesses
➢ Uniqueness: Adaptive platform is not only ➢ Emerging Applications: The industry is still
Strategic first-to-market for a much-needed capability, working out the best way to implement
Partners it is also the most mature solution, enjoying hardware abstraction in HPCs, and Adaptive
Premium 60 companies, including Aptiv, BlackBerry, Baidu, Honda, implementation by many suppliers & OEMs may not end up failing to meet many OEM
Partners Hyundai and others requirements
➢ Heritage: AUTOSAR Classic is nearly
ubiquitous in traditional ECU development; ➢ Cloud Integration: Adaptive platform
Development 59 companies, including TTTech, OpenSynergy, Excelfore, this builds the support framework & supports connectivity, but there is no specific
Partners Airbiquity and others credibility of Adaptive, with many of the standard or platform for holistic management
OEMs who would need such a solution of software and configuration – a key area of
14 Associate 147 companies, including other OEMs, suppliers and service
already supporting the Alliance R&D for cloud vendors, OTA solution
Partners providers
providers, and OEMs
14
Request the price
 Contact Us

Contact SBD Automotive

Do you have any questions?

If you have any questions or feedback about this
research report or SBD Automotive’s consulting services,
you can email us at [email protected] or discuss
with your local account manager below.

[email protected]

Book a meeting USA UK Germany India China Japan

Garren Carr Luigi Bisbiglia SBD China Sales Team

North America South Europe & RoW China
[email protected] [email protected] [email protected]
+1 734 619 7969 +44 1908 305102 +86 18516653761

Alessio Ballatore Andrea Sroczynski SBD Japan Sales Team

West Europe Germany, North & East Europe Japan, South Korea & Australia
[email protected] [email protected] [email protected]
16 +44 74 71 03 86 22 +49 211 9753153-1 +81 52 253 6201
16