123 Main Street, New York, NY 10001

Microwave / mmWave Backhaul: RF Conversion, IQ, PLLs & I/O

← Back to: Telecom & Networking Equipment

Microwave/mmWave backhaul radios turn Ethernet/SDH traffic into a high-capacity wireless hop using frequency conversion, IQ modulation, and low phase-noise LO chains while staying inside EVM and spectral-mask limits. This page explains the end-to-end architecture and the practical knobs—duplexing, PLL/PA linearity, ACM and link budget, plus field counters/loopbacks—to build and troubleshoot stable links in rain, heat, and interference.

H2-1 · What it is (and what it is NOT): scope boundary & typical deployments

Goal: define “microwave/mmWave backhaul” in one screen, set hard boundaries, then map the common deployment shapes.

Microwave / mmWave backhaul is the wireless transport hop that carries Ethernet or SDH traffic between a cell site (or remote node) and the aggregation / metro network. It sits between “base station access” and “core transport,” turning framed digital traffic into a stable RF link with the availability and spectral compliance required for carrier service.

This page focuses on the radio transport chain (RF conversion, IQ modulation/demodulation, low phase-noise LO/PLL, and interface-level Ethernet/SDH integration). It does not cover DU/CU compute, O-RAN RU transceiver/DPD specifics, optical transport (DWDM/ROADM/OTN), or timing-switch (PTP/SyncE) architecture details.

RF up/down conversion IQ mod/demod & EVM Low phase-noise PLL/LO Ethernet/SDH I/O (interface-level)

Microwave vs mmWave (E-band) — practical engineering boundaries:

  • Distance vs throughput: higher carrier frequency enables wide channels and high throughput, but pushes tighter requirements on alignment, phase noise (EVM), and fade margin.
  • Weather sensitivity: mmWave links typically demand a more deliberate plan for rain fade and availability (fade margin + adaptive modulation/coding policy), especially for strict SLAs.
  • Mechanical realities: narrower beams at higher bands raise sensitivity to antenna pointing error and wind-induced drift; this directly shows up as SNR/EVM degradation and ACM downshifts.
  • Spectral compliance: as channels widen and QAM order increases, meeting spectral mask / spurious constraints depends heavily on LO purity, mixer spurs, and PA linearity.

Typical deployment shapes:

  • PtP (point-to-point): the dominant mode for high-capacity site-to-aggregation hops; predictable interference and throughput.
  • PtMP (point-to-multipoint): useful for multi-site access; shared medium means scheduling and load can drive throughput variance.
  • 1+1 protection: redundancy to maintain availability under fades or hardware faults; commonly paired with conservative ACM thresholds.

Reader expectation set: the rest of this page explains how RF conversion, LO/PLL quality, and IQ impairments map into “what the network sees” (throughput stability, EVM/BER margin, and link availability).

Figure F1 — Backhaul in site topology (what it connects, and where)
Ethernet/SDH → Microwave/mmWave Backhaul → Aggregation/Core RAN / Cell Site DU / Site equipment Traffic: Eth / SDH Backhaul Radio IDU Ethernet/SDH I/O ODU RF front-end + dish Aggregation Router / Switch Metro / Core uplink Ethernet / SDH Wireless hop Microwave / mmWave (E-band) Deployment tags PtP PtMP 1+1
Reading tip: treat the “wireless hop” as a transport pipe whose stability is dominated by fade margin, EVM/BER margin, and spectral compliance.

H2-2 · Reference architecture: IDU/ODU split and the signal path end-to-end

Goal: lock the end-to-end “golden path” (interfaces → baseband → RF → antenna), then show the feedback loops that keep EVM/BER stable outdoors.

A practical way to reason about backhaul radios is to separate the design into an Indoor Unit (IDU) and an Outdoor Unit (ODU). The split is not only mechanical; it clarifies where digital framing ends and where RF impairments begin, which helps diagnose field issues without guessing.

IDU typically contains:

  • Ethernet / SDH interfaces (PHY/framer, buffering, alarms/counters) to present a transport endpoint.
  • Baseband modem functions (mapping, modulation/demodulation control, and adaptive modulation/coding policy) to keep throughput stable under fades.
  • Management plane (telemetry, configuration, and event logs) to expose “why the link stepped down” rather than only “that it stepped down.”

ODU typically contains:

  • RF/IF conversion chain (mixers, IF filtering, gain stages) that sets spurs/image rejection and noise figure.
  • LO/PLL synthesizer and distribution where phase noise and spurs often become the hidden EVM limiters for high-order QAM.
  • PA/LNA + antenna / waveguide that defines EIRP, receiver sensitivity, and thermal-limited operating regions.

The most important “systems insight” is that a backhaul radio is not a one-way signal chain. It stays within spec by closing a few lightweight loops that continuously fight outdoor drift:

  • AGC loop: observes IF/baseband level (and sometimes SNR proxies) → adjusts analog/digital gain to protect dynamic range and EVM.
  • Tx power / linearity loop: observes EVM/adjacent leakage proxies + temperature → trims output power or bias to stay within spectral mask.
  • Frequency / lock loop: monitors lock detect and residual frequency error → maintains carrier/LO integrity to avoid demod stress and throughput collapse.
  • Calibration loop: tracks temperature and I/Q imbalance drift → updates correction coefficients so the constellation remains “round” over time.

Boundary reminder: interface timing (PTP/SyncE) may exist around these blocks, but detailed timing-switch architecture belongs to the “Timing Switch” sibling page.

