4  NB-IoT Technical Specifications

Bandwidth, Data Rates, and Deployment Modes

In 60 Seconds

NB-IoT operates in 180 kHz bandwidth (one LTE PRB), delivers 25-250 kbps data rates with 164 dB maximum coupling loss, and supports three deployment modes (standalone, guard-band, in-band) across 3GPP Releases 13-17, evolving from basic connectivity to features like multicast, MIMO, and 5G RedCap integration.

Key Concepts

• NB-IoT Physical Layer: SC-FDMA uplink (single-carrier), OFDMA downlink; 15 kHz or 3.75 kHz subcarrier spacing; 200 kHz channel bandwidth (1 PRB)
• Modulation Schemes: NB-IoT uses: BPSK and QPSK for NPUSCH; QPSK for NPDSCH; BPSK for NPRACH; simpler modulation than LTE for robustness in poor coverage
• Peak Data Rates: DL: 250 kbps (15 kHz, multi-tone, no repetitions); UL: 250 kbps (multi-tone) or 20 kbps (single-tone 3.75 kHz); practical rates 5–50 kbps
• Frequency Bands: NB-IoT operates on dedicated LTE frequency bands; key global bands: Band 1 (2100 MHz), Band 3 (1800 MHz), Band 8 (900 MHz), Band 20 (800 MHz), Band 28 (700 MHz)
• UE Power Classes: PC3 = 23 dBm (standard IoT), PC5 = 20 dBm (low power), PC6 = 14 dBm (ultra-low power for small form factor)
• Receiver Sensitivity: NB-IoT minimum sensitivity: -114 dBm (DL), -114 dBm (UL); with CE Mode B and 2048 repetitions: effectively -130 to -137 dBm
• NB-IoT Frame Structure: Based on LTE frame structure; 10 ms radio frames, 1 ms subframes; NB-IoT uses 1 PRB (200 kHz) anchored within LTE carrier or standalone
• Inter-Band CA: NB-IoT does NOT support carrier aggregation — intentional simplification to reduce modem complexity and cost compared to LTE UE

Prerequisites: NB-IoT Introduction | Cellular IoT Fundamentals

This enables: NB-IoT Architecture | NB-IoT Power Optimization

4.1 Learning Objectives

By the end of this chapter, you will be able to:

• Analyze technical specifications: Differentiate NB-IoT bandwidth, data rate, and latency characteristics across operating configurations
• Evaluate deployment modes: Justify the selection of standalone, guard-band, or in-band deployment for a given operator scenario
• Calculate coverage margins: Compute link budgets using the 164 dB MCL and determine repetition levels for target coverage depths
• Apply specifications to design: Select appropriate NB-IoT configurations for specific IoT applications based on data rate and latency constraints

For Beginners: NB-IoT Technical Specs

This chapter covers the key NB-IoT specifications: 180 kHz bandwidth, data rates up to 127 kbps downlink, three deployment modes (in-band, guard band, standalone), and coverage enhancement through repetition. Understanding these numbers helps you evaluate whether NB-IoT meets your project’s technical requirements.

Sensor Squad: NB-IoT by the Numbers!

“Let me tell you about NB-IoT’s key numbers!” Sammy the Sensor said. “I operate on just 180 kHz of bandwidth – that is one LTE resource block. It sounds tiny, but it is perfect for sending small sensor readings. My data rate is about 25 to 250 kilobits per second, which is plenty for a 100-byte temperature reading!”

“The 164 dB maximum coupling loss is the impressive number,” Lila the LED added. “Regular LTE can handle about 144 dB. Those extra 20 dB let NB-IoT signals reach devices deep inside buildings, in basements, and even underground. That is why NB-IoT can work in places where your phone signal would struggle.”

Max the Microcontroller explained, “NB-IoT has three deployment modes that make it flexible. In-band mode shares spectrum with existing LTE – just borrows one resource block. Guard-band mode uses the unused spectrum between LTE channels. And standalone mode repurposes old GSM channels. Carriers can choose whichever mode fits their network best.”

“The specs have been improving with each 3GPP release,” Bella the Battery noted. “Release 13 gave us the basics. Release 14 added multicast and positioning. Release 15 brought early data transmission to save even more power. And Release 16 introduced small cell support and MIMO. NB-IoT keeps getting better while staying simple and power-efficient!”

