Gateway IPC Binding Component Requirements#
These requirements cover the Gateway IPC Binding’s control and event data transport. They do not claim method-call transport, which is not implemented.
IPC binding connects service connectors across peers
|
status: valid
security: NO
safety: ASIL_B
|
||||
When a configured service is offered on one side of the IPC connection, the binding shall make it available to SOCom clients on the other side, and make it unavailable when the service stops being offered. |
|||||
IPC binding propagates event subscriptions
|
status: valid
security: NO
safety: ASIL_B
|
||||
A subscription or unsubscription to a bridged SOCom event on one peer shall be propagated to the corresponding server connector on the other peer. |
|||||
IPC binding forwards event payloads across peers
|
status: valid
security: NO
safety: ASIL_B
|
||||
When an event is updated on a bridged SOCom server connector, the binding shall deliver the same payload bytes to subscribed clients on the remote peer. |
|||||