Figure F2 — IDU↔ODU functional split (signal path + control loops)
IDU (Indoor Unit) Ethernet / SDH I/O Framer / MAC Buffers · counters · alarms Baseband Modem ACM control · EVM/BER monitor Mgmt / Telemetry ODU (Outdoor Unit) IQ Mod / Demod IF Chain Mixer (Up/Down) PLL / LO phase noise · spurs PA / LNA power · NF · thermal data + control RF to antenna/dish EVM/BER power/temp telemetry lock status Golden path: I/O → framer/MAC → baseband → IQ → conversion → PLL/LO → PA/LNA → antenna
Use this diagram as a debugging map: symptoms visible at Ethernet/SDH counters, EVM/BER monitors, lock status, and thermal/power telemetry usually point to one of the blocks above.

H2-3 · Bands, duplexing, and channelization: what drives hardware choices

Goal: turn “band / duplex / bandwidth” choices into a clear hardware cost chain (phase noise, linearity, filtering, thermal, alignment).

Band selection, duplexing method, and channel bandwidth are not “RF preferences.” They set the constraints that ultimately decide whether the link can hold a stable throughput under fades while staying inside spectral mask and EVM limits. The practical chain is: throughput / distance / availabilitySNR & EVM marginphase noise + linearity + filtering + thermal.

Band choice directly shifts the hardware difficulty:

  • PA output and efficiency: higher bands often reduce the “easy” linear output power. The system-level symptom is earlier ACM downshifts and less headroom during rain fades.
  • Phase-noise pressure: higher-order QAM and wide channels tighten EVM tolerance, making PLL/LO purity a top limiter instead of an afterthought.
  • Packaging and antenna mechanics: higher bands push tighter routing, shielding, and connector/waveguide sensitivity; narrower beams raise alignment sensitivity and wind-induced drift impact.

Duplexing choice changes the dominant interference paths:

  • FDD (duplexer-based): filtering and isolation become the bottleneck. Insufficient isolation shows up as Rx desense (weaker sensitivity, BER spikes under low SNR). Filter behavior can also stress spectral compliance and EVM margin.
  • TDD (switch-based): fast switching creates transient risks. Poor gating/isolation can cause Tx→Rx leakage during turn-around, leading to burst errors or unstable demod performance even when average SNR looks acceptable.

Channel bandwidth and modulation order tighten both LO and PA requirements:

  • Bandwidth ↑ increases the chance that spurs/images land near the wanted channel; filters must leave margin for skirts and drift.
  • QAM order ↑ reduces constellation spacing, so the same phase noise or nonlinearity consumes more of the EVM budget.
  • System outcome: passing spectral mask + EVM often forces either cleaner LO, more linear PA operation (lower output or better biasing), or stronger filtering—each with power/thermal cost.

Choice Prompt A — “Max throughput”

Expect tighter phase-noise/EVM constraints and higher linearity demand; budget more for LO purity and PA headroom.

Choice Prompt B — “Max distance / availability”

Expect tighter fade-margin planning; hardware pressure shifts to stable EIRP, thermal control, and robust isolation.

Regulatory note (kept brief by scope): spectrum planning constrains usable channels and EIRP limits, which become fixed inputs to frequency planning and PA/antenna headroom.

Figure F3 — Duplexing & leakage paths (FDD vs TDD)
Key risk paths: Tx leakage → Rx desense · LO feedthrough · image landing FDD (Duplexer) TDD (RF Switch) Tx PA Rx LNA Duplexer Antenna LO/PLL RF to air Tx leakage → desense LO feedthrough Tx PA Rx LNA TDD Switch Antenna LO/PLL RF to air Tx→Rx leakage LO feedthrough Image risk
Interpretation: duplexing is a leakage-management problem. Isolation limits often surface as sensitivity loss (Rx desense) or burst errors during TDD turn-around.

H2-4 · Up/down conversion fundamentals: mixers, images, LO feedthrough, filtering

Goal: build a frequency-planning mindset—identify images, LO leakage, and spurs early, then assign filtering and linearity budget by stage.

A backhaul radio moves a complex-modulated waveform from baseband into RF and back again using one or more conversion steps. Implementation details vary, but the engineering risks repeat: image landing, LO feedthrough, and spurs/intermod—all of which can break spectral mask compliance or consume EVM margin.

Typical conversion paths (kept at system level):

  • IF architecture: Baseband (I/Q) → IF → RF. Easier to place filters for image/spur suppression, but adds frequency-planning complexity.
  • Direct conversion: Baseband (I/Q) → RF. Short chain and integration-friendly, but more sensitive to DC offset and LO leakage shaping the spectrum.

Symptom → Cause → Fix: Image

Channel-dependent EVM/BER issues often indicate an image or near-in-band product. Fix with planning + preselect/IF filtering + I/Q balance control.

Symptom → Cause → Fix: LO leakage

A “fixed spur” that ignores modulation points to LO feedthrough. Fix with isolation/layout, balanced paths, and calibration to suppress DC-related leakage.

How to budget gain, noise, and linearity without drowning in formulas:

  • Near the antenna: prioritize noise figure and overload resilience (avoid compression/desense under strong signals).
  • In conversion stages: prioritize spur hygiene (keep LO-related products out of the wanted band and leave filter margin for drift).
  • Near the PA / output: prioritize linearity headroom to meet spectral mask while keeping EVM stable at the required throughput.
  • Validation habit: sweep frequency, output power, and temperature to confirm that spurs do not “walk into” the channel under real conditions.

The conversion chain is best treated as a frequency-planning exercise first, and a component-selection exercise second. If planning is wrong, no single “better mixer” can fully rescue the spectrum.

