CLASSIC
Modul: det
Rolle: constitutive
Konfidenz: 95%
SNIP_CLASSIC_DET_SECTION_7_2_3_Safety_requirements
Wortlaut
7.2.3 Safety requirements
[CP_SWS_Dds_00761] Repetition or Insertion of Information Upstream requirements: FO_RS_Dds_00010
⌈The Dds module shall, as described in [FO_PRS_DDS_00601], use submessages which have counters, e.g., AckNack, Data and DataFrag, etc., to guarantee safety mechanisms against Repetition or Insertion of Information faults. At receiving side, if a message with a duplicated counter is received, the Dds module shall discard the message and call the API Det_ReportRuntimeError with the DDS_E_SAMPLE_REJECTED.⌋
[CP_SWS_Dds_00762] Loss or Incorrect sequence of Information Upstream requirements: FO_RS_Dds_00010
⌈The Dds module shall, as described in [FO_PRS_DDS_00602], use submessages which have counters, e.g., AckNack, Data and DataFrag, etc., to guarantee safety mechanisms against Loss or Incorrect sequence of Information faults. At receiving side, if a message with a non-consecutive counter is received, the Dds module shall discard the message and call the API Det_ReportRuntimeError with the DDS_E_SAMPLE_LOST runtime error code.⌋ The Dds module shall use QoSs able to monitor timeouts, such as DEADLINE, LATENCY_BUDGET, LIFESPAN and TIME_BASED_FILTER (refer respectively to DdsDeadline, DdsLatencyBudget, DdsLifespan and DdsTimeBasedFilter) to guarantee safety mechanisms against Delay of Information fault (take [2] for details on those QoS policies).
[CP_SWS_Dds_00763] Delay of Information - sending checks Upstream requirements: FO_RS_Dds_00005, FO_RS_Dds_00010
⌈At sending side, if some timing constraint is not fulfilled, the Dds module shall, as described in [FO_PRS_DDS_00603], discard the message and call the API Det_ReportRuntimeError with the DDS_E_SENDER_TIMING_MISSED runtime error code.⌋
[CP_SWS_Dds_00764] Delay of Information - receiving checks Upstream requirements: FO_RS_Dds_00005, FO_RS_Dds_00010
⌈At receiving side, if some timing constraint is not fulfilled, the Dds module shall, as described in [FO_PRS_DDS_00603], discard the message and call the API Classic Platform Det_ReportRuntimeError with the DDS_E_RECEIVER_TIMING_MISSED runtime error code.⌋
[CP_SWS_Dds_00766] Corruption of Information Upstream requirements: FO_RS_Dds_00010
⌈The Dds module shall, as described in [FO_PRS_DDS_00604], use CRC check to guarantee safety mechanisms against Corruption of Information fault.⌋
[CP_SWS_Dds_00769] CRC check failure Upstream requirements: FO_RS_Dds_00010
⌈On received side, if the CRC check fails, the Dds module shall, as described in
[FO_PRS_DDS_00604], call the API Det_ReportRuntimeError with the DDS_E_CRC_CHECK_FAILED runtime error code and discard the message.⌋
Versionen & Provenienz · Zugeordnete Anforderungen
Diese Angaben zeigt der Versions-Explorer.
Begründung & Zuweisungs-Evidenz
Cited verbatim in the snippet (deterministic citation).
Dokumenten-Herkunft & Rückverfolgbarkeit
| Spezifikations-Dokument | SWS_DataDistributionService.pdf |
|---|---|
| Dokumentseite | Seite 53 |
| Ziel-Modul | det (classic) |
| Ziel-Anforderung | SWS_Det_01001 |
| Semantische Rolle | constitutive |
| Automatisierungs-Konfidenz | 0.95 |