4.2 NB-IoT Overview

Narrowband IoT (NB-IoT) is a Low-Power Wide-Area Network (LPWAN) radio technology standardized by 3GPP (3rd Generation Partnership Project) specifically designed for IoT applications. Unlike LoRaWAN and Sigfox which use unlicensed spectrum, NB-IoT operates in licensed cellular spectrum, providing carrier-grade reliability and quality of service.

4.2.1 Standardization and Evolution

NB-IoT was standardized by 3GPP in Release 13 (2016) to enable IoT connectivity over existing cellular infrastructure with focus on reliability, coverage, and long battery life.

NB-IoT Standardization Timeline

Figure 4.1

Figure 4.2: NB-IoT paradigm and architecture for cellular IoT

4.3 Core Technical Specifications

4.3.1 Key Parameters

Parameter	Specification
Standard	3GPP Release 13+
Bandwidth	180 kHz (1 PRB)
Data Rate	DL: ~26 kbps (Rel-13, single HARQ) UL: 62.5 kbps (multi-tone, 15 kHz)
Peak Rate	~250 kbps (multi-carrier)
Latency	<10 seconds (normal) <1 second (exception mode)
Duplex	Half-duplex FDD
Max Coupling Loss	164 dB (MCL)
Power Class	23 dBm (200 mW)
Modulation	QPSK (uplink), QPSK (downlink)

NB-IoT Technical Specifications Overview

Figure 4.3

4.3.2 Data Rates and Capacity

NB-IoT supports different data rates depending on the configuration:

Downlink (Network to Device):

• Single-tone: 25 kbps
• Multi-tone: up to 200+ kbps

Uplink (Device to Network):

• Single-tone (3.75 kHz): 16 kbps
• Single-tone (15 kHz): 64 kbps
• Multi-tone (15 kHz x 3): up to 160 kbps

Putting Numbers to It

NB-IoT data rates are directly determined by the modulation scheme (QPSK) and the number of tones (frequency channels) used. For a single 15 kHz uplink tone:

Bits per symbol: QPSK encodes 2 bits per symbol (4 phases)

Symbol rate: 15 kHz subcarrier with OFDM overhead = ~15,000 symbols/sec

Theoretical rate: \(15,000 \text{ symbols/s} \times 2 \text{ bits/symbol} = 30 \text{ kbps (raw)}\)

Actual rate after coding: \(30 \text{ kbps} \times 0.5 \text{ (code rate 1/2)} = 15 \text{ kbps}\)

With channel coding and overhead: 64 kbps achievable (using more efficient coding in good coverage).

Multi-tone (3 tones): \(64 \text{ kbps} \times 3 = 192 \text{ kbps theoretical, ~160 kbps practical}\)

This is why a 100-byte sensor reading takes ~12 ms at 64 kbps uplink, but a 64 KB firmware update takes ~3 seconds at 160 kbps downlink multi-tone.

NB-IoT Data Rate Configurations

Figure 4.4

4.4 Deployment Modes

NB-IoT can be deployed in three different modes, allowing operators to introduce IoT services without requiring entirely new spectrum.

Academic Resource: NPTEL IoT Course (IIT) - Fog Computing Architecture for NB-IoT

The NPTEL IoT course from IIT Kharagpur describes a three-tier fog computing architecture that illustrates how NB-IoT devices integrate with edge and cloud infrastructure:

• IoT Devices Tier (Bottom): Sensors, smart homes, vehicles, and wearables generate data
• Fog Layer (Middle): Fog nodes (switches, routers, gateways) provide local processing for high-sensitivity data, with private server/cloud options for confidential information
• Cloud Tier (Top): Processes less sensitive data and provides global analytics

This architecture demonstrates how NB-IoT sensors can leverage fog computing for local processing before sending aggregated data to the cloud, reducing latency and bandwidth requirements while maintaining data privacy.

Source: NPTEL Internet of Things Course, IIT Kharagpur

4.4.1 Standalone Mode

Operates in dedicated spectrum (e.g., refarmed GSM spectrum):

NB-IoT Standalone Deployment Mode

Figure 4.5

Typical bands:

• 900 MHz (former GSM)
• 800 MHz
• 700 MHz

Advantages:

• No impact on existing LTE services
• Full bandwidth available
• Easier network planning

