Add CRC Mechanism to gatewayd for ASIL Compliance

[adityadave29]

Feature Request / Modification Description

There is a need to add a CRC mechanism to gatewayd as soon as possible and use SOME/IP only as the parser. The implementation should be made compatible with the required ASIL standards. Is anyone currently working on this section? Please let me know.

Expected Changes of work products

• Requirements
• Architecture
• Safety Analysis
• Security Analysis
• Detailed Design
• Implementation and Testing
• all

Impact analysis

The implementation will make Gateway some IP compatible with the required ASIL standards.

Safety or Security relevance

• none
• Safety relevant
• Security relevant

Expected required ASIL classification

ASIL_B

Expected Implementation Version (Release)

1.0

[lurtz]

The plan is to add E2E CRC verification to the gatewayd. You are right that this is not reflected at all in our documentation.

What is also missing are any ways how to communicate failed CRC checks to the mw::com API and mw::com needs to use of the E2E state machine to decide whether the state is trustworthy or not. Due to IP issues, we will likely do that with a plugin architecture.

Since we have not e.g. the serializer done yet, we have not yet started with any E2E / CRC work. Also the IPC binding will be reworked: https://github.com/orgs/eclipse-score/discussions/3240

However improvements from your side are welcome. I guess we could at least add E2E to the envisioned architecture.

[adityadave29]

Hi @lurtz, Thank you for your response. I have one question regarding compatibility with Adaptive AUTOSAR as well.

I noticed that, as of now, S-CORE uses a null serializer for serialization, whereas Adaptive AUTOSAR generally uses mechanisms such as TLV, depending on the vendor implementation. This seems like it could lead to compatibility issues at the communication/serialization layer. Are there any plans to address this and provide compatibility with the serialization mechanisms used by Adaptive AUTOSAR?

[lurtz]

For serialization we will use plugins. This is hard to do in a generic way because we have again IP issues and mw::com memory layout is compiler defined. For the time being we use the null serializer as pass through.

[adityadave29]

Hi @lurtz, I’d really like to contribute to this repo. It would be great if you could assign me a task that would be a good starting point for getting familiar with the codebase.