Mesh Network Port Binding via Control Infrastructure
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In mesh networks, endpoints face communication disruptions due to unpredictable public port reallocations by NAT devices, leading to inefficient retransmissions and resource consumption as they are unaware of port changes, causing dropped data and increased resource usage.
Innovation Solution
A method where devices in a mesh network transmit binding requests to a control infrastructure using a dedicated meshnet local port, allowing the infrastructure to determine and communicate the currently allocated public port, ensuring seamless data routing and minimizing resource wastage by avoiding retransmissions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of energy
If NAT devices reallocate public ports dynamically, then network resource utilization is improved, but communication reliability deteriorates due to unpredictable port changes
Solution Approach 1:
The patent implements a feedback mechanism where the control infrastructure continuously monitors public port allocations and sends updates to mesh network devices. When a NAT device reallocates a public port, the control infrastructure detects this change and communicates the new port assignment to the relevant devices, ensuring they can maintain reliable communication despite dynamic port changes.
Solution Approach 2:
The control infrastructure acts as an intermediary between NAT devices and mesh network endpoints. It receives port allocation information from NAT devices and distributes this information to the appropriate endpoints, shielding them from the complexity and unpredictability of NAT port management while maintaining communication reliability.
2Device complexity
If endpoints are unaware of port changes, then device complexity is reduced, but data transmission reliability deteriorates due to dropped packets
Solution Approach 1:
The control infrastructure serves as an intermediary that handles port change notifications centrally. Endpoints simply send binding requests to the control infrastructure, which then provides the current public port information. This approach keeps endpoint complexity low while ensuring reliable data transmission through accurate port information.
Solution Approach 2:
The system implements a self-service mechanism where the control infrastructure automatically tracks and communicates port allocations to endpoints on demand. When an endpoint needs to communicate, it queries the control infrastructure for the current port binding, and the infrastructure provides this information without requiring the endpoint to monitor or manage port changes itself.
3Productivity
If binding requests are transmitted to control infrastructure, then routing efficiency is improved, but network communication overhead increases
Solution Approach 1:
The system performs preliminary actions by establishing binding requests before actual data transmission. Endpoints query the control infrastructure in advance to obtain current public port bindings, ensuring that subsequent data transmissions use the correct ports. This preliminary information gathering improves routing efficiency while minimizing overhead through batched or cached queries.
Solution Approach 2:
The binding request mechanism operates periodically or on-demand rather than continuously. Endpoints transmit binding requests at intervals or when needed, allowing the control infrastructure to maintain port information without requiring constant communication. This periodic approach improves routing efficiency while limiting network overhead to necessary update moments.
Data Source
AI summary
A method including receiving, by an infrastructure device in communication with a first device in a mesh network, a binding request from a meshnet local port associated with the first device that is dedicated for communicating meshnet data associated with the first device, the binding request requesting the infrastructure device to determine a currently allocated public port associated with the first device; and transmitting, by the infrastructure device to the first device, a response indicating the currently allocated public port associated with the first device. Various other aspects are contemplated.