33  NB-IoT Knowledge Check

In 60 Seconds

This assessment validates your understanding of NB-IoT through scenario-based questions covering power-saving features (PSM, eDRX, coverage extension), deployment mode selection (in-band, guard-band, standalone), network architecture components, and technology selection decisions between NB-IoT and LTE-M.

33.1 Learning Objectives

By the end of this assessment, you will have:

  • Validated Understanding: Tested comprehension of NB-IoT deployment, architecture, and comparison
  • Applied Concepts: Solved practical scenarios involving technology selection and configuration
  • Identified Gaps: Recognized areas requiring additional study
  • Reinforced Learning: Strengthened knowledge through active recall

33.2 Prerequisites

Complete These Chapters First:

Estimated Time: 30 minutes

33.3 Power Saving and Coverage Quiz

Question 2: Mark each statement about NB-IoT as True (T) or False (F):
1. PSM (Power Saving Mode) allows devices to sleep deeply but they cannot receive downlink messages while in PSM
2. eDRX (Extended Discontinuous Reception) enables devices to remain reachable for mobile-terminated data while still saving power
3. NB-IoT supports full-duplex operation allowing simultaneous transmit and receive for lower latency
4. Coverage extension through repetitions improves link budget at the cost of increased latency and power consumption
1. ✓ True - In PSM, device enters deep sleep (<5 µA) and is NOT reachable by network. Device must wake and reconnect to send/receive data. Used for uplink-only applications (e.g., daily meter readings). 2. ✓ True - eDRX extends paging cycle (up to 2.91 hours) while maintaining reachability. Device wakes periodically to listen for paging. Sleep current ~15 µA. Enables mobile-terminated messaging with seconds-to-minutes latency. 3. ✗ False - NB-IoT uses half-duplex operation (transmit OR receive, never simultaneously). This reduces hardware complexity, module cost (~30% savings), and power consumption. Full-duplex not needed for IoT's asymmetric low-rate traffic. 4. ✓ True - Repetition coding transmits same message multiple times. Receiver combines copies to improve SNR (~3 dB per repetition). Up to 2048 repetitions possible. Extends coverage (+20 dB) but increases time-on-air (higher latency and energy consumption). Example: 100 repetitions × 50 ms = 5 seconds transmission time.

33.4 Scenario-Based Questions

A mobile operator has an existing LTE network with 10 MHz carriers and wants to introduce NB-IoT services. They have 900 MHz spectrum previously used for GSM that is now idle. What deployment mode options do they have, and what are the trade-offs?

  1. Only in-band mode within the LTE carriers
  2. Only standalone mode using the 900 MHz spectrum
  3. Both standalone (900 MHz) and in-band (LTE) are options, each with different trade-offs
  4. Guard-band mode only
Click to reveal answer

Answer: C) Both standalone (900 MHz) and in-band (LTE) are options, each with different trade-offs

Explanation:

The operator has multiple deployment options:

Option 1: Standalone Mode (900 MHz GSM spectrum)

Advantages: - Full 180 kHz bandwidth dedicated to NB-IoT - No impact on existing LTE services - Excellent coverage (900 MHz low-frequency propagation) - Simple network planning

Disadvantages: - Requires refarm of GSM spectrum - May need hardware upgrades if GSM still active - Separate frequency planning

Option 2: In-Band Mode (within 10 MHz LTE carrier)

Advantages: - Rapid deployment (software upgrade) - No new spectrum allocation needed - Shared infrastructure with LTE

Disadvantages: - Reduces LTE capacity slightly (1-2 PRBs = 180-360 kHz) - More complex interference management - Potential impact on LTE user experience

Recommendation for this scenario:

Deploy standalone mode in 900 MHz because: 1. Excellent coverage (low frequency) 2. No LTE impact 3. GSM spectrum is idle (no migration complexity) 4. Best customer experience for both IoT and LTE users

Use in-band mode as secondary coverage in areas without 900 MHz deployment or for capacity expansion.

An NB-IoT smart parking sensor needs to report occupancy changes immediately (event-driven) and send a daily heartbeat. It must respond to configuration commands from the platform within 1 minute. Which power-saving configuration is most appropriate?

  1. PSM with T3412 = 24 hours (lowest power)
  2. eDRX with 10-minute cycle (balance power and reachability)
  3. Normal DRX (always listening, highest power)
  4. eDRX with 1-hour cycle (longer battery, acceptable latency)
Click to reveal answer

Answer: B) eDRX with 10-minute cycle (balance power and reachability)

Explanation:

Let’s analyze the requirements:

Requirements: 1. Event-driven uplink: Report occupancy changes immediately (device-initiated) 2. Daily heartbeat: Once per 24 hours if no events 3. Downlink commands: Respond within 1 minute to configuration

Analysis of each option:

Option A: PSM with T3412 = 24 hours - Excellent battery life (< 5 µA sleep) - Can wake up immediately for events (uplink) - Cannot receive downlink while in PSM (network cannot reach device) - Config commands would wait up to 24 hours (unacceptable)

Option B: eDRX with 10-minute cycle - Good battery life (~15 µA sleep) - Can wake up immediately for events (uplink) - Reachable for downlink every 10 minutes - Config commands delivered within 10 min (< 1 min requirement on average) - Slightly higher power than PSM

Option C: Normal DRX - Always reachable (seconds latency) - Fast downlink delivery - High power consumption (1-5 mA continuous) - Battery life measured in months, not years

Option D: eDRX with 1-hour cycle - Better battery life than shorter eDRX - Can wake for events - Config commands wait up to 1 hour (exceeds 1 min requirement)

Why Option B is optimal:

  1. Uplink (events): Device can wake anytime to report occupancy change
  2. Downlink (config): With 10-minute eDRX cycle, device listens for paging every 10 minutes
    • Average latency for downlink: 5 minutes (half the cycle)
    • Maximum latency: 10 minutes (end of cycle)

Current consumption estimate for Option B: - Sleep (eDRX): 15 µA × 99% time - Paging window: 50 mA × 1% time - Average: ~0.5 mA → 5-10 year battery life with 5 Ah battery

Note: If strict < 1 minute downlink is required, eDRX cycle should be configured < 2 minutes.

An NB-IoT water meter is deployed in a basement with significant signal attenuation. The link budget shows 150 dB coupling loss. The eNodeB needs to communicate reliably. How does NB-IoT achieve this, and what are the trade-offs?

  1. Use higher transmit power (> 23 dBm) to overcome path loss
  2. Use message repetitions to improve SNR through processing gain
  3. Switch to LTE-M which has better coverage
  4. Deploy a local repeater/amplifier
Click to reveal answer

Answer: B) Use message repetitions to improve SNR through processing gain

Explanation:

NB-IoT is designed for 164 dB Maximum Coupling Loss (MCL), which is more than sufficient for this 150 dB scenario. The key technique is repetition coding.

How repetition coding works:

  1. Transmit the same message multiple times on the physical layer
  2. Receiver combines all copies (maximal ratio combining)
  3. Each repetition improves SNR by ~3 dB

Link budget for 150 dB coupling loss: - Device TX power: +23 dBm - eNB RX sensitivity (normal): -141 dBm (after processing gain) - Maximum path loss supported: 23 - (-141) = 164 dB MCL - Link margin: 164 - 150 = 14 dB margin - comfortable!

Coverage classes: - Class 0: Normal coverage (no/minimal repetitions) - Latency: < 1 second - Class 1: Extended coverage (10-100 repetitions) - Latency: 1-10 seconds - Class 2: Extreme coverage (up to 2048 repetitions) - Latency: > 10 seconds

Trade-offs of repetition:

Advantages: - No additional hardware cost - Automatic in NB-IoT protocol - Effective coverage enhancement

Disadvantages: - Increased latency: Each repetition adds transmission time - Higher power consumption: More transmissions = more energy - Reduced capacity: More air time per device = fewer devices per cell

Why other options are incorrect:

Option A: Higher transmit power - NB-IoT devices are limited to 23 dBm (200 mW) by standard - Regulatory limits prevent higher power - Not a practical solution

Option C: Switch to LTE-M - LTE-M has 156 dB MCL vs NB-IoT’s 164 dB MCL - NB-IoT has BETTER coverage than LTE-M (by 8 dB) - LTE-M would perform worse in this scenario

Option D: Deploy repeater - Expensive additional hardware - Maintenance burden - Not necessary when NB-IoT coverage is already sufficient

33.5 Technology Selection Quiz

Question 6: For a smart water meter deployment requiring 15-year battery life, deep basement coverage, and 100 bytes/day transmission, which technology is BEST?
Technology Bandwidth Latency Mobility Battery Life Coverage (MCL) Select
NB-IoT 250 kbps 1.6-10 sec Limited 10+ years 164 dB
LTE-M 1 Mbps 10-15 ms Full handover 5-10 years 156 dB
EC-GSM-IoT 70-240 kbps 700-1400 ms Full 5-10 years 164 dB
4G LTE 100 Mbps 20-50 ms Full Months 142 dB
💡 Explanation: NB-IoT is optimal for this smart metering application: Coverage: 164 dB Maximum Coupling Loss matches deep basement requirements (+20 dB vs GPRS, +8 dB vs LTE-M). Battery Life: 10+ years with PSM mode (5 µA sleep current), perfect for 15-year target. Bandwidth: 250 kbps easily handles 100 bytes/day (0.008 kbps average). Cost: Lowest module cost ($8-12) and data plans. Stationary: No mobility needed for fixed meters. LTE-M offers unnecessary mobility features at higher power. EC-GSM-IoT is being phased out with 2G sunset. 4G LTE consumes too much power for battery operation.

33.6 Comprehensive Review Quiz

33.7 Cross-Hub Connections

Explore NB-IoT Across Learning Resources

Explore NB-IoT across learning resources:

  • Videos Hub: Watch cellular IoT deployment tutorials, NB-IoT vs LTE-M comparisons, and real-world smart metering implementations
  • Quizzes Hub: Test your NB-IoT knowledge with interactive assessments on deployment modes, power-saving modes, and coverage enhancement techniques
  • Simulations Hub: Experiment with NB-IoT link budget calculators, PSM/eDRX power consumption simulators, and deployment mode decision tools
  • Knowledge Gaps Hub: Address common misconceptions about NB-IoT mobility support, latency characteristics, and comparison with LoRaWAN

33.8 Summary

This knowledge check covered:

  • Deployment modes: In-band (2% LTE impact), guard-band (zero impact), standalone (dedicated spectrum)
  • Power-saving modes: PSM (<5 µA, not reachable), eDRX (15 µA, reachable), trade-offs
  • Coverage enhancement: Repetition coding for 164 dB MCL, latency/power trade-offs
  • Technology selection: NB-IoT vs LTE-M based on mobility, latency, power requirements
  • Practical scenarios: Smart metering, asset tracking, cold chain logistics

33.9 What’s Next

Continue your learning journey: