Continuous Management-Based Minimization of Drive Tests

Description

Continuous Management-Based Minimization of Drive Tests (C-MDT) is an advanced network management and optimization feature standardized in 3GPP Release 19. It extends the traditional MDT framework by enabling operators to configure and activate measurement collection sessions that run continuously over extended periods, rather than being limited to immediate or logged MDT sessions triggered by specific events or locations. The architecture involves the Management System (typically the Network Management System or Element Management System) acting as the initiating entity, which sends MDT configuration commands to the RAN nodes (gNB in 5G, eNB in LTE) via the Itf-N interface or to the Core Network for UE-based configurations. The RAN then activates the specified measurements on targeted UEs or cells.

C-MDT operates by establishing a persistent measurement task defined by the operator through the management plane. This task includes parameters such as the target area (list of cells or tracking areas), measurement types (e.g., Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Timing Advance, radio link failure reports, handover success rates), reporting criteria (periodic or event-triggered), and a validity timer that can be set for days, weeks, or even months. The RAN configures the selected UEs—which can be in idle or connected mode—to perform these measurements. For UEs supporting MDT, the measurements and associated location information (if available and authorized) are collected and stored either in the RAN or reported directly, depending on the configuration.

The collected data is then aggregated and reported back to the Management System. The reporting can occur in near-real-time for connected UEs or be logged and reported later when the UE establishes a connection. The RAN uses the Trace functionality to associate measurements with specific UEs and sessions. Key components include the Trace Function in the RAN and Core Network, the MDT configuration and collection functions in the RAN nodes, and the MDT data processing and analysis functions in the Management System. The interface between the Management System and the Network Functions is standardized in 3GPP TS 28.622 and TS 32.422, ensuring interoperability.

C-MDT's role in the network is pivotal for operational automation and intelligence. It transforms network optimization from a reactive, manual process based on sporadic drive tests and customer complaints to a proactive, continuous data analytics process. By gathering massive amounts of field data from actual user devices under real usage conditions, operators can build highly accurate radio frequency maps, precisely locate and characterize coverage issues (like weak signal areas or pilot pollution), analyze mobility performance (handover failures, ping-pong effects), and understand quality of experience (QoE) metrics correlated with location and radio conditions. This data is essential for planning network expansions, tuning antenna parameters, optimizing neighbor cell lists, and validating the impact of optimization changes.

Purpose & Motivation

C-MDT was created to address the significant limitations and escalating costs associated with traditional drive tests for cellular network optimization and monitoring. Physical drive tests are labor-intensive, time-consuming, expensive, and provide only a snapshot of network performance at a specific time and on specific routes. They cannot capture the dynamic, user-centric performance experienced across the entire network footprint 24/7, especially in indoor environments or private areas where drive tests are impractical. Furthermore, as networks evolved to 5G with increased density (small cells), wider bandwidths, and more complex features like carrier aggregation and beamforming, the need for granular, continuous performance data became critical.

The historical context stems from the initial MDT framework introduced in 3GPP Release 10, which allowed for Immediate MDT (triggered by a management command for connected UEs) and Logged MDT (where idle UEs store measurements for later reporting). While revolutionary, these modes were often campaign-based—activated for a short duration to investigate a specific issue. C-MDT addresses the need for persistent monitoring, enabling operators to establish a 'always-on' measurement layer for key performance indicators. This is motivated by the industry's shift towards zero-touch network and service management (ZSM), data-driven operations, and artificial intelligence for network automation (AINA).

By solving the problem of discontinuous data collection, C-MDT allows operators to detect and diagnose intermittent or location-specific issues that short-term MDT campaigns might miss. It provides the foundational data pipeline for machine learning models that predict network failures, optimize resource allocation, and ensure consistent service quality. Ultimately, C-MDT reduces operational expenditure (OPEX) by automating data collection, accelerates optimization cycles, and improves network quality and customer experience by enabling evidence-based, continuous optimization.

Key Features

• Persistent, operator-configured measurement tasks with long validity timers (days to months)
• Support for both idle mode and connected mode UE measurements
• Collection of comprehensive radio measurements (RSRP, RSRQ, SINR) with optional location info
• Management-based activation via standardized Itf-N interfaces (TS 28.622/32.422)
• Data collection targeted by geographical area (cell list, tracking area) or specific UE groups
• Flexible reporting: both immediate reporting and logged reporting with later retrieval

Evolution Across Releases

Defining Specifications