Enable E2E support for android and handling addition/removal of CRC data from SOME-I/P message #861
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
In the original e2e implementation,
The vsomeip application was required to reserve a certain number of bytes from the payload for adding E2E Header. The vsomeip stack would then use these reserved bytes to add E2E Header after the CRC calculation, based on the e2e profile.
If the application changes the profile, the application developer needs to update the code, reserve the required number of bytes for CRC in the payload, and reflect the profile changes in the JSON configuration.
Motivation for this change:
Changes that we have done:
e2e sender & receiver side implementation
To handle the error case when crc check or counter fails
Remove instance ID from data_id in vsomeip E2E protect & check
According to the AUTOSAR E2E protocol specification,
there is no requirement to include an instance ID along with the Data ID.
references:
[PRS_E2E_00323]
[PRS_E2E_00324]
Validation: