Domain vs Zone-Based Architectures - Vehicle Networks

Domain Architecture: Functional Grouping

Domain Architecture Signal Flow

  Powertrain Domain              Chassis Domain
  ┌────────────────┐             ┌─────────────────┐
  │ ECU_Engine     │             │ ECU_ABS         │
  │ ECU_Trans      │             │ ECU_ESC         │
  │ ECU_Catalyst   │             │ ECU_EPS         │
  └──────┬─────────┘             └────────┬────────┘
   CAN 500k│                              │CAN 500k
           └────────────┬─────────────────┘
                 ┌──────┴───────┐
                 │  Gateway ECU │ ← routes cross-domain signals
                 └──────┬───────┘
            Body CAN 125k│
          ┌──────────────┼──────────────────┐
      ECU_BCM      ECU_Door_FL         ECU_Seat

  BMW F-series, Toyota pre-2020, most current production vehicles

Zone Architecture: Physical Grouping

Zonal Architecture (2025+ vehicles)

                   Vehicle Computer
                  (Central High-Perf SoC)
                   1000BASE-T1 backbone
         ┌──────────────┼──────────────┐
         ▼              ▼              ▼
  Front-Left Zone   Front-Right Zone   Rear Zone
  ┌───────────┐     ┌────────────┐   ┌──────────┐
  │Zone ECU   │     │Zone ECU    │   │Zone ECU  │
  │(NXP S32G) │     │(NXP S32G)  │   │(NXP S32G)│
  ├───────────┤     ├────────────┤   ├──────────┤
  │Window FL  │     │Window FR   │   │Seat RL   │
  │Mirror FL  │     │Mirror FR   │   │Seat RR   │
  │Door FL    │     │Door FR     │   │Trunk     │
  │Corner rad │     │Headlight FR│   │Rear cam  │
  └───────────┘     └────────────┘   └──────────┘
  Legacy ECUs connect via CAN to Zone ECU (gateway inside Zone ECU)

Comparison	Domain Architecture	Zone Architecture
Grouping	By function (powertrain, chassis, body)	By physical location (FL, FR, Rear, Roof)
Wiring harness	Long runs from ECU to actuator in its zone	Short runs — actuator connects to nearest Zone ECU
ECU count	70–120 ECUs	20–30 ECUs (zone ECUs consolidate function)
OTA update	Per ECU binary (100+ OTA targets)	Per zone (20–30 OTA targets; one update covers all zone peripherals)
Bandwidth	Domain CAN buses (limited, 500 kbps)	GbE backbone (1 Gbps); zone CAN legacy integration
New feature	New hardware ECU + wiring harness change	Software deployment to existing zone ECU

Migration Challenges: Classic-to-Zone Transition

⚠️ Hybrid Classic/Adaptive Architecture (2022–2028)

Most vehicles in production today and entering development are hybrid architectures: some zones use AUTOSAR Classic ECUs (NXP MPC57xx, Infineon AURIX) for real-time body/chassis functions, while the central Vehicle Computer runs AUTOSAR Adaptive on a high-performance SoC (Qualcomm SA8295, NXP S32G). The Zone ECU must bridge between Classic CAN signals and Adaptive SOME/IP services — a gateway role requiring careful signal routing matrix design, latency budget analysis, and end-of-line configuration of Classic node NADs.

Summary

Domain architecture is proven, widely deployed, and well-understood but creates long wiring harnesses and a fragmented OTA update landscape. Zone architecture reduces harness length by 30–50% and consolidates ECU count, but requires migrating legacy supplier CAN ECUs to SOME/IP interfaces via zone gateway software. The 2022–2028 transition period means virtually all new vehicle programs implement hybrid Classic/Adaptive zonal architectures rather than purely one approach.

🔬 Deep Dive — Core Concepts Expanded

This section builds on the foundational concepts covered above with additional technical depth, edge cases, and configuration nuances that separate competent engineers from experts. When working on production ECU projects, the details covered here are the ones most commonly responsible for integration delays and late-phase defects.

Key principles to reinforce:

Configuration over coding: In AUTOSAR and automotive middleware environments, correctness is largely determined by ARXML configuration, not application code. A correctly implemented algorithm can produce wrong results due to a single misconfigured parameter.
Traceability as a first-class concern: Every configuration decision should be traceable to a requirement, safety goal, or architecture decision. Undocumented configuration choices are a common source of regression defects when ECUs are updated.
Cross-module dependencies: In tightly integrated automotive software stacks, changing one module's configuration often requires corresponding updates in dependent modules. Always perform a dependency impact analysis before submitting configuration changes.

🏭 How This Topic Appears in Production Projects

Project integration phase: The concepts covered in this lesson are most commonly encountered during ECU integration testing — when multiple software components from different teams are combined for the first time. Issues that were invisible in unit tests frequently surface at this stage.
Supplier/OEM interface: This is a topic that frequently appears in technical discussions between Tier-1 ECU suppliers and OEM system integrators. Engineers who can speak fluently about these details earn credibility and are often brought into critical design review meetings.
Automotive tool ecosystem: Vector CANoe/CANalyzer, dSPACE tools, and ETAS INCA are the standard tools used to validate and measure the correct behaviour of the systems described in this lesson. Familiarity with these tools alongside the conceptual knowledge dramatically accelerates debugging in real projects.

⚠️ Common Mistakes and How to Avoid Them

Assuming default configuration is correct: Automotive software tools ship with default configurations that are designed to compile and link, not to meet project-specific requirements. Every configuration parameter needs to be consciously set. 'It compiled' is not the same as 'it is correctly configured'.
Skipping documentation of configuration rationale: In a 3-year ECU project with team turnover, undocumented configuration choices become tribal knowledge that disappears when engineers leave. Document why a parameter is set to a specific value, not just what it is set to.
Testing only the happy path: Automotive ECUs must behave correctly under fault conditions, voltage variations, and communication errors. Always test the error handling paths as rigorously as the nominal operation. Many production escapes originate in untested error branches.
Version mismatches between teams: In a multi-team project, the BSW team, SWC team, and system integration team may use different versions of the same ARXML file. Version management of all ARXML files in a shared repository is mandatory, not optional.

📊 Industry Note

Engineers who master both the theoretical concepts and the practical toolchain skills covered in this course are among the most sought-after professionals in the automotive software industry. The combination of AUTOSAR standards knowledge, safety engineering understanding, and hands-on configuration experience commands premium salaries at OEMs and Tier-1 suppliers globally.