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...

Create successful ePaper yourself

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

226 <strong>Wireless</strong> <strong>Ad</strong> <strong>Hoc</strong> <strong>and</strong> <strong>Sensor</strong> <strong>Networks</strong>90Outage probability (%)8070605040302010OptimalBambosSSCDCSOPCNew05 10 15 20 25Time30 35 40 45 50FIGURE 5.32Outage probability.simulation scenario, the number of mobile users trying to gain admissionincreases by 25 from the previous value, <strong>and</strong> the correspondingoutage probability is calculated. Figure 5.33 <strong>and</strong> Figure 5.34 presentthe performance of the DPC in terms of total power consumed <strong>and</strong>outage probability, respectively, when the channel changes slowly. Asexpected, the proposed scheme renders significantly low outage probabilitywhile ensuring low power per active mobile user compared toother schemes.Example 5.4.3: Mobile User ScenarioBecause the users are mobile <strong>and</strong> in the presence of channel uncertainties,Figure 5.35 illustrates the initial location of mobile users, whereasFigure 5.36 presents the final location. Users in the cellular network tryto move in any one of the eight predefined directions chosen at r<strong>and</strong>omat the beginning of the simulation. A user can move a maximum of 0.01km per time unit. Because the time unit is small, the 0.01 km is a considerableamount of distance for any mobile user. Figure 5.37 <strong>and</strong> Figure 5.38display the total power consumed <strong>and</strong> the corresponding outage probability.As evident from the result, the proposed DPC renders a loweroutage probability (average of about 30%) compared to others (about 90%)while consuming low power per active mobile.

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

Saved successfully!

Ooh no, something went wrong!