UE MDT and QoE Reporting Triggered by Application Start
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing wireless communication systems face challenges in efficiently collecting and reporting minimization of drive test (MDT) and quality of experience (QoE) measurements, particularly in relation to application and network slice-based measurements, which can impact communication quality and device performance.
Innovation Solution
The solution involves devices like user equipment (UE) and serving base stations collecting immediate MDT and QoE measurements based on application or service triggers, with measurement configurations adjusting reporting intervals and amounts based on network slicing, area configurations, and time of day, and generating reports for centralized servers to enhance communication quality and efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the UE performs MDT and QoE measurements based on application or service triggers, then the network can obtain timely measurement data for quality verification, but the device complexity and power consumption increase due to continuous monitoring and reporting
Solution Approach 1:
The measurement system is segmented into trigger-based events rather than continuous monitoring. The UE monitors for specific application or service start events that trigger measurement collection, rather than continuously monitoring all applications. This event-driven approach reduces device complexity while maintaining reliable quality verification when needed.
Solution Approach 2:
The network pre-configures the UE with measurement parameters, thresholds, and reporting requirements before the actual measurements are needed. The UE is prepared with the necessary measurement configurations in advance, so when a trigger event occurs, the measurements can be performed immediately without complex real-time decision-making, reducing device complexity.
2Loss of information
If the UE reports MDT and QoE measurements frequently, then the network gains real-time insights into network performance, but the loss of time and energy increases due to continuous reporting overhead
Solution Approach 1:
Instead of continuous reporting, the system uses periodic or event-triggered reporting based on application or service start events. The UE reports measurements at specific intervals or when predefined events occur, rather than continuously. This reduces time overhead while still providing the network with necessary performance information at meaningful intervals.
Solution Approach 2:
The system extracts and reports only the most relevant measurement data that indicates network performance changes, rather than reporting all possible measurements continuously. By selecting and reporting only critical performance indicators triggered by specific events, the system reduces reporting overhead while maintaining effective network performance monitoring.
3Adaptability or versatility
If the measurement configuration includes multiple triggering events for MDT measurements, then the network can assess various service qualities, but the device complexity increases due to managing multiple trigger conditions
Solution Approach 1:
The measurement system uses a universal trigger mechanism that can handle multiple different application or service start events through a common event-driven architecture. Rather than implementing separate complex monitoring logic for each service type, the system uses a unified approach where the UE monitors for a category of events (application/service starts) and applies pre-configured measurement rules, reducing device complexity while maintaining versatility in assessing different service qualities.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
In some wireless communications systems, devices may support minimization of drive test (MDT) reporting, quality of service (QoS) reporting, and quality of experience (QoE) measurements. A user equipment (UE) and the serving base station may obtain measurements in accordance with a measurement configuration that indicates various triggering events or reporting adjustment factors associated with the measurements. The measurement configuration may indicate a triggering event such as the start of an application or service at the UE, and the UE may obtain MDT or QoE measurements based on identifying the application or service. Additionally, the serving base station may obtain MDT and QoE measurements based on identifying the application and service or a notification from the UE. The UE and the serving base station may identify reporting adjustment factors based on network slicing, area configurations and times of the day affecting the reporting interval and reporting amount for the measurement report.