Go To Phase 0 Implementation Requirements
This section identifies the normative requirements established for the Phase 0 QoS Profile Model. The canonical requirement statements are maintained in Annex D: Requirements, Part 4, Section 21.9.
Table 21-8: QoS profile requirements.
| Requirement ID | Statement |
|---|---|
| P4-REQ-21-9-001 |
The Phase 0 Implementation Profile / PSM SHALL define a Phase 0 QoS Profile Model. |
| P4-REQ-21-9-002 |
Each QoS profile mapping SHALL identify the Runtime Plane or Runtime Planes it supports. |
| P4-REQ-21-9-003 |
Each QoS profile mapping SHALL identify the DDS Topic or Topic family that uses the profile. |
| P4-REQ-21-9-004 |
Each QoS profile mapping SHALL identify the communication purpose of the profile. |
| P4-REQ-21-9-005 |
Each QoS profile mapping SHALL identify the expected reliability behavior. |
| P4-REQ-21-9-006 |
Each QoS profile mapping SHALL identify the expected durability behavior. |
| P4-REQ-21-9-007 |
Each QoS profile mapping SHALL identify the expected history behavior. |
| P4-REQ-21-9-008 |
Each QoS profile mapping SHALL identify the expected ordering behavior. |
| P4-REQ-21-9-009 |
Each QoS profile mapping SHALL identify the expected liveliness or availability behavior. |
| P4-REQ-21-9-010 |
Each QoS profile mapping SHALL identify publisher and subscriber compatibility expectations. |
| P4-REQ-21-9-011 |
Each QoS profile mapping SHALL identify the configuration artifact that defines the profile. |
| P4-REQ-21-9-012 |
Each QoS profile mapping SHALL preserve traceability to the applicable FX logical Communication Endpoint and Runtime Plane. |
| P4-REQ-21-9-013 |
QoS profiles SHALL NOT redefine Runtime Planes, FX logical Communication Endpoints, FX logical information structures, or FX logical interaction patterns. |
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.