Terminal Latency Bound for Channel State Information Reporting
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In the inter-terminal direct communication in the NR, the timing of reporting Channel State Information (CSI) is not specified, leading to potential delays in CSI reports, which can subsequently delay data transmission.
Innovation Solution
A terminal is equipped with a transmission unit to request channel state information and a reference signal, a control unit to configure a latency bound for the CSI report, and a reception unit to receive the CSI report before the specified latency bound. The control unit also manages the CSI report based on Hybrid Automatic Repeat Request (HARQ) feedback and configures specific latency bounds for multiple CSI requests.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If no latency bound is specified for CSI report timing, then the system maintains flexibility in reporting timing, but the CSI report may be delayed causing subsequent data transmission to be delayed
Solution Approach 1:
The transmitting terminal specifies the latency bound for the CSI report in advance when sending the CSI request. This preliminary action defines the maximum acceptable delay before the CSI report should be received, allowing the receiving terminal to prioritize and timely send the report within the specified time frame, thus preventing subsequent data transmission delays.
2Reliability
If a latency bound is configured for CSI report timing, then the timing of CSI reports is clarified and data transmission is prevented from being delayed, but the system requires additional configuration parameters and control operations
Solution Approach 1:
The transmitting terminal sends a CSI request including a latency bound to the receiving terminal. The receiving terminal uses this feedback parameter to determine when to send the CSI report, ensuring it meets the timing requirement. This feedback mechanism allows the system to adapt to different timing requirements without complex centralized control.
Solution Approach 2:
The system introduces a configurable latency bound parameter that can be adjusted based on different service requirements. By changing this single parameter, the system can flexibly control the timing of CSI reports without redesigning the entire communication protocol, thus managing complexity while ensuring reliability.
3Reliability
If multiple CSI requests are transmitted for the same channel state report event, then the system can ensure receipt of CSI reports under different conditions, but managing multiple latency bounds increases control complexity
Solution Approach 1:
When multiple CSI requests are sent for the same channel state report event, each request is segmented with its own specific latency bound parameter. This allows the receiving terminal to process each request independently with appropriate timing requirements, ensuring reliable report reception while keeping the management of each request's timing separate and manageable.
Data Source
AI summary
A terminal includes a transmission unit that transmits a request for channel state information and one or more shared channels including a reference signal to another terminal, a control unit that configures a latency bound for a channel state report triggered by the request, and a reception unit that receives the channel state report triggered by the request, before the latency bound from the other terminal, wherein the control unit performs at least one of: an operation of controlling the channel state report based on reception of a HARQ feedback in a case where the reception unit receives the HARQ feedback corresponding to the request; and an operation of configuring a specific latency bound for each of multiple requests for the channel state information in a case where the transmission unit transmits the multiple requests for the channel state information corresponding to a channel state report event.