Figure F4 — Frequency plan: IF/RF, image & spurs (and where filters help)
Plan RF/IF/LO so images and spurs stay outside filter skirts Frequency Wanted Filter skirts LO Image Spurs IF planning Choose IF to keep image/spurs out of the wanted band RF IF Wanted channel Image LO Spurs Filter skirts
Reading tip: if a spur line sits near the skirt, it may pass in the lab but fail across temperature/power because drift reduces margin.

H2-5 · IQ mod/demod and impairments: EVM as the north-star metric

Goal: connect IQ impairments to a single system outcome (EVM → BER margin → ACM mode → throughput stability), then map the six most common EVM killers.

In a microwave/mmWave backhaul radio, IQ modulation/demodulation is the step that places complex vector information (amplitude and phase) onto a carrier and recovers it on the receive side. For high-order QAM and wide channels, EVM (Error Vector Magnitude) is the most practical north-star metric because it captures the combined impact of IQ imbalance, LO/PLL quality, residual frequency error, and nonlinearity.

The system chain is simple and useful in the field: EVM margin determines BER margin, which drives ACM downshift frequency, which decides whether throughput is stable or “steps down” under fades.

How to use this chapter: when EVM degrades, identify the dominant signature (shape vs rotation vs fuzz vs power-dependence), then validate with a targeted sweep (frequency, power, temperature).

Six common EVM killers (symptom → likely cause → practical check):

  • I/Q gain mismatch: constellation stretches into an ellipse → I/Q amplitudes differ → compare EVM shape across frequency and temperature; calibration should reduce axis-dependent spread.
  • Quadrature phase error: points skew with cross-axis coupling → I/Q not at 90° → check whether distortion is frequency-dependent; phase calibration should straighten the pattern.
  • DC offset / carrier leakage: constellation shifts off-center or a fixed tone appears → imperfect balance or DC bias → verify “quiet” spectrum for a persistent spur; DC correction should reduce it.
  • Residual carrier frequency offset (CFO): constellation slowly rotates → LO frequency error or marginal lock → correlate rotation rate with lock status and temperature drift.
  • Phase noise: constellation becomes “fuzzy” (random angular jitter) → LO/PLL noise dominates → compare EVM across modulation orders and channel widths; higher order/wider channels amplify sensitivity.
  • PA nonlinearity / compression: EVM worsens sharply with output power and spectral mask tightens → AM-AM/AM-PM distortion → run a power sweep to locate the linear operating window.

Calibration approach: startup

Best for fixed manufacturing offsets. Verify with temperature sweep to ensure the correction does not drift out-of-range outdoors.

Calibration approach: in-service tracking

Best for temperature/aging drift. Verify with event logs and stable EVM during slow thermal ramps (no business disruption).

Boundary note: deeper baseband equalization and OFDM receiver algorithms are intentionally out of scope here; the focus is the radio-level impairment map and calibration mindset.

Figure F5 — Constellation degradation map (Ideal vs IQ imbalance vs Phase noise)
Constellation signatures: shape (IQ) vs fuzz (phase noise) Ideal IQ imbalance Phase noise I Q I Q I Q shape error angular jitter
Quick read: IQ issues primarily distort constellation shape; phase noise primarily adds random fuzz. Power-dependent collapse often points to PA linearity limits.

H2-6 · Low phase-noise PLL & LO distribution: from L(f) to EVM

Goal: make phase noise operational—identify loop “knobs” (benefit / side-effect / validation) and connect L(f) shape and spurs to EVM and spectral mask risk.

For wide channels and high-order QAM, phase noise often becomes the hidden EVM limiter. Even when received power looks adequate, a noisy LO spreads phase error across the constellation, reducing BER margin and triggering ACM downshifts. The right way to work this problem is to treat the LO as a system resource: PLL architecture + loop shaping + spur management + distribution integrity.

Common PLL/LO architecture choices (engineering-level):

  • Integer-N vs Fractional-N: Integer-N tends to be spur-friendly but less flexible; Fractional-N expands frequency agility but demands stricter spur hygiene.
  • Reference strategy: reference quality and distribution cleanliness can dominate close-in regions after loop shaping.
  • LO distribution: buffers/splitters/isolation matter because any added noise or coupling propagates into every mixer, impacting both EVM and spurious emissions.

Practical “knob list” (benefit → side-effect → validation):

  • Loop bandwidth: reshapes ref vs VCO dominance → too wide imports reference noise; too narrow leaves VCO drift → validate by L(f) crossover position plus lock/temperature behavior.
  • Reference noise: improves the region where ref dominates → distribution coupling can erase gains → validate by swapping reference/distribution conditions and correlating EVM change.
  • VCO noise: improves far-out regions that wide channels integrate → may raise power/thermal demands → validate with temperature sweeps and modulation-order sensitivity.
  • Divider/PFD/CP noise: reduces mid-band “humps” → can increase spur sensitivity → validate by searching for platform-like bumps vs discrete spurs.
  • Spur management: prevents discrete tones from landing near the channel or skirt → may constrain frequency plans → validate by sweeping channel plans and ensuring spurs stay away from skirts.
  • Distribution isolation: limits LO feedthrough and cross-coupling → adds insertion loss and gain staging needs → validate by changing load/enable states and checking spur/EVM stability.

What to “read” in a phase-noise plot: the curve shape (which region dominates), the crossover (loop shaping), and spurs (discrete mask/EVM risks).

