System and method for minimization drive test data collection and reporting in wireless communication networks

Abstract

A method (200) and a system (100) for optimizing minimization drive test (MDT) in wireless communication networks by reducing a user equipment (UE) dependency on base station-triggered configurations is disclosed. The system (100) includes a UE (102) and a base station (104). The UE (102) is configured to transmit a UE capability message indicating support for a feature, representing that the UE (102) includes a default set of self-MDT logged configurations based on one or more UE conditions, to the base station (104). The base station (104) transmits a control signal to enable the feature, and to allow the UE (102) to perform MDT measurement based on one or more trigger conditions, using one of the default set of self-MDT logged configurations based on a UE condition from the one or more UE conditions.

Description

SYSTEM AND METHOD FOR MINIMIZATION DRIVE TEST DATA COLLECTION AND REPORTING IN WIRELESS COMMUNICATION NETWORKSTECHNICAL FIELD

[0001] The present disclosure relates to the field of wireless communication. In particular, the present disclosure provides a system and a method for optimizing minimization of drive test (MDT) data collection and reporting in wireless networks.BACKGROUND

[0002] Minimization of drive test (MDT) is a feature introduced in modem wireless communication networks, such as Long-Term Evolution (LTE) and 5G networks for performance optimization and quality of service (QoS) while reducing the reliance on traditional, resource-intensive drive tests. The MDT enables a user equipment (UE) to collect and report network performance data, facilitating network optimization and troubleshooting. An MDT supports two main categories: Immediate MDT, where data is collected and reported in real time, and Logged MDT, where data is stored in the UE and transmitted to the network at a later time. The UE measurements include key performance indicators such as Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Signal-to-Interference-plus-Noise Ratio (SINR), location information (e.g., GPS coordinates), and timing data (e.g., measurement timestamps). Configurable parameters like measurement triggers, logging duration, and logging intervals are managed via RRC signaling by the network. MDT data is used to analyze call drops, optimize handovers, identify coverage gaps, and improve overall network QoS.

[0003] In the current implementation, MDT (Minimization of Drive Test) measurement is initiated and configured by the base station (e.g., eNodeB or gNodeB) for a User Equipment (UE). The base station transmits the required MDT parameters to the UE, which include the MDT logging duration, logging interval, and target measurement conditions. Once configured, the UE performs and logs the MDT measurements according to the provided parameters. Subsequently, upon receiving a request from the base station, the UE transfers the logged MDT measurement report or data file to the base station for analysis.

[0004] However, a significant limitation of the current MDT framework is the UE's dependency on the base station for MDT configuration. In real-world deployments — particularly in mixed network environments involving advanced Radio Access Technologies(RATs) like 6G — there may be numerous real-time network issues requiring resolution to ensure effective 6G deployment alongside other RATs. Real-time MDT monitoring could be highly beneficial in such scenarios. Moreover, there are cases where the base station may not configure or initiate MDT logging. The dependency poses challenges for the UE, especially when the UE encounters real-time field issues such as poor signal quality, coverage gaps, or mobility anomalies. Without a predefined or default MDT configuration at the UE, critical network performance data may be lost, thereby limiting the effectiveness of MDT in identifying and resolving real-time network issues. This problem is exacerbated in heterogeneous network environments where legacy networks coexist with next-generation systems.

[0005] Additionally, the current MDT framework lacks a mechanism for dynamic optimization of the logging process. Specifically, there is no provision for the UE to adjust MDT measurement parameters — such as the logging interval, logging duration, or specific measurement metrics — based on real-time field conditions. For instance, in areas experiencing significant signal variations or network interference or UE different mobility states, the ability to modify measurement parameters dynamically could enhance the quality and relevance of the collected data. Without such optimizations, the gathered MDT data may be suboptimal, leading to inefficient network analysis and less effective performance tuning.

[0006] As advanced RATs like 6G and other emerging technologies are deployed, further challenges with the existing MDT framework are likely to emerge. The challenges include increased complexity in managing measurements across diverse network conditions, integrating multiple RATs, and ensuring seamless data collection for network optimization.

[0007] Thus, there is a need to address the aforementioned drawbacks, shortcomings, and limitations of existing MDT frameworks to ensure the timely availability of drive test data and enable proactive network maintenance and optimization in increasingly complex network environments.OBJECTS OF THE PRESENT DISCLOSURE

[0008] A general object of the present disclosure is to provide a method and system for optimizing minimization drive test (MDT) data collection and reporting in wireless communication networks.

[0009] An object of the present disclosure is to enable user equipment (UE) to autonomously perform and log MDT measurements using a default set of self-MDT logged configurations, thereby reducing dependency on base station-triggered MDT processes.

[0010] An object of the present disclosure is to ensure continuous and reliable data collection for network optimization, even when the base station does not provide specific MDT configurations.

[0011] An object of the present disclosure is to provide a mechanism for dynamically optimizing MDT measurement parameters based on real-time field conditions, such as signal quality, network congestion, and UE mobility.

[0012] An object of the present disclosure is to enable the base station to store UE capability information associated with the feature for one or more UEs, thereby enhancing network management and optimization.

[0013] An object of the present disclosure is to support the transmission of MDT logged measurement configurations from the base station or a third-party server to the UE, allowing the UE to modify its default self-MDT logged configurations based on received parameters and UE conditions.SUMMARY

