16.08.2013 Views

Gugrajah_Yuvaan_ Ramesh_2003.pdf

Gugrajah_Yuvaan_ Ramesh_2003.pdf

Gugrajah_Yuvaan_ Ramesh_2003.pdf

SHOW MORE
SHOW LESS

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 Chapter 2<br />

connected to one of the nodes in the dominating set. The second phase involves<br />

another flooding process which connects the nodes of the dominating set and this<br />

finally results in a single spine that runs through the network.<br />

Once the spine has been formed, spine nodes gather topology information from<br />

nodes that they dominate and the spine nodes transmit this link information to all<br />

other nodes on the spine. Using this global knowledge of the topology, the spine<br />

nodes determine the shortest paths for all node pairs. When a source node requires a<br />

route to a destination, the source node requests a route from its dominator in the<br />

spine. Route maintenance by the spine nodes are event-driven where the spine nodes<br />

update routes when nodes move and time-driven with topology updates being<br />

periodic.<br />

Core-Extraction Distributed Ad Hoc Routing (CEDAR) algorithm [Siva99] was<br />

introduced in an attempt to provide Quality of Service (QoS) routing in ad hoc<br />

networks. CEI?AR is based on the original spine routing algorithm using MCDS but<br />

bandwidth information is also included in the information stored at each dominator.<br />

When a source seeks a destination with a required bandwidth, a core-path is first<br />

established from the dominator node of the source to the dominator node of the<br />

destination. The core-path is then used to provide the direction in which to iteratively<br />

find a set of partial routes using only local information each of which satisfies the<br />

bandwidth requirement. Together the partial routes are expected to form a single QoS<br />

admissible route.<br />

The main problem with the spine routing is that with node movement the structure of<br />

the spine needs to change often. This means that it will be common for a new node to<br />

be added to the spine or for a spine node to move into a position where it finds a<br />

dominator and no longer needs to be a spine node. Changes in the spine structure<br />

mean that the topological information needs to be updated on all nodes along the<br />

spine. To overcome this problem, Partial Knowledge Spine Routing (PSR) [Siva98]<br />

was introduced, which only allows spine nodes to maintain local information of the<br />

nodes for which they are the dominator. Routing is then achieved by using on­<br />

demand methods. However, the spine routing infrastructure may still be unable to<br />

2-23

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

Saved successfully!

Ooh no, something went wrong!