@matter/types 0.16.0-alpha.0-20251022-5a69ce65a → 0.16.0-alpha.0-20251027-17770fb28

package/dist/cjs/clusters/icd-management.d.ts

@@ -13,7 +13,7 @@ export declare namespace IcdManagement {
     /**
      * These are optional features supported by IcdManagementCluster.
      *
-     * @see {@link MatterSpecification.v141.Core} § 9.17.4
+     * @see {@link MatterSpecification.v141.Core} § 9.16.4
      */
     enum Feature {
         /**
@@ -22,7 +22,7 @@ export declare namespace IcdManagement {
          * When this feature is supported, the device shall support all the associated commands and attributes to
          * properly support the Check-In Protocol.
          *
-         * @see {@link MatterSpecification.v141.Core} § 9.17.4.1
+         * @see {@link MatterSpecification.v141.Core} § 9.16.4.1
          */
         CheckInProtocolSupport = "CheckInProtocolSupport",
         /**
@@ -30,7 +30,7 @@ export declare namespace IcdManagement {
          *
          * This feature is supported if and only if the device has a user active mode trigger.
          *
-         * @see {@link MatterSpecification.v141.Core} § 9.17.4.2
+         * @see {@link MatterSpecification.v141.Core} § 9.16.4.2
          */
         UserActiveModeTrigger = "UserActiveModeTrigger",
         /**
@@ -38,7 +38,7 @@ export declare namespace IcdManagement {
          *
          * This feature is supported if and only the device is a Long Idle Time ICD.
          *
-         * @see {@link MatterSpecification.v141.Core} § 9.17.4.3
+         * @see {@link MatterSpecification.v141.Core} § 9.16.4.3
          */
         LongIdleTimeSupport = "LongIdleTimeSupport",
         /**
@@ -47,12 +47,12 @@ export declare namespace IcdManagement {
          * This feature is supported if and only if the device can switch between SIT and LIT operating modes even if it
          * has a valid registered client. See the dynamic SIT / LIT operating mode switching for more details.
          *
-         * @see {@link MatterSpecification.v141.Core} § 9.17.4.4
+         * @see {@link MatterSpecification.v141.Core} § 9.16.4.4
          */
         DynamicSitLitSupport = "DynamicSitLitSupport"
     }
     /**
-     * @see {@link MatterSpecification.v141.Core} § 9.17.5.1.1
+     * @see {@link MatterSpecification.v141.Core} § 9.16.5.1.1
      */
     enum ClientType {
         /**
@@ -65,14 +65,14 @@ export declare namespace IcdManagement {
         Ephemeral = 1
     }
     /**
-     * @see {@link MatterSpecification.v141.Core} § 9.17.5.3
+     * @see {@link MatterSpecification.v141.Core} § 9.16.5.3
      */
     const TlvMonitoringRegistration: import("../tlv/TlvObject.js").ObjectSchema<{
         /**
          * This field shall indicate the NodeID of the Node to which Check-In messages will be sent when the
          * MonitoredSubject is not subscribed.
          *
-         * @see {@link MatterSpecification.v141.Core} § 9.17.5.3.1
+         * @see {@link MatterSpecification.v141.Core} § 9.16.5.3.1
          */
         checkInNodeId: import("../tlv/TlvObject.js").FieldType<import("../datatype/NodeId.js").NodeId>;
         /**
@@ -95,46 +95,47 @@ export declare namespace IcdManagement {
          * the server on the entry’s associated fabric bears the CASE Authenticated TAG value 0xAA12 and the version
          * 0x0002 or higher within its NOC, then the entry matches.
          *
-         * @see {@link MatterSpecification.v141.Core} § 9.17.5.3.2
+         * @see {@link MatterSpecification.v141.Core} § 9.16.5.3.2
          */
         monitoredSubject: import("../tlv/TlvObject.js").FieldType<import("../datatype/NodeId.js").NodeId>;
         /**
          * This field shall indicate the client’s type to inform the ICD of the availability for communication of the
          * client.
          *
-         * @see {@link MatterSpecification.v141.Core} § 9.17.5.4
+         * @see {@link MatterSpecification.v141.Core} § 9.16.5.3.4
          */
         clientType: import("../tlv/TlvObject.js").FieldType<ClientType>;
         fabricIndex: import("../tlv/TlvObject.js").FieldType<import("../datatype/FabricIndex.js").FabricIndex>;
     }>;
     /**
-     * @see {@link MatterSpecification.v141.Core} § 9.17.5.3
+     * @see {@link MatterSpecification.v141.Core} § 9.16.5.3
      */
     interface MonitoringRegistration extends TypeFromSchema<typeof TlvMonitoringRegistration> {
     }
     /**
      * Input to the IcdManagement registerClient command
      *
-     * @see {@link MatterSpecification.v141.Core} § 9.17.7.1
+     * @see {@link MatterSpecification.v141.Core} § 9.16.7.1
      */
     const TlvRegisterClientRequest: import("../tlv/TlvObject.js").ObjectSchema<{
         /**
          * This field shall provide the node ID to which a Check-In message will be sent if there are no active
          * subscriptions matching MonitoredSubject.
          *
-         * @see {@link MatterSpecification.v141.Core} § 9.17.7.1.1
+         * @see {@link MatterSpecification.v141.Core} § 9.16.7.1.1
          */
         checkInNodeId: import("../tlv/TlvObject.js").FieldType<import("../datatype/NodeId.js").NodeId>;
         /**
          * This field shall provide the monitored subject ID.
          *
-         * @see {@link MatterSpecification.v141.Core} § 9.17.7.1.2
+         * @see {@link MatterSpecification.v141.Core} § 9.16.7.1.2
          */
         monitoredSubject: import("../tlv/TlvObject.js").FieldType<import("../datatype/NodeId.js").NodeId>;
         /**
-         * This field shall provide the shared secret between the client and the ICD to encrypt the Check-In message.
+         * This field shall contain the ICDToken, a 128-bit symmetric key shared by the ICD and the ICD Client, used to
+         * encrypt Check-In messages from this ICD to the MonitoredSubject.
          *
-         * @see {@link MatterSpecification.v141.Core} § 9.17.7.1.3
+         * @see {@link MatterSpecification.v141.Core} § 9.16.7.1.3
          */
         key: import("../tlv/TlvObject.js").FieldType<AllowSharedBufferSource>;
         /**
@@ -145,20 +146,75 @@ export declare namespace IcdManagement {
          * provided by clients with administrator permissions for the server cluster. The verification key shall be
          * ignored by the server if it is provided by a client with administrator permissions for the server cluster.
          *
-         * @see {@link MatterSpecification.v141.Core} § 9.17.7.1.4
+         * @see {@link MatterSpecification.v141.Core} § 9.16.7.1.4
          */
         verificationKey: import("../tlv/TlvObject.js").OptionalFieldType<AllowSharedBufferSource>;
         /**
          * This field shall provide the client type of the client registering.
          *
-         * @see {@link MatterSpecification.v141.Core} § 9.17.7.1.5
+         * ### Effect on Receipt
+         *
+         * On receipt of the RegisterClient command, the server shall perform the following procedure:
+         *
+         *   1. The server verifies that an entry for the fabric is available in the server’s list of registered
+         *      clients.
+         *
+         *     a. If one of the entries in storage for the fabric has the same CheckInNodeID as the received
+         *        CheckInNodeID, the server shall continue from step 2.
+         *
+         *     b. If there is an available entry for the fabric, an entry is created for the fabric and the received
+         *        CheckInNodeID, MonitoredSubject, Key and ClientType are stored. The server shall continue from step 5.
+         *
+         *     c. If there are no available entries for the fabric, the status shall be RESOURCE_EXHAUSTED and the
+         *        server shall continue from step 6.
+         *
+         *   2. The server shall verify the privileges of the command’s ISD.
+         *
+         *     a. If the ISD of the command has administrator privileges for the server cluster, the server shall
+         *        continue from step 4.
+         *
+         *     b. If the ISD of the command does not have administrator privileges for the server cluster, the server
+         *        shall continue from step 3.
+         *
+         *   3. The server shall verify that the received verification key is equal to the key previously stored in the
+         *      list of registered clients with the matching CheckInNodeID.
+         *
+         *     a. If the verification key does not have a valid value, the status shall be FAILURE. the server shall
+         *        continue from step 6.
+         *
+         *     b. If the verification key is not equal to the Key value stored in the entry, the status shall be
+         *        FAILURE. The server shall continue from step 6.
+         *
+         *     c. If the verification key is equal to the Key value stored in the entry, the server shall continue from
+         *        step 4.
+         *
+         *   4. The entry shall be updated with the received CheckInNodeID, MonitoredSubject, Key and ClientType.
+         *
+         *     a. If the update fails, the status shall be FAILURE. The server shall continue from step 6.
+         *
+         *     b. If the update succeeds, the server shall continue from step 5.
+         *
+         *   5. The server shall persist the client information.
+         *
+         *     a. If the persistence fails, the status shall be FAILURE and the server shall continue from step 6.
+         *
+         *     b. If the persistence succeeds, the status shall be SUCCESS and the server shall continue from step 6.
+         *
+         *   6. The server shall generate a response.
+         *
+         *     a. If the status is SUCCESS, the server shall generate a RegisterClientResponse command.
+         *
+         *     b. If the status is not SUCCESS, the server shall generate a default response with the Status field set
+         *        to the evaluated error status.
+         *
+         * @see {@link MatterSpecification.v141.Core} § 9.16.7.1.5
          */
         clientType: import("../tlv/TlvObject.js").FieldType<ClientType>;
     }>;
     /**
      * Input to the IcdManagement registerClient command
      *
-     * @see {@link MatterSpecification.v141.Core} § 9.17.7.1
+     * @see {@link MatterSpecification.v141.Core} § 9.16.7.1
      */
     interface RegisterClientRequest extends TypeFromSchema<typeof TlvRegisterClientRequest> {
     }
@@ -166,7 +222,12 @@ export declare namespace IcdManagement {
      * This command shall be sent by the ICD Management Cluster server in response to a successful RegisterClient
      * command.
      *
-     * @see {@link MatterSpecification.v141.Core} § 9.17.7.2
+     * ### When Generated
+     *
+     * This command shall be generated in response to a successful RegisterClient command. The ICDCounter field shall be
+     * set to the ICDCounter attribute of the server.
+     *
+     * @see {@link MatterSpecification.v141.Core} § 9.16.7.2
      */
     const TlvRegisterClientResponse: import("../tlv/TlvObject.js").ObjectSchema<{
         icdCounter: import("../tlv/TlvObject.js").FieldType<number>;
@@ -175,20 +236,25 @@ export declare namespace IcdManagement {
      * This command shall be sent by the ICD Management Cluster server in response to a successful RegisterClient
      * command.
      *
-     * @see {@link MatterSpecification.v141.Core} § 9.17.7.2
+     * ### When Generated
+     *
+     * This command shall be generated in response to a successful RegisterClient command. The ICDCounter field shall be
+     * set to the ICDCounter attribute of the server.
+     *
+     * @see {@link MatterSpecification.v141.Core} § 9.16.7.2
      */
     interface RegisterClientResponse extends TypeFromSchema<typeof TlvRegisterClientResponse> {
     }
     /**
      * Input to the IcdManagement unregisterClient command
      *
-     * @see {@link MatterSpecification.v141.Core} § 9.17.7.3
+     * @see {@link MatterSpecification.v141.Core} § 9.16.7.3
      */
     const TlvUnregisterClientRequest: import("../tlv/TlvObject.js").ObjectSchema<{
         /**
          * This field shall provide the registered client node ID to remove from storage.
          *
-         * @see {@link MatterSpecification.v141.Core} § 9.17.7.3.1
+         * @see {@link MatterSpecification.v141.Core} § 9.16.7.3.1
          */
         checkInNodeId: import("../tlv/TlvObject.js").FieldType<import("../datatype/NodeId.js").NodeId>;
         /**
@@ -200,21 +266,75 @@ export declare namespace IcdManagement {
          * server cluster. The verification key shall be ignored by the server if it is provided by a client with
          * administrator permissions for the server cluster.
          *
-         * @see {@link MatterSpecification.v141.Core} § 9.17.7.3.2
+         * ### Effect on Receipt
+         *
+         * On receipt of the UnregisterClient command, the server shall perform the following procedure:
+         *
+         *   1. The server shall check whether there is a entry stored on the device for the fabric with the same
+         *      CheckInNodeID.
+         *
+         *     a. If there are no entries stored for the fabric, the status shall be NOT_FOUND. The server shall
+         *        continue from step 6.
+         *
+         *     b. If there is an error when reading from storage, the status shall be FAILURE. The server shall continue
+         *        from step 6.
+         *
+         *     c. If there is at least one entry stored on the server for the fabric, the server shall continue from
+         *        step 2.
+         *
+         *   2. The server shall verify if one of the entries for the fabric has the corresponding CheckInNodeID
+         *      received in the command.
+         *
+         *     a. If no entries have the corresponding CheckInNodeID, the status shall be NOT_FOUND. The server shall
+         *        continue from step 6.
+         *
+         *     b. If an entry has the corresponding CheckInNodeID, the server shall continue to step 3.
+         *
+         *   3. The server shall check whether the ISD of the command has administrator permissions for the server
+         *      cluster.
+         *
+         *     a. If the ISD of the command has administrator privileges for the server cluster, the server shall
+         *        continue from step 5.
+         *
+         *     b. If the ISD of the command does not have administrator privileges for the server cluster, the server
+         *        shall continue from step 4.
+         *
+         *   4. The server shall verify that the received verification key is equal to the key previously stored in the
+         *      list of registered clients with the matching CheckInNodeID.
+         *
+         *     a. If the verification key does not have a valid value, the status shall be FAILURE. the server shall
+         *        continue from step 6.
+         *
+         *     b. If the verification key is not equal to the Key value stored in the entry, the status shall be
+         *        FAILURE. The server shall continue from step 6.
+         *
+         *     c. If the verification key is equal to the Key value stored in the entry, the server shall continue from
+         *        step 5.
+         *
+         *   5. The server shall delete the entry with the matching CheckInNodeID from storage and will persist the
+         *      change.
+         *
+         *     a. If the removal of the entry fails, the status shall be FAILURE. The server shall continue from step 6.
+         *
+         *     b. If the removal succeeds, the status shall be SUCCESS and the server shall continue to step 6.
+         *
+         *   6. The server shall generate a response with the Status field set to the evaluated status.
+         *
+         * @see {@link MatterSpecification.v141.Core} § 9.16.7.3.2
          */
         verificationKey: import("../tlv/TlvObject.js").OptionalFieldType<AllowSharedBufferSource>;
     }>;
     /**
      * Input to the IcdManagement unregisterClient command
      *
-     * @see {@link MatterSpecification.v141.Core} § 9.17.7.3
+     * @see {@link MatterSpecification.v141.Core} § 9.16.7.3
      */
     interface UnregisterClientRequest extends TypeFromSchema<typeof TlvUnregisterClientRequest> {
     }
     /**
      * See the UserActiveModeTriggerHint table for requirements associated to each bit.
      *
-     * @see {@link MatterSpecification.v141.Core} § 9.17.5.1
+     * @see {@link MatterSpecification.v141.Core} § 9.16.5.1
      */
     const UserActiveModeTrigger: {
         /**
@@ -287,7 +407,7 @@ export declare namespace IcdManagement {
         appDefinedButton: BitFlag;
     };
     /**
-     * @see {@link MatterSpecification.v141.Core} § 9.17.5.2
+     * @see {@link MatterSpecification.v141.Core} § 9.16.5.2
      */
     enum OperatingMode {
         /**
@@ -302,7 +422,7 @@ export declare namespace IcdManagement {
     /**
      * Input to the IcdManagement stayActiveRequest command
      *
-     * @see {@link MatterSpecification.v141.Core} § 9.17.7.4
+     * @see {@link MatterSpecification.v141.Core} § 9.16.7.4
      */
     const TlvStayActiveRequest: import("../tlv/TlvObject.js").ObjectSchema<{
         stayActiveDuration: import("../tlv/TlvObject.js").FieldType<number>;
@@ -310,7 +430,7 @@ export declare namespace IcdManagement {
     /**
      * Input to the IcdManagement stayActiveRequest command
      *
-     * @see {@link MatterSpecification.v141.Core} § 9.17.7.4
+     * @see {@link MatterSpecification.v141.Core} § 9.16.7.4
      */
     interface StayActiveRequest extends TypeFromSchema<typeof TlvStayActiveRequest> {
     }
@@ -318,17 +438,19 @@ export declare namespace IcdManagement {
      * This message shall be sent by the ICD in response to the StayActiveRequest command and shall contain the computed
      * duration (in milliseconds) that the ICD intends to stay active for.
      *
-     * @see {@link MatterSpecification.v141.Core} § 9.17.7.5
+     * @see {@link MatterSpecification.v141.Core} § 9.16.7.5
      */
     const TlvStayActiveResponse: import("../tlv/TlvObject.js").ObjectSchema<{
         /**
          * This field shall provide the actual duration that the ICD server can stay active from the time it receives
          * the StayActiveRequest command.
          *
+         * ### Minimum Value for PromisedActiveDuration
+         *
          * The minimum value of the PromisedActiveDuration field shall be equal to either 30000 milliseconds or
          * StayActiveDuration (from the received StayActiveRequest command), whichever is smaller.
          *
-         * @see {@link MatterSpecification.v141.Core} § 9.17.7.5.1
+         * @see {@link MatterSpecification.v141.Core} § 9.16.7.5.1
          */
         promisedActiveDuration: import("../tlv/TlvObject.js").FieldType<number>;
     }>;
@@ -336,7 +458,7 @@ export declare namespace IcdManagement {
      * This message shall be sent by the ICD in response to the StayActiveRequest command and shall contain the computed
      * duration (in milliseconds) that the ICD intends to stay active for.
      *
-     * @see {@link MatterSpecification.v141.Core} § 9.17.7.5
+     * @see {@link MatterSpecification.v141.Core} § 9.16.7.5
      */
     interface StayActiveResponse extends TypeFromSchema<typeof TlvStayActiveResponse> {
     }
@@ -351,14 +473,14 @@ export declare namespace IcdManagement {
              * fabric supported on the server, as indicated by the value of the SupportedFabrics attribute in the
              * Operational Credentials cluster.
              *
-             * @see {@link MatterSpecification.v141.Core} § 9.17.6.4
+             * @see {@link MatterSpecification.v141.Core} § 9.16.6.4
              */
             readonly registeredClients: FabricScopedAttribute<import("../tlv/TlvObject.js").TypeFromFields<{
                 /**
                  * This field shall indicate the NodeID of the Node to which Check-In messages will be sent when the
                  * MonitoredSubject is not subscribed.
                  *
-                 * @see {@link MatterSpecification.v141.Core} § 9.17.5.3.1
+                 * @see {@link MatterSpecification.v141.Core} § 9.16.5.3.1
                  */
                 checkInNodeId: import("../tlv/TlvObject.js").FieldType<import("../datatype/NodeId.js").NodeId>;
                 /**
@@ -381,14 +503,14 @@ export declare namespace IcdManagement {
                  * the server on the entry’s associated fabric bears the CASE Authenticated TAG value 0xAA12 and the version
                  * 0x0002 or higher within its NOC, then the entry matches.
                  *
-                 * @see {@link MatterSpecification.v141.Core} § 9.17.5.3.2
+                 * @see {@link MatterSpecification.v141.Core} § 9.16.5.3.2
                  */
                 monitoredSubject: import("../tlv/TlvObject.js").FieldType<import("../datatype/NodeId.js").NodeId>;
                 /**
                  * This field shall indicate the client’s type to inform the ICD of the availability for communication of the
                  * client.
                  *
-                 * @see {@link MatterSpecification.v141.Core} § 9.17.5.4
+                 * @see {@link MatterSpecification.v141.Core} § 9.16.5.3.4
                  */
                 clientType: import("../tlv/TlvObject.js").FieldType<ClientType>;
                 fabricIndex: import("../tlv/TlvObject.js").FieldType<import("../datatype/FabricIndex.js").FabricIndex>;
@@ -396,14 +518,14 @@ export declare namespace IcdManagement {
             /**
              * This attribute returns the value of the ICD Counter.
              *
-             * @see {@link MatterSpecification.v141.Core} § 9.17.6.5
+             * @see {@link MatterSpecification.v141.Core} § 9.16.6.5
              */
             readonly icdCounter: Attribute<number, any>;
             /**
              * Indicates the maximum number of entries that the server is able to store for each fabric in the
              * RegisteredClients attribute.
              *
-             * @see {@link MatterSpecification.v141.Core} § 9.17.6.6
+             * @see {@link MatterSpecification.v141.Core} § 9.16.6.6
              */
             readonly clientsSupportedPerFabric: FixedAttribute<number, any>;
             /**
@@ -412,7 +534,7 @@ export declare namespace IcdManagement {
              *
              * If the MaximumCheckInBackoff is equal to the IdleModeDuration, it means the ICD does not back-off.
              *
-             * @see {@link MatterSpecification.v141.Core} § 9.17.6.10
+             * @see {@link MatterSpecification.v141.Core} § 9.16.6.10
              */
             readonly maximumCheckInBackoff: FixedAttribute<number, any>;
         };
@@ -421,26 +543,27 @@ export declare namespace IcdManagement {
              * This command allows a client to register itself with the ICD to be notified when the device is available
              * for communication.
              *
-             * @see {@link MatterSpecification.v141.Core} § 9.17.7.1
+             * @see {@link MatterSpecification.v141.Core} § 9.16.7.1
              */
             readonly registerClient: Command<import("../tlv/TlvObject.js").TypeFromFields<{
                 /**
                  * This field shall provide the node ID to which a Check-In message will be sent if there are no active
                  * subscriptions matching MonitoredSubject.
                  *
-                 * @see {@link MatterSpecification.v141.Core} § 9.17.7.1.1
+                 * @see {@link MatterSpecification.v141.Core} § 9.16.7.1.1
                  */
                 checkInNodeId: import("../tlv/TlvObject.js").FieldType<import("../datatype/NodeId.js").NodeId>;
                 /**
                  * This field shall provide the monitored subject ID.
                  *
-                 * @see {@link MatterSpecification.v141.Core} § 9.17.7.1.2
+                 * @see {@link MatterSpecification.v141.Core} § 9.16.7.1.2
                  */
                 monitoredSubject: import("../tlv/TlvObject.js").FieldType<import("../datatype/NodeId.js").NodeId>;
                 /**
-                 * This field shall provide the shared secret between the client and the ICD to encrypt the Check-In message.
+                 * This field shall contain the ICDToken, a 128-bit symmetric key shared by the ICD and the ICD Client, used to
+                 * encrypt Check-In messages from this ICD to the MonitoredSubject.
                  *
-                 * @see {@link MatterSpecification.v141.Core} § 9.17.7.1.3
+                 * @see {@link MatterSpecification.v141.Core} § 9.16.7.1.3
                  */
                 key: import("../tlv/TlvObject.js").FieldType<AllowSharedBufferSource>;
                 /**
@@ -451,13 +574,68 @@ export declare namespace IcdManagement {
                  * provided by clients with administrator permissions for the server cluster. The verification key shall be
                  * ignored by the server if it is provided by a client with administrator permissions for the server cluster.
                  *
-                 * @see {@link MatterSpecification.v141.Core} § 9.17.7.1.4
+                 * @see {@link MatterSpecification.v141.Core} § 9.16.7.1.4
                  */
                 verificationKey: import("../tlv/TlvObject.js").OptionalFieldType<AllowSharedBufferSource>;
                 /**
                  * This field shall provide the client type of the client registering.
                  *
-                 * @see {@link MatterSpecification.v141.Core} § 9.17.7.1.5
+                 * ### Effect on Receipt
+                 *
+                 * On receipt of the RegisterClient command, the server shall perform the following procedure:
+                 *
+                 *   1. The server verifies that an entry for the fabric is available in the server’s list of registered
+                 *      clients.
+                 *
+                 *     a. If one of the entries in storage for the fabric has the same CheckInNodeID as the received
+                 *        CheckInNodeID, the server shall continue from step 2.
+                 *
+                 *     b. If there is an available entry for the fabric, an entry is created for the fabric and the received
+                 *        CheckInNodeID, MonitoredSubject, Key and ClientType are stored. The server shall continue from step 5.
+                 *
+                 *     c. If there are no available entries for the fabric, the status shall be RESOURCE_EXHAUSTED and the
+                 *        server shall continue from step 6.
+                 *
+                 *   2. The server shall verify the privileges of the command’s ISD.
+                 *
+                 *     a. If the ISD of the command has administrator privileges for the server cluster, the server shall
+                 *        continue from step 4.
+                 *
+                 *     b. If the ISD of the command does not have administrator privileges for the server cluster, the server
+                 *        shall continue from step 3.
+                 *
+                 *   3. The server shall verify that the received verification key is equal to the key previously stored in the
+                 *      list of registered clients with the matching CheckInNodeID.
+                 *
+                 *     a. If the verification key does not have a valid value, the status shall be FAILURE. the server shall
+                 *        continue from step 6.
+                 *
+                 *     b. If the verification key is not equal to the Key value stored in the entry, the status shall be
+                 *        FAILURE. The server shall continue from step 6.
+                 *
+                 *     c. If the verification key is equal to the Key value stored in the entry, the server shall continue from
+                 *        step 4.
+                 *
+                 *   4. The entry shall be updated with the received CheckInNodeID, MonitoredSubject, Key and ClientType.
+                 *
+                 *     a. If the update fails, the status shall be FAILURE. The server shall continue from step 6.
+                 *
+                 *     b. If the update succeeds, the server shall continue from step 5.
+                 *
+                 *   5. The server shall persist the client information.
+                 *
+                 *     a. If the persistence fails, the status shall be FAILURE and the server shall continue from step 6.
+                 *
+                 *     b. If the persistence succeeds, the status shall be SUCCESS and the server shall continue from step 6.
+                 *
+                 *   6. The server shall generate a response.
+                 *
+                 *     a. If the status is SUCCESS, the server shall generate a RegisterClientResponse command.
+                 *
+                 *     b. If the status is not SUCCESS, the server shall generate a default response with the Status field set
+                 *        to the evaluated error status.
+                 *
+                 * @see {@link MatterSpecification.v141.Core} § 9.16.7.1.5
                  */
                 clientType: import("../tlv/TlvObject.js").FieldType<ClientType>;
             }>, import("../tlv/TlvObject.js").TypeFromFields<{
@@ -468,13 +646,13 @@ export declare namespace IcdManagement {
              * network (e.g. running on a phone which is leaving the home) can (and should) remove its subscriptions and
              * send this UnregisterClient command before leaving to prevent the burden on the ICD of an absent client.
              *
-             * @see {@link MatterSpecification.v141.Core} § 9.17.7.3
+             * @see {@link MatterSpecification.v141.Core} § 9.16.7.3
              */
             readonly unregisterClient: Command<import("../tlv/TlvObject.js").TypeFromFields<{
                 /**
                  * This field shall provide the registered client node ID to remove from storage.
                  *
-                 * @see {@link MatterSpecification.v141.Core} § 9.17.7.3.1
+                 * @see {@link MatterSpecification.v141.Core} § 9.16.7.3.1
                  */
                 checkInNodeId: import("../tlv/TlvObject.js").FieldType<import("../datatype/NodeId.js").NodeId>;
                 /**
@@ -486,7 +664,61 @@ export declare namespace IcdManagement {
                  * server cluster. The verification key shall be ignored by the server if it is provided by a client with
                  * administrator permissions for the server cluster.
                  *
-                 * @see {@link MatterSpecification.v141.Core} § 9.17.7.3.2
+                 * ### Effect on Receipt
+                 *
+                 * On receipt of the UnregisterClient command, the server shall perform the following procedure:
+                 *
+                 *   1. The server shall check whether there is a entry stored on the device for the fabric with the same
+                 *      CheckInNodeID.
+                 *
+                 *     a. If there are no entries stored for the fabric, the status shall be NOT_FOUND. The server shall
+                 *        continue from step 6.
+                 *
+                 *     b. If there is an error when reading from storage, the status shall be FAILURE. The server shall continue
+                 *        from step 6.
+                 *
+                 *     c. If there is at least one entry stored on the server for the fabric, the server shall continue from
+                 *        step 2.
+                 *
+                 *   2. The server shall verify if one of the entries for the fabric has the corresponding CheckInNodeID
+                 *      received in the command.
+                 *
+                 *     a. If no entries have the corresponding CheckInNodeID, the status shall be NOT_FOUND. The server shall
+                 *        continue from step 6.
+                 *
+                 *     b. If an entry has the corresponding CheckInNodeID, the server shall continue to step 3.
+                 *
+                 *   3. The server shall check whether the ISD of the command has administrator permissions for the server
+                 *      cluster.
+                 *
+                 *     a. If the ISD of the command has administrator privileges for the server cluster, the server shall
+                 *        continue from step 5.
+                 *
+                 *     b. If the ISD of the command does not have administrator privileges for the server cluster, the server
+                 *        shall continue from step 4.
+                 *
+                 *   4. The server shall verify that the received verification key is equal to the key previously stored in the
+                 *      list of registered clients with the matching CheckInNodeID.
+                 *
+                 *     a. If the verification key does not have a valid value, the status shall be FAILURE. the server shall
+                 *        continue from step 6.
+                 *
+                 *     b. If the verification key is not equal to the Key value stored in the entry, the status shall be
+                 *        FAILURE. The server shall continue from step 6.
+                 *
+                 *     c. If the verification key is equal to the Key value stored in the entry, the server shall continue from
+                 *        step 5.
+                 *
+                 *   5. The server shall delete the entry with the matching CheckInNodeID from storage and will persist the
+                 *      change.
+                 *
+                 *     a. If the removal of the entry fails, the status shall be FAILURE. The server shall continue from step 6.
+                 *
+                 *     b. If the removal succeeds, the status shall be SUCCESS and the server shall continue to step 6.
+                 *
+                 *   6. The server shall generate a response with the Status field set to the evaluated status.
+                 *
+                 * @see {@link MatterSpecification.v141.Core} § 9.16.7.3.2
                  */
                 verificationKey: import("../tlv/TlvObject.js").OptionalFieldType<AllowSharedBufferSource>;
             }>, void, any>;
@@ -512,7 +744,7 @@ export declare namespace IcdManagement {
              * bitmap at the same time. However, a device shall NOT set more than one bit which has a dependency on the
              * UserActiveModeTriggerInstruction attribute.
              *
-             * @see {@link MatterSpecification.v141.Core} § 9.17.6.7
+             * @see {@link MatterSpecification.v141.Core} § 9.16.6.7
              */
             readonly userActiveModeTriggerHint: FixedAttribute<import("../schema/BitmapSchema.js").TypeFromPartialBitSchema<{
                 /**
@@ -592,13 +824,13 @@ export declare namespace IcdManagement {
     const LongIdleTimeSupportComponent: {
         readonly attributes: {
             /**
-             * This attribute shall indicate the operating mode of the ICD as specified in the OperatingModeEnum.
+             * Indicates the operating mode of the ICD as specified in the OperatingModeEnum.
              *
              *   • If the ICD is operating as a LIT ICD, OperatingMode shall be LIT.
              *
              *   • If the ICD is operating as a SIT ICD, OperatingMode shall be SIT.
              *
-             * @see {@link MatterSpecification.v141.Core} § 9.17.6.9
+             * @see {@link MatterSpecification.v141.Core} § 9.16.6.9
              */
             readonly operatingMode: Attribute<OperatingMode, any>;
         };
@@ -612,7 +844,25 @@ export declare namespace IcdManagement {
              * message exchanges during that period. The client may slightly overestimate the duration it wants the ICD
              * to be active for, in order to account for network delays.
              *
-             * @see {@link MatterSpecification.v141.Core} § 9.17.7.4
+             * ### Effect on Receipt
+             *
+             * When receiving a StayActiveRequest command, the server shall calculate the maximum PromisedActiveDuration
+             * it can remain active as the greater of the following two values:
+             *
+             *   • StayActiveDuration: Specified in the received command by the client.
+             *
+             *   • Remaining Active Time: The server’s planned remaining active time based on the ActiveModeThreshold
+             *     and its internal resources and power budget.
+             *
+             * A server may replace StayActiveDuration with Minimum Active Duration in the above calculation.
+             *
+             * PromisedActiveDuration represents the guaranteed minimum time the server will remain active, taking into
+             * account both the requested duration and the server’s capabilities.
+             *
+             * The ICD shall report the calculated PromisedActiveDuration in a StayActiveResponse message back to the
+             * client.
+             *
+             * @see {@link MatterSpecification.v141.Core} § 9.16.7.4
              */
             readonly stayActiveRequest: Command<import("../tlv/TlvObject.js").TypeFromFields<{
                 stayActiveDuration: import("../tlv/TlvObject.js").FieldType<number>;
@@ -621,10 +871,12 @@ export declare namespace IcdManagement {
                  * This field shall provide the actual duration that the ICD server can stay active from the time it receives
                  * the StayActiveRequest command.
                  *
+                 * ### Minimum Value for PromisedActiveDuration
+                 *
                  * The minimum value of the PromisedActiveDuration field shall be equal to either 30000 milliseconds or
                  * StayActiveDuration (from the received StayActiveRequest command), whichever is smaller.
                  *
-                 * @see {@link MatterSpecification.v141.Core} § 9.17.7.5.1
+                 * @see {@link MatterSpecification.v141.Core} § 9.16.7.5.1
                  */
                 promisedActiveDuration: import("../tlv/TlvObject.js").FieldType<number>;
             }>, any>;
@@ -642,26 +894,26 @@ export declare namespace IcdManagement {
              * When this feature is supported, the device shall support all the associated commands and attributes to
              * properly support the Check-In Protocol.
              *
-             * @see {@link MatterSpecification.v141.Core} § 9.17.4.1
+             * @see {@link MatterSpecification.v141.Core} § 9.16.4.1
              */
             readonly checkInProtocolSupport: BitFlag;
             /**
              * This feature is supported if and only if the device has a user active mode trigger.
              *
-             * @see {@link MatterSpecification.v141.Core} § 9.17.4.2
+             * @see {@link MatterSpecification.v141.Core} § 9.16.4.2
              */
             readonly userActiveModeTrigger: BitFlag;
             /**
              * This feature is supported if and only the device is a Long Idle Time ICD.
              *
-             * @see {@link MatterSpecification.v141.Core} § 9.17.4.3
+             * @see {@link MatterSpecification.v141.Core} § 9.16.4.3
              */
             readonly longIdleTimeSupport: BitFlag;
             /**
              * This feature is supported if and only if the device can switch between SIT and LIT operating modes even
              * if it has a valid registered client. See the dynamic SIT / LIT operating mode switching for more details.
              *
-             * @see {@link MatterSpecification.v141.Core} § 9.17.4.4
+             * @see {@link MatterSpecification.v141.Core} § 9.16.4.4
              */
             readonly dynamicSitLitSupport: BitFlag;
         };
@@ -670,21 +922,21 @@ export declare namespace IcdManagement {
              * Indicates the maximum interval in seconds the server can stay in idle mode. The IdleModeDuration shall
              * NOT be smaller than the ActiveModeDuration.
              *
-             * @see {@link MatterSpecification.v141.Core} § 9.17.6.1
+             * @see {@link MatterSpecification.v141.Core} § 9.16.6.1
              */
             readonly idleModeDuration: FixedAttribute<number, any>;
             /**
              * Indicates the minimum interval in milliseconds the server typically will stay in active mode after
              * initial transition out of idle mode. The ActiveModeDuration does not include the ActiveModeThreshold.
              *
-             * @see {@link MatterSpecification.v141.Core} § 9.17.6.2
+             * @see {@link MatterSpecification.v141.Core} § 9.16.6.2
              */
             readonly activeModeDuration: FixedAttribute<number, any>;
             /**
              * Indicates the minimum amount of time in milliseconds the server typically will stay active after network
              * activity when in active mode.
              *
-             * @see {@link MatterSpecification.v141.Core} § 9.17.6.3
+             * @see {@link MatterSpecification.v141.Core} § 9.16.6.3
              */
             readonly activeModeThreshold: FixedAttribute<number, any>;
             /**
@@ -697,9 +949,9 @@ export declare namespace IcdManagement {
              * string shall consist solely of an encoding of N as a decimal unsigned integer using the ASCII digits 0-9,
              * and without leading zeros.
              *
-             * For example, given UserActiveModeTriggerHint="2048", ResetButtonTimes is set which indicates "Press Reset
-             * Button for N seconds". Therefore, a value of UserActiveModeTriggerInstruction="10" would indicate that N
-             * is 10 in that context.
+             * For example, given UserActiveModeTriggerHint="1024", ResetButtonSeconds is set which indicates "Press
+             * Reset Button for N seconds". Therefore, a value of UserActiveModeTriggerInstruction="6" would indicate
+             * that N is 6 in that context.
              *
              * When CustomInstruction is set by the UserActiveModeTriggerHint attribute, indicating presence of a custom
              * string, the ICD SHOULD perform localization (translation to user’s preferred language, as indicated in
@@ -712,7 +964,7 @@ export declare namespace IcdManagement {
              * UserActiveModeTriggerInstruction attribute, the string shall consist of exactly 6 hexadecimal digits
              * using the ASCII characters 0-F and encoding the RGB color value as used in HTML encodings.
              *
-             * @see {@link MatterSpecification.v141.Core} § 9.17.6.8
+             * @see {@link MatterSpecification.v141.Core} § 9.16.6.8
              */
             readonly userActiveModeTriggerInstruction: OptionalFixedAttribute<string, any>;
         };
@@ -726,7 +978,25 @@ export declare namespace IcdManagement {
              * message exchanges during that period. The client may slightly overestimate the duration it wants the ICD
              * to be active for, in order to account for network delays.
              *
-             * @see {@link MatterSpecification.v141.Core} § 9.17.7.4
+             * ### Effect on Receipt
+             *
+             * When receiving a StayActiveRequest command, the server shall calculate the maximum PromisedActiveDuration
+             * it can remain active as the greater of the following two values:
+             *
+             *   • StayActiveDuration: Specified in the received command by the client.
+             *
+             *   • Remaining Active Time: The server’s planned remaining active time based on the ActiveModeThreshold
+             *     and its internal resources and power budget.
+             *
+             * A server may replace StayActiveDuration with Minimum Active Duration in the above calculation.
+             *
+             * PromisedActiveDuration represents the guaranteed minimum time the server will remain active, taking into
+             * account both the requested duration and the server’s capabilities.
+             *
+             * The ICD shall report the calculated PromisedActiveDuration in a StayActiveResponse message back to the
+             * client.
+             *
+             * @see {@link MatterSpecification.v141.Core} § 9.16.7.4
              */
             readonly stayActiveRequest: OptionalCommand<import("../tlv/TlvObject.js").TypeFromFields<{
                 stayActiveDuration: import("../tlv/TlvObject.js").FieldType<number>;
@@ -735,10 +1005,12 @@ export declare namespace IcdManagement {
                  * This field shall provide the actual duration that the ICD server can stay active from the time it receives
                  * the StayActiveRequest command.
                  *
+                 * ### Minimum Value for PromisedActiveDuration
+                 *
                  * The minimum value of the PromisedActiveDuration field shall be equal to either 30000 milliseconds or
                  * StayActiveDuration (from the received StayActiveRequest command), whichever is smaller.
                  *
-                 * @see {@link MatterSpecification.v141.Core} § 9.17.7.5.1
+                 * @see {@link MatterSpecification.v141.Core} § 9.16.7.5.1
                  */
                 promisedActiveDuration: import("../tlv/TlvObject.js").FieldType<number>;
             }>, any>;
@@ -759,14 +1031,14 @@ export declare namespace IcdManagement {
                      * fabric supported on the server, as indicated by the value of the SupportedFabrics attribute in the
                      * Operational Credentials cluster.
                      *
-                     * @see {@link MatterSpecification.v141.Core} § 9.17.6.4
+                     * @see {@link MatterSpecification.v141.Core} § 9.16.6.4
                      */
                     readonly registeredClients: FabricScopedAttribute<import("../tlv/TlvObject.js").TypeFromFields<{
                         /**
                          * This field shall indicate the NodeID of the Node to which Check-In messages will be sent when the
                          * MonitoredSubject is not subscribed.
                          *
-                         * @see {@link MatterSpecification.v141.Core} § 9.17.5.3.1
+                         * @see {@link MatterSpecification.v141.Core} § 9.16.5.3.1
                          */
                         checkInNodeId: import("../tlv/TlvObject.js").FieldType<import("../datatype/NodeId.js").NodeId>;
                         /**
@@ -789,14 +1061,14 @@ export declare namespace IcdManagement {
                          * the server on the entry’s associated fabric bears the CASE Authenticated TAG value 0xAA12 and the version
                          * 0x0002 or higher within its NOC, then the entry matches.
                          *
-                         * @see {@link MatterSpecification.v141.Core} § 9.17.5.3.2
+                         * @see {@link MatterSpecification.v141.Core} § 9.16.5.3.2
                          */
                         monitoredSubject: import("../tlv/TlvObject.js").FieldType<import("../datatype/NodeId.js").NodeId>;
                         /**
                          * This field shall indicate the client’s type to inform the ICD of the availability for communication of the
                          * client.
                          *
-                         * @see {@link MatterSpecification.v141.Core} § 9.17.5.4
+                         * @see {@link MatterSpecification.v141.Core} § 9.16.5.3.4
                          */
                         clientType: import("../tlv/TlvObject.js").FieldType<ClientType>;
                         fabricIndex: import("../tlv/TlvObject.js").FieldType<import("../datatype/FabricIndex.js").FabricIndex>;
@@ -804,14 +1076,14 @@ export declare namespace IcdManagement {
                     /**
                      * This attribute returns the value of the ICD Counter.
                      *
-                     * @see {@link MatterSpecification.v141.Core} § 9.17.6.5
+                     * @see {@link MatterSpecification.v141.Core} § 9.16.6.5
                      */
                     readonly icdCounter: Attribute<number, any>;
                     /**
                      * Indicates the maximum number of entries that the server is able to store for each fabric in the
                      * RegisteredClients attribute.
                      *
-                     * @see {@link MatterSpecification.v141.Core} § 9.17.6.6
+                     * @see {@link MatterSpecification.v141.Core} § 9.16.6.6
                      */
                     readonly clientsSupportedPerFabric: FixedAttribute<number, any>;
                     /**
@@ -820,7 +1092,7 @@ export declare namespace IcdManagement {
                      *
                      * If the MaximumCheckInBackoff is equal to the IdleModeDuration, it means the ICD does not back-off.
                      *
-                     * @see {@link MatterSpecification.v141.Core} § 9.17.6.10
+                     * @see {@link MatterSpecification.v141.Core} § 9.16.6.10
                      */
                     readonly maximumCheckInBackoff: FixedAttribute<number, any>;
                 };
@@ -829,26 +1101,27 @@ export declare namespace IcdManagement {
                      * This command allows a client to register itself with the ICD to be notified when the device is available
                      * for communication.
                      *
-                     * @see {@link MatterSpecification.v141.Core} § 9.17.7.1
+                     * @see {@link MatterSpecification.v141.Core} § 9.16.7.1
                      */
                     readonly registerClient: Command<import("../tlv/TlvObject.js").TypeFromFields<{
                         /**
                          * This field shall provide the node ID to which a Check-In message will be sent if there are no active
                          * subscriptions matching MonitoredSubject.
                          *
-                         * @see {@link MatterSpecification.v141.Core} § 9.17.7.1.1
+                         * @see {@link MatterSpecification.v141.Core} § 9.16.7.1.1
                          */
                         checkInNodeId: import("../tlv/TlvObject.js").FieldType<import("../datatype/NodeId.js").NodeId>;
                         /**
                          * This field shall provide the monitored subject ID.
                          *
-                         * @see {@link MatterSpecification.v141.Core} § 9.17.7.1.2
+                         * @see {@link MatterSpecification.v141.Core} § 9.16.7.1.2
                          */
                         monitoredSubject: import("../tlv/TlvObject.js").FieldType<import("../datatype/NodeId.js").NodeId>;
                         /**
-                         * This field shall provide the shared secret between the client and the ICD to encrypt the Check-In message.
+                         * This field shall contain the ICDToken, a 128-bit symmetric key shared by the ICD and the ICD Client, used to
+                         * encrypt Check-In messages from this ICD to the MonitoredSubject.
                          *
-                         * @see {@link MatterSpecification.v141.Core} § 9.17.7.1.3
+                         * @see {@link MatterSpecification.v141.Core} § 9.16.7.1.3
                          */
                         key: import("../tlv/TlvObject.js").FieldType<AllowSharedBufferSource>;
                         /**
@@ -859,13 +1132,68 @@ export declare namespace IcdManagement {
                          * provided by clients with administrator permissions for the server cluster. The verification key shall be
                          * ignored by the server if it is provided by a client with administrator permissions for the server cluster.
                          *
-                         * @see {@link MatterSpecification.v141.Core} § 9.17.7.1.4
+                         * @see {@link MatterSpecification.v141.Core} § 9.16.7.1.4
                          */
                         verificationKey: import("../tlv/TlvObject.js").OptionalFieldType<AllowSharedBufferSource>;
                         /**
                          * This field shall provide the client type of the client registering.
                          *
-                         * @see {@link MatterSpecification.v141.Core} § 9.17.7.1.5
+                         * ### Effect on Receipt
+                         *
+                         * On receipt of the RegisterClient command, the server shall perform the following procedure:
+                         *
+                         *   1. The server verifies that an entry for the fabric is available in the server’s list of registered
+                         *      clients.
+                         *
+                         *     a. If one of the entries in storage for the fabric has the same CheckInNodeID as the received
+                         *        CheckInNodeID, the server shall continue from step 2.
+                         *
+                         *     b. If there is an available entry for the fabric, an entry is created for the fabric and the received
+                         *        CheckInNodeID, MonitoredSubject, Key and ClientType are stored. The server shall continue from step 5.
+                         *
+                         *     c. If there are no available entries for the fabric, the status shall be RESOURCE_EXHAUSTED and the
+                         *        server shall continue from step 6.
+                         *
+                         *   2. The server shall verify the privileges of the command’s ISD.
+                         *
+                         *     a. If the ISD of the command has administrator privileges for the server cluster, the server shall
+                         *        continue from step 4.
+                         *
+                         *     b. If the ISD of the command does not have administrator privileges for the server cluster, the server
+                         *        shall continue from step 3.
+                         *
+                         *   3. The server shall verify that the received verification key is equal to the key previously stored in the
+                         *      list of registered clients with the matching CheckInNodeID.
+                         *
+                         *     a. If the verification key does not have a valid value, the status shall be FAILURE. the server shall
+                         *        continue from step 6.
+                         *
+                         *     b. If the verification key is not equal to the Key value stored in the entry, the status shall be
+                         *        FAILURE. The server shall continue from step 6.
+                         *
+                         *     c. If the verification key is equal to the Key value stored in the entry, the server shall continue from
+                         *        step 4.
+                         *
+                         *   4. The entry shall be updated with the received CheckInNodeID, MonitoredSubject, Key and ClientType.
+                         *
+                         *     a. If the update fails, the status shall be FAILURE. The server shall continue from step 6.
+                         *
+                         *     b. If the update succeeds, the server shall continue from step 5.
+                         *
+                         *   5. The server shall persist the client information.
+                         *
+                         *     a. If the persistence fails, the status shall be FAILURE and the server shall continue from step 6.
+                         *
+                         *     b. If the persistence succeeds, the status shall be SUCCESS and the server shall continue from step 6.
+                         *
+                         *   6. The server shall generate a response.
+                         *
+                         *     a. If the status is SUCCESS, the server shall generate a RegisterClientResponse command.
+                         *
+                         *     b. If the status is not SUCCESS, the server shall generate a default response with the Status field set
+                         *        to the evaluated error status.
+                         *
+                         * @see {@link MatterSpecification.v141.Core} § 9.16.7.1.5
                          */
                         clientType: import("../tlv/TlvObject.js").FieldType<ClientType>;
                     }>, import("../tlv/TlvObject.js").TypeFromFields<{
@@ -876,13 +1204,13 @@ export declare namespace IcdManagement {
                      * network (e.g. running on a phone which is leaving the home) can (and should) remove its subscriptions and
                      * send this UnregisterClient command before leaving to prevent the burden on the ICD of an absent client.
                      *
-                     * @see {@link MatterSpecification.v141.Core} § 9.17.7.3
+                     * @see {@link MatterSpecification.v141.Core} § 9.16.7.3
                      */
                     readonly unregisterClient: Command<import("../tlv/TlvObject.js").TypeFromFields<{
                         /**
                          * This field shall provide the registered client node ID to remove from storage.
                          *
-                         * @see {@link MatterSpecification.v141.Core} § 9.17.7.3.1
+                         * @see {@link MatterSpecification.v141.Core} § 9.16.7.3.1
                          */
                         checkInNodeId: import("../tlv/TlvObject.js").FieldType<import("../datatype/NodeId.js").NodeId>;
                         /**
@@ -894,7 +1222,61 @@ export declare namespace IcdManagement {
                          * server cluster. The verification key shall be ignored by the server if it is provided by a client with
                          * administrator permissions for the server cluster.
                          *
-                         * @see {@link MatterSpecification.v141.Core} § 9.17.7.3.2
+                         * ### Effect on Receipt
+                         *
+                         * On receipt of the UnregisterClient command, the server shall perform the following procedure:
+                         *
+                         *   1. The server shall check whether there is a entry stored on the device for the fabric with the same
+                         *      CheckInNodeID.
+                         *
+                         *     a. If there are no entries stored for the fabric, the status shall be NOT_FOUND. The server shall
+                         *        continue from step 6.
+                         *
+                         *     b. If there is an error when reading from storage, the status shall be FAILURE. The server shall continue
+                         *        from step 6.
+                         *
+                         *     c. If there is at least one entry stored on the server for the fabric, the server shall continue from
+                         *        step 2.
+                         *
+                         *   2. The server shall verify if one of the entries for the fabric has the corresponding CheckInNodeID
+                         *      received in the command.
+                         *
+                         *     a. If no entries have the corresponding CheckInNodeID, the status shall be NOT_FOUND. The server shall
+                         *        continue from step 6.
+                         *
+                         *     b. If an entry has the corresponding CheckInNodeID, the server shall continue to step 3.
+                         *
+                         *   3. The server shall check whether the ISD of the command has administrator permissions for the server
+                         *      cluster.
+                         *
+                         *     a. If the ISD of the command has administrator privileges for the server cluster, the server shall
+                         *        continue from step 5.
+                         *
+                         *     b. If the ISD of the command does not have administrator privileges for the server cluster, the server
+                         *        shall continue from step 4.
+                         *
+                         *   4. The server shall verify that the received verification key is equal to the key previously stored in the
+                         *      list of registered clients with the matching CheckInNodeID.
+                         *
+                         *     a. If the verification key does not have a valid value, the status shall be FAILURE. the server shall
+                         *        continue from step 6.
+                         *
+                         *     b. If the verification key is not equal to the Key value stored in the entry, the status shall be
+                         *        FAILURE. The server shall continue from step 6.
+                         *
+                         *     c. If the verification key is equal to the Key value stored in the entry, the server shall continue from
+                         *        step 5.
+                         *
+                         *   5. The server shall delete the entry with the matching CheckInNodeID from storage and will persist the
+                         *      change.
+                         *
+                         *     a. If the removal of the entry fails, the status shall be FAILURE. The server shall continue from step 6.
+                         *
+                         *     b. If the removal succeeds, the status shall be SUCCESS and the server shall continue to step 6.
+                         *
+                         *   6. The server shall generate a response with the Status field set to the evaluated status.
+                         *
+                         * @see {@link MatterSpecification.v141.Core} § 9.16.7.3.2
                          */
                         verificationKey: import("../tlv/TlvObject.js").OptionalFieldType<AllowSharedBufferSource>;
                     }>, void, any>;
@@ -921,7 +1303,7 @@ export declare namespace IcdManagement {
                      * bitmap at the same time. However, a device shall NOT set more than one bit which has a dependency on the
                      * UserActiveModeTriggerInstruction attribute.
                      *
-                     * @see {@link MatterSpecification.v141.Core} § 9.17.6.7
+                     * @see {@link MatterSpecification.v141.Core} § 9.16.6.7
                      */
                     readonly userActiveModeTriggerHint: FixedAttribute<import("../schema/BitmapSchema.js").TypeFromPartialBitSchema<{
                         /**
@@ -1002,13 +1384,13 @@ export declare namespace IcdManagement {
             readonly component: {
                 readonly attributes: {
                     /**
-                     * This attribute shall indicate the operating mode of the ICD as specified in the OperatingModeEnum.
+                     * Indicates the operating mode of the ICD as specified in the OperatingModeEnum.
                      *
                      *   • If the ICD is operating as a LIT ICD, OperatingMode shall be LIT.
                      *
                      *   • If the ICD is operating as a SIT ICD, OperatingMode shall be SIT.
                      *
-                     * @see {@link MatterSpecification.v141.Core} § 9.17.6.9
+                     * @see {@link MatterSpecification.v141.Core} § 9.16.6.9
                      */
                     readonly operatingMode: Attribute<OperatingMode, any>;
                 };
@@ -1022,7 +1404,25 @@ export declare namespace IcdManagement {
                      * message exchanges during that period. The client may slightly overestimate the duration it wants the ICD
                      * to be active for, in order to account for network delays.
                      *
-                     * @see {@link MatterSpecification.v141.Core} § 9.17.7.4
+                     * ### Effect on Receipt
+                     *
+                     * When receiving a StayActiveRequest command, the server shall calculate the maximum PromisedActiveDuration
+                     * it can remain active as the greater of the following two values:
+                     *
+                     *   • StayActiveDuration: Specified in the received command by the client.
+                     *
+                     *   • Remaining Active Time: The server’s planned remaining active time based on the ActiveModeThreshold
+                     *     and its internal resources and power budget.
+                     *
+                     * A server may replace StayActiveDuration with Minimum Active Duration in the above calculation.
+                     *
+                     * PromisedActiveDuration represents the guaranteed minimum time the server will remain active, taking into
+                     * account both the requested duration and the server’s capabilities.
+                     *
+                     * The ICD shall report the calculated PromisedActiveDuration in a StayActiveResponse message back to the
+                     * client.
+                     *
+                     * @see {@link MatterSpecification.v141.Core} § 9.16.7.4
                      */
                     readonly stayActiveRequest: Command<import("../tlv/TlvObject.js").TypeFromFields<{
                         stayActiveDuration: import("../tlv/TlvObject.js").FieldType<number>;
@@ -1031,10 +1431,12 @@ export declare namespace IcdManagement {
                          * This field shall provide the actual duration that the ICD server can stay active from the time it receives
                          * the StayActiveRequest command.
                          *
+                         * ### Minimum Value for PromisedActiveDuration
+                         *
                          * The minimum value of the PromisedActiveDuration field shall be equal to either 30000 milliseconds or
                          * StayActiveDuration (from the received StayActiveRequest command), whichever is smaller.
                          *
-                         * @see {@link MatterSpecification.v141.Core} § 9.17.7.5.1
+                         * @see {@link MatterSpecification.v141.Core} § 9.16.7.5.1
                          */
                         promisedActiveDuration: import("../tlv/TlvObject.js").FieldType<number>;
                     }>, any>;
@@ -1072,26 +1474,26 @@ export declare namespace IcdManagement {
              * When this feature is supported, the device shall support all the associated commands and attributes to
              * properly support the Check-In Protocol.
              *
-             * @see {@link MatterSpecification.v141.Core} § 9.17.4.1
+             * @see {@link MatterSpecification.v141.Core} § 9.16.4.1
              */
             readonly checkInProtocolSupport: BitFlag;
             /**
              * This feature is supported if and only if the device has a user active mode trigger.
              *
-             * @see {@link MatterSpecification.v141.Core} § 9.17.4.2
+             * @see {@link MatterSpecification.v141.Core} § 9.16.4.2
              */
             readonly userActiveModeTrigger: BitFlag;
             /**
              * This feature is supported if and only the device is a Long Idle Time ICD.
              *
-             * @see {@link MatterSpecification.v141.Core} § 9.17.4.3
+             * @see {@link MatterSpecification.v141.Core} § 9.16.4.3
              */
             readonly longIdleTimeSupport: BitFlag;
             /**
              * This feature is supported if and only if the device can switch between SIT and LIT operating modes even
              * if it has a valid registered client. See the dynamic SIT / LIT operating mode switching for more details.
              *
-             * @see {@link MatterSpecification.v141.Core} § 9.17.4.4
+             * @see {@link MatterSpecification.v141.Core} § 9.16.4.4
              */
             readonly dynamicSitLitSupport: BitFlag;
         };
@@ -1100,21 +1502,21 @@ export declare namespace IcdManagement {
              * Indicates the maximum interval in seconds the server can stay in idle mode. The IdleModeDuration shall
              * NOT be smaller than the ActiveModeDuration.
              *
-             * @see {@link MatterSpecification.v141.Core} § 9.17.6.1
+             * @see {@link MatterSpecification.v141.Core} § 9.16.6.1
              */
             readonly idleModeDuration: FixedAttribute<number, any>;
             /**
              * Indicates the minimum interval in milliseconds the server typically will stay in active mode after
              * initial transition out of idle mode. The ActiveModeDuration does not include the ActiveModeThreshold.
              *
-             * @see {@link MatterSpecification.v141.Core} § 9.17.6.2
+             * @see {@link MatterSpecification.v141.Core} § 9.16.6.2
              */
             readonly activeModeDuration: FixedAttribute<number, any>;
             /**
              * Indicates the minimum amount of time in milliseconds the server typically will stay active after network
              * activity when in active mode.
              *
-             * @see {@link MatterSpecification.v141.Core} § 9.17.6.3
+             * @see {@link MatterSpecification.v141.Core} § 9.16.6.3
              */
             readonly activeModeThreshold: FixedAttribute<number, any>;
             /**
@@ -1127,9 +1529,9 @@ export declare namespace IcdManagement {
              * string shall consist solely of an encoding of N as a decimal unsigned integer using the ASCII digits 0-9,
              * and without leading zeros.
              *
-             * For example, given UserActiveModeTriggerHint="2048", ResetButtonTimes is set which indicates "Press Reset
-             * Button for N seconds". Therefore, a value of UserActiveModeTriggerInstruction="10" would indicate that N
-             * is 10 in that context.
+             * For example, given UserActiveModeTriggerHint="1024", ResetButtonSeconds is set which indicates "Press
+             * Reset Button for N seconds". Therefore, a value of UserActiveModeTriggerInstruction="6" would indicate
+             * that N is 6 in that context.
              *
              * When CustomInstruction is set by the UserActiveModeTriggerHint attribute, indicating presence of a custom
              * string, the ICD SHOULD perform localization (translation to user’s preferred language, as indicated in
@@ -1142,7 +1544,7 @@ export declare namespace IcdManagement {
              * UserActiveModeTriggerInstruction attribute, the string shall consist of exactly 6 hexadecimal digits
              * using the ASCII characters 0-F and encoding the RGB color value as used in HTML encodings.
              *
-             * @see {@link MatterSpecification.v141.Core} § 9.17.6.8
+             * @see {@link MatterSpecification.v141.Core} § 9.16.6.8
              */
             readonly userActiveModeTriggerInstruction: OptionalFixedAttribute<string, any>;
         };
@@ -1156,7 +1558,25 @@ export declare namespace IcdManagement {
              * message exchanges during that period. The client may slightly overestimate the duration it wants the ICD
              * to be active for, in order to account for network delays.
              *
-             * @see {@link MatterSpecification.v141.Core} § 9.17.7.4
+             * ### Effect on Receipt
+             *
+             * When receiving a StayActiveRequest command, the server shall calculate the maximum PromisedActiveDuration
+             * it can remain active as the greater of the following two values:
+             *
+             *   • StayActiveDuration: Specified in the received command by the client.
+             *
+             *   • Remaining Active Time: The server’s planned remaining active time based on the ActiveModeThreshold
+             *     and its internal resources and power budget.
+             *
+             * A server may replace StayActiveDuration with Minimum Active Duration in the above calculation.
+             *
+             * PromisedActiveDuration represents the guaranteed minimum time the server will remain active, taking into
+             * account both the requested duration and the server’s capabilities.
+             *
+             * The ICD shall report the calculated PromisedActiveDuration in a StayActiveResponse message back to the
+             * client.
+             *
+             * @see {@link MatterSpecification.v141.Core} § 9.16.7.4
              */
             readonly stayActiveRequest: OptionalCommand<import("../tlv/TlvObject.js").TypeFromFields<{
                 stayActiveDuration: import("../tlv/TlvObject.js").FieldType<number>;
@@ -1165,10 +1585,12 @@ export declare namespace IcdManagement {
                  * This field shall provide the actual duration that the ICD server can stay active from the time it receives
                  * the StayActiveRequest command.
                  *
+                 * ### Minimum Value for PromisedActiveDuration
+                 *
                  * The minimum value of the PromisedActiveDuration field shall be equal to either 30000 milliseconds or
                  * StayActiveDuration (from the received StayActiveRequest command), whichever is smaller.
                  *
-                 * @see {@link MatterSpecification.v141.Core} § 9.17.7.5.1
+                 * @see {@link MatterSpecification.v141.Core} § 9.16.7.5.1
                  */
                 promisedActiveDuration: import("../tlv/TlvObject.js").FieldType<number>;
             }>, any>;
@@ -1189,14 +1611,14 @@ export declare namespace IcdManagement {
                      * fabric supported on the server, as indicated by the value of the SupportedFabrics attribute in the
                      * Operational Credentials cluster.
                      *
-                     * @see {@link MatterSpecification.v141.Core} § 9.17.6.4
+                     * @see {@link MatterSpecification.v141.Core} § 9.16.6.4
                      */
                     readonly registeredClients: FabricScopedAttribute<import("../tlv/TlvObject.js").TypeFromFields<{
                         /**
                          * This field shall indicate the NodeID of the Node to which Check-In messages will be sent when the
                          * MonitoredSubject is not subscribed.
                          *
-                         * @see {@link MatterSpecification.v141.Core} § 9.17.5.3.1
+                         * @see {@link MatterSpecification.v141.Core} § 9.16.5.3.1
                          */
                         checkInNodeId: import("../tlv/TlvObject.js").FieldType<import("../datatype/NodeId.js").NodeId>;
                         /**
@@ -1219,14 +1641,14 @@ export declare namespace IcdManagement {
                          * the server on the entry’s associated fabric bears the CASE Authenticated TAG value 0xAA12 and the version
                          * 0x0002 or higher within its NOC, then the entry matches.
                          *
-                         * @see {@link MatterSpecification.v141.Core} § 9.17.5.3.2
+                         * @see {@link MatterSpecification.v141.Core} § 9.16.5.3.2
                          */
                         monitoredSubject: import("../tlv/TlvObject.js").FieldType<import("../datatype/NodeId.js").NodeId>;
                         /**
                          * This field shall indicate the client’s type to inform the ICD of the availability for communication of the
                          * client.
                          *
-                         * @see {@link MatterSpecification.v141.Core} § 9.17.5.4
+                         * @see {@link MatterSpecification.v141.Core} § 9.16.5.3.4
                          */
                         clientType: import("../tlv/TlvObject.js").FieldType<ClientType>;
                         fabricIndex: import("../tlv/TlvObject.js").FieldType<import("../datatype/FabricIndex.js").FabricIndex>;
@@ -1234,14 +1656,14 @@ export declare namespace IcdManagement {
                     /**
                      * This attribute returns the value of the ICD Counter.
                      *
-                     * @see {@link MatterSpecification.v141.Core} § 9.17.6.5
+                     * @see {@link MatterSpecification.v141.Core} § 9.16.6.5
                      */
                     readonly icdCounter: Attribute<number, any>;
                     /**
                      * Indicates the maximum number of entries that the server is able to store for each fabric in the
                      * RegisteredClients attribute.
                      *
-                     * @see {@link MatterSpecification.v141.Core} § 9.17.6.6
+                     * @see {@link MatterSpecification.v141.Core} § 9.16.6.6
                      */
                     readonly clientsSupportedPerFabric: FixedAttribute<number, any>;
                     /**
@@ -1250,7 +1672,7 @@ export declare namespace IcdManagement {
                      *
                      * If the MaximumCheckInBackoff is equal to the IdleModeDuration, it means the ICD does not back-off.
                      *
-                     * @see {@link MatterSpecification.v141.Core} § 9.17.6.10
+                     * @see {@link MatterSpecification.v141.Core} § 9.16.6.10
                      */
                     readonly maximumCheckInBackoff: FixedAttribute<number, any>;
                 };
@@ -1259,26 +1681,27 @@ export declare namespace IcdManagement {
                      * This command allows a client to register itself with the ICD to be notified when the device is available
                      * for communication.
                      *
-                     * @see {@link MatterSpecification.v141.Core} § 9.17.7.1
+                     * @see {@link MatterSpecification.v141.Core} § 9.16.7.1
                      */
                     readonly registerClient: Command<import("../tlv/TlvObject.js").TypeFromFields<{
                         /**
                          * This field shall provide the node ID to which a Check-In message will be sent if there are no active
                          * subscriptions matching MonitoredSubject.
                          *
-                         * @see {@link MatterSpecification.v141.Core} § 9.17.7.1.1
+                         * @see {@link MatterSpecification.v141.Core} § 9.16.7.1.1
                          */
                         checkInNodeId: import("../tlv/TlvObject.js").FieldType<import("../datatype/NodeId.js").NodeId>;
                         /**
                          * This field shall provide the monitored subject ID.
                          *
-                         * @see {@link MatterSpecification.v141.Core} § 9.17.7.1.2
+                         * @see {@link MatterSpecification.v141.Core} § 9.16.7.1.2
                          */
                         monitoredSubject: import("../tlv/TlvObject.js").FieldType<import("../datatype/NodeId.js").NodeId>;
                         /**
-                         * This field shall provide the shared secret between the client and the ICD to encrypt the Check-In message.
+                         * This field shall contain the ICDToken, a 128-bit symmetric key shared by the ICD and the ICD Client, used to
+                         * encrypt Check-In messages from this ICD to the MonitoredSubject.
                          *
-                         * @see {@link MatterSpecification.v141.Core} § 9.17.7.1.3
+                         * @see {@link MatterSpecification.v141.Core} § 9.16.7.1.3
                          */
                         key: import("../tlv/TlvObject.js").FieldType<AllowSharedBufferSource>;
                         /**
@@ -1289,13 +1712,68 @@ export declare namespace IcdManagement {
                          * provided by clients with administrator permissions for the server cluster. The verification key shall be
                          * ignored by the server if it is provided by a client with administrator permissions for the server cluster.
                          *
-                         * @see {@link MatterSpecification.v141.Core} § 9.17.7.1.4
+                         * @see {@link MatterSpecification.v141.Core} § 9.16.7.1.4
                          */
                         verificationKey: import("../tlv/TlvObject.js").OptionalFieldType<AllowSharedBufferSource>;
                         /**
                          * This field shall provide the client type of the client registering.
                          *
-                         * @see {@link MatterSpecification.v141.Core} § 9.17.7.1.5
+                         * ### Effect on Receipt
+                         *
+                         * On receipt of the RegisterClient command, the server shall perform the following procedure:
+                         *
+                         *   1. The server verifies that an entry for the fabric is available in the server’s list of registered
+                         *      clients.
+                         *
+                         *     a. If one of the entries in storage for the fabric has the same CheckInNodeID as the received
+                         *        CheckInNodeID, the server shall continue from step 2.
+                         *
+                         *     b. If there is an available entry for the fabric, an entry is created for the fabric and the received
+                         *        CheckInNodeID, MonitoredSubject, Key and ClientType are stored. The server shall continue from step 5.
+                         *
+                         *     c. If there are no available entries for the fabric, the status shall be RESOURCE_EXHAUSTED and the
+                         *        server shall continue from step 6.
+                         *
+                         *   2. The server shall verify the privileges of the command’s ISD.
+                         *
+                         *     a. If the ISD of the command has administrator privileges for the server cluster, the server shall
+                         *        continue from step 4.
+                         *
+                         *     b. If the ISD of the command does not have administrator privileges for the server cluster, the server
+                         *        shall continue from step 3.
+                         *
+                         *   3. The server shall verify that the received verification key is equal to the key previously stored in the
+                         *      list of registered clients with the matching CheckInNodeID.
+                         *
+                         *     a. If the verification key does not have a valid value, the status shall be FAILURE. the server shall
+                         *        continue from step 6.
+                         *
+                         *     b. If the verification key is not equal to the Key value stored in the entry, the status shall be
+                         *        FAILURE. The server shall continue from step 6.
+                         *
+                         *     c. If the verification key is equal to the Key value stored in the entry, the server shall continue from
+                         *        step 4.
+                         *
+                         *   4. The entry shall be updated with the received CheckInNodeID, MonitoredSubject, Key and ClientType.
+                         *
+                         *     a. If the update fails, the status shall be FAILURE. The server shall continue from step 6.
+                         *
+                         *     b. If the update succeeds, the server shall continue from step 5.
+                         *
+                         *   5. The server shall persist the client information.
+                         *
+                         *     a. If the persistence fails, the status shall be FAILURE and the server shall continue from step 6.
+                         *
+                         *     b. If the persistence succeeds, the status shall be SUCCESS and the server shall continue from step 6.
+                         *
+                         *   6. The server shall generate a response.
+                         *
+                         *     a. If the status is SUCCESS, the server shall generate a RegisterClientResponse command.
+                         *
+                         *     b. If the status is not SUCCESS, the server shall generate a default response with the Status field set
+                         *        to the evaluated error status.
+                         *
+                         * @see {@link MatterSpecification.v141.Core} § 9.16.7.1.5
                          */
                         clientType: import("../tlv/TlvObject.js").FieldType<ClientType>;
                     }>, import("../tlv/TlvObject.js").TypeFromFields<{
@@ -1306,13 +1784,13 @@ export declare namespace IcdManagement {
                      * network (e.g. running on a phone which is leaving the home) can (and should) remove its subscriptions and
                      * send this UnregisterClient command before leaving to prevent the burden on the ICD of an absent client.
                      *
-                     * @see {@link MatterSpecification.v141.Core} § 9.17.7.3
+                     * @see {@link MatterSpecification.v141.Core} § 9.16.7.3
                      */
                     readonly unregisterClient: Command<import("../tlv/TlvObject.js").TypeFromFields<{
                         /**
                          * This field shall provide the registered client node ID to remove from storage.
                          *
-                         * @see {@link MatterSpecification.v141.Core} § 9.17.7.3.1
+                         * @see {@link MatterSpecification.v141.Core} § 9.16.7.3.1
                          */
                         checkInNodeId: import("../tlv/TlvObject.js").FieldType<import("../datatype/NodeId.js").NodeId>;
                         /**
@@ -1324,7 +1802,61 @@ export declare namespace IcdManagement {
                          * server cluster. The verification key shall be ignored by the server if it is provided by a client with
                          * administrator permissions for the server cluster.
                          *
-                         * @see {@link MatterSpecification.v141.Core} § 9.17.7.3.2
+                         * ### Effect on Receipt
+                         *
+                         * On receipt of the UnregisterClient command, the server shall perform the following procedure:
+                         *
+                         *   1. The server shall check whether there is a entry stored on the device for the fabric with the same
+                         *      CheckInNodeID.
+                         *
+                         *     a. If there are no entries stored for the fabric, the status shall be NOT_FOUND. The server shall
+                         *        continue from step 6.
+                         *
+                         *     b. If there is an error when reading from storage, the status shall be FAILURE. The server shall continue
+                         *        from step 6.
+                         *
+                         *     c. If there is at least one entry stored on the server for the fabric, the server shall continue from
+                         *        step 2.
+                         *
+                         *   2. The server shall verify if one of the entries for the fabric has the corresponding CheckInNodeID
+                         *      received in the command.
+                         *
+                         *     a. If no entries have the corresponding CheckInNodeID, the status shall be NOT_FOUND. The server shall
+                         *        continue from step 6.
+                         *
+                         *     b. If an entry has the corresponding CheckInNodeID, the server shall continue to step 3.
+                         *
+                         *   3. The server shall check whether the ISD of the command has administrator permissions for the server
+                         *      cluster.
+                         *
+                         *     a. If the ISD of the command has administrator privileges for the server cluster, the server shall
+                         *        continue from step 5.
+                         *
+                         *     b. If the ISD of the command does not have administrator privileges for the server cluster, the server
+                         *        shall continue from step 4.
+                         *
+                         *   4. The server shall verify that the received verification key is equal to the key previously stored in the
+                         *      list of registered clients with the matching CheckInNodeID.
+                         *
+                         *     a. If the verification key does not have a valid value, the status shall be FAILURE. the server shall
+                         *        continue from step 6.
+                         *
+                         *     b. If the verification key is not equal to the Key value stored in the entry, the status shall be
+                         *        FAILURE. The server shall continue from step 6.
+                         *
+                         *     c. If the verification key is equal to the Key value stored in the entry, the server shall continue from
+                         *        step 5.
+                         *
+                         *   5. The server shall delete the entry with the matching CheckInNodeID from storage and will persist the
+                         *      change.
+                         *
+                         *     a. If the removal of the entry fails, the status shall be FAILURE. The server shall continue from step 6.
+                         *
+                         *     b. If the removal succeeds, the status shall be SUCCESS and the server shall continue to step 6.
+                         *
+                         *   6. The server shall generate a response with the Status field set to the evaluated status.
+                         *
+                         * @see {@link MatterSpecification.v141.Core} § 9.16.7.3.2
                          */
                         verificationKey: import("../tlv/TlvObject.js").OptionalFieldType<AllowSharedBufferSource>;
                     }>, void, any>;
@@ -1351,7 +1883,7 @@ export declare namespace IcdManagement {
                      * bitmap at the same time. However, a device shall NOT set more than one bit which has a dependency on the
                      * UserActiveModeTriggerInstruction attribute.
                      *
-                     * @see {@link MatterSpecification.v141.Core} § 9.17.6.7
+                     * @see {@link MatterSpecification.v141.Core} § 9.16.6.7
                      */
                     readonly userActiveModeTriggerHint: FixedAttribute<import("../schema/BitmapSchema.js").TypeFromPartialBitSchema<{
                         /**
@@ -1432,13 +1964,13 @@ export declare namespace IcdManagement {
             readonly component: {
                 readonly attributes: {
                     /**
-                     * This attribute shall indicate the operating mode of the ICD as specified in the OperatingModeEnum.
+                     * Indicates the operating mode of the ICD as specified in the OperatingModeEnum.
                      *
                      *   • If the ICD is operating as a LIT ICD, OperatingMode shall be LIT.
                      *
                      *   • If the ICD is operating as a SIT ICD, OperatingMode shall be SIT.
                      *
-                     * @see {@link MatterSpecification.v141.Core} § 9.17.6.9
+                     * @see {@link MatterSpecification.v141.Core} § 9.16.6.9
                      */
                     readonly operatingMode: Attribute<OperatingMode, any>;
                 };
@@ -1452,7 +1984,25 @@ export declare namespace IcdManagement {
                      * message exchanges during that period. The client may slightly overestimate the duration it wants the ICD
                      * to be active for, in order to account for network delays.
                      *
-                     * @see {@link MatterSpecification.v141.Core} § 9.17.7.4
+                     * ### Effect on Receipt
+                     *
+                     * When receiving a StayActiveRequest command, the server shall calculate the maximum PromisedActiveDuration
+                     * it can remain active as the greater of the following two values:
+                     *
+                     *   • StayActiveDuration: Specified in the received command by the client.
+                     *
+                     *   • Remaining Active Time: The server’s planned remaining active time based on the ActiveModeThreshold
+                     *     and its internal resources and power budget.
+                     *
+                     * A server may replace StayActiveDuration with Minimum Active Duration in the above calculation.
+                     *
+                     * PromisedActiveDuration represents the guaranteed minimum time the server will remain active, taking into
+                     * account both the requested duration and the server’s capabilities.
+                     *
+                     * The ICD shall report the calculated PromisedActiveDuration in a StayActiveResponse message back to the
+                     * client.
+                     *
+                     * @see {@link MatterSpecification.v141.Core} § 9.16.7.4
                      */
                     readonly stayActiveRequest: Command<import("../tlv/TlvObject.js").TypeFromFields<{
                         stayActiveDuration: import("../tlv/TlvObject.js").FieldType<number>;
@@ -1461,10 +2011,12 @@ export declare namespace IcdManagement {
                          * This field shall provide the actual duration that the ICD server can stay active from the time it receives
                          * the StayActiveRequest command.
                          *
+                         * ### Minimum Value for PromisedActiveDuration
+                         *
                          * The minimum value of the PromisedActiveDuration field shall be equal to either 30000 milliseconds or
                          * StayActiveDuration (from the received StayActiveRequest command), whichever is smaller.
                          *
-                         * @see {@link MatterSpecification.v141.Core} § 9.17.7.5.1
+                         * @see {@link MatterSpecification.v141.Core} § 9.16.7.5.1
                          */
                         promisedActiveDuration: import("../tlv/TlvObject.js").FieldType<number>;
                     }>, any>;
@@ -1499,7 +2051,7 @@ export declare namespace IcdManagement {
      * IcdManagementCluster supports optional features that you can enable with the IcdManagementCluster.with() factory
      * method.
      *
-     * @see {@link MatterSpecification.v141.Core} § 9.17
+     * @see {@link MatterSpecification.v141.Core} § 9.16
      */
     interface Cluster extends Identity<typeof ClusterInstance> {
     }
@@ -1516,26 +2068,26 @@ export declare namespace IcdManagement {
              * When this feature is supported, the device shall support all the associated commands and attributes to
              * properly support the Check-In Protocol.
              *
-             * @see {@link MatterSpecification.v141.Core} § 9.17.4.1
+             * @see {@link MatterSpecification.v141.Core} § 9.16.4.1
              */
             readonly checkInProtocolSupport: BitFlag;
             /**
              * This feature is supported if and only if the device has a user active mode trigger.
              *
-             * @see {@link MatterSpecification.v141.Core} § 9.17.4.2
+             * @see {@link MatterSpecification.v141.Core} § 9.16.4.2
              */
             readonly userActiveModeTrigger: BitFlag;
             /**
              * This feature is supported if and only the device is a Long Idle Time ICD.
              *
-             * @see {@link MatterSpecification.v141.Core} § 9.17.4.3
+             * @see {@link MatterSpecification.v141.Core} § 9.16.4.3
              */
             readonly longIdleTimeSupport: BitFlag;
             /**
              * This feature is supported if and only if the device can switch between SIT and LIT operating modes even
              * if it has a valid registered client. See the dynamic SIT / LIT operating mode switching for more details.
              *
-             * @see {@link MatterSpecification.v141.Core} § 9.17.4.4
+             * @see {@link MatterSpecification.v141.Core} § 9.16.4.4
              */
             readonly dynamicSitLitSupport: BitFlag;
         };
@@ -1545,7 +2097,7 @@ export declare namespace IcdManagement {
                  * This field shall indicate the NodeID of the Node to which Check-In messages will be sent when the
                  * MonitoredSubject is not subscribed.
                  *
-                 * @see {@link MatterSpecification.v141.Core} § 9.17.5.3.1
+                 * @see {@link MatterSpecification.v141.Core} § 9.16.5.3.1
                  */
                 checkInNodeId: import("../tlv/TlvObject.js").FieldType<import("../datatype/NodeId.js").NodeId>;
                 /**
@@ -1568,14 +2120,14 @@ export declare namespace IcdManagement {
                  * the server on the entry’s associated fabric bears the CASE Authenticated TAG value 0xAA12 and the version
                  * 0x0002 or higher within its NOC, then the entry matches.
                  *
-                 * @see {@link MatterSpecification.v141.Core} § 9.17.5.3.2
+                 * @see {@link MatterSpecification.v141.Core} § 9.16.5.3.2
                  */
                 monitoredSubject: import("../tlv/TlvObject.js").FieldType<import("../datatype/NodeId.js").NodeId>;
                 /**
                  * This field shall indicate the client’s type to inform the ICD of the availability for communication of the
                  * client.
                  *
-                 * @see {@link MatterSpecification.v141.Core} § 9.17.5.4
+                 * @see {@link MatterSpecification.v141.Core} § 9.16.5.3.4
                  */
                 clientType: import("../tlv/TlvObject.js").FieldType<ClientType>;
                 fabricIndex: import("../tlv/TlvObject.js").FieldType<import("../datatype/FabricIndex.js").FabricIndex>;
@@ -1706,26 +2258,26 @@ export declare namespace IcdManagement {
                  * When this feature is supported, the device shall support all the associated commands and attributes to
                  * properly support the Check-In Protocol.
                  *
-                 * @see {@link MatterSpecification.v141.Core} § 9.17.4.1
+                 * @see {@link MatterSpecification.v141.Core} § 9.16.4.1
                  */
                 readonly checkInProtocolSupport: BitFlag;
                 /**
                  * This feature is supported if and only if the device has a user active mode trigger.
                  *
-                 * @see {@link MatterSpecification.v141.Core} § 9.17.4.2
+                 * @see {@link MatterSpecification.v141.Core} § 9.16.4.2
                  */
                 readonly userActiveModeTrigger: BitFlag;
                 /**
                  * This feature is supported if and only the device is a Long Idle Time ICD.
                  *
-                 * @see {@link MatterSpecification.v141.Core} § 9.17.4.3
+                 * @see {@link MatterSpecification.v141.Core} § 9.16.4.3
                  */
                 readonly longIdleTimeSupport: BitFlag;
                 /**
                  * This feature is supported if and only if the device can switch between SIT and LIT operating modes even
                  * if it has a valid registered client. See the dynamic SIT / LIT operating mode switching for more details.
                  *
-                 * @see {@link MatterSpecification.v141.Core} § 9.17.4.4
+                 * @see {@link MatterSpecification.v141.Core} § 9.16.4.4
                  */
                 readonly dynamicSitLitSupport: BitFlag;
             }>, never>;
@@ -1739,19 +2291,20 @@ export declare namespace IcdManagement {
                  * This field shall provide the node ID to which a Check-In message will be sent if there are no active
                  * subscriptions matching MonitoredSubject.
                  *
-                 * @see {@link MatterSpecification.v141.Core} § 9.17.7.1.1
+                 * @see {@link MatterSpecification.v141.Core} § 9.16.7.1.1
                  */
                 checkInNodeId: import("../tlv/TlvObject.js").FieldType<import("../datatype/NodeId.js").NodeId>;
                 /**
                  * This field shall provide the monitored subject ID.
                  *
-                 * @see {@link MatterSpecification.v141.Core} § 9.17.7.1.2
+                 * @see {@link MatterSpecification.v141.Core} § 9.16.7.1.2
                  */
                 monitoredSubject: import("../tlv/TlvObject.js").FieldType<import("../datatype/NodeId.js").NodeId>;
                 /**
-                 * This field shall provide the shared secret between the client and the ICD to encrypt the Check-In message.
+                 * This field shall contain the ICDToken, a 128-bit symmetric key shared by the ICD and the ICD Client, used to
+                 * encrypt Check-In messages from this ICD to the MonitoredSubject.
                  *
-                 * @see {@link MatterSpecification.v141.Core} § 9.17.7.1.3
+                 * @see {@link MatterSpecification.v141.Core} § 9.16.7.1.3
                  */
                 key: import("../tlv/TlvObject.js").FieldType<AllowSharedBufferSource>;
                 /**
@@ -1762,13 +2315,68 @@ export declare namespace IcdManagement {
                  * provided by clients with administrator permissions for the server cluster. The verification key shall be
                  * ignored by the server if it is provided by a client with administrator permissions for the server cluster.
                  *
-                 * @see {@link MatterSpecification.v141.Core} § 9.17.7.1.4
+                 * @see {@link MatterSpecification.v141.Core} § 9.16.7.1.4
                  */
                 verificationKey: import("../tlv/TlvObject.js").OptionalFieldType<AllowSharedBufferSource>;
                 /**
                  * This field shall provide the client type of the client registering.
                  *
-                 * @see {@link MatterSpecification.v141.Core} § 9.17.7.1.5
+                 * ### Effect on Receipt
+                 *
+                 * On receipt of the RegisterClient command, the server shall perform the following procedure:
+                 *
+                 *   1. The server verifies that an entry for the fabric is available in the server’s list of registered
+                 *      clients.
+                 *
+                 *     a. If one of the entries in storage for the fabric has the same CheckInNodeID as the received
+                 *        CheckInNodeID, the server shall continue from step 2.
+                 *
+                 *     b. If there is an available entry for the fabric, an entry is created for the fabric and the received
+                 *        CheckInNodeID, MonitoredSubject, Key and ClientType are stored. The server shall continue from step 5.
+                 *
+                 *     c. If there are no available entries for the fabric, the status shall be RESOURCE_EXHAUSTED and the
+                 *        server shall continue from step 6.
+                 *
+                 *   2. The server shall verify the privileges of the command’s ISD.
+                 *
+                 *     a. If the ISD of the command has administrator privileges for the server cluster, the server shall
+                 *        continue from step 4.
+                 *
+                 *     b. If the ISD of the command does not have administrator privileges for the server cluster, the server
+                 *        shall continue from step 3.
+                 *
+                 *   3. The server shall verify that the received verification key is equal to the key previously stored in the
+                 *      list of registered clients with the matching CheckInNodeID.
+                 *
+                 *     a. If the verification key does not have a valid value, the status shall be FAILURE. the server shall
+                 *        continue from step 6.
+                 *
+                 *     b. If the verification key is not equal to the Key value stored in the entry, the status shall be
+                 *        FAILURE. The server shall continue from step 6.
+                 *
+                 *     c. If the verification key is equal to the Key value stored in the entry, the server shall continue from
+                 *        step 4.
+                 *
+                 *   4. The entry shall be updated with the received CheckInNodeID, MonitoredSubject, Key and ClientType.
+                 *
+                 *     a. If the update fails, the status shall be FAILURE. The server shall continue from step 6.
+                 *
+                 *     b. If the update succeeds, the server shall continue from step 5.
+                 *
+                 *   5. The server shall persist the client information.
+                 *
+                 *     a. If the persistence fails, the status shall be FAILURE and the server shall continue from step 6.
+                 *
+                 *     b. If the persistence succeeds, the status shall be SUCCESS and the server shall continue from step 6.
+                 *
+                 *   6. The server shall generate a response.
+                 *
+                 *     a. If the status is SUCCESS, the server shall generate a RegisterClientResponse command.
+                 *
+                 *     b. If the status is not SUCCESS, the server shall generate a default response with the Status field set
+                 *        to the evaluated error status.
+                 *
+                 * @see {@link MatterSpecification.v141.Core} § 9.16.7.1.5
                  */
                 clientType: import("../tlv/TlvObject.js").FieldType<ClientType>;
             }>, import("../tlv/TlvObject.js").TypeFromFields<{
@@ -1785,7 +2393,7 @@ export declare namespace IcdManagement {
                 /**
                  * This field shall provide the registered client node ID to remove from storage.
                  *
-                 * @see {@link MatterSpecification.v141.Core} § 9.17.7.3.1
+                 * @see {@link MatterSpecification.v141.Core} § 9.16.7.3.1
                  */
                 checkInNodeId: import("../tlv/TlvObject.js").FieldType<import("../datatype/NodeId.js").NodeId>;
                 /**
@@ -1797,7 +2405,61 @@ export declare namespace IcdManagement {
                  * server cluster. The verification key shall be ignored by the server if it is provided by a client with
                  * administrator permissions for the server cluster.
                  *
-                 * @see {@link MatterSpecification.v141.Core} § 9.17.7.3.2
+                 * ### Effect on Receipt
+                 *
+                 * On receipt of the UnregisterClient command, the server shall perform the following procedure:
+                 *
+                 *   1. The server shall check whether there is a entry stored on the device for the fabric with the same
+                 *      CheckInNodeID.
+                 *
+                 *     a. If there are no entries stored for the fabric, the status shall be NOT_FOUND. The server shall
+                 *        continue from step 6.
+                 *
+                 *     b. If there is an error when reading from storage, the status shall be FAILURE. The server shall continue
+                 *        from step 6.
+                 *
+                 *     c. If there is at least one entry stored on the server for the fabric, the server shall continue from
+                 *        step 2.
+                 *
+                 *   2. The server shall verify if one of the entries for the fabric has the corresponding CheckInNodeID
+                 *      received in the command.
+                 *
+                 *     a. If no entries have the corresponding CheckInNodeID, the status shall be NOT_FOUND. The server shall
+                 *        continue from step 6.
+                 *
+                 *     b. If an entry has the corresponding CheckInNodeID, the server shall continue to step 3.
+                 *
+                 *   3. The server shall check whether the ISD of the command has administrator permissions for the server
+                 *      cluster.
+                 *
+                 *     a. If the ISD of the command has administrator privileges for the server cluster, the server shall
+                 *        continue from step 5.
+                 *
+                 *     b. If the ISD of the command does not have administrator privileges for the server cluster, the server
+                 *        shall continue from step 4.
+                 *
+                 *   4. The server shall verify that the received verification key is equal to the key previously stored in the
+                 *      list of registered clients with the matching CheckInNodeID.
+                 *
+                 *     a. If the verification key does not have a valid value, the status shall be FAILURE. the server shall
+                 *        continue from step 6.
+                 *
+                 *     b. If the verification key is not equal to the Key value stored in the entry, the status shall be
+                 *        FAILURE. The server shall continue from step 6.
+                 *
+                 *     c. If the verification key is equal to the Key value stored in the entry, the server shall continue from
+                 *        step 5.
+                 *
+                 *   5. The server shall delete the entry with the matching CheckInNodeID from storage and will persist the
+                 *      change.
+                 *
+                 *     a. If the removal of the entry fails, the status shall be FAILURE. The server shall continue from step 6.
+                 *
+                 *     b. If the removal succeeds, the status shall be SUCCESS and the server shall continue to step 6.
+                 *
+                 *   6. The server shall generate a response with the Status field set to the evaluated status.
+                 *
+                 * @see {@link MatterSpecification.v141.Core} § 9.16.7.3.2
                  */
                 verificationKey: import("../tlv/TlvObject.js").OptionalFieldType<AllowSharedBufferSource>;
             }>, void, any> & {
@@ -1815,10 +2477,12 @@ export declare namespace IcdManagement {
                  * This field shall provide the actual duration that the ICD server can stay active from the time it receives
                  * the StayActiveRequest command.
                  *
+                 * ### Minimum Value for PromisedActiveDuration
+                 *
                  * The minimum value of the PromisedActiveDuration field shall be equal to either 30000 milliseconds or
                  * StayActiveDuration (from the received StayActiveRequest command), whichever is smaller.
                  *
-                 * @see {@link MatterSpecification.v141.Core} § 9.17.7.5.1
+                 * @see {@link MatterSpecification.v141.Core} § 9.16.7.5.1
                  */
                 promisedActiveDuration: import("../tlv/TlvObject.js").FieldType<number>;
             }>, any> & {