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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Deliver<strong>in</strong>g Messages <strong>in</strong> Disconnected Mobile Ad Hoc Networks 75its neighbour<strong>in</strong>g nodes. However, s<strong>in</strong>ce some nodes are known to have alreadyparticipated <strong>in</strong> the selection process for this message, node R can elim<strong>in</strong>ate fromconsideration the node it received the message from (S), the orig<strong>in</strong>al source node(X), and those nodes that are <strong>in</strong> the elim<strong>in</strong>ated set sent <strong>by</strong> S.A neighbour list request message, NBREQ, consists of the follow<strong>in</strong>g fields:A node T receiv<strong>in</strong>g a NBREQ message from node R replies with a neighbourlist reply message, NBREP. A NBREP control message sent <strong>by</strong> a node T consistsof the follow<strong>in</strong>g fields:The status field <strong>in</strong> the NBREP message reports on the status of this messageat the node that sent the reply, and can be one of three values: NEW mean<strong>in</strong>gthat this node knows noth<strong>in</strong>g of the message, NACKED, mean<strong>in</strong>g that this nodehas previously been sent a NACK for the message, or HELD, mean<strong>in</strong>g that thisnode is hold<strong>in</strong>g the message.Nodes respond<strong>in</strong>g with NACKED or HELD <strong>in</strong> their status are elim<strong>in</strong>atedfrom further consideration <strong>by</strong> R. After node R receives the neighbour list fromthe nodes, it uses the same algorithm as the source node X to select othernodes to hold message M. The only difference is <strong>in</strong> the <strong>in</strong>itialization of the setneigh(R). neigh(R) conta<strong>in</strong>s only those neighbour<strong>in</strong>g nodes of R that have notbeen elim<strong>in</strong>ated from consideration <strong>by</strong> R <strong>in</strong> any of the above steps. Aga<strong>in</strong> thenodes <strong>in</strong> the picked(R) set are sent a HOLD message conta<strong>in</strong><strong>in</strong>g the message Mand the set of R’s neighbours that were elim<strong>in</strong>ated from further consideration.This set conta<strong>in</strong>s the f<strong>in</strong>al value of elim<strong>in</strong>ated(R) together with the send<strong>in</strong>g node(S) and those neighbours that were elim<strong>in</strong>ated from consideration <strong>by</strong> R before.The nodes <strong>in</strong> the elim<strong>in</strong>ated(R) set are sent a NACK for the message.In order to bound the size of the HOLD control message, the elim<strong>in</strong>ated setsent <strong>by</strong> any node conta<strong>in</strong>s only those nodes that are its neighbours. Therefore,the upper bound on the size of the elim<strong>in</strong>ated set is the maximum number ofneighbours a node can have. The alternative of accumulat<strong>in</strong>g elim<strong>in</strong>ated nodes asthe HOLD message propagates would elim<strong>in</strong>ate some redundancy, at the expenseof hav<strong>in</strong>g HOLD messages that could be as large as the number of nodes <strong>in</strong> anypartition.Figure 1a shows an example network partition of 10 nodes. Suppose node 0wants to send a message to a node outside the network partition. It <strong>in</strong>itiates theprocess of select<strong>in</strong>g carrier nodes <strong>by</strong> first request<strong>in</strong>g the neighbour list from itsneighbour<strong>in</strong>g nodes 1, 2, 3, 4 and 5. After execution of the elim<strong>in</strong>ation processits picked set consists of nodes {2, 4} while its elim<strong>in</strong>ated set consists of {1, 3,5} which it sends to nodes <strong>in</strong> the picked set along with the message <strong>in</strong> a HOLDcontrol message. When node 2 receives the HOLD message it starts the selectionprocess <strong>by</strong> elim<strong>in</strong>at<strong>in</strong>g nodes 0, 1 and 3 from consideration and request<strong>in</strong>g theneighbour list from nodes 6 and 7. After execution of the algorithm its picked

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

Saved successfully!

Ooh no, something went wrong!