Diese Seite wurde vollständig KI-generiert auf Basis von SWS IntrusionDetectionSystemManager (R25-11) — kein offizieller AUTOSAR-Text und keine automatisch extrahierte API-Seite wie die übrigen Module. Als Interpretation gekennzeichnete Aussagen sind Schlussfolgerungen aus den Quellen.
Receives qualified security events from the IdsM via a modeled P-Port and forwards them to callbacks.
AI-GENERATEDunreviewedModel: gemini-3.8-flash-medium · Effort: medium · Temperature: not controllable · Prompt: 46b1b6dbd698ProvenanceOpen questions (2)
translated from the German guidegemini-3.8-flash-low · 2026-10-13 · German original
Receives qualified security events from the IdsM via a modeled P-Port and forwards them to callbacks.
The abstract class enables the reception of qualified security events from the IdsM via a modeled PPort [SWS_AIDSM_10800]. Applications derive their own receiver class, instantiate it with an instance specifier, and activate event delivery via Offer()[SWS_AIDSM_10801]. Incoming events are received via abstract callback methods with optional context and time data. Because essential state and callback methods are not thread-safe, the instance requires coordinated lifecycle management.
Context
The class ara::idsm::QualifiedEventsReceiver represents the functional interface for receiving qualified security events (Qualified Security Events, QSEv) in module idsm of the AUTOSAR Adaptive Platform [SWS_AIDSM_10800]. It serves as an application-side endpoint for a provided port (PPort) modeled in the software design [SWS_AIDSM_10801].
The concept is based on the principle of an abstract base class: ara::idsm::QualifiedEventsReceiver declares pure virtual callback methods [SWS_AIDSM_10807], [SWS_AIDSM_10810]. The main interaction partners are the adaptive application, which implements a specialized subclass, and the Intrusion Detection System Manager (IdsM), which detects qualified security events and forwards them to the instance via the PPort.
Lifecycle
Creation of a receiver is performed by instantiating a class derived from QualifiedEventsReceiver while specifying an ara::core::InstanceSpecifier that references the modeled PPort [SWS_AIDSM_10801]. This parameterized constructor is specified as thread-safe [SWS_AIDSM_10801].
Regarding ownership and value semantics, the class is strictly designed as move-only. Both the copy constructor [SWS_AIDSM_10804] and the copy assignment operator [SWS_AIDSM_10806] are deleted (= delete). However, a transfer of ownership is possible: the move constructor is implemented as thread-safe [SWS_AIDSM_10803], whereas the move assignment operator is not thread-safe [SWS_AIDSM_10805].
The functional lifecycle is divided into two main phases:
Offer: Immediately after instantiation, no events are delivered yet. Only calling Offer() enables the acceptance of events and authorizes calls to the callback methods by the IdsM [SWS_AIDSM_10808].
Deactivation: Acceptance of further events is prevented via the method StopOffer()[SWS_AIDSM_10809].
Destruction takes place via the virtual destructor ~QualifiedEventsReceiver()[SWS_AIDSM_10802]. Since the destructor is not thread-safe, StopOffer() should always be executed prior to releasing the receiver object in order to reliably rule out parallel executions of callbacks during the destruction process.
Usage Path
The typical sequence for using the receiver comprises derivation, offering, and orderly teardown:
Class definition: The application defines a subclass and overrides the two pure virtual methods OnEventQualification() for events with unversioned context data [SWS_AIDSM_10807] and for versioned or empty context data [SWS_AIDSM_10810].
Instantiation: The subclass is instantiated, passing the instance specifier of the port to the base constructor [SWS_AIDSM_10801].
Activation via Offer: The application calls Offer() to start event acceptance [SWS_AIDSM_10808]. The returned ara::core::Result<void> confirms the successful offer.
Event reception: If the IdsM detects a qualified security event, it calls the appropriate callback method depending on the data format:
OnEventQualification(EventIdType, ara::core::Optional<ContextDataType>, ara::core::Optional<TimestampType>) for unversioned data [SWS_AIDSM_10807].
OnEventQualification(EventIdType, ara::core::Optional<VersionedContextDataType>, ara::core::Optional<TimestampType>) for versioned context data or event-specifically missing data [SWS_AIDSM_10810].
Deactivation and destruction: Prior to terminating the application, StopOffer() is called [SWS_AIDSM_10809] and the object is released regularly via the destructor [SWS_AIDSM_10802].
During use, various error conditions and concurrency conflicts can occur:
Failure during Offer(): The method Offer() returns a ara::core::Result<void>[SWS_AIDSM_10808]. Interpretation: If the modeled port cannot be bound in the system or registration with the IdsM fails, the Result object returns an error. Question (open) The application may only assume that callbacks will be triggered after successful verification.
Missing context or timestamp values: In both callback signatures, context data and timestamps are encapsulated in ara::core::Optional ([SWS_AIDSM_10807], [SWS_AIDSM_10810]). Unchecked access without validation (such as to empty context data) leads to errors in the processing logic of the application.
Klasse zum Empfangen qualifizierter Security Events von IdsM.
AI-GENERATEDunreviewedModel: gemini-3.8-flash-medium · Effort: medium · Temperature: not controllable · Prompt: b8f71cd4e8edProvenance
translated from the German guidegemini-3.8-flash-low · 2026-10-13 · German original
The class QualifiedEventsReceiver serves to receive qualified Security Events from the Intrusion Detection System Manager (IdsM) [SWS_AIDSM_10800] in the context of header ara/idsm/qualified_events_receiver.h.
Usage and instantiation: An instance is created via the constructor QualifiedEventsReceiver(const ara::core::InstanceSpecifier& instance) for a modeled PPort [SWS_AIDSM_10801]. The class model enforces move semantics: The copy constructor [SWS_AIDSM_10804] and the copy assignment operator [SWS_AIDSM_10806] are deleted (= delete). Instead, instances can be transferred via the move constructor [SWS_AIDSM_10803] or the move assignment [SWS_AIDSM_10805].
Concurrency and thread safety: The creation of the instance via the parameterized constructor [SWS_AIDSM_10801] and moving by means of the move constructor [SWS_AIDSM_10803] are specified as thread-safe. In contrast, destruction via the virtual destructor [SWS_AIDSM_10802] and move assignment via operator=[SWS_AIDSM_10805] are defined as not thread-safe (not thread-safe). Callers must therefore ensure that assignment and destruction operations are not executed concurrently on the same object.
Error Handling: All specified lifecycle and assignment functions—constructors, destructor, and move assignment—are marked with noexcept and therefore do not throw exceptions.
This text was generated by an AI and serves as guidance. The AUTOSAR specification is authoritative.
Implementer's Guide to follow (complexity I1)
Request a governed re-review of this record. The record is not changed immediately.
AI-GENERATEDunreviewedModel: gemini-3.8-flash-medium · Effort: medium · Temperature: not controllable · Prompt: 07e3f8fb1ccdProvenanceOpen questions (1)
translated from the German guidegemini-3.8-flash-low · 2026-10-13 · German original
The synchronous method Offer() from header ara/idsm/qualified_events_receiver.h is called without input parameters and serves to indicate readiness to receive qualified security events [SWS_AIDSM_10808]. Upon successful call, the Intrusion Detection System Manager (IdsM) is permitted to subsequently transmit qualified events to the instance via the callback method OnEventQualification[SWS_AIDSM_10808].
The signature declares the function with noexcept, so that no C++ exceptions occur, and provides ara::core::Result<void> as return type [SWS_AIDSM_10808]. Since the specification does not list any specific error codes, an error conveyed in the result is likely to indicate that provision in the IdsM has failed. Question Q-2eca6bb6ce27ec78 (open) Regarding concurrency, the operation is explicitly specified as not thread-safe[SWS_AIDSM_10808]. Callers must therefore ensure that calls to Offer() are not executed unguarded in parallel with other methods of the instance.
The provision pattern corresponds to the standardized interaction in module aidsm, where service providers actively enable their services for the IdsM:
In header ara/idsm/timestamp_provider.h, the function Offer() enables the provision of timestamps and allows the IdsM to call GetTimestamp[SWS_AIDSM_10408].
In header ara/idsm/context_data_provider.h, Offer() enables the modification of context data by allowing the IdsM calls to ModifyContextData[SWS_AIDSM_10507].
This usage note was created automatically based on the specification requirements of AUTOSAR R25-11.
Request a governed re-review of this record. The record is not changed immediately.
Abstrakter Callback für ein QSEv mit unversionierten Kontextdaten.
AI-GENERATEDunreviewedModel: gemini-3.8-flash-medium · Effort: medium · Temperature: not controllable · Prompt: c315ee5144f2Provenance
translated from the German guidegemini-3.8-flash-low · 2026-10-13 · German original
The pure virtual function OnEventQualification is defined in the header ara/idsm/qualified_events_receiver.h and serves as an abstract callback for receiving qualified security events (QSEv) with unversioned context data [SWS_AIDSM_10807].
Usage and parameters: The method is called by the Intrusion Detection System Manager (IdsM) upon the occurrence of a qualified event. It declares the following interface parameters [SWS_AIDSM_10807]:
event (EventIdType): Unique identifier of the qualified event.
contextData (ara::core::Optional<ContextDataType>): Optional unversioned context data of the event.
timestamp (ara::core::Optional<TimestampType>): Optional timestamp of the event occurrence.
The method has no return value (void) and throws no exceptions (noexcept) [SWS_AIDSM_10807].
Concurrency: The callback method is specified as not thread-safe (not thread-safe) [SWS_AIDSM_10807]. Application-side implementations must therefore ensure that concurrent calls or accesses are synchronized.
Lifecycle and interaction: Calls of OnEventQualification by the IdsM are state-dependent: they are only permissible after activation via Offer[SWS_AIDSM_10808] and are prevented by StopOffer[SWS_AIDSM_10809]. For events with versioned context data or without context data, a separate overload of OnEventQualification with VersionedContextDataType exists [SWS_AIDSM_10810].
This usage note was generated by an AI and is based exclusively on specification data from AUTOSAR R25-11.
Implementer's Guide to follow (complexity I1)
Request a governed re-review of this record. The record is not changed immediately.
Abstrakter Callback für ein QSEv mit versionierten oder ohne Kontextdaten.
AI-GENERATEDunreviewedModel: gemini-3.8-flash-medium · Effort: medium · Temperature: not controllable · Prompt: 34e6800f4e26ProvenanceOpen questions (1)
translated from the German guidegemini-3.8-flash-low · 2026-10-13 · German original
use
The pure virtual member function OnEventQualification serves as an application-specific callback for notification of a qualified security event (QSEv) with versioned or without context data [SWS_AIDSM_10810]. The function declares the following input parameters:
event (EventIdType): Identifier of the qualified event [SWS_AIDSM_10810].
contextData (ara::core::Optional<VersionedContextDataType>): Optional versioned context data of the event [SWS_AIDSM_10810].
timestamp (ara::core::Optional<TimestampType>): Optional timestamp of the event [SWS_AIDSM_10810].
The function does not return a value (void) and is declared with the specifier noexcept[SWS_AIDSM_10810].
Interaction and Lifecycle
For the IdsM to be able to execute calls to OnEventQualification, the receiver must first activate the interface via Offer[SWS_AIDSM_10808]. Subsequent calls to the callback function are prevented again with StopOffer[SWS_AIDSM_10809]. While SWS_AIDSM_10810 processes versioned context data, the alternative signature according to [SWS_AIDSM_10807] exists for unversioned data.
Concurrency and Error Handling
The function is specified as not thread-safe (not thread-safe) [SWS_AIDSM_10810]. Presumably, the calling instance of the IdsM or the concrete implementation must ensure appropriate synchronization if calls occur concurrently. Question Q-6b9e9525b682ad70 (open) Since the signature is defined as noexcept and does not return an error code, no exceptions may escape from within the callback implementation [SWS_AIDSM_10810].
This usage note was created automatically based on the specification.
Implementer's Guide to follow (complexity I1)
Request a governed re-review of this record. The record is not changed immediately.
Unterbindet IdsM-Aufrufe von OnEventQualification.
AI-GENERATEDunreviewedModel: gemini-3.8-flash-medium · Effort: medium · Temperature: not controllable · Prompt: 8389f042ab00ProvenanceOpen questions (1)
translated from the German guidegemini-3.8-flash-low · 2026-10-13 · German original
The function StopOffer in header ara/idsm/qualified_events_receiver.h is called according to [SWS_AIDSM_10809] to stop offering the receiver service for qualified security events. The synchronous call ensures that the Intrusion Detection System Manager (IdsM) subsequently forwards no further calls to the callback method OnEventQualification.
Regarding usage and interface behavior, the following properties apply:
Signature and error handling: The function takes no parameters and has no return value (void StopOffer() noexcept;). Since it is declared as noexcept, it throws no exceptions and provides no error codes [SWS_AIDSM_10809].
Concurrency: The operation is explicitly declared in the specification as not thread-safe[SWS_AIDSM_10809]. Calling components must therefore ensure that calls to StopOffer are externally synchronized with respect to other accesses to the same instance.
Call context: The call should expediently take place within the scope of an orderly shutdown or during the deregistration of the event receiver before the instance is destroyed. Question Q-77dc1d3a09426bdf (open)
The design pattern exists analogously in other service providers of module aidsm. Thus, StopOffer in header ara/idsm/timestamp_provider.h terminates subsequent calls to GetTimestamp by the IdsM [SWS_AIDSM_10409], whereas the function of the same name in ara/idsm/context_data_provider.h prevents future calls to ModifyContextData[SWS_AIDSM_10508]. Both related interfaces are likewise implemented as not thread-safe.
This usage note was created automatically and relies exclusively on the AUTOSAR specification.
Request a governed re-review of this record. The record is not changed immediately.
gemini-3.8-flash-low· 2026-10-13 · German original