Gateway Daemon Architecture#
Overview#
gatewayd (SOME/IP Gateway Daemon (comp__gatewayd)) is the ASIL_B SOME/IP Gateway Daemon in the S-CORE communication stack. It bridges local ASIL_B and QM applications communicating over score::mw::com (LoLa shared-memory IPC) with the QM someipd network daemon (SOME/IP Network Daemon (comp__someipd)), isolating local safety-critical applications from the third-party SOME/IP network stack while handling SOME/IP header framing and sample serialization within the ASIL_B process boundary.
Description#
Rationale Behind Architecture Decomposition#
gatewayd separates process-level safety isolation and startup coordination from per-service directional bridging:
ASIL_B isolation from the QM network stack: To maintain freedom from interference (FFI) between
vsomeip(QM) andASIL_Bapplications,gatewaydruns as a separateASIL_Bprocess with zero dependency onvsomeip. It runsscore_com_serializerand frames or strips the 16-byte SOME/IP header contiguously in shared memory inside theASIL_Bdomain (where E2E protection will run), whilesomeipd(QM) owns the network sockets andvsomeiprouting.Startup synchronization before service bridging (
main.cpp):main.cppinitializes the configuration, serializer plugin,mw::comruntime, andsocom::Runtime, creates thegateway_ipc_bindingclient, and waits forbinding_client->is_connected()before creating any service adapters sosomeipdis guaranteed to have registered the bridged IPC services first.Directional split (
LocalServiceInstancevsRemoteServiceInstance): Outbound and inbound services have opposite discovery andmw::comroles —LocalServiceInstancediscovers localmw::comproviders viaGenericProxyand publishes framed SOME/IP events into asocomserver connector, whereasRemoteServiceInstanceoffers a localGenericSkeletonup front and subscribes to incoming SOME/IP events via asocomclient connector.
Static Architecture#
Gateway Daemon Static Architecture
|
status: valid
security: NO
safety: ASIL_B
|
||||
Component structure of
Fig. 7 Gateway Daemon Static Component Diagram# |
|||||
Dynamic Architecture#
Gateway Daemon Event Forwarding
|
status: valid
security: NO
safety: ASIL_B
|
||||
Runtime sequence for local service event forwarding (Application to
Fig. 8 Gateway Daemon Event Forwarding Sequence Diagram# |
|||||
Interfaces#
gatewayd is an executable daemon process and does not expose a C++ library header to external applications. Internally, main.cpp uses two adapter factory interfaces in namespace score::someip_gateway::gatewayd.
LocalServiceInstance Adapter Interface
|
status: valid
security: NO
safety: ASIL_B
|
||||
Internal C++ factory and discovery interface declared in |
|||||
CreateAsyncLocalServices and Create
|
status: valid
security: NO
safety: ASIL_B
|
||||
|
|||||
RemoteServiceInstance Adapter Interface
|
status: valid
security: NO
safety: ASIL_B
|
||||
Internal C++ factory interface declared in |
|||||
CreateAsyncRemoteService and Create
|
status: valid
security: NO
safety: ASIL_B
|
||||
|
|||||