Communication Architecture#
Communication Architecture
|
status: valid
security: YES
safety: ASIL_B
|
||||
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
|
||||
Interface Description#
The public API for communication is defined as:
Communication User Interface
|
status: valid
security: YES
safety: ASIL_B
|
||||
|
|||||
Initialize
|
status: valid
security: YES
safety: ASIL_B
|
||||
Offer Service
|
status: valid
security: YES
safety: ASIL_B
|
||||
Update
|
status: valid
security: YES
safety: ASIL_B
|
||||
Send
|
status: valid
security: YES
safety: ASIL_B
|
||||
StartFindService
|
status: valid
security: YES
safety: ASIL_B
|
||||
CreateProxy
|
status: valid
security: YES
safety: ASIL_B
|
||||
Subscribe
|
status: valid
security: YES
safety: ASIL_B
|
||||
GetNewSamples
|
status: valid
security: YES
safety: ASIL_B
|
||||