Ad hoc On-Demand Distance Vector (AODV) Routing
01 Jul 2003-Vol. 3561, pp 1-37
TL;DR: A logging instrument contains a pulsed neutron source and a pair of radiation detectors spaced along the length of the instrument to provide an indication of formation porosity which is substantially independent of the formation salinity.
Abstract: The Ad hoc On-Demand Distance Vector (AODV) routing protocol is intended for use by mobile nodes in an ad hoc network. It offers quick adaptation to dynamic link conditions, low processing and memory overhead, low network utilization, and determines unicast routes to destinations within the ad hoc network. It uses destination sequence numbers to ensure loop freedom at all times (even in the face of anomalous delivery of routing control messages), avoiding problems (such as "counting to infinity") associated with classical distance vector protocols.
Citations
More filters
17 Jul 2006
TL;DR: A multi-hop routing protocol, called MURU that is able to find robust paths in urban VANETs to achieve high end-to-end packet delivery ratio with low overhead and is sufficiently justified through theoretical analysis and the protocol is evaluated with extensive simulations.
Abstract: Vehicular ad hoc networks (VANETs) are going to be an important communication infrastructure in our life. Because of high mobility and frequent link disconnection, it becomes quite challenging to establish a robust multi-hop path that helps packet delivery from the source to the destination. This paper presents a multi-hop routing protocol, called MURU, that is able to find robust paths in urban VANETs to achieve high end-to-end packet delivery ratio with low overhead. MURU tries to minimize the probability of path breakage by exploiting mobility information of each vehicle in VANETs. A new metric called expected disconnection degree (EDD) is used to select the most robust path from the source to the destination. MURU is fully distributed and does not incur much overhead, which makes MURU highly scalable for VANETs. The design is sufficiently justified through theoretical analysis and the protocol is evaluated with extensive simulations. Simulation results demonstrate that MURU significantly outperforms existing ad hoc routing protocols in terms of packet delivery ratio, packet delay and control overhead.
139 citations
Cites background from "Ad hoc On-Demand Distance Vector (A..."
...1) Trajectory-constrained Route Request:Suppose a source node wants to send data packets to a destination node, the shortest trajectory from the source to the destination can be calculated with the roadway geometry plus source and destination’s location as well as mobility information....
[...]
...Based on this observation, every a certain time period, we can find the most robust path from the source to the destination....
[...]
...Existing routing protocols for MANETs (i.e. AODV[14], DSR [8], and GPSR[9]) are inadequate to achieve this goal....
[...]
TL;DR: A detailed overview on the current solutions for medium access control, network, and transport layer protocols is given and open research issues are discussed in this article, where architectures for two-dimensional and three-dimensional underwater sensor networks are proposed.
Abstract: Underwater networks of sensors have the potential to enable unexplored applications and to enhance our ability to observe and predict the ocean. In this paper, architectures for two-dimensional and three-dimensional underwater sensor networks are proposed. A detailed overview on the current solutions for medium access control, network, and transport layer protocols is given and open research issues are discussed.
139 citations
Cites background from "Ad hoc On-Demand Distance Vector (A..."
...Reactive protocols (e.g., AODV [ 18 ], DSR [11]) are more appropriate for dynamic environments but incur a higher latency and still require source-initiated flooding of control packets to establish paths....
[...]
Journal Article•
TL;DR: This paper gives an overview of Vehicular ad hoc networks (VANETs) and the existing VANET routing protocols; mainly it focused on vehicle to vehicle (V2V) communication and protocols.
Abstract: In recent years, the aspect of vehicular ad hoc network (VANET) is becoming an interesting research area; VANET is a mobile ad hoc network considered as a special case of mobile ad hoc network (MANET). Similar to MANET, VANET is characterized as autonomous and self-configured wireless network. However, VANET has very dynamic topology, large and variable network size, and constrained mobility; these characteristics led to the need for efficient routing and resource saving VANET protocols, to fit with different VANET environments. These differences render traditional MANET's protocols unsuitable for VANET. The aim of this work is to give a survey of the VANETs routing mechanisms, this paper gives an overview of Vehicular ad hoc networks (VANETs) and the existing VANET routing protocols; mainly it focused on vehicle to vehicle (V2V) communication and protocols. The paper also represents the general outlines and goals of VANETs, investigates different routing schemes that have been developed for VANETs, as well as providing classifications of VANET routing protocols (focusing on two classification forms), and gives summarized comparisons between different classes in the context of their methodologies used, strengths, and limitations of each class scheme compared to other classes. Finally, it extracts the current trends and the challenges for efficient routing mechanisms in VANETs.
139 citations
Cites background from "Ad hoc On-Demand Distance Vector (A..."
...So AODV is flexible to highly dynamic network topology and large-scale network [20]....
[...]
01 Jul 2003
TL;DR: The current state of AODV is described, including its base functionality as well as optional features that improve performance and add capabilities, and some direction for the continued evolution is offered by presenting areas that can be targeted for future enhancements.
Abstract: The ad hoc on-demand distance-vector (AODV) routing protocol has been designed for use in ad hoc networks, which are presently receiving wide interest within many diverse research communities. These networks represent a significant departure from traditional wired networks due to the distinguishing characteristics of both the wireless channel and mobile devices. Consequently, AODV incorporates many novel features for handling mobility, reduced capacity links, and the variable, indeterminate nature of the signaling range of wireless media. Since its initial design, AODV has evolved in a number of ways for improved performance, robustness, and better scalability. Nevertheless, we see many opportunities for continued improvement. This paper describes the current state of AODV, including its base functionality as well as optional features that improve performance and add capabilities. We also offer some direction for the continued evolution of AODV by presenting areas that can be targeted for future enhancements. Many of the described current and planned features are a result of AODVs history and evolution within the Internet engineering task force. � 2003 Elsevier B.V. All rights reserved.
139 citations
TL;DR: A discussion of the main aspects of RPL and the advantages and disadvantages of using it in different IoT applications, and a comparison of related RPL-based protocols in terms of energy efficiency, reliability, flexibility, robustness, and security.
Abstract: In the last few years, the Internet of Things (IoT) has proved to be an interesting and promising paradigm that aims to contribute to countless applications by connecting more physical “things” to the Internet. Although it emerged as a major enabler for many next-generation applications, it also introduced new challenges to already saturated networks. The IoT is already coming to life especially in healthcare and smart environment applications adding a large number of low-powered sensors and actuators to improve lifestyle and introduce new services to the community. The Internet Engineering Task Force (IETF) developed RPL as the routing protocol for low-power and lossy networks (LLNs) and standardized it in RFC6550 in 2012. RPL quickly gained interest, and many research papers were introduced to evaluate and improve its performance in different applications. In this paper, we present a discussion of the main aspects of RPL and the advantages and disadvantages of using it in different IoT applications. We also review the available research related to RPL in a systematic manner based on the enhancement area and the service type. In addition to that, we compare related RPL-based protocols in terms of energy efficiency, reliability, flexibility, robustness, and security. Finally, we present our conclusions and discuss the possible future directions of RPL and its applicability in the Internet of the future.
138 citations
Cites methods from "Ad hoc On-Demand Distance Vector (A..."
...In an outdoor practical test using three mobile nodes and one collection node, the PDR is similar to that of AODV with less packet overhead....
[...]
...However, RPL already covers these methods and while DMR outperforms the ad-hoc on-demand distance vector (AODV) [60] and the ad-hoc on demand multipath distance vector(AOMDV) [61] protocols which were not designed for LLNs and it wasn’t compared to native RPL....
[...]
...According to the simulation results, this protocol achieves similar PDR when compared to the native RPL and to the AODV, it has less packet overhead than AODV but slightly more than the native RPL....
[...]
References
More filters
01 Mar 1997
TL;DR: This document defines these words as they should be interpreted in IETF documents as well as providing guidelines for authors to incorporate this phrase near the beginning of their document.
Abstract: In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. Authors who follow these guidelines should incorporate this phrase near the beginning of their document:
3,501 citations
12 Nov 2001
TL;DR: In this article, a logging instrument contains a pulsed neutron source and a pair of radiation detectors spaced along the length of the instrument to provide an indication of formation porosity which is substantially independent of the formation salinity.
Abstract: A logging instrument contains a pulsed neutron source and a pair of radiation detectors spaced along the length of the instrument. The radiation detectors are gated differently from each other to provide an indication of formation porosity which is substantially independent of the formation salinity. In the preferred embodiment, the electrical signals indicative of radiation detected by the long-spaced detector are gated for almost the entire interval between neutron pulses and the short-spaced signals are gated for a significantly smaller time interval which commences soon after the termination of a given neutron burst. The signals from the two detectors are combined in a ratio circuit for determination of porosity.
574 citations
01 Jan 1998
TL;DR: In this article, the authors discuss issues that should be considered in formulating a policy for assigning values to a name space and provide guidelines to document authors on the specific text that must be included in documents that place demands on the IANA.
Abstract: Many protocols make use of identifiers consisting of constants and other well-known values. Even after a protocol has been defined and deployment has begun, new values may need to be assigned (e.g., for a new option type in DHCP, or a new encryption or authentication algorithm for IPSec). To insure that such quantities have consistent values and interpretations in different implementations, their assignment must be administered by a central authority. For IETF protocols, that role is provided by the Internet Assigned Numbers Authority (IANA). In order for the IANA to manage a given name space prudently, it needs guidelines describing the conditions under which new values can be assigned. If the IANA is expected to play a role in the management of a name space, the IANA must be given clear and concise instructions describing that role. This document discusses issues that should be considered in formulating a policy for assigning values to a name space and provides guidelines to document authors on the specific text that must be included in documents that place demands on the IANA.
536 citations
01 Oct 1998
TL;DR: Many protocols make use of identifiers consisting of constants and other well-known values that must be administered by a central authority to insure that such quantities have consistent values and interpretations in different implementations.
Abstract: Many protocols make use of identifiers consisting of constants and other well-known values. Even after a protocol has been defined and deployment has begun, new values may need to be assigned (e.g., for a new option type in DHCP, or a new encryption or authentication algorithm for IPSec). To insure that such quantities have consistent values and interpretations in different implementations, their assignment must be administered by a central authority. For IETF protocols, that role is provided by the Internet Assigned Numbers Authority (IANA).
334 citations
01 Jun 2004
TL;DR: This document defines terms for mobility related terminology out of work done in the Seamoby Working Group but has broader applicability for terminology used in IETF-wide discourse on technology for mobility and IP networks.
Abstract: There is a need for common definitions of terminology in the work to
be done around IP mobility. This document defines terms for mobility
related terminology. The document originated out of work done in the
Seamoby Working Group but has broader applicability for terminology
used in IETF-wide discourse on technology for mobility and IP
networks. Other working groups dealing with mobility may want to take
advantage of this terminology. This memo provides information for the
Internet community.
207 citations
"Ad hoc On-Demand Distance Vector (A..." refers methods in this paper
...This section defines other terminology used with AODV that is not already defined in [3]....
[...]