Skip to content

Foundations

How vehicle electronics evolved

Distributed, then domain, then zonal, then central — four architectures, what each solved, what each broke, and how to tell which one a programme is actually on.

Beginner6 minArchitecture · E/E · Zonal

The phrase you will hear is E/E architecture — electrical and electronic architecture. It means how the computers in a vehicle are organised and wired.

It has been through four generations. Knowing which one a programme is on tells you more about what is possible than any amount of feature discussion.

Fewer, more powerful computers — the physical change behind SDVDistributedone ECU per function~1990s–2010sDomaingrouped by function~2015+Zonalgrouped by locationSDV eraCentralone computer, zonal I/Oemergingwiring shrinks · compute concentrates · functions become software
Four generations of vehicle electronicsEach square is a computer. The trend is fewer, more capable ones — and the wiring shrinks with them.

Generation 1 — Distributed#

One per function. A door module, a seat module, a lighting module, an engine controller. Each does one job and does it reliably.

They talk over , broadcasting values that anything interested can hear.

What it solved. Independence. A supplier delivered a complete, testable component. A fault in one thing did not affect another. Adding a function meant adding a box — simple to plan and simple to price.

What it broke. Everything, once the count grew.

Generation 2 — Domain#

Group ECUs by what they do: a powertrain domain, a body domain, a chassis domain, an infotainment domain. Each has a domain controller; the small ECUs under it get simpler.

What it solved. Fewer independent parties per feature. A body feature is now mostly one supplier's problem.

What it broke. The wiring, mostly. A body domain controller still needs a wire to every lamp in the vehicle, so the harness barely shrank. And features increasingly crossed domains — a "welcome" sequence touches body, comfort and infotainment at once, which the domain split makes awkward rather than easier.

Generation 3 — Zonal#

The insight is to stop grouping by function and start grouping by location.

puts a controller in each corner of the vehicle. It connects to whatever is physically near it — the lamps, the door motor, the sensors in that corner — regardless of what function they belong to. One high-speed cable links it back to the centre.

Zones own the wiring near them; the centre owns the softwareCentral computecockpit · ADAS · vehiclefunctions run hereupdatable over the airFront-left zonelights · door · mirrorFront-right zonelights · door · sensorsRear-left zonedoor · seat · bootRear-right zonedoor · seat · lampsAutomotive Ethernetshort local wiring to sensors and actuators · one high-speed link back to the centre
Zonal wiringEach zone owns short local wiring to whatever is nearby. One fast link carries everything back. The intelligence is not in the zone — it is in the centre.

Generation 4 — Central compute#

The endpoint: a small number of powerful computers running nearly all vehicle functions, with zones acting as little more than intelligent connectors.

is where becomes fully realisable. When a function is software on a shared computer, it can be updated, replaced, or added without touching hardware.

What it solves. Everything the earlier generations struggled with: integration, updatability, feature addition, wiring.

What it breaks. Isolation. A hundred separate boxes could not interfere with each other; software sharing a processor absolutely can.

Where real programmes actually are#

What each generation means for software#

GenerationAdding a feature meansUpdating means
DistributedA new ECU, new wiring, new supplierReflashing an ECU in a workshop
DomainChanging a domain controller, coordinating below itReflashing that domain
ZonalSoftware on central compute, using existing zone I/OAn over-the-air update
CentralSoftware, deployed like any other softwareContinuous delivery

Next#

An honest look at how far the industry has actually got.

References & further reading

Code links target the main branch on cs.android.com. AOSP moves — if a path 404s, search the symbol instead.