class ara::rds::IEEE1722DatagramTSCF

The class ara::rds::IEEE1722DatagramTSCF represents IEEE 1722 TSCF datagrams in the Raw Data Stream (RDS) module of the AUTOSAR Adaptive Platform and is provided via header ara/rds/raw_data_stream_IEEE1722.h [SWS_RDS_90275]. As an essential interface property, it has a virtual destructor that ensures polymorphic destruction via base pointers AUTOSAR_AP_SWS_RawDataStream §1 “Virtual destructor of the IEEE 1722 datagram type”. As a central boundary condition, the declaration with noexcept guarantees completely exception-free cleanup of all resources at the end of the object lifecycle.

more ›

Context

Within the AUTOSAR Adaptive Platform, the class ara::rds::IEEE1722DatagramTSCF represents a specific data format for IEEE 1722 datagrams, more specifically for the Time-Sensitive Control Format (TSCF) according to specification AUTOSAR_AP_SWS_RawDataStream §1 “Virtual destructor of the IEEE 1722 datagram type”. This data type is located in the Raw Data Stream (RDS) module, which enables the acquisition and forwarding of unformatted or protocol-specific data streams in adaptive vehicle applications. For inclusion and usage of the class, provision via the standardized header #include "ara/rds/raw_data_stream_IEEE1722.h" in namespace ara::rds is specified [SWS_RDS_90275].

As a structured representation of an IEEE 1722 TSCF datagram, the class serves to map control and sensor data transmitted over time-critical network connections such as Ethernet in the automotive domain. Interpretation: The class is likely to act as a standardized carrier for TSCF payload data within the data stream processing of the RDS module to allow application-specific components uniform access to corresponding datagrams, as indicated by the type name AUTOSAR_AP_SWS_RawDataStream §1 “Virtual destructor of the IEEE 1722 datagram type”. Question Q-64f198106e28f54e (open) In doing so, it functions in the C++ type system as a defined data or interface type that is integrated into data stream pipelines of the RDS subsystem [SWS_RDS_90275].

Lifecycle

The lifecycle of instances of class ara::rds::IEEE1722DatagramTSCF comprises their creation, usage for data transmission, and subsequent release. The specification explicitly defines a virtual destructor for the class ~IEEE1722DatagramTSCF() noexcept [SWS_RDS_90275]. The presence of a virtual destructor proves that the class is designed for polymorphic usage AUTOSAR_AP_SWS_RawDataStream §1 “Virtual destructor of the IEEE 1722 datagram type”. Interpretation: Instances of ara::rds::IEEE1722DatagramTSCF are likely to act as a base class or be managed via pointers or references to higher-level datagram interfaces, thereby ensuring safe destruction of derived classes via base class pointers. Question Q-6f91c3dc1d6d129e (open)

With regard to memory management, objects of the class can be instantiated either on the stack or dynamically on the heap depending on the use case and data stream architecture. When leaving scope or upon explicit release, the virtual destructor ensures deterministic cleanup of all assigned resources [SWS_RDS_90275]. Since the destructor is declared with the identifier noexcept, the implementation guarantees that no exceptions are propagated outward during the destruction process, which is mandatory for lifecycle stability and safe release in multithreaded runtime environments AUTOSAR_AP_SWS_RawDataStream §1 “Virtual destructor of the IEEE 1722 datagram type”.

Error Scenarios

In the area of error handling and exception handling, the interface is characterized by strict no-fail guarantees when tearing down instances. According to requirement [SWS_RDS_90275], the destructor ~IEEE1722DatagramTSCF() is declared with the specifier noexcept. This formally ensures that no C++ exceptions may be thrown during the destruction of a datagram object AUTOSAR_AP_SWS_RawDataStream §1 “Virtual destructor of the IEEE 1722 datagram type”.

If unexpected errors occur internally during the cleanup process, the method must under no circumstances propagate them across the stack to the caller. Throwing an exception from a function declared as noexcept would immediately result in a call to std::terminate in the C++ runtime system. Interpretation: Any internal cleanup errors must therefore be handled defensively or logged internally to prevent an uncontrolled termination of the overall process. Question (open) The destructor has no error return values and requires no preconditions beyond the existence of a valid object, thereby ensuring safe termination even in exceptional situations, such as during stack unwinding [SWS_RDS_90275].