Low Power
Built on IEEE 802.15.4 with sleepy-device support, ideal for battery sensors, locks, and buttons.
EXPLORE MATTER OVER THREAD
Thread IPv6 Mesh for Low-Power Smart Devices & Matter over Thread Deployment
Thread is a low-power IPv6 Mesh network for battery devices, low-to-moderate data, and multi-node deployments. With Matter, it connects to Wi-Fi / Ethernet through a Thread Border Router.
Where Thread Fits in Matter
Matter defines device functions and interoperability; Thread provides low-power IPv6 connectivity. BLE assists Commissioning, then Thread handles daily communication.
What Thread Brings to Low-Power Devices
Thread combines low power, Mesh networking, native IPv6, and multi-Border Router flexibility.
Mesh Coverage
Router nodes extend the Thread network; Sleepy End Devices connect through a Parent Router.
Native IPv6
Thread uses IPv6 directly, connecting to IP networks with fewer proprietary conversion layers.
Multiple Border Routers
A Thread network can use multiple Border Routers to improve path availability.
Is Matter over Thread Right for My Product?
Power, data volume, and deployment are key factors when deciding whether Thread fits.
Low Power, Low-to-Moderate Data, Multi-Node
- Battery PoweredSensors, locks, buttons, and other power-sensitive products
- Low-to-Moderate Data VolumeMainly status, commands, and sensor data
- Multi-Node DeploymentDistributed lights, switches, sensors, and similar devices
Video, High Bandwidth, or Large Data
- Video DataCameras, displays, and streaming devices
- High-Bandwidth RequirementsDevices with continuous high-volume data transfer
- Continuous PowerProducts with established Wi-Fi or Ethernet networks
Thread vs. Wi-Fi Connectivity
| Comparison | Thread | Wi-Fi |
|---|---|---|
| Network Architecture | IEEE 802.15.4 low-power IPv6 Mesh | Connects to a Wi-Fi Access Point |
| Power Characteristics | Suited to low-power and sleepy devices | Better suited to continuously powered devices |
| Data Transfer | Low-to-Moderate Data Volume | Higher bandwidth and larger data volumes |
| Network Role | Needs a Thread Border Router to reach other IP networks | Uses the existing Wi-Fi IP network |
Border Router, Bridge, and RCP Differences
Gateway, Hub, and controller products may combine several roles, with hardware/software duties varying by design.
Thread Border Router
Routes IPv6 packets between Thread and adjacent IP networks such as Wi-Fi or Ethernet.
For always-powered home hubs, Wi-Fi APs, and building controllers.Matter Bridge
Maps Zigbee, Z-Wave, Bluetooth Mesh, or proprietary devices to Matter device types and Clusters.
For upgrading existing ecosystems and extending legacy devices.Thread RCP (Radio Co-Processor)
Provides Thread radio and lower-layer networking over USB or UART; higher-layer Thread / Matter runs on the Host.
For adding Thread to existing hosts, Gateways, STBs, or controllers.Gateway / Hub
Can combine Border Router, Matter Controller, Bridge, cloud, and UI functions.
For home or building platforms combining network, control, and management functions.Adding Thread to Existing Products: Start with the Hardware
New products, existing hosts, and Gateways need different approaches. Choose based on the MCU, Host architecture, and product role to limit board changes and software overlap.
New Thread End Device
- Select a Thread / Matter MCU or module
- Develop device types and functional groups
- Integrate product I/O
- Plan DAC, Factory Data, certification, and mass production
Existing Host + Thread RCP
- Connect RCP via USB or UART
- Define Host and RCP responsibilities
- Connect with the existing product control logic
- Reduce the need for major mainboard changes
Thread Border Router / Gateway
- Add Thread RCP, Host, OTBR, or related software
- Assess Matter Controller, Bridge, HMI, and cloud functions
- Integrate Wi-Fi / Ethernet with Thread
From Architecture to DAC Provisioning and Production
Ciot helps plan Matter / Thread architecture across modules, firmware, security data, and production. Realtek is the primary platform; existing MCU, Module, or Host designs can also be assessed for RCP, product upgrades, and Border Router / Gateway hardware-software split.
Platform and Architecture
Assess Realtek Matter / Thread modules and define End Device, Router, RCP, Border Router, and Host configuration.
Firmware and Interfaces
Integrate Matter SDK, device types, Clusters, Host Command, GPIO, UART, I²C, and SPI.
Security and Mass Production
Plan DAC / PAI, Factory Data, keys, TrustZone / Secure Element, then connect MES, programming tools, Provisioning, and Matter Certification.
Frequently Asked Questions
Does Matter Require Thread?
No. Matter can use Thread, Wi-Fi, or Ethernet; choose based on power, bandwidth, power source, and deployment.
Does a Thread Device Need a Border Router?
A Thread Border Router is needed when Thread must connect to adjacent IP networks such as Wi-Fi or Ethernet.
Border Router vs. Matter Bridge?
Border Router routes IPv6 between Thread and other IP networks; Matter Bridge maps non-Matter device functions into Matter devices and Clusters.
Do All Thread Devices Route Mesh Traffic?
No. Routers forward traffic; Sleepy End Devices connect through a Parent Router and do not forward other nodes’ packets.
Can an Existing MCU Add Thread via RCP?
Yes, subject to evaluation. RCP provides Thread radio and lower-layer processing over USB or UART; the Host runs higher-layer software. Check performance, memory, and interface split.
Does a Certified Module Remove End-Product Certification?
No. A certified module does not automatically certify the end product; requirements still depend on module status, software version, product, market, and scope.
START WITH YOUR PRODUCT
Determine Matter over Thread Architecture from Product Requirements
Share product type, MCU / Module, power, connectivity, target market, and production timing. Ciot can assess End Device, RCP, Border Router, or hybrid designs.