4.4.2 Guard-Band Mode

Operates in the guard band between LTE carriers:

NB-IoT Guard-Band Deployment Mode

Figure 4.6

Use case:

• Maximize spectrum efficiency
• Rapid NB-IoT introduction
• No need for new spectrum

4.4.3 In-Band Mode

Operates within an LTE carrier using one or more Physical Resource Blocks (PRBs):

NB-IoT In-Band Deployment Mode

Figure 4.7

Trade-off:

• Easy deployment (software upgrade)
• Slightly reduces LTE capacity
• Most common initial deployment mode

4.4.4 Deployment Mode Comparison

Mode	Spectrum	LTE Impact	Complexity	Coverage
Standalone	Dedicated (GSM)	None	Low	Excellent
Guard-Band	Between LTE	Minimal	Medium	Very good
In-Band	Within LTE PRB	Some reduction	Higher	Very good

Overview

NB-IoT Deployment Modes

Deployment Architecture

NB-IoT Deployment Architecture

Figure 4.8: NB-IoT deployment modes enable flexible integration with existing cellular infrastructure

Common Misconception: “In-Band Mode Barely Impacts LTE Performance”

The Misconception: Many engineers assume that because NB-IoT uses only 180 kHz (1 PRB) of a 10-20 MHz LTE carrier, the performance impact is negligible (< 1%).

The Reality: In dense urban deployments, the actual capacity reduction can be 3-7% during peak hours, significantly higher than the theoretical 1-2% PRB allocation suggests.

Real-World Example: Major European Carrier (2019-2021)

A tier-1 European mobile operator deployed NB-IoT in in-band mode across 250 urban cell sites to support 500,000 smart meters:

Initial Assumptions (2019):

LTE carrier: 20 MHz (100 PRBs)
NB-IoT allocation: 1 PRB (180 kHz)
Expected LTE capacity loss: 1%
Expected customer impact: Negligible

Actual Results After 18 Months (2021):

Peak hour LTE throughput reduction: 5-7%
Off-peak reduction: 1-2%
Customer complaints: +12% (congestion)
Root cause: Scheduler overhead + guard tones

Why the Discrepancy?

1. Scheduler Complexity (+2-3% overhead):
   • LTE scheduler must coordinate both LTE and NB-IoT transmissions
   • NB-IoT uses a separate scheduling framework with independent HARQ processes
   • Processing overhead: additional scheduling complexity per subframe
2. Guard Tone Overhead (+1-2%):
   • NB-IoT requires 10-15 kHz guard tones on each side
   • Actual spectrum usage: 200-210 kHz (not 180 kHz)
   • Adjacent PRBs experience 5-10% throughput degradation
3. Uplink Interference (+0.5-1%):
   • NB-IoT devices transmit at +23 dBm (200 mW max)
   • Some devices have poor RF filtering
   • Cross-interference into adjacent LTE PRBs
4. Peak Hour Congestion Amplification (+1-2%):
   • NB-IoT messages during peak hours (6-9 PM)
   • Smart meters often report at fixed times
   • Coincides with residential LTE peak usage

Best Practice Recommendation:

For large-scale urban NB-IoT deployments (>100,000 devices per cell site):

• Preferred: Standalone mode (refarmed GSM 900 MHz) - 0% LTE impact
• Acceptable: Guard-band mode - 2-3% LTE impact
• Avoid: In-band mode for > 50,000 devices/site - 5-7% peak hour impact

Takeaway: Always measure real-world performance under peak load, not just theoretical PRB allocation.

4.4.5 NB-IoT Deployment Mode Selection (Decision Flowchart)

This decision flowchart provides an approach to selecting the optimal NB-IoT deployment mode based on operator constraints and spectrum availability:

NB-IoT Deployment Mode Selection Flowchart

Figure 4.9: NB-IoT deployment mode selection flowchart guiding operators through spectrum availability assessment. Standalone (green) is optimal when GSM spectrum can be refarmed. Guard-band (orange) utilizes unused LTE guard bands. In-band (blue) sacrifices 1 PRB from LTE carrier for maximum flexibility. Hybrid deployment uses multiple modes across coverage areas.

4.5 Worked Example: NB-IoT Coverage Enhancement Through Repetition

