Exercise set
Digital Modulation and Coding Exercises
Practice digital modulation and coding problems for symbol rate, Eb/N0, MCS, OFDM, EVM, BER, HARQ, ACLR, LLR and fallback gates.
These exercises practise digital modulation and coding calculations as engineering review work. They connect payload rate, coded bit rate, symbol rate, occupied bandwidth, signal-to-noise ratio, E_b/N_0, modulation-and-coding selection, coding gain, OFDM overhead, spectral mask, ACLR, residual carrier-frequency offset, inter-carrier interference, phase-noise EVM, packet error, HARQ goodput, fallback service impact, interleaving latency, decoder resources, soft-decision quantization, BER confidence and validation margins.
Assume simplified screening models unless an exercise states otherwise. Real systems also require standard-specific framing, measured channel data, synchronization behavior, nonlinear distortion, phase noise, adjacent-channel interference, regulatory constraints, firmware settings, calibrated instruments and service acceptance criteria.
Release Evidence Notes
Use these exercises as screening evidence for waveform and modem-release decisions, not as proof that a selected mode will hold in service. A credible release should connect each calculation to the rate boundary, channel condition, modem configuration, impairment state, measurement setup, traffic objective and fallback action being controlled.
The minimum evidence set is:
- rate evidence for payload, coded, physical-layer and application throughput boundaries, framing overhead, pilot overhead, guard intervals, retransmissions, scheduling gaps and service acceptance target;
- channel evidence for received power, noise density, SINR, interference occupancy, fading state, delay spread, Doppler, phase noise, carrier-frequency offset and temperature range;
- modem evidence for MCS table, coding rate, interleaver depth, decoder settings, LLR quantization, HARQ policy, synchronization lock state, equalizer state, firmware version and fallback hysteresis;
- measurement evidence for instrument calibration, reference plane, bandwidth, averaging, capture duration, traffic mix, packet size, confidence level, EVM method, BER/PER counter behavior and clock stability;
- validation evidence for lab-to-field correlation, packet-error target, latency budget, goodput under load, burst-error behavior, route or antenna state, alarms, rollback rule and release authority.
Treat a numerical pass as provisional when it depends on clean-channel SNR, nominal MCS thresholds, zero observed errors, average EVM, ideal coding gain, a single channel capture or a lab impairment profile that does not match the field. MCS, OFDM, HARQ, BER and LLR decisions should support release only when the evidence covers the same waveform, traffic class, receiver state and service margin.
How to Use These Exercises
For each problem:
- define whether the rate is payload, coded, line, physical-layer or application throughput;
- keep dB ratios separate from absolute units such as dBm;
- state the modulation order, coding rate, overhead boundary and bandwidth convention;
- reserve margin for implementation loss, interference, fading, temperature and measurement uncertainty;
- identify the field or laboratory evidence that would validate the calculation.
The common mistake is to select a high-order modulation mode from a clean formula without checking the operating boundary. A credible release decision connects rate accounting, SNR, coding, error behavior, latency and validation evidence.
Engineering Boundary Notes
Digital modulation evidence must identify the rate boundary before any MCS decision is accepted. Payload rate, coded bit rate, symbol rate, occupied bandwidth, application goodput and fallback goodput are not interchangeable. Overheads, pilots, guard intervals, retransmissions, scheduler gaps and packetization should be visible in the same boundary as the requirement.
Link-quality evidence also has a boundary. SNR, E_b/N_0, EVM, SINR, BER, PER, HARQ success and post-FEC counters answer different questions. A clean E_b/N_0 calculation does not prove phase-noise margin, CFO tolerance, inter-carrier interference, adjacent-channel compliance, decoder memory, latency or burst-error recovery.
Validation should match the deployed receiver state. MCS release depends on firmware version, synchronization loop settings, channel-estimation method, equalizer state, LLR quantization, confidence level, traffic mix, temperature and impairment profile. If the field channel differs from the lab model, the calculation should be treated as a hypothesis to test, not as release evidence.
Common Release Mistakes
- quoting payload throughput while the calculation used coded or physical-layer rate;
- selecting a high-order MCS from clean SNR while ignoring interference, phase noise, CFO or EVM reserve;
- treating zero observed errors as proof without confidence level, bit count and test duration;
- accepting BER while packet error, HARQ latency or backlog growth violates the service objective;
- applying coding gain without checking decoder settings, interleaver depth, LLR precision and implementation loss;
- passing a spectral mask without checking ACLR, power backoff and adjacent-channel coexistence;
- using fallback MCS as a safety net without verifying recovery time and degraded goodput.
Scenario Map
| Scenario | Main calculation | Engineering decision |
|---|---|---|
| Rate accounting | payload, coded bit rate, symbol rate and occupied bandwidth | Check that throughput claims use the right boundary. |
| Link margin | SNR, E_b/N_0, EVM and release reserves | Select a mode that still works outside ideal lab conditions. |
| OFDM timing | cyclic prefix, pilot spacing, pilot overhead and delay-spread margin | Balance robustness, throughput, channel-estimation cost and mobility/frequency-selective fading evidence. |
| Receiver impairment | residual CFO, ICI, phase noise and EVM margin | Decide whether synchronization error blocks a high-order MCS. |
| Transmitter emission | spectral mask and ACLR guard | Decide whether waveform shaping, backoff or predistortion is needed before field release. |
| Error behavior | BER, PER, HARQ, interleaving, decoder latency and soft-decision quantization | Convert bit errors into service impact. |
| Adaptive fallback | fallback MCS, HARQ goodput, backlog growth and latency recovery | Decide whether a degraded link remains usable for the offered traffic. |
| Validation evidence | confidence intervals, traffic tests and release margin | Decide whether the measured evidence is strong enough for release. |
Validation Package Checklist
Before treating a modulation or coding result as release evidence, collect:
- required payload, coded, physical-layer and application-rate boundaries;
- modulation order, coding rate, overheads, symbol rate and occupied bandwidth;
- SNR, E_b/N_0, SINR, EVM, BER, PER and HARQ target definitions;
- channel condition, interference state, phase noise, CFO, Doppler and delay spread;
- modem firmware, MCS table, synchronization, equalizer and decoder settings;
- spectral mask, ACLR, backoff and regulatory or coexistence constraints;
- test duration, confidence level, traffic mix, instrument calibration and uncertainty allowance;
- release decision, fallback rule, rollback criterion or additional validation test.
Exercise 1: Symbol Rate and Occupied Bandwidth
A digital link must carry:
of payload traffic. The waveform uses 16-QAM, coding rate:
and overhead for pilots, framing and control:
The raised-cosine roll-off factor is:
Find the gross coded bit rate, symbol rate, approximate occupied bandwidth and payload spectral efficiency.
Solution
16-QAM carries:
Gross coded bit rate required at the mapper boundary:
Symbol rate:
Approximate occupied bandwidth:
Payload spectral efficiency:
Engineering Comment
The payload rate is not the same as the coded bit rate. Coding and overhead raise the physical-layer rate to 179.2\ \text{Mbit/s} before pulse shaping sets the occupied bandwidth. If an engineer used 120\ \text{Mbit/s} directly in the symbol-rate calculation, the bandwidth estimate would be too low and the spectrum plan would be optimistic.
Plausibility Check
An uncoded 16-QAM stream could carry 4\ \text{bit/symbol}, but the net result is only 2.14\ \text{bit/s/Hz} after coding, overhead and roll-off. That is plausible for a practical robust mode.
Exercise 2: Eb/N0 From Measured SNR
A receiver reports:
over a noise bandwidth:
The selected modulation-and-coding mode has a coded bit rate:
The mode requires:
for the target error rate, plus:
of implementation and measurement allowance. Find the available E_b/N_0 margin.
Solution
Use the dB conversion:
Substitute the values:
Therefore:
Required value including allowance:
Margin:
Engineering Comment
The mode passes, but only by about 0.7\ \text{dB}. That is a thin margin for a fielded system. If interference, temperature drift, antenna misalignment, phase noise or calibration uncertainty is worse than assumed, the selected mode may become unstable.
Plausibility Check
Because the coded bit rate is higher than the noise bandwidth, E_b/N_0 is lower than SNR. That direction is correct: the energy assigned to each bit is spread across a high bit rate.
Exercise 3: Modulation-and-Coding Selection With Release Margin
A field link has measured:
The release rule reserves:
for fading and interference plus:
for measurement uncertainty. Candidate modes are:
| Mode | Net spectral efficiency before protocol overhead | Required SNR |
|---|---|---|
| QPSK, rate 1/2 | 1.0\ \text{bit/s/Hz} | 4.0\ \text{dB} |
| 16-QAM, rate 3/4 | 3.0\ \text{bit/s/Hz} | 16.0\ \text{dB} |
| 64-QAM, rate 2/3 | 4.0\ \text{bit/s/Hz} | 22.0\ \text{dB} |
The channel bandwidth is:
Protocol overhead after the physical layer is:
Choose the highest releasable mode and estimate payload throughput.
Solution
Usable SNR after release reserves:
Compare with the required values:
| Mode | Required SNR | Passes with 16.5\ \text{dB} usable? |
|---|---|---|
| QPSK, rate 1/2 | 4.0\ \text{dB} | yes |
| 16-QAM, rate 3/4 | 16.0\ \text{dB} | yes |
| 64-QAM, rate 2/3 | 22.0\ \text{dB} | no |
The highest releasable mode is 16-QAM, rate 3/4.
Payload throughput estimate:
Engineering Comment
The measured SNR might seem close to 64-QAM operation if the reserves are ignored. With release reserves included, 64-QAM is clearly not acceptable. The correct decision is not the highest mode that works in a short test. It is the highest mode that still meets margin and service evidence.
Plausibility Check
The selected net spectral efficiency is 3\ \text{bit/s/Hz} before protocol overhead, so a 10\ \text{MHz} channel producing about 27\ \text{Mbit/s} payload is consistent.
Exercise 4: OFDM Cyclic Prefix, Overhead and Delay-Spread Margin
An OFDM waveform uses subcarrier spacing:
The cyclic prefix duration is:
The channel survey estimates maximum excess delay:
and the release rule reserves:
for measurement uncertainty and channel variation. The waveform has 600 active subcarriers, QPSK modulation and coding rate 1/2. Pilot and control overhead remove 12\% of physical-layer capacity.
Find useful symbol time, cyclic-prefix efficiency, delay-spread margin and estimated payload throughput.
Solution
Useful OFDM symbol time is approximately:
Total OFDM symbol time:
Cyclic-prefix efficiency:
Delay-spread margin:
QPSK carries:
Coded useful bits per OFDM symbol before pilot/control overhead:
Physical-layer rate before pilot/control overhead:
Payload rate after pilot/control overhead:
Engineering Comment
The cyclic prefix passes the delay-spread screen with 0.8\ \mu\text{s} margin, but it also consumes time. The release decision must include both timing robustness and throughput. If the channel delay increases because of a new reflector, antenna change or industrial structure, the margin may disappear even though received power is unchanged.
Plausibility Check
The cyclic-prefix efficiency of about 93.4\% is plausible for this spacing and guard interval. A payload near 7.4\ \text{Mbit/s} is also plausible because QPSK and rate-1/2 coding are robust but not spectrally aggressive.
Exercise 5: Packet Error Rate From Bit Error Rate
A decoder reports post-correction bit error rate:
The service transports frames of:
Assume independent residual bit errors for this screening calculation. Estimate packet error rate. The service requirement is:
Find the maximum acceptable residual BER for this frame size. Decide whether the mode passes.
Solution
Frame length:
Packet error rate for independent residual bit errors is:
For small BER, a useful approximation is:
Therefore:
The estimated packet error rate is about:
Maximum residual BER for the required packet error rate:
The reported residual BER:
so the mode does not pass the packet error requirement.
Engineering Comment
A residual BER that looks numerically small can still produce too many packet errors when frames are long or traffic volume is high. If the system carries retransmitted data, the service may slow down instead of visibly failing. If it carries real-time control or voice, the same residual errors may be unacceptable.
Plausibility Check
For rare independent bit errors, multiplying by frame length is a reasonable first screen. If errors are bursty, the independent model can be misleading. Interleaving, coding, packet size, fading and interference records should be reviewed before release.
Exercise 6: Interleaving Depth and Latency Tradeoff
A receiver sees burst interference events lasting:
The coded system processes one codeword every:
The decoder can correct at most 3 corrupted codeword positions within one interleaving span. A block interleaver of depth D spreads a contiguous burst so that the approximate number of affected positions per decoded block is:
where:
The service allows no more than:
of added interleaver latency. Choose a practical interleaver depth.
Solution
Number of codeword intervals hit by the burst:
The decoder condition is:
Test D=3:
So D=3 is the minimum depth that meets the correction condition.
Added latency is approximately:
For D=3:
This is below the 2.0\ \text{ms} service limit.
A conservative choice is D=4:
and:
The practical selection is D=4 if memory and implementation constraints allow it.
Engineering Comment
Interleaving improves burst-error tolerance by spreading a localized disturbance across a longer coded block. It also adds latency and memory demand. The best depth is therefore not the largest possible value. It is the smallest value that gives correction margin while staying within the service latency budget.
Plausibility Check
The selected D=4 converts an 8-codeword burst into about 2 affected positions per decoded block, below the correction limit of 3. The added latency remains half of the service limit, leaving room for buffering, scheduling and processing variation.
Exercise 7: EVM-Based MCS Release Decision
A test receiver reports RMS error vector magnitude:
A common screening approximation is:
The release process subtracts:
- 0.8\ \text{dB} for instrument uncertainty;
- 1.2\ \text{dB} for implementation variation;
- 1.5\ \text{dB} for expected interference variation.
Candidate modes require:
| Mode | Required SNR before release reserves |
|---|---|
| 16-QAM, rate 3/4 | 16.0\ \text{dB} |
| 64-QAM, rate 3/4 | 21.5\ \text{dB} |
| 256-QAM, rate 3/4 | 28.0\ \text{dB} |
The policy also requires at least 2.0\ \text{dB} margin above the selected mode. Select the highest releasable mode.
Solution
Estimate linear SNR:
Convert to dB:
Subtract release reserves:
Required SNR including the 2.0\ \text{dB} policy margin:
| Mode | Required including policy margin |
|---|---|
| 16-QAM, rate 3/4 | 18.0\ \text{dB} |
| 64-QAM, rate 3/4 | 23.5\ \text{dB} |
| 256-QAM, rate 3/4 | 30.0\ \text{dB} |
The usable SNR is:
This is slightly below the 64-QAM release requirement:
Therefore the highest releasable mode is 16-QAM, rate 3/4.
Engineering Comment
The result is intentionally close. A short lab test might tempt the team to release 64-QAM, but the documented reserves make it fail by a small amount. In production engineering, a 0.06\ \text{dB} shortfall should not be hidden by rounding if the acceptance policy is explicit. The right response is to release the lower mode or gather stronger evidence that reduces uncertainty.
Plausibility Check
An EVM of 4.5\% corresponds to an idealized SNR near 27\ \text{dB}. After realistic reserves, the usable value is closer to 23.4\ \text{dB}, which is plausible for robust 16-QAM and marginal for 64-QAM.
Exercise 8: Coding Gain Versus Throughput Loss
A QPSK link is evaluated in two modes at the same symbol rate:
Uncoded QPSK requires:
for the target BER. A coded QPSK mode with code rate:
requires:
but adds:
of implementation loss. Protocol overhead after decoding is 8\%. Compute gross bit rates, net payload rate and effective coding gain.
Solution
QPSK carries:
Uncoded gross bit rate:
Coded information bit rate before protocol overhead:
Payload after protocol overhead:
Nominal coding gain:
Effective gain after implementation loss:
Engineering Comment
Coding improves the energy margin but reduces information throughput at a fixed symbol rate. The right decision depends on service objective: weak-signal coverage, packet reliability, latency, spectrum efficiency or peak throughput. A coding gain should not be quoted without the rate and implementation boundary.
Plausibility Check
Rate-1/2 coding roughly halves the information rate before overhead, so a payload near 9.2\ \text{Mbit/s} from a 20\ \text{Mbit/s} QPSK symbol stream is plausible.
Exercise 9: HARQ Retransmission Goodput
Use the payload rate selected in Exercise 3:
The measured packet error rate before retransmission is:
Assume independent packet errors and at most one HARQ retransmission. Estimate probability of delivery within two attempts, average transmissions per original packet, effective goodput and residual packet loss.
Solution
Probability of delivery within two attempts:
Average transmissions per original packet with one possible retry:
Effective goodput:
Residual packet loss after the retry:
or:
Engineering Comment
HARQ can hide many first-pass packet errors, but it consumes airtime and adds delay. Goodput, residual loss and latency should all be reported. A high physical-layer rate with frequent retransmission may deliver less useful service than a lower MCS with fewer retries.
Plausibility Check
An 8\% first-pass packet error rate should reduce goodput by roughly the same order because retries consume extra transmissions. The computed drop from 27.27 to 25.1\ \text{Mbit/s} is consistent.
Exercise 10: Pilot Overhead Sensitivity in an OFDM Mode
Use the physical-layer OFDM rate before pilot and control overhead from Exercise 4:
The original overhead was 12\%. A mobility update increases pilot and control overhead to:
Compute the new payload rate, absolute throughput loss and percentage loss relative to the original 7.40\ \text{Mbit/s} payload rate.
Solution
New payload rate:
Absolute loss:
Percentage loss:
or:
Engineering Comment
Pilot overhead is not wasted if it keeps channel estimates valid, but it is still a throughput cost. Mobility, Doppler, phase noise and frequency-selective fading can force more reference symbols. The MCS decision should include this overhead rather than comparing only nominal modulation order.
Plausibility Check
Raising overhead from 12\% to 20\% removes an additional 8\% of the physical rate. A throughput loss near 9\% relative to the original payload rate is therefore reasonable.
Exercise 11: Decoder Memory and Latency Budget
A receiver uses soft-decision decoding with:
Soft information is stored with:
The interleaver depth selected for a robust mode is:
There are two spatial streams. Available decoder buffer memory is:
Decoder processing time is 0.18\ \text{ms} per codeword, interleaver latency is 1.0\ \text{ms} and framing latency is 0.25\ \text{ms}. Check memory use and latency against a 2.0\ \text{ms} service limit.
Solution
Buffer memory in bits:
Convert to bytes:
Therefore:
Memory margin:
Total latency:
Latency margin:
The configuration fits both memory and latency limits.
Engineering Comment
Coding and interleaving are implementation choices as well as link-budget choices. A mode that looks good in E_b/N_0 may fail in an embedded receiver if soft-buffer memory, decoding time, power, thermal limits or service latency are not available.
Plausibility Check
Four interleaver depths, two streams and 6-bit soft values multiply memory quickly. A result near 25\ \text{kB} is plausible for a modest codeword size and explains why buffer budgeting belongs in the modulation-and-coding review.
Exercise 12: Zero-Error BER Confidence Test Duration
A release test wants to demonstrate:
with 95\% confidence using a zero-error test. For a Poisson rare-error approximation, the required number of tested bits is:
where C is confidence. The test bit rate is:
A proposed test duration is 60\ \text{s}. Determine required bits, required duration and whether the proposed test is long enough.
Solution
For 95\% confidence:
Required bits:
Required duration:
Bits in the proposed 60\ \text{s} test:
Zero-error upper BER from the proposed test:
The proposed zero-error test is not long enough to demonstrate 1.0\times10^{-9} at 95\% confidence.
Engineering Comment
Short successful tests can be statistically weak. A release report should state tested bits, confidence method, error count, traffic pattern, channel condition and whether the test covers burst errors as well as random errors. Zero observed errors is not the same as zero error probability.
Plausibility Check
At 25\ \text{Mbit/s}, testing about 3\times10^9 bits should take about two minutes. A 60\ \text{s} test covers only half that evidence, so its confidence bound should be about twice the target BER.
Exercise 13: Residual Carrier-Frequency Offset and OFDM ICI Margin
An OFDM receiver uses subcarrier spacing:
After carrier recovery, the measured residual carrier-frequency offset is:
The receiver has baseline RMS EVM from noise, equalization error and quantization of:
For a small normalized CFO, use the screening approximation:
where:
The 64-QAM release budget allows total RMS EVM no greater than:
A revised carrier-recovery setting reduces residual CFO to:
Estimate ICI power, equivalent ICI EVM, total EVM before and after retuning, and decide whether 64-QAM should be released.
Solution
Normalized CFO before retuning:
ICI power ratio:
In dB relative to the wanted subcarrier power:
Equivalent ICI EVM:
Combine independent EVM terms by root-sum-square:
Release margin before retuning:
The initial condition fails the 64-QAM EVM release budget.
After retuning:
New ICI power ratio:
In dB:
New equivalent ICI EVM:
New total EVM:
New EVM margin:
ICI improvement from retuning:
The revised carrier-recovery setting makes 64-QAM releasable under this EVM budget, provided the measured PER and synchronization logs also pass.
Engineering Comment
Residual CFO in OFDM is not just a frequency-label error. It breaks subcarrier orthogonality and creates inter-carrier interference, so the impairment appears as EVM and can erase MCS margin even when received power is adequate. The release decision should use measured residual CFO, EVM, PER, carrier-loop state and channel conditions together.
Plausibility Check
The first residual CFO is only 2.8\% of the subcarrier spacing, yet it creates an ICI EVM term near 5\% under the screening model. Reducing the offset to 0.8\% of spacing lowers ICI power by about 11\ \text{dB}, which is consistent with the square-law dependence on normalized CFO.
Exercise 14: Soft-Decision LLR Quantization and Decoder Memory
A receiver stores soft-decision log-likelihood ratios, or LLRs, for a forward-error-correction decoder. The demapper clips LLRs to:
A proposed implementation uses:
per LLR value. Treat the quantizer as using 2^b uniformly spaced levels across the full range. The decoder team estimates that RMS LLR quantization noise should be no greater than:
in LLR units for the selected mode. Each codeword has:
The receiver stores:
spatial streams and:
HARQ processes. Compare the 4-bit and 5-bit LLR options for quantization step, RMS quantization noise, soft-buffer memory and release decision.
Solution
The full LLR range is:
For b bits, the number of quantization levels is:
Using endpoint-spaced levels, the step size is:
For 4-bit LLR storage:
Uniform quantization noise RMS is:
Therefore:
The 4-bit option fails the quantization-noise allowance:
Soft-buffer memory for the 4-bit option:
For 5-bit LLR storage:
The 5-bit option passes the quantization-noise allowance:
Soft-buffer memory for the 5-bit option:
Memory increase:
Relative memory increase:
The 5-bit option should be selected if the receiver can absorb the extra 1.0\ \text{kB} of soft-buffer memory and the associated bandwidth or latency cost.
Engineering Comment
Soft-decision precision is part of the link implementation, not only a firmware detail. Coarse LLR quantization can erase coding gain even when measured SNR and EVM look acceptable. The release decision should connect BER or PER evidence with LLR clipping statistics, quantizer range, soft-buffer memory, decoder latency, HARQ depth and worst-case MCS.
Plausibility Check
The 4-bit quantizer spans 16 LLR units with only 15 intervals, so a step slightly above 1 LLR unit is expected. Its RMS quantization noise is about 0.31, above the 0.25 allowance. Adding one bit roughly halves the step and reduces RMS noise to 0.149, while memory grows by 1/4 because the stored word width rises from 4 to 5 bits.
Exercise 15: Phase-Noise EVM Budget for MCS Release
A receiver team wants to release a 64-QAM mode. The measured integrated RMS phase error from oscillator phase noise over the receiverโs relevant bandwidth is:
Other measured implementation impairments, excluding phase noise, contribute RMS EVM of:
The 64-QAM mode has an RMS EVM limit of:
The release policy reserves:
as guard margin below the limit. Use the small-angle screen:
where EVM_{\phi} is a linear ratio. Combine independent RMS EVM contributions by root-sum-square. Then check an improved oscillator with:
Solution
Convert phase error to radians:
Phase-noise EVM contribution is approximately:
Combine RMS EVM contributions:
The guarded EVM limit is:
Guarded EVM margin is:
The receiver is inside the raw 8.0\% EVM limit but fails the guarded release rule.
For the improved oscillator:
New phase-noise EVM contribution:
New total RMS EVM:
New guarded margin is:
The improved oscillator passes the guarded EVM release screen.
Engineering Comment
Phase noise is not interchangeable with a static carrier-frequency offset. CFO can often be estimated and corrected as a deterministic frequency error, while phase noise spreads constellation points over time and can raise EVM even when average SNR looks good. The integration bandwidth, receiver tracking loop, symbol rate, pilot structure and measurement method must therefore be stated with the phase-error number.
The root-sum-square combination is a screening model. It assumes the EVM contributors are independent and RMS-like. If phase noise, nonlinear distortion, IQ imbalance, clipping or equalizer error are correlated with the same operating condition, a measured constellation and BER/PER test under that condition should override the simplified budget.
Plausibility Check
A phase error of 3.2^\circ is about 0.056\ \text{rad}, so an EVM contribution near 5.6\% is expected. Combining that with an existing 4.5\% implementation EVM gives a total a little above 7\%, which explains why the raw limit passes but the guarded release fails. Reducing phase error to 2.2^\circ lowers the phase-noise contribution enough to recover about one percentage point of guarded EVM margin.
Exercise 16: OFDM Pilot Spacing and Coherence Margin
An OFDM modem is being released for a moving field channel. The current pilot grid has time spacing:
and frequency spacing:
Channel measurements estimate coherence time:
and coherence bandwidth:
The release rule requires pilot spacing no larger than half of each coherence measure:
The current pilot overhead is:
and the physical-layer rate before pilot overhead is:
A revised pilot grid uses:
Assume pilot overhead scales inversely with the pilot spacing product: