Why there are different classes
A vehicle needs both: huge compute for perception and services, and tiny, cheap, robust nodes that switch a lamp or read a door switch. No single kind of computer fits all of this, so the architecture is a pyramid of node classes.
What the classes are
| Class | Typical silicon | Software | Attached via | Examples |
|---|---|---|---|---|
| HPC / central computer | Multi-core SoC, DRAM, GPU/NPU, HSM, safety island | Hypervisor, Linux/QNX, AUTOSAR Adaptive, services | Multi-gig Ethernet | Vehicle computer, ADAS computer, cockpit |
| Zone controller | High-end MCU or small SoC | AUTOSAR Classic, gateway, power management | Ethernet + CAN FD/LIN/T1S | Front, rear, left, right zone |
| MCU-based ECU | 32-bit MCU, embedded flash, HSM, often lockstep | AUTOSAR Classic or RTOS | CAN FD or classical CAN | Brake, steering, airbag, BMS, inverter |
| Smart sensor / actuator | Small MCU or ASIC with transceiver | Small firmware | LIN, 10BASE-T1S, CAN | Window lifter, seat motor, smart lamp, ultrasonic sensor |
| LIN slave | Very small MCU or LIN-ASIC | State machine or none | LIN | Mirror, HVAC flap, rain/light sensor |
| Hardwired I/O | No electronics, or a simple sensor | None | Copper wire to an ECU or zone | Door switch, lamp, temperature sensor, solenoid |
How they work together
Control loops close at the lowest level that can meet their timing: a brake ECU reads wheel speeds and drives valves itself, while the central computer decides what the vehicle should do. Zone controllers collect simple I/O and power, and LIN or 10BASE-T1S connect smart edge devices. Data flows upward for services and diagnostics; commands flow down.
When to choose which
- Highest ASIL, hard real-time, actuator nearby: dedicated MCU ECU.
- Feature-rich, frequently updated: service on central compute.
- Many simple loads in one area: zone controller with hardwired I/O and eFuses.
- Cheap, low-data devices: LIN slaves; for more data or diagnostics at the edge, 10BASE-T1S.
Best practices
- Allocate by timing, safety and update frequency — not by organisational history.
- Keep the number of software-bearing node types small to reduce update and security effort.
- Remember that hardwired I/O has no software to update but also no diagnostics beyond what the reading ECU provides.
Common pitfalls
- Putting security-relevant logic in nodes that cannot hold keys.
- Underestimating lifetime: MCUs and SoCs must stay available for 10–15 years of production and service.