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.

IDEA: An Iterative-Deepen<strong>in</strong>g Algorithm for Energy-Efficient Query<strong>in</strong>g 201algorithm would asymptotically perform well <strong>by</strong> satisfy<strong>in</strong>g the query at a depthless than d. In deed, experiments show (Section 6) that for a fairly dense ad-hocnetwork with approximately 8 neighbors per node, with depth,d = 7, almost70% of all queries can be satisfied at a depth less than d.IDEA works on a network-wide rule called i-Rule which specifies the policyfor depths of iteration for search<strong>in</strong>g and the time-<strong>in</strong>terval between successiveiterations. Suppose the rule is, i − Rule = {i 1 ,i 2 ,i 3 ,T}, this means that thedepth of search for the first iteration is i 1 , the search depth for second iterationis i 2 and the third to depth i 3 . Intuitively, if the search reaches the third-leveliteration, then it has the same performance as BFS of depth i 3 . The <strong>in</strong>tervalbetween these successive iterations known as the <strong>in</strong>ter-iteration <strong>in</strong>terval, T, whichis required for the source (which <strong>in</strong>itiates the query) to receive and analyze theresponse messages. One advantage of such a policy is that the rule could bebased on any metric like the number of hops, time-to-search (like TTL) etc. But<strong>in</strong> case of ad hoc networks, the most common metric is the number of hops,consider<strong>in</strong>g that the communication cost is proportional to the number of hops.The algorithm details are expla<strong>in</strong>ed further below.For a i-Rule = {i,j,k,T}, a source node S <strong>in</strong>itiates flood<strong>in</strong>g (or BFS) tilla depth i i.e. start<strong>in</strong>g from the source the query is flooded to all nodes i hopsaway from the source. When the query reaches nodes that are i hops away,the query is halted and not flooded further. Dur<strong>in</strong>g this time the source S, mayor may not receive the response messages to the query. After wait<strong>in</strong>g for the<strong>in</strong>ter-iteration <strong>in</strong>terval, T, if it receives appropriate responses, then the sourcewould stop query<strong>in</strong>g. Else if the source does not receive appropriate results orno results, it <strong>in</strong>itiates the second search iteration. It is important to note that,the def<strong>in</strong>ition of the term ‘appropriate response’ or ‘search results’ is applicationspecific and is not addressed <strong>in</strong> this paper.To <strong>in</strong>itiate the second search iteration, source S will send the Cont<strong>in</strong>ue-jmessage, <strong>in</strong>dicat<strong>in</strong>g nodes to flood the message, j hops from the source. It shouldbe noted that nodes which are i hops away from the source, have already processedthe query and store the query with them (they are <strong>in</strong> halted state). Henceif these nodes (with<strong>in</strong> i hops from the source) were to process the query, it woulddegrade the performance of the protocol <strong>by</strong> wast<strong>in</strong>g energy of this constra<strong>in</strong>ed adhoc network. Instead of re-process<strong>in</strong>g the query, these nodes which are with<strong>in</strong> ihops from the source would simply forward the received cont<strong>in</strong>ue-j messages.Once the last node (i.e. i hops from the source) receives the message, thesenodes re-send the halted query, and flood it to all the nodes which are ‘j - i’hops from the present node (remember, j means j nodes from the source). Oneimportant po<strong>in</strong>t to note here is that, node will halt the query only for a timegreater than the <strong>in</strong>ter-iteration <strong>in</strong>terval, T; before delet<strong>in</strong>g its state.It would always be a case that more than one query and consequently manycont<strong>in</strong>ue messages are be<strong>in</strong>g flooded <strong>in</strong> the network. To match the queries withappropriate cont<strong>in</strong>ue messages, every query is assigned a unique identifier, as<strong>in</strong> case of DSR [2]. The cont<strong>in</strong>ue message will have the identifier for the correspond<strong>in</strong>gquery, thus nodes know which query is to be re-sent.

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

Saved successfully!

Ooh no, something went wrong!