Feature change SOME/IP GW remove AUTOSAR refs #2316

ZoranCutura · 2025-12-09T15:50:56Z

Removing references to Autosar specs and refering to vsomeip instead.
Resolves #2251

github-actions · 2025-12-09T15:51:07Z

⚠️ Docs-as-Code version mismatch detected
Please check the CI build logs for details and align the documentation version with the Bazel dependency.

ZoranCutura · 2025-12-11T10:13:18Z

unintendedly closed, will reopen!

github-actions · 2025-12-11T13:48:28Z

The created documentation from the pull request is available at: docu-html

ZoranCutura · 2025-12-11T14:03:02Z

@lurtz please also review and check if proposed changes are ok for you

anmittag

there is still one autosar reference in a diagram

docs/features/communication/some_ip_gateway/assets/e2e_state_machine_on_client_side.drawio.svg

docs/modules/orchestrator/docs/safety_mgt/module_safety_plan.rst

NEOatNHNG

vsomeip doesn't contain an E2E implementation nor a "Payload Transformation".
For the payload transformation can implement a S-CORE payload transformation which is based e.g. on OpenSOMEIP spec and only supports a subset of the features for the MVP.
For the E2E we have to come up with a better plan. So far for E2E it would use "AUTOSAR" code (i.e. use a commercial stack).

NEOatNHNG · 2025-12-18T18:13:20Z

docs/features/code_generation/index.rst

Is it intentional that this PR also includes the addition of the "Code Generation" feature? Seems to be a separate topic to me.

Bad rebaseing by me! Rebased it again so this was removed.

NEOatNHNG · 2025-12-18T18:14:52Z

docs/features/communication/some_ip_gateway/architecture/index.rst


 It also is a participant in the SOME/IP network and provides services for the service oriented communication.
-This shall be possible by including SOME/IP stacks that are AUTOSAR compliant.
+This shall be possible by including SOME/IP stacks from `vsomeip <https://github.com/COVESA/vsomeip>`_ for reference, which can be replaced by other


Suggested change

This shall be possible by including SOME/IP stacks from `vsomeip <https://github.com/COVESA/vsomeip>`_ for reference, which can be replaced by other

This shall be possible by including the `vsomeip <https://github.com/COVESA/vsomeip>`_ SOME/IP stack for reference, which can be replaced by other

I resolved this one. (Note, will not be able to resolve all the review findings in this PR, as I miss the necessary background on SOME/IP)

NEOatNHNG · 2025-12-18T18:23:40Z

docs/features/communication/some_ip_gateway/assets/e2e_state_machine_in_gateway.drawio.svg

vsomeip doesn't contain an E2E implementation nor a "Payload Transformation".
For the payload transformation can implement a S-CORE payload transformation which is based e.g. on OpenSOMEIP spec and only supports a subset of the features for the MVP.
For the E2E we have to come up with a better plan. So far for E2E it would use "AUTOSAR" code (i.e. use a commercial stack).

NEOatNHNG · 2025-12-18T18:23:48Z

docs/features/communication/some_ip_gateway/index.rst

 CRC-protection and checks, and message counters.

-There are several E2E (= End-to-End) profiles, which utilize various CRC routines as part of AUTOSAR E2E Protocol Specification, that shall be supported with the SOME/IP Gateway.
+There are several E2E (= End-to-End) profiles, which utilize various CRC routines as part of E2E Protocol Specification, that shall be supported with the SOME/IP Gateway.


E2E is still AUTOSAR only. So I guess here we need to stick to the previous wording.

specs on some-ip.com also refer to AUTOSAR, so this is actually AUTOSAR for the moment.

NEOatNHNG · 2025-12-18T18:23:50Z

docs/features/communication/some_ip_gateway/index.rst

- `AUTOSAR_FO_PRS_E2EProtocol <https://www.autosar.org/fileadmin/standards/R24-11/FO/AUTOSAR_FO_PRS_E2EProtocol.pdf>`_
- `AUTOSAR_FO_RS_E2E <https://www.autosar.org/fileadmin/standards/R24-11/FO/AUTOSAR_FO_RS_E2E.pdf>`_


Keep references for E2E

specs on some-ip.com also refer to AUTOSAR, so this is actually AUTOSAR for the moment.

NEOatNHNG · 2025-12-18T18:23:53Z

docs/features/communication/some_ip_gateway/requirements/index.rst