Figure F6 — PLL noise contributions & loop shaping (blocks + simplified L(f) shapes)
Ref vs VCO dominance is set by loop shaping; spurs are discrete risks PLL chain Ref PFD/CP Loop filter VCO Divider LO out LO dist. Mixer A Mixer B Ref noise VCO noise Simplified L(f) shapes offset L(f) Ref-dominated VCO-dominated crossover spur Why it matters Shape + spurs → EVM margin → ACM stability EVM ACM
Practical read: move the crossover (loop shaping) and clean discrete spurs first; then confirm EVM stability across temperature, output power, and channel plans.

H2-7 · RF front-end: PA/LNA, linearity, power control, and thermal reality

Goal: treat PA/LNA + control loops as a stability system—keep EVM and BER stable without triggering thermal derating.

In backhaul radios, the RF front-end is not optimized for “peak power at any cost.” The practical objective is: maintain EVM and spectral mask compliance across temperature and fading, so the link does not oscillate between ACM modes. That makes linearity headroom, controlled gain, and thermal behavior more important than headline output power alone.

Failure-mode view (useful in the field): EVM gets worse → BER margin shrinks → ACM downshifts become frequent → temperature rises → derating reduces power → margin collapses again.

PA: linearity vs efficiency (backhaul bias):

  • Linearity protects EVM and adjacent-channel emissions: when PA approaches compression, EVM and mask margins can collapse rapidly.
  • Power sweep is the fastest truth test: measure EVM (and an emission proxy such as adjacent leakage) versus output level to find the stable operating window.
  • Control-friendly operation matters: a PA that behaves predictably across temperature enables smooth power backoff instead of abrupt “cliff” behavior.

LNA: noise figure vs linearity under strong interferers:

  • Low NF helps when noise dominates, but linearity prevents desense when strong blockers or leakage push the front-end toward compression.
  • Desense signature: link quality drops even while RSSI appears high; reducing gain can temporarily improve BER (a hint of compression/IMD).
  • Practical check: compare BER stability under strong nearby signals with different gain/attenuation states.

Tx control loop: protect EVM/mask

Use EVM and emission monitors to back off PA drive or bias before compression turns into a throughput cliff.

Rx control loop: avoid desense

Use RSSI and BER/health indicators to keep the chain out of compression while preserving sensitivity in weak-signal fades.

Thermal reality: drift and derating:

  • Temperature drift changes gain and phase, shifting EVM and sometimes frequency/lock margins indirectly through the LO chain.
  • Derating must be predictable: controlled power reduction protects hardware, but it should not cause unstable ACM “ping-pong.”
  • Protection strategy: temperature-triggered backoff + re-calibration events + clear alarms/logs (at system level) to explain throughput steps.
Figure F7 — AGC & power-control loops with thermal derating
Control the operating point: protect EVM/mask (Tx) and avoid desense (Rx) Tx loop Baseband Upconv PA Antenna EVM monitor ACP / Mask Power control backoff Rx loop Antenna LNA Downconv Demod RSSI BER / Health AGC gain Thermal derating temp backoff trigger
Reading tip: if throughput “steps down” with temperature, correlate EVM/mask monitors with the thermal derating state before chasing link budget.

H2-8 · Baseband/IF implementation choices: direct conversion vs IF, ADC/DAC constraints

Goal: compare direct-conversion and IF architectures using practical tradeoffs, then connect ADC/DAC + sample clock constraints back to EVM.

Microwave/mmWave backhaul radios commonly implement either direct conversion (RF ↔ baseband I/Q in one step) or an IF-based chain (RF ↔ IF ↔ baseband). The best choice depends on which problems should be controlled by filtering/frequency planning versus handled by calibration and digital correction.

Direct conversion (RF ↔ I/Q)

Fewer stages and easier integration, but more sensitive to DC offset, LO leakage, and I/Q mismatch near carrier.

IF architecture (RF ↔ IF ↔ I/Q)

Better separation for images and DC-related issues, but more spurs and calibration complexity due to extra conversion stages.

Architecture comparison checklist (practical):

  • Direct conversion: fewer blocks and losses; watch DC offset / 1/f sensitivity / LO leakage; calibration quality strongly impacts EVM stability.
  • IF chain: filtering can control image placement and move DC away; watch spur budgeting across mixers and synthesizers; more blocks mean more drift sources.
  • ADC/DAC (abstract constraints): sampling rate and usable bandwidth set the integration window; ENOB/SNR sets quantization floor; sample clock jitter can translate into phase error at wide bandwidth.
  • Clock boundary (this page only): focus is local sampling and LO reference quality; network timing distribution details are intentionally out of scope.
Engineering shortcut: if a problem is “glued” near carrier (DC/leakage), direct conversion demands excellent calibration; if the problem is image/spur placement, IF gives more frequency-planning leverage.
Figure F8 — Direct conversion vs IF chain (key differences at a glance)
Direct conversion vs IF: which problems move to calibration vs filtering Direct conversion BB I/Q IQ mod RF PA Fewer stages ! DC offset ! LO leakage ! IQ mismatch ! 1/f sensitivity IF architecture BB I/Q IF Mixer RF Filterable image DC moved away ! More spurs ! More parts ! More cal ADC/DAC Sample clock jitter EVM wide BW ↑
Quick read: direct conversion pushes “near-carrier” problems into calibration; IF pushes many issues into frequency planning and spur budgeting.

H2-9 · Ethernet/SDH interfaces: framing, buffering, and link protection (interface-level)

Goal: an “interface engineer bring-up” view—connect, verify, and localize issues using counters and alarms (without expanding into routing/BNG/CGNAT).

