46  Fresnel Zones & Deployment

Key Concepts
  • Fresnel Zone: An ellipsoidal region around the direct line-of-sight path between two antennas; radio waves diffract within this zone and interference with obstacles reduces signal strength
  • First Fresnel Zone: The most critical zone; at least 60% of its cross-section must be clear of obstacles to avoid significant signal attenuation
  • Fresnel Zone Radius: The radius at the midpoint of the path, calculated as r₁ = √(λd/4) for a symmetric path of length d
  • Line of Sight (LOS): An unobstructed straight-line path between transmitter and receiver; Fresnel zone clearance is required even when LOS exists
  • Earth Bulge: The curvature of the Earth that obstructs long-distance line-of-sight paths; must be accounted for in links over 10 km
  • Knife-Edge Diffraction: A simplified model for signal diffraction around a sharp obstacle, used to estimate attenuation from partial Fresnel zone obstruction
  • Fresnel Clearance: The minimum required distance between the first Fresnel zone boundary and any obstacle; typically 0.6 × r₁

46.1 In 60 Seconds

Wireless signals do not travel in a thin beam – they occupy a 3D ellipsoid volume called the Fresnel zone around the line-of-sight path. For reliable outdoor IoT links (LoRaWAN, Sigfox, point-to-point Wi-Fi), at least 60% of the first Fresnel zone must be clear of obstructions. This zone grows with distance and shrinks with frequency, directly determining required antenna heights and explaining why ground-mounted sensors lose range.

46.2 Learning Objectives

By the end of this chapter, you will be able to:

  • Explain Fresnel zone requirements for reliable outdoor deployments
  • Calculate first Fresnel zone radius for different frequencies and distances
  • Apply the 60% clearance rule for reliable wireless links
  • Design antenna heights for long-range deployments
  • Troubleshoot ground-mounted sensor range issues
  • Evaluate practical IoT deployments considering terrain and buildings

When a wireless signal travels between two antennas, it does not just go in a straight line – it spreads out in an invisible football-shaped zone called a Fresnel zone. If trees, buildings, or hills poke into this zone, the signal gets weaker. Understanding Fresnel zones helps you position antennas so IoT devices can communicate reliably over long distances.

“My radio signal goes in a straight line to the gateway, right?” asked Sammy the Sensor. Max the Microcontroller shook his head. “Not exactly! Your signal actually spreads out in a big invisible football shape between you and the gateway. That shape is called the Fresnel zone.”

“A football shape?!” Lila the LED exclaimed. “So if a tree or a building pokes into that invisible football, my signal gets weaker?” Max nodded. “Exactly! You need at least 60% of that football zone to be clear of obstacles. That is why putting sensors on the ground is a bad idea – the Earth itself blocks the Fresnel zone!”

“Think of it like rolling a ball across a field,” said Bella the Battery. “If there are no bumps, it rolls smoothly. But if a hill sticks up in the middle, the ball gets deflected. For IoT antennas, the solution is simple – mount them higher up! The higher the antenna, the more of the Fresnel zone stays clear.”

“So when planning a LoRa network across a farm,” Sammy concluded, “we cannot just check that we can SEE the gateway. We need to make sure the whole invisible football between us is mostly clear of trees, hills, and buildings. That is why antenna height matters so much!”

46.3 Introduction

While path loss calculations assume a direct line-of-sight path between transmitter and receiver, wireless signals actually occupy a three-dimensional ellipsoid volume around this path called the Fresnel Zone. Understanding Fresnel zones is critical for outdoor IoT deployments, especially long-range links like LoRaWAN, Sigfox, and point-to-point Wi-Fi.

Time: ~25 min | Difficulty: Intermediate | P07.C15.U05d

46.4 What Are Fresnel Zones?

Fresnel zones are concentric ellipsoid regions around the direct line-of-sight path. Radio waves traveling through these zones can constructively or destructively interfere at the receiver depending on their path length.

