PaperlayerView exact revision on arXiv

Source-linked AI summary

A Primer on 3GPP Narrowband Internet of Things (NB-IoT)

Y. -P. Eric Wang, Xingqin Lin, Ansuman Adhikary, Asbjörn Grövlen, Yutao Sui, Yufei Blankenship, Johan Bergman, Hazhir S. Razaghi

arXiv:1606.04171v1cs.NIcs.IT

TL;DR

NB-IoT addresses the need for wide-area IoT connectivity with low-complexity, long-lived, high-capacity devices and extended coverage. The article surveys its air interface and design rationale, including synchronization, channel structures, and coverage mechanisms. It reports substantial coverage extension alongside operating points for data rate, latency, battery life, and device capacity.

  • Problem

    IoT requires wide-area connectivity supporting low device complexity, long battery life, massive device populations, flexible deployment, and coverage beyond existing cellular technologies.

  • Method

    The article provides a state-of-the-art overview of NB-IoT air access, emphasizing deviations from LTE, design rationales, synchronization, physical channels, and performance-related procedures.

  • Results

    NB-IoT achieves a maximum coupling loss 20 dB higher than LTE Rel-12, with approximately 20 bps uplink and 35 bps downlink configurations supporting close to 170 dB coupling loss.

  • Takeaways & Limitations

    NB-IoT combines LTE-derived air-interface elements with features supporting significant coverage extension, long battery lifetime, low device complexity, and massive IoT capacity.

Abstract

from arXiv · show

Narrowband Internet of Things (NB-IoT) is a new cellular technology introduced in 3GPP Release 13 for providing wide-area coverage for the Internet of Things (IoT). This article provides an overview of the air interface of NB-IoT. We describe how NB-IoT addresses key IoT requirements such as deployment flexibility, low device complexity, long battery life time, support of massive number of devices in a cell, and significant coverage extension beyond existing cellular technologies. We also share the various design rationales during the standardization of NB-IoT in Release 13 and point out several open areas for future evolution of NB-IoT.

I. INTRODUCTION

NB-IoT is a new 3GPP radio-access technology designed for wide-area IoT connectivity and coexistence with GSM, GPRS, and LTE. The article surveys its air interface, emphasizing departures from LTE and features supporting IoT requirements.

  • Motivation: NB-IoT addresses wide-area IoT connectivity within 3GPP’s Release 13 work on machine-type communications.The broader IoT landscape includes sensors, actuators, meters, cars, and appliances requiring different network designs.
  • Design goals: NB-IoT is not fully backward compatible with existing 3GPP devices but is designed for coexistence with legacy GSM, GPRS, and LTE.Its 180 kHz minimum bandwidth enables GSM-carrier replacement and LTE in-band deployment.
  • Design rationale: The air interface extensively reuses LTE numerologies, OFDMA, SC-FDMA, coding, rate matching, and interleaving to reduce specification and product-development time.The reuse is particularly relevant to existing LTE equipment and software vendors.
  • Article scope: The article provides a state-of-the-art overview of NB-IoT air access, focusing on deviations from LTE and procedures including deployment, channels, synchronization, random access, scheduling, and HARQ.It also discusses NB-IoT performance and concludes with future evolution areas.
  • Air interface: NB-IoT downlink uses LTE-compatible OFDMA numerology and one 180 kHz LTE PRB, supporting coexistence with LTE.The 15 kHz subcarrier spacing and 0.5 ms slot, 1 ms subframe, and 10 ms frame durations match LTE.

B. Uplink transmission scheme

NB-IoT uplink supports LTE-compatible multi-tone transmission and narrower single-tone numerologies. It can operate stand-alone, in-band, or in LTE guard bands, with anchor-carrier synchronization enabling flexible deployment.

  • Uplink numerology: NB-IoT uplink supports multi-tone SC-FDMA and single-tone transmission at 15 kHz or 3.75 kHz numerology.The 15 kHz single-tone option matches LTE, while 3.75 kHz uses a 2 ms slot; all use 180 kHz system bandwidth.
  • Deployment options: NB-IoT can be deployed as a stand-alone carrier, inside an LTE carrier, or in an LTE guard band.The deployment scenario is intended to be transparent to a UE during initial carrier search.
  • Raster alignment: NB-IoT UEs search for carriers on a 100 kHz raster, while in-band LTE deployment can introduce a 2.5 kHz raster offset.Specific PRBs, including #30, #35, #40, and #45 in the described LTE configurations, align 2.5 kHz from the nearest 100 kHz grid.
  • Guard-band operation: Guard-band anchor carriers may be offset by up to 7.5 kHz from the 100 kHz raster, and cell search is designed to handle this offset.This supports synchronization despite guard-band frequency placement.
  • Multi-carrier operation: Multi-carrier NB-IoT operation uses one anchor carrier for initial synchronization, while secondary carriers need not be near the 100 kHz raster.Additional IoT capacity can therefore be added through secondary carriers.

