Finding
The move from distributed ECUs to zonal and central compute shifts value from traditional Tier-1s to SoC vendors and to automakers that write their own software
A legacy vehicle carries 70-150 electronic control units, each running one function on software the supplier owns. Zonal and central architectures cut ECU count by 60-80%, put cross-domain software on a few high-performance SoCs and let the automaker update the vehicle over the air for its whole life. Tesla, BYD, XPeng and NIO are already there; BMW's Neue Klasse, Mercedes-Benz MB.OS on the CLA and Volkswagen's Rivian-based architecture are the Western catch-up programs.
Value moves to three places. The central SoC is the most valuable single part: NVIDIA DRIVE Orin and Thor, Qualcomm Snapdragon Ride, Mobileye EyeQ6, Horizon Journey 6 and in-house chips from Tesla, NIO and XPeng, nearly all built at TSMC on 5 nm and 4 nm, with Tesla's AI5 split between TSMC Arizona and Samsung Taylor. Zonal controllers run on automotive MCUs from Renesas, NXP, Infineon and STMicroelectronics. And the vehicle OS - proprietary at Tesla, BYD and XPeng, or built on QNX, AUTOSAR and Android Automotive elsewhere - sets who controls the feature roadmap.
Every OTA-capable vehicle is also a data source. Fleet camera, radar and CAN logs flow to training clusters, and updated models flow back by OTA. Tesla shut down its Dojo program in 2025 and trains on NVIDIA-based clusters, including Cortex at Giga Texas; XPeng and Huawei run the same loop on Chinese road data. SemiconductorX estimates 2,500-4,000 semiconductor devices per Tesla, so one automaker building about 1.65 million vehicles a year consumes billions of chips. See Autonomy Training Clusters.
Risks concentrate at the same points. Advanced-node SoCs depend on TSMC in Taiwan. Automotive MCU and discrete supply proved fragile in the 2020-2022 shortage and again in late 2025, when the Dutch government took control of Nexperia and China blocked exports from Nexperia's Chinese plants. UN R155 and R156 have required cybersecurity and software-update management for all new vehicles in Europe since July 2024, and US rules bar Chinese and Russian connected-vehicle software from model year 2027 and hardware from model year 2030, which keeps Huawei's Qiankun ADS and HiSilicon chips out of the US market. See Semiconductor Dependencies.
E/E transition
Four E/E architectures
Each generation changes Tier-1 relationships, semiconductor content and how much of the stack the automaker controls.
| Architecture | Controllers | Control model | OEM control | Who benefits |
|---|---|---|---|---|
| Distributed ECU (legacy) | 70-150 ECUs | One function per ECU | Low | Traditional Tier-1s: Bosch, Continental, Denso |
| Domain controller | 20-40 ECUs plus domain controllers | One controller per domain | Medium | SoC vendors: NVIDIA, Qualcomm, Mobileye |
| Zonal | 5-15 zone controllers plus central compute | Zones by location; central intelligence | High | OEMs with in-house software; MCU vendors |
| Central vehicle computer | 1-3 compute nodes plus thin zones | Single vehicle computer | Maximum | Software-led OEMs: Tesla, BYD, XPeng, NIO |
Domains
SDV domains and their parts
| Domain | Role | Key parts and suppliers |
|---|---|---|
| Central compute | Vehicle OS, cross-domain software, AI inference | NVIDIA Orin and Thor, Qualcomm Snapdragon Ride, Mobileye EyeQ6, Horizon Journey 6; LPDDR5 memory |
| Zonal controllers | Local I/O, actuators, power distribution | Renesas RH850, NXP S32, Infineon AURIX, ST Stellar; AUTOSAR Classic |
| Chassis and motion | Brake-, steer-by-wire, suspension, torque vectoring | Bosch, ZF, Aumovio, Hyundai Mobis, BYD; ASIL-D |
| Digital cockpit | Displays, HMI, voice, infotainment | Qualcomm Snapdragon 8295 and Cockpit Elite, Samsung Exynos Auto, MediaTek Dimensity Auto, SiEngine |
| ADAS and autonomy hardware | Perception sensors and fusion | Cameras, 77 GHz radar, lidar; see EV Sensors |
| Vehicle OS and middleware | Runtime, services, hardware abstraction | QNX, AUTOSAR Adaptive, Android Automotive, Linux; OEM OS at Tesla, BYD, XPeng |
| OTA system | Fleet software delivery and rollback | Aptiv/Wind River, Harman, Excelfore, Sibros; in-house at Tesla, BYD, NIO |
| Vehicle networking | Backbone between compute, zones, sensors | Automotive Ethernet (Marvell, NXP, Broadcom), CAN FD, LIN |
Suppliers
Key suppliers by layer
| Layer | Company | Platform | Position |
|---|---|---|---|
| Central SoC | NVIDIA | DRIVE Orin (254 TOPS), Thor (up to 2,000 FP4 TFLOPS) | Default for Mercedes-Benz, Volvo, Li Auto, BYD, Toyota |
| Central SoC | Qualcomm | Snapdragon Ride, Ride Elite | BMW, GM, Renault; strong in combined cockpit-ADAS |
| Central SoC | Mobileye | EyeQ6 | Camera-based ADAS volume leader; Volkswagen, Porsche, Ford |
| Central SoC | Horizon Robotics | Journey 6 | Supplies most Chinese brands; VW Carizon joint venture |
| Central SoC | Tesla, NIO, XPeng | AI4/AI5, Shenji NX9031, Turing | In-house; XPeng Turing also in VW China models |
| MCU | Renesas | RH850, R-Car | Largest automotive MCU supplier; Toyota, Honda |
| MCU | NXP | S32 | Zonal and networking leader |
| MCU | Infineon | AURIX | ASIL-D safety for braking, steering, powertrain |
| Cockpit SoC | Qualcomm | Snapdragon 8295, Cockpit Elite | Premium cockpit leader; widely used by Chinese OEMs |
| Vehicle OS | BlackBerry | QNX | Safety-certified RTOS in most Tier-1 ECUs |
| Vehicle OS | Android Automotive | Infotainment for Volvo, Polestar, Renault, GM | |
| Vehicle OS | Volkswagen and Rivian | RV Tech joint venture | Rivian zonal architecture for VW Group from 2027 |
Platforms
Chinese and Western SDV platforms
| Automaker | Stack | Position |
|---|---|---|
| Tesla | Proprietary OS, OTA, FSD; AI4, AI5 next | Western full-stack benchmark |
| BYD | Proprietary OS; God's Eye ADAS (DiPilot) | Full stack, ADAS standard across the lineup |
| XPeng | XOS, VLA driving model, Turing chips | Most advanced Chinese in-house stack; exports to Europe |
| Huawei (HIMA) | HarmonyOS cockpit, Qiankun ADS | Supplied to AITO (Seres), Luxeed, Stelato, Avatr; barred from US |
| Volkswagen | CARIAD; Rivian joint venture | Billions in CARIAD losses; Rivian architecture is the reset |
| Mercedes-Benz, BMW | MB.OS; BMW Neue Klasse with four central computers | Shipping from 2025; behind Chinese OTA cadence |
| GM, Ford | GM centralized platform (from 2028); Ford FNV | US programs restarting on central compute |
Sources
Sources and scope
- Scope
- SDV Systems Supply Chain
- Sources
- Automaker and supplier disclosures; SemiconductorX (Tesla device count); UNECE R155/R156; BIS connected vehicle rule (January 2025)
- Updated
- October 2026