Also known as: Thread, Thread protocol
Thread is a low-power wireless mesh networking protocol that carries native IPv6 to IoT devices, running on the same IEEE 802.15.4 2.4 GHz radio as Zigbee but replacing its proprietary networking stack with internet-standard IPv6 over 6LoWPAN.1 The result is a self-healing, router-less mesh in which every full device is IP-addressable and can route for its neighbours.
Overview
Thread reuses the proven 802.15.4 radio — OQPSK with DSSS at 250 kbit/s on 2.4 GHz — but runs a modern IP stack above it. Devices are either routers (always-on, relaying traffic) or end devices (often battery-powered, attaching to a parent router). The mesh elects and re-elects routers automatically, so there is no single coordinator whose loss breaks the network; this is Thread’s headline reliability feature. A border router connects the mesh to the home Wi-Fi/Ethernet LAN and the wider internet, translating 6LoWPAN-compressed IPv6 to ordinary IPv6.
Technical characteristics
| Property | Value |
|---|---|
| Radio | IEEE 802.15.4 (2.4 GHz OQPSK/DSSS) |
| Network layer | IPv6 over 6LoWPAN |
| Topology | Self-healing mesh, no single coordinator |
| Roles | Router, REED, end device, border router |
| Security | AES-based link and network keys |
| Data rate | 250 kbit/s (802.15.4 PHY) |
Because it is IP-native, a Thread device can be addressed like any host on the network, which simplifies application protocols layered on top — most notably Matter.
History
The Thread Group, founded in 2014 by Nest, ARM, Silicon Labs, and others, published Thread 1.0 in 2015. Adoption accelerated once Matter chose Thread as one of its two transport networks, and border-router support arrived in mainstream smart-home hubs and phones.
Deployment
Thread underpins a growing share of smart-home sensors, locks, and lighting, especially Matter-certified devices. It coexists on the 802.15.4 radio with Zigbee (a device’s chip often supports either) and complements Wi-Fi for higher-bandwidth endpoints.
Decoding it with GopherTrunk
GopherTrunk does not decode Thread. Its 802.15.4 OQPSK/DSSS radio, AES-secured mesh, and IPv6 stack are entirely outside GopherTrunk’s land-mobile decode chain, and the traffic is encrypted by default. Thread is relevant to an SDR operator only as 2.4 GHz band occupancy.
Sources
-
Thread (network protocol) — Wikipedia, on the Thread IPv6 mesh, its 802.15.4 radio, border routers, self-healing mesh, and relationship to Matter. ↩