SNIP_ADAPTIVE_CAN_FIGURE_Figure_5_5

Figure 5.5: StateMachine interactions T o differentiate between the pure customer written StateManagement and the StateMachine approach, which is provided by stack vendor new interfaces were introduced. • StateMachineService::RequestState, to be used by SMControlApplication to request a certain state • UpdateAllowedService::UpdateAllowed, which will be used by SMControlApplication to signal StateManagement if under current conditions an update is allowed or not The number of StateMachines, which can be configured by the user is not limited. T o cover the interaction with UpdateAndConfigurationManagement each StateMachine has to have a number of mandatory states: • PrepareUpdate, where - at least - all managed FunctionGroups and StateMachines shall be set to Off state, respectively stopped • VerifyUpdate, where - at least - all managed FunctionGroups and StateMachines shall be set to Verify state, respectively started in Verify state • PrepareRollback, where - at least - all managed FunctionGroups and StateMachines shall be set to Off state, respectively stopped The request of the corresponding states will be done within StateManagement, following the needed sequence from UpdateAndConfigurationManagement. Please note that the interaction with DiagnosticManagement for the StateMachine approach will be defined within future release of Autosar.