Skip to main content

E2E

End-to-end communication protection (E2E) is a central safety and security framework within AUTOSAR for automotive communication. To ensure performance and reliability, E2E protection uses a checksum (CRC) together with a counter to detect data corruption, loss, repetition, or reordering. A data id, essentially a unique constant, is included in the checksum to ensure the integrity of the intended signal.

RemotiveBroker simplifies the implementation of end-to-end protection in ECU development.

Check out the blog post about E2E at remotivelabs.com.

How it works with RemotiveBroker​

RemotiveBroker adds E2E protection directly if the configured signal database contains E2E information. This means that when signals are published they're automatically wrapped with E2E information such as CRC, counter values, and data id. This applies for sporadic signals that are published as well as signals that are configured in a restbus.

It's also possible to subscribe to CRC and counters.

Supported profiles​

Currently, RemotiveBroker supports:

  • Profile 1 - All data id modes
  • Profile 5

Supported databases​

RemotiveBroker parses E2E information from:

  • ARXML
  • DBC

If you are using LDF or Fibex, see the RemotiveBroker meta database.

DBC keys​

The following keys are valid for annotating your signals with GenSigFuncType

Counter​

  • CNT1 and CNTR_AR_01 for a profile 1 counter
  • CNT5 and CNTR_AR_05 for a profile 5 counter

CRC​

  • CRC1A and CRC_AR_01_BOTH for profile 1 A
  • CRC1B and CRC_AR_01_ALT for profile 1 B
  • CRC1L and CRC_AR_01_LOW for profile 1 Low
  • CRC1N and CRC_AR_01_NIBBLE for profile 1 Nibble
  • CRC5 and CRC_AR_05 for profile 5

RemotiveBroker meta database​

If you are using LDF, Fibex, or your database is missing E2E information. Then you can easily extend the database by adding the information in a simple json format, as described in Meta Database json Schema and shown in an example on GitHub.