1 / 16

QoS Constraint Routing Protocols for Mobile Ad Hoc

QoS Constraint Routing Protocols for Mobile Ad Hoc. Igli Tafaj. Introduction. Which is the aim of this paper…? What is MANET? Classification of Multicast Routing Protocol? What is MAODV?. Some QoS Multicast Routing Protocols. QAMNet QMR QMRP AQM. The dynamism of Routing Protocols.

ardice
Download Presentation

QoS Constraint Routing Protocols for Mobile Ad Hoc

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. QoS Constraint Routing Protocols for Mobile Ad Hoc IgliTafaj

  2. Introduction • Which is the aim of this paper…? • What is MANET? • Classification of Multicast Routing Protocol? • What is MAODV?

  3. Some QoS Multicast Routing Protocols • QAMNet • QMR • QMRP • AQM

  4. The dynamism of Routing Protocols TAG REQ_PKT FLAG_FW • Path selection depend on: • Stability of neighbours node • Power level (batery) • Buffer Level (overhead) Each forwarding packet should have a reply, in which could determine the appropriate selected path

  5. MAODV-Extension • Route Discovery • Path Selection • Hop Count • Power Level • Buffer Level • Stability Level • Cost • Class

  6. L2QoS • The selection of path based on QoS metrics • The metrics depends entirely on MAC Sub layer (Layer_2) • On these metrics supported MAODV • MAODV – Extended based on some featuring of Network and Application metrics mixed • Network Metrics depends on maximum hop count metric • Application Metrics depends on cost of some concave and additive metrics like: Bandwidth, Delay etc

  7. Experiment Envirement • Operating System: Linux Red Hat 9.0 • NS2 version: ns-allinone-2.26 • The simulation environment is: • 1) Area: 1500 x 300 meters; • 2) Number of nodes: 60; • 3) Simulation duration: 900 seconds; • 4) Number of repetitions: 4; • 5) Physical/Mac Layer: IEEE 802.11 at 2Mbps, 250 meter transmission range;

  8. Experiment Envirement • 6) Mobility model: random waypoint model with no pause time, and node movement speed 0m/s, 1m/s or 20m/s. • 7) Each sender sends 2 multicast data packets per second with each packet 256 bytes long;

  9. Experiment Envirement • 8) All receivers join a single multicast group at the beginning of the simulation, and the senders start sending data 30 seconds later. After 900 seconds, all senders stop transmitting data; • 9) Only multicast traffic exists in the simulation.

  10. Implementation • Network Layer Metrics: • Power: power=min(path.power, power) • Buffer: path.buffer=hop*path.buffer+buffer/hop+1 • Stability: path.stab=max(path.stab,stab) • Application Layer Metric: • Throughput=total no.of bit*8 (from the Start time-End time)

  11. Simulation Graphs Average end-to-end delay vs speed PDR vs Speed

  12. Simulation Graphs PDR vs Nr of Nodes Average end-to-end delay vs speed

  13. Simulation Graphs Throughput vs Nr of Nodes PDR vs Nr of Nodes

  14. Conclusions • QoS-MAODV, the multicast routing protocol is the extension of MAODV with the QoS support • The network layer metrics is involved in the path discovery to find a QoS path to the destination. • The path with the highest stability is the preferred path. If more than one path is found the destination node selected the path with the highest power level.

  15. Conclusions • Regarding the application requirements, if the application is delay sensitive then the path with the minimum delay is chosen • For the application with throughput constrained the path with maximum bandwidth is selected • With no constraint any path is chosen by the destination.

  16. Conclusions • The protocol balanced the routing load and also minimized the consumption of resources. • As a future work, different number of flows can be analyzed with different network scenarios.

More Related