Matter Cluster 1364 — WebRTC Transport Requestor Cluster

Cluster Identity

Revision history

Shadow Path Format

Cluster 1364 values in the device shadow use this format:

endpoint_id / 1364 / attribute_id

Example:

{
  "1/1364/0": []
}

Cluster 1364 Attributes

Cluster 1364 defines 1 attribute plus the global attributes. Conformance: M mandatory, O optional, a feature code means "mandatory when that feature is present", square brackets mean "optional when …".

Global attributes

Attribute Details

Attribute 0 / 0x0000 — CurrentSessions

Path example:

1/1364/0

This attribute is a list of WebRTCSessionStruct, which represents all the active WebRTC Sessions on this Node.

Example:

{
  "1/1364/0": []
}

Cluster 1364 Commands

Cluster 1364 has 4 client-to-server commands and 0 responses.

AcceptedCommandList

The AcceptedCommandList attribute lists the command IDs the endpoint actually implements:

endpoint_id / 1364 / 65529

{
  "1/1364/65529": [
    0,
    1,
    2,
    3
  ]
}

Bridge Command Payload Format

The bridge accepts Matter commands in this structure:

{
  "message_id": "1",
  "command": "device_command",
  "args": {
    "endpoint_id": 1,
    "cluster_id": 1364,
    "command_name": "Offer",
    "payload": {},
    "timed_request_timeout_ms": 1000
  }
}

For Cluster 1364, always use "cluster_id": 1364. Payload keys are the command field names in lowerCamelCase. Octet-string fields are base64-encoded. timed_request_timeout_ms is required for timed commands and ignored otherwise.

Command: Offer

Purpose

This command provides the stream requestor with WebRTC session details. It is sent following the receipt of a SolicitOffer command or a re-offer initiated by the Provider. This command must respond with a response status of NOT_FOUND if the WebRTCSessionID does not match an entry in CurrentSessions, or if the matching entry's associated fabric and PeerNodeID do not match the accessing fabric and the Peer Node ID entry stored in the Secure Session Context of the session this command was received on.

Command Identity

Payload Fields

Bridge Command Example

{
  "message_id": "1",
  "command": "device_command",
  "args": {
    "endpoint_id": 1,
    "cluster_id": 1364,
    "command_name": "Offer",
    "payload": {
      "webRTCSessionID": 0,
      "sdp": "example"
    }
  }
}

Command: Answer

Purpose

This command provides the stream requestor with the WebRTC session details (i.e. Session ID and SDP answer), It is the next command in the Offer/Answer flow to the ProvideOffer command. This command must respond with a response status of NOT_FOUND if the WebRTCSessionID does not match an entry in CurrentSessions, or if the matching entry's associated fabric and PeerNodeID do not match the accessing fabric and the Peer Node ID entry stored in the Secure Session Context of the session this command was received on.

Command Identity

Payload Fields

Bridge Command Example

{
  "message_id": "1",
  "command": "device_command",
  "args": {
    "endpoint_id": 1,
    "cluster_id": 1364,
    "command_name": "Answer",
    "payload": {
      "webRTCSessionID": 0,
      "sdp": "example"
    }
  }
}

Command: ICECandidates

Purpose

ICECandidates is a client-to-server command of the WebRTC Transport Requestor cluster.

Command Identity

Payload Fields

Bridge Command Example

{
  "message_id": "1",
  "command": "device_command",
  "args": {
    "endpoint_id": 1,
    "cluster_id": 1364,
    "command_name": "ICECandidates",
    "payload": {
      "webRTCSessionID": 0,
      "iceCandidates": []
    }
  }
}

Command: End

Purpose

This command notifies the stream requestor that the provider has ended the WebRTC session.

Command Identity

Payload Fields

Bridge Command Example

{
  "message_id": "1",
  "command": "device_command",
  "args": {
    "endpoint_id": 1,
    "cluster_id": 1364,
    "command_name": "End",
    "payload": {
      "webRTCSessionID": 0,
      "reason": 0
    }
  }
}

Cluster 1364 Events

Cluster 1364 defines no events.

SmartphoneKey Notes

• Cluster 1364 is not currently exposed by SmartphoneKey devices. This page documents the Matter 1.6.1 specification so that future devices can be interpreted without changes to the backend.
• Shadow paths follow endpoint/1364/attribute; attribute values that the device reports as unreadable are written as n/a.
• Attribute IDs, command IDs and enum values on this page come from the CSA Matter 1.6.1 data model; descriptions are condensed from the specification text.