Thread over IP Multi-PHY Routing for Partitioned Network Connectivity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Thread networks face challenges with limited coverage and partitioning, leading to connectivity issues and increased complexity in managing multiple IPv6 subnets and routing, which can result in delayed or lost application data and user confusion during device commissioning.
Innovation Solution
Incorporating Internet Protocol (IP)-based link technologies like Wi-Fi and Ethernet into Thread networks to leverage their higher throughput and coverage while maintaining compatibility with low-power devices, using the Thread Radio Encapsulation Link (TREL) protocol to enable communication over multiple physical layers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If Thread networks operate over IEEE 802.15.4 radio networks with limited coverage, then low-power device operation is maintained, but network partitioning occurs and connectivity is limited
Solution Approach 1:
The patent combines Thread (IEEE 802.15.4) and Wi-Fi networks into a unified fabric network, allowing devices to communicate through either Thread direct links or Wi-Fi backhaul links. This merging extends network coverage while maintaining low-power operation for Thread devices, resolving the contradiction between limited coverage and power consumption.
Solution Approach 2:
The patent introduces Wi-Fi as an intermediary backhaul network that bridges Thread partitions. When Thread direct connectivity is unavailable, devices can route traffic through the Wi-Fi network, which acts as a mediator to restore connectivity without requiring Thread devices to increase their radio power or range.
2Reliability
If multiple Thread partitions are created to maintain connectivity, then device communication within partitions is preserved, but complexity in managing multiple IPv6 subnets and routing increases
Solution Approach 1:
The patent implements a universal IPv6 addressing scheme where all devices in the fabric network, regardless of which Thread partition they belong to, share a common IPv6 subnet. This multi-functionality allows the network to maintain partitioned Thread topology for reliable device communication while presenting a unified IPv6 network to applications, eliminating the need to manage multiple subnets and complex routing.
3Use of energy by moving object
If Thread network deployment is sparse to conserve resources, then battery life is extended, but coverage is limited and partitions are more likely to occur
Solution Approach 1:
The patent uses Wi-Fi as an intermediary backhaul that compensates for sparse Thread deployment. Battery-powered Thread devices can maintain low power consumption with limited Thread radio activity, while the Wi-Fi network provides the necessary backhaul connectivity to overcome the limited Thread coverage, ensuring reliable network connectivity without sacrificing battery life.
Data Source
AI summary
Techniques and devices for determining a preferred physical layer for communication by a node in a Thread network are described. The node transmits a first IPv6 over Low power Wireless Personal Area Networks, 6LoWPAN, frame to a neighbor node using a first physical layer and transmits the first 6LoWPAN frame to the neighbor node using a second physical layer. The node determines a first preference value for the neighbor node using the first physical layer and determines a second preference value for the neighbor node using the second physical layer. The node compares the first preference value and the second preference value to determine the preferred physical layer for communication and transmits a second 6LoWPAN frame to the neighbor node using the preferred physical layer.