Contents

The AUTOSAR communication stack

How a signal travels from an application to the bus in an AUTOSAR ECU — through COM, PduR, the bus interfaces and drivers — and where security, safety and gateways plug in.

Why it matters

Most integration problems in an ECU are communication problems: a signal arrives late, in the wrong format or not at all. Knowing the path a signal takes makes them findable.

What the layers are

Module Role
COM Packs signals into PDUs, handles timeouts, update bits, transmission modes
PduR (PDU Router) Routes PDUs between COM, transport protocols, SecOC and bus interfaces — and between buses on gateways
SecOC Adds/verifies authenticators for selected PDUs
CanTp / LinTp / DoIP Transport protocols for long messages (e.g. diagnostics)
CanIf / LinIf / SoAd Bus-specific interfaces
Drivers Hardware access (MCAL)

How a message flows

An application writes a signal → the RTE passes it to COM → COM packs it into a PDU and triggers transmission → PduR sends it (via SecOC if configured) to CanIf → the CAN driver puts it on the bus. Reception runs the same path upward, with timeout monitoring in COM.

A signal reaches the CAN bus
Application / RTEWrites and passes a signal
COMPacks signals into a PDU
PduRRoutes the PDU
CanIfCAN interface
CAN driverAccesses CAN hardware
CAN busCarries the frame

Simplified CAN transmit path; configured SecOC protection adds authentication processing along the PDU routing path.

Best practices

  • Generate stack configuration from one communication database for all ECUs.
  • Configure timeouts and substitute values explicitly for every received signal.
  • Keep gateway routing in PduR simple and documented.

Common pitfalls

  • Inconsistent PDU layouts between sender and receiver after a database change.

What it means for your discipline

  • Base software Core

    Configures signals, PDUs, routing paths and timeouts in COM, PduR, CanIf/LinIf/SoAd and the drivers.

  • Networks & communication Core

    Provides the communication matrix (DBC, ARXML) that the stack implements.

  • Cybersecurity Partial

    SecOC sits between PduR and the bus interface to add and check authenticators.

  • Functional safety Partial

    E2E protection is applied around signal groups before they enter COM.

  • Diagnostics & lifecycle Partial

    Diagnostic messages take their own path (Dcm, transport protocols) through the same stack.

  • Software update & OTA Partial

    Works with BSW teams on diagnostic routing and transport configuration to keep flash transfers reliable through ECUs and gateways.

No direct stake: E/E architecture · HPC & application software · Hardware & silicon

Where it sits in the software stack

Generic layered software of a central HPC (application processor with hypervisor, plus a safety island) and of a classic MCU-based ECU (AUTOSAR Classic). Highlighted modules matter for this topic. Click any module to open its page.

HPC · application processor (MPU) and safety island (MCU)
  • Classic RTE & COM — Passes application signals through the safety island's Classic RTE and communication stack.
  • WdgM · E2E · Dem — Provides E2E protection used around safety-relevant signal groups before transmission and after reception.
  • MCAL — Drives the safety island's bus peripherals beneath the Classic communication interfaces.
MCU-based ECU · AUTOSAR Classic
  • Communication — Packs signals, routes PDUs, monitors reception timeouts and authenticates selected traffic through SecOC.
  • ECU abstraction — Provides bus interfaces such as CanIf that connect PDU routing to peripheral drivers.
  • Microcontroller abstraction (MCAL) — Accesses bus controller hardware to transmit and receive frames.
  • Runtime environment (RTE) — Passes application signal reads and writes between software components and COM.