Wireless Mesh Configuration Distribution via Version Broadcasting
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing wireless mesh network configuration methods face issues such as message loss due to bad links and inefficient use of power and bandwidth resources, particularly in multi-hop communication, and require a more robust and efficient method for distributing configuration data.
Innovation Solution
A configuration system where each communication device broadcasts a configuration data description with a version identifier, allowing devices to request and update configuration data as needed, reducing the need for unsolicited push and solicited poll methods, and optimizing power and bandwidth usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If unsolicited push messages are used to distribute configuration data, then configuration data can be sent to nodes, but messages may be lost in multi-hop paths due to bad links and the gateway device cannot be aware of such loss
Solution Approach 1:
The patent implements feedback mechanisms where receiving nodes send acknowledgments back to the gateway device to confirm successful receipt of configuration data. The gateway device tracks which nodes have received updates and can retransmit to nodes that failed to acknowledge, ensuring reliable delivery despite multi-hop path issues.
Solution Approach 2:
The patent uses preliminary actions by maintaining buffers at the gateway device to store configuration data before it is needed, and by pre-establishing acknowledgment protocols. This allows the system to handle link failures and node connectivity issues proactively rather than reactively.
2Ease of operation
If solicited multi-hop poll method is used, then nodes can request configuration data, but it consumes power and bandwidth resources of multiple nodes and causes load in the network
Solution Approach 1:
The patent extracts the configuration data distribution function from individual node requests and implements it as a gateway-initiated push mechanism. Instead of every node polling the gateway, the gateway actively pushes updates only to nodes that need them, eliminating unnecessary power consumption and network traffic from nodes that already have current configuration data.
Solution Approach 2:
The patent applies partial action by selectively pushing configuration data only to specific nodes that require updates, rather than broadcasting to all nodes. The gateway uses node capability information and version tracking to determine which nodes need configuration data, reducing overall network load and node power consumption.
3Reliability
If long buffering times are used to handle node connectivity issues, then downlink messages can be retained for nodes with temporary connectivity loss, but message delivery is delayed
Solution Approach 1:
The patent implements dynamic buffering where the gateway device adjusts message retention based on real-time node connectivity status. Instead of fixed long buffering times, the system dynamically determines when to send, buffer, or discard messages based on acknowledgment receipts and connectivity monitoring, reducing unnecessary delays while maintaining reliability.
Data Source
AI summary
The application relates to a configuration system (100) for a wireless communication network (102) that comprises at least one first communication device (104b) and at least one second communication device (104c). The at least one first and second communication devices (104b, 104c) belong to a plurality of communication devices (104, 104a, 104b, 104c, 104d). Each communication device (104, 104a, 104b, 104c, 104d) in the plurality of the communication devices is a radio node device configured to provide a bi-directional radio communication with at least one of the plurality of the communication devices. After receiving (220) a content of a network persistent configuration data (CO) from a communication device (104a) belonging to the plurality of the communication devices and storing (222) the received content of the configuration data, each first communication device (104b) is configured to broadcast (224) a configuration data description (DE), which comprises a version identifier (VE) of the configuration data, periodically in the network for indicating a capability of said first communication device to send (228) the stored content of the configuration data, which is in accordance with the version identifier, on request.


