UE-Initiated CLI Reporting for Random Cross-Link Interference
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current CLI reporting procedures in wireless communications systems are inadequate in addressing the randomness and unpredictability of UE-to-UE cross-link interference, leading to high bit error rates and inefficient resource utilization, with periodic reporting causing excessive overhead and aperiodic reporting being ineffective due to unawareness of interference occurrences.
Innovation Solution
UE-initiated and event-driven CLI reporting procedures, where a victim UE determines CLI events and requests resources for sending reports, minimizing issues associated with periodic or aperiodic reporting and enabling quick and efficient mitigation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If periodic CLI reporting is used, then CLI monitoring is continuous, but resource overhead increases excessively
Solution Approach 1:
The patent implements event-triggered periodic reporting where the UE sends CLI reports only when specific events occur (such as when CLI measurements exceed thresholds or when entering/leaving coverage areas), rather than using continuous periodic reporting. This event-driven approach maintains reliable CLI monitoring while significantly reducing the frequency of reports and associated resource overhead.
Solution Approach 2:
The UE autonomously determines when to initiate CLI reporting based on locally measured events and conditions, without requiring continuous network scheduling. The UE self-manages the reporting process by monitoring its own CLI measurements and independently deciding when reports are necessary, thereby reducing network resource consumption while maintaining monitoring effectiveness.
2Quantity of substance
If aperiodic CLI reporting is used, then resource overhead is reduced, but effectiveness decreases due to unawareness of interference occurrences
Solution Approach 1:
The patent establishes a feedback mechanism where the UE continuously monitors CLI measurements and compares them against configured thresholds. When measurements indicate interference events (such as exceeding thresholds or detecting coverage changes), the UE provides feedback by initiating CLI reports. This feedback-driven approach ensures reports are sent only when actually needed, maintaining effectiveness while reducing overhead.
Solution Approach 2:
The network pre-configures the UE with CLI measurement parameters, thresholds, and reporting conditions before the UE begins monitoring. This preliminary configuration enables the UE to autonomously determine when reporting is necessary based on pre-established criteria, ensuring that aperiodic reporting remains effective without requiring continuous network intervention or excessive resource allocation.
3Quantity of substance
If network-scheduled CLI reporting is used, then reporting resources are allocated, but UE autonomy and responsiveness are reduced
Solution Approach 1:
Instead of the network scheduling and controlling CLI reporting transmissions, the patent inverts the control relationship by enabling the UE to autonomously initiate reports based on its own measurements and events. The network provides initial configuration and resources, but the UE determines timing and necessity of reports, thereby increasing UE autonomy and responsiveness while maintaining efficient resource utilization.
Solution Approach 2:
The patent implements dynamic CLI reporting where the reporting behavior adapts to real-time conditions. The UE can adjust its reporting behavior based on measured events, coverage changes, and interference levels, making the system responsive to dynamic conditions rather than following rigid network-scheduled patterns. This dynamic approach enhances UE autonomy while maintaining efficient resource usage.
Data Source
AI summary
Various aspects of the present disclosure relate to a user equipment (UE) being enabled to control performance of cross-link interference (CLI) reporting procedures, such as via UE-initiated and/or event-driven CLI reporting procedures. For example, a victim UE identifies and/or determines occurrences of CLI events at or associated with the UE and requests resources (e.g., resources associated with uplink (UL) grants) for sending CLI reports in response to the CLI events (e.g., CLI report triggering events).


