Terminal CSI Trigger-State Mapping for Multiple DCI Formats
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current wireless communication systems support only one DCI format to trigger an aperiodic CSI report, limiting flexibility and efficiency for multiple service types, such as eMBB, URLLC, and mMTC in 5G cellular systems.
Innovation Solution
Implementing multiple DCI formats to trigger aperiodic CSI reports, allowing selection of CSI trigger states based on the number of bits in the CSI request field, enhancing communication flexibility and efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If only one DCI format is used to trigger aperiodic CSI report, then the system is simpler to implement, but communication flexibility and efficiency for multiple service types deteriorates
Solution Approach 1:
The patent enables a single DCI format to serve multiple service types (eMBB, URLLC, mMTC) by configuring different CSI trigger states that correspond to different service requirements. The base station can selectively trigger appropriate CSI reports based on service type using the same DCI format structure, making the system universal across diverse 5G services without requiring separate DCI formats for each service type.
Solution Approach 2:
The patent changes the parameters within the DCI format, specifically the CSI request field values, to indicate different trigger states that correspond to different service types. By varying the CSI trigger state parameters rather than the DCI format structure itself, the system achieves adaptability for multiple services while maintaining structural simplicity.
2Adaptability or versatility
If multiple DCI formats are supported to trigger CSI reports, then communication flexibility and efficiency improve, but device complexity increases
Solution Approach 1:
The patent uses a copying approach where multiple CSI trigger states are configured with similar structures but different parameter values. Instead of creating entirely different DCI formats for each service type, the system copies the basic DCI format structure and varies the CSI request field values to point to different trigger states, reducing processing complexity while maintaining versatility.
Solution Approach 2:
The patent segments the CSI reporting functionality by dividing it into multiple trigger states, each optimized for different service types. The DCI format contains a segmented CSI request field that can selectively activate specific trigger states, allowing the terminal to process only relevant CSI reporting configurations rather than handling all possible formats simultaneously, thus reducing overall complexity.
3Adaptability or versatility
If the number of CSI trigger states exceeds 2^N_TS-1, then more service types can be supported, but mapping complexity increases
Solution Approach 1:
The patent resolves the mapping complexity by introducing an additional dimension through RRC configuration. Instead of trying to map all trigger states directly within the limited codepoint space, the system uses RRC to pre-configure associations between codepoints and trigger states, effectively adding a configuration layer that simplifies the runtime mapping process while supporting extensive numbers of trigger states.
Solution Approach 2:
The patent applies preliminary action by pre-configuring the mapping relationships between codepoints and CSI trigger states through RRC signaling before actual CSI reporting occurs. This advance configuration eliminates complex runtime mapping decisions, as the terminal already has predetermined associations established, thereby reducing processing complexity while supporting a large number of trigger states.
Data Source
AI summary
A method by a user equipment (UE) is described. The method includes receiving, from a base station, a first radio resource control (RRC) parameter including a first list of one or more CSI trigger states, a second RRC parameter indicating a first total number of bits N_TS1 for a first CSI request field of a first DCI format, a third RRC parameter including a second list of one or more CSI trigger states, and a fourth RRC parameter indicating a second total number of bits N_TS2 for a second CSI request field of a second DCI format, determining a CSI trigger state in response to a CSI request field of a DCI format, wherein in a first case that a total number of the one or more CSI trigger states within the first list is greater than 2N_TS1 1, the processing circuitry is further configured to select one or more of the CSI trigger states out of the first list which are mapped to one or more codepoints of the first CSI request field of the first DCI format, in a second case that a total number of the one or more CSI trigger states within the second list is greater than 2N_TS2−1, the processing circuitry is further configured to select one or more of the CSI trigger states out of the second list which are mapped to one or more codepoints of the second CSI request field of the second DCI format.