What runs here
An MCU-based zone controller combines local sensor and actuator communication with gateway traffic. Its AUTOSAR Classic middleware connects application software to configured communication paths. The grid groups runtime and communication functions together; COM and PduR belong to basic software in the formal AUTOSAR architecture.
| Component | Role |
|---|---|
| Runtime Environment (RTE) | Provides generated interfaces between application software components and access to basic software services. |
| AUTOSAR COM | Packs and unpacks signals and signal groups, manages configured transmission behavior and reception deadline monitoring, and provides signal gateway functions. |
| PDU Router (PduR) | Routes interaction-layer protocol data units, or I-PDUs, between configured communication modules. |
| Supporting communication modules | Connect routing paths to CAN FD, LIN and Ethernet through the appropriate interfaces, transport protocols and socket services. |
Local application communication may pass through RTE and COM. Transit traffic can follow a PduR gateway path without visiting an application component. AUTOSAR Classic architecture
PduR forwards I-PDUs without interpreting their individual signals. COM’s signal gateway copies configured signals or signal groups into outgoing I-PDUs. Unit conversion, plausibility decisions and content-dependent translation need explicitly designed processing beyond simple signal mapping. PduR specification, COM specification
Why it looks like this
The controller must serve local control deadlines while forwarding traffic between networks with different capacities and transmission schedules. Static configuration makes routes, memory use and execution paths easier to analyze. MCU memory, communication peripherals and cost constrain buffering, protocol choices and processing overhead.
A gateway concentrates load: several ingress channels may feed one slower destination. Multicore silicon can distribute work, but shared buffers, locks and cross-core transfers introduce contention. Timing analysis must include bursts, diagnostic traffic and communication recovery alongside normal control traffic.
ASIL B–D requirements arise from allocated safety functions, rather than automatically applying equally to every route. Safety-related communication needs suitable integrity checks, timeout behavior and freedom from interference. More frequently updated gateway logic also needs stable interface contracts and regression checks against unchanged downstream devices.
How it connects
Above this layer, application software uses RTE interfaces for local I/O logic and gateway decisions. Below it, a typical CAN signal path passes through COM, PduR, CAN Interface (CanIf) and the CAN driver. LIN communication uses LIN Interface (LinIf), with transmission constrained by configured schedules.
For IP-based Ethernet communication, the Socket Adaptor (SoAd) connects suitable PDU paths to TCP/IP (TcpIp), which reaches Ethernet through Ethernet Interface (EthIf) and drivers. SOME/IP requires additional configured functions where used. Socket Adaptor specification
10BASE-T1S supplies an Ethernet physical link; the chosen upper protocols determine its middleware path. Connecting CAN FD to Ethernet therefore requires an agreed payload mapping or encapsulation. PduR routing is distinct from Ethernet frame switching and IP packet forwarding.
Adjacent platform services control communication availability, diagnostics and security event reporting. Routing must respect their startup, shutdown and recovery states.
Compared with other node classes
- HPC application processor: Adaptive or other service middleware emphasizes services and processes; the zone MCU emphasizes configured signal and PDU paths. Classic can also support SOME/IP.
- HPC safety island: RTE and COM support bounded safety functions, typically with less heterogeneous gateway responsibility than the zone controller.
- MCU-based ECU: Uses similar Classic mechanisms, usually with a narrower set of local functions and routes.
- Smart node or LIN slave: Often implements only its required protocol handling, without a full RTE, COM and multi-network gateway stack.
Best practices
- Define each route’s owner, payload contract, destination, timing budget and failure behavior before generating configuration.
- Choose PDU forwarding, signal mapping or application translation explicitly; document where data meaning changes.
- Bound buffers and define overflow behavior. Verify latency under bursts, slow destinations, diagnostics and recovery.
- Allocate tasks, interrupts and cross-core communication using measured execution times and interference analysis.
- Preserve end-to-end safety protection where possible. Treat protection termination and regeneration as an explicit safety design decision.
- Apply permitted-route policies and required authentication mechanisms; version routing configuration with software and network descriptions.
Common pitfalls
- Assuming PduR automatically translates signals, changes transmission rates or implements a security firewall.
- Treating successful forwarding as proof of timely delivery; queued data can arrive too late for control.
- Assuming a safety-capable MCU makes all middleware paths safety-compliant without integration evidence.
- Ignoring sleep, wake-up and unavailable destinations, causing stale transmissions or unintended network activity.