MatterSpecification.v13.Core § 9.17.5.2

interface MonitoringRegistration {
    checkInNodeId: NodeId;
    fabricIndex: FabricIndex;
    monitoredSubject: NodeId;
}

Hierarchy (view full)

Properties

checkInNodeId: NodeId

This field shall indicate the NodeID of the Node to which Check-In messages will be sent when the MonitoredSubject is not subscribed.

MatterSpecification.v13.Core § 9.17.5.2.1

fabricIndex: FabricIndex
monitoredSubject: NodeId

This field shall indicate the monitored Subject ID. This field shall be used to determine if a particular client has an active subscription for the given entry. The MonitoredSubject, when it is a NodeID, may be the same as the CheckInNodeID. The MonitoredSubject gives the registering client the flexibility of having a different CheckInNodeID from the MonitoredSubject. A subscription shall count as an active subscription for this entry if:

• It is on the associated fabric of this entry, and

• The subject of this entry matches the ISD of the SubscriptionRequest message that created the subscription. Matching shall be determined using the subject_matches function defined in the Access Control Privilege Granting Algorithm.

For example, if the MonitoredSubject is Node ID 0x1111_2222_3333_AAAA, and one of the subscribers to the server on the entry’s associated fabric bears that Node ID, then the entry matches.

Another example is if the MonitoredSubject has the value 0xFFFF_FFFD_AA12_0002, and one of the subscribers to 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.

MatterSpecification.v13.Core § 9.17.5.2.2