|Publication number||WO2010013154 A1|
|Publication date||4 Feb 2010|
|Filing date||8 Jul 2009|
|Priority date||30 Jul 2008|
|Also published as||CN102124783A, CN102124783B, EP2319268A1, EP2319268B1, US20110128918|
|Publication number||PCT/2009/52977, PCT/IB/2009/052977, PCT/IB/2009/52977, PCT/IB/9/052977, PCT/IB/9/52977, PCT/IB2009/052977, PCT/IB2009/52977, PCT/IB2009052977, PCT/IB200952977, PCT/IB9/052977, PCT/IB9/52977, PCT/IB9052977, PCT/IB952977, WO 2010/013154 A1, WO 2010013154 A1, WO 2010013154A1, WO-A1-2010013154, WO2010/013154A1, WO2010013154 A1, WO2010013154A1|
|Applicant||Koninklijke Philips Electronics, N.V.|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (4), Non-Patent Citations (2), Referenced by (4), Classifications (13), Legal Events (5)|
|External Links: Patentscope, Espacenet|
A METHOD FOR DISCOVERING HIGH THROUGHPUT ROUTES IN
WIRELESS MESH NETWORKS
This application claims the benefit of U.S. Provisional Application No. 61/084,709 filed on July 30, 2008. The invention generally relates to the discovery of routes in mesh networks.
The WiMedia specification for ultra-wideband (UWB) systems defines a fully distributed medium access control (MAC) protocol for wireless personal area networks (WPANs). Due to regulatory restrictions the transmission power and transmission range of nodes in a WPAN is now limited. The WiMedia specification supports a number of different channel rates, including 53.3 Mbps, 80 Mbps, 106.7 Mbps, 160 Mbps, 200 Mbps, 320 Mbps, 400 Mbps, and 480Mbps.
To extend the communication range of WiMedia based WPANs, a mesh- enabled MAC protocol can be utilized in such networks. The mesh-enabled MAC protocol enables a node in the network to reach another node out of its direct communication range through other intermediate nodes. The intermediate nodes forward/relay the packets from a source node towards a destination node. The operation of the mesh MAC protocol is illustrated in Figure 1. In a mesh WiMedia based WPAN 100 a node 110-A cannot directly communicate with a node 110-F as they are out of each other's transmission range. However, the node 110-A can send packets to the node 110-F through mesh-enabled nodes 110-B and 110-D. Therefore, the route for transmitting data from the source node 110-A to a destination node 110-F includes the forwarding nodes 110-B and 110-D. The mesh-enabled nodes are nodes that implement the mesh MAC protocol.
Existing route discovery and routing protocols include, for example, a dynamic source routing (DSR) protocol and an ad hoc on demand distance vector (AODV) protocol. These protocols find a route only when there is a demand of traffic delivery, thus facilitating low routes maintenance overhead. As illustrated in Figure 2A, in order to discover a route, a source node 210-A broadcasts a route discovery request (RREQ) packet that is received by nodes 210-B and 210-C, which then forward the RREQ to their neighboring device(s). For example, as shown in Figure 2B, the node 210-B forwards a received RREQ to a node 210-C, 210-D, and 210-E, while the node 210-A forwards a received RREQ to a node 210-B and 210-D. The same process is carried out by the nodes 210-E and 210-D (see Figure 2C). After receiving a RREQ packet, the destination node sends back a route discovery response (RREP) packet to the source node along the route that a received RREQ travelled through. This is illustrated in Figure 2D where a node 210-F is the destination node. Based on the RREP the source node 210-A determines the route to send packets to the destination node 210-F.
The DSR and AODV protocols typically find routes with the smallest hop count, i.e., routes travelling through the smallest number of intermediate nodes. Consequently, each hop along the route has a hop distance close to the largest communication range. Thus, discovered routes can support only low transmission rates. As a result, the benefits of higher rates are not fully utilized. It would be therefore advantageous to provide an efficient route discovery solution in WiMedia mesh networks.
Certain embodiments of the invention include a method for discovering a route between a source node and a destination node in mesh wireless media (WiMedia) based networks. The method comprises upon receiving a route request (RREQ) by an intermediate node between the source node and the destination node, saving, in the RREQ, at least the identification (ID) number of the intermediate node and a transmission channel rate of a link on which the RREQ is received on; computing a new route price; determining if the new route price is larger than a price included in the received RREQ; updating the received RREQ to include the new route price when the new route price is larger than the route price in the received RREQ; and forwarding the updated RREQ to one or more neighbors of the intermediate node. Certain embodiments of the invention also include a computer readable medium having stored thereon computer executable code, when executed causing a processor to perform the process of discovering a route between a source node and a destination node in mesh wireless media (WiMedia) based networks. The process comprises upon receiving a route request (RREQ) by an intermediate node between the source node and the destination node, saving, in the RREQ, at least the identification (ID) number of the intermediate node and a transmission channel rate of a link on which the RREQ is received on; computing a new route price; determining if the new route price is larger than a price included in the received RREQ; updating the received RREQ to include the new route price when the new route price is larger than the route price in the received RREQ; and forwarding the updated RREQ to one or more neighbors of the intermediate node.
The subject matter that is regarded as the invention is particularly pointed out and distinctly claimed in the claims at the conclusion of the specification. The foregoing and other features and advantages of the invention will be apparent from the following detailed description taken in conjunction with the accompanying drawings.
Figure 1 is a schematic diagram of a mesh WiMedia WPAN. Figures 2A, 2B, 2C, and 2D are schematic diagrams of networks useful in demonstrating the operation of the existing discovery protocols.
Figure 3 is a flowchart describing the route discovery method implemented in accordance with an embodiment of the invention.
Figure 4 is a flowchart describing the step of computing a route price implemented in accordance with an embodiment of the invention.
Figures 5A, 5B, 5C, 5D, 5E, 5F and 5G are schematic diagrams of networks useful in demonstrating the operation of the discovery protocol implemented in accordance with an embodiment of the invention. It is important to note that the embodiments disclosed by the invention are only examples of the many advantageous uses of the innovative teachings herein. In general, statements made in the specification of the present disclosure do not necessarily limit any of the various claimed inventions. Moreover, some statements may apply to some inventive features but not to others. In general, unless otherwise indicated, singular elements may be in plural and vice versa with no loss of generality. In the drawings, like numerals refer to like parts through several views.
The discovery process disclosed herein finds a route between a source node and a destination node with the highest throughput. In accordance with the principles of the invention a route discovery request (RREQ) is a packet constructed to carry at least identification (ID) numbers of nodes that the RREQ travels through, channel rates used by links along the route to transmit the RREQ, a price of the route that the RREQ travelled through, and a last-node- neighbors list. The route price is a reciprocal sum of the effective rates calculated for links in a route. The last-node-neighbors list keeps a record of nodes on the route which are also the neighbors of the last node that the RREQ travelled through. Each node in the network maintains a neighbor table including an ID number of each of its neighboring nodes and a cache memory for storing recently received RREQs.
Figure 3 shows an exemplary and non-limiting flowchart 300 describing the method for discovering routes in wireless mesh networks implemented in accordance with an embodiment of the invention. The method is initiated by a source node which broadcasts a RREQ carrying at least the information mentioned above. The method is executed by each intermediate node, (i.e., a node in a path between the source node and destination node) receiving a RREQ. When transmitted from the source node the RREQ includes the source node's ID. At S310, an intermediate node receives a RREQ. At S320, an intermediate node inserts into the RREQ its ID and the rate of a link on which the RREQ is received. At S330, a price of route on which the RREQ travelled, i.e., a route between the source node and the intermediate node, is computed. Reference is now made to Figure 4, where the execution of S330 is shown in greater detail. At S410, a route R, which the received RREQ has travelled through, is retrieved from the RREQ. The route R is represented as:
R(S, F1, F2, F3, ..., Fk), where the node S is the source node and nodes F1 , F2,..., Fk-1 are the nodes that the RREQ already travelled through. At S420, the channel rates used by links along the route are obtained from the received RREQ. The channel rates are represented as (R1 , R2, ..., Rk-1 ), where R1 is the effective channel rate used by the link from nodes S to F1 , and Ri (2 < i < k-1 ) are the channel rates used by the links from nodes Fi-1 to Fi (2 < i < k-1 ). At S430, an effective transmission channel rate of the link between the nodes that transmitted the RREQ and the node that received the RREQ is computed. The effective channel rate of the link from a transmitting node (Fk-1 ) to a receiving node (Fk) is referred to as 'Rk', and Li (1 < i < k) denotes links between these nodes. An effective channel rate is the effective channel throughput computed by excluding the PHY/MAC protocol overhead for a given raw channel rate. The effective channel rate is different from a raw channel rate, which is defined by the WiMedia specification. In accordance with one embodiment the effective channel rate Rk is computed, by the receiving node (Fk), as follows:
TP = : τrts + 1CtS + ^ LT data + T 1T ack + T 1Tφ or Tp ~ * data "*" ' *- ack "*~ T
T data = τpre ■amble n
In the above equations, the parameter P is a payload size of a data packet, and the parameter Tp is the total time for completing a transmission of a data packet. The parameter Tp includes the transmission times of data (Tdata) packet and ACK(T3Ck) frames as well as any interframe spacing (Tlfs) between these frames. The time Tp may also include the transmission time of RTS/CTS (Trts/Tcts) if such are used. A transmission time of a data frame is based on the transmission time of the preamble ( Tpreamble ) which is fixed regardless of the selected channel ratei?c , a frame header (H^ ) which is transmitted at the channel rate Rc , the payload size P, and the raw channel rate Rc used to transmit the data frame. The payload size P may be an average payload size or any value adopted by the source node. The raw channel rate Rc may be a fixed channel rate used by the link or can be determined using known link adaptation algorithms.
At S440, the intermediate node (Fk) creates an updated last-node- neighbors list consisting of nodes on the route which are also the neighbors of node (Fk). As mentioned hereinabove, the node Fk receives a RREQ transmitted by the node Fk-1. At S450, a links list is created to include all links having at least one end-node being included in the last-node-neighbors list in the received RREQ or being a neighbor of node (Fk). For example, if the route is R(S, F1 , F2, F3 and F4) and the last-node-neighbors list in the RREQ received by a node F4 includes only node F2, then the links list includes links F1 ->F2, F2->F3 and F3->F4. At S460, a route price of the node (Fk) is computed by summing the reciprocals of the effective channel rate of all links in the links list. That is, the price is calculated as follows:
f price new
It should be noted that the existing routes discovery protocols, such as DSR and AODV can be adapted to implement the route discovery method disclosed herein. For example, existing routing protocols are required to wait a predefined amount of time to check whether additional RREQs are received during that time before the destination node can send back a RREP.
As another example, if a routing protocol is required to record a route and the route's price between all or some pairs of nodes that RREQs travelled through, the RREQ can be adapted to indicate the list of neighbors that the RREQ travelled through for all or some intermediate nodes (i.e., not only for the last node that the RREQ travelled through).
Referring to Figures 5A-5G where a non-limiting example demonstrating the operation of the route discovery process implemented in accordance with an embodiment of the invention is provided. Figure 5A shows a network including six nodes 510-A though 510-F. The effective channel rates of links are shown on the edges between two nodes. For sake of simplicity and demonstration the effective channel rates are the same as raw channel rates.
Figure 5B through Figure 5G show the travel route of RREQ sent from a source node 510-A to a destination node 510-F. The source node 510-A starts the route discovery process by sending a RREQ to nodes 510-B and 510-C (see Figure 5B). The route price calculated by the node 510-B is 1/160 and the route price calculated by node 510-C is 1/53.3. Then, the nodes 510-B and 510-C broadcasts the RREQ. The node 510-C also receives the RREQ sent by the node 510-B, and thereafter calculates the route price for that RREQ, which is 2/160. The new route price is less than previous calculated value 1/53.3. Thus, the node 510-C rebroadcasts the RREQ again with a new route (510-A, 510-B, 510-C) and a new price 2/160 to nodes 510-D and 510-E (see Figure 5C). Other nodes in the network 500 follow the same rule, see Figures 5E and 5F. The destination node 510-F receives a RREQ with a route (510-A, 510-B,
510-C, 510-D, 510-E, 510-F) with a price 4/160, a RREQ with a route (510-A, 510-C, 510-E, 510-F) with a route price 2/53.3+1/160, and some other RREQs. The node 510-F compares all the route prices, and selects the route with the smallest price, which is the route (510-A, 510-B, 510-C, 510-D, 510-E, 510-F). Subsequently, the destination node 510-F sends back a RREP along the selected route to the source node 510-A (see Figure 5G). The source node 510-A updates its route cache/table, and the route from nodes 510-A to 510-F is established.
It should be appreciated that routes discovered using the method described above have better throughput than shortest-hop routes discovered by existing protocols. For example such protocols would select routes (510-A, 510-C, 510- E, 510-F), (510-A, 510-B, 510-D, 510-F), or (510-A, 510-C, 510-D, 510-F). All these three routes have the same price 2/53.3+1/160 ~ 1/22.8, which has an approximate throughput of 22.8Mbps. For the network, the disclosed method selects the route (510-A, 510-B, 510-C, 510-D, 510-E, 510-F) with a price of 1/40 and an approximate throughput of 40Mbps. Therefore, the improvement for this example is about 75% in the end-to-end throughput. If there are more nodes and higher rates are available, the improvement can be even higher. The disclosed method can be implemented in communication systems including, but not limited to, UWB based WPANs, WiMedia based wireless networks and WPANs, or any time division multiple access (TDMA) or super- frame based wireless networks.
The principles of the invention are implemented as a combination of hardware, firmware and software. Moreover, the software is preferably implemented as an application program tangibly embodied on a program storage unit or computer readable medium. The application program may be uploaded to, and executed by, a machine comprising any suitable architecture. Preferably, the machine is implemented on a computer platform having hardware such as one or more central processing units ("CPUs"), a memory, and input/output interfaces. The computer platform may also include an operating system and microinstruction code. The various processes and functions described herein may be either part of the microinstruction code or part of the application program, or any combination thereof, which may be executed by a CPU, whether or not such computer or processor is explicitly shown. In addition, various other peripheral units may be connected to the computer platform such as an additional data storage unit and a printing unit. The foregoing detailed description has set forth a few of the many forms that the invention can take. It is intended that the foregoing detailed description be understood as an illustration of selected forms that the invention can take and not as a limitation to the definition of the invention. It is only the claims, including all equivalents that are intended to define the scope of this invention.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|WO2004114690A1 *||7 Jun 2004||29 Dec 2004||Meshnetworks, Inc.||Optimal routing in ad hac wireless communication network|
|WO2007073466A1 *||7 Dec 2006||28 Jun 2007||Intel Corporation||Routing in wireless mesh networks|
|WO2007099263A1 *||1 Mar 2007||7 Sep 2007||France Telecom||Routing method in an ad hoc network|
|US20040029553 *||8 Aug 2002||12 Feb 2004||Harris Corporation||Multiple path reactive routing in a mobile ad hoc network|
|1||*||JOHNSON RICE UNIVERSITY Y HU UIUC D MALTZ MICROSOFT RESEARCH D: "The Dynamic Source Routing Protocol (DSR) for Mobile Ad Hoc Networks for IPv4; rfc4728.txt", IETF STANDARD, INTERNET ENGINEERING TASK FORCE, IETF, CH, 1 February 2007 (2007-02-01), inet, pages 1 - 107, XP015055045, ISSN: 0000-0003|
|2||*||PERKINS NOKIA RESEARCH CENTER E BELDING-ROYER UNIVERSITY OF CALIFORNIA C ET AL: "Ad hoc On-Demand Distance Vector (AODV) Routing; rfc3561.txt", IETF STANDARD, INTERNET ENGINEERING TASK FORCE, IETF, CH, 1 July 2003 (2003-07-01), XP015009343, ISSN: 0000-0003|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|WO2016202381A1 *||17 Jun 2015||22 Dec 2016||Telefonaktiebolaget Lm Ericsson (Publ)||Path setup in a mesh network|
|CN103621144B *||4 Jun 2012||29 Mar 2017||三菱电机株式会社||用于在网络中发现路由集合的方法|
|EP3211841A1 *||21 Feb 2017||30 Aug 2017||Sagemcom Energy & Telecom SAS||Method for deciding to relay a copy of a route discovery request in a communication network by broadcast|
|US9319301||20 Sep 2011||19 Apr 2016||Fujitsu Limited||Method and node for realizing route discovery in network|
|International Classification||H04L12/56, H04W40/02|
|Cooperative Classification||H04L45/26, H04L45/302, H04L45/34, H04L45/125, H04W40/24|
|European Classification||H04L45/26, H04L45/302, H04L45/34, H04L45/125, H04L45/00, H04W40/24|
|24 Mar 2010||121||Ep: the epo has been informed by wipo that ep was designated in this application|
Ref document number: 09786551
Country of ref document: EP
Kind code of ref document: A1
|19 Jan 2011||ENP||Entry into the national phase in:|
Ref document number: 2011520620
Country of ref document: JP
Kind code of ref document: A
|28 Jan 2011||WWE||Wipo information: entry into national phase|
Ref document number: 13056466
Country of ref document: US
|1 Feb 2011||NENP||Non-entry into the national phase in:|
Ref country code: DE
|25 Feb 2011||ENP||Entry into the national phase in:|
Ref document number: 20117004521
Country of ref document: KR
Kind code of ref document: A