Security continues to be a concern and challenge to those considering Internet of Things (IoT) implementations. A major threat that remains today is where the IoT network actually connects to the Internet, or what's often referred to as the border.
In a Thread mesh network, border routers are routers that sit at the edge of the Thread network and route between the Thread network and an external network. Border routers provide connectivity of the nodes on the Thread network to other devices in external networks or to the cloud. Thread gives IoT developers' flexibility and choices on how to implement this border router functionality via the following approaches:
- A function built into an end product (e.g. thermostat, dishwasher, home Wi-Fi routers, etc.)
- A standalone product that's an accessory to an end product(s) - can be built by your own resources or from an external company as a white label
- Access a border router already in the market, created by another vendor (standalone device, gateway, cable modem, etc.)
Because Thread is based on IPv6, Thread can carry one or more simultaneous flows of application layer traffic. Thread doesn't need to translate application layer traffic or act as a gateway from one network type to another at the edge of the Thread network. Thread border routers simply leverage IP routing to move IP traffic onto and off of the Thread network without translation.
Thanks to this IP routing design, the border router can offer access to Thread network services to devices connected to an external WAN. One type of basic service is the ability to discover and control the Thread commissioner. This service enables non-Thread devices such as computers, mobile phones and tablets to securely commission new Thread devices onto the mesh network through the border router via DTLS sessions. This service can also be expanded to include a trans-border router application layers. Features like service discovery and security can also allow a Thread device to access cloud-based services. While border routers enable Thread devices to access complementary network types and the multiple services running on them, border routers are not required in some applications. In such a cases, a Thread-native device must serve as the Commissioner.
Read more about the important functions these border routers bring to Thread members looking to securely connect their networks in this whitepaper.
Also, while there's much to consider in terms of security when developing a value-added IoT solution or product, you also need to consider cost, development investment, implementation, support, scalability, the ecosystem (or ecosystems) and future proofing. Learn more about each in this recent webinar, "Learn How Thread Delivers Value to You and Your Customers."
You'll see why Thread is not just a connectivity technology but is actually a flexible and future-proof IoT network technology. To view the webinar recording click here.