Scenario: A water utility deploys NB-IoT smart meters in basement meter rooms. The meters are 2 floors below ground level in concrete buildings. Standard LTE coverage (144 dB MCL) cannot reach them. How does NB-IoT achieve 164 dB MCL?

Step 1: Quantify the basement penetration loss

Material	Thickness	Loss per layer	Layers	Total
Concrete floor	200 mm	12 dB	2 floors	24 dB
Exterior wall	300 mm	15 dB	1 wall	15 dB
Internal walls	100 mm	5 dB	2 walls	10 dB
Total building penetration				49 dB

Step 2: Link budget comparison

Standard LTE link budget:
  TX power (eNodeB):      +46 dBm
  Antenna gain:           +18 dBi
  Path loss (1 km urban): -128 dB
  Building penetration:   -49 dB
  Received power:         -113 dBm
  LTE sensitivity:        -102 dBm
  Link margin:            -11 dB  <- FAILS (negative margin)

NB-IoT link budget (same scenario):
  TX power (eNodeB):      +46 dBm
  Antenna gain:           +18 dBi
  Path loss (1 km urban): -128 dB
  Building penetration:   -49 dB
  Received power:         -113 dBm
  NB-IoT sensitivity:     -141 dBm (with 2048 repetitions)
  Link margin:            +28 dB  <- PASSES

Step 3: How repetition buys 20 dB

NB-IoT achieves its 20 dB coverage extension primarily through message repetition. The same data block is transmitted up to 2,048 times, and the base station coherently combines all copies. Each doubling of repetitions adds approximately 3 dB of processing gain:

• 1 repetition: 0 dB gain (baseline)
• 4 repetitions: 6 dB gain
• 16 repetitions: 12 dB gain
• 128 repetitions: 21 dB gain (theoretical maximum ~33 dB with 2,048)

The cost: A 100-byte message at the maximum repetition level (2,048x) takes approximately 40 seconds to transmit instead of 20 ms. This increases latency from milliseconds to tens of seconds and raises power consumption proportionally. For a smart meter reporting once per hour, this trade-off is acceptable. For a real-time alarm, it is not.

Key insight: NB-IoT’s 164 dB MCL is not free – it trades latency and power for coverage depth. Engineers must balance repetition level against their application’s latency and battery requirements. Release 14 introduced early data transmission (EDT) to partially offset this by embedding small payloads in the connection setup procedure.

4.6 NB-IoT vs Other LPWAN Technologies

4.6.1 Technology Comparison

LPWAN Technology Comparison

Figure 4.10

4.6.2 Detailed Comparison

Feature	NB-IoT	LoRaWAN	Sigfox
Spectrum	Licensed cellular	Unlicensed ISM	Unlicensed ISM
Standard	3GPP Release 13+	LoRa Alliance	Proprietary
Data Rate	25-250 kbps	0.3-50 kbps	0.1 kbps
Latency	<10s (normal)	1-5s	seconds-minutes
Range	10-15 km (urban)	2-5 km (urban)	3-10 km (urban)
Battery Life	10+ years	5-10 years	10-20 years
QoS	Guaranteed (SLA)	Best effort	Best effort
Infrastructure	Existing cellular	Deploy gateways	Operator network only
Cost (device)	$5-15	$5-15	$5-10
Cost (service)	$1-5/month	$0 (private) or $1-3/month (public)	$1-10/year
Mobility	No handover (stationary)	Limited	Limited
Security	3GPP security (256-bit)	AES-128	Proprietary

4.6.3 When to Choose NB-IoT

Choose NB-IoT when you need:

• Guaranteed quality of service (SLA from mobile operator)
• Existing cellular coverage (no gateway deployment)
• Regulatory compliance (licensed spectrum)
• Stationary IoT support (optimized for fixed devices, no handover needed)
• Higher data rates occasionally (firmware updates)
• Carrier-grade security and authentication
• No technical team to manage infrastructure

Consider alternatives when:

• Deploying < 100 devices (LPWAN private network more economical)
• Need very low cost per device long-term (Sigfox cheaper for simple apps)
• Require complete data privacy (private LoRaWAN)
• Want zero recurring costs (private LoRaWAN)

4.7 Knowledge Check

Test your understanding of NB-IoT technical specifications.

Match NB-IoT Parameters to Their Values

Order the NB-IoT Coverage Enhancement Process

