Description
The MDL (Offset of NB-IoT Downlink channel number to Downlink EARFCN) is a fundamental parameter defined within the 3GPP specifications for Narrowband Internet of Things (NB-IoT) technology. NB-IoT is designed as a low-power wide-area (LPWA) radio technology that can be deployed in three modes: standalone, guard-band, and in-band within existing LTE spectrum. The MDL parameter specifically addresses the in-band and guard-band deployment scenarios where an NB-IoT carrier occupies a subset of the LTE physical resource blocks (PRBs). Its primary function is to provide a precise mapping between the narrowband physical resource block index used by the NB-IoT carrier and the downlink EARFCN of the host LTE carrier. This mapping is essential because the NB-IoT carrier's center frequency is derived from the LTE carrier's frequency raster.
Technically, the downlink EARFCN (E-UTRA Absolute Radio Frequency Channel Number) is a unique number that defines a specific LTE carrier frequency. For an in-band NB-IoT deployment, the NB-IoT carrier occupies one physical resource block (180 kHz) within the LTE carrier's bandwidth. The MDL offset, expressed as an integer number of 100 kHz units (the LTE subcarrier spacing), specifies the frequency offset from the LTE carrier's center frequency to the center of the NB-IoT carrier's assigned PRB. This calculation allows the network and the UE to determine the exact radio frequency for the NB-IoT synchronization signals (NPSS and NSSS) and broadcast channels (NPBCH).
The parameter is defined in the base station (eNodeB) radio transmission and reception specifications (e.g., 36.104, 36.141). Network operators configure the MDL value as part of the cell planning parameters. The UE acquires this parameter implicitly through synchronization and system information decoding. Correct configuration of MDL is critical for avoiding interference between the NB-IoT signals and the host LTE signals, ensuring that the NB-IoT carrier is correctly placed within the assigned PRB. It plays a silent but vital role in the RF layer, enabling the seamless integration of NB-IoT as a 'clean-slate' technology within the legacy LTE frequency grid.
Purpose & Motivation
MDL was introduced to solve the specific frequency alignment challenge posed by deploying NB-IoT within existing LTE spectrum. Prior to NB-IoT, LTE-M (eMTC) was another LPWA technology that reused the entire LTE carrier structure. NB-IoT, however, was designed with a new 180 kHz carrier bandwidth that did not align with the LTE carrier center. For in-band deployment, this meant the NB-IoT carrier would sit on an LTE PRB offset from the center. Without a standardized offset parameter, there would be ambiguity in defining the NB-IoT carrier's absolute frequency, leading to potential misalignment and interference between NB-IoT and LTE services sharing the same spectrum.
The creation of MDL was motivated by the need for precise network planning and UE cell search procedures. It provides a deterministic formula for deriving the NB-IoT carrier frequency from the known LTE EARFCN. This standardization ensures that all UEs and base stations from different vendors interpret the carrier location consistently, which is a prerequisite for interoperability. It addresses the limitation of having a flexible, yet well-defined, frequency relationship between the host LTE layer and the NB-IoT layer, which was a novel concept introduced with the 3GPP Rel-13 NB-IoT specifications.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (12 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-13, normative work from Rel-15.
In Release 15, the MDL function was updated to introduce an implementation for the UL PRB to DL PRB center offset specifically for TDD NB-IoT operation. This change was documented through corrections to both the base station transmission (TS 36.104) and conformance testing (TS 36.141) specifications. The release did not introduce changes to the MDL function for FDD NB-IoT or other band configurations.
- CR to TS 36.104: Implementation of UL PRB to DL PRB center offset for TDD NB-IoT TS 36.104CR4816
- CR to TS 36.141: Implementation of UL PRB to DL PRB center offset for TDD NB-IoT TS 36.141CR1189
- Correction of channel spacing for band 46 intraband CA band combinations with 10 MHz bandwidth TS 36.104CR4737
In Release 16, the specification introduced new technical details for the MDL function to define the frequency offset between anchor and non-anchor carriers for Time Division Duplex (TDD) NB-IoT standalone operation. This provided necessary clarifications for the channel arrangement in these operating bands. The changes ensured synchronized operation requirements were addressed for this specific NB-IoT deployment mode.
- CR for TS 36.104 Rel-16: Clarification on LAA and eLAA channel access TS 36.104CR4829
- CR to 36.104: frequency offset between anchor and non-anchor carrier for TDD NB-IoT standalone operation TS 36.104CR4833
- CR to 36.141: frequency offset between anchor and non-anchor carrier for TDD NB-IoT standalone operation TS 36.141CR1194
In Release 18, the MDL function was updated with a correction to the EARFCN for bands 107 and 108, as specified in the 3GPP TS 36.104 document. This change ensures the accurate alignment of the NB-IoT downlink channel number offset to the downlink EARFCN in these specific operating bands. The adjustment maintains proper channel arrangement and regional operation for these supplemental downlink bands.
In Release 19, no new changes were introduced for the "MDL" (Offset of NB-IoT Downlink channel number to Downlink EARFCN) function, as the provided Change Requests and grounding context contain no modifications or mentions related to this specific parameter. The listed CRs for TS 36.108 instead focused on updates to channel model parameters, clarifications for ACLR requirements, and corrections for NB-IoT NPUSCH channel estimation notes. Therefore, the MDL function specification remained unchanged from the previous release.
- CR to TS 36.108: Clarification on channel bandwidth applicability in ACLR requirement TS 36.108CR0052
- Channel Model Parameters Annex D update for 36.108 TC 8.5 - Rel 19 TS 36.108CR0041
- CR to TS 36.108: Adding a missing Note on channel estimation lengths for NB-IoT NPUSCH format 1 FRC TS 36.108CR0051
- Channel Model Parameters Annex F update for 36.181 TC 8.5 - Rel 19 TS 36.181CR0030
Explore further
Broader topics and technologies where MDL plays a role.
Defining Specifications
3GPP specifications that define or reference MDL, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 36.104 vj10 | Base Station (BS) radio transmission and reception | Rel-19 |
| TS 36.108 vj10 | Satellite Access Node RF Requirements | Rel-19 |
| TS 36.141 vj00 | E-UTRA BS Conformance Testing | Rel-19 |
| TS 36.181 vj30 | E-UTRA RF Test Methods for Satellite Access Node | Rel-19 |