III. PHYSICAL CHANNELS

NB-IoT physical channels largely reuse LTE designs but are adapted to a narrow 180 kHz carrier and rely primarily on time multiplexing. New synchronization and random-access structures address NB-IoT’s bandwidth and coverage constraints.

  • Design basis: NB-IoT physical channels are based largely on LTE, with the overview focusing on differences from LTE counterparts.The downlink and uplink channels are tailored to NB-IoT’s narrowband operation.
  • Downlink multiplexing: NB-IoT downlink channels and signals are primarily multiplexed in time, with each subframe spanning one PRB and 1 ms.The listed signals and channels include NPSS, NSSS, NPBCH, NRS, NPDCCH, and NPDSCH.
  • Synchronization: NPSS supports cell search and is transmitted in subframe #5 of every 10 ms frame using the last 11 OFDM symbols.Its hierarchical Zadoff-Chu-based sequence is intended to enable efficient detection.
  • Synchronization: NSSS supports cell search with 20 ms periodicity in subframe #9 and encodes NB-PCID through its sequence construction.Its Zadoff-Chu and scrambling sequences depend on the cell identity, with cyclic shift further determined by frame number.
  • Downlink channels: NPBCH carries the MIB, while NPDCCH carries scheduling and related control information and NPDSCH carries higher-layer data, paging, system information, and RAR messages.Downlink channels use LTE tail-biting convolutional coding to reduce UE complexity; NPDSCH maximum TBS is 680 bits.
  • Reference signal: NRS provides the phase reference for demodulating downlink channels and is time-and-frequency multiplexed with information-bearing symbols.It uses 8 resource elements per subframe per antenna port in subframes carrying NPBCH, NPDCCH, or NPDSCH.

B. Uplink

NB-IoT introduces a narrowband random-access channel and supports flexible uplink data transmission. Its single-tone frequency hopping and repetition mechanisms accommodate the limited bandwidth and coverage-extension requirements.

  • NPRACH: NPRACH is newly designed because LTE PRACH requires 1.08 MHz, exceeding NB-IoT uplink bandwidth.An NPRACH preamble contains four symbol groups and uses 3.75 kHz tones with changing tone frequency indices.
  • NPRACH: NPRACH uses single-tone frequency hopping, with CP formats supporting cell radii up to 10 km or 40 km.Format 0 uses a 66.67 μs CP for up to 10 km, while Format 1 uses a 266.7 μs CP for up to 40 km.
  • Coverage extension: NPRACH preambles can be repeated up to 128 times to support coverage extension.Repetition increases robustness for weak-coverage access attempts.
  • NPUSCH: NPUSCH Format 1 carries uplink data with LTE turbo coding and supports 12-tone, 6-tone, or 3-tone multi-tone transmission.The 6-tone and 3-tone formats are introduced for NB-IoT, while Format 2 carries HARQ acknowledgements using repetition coding.
  • NPUSCH: NPUSCH uses seven OFDM symbols per slot, with the middle symbol serving as DMRS for Format 1 and the middle three symbols for Format 2.DMRS supports channel estimation.
  • Summary: Table 1 summarizes NB-IoT physical channels and their differences from LTE counterparts.The table provides a compact comparison of the channel designs described in this section.

IV. RESOURCE MAPPING

NB-IoT resource mapping preserves coexistence with LTE by avoiding LTE-occupied resource elements in in-band deployments, while stand-alone and guard-band modes can use all resource elements in a PRB pair.

  • NB-IoT avoids LTE-occupied resource elements to preserve orthogonality when deployed inside an LTE carrier.
  • Figure 4 illustrates the NPDCCH and NPDSCH resource-mapping example across the supported deployment modes.
  • Stand-alone and guard-band deployments allow NPDCCH, NPDSCH, and NRS to use all resource elements in one PRB pair.A PRB pair contains 12 subcarriers over one subframe.
  • In-band deployments exclude resource elements used by LTE CRS and PDCCH from NPDCCH, NPDSCH, and NRS mapping.
  • Initial acquisition provides the deployment mode and cell identities, enabling the UE to determine LTE-used resource elements before mapping NB-IoT symbols.

V. CELL SEARCH AND INITIAL ACQUISITION PROCEDURE

