Mesh Network Root Node TCP/IP Configuration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In large mesh networks, the need for each IP datagram to undergo a NAT process at the parent node before reaching the router significantly reduces efficiency, as each parent node must maintain tables and recalculate checksums for IP packets.
Innovation Solution
Implementing a method where the root node shares its IP configuration with ordinary nodes, allowing them to use a static IP configuration and map MAC addresses to ports, thereby eliminating the need for NAT at each parent node and reducing the need for checksum recalculation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If each parent node performs NAT process for IP datagrams, then external devices can access internal devices through the mesh network, but the mesh network efficiency is greatly reduced due to table maintenance and checksum recalculation at each parent node
Solution Approach 1:
The invention extracts the NAT function from multiple parent nodes and concentrates it solely at the root node. This eliminates the need for intermediate parent nodes to perform NAT operations, table maintenance, and checksum recalculation, thereby resolving the contradiction between maintaining network accessibility and improving mesh network efficiency
Solution Approach 2:
The root node serves multiple functions: it acts as the NAT gateway for the entire mesh network, maintains the NAT table, and coordinates IP address allocation. This universal role at the root node eliminates the need for distributed NAT operations across multiple parent nodes, improving overall network efficiency while preserving external accessibility
2Reliability
If each parent node maintains a table for IP datagrams and recalculates checksums, then NAT functionality is achieved, but processing overhead and time consumption increase significantly
Solution Approach 1:
The invention extracts the time-consuming table maintenance and checksum recalculation operations from multiple parent nodes and centralizes them at the root node only. This reduces the number of nodes performing these operations from potentially many to just one, significantly reducing total processing time while maintaining NAT functionality
Solution Approach 2:
The root node performs NAT table maintenance and checksum operations in advance and centrally, rather than having each parent node perform them independently when packets pass through. This preliminary and centralized action reduces redundant processing and time loss across the network
Data Source
AI summary
Disclosed is a method for applying a TCP/IP protocol in a mesh network, comprising: constructing protocol stack models of a root node and one or more ordinary nodes in the mesh network; the root node using a custom IE in a management frame to share an IP configuration acquired by itself from a router, a MAC address of itself, and a MAC address of the router with the ordinary nodes; each ordinary node adopting a static IP configuration mode to set its IP configuration as that of the root node; the root node acquiring a port range available for each ordinary node; and each node in the mesh network communicating with an external IP network over a TCP/IP protocol stack. In the invention, when an IP datagram is forwarded in the mesh network, there is no need to perform layer-by-layer NAT, and no need to recalculate a checksum of the IP datagram when it reaches the root node, thereby greatly improving network communication efficiency.