Minimization of Drive Tests (MDT)

Immediate MDT collects measurements from UEs in RRC_CONNECTED state and reports them in real-time to the network. This mode is ideal for troubleshooting active sessions and capturing detailed radio conditions during data transfers.

• Measurement triggers: periodic, event-based (e.g., A2 serving cell threshold)
• Includes detailed L1/L3 RSRP/RSRQ and power headroom reports
• Location information derived from GNSS or RF fingerprinting
• Used for real-time coverage hole detection and handover boundary analysis

Logged MDT allows UEs in RRC_IDLE or RRC_INACTIVE state to record measurements according to a configuration received while connected. The UE stores data and reports it when it next establishes a connection.

• Configuration includes logging duration, interval, and area scope (cell list or tracking area)
• Records serving cell and intra-frequency neighbor measurements
• Timestamps and location stamps each log entry
• Critical for mapping idle-mode coverage and detecting sleeping cell issues

In Management-Based MDT, the network operator selects specific UEs for measurement collection based on criteria such as IMSI, IMEI, or area scope. This is initiated from the Element Management System (EMS) or Network Management System (NMS).

• Uses Trace Function activation via the Home Subscriber Server (HSS)
• Supports both Immediate and Logged MDT modes
• Enables targeted troubleshooting for VIP users or specific device models
• Selection criteria: IMSI ranges, IMEI-SV ranges, or geographic area

Signaling-Based MDT activates measurement collection for a specific UE through control plane signaling, initiated by the Mobility Management Entity (MME). This targets an individual subscriber for detailed session analysis.

• Activated via S1-AP Initial Context Setup or UE Context Modification procedures
• Tied to a specific UE context, not a general area
• Enables per-subscriber QoS verification and mobility analysis
• Complements Management-Based MDT for granular, subscriber-level diagnostics

MDT enriches radio measurements with location data to geolocate coverage problems. Multiple positioning methods are supported, balancing accuracy against UE power consumption.

• GNSS (GPS/GLONASS/Galileo): Highest accuracy, available only with clear sky view
• RF Fingerprinting: Pattern-matches measured cell IDs and signal strengths against a predicted database
• Enhanced Cell ID (E-CID): Uses timing advance and angle of arrival for improved cell-level positioning
• Location data is privacy-controlled; operators must anonymize or obtain consent per local regulations

The network configures MDT behavior through a set of standardized parameters transmitted to the UE via RRC signaling. These parameters define what, when, and how measurements are collected.

• LoggingInterval: Time between consecutive measurement samples (e.g., 1.28s, 2.56s)
• LoggingDuration: Total time the UE should record measurements (e.g., 10min, 60min)
• AreaConfiguration: Defines the geographic scope using cell IDs or tracking area codes
• TraceReference: Unique identifier linking the MDT session to the management system
• TargetMBSFN-AreaList: Optionally restricts logging to specific MBSFN areas for multicast optimization

A mode where connected-mode UEs perform measurements and report them in near-real-time. The RAN node configures the UE via RRC signaling, and reports are sent immediately when conditions are met.

• Trigger: RRC Connection Reconfiguration
• Data Path: UE → eNB/gNB → TCE via RRC
• Use Case: Active call tracing and real-time coverage mapping
• Limitation: Only available during active data sessions

A mode where idle-mode UEs log measurements according to a configuration received while connected, then report the stored data during a subsequent connection.

• Trigger: Idle mode logging based on timer and area scope
• Data Path: UE storage → eNB/gNB → TCE at next connection
• Key Parameter: loggingDuration and loggingInterval
• Advantage: Captures coverage holes where no connection is possible

The 3GPP-defined network node responsible for collecting, storing, and processing MDT measurement reports from multiple RAN nodes. It acts as the centralized aggregation point.

• Function: Decodes and correlates trace records
• Interface: Receives data from eNB/gNB via standardized file-based or streaming interfaces
• Integration: Feeds processed data to network planning and SON tools
• Vendor Role: Typically a dedicated server or cloud-based analytics platform

An activation method where the Network Management System (NMS) or Operations Support System (OSS) initiates MDT sessions by sending trace activation requests to specific RAN nodes or based on geographical area targets.

• Scope: Area-based (tracking area, cell list) or UE-based (IMSI group)
• Protocol: Uses Itf-N interface (IRP-based) from the management plane
• Advantage: Enables network-wide, planned measurement campaigns
• Contrast: Differs from Signaling-Based MDT, which targets specific UEs via core network signaling

An activation method where the Core Network (MME/AMF) initiates MDT for a specific subscriber by including MDT configuration parameters in the initial context setup request to the RAN node.

• Target: Specific IMSI or IMEI
• Protocol: Uses S1/NG Application Protocol (S1AP/NGAP)
• Use Case: Troubleshooting a specific user's reported poor experience
• Privacy: Requires user consent management per 3GPP TS 32.422

The geospatial data associated with MDT measurements, critical for mapping RF conditions to physical coordinates. 3GPP specifies multiple methods with varying accuracy.

• GNSS: GPS/Galileo coordinates (highest accuracy, UE-dependent)
• RF Fingerprinting: Pattern matching against a predicted coverage database
• Timing Advance + AoA: Network-based triangulation
• Cell ID: Coarse location (cell centroid)
• Requirement: Location data must be anonymized or aggregated before use in SON tools