Sync SOME/IP Gateway [2025-06-11]

[LittleHuba]

Participants

@ZoranCutura
Kaluza Andreas
Braun Holger
Reinhardt Lutz
@LittleHuba
@LuNieb
@FScholPer

Minutes

Motivation

Communication within ECU via IPC
Communication framework is used for any service-oriented communication.
If gateway does serialization, it must support additional plugins?

Discussion

Discussion based on communication steps presented by @crimson11 in a previous COM FT weekly.
SOME/IP specifics to be handled in a SOME/IP plugin, which is centrally utilized by a gateway.
Gateway communicates with IPC to any other applications within the ECU.

Goal is to centralize as many steps of the communication path as possible/sensible.
Further, common concepts shall be reused in different gateways.

Further steps

Participants will share their thoughts beneath this discussion and a future meeting will be set up for a discussion on open points.

[dasoho]

Additional meeting minutes:

Motivation
Common plugins are planned to be shared across S-Core and Autosar. Two identified candidates are SOME/IP, SOME/IP-SD and E2E.
Main goal of this meeting was to see what constraints and/or requirements we see towards a common SOME/IP and E2E plugin from S-Core perspective. Main touch point from S-Core perspective is the planned SOME/IP gateway (see corresponding feature request

Discussion
Starting from the communication steps presented by @crimson11 we discussed whether these communication steps can be either allocated to the overall SOME/IP gateway or to the core responsibility of the SOME/IP plugin (resp. E2E plugin).
Result of the discussion can be seen in slide 5 of the attached Powerpoint.
mw_com_layers_networking_someipgateway.pptx

The following additional points were discussed:

• To be considered: Should we assume a dedicated ABI compatibility across network/mw::com to avoid unnecessary transformations? E.g. SOME/IP ABI compatibilty in case of an SOME/IP vehicle network or DDS ABI compatibility in case the vehicle network is based on DDS.
  Constraint: There could be just one standard which drives the ABI compatibility
• Suggestions for serialization by @LittleHuba:
  -- utilize templates efficiently
  -- consider Visitor pattern