没有合适的资源?快使用搜索试试~ 我知道了~
安永:软件革命重新定义汽车行业.pdf
1.该资源内容由用户上传,如若侵权请联系客服进行举报
2.虚拟产品一经售出概不退款(资源遇到问题,请及时私信上传者)
2.虚拟产品一经售出概不退款(资源遇到问题,请及时私信上传者)
版权申诉
0 下载量 27 浏览量
2023-11-29
22:20:56
上传
评论
收藏 1.49MB PDF 举报
温馨提示
试读
22页
安永:软件革命重新定义汽车行业.pdf
资源推荐
资源详情
资源评论
2
The software-driven revolution redening the automotive industry
Table of
content
1. Foreword
03
6. Development approach
12
3. Introduction
04
8. The path forward: EY-P’s Outlook
14
2. Executive Summary
03
7. Shifting value chain
13
4. Current challenges
05
9. Conclusion
16
5. Shifting technology landscape
07
10. Glossary
19
3
The software-driven revolution redening the automotive industry
Through this paper, EY-Parthenon’s Future Mobility team aims to
analyze the disruption caused by the increasing importance of
software in the automotive. We begin by looking at the existing
challenges with the current approach to vehicle development and
the limitations it places on software to grow. We also analyzed
the key upcoming technology trends to combat the existing
challenges and how they are giving rise to a new approach for
developing SDVs. Lastly, we look at how the new development
approach is redening the existing automotive value chain and
what this means for existing and emerging players in the future.
Foreword
Executive Summary
1
2
Demand for advanced automotive technologies like ADAS,
electrication & connectivity are highlighting the importance of
software in automotive and are characterized by independent
development of software & hardware. Software-Dened Vehicles
are reshaping the automotive industry by enabling increased
exibility, customization, and remote upgradeability. This is
leading to new business models, such as subscription-based
vehicle ownership, over-the-air software updates and enabling
OEMS to offer new services to customers. However, despite all
the inherit advantages, software dened vehicles are marred
by challenges such as changes in vehicle E/E architecture,
lack of independent software development for distributed
E/E architectures, lack of seamless connectivity options and
cybersecurity concerns. OEMs have addressed these concerns
by focusing on developing dedicated software platforms
independent of hardware, consolidating the E/E architecture,
and leveraging high-speed 5G connectivity to enhance the V2X
connectivity. Overall, software-dened vehicles are disrupting
the automotive industry by changing the way cars are designed,
manufactured, and used. Traditional OEM-Supplier dynamics are
changing; Tier 2s and pure play software players are expanding
their market position and are utilizing this opportunity to start
engaging with the OEMs directly, by-passing traditional Tier1s.
Through this paper, EY-P explores this changing automotive
landscape and proposes a 3-pronged approach (Prioritizing
software opportunities, building software capabilities, evaluating
partnerships / acquisitions) to enable a smoother transition to
the software domain.
4
The software-driven revolution redening the automotive industry
Introduction
3
Automotive consumers have increasingly come to expect a
standard of convenience from their vehicles that they get
from their smart phones, tablets, and appliances. Demand for
advanced technology features, such as connectivity, driver
assistance/autonomous-driving and safety, parallelly with market
trends, such as vehicle electrication and increased efciency
norms, are placing an ever-increasing emphasis on the role that
software plays in a vehicle.
Traditional vehicle development approaches of developing
hardware and software in unison can no longer keep up with
A key enabler for SDVs is Over the Air (OTA) updates. Besides
security patches and incremental software performance
improvements, OTA updates carry the potential to massively
cut down costs and realize value from software for OEMs with
the ability to roll out entirely upgraded features to customers
without massive rollbacks or developing new vehicle programs.
Players from markets like the US, EU and China are currently
trendsetters and are leading the way in software development
for various safety, convenience and performance related aspects
of a vehicle. The US, with an extensive talent pool of software
developers from Silicon Valley, has radically changed the way
software for automotive is developed. New age automotive
companies / Start-ups in this region have pioneered our
understanding of SDVs today. They have adopted a “Software
the exponentially rising complexity of software needed to meet
evolving consumer and market demands.
Enter Software-Dened Vehicles (SDVs). SDVs are characterized
by the radically different approach of automotive development,
where software is separated from the hardware it runs on.
Like smart phones and computers of today, SDVs aim to utilize
standardized software platforms, running on next generation
consolidated and centralized computing hardware, with a focus
on high-speed connectivity to the cloud, other vehicles and smart
infrastructure.
Figure 1 High level architecture for a Software Dened Vehicle
Application software: Front-end software components responsible for
executing functional logic of that application. Development is completely
abstracted away from hardware functions, aiding in scalability and ease
of deployment across various vehicle programs and types
Software platform: Unified software platform, responsible for
centralization of functions across various vehicle domains. A software
platform reduces development efforts, aids scalability, enables easier
implementation of OTA updates and cloud connectivity
Centralized High-Performance Compute (HPC) platform:
Centralized processor that controls functions by connecting to sensors
and controllers across the vehicle, with assistance from few zone
controllers that take care of simpler computational tasks. Greatly reduces
the number of ECUs required in a vehicle and allows for a standardized
development environment, reducing development efforts
Software-Defined
Application software: Front-end software components responsible for
executing functional logic of that application. Development is completely
abstracted away from hardware functions, aiding in scalability and ease of
deployment across various vehicle programs and types
Software platform: Unified software platform, responsible for
centralization of functions across various vehicle domains. A software
platform reduces development efforts, aids scalability, enables easier
implementation of OTA updates and cloud connectivity
Centralized High-Performance Compute (HPC) platform: Centralized
processor that controls functions by connecting to sensors and controllers
across the vehicle, with assistance from few zone controllers that take care
of simpler computational tasks. Greatly reduces the number of ECUs
required in a vehicle and allows for a standardized development
environment, reducing development efforts
High-Speed 5G
connectivity
Vehicle Region Domain Controller
Cloud
connectivity
Software-Defined
Vehicle
First” approach where the vehicle and all the hardware in it is
centered around a centralized software platform.
The transition from current vehicle architecture to a software
driven one is not a straightforward approach. OEMs are racing
to achieve a fully software driven vehicle. However, this entails a
ground-up transformation of vehicle architecture, development
methodologies, and business models. There are several pathways
that can be taken by leveraging different technologies and
development approaches to cater to specic market needs. The
transition is therefore disrupting the traditional automotive value
chain, with entry of newer players, such as pure play software
giants, redened relations between traditional players and
repositioning of suppliers across the value chain.
5
The software-driven revolution redening the automotive industry
Current challenges
4
One of the major challenges facing the automotive industry
today is keeping up with the upcoming trends of Connectivity,
Autonomy, Shared and Electrication (CASE) for automobiles.
Advancements in these areas require signicant boosts in
on-board processing, integration of components across the
vehicle, and the need for broader connectivity. However, given
how vehicles are developed today, moving toward a software-
dened future presents signicant challenges. Currently, most
OEMs are observing relatively lower than expected returns on
their investments toward developing the next generation of
automotive software platforms. Certain factors, highlighted
below, are responsible for this trend:
This establishes the need for hundreds of ECUs in vehicles today, communicating through a relatively low speed communication
protocol. Having a distributed approach creates one of the biggest challenges for the development of the next generation of
automotive software.
• • Low compatibility with a centralized software platform: Due to their distributed nature, architectures like this have very low
compatibility with centralized software platforms, like those found in modern consumer electronics, such as mobile phones and
computers.
• • High development effort: The development effort for a distributed architecture is inherently high, as each ECU might have its own
development environment and operating systems.
• • Lack of scalability: With a distributed approach and the lack of a centralized software platform, it becomes difcult to scale the
software products across multiple vehicle programs and variants.
The current distributed Electrical and Electronic (E/E) vehicle
architecture means that for each specic feature, there might
be several Electronic Control Units (ECUs). These ECUs contain
a monolithic software stack as seen below (gure 2) and
communicate with each other over the Communication Area
Network (CAN) bus.
Vehicle E/E architecture
Contains logic which dictates what the hardware will do based on predened condions
Abstracts soware based applicaon layer from the hardware-oriented layers below
Contains the operang system responsible for controlling the computaonal hardware
Hardware components that work based on the logic dened in the applicaon layer
Contains logic which dictates what the hardware will do based on predened conditions
Abstracts software based application layer from the hardware-oriented layers below
Contains the operating system responsible for controlling the computational hardware
Hardware components that work based on the logic dened in the application layer
Figure 2 Monolithic Embedded Software Stack of a single ECU
剩余21页未读,继续阅读
资源评论
T0620514
- 粉丝: 1122
- 资源: 1万+
下载权益
C知道特权
VIP文章
课程特权
开通VIP
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功