[0014] Aspects of the present disclosure relate to the field of wireless communication. In particular, the present disclosure provides a system and a method for optimizing minimization of drive test (MDT) data collection and reporting in wireless networks.

[0015] An aspect of the present disclosure pertains to a method for optimizing minimization drive test (MDT) in a wireless communication network, performed by a user equipment (UE). The method includes transmitting a UE capability message to a base station. Herein, the UE capability message indicates support for a feature. Herein, the feature represents that the UE (102) includes a default set of self-MDT logged configurations. Herein, the default set of self-MDT logged configurations includes a default set of MDT logged parameters based on one or more UE conditions.

[0016] Further, the method also includes receiving a control signal from the base station based on one or more network performance parameters that the base station needs to, one or more of: monitor, optimize, and troubleshoot. Herein, the control signal includes an enable signal to, one of: enable and disable, the feature for the UE, and one or more trigger conditions, wherein the UE performs MDT measurement based on the one or more trigger conditions when the feature is enabled. The method also includes performing the MDT measurement based on the control signal, and using one of the default set of self-MDT logged configurations based on a UE condition from the one or more UE conditions.

[0017] In an additional embodiment, the method further includes transmitting, by the UE, data associated with the MDT measurement to the base station.

[0018] In an additional embodiment, the method further includes receiving, by the UE, from one of: the base station and a third-party server, an MDT logged measurement configuration, including one or more parameters. The method also includes modifying, by the UE, a default self-MDT logged configuration from the default set of self-MDT logged configurations based on the one or more parameters and a UE condition from the one or more UE conditions.

[0019] In another aspect of the present disclosure pertains to a system for optimizing minimization drive test (MDT) in a wireless communication network. The system includes a user equipment (UE) and a base station (BS). The UE is configured to transmit a UE capability message to the base station. Herein, the UE capability message indicates support for a feature. Herein, the feature represents that the UE includes a default set of self-MDT logged configurations. Herein, the default set of self-MDT logged configurations includes a default set of MDT logged parameters based on one or more UE conditions. The UE is also configured to receive a control signal from the base station.

[0020] Additionally, the base station is configured to receive the UE capability message from the UE. The base station is also configured to transmit the control signal to the UE based on one or more network performance parameters that the base station needs to, one or more of: monitor, optimize, and troubleshoot. Herein, the control signal includes an enable signal to, one of: enables and disables, the feature for the UE, and one or more trigger condition, wherein the UE performs MDT measurement based on the one or more trigger conditions when the feature is enabled. Herein, the UE is also configured to perform the MDT measurement, based on the control signal, and using one of the default set of self-MDT logged configurations based on a UE condition from the one or more UE conditions.

[0021] In an additional embodiment, the UE is further configured to transmit data associated with the MDT measurement to the base station.

[0022] In an additional embodiment, the base station is further configured to transmit an MDT logged measurement configuration, including one or more parameters, to the UE. Further, the UE is configured to receive the MDT logged measurement configuration. The UE is also configured to modify a default self-MDT logged configuration from the default set of self-MDT logged configurations based on the one or more parameters and a UE condition from the one or more UE conditions.

[0023] In an additional embodiment, the base station is further configured to store the UE capability information associated with the feature for the UE.

[0024] In an additional embodiment, the system further includes a third-party server, configured to transmit an MDT logged measurement configuration, including one or more parameters, to the UE. Further, the UE is configured to receive the MDT logged measurement configuration. The UE is also configured to modify a default self-MDT logged configuration from the default set of self-MDT logged configurations based on the one or more parameters and a UE condition from the one or more UE conditions.

[0025] Various objects, features, aspects, and advantages of the inventive subject matter will become more apparent from the following detailed description of preferred embodiments, along with the accompanying drawing figures in which like numerals represent like components.BRIEF DESCRIPTION OF DRAWINGS

[0026] The accompanying drawings are included to provide a better understanding of the present disclosure and form an integral part of this specification. The drawings illustrate exemplary embodiments of the present disclosure and, together with the detailed description, help explain its underlying principles. It should be noted, however, that the appended drawings depict only certain representative aspects of the present disclosure and are not intended to limit its scope, as the description may encompass other equally effective embodiments. Identical or similar elements in different drawings may be identified by the same reference numbers.

[0027] FIG. 1 illustrates an exemplary diagram representing the components of the proposed system, in accordance with an embodiment of the present disclosure.

[0028] FIG. 2 illustrates an exemplary flow diagram for implementing the steps of the proposed method, in accordance with an embodiment of the present disclosure.DETAILED DESCRIPTION

[0029] The following is a detailed description of embodiments of the disclosure depicted in the accompanying drawings. The embodiments are in such detail as to clearly communicate the disclosure. However, the amount of detail offered is not intended to limit the anticipated variations of embodiments; on the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the present disclosure as defined by the appended claims.

[0030] The following is a detailed description of embodiments of the disclosure depicted in the accompanying drawings. The embodiments are in such detail as to clearly communicate the disclosure. If the specification states a component or feature “may”, “can”, “could”, or “might” be included or have a characteristic, that particular component or feature is not required to be included or have the characteristic.

