Zonal architecture organizes vehicle hardware by physical zone instead of by function. Each zonal controller owns the sensors, actuators and power in its region of the car, then talks to central compute over a high-speed Ethernet backbone.
Domain and centralized architectures group electronics by function. Zonal architecture groups them by location: front-left, rear-right, and so on. Local I/O terminates at the nearest zonal controller rather than running all the way to a central box, which dramatically shortens the wiring harness and reduces weight, cost and assembly time.
Zonal controllers double as power distribution nodes. Moving from centralized fuse boxes to zonal smart fusing lets software control loads, detect faults locally and reconfigure power paths. This is a key enabler for redundancy in automated driving, where a single power or network fault must not disable a safety function.
Zones connect to central compute over automotive Ethernet, often with time-sensitive networking for deterministic delivery. The backbone carries service-oriented traffic (SOME/IP, DDS) alongside best-effort data, so the gateway and switches must police bandwidth, priority and timing to keep safety-relevant streams bounded.
Zonal and centralized designs are complementary, not competing. Zonal controllers solve the wiring and I/O problem close to the hardware; centralized high-performance computers solve the application and AI compute problem. Together they form the dominant target architecture for software-defined vehicles.