scispace - formally typeset
Search or ask a question

Ad hoc On-Demand Distance Vector (AODV) Routing

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.

Content maybe subject to copyright    Report

Citations
More filters
Journal Article
TL;DR: This paper describes experiences with software model checking after several years of using static analysis to find errors, finding that expectations were often wrong.
Abstract: This paper describes experiences with software model checking after several years of using static analysis to find errors. We initially thought that the trade-off between the two was clear: static analysis was easy but would mainly find shallow bugs, while model checking would require more work but would be strictly better – it would find more errors, the errors would be deeper, and the approach would be more powerful. These expectations were often wrong.

116 citations

Journal ArticleDOI
01 Mar 2005
TL;DR: It is found that simulations have to be complemented to a much higher degree by real-world experiments, that there is a lack of mature implementations and integration and that efforts should be focused on more realistic settings inside the ''ad hoc horizon'' where decent network services still can be provided.
Abstract: After almost a decade of research into ad hoc networking, MANET technology has not yet affected our way of using wireless networks. In this paper we discuss lessons to draw and back them with experiences from our experimental work. We find that simulations have to be complemented to a much higher degree by real-world experiments, that there is a lack of mature implementations and integration and that efforts should be focused on more realistic settings inside the ''ad hoc horizon'' where decent network services still can be provided.

116 citations


Cites background from "Ad hoc On-Demand Distance Vector (A..."

  • ...We find that simulations have to be complemented to a much higher degree by real-world experiments, that there is a lack of mature implementations and integration and that efforts should be focused on more realistic settings inside the ‘‘ad hoc horizon’’ where decent network services still can be…...

    [...]

01 Jan 2007
TL;DR: This paper examines two on demand routing protocols AODV and DSR based on packet delivery ratio, normalized routing load, normalized MAC load, average end to end delay by varying the number of sources, speed and pause time.
Abstract: Summary Ad hoc networks are characterized by multi-hop wireless connectivity, frequently changing network topology and the need for efficient dynamic routing protocols plays an important role. We compare the performance of two prominent on-demand routing protocols for mobile ad hoc networks: Dynamic Source Routing (DSR), Ad Hoc Ondemand distance Vector Routing (AODV). A detailed simulation model with MAC and physical layer models is used to study the interlayer interactions and their performance implications. We demonstrate that even though DSR and AODV share similar on-demand behavior, the differences in the protocol mechanisms can lead to significant performance differentials. In this paper we examine two on demand routing protocols AODV and DSR based on packet delivery ratio, normalized routing load, normalized MAC load, average end to end delay by varying the number of sources, speed and pause time.

115 citations

01 Jan 2002
TL;DR: This paper designs and evaluates a security framework for multi-layer ad-hoc wireless networks with unmanned aerial vehicles (UAVs) and studies the instantiation of these two modes and the transitions between them.
Abstract: Secure communication is critical in military environments where the network infrastructure is vulnerable to various attacks and compromises A conventional centralized solution breaks down when the security servers are destroyed by the enemies In this paper we design and evaluate a security framework for multi-layer ad-hoc wireless networks with unmanned aerial vehicles (UAVs) In battlefields, the framework adapts to the contingent damages on the network infrastructure Depending on the availability of the network infrastructure, our design is composed of two modes In infrastructure mode, security services, specifically the authentication services, are implemented on UAVs that feature low overhead and flexible managements When the UAVs fail or are destroyed, our system seamlessly switches to infrastructureless mode, a backup mechanism that maintains comparable security services among the surviving units In the infrastructureless mode, the security services are localized to each node’s vicinity to comply with the ad-hoc communication mechanism in the scenario We study the instantiation of these two modes and the transitions between them Our implementation and simulation measurements confirm the effectiveness of our design

115 citations

Journal ArticleDOI
TL;DR: A formal operational semantics of the @w-calculus is given in terms of labeled transition systems and it is proved that the state reachability problem is decidable for finite-control @w -processes and that late bisimulation equivalence is a congruence.

114 citations

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

    [...]