Gugrajah_Yuvaan_ Ramesh_2003.pdf
Gugrajah_Yuvaan_ Ramesh_2003.pdf
Gugrajah_Yuvaan_ Ramesh_2003.pdf
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Routing Protocols for Ad Hoc Networks<br />
2.2.4.3. Comparison of LAR and DREAM<br />
Chapter 2<br />
[Camp02] presents a simulation comparison of DSR, LAR, DREAM and a pure<br />
flooding algorithm. With zero average node speed the data packet delivery ratio of<br />
the DSR and LAR protocols is 100 % while that of DREAM and flooding is<br />
approximately 68% since there is much congestion in the network with the flooding<br />
algorithm and DREAM. When average speed is increased, LAR performs better than<br />
DSR. This is because LAR's use of location information to find a new route is more<br />
efficient than DSR's route discovery method. The promiscuous mode of DSR was<br />
found to significantly aid nodes in finding routes. DREAM had the highest average<br />
end-to-end delay of all protocols simulated. This is because the DREAM recovery<br />
procedure is used approximately 40 % of the time at low mobility and almost all the<br />
time at high speeds since the ACK is not received within the timeout. [Camp02]<br />
concluded that the added location capability of DREAM did not provide benefits<br />
over simple flooding algorithms. The location information used in the LAR protocols<br />
however was found to be significantly more beneficial than using the route request<br />
procedure of DSR. The LAR protocols were found to be considerably more efficient<br />
than DREAM in terms of packet delivery ratio and throughput.<br />
2.2.5. Routing with a Backbone<br />
Sivakumar et al [Siva98] describe a self organizing network structure ,called a spine<br />
which functions as a virtual backbone to facilitate routing in ad hoc networks. The<br />
spine is chosen to be a small and relatively stable sub-network of the ad hoc network<br />
whose primary role is to compute and maintain routes as opposed to carrying data<br />
packets. Every node in the network is either in the spine or is a neighbour of a node<br />
in the spine. The spine nodes maintain local copies of the global topology of the<br />
network and .collectively compute routes between any pair of nodes in the network.<br />
They are thus able to minimize the access overhead for routing information. Besides<br />
computing routes and tracking topology changes, the spine nodes also provide<br />
temporary backup routes for fault tolerance. The spine of an ad hoc network is<br />
depicted in Figure 2-6.<br />
2-21