[0031] No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more.” Further, as used herein, the article “the” is intended to include one or more items referenced in connection with the article “the” and may be used interchangeably with “the one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items (e.g., related items, unrelated items, or a combination of related and unrelated items), and may be used interchangeably with “one or more.” Where only one item is intended, the phrase “only one” or similar language is used. Also, as used herein, the terms “has,” “have,” “having,” or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and / or,” unless explicitly stated otherwise (e.g., if used in combination with “either” or “only one of’.

[0032] As used in the description herein and throughout the claims that follow, the meaning of “minimization drive test,” “MDT,” and “minimization of drive test” are same unless the context clearly dictates otherwise. As used in the description herein and throughout the claims that follow, the meaning of “base station,” “base stations,” and “BS” are same unless the context clearly dictates otherwise. As used in the description herein and throughout the claims that follow, the meaning of “invention,” and “disclosure” are same unless the context clearly dictates otherwise.

[0033] Embodiments explained herein relate to the field of wireless communication. In particular, the present disclosure provides a system and methods for optimizing minimization of drive test (MDT) data collection and reporting in next-generation wireless networks.

[0034] It should be noted that while aspects may be described herein using terminology commonly associated with a 5G or NR radio access technology (RAT), aspects of the present disclosure may be applied to other RATs, such as a 3G RAT, a 4G RAT, and / or a RAT subsequent to 5G (e.g., 6G, open radio access network (ORAN) technology).

[0035] Referring to FIG. 1, the proposed system (100) for optimizing minimization drive test (MDT) in a wireless communication network is shown, in accordance with one or more embodiments of the present disclosure. The system (100) may include a user equipment (UE) (102) and a base station (BS) (104). The UE (102) may be configured to transmit a UE capability message to the base station (104). Herein, the UE capability message indicates support for a feature, wherein the feature represents that the UE (102) includes a default set of self-MDT logged configurations. Herein, the default set of self-MDT logged configurations includes a default set of MDT logged parameters based on one or more UE conditions. Further, the UE (102) may also be configured to receive a control signal from the base station (104).

[0036] Herein, the control signal may include, but not limited to, an enable signal to, one of: enables and disables, the feature for the UE (102), and one or more trigger condition, wherein the UE (102) performs MDT measurement based on the one or more trigger conditions when the feature is enabled.

[0037] Further, the base station (104) may be configured to transmit the control signal to the UE (102) based on one or more network performance parameters that the base station (104) needs to, one or more of: monitor, optimize, and troubleshoot.

[0038] Further, the UE (102) may also be configured to perform the MDT measurement, based on the control signal, and using one of the default set of self-MDT logged configurations based on a UE condition from the one or more UE conditions. It should be noted that the system described herein may also include a plurality of UEs, and the various steps outlined in the present disclosure are equally applicable to all such UEs.

[0039] In an additional embodiment, the base station (104), may also be configured to evaluate the UE capability message based on one or more network performance parameters that the base station (104) needs to either monitor, optimize, or troubleshoot.

[0040] In an exemplary embodiment, the UE capability message refers to a signaling message transmitted by the user equipment (UE) (102) to the base station (104), indicating the UE’s support for specific features and capabilities. One such feature, as per the present invention (may also be referred as present disclosure) is that a UE (102) is configured to have a default set of self-MDT logged configurations. Herein, the default set of self-MDT logged configurations includes a default set of MDT logged parameters based on one or more UE conditions.

[0041] Further, the UE capability enables the UE (102) to autonomously perform and log MDT measurements without relying entirely on base station configurations. The featurerepresents that the UE (102) includes a default set of self-MDT logged configurations, which are pre-defined logging parameters tailored to various UE conditions such as, but not limited to, mobility, signal quality, and network congestion. Upon receiving the UE capability message, the base station (104) may enable or disable the feature based on current network requirements, such as performance monitoring, optimization, or troubleshooting needs. By incorporating the feature, the UE gains the flexibility to initiate MDT measurements independently, ensuring continuous data collection even when the base station (104) does not provide specific MDT configurations. This approach enhances network optimization by reducing dependency on base station (104)-triggered MDT processes and ensuring timely availability of critical network performance data.

[0042] In an exemplary embodiment, the default set of self-MDT logged configurations ensures consistent, reliable, and traceable data collection. The configurations may include the default set of MDT logged parameters, such as, but not limited to, timestamp configuration, data collection frequency, logging mode, data integrity check, sensor calibration, data storage configuration, transmission protocol, error logging, data format, logging level, anomaly detection threshold, sync configuration.

[0043] For instance, the timestamp configuration may utilize an ISO format (YYYY - MM-DD HH:MM:SS) to ensure precise time-based tracking of each logged event. The data collection frequency may be set to 1 minute by default, allowing periodic and balanced data collection while minimizing resource consumption. The logging mode may be configured as continuous, ensuring uninterrupted data capture, though alternate modes such as on-demand or event-driven may be supported for specific use cases. Additionally, the data integrity check may involve enabling a checksum mechanism to validate the accuracy and completeness of logged data during transmission. The sensor calibration setting may default to auto, allowing automated calibration at predefined intervals or upon initialization, while providing an option for manual calibration when necessary.

[0044] Further, the data storage configuration may default to local, where initial data logging occurs on the local storage medium, with an option to enable cloud or remote storage for redundancy or remote access. The transmission protocol may default to secure Hypertext Transfer Protocol Secure (HTTPS), ensuring encrypted and secure communication of logged data. The error logging feature may be enabled by default to automatically record any operational errors or issues encountered during data logging or transmission, aiding in troubleshooting and system maintenance. The data format may be set to JavaScript Object Notation (JSON), which offers flexibility in data parsing and integration with various externalsystems. The logging level may default to INFO, ensuring that general system activity, warnings, and errors are captured, with the capability to adjust the level to DEBUG for more detailed logging when required.

[0045] Furthermore, the anomaly detection threshold may be disabled (false) by default but can be activated in scenarios where real-time detection of anomalies or out-of-range values is critical. Finally, the sync configuration may default to a 24-hour interval, ensuring periodic synchronization of local logs with remote servers or cloud storage, thereby maintaining consistency across distributed systems. By setting default set of MDT logged parameters optimally or as per network requirement or as based on a UE condition, ensures that the self-MDT logging configurations are efficient and reliable, providing a robust framework for data-driven analysis and monitoring.

[0046] In an exemplary embodiment, the one or more trigger condition may include but is not limited to, the one or more trigger conditions may include, but are not limited to, specific geographical areas where MDT measurements need to be performed by the User Equipment (UE). For instance, when a network operator deploys new base stations or introduces a new Radio Access Technology (RAT) in a particular area, the base station may configure the particular area as a trigger condition for performing MDT measurements by the UE using one of associated default set of self-MDT logged configuration in the UE to collect network performance data from the particular area. Other trigger conditions may include specific time durations, such as nighttime or periods of low network traffic, during which network performance data is critical for optimization.

[0047] Further, the one or more trigger condition may also include network performance thresholds and / or criteria, such as areas with high call drop rates, excessive signal fluctuations, or throughput dips below acceptable levels. In scenarios involving NonTerrestrial Network (NTN) deployments, MDT measurements may be triggered to monitor performance in NTN-specific regions. Similarly, areas with high interference levels may require targeted MDT logging to identify and mitigate issues.

[0048] Additionally, the one or more trigger conditions may further include, but not limited to, handover zones where frequent handovers occur, such as at cell boundaries or in high-mobility scenarios like highways or railways, where the base station may require MDT data to optimize handover performance. Another trigger condition could involve specific UE states, such as idle mode or connected mode, where different types of measurements may be prioritized. Additionally, coverage holes or regions with weak signal strength can serve as trigger conditions to collect data for enhancing network coverage. High user density areas,such as stadiums, malls, or large event venues, may also trigger MDT logging to monitor network load and performance under heavy usage. Further, areas prone to weather-related signal degradation, such as mountainous regions or coastal areas, could be configured as trigger conditions, ensuring reliable performance under varying environmental factors. The diverse trigger conditions may enable comprehensive data collection for improving network reliability, capacity, and user experience.

[0049] In one or more embodiments, the UE (102) may further be configured to transmit data associated with the MDT measurement to the base station (104).

[0050] In one or more embodiments, the base station (104) may further be configured to transmit an MDT logged measurement configuration, including one or more parameters, to the UE (102). Further, the UE (102) may also be configured to receive the MDT logged measurement configuration and modify a default self-MDT logged configuration from the default set of self-MDT logged configurations based on the one or more parameters and a UE condition from the one or more UE conditions.

[0051] In one or more embodiments, the base station (104) may further be configured to store the UE capability information associated with the feature for the UE (102).

[0052] In one or more embodiments, the system (100), may further include a third-party server (106), configured to transmit an MDT logged measurement configuration, including one or more parameters, to the UE (102). Further, the UE (102) may also be configured to receive the MDT logged measurement configuration, the UE (102) may also be configured to modify a default self-MDT logged configuration from the default set of self-MDT logged configurations based on the one or more parameters and a UE condition from the one or more UE conditions.

[0053] In an exemplary embodiment, the one or more UE conditions may include, but not limited to, UE mobility, such as high mobility and low mobility scenarios. High mobility refers to situations where the UE is moving rapidly, such as in a vehicle or high-speed train, leading to frequent handovers and varying signal quality. In such cases, a default self-MDT logged configuration may specify a shorter logging interval and prioritize parameters related to handover performance and signal strength. Conversely, low mobility refers to scenarios where the UE remains stationary or moves slowly, such as when the user is indoors or walking. In the situations, a default self-MDT logged configuration may extend the logging interval and emphasize parameters such as signal stability and coverage gaps. By tailoring MDT logging parameters based on UE mobility, the embodiment ensures that relevant andhigh-quality data is collected, facilitating more effective network optimization and troubleshooting.

[0054] In an exemplary embodiment, the one or more UE conditions influencing the self- MDT logged configurations may also include, but not limited to signal quality, environmental context, battery level, connection type, network congestion, and application type.

[0055] Herein, the connection type refers to the specific network technology being used by the UE, such as 5G NR, LTE, or Wi-Fi offload. For instance, when the UE is connected to a 5G network, the self-MDT logging may prioritize parameters like beamforming performance, signal strength in millimeter-wave bands, and handover between 5G and LTE cells. Similarly, in dual connectivity scenarios where the UE simultaneously uses multiple RATs (e.g., LTE and 5G), the logging configuration may focus on metrics related to load balancing and dual -connectivity handovers. Additionally, the application type refers to the nature of the application currently consuming network resources. For real-time applications like video calls or online gaming, MDT logging may emphasize parameters such as latency, jitter, and packet loss to capture critical performance metrics. In contrast, for bulk data transfer applications such as file downloads or cloud backups, MDT logging may focus on throughput and error rates.

[0056] Additionally, the default self-MDT logged configuration can dynamically adapt based on other UE conditions such as signal quality and network congestion. When the UE detects poor signal quality (e.g., low RSRP or SINR values), the UE may increase the logging frequency to capture critical parameters for identifying weak coverage areas. In scenarios where the network experiences high congestion, parameters related to throughput, latency, and packet error rate may be prioritized to facilitate load-balancing and congestion mitigation analysis. Moreover, when the UE operates in an indoor environment, parameters such as penetration loss and multipath fading may be logged, while outdoor scenarios may focus on line-of-sight signal strength and interference from adjacent cells. The embodiments ensure efficient collection of data tailored to real-world conditions, enabling timely and effective network optimization.

[0057] In an embodiment, the base station (104) may enable the feature for the UE (102) based on one or more network performance parameters that the base station (104) needs to one or more of: monitor, optimize, and troubleshoot. Herein, the one or more network performance parameters may include, but are not limited to, signal quality and strength metrics such as reference signal received power (RSRP), reference signal received quality (RSRQ), signal-to-interference-plus-noise ratio (SINR), and received signal strength indicator(RSSI); interference metrics such as interference levels from neighboring cells, intermodulation distortion, and adjacent channel interference; handover and connectivity metrics including handover success rate, handover failure rate, radio link failure rate, and call setup success rate (CSSR).

[0058] Additionally, the network performance parameters may also include, but not limited to, data performance metrics such as throughput, latency, jitter, and packet loss rate; coverage and accessibility metrics such as coverage holes, cell accessibility rate, and blocked call rate; user equipment (UE)-related metrics such as UE battery status, device temperature, UE location, and mobility status.

[0059] Further, the network performance parameters may also include, but not limited to, traffic and load metrics such as traffic load, resource utilization, and load balancing efficiency; network reliability and stability metrics including call drop rate (CDR), session retention rate, and connection stability; and environmental and contextual metrics such as noise levels, signal propagation delay, and time-specific analysis. The network performance parameters provide comprehensive insights into the network's operational performance.

[0060] In an exemplary embodiment, the data associated with the MDT measurement refers to the logged information collected by the User Equipment (UE) (102) during the execution of minimization drive test (MDT) procedures. The data may include various network performance metrics such as, but not limited to, signal strength (e.g., RSRP and RSRQ), signal quality (e.g., SINR), handover events, cell ID information, and geolocation data (if available). The collected data is contextually relevant to the UE’s operating conditions, such as mobility status, signal environment, or ongoing network events. Once logged, the UE may transmit the data to the base station (104) or a third-party server (106) for further analysis. The transmitted MDT data enables network operators to monitor network performance in real time, identify coverage gaps, optimize handover performance, and improve overall quality of service.

[0061] In one exemplary embodiment, a base station (104) in a wireless communication network serves as a central node that facilitates communication between the UEs and the broader network. Examples of a base station (104) may include, but not limited to, macro base stations, which provide wide-area coverage; micro base stations, which cover smaller areas such as urban environments; and pico and femto base stations, which are used for even smaller coverage areas, such as within buildings. The base stations are equipped with advanced processing capabilities to receive and evaluate a UE capability message from a UE.

[0062] In one exemplary embodiment, the base station (104) in a wireless communication network may include a transceiver, a processor, and a memory configured to manage communications with multiple user equipment (UE) (102) devices within its coverage area. The transceiver is equipped to transmit and receive radio signals across multiple frequency bands, supporting various communication standards such as LTE, 5G NR, or Wi-Fi. The processor is designed to perform advanced signal processing, scheduling, and resource allocation tasks to optimize network performance and reduce interference. Additionally, the memory stores software instructions, including protocols for adaptive modulation, beamforming, and handover procedures, ensuring seamless connectivity. For instance, the base station may dynamically adjust transmission power and frequency to maintain stable links with mobile devices during high-speed movement or in environments with dense obstructions. The base station may further include Machine Learning (ML) algorithms implemented in the processor to enhance network efficiency by predicting traffic patterns and optimizing resource utilization.

[0063] In an exemplary embodiment, Artificial Intelligence (Al) and Machine Learning (ML) algorithms may be used at the base station (104) to enhance the analysis and utilization of minimization drive test (MDT) data. By leveraging MDT data patterns, the algorithms may identify potential network issues such as coverage gaps, high interference zones, or regions with frequent call drops. The AI / ML models analyze historical and real-time MDT datasets, extracting meaningful insights from various features such as signal quality metrics (RSRP, RSRQ, SINR), handover performance, radio link failures, and UE location information. The features serve as input labels, enabling the models to detect patterns indicative of network performance problems. For instance, areas with consistently low RSRP values or high handover failures can be flagged as problematic, allowing the network operator to prioritize optimization efforts.

[0064] In an exemplary embodiment, integration of GPS or positioning systems in the one or more UEs (102) may help accurately map network issues to specific geographic locations, enabling precise identification of problematic areas. MDT data, when combined with geolocation data, allows network operators to optimize coverage in specific zones.

[0065] The use of machine learning models as mentioned above may enable dynamic and proactive network management. Historical MDT data may be utilized to train supervised or semi-supervised models to identify trends and predict future network performance. For example, clustering algorithms might group areas based on similar performance characteristics, while regression models forecast degradation in signal quality. The predictivecapability allows the network to configure MDT measurement configurations more intelligently, focusing on specific UEs and regions that are likely to experience performance issues. By doing so, the system minimizes redundant measurements and ensures that resources are efficiently allocated. Additionally, the models can dynamically adjust MDT parameters such as logging frequency, reporting intervals, or the choice of UEs, tailoring the tasks to current network conditions and anticipated requirements. The AI / ML-driven approach not only reduces operational costs but also enhances the overall user experience by maintaining robust and optimized network performance.

[0066] In one exemplary embodiment, the base station (104) in a wireless communication network may also include, but not limited to, an eNodeB (evolved Node B) for LTE or a gNB (next-generation Node B) for 5G NR. The eNodeB may manage resource scheduling and mobility management in an LTE network, while the gNB can leverage advanced features like beamforming and massive MIMO to enhance data throughput and coverage in a 5G network. The transceiver is designed to handle diverse frequency ranges, including sub-6 GHz and millimeter-wave bands, to support various scenarios such as urban densification and rural connectivity. The processor in the nodes implements protocols for inter-node communication, such as X2 for eNodeBs or Xn for gNBs, enabling seamless handovers and efficient inter-cell coordination.

[0067] Further, some future advancements may decentralize the base station (104) functionality, distributing tasks such as, but not limited to, resource allocation and signal processing across other network elements, such as edge servers or user devices, to enhance efficiency. For example, in a Cloud-RAN (C-RAN) architecture, centralized units (CUs) might take over functions traditionally handled by base stations, while distributed units (DUs) handle real-time processing. Similarly, the base station’s role may be expanded in ultrareliable low-latency communication (URLLC) scenarios, with functionalities like predictive analytics and Al-driven network optimization being offloaded to edge devices or data centers. The enhancements pave the way for a more flexible, software-defined approach to network management, supporting future applications like autonomous vehicles, industrial loT, and immersive AR / VR experiences.

[0068] In an exemplary embodiment, the base station (104) may be configured to enable the feature for one or more UEs (102) dynamically, selectively or non-selectively, based on predicted network requirements of a specific area. However, the base station (104) may also be configured to enable the feature for a UE (102) based on one or more networkperformance parameters that the base station (104) needs to one or more of: monitor, optimize, and troubleshoot.

[0069] In an exemplary embodiment, the UE (102) may include a wide range of devices that are capable of wireless communication. Examples of UEs (102) include, but are not limited to, a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, biometric sensors / devices, wearable devices (smart watches, smart clothing, smart glasses, smart wrist bands, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music or video device, or a satellite radio), a vehicular component or sensor, smart meters / sensors, industrial manufacturing equipment, a global positioning system device, any other suitable device that is configured to communicate via a wireless or wired medium and other portable communication devices.

[0070] Further, the UE (102) may be equipped with the necessary hardware, firmware and software to monitor network parameters, such as, but not limited to, signal strength and quality, and local parameters, such as battery status, device temperature, UE location, timestamp, serving cell information, neighbor cell information. The UE (102) may also support checking and / or transmitting UE capability information such as, but not limited to, support for the feature. Herein, the feature represents that the UE (102) includes a default set of self-MDT logged configurations, wherein the default set of self-MDT logged configurations includes a default set of MDT logged parameters based on one or more UE conditions.

[0071] In an exemplary embodiment, a third-party server (106) may refer to an external network entity that can participate in the collection, processing, or configuration of minimization drive test (MDT) data. The third-party server (106) may be operated by entities such as network analytics providers, service optimization platforms, or infrastructure vendors. In scenarios where the base station (104) does not directly configure the MDT parameters, the third-party server (106) may transmit an MDT logged measurement configuration to a user equipment (UE) (102).

[0072] Further, the configuration may include parameters such as logging interval, measurement duration, and specific metrics to be collected by the UE (102). Upon receiving the configuration, the UE (102) modifies its default self-MDT logged settings accordingly and begins logging data based on the provided instructions. The logged data may then betransmited back to the third-party server (106) for detailed analysis, which can include network performance evaluation, identification of problem areas, and generation of optimization insights. By involving a third-party server, enables more flexible and scalable MDT operations, allowing network operators to leverage advanced analytics and external expertise for improving network quality.

[0073] In an exemplary embodiment, the third-party servers (106) may include various types of external entities involved in network performance management and optimization e.g., servers operated by Original Equipment Manufacturers (OEMs). Examples include, but not limited to network analytics servers, which analyze MDT data to identify coverage gaps, signal interference, or handover issues; optimization servers, which generate recommendations for network tuning based on real-time and historical MDT data; and infrastructure monitoring servers, which track and report the health and performance of network equipment. Additionally, cloud-based data aggregation platforms may act as third- party servers by collecting MDT data from multiple UEs across different regions and providing insights to network operators for large-scale performance optimization. The third- party servers may also include research and development platforms used by telecom vendors to study advanced Radio Access Technologies (RATs) and improve future deployments based on real-world data. By utilizing such third-party servers, network operators gain access to specialized tools and services that enhance their ability to maintain and optimize complex heterogeneous networks.

[0074] It should be noted that other components of a wireless communication network, such as, but not limited to, a core network, cloud infrastructure, and network management system, are assumed to be present and operational, even if not explicitly discussed in the present disclosure, for the suitability and completeness of the implementation. The components, while not elaborated upon, play essential roles in enabling and supporting the disclosed embodiments.

[0075] A wireless network may also incorporate relay stations. A relay station is a device that may accept data transmissions from upstream stations (such as base stations or UEs) and deliver them to downstream stations. A relay station may also be a UE capable of relaying transmissions for other UEs. A wireless network may be a heterogeneous network with base stations of many sorts, such as macro base stations, pico base stations, femto base stations, relay base stations, and so on. The various types of base stations may have varied transmit power levels, coverage areas, and impacts on interference in the wireless network.

[0076] Referring to FIG. 2, a flow diagram for implementing the steps of the proposed method (200) for optimizing minimization drive test (MDT) in a wireless communication network is shown. In one or more embodiments, the method (200) may be implemented by the system (100).

[0077] At step (202), the method (200) includes transmitting, by a user equipment (UE) (102), a UE capability message to a base station (104). Herein, the UE capability message indicates support for a feature. Herein the feature represents that the UE (102) includes a default set of self-MDT logged configurations, wherein the default set of self-MDT logged configurations includes a default set of MDT logged parameters based on one or more UE conditions.

[0078] At step (204), the method (200) includes receiving (204), by the base station (104), the UE capability message from the UE (102).

[0079] At step (206), the method (200) includes transmitting (206), by the base station (104), a control signal to the UE (102) based on one or more network performance parameters that the base station (104) needs to, one or more of: monitor, optimize, and troubleshoot. Herein, the control signal may include an enable signal to, one of: enables and disables, the feature for the UE (102), and one or more trigger condition. Herein the UE (102) performs MDT measurement based on the one or more trigger conditions when the feature is enabled.

[0080] At step (207), the method (200) includes, receiving, by the UE (102), the control signal from the base station (104).

[0081] At step (208), the method (200) includes performing, by the UE (102), the MDT measurement, based on the control signal, and using one of the default set of self-MDT logged configurations based on a UE condition from the one or more UE conditions.

[0082] In one or more embodiments, the method (200) may further include transmitting (210), by the UE (102), data associated with the MDT measurement to the base station (104).

[0083] In one or more embodiments, the method (200) may further include transmitting (212), by one of: the base station (104) and a third-party server (106), an MDT logged measurement configuration, including one or more parameters, to the UE (102). The method (200) may also include receiving (214), by the UE (102), the MDT logged measurement configuration. The method (200) may also include modifying (216), by the UE (102), a default self-MDT logged configuration from the default set of self-MDT logged configurations based on the one or more parameters and a UE condition from the one or more UE conditions.

[0084] In one or more embodiments, the method (200) may further include storing (218), the base station (104), the UE capability information associated with the feature for the UE (102).

[0085] It should be noted that the steps for executing the method (200) described herein are not limited to the specific steps outlined above. The method may be implemented in various other ways, and the steps may be reordered, combined, or modified without departing from the scope and spirit of the invention. The examples provided are for illustrative purposes only and are not intended to limit the invention to the specific embodiments disclosed. Those skilled in the art will recognize that various modifications and adaptations can be made to the method without departing from the broader inventive concepts disclosed herein.

[0086] While aspects are described in the present disclosure by illustration to some examples, those skilled in the art will understand that such aspects may be implemented in many different arrangements and scenarios. Techniques described herein may be implemented using different platform types, devices, systems, shapes, sizes, and / or packaging arrangements. For example, some aspects may be implemented via integrated chip embodiments or other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, or artificial intelligence-enabled devices). Aspects may be implemented in chip-level components, modular components, non-modular components, non- chip-level components, device-level components, or system-level components. Devices incorporating described aspects and features may include additional components and features for implementation and practice of claimed and described aspects. For example, transmission and reception of wireless signals may include a number of components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffer, processors, interleavers, adders, or summers). It is intended that aspects described herein may be practiced in a wide variety of devices, components, systems, distributed arrangements, or end-user devices of varying size, shape, and constitution.

