SNIP_ADAPTIVE_CAN_FIGURE_Figure_7_22_EXECUTIONMANAGEMENT

Figure 7.22: Sequence Diagram of the Synchronization Control Messages with single DeterministicSyncMaster For event-triggered activation, a specific policy of the synchronization should be provided. The policy is highly dependent on vendor solution and requirements, for example, the synchronization response is sent to the DeterministicClients only if the synchronization requests from all the processes are received. There can be more complicated policies, e.g. the match of 2 out of 3 synchronization requests are received before the given deadline, which is also known as the M-out-of-N (MooN) policy . For periodic activation, the DeterministicClients require a single synchronization for the first ara::exec::DeterministicClient::WaitForActivation call that is initiated after the execution of kInit or kServiceDiscovery cycle (see [SWS_EM_01304] for service modification). The activation response includes a global time stamp for the activation of the first kRun cycle, which should also give a reasonable time buffer for receiving the activation response for the DeterministicClients through the channel. All DeterministicClients will count on local time until the activation time is reached and then starts kRun. Further calls of ara::exec::DeterministicClient::WaitForActivation will not send any synchronization request, but just return when the predefined deadline that was configured with cycleTimeValue property is reached by the local time counter (see [SWS_EM_01351]). The handling of missed deadline in the kRun cycles for periodic activation is described in [SWS_EM_01352]. For both periodic and event-triggered activation, a set of parameters need to be defined before the DeterministicSyncMaster starts. [SWS_EM_01320]{OBSOLETE} Number of DeterministicClients⌈The number of DeterministicClients that are connected to the DeterministicSyncMaster shall be defined by attribute numberOfConnectedClients.⌋(RS_EM_00050, RS_EM_00051, RS_EM_00053)