2. AODV AND OLSR ROUTING PROTOCOLS
Key Terms
Ad hoc Network: Infra Structure less networks
AODV: Ad hoc On Demand Distance Vector
OLSR: Optimized Link State Routing
Wireless Ad hoc is Dynamically forming a temporary
network
3. 1: COMPARING AODV AND OLSR
ROUTING PROTOCOLS
By: Aleksandr Huhtonen (Helsinki University of
Technology)
Abstract
Mobile networks creates underlying architecture for
communication without the help of fixed routers
Hosts have limited transmission range
No fixed router
Each host act as a router
4. PROBLEM
Challenge for mobile protocols is that they also
have to deal with mobility of hosts. Hosts can
appear and disappear in various locations.
5. AD HOC NETWORK ROUTING PROTOCOLS
Ad hoc network routing protocols
Table Driven (Pro-Active): OLSR and Better
Approach To Mobile Ad hoc Networking
(B.A.T.M.A.N)
On Demand (Reactive): AODV, Admission Control
Enabled On Demand Routing (ACOR), Dynamic
Source Routing and Dynamic Man-NET on Demand
Routing
6. QUALITIES TO BE EFFECTIVE
Distributed Operation
Loop freedom
Demand based operation
Proactive operation
Security
Sleep period operation
7. AD HOC ON DEMAND PROTOCOL (AODV)
AODV is a Reactive protocol n Routes are created
when needed
Routing table stores information about next hop
2 destination
Route Discovery
RREQ message with destination IP and Seq. # is
broadcasted
Sequence number prevent looping
RREP from desired destination is unicasted
RREP-ACK optional
RERR in case of route breakage
Route repairing
10. AODV ROUTING TABLE
Destination address
Destination sequence number
Hop count
Next hop
Route state (valid, in valid)
Precursor list
11. ADVANTAGES
Doesn’t need any central administrative system
to handle the routing system
Reduce the control traffic messages
The AODV has great advantage in overhead over
simple protocols.
Using the RRER message AODV reacts relatively
quickly to the topological changes in the network
and updating affected host
AODV is a loop free protocol
12. OPTIMIZED LINK STATE ROUTING (OLSR)
OLSR is a proactive protocol, Routes are always
available
Information of the network
Topological change causes flooding
Control Messages
Hello Messages (one hop count)
Topology Control Messages (TC) topology info.
Multipoint Relays (MPR)
Neighbor Sensing by Hello Messages
MPR Selector Set
MPR can only transmit topology information
13. MPR (MULTI-POINT RELAYS)
The core optimization in OLSR is that of MPR.
It’s used to reduce the message exchange
overhead by reducing the number of hosts that
broadcast messages in a network.
For efficiency MPR is kept low n only MPR can
send throughout messages.
14. ROUTING TABLE CALCULATION
The host maintains the routing table
The routing table entries have following
information:
i. destination address
ii. next address,
iii. number of hops to the destination
iv. local interface address.
The routing table is recalculated if any change
occurs in these sets.
For the routes for routing table entry the
shortest path algorithm is used.
15. ADVANTAGES
OLSR doesn’t need any infrastructure
The proactive protocol provides that the protocol
has all the information to all the participated
hosts.
Flooding is minimized by the MPRs having the
drawback of maximum usage of bandwidth
OLSR is best for the networks using larger
number of nodes.
16. AODV AND OLSR ROUTING PROTOCOLS
FOR WIRELESS AD-HOC AND MESH
NETWORKSANALYSIS & RESULTS
End to end delay
For 100 nodes
For 50 nodes
19. IMPLEMENTATION AND PERFORMANCES OF
AODV AND OLSR
Writers
A. Saika
M.M.Himmi
Abstract
Comparing a reactive and proactive protocol
Network Simulator 2 was used
Concluded that it depends on several constraints
20. EXPERIMENT AND RESULTS
There were 4 nodes, two fixed and two mobile.
Measuring area was set to 500 x 500 m2
Time of simulation was 150 seconds
Protocols used were:
AODV (for reactive)
OLSR (for proactive)
The result of network was a .tr file, used for
creating graphs and charts
23. A COMPARATIVE STUDY OF AODV
AND OLSR ON THE ORBIT TEST BED
ORBIT stands for Open Access Research Test bed
It is an indoor grid based wireless network
emulator consisting of 400 radio nodes.
It is a test bed to conduct network based
experiments under conditions that are similar to
real life conditions.
24. EXPERIMENTAL SETUP
Orbit Traffic Generator(OTG) and Orbit Traffic
Receiver(OTR) was used to generate TCP and
UDP traffic.
20 nodes were created in the experiment. The
input load was gradually increased and
conducted the experiment for 100 s at each
setting to obtain steady.
For each channel rate offered load was increased
until saturation.
25. RESULTS AND CONCLUSION
After saturation OLSR lost stability and showed
large variation in throughput.
At high loads the nodes started competing for
bandwidth ,causing collisions
AODV performed better in terms of stability.
AODV doesn’t allow throughput to increase
beyond saturation.
26. TCP UDP BASED ANALYSIS OF AODV
AND OLSR
Experimental Setup
Network simulations are implemented using NS-2
simulator.
Each node is then assigned a particular trajectory .
The number of nodes which we take in this is of
about 30.
In each simulation scenario, the nodes are initially
located at the center of the simulation.
27. EXPERIMENTAL SETUP
Data rate of 512 Mbps in UDP and of 1024 Mbps
in TCP is used
The nodes start moving after the first 20 seconds.
Constant Bit Rate (CBR) traffic and Internet
Protocol (IP) is used as Network layer protocol.
the number of traffic sources was fixed at 20
maximum speed of the nodes was set to 100m /s
the pause time was varied as 20, 40 ,60, 80 and
100 seconds.
28. RESULTS AND CONCLUSION
The AODV protocol will perform better in the
networks with static traffic.
It uses fewer resources than OLSR.
The AODV protocol can be used in resource
critical environments.
The OLSR protocol is more efficient in networks
with high density and highly sporadic traffic.
29. COMPARISON AND CONCLUSION
AODV performs efficiently in case of low
bandwidth
OLSR requires more band width to send TC
messages in case of topology change
AODV performs better in case of low mobility
In case of high mobility AODV per packet delay
is increased but is more effective in case of
throughput as compared to OLSR.
Scalability is limited in case of large network,
AODV suffers flooding and OLSR table grows
Remarkable to consider to combine both and
have maximum benefit
Notes de l'éditeur
AODV differs from other on-demand routing protocols in that is uses sequence numbers to determine an up-to-date path to a destination. Every entry in the routing table is associated with a sequence number. The sequence number act as a route timestamp, ensuring freshness of the route. Upon receiving a RREQ packet, an intermediate node compares its sequence number with the sequence number in the RREQ packet. If the sequence number already registered is greater than that in the packet, the existing route is more up-to-date.http://www.ietf.org/rfc/rfc3561.txt
The format of the Route Request message is illustrated above, and contains the following fields: Type 1 J Join flag; reserved for multicast. R Repair flag; reserved for multicast. G Gratuitous RREP flag; indicates whether a gratuitous RREP should be unicast to the node specified in the Destination IP Address field D Destination only flag; indicates only the destination may respond to this RREQ (see section 6.5). U Unknown sequence number; indicates the destination sequence number is unknown. Reserved Sent as 0; ignored on reception. Hop Count The number of hops from the Originator IP Address to the node handling the request. Perkins, et. al. Experimental [Page 7] RFC 3561 AODV Routing July 2003 RREQ ID A sequence number uniquely identifying the particular RREQ when taken in conjunction with the originating node's IP address. Destination IP Address The IP address of the destination for which a route is desired. Destination Sequence Number The latest sequence number received in the past by the originator for any route towards the destination. Originator IP Address The IP address of the node which originated the Route Request. Originator Sequence Number The current sequence number to be used in the route entry pointing towards the originator of the route request.
The format of the Route Reply message is illustrated above, and contains the following fields: Type 2 R Repair flag; used for multicast. A Acknowledgment required; see sections 5.4 and 6.7. Reserved Sent as 0; ignored on reception. Perkins, et. al. Experimental [Page 8] RFC 3561 AODV Routing July 2003 Prefix Size If nonzero, the 5-bit Prefix Size specifies that the indicated next hop may be used for any nodes with the same routing prefix (as defined by the Prefix Size) as the requested destination.Hop Count The number of hops from the Originator IP Address to the Destination IP Address. For multicast route requests this indicates the number of hops to the multicast tree member sending the RREP. Destination IP Address The IP address of the destination for which a route is supplied. Destination Sequence Number The destination sequence number associated to the route. Originator IP Address The IP address of the node which originated the RREQ for which the route is supplied.Lifetime The time in milliseconds for which nodes receiving the RREP consider the route to be valid. Note that the Prefix Size allows a subnet router to supply a route for every host in the subnet defined by the routing prefix, which is determined by the IP address of the subnet router and the Prefix Size. In order to make use of this feature, the subnet router has to guarantee reachability to all the hosts sharing the indicated subnet prefix. See section 7 for details. When the prefix size is nonzero, any routing information (and precursor data) MUST be kept with respect to the subnet route, not the individual destination IP address on that subnet. The 'A' bit is used when the link over which the RREP message is sent may be unreliable or unidirectional. When the RREP message contains the 'A' bit set, the receiver of the RREP is expected to return a RREP-ACK message. See section 6.8.