Diagram showing Fresnel zone ellipsoid between transmitter and receiver with concentric zones, illustrating the first Fresnel zone which must be 60 percent clear for reliable links, the second Fresnel zone, the direct line-of-sight path, and ground obstacles, along with clearance rules for reliable, marginal, and failed links
Figure 46.1: Fresnel zone ellipsoid showing clearance requirements for reliable wireless links

46.5 First Fresnel Zone Radius Formula

The radius of the first Fresnel zone at the midpoint between transmitter and receiver is:

\[r_1 = 17.3 \sqrt{\frac{d}{4f}}\]

Where:

  • r_1 = First Fresnel zone radius (meters)
  • d = Total distance between TX and RX (kilometers)
  • f = Frequency (GHz)

Alternative Formula (for any point along the path):

\[r_1 = \sqrt{\frac{\lambda \, d_1 \, d_2}{d_1 + d_2}}\]

Where:

  • lambda = Wavelength (meters) = c/f
  • d_1 = Distance from TX to obstacle (meters)
  • d_2 = Distance from obstacle to RX (meters)

60% Clearance Rule:

For reliable wireless links, at least 60% of the first Fresnel zone radius must be clear of obstacles. This accounts for ground reflections, diffraction, and multipath interference.

\[r_{clearance} = 0.6 \times r_1\]

Try It: Fresnel Zone Calculator

46.6 Worked Example: Wi-Fi 2.4 GHz Fresnel Zone

Scenario: Point-to-point Wi-Fi link between two buildings 100 meters apart at 2.4 GHz. What antenna height is required?

Given:

  • Distance: d = 100 m = 0.1 km
  • Frequency: f = 2.4 GHz
  • 60% clearance required

Step 1: Calculate first Fresnel zone radius at midpoint

\[r_1 = 17.3 \sqrt{\frac{0.1}{4 \times 2.4}}\] \[r_1 = 17.3 \sqrt{\frac{0.1}{9.6}}\] \[r_1 = 17.3 \sqrt{0.01042}\] \[r_1 = 17.3 \times 0.1021\] \[r_1 = 1.77 \text{ meters}\]

Step 2: Calculate required clearance (60% rule)

\[r_{clearance} = 0.6 \times 1.77 = 1.06 \text{ meters}\]

Step 3: Determine minimum antenna height

If antennas are mounted at same height h, the midpoint sag due to Earth’s curvature (negligible at 100m) and required clearance:

\[h_{min} = r_{clearance} + h_{obstacle}\]

For ground-level obstacles (h_obstacle = 0):

\[h_{min} = 1.06 \text{ meters}\]

Practical antenna height: 2-3 meters (provides 60% Fresnel clearance plus margin for ground reflections).

What if antennas are ground-mounted (h = 0.5m)?

At 100m distance with 0.5m antenna height, the Fresnel zone would be partially blocked by ground, causing:

  • 6-10 dB additional loss from ground reflection/diffraction
  • Reduced effective range from 100m to ~40-60m
  • This explains why ground-mounted sensors have poor range!

46.7 Worked Example: LoRa 915 MHz Long-Range Link

Scenario: LoRaWAN gateway to sensor link across 5 km farmland at 915 MHz. How high should the gateway antenna be?

Given:

  • Distance: d = 5 km
  • Frequency: f = 915 MHz = 0.915 GHz
  • Flat farmland with crops up to 2 meters tall

Step 1: Calculate first Fresnel zone radius at midpoint (2.5 km from each end)

\[r_1 = 17.3 \sqrt{\frac{5}{4 \times 0.915}}\] \[r_1 = 17.3 \sqrt{\frac{5}{3.66}}\] \[r_1 = 17.3 \sqrt{1.366}\] \[r_1 = 17.3 \times 1.169\] \[r_1 = 20.22 \text{ meters}\]

Step 2: Calculate required clearance (60% rule)

