SNIP_CLASSIC_COMM_SECTION_7_Functional_specification

7 Functional specification The Communication Manager (ComM) module simplifies the resource management for the users, whereat users may be runnable entities, SW-Cs, the BswM (e.g. SW-C request via BswM) or DCM (communication needed to diagnostic purpose). [SWS_ComM_00867] Upstream requirements: SRS_ModeMgm_09083 ⌈The ComM shall provide three different Communication Modes. The highest Communication Mode shall be COMM_FULL_COMMUNICATION. The lowest Communication Mode shall be COMM_NO_COMMUNICATION.⌋ [SWS_ComM_00151] Upstream requirements: SRS_ModeMgm_09246 ⌈For a user it shall only be possible to request the Communication Modes COMM_NO_COMMUNICATION and COMM_FULL_COMMUNICATION (see ComM_RequestComMode(), [SWS_ComM_00110]).⌋ Rationale for [SWS_ComM_00151]: • The Communication Mode COMM_SILENT_COMMUNICATION and sub- modes/sub-states are only necessary for synchronization with AUTOSAR NM. • The Communication Mode COMM_FULL_COMMUNICATION_WITH_WAKEUP_REQUEST is only necessary to request the lower layer to trigger a wake-up on the network (e.g. Ethernet hardware compliant to [2, OA TC10]). This mode could not be requested by a user. [SWS_ComM_00868] Upstream requirements: SRS_ModeMgm_09083 ⌈The Communication Mode COMM_SILENT_COMMUNICATION shall only be used for network synchronization.⌋ Note: The possibility to request COMM_SILENT_COMMUNICATION mode is removed since release 2.0. Comment: • The ComM module allows querying the Communication Mode requested by a particular user (see ComM_GetRequestedComMode(), [SWS_ComM_00079]). • The ComM module allows querying the actual Communication Mode of a channel if the user is assigned to channel(see ComM_GetCurrentComMode(), [SWS_ComM_00083]) • The ComM module allows querying for the current PNC mode if the user is assigned to a PNC (see ComM_GetCurrentPNCComMode(), [SWS_ComM_91002]) [SWS_ComM_00845] Upstream requirements: SRS_ModeMgm_09083 ⌈In COMM_FULL_COMMUNICATION mode, the ComM module shall allow transmission and reception on the affected physical channel.⌋ [SWS_ComM_00846] Upstream requirements: SRS_ModeMgm_09083 ⌈In COMM_NO_COMMUNICATION mode, the ComM module shall prevent transmission and reception on the affected physical channel.⌋ [SWS_ComM_00686] Upstream requirements: SRS_ModeMgm_09078 ⌈If at least one of multiple independent user requests demands a higher Communication Mode (see [SWS_ComM_00867] and [SWS_ComM_00868]), the ComM module shall set this higher Communication Mode as the target Communication Mode.⌋ Rationale for [SWS_ComM_00686]: ComM coordinates multiple independent user requests according to the "highest wins" strategy: COMM_FULL_COMMUNICATION Communication Mode overrules COMM_NO_COMMUNICATION. [SWS_ComM_00500] Upstream requirements: SRS_ModeMgm_09246 ⌈The ComM module shall not queue user requests. The latest user request of the same user shall overwrite an old user request even if the request is not finished.⌋ [SWS_ComM_00866] Upstream requirements: SRS_ModeMgm_09083 ⌈If configuration parameter ComMNmVariant=FULL|LIGHT|NONE ([ECUC_ComM_00568]), an DCM_ActiveDiagnostic indication shall be treated as a COMM_FULL_COMMUNICATION request for the specified communication channel (see ComM_DCM_ActiveDiagnostic(channel), [SWS_ComM_00873]).⌋ Rationale for [SWS_ComM_00866]: If more channels needed for diagnostic purpose, DCM needs to indicate DCM_ActiveDiagnostic for each channel. [SWS_ComM_00092] Upstream requirements: SRS_ModeMgm_09078, SRS_ModeMgm_09080, SRS_ModeMgm_- 09083, SRS_ModeMgm_09172 ⌈There shall be one Communication Mode target state (evaluated according to [SWS_ComM_00686]) per communication channel. This target mode can differ temporarily from the actual mode controlled by the corresponding Bus State Manager module.⌋ Comment: Mode switching by the corresponding Bus State Manager module takes time and a mode inhibition can be active. [SWS_ComM_00084] Upstream requirements: SRS_ModeMgm_09149 ⌈The ComM module shall propagate a call of ComM_GetCurrentComMode() (see [SWS_ComM_00083]) to the Bus State Manager module(s) for the channel(s) the user are configured to (see also [SWS_ComM_00176] and [SWS_ComM_00798])⌋ Rationale for [SWS_ComM_00084]: State requests have to be propagated to the corresponding Bus State Manager module since the ComM module does not control the actual bus state. Comment: This feature is not used by a "normal SW-C" because they don’t have knowledge about channels. This feature is necessary for privileged SW-Cs, which (have to) know about the system topology, e.g. system diagnostic functions. [SWS_ComM_00884] ⌈The ComM module shall store status if communication for a channel is allowed or not allowed in separate CommunicationAllowed boolean flags for all supported channels. The default value after ComM initialization shall be communication is not allowed, i.e. CommunicationAllowed is set to FALSE.⌋ [SWS_ComM_00885] ⌈Status changes for communication allowed or not allowed in [SWS_ComM_00884] shall be provided to ComM in ComM_CommunicationAllowed (<channel>, TRUE|FALSE) ([SWS_ComM_00871]) indications.⌋