Thread Drone Mesh Networking for Low-Power Indoor Resilience
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing drone mesh networks are expensive, designed for outdoor environments, and lack low power and GPS capabilities, failing to provide seamless indoor connectivity and access to external networks.
Innovation Solution
A low-power mesh network using the Thread protocol, implemented with OpenThread, enables ground-to-air, air-to-air, and air-to-ground connectivity, utilizing battery-powered drones equipped with NRF52840 MDK chips and OpenThread for IPv6 mesh connectivity, allowing seamless integration with future IoT networks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional IEEE 802.11-based protocols are used for drone mesh networks, then network connectivity is established, but power consumption is high and devices are expensive
Solution Approach 1:
The patent changes the fundamental protocol parameters from IEEE 802.11 (WiFi) to Thread/802.15.4, which operates at lower power consumption levels suitable for battery-powered drones. This parameter change enables the network to maintain connectivity while significantly reducing energy usage.
Solution Approach 2:
The patent employs low-cost Thread-certified modules instead of expensive WiFi equipment. These modules are designed for cost-effective deployment in large numbers, enabling economical mesh network formation across multiple drones without requiring high-end hardware.
2Reliability
If IEEE 802.11-based mesh networks are deployed, then connectivity is achieved, but the network lacks low power capabilities and GPS functionality for indoor environments
Solution Approach 1:
The patent creates a universal mesh network solution using Thread protocol that works across both indoor and outdoor environments. The network is designed to be protocol-agnostic and environment-agnostic, providing seamless connectivity without requiring GPS or external infrastructure, making it adaptable to diverse deployment scenarios.
Solution Approach 2:
The patent extracts the dependency on GPS and external infrastructure from the network design. By using Thread's self-organizing mesh capability, the network operates independently without requiring satellite signals or access points, enabling pure indoor operation.
3Ease of operation
If BATMAN routing protocol is used in drone mesh networks, then routing is enabled, but the network cannot access external networks or the cloud
Solution Approach 1:
The patent introduces Thread border routers as intermediary devices that bridge the Thread mesh network with IP-based external networks. These border routers translate and route traffic between the Thread protocol and standard IP protocols, enabling cloud connectivity and external network access while maintaining the Thread network's independence.
4Device complexity
If centralized approaches are used for IoFT networks, then network management is simplified, but single point failure risk increases
Solution Approach 1:
The patent segments the network control function across multiple distributed Thread nodes rather than centralizing it. Each drone equipped with Thread can independently make routing decisions and maintain network operation, eliminating single points of failure while keeping management straightforward through Thread's built-in automated protocols.
Data Source
AI summary
Embodiments of the disclosure relate to a mesh network. The mesh network includes a plurality of drones and a border router. The plurality of drones is configured to communicate with each other and with the border router over a first protocol. The first protocol uses IPV6 mesh connectivity at a first bandwidth. At least one drone of the plurality of drones operates as a router, and at least one drone of the plurality of drones operates as an end device. The router is configured to communicate with the border router and with the end device, and the end device is configured to communicate only with the router. The border router can be configured to communicate with an external network over a second protocol using a second bandwidth, and the second bandwidth can be greater than the first bandwidth.