Thread (network protocol): Difference between revisions
Pat Palmer (talk | contribs) mNo edit summary |
Pat Palmer (talk | contribs) m (→Notes) |
||
Line 32: | Line 32: | ||
<ref name=Consortium> | <ref name=Consortium> | ||
The industry consortion was formed in July of 2014 with a mission to develop and maintain Thread as an industry networking standard for [[Internet of Things|IoT]] devices. The Thread Group also does testing and certification of products to ensure adherence to the specification. The initial group members included ARM Holdings, Big Ass Solutions, NXP Semiconductors/Freescale, Nest Labs (a Google subsidiary), OSRAM, Samsung, Silicon Labs, Somfy, Tyco International, Qualcomm, and the Yale lock company. In August 2018, Apple also joined the group. | |||
</ref> | </ref> | ||
</references> | </references> |
Revision as of 06:47, 21 April 2023
Thread is an emerging standard for a mesh network protocol developed by a consortium of competing smart home companies[1], using IP version 6 over an IEEE 802.15.4 wireless network (on the 2.4 GHz spectrum) designed for low-power, fast, reliable messaging among IoT devices.
Thread is a lot like existing smart home protocols Zigbee and Z-Wave, except that no central hub or bridge is needed; Thread devices talk directly to each other in a wireless mesh configuration and can talk directly to any other IP-based device, including smart phones, tablets, computers, and Wi-Fi routers. Thread is the first low-power, wireless mesh networking protocol to allow low-power devices to use IP.
Thread device roles: Router, End Device, Border Router
Devices on a Thread network are divided into two main categories--those plugged into power (i.e., a light bulb or smart plug) vs. those that are battery-powered (i.e., a motion sensor or a smart lock). Always-powered devices on a Thread network play the role of a router that forwards traffic along to other devices as needed. Any battery-powered device on a Thread network is called an "end device". An always-powered device that also connects to the internet (such as a smart speaker or Wi-Fi router) can, if it contains the necessary software capability, also act as a Thread "border router", passing messages between the Thread network and servers out on the internet. A smart home will usually want to have at least one border router so that its Thread-capable devices can reach the internet. Any Thread-capable device should be able to use any Border Router to reach the internet, regardless of manufacturer. A Thread Border Router is not usually going to be a dedicated device like a hub or bridge; instead, it is a feature that can be integrated into any powered device that has access to the internet.
Any device can be unplugged without ruining the network
The advantage of using a mesh network is that there is no single point of failure. Any device can be removed, and all the other devices should continue to work, although at least one border router must be present for devices to access the internet.
Thread network capacity
A Thread network can support more the 250 devices, and of those, as many as 64 can be Routers (always-powered), with at most 32 Routers active simultaneously. Among the Routers, multiple instances of Border Routers may exist.
Applications that run on top of Thread
The new smart home standard, Matter, is an application that runs on top of a Thread network. Matter supports both Wi-Fi and Thread for connecting its devices, and its use of Thread means that there is no single point of failure in the home network--any one device may fail or be unplugged, but the rest of the network can continue to work normally. Other applications that may run over Thread include HomeKit, Google/Weave, or Open Thread, etc. Because it's an IP-based network, a Thread network could support multiple of these application laters running simultaneously.
Thread scales for most IoT devices, except cameras
Unlike earlier technologies, Thread has been optimized from its inception to run on low-power devices that require near real-time access to rapidly changing data, and thus to handle a high volume of data messages with minimal delay (latency). Early benchmarking of Thread, as compared with Zigbee and Bluetooth networks, show Thread networks to have much less delay, especially when scaled to large numbers of devices, and the quicker activity of Thread translates into less power usage, which is especially important for battery-driven devices.
The one kind of smart home device currently in use that does not work well on Thread is security cameras, because those require high-bandwidth internet connections, whereas Thread is designed for much lower-bandwidth applications. Thread is specifically intended to do well for small, low-powered devices such as leak detectors, CO detectors, and motion sensors. Such devices may be left untouched and unused for months but need to spring into action reliably when required and need still to have battery life left when that happens. In addition to sensors, Thread is designed to perform actions on devices such as door locks, window shades, light bulbs, water valves, thermostats, and so on.
Thread traffic is encrypted
Finally, unlike with a bridge of hub, a Border Router cannot read the traffic that it passes along, because all communications in a Thread network are encrypted.
Status of Thread
Thread, and the Matter application layer which can run over it, are both emerging standards in 2023. The latest release of Thread as of April 2023 is version 1.3.0.
Notes
- ↑ The industry consortion was formed in July of 2014 with a mission to develop and maintain Thread as an industry networking standard for IoT devices. The Thread Group also does testing and certification of products to ensure adherence to the specification. The initial group members included ARM Holdings, Big Ass Solutions, NXP Semiconductors/Freescale, Nest Labs (a Google subsidiary), OSRAM, Samsung, Silicon Labs, Somfy, Tyco International, Qualcomm, and the Yale lock company. In August 2018, Apple also joined the group.