From 4f3be85c079aa267d81c6ec25e6c2142d0dde33a Mon Sep 17 00:00:00 2001 From: Holger Braun Date: Sun, 1 Feb 2026 14:52:07 +0100 Subject: [PATCH] Open SOME/IP spec references added. Open SOME/IP secification references added to SOME/IP Gateway feature specification. Signed-off-by: Holger Braun --- .../some_ip_gateway/architecture/index.rst | 6 ++++-- docs/features/communication/some_ip_gateway/index.rst | 8 ++++++-- .../some_ip_gateway/requirements/index.rst | 10 +++++----- .../some_ip_gateway/service_discovery/index.rst | 2 +- 4 files changed, 16 insertions(+), 10 deletions(-) diff --git a/docs/features/communication/some_ip_gateway/architecture/index.rst b/docs/features/communication/some_ip_gateway/architecture/index.rst index 65dce26e750..daffdcbb409 100644 --- a/docs/features/communication/some_ip_gateway/architecture/index.rst +++ b/docs/features/communication/some_ip_gateway/architecture/index.rst @@ -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 `_ 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 `_ stack, +which is based on the publicly released `Open SOME/IP `_ Specification +and serves as a reference implementation that may be substituted with alternative solutions, including proprietary +commercial SOME/IP stacks. 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 diff --git a/docs/features/communication/some_ip_gateway/index.rst b/docs/features/communication/some_ip_gateway/index.rst index 0a7d28743de..b3cdd2c51eb 100644 --- a/docs/features/communication/some_ip_gateway/index.rst +++ b/docs/features/communication/some_ip_gateway/index.rst @@ -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 `_ protocol -implementation that is compatible and complying with the SOME/IP specification from `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 `_ (: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. @@ -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 `_ implementation that refers to `some-ip.com `_. +which is defined by multiple organizations, here we refer to the use of `vsomeip `_ implementation that refers to `some-ip.com `_ and +the associated protocol specification of `Open SOME/IP `_. 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. diff --git a/docs/features/communication/some_ip_gateway/requirements/index.rst b/docs/features/communication/some_ip_gateway/requirements/index.rst index b182582bc02..c47c740517e 100644 --- a/docs/features/communication/some_ip_gateway/requirements/index.rst +++ b/docs/features/communication/some_ip_gateway/requirements/index.rst @@ -39,7 +39,7 @@ 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 `_ Protocol Specification +.. feat_req:: Compatibility with Open SOME/IP Protocol Specification :id: feat_req__some_ip_gateway__someip_protocol :reqtype: Functional :security: NO @@ -47,9 +47,9 @@ Functional Requirements :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 `_. + The SOME/IP protocol implementation shall be fully compatible and complying with the SOME/IP protocol specification from `Open SOME/IP `_. -.. feat_req:: Compatibility with `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 @@ -59,7 +59,7 @@ Functional Requirements The E2E protection implementation shall be fully compatible and complying with the E2E protocol specification from `some-ip.com `_. -.. feat_req:: Compatibility with `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 @@ -67,4 +67,4 @@ Functional Requirements :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 `_. + The Service Discovery implementation shall be fully compatible and complying with the SOME/IP service discovery specification from `Open SOME/IP `_. diff --git a/docs/features/communication/some_ip_gateway/service_discovery/index.rst b/docs/features/communication/some_ip_gateway/service_discovery/index.rst index cee8f4ac6db..645e159550c 100644 --- a/docs/features/communication/some_ip_gateway/service_discovery/index.rst +++ b/docs/features/communication/some_ip_gateway/service_discovery/index.rst @@ -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 `_. Service discovery deals with discovery and connection setup of services. The basic summary of service discovery is as follows: