Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Management

Immediate MDT

Immediate Minimization of Drive Tests

Management →

Immediate MDT is a Minimization of Drive Tests functionality where connected user equipment performs and reports measurements to the radio access network when triggered, enabling network optimization without manual drive tests.

Introduced
Rel-10
Where
Management
Specifications
3 specs
Immediate MDT Description Purpose What changed Neighbours Detected Changes Specifications

Description

Immediate MDT (Minimization of Drive Tests) is a 3GPP feature introduced in Rel-10 that allows the network to collect measurements from User Equipments (UEs) in CONNECTED state and report them to the Radio Access Network (RAN) as soon as reporting conditions are met. It is part of the broader MDT framework, which aims to minimize the need for manual drive tests by leveraging UEs to collect radio measurements and location information. Immediate MDT is defined in 3GPP TS 32.421, 32.422, and 37.320. The term 'immediate' refers to the fact that measurements are reported promptly (e.g., upon event trigger or periodic reporting) rather than stored and reported later, as in logged MDT. Immediate MDT is used for network optimization, such as coverage and capacity tuning, mobility optimization, and QoS verification.

The technical realization of Immediate MDT involves the UE performing measurements as configured by the network. These measurements can include Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Signal-to-Interference-plus-Noise Ratio (SINR), and others, depending on the access technology (e.g., LTE, 5G NR). The network configures the UE with measurement configurations via Radio Resource Control (RRC) signaling. The UE then performs the measurements and reports them to the eNB (in LTE) or gNB (in 5G NR) when the reporting conditions are met. These conditions can be periodic (e.g., every 1 second) or event-based (e.g., when a measurement exceeds a threshold). The reports are sent over the air interface and then forwarded to the Element Manager (EM) or Network Manager (NM) for further processing and analysis. Immediate MDT also includes network-based measurements, such as those performed by the eNB/gNB itself.

Key components of Immediate MDT include the UE, which acts as a measurement probe; the RAN node (eNB/gNB), which configures and collects the measurements; the Element Manager (EM) and Network Manager (NM), which manage the MDT job and collect the results; and the Trace Collection Entity (TCE), which stores and processes the MDT data. The MDT job is initiated by the network management system, which sends a configuration to the RAN node. The RAN node then configures the UE accordingly. The UE reports the measurements, which are collected by the RAN node and forwarded to the TCE. The data is then used for network optimization. Immediate MDT supports both UE-based and network-based measurements, providing a comprehensive view of network performance.

Immediate MDT is important because it enables operators to optimize their networks without the costly and time-consuming manual drive tests. Drive tests involve sending vehicles with specialized equipment to measure network performance, which is expensive and limited in coverage. By using UEs as measurement probes, Immediate MDT provides a much larger and more representative dataset at a fraction of the cost. It also allows for continuous monitoring of network performance, as UEs are constantly connected and can report measurements. This is particularly valuable for optimizing coverage in hard-to-reach areas, detecting interference, and verifying QoS. Immediate MDT is a key tool for Self-Organizing Networks (SON) and automated network optimization.

From a technical standpoint, Immediate MDT involves several procedures: MDT configuration, measurement collection, and reporting. The network management system initiates an MDT job by sending a configuration to the RAN node, which includes the measurement types, reporting triggers, and area scope. The RAN node then selects UEs (based on criteria such as subscription type or UE capabilities) and configures them via RRC. The UE performs the measurements and sends reports as configured. The RAN node may also perform its own measurements. The collected data is then forwarded to the TCE. The entire process is standardized across 3GPP specifications to ensure interoperability. Immediate MDT supports various measurement types and can be used in conjunction with logged MDT, which stores measurements for later reporting when the UE is in IDLE state.

In summary, Immediate MDT is a powerful feature for network optimization that leverages UEs to collect and report measurements in a timely manner. It has evolved from Rel-10 to Rel-20, with the definition remaining largely stable, although the terminology has been updated to reflect the broader 'RAN' instead of specific nodes like eNB/RNC. The feature continues to be relevant in 5G and beyond, where network densification and complexity make automated optimization essential.

Purpose & Motivation

Immediate MDT exists to minimize the operational effort and cost associated with traditional drive tests. Before MDT, operators had to rely on manual drive tests to collect radio measurements for network optimization. Drive tests involve vehicles equipped with measurement tools driving around the network to collect data. This approach is expensive, time-consuming, and provides only a snapshot of network performance at a given time. It also cannot capture the full range of user conditions, such as indoor coverage or high-rise buildings. The 3GPP introduced MDT in Rel-10 to leverage the UEs themselves as measurement probes, providing a much more comprehensive and cost-effective way to collect network performance data. Immediate MDT specifically addresses scenarios where measurements need to be reported promptly, enabling real-time or near-real-time optimization.

The motivation for Immediate MDT was to enable operators to optimize their networks more efficiently and accurately. By collecting measurements from UEs in CONNECTED state, operators can get a real-time view of network performance, including coverage holes, interference, and mobility issues. This data can be used to adjust network parameters, such as antenna tilts, power levels, and handover thresholds, to improve coverage and capacity. Immediate MDT also supports QoS verification, allowing operators to ensure that the network meets the required service levels. It is a key enabler for Self-Organizing Networks (SON) and automated network management. The feature also helps with regulatory compliance by providing data for coverage obligations.

Historically, Immediate MDT was introduced in Rel-10 as part of the broader MDT work item. It built upon earlier concepts of UE-assisted network optimization, such as those defined for UMTS. The initial definition focused on measurements by the UE in CONNECTED state and reporting to eNB/RNC. Over the releases, the definition has remained largely unchanged, but in Rel-16, the terminology was updated to refer to 'RAN' instead of specific nodes, reflecting the introduction of 5G NR and the need for a technology-agnostic description. In Rel-20, the definition text was replaced with a reference to TS 37.320, which likely indicates a restructuring of the specification rather than a change in the concept itself. Immediate MDT continues to be an important tool for network optimization in modern mobile networks.

What changed in its specifications

The latest release-to-release comparison of specifications that define Immediate MDT. Each summary describes the whole specification, not only this term.

TS 32.421Rel-18 → Rel-19

Rel-19 adds RRC report collection to TS 32.421 for NG-RAN, covering RLF, RCEF, RA, SHR, SPR and MHI reports. It also introduces new clauses, definitions and requirements for subscriber and equipment trace and QoE collection management.

Full comparison in TS 32.421 →
TS 32.422Rel-18 → Rel-19

C-MDT for non-split and split RAN architectures, RRC reporting trace sessions, trace failure notification, and new parameters.

Full comparison in TS 32.422 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (2 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-16 1 change
  • Immediate MDT configurations for UE in inactive TS 37.320CR0116
Rel-18 1 change
  • Correction to Immediate MDT measurements TS 37.320CR0139

Defining Specifications

3GPP specifications that define or reference Immediate MDT, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 32.421 vj40 Subscriber & Equipment Trace Concepts & Requirements Rel-19 read
TS 32.422 vk30 Trace, MDT and UE Measurement Control Rel-20 read
TS 37.320 vj40 MDT Overall Description (Stage 2) Rel-19 read