[0087] Even though particular combinations of features are recited in the claims and / or disclosed in the specification, the combinations are not intended to limit the disclosure of various aspects. In fact, many of the features may be combined in ways not specifically recited in the claims and / or disclosed in the specification. Although each dependent claim listed below may directly depend on only one claim, the disclosure of various aspects includes each dependent claim in combination with every other claim in the claim set.

[0088] While the foregoing describes various embodiments of the invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof. The scope of the invention is determined by the claims that follow. The invention is not limited to the described embodiments, versions or examples, which are included to enable a person having ordinary skill in the art to make and use the invention when combined with information and knowledge available to the person having ordinary skill in the art.

[0089] A person with ordinary skills in the art will appreciate that the systems, modules, and sub-modules have been illustrated and explained to serve as examples and should not be considered limiting in any manner. It will be further appreciated that the variants of the above-disclosed system elements, modules, and other features and functions, or alternatives thereof, may be combined to create other different systems or applications.

[0090] Those skilled in the art will appreciate that any of the aforementioned steps and / or system modules may be suitably replaced, reordered, or removed, and additional steps and / or system modules may be inserted, depending on the needs of a particular application. In addition, the systems of the aforementioned embodiments may be implemented using a wide variety of suitable processes and system modules, and are not limited to any particular computer hardware, software, middleware, firmware, microcode, and the like. The claims can encompass embodiments for hardware and software or a combination thereof.