\[r_{clearance} = 0.6 \times 20.22 = 12.13 \text{ meters}\]

Step 3: Account for crop height + clearance

\[h_{min} = h_{crop} + r_{clearance} = 2 + 12.13 = 14.13 \text{ meters}\]

Practical deployment:

  • Gateway antenna height: 15 meters (pole-mounted on rooftop)
  • Sensor antenna height: 3 meters (above crop level)
  • Result: Clear first Fresnel zone, reliable 5 km link

What if gateway is only 3m high (same as sensor)?

Fresnel zone radius at midpoint: 20.22 m
Gateway height: 3 m
Crop height: 2 m
Clearance above crops: 3 - 2 = 1 m

Percentage of Fresnel zone clear: 1 / 20.22 = 4.9% (far below 60% requirement)

Expected loss: 15-20 dB additional diffraction loss
Link budget impact: May exceed -137 dBm sensitivity, causing link failure!

This is why LoRa gateways are mounted on towers/rooftops, not ground level!

How much does proper Fresnel zone clearance affect deployment costs and reliability? Let’s quantify the cost-benefit tradeoff.

Scenario: 1,000-sensor farm LoRaWAN deployment, 5 km max distance, 915 MHz.

Fresnel zone requirement at 5 km: \(r_1 = 17.3\sqrt{\frac{5}{4 \times 0.915}} = 20.2\text{ m}\) \(\text{60\% clearance} = 0.6 \times 20.2 = 12.1\text{ m}\)

Option A: Ground-level gateway (3 m antenna height)

  • Fresnel clearance above 2 m crops: \(\frac{3 - 2}{20.2} = 5.0\%\) (far below 60% requirement)
  • Diffraction loss: ~18 dB
  • Link budget impact: Reduces 5 km range to ~800 m \(\text{Required gateways} = \frac{\pi (5{,}000)^2}{\pi (800)^2} = \frac{25{,}000{,}000}{640{,}000} \approx 39\text{ gateways}\) \(\text{Cost} = 39 \times \$1{,}500 = \$58{,}500\)

Option B: Tower-mounted gateway (15 m antenna height)

  • Fresnel clearance above 2 m crops: \(\frac{15 - 2}{20.2} = 64.4\%\) (above 60% threshold!)
  • Diffraction loss: ~2 dB
  • Full 5 km range achieved \(\text{Required gateways} = 4\text{ gateways (with overlap)}\) \(\text{Gateway cost} = 4 \times \$1{,}500 = \$6{,}000\) \(\text{Tower installation} = 4 \times \$3{,}000 = \$12{,}000\) \(\text{Total cost} = \$18{,}000\)

Savings: \(\text{Cost reduction} = \frac{\$58{,}500 - \$18{,}000}{\$58{,}500} \times 100\% = 69\%\text{ cheaper}\)

Additional benefits:

  • Maintenance: 4 sites vs 39 sites (90% reduction in site visits)
  • Backhaul: 4 cellular connections vs 39 (88% lower monthly cost)
  • Reliability: 64% Fresnel clearance vs 5% (orders of magnitude better uptime)

Key insight: Proper antenna height (achieving 60%+ Fresnel clearance) reduces gateway count by 10x, cutting deployment costs by 69% despite tower installation. The Fresnel zone formula is not just physics – it is a deployment cost model. Every meter of antenna height below the required 15 m adds exponentially more gateways to compensate for diffraction loss.

46.8 Fresnel Zone Clearance by Protocol

Different IoT protocols operating at different frequencies have vastly different Fresnel zone requirements:

46.8.1 Fresnel Zone Radius at 1 km Distance

Protocol Frequency Fresnel Radius (r_1) 60% Clearance Height Requirement
Sigfox 868 MHz 9.3 m 5.6 m 6-8 m minimum
LoRa US 915 MHz 9.0 m 5.4 m 6-8 m minimum
Wi-Fi 2.4 GHz 2.4 GHz 5.6 m 3.4 m 4-5 m minimum
Wi-Fi 5 GHz 5 GHz 3.9 m 2.3 m 3-4 m minimum
BLE 2.4 GHz 5.6 m 3.4 m 4-5 m minimum

