Avoiding mesh path discovery in wireless mesh networks

• US 8,687,521 B1
• Filed: 01/09/2012
• Issued: 04/01/2014
• Est. Priority Date: 12/01/2008
• Status: Active Grant

• Current Assignee: NXP USA, Inc. (NXP Semiconductors NV)
• Original Assignee: Marvell International Limited (Marvell Technology Group Limited)
• Inventors: Goel, Sandesh, Shukla, Ashish Kumar
• Primary Examiner(s): Orgad, Edan
• Assistant Examiner(s): MAGLO, EMMANUEL K
• Application Number:
  US13/346,177
• Time in Patent Office: 813 Days
• Field of Search: 370/248, 370/254, 370/351
• US Class Current: 370/254
• CPC Class Codes: H04L 45/122 by minimising distances, e.g. by selecting a route with minimum of number of hops
• CPC Class Codes: H04W 40/12 based on transmission quality or channel quality
• CPC Class Codes: H04W 40/246 Connectivity information discovery

Abstract

A network interface of a first mesh point device, the network interface including a memory and a medium access controller. In response to the first mesh point device receiving a frame, the medium access controller determines whether a mesh path for routing the frame from the first mesh point device to a second mesh point device is stored in the memory. In response to a mesh path not being stored in the memory, and prior to performing a mesh path discovery protocol, the medium access controller (i) determines whether the second mesh point device is one hop from the first mesh point device, and if so selects a one hop path for routing the frame to the second mesh point device, otherwise (ii) uses the mesh path discovery protocol to determine a mesh path for routing the frame to the second mesh point device.

Claims

1. A network interface of a first mesh point device, the network interface comprising:

a memory; and

a medium access controller, wherein in response to the first mesh point device receiving a frame to be transmitted to a second mesh point device, the medium access controller is configured to determine whether a mesh path for routing the frame from the first mesh point device to the second mesh point device is stored in the memory,

wherein, in response to a mesh path for routing the frame from the first mesh point device to the second mesh point device not being stored in the memory, and prior to performing a mesh path discovery protocol to determine a mesh path for routing the frame from the first mesh point device to the second mesh point device, the medium access controller is configured to

(i) determine, without using the mesh path discovery protocol, whether the second mesh point device is one hop from the first mesh point device, and if so select a one hop path for routing the frame from the first mesh point device to the second mesh point device, otherwise

(ii) use the mesh path discovery protocol to determine a mesh path for routing the frame from the first mesh point device to the second mesh point device.

2. The network interface of claim 1, wherein the medium access controller is configured to use a neighbor discovery protocol to determine whether the second mesh point device is one hop from the first mesh point device.

3. The network interface of claim 1, wherein the medium access controller is configured to determine whether the second mesh point device is one hop from the first mesh point device by sending the frame to the second mesh point device.

4. The network interface of claim 1, wherein the mesh path discovery protocol comprises a hybrid wireless mesh protocol or a multi-hop routing protocol.

5. The network interface of claim 1, wherein the medium access controller is configured to employ a history of previously found mesh paths to determine whether the second mesh point device is one hop from the first mesh point.

6. The network interface of claim 1, wherein, in response to a mesh path for routing the frame from the first mesh point device to the second mesh point device being stored in the memory, the medium access controller is configured to select the mesh path for routing the frame from the first mesh point device to the second mesh point device.

7. The network interface of claim 1, wherein:

the memory is configured to store a forwarding table; and

the medium access controller is configured to determine whether a mesh path for routing the frame from the first mesh point device to the second mesh point device is stored in the memory by determining whether an entry corresponding to the second mesh point device exists in the forwarding table.

8. The network interface of claim 1, wherein the medium access controller comprises:

a path loss module configured to measure a one-hop path loss of a multi-hop mesh path between the first mesh point device and the second mesh point device; and

a mesh path module configured to select a one-hop mesh path between the first mesh point device and the second mesh point device when the one-hop path loss of the multi-hop mesh path decreases to a value less than a predetermined threshold.

9. The network interface of claim 1, wherein the medium access controller comprises:

a forwarding module configured to forward the frame according to an entry for the second mesh point device in a forwarding table, wherein the frame is addressed to the second mesh point device, and wherein the forwarding table is stored in the memory; and

a mesh path module configured to generate the entry in the forwarding table for the second mesh point device in order to establish a one-hop mesh path from the first mesh point device to the second mesh point device.

10. The network interface of claim 9, wherein the medium access controller comprises:

a lifetime module configured to determine when a path lifetime ends for the entry; and

a discovery module configured to determine whether the second mesh point device is one hop from the first mesh point device in response to the path lifetime for the entry ending.

11. The network interface of claim 10, wherein:

the first mesh point device comprises a desktop computer, a personal digital assistant (PDA), a mobile phone, a laptop, a personal computer (PC), a printer, a digital camera, or an internet protocol (IP) phone; and

the second mesh point device comprises a desktop computer, a personal digital assistant (PDA), a mobile phone, a laptop, a personal computer (PC), a printer, a digital camera, or an internet protocol (IP) phone.

12. A method comprising:

receiving, at a first mesh point device, a frame to be forwarded to a second mesh point device; and

determining whether a mesh path for routing the frame from the first mesh point device to the second mesh point device is stored in a memory of the first mesh point device,

wherein, in response to a mesh path for routing the frame from the first mesh point device to the second mesh point device not being stored in the memory, and prior to performing a mesh path discovery protocol to determine a mesh path for routing the frame from the first mesh point device to the second mesh point device,

(i) determining, without using the mesh path discovery protocol, whether the second mesh point device is one hop from the first mesh point device, and if so selecting a one hop path for routing the frame from the first mesh point device to the second mesh point device, otherwise

(ii) using the mesh path discovery protocol to determine a mesh path for routing the frame from the first mesh point device to the second mesh point device.

13. The method of claim 12, wherein determining whether the second mesh point device is one hop from the first mesh point device comprises using a neighbor discovery protocol to determine whether the second mesh point device is one hop from the first mesh point device.

14. The method of claim 12, wherein determining whether the second mesh point device is one hop from the first mesh point device comprises sending the frame to the second mesh point device.

15. The method of claim 12, further comprising, wherein the mesh path discovery protocol comprises a hybrid wireless mesh protocol or a multi-hop routing protocol.

16. The method of claim 12, wherein determining whether the second mesh point device is one hop from the first mesh point device comprises employing a history of previously found mesh paths.

17. The method of claim 12, wherein:

the memory is configured to store a forwarding table; and

determining whether a mesh path for routing the frame from the first mesh point device to the second mesh point device is stored in the memory comprises determining whether an entry corresponding to the second mesh point device exists in the forwarding table.

18. The method of claim 12, wherein:

the first mesh point device comprises a desktop computer, a personal digital assistant (PDA), a mobile phone, a laptop, a personal computer (PC), a printer, a digital camera, or an internet protocol (IP) phone; and

the second mesh point device comprises a desktop computer, a personal digital assistant (PDA), a mobile phone, a laptop, a personal computer (PC), a printer, a digital camera, or an internet protocol (IP).