Downlink DCI Triggering Aperiodic CSI on PUCCH
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current NR specifications only support aperiodic CSI feedback on the physical uplink shared channel (PUSCH) via uplink-related DCI formats, which is not flexible in downlink-heavy scenarios where PDSCH is more frequently scheduled via downlink-related DCI formats, limiting network scheduling flexibility.
Innovation Solution
Incorporating a CSI request field in downlink-related DCI to trigger aperiodic CSI reports on the PUCCH, allowing PUCCH resource configuration for A-CSI feedback, and enabling A-CSI transmission without relying on an uplink grant, with support for repetition to enhance reliability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If aperiodic CSI feedback is only supported on PUSCH via uplink-related DCI formats, then the system maintains simple resource allocation, but network scheduling flexibility deteriorates in downlink-heavy scenarios
Solution Approach 1:
The patent enables downlink-related DCI formats (originally designed for PDSCH scheduling) to also trigger aperiodic CSI reports, making these DCI formats multi-functional. This allows the same DCI structure to serve both scheduling and CSI triggering purposes, improving network scheduling flexibility without requiring entirely new signaling mechanisms.
Solution Approach 2:
The patent introduces dynamic resource allocation for aperiodic CSI on PUCCH by allowing the gNB to trigger CSI reports flexibly through DCI formats 1_1 and 1_2. The PUCCH resource selection can be dynamically indicated through the PUCCH resource indicator (PRI) field in the DCI, enabling adaptive resource allocation based on downlink traffic conditions.
2Productivity
If A-CSI reporting is enabled on PUCCH triggered by downlink DCI, then scheduling flexibility improves, but device complexity increases due to additional resource configuration
Solution Approach 1:
The patent leverages existing PUCCH resource configuration mechanisms and DCI structures to enable A-CSI triggering. The system uses already-configured PUCCH resources and existing DCI fields (such as PRI) for their additional CSI-triggering function, rather than requiring entirely new configuration procedures. This self-service approach minimizes additional configuration overhead.
Solution Approach 2:
Existing DCI fields such as the PUCCH resource indicator are made multi-functional, serving both their original purposes and new CSI-triggering functions. This universal usage of existing structures reduces the need for additional configuration elements and simplifies the overall system complexity.
3Productivity
If A-CSI is transmitted without uplink grant, then scheduling efficiency improves, but reliability deteriorates compared to PUSCH-based transmission
Solution Approach 1:
The patent enables the system to change the transmission parameter (channel type) dynamically based on scheduling needs. A-CSI can be transmitted on PUCCH for efficiency when uplink grants are not available, while the system maintains the option to use PUSCH for more reliable transmission when needed, adapting to different operational conditions.
Solution Approach 2:
The patent introduces repetition mechanisms for PUCCH-based A-CSI transmission to cushion against potential transmission failures. By allowing multiple repetitions of the A-CSI report on PUCCH, the system compensates for the lower inherent reliability of PUCCH compared to PUSCH, ensuring successful delivery without requiring uplink grants.
Data Source
AI summary
According to some embodiments, a method implemented by a network node in a communication network for obtaining channel state information (CSI) comprises generating a downlink control information (DCI) to trigger an aperiodic CSI (A-CSI) reporting via a physical uplink control channel (PUCCH) and transmitting the DCI to a terminal device to initiate A-CSI reporting on the PUCCH.