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 77from node 4 and a NACK from node 2 for the same application message. In sucha situation, the HOLD message always overrides the negative acknowledgement.3.3 Message DeliveryOnce every FIND DST INTERVAL, each node tries to f<strong>in</strong>d a route to the dest<strong>in</strong>ationsof the messages it has stored <strong>in</strong> its HOLDMSG queue. If it is able to f<strong>in</strong>da route to a dest<strong>in</strong>ation then it delivers all the messages stored for the dest<strong>in</strong>ation<strong>in</strong> its HOLDMSG queue. When a dest<strong>in</strong>ation node receives a message, eitherfrom the orig<strong>in</strong>al source or from an <strong>in</strong>termediate node, it sends an acknowledgementto the send<strong>in</strong>g node. For each message stored <strong>in</strong> the HOLDMSG queue ofa node, ids of the node that sent the HOLD message to the node and the nodesthat were sent an HOLD message <strong>by</strong> the current node are also kept. When anacknowledgement is received for a message <strong>in</strong> the HOLDMSG queue the nodeforwards the acknowledgement to all such nodes. These forwarded acknowledgementshelp <strong>in</strong> remov<strong>in</strong>g messages that have been successfully delivered to thedest<strong>in</strong>ation from the HOLDMSG queues of other nodes. This potentially preventsa lot of route search messages be<strong>in</strong>g broadcasted <strong>by</strong> all the nodes hold<strong>in</strong>gthe message <strong>in</strong> the HOLDMSG queue. Some of the nodes to which the acknowledgementsare forwarded may be disconnected from the forwarder node. In thatcase the acknowledgement is either dropped or a selection process similar tothe one used for the data messages, is started depend<strong>in</strong>g on how important theacknowledgements are <strong>in</strong> a particular application. A message is removed froma HOLDMSG queue if an acknowledgement for the message is received or themessage has been <strong>in</strong> the HOLDMSG queue for longer than MAX HOLD TIME.3.4 Node Selection MetricWhile select<strong>in</strong>g nodes for replicat<strong>in</strong>g a message, a node picks the one that has thelargest number of neighbours that are not its neighbours. The <strong>in</strong>tuition here is toselect a node that is connected to the most nodes outside the range of the nodecurrently <strong>in</strong>volved <strong>in</strong> selection process and hence can potentially dissem<strong>in</strong>ate themessage farthest <strong>in</strong> the connected graph conta<strong>in</strong><strong>in</strong>g the source.4 Experimental Set UpWe implemented our protocol for the ns2 simulator [14] and have evaluated itsperformance for scenarios <strong>in</strong>volv<strong>in</strong>g upto 120 nodes. The poor performance of ns2<strong>in</strong> simulat<strong>in</strong>g large number of nodes has prevented us from experiment<strong>in</strong>g withscenarios <strong>in</strong>volv<strong>in</strong>g a larger number of nodes. We use the modified Random WayPo<strong>in</strong>t Model described <strong>in</strong> the next subsection of this paper for our experiments.The range of each wireless node is set to 100m. The traffic generator consistsof an application runn<strong>in</strong>g at each node that tries to send a message of 64 <strong>by</strong>tesonce every five seconds to a random node (other than itself). The underly<strong>in</strong>grout<strong>in</strong>g protocol used is AODV. Table 1 shows the values of various parametersof AODV used <strong>in</strong> the simulations.

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

Saved successfully!

Ooh no, something went wrong!