Case study
RF Receiver Desensitization and Intermodulation Case Study
Telecommunications case study on RF receiver desensitization, adjacent strong signals, third-order intermodulation, noise-floor rise, IIP3 screening, filtering, field evidence, and release decision.
A radio link can pass a receiver-sensitivity test and still fail in service. Sensitivity tests usually ask whether the receiver can recover a weak desired signal in a controlled noise condition. Field service also asks whether the same receiver can tolerate strong nearby signals without compression, desensitization, or intermodulation products falling into the wanted channel.
This case study follows an industrial RF telemetry receiver that intermittently loses packets even though the ordinary link budget appears adequate. The case is hypothetical and intended for engineering education. It shows how an engineer connects received signal level, thermal noise floor, required SNR, strong-signal measurements, third-order intermodulation, filtering, field evidence, and release criteria.
The central question is:
Is the radio link failing because the desired signal is too weak, or because strong adjacent signals are degrading the receiver front end?
In this case, the evidence points to receiver desensitization from third-order intermodulation, not a weak-signal coverage problem.
Case Context
An industrial plant uses a narrowband telemetry link near 919\ \text{MHz} to collect equipment status from a remote skid. The link passed initial commissioning during a quiet spectrum window. Two weeks later, packet loss appears during shift changes when nearby handheld radios and a maintenance gateway are active.
The service symptoms are:
| Symptom | Observation |
|---|---|
| received signal indication | remains near normal during failures |
| packet error rate | rises sharply during nearby transmitter activity |
| latency and jitter | worsen only during packet retries |
| antenna alignment | unchanged from commissioning record |
| weather and path condition | no correlated change |
| laboratory sensitivity test | still passes when strong adjacent signals are absent |
| field spectrum scan | shows two strong nearby carriers around the telemetry channel |
The important clue is that received signal strength is not collapsing. The link is not simply fading out. Something is reducing usable receiver margin while the desired carrier remains present.
Receiver and Field Data
Use the following simplified data from the event review:
| Quantity | Value |
|---|---|
| desired receive frequency | 919.0\ \text{MHz} |
| receiver noise bandwidth | 200\ \text{kHz} |
| receiver noise figure before fix | 7.0\ \text{dB} |
| required detector SNR | 12\ \text{dB} |
| implementation allowance | 3\ \text{dB} |
| desired signal at receiver input | P_C=-84\ \text{dBm} |
| nearby carrier 1 | f_1=920.0\ \text{MHz}, P_1=-28\ \text{dBm} |
| nearby carrier 2 | f_2=921.0\ \text{MHz}, P_2=-30\ \text{dBm} |
| receiver input third-order intercept | IIP3=-8\ \text{dBm} |
| receiver input compression point | P_{1dB}=-18\ \text{dBm} |
| required co-channel carrier-to-interference ratio | C/I_{req}=15\ \text{dB} |
The two nearby carriers are not on the wanted channel, but they are close enough and strong enough to test receiver linearity.
Thermal Noise and Required Signal
Receiver noise floor for bandwidth B is:
With:
and:
the receiver noise floor is:
Required received signal for the selected waveform is:
The measured desired signal is:
Nominal thermal margin is:
The weak-signal link budget is therefore not the primary suspect. In a clean channel, the receiver has about 15\ \text{dB} of margin.
Strong-Signal Compression Screen
First check whether the receiver is being driven into obvious front-end compression. Combine the two blocker powers approximately by converting to linear power or by using a dB power sum.
For two signals at -28\ \text{dBm} and -30\ \text{dBm}:
The receiver input compression point is:
Compression margin is:
The blockers are close enough to be concerning, but they are not clearly above the one-decibel compression point. Hard compression is possible during peaks, but the stronger explanation comes from third-order intermodulation.
Third-Order Intermodulation Check
Two strong input signals can generate third-order products at:
and:
For:
one third-order product is:
That is exactly the wanted telemetry channel.
For an input-referred third-order intercept estimate, the intermodulation product level is approximately:
Substitute:
Then:
The desired carrier is:
The carrier-to-intermodulation ratio is:
This fails the required:
by:
This is a decisive result. The receiver can have adequate thermal margin and still fail because the intermodulation product is stronger than the wanted signal.
Evidence Review
The engineering review should not rely on one equation alone. It should compare calculation with field evidence:
| Evidence | Interpretation |
|---|---|
| desired RSSI remains near -84\ \text{dBm} | coverage is not disappearing |
| packet loss correlates with two adjacent transmitters | strong-signal mechanism is plausible |
| calculated IM3 product falls at 919.0\ \text{MHz} | product is on the wanted channel |
| calculated P_{IM3} is above desired carrier | failure severity matches observed packet loss |
| clean-channel sensitivity test passes | weak-signal receiver noise is not the main issue |
| spectrum trace shows in-channel rise during blocker activity | field evidence supports intermodulation diagnosis |
| retries drive latency and jitter upward | packet service symptoms follow physical-layer impairment |
This is enough to stop treating the issue as antenna alignment or transmit-power shortage. Increasing desired transmit power might mask the symptom, but it would not remove the receiver-linearity problem and may create new coexistence issues.
Mitigation Options
The corrective action should reduce the strong signals at the nonlinear receiver stage or move the system away from the intermodulation product. Options include:
- add a preselector or cavity filter before the sensitive receiver stage;
- increase antenna separation or change antenna pattern to reject the blockers;
- move the telemetry channel away from the third-order product;
- reduce nearby transmitter power if allowed and operationally safe;
- improve receiver linearity with a higher-IIP3 front end;
- add monitoring that alarms on blocker level or packet-error bursts;
- document coexistence limits for future site changes.
For this case, the selected correction is a receive preselector that attenuates the two adjacent carriers by at least 20\ \text{dB} while adding 1.2\ \text{dB} insertion loss in the wanted channel.
Corrected Receiver Margin
After the preselector, desired carrier is reduced by insertion loss:
The noise figure worsens approximately by the same front-end loss:
New noise floor:
New required signal:
New thermal margin:
The filter costs about 2.4\ \text{dB} of thermal margin compared with the original clean-channel margin, but the link still has useful weak-signal margin.
Now attenuate the blockers:
New third-order product:
New carrier-to-intermodulation ratio:
This exceeds the 15\ \text{dB} requirement with substantial margin:
The filter slightly worsens noise-limited sensitivity, but it removes the dominant intermodulation failure mode. That is the correct tradeoff for this site.
Validation Test
The validation test should reproduce the problem and prove the correction under controlled and field conditions.
| Test | Before correction | After correction | Acceptance logic |
|---|---|---|---|
| desired carrier level | -84\ \text{dBm} | -85.2\ \text{dBm} | loss is expected from filter |
| clean-channel margin | 15\ \text{dB} | 12.6\ \text{dB} | remains above minimum margin |
| calculated IM3 product | -70\ \text{dBm} | -130\ \text{dBm} | no longer dominates channel |
| C/I against IM3 | -14\ \text{dB} | 44.8\ \text{dB} | exceeds 15\ \text{dB} requirement |
| packet error during blocker activity | high | normal baseline | validates service behavior |
| latency and jitter during retries | unstable | back to baseline | confirms packet-layer recovery |
| field spectrum at receiver | in-channel rise visible | no material in-channel rise | supports physical diagnosis |
The test record should include spectrum analyzer settings, resolution bandwidth, detector mode, antenna or coupler setup, blocker levels, receiver configuration, packet test duration, firmware version, temperature, and time of day.
Release Decision
The recommended decision is:
Release the corrected receiver installation with the preselector in place, record the measured blocker levels and accepted channel plan, set monitoring thresholds for packet-error bursts and received-signal changes, and require RF coexistence review before adding new nearby transmitters.
The decision is conditional because the fix depends on the site spectrum staying within the validated envelope. If a future transmitter is added closer to the receiver, or if blocker levels increase, the intermodulation screen must be repeated.
Failure-Mode Controls
| Failure mode | Control |
|---|---|
| intermodulation product falls in wanted channel | frequency plan and IIP3 screen |
| receiver desensitization from adjacent transmitters | preselector filter and blocker-level test |
| false weak-signal diagnosis | compare RSSI, noise floor, packet errors, and spectrum trace |
| margin consumed by added filter loss | recalculate noise floor and required signal |
| future site change reintroduces failure | configuration control and coexistence review |
| intermittent packet service symptoms misclassified as network issue | preserve physical-layer evidence and packet-layer correlation |
The strongest control is traceable evidence. A spectrum screenshot without settings is weak evidence. A packet-loss graph without RF state is weak evidence. Together, calibrated RF and service data can support a defensible engineering decision.
Engineering Lessons
The first lesson is that receiver sensitivity is not receiver robustness. A receiver can detect weak signals in a clean lab and fail near strong transmitters in the field.
The second lesson is that intermodulation is a frequency-planning problem as well as a hardware-linearity problem. Two adjacent carriers can create an unwanted product directly inside the wanted channel.
The third lesson is that adding a filter can reduce weak-signal margin while improving total system performance. Engineering review should compare both effects instead of assuming every insertion loss is bad.
The final lesson is that physical-layer failures can appear as network problems. Packet loss, latency, and jitter may be symptoms of RF front-end overload, not routing or protocol failure.