46.8.2 Fresnel Zone Radius at 5 km Distance

Protocol Frequency Fresnel Radius (r_1) 60% Clearance Height Requirement
Sigfox 868 MHz 20.8 m 12.5 m 13-15 m minimum
LoRa US 915 MHz 20.2 m 12.1 m 13-15 m minimum
LoRa EU 868 MHz 20.8 m 12.5 m 13-15 m minimum
Wi-Fi 2.4 GHz 2.4 GHz 12.5 m 7.5 m 8-10 m minimum
NB-IoT 900 MHz 20.4 m 12.2 m 13-15 m minimum

Key Observations:

  1. Lower frequency = larger Fresnel zone: LoRa/Sigfox at 900 MHz have ~2x larger Fresnel zones than Wi-Fi at 2.4 GHz
  2. Longer distance = larger Fresnel zone: At 5 km, Fresnel zones are ~2.2x larger than at 1 km (sqrt(5) scaling)
  3. Height requirements scale with distance: 1 km link needs 6m height, 5 km link needs 13-15m height for the same protocol

46.9 Building Penetration and Fresnel Zones

Fresnel zone analysis also explains why lower frequencies penetrate buildings better than higher frequencies:

Building Penetration Loss at 60% Fresnel Blockage:

Material 900 MHz LoRa 2.4 GHz Wi-Fi 5 GHz Wi-Fi Explanation
Drywall 2 dB 3-5 dB 5-8 dB Higher freq = more diffraction loss
Brick wall 4-6 dB 6-10 dB 10-15 dB Wavelength vs brick size
Concrete 6-8 dB 10-15 dB 15-25 dB Absorption scales with frequency
Metal mesh 15-20 dB 20-30 dB 30-50 dB Aperture size vs wavelength

Why LoRa Penetrates Better Than Wi-Fi:

At 915 MHz LoRa:

  • Wavelength: lambda = c/f = 3x10^8 / 915x10^6 = 0.328 m = 32.8 cm
  • Typical wall thickness: 10-20 cm ~ 0.3-0.6 lambda
  • Diffraction around obstacles is effective when obstacle size is comparable to the wavelength

At 2.4 GHz Wi-Fi:

  • Wavelength: lambda = 3x10^8 / 2.4x10^9 = 0.125 m = 12.5 cm
  • Typical wall thickness: 10-20 cm ~ 0.8-1.6 lambda
  • Less effective diffraction when obstacle size exceeds the wavelength

Result: LoRa experiences ~40% less building penetration loss than Wi-Fi due to longer wavelength allowing better diffraction around obstacles.

46.10 Ground-Mounted Sensors: Why Range is Poor

Real-World Problem: Smart agriculture soil moisture sensors placed at ground level (10-20 cm height) consistently fail to reach gateways at 1-2 km distance, despite theoretical range calculations showing 5-10 km capability.

Root Cause: Fresnel Zone Blockage

Comparison diagram showing ground-mounted sensor at 0.2 m height with over 95 percent Fresnel zone blockage causing 15 to 25 dB loss and only 200 to 500 m range, versus elevated sensor at 3 m height with clear Fresnel zone achieving 0 to 3 dB loss and 5 to 10 km range, demonstrating the critical importance of sensor height for long-range wireless links
Figure 46.2: Ground-mounted vs elevated sensor showing Fresnel zone blockage impact on range

Numerical Analysis (LoRa 915 MHz, 1 km link):

Ground-mounted sensor (h = 0.2m):

Fresnel zone radius at midpoint: r_1 = 9.0 m
Sensor height: 0.2 m
Ground clearance: 0.2 / 9.0 = 2.2% (far below 60% requirement!)