[0091] While the present disclosure has been described with reference to certain embodiments, it will be understood by those skilled in the art that various changes may be made, and equivalents may be substituted without departing from the scope of the present disclosure. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the present disclosure without departing from its scope. Therefore, it is intended that the present disclosure not be limited to the particular embodiment disclosed, but that the present disclosure will include all embodiments falling within the scope of the appended claims.ADVANTAGES OF THE PRESENT DISLCOSURE

[0092] The present disclosure provides a system and a method for autonomously performing and logging MDT measurements using a default set of self-MDT logged configurations, reducing dependency on base station-triggered MDT processes and ensuring continuous real time need data collection

[0093] The present disclosure provides a new feature of default set of self-MDT logged configurations in a UE for consistent, reliable, and traceable data collection, providing a robust framework for data-driven analysis and monitoring.

[0094] The present disclosure provides a system for dynamic optimization of MDT measurement parameters based on real-time field conditions, such as signal quality, network congestion, and UE mobility, enhancing the relevance and quality of the collected data.

[0095] The present disclosure provides a system for the transmission of MDT logged measurement configurations from a base station or a third-party server to the UE, allowing the UE to modify its default self-MDT logged configurations based on received parameters and UE conditions.

[0096] The present disclosure addresses the limitations and challenges of existing MDT frameworks, as well as in the context of next-generation wireless networks such as 5G and 6G, ensuring readiness for future advancements in wireless communication technologies.

