From f5f178daac8eebee921834c25e00202702ae1e28 Mon Sep 17 00:00:00 2001
From: JavierEspina <javier.espina@philips.com>
Date: Fri, 27 Oct 2023 19:19:05 +0200
Subject: [PATCH] Resolution of issue "Non slewing time adjustments #203"

---
 .../use-cases/tf1-ch-c-use-case-stad.adoc     | 22 +++++++++++++++++++
 1 file changed, 22 insertions(+)

diff --git a/asciidoc/volume1/use-cases/tf1-ch-c-use-case-stad.adoc b/asciidoc/volume1/use-cases/tf1-ch-c-use-case-stad.adoc
index 810f475..ae644bc 100644
--- a/asciidoc/volume1/use-cases/tf1-ch-c-use-case-stad.adoc
+++ b/asciidoc/volume1/use-cases/tf1-ch-c-use-case-stad.adoc
@@ -51,7 +51,29 @@ NOTE: The 50ms target accuracy is suitable for highly demanding use cases like r
 ====
 ****
 
+.R1521
+[sdpi_requirement#r1521,sdpi_req_level=should]
+****
+The <<term_manufacturer>> of a <<vol1_spec_sdpi_p_actor_somds_participant>> should configure its <<acronym_ts_service>> client to give priority to system clock adjustments that are slewing (over stepping adjustments).
+
+.Notes
+[%collapsible]
+====
+NOTE: If possible, the priority of slewing adjustments starts applying once the <<vol1_spec_sdpi_p_actor_somds_participant>> has acquired synchronization to the <<acronym_ts_service>> after a system (re)start.
+====
+****
 
+.R1522
+[sdpi_requirement#r1522,sdpi_req_level=shall]
+****
+When the <<vol1_spec_sdpi_p_actor_somds_provider>> detects a stepping adjustment of its system clock, the <<vol1_spec_sdpi_p_actor_somds_provider>> shall initiate a new MDIB sequence by assigning a new MDIB sequence identifier.
+
+.Notes
+[%collapsible]
+====
+NOTE: Note: The <<vol1_spec_sdpi_p_actor_somds_consumer>> considers the possibility of a stepping clock adjustment having occurred at the <<vol1_spec_sdpi_p_actor_somds_provider>> when it receives a changed value in the <<vol1_spec_sdpi_p_actor_somds_provider>>'s MDIB sequence identifier.
+====
+****
 
 ===== Scenario: <<acronym_stad>> {var_use_case_id}.2 - Device is connected to the MD LAN network and a user wants to change the device's time