Diffraction loss from Fresnel blockage: ~18 dB
Ground reflection loss: ~5 dB
Total extra loss: 23 dB

Link budget impact:
Original margin: +25 dB
After ground loss: 25 - 23 = +2 dB (marginal link, unreliable)

Elevated sensor (h = 3m):

Fresnel zone radius at midpoint: r_1 = 9.0 m
Sensor height: 3 m
Ground clearance: 3 / 9.0 = 33.3% (still below 60%, but much better)

Diffraction loss: ~6 dB
Ground reflection loss: ~2 dB
Total extra loss: 8 dB

Link budget impact:
Original margin: +25 dB
After losses: 25 - 8 = +17 dB (excellent, reliable link)

Design Guideline: For long-range LoRa/Sigfox sensors, mount antennas at minimum 2-3 meters height, even for ground-level sensing applications (use cables to connect sensors at ground to antenna on pole).

Try It: Ground vs Elevated Sensor Comparison

46.11 Practical Deployment Examples

46.11.1 Example 1: Smart Agriculture (5 km LoRaWAN)

Problem: Soil sensors at ground level cannot reach gateway 5 km away.

Solution:

  • Move sensors to 3m poles with antenna at top
  • Use waterproof cables to connect ground-level soil probes to elevated transceivers
  • Result: Achieve improved Fresnel clearance, maintain 5 km range

Cost Impact:

  • 3m pole per sensor: $50
  • Labor for pole installation: $100
  • Total per sensor: $150
  • ROI: Reliable connectivity vs sensor failures requiring gateway densification ($5,000+ per gateway)

46.11.2 Example 2: Point-to-Point Wi-Fi Bridge (500m between buildings)

Problem: Direct line-of-sight between buildings, but connection is unstable.

Root cause analysis:

Distance: 500 m
Frequency: 2.4 GHz
Fresnel radius at midpoint: r_1 = 17.3 sqrt(0.5 / (4 x 2.4)) = 3.9 m
60% clearance: 2.4 m

Building A antenna: 3m above roof (20m total height)
Building B antenna: 3m above roof (22m total height)
Midpoint height: (20 + 22) / 2 = 21 m

Trees in path: 18m tall
Clearance: 21 - 18 = 3m (3/3.9 = 77% Fresnel clearance -> acceptable)

But the connection was still unstable – further investigation revealed seasonal foliage growth added 2-3m to tree canopy height in summer:

Summer tree height: 20m (with foliage)
Clearance: 21 - 20 = 1m (1/3.9 = 26% Fresnel clearance -> poor!)

Solution:

  • Raise Building A antenna to 5m above roof (22m total)
  • Midpoint height: (22 + 22) / 2 = 22 m
  • Summer clearance: 22 - 20 = 2m (2/3.9 = 51% Fresnel clearance)
  • Add 10 dB fade margin for seasonal variation
  • Result: Stable year-round link

46.11.3 Example 3: Urban NB-IoT Deployment

Problem: NB-IoT smart parking sensors (ground-level) have poor coverage.

Analysis:

NB-IoT frequency: 900 MHz (LTE Band 8)
Distance to cell tower: 2 km
Fresnel radius: r_1 = 17.3 sqrt(2 / (4 x 0.9)) = 12.9 m

Sensor height: 0.1 m (embedded in pavement)
Ground clearance: 0.1 / 12.9 = 0.8% (far below 60%)

Buildings, cars, and urban clutter block Fresnel zone
Additional loss: 20-30 dB

Why NB-IoT still works despite blockage:

  1. High transmit power: 23 dBm (200 mW) vs LoRa 14 dBm (25 mW) = +9 dB advantage
  2. Excellent receiver sensitivity: -140 dBm vs LoRa -137 dBm = +3 dB advantage
  3. Total extra margin: 12 dB compensates for some (but not all) Fresnel blockage
  4. Multipath propagation: Urban reflections provide alternative signal paths (not available in rural areas)

Result: NB-IoT works for ground-level urban sensors, but LoRa would fail in same conditions without elevation.

46.12 Advanced Worked Examples

Worked Example: Multi-Floor Building Wi-Fi Coverage Planning

Scenario: A 5-story office building (each floor 40m x 30m) needs Wi-Fi coverage for 200 IoT devices per floor. Building has concrete floors (15 dB attenuation) and drywall partitions (4 dB each). Determine access point placement.

Given:

  • Floor dimensions: 40m x 30m = 1,200 sq m per floor
  • Concrete floor attenuation: 15 dB per floor
  • Drywall partition attenuation: 4 dB
  • Wi-Fi 2.4 GHz AP specifications:
    • TX power: 20 dBm
    • Receiver sensitivity: -90 dBm
    • Antenna gain: 3 dBi (omnidirectional)
  • Minimum required signal: -75 dBm for reliable IoT operation

Steps:

  1. Calculate available link budget:
    • TX EIRP: 20 + 3 = 23 dBm
    • Required received: -75 dBm
    • Maximum allowable path loss: 23 - (-75) = 98 dB
  2. Calculate single-floor horizontal coverage:
    • Path loss at 20m (indoor office, n=3.0):
    • FSPL at 20m, 2.4 GHz: 20 log(20) + 20 log(2400) + 32.45 = 66 dB
    • Environmental excess (n=3 vs n=2): 10(1.0) log(20) = 13 dB
    • Total at 20m: 66 + 13 = 79 dB
    • Add 2 partitions: 79 + 8 = 87 dB
    • Margin at 20m: 98 - 87 = 11 dB (acceptable)
  3. Test vertical coverage (floor-to-floor):
    • Horizontal distance: 10m (directly above/below)
    • Path loss at 10m: 60 + 10 = 70 dB
    • Add concrete floor: 70 + 15 = 85 dB
    • Received power: 23 - 85 = -62 dBm (above -75 dBm, works!)
    • One AP can serve devices directly above/below
  4. Calculate APs needed per floor:
    • Effective coverage radius: ~20m (with margin)
    • Coverage area per AP: pi x 20^2 = 1,257 sq m
    • Floor area: 1,200 sq m
    • Minimum APs per floor: 1,200 / 1,257 = 1 (theoretically)
    • Add 30% overlap: 1.3 APs per floor
    • Recommend: 2 APs per floor for redundancy and load balancing

Result: Deploy 2 APs per floor (10 total) in a staggered pattern. Each AP covers 600 sq m per floor plus partial coverage to adjacent floors. Total received signal ranges from -62 dBm (near AP) to -75 dBm (floor corners), with 13+ dB margin.

Key Insight: Concrete floors attenuate more than horizontal distance in most cases. An AP 10m away through concrete (85 dB loss) has similar path loss to an AP 25m away horizontally (86 dB loss). Plan coverage in 3D, not just 2D floor plans.

Worked Example: Outdoor LoRaWAN Network Coverage with Terrain

Scenario: A utility company deploys LoRaWAN water meters across a 15 km x 10 km service area with varied terrain: urban core (2 km radius), suburban ring (5 km radius), and rural edge. A 50m hill blocks line-of-sight to 30% of the rural area. Determine gateway placement strategy.

Given:

  • LoRa 915 MHz specifications:
    • TX power: 14 dBm (sensor), 27 dBm (gateway)
    • Receiver sensitivity: -137 dBm (SF12)
    • Antenna gain: 2 dBi (sensor), 8 dBi (gateway)
  • Environment path loss exponents:
    • Urban (n=4.0), Suburban (n=3.0), Rural (n=2.3)
  • Hill height: 50m above surrounding terrain
  • Required link margin: 15 dB for 99.9% reliability

