Communication Architecture#

Communication Architecture
status: valid
security: YES
safety: ASIL_B
version: 2

Overview#

An brief overview of communication is described here.

Description#

A description of the communication module is located here

Static Architecture#

As discussed in Rationale, the overall architecture of the communication framework must be layered. This is required, to separate the frontend from the underlying communication mechanisms (also called bindings).

This ensures a stable public API, independent of the underlying binding(s). At the same time, the communication framework can support many different communication protocols in a flexible manner.

Communication Feature
status: valid
security: YES
safety: ASIL_B
version: 1
satisfies: feat_req__com__acl_for_consumer, feat_req__com__acl_for_producer, feat_req__com__acl_per_service_instance, feat_req__com__acl_placement, feat_req__com__asil, feat_req__com__async_support, feat_req__com__bi_directional_comm, feat_req__com__binding_agnostic_api, feat_req__com__config_notifications, feat_req__com__configurable_queues, feat_req__com__consistent_data, feat_req__com__data_corruption, feat_req__com__data_driven_arch, feat_req__com__data_loss, feat_req__com__data_notifications, feat_req__com__data_reordering, feat_req__com__data_repetition, feat_req__com__depl_config_runtime, feat_req__com__event_type, feat_req__com__interfaces, feat_req__com__lang_idioms, feat_req__com__lang_infra, feat_req__com__lock_free_access, feat_req__com__lock_free_queue, feat_req__com__method, feat_req__com__multi_binding_depl, feat_req__com__multi_binding_support, feat_req__com__multi_lang, feat_req__com__one_way_sharing, feat_req__com__producer_consumer, feat_req__com__producer_timestamps, feat_req__com__readonly_vm, feat_req__com__request_driven_arch, feat_req__com__safe_communication, feat_req__com__service_discovery, feat_req__com__service_instance, feat_req__com__service_instance_granularity, feat_req__com__service_instance_names, feat_req__com__service_location_transparency, feat_req__com__shared_memory, feat_req__com__signal, feat_req__com__stateless_communication, feat_req__com__streamed_data, feat_req__com__testability_fake_binding, feat_req__com__testability_mock_api, feat_req__com__time_based_arch, feat_req__com__tracing, feat_req__com__versioning, feat_req__com__zero_copy, feat_req__ipc__availability, feat_req__ipc__confidentiality, feat_req__ipc__integrity, feat_req__ipc__zero_copy, feat_req__some_ip_gateway__e2e_plugin_ifc, feat_req__some_ip_gateway__e2e_specs, feat_req__some_ip_gateway__someip_protocol, feat_req__some_ip_gateway__someip_sd_protocol, feat_req__some_ip_gateway__stack_plugin_ifc

Interface Description#

The public API for communication is defined as:

Initialize
status: valid
security: YES
safety: ASIL_B
version: 1
Offer Service
status: valid
security: YES
safety: ASIL_B
version: 1
Update
status: valid
security: YES
safety: ASIL_B
version: 1
Send
status: valid
security: YES
safety: ASIL_B
version: 1
StartFindService
status: valid
security: YES
safety: ASIL_B
version: 1
CreateProxy
status: valid
security: YES
safety: ASIL_B
version: 1
Subscribe
status: valid
security: YES
safety: ASIL_B
version: 1
GetNewSamples
status: valid
security: YES
safety: ASIL_B
version: 1