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

Glossary term · Management

C-MDT

Continuous Management-Based Minimization of Drive Tests

Management →

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.

Introduced
Rel-19
Where
Management
Specifications
2 specs
C-MDT Description Purpose What changed Neighbours 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.

What changed in its specifications

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

TS 28.622Rel-18 → Rel-19

Rel-19 added external management data IOCs, discovery, notification retrieval, and single notifications. It added network slice lists in Area Scope, measurement conditions, and new data types for selecting instances via DNs, GeoAreas, or TAIs.

Full comparison in TS 28.622 →
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 →

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-19 Initial

Introduced the Continuous MDT concept as a new management-based activation mode. Defined the architecture where the Management System can configure long-duration MDT tasks via the Service Management and Orchestration layer. Specified support for continuous collection of measurements like RSRP, RSRQ, and location information from both idle and connected UEs over extended periods, filling the gap for persistent network performance monitoring.

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 vk40 Generic Network Resource Information Service Rel-20 read
TS 32.422 vk30 Trace, MDT and UE Measurement Control Rel-20 read