-   The E2E protection implementation shall be fully compatible and complying with the E2E protocol specification from AUTOSAR Adaptive Version 24-11.
-   - `AUTOSAR_FO_PRS_E2EProtocol <https://www.autosar.org/fileadmin/standards/R24-11/FO/AUTOSAR_FO_PRS_E2EProtocol.pdf>`_
-   - `AUTOSAR_FO_RS_E2E <https://www.autosar.org/fileadmin/standards/R24-11/FO/AUTOSAR_FO_RS_E2E.pdf>`_
+   The E2E protection implementation shall be fully compatible and complying with the E2E protocol specification from `some-ip.com <https://some-ip.com/>`_.


specs on some-ip.com also refer to AUTOSAR, so this is actually AUTOSAR for the moment.

NEOatNHNG · 2025-12-18T18:25:14Z

docs/features/diagnostics/index.rst

This part is a different feature, right?

my bad, did some wrong rebaseing. Changed the rebase again., this should now be resolved

removed references to AUTOSAR, now using vsomeip and some-ip.com . one more ref to AUTOSAR removed

Minor correction from review finding. Signed-off-by: Philipp Ahmann <2428012+pahmann@users.noreply.github.com>

ZoranCutura closed this Dec 10, 2025

ZoranCutura force-pushed the feature_change_some_ip_gw branch from fd1612c to e54ca4e Compare December 10, 2025 16:19

ZoranCutura reopened this Dec 11, 2025

ZoranCutura requested review from AThums, LittleHuba, dasoho and opajonk December 11, 2025 13:52

ZoranCutura marked this pull request as ready for review December 11, 2025 14:01

ZoranCutura requested review from a team, FScholPer, antonkri, johannes-esr and qor-lb as code owners December 11, 2025 14:01

anmittag suggested changes Dec 11, 2025

View reviewed changes

docs/features/communication/some_ip_gateway/assets/e2e_state_machine_on_client_side.drawio.svg Show resolved Hide resolved

anmittag approved these changes Dec 16, 2025

View reviewed changes

anmittag assigned ZoranCutura Dec 17, 2025

LittleHuba reviewed Dec 17, 2025

View reviewed changes

docs/modules/orchestrator/docs/safety_mgt/module_safety_plan.rst Show resolved Hide resolved

ZoranCutura force-pushed the feature_change_some_ip_gw branch from 85491c7 to d4ddbc3 Compare December 17, 2025 16:09

LittleHuba previously approved these changes Dec 17, 2025

View reviewed changes

ZoranCutura requested review from PhilipPartsch, aschemmel-tech, masc2023 and pahmann as code owners December 18, 2025 15:07

NEOatNHNG suggested changes Dec 18, 2025

View reviewed changes

ZoranCutura dismissed LittleHuba’s stale review via 74a946d December 19, 2025 09:47

some_ip_gateway: removed references to AUTOSAR

abd8463

removed references to AUTOSAR, now using vsomeip and some-ip.com . one more ref to AUTOSAR removed

ZoranCutura force-pushed the feature_change_some_ip_gw branch from 74a946d to abd8463 Compare December 19, 2025 09:51

NEOatNHNG approved these changes Dec 19, 2025

View reviewed changes

Correct reference to vsomeip including repo link

b204b77

Minor correction from review finding. Signed-off-by: Philipp Ahmann <2428012+pahmann@users.noreply.github.com>

NEOatNHNG approved these changes Jan 5, 2026

View reviewed changes

FScholPer approved these changes Jan 8, 2026

View reviewed changes

FScholPer merged commit 3266359 into eclipse-score:main Jan 8, 2026
6 checks passed

	This shall be possible by including SOME/IP stacks from `vsomeip <https://github.com/COVESA/vsomeip>`_ for reference, which can be replaced by other
	This shall be possible by including the `vsomeip <https://github.com/COVESA/vsomeip>`_ SOME/IP stack for reference, which can be replaced by other

		- `AUTOSAR_FO_PRS_E2EProtocol <https://www.autosar.org/fileadmin/standards/R24-11/FO/AUTOSAR_FO_PRS_E2EProtocol.pdf>`_
		- `AUTOSAR_FO_RS_E2E <https://www.autosar.org/fileadmin/standards/R24-11/FO/AUTOSAR_FO_RS_E2E.pdf>`_

Feature change SOME/IP GW remove AUTOSAR refs #2316

Feature change SOME/IP GW remove AUTOSAR refs #2316

Uh oh!

Conversation

ZoranCutura commented Dec 9, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Dec 9, 2025

Uh oh!

ZoranCutura commented Dec 11, 2025

Uh oh!

github-actions bot commented Dec 11, 2025

Uh oh!

ZoranCutura commented Dec 11, 2025

Uh oh!

anmittag left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

NEOatNHNG left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

ZoranCutura commented Dec 9, 2025 •

edited

Loading