Microwave/mmWave backhaul radios often terminate customer traffic as Ethernet and sometimes SDH/SONET. At integration time, most problems are not “mysterious RF issues”—they are mismatches in interface expectations, burst behavior that overflows buffers, or protection switching that looks like random jitter unless the right counters are checked.

Ethernet bring-up focus

Link up stability, negotiation vs forced settings, error counters (CRC/FCS), and congestion indicators.

SDH/SONET bring-up focus

Framer alignment, loopback tests, alarms, and performance monitoring counters for rapid fault isolation.

Ethernet interface (PHY/MAC + service mapping):

  • PHY/MAC sanity first: stabilize link state (avoid flaps), confirm expected speed/duplex, and verify a clean error baseline before throughput tests.
  • VLAN/QoS mapping (interface-only): confirm tags and priority marking are preserved or translated as intended; keep this at the port mapping level (not network policy).
  • Buffers and congestion: bursts can trigger queue drops or latency spikes; correlate throughput instability with queue counters rather than guessing RF quality.

SDH/SONET interface (framing + OAM-style checks):

  • Framer alignment and loopbacks: use local/remote loopback to isolate whether faults originate in the port, the framer, or beyond the handoff.
  • Alarms are the fast filter: loss-of-signal / loss-of-frame style alarms (concept-level) quickly narrow the failure to physical vs framing layers.
  • Performance counters: treat error bursts and persistent error floors differently; the pattern often tells “intermittent connection” vs “systematic mismatch.”

Link protection (mention-only, interface behavior):

  • 1+0 vs 1+1: understand whether protection exists and whether a switch event can explain short disruptions or jitter.
  • APS and aggregation: keep focus on “switch count / switch reason / restore behavior” counters—do not expand into routing design.
Fast localization rule: PHY errors (CRC/FCS) point to physical issues; framer alarms point to alignment/transport issues; queue drops point to buffering/congestion; switch counters point to protection events.
Link flap CRC/FCS Line errors Framer alarms Loopback Queue drop Switch count
Figure F10 — Counters & alarms map (what to check, and where it lives)
Interface-localization map: pick counters before chasing RF Ethernet PHY/MAC Link flap CRC/FCS Line errors Pause VLAN/QoS mapping SDH/SONET Framer Alarms LOF/LOS Loopback PM Error burst vs floor Buffers / Queues Queue drop ECN Congestion events Burst sensitivity Protection Switch count Switch reason Restore Symptom → where to look CRC rising → PHY/MAC Alarms → Framer layer Sawtooth throughput → Queues Random short disruptions → Switch counters Clean counters but low throughput → revisit RF/ACM
Use loopback first: it reduces guesswork by separating “local interface faults” from “beyond the handoff.”

H2-10 · Link budget & propagation: rain fade, oxygen absorption, and ACM strategy

Goal: a workflow view—turn distance, frequency, antennas, and weather into fade margin decisions and an ACM ladder that keeps the link usable.

A backhaul link is an accounting problem: every gain and loss must be placed into a single budget waterfall. At mmWave (especially E-band), the “extra terms” such as rain fade, atmospheric absorption, and alignment sensitivity are often what decide whether a link holds a high-throughput mode or drops to a more robust profile.

Why budget matters: the radio does not output a single fixed throughput—it outputs a throughput that follows an ACM ladder as SNR changes.

Engineering workflow (inputs → decisions):

  • Set targets: distance, frequency band, channel bandwidth, and availability (e.g., 99.9 vs 99.99).
  • Compute EIRP-side terms: Tx power, antenna gain, and feeder/waveguide losses.
  • Apply propagation losses: free-space path loss plus band-specific atmospheric terms.
  • Add weather and installation reality: rain/fog fade and alignment penalties for narrow beams.
  • Map to SNR: received level versus noise floor (wider bandwidth increases integrated noise).
  • Choose fade margin: margin is the “stability budget” that protects the desired availability.
  • Design ACM ladder behavior: define thresholds and stability (avoid excessive up/down switching).

E-band realities to plan for

Rain fade dominates, narrow beams amplify alignment errors, and absorption adds a non-negligible loss term.

ACM stability goals

Prefer predictable downshifts with clear margins over frequent mode “ping-pong” that hurts user experience.

Figure F9 — Budget waterfall + ACM ladder (from power to ModCod)
Link budget as a waterfall, throughput as an ACM ladder Budget waterfall Tx power + Tx antenna gain – Feeder / waveguide loss – Free-space path loss (FSPL) – Atmospheric absorption – Rain / fog fade – Alignment / pointing penalty ⇒ SNR (after noise floor) ACM ladder High-QAM Throughput ↑ Mid-QAM Low-QAM Robust Availability ↑ current SNR Hold time / hysteresis Mode switch count
If rain events cause repeated mode flips, prefer threshold stability (hold time/hysteresis) over chasing peak throughput.

H2-11 · Validation checklist: what proves the radio is done (lab + production)

Goal: a sign-off checklist that ties modulation quality, emission compliance, frequency purity, power accuracy, receiver performance, and robustness to measurable tests (lab DVT + production EOL).

A microwave/mmWave backhaul radio is “done” only when performance is stable across temperature, supply variation, strong interferers, and long-term drift. This section organizes acceptance into three layers: (1) KPI metrics, (2) stress scenarios, and (3) manufacturing flow (calibration + fast reject).

Lab validation (DVT)

Proves margin and worst-case corners; discovers “mode-dependent” failures (high-QAM, wide bandwidth, high power, high temperature).

Production test (EOL)

Fast, repeatable gating + calibration; uses golden units and simplified checks that correlate to lab results.

