Multiple Thread Networks and The Seamless Interconnectivity of IP
By Jorg Kennis, Thread Smart Building Marketing, Neovate Innovation Partners
From its inception, Thread was designed to deliver on the promise of a reliable smart home network: long battery life, low energy footprint, low latency, extended reach, and increased reliability. Instead of using proprietary networking technologies as was common with other protocols at the time, Thread prioritized widespread interconnectivity and was built on IPv6-based network technology, the same protocol that serves as the foundation for the Internet and every home network.
By doing so, Thread devices seamlessly integrate into existing networks. Thread devices can be used alongside Wi-Fi and ethernet-connected ones, and all three types of devices can be addressable to the network in the same way: as individual IP-based devices.
A unique aspect of a Thread network is the Border Router role. Thread-enabled devices don’t need a hub or bridge to connect, they simply need a Thread Border Router, which makes Thread devices appear on the home network in the same way as Wi-Fi and ethernet devices, and sends packages between the low-power Thread network wireless mesh and the rest of the network. Since Thread Border Router functionality can be embedded in existing devices such as smart speakers and smart TVs, it’s very likely that a typical smart home will have multiple Border Routers.
Multiple Thread Border Routers
When there are multiple devices that can perform the Thread Border Router role, there are two scenarios for how Thread devices operate:
- If these Thread Border Router devices share Thread credentials — the technical info needed to onboard devices to the network — with each other, then all the Thread devices form part of the same Thread mesh network. This means that they all benefit from the extended reach and reliability offered by all the mains-powered Thread devices that act as Mesh Extenders, and multiple Border Routers provide redundancies for connecting Thread devices to the network.
- If the various Thread Border Routers don’t share network credentials, each of the Border Routers forms its own Thread mesh network, and all use the Mesh Extending capabilities of mains-powered devices on that particular network. However, thanks to its IP protocol, any Thread devices from the various Thread networks can seamlessly “see” and work with each other as well as any other devices attached to the broader network.
For end users, their Thread-based devices will operate seamlessly whether they are connected to the same Border Router and mesh network, or to a different one. They are all equally treated as IP devices, just as the devices connected via Wi-Fi or ethernet. Given Thread’s inherent range and reliability, even point-to-point, most end users would not see a practical issue with having multiple Thread meshes in their homes or buildings.
Thread Border Routers From Various Ecosystems Operate Together
As creatures of habit, most people buy devices that operate in the ecosystem they’re most familiar with, whether it’s Apple HomeKit, Google Home, Amazon Alexa, or Samsung SmartThings, very few buy devices across multiple ecosystems.
However, when that does happen, Matter allows you to set up and use different ecosystems at once in your home, for example, to simultaneously use the voice assistants on different smart speaker platforms.
Most of these ecosystem vendors already allow Thread Border Router functionality on at least some of their speakers and display devices, and hence create a Thread mesh.
If you are using more than one ecosystem at the same time, you can still “see” and communicate with all Thread devices that are connected to another ecosystem vendor’s Border Router.
In other words, the Thread network is independent of a particular Matter ecosystem (or Matter Fabric) regardless of which one has set it up.
Unified Thread Networks: Credential Sharing
To support mass adoption, market dynamics for the home IOT industry indicate its primary goal is to create a positive user experience for the general consumer. Simultaneously, each ecosystem vendor is orchestrating its own roll-out for both how they simplify sharing of Thread credentials, and when they adopt APIs for more complicated home networks. This is complex work, and we are actively supporting our member companies as they diligently ensure the best possible outcome.
To that end, progress is evident in the growing number of vendors that have arranged for their Thread devices to share Thread credentials, the automatically generated encryption keys needed to join a specific Thread network. This allows all of the Thread devices to both appear on the home network and work together (which, as explained above, is always possible). And, because they share the same Thread network, the overall reliability and reach of the home network expands, as all Thread mains-powered devices can act as Mesh Extenders.
Ultimately, Thread Group is collaborating with its members to support the creation of a single Thread mesh between ecosystems and Border Routers, providing an even further boost in performance and reliability for the already intercommunicating Thread devices on a network.
Meanwhile, people continue to report that Thread-enabled devices deliver significant value -- including extended reach and increased reliability -- in their homes today.
Summary: Thread Devices Work Seamlessly Together on the Network
Whether you have one Thread Border Router, multiple Thread Border Routers connected to the same Thread mesh, or multiple Thread Border Routers each with their own Thread mesh: every Thread device is accessible by any other device (Wi-Fi, ethernet, or Thread) on the home network.
The devices on your home network work together – whether they are Thread, Wi-Fi, or ethernet connected – regardless of the Thread Border Router they are connected to. All thanks to the ingenuity and transparency of the ubiquitous Internet Protocol.