Contents

E2E protection

How safety-relevant messages are protected against corruption, loss, repetition and delay from sender to receiver — with CRCs, counters and timeouts.

1 min read · Discipline stake: Safety BSW Networks Security

Why it exists

Buses have their own error detection, but messages can still be corrupted inside ECUs or gateways, lost, repeated or delayed. A safety-relevant receiver must detect all of these, end to end.

What it is

The sender adds:

  • a CRC over the data and a hidden data ID (detects corruption and mix-ups),
  • a sequence counter (detects loss, repetition, wrong order).

The receiver checks both and monitors timing (detects delay and absence).

Example E2E protected PDU
CRCE2E header
CounterE2E header
PayloadSafety-relevant data

Schematic example: field sizes and positions depend on the profile and configuration; the data ID is implicit in this example.

Sender protection and receiver checks
Prepare dataSender prepares safety-relevant payload
Protect PDUUpdate counter; calculate CRC using data ID
Transport PDUAcross communication path
Check receptionReceiver checks CRC, counter and timing
Evaluate resultUse data or apply configured fault reaction

Receiver supervision combines protection checks and timing monitoring to determine whether received data can be used.

How it relates to SecOC

E2E is for faults (safety). SecOC is for attacks (security). They are complementary; a common order is to apply E2E to the payload and then SecOC to the PDU.

Best practices

  • Choose the E2E profile matching the bus and payload length.
  • Define the reaction to errors (substitute values, degraded mode) as part of the safety concept.

Common pitfalls

  • Gateways that repack signals and break the E2E protection.

What it means for your discipline

  • Functional safety Core

    Specifies which signals need E2E protection, the profile and the reaction to detected errors.

  • Base software Core

    Configures the E2E library/transformer and the state machines that evaluate it.

  • Networks & communication Partial

    E2E bytes reduce payload space and must survive gateway routing unchanged.

  • Cybersecurity Partial

    E2E detects faults, not attacks — an attacker can recompute a CRC. SecOC is the security counterpart.

No direct stake: E/E architecture · HPC & application software · Hardware & silicon · Diagnostics & lifecycle · Software update & OTA

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)
  • AUTOSAR Adaptive — Configured E2E protection checks safety-related ara::com data using CRCs, counters and receiver supervision.
  • WdgM · E2E · Dem — E2E services protect outgoing safety data and check received data for corruption, repetition and sequence errors.
  • Safety monitors — Safety monitors evaluate communication validity and trigger configured reactions when protected data becomes unusable.
MCU-based ECU · AUTOSAR Classic
  • Memory · crypto · WdgM — The E2E library generates and checks CRCs and counters using the configured profile and data ID.
  • Communication — Communication routing must preserve protected payloads and provide the configured reception deadline monitoring.
  • Application layer — Receiving components use E2E status and timing supervision to select valid data, substitute values or degraded operation.