Extended service set mesh topology representation

• US 7,835,301 B1
• Filed: 04/15/2005
• Issued: 11/16/2010
• Est. Priority Date: 04/15/2005
• Status: Active Grant

• Current Assignee: NVIDIA Corporation
• Original Assignee: NVIDIA Corporation
• Inventors: Maufer, Thomas A.
• Primary Examiner(s): Kumar; Pankaj
• Assistant Examiner(s): Jones; Prenell P
• Application Number:
  US11/106,967
• Time in Patent Office: 2,041 Days
• Field of Search: 370/329, 370/351, 370/389, 370/400, 370/401, 370/392, 370/255, 370/230, 370/254, 370/338, 370/447, 370/462, 370/449, 370/328, 370/310, 370/315, 370/323, 709/238, 709/201, 709/240, 709/241, 709/228, 709/248, 709/237, 709/233, 455/562, 455/446, 455/414, 455/456, 455/461, 455/422, 455/434, 455/443, 455/447, 455/569, 340/539, 340/932
• US Class Current: 370/254
• CPC Class Codes: H04W 24/02 Arrangements for optimising operational condition

Abstract

A system and methods for wireless computing devices to become mesh member nodes within a self-configuring mesh network includes mechanisms for neighbor discovery and sharing of a common topology database including mesh topology and mesh network information. Each mesh node may use the topology database to determine optimized routing paths within the mesh network. Mesh member nodes are configured to detect and communicate topology changes and measured mesh network attributes to other members of the self-configuring wireless network.

Claims

1. A self-configuring wireless client, comprising:

a memory configured to store a neighbor list and a topology database representing a topology of a mesh networking system that includes the self-configuring wireless client, wherein the topology represents all wireless mesh nodes and stations within the mesh networking system; and

a networking element configured to communicate with a neighboring mesh node to join the mesh networking system, measure one or more system parameters associated with the mesh networking system to produce measurements, interpret the measurements at a set frequency, and exchange topology database updates based on the interpreted measurements.

2. The self-configuring wireless client of claim 1, further comprising a media access control driver configured to compute routing path information based on any one or more of the topology of the mesh networking system, attributes of the mesh networking system, and the mesh networking system metrics.

3. The self-configuring wireless client of claim 2, wherein the routing path information is computed for each message that is transmitted by the self-configuring wireless client.

4. The self-configuring wireless client of claim 2, wherein the routing path information is computed for all currently reachable destinations within the mesh when a path selection attribute of the mesh networking system changes or when the topology of the mesh networking system changes.

5. The self-configuring wireless client of claim 2, wherein the routing path information is stored in the memory.

6. The self-configuring wireless client of claim 2, wherein the media access control driver is configured to compare a version identifier corresponding to the topology database to a version identifier received by the self-configuring wireless client and determine if a topology database update is needed to synchronize the topology database.

7. The self-configuring wireless client of claim 1, wherein the memory is configured to store a version identifier corresponding to the topology database.

8. The self-configuring wireless client of claim 1, wherein the networking element is configured to send the neighbor list to the neighboring mesh node using a beacon.

9. The self-configuring wireless client of claim 1, wherein the networking element is configured to send the neighbor list to the neighboring mesh node using a multicast management frame subtype.

10. The self-configuring wireless client of claim 1, wherein the self-configuring wireless client is coupled to a wired network.

11. The self-configuring wireless client of claim 1, wherein the topology represents a portion of the mesh networking system and the portion includes a single self-configuring wireless client that is coupled to a wired network.

12. The self-configuring wireless client of claim 1, wherein the networking element is configured to exchange topology database updates based on a change in the topology of the mesh networking system.

13. The self-configuring wireless client of claim 1, wherein the networking element is configured to issue topology database updates based on a detected change in an attribute of the mesh networking system.

14. The self-configuring wireless client of claim 1, wherein the topology database includes measured attributes of the mesh networking system.

15. The self-configuring wireless client of claim 1, wherein the networking element is configured to insert an address corresponding to the self-configuring wireless client into a header of a message received by the self-configuring wireless client.

16. The self-configuring wireless client of claim 1, wherein the networking element is configured to insert an address corresponding to a next-hop mesh node within the mesh networking system into a header of a message received by the self-configuring wireless client.

17. The self-configuring wireless client of claim 1, wherein the topology database includes vendor-specific meta-data.

18. The self-configuring wireless client of claim 1, wherein the one or more system parameters include transmission error rate, mesh node link speed, or signal-to-noise ratio.

20. The self-configuring wireless client of claim 1, wherein the network element is configured to join the mesh networking system by determining whether a meshHello message generated by the neighboring mesh node includes a first neighbor list that includes the self-configuring wireless client attempting to join the mesh networking system.

21. The self-configuring wireless client of claim 1, wherein the neighboring mesh node is configured to not forward messages received on a reserved multicast address.

19. A self-configuring wireless client, comprising:

a memory configured to store a neighbor list and a topology database representing a topology of a mesh networking system that includes the self-configuring wireless client; and

a networking element configured to communicate with a neighboring mesh node to join the mesh networking system, measure one or more system parameters associated with the mesh networking system to produce measurements, interpret the measurements at a set frequency, and exchange topology database updates based on the interpreted measurements;

wherein the networking element is configured to join the mesh networking system by performing the steps of;

sending a first meshHello message to the neighboring mesh node on a reserved multicast address, wherein the neighboring mesh node is configured to not forward messages received on the reserved multicast address;

receiving a second meshHello message generated by the neighboring mesh node;

determining whether the second meshHello message includes a first neighbor list that includes the self-configuring wireless client attempting to join the mesh networking system; and

adding the neighboring mesh node to the neighbor list stored in the memory.