ZRP Zone Radius for Campus

ZRP Zone Radius for Campus

Scenario: University campus deploys 150 IoT sensors for environmental monitoring. Calculate optimal ZRP zone radius based on traffic patterns and topology.

Given:

  • 150 sensor nodes across 5 buildings
  • Building-local traffic: 75% (sensors within same building)
  • Cross-building traffic: 25% (sensors to other buildings)
  • Average node degree: 5 neighbors
  • Typical intra-building path: 2-3 hops
  • Inter-building path: 6-8 hops
  • Data reporting: Every 2 minutes per sensor

Steps:

  1. Calculate zone sizes for different radii:

    • ρ=1: ~5 nodes (direct neighbors only)
    • ρ=2: ~5 + (5 × 4) = 25 nodes (neighbors of neighbors)
    • ρ=3: ~5 + 20 + 60 = 85 nodes (approaching building-wide)
    • ρ=4: ~120 nodes (exceeds single building)
  2. Analyze traffic locality:

    • 75% traffic within building → Want most building covered proactively
    • Average building: 30 sensors
    • Target: ρ covers ≥80% of building sensors
  3. Calculate proactive overhead for each ρ:

    ρ=2 (25 nodes/zone):

    • Proactive updates: Every 15s = 240/hour
    • Per node: 24 routes × 50 bytes = 1,200 bytes
    • Per node hourly: 240 × 1,200 = 288 kB
    • Network: 150 × 288 kB = 43.2 MB/hour

    ρ=3 (85 nodes/zone):

    • Per node: 84 routes × 50 bytes = 4,200 bytes
    • Per node hourly: 240 × 4,200 = 1,008 kB
    • Network: 150 × 1,008 kB = 151.2 MB/hour
  4. Calculate reactive traffic and an upper-bound query cost:

    Assume each radius-two zone contains 25 other sensors from its 30-sensor building; each source therefore has 29 possible same-building destinations. Assume a radius-three zone contains all 29 local peers plus 56 peers in other buildings (85 peers total); each source has 120 possible other-building destinations. For this upper-bound illustration only, assume every packet to an out-of-zone destination needs a fresh query; real routes can be reused, so actual query counts may be lower.

    ρ=2:

    • Intra-building reactive share: 75% × (29 - 25) / 29 = 10.34% of all traffic
    • Inter-building reactive share: 25% of all traffic
    • Total reactive share: 35.34% of traffic
    • Upper-bound fresh queries/hour: 150 sensors × 30 packets/hour × 0.353448 = about 1,591
    • Assumed bordercast cost: about 30 nodes/query × 60 bytes = 1,800 bytes/query
    • Upper-bound reactive overhead: about 1,591 × 1,800 = 2.86 MB/hour

    ρ=3:

    • Intra-building reactive share: 0% (all 29 local peers are in-zone)
    • Inter-building reactive share: 25% × (120 - 56) / 120 = 13.33% of all traffic
    • Upper-bound fresh queries/hour: 150 × 30 × 0.133333 = 600
    • Upper-bound reactive overhead: 600 × 1,800 = 1.08 MB/hour
  5. Compare overhead under those assumptions:

    • ρ=2: 43.2 MB/hour proactive + 2.86 MB/hour reactive = about 46.06 MB/hour; 64.66% of traffic has a proactive route.
    • ρ=3: 151.2 MB/hour proactive + 1.08 MB/hour reactive = 152.28 MB/hour; 86.67% of traffic has a proactive route.
  6. Decision analysis:

    • ρ=2: Lower modeled overhead, with 35.34% of traffic going to out-of-zone destinations.
    • ρ=3: About 3.3× higher modeled overhead, but 22.01 percentage points more traffic stays in-zone.
    • Trade-off: Is about 106 MB/hour of extra modeled overhead worth that additional coverage? Measure route reuse and actual zone membership before deployment.
  7. Cost per avoided fresh query in this upper-bound model:

    • Extra modeled overhead: 152.28 - 46.06293 = 106.21707 MB/hour
    • Upper-bound fresh queries avoided: 1,590.52 - 600 = 990.52/hour
    • Ratio: about 107 kB of extra overhead per avoided modeled query. This ratio is not a measured network cost.

Result: Choose ρ=2 (zone radius = 2 hops)

Rationale:

  • 75% intra-building traffic mostly covered (2-3 hop paths, zone covers 2 hops)
  • Overhead 3.3× lower than ρ=3
  • 35.34% of traffic has out-of-zone destinations under the upper-bound model, acceptable for environmental monitoring (not latency-critical)
  • Building-scale zones align naturally with campus physical topology

Alternative: If latency were critical (fire alarms), choose ρ=3 despite 3× overhead.

Key Insight: Optimal zone radius depends on traffic locality pattern. Match zone size to your network’s natural clusters (buildings, floors, departments). Oversizing zones (ρ → network diameter) degenerates to pure proactive with no hybrid benefit.

Back to the chapter