Central Compute and Control

VCU · DCU · ZCU · central compute

EVs are replacing dozens of single-function controllers with a few computers. The hard part is not the chips but deciding what runs where and how it fails safely.

Diagram of the control hierarchy in a zonal EV. At the top, central compute built from SoCs plus a safety microcontroller, such as Nvidia Orin and Thor, Tesla AI4 and Horizon Journey 6. Below it: the vehicle control unit (torque, modes), power control unit (power flow), domain controllers (cockpit, ADAS) and safety monitors (watchdog, backup). Below those, zonal controllers at the front, left and right, and rear bridge CAN and LIN to Ethernet. At the bottom are microcontrollers, sensors, actuators and smart power switches. Fewer, larger computers sit at the top, zonal I/O at the edge, and safety monitors beside every critical path. CONTROL HIERARCHY IN A ZONAL EV Central compute SoCs + safety MCU: Nvidia, Tesla, Horizon VCU torque, modes PCU power flow Domain ctrl cockpit, ADAS Safety watchdog, backup ZCU front CAN, LIN to Ethernet ZCU left / right CAN, LIN to Ethernet ZCU rear CAN, LIN to Ethernet MCUs, sensors, actuators, smart power switches Few big computers on top, zonal I/O at the edge, safety alongside.
Rivian Gen 2 ECUs
17 to 7
Tesla compute
AI4, AI5 next
Chinese ADAS SoC leader
Horizon Robotics
Safety standard
ISO 26262
Hub
Supply Chain

Finding

Control is consolidating from many ECUs into a hierarchy of central compute, domain or zonal controllers and safety MCUs, and the partitioning between them decides cost, update speed and fault behavior

A legacy premium car carries 100 or more ECUs, each owned by a different supplier with its own software. Zonal EVs collapse them: Rivian's Gen 2 R1 went from 17 controllers to seven, and Tesla, XPeng, Li Auto and NIO run most vehicle logic on one or two central computers above three or four zonal controllers. The central computer is built from high-performance SoCs - Nvidia Orin and Thor, Qualcomm Snapdragon Ride, Tesla's in-house AI4, Horizon Robotics Journey 6, Huawei's Ascend-based MDC, NIO's Shenji NX9031 and XPeng's Turing - paired with safety microcontrollers from Infineon, NXP, Renesas or ST.

Centralization concentrates risk: a fault in a central computer can take out many functions at once, so the architecture needs redundant power rails, independent safety monitors, failover network paths and degraded modes that still let the vehicle stop safely. ISO 26262 and the SOTIF standard (ISO 21448) govern that design work. Tesla's next chip, AI5, is built by TSMC in Arizona and by Samsung at its Taylor, Texas fab, which is also contracted for AI6.

The supply base splits by layer. Western and Japanese makers - Infineon, NXP, Renesas, ST, TI - dominate microcontrollers and safety chips. Nvidia, Qualcomm and Mobileye lead central compute outside China, while Horizon Robotics, Huawei, Black Sesame and SemiDrive are taking share in Chinese EVs and BYD runs its God's Eye system on Horizon and Nvidia tiers.

Layers

Control layers

A vehicle can have all of these at once; the design work is deciding which functions sit at which layer.

Compute and control layers
LayerRoleBest used forAvoidSuppliers
Vehicle control unit (VCU)Supervisory vehicle logic: drive state, torque requests, regen blending, modesCross-domain coordinationBecoming a dumping ground for low-level controlUAES, Bosch, ZF, Aumovio, Hyundai Mobis; in-house at Tesla and BYD
Power control unit (PCU)Power flow, limits and protection across inverter, charger and DC-DCElectrical power behaviorOwning non-power vehicle logicDenso, Bosch, BYD, Inovance, Tesla in-house
Domain control units (DCU)Body, chassis, cockpit or ADAS domain logicSpecialized domain controlLegacy fragmentation under a new nameBosch, Aptiv, Desay SV, Visteon, Neusoft Reach, iMotion
Zonal control units (ZCU)Local I/O, power distribution and CAN/LIN-to-Ethernet bridging by vehicle regionPhysical I/O concentrationHigh-level decision-makingAptiv, Bosch, Lear, Aumovio, Hirain; OEM in-house
Central computeShared software services, ADAS, cockpit and orchestrationCompute-heavy and cross-domain workloadsIgnoring thermal, safety or isolation limitsNvidia, Qualcomm, Mobileye, Tesla, Horizon Robotics, Huawei, Black Sesame
Safety and redundancyWatchdogs, lockstep cores, redundant power and links, safe-state managersControlled operation under faultsBeing added lateInfineon, NXP, Renesas, ST, TI

Shift

From distributed ECUs to centralized architecture

Integration quality now matters more than ECU count.

Legacy vs SDV control architecture
Legacy modelSDV modelImplication
Many single-function ECUs from many suppliersA few powerful controllers with broader rolesSoftware integration matters more than module sourcing
Function-based wiring and control islandsZonal aggregation under central computeLess harness mass and complexity
Updates limited by fragmented ownershipShared software layers updated over the airVehicle improves after sale
Fault handling local to one controllerSystem-level fault management and fail-operational designRedundancy becomes core architecture

Supply chain

Compute and control supply chain

Value is moving from individual controllers to platforms that combine silicon, software and lifecycle support.

Compute and control supply chain
Building blockUS, Europe, Japan, KoreaChina
Microcontrollers and safety MCUsInfineon AURIX, NXP S32, Renesas RH850, ST Stellar, TI, MicrochipBYD Semiconductor, SemiDrive, Flagchip, Chipways, GigaDevice, AutoChips
Central compute SoCsNvidia Orin and Thor, Qualcomm Snapdragon Ride, Mobileye EyeQ, Tesla AI4 and AI5Horizon Robotics Journey, Huawei MDC, Black Sesame, NIO Shenji, XPeng Turing
Power management and smart switchesInfineon, NXP, TI, ST, ADI, onsemiNovosense, SG Micro, Joulwatt
MemoryMicron, Samsung, SK hynixCXMT, YMTC (limited automotive qualification)
FoundryTSMC, Samsung, GlobalFoundries, IntelSMIC, Hua Hong
Embedded OS and middlewareQNX (BlackBerry), Vector, Elektrobit, Linux, AUTOSARHuawei HarmonyOS and AOS, Neusoft Reach, in-house OEM stacks

Sources

Sources and scope

Scope
Central Compute and Control
Sources
Rivian (Gen 2, 2024); ISO 26262; ISO 21448; Tesla and Samsung disclosures (2025); company disclosures
Updated
October 2026