Q
Q

Q

[user_favorites]

?

It seems that you entered incorrect user credentials. Please enter your email and password again.

[favorite_button]

The change in the vehicle E/E-Architectures

Summary

The automotive industry is still largely at the beginning of its journey to reshape how the electrical and electronic (E/E) architecture of vehicles  will be implemented.
The classic decentralized approach to the automotive E/E architecture no longer meets the needs of today’s, increasing electrification of vehicle. More new functions led to more ECU.
With Controller Area Network (CAN), Local Interconnect Network (LIN), Media Oriented Systems Transport (MOST), and FlexRay, each domain, from infotainment and chassis to powertrain and body and comfort, were implemented so far with an appropriately automotive...

Like what you see?

Then log-in to unlock all the content or become a member of Carmunication today!

The automotive industry is still largely at the beginning of its journey to reshape how the electrical and electronic (E/E) architecture of vehicles  will be implemented.
The classic decentralized approach to the automotive E/E architecture no longer meets the needs of today’s, increasing electrification of vehicle. More new functions led to more ECU.
With Controller Area Network (CAN), Local Interconnect Network (LIN), Media Oriented Systems Transport (MOST), and FlexRay, each domain, from infotainment and chassis to powertrain and body and comfort, were implemented so far with an appropriately automotive networking technology.

From Decentralized to Zonal Control
Instead, the in-vehicle networks are being upgraded to support simpler connectivity with sufficient bandwidth to allow a small number of zonal, central controllers and high performance computers to handle multiple functions, coupled with a reduced number of classic ECUs.

 

Details

From Decentralized to Zonal Control

History

Vehicles have gone from being mechanical marvels to software-defined rolling computers. The automotive industry is still largely at the beginning of its journey to reshape how the electrical and electronic (E/E) architecture of vehicles will be implemented. Electronic control units (ECU) handling individual functions within the vehicle have long been the approach to electrifying previously mechanical functions. New functions led to more ECUs. As a result, even a basic vehicle model contains around 70 ECUs, with premium models featuring well over 100. With the introduction of connectivity such as Controller Area Network (CAN), Local Interconnect Network (LIN), Media Oriented Systems Transport (MOST), and FlexRay, each domain, from infotainment and chassis to powertrain and body and comfort, were provided with an appropriately dimensioned automotive networking technology (Figure 1). Each ensured enough bandwidth and sufficient functional safety at an acceptable price point, linked together in a decentralized architecture. As a result, the wiring harness has become the third heaviest and third most expensive component in the modern vehicle and the addition of new, differentiating features often demands yet another connectivity technology. The classic decentralized approach to the automotive E/E architecture no longer meets the needs of today’s, increasing electrification of vehicle.
However, the vehicle original equipment manufacturers (OEM) look to differentiate their products add more advanced safety features (ADAS), it is obvious the old one-feature-per-box approach is no longer tenable.

Centralized Zone-ECU
Instead, the in-vehicle networks are being upgraded to support simpler connectivity with sufficient bandwidth to allow a small number of zonal, central controllers and high performance computers to handle multiple functions, coupled with a reduced number of classic ECUs. With the use of multicore system-on-chip (SoC) processors (well established in the industry), the challenge is to ensure that these devices have the connectivity needed by these new zonal controller-based E/E architectures.
The approach being taken is toward a zonal architecture (Figure 2). Each vehicle is equipped with one or two (for backup reasons) high-performance computers (HPC) and several powerful zone ECUs. These connect to a high-speed network tuned to the needs of automotive and based upon the well-established and understood Ethernet technology.
Functionality, e.g. the control of Matrix-LED Headlights, is implemented in software. The inputs required, from cameras to steering wheel angle, are fed from sensors around the vehicle to the zone controller hosting the software function Adaptive Driving Beam (ADB). From here, commands are issued to each headlamp cluster ECU. Should the software algorithm be improved, or a bug be found, this software function can be updated via an over-the-air (OTA) update.

Ethernet Tuned to the Needs of Automotive
Ethernet is a well-established networking technology that has continuously been updated and revised to meet the demands of IT systems and Internet connectivity. However, this IEEE standard technology is primarily focused on reliable data delivery and less on end-to-end delivery timing requirements. New extensions to the Ethernet standard have been developed to ensure bandwidth can be reserved for video and audio data and to guarantee that connected nodes can operate synchronously.

 

 

Sources

  • Toshiba study: Ethernet-based high-speed communication for Zonal Architectures and Telematics systems
  • KEYSIGHT: Advancing the autonomous vehicle ecosystem
  • shutterstock
Click to rate this post!
[Total: 1 Average: 5]

Written by Carmupedia Editorial Office

You might also be interested in

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Q

Please rate this article

Let us know if you like this article by leaving a rating. Don't worry, it's super easy.

Click to rate this post!
[Total: 1 Average: 5]

Placeholder
Manage my notifications

Your member panel

From here you have full control over your profile

My bookmarks

[user_favorites]

[clear_favorites_button]

Are you missing something here?

Feedback
Q