class apext::com::secoc::ComSecOcFvmException

In module com, the class apext::com::secoc::ComSecOcFvmException serves as a specialized exception class for signaling errors that occur within the SecOC Freshness Value Manager [SWS_CM_12512]. It inherits from ara::core::Exception and is instantiated and thrown by the Freshness Value Manager to transmit error states in a structured manner to higher communication layers. Its constructor obligatorily accepts a ara::core::ErrorCode and is declared as noexcept, thereby guaranteeing exception-safe creation of the error object without secondary errors [SWS_CM_12513].

more ›

Context

The class apext::com::secoc::ComSecOcFvmException is a specialized exception class of the AUTOSAR Adaptive Platform in module com [SWS_CM_12512]. It primarily serves to signal error states that occur within the SecOC Freshness Value Manager (FVM) (AUTOSAR_AP_SWS_CommunicationManagement §C.2.4 “Class: ComSecOcFvmException”). By deriving from the standard base class ara::core::Exception, ComSecOcFvmException integrates into the general error handling model of the Adaptive Platform and acts as a standardized information carrier for exceptional conditions when securing communication using SecOC.

Essentially three components act as interaction partners: the SecOC Freshness Value Manager itself, which triggers the exception in the event of an error, the calling functional communication layer or application that processes SecOC-secured data, and the FVM error domain, which is included via the header file apext/com/secoc/fvm_error_domain.h [SWS_CM_12513]. The class thus represents the link between the internal error states of freshness management and the higher-level software layers.

Lifecycle

Instantiation of ComSecOcFvmException occurs on demand precisely when an unrecoverable error is detected during the determination or verification of freshness values. For this purpose, the class provides an explicit constructor that accepts a ara::core::ErrorCode [SWS_CM_12513].

This constructor is declared as noexcept [SWS_CM_12513]. This guarantees that object creation itself under no circumstances fails or throws further exceptions, thereby adhering to the specification of exception safety (exception safe) [SWS_CM_12513]. With regard to lifecycle and ownership, the exception is created and thrown by value. On the receiver side, it is presumably caught as a constant reference (const ComSecOcFvmException& or polymorphically as const ara::core::Exception&). Question Q-d170140b08fe9ca0 (open)

As soon as the corresponding exception handling block (catch) has finished executing, the exception instance is automatically destroyed. With regard to concurrency, instances of the exception are likely to be processed thread-locally in the exception context of the respective thread. Question Q-bd368a082b887d14 (open)

Usage Path

The typical usage path extends from the detection of a freshness error to the targeted reaction by the higher-level communication layer.

Sequence diagram: Exception handling sequence by the Freshness Value Manager with ComSecOcFvmException. Sources: [SWS_CM_12512], [SWS_CM_12513], AUTOSAR_AP_SWS_CommunicationManagement §C.2.4

First, the communication module or application requests a freshness value from the Freshness Value Manager or passes one for validation as part of SecOC processing. If this operation fails—for example due to synchronization problems or invalid counter values—the Freshness Value Manager instantiates the exception class ComSecOcFvmException, passing the concrete error code [SWS_CM_12513]. The exception is thrown immediately after construction. The caller catches the exception in the appropriate handler and can query the contained ara::core::ErrorCode in order to react appropriately to the impairment of communication security [SWS_CM_12512].

Error Scenarios

Since ComSecOcFvmException itself represents the transport medium for error signaling, the error scenarios focus on the semantic content of the encapsulated error code. The class strictly requires a ara::core::ErrorCode for creation [SWS_CM_12513]. The header assignment to apext/com/secoc/fvm_error_domain.h demonstrates that these error codes originate from a dedicated FVM error domain [SWS_CM_12513].

An essential precondition for creation is that the triggering context provides an initialized error code. As a postcondition, the resulting object contains the complete error information of the respective error domain. A critical error scenario involving the emergence of secondary exceptions during exception creation is precluded by the noexcept guarantee of the constructor [SWS_CM_12513]. This reliably prevents premature termination of the process via std::terminate as a result of a failure in the error handling path.