Acceptance metrics (what to measure, and why):

  • EVM (north-star): the single metric that integrates IQ imbalance, phase noise, PA linearity, carrier offset, and spurious behavior into modulation quality.
  • BER / packet error: converts “signal quality” into a service outcome; correlates to ACM stability and field throughput behavior.
  • Spectrum mask / ACLR: emission compliance gate; often fails at high power, wide bandwidth, hot corners, or with LO spur growth.
  • Phase noise & spurs: frequency purity that directly impacts high-order QAM EVM and can also violate mask requirements.
  • Tx power accuracy: ensures link budget predictions remain valid; prevents “same design, different reach” field variability.
  • Rx sensitivity / noise figure (NF): sets the availability floor under rain fade and alignment penalties.
Practical sign-off rule: compliance (mask/ACLR) and frequency purity (lock/spurs) are hard gates; EVM and Rx sensitivity determine how reliably high throughput is held under real fading and drift.
Temp sweep Voltage margin Strong interferer Long soak drift Outdoor stress

Test scenarios (how to force worst-cases):

  • Temperature scan: verify EVM, mask/ACLR, phase noise/spurs, and Tx power across cold/room/hot; confirm calibration does not collapse at extremes.
  • Supply variation: margin supply rails that feed PA/PLL/baseband; look for lock loss, spur growth, compression shift, and EVM step-changes.
  • Strong interference: inject blockers to evaluate Rx desense, AGC behavior, and BER stability; distinguish “RF overload” from “digital instability.”
  • Long-duration soak: monitor drift of EVM, frequency error, spur levels, and power accuracy over hours/days; detect slow thermal or aging effects.
  • ODU outdoor reality: vibration / wind-induced alignment sensitivity, humidity/condensation effects on RF path and connectors, and surge/ESD susceptibility at external interfaces.

Kill criteria (fast reject gates):

  • Mask/ACLR fail at any required mode/corner.
  • EVM above limit at the defined high-throughput mode (or shows unstable jumps with temperature or power).
  • PLL/LO unlock, or spur spikes that violate limits or correlate with BER bursts.
  • Tx power out of tolerance after calibration steps (indicates sensor path, coupler, or control-loop issues).
  • Rx sensitivity/NF miss at the representative worst-case bandwidth (availability floor is compromised).

Production essentials (calibration + throughput):

Calibration station flow

Reference path correction (cables/attenuators), repeatable fixtures, temperature-aware steps, and pass/fail thresholds locked to golden units.

Golden unit strategy

Use multiple golden units to detect tester drift; schedule re-validation; separate “tester issues” from “unit issues.”

  • Fast EOL gating: pick 1–2 representative ModCod profiles + fixed power points; measure quick EVM + mask/ACLR snapshots and reject early.
  • Correlation to lab: every production metric must have a proven correlation to DVT worst-case behavior; avoid “tests that pass but do not predict field.”
  • Re-test rules: define which failures allow rework (e.g., calibration redo) versus immediate scrap (e.g., repeated spur spikes / unlock).

Example test equipment part numbers (typical lab + production tooling):

  • Vector/spectrum analysis (EVM, ACLR, mask, spurs): Keysight N9041B UXA; R&S FSW series.
  • Vector signal generation (QAM/OFDM stimulus): R&S SMW200A; equivalent VSG platforms with required bandwidth/options.
  • Phase noise / source analysis: R&S FSWP; Keysight E5052B (plus appropriate downconversion/extension where needed).
  • mmWave/E-band extension (when base instruments do not cover band): VDI spectrum analyzer extensions (SAX family) or equivalent frequency extension modules.
  • Ethernet traffic/validation (throughput, loss, burst behavior): Spirent TestCenter; VIAVI T-BERD/MTS class field testers.
Figure F10 — Test matrix map (metrics × stress conditions, lab vs production coverage)
Test matrix: coverage that proves “done” Legend ■ Required (Lab DVT) ▲ Sample (Production / audit) ○ Optional / investigative × N/A Temp Voltage Interference Aging/Drift Outdoor EVM BER / PER Mask / ACLR Phase noise / Spurs Tx power accuracy Rx sensitivity / NF Lock / Stability Surge/ESD (ODU) Tip: production uses a correlated subset (▲) while lab covers worst-case corners (■).
Recommended practice: lock production gates to lab correlation (worst-case mode + worst-case power/temperature) and monitor tester drift using golden units.

H2-12 · Field diagnostics: counters, loopbacks, and fast fault isolation

Goal: convert symptoms into evidence-based isolation using trends (RSSI/SNR/EVM/BER/ACM), loopbacks (interface/baseband/RF), and a short action ladder.

Triage in 90 seconds (before guessing)

  • Time-correlate: note start/stop time and whether it matches rain, heat, or maintenance windows.
  • Check three trends: SNR/RSSI, EVM trend, and ACM mode transitions (plus switch counts).
  • Classify quickly: SNR falls → likely RF/propagation; SNR stable but EVM/BER jumps → likely baseband/LO stability; RF metrics clean but throughput sawtooth → likely interface/buffering.
RSSI SNR EVM BER ACM mode Temp Power backoff Unlock count

Must-have observations (minimum set for fault isolation):

RF quality (propagation + alignment)

RSSI/Rx level, SNR, ACM downshift reasons (if available), fade events, and alignment-sensitive drift patterns.

Modulation quality

EVM trend, BER/PER, mode stability (switch counts), and sudden step changes that indicate instability.

Thermal & power behavior

Temperature, power-backoff / derate status, fan/thermal events (if present), and any temperature-correlated EVM shifts.

