METHOD FOR DISCOVERING A ROUTE TO A PEER NODE IN A MULTI-HOP WIRELESS MESH NETWORK

• US 20080317047A1
• Filed: 06/20/2007
• Published: 12/25/2008
• Est. Priority Date: 06/20/2007
• Status: Abandoned Application

• Current Assignee: Motorola, Inc. (Motorola Solutions, Inc.)
• Original Assignee: Motorola, Inc. (Motorola Solutions, Inc.)
• Inventors: Zeng, Surong, Ramachandran, Shyamal, Goldberg, Keith J., Strutt, Guenael T., Ozer, Sebnem Zorlu, Barker, Charles R. JR.
• Application Number:
  US11/765,704
• Publication Number:
  US 20080317047A1
• Time in Patent Office: Days
• US Class Current: 370/401
• CPC Class Codes: H04L 45/00 Routing or path finding of packets in data switching networks routing or path finding in wireless networks H04W40/00
• CPC Class Codes: H04W 40/12 based on transmission quality or channel quality
• CPC Class Codes: H04W 40/28 for reactive routing

Abstract

A method is provided for a particular multi-radio meshed node to discover a route to a peer multi-radio meshed node in a wireless multi-hop network including a plurality of multi-radio meshed nodes. Each of the multi-radio meshed nodes each includes a plurality of radio modules, and each radio module comprises an interface. The particular multi-radio meshed node transmits route request (RREQ) messages from each interface of a particular multi-radio meshed node. When a particular recipient multi-radio meshed node receives at least one of the route request (RREQ) messages, it generates a reverse route to the particular multi-radio meshed node. A peer-to-peer route is established when the particular multi-radio meshed node receives a route reply (RREP) message and can then be used to forward traffic to and from the destination node.

Claims

1. In a wireless multi-hop network including a plurality of multi-radio meshed nodes each comprising a plurality of radio modules, wherein each radio module comprises an interface, a method for a particular multi-radio meshed node to discover a route to a peer multi-radio meshed node, the method comprising:

transmitting route request (RREQ) messages from each interface of a particular multi-radio meshed node; and

receiving, at a particular recipient multi-radio meshed node, at least one of the route request (RREQ) messages and generating a reverse route to the particular multi-radio meshed node by;

(a) updating an existing reverse route entry for the reverse route based on the route information from the RREQ message, or (b) creating a new route entry for the reverse route based on the route information from the RREQ message if a route entry for the reverse route entry does not exist;

recording a local interface MAC address from which the RREQ message is received and a sending node interface MAC address in an interface information field of the reverse route entry; and

determining the sending node MAC address from a neighbor table, and recording the sending node MAC address as a next hop address in a particular node entry of the routing table.

2. A method according to claim 1, further comprising:

determining, at the particular recipient multi-radio meshed node, if the particular recipient multi-radio meshed node is the destination node of the route request (RREQ) message;

if the particular recipient multi-radio meshed node is the destination node of the route request (RREQ) message, generating at the particular recipient node a route reply (RREP) message, and transmitting the route reply (RREP) message using the local interface towards the next hop MAC interface along the reverse route to reach the particular multi-radio meshed node;

if the particular recipient multi-radio meshed node is not the destination node of the route request (RREQ) message, determining if the particular recipient multi-radio meshed node has another route to the destination node of the route request (RREQ) message; and

if the particular recipient multi-radio meshed node has another route to the destination node of the route request (RREQ) message, generating at the particular recipient node the route reply (RREP) message, and transmitting the route reply (RREP) message using the local interface towards the next hop MAC interface along the reverse route to reach the particular multi-radio meshed node; and

if the particular recipient multi-radio meshed node does not have another route to the destination node of the route request (RREQ) message, updating the route request (RREQ) message and retransmitting the updated route request (RREQ) message over each of the interfaces of the particular recipient multi-radio meshed node.

3. A method according to claim 2, further comprising:

upon receiving the route reply (RREP) message, generating a forward route entry to the destination node at the at least one intermediate multi-radio meshed node;

recording, at the at least one intermediate multi-radio meshed node, a local interface MAC address of the particular recipient multi-radio meshed node from which the route reply (RREP) message is received, and a the sending interface MAC address of the sending multi-radio meshed node in the next hop interface information field in a route table entry for the destination node;

determining, at the at least one intermediate multi-radio meshed node, a MAC address of the sending multi-radio meshed node by which the route reply (RREQ) message is transmitted from a neighbor table of the at one intermediate multi-radio meshed node;

updating the route table by recording the node MAC address of the sending multi-radio meshed node as the next hop address in a route table entry for the destination node;

determining, from the route table of the at least one intermediate multi-radio meshed node, the next hop interface MAC address and the local radio interface MAC address leading to the particular multi-radio meshed node identified by the originator MAC address in the route reply (RREP) message; and

forwarding the route reply (RREP) message towards the particular multi-radio meshed node identified by the originator MAC address in the route reply (RREP) message.

4. A method according to claim 3, further comprising:

receiving, at the particular multi-radio meshed node, the route reply (RREP) message, wherein a peer-to-peer route is established when the particular multi-radio meshed node receives the RREP message and can be used to forward traffic to and from the destination node; and

updating a route entry for the destination node at the particular multi-radio meshed node.

5. A wireless multi-hop network, comprising:

a plurality of multi-radio meshed nodes each comprising a plurality of radio modules, wherein each radio module comprises an interface;

a particular multi-radio meshed node seeking to discover a route to a peer multi-radio meshed node, wherein the particular multi-radio meshed node comprises a plurality of first radio modules each comprising a particular interface which transmits a particular route request (RREQ) message; and

a particular recipient multi-radio meshed node which receives at least one of the route request (RREQ) messages and generates a reverse route to the particular multi-radio meshed node.

6. A network according to claim 5, wherein the particular recipient multi-radio meshed node generates the reverse route to the particular multi-radio meshed node by:

performing at least one of;

(a) updating an existing reverse route entry for the reverse route based on the route information from the RREQ message, and (b) creating a new route entry for the reverse route based on the route information from the RREQ message if a route entry for the reverse route entry does not exist;

recording a local interface MAC address from which the RREQ message is received and a sending node interface MAC address in an interface information field of the reverse route entry; and

determining the sending node MAC address from a neighbor table, and recording the sending node MAC address as a next hop address in a particular node entry of the routing table.

7. A network according to claim 6, wherein the particular recipient multi-radio meshed node is designed to:

determine if the particular recipient multi-radio meshed node is the destination node of the route request (RREQ) message, or has a fresh route to the destination node of the route request (RREQ) message; and

generate a route reply (RREP) message if the particular recipient multi-radio meshed node;

is the destination node of the route request (RREQ) message, or has the fresh route to the destination node of the route request (RREQ) message; and

transmit the route reply (RREP) message using the local interface towards the next hop MAC interface along the reverse route to reach the particular interface of the particular multi-radio meshed node.

8. A network according to claim 7, wherein the at least one intermediate node which receives the route reply (RREP) message updates a forward route by generating a forward route entry to the destination node at the at least one intermediate multi-radio meshed node.

9. A network according to claim 8, wherein the particular multi-radio meshed node is designed to receive the route reply (RREP) message, wherein a peer-to-peer route is established when the particular multi-radio meshed node receives the RREP message and is usable to forward traffic to and from the destination node.