Place these steps in the correct order for how NB-IoT achieves deep indoor coverage through message repetition.

Concept Relationships

Builds on:

• Cellular IoT Fundamentals - NB-IoT fits within the broader cellular IoT ecosystem
• NB-IoT Introduction - High-level overview provides context for these technical details

Extends to:

• NB-IoT Architecture - These specs define what the architecture must support
• NB-IoT Power Optimization - Low data rates enable power-saving modes

Compares with:

• LoRaWAN Fundamentals - Alternative LPWAN with different spectrum/deployment tradeoffs
• LTE-M vs NB-IoT Comparison - LTE-M offers higher throughput at the cost of power

See Also

Related Technologies:

• LPWAN Fundamentals - Understanding the LPWAN landscape
• Spectrum Management - Licensed vs unlicensed spectrum tradeoffs

Implementation Guidance:

• Network Planning Best Practices - Coverage and capacity planning
• IoT Deployment Patterns - When to choose NB-IoT

Deeper Dives:

• 3GPP Standards Evolution - How NB-IoT specs evolved from Release 13 to 17
• MCL and Link Budget Calculations - Understanding 164 dB MCL

🏷️ Label the Diagram

💻 Code Challenge

4.8 Summary

• NB-IoT is a 3GPP-standardized LPWAN operating in licensed cellular spectrum with 180 kHz bandwidth
• Three deployment modes enable flexible spectrum utilization: standalone (dedicated spectrum), guard-band (between LTE carriers), and in-band (within LTE carrier using 1 PRB)
• Data rates range from 25 kbps to 250 kbps depending on configuration, suitable for small IoT payloads
• 164 dB Maximum Coupling Loss provides +20 dB better coverage than standard LTE (144 dB MCL), enabling deep indoor and underground penetration
• Licensed spectrum operation provides interference protection, guaranteed QoS, and carrier SLA

Common Pitfalls

1. Calculating Link Budget with Sensitivity but Without CE Gain

NB-IoT minimum sensitivity (-114 dBm) is the uncoded sensitivity for a single reception. The 164 dB MCL target includes the CE gain from repetition combining: up to +23 dB from 2048 repetitions. Including only the basic -114 dBm sensitivity in a link budget underestimates coverage by 23 dB. Full link budget must include CE gain: MCL = TX_power + TX_gain - path_loss = -114 dBm + CE_gain. Specify CE level when stating MCL figures.

2. Using Maximum Data Rate in Throughput Planning

NB-IoT’s 250 kbps peak rate requires ideal conditions: multi-tone NPUSCH, no repetitions, no scheduling delays, no retransmissions. Practical application throughput is 5–50 kbps. Planning application payloads based on 250 kbps results in severe underestimates of transmission time and energy. Plan for 20 kbps average throughput with 50 kbps burst capability. For applications in CE Mode B, use 5 kbps as the planning assumption.

3. Assuming BPSK Modulation Means Half the Throughput of QPSK

NB-IoT uses BPSK for NPRACH and some control channels, but QPSK for data channels (NPUSCH/NPDSCH). BPSK carries 1 bit/symbol vs QPSK 2 bits/symbol, so switching from QPSK to BPSK halves spectral efficiency. However, the NB-IoT standard does not allow choosing modulation independently — the protocol assigns modulation based on channel conditions and coverage class. Application developers cannot directly control modulation selection; focus on payload size and transmission timing rather than modulation.

4. Neglecting the Impact of Band Selection on Module Cost

NB-IoT modules supporting many frequency bands require more RF filters and switching components, increasing module cost and PCB size. A module supporting 15 bands costs 30–50% more than a module supporting 4 targeted bands for a specific geographic market. Analyze target deployment regions, identify the minimum band set required for carrier coverage in those regions, and select a module supporting only the required bands. Over-specification of RF bands adds cost without benefit.

4.9 What’s Next

Chapter	Focus Area
NB-IoT Architecture	CIoT architecture, SCEF, and control/user plane optimization
NB-IoT Applications	Smart metering, asset tracking, and smart city use cases
NB-IoT Power Optimization	PSM and eDRX configuration for 10+ year battery life
NB-IoT Coverage Enhancement	Repetition coding and deep indoor penetration techniques
Cellular IoT Fundamentals	Broader cellular IoT ecosystem and technology comparison