Minimization of Drive Tests

Description

Minimization of Drive Tests (MDT) is a network management and optimization feature standardized across 3GPP releases. Its core function is to automate the collection of radio measurements, location information, and other relevant data from participating User Equipment (UE) and evolved NodeBs (eNBs/gNBs) in a controlled manner. This data is then reported to the network management system (NMS) or trace collection entity for analysis. MDT transforms passive UEs into active network probes, providing a detailed, real-world view of network performance, coverage, and quality of service (QoS) from the end-user perspective.

Architecturally, MDT involves several key network elements. The Management System (e.g., OAM) configures MDT tasks, specifying what measurements to collect (e.g., Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), throughput), under what conditions (immediate or logged), and from which UEs (based on area, subscription, etc.). This configuration is communicated to the Radio Access Network (RAN) via the Itf-N interface (between OAM and RAN) or within the RAN. The RAN node (eNB/gNB) then activates MDT for selected UEs via RRC signaling. UEs perform the requested measurements, which can be reported immediately (Immediate MDT) or stored locally and reported later when connected (Logged MDT). Location information can be obtained via UE-based GNSS, network-based positioning, or RF fingerprinting. The collected MDT reports are ultimately aggregated in the Network Management System for processing and analysis.

MDT works in two primary modes: Immediate MDT and Logged MDT. Immediate MDT is performed by UEs in RRC_CONNECTED state, with measurements reported directly to the network. This is useful for real-time troubleshooting. Logged MDT is performed by UEs in RRC_IDLE or RRC_INACTIVE states; measurements are stored in an internal log with timestamps and location info (if available) and reported when the UE transitions back to RRC_CONNECTED. This mode is invaluable for coverage optimization, especially in areas with poor connectivity. The data collected provides insights into coverage holes, pilot pollution, handover failures, and QoS degradation, enabling data-driven network planning and optimization.

Purpose & Motivation

MDT was created to address the significant operational expenditure (OPEX) and limitations associated with traditional manual drive testing. Manual tests are costly, time-consuming, provide only a snapshot in time, cannot cover all geographical areas (e.g., indoors, private property), and lack the end-user context for data services. As networks grew denser and more complex with 3G and 4G, these limitations became increasingly burdensome for operators striving to maintain high service quality.

The technology solves the problem of inefficient and incomplete network performance monitoring by leveraging the existing fleet of user devices as distributed sensors. This provides continuous, large-scale, and user-centric data that reflects the actual service experience. It enables proactive network optimization, faster fault detection, and more accurate capacity planning. Historically, MDT was introduced in 3GPP Release 9 for LTE and later extended to UMTS, GSM, and NR, becoming a cornerstone of Self-Organizing Network (SON) functionalities.

MDT addressed the key limitation of previous approaches—the lack of scalable, ubiquitous measurement collection—by standardizing the procedures for UE-based measurement gathering and reporting. This allowed operators to move from reactive, sample-based optimization to a data-driven, continuous optimization paradigm. It was motivated by the industry's push towards automation (SON) and the need to manage increasingly heterogeneous and dense networks cost-effectively.

Key Features

• Automated collection of UE and cell measurements (RSRP, RSRQ, etc.)
• Supports two modes: Immediate MDT (connected state) and Logged MDT (idle/inactive state)
• Incorporates UE location information (GNSS, RF fingerprinting)
• Configurable by the management system (OAM) for targeted data collection
• Enables user-centric network performance and quality of experience (QoE) monitoring
• Foundation for advanced Self-Organizing Network (SON) use cases like coverage and capacity optimization

Evolution Across Releases

Defining Specifications