16.11.2012 Views

Wireless Network Design: Optimization Models and Solution ...

Wireless Network Design: Optimization Models and Solution ...

Wireless Network Design: Optimization Models and Solution ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

9 Routing in Mobile Ad Hoc <strong>Network</strong>s 209<br />

flows. After traffic forwarding is achieved, the routing information is maintained for<br />

a fixed time before it is purged from the routing table.<br />

When a mobile node wishes to send packets to a destination, it starts checking if it<br />

has an available route in its routing table. If this is not the case, it will initiate a route<br />

discovery by sending a Route Request packet (RREQ) to locate the mobile recipient.<br />

This packet is distributed to its neighbors. The mobiles receiving the RREQ will<br />

look to determine if they have a route available to the recipient in their routing tables.<br />

If this is not the case, they in turn rebroadcast the RREQ packet to their neighbors<br />

<strong>and</strong> keep a trace 1 . RREQ packets are flooded throughout the network. When such a<br />

packet reaches the destination, or a mobile node that has a route to this recipient, a<br />

response packet (RREP) is generated by the mobile <strong>and</strong> sent back again, thanks to<br />

information stored in the caches traversed by the RREQ. During the flooding of the<br />

RREP packet, each mobile node will update its routing table by keeping the identity<br />

of the destination according to the selected route.<br />

For example, in Figure 9.5, the mobile node X, which has no route to mobile node<br />

Y, initiates a route discovery process. As we can see, the RREQ generates many<br />

redundancies <strong>and</strong> uses a high number of resources. From the MAC layer point of<br />

view, many nodes will compete in order to win a slot within the conflict resolution<br />

protocol. When the number of requests is very high, this protocol might result in<br />

very poor network performance. In a dense network (high number of neighbors per<br />

node), the uncontrolled flooding is a disaster for network performance.<br />

Fig. 9.5 Route discovery<br />

flooding<br />

9.4.2.2 DSR (Dynamic Source Routing)<br />

RREQ(1)<br />

RREQ(3)<br />

X Y<br />

RREQ(1)<br />

RREQ(2) RREQ(6)<br />

RREP<br />

RREP<br />

RREQ(4) RREQ(1)<br />

RREQ(7)<br />

RREQ(5)<br />

DSR is also a reactive protocol <strong>and</strong> it works in a very similar way to AODV. The<br />

main difference is in the routing procedure. AODV is table driven <strong>and</strong> DSR uses<br />

source routing. Nodes in DSR are idle <strong>and</strong> when a node decides to send traffic to a<br />

destination, it will initiate a route discovery in an identical procedure to AODV. Then<br />

to indicate the route, instead of creating local routing tables, each intermediate node<br />

1 Using sequence numbers on packets avoids infinite loops.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!