AODV vs DSR vs OLSR vs DSDV: VANET Routing Protocols Performance Comparison
Blog 2026-06-20
AODV vs DSR vs OLSR vs DSDV: VANET Routing Protocols Performance Comparison
Key Overview
Target Audience: Network engineers, automotive embedded systems developers, VANET researchers, and ITS architects.
Core Issue: Which routing protocol performs best in high-speed vehicular networks? Users need concrete performance data, not generic descriptions.
Key Conclusions: AODV excels in high-density urban VANET scenarios; OLSR provides lowest latency for stable highway deployments; DSR suffers from route maintenance overhead; DSDV is unsuitable for high-mobility environments.
Why VANET Routing Is Different from MANET
In traditional Mobile Ad Hoc Networks (MANET), nodes are typically pedestrians with smartphones or static sensors. VANET introduces extreme mobility patterns that break conventional assumptions:
The VANET Routing Challenge
- High speed topology changes: A vehicle traveling at 100 km/h crosses a 300m communication range in just 10.8 seconds
- Predictable mobility: Vehicles follow road constraints (lanes, intersections), unlike random-waypoint models
- Partitioned networks: Rural highways may have sparse vehicle density, causing network fragmentation
- Safety-critical latency: Emergency brake warnings require sub-100ms end-to-end delay
What Happens When You Use Standard MANET Protocols in VANET?
Research Data: Protocol Adaptation Requirements
According to IEEE research papers on VANET protocol performance:
- Standard AODV route expiration timers need reduction by 60-70% for highway VANET
- Hello interval must decrease from 1-10 seconds to 0.5-1 second
- Buffer sizes must increase by 3-5x to handle burst re-transmissions
Protocol Classification: Proactive vs Reactive vs Hybrid
| Category | Route Discovery | Control Overhead | Route Latency | Best For |
|---|---|---|---|---|
| Proactive | Pre-computed | High (periodic updates) | Very Low | High-density urban, frequent communications |
| Reactive | On-demand | Low (only when needed) | High (discovery delay) | Sparse networks, infrequent communications |
| Hybrid | Mixed approach | Moderate | Moderate | Large-scale networks with zones |
Protocols in This Comparison
- AODV (Reactive): Industry standard, widely implemented in research
- DSR (Reactive): Source routing approach, cache-heavy
- OLSR (Proactive): Link-state routing, MPR optimization
- DSDV (Proactive): Distance-vector, sequence-number based
AODV: Ad Hoc On-Demand Distance Vector Routing
How AODV Works in VANET
AODV uses three message types for route management:
• Broadcast ID + Source IP → uniquely identifies each request
• Destination Sequence Number → ensures loop freedom
• Hop Count → limits search radius
RREP (Route Reply) — Unicast back to source:
• Lifetime field → how long this route is valid
• Sequence number → freshness guarantee
RERR (Route Error) — Triggered on link break:
• Unreachable destination list → which routes are broken
• Causes local route repair or discovery restart
Why AODV Works Relatively Well in VANET
- Sequence numbers prevent routing loops — critical for high-speed topology changes
- Local route repair reduces discovery frequency after link breaks
- No source routing overhead — smaller packet headers than DSR
- Widely supported — available in ns-3, OMNeT++, SUMO simulations
AODV VANET Performance Data
| Scenario | Packet Delivery Ratio | End-to-End Delay | Routing Overhead |
|---|---|---|---|
| Urban (30 nodes/km²) | 85-92% | 45-80ms | High (frequent discoveries) |
| Highway (10 nodes/km²) | 70-85% | 120-250ms | Very High (link breaks) |
| Dense Traffic (50 nodes/km²) | 90-95% | 35-60ms | Moderate |
AODV VANET Limitations
- Route discovery latency (200-500ms) violates safety application timing requirements
- Periodic Hello messages consume bandwidth (every 1-2 seconds)
- Symmetric links assumed — fails in anisotropic signal environments
DSR: Dynamic Source Routing
DSR vs AODV: Fundamental Difference
While AODV maintains routing tables at each node, DSR includes the complete route in every packet header:
Route: [Vehicle_A → Vehicle_B → Vehicle_F → Vehicle_K → Destination]
As hops increase, header grows proportionally:
• 3 hops: 24 bytes overhead
• 5 hops: 40 bytes overhead
• 8 hops: 64 bytes overhead (significant for small BSM packets!)
DSR VANET Performance Characteristics
- Advantages:
- Route cache enables faster recovery from link breaks
- No periodic Hello messages needed
- Works well when source-destination pairs communicate frequently
- Disadvantages:
- Header overhead degrades performance at high node density
- Cache staleness in rapidly changing topologies
- Maximum hop limit (typically 8) restricts multi-hop scenarios
DSR VANET Performance Data
| Scenario | Packet Delivery Ratio | End-to-End Delay | Jitter |
|---|---|---|---|
| Urban Low Density | 65-78% | 80-150ms | High variability |
| Urban High Density | 75-85% | 50-100ms | Moderate |
| Highway | 60-72% | 150-300ms | Very High |
OLSR: Optimized Link State Routing
OLSR’s Key Innovation: Multipoint Relays (MPR)
Instead of flooding link-state updates to all neighbors, OLSR uses Multipoint Relays to reduce control overhead:
- Each node selects a subset of neighbors as MPRs
- Only MPRs forward control messages
- MPR set size determines efficiency — typically 20-30% of neighbors
OLSR VANET Performance Characteristics
| Metric | Low Density (10 nodes/km²) | Medium Density (30 nodes/km²) | High Density (50 nodes/km²) |
|---|---|---|---|
| Packet Delivery Ratio | 78-85% | 88-94% | 92-97% |
| End-to-End Delay | 25-40ms | 20-35ms | 15-30ms |
| Control Overhead | Low | Moderate | High |
| Throughput | Good | Excellent | Good (overhead) |
When OLSR Excels in VANET
- Highway platooning: Vehicles maintaining formation have stable local topology
- Urban traffic lights: Stopped vehicles maintain stable links briefly
- Safety applications: Low latency critical for forward collision warnings
OLSR VANET Limitations
- Periodic TC messages (every 2 seconds) consume bandwidth
- MPR selection algorithm adds computational overhead
- Not optimized for highly dynamic topologies
DSDV: Destination-Sequenced Distance Vector
Why DSDV Fails in VANET
DSDV requires periodic full-table broadcasts from every node, which creates:
- Count-to-infinity problem: Network convergence takes seconds in large VANET
- Routing loops: Can occur before sequence numbers propagate
- Excessive overhead: O(N) broadcasts where N = number of nodes
DSDV VANET Performance (For Comparison)
| Metric | DSDV Performance | Acceptable for VANET? |
|---|---|---|
| Packet Delivery Ratio | 40-60% | ❌ No |
| End-to-End Delay | 200-500ms | ❌ No |
| Control Overhead | Extremely High | ❌ No |
Comprehensive Performance Comparison
Decision Matrix: Which Protocol to Choose?
| Your Requirement | Recommended Protocol | Why |
|---|---|---|
| Lowest latency (< 50ms) | OLSR | Pre-computed routes, no discovery delay |
| Highest PDR (> 90%) | AODV | Best balance in urban high-density |
| Low bandwidth overhead | DSR | No periodic Hello messages |
| Highway sparse network | AODV (modified) | Need shorter timers, larger windows |
| Safety-critical (< 100ms) | OLSR | Only protocol meeting latency specs |
| Maximum scalability | OLSR (with MPR) | MPR reduces O(N²) to O(N·logN) |
Simulation Parameters Used in Research
• Mobility: VanetMobility model (realistic car-following)
• Transmission range: 300m (802.11p default)
• MAC: IEEE 802.11p (wifi-phy standard)
• Packet size: 512 bytes (BSM equivalent)
• Transmission rate: 10 Hz (BSM broadcast rate)
• Simulation time: 300 seconds per scenario
• Runs: 10+ with different seeds for statistical significance
Hybrid Approaches: The Future of VANET Routing
Modern VANET research combines protocol strengths:
- ZRP (Zone Routing Protocol): OLSR inside local zones, AODV for inter-zone
- Geographic forwarding: GPS-based position routing reduces topology dependency
- AI/ML-enhanced: Predict vehicle trajectories to pre-compute routes
Frequently Asked Questions
Q: Can I use AODV for safety-critical collision warning applications?
Standard AODV is not suitable for safety applications requiring sub-100ms latency. Research shows AODV route discovery adds 200-500ms delay. For safety applications, use OLSR with pre-computed routes, or implement dedicated short-range protocols like IEEE 802.11p’s contention-free period allocation.
Q: What is the optimal Hello interval for VANET?
For AODV in VANET: Reduce from standard 1-2 seconds to 0.5-1.0 seconds. Some research suggests adaptive Hello intervals based on vehicle speed — faster vehicles send Hello more frequently to detect link breaks sooner.
Q: How many hops can VANET support effectively?
Practical limit is 3-5 hops for safety applications. Each hop adds 5-15ms latency plus processing delay. Beyond 5 hops, PDR drops below 70% in typical urban scenarios, making multi-hop VANET unsuitable for time-critical safety messages.
Q: Which ns-3 module should I use for VANET routing simulation?
Use ns3::VanetRoutingModule with ns3::AodvHelper or ns3::OlsrHelper. The vanilla protocols need modification for VANET parameters. SUMO (Simulation of Urban MObility) generates realistic vehicle traces for ns-3 integration.
▶ Related Cluster Articles:
