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).
Schematic example: field sizes and positions depend on the profile and configuration; the data ID is implicit in this example.
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.