What it is
Data Distribution Service (DDS) is an OMG specification for data-centric publish/subscribe communication. Applications publish typed data to named topics; interested applications subscribe without needing a hard-coded connection to each producer. Data-centric means the model includes identifiable data instances and their lifecycle, rather than only an exchange of messages.
DDS defines the application-facing communication model and quality-of-service (QoS) behavior. The companion DDS Interoperability Wire Protocol, commonly called DDSI-RTPS, defines network messages and protocol behavior that allow implementations to communicate. Both specifications are publicly readable; implementation products have their own licensing terms.
Who it applies to
DDS is relevant to middleware developers, platform integrators, application teams, and vehicle architects choosing communication for distributed software. In automotive systems, it can support communication among applications on high-performance computers and across Ethernet-connected computing nodes.
It is a technical specification, not a vehicle regulation. A project takes on conformance obligations through its chosen platform, procurement requirements, or interface agreements. Application teams usually work through a DDS implementation, while middleware suppliers implement the underlying specification. Integrators still need to agree on supported features and configurations across suppliers.
What it covers
The DDS model includes domain participants, topics, publishers, subscribers, DataWriters, and DataReaders. A domain provides a logical communication scope; it should not be treated as a security boundary by itself.
| Document | Main responsibility |
|---|---|
| DDS | Typed data model, communication entities, instance lifecycle, and QoS semantics |
| DDSI-RTPS | Endpoint discovery, wire messages, and reliable or best-effort exchange between implementations |
QoS policies express requirements such as reliability, retained history, durability for late-joining readers, expected update deadlines, and liveliness. Some policies participate in endpoint compatibility: discovering a reader and writer does not necessarily mean they can exchange data.
DDSI-RTPS specifies how participants and endpoints discover one another and exchange user data, including protocol mechanisms for reliable delivery. Its standardized UDP/IP mapping is relevant to Ethernet deployments. QoS settings alone do not establish an end-to-end timing guarantee; scheduling, network capacity, and resource limits also matter.
How it fits with other documents
DDS and DDSI-RTPS address complementary layers. The DDS Extensible and Dynamic Topic Types specification, usually called DDS-XTypes, adds rules for type representation and evolution. DDS Security separately specifies security mechanisms; authentication, access control, and cryptographic protection should be selected and configured explicitly.
Automotive frameworks may define additional bindings, profiles, and integration requirements. Where an AUTOSAR platform uses DDS, follow the applicable AUTOSAR requirements alongside the referenced OMG specifications. SOME/IP is another automotive communication approach; a shared Ethernet network does not make SOME/IP and DDS endpoints directly interoperable.
Functional-safety and cybersecurity engineering remain system responsibilities. Neither DDS conformance nor reliable delivery establishes compliance with ISO 26262 or ISO/SAE 21434.
In practice
Start with a data contract: define each topic’s type, units, instance keys, producer ownership, update expectations, and acceptable age. For example, a consumer of vehicle-state data needs an explicit response when updates stop, even when reliable delivery is enabled.
Choose QoS from those requirements, then verify reader–writer compatibility and bound history and memory use. Test discovery, participant restarts, late joiners, packet loss, and overloaded consumers on the intended network.
For multiple suppliers, record the supported DDSI-RTPS version, type representations, discovery configuration, and security options. Test the actual implementations together: citing the same specification does not establish that every optional feature or deployment setting matches.