P4-REQ-21-9-009

Return to Requirements

Each QoS profile mapping SHALL identify the expected liveliness or availability behavior.

Part 4, Section 21.9: QoS Profile Requirements.

Liveliness and availability behavior supports detection of implementation participants that become unavailable, silent, or unable to perform their expected communication responsibilities.

Explicit expectations allow Phase 0 to align participant availability detection with the communication purpose and operational needs of the applicable Runtime Plane.

This requirement applies to:

• QoS profile mappings;
• DDS publishers;
• DDS subscribers;
• implementation participants; and
• applicable health and operational behavior.

Verification SHALL confirm that each QoS profile mapping identifies its expected liveliness or availability behavior.

Verification activities should include review checks confirming that:

• the expected behavior is stated;
• applicable participant unavailability can be detected where required;
• publisher and subscriber settings are compatible; and
• the selected behavior supports the applicable Runtime Plane purpose.

This requirement establishes the liveliness or availability expectation associated with each Phase 0 QoS profile mapping.

Related requirement identifiers:

• P4-REQ-21-9-002
• P4-REQ-21-9-010

Related source section:

• 21.9 QoS Profile Requirements

Draft