13.07.2015 Views

Page 2 Lecture Notes in Computer Science 2865 Edited by G. Goos ...

Page 2 Lecture Notes in Computer Science 2865 Edited by G. Goos ...

Page 2 Lecture Notes in Computer Science 2865 Edited by G. Goos ...

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.

14 J. Doshi and P. Kilambiour protocol differs from [10] <strong>in</strong> various ways. In [10] the proactive region isuniform depend<strong>in</strong>g on the zone radius. [10] adjusts the zone radius dynamically.In our protocol the zone is not uniform. Each node selectively adds only thebest (most fit) nodes <strong>in</strong> its neighborhood to its proactive region. In [10], theadjustment of the zone is based on an approximation cost model. [10] adjuststhe proactive region <strong>in</strong> order to make a node more accessible. We change theproactive region <strong>in</strong> order to reduce route acquisition latencies. Unlike [10], we usethe concept of FITNESS(a Genetic Algorithm-based technique) to determ<strong>in</strong>e thenode’s participation <strong>in</strong> proactive rout<strong>in</strong>g. This yields a more realistic proactiveregion as it takes <strong>in</strong>to account the chang<strong>in</strong>g environment of a node.This paper is organized as follows. In section 3, we give an overview of theproposed protocol, br<strong>in</strong>g<strong>in</strong>g out its salient features. Section 4 conta<strong>in</strong>s the completefunctional description of the protocol. Section 5 conta<strong>in</strong>s simulation resultswhere we <strong>in</strong>vestigate performance of our protocol and the issues of scalabilityand route acquisition latencies. In section 6 we <strong>in</strong>vestigate adapt<strong>in</strong>g the protocolfor power oriented rout<strong>in</strong>g.3 Overview of SAFAROur protocol uses a fitness-based rout<strong>in</strong>g table buildup scheme. The fitness ofa node is based on node characteristics like power or bandwidth value and canchange over time. We query nodes, which have a “good” idea about its surround<strong>in</strong>gs.This m<strong>in</strong>imizes the overhead to ma<strong>in</strong>ta<strong>in</strong> the routes when comparedto proactive protocols and other hybrid protocols. In comparison to purely reactiveschemes, our protocol reduces route acquisition latency. Exist<strong>in</strong>g protocolsare not adaptive <strong>in</strong> terms of overhead. The disadvantage of a non-adaptive approachis that the diversity of the nodes is completely ignored. A node withlow bandwidth (or power - <strong>in</strong> battery time left) cannot afford the overhead <strong>in</strong>volved<strong>in</strong> hav<strong>in</strong>g actively ma<strong>in</strong>ta<strong>in</strong>ed routes. But a node with good bandwidth,which can afford this, helps boost its own performance as well as that of itsneighborhood. This is an example of an adaptive “overhead” scheme.For rout<strong>in</strong>g we use a two-stage approach with a limited discovery scheme <strong>in</strong>the first stage. There is a very high probability of f<strong>in</strong>d<strong>in</strong>g a route <strong>in</strong> the firststage itself. Thus the overhead of a reactive route discovery stage is avoided. Ifthe route is not found <strong>in</strong> the first stage then we use a route discovery proceduresimilar to the on demand protocols. In our protocol, data is routed be-tween twomobile nodes. We do not explore multicast operation of SAFAR. Each mobilenode ma<strong>in</strong>ta<strong>in</strong>s a rout<strong>in</strong>g table. The rout<strong>in</strong>g table conta<strong>in</strong>s the node’s address,next-hop address, bandwidth (<strong>in</strong> kbps) and power(<strong>in</strong> battery m<strong>in</strong>utes rema<strong>in</strong><strong>in</strong>g).Ancillary <strong>in</strong>formation like neighbor and update lists, required <strong>by</strong> the protocol,need to be ma<strong>in</strong>ta<strong>in</strong>ed separately or as part of the rout<strong>in</strong>g table itself. Eachnode also ma<strong>in</strong>ta<strong>in</strong>s a node heap which is a max heap ma<strong>in</strong>ta<strong>in</strong>ed <strong>in</strong> terms ofa cost value (power or bandwidth). This heap is used dur<strong>in</strong>g the table buildupprocedure expla<strong>in</strong>ed <strong>in</strong> 4.2. Power optimizations will be expla<strong>in</strong>ed <strong>in</strong> section 6.

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

Saved successfully!

Ooh no, something went wrong!