Claims

I Claim:

1. A method (200) for optimizing minimization drive test (MDT) in a wireless communication network, performed by a user equipment (UE), the method (200) comprising: transmitting (202) a UE capability message to a base station (104), wherein the UE capability message indicates support for a feature, wherein the feature represents that the UE (102) comprises a default set of self-MDT logged configurations, and wherein the default set of self-MDT logged configurations comprises a default set of MDT logged parameters based on one or more UE conditions; receiving (207) a control signal from the base station (104) based on one or more network performance parameters that the base station (104) needs to, one or more of: monitor, optimize, and troubleshoot, wherein the control signal comprises: an enable signal to, one of: enable and disable, the feature for the UE (102), and one or more trigger conditions, wherein the UE (102) performs MDT measurement based on the one or more trigger conditions when the feature is enabled; and performing (208) the MDT measurement based on the control signal, and using one of the default set of self-MDT logged configurations based on a UE condition from the one or more UE conditions.

2. The method (200) as claimed in claim 1, wherein the method (200) further comprises: transmitting (210), by the UE (102), data associated with the MDT measurement to the base station (104).

3. The method (200) as claimed in claim 1, wherein the method (200) further comprises: receiving (214), by the UE (102), from one of: the base station (104) and a third- party server (106), an MDT logged measurement configuration, comprising one or more parameters; and modifying (216), by the UE (102), a default self-MDT logged configuration from the default set of self-MDT logged configurations based on the one or more parameters and a UE condition from the one or more UE conditions.

