class ara::diag::ServiceValidation

The method Confirmation of interface ara::diag::ServiceValidation ([SWS_DM_00775], declared in ara/diag/service_validation.h) serves as notification about the completion and result of a previously processed diagnostic request.

Usage and Semantics

The virtual callback function is called synchronously by Diagnostic Management as soon as request processing is finished. It has no return value (void) and takes two input parameters ([SWS_DM_00775]):

• status (ConfirmationStatusType): Signals the final status or the result of the service processing ([SWS_DM_00775]).
• metaInfo (const Meta Info &): Contains associated meta-information of the diagnostic request ([SWS_DM_00775]).

Error Handling and Concurrency

The function is specified as exception-safe (exception safe) and declared with the identifier noexcept ([SWS_DM_00775]). Application-side overrides must therefore not propagate exceptions to the outside. Specific error codes such as DET or DEM reports are not defined for this method. Regarding concurrency, Confirmation is classified as not thread-safe (not thread-safe) ([SWS_DM_00775]); access to application-internal states within the callback requires appropriate synchronization during concurrent sequences.

Interaction

Triggering the notification is coupled to the lifecycle end of a diagnostic request ([SWS_DM_00775]). This cycle is completed as soon as a positive or negative response has been transmitted or suppressed (AUTOSAR_AP_SWS_Diagnostics §7.3.2.1.2 “Life-cycle of a Diagnostic Conversation”). Interpretation: At module level, Diagnostic Management is likely to trigger the callback Confirmation only after transmission via the transport layer has been acknowledged by means of TransmitConfirmation and the result kTransmitOk or kTransmitFailed ([SWS_DM_00307], [SWS_DM_00351]). Question Q-97c38586ef5e3704 (open)

use

The member function Offer of class ara::diag::ServiceValidation (header ara/diag/service_validation.h) activates the forwarding of incoming diagnostic requests by the Diagnostic Manager (DM) to this specific validation handler [SWS_DM_00776]. The call is made synchronously and without input parameters via the signature ara::core::Result<void> Offer() noexcept; [SWS_DM_00776]. A ara::core::Result<void> serves as the return value, which is empty in case of success or encapsulates the occurred error code in case of an error [SWS_DM_00776].

Error handling

If the registration fails, the method returns an errored Result. If the service was already offered previously for the instance in question, the error code DiagOfferErrc::kAlreadyOffered is returned [SWS_DM_00776]. Here, rollback semantics apply, so that the previous state of the instance remains unchanged [SWS_DM_00776].

Concurrency and Limitations

The function is specified as exception-safe (exception safe), but explicitly as not thread-safe (not thread-safe) [SWS_DM_00776]. Parallel accesses to the same instance must be coordinated by the calling application. Regarding the sequence, Offer must be called before the Diagnostic Manager can forward service requests for validation [SWS_DM_00776].

Interaction

Offering interfaces via Offer is a consistent design pattern of AUTOSAR Adaptive diagnostics and is applied analogously to routines ([SWS_DM_00557], [SWS_DM_00594]), generic UDS services ([SWS_DM_00619]), DoIP functions ([SWS_DM_00725], [SWS_DM_00735]), and security access ([SWS_DM_00766]), among others. As long as an interface has not been provided via Offer, the DM discards requests or falls back on defined replacement values ([SWS_DM_01525], [SWS_DM_01527]). Conceptual parallels to ara::com are functionally motivated, but represent an independent implementation of diagnostics (AUTOSAR_AP_SWS_Diagnostics §7.3.4.1.2 “Monitors”).

use

Method StopOffer() of class ara::diag::ServiceValidation (header file ara/diag/service_validation.h) serves to disable the forwarding of incoming request messages from Diagnostic Management (DM) to the service validation instance [SWS_DM_00777]. The call is synchronous, takes no input parameters, and returns no return value [SWS_DM_00777].

Error Handling and Concurrency

The function is declared as noexcept and is considered exception safe, so that no C++ exceptions occur during execution [SWS_DM_00777]. Specific error codes or feedback to error management are not defined for this call [SWS_DM_00777].

With regard to concurrency, the method is specified as not thread-safe [SWS_DM_00777]. Interpretation: The calling application must ensure that concurrent calls to the same instance of StopOffer() are synchronized to avoid data inconsistencies. Question Q-dde3c015d30a9db1 (open)

Interaction

Offering and stopping interfaces via Offer() and StopOffer() is modeled on the familiar semantics of ara::com, but represents independent functionality in the diagnostics domain AUTOSAR_AP_SWS_Diagnostics §7.3.4.1.2 “Monitors”. The pattern for disabling request forwarding from the DM is used consistently across the standard for further diagnostic handlers, such as for authentication services [SWS_DM_01131], communication control [SWS_DM_00810], download services [SWS_DM_00793], and ECU reset requests [SWS_DM_01017].

use

The virtual method ara::diag::ServiceValidation::Validate is invoked for each incoming diagnostic request message [SWS_DM_00774]. Through it, the Diagnostic Server (DM) executes configured manufacturer-specific [SWS_DM_01252] as well as supplier-specific service checks [SWS_DM_01253] in accordance with ISO 14229-1. The assignment as manufacturer or supplier check depends on the modeling in the constructor [SWS_DM_00772].

The function accepts the diagnostic data including Service Identifier (SID) via requestData as well as meta information via metaInfo [SWS_DM_00774]. Buffer requestData remains valid until the returned ara::core::Future<void> is satisfied via the associated promise or execution is cancelled [SWS_DM_00774]. If validation completes successfully without error, the Diagnostic Server continues processing the request in accordance with ISO 14229-1 [SWS_DM_01254].

Error Handling and Boundary Conditions

If the check fails, an appropriate NRC in accordance with ISO 14229-1 must be returned using DiagUdsNrcErrc [SWS_DM_00774]. If Validate returns the error kNoProcessingNoResponse, the instance of the Diagnostic Server discards the message without further response [SWS_DM_00860].

With regard to concurrency, Validate is specified as exception safe (exception safe), but as not thread-safe (not thread-safe) [SWS_DM_00774]. Interpretation: Because the function is not thread-safe, the Diagnostic Server is likely to serialize calls to the same instance or exclude concurrent accesses. Question Q-e150c15ad709602c (open) The call context is defined by the NRC sequence of ISO 14229-1 prior to the actual service execution [SWS_DM_00772].