Protocol Basics

Matter Protocol Overview

Matter is an open-source, royalty-free connectivity standard developed by the Connectivity Standards Alliance (CSA). It unifies smart home devices across major ecosystems including Apple Home, Google Home, Amazon Alexa, and Samsung SmartThings.

The protocol operates at the application layer, sitting above existing transport technologies. This design philosophy enables Matter to leverage proven networking infrastructure while providing a consistent, secure, and reliable communication framework for IoT devices.

Key Protocol Characteristics:

• Application-Layer Protocol: Works over existing IP-based networks
• IPv6 Native: All Matter communication uses IPv6 addressing
• End-to-End Encrypted: Every message is encrypted from source to destination
• Local-First: Core functionality operates without cloud connectivity
• Multi-Admin Support: Devices can be controlled by multiple ecosystems simultaneously

Protocol Stack

┌─────────────────────────────────────┐
│        Application Layer            │
│    (Clusters, Attributes, Commands) │
├─────────────────────────────────────┤
│        Data Model Layer             │
│    (Device Types, Endpoints)        │
├─────────────────────────────────────┤
│        Interaction Model            │
│    (Read, Write, Invoke, Subscribe) │
├─────────────────────────────────────┤
│        Security Layer               │
│    (CASE, PASE, Encryption)         │
├─────────────────────────────────────┤
│        Transport Layer              │
│    (UDP/IPv6, mDNS, SRP)            │
├─────────────────────────────────────┤
│        Network Layer                │
│    (Wi-Fi / Thread)                 │
└─────────────────────────────────────┘

Matter over Wi-Fi vs Matter over Thread

Matter supports two primary transport technologies, each with distinct characteristics suited to different deployment scenarios.

Matter over Wi-Fi

Best For: High-bandwidth devices, existing Wi-Fi infrastructure, retrofit installations

Advantages:

• Leverages existing network infrastructure
• No additional hub required for Wi-Fi devices
• Higher bandwidth supports complex devices
• Familiar troubleshooting for IT teams

Considerations:

• Higher power consumption limits battery-powered devices
• Network congestion can impact performance
• Requires strong Wi-Fi coverage throughout deployment

Matter over Thread

Best For: Low-power devices, battery-operated sensors, large-scale mesh networks

Advantages:

• Self-healing mesh topology
• Extremely low power consumption
• Self-forming and self-maintaining network
• Good scalability (100–200 devices per Thread network in practice)

Considerations:

• Requires Thread Border Router for IP connectivity
• Lower bandwidth limits data-intensive applications
• Additional infrastructure planning required

Hybrid Deployments

Professional installations often combine both technologies:

# Example hybrid deployment configuration
Lighting:
  - Ceiling Fixtures: Matter over Wi-Fi (constant power, high reliability)
  - Wall Switches: Matter over Thread (low power, mesh coverage)
  
Sensors:
  - Motion Detectors: Matter over Thread (battery-powered)
  - Temperature Sensors: Matter over Thread (battery-powered)
  
Controllers:
  - Central Hub: Thread Border Router + Wi-Fi bridge

Communication Patterns

Matter defines four primary interaction patterns for device communication:

1. Read/Write Operations

Controller → Device: Read attribute request
Device → Controller: Attribute value response

Controller → Device: Write attribute request
Device → Controller: Write success/failure

Use Case: Querying light state, setting brightness level

2. Command Invocation

Controller → Device: Invoke command (e.g., "TurnOn")
Device → Controller: Command response with status

Use Case: Toggling lights, triggering scenes

3. Event Subscription

Controller → Device: Subscribe to attribute
Device → Controller: Initial value
Device → Controller: Updates on change (push)

Use Case: Real-time UI updates, automation triggers

4. Event Reporting

Device → Controller: Event notification (unsolicited)

Use Case: Button presses, sensor triggers, alerts

Device Types and Clusters

Device Types

Matter defines standardized device types that specify required functionality:

Clusters

Clusters are functional units that group related attributes and commands:

Common Lighting Clusters:

On/Off Cluster (0x0006):
  Attributes:
    - OnOff (boolean): Current on/off state
    - GlobalSceneControl (boolean): Scene control status
  Commands:
    - Off(): Turn device off
    - On(): Turn device on
    - Toggle(): Toggle current state

Level Control Cluster (0x0008):
  Attributes:
    - CurrentLevel (0-254): Brightness level
    - RemainingTime (seconds): Transition time
    - MinLevel, MaxLevel: Level bounds
  Commands:
    - MoveToLevel(level, transitionTime)
    - Move(rate, direction)
    - Step(stepSize, direction)

Color Control Cluster (0x0300):
  Attributes:
    - CurrentHue (0-254): Hue value
    - CurrentSaturation (0-254): Saturation value
    - ColorTemperatureMireds: CT in mireds
  Commands:
    - MoveToHue(hue, direction, transitionTime)
    - MoveToColorTemperature(ct, transitionTime)

Data Models

Endpoint Architecture

Matter devices expose functionality through endpoints:

┌─────────────────────────────────────┐
│           Device (Node)             │
├─────────────────────────────────────┤
│ Endpoint 0: Root Device             │
│   - Basic Information Cluster       │
│   - Network Commissioning Cluster   │
├─────────────────────────────────────┤
│ Endpoint 1: Primary Function        │
│   - On/Off Cluster                  │
│   - Level Control Cluster           │
│   - Color Control Cluster           │
├─────────────────────────────────────┤
│ Endpoint 2: Secondary Function      │
│   - (Additional functionality)      │
└─────────────────────────────────────┘

Attribute Types

Security Architecture

Matter implements a comprehensive security framework based on established cryptographic standards.

Commissioning Security

PASE (Password Authenticated Session Establishment):

• Used during initial device commissioning
• QR code or manual code provides shared secret
• Establishes secure channel for credential transfer

CASE (Certificate Authenticated Session Establishment):

• Used for ongoing device communication
• X.509 certificates verify device identity
• Supports multi-admin scenarios

Encryption Standards

Encryption:
  Algorithm: AES-128-CCM
  Key Derivation: HKDF-SHA256
  Certificate Format: X.509v3
  Message Authentication: 8-byte MIC
  
Key Management:
  - Operational Credentials: Long-term identity
  - Group Keys: Multicast/scene control
  - Session Keys: Per-session encryption

Security Levels

1. No Security: Only for network discovery
2. Unauthenticated: Reserved, rarely used
3. CASE Authenticated: Standard operational security
4. Group Encrypted: For multicast commands

Certification Requirements

All Matter devices must be certified by the Connectivity Standards Alliance (CSA) to use the Matter logo and ensure interoperability.

Certification Process

1. Development Phase

   • Join CSA as member
   • Access Matter specification and SDK
   • Implement required clusters and features

2. Testing Phase

   • Complete self-testing using official test harness
   • Verify compliance with device type specifications
   • Test interoperability with reference platforms

3. Certification Phase

   • Submit to authorized test lab
   • Complete certification testing
   • Receive certification ID (VID/PID)

Required Documentation

• Device type specification compliance matrix
• Security certification evidence
• User manual and setup instructions
• Firmware version and update mechanism

Compliance Levels

For implementation guidance, see our Network Architecture and Firmware Management guides.