class ara::rds::IEEE1722Datagram61883_IIDC

Class ara::rds::IEEE1722Datagram61883_IIDC serves in module rds as a representation of IEEE 1722 datagrams for IEC 61883 and IIDC data streams (AUTOSAR_AP_SWS_RawDataStream p. 1). It encapsulates protected protocol fields in ara::core::Optional and acts as a base class for the layered configuration of streaming packets. Destruction occurs exception-safely via the virtual destructor ~IEEE1722Datagram61883_IIDC() noexcept [SWS_RDS_90260]. As an essential constraint, uncoordinated concurrent access to instances requires external synchronization.

more ›

Context

Within the rds (Raw Data Stream) module of the AUTOSAR Adaptive Platform, class ara::rds::IEEE1722Datagram61883_IIDC acts as a structured representation of IEEE 1722 datagrams for IEC 61883 and IIDC data streams (AUTOSAR_AP_SWS_RawDataStream p. 1). It maps the protocol fields of the specification and holds them in protected members. All datagram fields—including tag [SWS_RDS_90244], channel [SWS_RDS_90245], syt [SWS_RDS_90246], sph [SWS_RDS_90247], qi_2 [SWS_RDS_90248], qpc [SWS_RDS_90249], dbs [SWS_RDS_90250], fn [SWS_RDS_90251], sid [SWS_RDS_90252], sy [SWS_RDS_90253], dbc [SWS_RDS_90254], qi_1 [SWS_RDS_90255], fmt [SWS_RDS_90256], fdf_with_sph [SWS_RDS_90257], tcode [SWS_RDS_90258], and fdf_without_sph [SWS_RDS_90259]—have protection level protected. Because no public access methods are specified, the class likely serves primarily as a base class for derived protocol specializations or decoders within the streaming subsystem (interpretation: base class in inheritance hierarchy). Question Q-e94037851fe92b8d (open) The interaction between datagram, specialization, and stream processing is illustrated in the following context diagram.

Context diagram: Classification of the datagram base class between deriving protocol specializations and RDS stream processing. Sources: [SWS_RDS_90244], [SWS_RDS_90260], AUTOSAR_AP_SWS_RawDataStream p. 1

Lifecycle

Instances of ara::rds::IEEE1722Datagram61883_IIDC typically originate during data transmission or upon receiving audio and video streams over the network. Destruction and resource deallocation occur deterministically via the virtual destructor ~IEEE1722Datagram61883_IIDC() noexcept [SWS_RDS_90260]. The declaration as a virtual destructor ensures that derived classes are cleaned up completely when deleted via base class pointers, while the specifier noexcept guarantees that no exceptions may be thrown during destruction.

Regarding the internal state, the class has no complex state machine, but encapsulates its state via separate ara::core::Optional fields. Each field, such as the data block counter dbc [SWS_RDS_90254] or the data block size field dbs [SWS_RDS_90250], is either in an unset state or contains a valid protocol value. Regarding concurrency, the standard does not specify any internal synchronization mechanisms; concurrent read and write access to the same instance across multiple threads is therefore presumably not thread-safe (interpretation: lack of synchronization) and requires external coordination. Question Q-e1381bdfdee717e9 (open)

Usage Path

A typical usage path takes place in derived classes or within streaming pipelines for creating or evaluating datagrams:

• Initialization: A derived class instantiates the datagram object in preparation for a transmission or reception operation.
• Configuration of Fields: The required protocol headers are set selectively. In this process, standard parameters such as tag [SWS_RDS_90244], channel [SWS_RDS_90245], fmt [SWS_RDS_90256], and tcode [SWS_RDS_90258] are populated with values. Encapsulation in ara::core::Optional suggests that, depending on the specific IEEE 1722 subformat, not every field necessarily needs to be populated (interpretation: selective population). Question Q-925b6c1d9b5a8ce6 (open)
• Processing and Forwarding: The assembled datagram data is handed over to the downstream transport layer of the RDS module.
• Deallocation: After transmission or packet processing is complete, the object is destroyed, with the virtual destructor [SWS_RDS_90260] ensuring clean polymorphic cleanup.

Error Scenarios

Because ara::rds::IEEE1722Datagram61883_IIDC is defined as a data class, its methods do not signal explicit AUTOSAR error codes via ara::core::Result. Potential error sources arise primarily from incorrect handling of optional data members. Accessing empty instances of ara::core::Optional without prior validation—for example when reading sid [SWS_RDS_90252], fn [SWS_RDS_90251], or qpc [SWS_RDS_90249]—can lead to runtime errors. As a precondition for read access, derived components must always verify whether the respective field is initialized. Furthermore, mutually dependent or alternative fields, such as fdf_with_sph [SWS_RDS_90257] and fdf_without_sph [SWS_RDS_90259], must be set consistently with each other.