Steps:

  1. Calculate uplink budget (sensor to gateway):

    • TX EIRP (sensor): 14 + 2 = 16 dBm
    • RX (gateway): -137 + 8 = -129 dBm effective sensitivity
    • Max path loss: 16 - (-129) - 15 = 130 dB

  2. Determine range by environment:

    Urban (n=4.0):

    • Path loss = 58 + 40 log(d) = 130 dB
    • 40 log(d) = 72, log(d) = 1.8, d = 63m… too short!
    • Problem: n=4.0 assumes heavy obstruction
    • With gateway at 30m height (above buildings): n reduces to ~3.2
    • 58 + 32 log(d) = 130 dB, d = 1.26 km
    • Urban coverage radius: ~1.2 km

    Suburban (n=3.0):

    • 58 + 30 log(d) = 130 dB
    • 30 log(d) = 72, log(d) = 2.4, d = 251m… still seems short
    • Gateway height advantage: reduces n to 2.6
    • 58 + 26 log(d) = 130, d = 2.77 km
    • Suburban coverage radius: ~2.8 km

    Rural (n=2.3):

    • 58 + 23 log(d) = 130 dB
    • 23 log(d) = 72, log(d) = 3.13, d = 8.5 km
    • Rural coverage radius: ~8.5 km

  3. Address hill obstruction using knife-edge diffraction:

    • Hill creates 50m obstruction above the line-of-sight path
    • The knife-edge diffraction parameter v depends on how far the obstruction extends into the Fresnel zone
    • At 10 km total path (5 km each side), the Fresnel radius at midpoint: r_1 = 17.3 sqrt(10 / (4 x 0.915)) = 28.6 m
    • A 50m hill extending well above the line-of-sight path creates significant diffraction loss
    • Using the ITU knife-edge model, this obstruction causes approximately 15-20 dB of diffraction loss
    • With only 15 dB design margin, this link is marginal or fails

  4. Gateway placement plan:

    • Primary gateway: Urban center, 30m rooftop, covers urban + inner suburban
    • Secondary gateway: Opposite side of hill, 15m tower, covers blocked rural area (eliminates hill obstruction entirely)
    • Tertiary gateway: Far edge of service area for redundancy

Result: 3 gateways provide full coverage with redundancy. Primary gateway at urban center reaches 2.8 km (covers urban + most suburban). Secondary gateway behind the hill eliminates the obstruction shadow zone. Gateway costs: $1,500 each ($4,500 total) versus 15,000 meters served = $0.30/meter for infrastructure.

Key Insight: A single high-elevation gateway in urban areas outperforms multiple low-elevation gateways. The urban n=4.0 path loss exponent assumes ground-level propagation; elevating gateways 30m+ reduces effective path loss exponent by 0.5-1.0, dramatically increasing range. For terrain obstructions, the practical solution is often to place a gateway on the far side of the obstruction rather than trying to engineer a link over it.

Step 1: Calculate first Fresnel zone radius

Use: r_1 = 17.3 x sqrt(d / 4f) where d = distance (km), f = frequency (GHz)

Distance 868 MHz 915 MHz 2.4 GHz
1 km 9.3 m 9.0 m 5.6 m
3 km 16.1 m 15.7 m 9.7 m
5 km 20.8 m 20.2 m 12.5 m
10 km 29.4 m 28.6 m 17.7 m

Step 2: Apply 60% clearance rule

Minimum clearance = 0.6 x r_1

Step 3: Add obstacle height

Antenna height = Obstacle height + 60% clearance

Example Decision Tree (LoRa 915 MHz, 5 km link):

Distance: 5 km
Fresnel radius: 20.2 m
60% clearance: 12.1 m

Terrain:
+-- Flat farmland (2m crops)?
|   +-- Gateway height: 2m + 12.1m = 15m pole
|
+-- Urban (10m buildings)?
|   +-- Gateway height: 10m + 12.1m = 23m rooftop
|
+-- Ground sensor (0.2m)?
    +-- Clearance: 0.2m / 20.2m = 1% (too low)
    +-- Solution: Elevate sensor to 3m pole -> 3m / 20.2m = 15% (marginal)
    +-- Better: Elevate both ends -> sensor 3m + gateway 15m = OK

