12.07.2015 Views

Wireless Ad Hoc and Sensor Networks

Wireless Ad Hoc and Sensor Networks

Wireless Ad Hoc and Sensor Networks

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Optimized Energy <strong>and</strong> Delay-Based Routing 3791210Average contention timesOEDROLSRAODVContention time (milli-seconds)8642020 30 40 50 60 70Mobility (km/hr)80 90 100FIGURE 8.12Contention time <strong>and</strong> mobility.The average packet delay is illustrated in Figure 8.13, which indicatesthat the E2E delays using the OEDR protocol are always smaller than thedelays incurred using the OLSR <strong>and</strong> AODV protocols, owing to the factthat delay information is taken into account in OEDR when calculatingthe routes. Moreover, the average packet delays tend to increase with anincrease in the number of nodes because of higher interferences <strong>and</strong>channel contentions resulting from the density of the nodes <strong>and</strong> theirtraffic.According to Figure 8.14 the throughput/delay values of the OEDRprotocol are higher than those of OLSR <strong>and</strong> AODV protocols, because ofsignificant reduction in the average delays achieved by the OEDR protocol.As the density of the nodes <strong>and</strong> the traffic increases, the throughput/delay ratio decreases as shown in the figure, because of an increase indelays caused by the retransmissions.Energy delay product as a cost function <strong>and</strong> contention times are shownin Figure 8.15 <strong>and</strong> Figure 8.16, respectively. The contention times for theOEDR protocol are almost equal to those of the OLSR protocol <strong>and</strong> thedifferences are negligible (in milliseconds). This indicates that the OEDRprotocol does not result in additional increase in the contention times.The energy <strong>and</strong> delay product values are smaller for the OEDR protocol

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

Saved successfully!

Ooh no, something went wrong!