Vehicle E/E architecture: from ECUs to the zonal architecture
The move from a distributed structure, with one ECU per function, to domain controllers, and then to a zonal architecture with a central computer.
Distributed structure
Windows, seats, engine and brakes each have their own ECU, connected by CAN and LIN. A single car came to have 70 to 100 ECUs and tens of kilograms of wiring.
Domain architecture
Functions are grouped into areas (domains), each handled by a powerful domain controller.
| Domain | Examples |
|---|---|
| Powertrain | Engine, motor, transmission, battery |
| Chassis | Brakes, steering, suspension |
| Body | Doors, lighting, climate control |
| Infotainment | Displays, navigation |
| ADAS | Cameras, radar, automated driving |
Zonal architecture
A zone controller is placed for each location in the car (front left, rear right …) and connects the nearby sensors and actuators. The zone controllers connect to a central computer over automotive Ethernet, and the function software runs centrally. Wiring is greatly reduced and adding functions by OTA becomes easier (the software-defined vehicle, SDV).
What it means for embedded developers
- Zone controllers: still MCUs, real-time, power distribution and I/O
- Central computer: high-performance SoC, hypervisor, a mix of Linux and RTOS
- Communication: automotive Ethernet and service-oriented communication such as SOME/IP, in addition to CAN/LIN