Interface sanity (port-level)

CRC/FCS, link flap, rate/duplex change, queue drops, and protection switch counters (1+1/APS events).

Evidence rule: treat trends as primary evidence. Single snapshots can lie; correlated changes across RSSI/SNR/EVM/ACM counters usually do not.

Loopback ladder (isolate one segment at a time):

  • Interface loopback: validates local Ethernet/SDH port behavior (link stability, CRC, buffering) without relying on the wireless hop.
  • Baseband loopback: isolates digital processing stability (coding/modulation path, calibration state, internal timing) from the RF path and antenna alignment.
  • RF loopback: validates LO/mixer/PA/LNA path stability using internal coupling or a test path; helps separate propagation/alignment issues from radio hardware drift.

Common field faults (symptom → evidence → first action):

Alignment drift (beam mispoint)

Evidence: RSSI/SNR slowly worsens; rain makes it much worse; ACM downshifts become frequent. First action: verify alignment sensitivity and look for SNR recovery with minor pointing correction.

Rain fade thresholds mis-tuned

Evidence: frequent ACM “ping-pong” (high switch count) during rain without full link loss. First action: check mode stability settings (hold time/hysteresis conceptually) and confirm fade margin behavior.

LO unlock / reacquire events

Evidence: sudden EVM/BER collapse with unlock/relock counters; may correlate with temperature or voltage events. First action: check lock counters and event timestamps; run RF/baseband loopback to isolate.

Thermal derating

Evidence: temperature crosses a threshold; power-backoff counter rises; throughput drops even if link remains up. First action: confirm derate state and improve cooling/solar shielding/airflow.

Ethernet negotiation anomalies

Evidence: link flap, speed/duplex changes, CRC bursts; RF metrics stay normal. First action: lock port settings if needed and swap cable/SFP/port to confirm interface-side root cause.

Congestion / buffering behavior

Evidence: throughput sawtooth with queue drop indicators; RF metrics clean. First action: inspect queue/drop counters and traffic burst patterns; use interface loopback to rule out wireless hop.

Symptom → most likely bucket → first counters → next step:

  • Throughput drops during rain: likely RF/propagation → check SNR/RSSI + ACM downshift count → verify fade margin behavior and alignment stability.
  • Intermittent BER spikes: RF or baseband → check EVM trend + unlock events + BER timestamp → run baseband loopback; if clean, move to RF/alignment checks.
  • Link down / frequent reconnect: RF or interface → check lock/reacquire + link flap + event timeline → isolate with interface loopback, then examine RF stability and thermal/power events.
  • SNR stable but EVM suddenly worsens: baseband/LO stability → check unlock count + temperature/voltage events → run RF loopback to see if impairment originates in LO/RF chain.
  • RF counters clean but throughput “sawtooth”: interface/buffering → check queue drops + CRC + speed/duplex changes → validate via interface loopback.
Figure F11 — Fault tree (symptom → RF / Baseband / Interface, with key evidence chips)
Symptom-to-cause fault tree (use counters before guessing) Throughput drop BER spikes Link down RF Baseband Interface RF evidence SNR ↓ ACM ↓ RSSI drift Rain fade Alignment sensitivity Baseband evidence EVM ↑ Unlock cnt BER burst Temp event Calibration state change Interface evidence CRC ↑ Link flap Queue drop Neg change Protection switch cnt Next actions (fast) Check trends Run loopback Inspect install Thermal
Use loopbacks as a ladder: interface → baseband → RF. Each step removes a segment from suspicion and prevents blind part swapping.

Request a Quote

Accepted Formats

pdf, csv, xls, xlsx, zip

Attachment

Drag & drop files here or use the button below.

H2-13 · FAQs (Microwave / mmWave Backhaul)

