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.

Rout<strong>in</strong>g Update <strong>in</strong> Ad Hoc Networks 279The discovery phase: We use the route discovery phase as described <strong>in</strong> the AODVprotocol for which we add provisions for the availability and density parameters.These two parameters need to be taken <strong>in</strong>to account <strong>in</strong> order for our protocol to provideQoS. Thus, <strong>in</strong> our protocol, the source <strong>in</strong>itiates the rout<strong>in</strong>g process upon receiv<strong>in</strong>ga connection request. Then, it sends a route request for this connection to all itsneighbors. The nodes that receive the message for the first time and that fulfill theQoS requirements propagate the request message towards the dest<strong>in</strong>ation after thefollow<strong>in</strong>g scenario :The request message is gradually propagated towards the dest<strong>in</strong>ation follow<strong>in</strong>g theaforementioned scenario. F<strong>in</strong>ally, when it arrives at its dest<strong>in</strong>ation, the dest<strong>in</strong>ationnode <strong>in</strong>itiates a countdown and records all of the <strong>in</strong>com<strong>in</strong>g request messages.To select a route, we need the parameters conta<strong>in</strong>ed <strong>in</strong> each request message thatarrived at the dest<strong>in</strong>ation. It is important to mention that a route conta<strong>in</strong><strong>in</strong>g long sequencesof high density nodes will be easier to repair with the local route repair procedurethan a route that does not hold that property.4 Implementation and ResultsThe modifications to the AODV protocol were implemented us<strong>in</strong>g Opnet Modeler.The protocol def<strong>in</strong>es four types of packets that can be exchanged between the topologynodes: RERR, REEQ, RREP and DATA.4.1 ExampleHere is a specific example which illustrates the rationale for such modifications to the<strong>in</strong>itial protocol (Figure 1).Fig. 1. Topology used

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

Saved successfully!

Ooh no, something went wrong!