05.01.2013 Views

Ad Hoc Networks : Technologies and Protocols - University of ...

Ad Hoc Networks : Technologies and Protocols - University of ...

Ad Hoc Networks : Technologies and Protocols - University of ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Routing with Directional Antennas 217<br />

based on which the schedules are formed are based on identifiers <strong>and</strong> not based<br />

on the traffic generated.<br />

7.4 Routing with Directional Antennas<br />

The use <strong>of</strong> directional antennas can have an effect on routing. On-dem<strong>and</strong><br />

routing schemes can now scope their route queries in the direction in which the<br />

destination was last seen. With omni-directional antennas multi-path routing<br />

wherein (multiple paths are found between a source <strong>and</strong> a destination <strong>and</strong> used<br />

simultaneously) cannot be exploited very well since packets routed on one<br />

<strong>of</strong> the paths cause an interference zone that typically encompasses the other<br />

paths <strong>and</strong> thereby limits the number <strong>of</strong> packets routed on these paths. With<br />

directional antennas it is now possible to construct disjoint paths that do not<br />

interfere with each other [6]. The scheduling <strong>of</strong> transmissions (the directions<br />

in which antennas are to be pointed at different times) is tightly coupled with<br />

routing. However, current state <strong>of</strong> the art research has not looked at routing in<br />

great depth. It still remains an open area <strong>of</strong> research <strong>and</strong> possibilities for joint<br />

MAC/routing layer optimizations remain. In this section, we review the work<br />

on routing to date.<br />

7.4.1 On Dem<strong>and</strong> Routing Using Directional Antennas<br />

The first work on routing with directional antennas was by Nasipuri et al<br />

[2]. In this work, the authors examine the impact <strong>of</strong> directional antennas on the<br />

performance <strong>of</strong> on-dem<strong>and</strong> routing protocols (such as the <strong>Ad</strong> hoc On Dem<strong>and</strong><br />

Distance Vector Routing or the Dynamic Source Routing [9]). On-dem<strong>and</strong><br />

routing protocols are based on searching for a route to a desired destination<br />

when the need arises. This search typically involves the flood <strong>of</strong> a route request<br />

or RREQ message. The key idea in [2] is to propagate this route request<br />

message in the direction <strong>of</strong> the desired destination with the help <strong>of</strong> directional<br />

transmissions by a restricted set <strong>of</strong> nodes. The authors assume the presence <strong>of</strong><br />

simple switch beam or sectorized antennas. Two protocols are proposed.<br />

In the first protocol, when a source (say S) intends to compute a new route to<br />

a destination denoted by D, it broadcasts the route request query in the direction<br />

in which it had been communicating earlier with D. Any node that receives this<br />

query would then use the same technique, i.e., propagates the query in the same<br />

direction. This in effect, causes the query to be flooded in a conical section in the<br />

presumed direction <strong>of</strong> the destination. Clearly, the advantage <strong>of</strong> this process is<br />

to limit the scope <strong>of</strong> the flood. The scheme has been designed with the premise<br />

that the destination would not have moved too far from its initial position when<br />

it communicated with the originating node S. If this query were to fail, the<br />

query is re-initiated. The second time, it is flood throughout the network. The<br />

main drawback <strong>of</strong> this protocol is that it requires that the destination be in the

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

Saved successfully!

Ooh no, something went wrong!