1) Microwave backhaul vs mmWave/E-band—how to choose by distance and availability? H2-1/H2-10
Choose by the availability target and the “fade physics” your path will see. Microwave bands usually hold longer hops with more forgiving rain behavior, while mmWave/E-band can deliver very high capacity over shorter distances but is more rain- and alignment-sensitive. Start from distance + required uptime (e.g., 99.9 vs 99.99), then size antenna/EIRP and verify the fade margin and ACM ladder can hold service during worst fades.
Look for correlated changes in SNR/RSSI and ACM downshifts during weather events.
2) What’s the practical IDU/ODU split and when does all-outdoor make sense? H2-2
In a typical split, the IDU hosts Ethernet/SDH interfaces, framing, baseband processing (coding/modulation control, ACM logic), and management, while the ODU houses RF/IF, PLL/LO generation, PA/LNA, antenna/waveguide interfaces, and calibration/telemetry loops. All-outdoor designs can simplify cabling and deployment when space or indoor power/rooms are constrained, but they demand robust thermal design and service access. Diagnostics follow the split: port counters live near the IDU, RF stability and derate signals live near the ODU.
When troubleshooting, confirm where each counter is sourced (IDU vs ODU) before drawing conclusions.
3) TDD vs FDD in microwave radios—what failures show up if you pick wrong? H2-3
FDD pushes isolation and filtering; if duplexing/isolation is insufficient, TX leakage can desensitize RX, showing as degraded sensitivity, unstable BER, or reduced throughput even at good RSSI. TDD shifts pain to switching transients and self-interference control; poor timing or isolation can cause bursty EVM/BER spikes around TX/RX transitions. The “wrong choice” often appears as a mismatch between good-looking RSSI and bad EVM/BER behavior under real traffic patterns.
Use mode-dependent evidence: problems that align with TX/RX switching strongly implicate TDD transition behavior.
4) Why do image and LO leakage suddenly dominate in wideband links? H2-4
Wide bandwidth shrinks the “filtering slack,” so images, LO feedthrough, and close-in spurs have fewer places to hide. As channels widen and modulation orders increase, small unwanted tones or mirror responses can land inside the occupied spectrum or raise the noise floor, directly hurting EVM and sometimes triggering emission issues. The fix is usually frequency planning plus the right filter placement and rejection strategy, not one magic component.
If EVM and spectral mask failures appear together at wide bandwidth, suspect planning/filter skirts and LO leakage paths.
5) Which IQ impairment hurts EVM the most in the field: gain, phase, or DC offset? H2-5/H2-12
The “worst” impairment is the one that drifts in your environment. Gain/phase imbalance often creates predictable constellation skew and can be stable after calibration, while DC offset and low-frequency effects can be temperature- or state-dependent and show up as mode-specific EVM jumps. In the field, distinguish by trends and isolation: if EVM shifts correlate with temperature or power state, suspect drift-sensitive offsets/imbalances; confirm by running baseband and RF loopbacks to see whether the impairment persists without the over-the-air hop.
Correlate EVM steps with temperature, unlock events, and calibration state changes before swapping RF parts.
6) Phase noise vs EVM—how do you tell if the PLL is the bottleneck? H2-6/H2-11
If phase noise is the bottleneck, EVM usually degrades disproportionately as you move to higher-order QAM or wider bandwidth, even when RSSI/SNR are strong. Another clue is repeatable EVM limitation across power settings (not improving with more output power) while spectral purity or spur indicators worsen. The clean way is a lab correlation: measure phase noise/spurs and compare with EVM across the same ModCod and bandwidths; if EVM tracks close-in noise or spur growth, the LO chain is likely limiting.
Watch for “EVM ceiling” behavior: strong link quality but EVM refuses to improve at high ModCod.
7) Why does high output power sometimes reduce throughput (ACM drop)? H2-7/H2-10
More power is not always cleaner power. Near compression, PA nonlinearity raises EVM and out-of-channel emissions, which can force ACM to downshift to a more robust mode, reducing throughput despite higher RSSI. High power also increases heat, and thermal derating can trigger power backoff or drift that destabilizes EVM over time. Confirm by checking whether ACM downshifts coincide with EVM worsening, power-backoff counters, or temperature thresholds.
If throughput drops while RSSI rises, suspect linearity/thermal limits rather than propagation.
8) Direct-conversion vs IF—what symptoms point to DC offset/1/f issues? H2-8/H2-12
Direct conversion can be more sensitive to DC offset and low-frequency noise, so issues often appear as state-dependent EVM degradation or instability that correlates with temperature, gain state, or calibration. IF architectures tend to make filtering and image control more explicit, but introduce additional conversion stages and spur opportunities. Field clues that hint at DC/1-f sensitivity include EVM behavior that changes with AGC/gain state even when RSSI is stable; isolate using baseband loopback to remove the over-the-air variable.
A stable RSSI/SNR with gain-state-dependent EVM swings is a strong hint to check offset/low-frequency behavior.
9) Ethernet looks fine but throughput collapses—what interface counters matter most? H2-9/H2-12
Start with four counter buckets: CRC/FCS errors (integrity), link flap and speed/duplex renegotiation (stability), queue drops (buffering/congestion), and protection switch events (1+1/APS behavior). A “link up” status can hide repeated micro-outages, bursts of CRC, or queue overflow that crushes goodput. If RF counters are clean, run an interface loopback to prove whether the collapse is local to the port path before investigating the wireless hop.
Queue drops + clean RF metrics often explain “sawtooth” throughput without implying routing-layer causes.
10) Rain fade planning: how much fade margin is “enough” for 99.99%? H2-10
“Enough” margin is the margin that keeps your service above the required ModCod during the worst expected fades for your geography and path. For 99.99% availability, plan the budget from Tx power and antenna gains through losses to Rx SNR, then map that SNR to an ACM ladder with clear switching thresholds. The practical output is not a single number but a decision: antenna size/EIRP plus ACM profile that maintains a minimum throughput (or a minimum connectivity mode) during heavy rain events.
Validate that ACM does not ping-pong during moderate rain; stability is part of availability.
11) What is the minimal lab validation set to avoid field surprises? H2-11
A minimal set should cover modulation quality, emissions, frequency purity, power accuracy, and receiver floor under stress. Concretely: EVM and BER in representative high-throughput modes; spectrum mask/ACLR at worst-case power and bandwidth; phase noise/spurs (or at least spur behavior correlated to EVM/mask); Tx power accuracy after calibration; and Rx sensitivity/NF at the target bandwidth. Run these across temperature corners, supply margin, a blocker/interference condition, and a long soak to catch drift.
If production tests only one thing, choose a correlated EVM+mask gate at a worst-case corner.
12) Intermittent BER spikes: alignment, LO unlock, or thermal derating—how to triage fast? H2-12
Triaging starts with correlation. If BER spikes align with RSSI/SNR dips or rain, suspect propagation or alignment drift (watch ACM downshifts). If SNR is stable but EVM collapses and unlock/reacquire counters jump, suspect LO stability. If spikes cluster near hot hours and power-backoff/derate counters increase, suspect thermal derating. Use the loopback ladder to isolate: interface loopback first if port counters look suspicious; otherwise baseband/RF loopbacks to separate radio hardware drift from over-the-air fading.
Timestamped counters are the fastest truth source: unlock, derate, ACM switches, and CRC bursts.