NB-IoT Coverage Enhancement Workbench

Explore how NB-IoT uses repetition and coverage enhancement levels to close difficult cellular IoT links.

Learner-ready NB-IoT coverage enhancement workbench with repetition gain, CE level selection, MCL margin, latency and battery trade-offs, channel-specific repetition limits, deployment scenarios, source links, and local desktop/mobile visual verification.

Cellular IoT Coverage enhancement Repetition trade-off

NB-IoT Coverage Enhancement Workbench

Adjust deployment loss, physical channel, and repetition count to see whether an NB-IoT device closes the link. The important lesson is not just "more repetitions"; it is the trade-off between margin, latency, data rate, and energy.

Diagnosis CE Level 1 gives enough margin without moving into the highest latency mode.

CE level CE Level 1

MCL margin 5.0 dB

Current phase Estimate loss

MCL Maximum coupling loss is the largest path loss a link can tolerate. If required loss is above MCL, the device is not reliably reachable.

Repetition NB-IoT can send the same physical-channel information many times so the receiver can combine energy across attempts.

Processing gain Ideal repetition gain is about 10 log10(N) dB. Practical coverage gain is capped and depends on channel and implementation.

Trade-off More repetitions improve reachability but reduce effective rate, stretch latency, and keep the radio active longer.

Scenario set

Coverage controls

Try a realistic deployment, then step through how the network chooses coverage enhancement.

Scenario

Physical channel focus NPUSCH uplink data NPDSCH downlink data NPDCCH downlink control NPRACH random access

Deployment environment Outdoor cabinet or roofline Indoor utility room Deep basement or meter room Underground car park Rural long-range cell edge

Repetitions

16 repetitions, ideal +12.0 dB

Required coupling loss

151 dB needed

Payload size

48 byte payload

Reporting interval Hourly sensor reading Daily meter read Alarm or event burst Downlink command response

Guided task flow

Cell site Loss and combining IoT device

Roof

Floor 3

Floor 2

Floor 1

Basement

Core network scheduler and RRC config

NB-IoT cell 180 kHz carrier

Repetition plan 16 copies

IoT device indoor meter

Estimate the link loss Start with the required coupling loss for the deployment. Deep indoor and underground locations need more link budget than outdoor devices.

Coverage decision

The result is a margin decision, not a promise that every device at that location will work.

Link budget bars

These bars separate required loss, available MCL, and the practical cost of repetitions.

Channel and CE level

The allowed repetition range depends on whether the message is access, control, uplink data, or downlink data.

Event log

Each row links the animation to an engineering decision.

MCL target NB-IoT is commonly planned around up to about 164 dB maximum coupling loss, but field validation is still required.

CE Level 0 Normal coverage. Low repetition, lower latency, and better effective throughput.

CE Level 1 Extended coverage. Moderate repetition for indoor rooms and weaker cell-edge links.

CE Level 2 Extreme coverage. Useful for basements and underground deployments, but latency and energy cost dominate.

Technical notes and primary sources

Ideal versus practical gain The ideal teaching estimate is 10 log10(N) dB for N repetitions. Real systems cap useful coverage improvement because coding, scheduling, channel estimation, interference, and implementation limits matter.

Repetition is per physical channel Access, control, uplink data, and downlink data can have different repetition settings. A single slider here is a teaching focus, not a full base-station scheduler.

Battery impact PSM and eDRX help between reports. During a repeated transmission, however, the radio stays active longer, so coverage and battery targets must be planned together.

3GPP TS 36.300: E-UTRA and E-UTRAN overall description 3GPP TS 36.211: E-UTRA physical channels and modulation 3GPP TS 36.213: E-UTRA physical layer procedures 3GPP TS 36.331: Radio Resource Control protocol 3GPP TR 45.820: Cellular system support for ultra-low complexity and low-throughput IoT

Practice prompts

Basement meter Choose the basement scenario. Reduce repetitions until the MCL margin becomes weak, then explain the latency and battery trade-off.

Downlink control Switch to NPDCCH or NPDSCH and compare the allowed repetition range with uplink data.

Impossible location Set required coupling loss above 164 dB. Decide whether a repeater, antenna change, denser cell plan, or another LPWAN should be considered.