[yaml] Update IDM and SC test scripts to match Test Plan and Specification

src/app/tests/suites/certification/Test_TC_IDM_4_2.yaml

@@ -32,12 +32,23 @@ tests:
           Here the command to enter interactive mode:--   ./chip-tool interactive start
       disabled: true
 
+    - label:
+          If the device is has the ICD Management cluster, TH reads from the DUT
+          the IdleModeInterval attribute and sets the
+          SubscriptionMaxIntervalPublisherLimit to the value read. If the device
+          does not have the ICD Management cluster, set the
+          SubscriptionMaxIntervalPublisherLimit to 60 minutes.
+      verification: |
+          The cluster used in the below command is an example,
+          icdmanagement read idle-mode-interval 12344321 0
+      disabled: true
+
     - label:
           "Step 1: TH sends a subscription message to the DUT with
-          MaxIntervalCeiling set to a value greater than 60 mins. DUT sends a
-          report data action to the TH. TH sends a success status response to
-          the DUT. DUT sends a Subscribe Response Message to the TH to activate
-          the subscription."
+          MaxIntervalCeiling set to a value greater than the
+          SubscriptionMaxIntervalPublisherLimit. DUT sends a report data action
+          to the TH. TH sends a success status response to the DUT. DUT sends a
+          Subscribe Response Message to the TH to activate the subscription."
       verification: |
           onoff subscribe on-off  100  3900 1 1 --keepSubscriptions true
 
@@ -73,18 +84,18 @@ tests:
 
     - label:
           "Step 2: TH sends a subscription message to the DUT with
-          MaxIntervalCeiling set to a value less than 60 mins. DUT sends a
-          report data action to the TH. TH sends a success status response to
-          the DUT. DUT sends a Subscribe Response Message to the TH to activate
-          the subscription."
+          MaxIntervalCeiling set to a value less than han the
+          SubscriptionMaxIntervalPublisherLimit. DUT sends a report data action
+          to the TH. TH sends a success status response to the DUT. DUT sends a
+          Subscribe Response Message to the TH to activate the subscription."
       verification: |
           basicinformation subscribe location 10 2400 1 0 --keepSubscriptions true
           On the TH(chip-tool), verify a report data message is received and verify it contains the following data :
            Report data - data of the attribute/event requested earlier.
            Verify on the TH the Subscribe Response has the following fields,
            SubscriptionId - Verify it is of type uint32.
            MaxInterval - Verify it is of type uint32.
-           Verify that the MaxInterval is less than or equal to 60 mins.
+           Verify that the MaxInterval is less than or equal to the MaxIntervalCeiling.
 
           [1686294932.404445][101362:101364] CHIP:DMG:         InteractionModelRevision = 1
           [1686294932.404449][101362:101364] CHIP:DMG: }
@@ -105,9 +116,6 @@ tests:
           [1686294932.420822][101362:101364] CHIP:DMG: }
           [1686294932.420834][101362:101364] CHIP:DMG: Subscription established with SubscriptionID = 0xcbbba269 MinInterval = 10s MaxInterval = 2400s Peer = 01:0000000000000001
           [1686294932.420847][101362:101364] CHIP:DMG: MoveToState ReadClient[0x7fc7ec00e400]: Moving to [Subscripti]
-
-
-           MaxInterval and MaxIntervalCeiling are different parameters. One is sent from the TH the other from DUT, verify MaxInterval >=  MaxIntervalCeiling
       disabled: true
 
     - label:

src/app/tests/suites/certification/Test_TC_SC_2_1.yaml

@@ -30,14 +30,14 @@ tests:
           "Initiator constructs and sends a TLV-encoded PBKDFParamRequest
           message"
       verification: |
-          Verify that the responder receives the PBKDFParamRequest message. Verify that the protocol header is properly constructed: Message Flags: S Flag is set to 0, and DSIZ field is set to 0 Session ID is set to 0 Security Flags: Session Type bits are set to 0 Exchange Flags: I Flag is set to 1 Protocol Opcode is set to 32 (0x20) Protocol ID is set to 0 Verify, if possible in a debug mode, that the PBKDFParamRequest message contains: initiatorRandom - randomly generated 32-bit octet string initiatorSessionId - max size 16-bits unsigned integer that does not overlap with existing initiator session identifiers passcodeId - max size 16-bits unsigned integer hasPBKDFParameters - boolean If hasPBKDFParameters is set to true then PBKDF parameters are not known for the given passcodeId If hasPBKDFParameters is set to false then PBKDF parameters are known for the given passcodeId initiatorSEDParams - optional sed-parameter-struct which contains SLEEPY_IDLE_INTERVAL - max size 16-bits unsigned integer SLEEPY_ACTIVE_INTERVAL - max size 16-bits unsigned integer
+          Verify that the responder receives the PBKDFParamRequest message. Verify that the protocol header is properly constructed: Message Flags: S Flag is set to 0, and DSIZ field is set to 0 Session ID is set to 0 Security Flags: Session Type bits are set to 0 Exchange Flags: I Flag is set to 1 Protocol Opcode is set to 32 (0x20) Protocol ID is set to 0 Verify, if possible in a debug mode, that the PBKDFParamRequest message contains: initiatorRandom - randomly generated 32-bit octet string initiatorSessionId - max size 16-bits unsigned integer that does not overlap with existing initiator session identifiers passcodeId - max size 16-bits unsigned integer hasPBKDFParameters - boolean If hasPBKDFParameters is set to true then PBKDF parameters are not known for the given passcodeId If hasPBKDFParameters is set to false then PBKDF parameters are known for the given passcodeId initiatorSessionParams - optional session-parameter-struct which contains SESSION_IDLE_INTERVAL - max size 32-bits unsigned integer SESSION_ACTIVE_INTERVAL - max size 32-bits unsigned integer SESSION_ACTIVE_THRESHOLD - max size 16-bits unsigned integer
       disabled: true
 
     - label:
           "Responder verifies the passcodeID, constructs and sends a TLV-encoded
           PBKDFParamResponse message"
       verification: |
-          Verify that the Initiator receives the PBKDFParamResponse message. Verify that the protocol header is properly constructed: Message Flags: S Flag is set to 0, and DSIZ field is set to 0 Session ID is set to 0 Security Flags: Session Type bits are set to 0 Exchange Flags: I Flag is set to 0 Protocol Opcode is set to 33 (0x21) Protocol ID is set to 0 Verify, if possible in a debug mode, that the PBKDFParamResponse message contains: initiatorRandom - value from the PBKDFParamRequest message responderRandom - randomly generated 32-bit octet string responderSessionId - max size 16-bits unsigned integer that does not overlap with existing that does not overlap with existing responder session identifiers pbkdf_parameters If hasPBKDFParameters from the PBKDFParamRequest message is true, then pbkdf_parameters should not be included. If hasPBKDFParameters from the PBKDFParamRequest message is false, then PBKDFParameters should contain a + Crypto_PBKDFParameterSet struct with values for iterations (max size 32 bit unsigned integer) and salt (octet string with a minimum of 16 bits and maximum of 32 bits) responderSEDParams - optional sed-parameter-struct SLEEPY_IDLE_INTERVAL - max size 16-bits unsigned integer SLEEPY_ACTIVE_INTERVAL - max size 16-bits unsigned integer
+          Verify that the Initiator receives the PBKDFParamResponse message. Verify that the protocol header is properly constructed: Message Flags: S Flag is set to 0, and DSIZ field is set to 0 Session ID is set to 0 Security Flags: Session Type bits are set to 0 Exchange Flags: I Flag is set to 0 Protocol Opcode is set to 33 (0x21) Protocol ID is set to 0 Verify, if possible in a debug mode, that the PBKDFParamResponse message contains: initiatorRandom - value from the PBKDFParamRequest message responderRandom - randomly generated 32-bit octet string responderSessionId - max size 16-bits unsigned integer that does not overlap with existing that does not overlap with existing responder session identifiers pbkdf_parameters If hasPBKDFParameters from the PBKDFParamRequest message is true, then pbkdf_parameters should not be included. If hasPBKDFParameters from the PBKDFParamRequest message is false, then PBKDFParameters should contain a + Crypto_PBKDFParameterSet struct with values for iterations (max size 32 bit unsigned integer) and salt (octet string with a minimum of 16 bits and maximum of 32 bits) responderSessionParams - optional session-parameter-struct SESSION_IDLE_INTERVAL - max size 32-bits unsigned integer SESSION_ACTIVE_INTERVAL - max size 32-bits unsigned integer SESSION_ACTIVE_THRESHOLD - max size 16-bits unsigned integer
       disabled: true
 
     - label: "Initiator constructs and sends a TLV-encoded Pake1 message"

