English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Plus annual

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Tools annual

Global: Zendy Free Plan

Global: Zendy Tools monthly

Global: Zendy Plus monthly

An ad hoc network is very popular because of its easy deployment. It is a self-organising network which has dynamic topology. The routing is a major issue in the ad hoc network due to its node mobility. As nodes are moving continuously the source to destination pair is completely broken and repeated route discovery increases delay and network load and reduces throughput of ad hoc network. The routing protocols play a vital role in data transmission and affect the efficiency of the ad hoc network. Also, mobility factor affects the efficiency of the ad hoc network. The ad hoc network is said to be efficient if it transfers data with higher throughput, minimum delay and low overheads. In this paper, researcher studies efficiency of AODV protocol against node mobility. The node mobility term relates to the pause time i.e. the amount of time node is stable at a particular location. The high pause time means nodes in the network have low mobility and low pause time means nodes have high mobility. The performance of AODV protocol is evaluated on the basis of four performance matrices i.e. throughput, delay, routing load, and packet delivery ratio using the Network simulator NS2.34. This study will help the researcher further to regulate the scenario parameters of ad hoc network which will help to improve performance of the protocol.

Analysis of AODV Protocol against Pause Time Using NS2.34