NB-IoT cell search and acquisition adapt LTE-like synchronization to low-cost UEs facing large frequency offsets and very low SNR, then acquire system information through repeated NPBCH sub-blocks.

  • NB-IoT synchronization addresses symbol, subframe, and frame timing together with carrier-frequency synchronization during initial cell detection.
  • Low-cost oscillators can produce an initial carrier frequency offset as large as 20 ppm, with in-band and guard-band deployment adding a 2.5 or 7.5 kHz raster offset.
  • NB-IoT uses NPSS for symbol timing and CFO estimation, and NSSS for NB-PCID and timing within an 80 ms block.
  • Coherent accumulation over multiple 10 ms segments supports NPSS detection for UEs operating at very low SNR.
  • After synchronization, the UE acquires the MIB through NPBCH, whose 8 self-decodable sub-blocks are each repeated 8 times across consecutive frames.
  • A residual raster offset can cause carrier-frequency overcompensation or undercompensation, producing symbol-timing drift.

VI. RANDOM ACCESS

NB-IoT random access establishes radio links, supports scheduling requests, and achieves uplink synchronization through coverage-aware NPRACH configurations and repeated preambles.

  • NB-IoT random access supports initial access, scheduling requests, and uplink synchronization needed to maintain uplink orthogonality.
  • A contention-based NB-IoT random access procedure uses four steps beginning with a UE preamble and a network response containing timing advance.
  • The network can configure up to three NPRACH resource configurations for UEs in different coverage classes.
  • The UE estimates its coverage level from downlink received signal power and selects the corresponding NPRACH resources and repetition value.
  • NPRACH resources are configured in time by periodicity and starting time, and in frequency by subcarrier offset and subcarrier count.
  • The UE transmits the required repetitions of a basic single-tone random access preamble back-to-back within one NPRACH resource period.

VII. SCHEDULING AND HARQ OPERATION

NB-IoT scheduling and HARQ reduce UE complexity by using one HARQ process per link direction, longer decoding time, and asynchronous adaptive retransmission control.

  • NB-IoT permits only one HARQ process in downlink and uplink to enable low-complexity UE implementation.
  • Longer UE decoding time is allowed for NPDCCH and NPDSCH, while asynchronous adaptive HARQ supports scheduling flexibility.
  • NPDCCH carries the DCI scheduling command and may use aggregation level 1 or 2.
  • For uplink scheduling, the DCI specifies allocated subcarriers, and NPUSCH begins at least 8 ms after NPDCCH ends.
  • After NPUSCH transmission, the UE monitors NPDCCH to determine whether retransmission is needed.

VIII. PERFORMANCE

NB-IoT performance is evaluated against IoT requirements including data rate, coverage, device complexity, latency, battery lifetime, and capacity. IoT traffic growth makes cell capacity an important consideration.

  • IoT performance evaluation considers data rate, coverage, device complexity, latency, battery lifetime, and capacity.
  • 23% compounded annual growth in IoT traffic was forecast between 2015 and 2023.
  • The section discusses NB-IoT performance across the identified IoT requirements.

A. Peak Data Rates

NB-IoT provides distinct downlink and uplink peak layer-1 data rates, while its low-complexity design reduces UE processing and hardware requirements. Accounting for scheduling and HARQ timing lowers practical peak throughput relative to raw rates.

  • A. Peak Data Rates: 250 kbps is the NPUSCH peak layer-1 data rate using a 1000-bit transport block over 4 ms.
  • A. Peak Data Rates: 226.7 kbps is the NDSCH peak layer-1 data rate using a 680-bit transport block over 3 ms.
  • A. Peak Data Rates: Scheduling and HARQ acknowledgement time offsets reduce the peak throughputs below the stated downlink and uplink layer-1 rates.
  • A. Peak Data Rates: NB-IoT targets low-complexity UE implementation through reduced transport block sizes, one redundancy version, single-stream transmission, and one antenna.
  • A. Peak Data Rates: The UE uses one HARQ process, no turbo decoder for downlink channels, sequential processing, and an integrated PA enabled by 20 or 23 dBm power.

D. Latency and battery lifetime

NB-IoT targets latency-insensitive applications while supporting selected low-latency alarm signaling and long battery life. It also addresses massive capacity and is positioned for continued evolution toward 5G requirements.

  • D. Latency and battery lifetime: Less than 10 s latency is supported for applications such as sending alarm signals.
  • D. Latency and battery lifetime: 10-year battery life can be reached at 164 dB coupling loss when the UE transmits 200-byte data per day on average.
  • E. Capacity: More than 52500 UEs per cell are supported with one PRB under the cited traffic model.
  • E. Capacity: Additional IoT capacity can be added through multiple NB-IoT carriers.
  • IX. CONCLUSION: Future NB-IoT enhancements discussed for the next 3GPP release include low-complexity multicast and improved positioning accuracy.
Loading 1606.04171v1…