Drivers Proactive Routing Protocol

DSDV is a proactive routing protocol for mobile ad hoc networks that uses Bellman-Ford distributed routing algorithm and sequence numbers to avoid routing loops. Each node maintains a routing table with destinations, hops, and sequence numbers originating from the destination. Periodic routing updates and immediate updates when changes occur ensure consistency across dynamic topology changes. Sequence numbers distinguish stable from new routes to prevent routing loops.

Uploaded by

Basit Khan

Available Formats

Download as PPT, PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

74 views

Drivers Proactive Routing Protocol

Uploaded by

Basit Khan

Available Formats

Download as PPT, PDF, TXT or read online on Scribd

You are on page 1/ 15

Table-Driven/Proactive

MANET Routing Protocol:

DSDV

Destination Sequenced Distance

Vector (DSDV) Protocol
Why do we need a new
protocol like DSDV?
 Routing protocols for ad hoc networks have to be
designed specifically to provide the kind of dynamic,
self-starting behavior.
 Although mobile computers could naturally be
modeled as routers, existing fixed-network routing
protocols would place too heavy computational
burden on each mobile computer. (“routers” have
only one job to do, where as a mobile node might do
more work)
 The convergence (stability) characteristics of
existing routing protocols did not seem good enough
to fit the needs of ad-hoc networks.
Why DSDV uses a distance
vector?
 DSDV uses (distributed) Bellman-Ford (DBF)
algorithm to find the shortest path from any node to
any other node
 According to DBF, a node knows the length of the
shortest path from each neighbor node to every
network destination and this information is used to
compute the shortest path and next node in the path
to each destination.
 Compared to link-state method (such as using
Dijkstra’s algorithm), it is computationally more
efficient, easier to implement and requires much
less storage space, However, it is well known that
this algorithm can cause the formation of both short-
lived and long-lived loops
But…, there are problems with
looping in distance vector routing
protocols
 The primary cause for formation of routing loops is that nodes
choose their next-hops in a completely distributed fashion based
on information which can possibly be stale and, therefore,
incorrect.
 Almost all proposed modifications to DBF algorithm eliminate the
looping problem by forcing all nodes in the network to participate
in some form of inter-nodal coordination protocol. Such inter-
nodal coordination mechanisms might be effective when
topological changes are rare.
 However, within an ad-hoc mobile environment enforcing any
such inter-nodal coordination mechanism will be difficult due to
the rapidly changing topology of the underlying routing network.
 Simplicity is one of the primary attributes which
makes any routing protocol preferred over others for
implementation within operational networks. RIP
(Routing Information Protocol) is a classical example
of a fixed-network routing protocol.
 Despite the counting-to-infinity problem it, RIP has
proven to be very successful within small size
internetworks.
 The usefulness of RIP within ad-hoc environment,
however, is limited as it was not designed to handle
rapid topological changes.
 The techniques of split-horizon using poison-
reverse are not useful within the wireless
environment due to the broadcast nature of the
transmission medium.
 DSDV design goal therefore is to design a routing
method for ad-hoc networks which preserves the
simplicity of RIP, yet at the same time avoids the
looping problem.
 The approach is to tag each route table entry with a
sequence number so that nodes can quickly
distinguish stale routes from the new ones and thus
avoid formation of routing loops.
 DSDV routing method allows a collection of
mobile computers, which may not be close to
any base station and can exchange data
along changing and arbitrary paths of
interconnection,
 DSDV also remains compatible with
operation in cases where a base station is
available.
Routing table in DSDV
 Packets are transmitted between the stations of the network by
using routing tables which are stored at each station oft he
network.
 Each routing table, at each of the stations, lists all available
destinations, and the number of hops to each.
 Each route table entry is tagged with a sequence number which
is originated by the destination station.
 To maintain the consistency of routing tables in a dynamically
varying topology, each station periodically transmits updates, and
transmits updates immediately when significant new information
is available.
30 sec updating in DV
 Since DSDV does not assume that the
mobile hosts are maintaining any sort of time
synchronization, DSDV makes no
assumption about the phase relationship of
the update periods between the mobile hosts.
These packets indicate which stations are
accessible from each station and the number
of hops necessary to reach these accessible
stations, as is often done in distance-vector
(DV) routing algorithms.
Time before route
convergence
 Routing information is advertised by broadcasting or multicasting
the packets which are transmitted periodically and incrementally
as topological changes are detected – for instance, when
stations move within the network.
 Data is also kept about the length of time between arrival of the
first and the arrival of the best route for each particular
destination. Based on this data, a decision may be made to delay
advertising routes which are about to change soon, thus damping
fluctuations of the route tables. The advertisement of routes
which may not have stabilized yet is delayed in order to reduce
the number of rebroadcasts of possible route entries that
normally arrive with the same sequence number.
The data broadcast by each mobile node will
contain its new sequence number and the
following information for each new host:

 The destination address

 The number of hops required to reach the
destination
 The sequence number of the information received
regarding that destination, as originally stamped
by the destination.
 The transmitted routing table will also contain
the hardware address (MAC) and the network
address of the station transmitting, within the
header of the packet
 The routing table will also contain the
sequence number created by the transmitter
 Routes with the most recent (destination)
sequence numbers are always preferred.
 Of the paths with the same sequence
number, the one with smallest metric will be
used.
 Broken links can be detected through Layer 2
(beacon/infrared) or Ping at Layer 3 if no broadcast
has been received for a while from a neighbour
 A broken link is described by a metric ∞ (i.e any
value greater than the maximum allowed)
 When a link to the next hop has broken, any route
through that next hop is assigned a metric ∞ and a
new sequence number.
 The modified routes are immediately disclosed
through broadcast.
 Building information to describe a broken link is the
only situation when the sequence number is
generated by any mobile host other than the
destination host.
 Sequence numbers for the originating host
(destination) are even numbers (non-broken
links).
 The sequence number generated to indicate
∞ (broken links) are odd numbers.
 In this way, when a node receives an ∞
metric with an odd sequence number that is
bigger than its current even sequence
number with a finite metric, it triggers a route
update broadcast to disseminate/propagate
this important broken link (∞)information.
 At all times, the DSDV protocol guarantee
loop free paths to each destination.