Lifecycle Architecture#
Lifecycle Architecture
|
status: valid
security: YES
safety: ASIL_B
|
||||
Lifecycle Feature#
Lifecycle
|
status: valid
security: YES
safety: ASIL_B
|
||||
Interfaces#
Lifecycle
Lifecycle
|
status: valid
security: YES
safety: ASIL_B
|
||||
The lifecycle interface supports the initialization, execution, and termination phases of the application. It registers the necessary signal handler for termination signals. It calls the Initialize() and Run() methods in sequence which need to be implemented by the user.
|
|||||
Initialize
|
status: valid
security: YES
safety: ASIL_B
|
||||
Initialize() method shall be implemented by the user to perform the initialization of the application.
Upon successful initialization, the Run() method is invoked next. |
|||||
Run
|
status: valid
security: YES
safety: ASIL_B
|
||||
Run() method shall be implemented by the user to perform the main execution of the application.
|
|||||
Report Running
Report Running
|
status: valid
security: YES
safety: ASIL_B
|
||||
The report running interface allows the application to report to the Launch Manager that it finished its initialization phase. The interface only offers a simple function without the sourrounding framework of the full Lifecycle interface.
|
|||||
ReportRunning
|
status: valid
security: YES
safety: ASIL_B
|
||||
The operation does not indicate the success or failure of the reporting. Failure to report would eventually result in an activation timeout and forced termination of the application process by the Launch Manager. |
|||||
Alive
Alive
|
status: valid
security: YES
safety: ASIL_B
|
||||
The alive interface allows the application to periodically report its liveness to the Launch Manager or escalate failures.
|
|||||
ReportAlive
|
status: valid
security: YES
safety: ASIL_B
|
||||
ReportAlive() operation is used by the application to cyclically indicate that it is still alive.
|
|||||
ReportFailure
|
status: valid
security: YES
safety: ASIL_B
|
||||
ReportFailure() operation is used by the application to indicate that it has encountered a failure condition.
|
|||||
Control
Control
|
status: valid
security: YES
safety: ASIL_B
|
||||
The Control interface is used by a State Manager application to control which components shall be active at any given time through the activation run targets.
|
|||||
ActivateRunTarget
|
status: valid
security: YES
safety: ASIL_B
|
||||
ActivateRunTarget() operation is used by the application to request the activation of a specific run target.
The successful execution of the request is returned asynchronously by the callback registered via RegisterActivationCallback(). |
|||||
GetActiveRunTarget
|
status: valid
security: YES
safety: ASIL_B
|
||||
GetActiveRunTarget() operation is used by the application to query the currently active run target.
|
|||||
RegisterActivationCallback
|
status: valid
security: YES
safety: ASIL_B
|
||||
RegisterActivationCallback() operation is used by the application to register a callback that will be invoked upon the successful execution of a Run Target activation.
|
|||||
Deadline
Deadline Monitor
|
status: valid
security: YES
safety: ASIL_B
|
||||
|
|||||
configure_minimum_time
|
status: valid
security: YES
safety: ASIL_B
|
||||
configure_maximum_time
|
status: valid
security: YES
safety: ASIL_B
|
||||
link_condition
|
status: valid
security: YES
safety: ASIL_B
|
||||
mark_start
|
status: valid
security: YES
safety: ASIL_B
|
||||
mark_end
|
status: valid
security: YES
safety: ASIL_B
|
||||
on_timer_expiry
|
status: valid
security: YES
safety: ASIL_B
|
||||
enable_monitoring
|
status: valid
security: YES
safety: ASIL_B
|
||||
disable_monitoring
|
status: valid
security: YES
safety: ASIL_B
|
||||
check_configuration
|
status: valid
security: YES
safety: ASIL_B
|
||||
Logical
Logical Monitor
|
status: valid
security: YES
safety: ASIL_B
|
||||
|
|||||
add_entry_point
|
status: valid
security: YES
safety: ASIL_B
|
||||
add_exit_point
|
status: valid
security: YES
safety: ASIL_B
|
||||
add_allowed_transition
|
status: valid
security: YES
safety: ASIL_B
|
||||
link_condition
|
status: valid
security: YES
safety: ASIL_B
|
||||
record_checkpoint
|
status: valid
security: YES
safety: ASIL_B
|
||||
enable
|
status: valid
security: YES
safety: ASIL_B
|
||||
disable
|
status: valid
security: YES
safety: ASIL_B
|
||||
verify
|
status: valid
security: YES
safety: ASIL_B
|
||||