Cost vs Performance Tradeoff:

Gateway Height Range (5 km link) Cost Use Case
3m (pole) 0.5-1 km $200 Dense urban
10m (2-story roof) 2-3 km $500 Suburban
15m (pole) 5-7 km $1,500 Rural farmland
30m (tower) 10-15 km $5,000+ Wide-area coverage

Decision: For most IoT deployments, target 60% Fresnel clearance at the link midpoint. Accept 40-50% clearance only if link budget has 10+ dB margin.

Common Pitfalls

A clear visual LOS between two antennas does not guarantee adequate RF propagation. The first Fresnel zone may be obstructed by terrain, vegetation, or buildings even when the direct path is visually clear. Fix: calculate the Fresnel zone radius at the link midpoint and verify clearance before antenna installation.

The Fresnel zone is widest at the midpoint but must be checked at all points along the path, especially where obstacles are present. Fix: calculate the Fresnel zone radius at each obstacle’s cross-section point along the path, not just at the midpoint.

At 10 km, Earth’s curvature adds approximately 1.96 m of effective obstacle height. Ignoring this leads to antenna mounting heights that are too low. Fix: add the earth bulge correction (h = d²/12.75 km for d in km, h in metres) to Fresnel zone calculations on long links.

46.13 Summary

  • Fresnel zones require 60% clearance for reliable wireless links – obstacles in the ellipsoid cause diffraction loss
  • Lower frequency = larger Fresnel zone: LoRa at 915 MHz needs more clearance than Wi-Fi at 2.4 GHz
  • Antenna height scales with distance: 1 km needs 6m height, 5 km needs 13-15m height for the same frequency
  • Ground-mounted sensors have 80-90% range reduction due to Fresnel blockage – elevate antennas to 2-3m minimum
  • Lower frequencies penetrate buildings better because wavelength enables diffraction around obstacles
  • Practical deployments must account for terrain, vegetation, and seasonal changes
Design Checklist: Wireless IoT Deployment

Before deploying wireless IoT devices:

  1. Calculate link budget for worst-case distance and obstacles
  2. Measure actual RSSI at planned deployment locations (do not trust theoretical models alone!)
  3. Add 10-20 dB fade margin for seasonal changes (foliage growth, rain, snow)
  4. Account for material attenuation: Concrete = 10-15 dB, metal = 20-30 dB per obstacle
  5. Consider frequency tradeoffs: Lower frequency = better penetration but larger antennas and less bandwidth
  6. Test in actual environment before large-scale deployment
  7. Plan for 20-30% coverage overlap to ensure handoff between access points/gateways

Common Mistake: Assuming line-of-sight range applies to indoor/urban deployments. Real range is typically 30-60% of theoretical maximum!

46.14 What’s Next

With Fresnel zone principles and antenna height design under your belt, continue exploring the propagation and link planning series below.

Topic Chapter Description
Path Loss Fundamentals Path Loss & Propagation Understand free-space path loss, log-distance models, and how frequency affects signal attenuation over distance
Link Budget Planning Link Budget and Coverage Planning Combine transmit power, antenna gain, and path loss into a link budget to predict coverage and select equipment
Material Attenuation Attenuation & RSSI Quantify how concrete, brick, glass, and vegetation attenuate signals; interpret RSSI measurements in real deployments
Shared Channel Collisions Address Collisions Explore how collisions in shared wireless channels reduce throughput and learn MAC strategies to manage contention
Collision Avoidance Design Collision Design Strategies Apply CSMA/CA, TDMA, and frequency planning to design IoT networks that minimize packet loss from channel contention
Bandwidth Planning Bandwidth Requirements Calculate bandwidth requirements for IoT data streams and select protocols that fit within spectrum allocations