Zonal architecture
An E/E architecture that organizes vehicle electronics by physical zone, with zone controllers aggregating local I/O and central computers running the logic.
A zonal architecture organizes a vehicle’s electronics by physical location rather than by function. Zone controllers — typically two to six, placed front/rear or by corner — aggregate local sensors, actuators and power distribution, while the actual application logic runs on one or more central computers.
This contrasts with the domain architecture, where electronics are grouped by function (powertrain, body, infotainment) regardless of where components sit in the car.
The main gains are wiring and scalability. Because devices connect to the nearest zone controller instead of a function-specific ECU across the car, the wiring harness gets shorter, lighter and cheaper to assemble. Software becomes largely independent of vehicle topology, which simplifies reuse across models. The cost is complexity elsewhere: zonal designs depend on high-bandwidth automotive Ethernet backbones, time-sensitive networking, and rigorous separation of safety-critical and non-critical traffic on shared infrastructure.
Related: Central compute / HPC · Domain controller · E/E architecture