Active Mesh Gate Verification in 802.11s Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The IEEE 802.11s standard lacks mechanisms for actively verifying if a candidate peer functions as a mesh gate and determining a primary mesh gate, leading to issues like network connectivity bottlenecks and broadcast storms due to unmanaged mesh gate interactions.
Innovation Solution
A method where a network device in a mesh basic service set actively verifies a candidate peer's function as a mesh gate by updating records and sending inquiry packets, and determines the primary mesh gate by processing information using a predetermined algorithm to manage mesh gate interactions and prevent broadcast storms.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If mesh stations connect to form multiple MBSSs through different channels according to IEEE 802.11s standard, then mesh network connectivity is established, but the MBSSs cannot be interconnected and some may have no mesh gate
Solution Approach 1:
The patent implements an active verification mechanism where mesh stations send verification packets to mesh gates and receive acknowledgments. This feedback loop allows the network to dynamically detect the operational status of mesh gates and maintain accurate routing information, ensuring reliable interconnection across MBSSs
Solution Approach 2:
The patent enables mesh stations to autonomously verify mesh gate status and update their own routing tables without external intervention. Each mesh station independently performs verification and maintains its own connection state information, allowing the network to self-heal and adapt to changes in mesh gate availability
2Loss of information
If IEEE 802.11s standard uses broadcast packets to announce mesh gate role, then mesh gate identity is published, but there is no retransmission and acknowledgement mechanism for active verification
Solution Approach 1:
The patent introduces a two-way verification mechanism where mesh stations send verification packets to mesh gates and receive acknowledgments. This feedback loop ensures reliable delivery of mesh gate status information without requiring complex retransmission protocols, as the acknowledgment confirms successful reception and processing
Solution Approach 2:
The patent extracts the essential verification function from the complex IEEE 802.11s protocol suite, implementing a simplified active verification mechanism that focuses specifically on mesh gate status detection. This extracted approach avoids the overhead of full protocol compliance while achieving the core verification objective
3Object-affected harmful factors
If RSTP blocks critical paths to prevent broadcast storms, then broadcast and multicast packets are prevented from loops, but unicast packet transmission paths are reduced causing bottlenecks
Solution Approach 1:
The patent segments the network traffic into different types (broadcast, multicast, unicast) and applies different handling mechanisms. Mesh gates maintain spanning tree blocks for broadcast/multicast traffic to prevent storms, while simultaneously maintaining separate unicast path information that can bypass blocked critical paths, thus preventing broadcast storms while preserving unicast transmission efficiency
Solution Approach 2:
The patent applies different quality characteristics to different traffic types and network paths. Critical paths are blocked for broadcast/multicast traffic locally at mesh gates to prevent storms, while unicast traffic is allowed to use alternative non-critical paths with different quality characteristics, optimizing transmission efficiency for each traffic type according to its specific requirements
Data Source
AI summary
A method for verifying whether a candidate peer functions as a mesh gate is performed by a network device in a mesh basic service set including the candidate peer. The method includes: providing a record indicates that the candidate peer doesn't function as the mesh gate, when the network device receives a notification from the candidate peer indicating that the candidate peer now functions as the mesh gate, having the network device update the record and start a counting process and verifying whether the candidate peer continues functioning as the mesh gate till the end of the counting process; when the network device doesn't receive an updated notification from the candidate peer indicating that the candidate functions as the mesh gate before the end of the counting process, having the network device send a packet to the candidate peer to verify whether the candidate peer functions as the mesh gate.