Skip to content

Open SOME/IP spec references added. #2525

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dasoho wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Open SOME/IP spec references added. #2525

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions docs/features/communication/some_ip_gateway/architecture/index.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,8 +27,10 @@ data or to subscribe to data. As such it will need to know and understand the da
the IPC network.

It also is a participant in the SOME/IP network and provides services for the service oriented communication.
This shall be possible by including the `vsomeip <https://github.com/COVESA/vsomeip>`_ SOME/IP stack for reference,
which can be replaced by other implementations, i.e. proprietary commercial stacks.
This functionality is enabled through the inclusion of the `vsomeip <https://github.com/COVESA/vsomeip>`_ stack,
which is based on the publicly released `Open SOME/IP <https://github.com/some-ip-com/open-someip-spec>`_ Specification
Copy link
Contributor

@FScholPer FScholPer Feb 2, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would make sense to pick a release here which can be later on updated: https://github.com/some-ip-com/open-someip-spec/tree/release-2025-12

Copy link
Contributor

@FScholPer FScholPer Feb 9, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dasoho any updates?

Copy link
Contributor Author

@dasoho dasoho Feb 9, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was not available last week, will provide an update by Feb. 11th.

Copy link
Contributor Author

@dasoho dasoho Feb 9, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will do the update and reference the current release.

and serves as a reference implementation that may be substituted with alternative solutions, including proprietary
commercial SOME/IP stacks.
Copy link
Contributor

@FScholPer FScholPer Feb 2, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should remove that sentence as this is not in scope for S-CORE

Copy link
Contributor Author

@dasoho dasoho Feb 9, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you really mean the entire sentence? (Incl. the vsomeip based plugin?)
Actually, the reference plugin based on vsomeip was already mentioned before. Has it been decided, that a reference plugin based on vomeip shouldn't be part of the SOME/IP Gateway?


There need to be some components between the two communication networks as data types and their according representations and
transmission cadence can be different. Translation of data types could be handled in some translation module
Expand Down
8 changes: 6 additions & 2 deletions docs/features/communication/some_ip_gateway/index.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -102,8 +102,11 @@ The requirements from Communication generally apply to the SOME/IP Gateway.
SOME/IP protocol implementation
-------------------------------



For reference purpose, the gateway shall use the `vsomeip <https://github.com/COVESA/vsomeip>`_ protocol
implementation that is compatible and complying with the SOME/IP specification from `some-ip.com <https://some-ip.com/>`_. (:need:`feat_req__some_ip_gateway__someip_protocol`)
implementation that is compatible and complying with the SOME/IP specification from `Open SOME/IP <https://github.com/some-ip-com/open-someip-spec>`_ (:need:`feat_req__some_ip_gateway__someip_protocol`)

Protocol implementations shall be wrapped in an abstraction API, that stays stable and allows implementations may be exchanged, potentially even by binary only libraries.

The SOME/IP Gateway shall support SOME/IP Events, Fields and Methods and shall map these accordingly into IPC.
Expand Down Expand Up @@ -235,7 +238,8 @@ License Impact
[How could the copyright impacted by the license of the new contribution?]

SOME/IP is a protocol, including applied E2E protection and the according profile (polynom, etc.),
is defined by multiple organizations, here we refer to the us of `vsomeip <https://github.com/COVESA/vsomeip>`_ implementation that refers to `some-ip.com <https://some-ip.com/>`_.
which is defined by multiple organizations, here we refer to the use of `vsomeip <https://github.com/COVESA/vsomeip>`_ implementation that refers to `some-ip.com <https://some-ip.com/>`_ and
the associated protocol specification of `Open SOME/IP <https://github.com/some-ip-com/open-someip-spec>`_.
The gateway implementation shall carefully distinguish between the SOME/IP communication stack,
the E2E protection of data, and the integration into S-CORE mw::com.

Expand Down
10 changes: 5 additions & 5 deletions docs/features/communication/some_ip_gateway/requirements/index.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,17 +39,17 @@ Functional Requirements

The SOME/IP Gateway shall support an interface to plug-in a E2E protection service implementation.

.. feat_req:: Compatibility with `some-ip.com <https://some-ip.com/>`_ Protocol Specification
.. feat_req:: Compatibility with Open SOME/IP Protocol Specification
:id: feat_req__some_ip_gateway__someip_protocol
:reqtype: Functional
:security: NO
:safety: ASIL_B
:satisfies: stkh_req__communication__supported_net
:status: valid

The SOME/IP protocol implementation shall be fully compatible and complying with the SOME/IP protocol specification from `some-ip.com <https://some-ip.com/>`_.
The SOME/IP protocol implementation shall be fully compatible and complying with the SOME/IP protocol specification from `Open SOME/IP <https://github.com/some-ip-com/open-someip-spec>`_.
Copy link
Contributor

@FScholPer FScholPer Feb 2, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this the case for vsomeip at the moment?

Copy link
Contributor Author

@dasoho dasoho Feb 9, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would say so:
As mentioned here vsomeip claims to implement the protocol specified in https://some-ip.com/ and the first link on this page points to the Open SOME/IP specification.
So, at least from documentation point of view, vsomeip traces to the Open SOME/IP specification.


.. feat_req:: Compatibility with `some-ip.com <https://some-ip.com/>`_ E2E Protocol Specification
.. feat_req:: Compatibility with some-ip.com E2E Protocol Specification
:id: feat_req__some_ip_gateway__e2e_specs
:reqtype: Functional
:security: NO
Expand All @@ -59,12 +59,12 @@ Functional Requirements

The E2E protection implementation shall be fully compatible and complying with the E2E protocol specification from `some-ip.com <https://some-ip.com/>`_.

.. feat_req:: Compatibility with `some-ip.com <https://some-ip.com/>`_ SOME/IP Service Discovery Protocol Specification
.. feat_req:: Compatibility with Open SOME/IP Service Discovery Protocol Specification
:id: feat_req__some_ip_gateway__someip_sd_protocol
:reqtype: Functional
:security: NO
:safety: ASIL_B
:satisfies: stkh_req__communication__supported_net
:status: valid

The Service Discovery implementation shall be fully compatible and complying with the SOME/IP service discovery specification from `some-ip.com <https://some-ip.com/>`_.
The Service Discovery implementation shall be fully compatible and complying with the SOME/IP service discovery specification from `Open SOME/IP <https://github.com/some-ip-com/open-someip-spec>`_.
2 changes: 1 addition & 1 deletion docs/features/communication/some_ip_gateway/service_discovery/index.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@
SOME/IP Gateway Service Discovery
#################################

The implementation shall be fully compatible and complying with the SOME/IP Service Discovery Protocol specification from AUTOSAR Adaptive.
The implementation shall be fully compatible and complying with the SOME/IP Service Discovery Protocol specification from `Open SOME/IP <https://github.com/some-ip-com/open-someip-spec>`_.
Service discovery deals with discovery and connection setup of services.
The basic summary of service discovery is as follows:

Expand Down