====== 13.2 QoS Profile Purpose ======

[[fxdemo:04-part:13-phase-0-qos-profile-model:start | Go To Phase 0 QoS Profile Model ]]

Phase 0 uses QoS profiles to make communication behavior explicit.

A QoS profile identifies the communication behavior expected for a selected [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] or Topic family. It allows implementation participants to use consistent settings for reliability, durability, history, ordering, liveliness, deadlines, resource limits, and related [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] concerns where Phase 0 requires those concerns.

The QoS Profile Model supports:

  * Consistent DDS behavior across implementation participants;
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] from Runtime Plane purpose to communication behavior;
  * Review of Topic compatibility between publishers and subscribers;
  * Repeatable configuration of DDS participants, publishers, subscribers, writers, and readers;
  * Later deployment and testability planning; and
  * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] planning for communication behavior.

The Phase 0 QoS Profile Model defines only the QoS discipline needed for the Phase 0 implementation baseline. Later development phases may extend, refine, supersede, or replace these profiles.

----

<WRAP centeralign>

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

</WRAP>