SNIP_CLASSIC_MODEMANAGEMENTGUIDE_SECTION_3_2_1_Interface_of_the_BSWM

3.2.1 Interface of the BSWM The interface is defined by the BswMModeRequestSource and the BswMActionListItem containers. BswMModeRequestSource is a ChoiceContainer, which can be of the following kinds: 1. C-APIs, which are defined in the specification of the BSWM. BasicSoftware- Modules can directly call C-APIs from the BSWM, which will translate it internally into a ModeRequest. For example a call to the API BswM_CanSM_CurrentState( NetworkHandleType Network, CanSM_BswMCurrentStateType CurrentState ) has to be mapped to different ModeRequestPorts depending on the parameter Network, which identifies the channel on which the event occurred. The parameter CurrentState then contains the mode which is requested. The follwing mode request types are defined: (a) BswMCanSMIndication (b) BswMEcuMWakeupSource (c) BswMEthSMIndication (d) BswMFrSMIndication (e) BswMLinSMIndication (f) BswMLinScheduleIndication (g) BswMLinTpModeRequest (h) BswMNvMRequest (i) BswMWdgMRequestPartitionReset (j) BswMComMIndication (k) BswMGenericRequest Guide to Modemanagement V1.0.0. R4.0 Rev 3 2. RPorts typed by a SenderReceiverInterface. (a) BswMSwcModeRequest: For each container of this type the BSWM has to create a corresponding RPort in its Service Component Description. 3. RPorts typed by a ModeSwitchInterface. (a) BswMSwcModeNotification: For each container of this type the BSWM has to create a corresponding RPort in its Service Component Description. As it is typed by a ModeSwitchInterface the BSWM acts as a mode user of this ModeMachineInstance and is informed if the mode manager performs an rte_switch. 4. RequiredModeDeclarationGroupPrototypes (a) BswMBswModeNotification: For each container of this type the BSWM has to create a corresponding RequiredModeDeclarationGroupPrototype in the role RequiredModeDeclarationGroup in its Basic Software Module Description. The BSWM also acts as a mode user, but the ModeMachineInstance is maintained by the Schedule Manager. The BSWM therefore gets informed if the mode manager e.g. another Basic Software Module performs a SchM_Switch call. BswMActionListItems can be of the following kinds: 1. C-APIs from other BSWM Modules, which are called directly during the execution of an ActionList. (a) BswMUserCall (b) BswMComMAllowCom (c) BswMComMModeSwitch (d) BswMDeadlineMonitoringControl (e) BswMLinScheduleSwitch (f) BswMNMControl (g) BswMPduGroupSwitch (h) BswMPduRouterControl (i) BswMResetSignalInitValues (j) BswMRteSwitch (k) BswMSchMSwitch (l) BswMTriggerIPduSend (m) BswMTriggerSlaveRTEStop (n) BswMTriggerStartUpPhase2 Guide to Modemanagement V1.0.0. R4.0 Rev 3 2. PPorts typed by a ModeSwitchInterface (a) BswMRteSwitch : For each container of this type the BSWM has to create a corresponding PPort in its Service Component Description. 3. ProvidedModeDeclarationGroupPrototypes (a) BswMSchMSwitch: For each container of this type the BSWM has to create a corresponding ProvidedModeDeclarationGroupPrototype in the role ProvidedModeDeclarationGroup in its Basic Software Module Description. The BSWM also acts as a mode manager, but the ModeMachineInstance is maintained by the Schedule Manager. Listing 3.1: Configuration of a ModeRequestSource in pseudo code request CanSMIndication Can1_indication { processing IMMEDIATE initialValue "CANSM_BSWM_NO_COMMUNICATION" source CanSM.CanStateManagerConfiguration.Can1StateManagerNetwork }