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.

SAFAR: An Adaptive Bandwidth-Efficient Rout<strong>in</strong>g Protocol 17Choice of fitness function: The ratioF(fitness), rema<strong>in</strong>s fairly constantthroughout the table buildup procedure.Hence, it makes for a stable fitnessfunction. The node is likely toquery half the nodes if its bandwidthmatches the average.Query<strong>in</strong>g Fit nodesThis <strong>in</strong>volves query<strong>in</strong>g the selectednodes once the fitness function hasbeen applied. In Fig. 2, Node Aqueries nodes B and C with a sendFig. 2. Node A, relay<strong>in</strong>g a send-table messageto nodes B,C and Etable message. This message is a request to these nodes to return their neighborlists back to the source node A. B and C are added to the proactive list(theproactive field <strong>in</strong> the rout<strong>in</strong>g table is set to true). As illustrated <strong>in</strong> Fig. 2, nodesB, C and E, on receiv<strong>in</strong>g a send table message from node A, generate a transfertable packet which reports address and bandwidth <strong>in</strong>formation of its neighbors(I,J,K,L,M,G,H respectively) back to A. It also adds A to its update list (i.e. theupdate field <strong>in</strong> the rout<strong>in</strong>g table is set to true). This list is expla<strong>in</strong>ed <strong>in</strong> section4.4. Node A, on receiv<strong>in</strong>g a table transfer message, updates its rout<strong>in</strong>g tableand its heap with the newly found nodes (I, J, K, L, M, G and H).These nodeswill be considered <strong>in</strong> the next iteration of fitness function application along withthe rejected nodes from the previous query (D). The node A calculates averagebandwidth aga<strong>in</strong> us<strong>in</strong>g new data <strong>in</strong> its rout<strong>in</strong>g table and recalculates number ofnodes to query. As shown <strong>in</strong> Fig. 3, nodes J and M are selected.It has to be noted that the Mnodes can be chosen from any hopon the basis of maximum bandwidthvalue. Thus the radius of the activeneighborhood is not ma<strong>in</strong>ta<strong>in</strong>ed uniformly.The procedure of query<strong>in</strong>g fitnodes is applied aga<strong>in</strong> on J and M(Fig. 3). At this stage the numberof nodes to query becomes zero andhence the table build-up procedureends.4.4 Rout<strong>in</strong>gFig. 3. Formation of the proactive zoneWhen a node requires a route to the dest<strong>in</strong>ation (say X), it starts a route discoveryprocedure, which follows a two-stage mechanism as given below.Type-1 messag<strong>in</strong>gThe node, <strong>in</strong> need of the route, sends a type-1 message to everyone <strong>in</strong> its proactivelist. If anyone of these queried nodes has a path to the dest<strong>in</strong>ation,it respondswith a Type-1 reply packet. This packet also reports the maximum cost(lowest

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

Saved successfully!

Ooh no, something went wrong!