Gugrajah_Yuvaan_ Ramesh_2003.pdf
Gugrajah_Yuvaan_ Ramesh_2003.pdf
Gugrajah_Yuvaan_ Ramesh_2003.pdf
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Routing Protocols for Ad Hoc Networks<br />
Chapter 2<br />
Chapter 2<br />
ROUTING PROTOCOLS FOR AD HOC NETWORKS<br />
2.1. Introduction<br />
Routing is the function of the network that detennines the path from a source to a<br />
destination for the establishment of viable communication. Ad hoc networking<br />
allows users to access the network independent of location and movement, but this<br />
mobility allows the topology of the network to change dynamically and<br />
unpredictably. The problem is amplified because routes often consist of multiple<br />
hops due to intentionally short transmission ranges that reduce interference and<br />
power consumption for nodes in the network. Several approaches have been<br />
proposed to provide routing for ad hoc networks by adapting techniques developed in<br />
wired networks. This chapter provides a survey of the existing schemes proposed for<br />
end-to-end routing in ad hoc networks.<br />
Section 2.2 introduces unicast protocols. The unicast protocols include traditional<br />
distance vector and link state routing, as well as newer path-finding routing protocols<br />
and on-demand routing protocols. Unicast protocols can be divided into proactive or<br />
table-driven protocols, described in Section 2.2.1 and the reactive or on-demand<br />
routing protocols described in Section 2.2.2. Modifications and hybrid varieties 'of<br />
the two types of unicast protocols have also been proposed and are discussed in<br />
Sections 2.2.3 to 2.2.7.<br />
Multicast routing protocols include variations on the shortest path tree algorithms,<br />
multicast trees and mesh-based protocols. In graph theory a tree is a path that does<br />
not contain any loops. Since this dissertation is focused on unicast routing protocols,<br />
multicasting is briefly reviewed in Section 2.3.<br />
2-1