gatewayd Component Requirements#

These requirements cover externally observable gateway daemon behavior. General service-instance and versioning semantics remain owned by mw::com.

gatewayd starts from runtime deployment configuration
status: valid
security: NO
safety: ASIL_B

On startup, gatewayd shall initialize the mw::com runtime from the supplied service-instance manifest and, for each service type declared in the SOME/IP configuration file, create a local bridge for every local_service_instances entry and a remote bridge for every remote_service_instances entry.

Integrity verification of the service-instance manifest is a property of the mw::com runtime and is not performed by gatewayd itself; integrity of the SOME/IP configuration file is covered by Integrity of the SOME/IP co... (aou_req__gatewayd__someip_config_integrity).

gatewayd prints usage on request
status: valid
security: NO
safety: ASIL_B
reqtype: Interface
version: 1
satisfied by: comp__gatewayd

When started with the --help command-line argument, gatewayd shall print its usage text and exit with a success exit code.

Integrity of the SOME/IP configuration file
status: valid
security: NO
safety: ASIL_B
reqtype: Non-Functional
version: 1

The integrator shall supply gatewayd with a SOME/IP configuration file whose integrity has been verified before the file is passed on the --configuration command-line argument. gatewayd consumes this file as-supplied and performs no additional integrity check.