Bridge Node VLAN Status Update in Mesh Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Managing VLAN status updates in wireless mesh networks is challenging due to dynamic reconfiguration and resource wastage when data streams are forwarded to outdated access points, leading to inefficiencies and service disruptions.
Innovation Solution
A method involving bridge nodes that process VLAN status messages through bind request messages to promptly update VLAN associations, ensuring data streams are redirected to relevant group members, using messages like BREQ, BANN, and BRED to maintain accurate network configurations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of energy
If VLAN status is not updated promptly when nodes move between access points, then network connectivity is maintained, but network resources are wasted transmitting data to outdated access points
Solution Approach 1:
The patent implements a feedback mechanism where access points send bind status information back to bridge nodes. When a mobile station binds to a new access point, the new access point sends a bind status message to the bridge node, which then updates its VLAN status table and sends notifications to other access points. This feedback loop ensures VLAN status is kept current throughout the network, preventing resource wastage while maintaining connectivity.
Solution Approach 2:
The patent performs preliminary actions by proactively notifying other access points about VLAN status changes before data transmission is affected. When a mobile station rebinds, the bridge node immediately notifies other access points of the status change, allowing them to update their forwarding tables in advance and stop wasting resources on the old access point before the next data transmission cycle begins.
2Productivity
If VLAN status updates are implemented promptly, then network efficiency improves, but network complexity increases due to additional message processing
Solution Approach 1:
The patent makes the bridge node multi-functional by having it perform several tasks: receiving bind status messages from access points, updating VLAN status tables, generating notifications, and forwarding these notifications to other access points. By consolidating these functions in the bridge node, the patent improves network efficiency without proportionally increasing overall system complexity, as the bridge node already serves as a central management component.
3Adaptability or versatility
If mobile stations frequently rebind between access points, then network adaptability improves, but VLAN status synchronization becomes difficult
Solution Approach 1:
The patent performs preliminary synchronization actions by immediately updating VLAN status information when a mobile station binds to a new access point. The bridge node receives the bind status message, updates its table, and proactively notifies other access points before any data transmission occurs. This preliminary action ensures that VLAN status synchronization keeps pace with mobile station mobility, preventing information loss even during frequent rebinds.
Solution Approach 2:
The patent establishes a feedback mechanism where the bridge node continuously monitors bind status messages from access points and propagates VLAN status information throughout the network. This feedback loop ensures that whenever a mobile station moves between access points, the VLAN status is updated and synchronized across all relevant network components, maintaining adaptability without losing synchronization information.
Data Source
AI summary
A method for updating at a bridge node a virtual local area network (VLAN) status of a first node in a mesh network as provided enables improved network connectivity. The method includes processing a first VLAN status message that associates a first VLAN identifier with the first node, wherein the first VLAN status message was generated in response to a first bind request (BREQ) message. A second VLAN status message is then transmitted, wherein the second VLAN status message associates the first VLAN identifier with the first node. A third VLAN status message that associates a second VLAN identifier with the first node is then processed, wherein the third VLAN status message was generated in response to a second bind request (BREQ) message that associated the second VLAN identifier with the first node, and whereby the VLAN status of the first node is updated.