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.
Allows applications to provide system-specific timestamps for security events of the IdsM.
AI-GENERATEDunreviewedModel: gemini-3.8-flash-medium · Effort: medium · Temperature: not controllable · Prompt: 3e143c113da9ProvenanceOpen questions (2)
translated from the German guidegemini-3.8-flash-low · 2026-10-13 · German original
Allows applications to provide system-specific timestamps for security events of the IdsM.
The class ara::idsm::TimestampProvider provides an interface through which applications can feed timestamps for the IdsM module via a modeled PPort [SWS_AIDSM_10400]. Activation and deactivation of the query callbacks take place via the methods Offer() and StopOffer()[SWS_AIDSM_10408][SWS_AIDSM_10409]. Instances cannot be copied, support move semantics, and require external synchronization for methods without guaranteed thread safety.
Context
The class ara::idsm::TimestampProvider serves as an interface for providing timestamps for the Intrusion Detection System Manager (IdsM) module within the AUTOSAR Adaptive Platform [SWS_AIDSM_10400]. Security-relevant events and logs in the IdsM require reliable time information, which is obtained by this provider class from the platform or an application-specific time source. An instance of TimestampProvider is bound to a PPort modeled via a ara::core::InstanceSpecifier[SWS_AIDSM_10401]. Since the method GetTimestamp() is defined as a pure virtual callback function [SWS_AIDSM_10407], TimestampProvider acts as an abstract base class from which concrete implementations must be derived.
Lifecycle
Creation of a timestamp provider takes place explicitly via the constructor specifying the associated ara::core::InstanceSpecifier[SWS_AIDSM_10401]. This constructor is declared as thread-safe. Copy operations are completely prevented: both the copy constructor [SWS_AIDSM_10404] and the copy assignment operator [SWS_AIDSM_10406] are deleted (= delete). Instances thus possess a unique identity and cannot be duplicated.
In contrast, the class supports move semantics: the move constructor transfers existing resources to a new object in a thread-safe manner [SWS_AIDSM_10403]. Move assignment via operator= is also available, but in contrast to the constructor is not thread-safe [SWS_AIDSM_10405]. The lifecycle of active service provision is controlled explicitly after instantiation: registration for the IdsM is activated via the method Offer()[SWS_AIDSM_10408]. With StopOffer(), provision is prevented again [SWS_AIDSM_10409]. The instance is released via the virtual destructor [SWS_AIDSM_10402], which is specified as not thread-safe. Interpretation: prior to destroying an instance, StopOffer() is typically likely to be called to ensure that no more pending calls occur through the IdsM. Question Q-fcf21d9d93d053a6 (open)
Usage Path
Typical usage requires deriving an application-specific class that overrides the method GetTimestamp() and returns the current timestamp as TimestampType[SWS_AIDSM_10407]. Once the instance has been created for the corresponding port [SWS_AIDSM_10401], the application signals operational readiness by calling Offer()[SWS_AIDSM_10408]. From this point onward, the IdsM can autonomously invoke the callback method GetTimestamp() to locate events in time. If the service is to be terminated or the component shut down, StopOffer() revokes the availability of the interface [SWS_AIDSM_10409].
All methods of the interface are declared as noexcept and do not throw C++ exceptions. Errors during activation of service provision are instead conveyed via the return type ara::core::Result<void> of Offer()[SWS_AIDSM_10408]. Interpretation: if registration with the communication or platform framework fails (for example, due to an unsuitable port configuration), the returned Result contains a corresponding error code that must be checked before further use. Question Q-5a971906b458dd6f (open)
Special attention is required for the concurrency behavior: neither the destructor [SWS_AIDSM_10402] nor the methods Offer()[SWS_AIDSM_10408], StopOffer()[SWS_AIDSM_10409], operator=(&&)[SWS_AIDSM_10405], or GetTimestamp()[SWS_AIDSM_10407] are classified as thread-safe. Callers must therefore ensure that lifecycle operations and callback processing occur thread-synchronized and that no data races arise.
This guide is based on the requirements of the AUTOSAR specification for the idsm module (R25-11).
AI-GENERATEDunreviewedModel: gemini-3.8-flash-medium · Effort: medium · Temperature: not controllable · Prompt: 8a357670f42bProvenanceOpen questions (1)
translated from the German guidegemini-3.8-flash-low · 2026-10-13 · German original
The synchronous member function Offer provides the timestamp service and enables subsequent calls to GetTimestamp for the Intrusion Detection System Manager (IdsM) [SWS_AIDSM_10408]. Declaration is provided via header ara/idsm/timestamp_provider.h without passing parameters [SWS_AIDSM_10408].
Error Handling and Semantics
The function is declared as noexcept and therefore throws no C++ exceptions [SWS_AIDSM_10408]. The success of the provision as well as any error states are returned to the caller encapsulated in return type ara::core::Result<void>[SWS_AIDSM_10408].
Concurrency and Limitations
Regarding concurrency, the function is explicitly specified as not thread-safe (not thread-safe) [SWS_AIDSM_10408]. Concurrent invocation from different threads must be synchronized on the application side. Interpretation: The call is likely to take place typically during the initialization phase, as it establishes the prerequisite for subsequent queries by the IdsM [SWS_AIDSM_10408]. Question Q-a9b16a23962a092f (open)
Interaction
The provision pattern follows the module convention of aidsm: Equivalent to this interface, function Offer in ara/idsm/context_data_provider.h enables IdsM access to ModifyContextData[SWS_AIDSM_10507], while Offer in ara/idsm/qualified_events_receiver.h permits the IdsM to execute OnEventQualification[SWS_AIDSM_10808].
This usage note was generated automatically based on the AUTOSAR specification.
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: 1890401ec4bdProvenance
translated from the German guidegemini-3.8-flash-low · 2026-10-13 · German original
The function StopOffer according to [SWS_AIDSM_10409] is declared in header ara/idsm/timestamp_provider.h and serves to terminate provision of the timestamp service for the Intrusion Detection System Manager (IdsM). Through the synchronous call without parameters and without return value, it is governed that subsequent calls to GetTimestamp by the IdsM are prevented.
Concurrency and Limitations
For the function, it is explicitly defined that it is not thread-safe (not thread-safe) [SWS_AIDSM_10409]. Callers must therefore ensure that calls to StopOffer occur serialized or are not executed concurrently with other activities of the same provider. Since the signature is declared with noexcept, the function does not throw exceptions.
Interaction and Distinction
In module aidsm, functions with the same name exist for other interfaces that follow an analogous pattern, but affect separate functional areas:
[SWS_AIDSM_10508]: StopOffer in header ara/idsm/context_data_provider.h prevents IdsM calls to ModifyContextData.
[SWS_AIDSM_10809]: StopOffer in header ara/idsm/qualified_events_receiver.h prevents IdsM calls to OnEventQualification.
The present function [SWS_AIDSM_10409] refers exclusively to timestamp_provider and selectively prevents timestamp queries of the IdsM.
This usage note was generated automatically based on the specification data.
Request a governed re-review of this record. The record is not changed immediately.
gemini-3.8-flash-low· 2026-10-13 · German original