Method and system for updating a virtual local area network (VLAN) status of a node in a mesh network
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.
1. A method for updating at a bridge node a virtual local area network (VLAN) status of a first node in a mesh network, the method comprising:
processing at the bridge node in the mesh network 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 indicating that the first node is presently associated with a first VLAN;
transmitting from the bridge node a second VLAN status message, wherein the second VLAN status message associates the first VLAN identifier with the first node; and
processing at the bridge node a third VLAN status message that associates a second VLAN identifier with the first node, wherein the third VLAN status message was generated in response to a second bind request (BREQ) message indicating that the first node is now associated with a second VLAN, and whereby the VLAN status of the first node is updated.
2. The method of claim 1 , further comprising transmitting from the bridge node a fourth VLAN status message, wherein the fourth VLAN status message associates the second VLAN identifier with the first node.
3. The method of claim 1 , wherein the fourth VLAN status message is a bind announcement (BANN) message, a test frame, or a mesh null frame that is transmitted to a first intelligent access point (IAP) that generated the first VLAN status message.
4. The method of claim 1 , further comprising:
processing at the bridge node a first binding removed (BRED) message received from a first intelligent access point (IAP) that generated the first VLAN status message; and
transmitting a second BRED message from the bridge node to a second intelligent access point (IAP) that generated the third VLAN status message, wherein both the first BRED message and the second BRED message associate the second VLAN identifier with the first node.
5. The method of claim 1 , wherein the first VLAN status message comprises a bind announcement (BANN) message, a test frame, or a mesh null frame.
6. The method of claim 1 , wherein the second VLAN status message comprises a bind announcement (BANN) message, a test frame, or a mesh null frame.
7. The method of claim 1 , wherein the third VLAN status message comprises a bind announcement (BANN) message, a test frame, or a mesh null frame.
8. The method of claim 1 , wherein the first VLAN status message was generated at a first intelligent access point (IAP) and the third VLAN status message was generated at a second IAP.
9. The method of claim 1 , wherein the first node is a routable device.
10. The method of claim 1 , wherein the first node is a non-routable device.
11. The method of claim 1 , wherein the first node is a station (STA) or a mesh point (MP).
12. A bridge node in a mesh network, comprising:
a computer readable medium being a non-transitory signal having computer readable program code components for processing at the bridge node in the mesh network a first VLAN status message that associates a first VLAN identifier with a first node, wherein the first VLAN status message was generated in response to a first bind request (BREQ) message indicating that the first node is presently associated with a first VLAN;
a computer readable medium being a non-transitory signal having computer readable program code components for transmitting from the bridge node a second VLAN status message, wherein the second VLAN status message associates the first VLAN identifier with the first node; and
a computer readable medium being a non-transitory signal having computer readable program code components for processing at the bridge node a third VLAN status message that associates a second VLAN identifier with the first node, wherein the third VLAN status message was generated in response to a second bind request (BREQ) message indicating that the first node is presently associated with a second VLAN, and whereby the VLAN status of the first node is updated.
13. The bridge node of claim 12 , further comprising a computer readable medium being a non-transitory signal having computer readable program code components for transmitting from the bridge node a fourth VLAN status message, wherein the fourth VLAN status message associates the second VLAN identifier with the first node.
14. The bridge node of claim 13 , wherein the fourth VLAN status message is a bind announcement (BANN) message, a test frame, or a mesh null frame that is transmitted to a first intelligent access point (IAP) that generated the first VLAN status message.
15. The bridge node of claim 12 , further comprising:
a computer readable medium being a non-transitory signal having computer readable program code components for processing at the bridge node a first binding removed (BRED) message received from a first intelligent access point (IAP) that generated the first VLAN status message; and
a computer readable medium being a non-transitory signal having computer readable program code components for transmitting a second BRED message from the bridge node to a second intelligent access point (IAP) that generated the third VLAN status message, wherein both the first BRED message and the second BRED message associate the second VLAN identifier with the first node.
16. The bridge node of claim 12 , wherein the first VLAN status message comprises a bind announcement (BANN) message, a test frame, or a mesh null frame.
17. The bridge node of claim 12 , wherein the second VLAN status message comprises a bind announcement (BANN) message, a test frame, or a mesh null frame.
18. The bridge node of claim 12 , wherein the third VLAN status message comprises a bind announcement (BANN) message, a test frame, or a mesh null frame.
19. The bridge node of claim 12 , wherein the first VLAN status message was generated at a first intelligent access point (IAP) and the third VLAN status message was generated at a second IAP.
20. A bridge node in a mesh network, comprising:
means for processing at the bridge node in the mesh network a first VLAN status message that associates a first VLAN identifier with a first node, wherein the first VLAN status message was generated in response to a first bind request (BREQ) message indicating that the first node is presently associated with a first VLAN;
means for transmitting from the bridge node a second VLAN status message, wherein the second VLAN status message associates the first VLAN identifier with the first node; and
means for processing at the bridge node a third VLAN status message that associates a second VLAN identifier with the first node, wherein the third VLAN status message was generated in response to a second bind request (BREQ) message indicating that the first node is now associated with a second VLAN, and whereby the VLAN status of the first node is updated.