src/app/tests/suites/certification/Test_TC_SC_3_2.yaml

@@ -28,7 +28,7 @@ tests:
           "Step 1: Initiator constructs and sends a TLV-encoded Sigma1 message
           to Responder with resumption containing initiatorRandom
           initiatorSessionId destinationId resumptionID initiatorResumeMIC
-          initiatorEphPubKey initiatorSEDParams"
+          initiatorEphPubKey initiatorSessionParams"
       verification: |
           On Initiator(chip-tool) verify that, Initiator(chip-tool)  constructs and sends a TLV-encoded Sigma1 message to Responder with resumption containing
           initiatorRandom
@@ -37,7 +37,7 @@ tests:
           resumptionID
           initiatorResumeMIC
           initiatorEphPubKey
-          initiatorSEDParams
+          initiatorSessionParams
           here is the log to verify on chip-tool
 
           1683884120.041635][5134:5136] CHIP:DMG: Decrypted Payload (182 bytes) =
@@ -88,9 +88,10 @@ tests:
           resumptionID is of Octet String maximum of length 16 bytes
           responderSessionID is of uint16
            sigma2ResumeMIC is of Octet String maximum of length 16 bytes
-          responderSEDParams is from any one of the following:
-                SLEEPY_IDLE_INTERVAL - Verify that it is of uint32
-                SLEEPY_ACTIVE_INTERVAL - Verify that it is of uint32
+          responderSessionParams is from any one of the following:
+                SESSION_IDLE_INTERVAL - Verify that it is of uint32
+                SESSION_ACTIVE_INTERVAL - Verify that it is of uint32
+                SESSION_ACTIVE_THRESHOLD - Verify that it is of uint16
 
           here is the log to verify on chip-tool
 

src/app/tests/suites/certification/Test_TC_SC_3_3.yaml

@@ -73,10 +73,10 @@ tests:
           resumptionID is of Octet String maximum of length 16 bytes
           responderSessionID is of uint16
            sigma2ResumeMIC is of Octet String maximum of length 16 bytes
-          responderSEDParams is from any one of the following:
-                SLEEPY_IDLE_INTERVAL - Verify that it is of uint32
-                SLEEPY_ACTIVE_INTERVAL - Verify that it is of uint32
-
+          responderSessionParams is from any one of the following:
+                SESSION_IDLE_INTERVAL - Verify that it is of uint32
+                SESSION_ACTIVE_INTERVAL - Verify that it is of uint32
+                SESSION_ACTIVE_THRESHOLD - Verify that it is of uint16
 
           [1683973658.044236][21637:21637] CHIP:EM: Rxd Ack; Removing MessageCounter:113416101 from Retrans Table on exchange 32995r
           [1683973662.299442][21637:21637] CHIP:DMG: << from UDP:[fe80::e9f6:2c08:2794:357d%wlp0s20f3]:41363 | 167307433 | [Secure Channel  (0) / Certificate Authenticated Session Establishment Sigma '1' (0x30) / Session = 0 / Exchange = 32997]