4. A system (100) for optimizing minimization drive test (MDT) in a wireless communication network, the system (100) comprising: a user equipment (UE) (102) and a base station (104), wherein:the UE (102) is configured to: transmit a UE capability message to the base station (104), wherein the UE capability message indicates support for a feature, wherein the feature represents that the UE (102) comprises a default set of self-MDT logged configurations, and wherein the default set of self-MDT logged configurations comprises a default set of MDT logged parameters based on one or more UE conditions; and receive a control signal from the base station (104), and the base station (104) is configured to: receive the UE capability message from the UE (102); and transmit the control signal to the UE (102) based on one or more network performance parameters that the base station (104) needs to, one or more of: monitor, optimize, and troubleshoot, wherein the control signal comprises: an enable signal to, one of: enable and disable, the feature for the UE (102), and one or more trigger conditions, wherein the UE (102) performs MDT measurement based on the one or more trigger conditions when the feature is enabled, wherein the UE (102) is configured to perform the MDT measurement based on the control signal, and using one of the default set of self-MDT logged configurations based on a UE condition from the one or more UE conditions.

5. The system (100) as claimed in claim 4, wherein the UE (102) is further configured to transmit data associated with the MDT measurement to the base station (104).

6. The system (100) as claimed in claim 4, wherein: the base station (104) is further configured to transmit an MDT logged measurement configuration, comprising one or more parameters, to the UE (102), and the UE (102) is further configured to: receive the MDT logged measurement configuration; and modify a default self-MDT logged configuration from the default set of self-MDT logged configurations based on the one or more parameters and the UE condition from the one or more UE conditions.

7. The system (100) as claimed in claim 4, wherein the base station (104) is further configured to store the UE capability information associated with the feature for the UE (102).

8. The system (100) as claimed in claim 4, wherein the system (100) further comprises a third-party server (106), configured to transmit an MDT logged measurement configuration, comprising one or more parameters, to the UE (102), and the UE (102) is further configured to: receive the MDT logged measurement configuration; and modify a default self-MDT logged configuration from the default set of self-MDT logged configurations based on the one or more parameters and a UE condition from the one or more UE conditions.

Images