C-MDT

Continuous Management-Based Minimization of Drive Tests

Management →
Introduced in Rel-19

C-MDT is a 3GPP feature for continuous, automated collection of UE and network measurements to monitor performance and optimize the RAN without physical drive tests.

Category
Management
Introduced
Rel-19
Where
Management
Specifications
2 specs
C-MDT Description Purpose Related Classification Detected Changes Specifications

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.

Classification

Part ofMDT
Related approachesSON

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-15 1 change

In Release 15, the Continuous Management-Based Minimization of Drive Tests (C-MDT) function was newly introduced, as formally defined within the specifications. This introduction included the addition of the missing Network Resource Model (NRM) fragment to support network performance management for this continuous, management-based drive test minimization capability.

  • Add the missing NRM fragment supporting network performance management TS 28.622CR0027
Rel-16 1 change

In Release 16, the enhancement for Continuous Management-Based Minimization of Drive Tests (C-MDT) involved a correction to the notification support table for the ManagedElement and ManagementNode Information Object Classes. This update ensured the management interfaces accurately reflected the event reporting capabilities for these key network resource objects within the Service Based Management Architecture.

  • Correct notification support table for ManagedElement and ManagementNode TS 28.622CR0097
Rel-17 3 changes

In Release 17, the enhancements for Continuous Management-Based Minimization of Drive Tests (C-MDT) introduced new stage 2 definitions for file management and for management data collection and discovery. These additions formalized the procedures and interfaces for handling collected MDT data files and for discovering available management data within the network resource model. The release also included updates to the attribute properties for the relevant Information Object Classes (IOCs) governing ManagementDataCollection.

  • Add stage2 definition for file management TS 28.622CR0147
  • Add stage 2 for management data collection and discovery TS 28.622CR0166
  • Include already approved changes or enhancements of attribute properties for IOC ManagementDataCollectio TS 28.622CR0170
Rel-18 4 changes

In Release 18, the C-MDT function was enhanced to support the request of management data per PLMN within the ManagementDataCollection. Furthermore, corrections and clarifications were made, including to the description and definition of the ManagementDataCollection IOC and to the name containment handling for Trace jobs during signalling-based activation.

  • Rel-18 CR TS 28.622 Enhance the ManagementDataCollection to support request management data per PLMN TS 28.622CR0308
  • Name containment of Trace job in case of Signalling based activation TS 28.622CR0271
  • Correct description for ManagementDataCollection IOC TS 28.622CR0181
  • Correct ManagementDataCollection definition TS 28.622CR0197
Rel-19 3 changes

In Release 19, the enhancements for Continuous MDT (C-MDT) included clarifications on the handling of historical management data and the addition of new enumerated values for data management-related management capabilities. These updates provided more precise definitions and expanded the configurable parameters for managing the continuous collection of drive test data. The changes specifically refined the management service interfaces and data models within the Service-Based Management Architecture framework.

  • Rel-19 CR TS 28.622 Continuous MDT TS 28.622CR0572
  • Rel-19 CR TS 28.622 Add Enum values for the management capabilities related to data management TS 28.622CR0579
  • Rel-19 CR TS 28.622 Clarification on historical management data TS 28.622CR0587
Rel-20 1 change

In Release 20, the update for Continuous Management-Based Minimization of Drive Tests (C-MDT) specifically added new enumeration values to the management capabilities that were missing from the previous Release 19. This was documented through a Change Request to the management specification TS 28.622, ensuring the model's completeness for network resource management. The change refined the Management System's Information Object Class (IOC) definitions to support the necessary operations and notifications for C-MDT.

  • Rel-20 CR TS 28.622 Add Enum values for missing R19 management capabilities TS 28.622CR0598

Explore further

Broader topics and technologies where C-MDT plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 28.622 vk20 Telecommunication Management; Generic NRM Information Service Rel-20
TS 32.422 vk00 Telecom Management: Trace Control & Configuration Rel-20