CN115918136A

CN115918136A - Channel state information triggering and reporting

Info

Publication number: CN115918136A
Application number: CN202080101893.2A
Authority: CN
Inventors: 张煜; L·肖; 陈万士; P·盖尔
Original assignee: Qualcomm Inc
Current assignee: Qualcomm Inc
Priority date: 2020-06-15
Filing date: 2020-06-15
Publication date: 2023-04-04
Also published as: EP4165896A4; WO2021253161A1; US20230198593A1; TW202203679A; KR20230024278A; EP4165896A1; BR112022024716A2; JP2023534383A

Abstract

Methods relate to wireless communication systems and scheduling channel state information operations and transmissions. A User Equipment (UE) receives a Channel State Information (CSI) calculation request from a Base Station (BS). The UE then identifies a first CSI measurement resource based on the CSI computation request. The UE determines CSI based on the first CSI measurement resource and receives a CSI report transmission request associated with the first CSI measurement resource from the BS. The UE may optionally transmit a CSI report to the BS based on the first CSI measurement resource or a different CSI measurement resource. Other features are also claimed and described.

Description

Channel state information triggering and reporting

Technical Field

The following discussion relates generally to wireless communication systems, and more particularly to channel state information triggering and reporting. Certain embodiments may implement and provide techniques that allow a base station to efficiently acquire channel state information from user equipment (e.g., without unnecessarily blocking other uplink scheduling during channel state information calculations).

Introduction to the design reside in

Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be able to support communication with multiple users by sharing the available system resources (e.g., time, frequency, and power). A wireless multiple-access communication system may include several Base Stations (BSs), each supporting communication for multiple communication devices (e.g., user Equipments (UEs)) simultaneously.

To meet the growing demand for extended mobile broadband connectivity, wireless communication technologies are advancing from Long Term Evolution (LTE) technology to the next generation of New Radio (NR) technology, which may be referred to as the fifth generation (5G). For example, NR is designed to provide lower latency, higher bandwidth or higher throughput, and higher reliability compared to LTE. NR is designed to operate over a wide range of frequency bands, for example, from low frequency bands below about 1 gigahertz (GHz) and intermediate frequency bands from about 1GHz to about 6GHz, to high frequency bands, such as the millimeter wave (mmWave) band. NR is also designed to operate across different spectrum types, from licensed spectrum to unlicensed and shared spectrum. As use cases and diverse deployment scenarios continue to expand in wireless communications, improvements in coding techniques may also bring benefits.

Brief summary of some examples

The following presents a simplified summary of some aspects of the disclosure in order to provide a basic understanding of the technology discussed. This summary is not an extensive overview of all contemplated features of the disclosure, and is intended to neither identify key or critical elements of all aspects of the disclosure, nor delineate the scope of any or all aspects of the disclosure. Its sole purpose is to present some concepts of one or more aspects of the disclosure in a general form as a prelude to the more detailed description that is presented later.

Some aspects of the present disclosure implement and provide mechanisms and techniques that enable a UE to determine and provide CSI to a BS at the request of the BS. For example, when the BS requests CSI from the UE, the UE may provide the CSI report without the BS allocating and scheduling uplink resources for CSI report transmission. This may allow the BS to schedule the UE to transmit other types of uplink data (e.g., ultra-reliable low latency communication (URLLC) data) after requesting CSI but before scheduling CSI reports. Instead of triggering the generation of CSI reports and scheduling UL resources for transmitting CSI reports in an Uplink (UL) grant at the same time, the BS may divide the process into discrete steps. The steps may include triggering generation of a CSI report by sending a CSI computation request to the UE and requesting transmission of a CSI report by sending a CSI report transmission request to the UE. The CSI computation request may result in the UE determining the CSI, but may not schedule any UL resources for transmitting CSI reports. The UE may store the CSI to wait for reception of a CSI report transmission request. Once the UE receives the CSI report transmission request, the UE may transmit the stored CSI report using UL resources (e.g., resources in a physical uplink shared channel) designated by the BS.

For example, in an aspect of the disclosure, a method of wireless communication performed by a User Equipment (UE) includes receiving a Channel State Information (CSI) calculation request from a Base Station (BS). The method further includes identifying a first CSI measurement resource based on the CSI computation request. The method further includes determining CSI based on the first CSI measurement resource and receiving a CSI report transmission request associated with the first CSI measurement resource from the BS after the CSI calculation request.

In another example, aspects may include a method of wireless communication for providing channel state information. The method may include determining channel state information based on one or more CSI measurement resources (e.g., first, second, third, etc.). The method may also include receiving or transmitting a CSI report. In some scenarios, the reception or transmission of a CSI report may be preceded by a CSI report request. The method may also optionally include receiving a CSI computation request and/or identifying a first CSI measurement resource. The first CSI measurement resource may be based on a CSI computation request.

In an additional aspect of the disclosure, a method of wireless communication performed by a BS includes transmitting a CSI computation request to a UE. The method further includes transmitting, to the UE, a CSI report transmission request associated with the first CSI measurement resource. The method further includes receiving, from the UE, a CSI report associated with the first CSI measurement resource in response to the CSI report transmission request.

In an additional aspect of the disclosure, a UE includes a processor and a transceiver. The transceiver is configured to receive a CSI computation request from a BS. The processor is configured to identify a first CSI measurement resource based on the CSI computation request and determine CSI based on the first CSI measurement resource. The transceiver is further configured to receive a CSI report transmission request associated with the first CSI measurement resource from the BS after the CSI computation request.

In an additional aspect of the disclosure, a BS includes a processor and a transceiver. The transceiver is configured to transmit a CSI computation request to the UE. The transceiver is further configured to transmit a CSI report transmission request associated with the first CSI measurement resource to the UE and receive a CSI report associated with the first CSI measurement resource from the UE in response to the CSI report transmission request.

In an additional aspect of the disclosure, a non-transitory computer-readable medium having program code recorded thereon is disclosed. The program code includes code for causing the UE to receive a CSI computation request from the BS. The program code further includes code for causing the UE to identify a first CSI measurement resource based on the CSI computation request. The program code further includes code for causing the UE to determine CSI based on the first CSI measurement resource. The program code further includes code for causing the UE to receive a CSI report transmission request associated with the first CSI measurement resource from the BS after the CSI calculation request.

In an additional aspect of the disclosure, a non-transitory computer-readable medium having program code recorded thereon is disclosed. The program code includes code for causing the BS to transmit a CSI computation request to the UE. The program code further includes code for causing the BS to transmit a CSI report transmission request associated with the first CSI measurement resource to the UE. The program code further includes code for causing the BS to receive, from the UE, a CSI report associated with the first CSI measurement resource in response to the CSI report transmission request.

In an additional aspect of the disclosure, a UE includes means for receiving a CSI computation request from a BS. The UE further includes means for identifying a first CSI measurement resource based on the CSI computation request. The UE further includes means for determining CSI based on the first CSI measurement resource. The UE further includes means for receiving a CSI report transmission request associated with the first CSI measurement resource from the BS after the CSI computation request.

In an additional aspect of the disclosure, a BS includes means for transmitting a CSI computation request to a UE. The BS further includes means for transmitting a CSI report transmission request associated with the first CSI measurement resource to the UE. The BS further includes means for receiving a CSI report associated with the first CSI measurement resource from the UE in response to the CSI report transmission request.

Other aspects, features and embodiments will become apparent to those ordinarily skilled in the art upon review of the following description of specific exemplary embodiments in conjunction with the accompanying figures. While various features may be discussed below with respect to certain embodiments and figures, all embodiments can include one or more of the advantageous features discussed herein. In other words, while one or more embodiments may be discussed as having certain advantageous features, one or more such features may also be used in accordance with the various embodiments discussed herein. In a similar manner, although example embodiments may be discussed below as device, system, or method embodiments, it should be appreciated that such example embodiments may be implemented in a variety of devices, systems, and methods.

Brief Description of Drawings

Fig. 1 illustrates a wireless communication network in accordance with some aspects of the present disclosure.

Fig. 2A illustrates a Channel State Information (CSI) request and resource allocation method in accordance with some aspects of the disclosure.

Fig. 2B illustrates a resource allocation method in accordance with some aspects of the present disclosure.

Fig. 3 illustrates a CSI request and resource allocation method in accordance with some aspects of the disclosure.

Fig. 4 is an exemplary sequence diagram illustrating a communication sequence in accordance with some aspects of the present disclosure.

Fig. 5 is a flow diagram of wireless communication in accordance with some aspects of the present disclosure.

Fig. 6 is a block diagram of an example Base Station (BS) in accordance with some aspects of the present disclosure.

Fig. 7 is a block diagram of an example User Equipment (UE) in accordance with some aspects of the present disclosure.

Fig. 8 is a flow diagram of wireless communication in accordance with some aspects of the present disclosure.

Fig. 9 is a flow diagram of wireless communication in accordance with some aspects of the present disclosure.

Detailed Description

The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. It will be apparent, however, to one skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

A Base Station (BS) may request Channel State Information (CSI) from a UE to determine a current state of a channel for communication between the BS and the UE based on a CSI measurement resource. The CSI measurement resources may be, for example, non-zero power channel state information reference signal (NZP CSI-RS) and/or channel state information interference measurement (CSI-IM) resources. The BS may send a single Physical Downlink Control Channel (PDCCH) Downlink Control Information (DCI) to request the UE to measure and/or collect CSI from the associated CSI measurement resources and to schedule uplink resources for the UE to transmit the resulting CSI report. Uplink scheduling is typically reserved (transmitted before the actual scheduling time). Because CSI computation at the UE can take a significant amount of time, the BS can account for the CSI computation time and transmit DCI (including CSI measurement and reporting triggers) at even earlier times than the CSI reporting scheduling resources (e.g., up to about 11 slots ahead, depending on subcarrier spacing). As such, there may be a significant duration between the time the CSI request is transmitted to the UE and the CSI reporting scheduling resource. Since the uplink scheduling is expected to be ordered, the BS may not schedule the UE for another uplink transmission between the time the UE receives the CSI request and the time the UE transmits the CSI report. This in effect gives CSI data a higher priority than other types of data, making ultra-reliable low latency communication (URLLC) difficult for the UE.

The present disclosure relates generally to wireless communication systems (also referred to as wireless communication networks). In various embodiments, the techniques and apparatus may be used for wireless communication networks such as Code Division Multiple Access (CDMA) networks, time Division Multiple Access (TDMA) networks, frequency Division Multiple Access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single carrier FDMA (SC-FDMA) networks, LTE networks, global system for mobile communications (GSM) networks, fifth generation (5G) or New Radio (NR) networks, and other communication networks. As described herein, the terms "network" and "system" may be used interchangeably.

An OFDMA network may implement radio technologies such as evolved UTRA (E-UTRA), institute of Electrical and Electronics Engineers (IEEE) 802.11, IEEE 802.16, IEEE 802.20, flash-OFDM, etc. UTRA, E-UTRA and GSM are part of the Universal Mobile Telecommunications System (UMTS). In particular, long Term Evolution (LTE) is a release of UMTS that uses E-UTRA. UTRA, E-UTRA, GSM, UMTS and LTE are described in documents from an organization named "third generation partnership project" (3 GPP), while cdma2000 is described in documents from an organization named "third generation partnership project 2" (3 GPP 2). These various radio technologies and standards are known or under development. For example, the third generation partnership project (3 GPP) is a collaboration between groups of telecommunications associations that is intended to define the globally applicable third generation (3G) mobile phone specification. The 3GPP Long Term Evolution (LTE) is a 3GPP project aimed at improving the UMTS mobile phone standard. The 3GPP may define specifications for next generation mobile networks, mobile systems, and mobile devices. The present disclosure concerns the evolution of wireless technologies from LTE, 4G, 5G, NR and beyond with shared access to the wireless spectrum between networks using new and different radio access technologies or sets of radio air interfaces.

In particular, 5G networks contemplate diverse deployments, diverse spectrum, and diverse services and devices that may be implemented using a unified OFDM-based air interface. To achieve these goals, in addition to developing new radio technologies for 5G NR networks, further enhancements to LTE and LTE-a are considered. The 5G NR will be able to scale to provide coverage for: (1) With ultra-high density (e.g., about 1M nodes/km) ² ) Ultra-low complexity (e.g., on the order of tens of bits/second), ultra-low energy (e.g., battery life of about 10+ years), and deep-coverage large-scale internet of things (IoT) capable of reaching challenging locations; (2) Mission-critical controls including users with strong security (to protect sensitive personal, financial, or confidential information), ultra-high reliability (e.g., about 99.9999% reliability), ultra-low latency (e.g., about 1 ms), and with a wide range of mobility or lack of mobility; and (3) having enhanced mobile broadband, which includes very high capacity (e.g., about 10 Tbps/km) ² ) Extreme data rates (e.g., multiple Gbps rate, 100+ Mbps user experience rate), and deep learning with advanced discovery and optimization.

The 5G NR communication system may be implemented to use optimized OFDM-based waveforms with scalable parameter sets and Transmission Time Intervals (TTIs). Additional features may also include Time Division Duplex (TDD)/Frequency Division Duplex (FDD) designs with a common, flexible framework to efficiently multiplex services and features using dynamic low latency; and utilize advanced wireless technologies such as massive Multiple Input Multiple Output (MIMO), robust millimeter wave (mmWave) transmission, advanced channel coding, and device-centric mobility. Scalability of parameter design (and scaling of subcarrier spacing (SCS)) in 5G NRs can efficiently address operating diverse services across diverse spectrum and diverse deployments. For example, in various outdoor and macro coverage deployments with less than 3GHz FDD/TDD implementations, the subcarrier spacing may occur at 15kHz, e.g., over a Bandwidth (BW) of 5, 10, 20MHz, etc. For other various outdoor and small cell coverage deployments of TDD greater than 3GHz, subcarrier spacing may occur at 30kHz on an 80/100MHz BW. For other various indoor wideband implementations, the subcarrier spacing may occur at 60kHz on a 160MHz BW by using TDD on the unlicensed portion of the 5GHz band. Finally, for various deployments transmitting with 28GHz TDD using mmWave components, subcarrier spacing may occur at 120kHz on a 500MHz BW.

The scalable parameter design of 5G NR facilitates a scalable TTI to meet diverse latency and quality of service (QoS) requirements. For example, shorter TTIs may be used for low latency and high reliability, while longer TTIs may be used for higher spectral efficiency. Efficient multiplexing of long and short TTIs allows transmission to start on symbol boundaries. The 5G NR also contemplates a self-contained integrated subframe design with UL/downlink scheduling information, data, and acknowledgements in the same subframe. Self-contained integrated subframes support communication in an unlicensed or contention-based shared spectrum, supporting adaptive UL/downlink that can be flexibly configured on a per-cell basis to dynamically switch between UL and downlink to meet current traffic needs.

Various other aspects and features of the disclosure are described further below. It should be apparent that the teachings herein may be embodied in a wide variety of forms and that any specific structure, function, or both being disclosed herein is merely representative and not limiting. Based on the teachings herein one of ordinary skill in the art should appreciate that an aspect disclosed herein may be implemented independently of any other aspects and that two or more of these aspects may be combined in various ways. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, such an apparatus may be implemented or such a method may be practiced using other structure, functionality, or structure and functionality in addition to or other than one or more of the aspects set forth herein. For example, the methods may be implemented as part of a system, apparatus, device, and/or as instructions stored on a computer-readable medium for execution on a processor or computer. Furthermore, an aspect may comprise at least one element of a claim.

A Base Station (BS) in a 5G NR may request channel state information from a User Equipment (UE). The BS may use the CSI to determine the operating conditions or states of the channels to assist in communication between the BS and the UE and/or to obtain interference measurements. The BS may request the UE to perform channel estimation and/or interference measurement by including an aperiodic channel state information (a-CSI) trigger as part of an Uplink (UL) grant to the UE. The UL grant with the trigger may be sent in a Physical Downlink Control Channel (PDCCH) transmission, and the grant may include a UL scheduling offset indicating a number of slots between a time the grant is transmitted and a time the UE is scheduled to transmit CSI reports in a Physical Uplink Shared Channel (PUSCH). The UL grant may precede the presence of a channel state information reference signal (CSI-RS) and/or the presence of a channel state information interference measurement (CSI-IM) resource. When the UL grant includes an a-CSI trigger (e.g., indicated by a CSI trigger field having a non-zero value), the scheduling offset is greater than a scheduling offset of an UL grant not associated with the a-CSI trigger to account for the time it takes for the UE to prepare the requested CSI report.

Currently, out-of-order PUSCH transmissions are prohibited, so the BS may not schedule the UE to transmit any PUSCH data during the scheduling offset (i.e., before the UE is scheduled to transmit the requested CSI report). In addition to the resulting inefficiencies, CSI data is actually given a higher priority than other types of uplink data, which can be problematic for ultra-reliable latency communications (URLLC). Accordingly, aspects and embodiments described herein provide techniques that allow and enable a BS to request CSI without requiring the BS to allocate and schedule uplink resources for CSI reporting when it requests CSI. This may allow the BS to schedule the UE to transmit other types of uplink data (e.g., URLLC data) after requesting CSI reports but before scheduling CSI, thereby satisfying an ordered PUSCH transmission scheduling report.

The present disclosure provides techniques for a UE to determine and provide CSI to a BS. In some scenarios, the UE may provide CSI to the BS at the request of the BS. The provisioning of the CSI by the UE may be done in case the BS does not reserve uplink resources for CSI reporting when it requests the CSI. This may allow the UE to transmit other types of uplink data (e.g., URLLC data) after receiving a request for CSI but before transmitting a CSI report. Instead of triggering the generation of CSI reports and scheduling UL resources for transmitting CSI reports in UL grants simultaneously, the BS may divide the process into discrete steps. The steps may include triggering generation of a CSI report by sending a CSI computation request to the UE and requesting transmission of a CSI report by sending a CSI report transmission request to the UE. The BS may transmit the CSI computation request as a Downlink Control Information (DCI) message (referred to herein as a computation-only DCI) in the PDCCH. Additionally or alternatively, the BS may transmit the CSI report transmission request as part of a DCI message (referred to herein as reporting-only DCI) in the PDCCH at a later time. Computing only DCI may trigger the UE to generate a CSI report. But in some instances, doing so does not schedule any UL resources for transmission of CSI reports. The UE may generate a CSI report and store it to wait for reception of the report-only DCI. Once the UE receives report-only DCI indicating which CSI report to transmit, the UE may transmit the stored CSI report using UL resources (e.g., resources in a Physical Uplink Shared Channel (PUSCH)) specified in the report-only DCI. In an example, the reporting-only DCI includes a CSI request field including a value mapped to a CSI trigger state. The CSI trigger state may be associated with one or more CSI reporting configurations. Each CSI reporting configuration may refer to CSI measurement resources that the BS is requesting for reporting.

For example, according to aspects of the present disclosure, the BS may request the UE to calculate CSI by transmitting a first CSI calculation request (e.g., as a DCI message in a PDCCH) to the UE. The first CSI calculation request may indicate one or more CSI measurement resources on which the UE may measure CSI, but may not indicate any resources for transmitting CSI reports by the UE. Based on the first CSI computation request, the UE may then identify a CSI measurement resource, which may be, for example, a channel state information reference signal (CSI-RS) resource and/or a channel state information interference measurement (CSI-IM) resource. Based on the CSI measurement resource(s), the UE may perform channel estimation and/or interference measurement, but the UE may store the resulting CSI in a memory within the UE, rather than immediately transmitting the results to the BS. During the CSI computation time, the BS may schedule the UE for other types of uplink data (e.g., URLLC data) by transmitting a scheduling grant to the UE and the UE may transmit the uplink data based on the scheduling grant. At a later time, the BS may transmit a first CSI report transmission request (e.g., as a DCI message on the PDCCH) to the UE to request the UE to transmit a report including the CSI it calculated in response to the first CSI calculation request. The CSI report transmission request may indicate which uplink resources (e.g., PUSCH resources) the UE should use for transmitting the report.

In some aspects, the UE may keep multiple CSI corresponding to different CSI computation requests and CSI measurement resources stored in its memory. For example, at some time after transmitting the first CSI calculation request, the BS may transmit a second CSI calculation request and indicate a second CSI measurement resource corresponding to the second CSI calculation request. The UE may perform channel and/or interference measurements based on the second CSI measurement resource and store the resulting CSI in memory without removing CSI corresponding to the first CSI computation request. The UE may store and maintain multiple CSIs in its memory, which may be useful, for example, if the gap between the CSI computation request and the CSI report transmission request is too short for the UE to determine the CSI. In these cases, it may be appropriate for the UE to transmit the stored older CSI. In some aspects, there may be a limit to the number of CSIs that the UE may store, and the UE may delete the stored CSI or not store the newly calculated CSI if the number of CSIs in memory exceeds the limit.

In some aspects, the UE may employ a timer to determine which, if any, stored CSI to transmit to the BS in response to the CSI transmission request. The timer mechanism may help the UE respond to CSI report transmission requests that arrive too early (e.g., before the UE has been able to determine CSI) or too late (e.g., when the CSI data has become stale or outdated).

Aspects may include further timing-related features. For example, the UE may start (or reset) the timer after a certain period (or duration) has elapsed from an end time of the CSI measurement resource (e.g., the end of the last symbol of the CSI measurement resource). The period may be (approximately) the minimum gap between the end time of the CSI measurement resource and the time at which the UE may determine the CSI. The timer duration may be preconfigured (e.g., to a value defined in a third generation partnership project (3 GPP) specification). Additionally or alternatively, the timer value may be semi-statically configured by the BS (e.g., through RRC signaling) or dynamically indicated by the BS (e.g., as part of the CSI computation request or via the MAC CE). The timer duration may be based on information (e.g., CSI report content) that the UE is to include in the CSI report (e.g., the timer duration may be greater when the UE is to include more information or more complex information in the CSI report).

The timer duration may also be based on a codebook type, a number of antenna ports, a Channel Quality Indicator (CQI) type, and/or a Precoding Matrix Indicator (PMI) type associated with the CSI report. In general, CSI reporting content may vary depending on: a codebook type to be used for CSI calculation, a number of antenna ports associated with CSI measurement resources, and/or a type of CQI and/or PMI to be reported. In other words, the CSI computation time may vary depending on the CSI report content.

The time period for which the timer runs may correspond to a time period during which a current CSI report should be transmitted to the BS in response to receiving a CSI report transmission request. For example, if a CSI report transmission request arrives while a timer is running, the UE may transmit the most recently calculated CSI in a CSI report. However, if the UE receives a CSI report transmission request before the timer starts, the UE may not be able to complete the requested channel estimation and/or interference measurement. If the CSI report transmission request is received after the timer has expired, this may indicate that the most recently calculated CSI data is now stale. In either case-when a CSI transmission request is received before the timer starts or after the timer expires-the UE may transmit CSI that may not be current (e.g., the most recently stored-now-stale-CSI, or the previously stored CSI based on the older CSI computation request and the corresponding CSI measurement resource) or placeholder data (which does not have useful CSI) in the CSI report. The transmission of the stale CSI or the useless CSI is to satisfy the CSI report transmission request because the UE will transmit as scheduled by the BS.

Transmitting older CSI or occupancy data may be appropriate when, for example, the transmission on which the CSI report transmission request arrives also includes a grant for transmitting uplink shared channel (UL-SCH) data or a hybrid automatic repeat request (HARQ) acknowledgement. In this case, the BS may determine that the CSI report is not based on the most recent CSI calculation request. Since the BS is aware of the timeline of the CSI calculation request and the CSI report transmission request, the BS can determine whether the CSI report is valid. In general, the BS does not configure the UE such that the CSI report transmission request is outside the period in which the reporting timer of the UE is running. Alternatively, the UE may ignore the CSI report transmission request entirely (i.e., refrain from transmitting the CSI report), for example, if the CSI transmission request includes only a grant for transmitting the CSI report. In some aspects, the UE may remove the stored CSI from memory based on expiration of a timer.

In some aspects, the resource occupancy reporting rules may be updated to reflect aspects of the present disclosure. The 5G NR provides rules for the UE to determine the resources (e.g., the maximum number of Central Processing Units (CPUs) and/or the maximum number of synchronous memory resources) for implementing the two-step CSI trigger (with separate CSI computation request and CSI report transmission request) and report its capabilities associated with the two-step CSI trigger. According to the present disclosure, the CPU resource is occupied for a duration of Z symbols from the end of the last symbol of the PDCCH (or control resource set (CORESET)) on which the CSI computation request (e.g., only DCI is computed), where Z is the minimum gap between the time the CSI computation request is transmitted and the time the UE can provide the CSI report. In other words, Z symbols are the amount of time to complete the CSI computation. The value of Z may vary depending on the capabilities of the UE. The UE may determine and report the value of Z to the BS based on the CPU resource occupancy rule. For example, a UE with high processing capability may report a smaller Z value than a UE with low processing capability. The memory resources may be occupied by Z + T from the end of the last symbol of the PDCCH (or control resource set (CORESET)) on which the CSI computation request (e.g., only DCI) is carried _exp Duration of one symbol, where Z is defined as above with respect to CPU occupancy and T _exp Is the duration of the window in which the UE waits for a CSI report transmission request (i.e., the timer duration discussed above in which the UE may provide the most recently calculated CSI to the BS). Memory resources occupied for CSI operations expire in the windowBecomes idle when or after the UE transmits a CSI report to the BS (in response to receiving a CSI request report transmission during the window).

Aspects of the present disclosure may provide a number of benefits. For example, aspects of the present disclosure enable a BS to schedule a UE to transmit uplink data in a time period between receiving a request for CSI and transmitting the result of the request. This may be done, for example, by decoupling the a-CSI triggering mechanism from the UL resource allocation used to report CSI. This may enable the UE to better communicate URLLC data (e.g., with lower latency) because by having the UE lock on to determining and transmitting CSI without interruption, CSI data is no longer actually prioritized.

Although aspects and embodiments are described herein by way of illustration of some examples, those skilled in the art will appreciate that additional implementations and use cases may be generated in many different arrangements and scenarios. The innovations described herein may be implemented across many different platform types, devices, systems, shapes, sizes, packaging arrangements. For example, embodiments and/or uses can be generated via integrated chip embodiments and other non-module component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/shopping devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specific to each use case or application, broad applicability of the described innovations may occur. Implementations may range from chip-level or modular components to non-module, non-chip-level implementations, and further to aggregated, distributed, or OEM devices or systems incorporating one or more aspects of the described innovations. In some practical environments, a device incorporating the described aspects and features may also include additional components and features as necessary to implement and practice the various embodiments as claimed and described. For example, the transmission and reception of wireless signals must include several components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, summers/summers, etc.). The innovations described herein are intended to be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, end-user devices, and the like, of various sizes, shapes, and configurations.

Fig. 1 illustrates a wireless communication network 100 in accordance with some aspects of the present disclosure. The network 100 may be a 5G network. The network 100 includes a number of Base Stations (BSs) 105 (labeled 105a, 105b, 105c, 105d, 105e, and 105f, respectively) and other network entities. The BS105 may be a station that communicates with the UEs 115 and may also be referred to as an evolved node B (eNB), a next generation eNB (gNB), an access point, and so on. Each BS105 may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" can refer to the particular geographic coverage area of the BS105 and/or the BS subsystem serving that coverage area, depending on the context in which the term is used.

The BS105 may provide communication coverage for macro cells or small cells (such as pico cells or femto cells), and/or other types of cells. A macro cell generally covers a relatively large geographic area (e.g., thousands of meters in radius) and may allow unrestricted access by UEs with service subscriptions with the network provider. Small cells (such as picocells) typically cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions with a network provider. Small cells, such as femtocells, typically also cover relatively small geographic areas (e.g., a home), and may have restricted access in addition to unrestricted access to UEs associated with the femtocell (e.g., UEs in a Closed Subscriber Group (CSG), UEs of users in the home, etc.). The BS for the macro cell may be referred to as a macro BS. The BS for the small cell may be referred to as a small cell BS, a pico BS, a femto BS, or a home BS. In the example shown in fig. 1, BSs 105D and 105e may be conventional macro BSs, while BSs 105a-105c may be one of three-dimensional (3D), full-dimensional (FD), or massive MIMO enabled macro BSs. The BSs 105a-105c may take advantage of their higher dimensional MIMO capabilities to increase coverage and capacity with 3D beamforming in both elevation and azimuth beamforming. The BS105 f may be a small cell BS, which may be a home node or a portable access point. The BS105 may support one or more (e.g., two, three, four, etc.) cells.

The network 100 may support synchronous or asynchronous operation. For synchronous operation, the BSs may have similar frame timing, and transmissions from different BSs may be approximately aligned in time. For asynchronous operation, BSs may have different frame timings, and transmissions from different BSs may not be aligned in time.

UEs 115 may be dispersed throughout wireless network 100, and each UE115 may be stationary or mobile. Each UE may take various forms and form factor ranges. UE115 may also be referred to as a terminal, mobile station, subscriber unit, station, etc. The UE115 may be a cellular telephone, a Personal Digital Assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a cordless telephone, a Wireless Local Loop (WLL) station, and so forth. In one aspect, the UE115 may be a device that includes a Universal Integrated Circuit Card (UICC). In another aspect, the UE may be a device that does not include a UICC. In some aspects, a UE115 that does not include a UICC may also be referred to as an IoT device or an internet of everything (IoE) device. The UEs 115a-115d are examples of mobile smartphone type devices that access the network 100. The UE115 may also be a machine specifically configured for connected communications including Machine Type Communications (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT), etc. UEs 115e-115h are examples of various machines of access network 100 that are configured for communication. The UEs 115i-115k are examples of vehicles equipped with wireless communication devices of the access network 100 that are configured for communication. The UE115 may be capable of communicating with any type of BS (whether a macro BS, a small cell, etc.). In fig. 1, a lightning bundle (e.g., a communication link) indicates a wireless transmission between a UE115 and a serving BS105, a desired transmission between BSs 105, a backhaul transmission between BSs, or a sidelink transmission between UEs 115, the serving BS105 being a BS designated to serve the UE115 on a Downlink (DL) and/or an Uplink (UL).

In operation, the BSs 105a-105c may serve the

UEs

115a and 115b using 3D beamforming and coordinated spatial techniques, such as coordinated multipoint (CoMP) or multi-connectivity. The macro BS105 d may perform backhaul communications with the BSs 105a-105c, as well as the small cell BS105 f. The macro BS105 d may also transmit multicast services subscribed to and received by the

UEs

115c and 115 d. Such multicast services may include mobile television or streaming video, or may include other services for providing community information (such as weather emergencies or alerts, such as amber alerts or gray alerts).

The BS105 may also communicate with a core network. The core network may provide user authentication, access authorization, tracking, internet Protocol (IP) connectivity, and other access, routing, or mobility functions. At least some BSs 105 (e.g., which may be examples of a gNB or Access Node Controller (ANC)) may interface with a core network over a backhaul link (e.g., NG-C, NG-U, etc.) and may perform radio configuration and scheduling for communication with UEs 115. In various examples, the BSs 105 can communicate with each other directly or indirectly (e.g., through a core network) over backhaul links (e.g., X1, X2, etc.), which can be wired or wireless communication links.

The network 100 may also support mission-critical communications with ultra-reliable and redundant links for mission-critical devices, such as UE115 e, which may be drones. The redundant communication links with the UE115 e may include links from the

macro BSs

105d and 105e, and links from the small cell BS105 f. Other machine type devices, such as UE115 f (e.g., a thermometer), UE115 g (e.g., a smart meter), and UE115 h (e.g., a wearable device), may communicate with BSs, such as small cell BS105 f and macro BS105 e, directly through network 100, or in a multi-step configuration by communicating with another user device that relays its information to the network (such as UE115 f communicating temperature measurement information to smart meter UE115 g, which is then reported to the network through small cell BS105 f). The network 100 may also provide additional network efficiency through dynamic, low latency TDD/FDD communications, such as V2V, V2X, C-V2X communications between a

UE

115I, 115j or 115k and other UEs 115, and/or vehicle-to-infrastructure (V2I) communications between a

UE

115I, 115j or 115k and a BS 105.

In some implementations, the network 100 utilizes OFDM-based waveforms for communication. An OFDM-based system may divide the system BW into multiple (K) orthogonal subcarriers, which are also commonly referred to as subcarriers, tones, bins, and so on. Each subcarrier may be modulated with data. In some instances, the subcarrier spacing between adjacent subcarriers may be fixed, and the total number of subcarriers (K) may be dependent on the system BW. The system BW may also be divided into sub-bands. In other examples, the subcarrier spacing and/or the duration of the TTI may be scalable.

In some aspects, the BS105 may assign or schedule transmission resources (e.g., in the form of time-frequency Resource Blocks (RBs)) for Downlink (DL) and Uplink (UL) transmissions in the network 100. DL refers to a transmission direction from the BS105 to the UE115, and UL refers to a transmission direction from the UE115 to the BS 105. The communication may take the form of radio frames. A radio frame may be divided into a number of subframes or slots, e.g. about 10. Each slot may be further divided into subslots. In FDD mode, simultaneous UL and DL transmissions may occur in different frequency bands. For example, each subframe includes an UL subframe in an UL frequency band and a DL subframe in a DL frequency band. In TDD mode, UL and DL transmissions occur in different time periods using the same frequency band. For example, a subset of subframes in a radio frame (e.g., DL subframes) may be used for DL transmissions and another subset of subframes in a radio frame (e.g., UL subframes) may be used for UL transmissions.

The DL subframe and the UL subframe may be further divided into several regions. For example, each DL or UL subframe may have a predefined area for transmission of reference signals, control information, and data. The reference signal is a predetermined signal that facilitates communication between the BS105 and the UE 115. For example, a reference signal may have a particular pilot pattern or structure in which pilot tones may span an operating BW or band, each pilot tone being located at a predefined time and a predefined frequency. For example, the BS105 may transmit cell-specific reference signals (CRS) and/or channel state information-reference signals (CSI-RS) to enable the UEs 115 to estimate the DL channel. Similarly, the UE115 may transmit a Sounding Reference Signal (SRS) to enable the BS105 to estimate the UL channel. The control information may include resource assignments and protocol controls. The data may include protocol data and/or operational data. In some aspects, the BS105 and the UE115 may communicate using self-contained subframes. The self-contained subframe may include a portion for DL communication and a portion for UL communication. The self-contained subframes may be DL-centric or UL-centric. The DL centric sub-frame may comprise a longer duration for DL communication than for UL communication. The UL centric sub-frame may comprise a longer duration for UL communications than for DL communications.

In some aspects, the network 100 may be an NR network deployed over a licensed spectrum. The BS105 may transmit synchronization signals (e.g., including a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS)) in the network 100 to facilitate synchronization. BS105 may broadcast system information associated with network 100 (e.g., including a Master Information Block (MIB), remaining system information (RMSI), and Other System Information (OSI)) to facilitate initial network access. In some examples, BS105 may broadcast PSS, SSS, and/or MIB in the form of Synchronization Signal Blocks (SSBs) on a Physical Broadcast Channel (PBCH), and may broadcast RMSI and/or OSI on a Physical Downlink Shared Channel (PDSCH).

In some aspects, a UE115 attempting to access the network 100 may perform an initial cell search by detecting a PSS from the BS 105. The PSS may enable synchronization of period timing and may indicate a physical layer identity value. The UE115 may then receive the SSS. The SSS may implement radio frame synchronization and may provide a cell identity value, which may be combined with a physical layer identity value to identify the cell. The PSS and SSS may be located in the center portion of the carrier or at any suitable frequency within the carrier.

After receiving the PSS and SSS, UE115 may receive the MIB. The MIB may include system information for initial network access and scheduling information for RMSI and/or OSI. After decoding the MIB, UE115 may receive RMSI and/or OSI. The RMSI and/or OSI may include Radio Resource Control (RRC) information related to Random Access Channel (RACH) procedures, paging, control resource sets (CORESET) for Physical Downlink Control Channel (PDCCH) monitoring, physical UL Control Channel (PUCCH), physical UL Shared Channel (PUSCH), power control, and SRS.

After obtaining the MIB, RMSI, and/or OSI, UE115 may perform a random access procedure to establish a connection with BS 105. The random access procedure (or RACH procedure) may be a single-step or a multi-step procedure. In some examples, the random access procedure may be a four-step random access procedure. For example, the UE115 may transmit a random access preamble and the BS105 may respond with a random access response. The Random Access Response (RAR) may include a detected random access preamble Identifier (ID), timing Advance (TA) information, UL grant, temporary cell radio network temporary identifier (C-RNTI), and/or backoff indicator corresponding to the random access preamble. Upon receiving the random access response, the UE115 may transmit a connection request to the BS105 and the BS105 may respond with the connection response. The connection response may indicate a contention resolution scheme. In some examples, the random access preamble, RAR, connection request, and connection response may be referred to as message 1 (MSG 1), message 2 (MSG 2), message 3 (MSG 3), and message 4 (MSG 4), respectively. In some examples, the random access procedure may be a two-step random access procedure in which the UE115 may transmit a random access preamble and a connection request in a single transmission, and the BS105 may respond by transmitting a random access response and a connection response in a single transmission.

After establishing the connection, the UE115 and the BS105 can enter a normal operation phase, in which operational data can be exchanged. For example, the BS105 may schedule the UE115 for UL and/or DL communications. The BS105 may transmit UL and/or DL scheduling grants to the UE115 via the PDCCH. The scheduling grant may be transmitted in the form of DL Control Information (DCI). The BS105 may transmit DL communication signals (e.g., carrying data) to the UEs 115 via the PDSCH according to the DL scheduling grant. The UE115 may transmit UL communication signals to the BS105 via PUSCH and/or PUCCH according to the UL scheduling grant.

In some aspects, the network 100 may operate on a system BW or a Component Carrier (CC) BW. The network 100 may divide the system BW into multiple BWPs (e.g., multiple portions). The BS105 may dynamically assign the UE115 to operate on a certain BWP (e.g., a certain portion of the system BW). The assigned BWP may be referred to as an active BWP. The UE115 may monitor the active BWP for signaling information from the BS 105. The BS105 may schedule the UE115 for UL or DL communication in active BWP. In some aspects, the BS105 may assign BWP pairs within a CC to the UEs 115 for UL and DL communications. For example, the BWP pair may include one BWP for UL communications and one BWP for DL communications.

In some aspects, the BS105 may request the UE115 to calculate CSI by transmitting a CSI calculation request to the UE115 (e.g., as a DCI message in a PDCCH). The CSI computation request may indicate the presence of at least one CSI measurement resource on which the UE115 should perform CSI measurements, but may not indicate any resources for transmitting CSI reports by the UE 115. The UE115 may then identify a CSI measurement resource based on the CSI computation request. Based on the CSI measurement resources, the UE may perform channel measurements and/or interference measurements, but the UE115 may store the resulting CSI in a memory within the UE115 rather than immediately transmitting the results to the BS 105. Thereafter, the UE115 may continue to transmit other types of uplink data (e.g., URLLC data). For example, the BS105 may transmit a scheduling grant to the UE115 and the UE115 may transmit uplink data based on the scheduling grant. At a later time, the BS105 may transmit a CSI report transmission request (e.g., as a DCI message on the PDCCH) to the UE115 to indicate that the UE115 should now transmit a report that includes the CSI it calculated based on the CSI calculation request. The CSI report transmission request may indicate which uplink resources (e.g., PUSCH resources) the UE115 should use when transmitting the report. Additionally, the CSI report transmission request may include a CSI request field including a value mapped to the CSI trigger state. The CSI trigger state may be associated with one or more CSI reporting configurations. Each CSI reporting configuration may refer to CSI measurement resources that the BS is requesting for reporting. For example, the CSI report transmission request may refer to the same CSI measurement resource as the CSI computation request. Accordingly, the UE115 may transmit the CSI report based on the CSI measurement resource indicated by the CSI report transmission request. Depending on the time at which the CSI report transmission request is received, the UE115 may transmit the CSI report based on the CSI measurement resource indicated by the CSI report transmission request or based on an earlier CSI measurement resource, depending on when the UE115 receives the CSI report transmission request, as discussed with reference to fig. 4-5, 7, and 8. In some examples, the UE115 may ignore the CSI report transmission request and refrain from transmitting the CSI report entirely (e.g., in the event that the CSI report transmission request does not arrive while the timer is running, as described above).

Fig. 2A illustrates a CSI request and resource allocation method 200A in accordance with some aspects of the present disclosure. When requesting CSI from the UE115 using an aperiodic CSI request, the BS105 may include an a-CSI trigger 202 (e.g., as part of the DCI) in the PDCCH transmission during slot S0 212. In an example, the DCI may include a CSI request field including a value mapped to a CSI trigger state. The CSI trigger state may be associated with one or more CSI reporting configurations. Each CSI reporting configuration may refer to CSI measurement resources that the BS105 is requesting for CSI reporting. An uplink grant may be included along with the a-CSI trigger 202 to indicate which UL resources 206 the UE115 is to use in the PUSCH when transmitting CSI reports to the BS 105. The BS may indicate that the reported CSI may be based on CSI measurement resources 204 (e.g., NZP CSI-RS resources and/or CSI-IM resources) referenced by the a-CSI trigger 202. The CSI measurement resource is a set of resource elements (spanning several subcarriers in frequency and several symbols in time) in which the UE115 may perform measurements. When the CSI measurement resource 204 is a CSI-RS or NZP CSI-RS resource, the BS105 may transmit the CSI-RS in the CSI measurement resource 204 for the UE115 to determine a channel response. When the CSI measurement resource 204 is a CSI-IM resource, the UE115 may measure interference from the CSI measurement resource 204. The BS may indicate (e.g., as part of the uplink grant) a scheduling offset 208 (which may be referred to as Y), which scheduling offset 208 indicates a gap between the time the a-CSI trigger is transmitted and the time the CSI report should be transmitted on the PUSCH. BS105 may have to reserve UL resources 206 a few time slots in advance (e.g., before transmitting a-CSI trigger 202 in time slot S0 212) and expect BS105 to perform ordered uplink scheduling. As a result, from the end time of CSI measurement resource 204 to the time that UE115 transmits a CSI report on UL resource 206, BS105 must not schedule UE115 to transmit any additional UL data during this gap time. The gap between CSI measurement resources 204 and the transmission of CSI reports (e.g., PUSCH transmissions) on UL resources 206 may be referred to as Y'. For example, the BS105 may not schedule the UE115 to transmit any additional UL data in the remaining portion of time slot S0 212 or time slot S1 214, time slot S2 216, time slot S3 218, or time slot S4 220. Thus, the UE115 may not transmit other types of UL data until after transmitting the CSI report during slot S5 222. As a result, CSI data is actually given a higher priority than other types of data, which may be problematic for UEs 115 participating in URLLC communications.

Fig. 2B illustrates a resource allocation method 200B in accordance with some aspects of the disclosure. In contrast to fig. 2a, ul grant 250-no a-CSI trigger-is included in PDCCH transmission. Since the UE115 is not occupied to determine CSI, the UE115 may transmit data (e.g., on PUSCH) using UL resources 252 faster after the UL grant 250 than the method 200A. Here, the UE115 may be in period N ₂ Thereafter, data is transmitted on UL resource 252, for time period N ₂ Is defined as the gap 254 between the end of the PDCCH transmission (i.e., UL grant 250) and the start of the scheduled UL resource 252 (e.g., PUSCH). In this example, the UL grant 250 is received in slot S0 260 and the UE may transmit UL data in the next slot, slot S1 262.

As illustrated in fig. 2A and 2B, the scheduling offset between transmitting the UL grant and the UE115 may transmit data on the resources indicated by the UL grant depends on whether an a-CSI trigger is included along with the UL grant. If an a-CSI trigger 202 is included as in fig. 2A, the minimum scheduling offset is Z symbols, depending on the SCS used and the type of CSI to be determined (e.g., number of antenna ports considered and codebook type). Different types of CSI may have different computational complexity and, therefore, may have different computation times. For example, for high latency CSI, Z may be set to Z ₂ As illustrated in table 1 below for various SCS values. The UE115 may ignore a-CSI triggers if the CSI computation timeline requirements are not met.

SCS(kHz)	Z ₂ (code element)
		15	40
30	72
		60	141
120	152

TABLE 1

For low latency CSI (e.g., wideband type 1CSI with up to 4 antenna ports), Z may be set to be a ratio Z ₂ Small values, but can still be quite large (e.g., long duration).

The minimum scheduling offset depends on the SCS and may be about N if the a-CSI trigger is not included with the UL grant ₂ As illustrated below in table 2 for various SCS values.

SCS(kHz)	N ₂ (code element)
		15	10
30	12
		60	23
120	36

TABLE 2

In some aspects, the CSI computation time Z or Z ₂ And UE PUSCH preparation time (without a-CSI trigger) N ₂ May be as described in the following documents: title 4 month 2020 is "third generation partnership project; a technical specification group radio access network; NR; 3GPP document TS 38.214, release 16, section 5.4 and section 6.4 ("3 GPP TS 38.214 document") for physical layer procedures "for data, which is incorporated herein by reference.

The much larger timeline for method 200A (when an a-CSI trigger is included along with an UL grant) compared to method 200B (when an a-CSI trigger is not included) creates several scheduling problems. For example, the BS105 may be interested in obtaining CSI for a large number of antenna ports and/or subband CQIs and PMIs that would be consistent with the longer Z described above ₂ High latency CSI of the timeline. And the PUSCH resources for CSI transmission need to be reserved several slots ahead of time, as illustrated in fig. 2A (e.g., 6 slots ahead when using an SCS value of 30 kHz) and table 1. As a result, UL data must not be transmitted in any of the reserved slots. Out-of-order PUSCH scheduling is not supported, so the UE cannot be scheduled for any PUSCH transmission carrying only UL-SCH in the time slot between when the UL grant and a-CSI trigger are transmitted and when the CSI report is scheduled. Thus, if UE115 has URLLC data ready for transmission, the transmission of the URLLC data will be delayed, which may be undesirable because the latency requirements of the URLLC transmission may not be met. Scheduling problems may be due to both: the time it takes for the UE115 to determine the requested CSI, and the a-CSI trigger and UL grant are jointly signaled in a single PDCCH as in method 200A.

Fig. 3 illustrates a CSI request and resource allocation method 300 in accordance with some aspects of the present disclosure. The method 300 solves some problems due to jointly signaling an a-CSI trigger and an UL grant in a single PDCCH as in the method 200A. Instead of jointly signaling the a-CSI trigger and the UL grant in a single PDCCH, the method 300 divides the process into discrete steps: generation of the CSI report is triggered by sending a CSI computation request 302 to the UE (e.g., as DCI in PDCCH), and transmission of the CSI report is requested by sending a CSI report transmission request 310 to the UE (e.g., as DCI in PDCCH). The BS105 may include information within the CSI computation request 302 (e.g., in the CSI request field) indicating which downlink resources 304 (e.g., CSI-RS or CSI-IM) the UE115 may use to measure CSI. However, the CSI calculation request 302 may not include any indication of which uplink resources to use for transmitting CSI reports. Although fig. 3 illustrates CSI measurement resources 304 as being located at a time after CSI computation request 302, it should be understood that CSI measurement resources 304 (e.g., RRC-configured semi-persistent resources) may be located at a time before CSI computation request 302 in other examples. The UE115 may determine the CSI and store the results (as described in fig. 4-8), but refrain from transmitting the CSI immediately. Instead, the UE115 is free to make other uplink transmissions (as scheduled by the BS 105), including, for example, URLLC data or any other type of uplink data, until it receives the CSI report transmission request 310. In the example of method 300, the BS105 may schedule the UE115 to transmit uplink data in the remaining portion of time slot S0 340, time slot S1 342, time slot S2 344, and time slot S3 346. During slot S4 348, the UE115 may receive a CSI report transmission request 310 including an allocation of resources 312 (e.g., on the PUSCH) for transmitting a CSI report, and in slot S5 350, the UE115 may transmit the CSI report. The BS105 may not transmit the CSI report transmission request 310 until the CSI computation timeline expires, which is defined in terms of Z "306, where Z" is the minimum gap between the CSI measurement resource 304 and the CSI report transmission request. Z "306 provides time for UE115 to perform CSI calculations instead of Z314 or Z'316 as discussed in fig. 2A and 2B. The UE115 may also cause the CSI report transmission request 310 to be received once it has been receivedReporting CSI with a shortened timeline corresponding to N as depicted in FIG. 2B ₂ And the sample values in table 2 above are used.

The minimum gap Z "306 may be a predetermined duration known to the BS105 and the UE 115. For example, the minimum gap Z "306 may be defined by a wireless communication standard, such as 3 GPP. In some aspects, the minimum gap Z "306 may be defined as the minimum gap from the end of the last symbol of the CSI measurement resource 304 to the beginning of the earliest symbol of the PDCCH (or CORESET) carrying the CSI report transmission request 310. In some other aspects, the minimum gap Z "306 may be defined as the minimum gap from the end of the PDCCH (or CORESET) carrying the CSI computation request 302 to the beginning of the earliest symbol of the PDCCH (or CORESET) carrying the CSI report transmission request 310. As discussed above, in some instances, CSI measurement resource 304 may be located at a time prior to CSI computation request 302. When the CSI measurement resource 304 is located at a time before the CSI computation request 302, the minimum gap Z "306 may be defined as the minimum gap from the end of the PDCCH (or CORESET) carrying the CSI computation request 302 to reduce implementation complexity at the UE 115.

The method 300 may employ a timer mechanism as described in fig. 4-9 to determine which CSI, if any, to transmit as part of the channel state report. For example, UE115 may start a timer at the end 320 of the Z "306 timeline, and the timer may run for duration 308 and expire at the end 322 of duration 308. The timer duration may be preconfigured (e.g., to a value defined in 3GPP specifications). Alternatively, the timer value may be configured by the BS105 (e.g., through RRC signaling) or indicated by the BS105 (e.g., as part of the CSI computation request 302). The timer duration may be based on information (e.g., CSI report content) that the UE115 is to include in the CSI report (e.g., the timer duration may be greater when the UE is to include more information in the CSI report). The timer duration may also be based on a codebook type, a number of antenna ports, a Channel Quality Indicator (CQI) type, and/or a Precoding Matrix Indicator (PMI) type associated with the CSI report. For example, the codebook type II based CSI may be associated with a longer processing or computation time (and thus a longer timer duration) than the codebook type I based CSI.

In some aspects, the minimum gap Z "306 may be defined using a similar mechanism as described in 3gpp TS 38.214 document section 5.4. For example, UE115 may be at symbol Z ″ _ref Where a timer is started, wherein Z ″) _ref Is defined as its Cyclic Prefix (CP) having elapsed a duration (e.g., T ″) from the last symbol of the PDCCH (or CORESET) carrying the CSI computation request 302 triggering the CSI computation _wait，CSI ) Next DL symbol starting later. Duration T ″) _wait，CSI Can be expressed as follows:

T″ _wait，CSI ＝Z″×(2048+144)×κ2 ^-μ ×T _c , (1)

where Z "represents Z"306 in units of OFDM symbols, k is a constant, μ represents SCS configuration, and T _c Representing the time unit in NR. In some examples, the μ parameter may be defined as SCS configuration for PDCCH (denoted μ _PDCCH ) With SCS configuration for CSI-RS (denoted as μ _CSI-RS ) Minimum between, which can be expressed as min (μ) _PDCCH ，μ _CSI-RS ). The μ parameter may be independent of the SCS configuration for PUSCH, since PUSCH resources are not scheduled in the DCI carrying CSI computation request 302.

If the CSI report transmission request 310 arrives while the timer is running (as illustrated herein), the UE115 may transmit the most recently computed CSI (based on the CSI measurement resources 304) in a CSI report. However, if the UE115 receives the CSI report transmission request 310 before the timer starts, the UE115 may not be able to complete the requested channel estimation and/or interference measurement or the UE115 may have missed an earlier CSI calculation request. If the CSI report transmission request is received after the timer has expired, this may indicate that the most recently computed CSI data is now stale, or that the UE115 may have missed an earlier CSI report request. In either case-when the CSI transmission request 310 is received before the timer starts or after the timer expires-the UE115 may transmit CSI (e.g., the most recently stored-now stale-CSI, or the previously stored CSI based on the older CSI computation request and the corresponding CSI measurement resource) or placeholder data in the CSI report that may not be current. The transmission of the stale CSI is to satisfy the CSI report transmission request because the UE will transmit as scheduled by the BS. Transmitting non-current CSI or placeholder data may be appropriate when, for example, the transmission on which the CSI report transmission request arrives also includes a grant for transmitting uplink shared channel (UL-SCH) data or a hybrid automatic repeat request (HARQ) acknowledgement. The placeholder CSI may be used as a filler because the BS is expecting a PUSCH transmission including the CSI and UL-SCH data or the CSI and HARQ ACK. It may be undesirable for the UE to discard UL-SCH data or HARQ ACKs due to failure of CSI report transmission requests to follow the CSI report timeline. In this case, the BS105 may determine that the CSI report is not based on the most recent CSI computation request. Alternatively, the UE may ignore the CSI report transmission request entirely (i.e., refrain from transmitting the CSI report), for example, if the CSI transmission request includes only a grant for transmitting the CSI report. In some aspects, the UE115 may remove the stored CSI from memory based on the expiration of the timer.

Fig. 4 is an exemplary sequence diagram illustrating a method 400 of communication between a BS105 and a UE115 in accordance with some aspects of the present disclosure. The method 400 may employ a mechanism similar to the method 300 discussed above with reference to fig. 3. As illustrated, method 400 includes several enumeration actions, although embodiments of method 400 may include additional actions before, after, and in between these enumeration actions. In some embodiments, one or more of these enumerated actions may be omitted or performed in a different order.

In step 402, the bs105 may transmit a first CSI calculation request (also referred to as a calculation trigger) to the UE115, which may include an indication of CSI measurement resources on which the UE115 should perform CSI measurements. The BS105 may transmit the first CSI computation request as a Downlink Control Information (DCI) message in PDCCH (also referred to herein as computing only DCI), and the first CSI computation request may not include any grant of UL resources for transmitting CSI reports. In other words, the first CSI calculation request may not include any scheduling information for transmitting CSI reports.

In step 404, the ue115 may identify a first CSI measurement resource based on the CSI computation request. The first CSI measurement resource may correspond to a CSI-RS (e.g., NZP CSI-RS) resource that the UE115 may use for channel response measurements and/or a CSI-IM resource that the UE115 may use for interference measurements. The first CSI measurement resource may be located at a time after the first CSI computation request. Alternatively, the first CSI measurement resource may be located at a time prior to the CSI computation request (e.g., in the case where the CSI will be based on a periodic or semi-persistent CSI-RS configured via RRC).

In step 406, the ue115 may determine the first CSI based on the first CSI measurement resource. The UE may perform channel and/or interference measurements to determine the CSI. The UE115 may store the resulting CSI in a memory of the UE 115. While the UE115 is calculating the first CSI and/or after the UE115 calculates the first CSI, the UE115 may receive a scheduling grant (e.g., for URLLC data) from the BS105 and may transmit uplink data based on the scheduling grant. In some examples, UE115 may keep multiple CSIs corresponding to different CSI computation requests and CSI measurement resources stored in its memory (e.g., memory 704 of fig. 7). The UE115 may store and maintain multiple CSIs in its memory. In some instances, there may be a limit to the number of CSIs that the UE may store, and the UE may delete the stored CSI (e.g., the oldest stored CSI) or not store the newly calculated CSI when the number of CSIs in memory exceeds the limit.

In step 408, the ue115 may receive a channel state report transmission request associated with the first CSI measurement resource from the BS105 (e.g., as a DCI message on a PDCCH). The channel state report transmission request may indicate that the UE115 may transmit a report including the first CSI it calculated based on the first CSI measurement resource. The CSI report transmission request may indicate which uplink resources (e.g., PUSCH resources) the UE115 may use to transmit the report. In an example, a channel state report transmission request (e.g., reporting only DCI) includes a CSI request field including a value mapped to a CSI trigger state. The CSI trigger state may be associated with a CSI reporting configuration referring to the first CSI measurement resource to be used for reporting CSI. Accordingly, the UE115 may determine that the BS105 is requesting CSI for the first CSI measurement resource.

In step 410, the ue115 may transmit a channel state report including the first CSI to the BS 105. In some examples, the UE115 may employ a timer as described in detail below with reference to method 500 (illustrated in fig. 5) to determine which, if any, stored CSI to transmit to the BS105 in response to the CSI transmission request, as described below in step 418.

In step 412, the bs105 may transmit a second CSI calculation request in a similar manner to the first calculation request.

In step 414, bs 115 may identify the second CSI measurement resource in a similar manner as the first CSI measurement resource. The UE115 may perform channel and/or interference measurements to determine the CSI. While the UE115 is calculating CSI based on the second CSI measurement resource and/or after the UE115 calculates the CSI, the UE115 may receive a scheduling grant (e.g., for URLLC data) from the BS105 and may transmit uplink data based on the scheduling grant. The UE115 may store the CSI determined based on the second CSI measurement resource in a memory (e.g., memory 704 of fig. 7). As depicted in step 406, the number of CSIs that the UE115 may store may be limited. For example, if the limit has been reached, the UE115 may delete older CSI (e.g., CSI from step 406) or refrain from storing newly calculated CSI.

In step 416, the ue115 may determine and store the second CSI based on the second CSI measurement resource.

In step 418, the ue115 may receive a second channel state report transmission request (e.g., as a DCI message on a PDCCH) associated with a second CSI measurement resource from the BS 105. The second channel state report transmission request may indicate that the UE115 may now transmit a CSI report including the second CSI it calculated based on the second CSI measurement resource in response to the second CSI calculation request. The second CSI report transmission request may indicate which uplink resources (e.g., PUSCH resources) the UE115 may use to transmit the report.

In some examples, the UE115 may employ a timer mechanism to determine whether to transmit the second CSI, the first CSI, or a different CSI as requested by the BS105 or not. For example, the UE115 may start (or reset) a timer after a certain period (or duration) has elapsed from the end time of the second CSI measurement resource. The period of time may be (approximately) a minimum gap between the end time of the second CSI measurement resource and the time at which the UE115 may determine the second CSI. The timer duration may be preconfigured (e.g., to a value defined in 3GPP specifications). Alternatively, the timer value may be indicated by the BS105 (e.g., through RRC signaling) or configured by the BS105 (e.g., as part of the CSI computation request). The timer duration may be based on information that the UE115 is to include in the second CSI report (e.g., the timer duration may be greater when the UE is to include more information in the second CSI report). The timer duration may also be based on a codebook type, a number of antenna ports, a Channel Quality Indicator (CQI) type, and/or a Precoding Matrix Indicator (PMI) type associated with the second CSI report.

In some examples, the time period for which the timer is running may correspond to a time period for which a second CSI report should be transmitted to the BS105 in response to receiving the second CSI report transmission request. For example, if the second CSI report transmission request arrives while the timer is running, the UE115 may transmit the second CSI (i.e., the most recently calculated CSI) in the CSI report. However, if the UE115 receives the second CSI report transmission request before the timer starts, the UE115 may not be able to complete the requested channel estimation and/or interference measurement corresponding to the second CSI measurement resource. If the second CSI report transmission request is received after the timer has expired, this may indicate that the second CSI is now stale. In either case-when the second CSI transmission request is received before the timer starts or after the timer expires-the UE115 may transmit CSI that may not be current (e.g., the most recently stored-now-stale-CSI, or the previously stored CSI based on the older CSI computation request and the corresponding CSI measurement resource). For example, UE115 may determine to transmit the first CSI it determined and stored in step 406. The UE115 may also determine to transmit the placeholder data in the CSI report instead of the second CSI. Transmitting the first CSI or placeholder data may be appropriate when, for example, the transmission on which the second CSI report transmission request arrives also includes a grant for transmitting UL-SCH data or HARQ acknowledgement. Alternatively, the UE115 may ignore the second CSI report transmission request entirely (i.e., refrain from transmitting the CSI report), for example, if the second CSI transmission request includes only a grant for transmitting the CSI report. In some examples, the UE115 may also remove the stored CSI from memory based on the expiration of a timer.

At block 420, ue115 may optionally transmit a second channel state report (e.g., in the uplink resources indicated in the second CSI report transmission request) that includes the CSI (or occupancy data) it determined to include after step 418.

Fig. 5 is a flow diagram of a method 500 of wireless communication in accordance with some aspects of the present disclosure. Aspects of the method may be performed by the UE115 alone or in conjunction with the BS 105.

At block 502, the ue115 may receive a CSI computation request (e.g., in a DCI message on a PDCCH) from the BS105, as described in detail in fig. 6-9. The CSI computation request may not include any resources for UL transmission of CSI data.

At block 504, the ue115 may identify a CSI measurement resource based on the CSI computation request. The CSI measurement resources may correspond to CSI-RS (e.g., NZP CSI-RS) resources that the UE115 may use for channel response measurements and/or CSI-IM resources that the UE115 may use for interference measurements. The first CSI measurement resource may be located at a time after the first CSI computation request. Alternatively, the first CSI measurement resource may be located at a time prior to the CSI computation request (e.g., in the case where the CSI will be based on a periodic or semi-persistent CSI-RS configured via RRC). The method then continues to

blocks

506 and 510. For example, UE115 may perform

blocks

506 and 510 in parallel.

At block 506, the UE115 starts a timer after Z "symbols, where Z" is the minimum gap between the end of the CSI measurement resource (e.g., CSI-RS resource and/or CSI-IM resource) and the start of the CSI report transmission request (e.g., the time at which the UE115 is the fastest to complete determining the CSI). Once Z "symbols have elapsed, the UE115 starts (or resets) a timer during which it expects to receive a CSI report transmission request. The timer may help the UE115 determine which, if any, stored CSI to transmit to the BS in response to the CSI transmission request, as described herein. The timer duration may be preconfigured (e.g., to a value defined in 3GPP specifications). Alternatively, the timer value may be indicated by the BS105 (e.g., through RRC signaling) or configured by the BS105 (e.g., as part of the CSI computation request). The timer duration may be based on information that the UE115 is to include in the CSI report (e.g., the timer duration may be greater when the UE is to include more information in the CSI report). The timer duration may also be based on a codebook type, a number of antenna ports, a Channel Quality Indicator (CQI) type, and/or a Precoding Matrix Indicator (PMI) type associated with the CSI report.

At block 510, the ue115 determines CSI based on the CSI measurement resources. The UE115 may perform channel and/or interference measurements on the CSI measurement resources. For example, if the CSI measurement resources include CSI-RS measurement resources, the UE115 may perform channel measurements based on the CSI-RS transmitted in the CSI-RS measurement resources. Additionally or alternatively, if the CSI measurement resources include CSI-IM resources, UE 116 may measure interference in the CSI-IM resources. While (or after) performing the channel measurements, the UE115 may transmit UL data (e.g., URLLC data that is independent of CSI data) to the BS 105. For example, the BS105 may transmit an UL grant to the UE115 during this time (e.g., during gap 306 of fig. 3), and the UE115 may transmit uplink data (e.g., on the PUSCH) to the BS 105. Although fig. 5 illustrates the UE115 determining CSI upon receiving a CSI computation request, it should be understood that in other examples, the CSI computation request may reference a CSI measurement resource (e.g., an RRC-configured semi-persistent CSI resource) located at a time prior to the CSI computation request. Accordingly, when the UE115 receives the CSI calculation request, the UE115 may have started or completed the CSI calculation.

At block 512, ue115 may receive a CSI report transmission request. If the UE115 has not received the request, the UE115 may remain in this block until it receives the request. Once the UE115 receives the CSI report transmission, the UE115 may proceed to block 514.

At block 514, the UE115 determines whether the CSI report transmission request was received before the timer (of block 508) started, which may indicate that the UE115 has not had time to complete determining the CSI. If the CSI report transmission request is received before the timer starts, the UE115 proceeds to block 518. Otherwise, the UE115 proceeds to block 516.

In block 516, the ue115 determines that the timer (of block 508) is currently in progress. If the timer is in progress, the UE115 proceeds to block 520. If the timer is not in progress (i.e., it expires), the UE may determine that the CSI at block 510 is stale, and the UE115 proceeds to block 518.

At block 518, the ue115 may transmit the older CSI (e.g., the previously stored CSI based on the earlier CSI computation request and the CSI of the earlier corresponding CSI measurement resource) or the placeholder data in the CSI report too early (as determined at block 514) or too late (as determined at block 516) based on the CSI report transmission request. Transmitting older CSI or placeholder data may be appropriate when, for example, the transmission on which the CSI transmission request arrived also includes a grant for transmitting uplink shared channel (UL-SCH) data or a hybrid automatic repeat request (HARQ) acknowledgement. Alternatively, the UE115 may ignore the CSI report transmission request entirely (i.e., refrain from transmitting the CSI report), for example, if the CSI transmission request includes only a grant for transmitting the CSI report.

At block 520, the ue115 may transmit a CSI report based on the current CSI.

Fig. 6 is a block diagram of an example BS 600 in accordance with some aspects of the present disclosure. The BS 600 may be a BS105 in the network 100 as discussed above in fig. 1. As shown, BS 600 may include a processor 602, a memory 604, a channel state module 608, a transceiver 610 including a modem subsystem 612 and an RF unit 614, and one or more antennas 616. These elements may communicate with each other directly or indirectly, e.g., via one or more buses.

The processor 602 may have various features that are special type processors. For example, these features may include a CPU, DSP, ASIC, controller, FPGA device, another hardware device, firmware device, or any combination thereof configured to perform the operations described herein. The processor 602 may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

The memory 604 may include cache memory (e.g., cache memory of the processor 602), RAM, MRAM, ROM, PROM, EPROM, EEPROM, flash memory, a solid state memory device, one or more hard drives, an array based on memristors, other forms of volatile and non-volatile memory, or a combination of different types of memory. In some aspects, memory 604 may include non-transitory computer-readable media. Memory 604 may store instructions 606. The instructions 606 may include instructions that, when executed by the processor 602, cause the processor 602 to perform the operations described herein (e.g., aspects of fig. 6-9 and 11). The instructions 606 may also be referred to as program code. The program code may be for causing a wireless communication device to perform the operations, for example, by causing one or more processors, such as processor 602, to control or instruct the wireless communication device to do so. The terms "instructions" and "code" should be read broadly to include any type of computer-readable statements. For example, the terms "instructions" and "code" may refer to one or more programs, routines, subroutines, functions, procedures, and the like. The "instructions" and "code" may comprise a single computer-readable statement or a plurality of computer-readable statements.

The channel state module 608 may be implemented via hardware, software, or a combination thereof. For example, the channel state module 608 may be implemented as a processor, circuitry, and/or instructions 606 stored in the memory 604 and executed by the processor 602. In some examples, channel state module 608 may be integrated within modem subsystem 612. For example, the channel state module 608 may be implemented by a combination of software components (e.g., executed by a DSP or general purpose processor) and hardware components (e.g., logic gates and circuitry) within the modem subsystem 612.

The channel state module 608 may be used for various aspects of the present disclosure, e.g., aspects of fig. 3-5 and 9. For example, channel state module 608 may transmit a CSI computation request (e.g., in cooperation with transceiver 610). The channel state module 608 may transmit the CSI computation request as a Downlink Control Information (DCI) message in the PDCCH (also referred to herein as compute-only DCI), and the CSI computation request may not include any grant of UL resources for transmitting CSI reports by the UE 115. In other words, the CSI computation request may not indicate any scheduling information or resources for transmitting the CSI report.

The channel state module 608 may also be configured to transmit (e.g., in cooperation with the transceiver 610) a channel state report transmission request associated with the first CSI measurement resource (e.g., as a DCI message on a PDCCH) to the UE 115. The first CSI measurement resource may include a CSI-RS (e.g., NZP CSI-RS) resource and/or a CSI-IM resource. The channel state report transmission request may indicate that the UE115 should transmit a report including the CSI it calculated based on the first CSI measurement resource. The CSI report transmission request may indicate which uplink resources (e.g., PUSCH resources) the UE115 should use when transmitting the report. In some examples, channel state module 608 may transmit the channel state report transmission request after a first duration has elapsed from a time at which the first CSI measurement resource was located (e.g., a beginning or end of the first CSI measurement resource). The first duration may be based on a CSI computation timeline (e.g., as may be defined in the 3GPP specifications), as described with reference to fig. 3. In some examples, channel state module 608 may also indicate to UE115 a configuration for a duration of a timer for associating a CSI report to the first CSI measurement resource (e.g., via RRC signaling or as part of a CSI computation request). The timer duration may be based on information to be included in the CSI report (CSI report type) (e.g., the timer duration may be larger when more information is to be in the CSI report). The timer duration may also be based on a codebook type, a number of antenna ports, a Channel Quality Indicator (CQI) type, and/or a Precoding Matrix Indicator (PMI) type associated with the CSI report.

The channel state module 608 may also be configured to receive, in response to the channel state report transmission request (e.g., using, on the PUSCH in cooperation with the transceiver 610, the resources indicated by the channel state module 608 in the channel state report transmission request), a channel state report associated with the first CSI measurement resource. In some aspects, the channel state report may instead be associated with a different CSI measurement resource. For example, the channel state module 608 may transmit an indication of a second CSI measurement resource prior to the first CSI measurement resource to the UE 115. Depending on when the channel state module 608 transmits a CSI report transmission request, the channel state report may instead be based on the second CSI measurement resource. For example, if the channel state module 608 transmits a CSI report transmission request while a timer is running (e.g., the timer described in fig. 5, which may be configured by the channel state module 608), the channel state report may be based on the first CSI measurement resource. However, if the CSI report transmission request is transmitted before the timer starts (which may be too early for the UE115 to complete determining the CSI) or after the timer expires (which may be when the CSI is stale), the channel state module 608 may instead receive a CSI report, or occupancy data, based on the second CSI measurement resource. This may occur when, for example, the BS105 includes a grant for transmitting UL-SCH data or HARQ acknowledgement along with a grant for transmitting CSI reports. In some examples, channel state module 608 may not receive CSI reports at all, e.g., where channel state module 608 has scheduled uplink resources for CSI reporting only.

In some aspects, the BS105 may transmit (e.g., in cooperation with the transceiver 610) a scheduling grant to the UE115 after the channel state module 608 transmits the CSI computation request and before the channel state module 608 transmits the CSI report transmission request. The BS 115 may then receive an uplink transmission (e.g., a transmission associated with URLLC data) from the UE115 based on the scheduling grant.

As shown, transceiver 610 may include a modem subsystem 612 and an RF unit 614. Transceiver 610 may be configured to communicate bi-directionally with other devices, such as UE115 and/or 500 and/or another core network element. Modem subsystem 612 may be configured to modulate and/or encode data in accordance with an MCS (e.g., an LDPC coding scheme, a turbo coding scheme, a convolutional coding scheme, a digital beamforming scheme, etc.). RF unit 614 may be configured to process (e.g., perform analog-to-digital conversion, digital-to-analog conversion, etc.) modulated/encoded data (e.g., PDCCH signals, DL data, scheduling grants, RRC configuration, reference signals, CSI-RS, CSI computation requests, CSI report transmission requests, CSI computation-only DCI, CSI report CSI, etc.) from modem subsystem 612 (on outgoing transmissions) or transmissions originating from another source, such as UE115 and/or UE 700. The RF unit 614 may be further configured to perform analog beamforming in conjunction with digital beamforming. Although shown as being integrated together in transceiver 610, modem subsystem 612 and/or RF unit 614 may be separate devices that are coupled together at BS105 to enable BS105 to communicate with other devices.

RF unit 614 may provide modulated and/or processed data, such as data packets (or, more generally, data messages that may contain one or more data packets and other information), to an antenna 616 for transmission to one or more other devices. The antenna 616 may further receive data messages transmitted from other devices and provide the received data messages for processing and/or demodulation at the transceiver 610. The transceiver 610 may provide the demodulated and decoded data (e.g., PUSCH signals, UL data, UL URLLC, CSI reports) to the channel state module 608 for processing. The antenna 616 may include multiple antennas of similar or different designs in order to maintain multiple transmission links.

In an example, the transceiver 610 is configured to transmit a CSI computation request to the UE 115. The transceiver 610 is further configured to transmit a CSI report transmission request associated with the first CSI measurement resource to the UE115, and receive a CSI report associated with the first CSI measurement resource from the UE115 in response to the CSI report transmission request.

Fig. 7 is a block diagram of an example UE 700, in accordance with some aspects of the present disclosure. The UE 700 may be the UE115 as discussed above in fig. 1. As shown, UE 700 may include a processor 702, a memory 704, a channel state module 708, a transceiver 710 (including a modem subsystem 712 and a Radio Frequency (RF) unit 714), and one or more antennas 716. These elements may communicate with each other, directly or indirectly, for example, via one or more buses.

The processor 702 may include a Central Processing Unit (CPU), a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a controller, a Field Programmable Gate Array (FPGA) device, another hardware device, a firmware device, or any combination thereof, configured to perform the operations described herein. The processor 702 may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

The memory 704 may include cache memory (e.g., cache memory of the processor 702), random Access Memory (RAM), magnetoresistive RAM (MRAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory devices, hard drives, other forms of volatile and non-volatile memory, or combinations of different types of memory. In an aspect, memory 704 includes non-transitory computer-readable media. The memory 704 may store or have instructions 706 recorded thereon. The instructions 706 may include instructions that, when executed by the processor 702, cause the processor 702 to perform the operations described herein with reference to the UE115 in connection with aspects of the disclosure (e.g., aspects of fig. 6-8, 10, and 12). The instructions 706 may also be referred to as program code, which may be broadly interpreted to include any type of computer-readable statements as discussed above with reference to fig. 4.

The channel status module 708 may be implemented via hardware, software, or a combination thereof. For example, the channel state module 708 may be implemented as a processor, circuitry, and/or instructions 706 that are stored in the memory 704 and executed by the processor 702. In some examples, channel state module 708 may be integrated within modem subsystem 712. For example, the channel state module 708 may be implemented by a combination of software components (e.g., executed by a DSP or general purpose processor) and hardware components (e.g., logic gates and circuitry) within the modem subsystem 712. Operations described as being performed by the channel state module 708 may be performed by or in conjunction with different modules (e.g., the transceiver 710).

The channel state module 708 may be used in various aspects of the present disclosure, e.g., the aspects of fig. 3-5 and fig. 8. For example, the channel state module 708 may be configured to receive (e.g., in conjunction with the transceiver 710) a CSI computation request from the BS 105. Channel state module 708 may receive the CSI computation request as a Downlink Control Information (DCI) message in the PDCCH (also referred to herein as computing only DCI), and the CSI computation request may not include any grant of UL resources for transmitting CSI reports. In other words, the CSI calculation request may not include any scheduling information for transmitting CSI reports.

The channel state module 708 may be further configured to identify a first CSI measurement resource based on the CSI computation request. The CSI measurement resources may include CSI-RS and/or CSI-IM resources. The channel state module 708 may receive a configuration for the first CSI measurement resource from the BS105 (e.g., included in the CSI computation request or received separately).

Channel state module 708 may also be configured to determine CSI based on the first CSI measurement resource (e.g., in cooperation with processor 702). Channel state module 708 may perform channel and/or interference measurements to determine CSI. In some examples, channel state module 708 may store the resulting CSI in memory 704. Thereafter, the UE115 may continue to transmit other types of uplink data (e.g., URLLC data). For example, the UE115 may receive a scheduling grant from the BS105 and may transmit uplink data based on the scheduling grant. In some examples, channel state module 708 may keep multiple CSI corresponding to different CSI computation requests and CSI measurement resources stored in its memory. For example, the channel state module 708 may receive an indication of a second CSI measurement resource preceding the first CSI measurement resource. Channel state module 708 may perform channel and/or interference measurements based on the second reference CSI measurement resource and store the resulting CSI in memory 704. Channel state module 708 may store and maintain multiple CSIs in its memory 704. In some instances, there may be a limit to the number of CSIs that module 708 may store, and channel state module 708 may delete the stored CSI or not store the newly calculated CSI when the number of CSIs in memory 704 exceeds the limit.

The channel state module 708 may also be configured to receive (e.g., in cooperation with the transceiver 710, as a DCI message on a PDCCH) a channel state report transmission request associated with the first CSI measurement resource from the BS 105. The channel state report transmission request may indicate that the channel state module 708 should now transmit a report including the CSI it calculated based on the first CSI measurement resource. The CSI report transmission request may indicate which uplink resources (e.g., PUSCH resources) the channel state module 708 should use when transmitting the report. The channel state module 708 may then transmit a channel state report (e.g., in cooperation with the transceiver 710) including the CSI to the BS 105.

In some examples, the channel state module 708 may employ a timer as described in method 500 (illustrated in fig. 5) to determine which, if any, stored CSI to transmit to the BS105 in response to the CSI transmission request. For example, channel state module 708 may start (or reset) a timer after a certain period (or duration) has elapsed from the time the first CSI measurement resource was located (e.g., the first CSI measurement resource started or ended). The period of time may be (approximately) the minimum gap between the end time of the CSI measurement resources and the time at which the channel state module 708 may determine the CSI. The timer duration may be preconfigured (e.g., to a value defined in 3GPP specifications). Alternatively, the timer value may be indicated by the BS105 (e.g., through RRC signaling) or configured by the BS105 (e.g., as part of the CSI computation request). The timer duration may be based on information that channel state module 708 is to include in the CSI report (e.g., the timer duration may be greater when channel state module 708 is to include more information in the CSI report). The timer duration may also be based on a codebook type, a number of antenna ports, a Channel Quality Indicator (CQI) type, and/or a Precoding Matrix Indicator (PMI) type associated with the CSI report.

The time period for which the timer is running may correspond to a time period for which a current CSI report should be transmitted to the BS105 in response to receiving a CSI report transmission request. For example, if a CSI report transmission request arrives while a timer is running, the channel state module 708 may transmit the most recently calculated CSI (i.e., based on the first CSI measurement resource) in the CSI report. However, if the channel state module 708 receives a CSI report transmission request before the timer starts, the channel state module 708 may not be able to complete the requested channel estimation and/or interference measurement. If the CSI report transmission request is received after the timer expires, this may indicate that the most recently calculated CSI data is now stale. In either case-when a CSI transmission request is received before the timer starts or after the timer expires-channel state module 708 may transmit CSI that is not current (e.g., previously stored) CSI. For example, channel state module 708 may transmit CSI determined relative to the second (earlier) CSI measurement resource instead of the most recent (later) first CSI measurement resource. Channel state module 708 may also transmit placeholder data in the CSI report instead of the actual CSI. Transmitting older CSI or placeholder data may be appropriate when, for example, the transmission on which the CSI transmission request arrived also includes a grant for transmitting UL-SCH data or HARQ acknowledgement. Alternatively, the channel state module 708 may ignore the CSI report transmission request entirely (i.e., refrain from transmitting the CSI report), for example, if the CSI transmission request includes only a grant for transmitting the CSI report. In some examples, channel state module 708 may also remove stored CSI from memory based on expiration of a timer.

As shown, transceiver 710 may include a modem subsystem 712 and an RF unit 714. The transceiver 710 may be configured for bidirectional communication with other devices, such as the BS 105. Modem subsystem 712 may be configured to modulate and/or encode data from memory 704 and/or channel state module 708 according to a Modulation and Coding Scheme (MCS) (e.g., a Low Density Parity Check (LDPC) coding scheme, a turbo coding scheme, a convolutional coding scheme, a digital beamforming scheme, etc.). The RF unit 714 may be configured to process (e.g., perform analog-to-digital conversion, digital-to-analog conversion, etc.) modulated/encoded data (e.g., PUSCH signals, UL data, UL URLLC data, CSI reports) from the modem subsystem 712 (on an out-of-band transmission) or a transmission originating from another source, such as the UE115 or BS 105. The RF unit 714 may be further configured to perform analog beamforming in conjunction with digital beamforming. Although shown as being integrated together in the transceiver 710, the modem subsystem 712 and the RF unit 714 may be separate devices that are coupled together at the UE115 to enable the UE115 to communicate with other devices.

RF unit 714 may provide modulated and/or processed data, such as data packets (or, more generally, data messages that may contain one or more data packets and other information), to antenna 716 for transmission to one or more other devices. The antenna 716 may further receive data messages transmitted from other devices. The antenna 716 can provide received data messages for processing and/or demodulation at the transceiver 710. The transceiver 710 may provide the demodulated and decoded data (e.g., PDCCH signals, DL data, scheduling grants, CSI-RS, CSI report requests, CSI report transmission requests, CSI-only computational DCI, CSI-only reporting CSI, etc.) to the channel state module 708 for processing. The antenna 716 may include multiple antennas of similar or different designs in order to maintain multiple transmission links. The RF unit 714 may be configured with an antenna 716.

In an aspect, the UE 700 may include multiple transceivers 710 implementing different RATs (e.g., NR and LTE). In an aspect, the UE 700 may include a single transceiver 710 that implements multiple RATs (e.g., NR and LTE). In an aspect, the transceiver 710 may include various components, where different combinations of the components may implement different RATs.

In an example, the transceiver 710 is configured to receive a CSI computation request from the BS 105. The processor 702 is configured to identify a first CSI measurement resource based on the CSI computation request and determine CSI based on the first CSI measurement resource. The transceiver 710 is further configured to receive a CSI report transmission request associated with the first CSI measurement resource from the BS105 after the CSI computation request.

Fig. 8 is a flow chart of a method 800 of wireless communication in accordance with some aspects of the present disclosure. Aspects of method 800 may be performed by a computing device (e.g., a processor, processing circuitry, and/or other suitable components) of a wireless communication device or other suitable means for performing steps. For example, a wireless communication device (such as UE115 or 700) may utilize one or more components (such as processor 704, memory 708, channel state module 710, transceiver 712, modem 716, and one or more antennas 516) to perform the steps of method 800. Method 800 may employ a mechanism similar to that in method 300, sequence 400, and method 500 as described above with reference to fig. 3-5. As illustrated, the method 800 includes several enumeration steps, but aspects of the method 800 may include additional steps before, after, and between these enumeration steps. In some aspects, one or more of the enumerated steps may be omitted or performed in a different order.

At block 802, the ue115 may receive a CSI computation request from the BS 105. The UE115 may receive the CSI computation request as a Downlink Control Information (DCI) message in the PDCCH (also referred to herein as computing only DCI), and the CSI computation request may not include any grant of UL resources for transmitting CSI reports. In other words, the CSI calculation request may not include any scheduling information for transmitting the CSI report. In some instances, UE115 may utilize one or more components, such as processor 702, memory 704, channel state module 708, transceiver 710, modem 712, and one or more antennas 716, to perform aspects of block 802.

At block 804, the ue115 may identify a first CSI measurement resource based on the CSI computation request. The first CSI measurement resource may include a CSI-RS (e.g., NZP CSI-RS) and/or a CSI-IM resource. The UE115 may receive a configuration for the first CSI measurement resource from the BS as part of the CSI computation request or independently. In some examples, the UE115 may utilize one or more components (such as the processor 702 and the channel state module 708) to perform aspects of block 802.

At block 806, the ue115 may determine CSI based on the first CSI measurement resource. The UE115 may perform channel and/or interference measurements to determine the CSI. In some examples, the UE115 may store the resulting CSI in a memory (e.g., memory 704) within the UE 115. Thereafter, the UE115 may continue to transmit other types of uplink data (e.g., URLLC data). For example, the UE115 may receive a scheduling grant from the BS105 and may transmit uplink data based on the scheduling grant. In some examples, the UE115 may keep multiple CSI corresponding to different CSI computation requests and CSI measurement resources stored in its memory. For example, the UE115 may have received an indication of the second CSI measurement resource prior to the CSI measurement resource. The UE115 may have performed channel estimation and/or interference measurement based on the second reference CSI measurement resource and stored the resulting CSI in memory. The UE115 may store and maintain multiple CSIs in its memory. In some instances, there may be a limit to the number of CSIs that the UE115 may store, and the UE115 may delete the stored CSI or not store the newly calculated CSI when the number of CSIs in memory exceeds the limit. In some examples, UE115 may utilize one or more components, such as processor 702, memory 704, and channel state module 708, to perform aspects of block 806.

In step 808, the ue115 may receive a channel state report transmission request associated with the CSI measurement resource from the BS105 (e.g., as a DCI message on a PDCCH). In an example, a channel state report transmission request (e.g., reporting only DCI) includes a CSI request field including a value mapped to a CSI trigger state. The CSI trigger state may be associated with one or more CSI reporting configurations. Each CSI reporting configuration may refer to CSI measurement resources that the BS105 is requesting for reporting. The channel state report transmission request may indicate that the UE115 should transmit a report including the CSI it calculated based on the CSI measurement resource. The CSI report transmission request may indicate which uplink resources (e.g., PUSCH resources) the UE115 should use when transmitting the report. The UE115 may then transmit a channel state report including the CSI to the BS 105.

In some examples, the UE115 may employ a timer as described in method 500 (illustrated in fig. 5) to determine which, if any, stored CSI to transmit to the BS105 in response to the CSI report transmission request. For example, the UE115 may start (or reset) a timer after a certain period (or duration) has elapsed from the end time of the first CSI measurement resource (e.g., the end of the last symbol of the CSI measurement resource). The period may be (approximately) a minimum gap from an end time of a last symbol of the first CSI measurement resource or an end time of a PDCCH (or CORESET) carrying a CSI computation request to a start time of an earliest symbol of the PDCCH (or CORESET) carrying a CSI report transmission request, e.g., as shown in equation (1) discussed above with reference to fig. 3. The timer duration may be preconfigured (e.g., to a value defined in a 3GPP specification). Alternatively, the timer value may be indicated by the BS105 (e.g., through RRC signaling) or configured by the BS105 (e.g., as part of the CSI computation request). The timer duration may be based on information that the UE115 is to include in the CSI report (e.g., the timer duration may be greater when the UE is to include more information in the CSI report). The timer duration may also be based on a codebook type, a number of antenna ports, a Channel Quality Indicator (CQI) type, and/or a Precoding Matrix Indicator (PMI) type associated with the CSI report.

The time period for which the timer is running may correspond to a time period for which a current CSI report should be transmitted to the BS105 in response to receiving a CSI report transmission request. For example, if a CSI report transmission request arrives while a timer is running, the UE115 may transmit the most recently calculated CSI in the CSI report (i.e., based on the first CSI measurement resource). However, if the UE115 receives a CSI report transmission request before the timer starts, the UE115 may not be able to complete the requested channel and/or interference measurements. If the CSI report transmission request is received after the timer expires, this may indicate that the most recently calculated CSI data is now stale. In either case-when a CSI transmission request is received before the timer starts or after the timer expires-the UE115 may transmit CSI that is not current (e.g., previously stored) CSI. For example, the UE115 may transmit CSI determined relative to the second (earlier) CSI measurement resource instead of the most recent (later) first CSI measurement resource.

The UE115 may also transmit placeholder data in the CSI report instead of the actual CSI. Transmitting older CSI or placeholder data may be appropriate when, for example, the transmission on which the CSI transmission request arrived also includes a grant for transmitting UL-SCH data or HARQ acknowledgement. Alternatively, the UE115 may ignore the CSI report transmission request entirely (i.e., refrain from transmitting the CSI report), for example, if the CSI transmission request includes only a grant for transmitting the CSI report. In some examples, UE115 may also remove the stored CSI from memory based on the expiration of a timer (because no CSI report transmission request for CSI was received). In some instances, UE115 may utilize one or more components, such as processor 702, memory 704, channel state module 708, transceiver 710, modem 712, and one or more antennas 716, to perform aspects of block 808.

Fig. 9 is a flow diagram of a method 900 of wireless communication in accordance with some aspects of the present disclosure. Aspects of method 900 may be performed by a computing device (e.g., a processor, processing circuitry, and/or other suitable components) of a wireless communication device or other suitable means for performing steps. For example, a wireless communication device (such as BS105 or 600) may perform the steps of method 900 using one or more components (such as processor 602, memory 604, channel state module 608, transceiver 610, modem 612, and one or more antennas 616). Method 900 may employ mechanisms similar to those in method 300, sequence 400, and method 500 as described above with reference to fig. 3-5. As illustrated, the method 900 includes several enumeration steps, although aspects of the method 900 may include additional steps before, after, and between these enumeration steps. In some aspects, one or more of the enumerated steps may be omitted or performed in a different order.

At block 902, the bs105 may transmit a CSI computation request to the UE 115. The UE115 may transmit the CSI computation request as a Downlink Control Information (DCI) message in the PDCCH (also referred to herein as computing only DCI), and the CSI computation request may not include any grant of UL resources for transmitting CSI reports by the UE 115. In other words, the CSI computation request may not indicate any scheduling information or resources for transmitting the CSI report. In some embodiments, the CSI computation request may include a configuration of a first CSI measurement resource, which may include a CSI-RS (e.g., NZP CSI-RS) or a CSI-IM resource. In some embodiments, the BS105 may transmit the configuration for the first CSI measurement resource separately to the UE 115. In some examples, BS105 may utilize one or more components, such as processor 602, memory 604, channel state module 608, transceiver 610, modem 612, and one or more antennas 616, to perform aspects of block 902.

At block 906, the bs105 may transmit a channel state report transmission request (e.g., as a DCI message on a PDCCH) associated with the first CSI measurement resource to the UE 115. In an example, a channel state report transmission request (e.g., reporting only DCI) includes a CSI request field including a value mapped to a CSI trigger state. The CSI trigger state may be associated with one or more CSI reporting configurations. Each CSI reporting configuration may refer to CSI measurement resources that the BS105 is requesting for reporting. The CSI measurement resource referenced by the CSI report transmission request may correspond to the first CSI measurement resource referenced by the CSI computation request. The channel state report transmission request may indicate that the UE115 should transmit a report including the CSI it calculated based on the first CSI measurement resource. The CSI report transmission request may indicate which uplink resources (e.g., PUSCH resources) the UE115 should use when transmitting the report. In some examples, the BS105 may transmit the channel state report transmission request after a first duration has elapsed from an end time of the first CSI measurement resource (e.g., an end of a last symbol of the CSI measurement resource). The first duration may be based on the CSI computation timeline, as described with reference to fig. 3. In some examples, the BS105 may also indicate to the UE115 a configuration for a duration of a timer for associating a CSI report to the first CSI measurement resource (e.g., via RRC signaling or as part of a CSI computation request). The timer duration may be based on information to be included in the CSI report (e.g., the timer duration may be greater when more information is to be in the CSI report). The timer duration may also be based on a codebook type, a number of antenna ports, a Channel Quality Indicator (CQI) type, and/or a Precoding Matrix Indicator (PMI) type associated with the CSI report. In some examples, the BS105 may utilize one or more components, such as the processor 602, the memory 604, the channel state module 608, the transceiver 610, the modem 612, and the one or more antennas 616, to perform aspects of block 904.

At block 908, the BS105 may receive (e.g., using the resources indicated by the BS105 in the channel state report transmission request on the PUSCH) a channel state report associated with the first CSI measurement resource in response to the channel state report transmission request. In some aspects, the channel state report may instead be associated with a different CSI measurement resource. For example, the BS105 may indicate to the UE115 a second CSI measurement resource prior to the first CSI measurement resource. Depending on when the UE115 transmits the CSI report transmission request, the channel state report may instead be based on the second CSI measurement resource. For example, if the UE115 receives the CSI report transmission request while a timer (e.g., the timer described in fig. 5, which may be configured by the BS105, as discussed with reference to block 906) is running, the channel state report may be based on the first CSI measurement resource. However, if the CSI report transmission request is received by the UE115 before the timer starts (which may be too early for the UE115 to complete determining the CSI) or after the timer expires (which may be when the CSI is stale), the BS105 may instead receive a CSI report based on the second CSI measurement resource, or placeholder data. This may occur when, for example, the BS105 includes a grant for transmitting UL-SCH data or HARQ acknowledgement along with a grant for transmitting a CSI report. In some instances, the BS105 may not receive the CSI report at all, e.g., where the BS105 schedules only uplink resources for the CSI report.

In some examples, the BS105 may transmit a scheduling grant to the UE115 after the CSI computation request and before the CSI report transmission request. The BS 115 may then receive an uplink transmission (e.g., a transmission associated with URLLC data) from the UE115 based on the scheduling grant.

Information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

The various illustrative blocks and modules described in connection with the disclosure herein may be implemented or performed with a general purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and the following claims. For example, due to the nature of software, the functions described above may be implemented using software executed by a processor, hardware, firmware, hard-wired, or any combination thereof. Features that perform a function may also be physically located at various positions, including being distributed such that portions of the function are performed at different physical locations. In addition, as used herein, including in the claims, "or" as used in a listing of items (e.g., a listing of items accompanied by a phrase such as "at least one of" or "one or more of") indicates an inclusive listing, such that a listing of, for example, [ A, B or C ] means a or B or C or AB or AC or BC or ABC (i.e., a and B and C).

As will thus far be appreciated by those of ordinary skill in the art and depending on the particular application at hand, many modifications, substitutions, and variations can be made in the materials, apparatus, configurations, and methods of use of the devices of the present disclosure without departing from the spirit and scope of the disclosure. In view of the above, the scope of the present disclosure should not be limited to the particular embodiments illustrated and described herein (as they are merely some examples of the disclosure), but rather should be fully commensurate with the appended claims and their functional equivalents.

The claims (modification of treaty clause 19)

1. A method of wireless communication performed by a User Equipment (UE), comprising:

receiving a Channel State Information (CSI) calculation request from a Base Station (BS);

identifying a first CSI measurement resource based on the CSI calculation request;

determining CSI based on the first CSI measurement resource; and

receiving a CSI report transmission request associated with the first CSI measurement resource from the BS after the CSI calculation request.

2. The method of claim 1, wherein receiving the CSI computation request comprises:

receiving the CSI calculation request including the configuration of the first CSI measurement resource from the BS.

3. The method of claim 1, further comprising:

starting a timer after a first duration has elapsed from an end time of the first CSI measurement resource.

4. The method of claim 3, wherein the end time of the first CSI measurement resource is the end of the last symbol of the CSI measurement resource.

5. The method of claim 3, further comprising:

storing the determined CSI at a memory of the UE; and

transmitting a CSI report including the stored CSI to the BS in response to the CSI report transmission request, based on the CSI report transmission request being received while the timer is in progress.

6. The method of claim 3, further comprising:

refrain from transmitting a CSI report based on the CSI report transmission request being received before the timer is started or after the timer expires.

7. The method of claim 3, further comprising:

receiving, from the BS, an indication of a second CSI measurement resource that is earlier than the first CSI measurement resource; and

transmitting, to the BS, a CSI report including CSI associated with the second CSI measurement resource in response to the CSI report transmission request, based on the CSI report transmission request being received before the timer is started or after the timer expires.

8. The method of claim 3, wherein a duration of the timer is based on information to be included in the CSI based CSI report.

9. The method of claim 1, wherein:

receiving the CSI calculation request includes:

receiving first Downlink Control Information (DCI) including the CSI calculation request; and receiving the CSI report transmission request comprises:

receiving a second DCI including the CSI report transmission request.

10. The method of claim 1, further comprising:

receiving a scheduling grant from the BS after the CSI calculation request and before the CSI report transmission request;

transmitting an uplink data transmission to the BS based on the scheduling grant.

11. The method of claim 10, wherein the uplink data transmission is associated with ultra-reliable low latency communication (URLLC).

12. A method of wireless communication performed by a Base Station (BS), comprising:

transmitting a Channel State Information (CSI) calculation request to a User Equipment (UE);

transmitting a CSI report transmission request associated with a first CSI measurement resource to the UE; and

receiving, from the UE, a CSI report associated with the first CSI measurement resource in response to the CSI report transmission request.

13. The method of claim 12, wherein transmitting the CSI computation request comprises:

transmitting the CSI calculation request including the configuration of the first CSI measurement resource to the UE.

14. The method of claim 12, further comprising:

transmitting, to the UE, a configuration for the first CSI measurement resource.

15. The method of claim 12, wherein transmitting the CSI report transmission request comprises:

transmitting the CSI report transmission request after a first duration has elapsed from an end time of the first CSI measurement resource.

16. The method of claim 15, wherein the end time of the first CSI measurement resource is the end of the last symbol of the CSI measurement resource.

17. The method of claim 12, further comprising:

transmitting, to the UE, a configuration for a duration of a timer for associating the CSI report to the first CSI measurement resource.

18. The method of claim 17, further comprising:

determining a duration of the timer based on information to be included in the CSI based CSI report.

19. The method of claim 12, further comprising:

transmitting, to the UE, an indication of a second CSI measurement resource that is earlier than the first CSI measurement resource; and

receiving, from the UE, a CSI report including CSI associated with the second CSI measurement resource in response to the CSI report transmission request.

20. The method of claim 12, wherein:

transmitting the CSI calculation request includes:

transmitting first Downlink Control Information (DCI) including the CSI calculation request; and transmitting the CSI report transmission request comprises:

transmitting a second DCI including the CSI report transmission request.

21. A User Equipment (UE), comprising:

a transceiver configured to:

receiving a Channel State Information (CSI) calculation request from a Base Station (BS); and

a processor configured to:

determining CSI based on the first CSI measurement resource,

wherein the transceiver is further configured to:

22. The UE of claim 21, wherein the transceiver configured to receive the CSI computation request is further configured to:

23. The UE of claim 21, wherein the transceiver is further configured to:

receiving a configuration for the first CSI measurement resource from the BS.

24. The UE of claim 21, wherein the transceiver is further configured to:

transmitting a CSI report including the CSI to the BS in response to the CSI report transmission request.

25. The UE of claim 21, wherein the processor is further configured to:

26. The UE of claim 21, wherein the end time of the first CSI measurement resource is the end of the last symbol of the CSI measurement resource.

27. The UE of claim 25, further comprising a memory, wherein:

the processor is further configured to:

storing the determined CSI at the memory; and is provided with

The transceiver is further configured to:

28. The UE of claim 25, wherein the processor is further configured to:

29. The UE of claim 25, wherein the transceiver is further configured to:

30. A Base Station (BS), comprising:

a processor; and

a transceiver configured to:

31. The BS of claim 30, wherein the transceiver configured to transmit the CSI computation request is further configured to:

32. The BS of claim 30, wherein the transceiver is further configured to:

33. The BS of claim 30, wherein the transceiver configured to transmit the CSI report transmission request is configured to:

34. The BS of claim 33, wherein the end time of the first CSI measurement resource is the end of the last symbol of the CSI measurement resource.

35. A User Equipment (UE), comprising:

means for receiving a Channel State Information (CSI) calculation request from a Base Station (BS);

means for identifying a first CSI measurement resource based on the CSI calculation request;

means for determining CSI based on the first CSI measurement resource; and

means for receiving a CSI report transmission request associated with the first CSI measurement resource from the BS following the CSI calculation request.

Claims

determining CSI based on the first CSI measurement resource; and

3. The method of claim 1, further comprising:

receiving a configuration for the first CSI measurement resource from the BS.

4. The method of claim 1, further comprising:

5. The method of claim 1, further comprising:

6. The method of claim 5, wherein the end time of the first CSI measurement resource is the end of the last symbol of the CSI measurement resource.

7. The method of claim 1 or claim 5, further comprising:

storing the determined CSI at a memory of the UE; and

8. The method of claim 1 or claim 5, further comprising:

9. The method of claim 1 or claim 5, further comprising:

10. The method of claim 5, wherein the duration of the timer is preconfigured.

11. The method of claim 5, further comprising:

receiving, from the BS, a configuration for a duration of the timer.

12. The method of claim 11, wherein receiving the configuration of the duration of the timer comprises:

receiving the configuration for the duration of the timer from the BS via Radio Resource Control (RRC) signaling.

13. The method of claim 5, wherein a duration of the timer is based on information to be included in the CSI based CSI report.

14. The method of claim 5, wherein a duration of the timer is based on at least one of a codebook type, a number of antenna ports, a Channel Quality Indicator (CQI) type, or a Precoding Matrix Indicator (PMI) type associated with a CSI report.

15. The method of claim 5, further comprising:

storing the determined CSI at a memory of the UE; and

removing the determined CSI from the memory based on expiration of the timer.

16. The method of claim 1, wherein:

receiving the CSI calculation request includes:

receiving a second DCI including the CSI report transmission request.

17. The method of claim 1, wherein the CSI computation request does not indicate any resources for transmitting CSI reports, and wherein the CSI report transmission request indicates resources for transmitting the CSI reports.

18. The method of claim 7, wherein storing the CSI comprises:

storing the determined CSI at the memory of the UE based on the number of stored CSI being below a limit.

19. The method of claim 1, wherein the first CSI measurement resource comprises a channel state information-reference signal (CSI-RS) resource.

20. The method of claim 19, wherein the CSI-RS resource is a non-zero power (NZP) CSI-RS resource.

21. The method of claim 1, wherein the first CSI measurement resource comprises a CSI interference measurement (CSI-IM) resource.

22. The method of claim 1, further comprising:

23. The method of claim 22, wherein the uplink data transmission is associated with ultra-reliable low latency communication (URLLC).

24. A method of wireless communication performed by a Base Station (BS), comprising:

25. The method of claim 24, wherein transmitting the CSI computation request comprises:

26. The method of claim 24, further comprising:

27. The method of claim 24, wherein transmitting the CSI report transmission request comprises:

28. The method of claim 27, wherein the end time of the first CSI measurement resource is the end of the last symbol of the CSI measurement resource.

29. The method of claim 27, further comprising:

determining the first duration based on a CSI computation timeline.

30. The method of claim 24, further comprising:

31. The method of claim 30, wherein transmitting the configuration of the duration of the timer comprises:

transmitting the configuration for the duration of the timer to the UE via Radio Resource Control (RRC) signaling.

32. The method of claim 30, further comprising:

33. The method of claim 30, further comprising:

determining a duration of the timer based on at least one of a codebook type, a number of antenna ports, a Channel Quality Indicator (CQI) type, or a Precoding Matrix Indicator (PMI) type associated with a CSI report.

34. The method of claim 24, further comprising:

35. The method of claim 24, wherein the CSI computation request does not indicate any resources for transmitting CSI reports, and wherein the CSI report transmission request indicates resources for transmitting the CSI reports.

36. The method of claim 24, wherein:

transmitting the CSI calculation request includes:

transmitting a second DCI including the CSI report transmission request.

37. The method of claim 24, wherein the first CSI measurement resource comprises a channel state information-reference signal (CSI-RS) resource.

38. The method of claim 37, wherein the CSI-RS resource is a non-zero power (NZP) CSI-RS resource.

39. The method of claim 24, wherein the first CSI measurement resource comprises a CSI interference measurement (CSI-IM) resource.

40. The method of claim 24, further comprising:

transmitting a scheduling grant to the UE after the CSI calculation request and before the CSI report transmission request;

receiving an uplink data transmission from the UE based on the scheduling grant.

41. The method of claim 40, wherein the uplink data transmission is associated with ultra-reliable low latency communication (URLLC).

42. A User Equipment (UE), comprising:

a transceiver configured to:

a processor configured to:

determining CSI based on the first CSI measurement resource,

wherein the transceiver is further configured to:

43. The UE of claim 42, wherein the transceiver configured to receive the CSI calculation request is further configured to:

44. The UE of claim 42, wherein the transceiver is further configured to:

receiving a configuration for the first CSI measurement resource from the BS.

45. The UE of claim 42, wherein the transceiver is further configured to:

46. The UE of claim 42, wherein the processor is further configured to:

47. The UE of claim 46, wherein an end time of the first CSI measurement resource is an end of a last symbol of the CSI measurement resource.

48. The UE of claim 42 or claim 46, further comprising a memory, wherein:

the processor is further configured to:

storing the determined CSI at the memory; and is

The transceiver is further configured to:

49. The UE of claim 42 or claim 46, wherein the processor is further configured to:

50. The UE of claim 42 or claim 46, wherein the transceiver is further configured to:

51. The UE of claim 46, wherein a duration of the timer is preconfigured.

52. The UE of claim 46, wherein the transceiver is further configured to:

receiving, from the BS, a configuration for a duration of the timer.

53. The UE of claim 52, wherein the transceiver configured to receive the configuration of the duration of the timer is further configured to:

54. The UE of claim 46, wherein the duration of the timer is based on information to be included in the CSI-based CSI report.

55. The UE of claim 46, wherein the duration of the timer is based on at least one of a codebook type, a number of antenna ports, a Channel Quality Indicator (CQI) type, or a Precoding Matrix Indicator (PMI) type associated with the CSI report.

56. The UE of claim 46, further comprising a memory, wherein the processor is further configured to:

storing the determined CSI at the memory; and

removing the determined CSI from the memory based on expiration of the timer.

57. The UE of claim 42, wherein:

the transceiver configured to receive the CSI calculation request is further configured to:

receiving first Downlink Control Information (DCI) including the CSI calculation request; and the transceiver configured to receive the CSI report transmission is further configured to:

receiving a second DCI including the CSI report transmission request.

58. The UE of claim 42, wherein the CSI calculation request does not indicate any resources for transmitting CSI reports, and wherein the CSI report transmission request indicates resources for transmitting the CSI reports.

59. The UE of claim 48, wherein the processor configured to store the CSI is further configured to:

storing the determined CSI at the memory based on the number of stored CSI being below a limit.

60. The UE of claim 42, wherein the first CSI measurement resource comprises a channel state information-reference signal (CSI-RS) resource.

61. The UE of claim 42, wherein the CSI-RS resource is a non-zero power (NZP) CSI-RS resource.

62. The UE of claim 42, wherein the first CSI measurement resource comprises a CSI interference measurement (CSI-IM) resource.

63. The UE of claim 42, wherein the transceiver is further configured to:

64. The UE of claim 63, wherein the uplink data transmission is associated with ultra-reliable low latency communication (URLLC).

65. A Base Station (BS), comprising:

a processor; and

a transceiver configured to:

66. The BS of claim 65, wherein the transceiver configured to transmit the CSI computation request is further configured to:

67. The BS of claim 65, wherein the transceiver is further configured to:

68. The BS of claim 65, wherein the transceiver configured to transmit the CSI report transmission request is configured to:

69. The BS of claim 68, wherein the end time of the first CSI measurement resource is the end of the last symbol of the CSI measurement resource.

70. The BS of claim 68, wherein the processor is configured to:

determining the first duration based on a CSI computation timeline.

71. The BS of claim 65, wherein the transceiver is further configured to:

72. The BS of claim 71, wherein the transceiver configured to transmit the configuration of the duration of the timer is further configured to:

73. The BS of claim 71, wherein the processor is configured to:

determining a duration of the timer based on information to be included in the CSI report based on the CSI.

74. The BS of claim 71, wherein the processor is configured to:

75. The BS of claim 65, wherein the transceiver is further configured to:

76. The BS of claim 65, wherein the CSI computation request does not indicate any resources for transmitting CSI reports, and wherein the CSI report transmission request indicates resources for transmitting the CSI reports.

77. The BS of claim 65, wherein:

the transceiver configured to transmit the CSI calculation request is further configured to:

transmitting first Downlink Control Information (DCI) including the CSI calculation request; and the transceiver configured to transmit the CSI report transmission request is further configured to:

transmitting a second DCI including the CSI report transmission request.

78. The BS of claim 65, wherein the first CSI measurement resource comprises a channel state information-reference signal (CSI-RS) resource.

79. The BS of claim 78, wherein the CSI-RS resource is a non-zero power (NZP) CSI-RS resource.

80. The BS of claim 65, wherein the first CSI measurement resource comprises a CSI interference measurement (CSI-IM) resource.

81. The BS of claim 65, wherein the transceiver is further configured to:

82. The BS of claim 81, wherein the uplink data transmission is associated with ultra-reliable low latency communication (URLLC).

83. A non-transitory computer-readable medium having program code recorded thereon, the program code comprising:

code for causing a User Equipment (UE) to receive a Channel State Information (CSI) calculation request from a Base Station (BS);

code for causing the UE to identify a first CSI measurement resource based on the CSI calculation request;

code for causing the UE to determine CSI based on the first CSI measurement resource; and

code for causing the UE to receive a CSI report transmission request associated with the first CSI measurement resource from the BS following the CSI calculation request.

84. The non-transitory computer-readable medium of claim 83, wherein code for causing the UE to receive the CSI calculation request comprises:

code for causing the UE to receive the CSI calculation request including the configuration of the first CSI measurement resource from the BS.

85. The non-transitory computer-readable medium of claim 83, the program code further comprising:

code for causing the UE to receive a configuration for the first CSI measurement resource from the BS.

86. The non-transitory computer-readable medium of claim 83, the program code further comprising:

code for causing the UE to transmit a CSI report including the CSI to the BS in response to the CSI report transmission request.

87. The non-transitory computer-readable medium of claim 83, the program code further comprising:

code for causing the UE to start a timer after a first duration has elapsed from an end time of the first CSI measurement resource.

88. The non-transitory computer-readable medium of claim 87, wherein the end time of the first CSI measurement resource is an end of a last symbol of the CSI measurement resource.

89. The non-transitory computer-readable medium of claim 83 or claim 87, the program code further comprising:

code for causing the UE to store the determined CSI at a memory of the UE; and

code for causing the UE to transmit a CSI report including the stored CSI to the BS in response to the CSI report transmission request based on the CSI report transmission request being received while the timer is in progress.

90. The non-transitory computer-readable medium of claim 83 or claim 87, the program code further comprising:

code for causing the UE to refrain from transmitting a CSI report based on the CSI report transmission request being received before the timer is started or after the timer expires.

91. The non-transitory computer-readable medium of claim 83 or claim 87, the program code further comprising:

code for causing the UE to receive an indication of a second CSI measurement resource from the BS that is earlier than the first CSI measurement resource; and

code for causing the UE to transmit, based on the CSI report transmission request being received before the timer is started or after the timer expires, a CSI report including CSI associated with the second CSI measurement resource to the BS in response to the CSI report transmission request.

92. The non-transitory computer-readable medium of claim 87, wherein a duration of the timer is preconfigured.

93. The non-transitory computer-readable medium of claim 87, the program code further comprising:

code for causing the UE to receive a configuration for a duration of the timer from the BS.

94. The non-transitory computer-readable medium of claim 93, wherein code for causing the UE to receive the configuration of the duration of the timer further comprises:

code for causing the UE to receive the configuration for the duration of the timer from the BS via Radio Resource Control (RRC) signaling.

95. The non-transitory computer-readable medium of claim 87, wherein a duration of the timer is based on information to be included in the CSI-based report.

96. The non-transitory computer-readable medium of claim 87, wherein a duration of the timer is based on at least one of a codebook type, a number of antenna ports, a Channel Quality Indicator (CQI) type, or a Precoding Matrix Indicator (PMI) type associated with a CSI report.

97. The non-transitory computer-readable medium of claim 87, the program code further comprising:

code for causing the UE to store the determined CSI at a memory of the UE; and

code for causing the UE to remove the determined CSI from the memory based on expiration of the timer.

98. The non-transitory computer-readable medium of claim 83, wherein:

code for causing the UE to receive the CSI calculation request comprises:

code for causing the UE to receive first Downlink Control Information (DCI) including the CSI calculation request; and is

Code for causing the UE to receive the CSI report transmission request comprises:

code for causing the UE to receive a second DCI including the CSI report transmission request.

99. The non-transitory computer-readable medium of claim 83, wherein the CSI calculation request does not indicate any resources for transmitting CSI reports, and wherein the CSI report transmission request indicates resources for transmitting the CSI reports.

100. The non-transitory computer-readable medium of claim 89, wherein the code for causing the UE to store the CSI comprises:

code for causing the UE to store the determined CSI at the memory of the UE based on the number of stored CSI being below a limit.

101. The non-transitory computer-readable medium of claim 83, wherein the first CSI measurement resource comprises a channel state information-reference signal (CSI-RS) resource.

102. The non-transitory computer-readable medium of claim 101, wherein the CSI-RS resource is a non-zero power (NZP) CSI-RS resource.

103. The non-transitory computer-readable medium of claim 83, wherein the first CSI measurement resource comprises a CSI interference measurement (CSI-IM) resource.

104. The non-transitory computer-readable medium of claim 83, the program code further comprising:

code for causing the UE to receive a scheduling grant from the BS after the CSI calculation request and before the CSI report transmission request;

code for causing the UE to transmit an uplink data transmission to the BS based on the scheduling grant.

105. The non-transitory computer-readable medium of claim 104, wherein the uplink data transmission is associated with ultra-reliable low latency communication (URLLC).

106. A non-transitory computer-readable medium having program code recorded thereon, the program code comprising:

code for causing a Base Station (BS) to transmit a Channel State Information (CSI) calculation request to a User Equipment (UE);

code for causing the BS to transmit a CSI report transmission request associated with a first CSI measurement resource to the UE; and

code for causing the BS to receive, from the UE, a CSI report associated with the first CSI measurement resource in response to a CSI report transmission request.

107. The non-transitory computer-readable medium of claim 106, wherein the code for causing the BS to transmit the CSI computation request comprises:

code for causing the BS to transmit the CSI calculation request including the configuration of the first CSI measurement resource to the UE.

108. The non-transitory computer-readable medium of claim 106, the program code further comprising:

code for causing the BS to transmit a configuration for the first CSI measurement resource to the UE.

109. The non-transitory computer-readable medium of claim 106, wherein the code for causing the BS to transmit the CSI report transmission request comprises:

code for causing the BS to transmit the CSI report transmission request after a first duration has elapsed from an end time of the first CSI measurement resource.

110. The non-transitory computer-readable medium of claim 109, wherein the end time of the first CSI measurement resource is an end of a last symbol of the CSI measurement resource.

111. The non-transitory computer-readable medium of claim 109, the program code further comprising:

code for causing the BS to determine the first duration based on a CSI computation timeline.

112. The non-transitory computer-readable medium of claim 106, the program code further comprising:

code for causing the BS to transmit, to the UE, a configuration for a duration of a timer for associating the CSI report to the first CSI measurement resource.

113. The non-transitory computer-readable medium of claim 112, wherein transmitting the configuration of the duration of the timer comprises:

code for causing the BS to transmit the configuration for the duration of the timer to the UE via Radio Resource Control (RRC) signaling.

114. The non-transitory computer-readable medium of claim 112, the program code further comprising:

code for causing the BS to determine a duration of the timer based on information to be included in the CSI report based on the CSI.

115. The non-transitory computer-readable medium of claim 112, the program code further comprising:

code for causing the BS to determine a duration of the timer based on at least one of a codebook type, a number of antenna ports, a Channel Quality Indicator (CQI) type, or a Precoding Matrix Indicator (PMI) type associated with a CSI report.

116. The non-transitory computer-readable medium of claim 106, the program code further comprising:

code for causing the BS to transmit an indication of a second CSI measurement resource that is earlier than the first CSI measurement resource to the UE; and

code for causing the BS to receive, from the UE in response to a CSI report transmission request, a CSI report including CSI associated with the second CSI measurement resource.

117. The non-transitory computer-readable medium of claim 106, wherein the CSI computation request does not indicate any resources for transmitting CSI reports, and wherein the CSI report transmission request indicates resources for transmitting the CSI reports.

118. The non-transitory computer-readable medium of claim 106, wherein:

code for causing the BS to transmit the CSI calculation request includes:

code for causing the BS to transmit first Downlink Control Information (DCI) including the CSI calculation request; and is

Code for causing the BS to transmit the CSI report transmission request includes:

code for causing the BS to transmit a second DCI including the CSI report transmission request.

119. The non-transitory computer-readable medium of claim 106, wherein the first CSI measurement resource comprises a channel state information-reference signal (CSI-RS) resource.

120. The non-transitory computer-readable medium of claim 119, wherein the CSI-RS resource is a non-zero power (NZP) CSI-RS resource.

121. The non-transitory computer-readable medium of claim 106, wherein the first CSI measurement resource comprises a CSI interference measurement (CSI-IM) resource.

122. The non-transitory computer-readable medium of claim 106, the program code further comprising:

code for causing the BS to transmit a scheduling grant to the UE after the CSI calculation request and before the CSI report transmission request;

code for causing the BS to receive an uplink data transmission from the UE based on the scheduling grant.

123. The non-transitory computer-readable medium of claim 122, wherein the uplink data transmission is associated with ultra-reliable low latency communication (URLLC).

124. A User Equipment (UE), comprising:

means for determining CSI based on the first CSI measurement resource; and

125. The UE of claim 124, wherein the means for receiving the CSI computation request comprises:

means for receiving the CSI calculation request including the configuration of the first CSI measurement resource from the BS.

126. The UE of claim 124, further comprising:

means for receiving a configuration for the first CSI measurement resource from the BS.

127. The UE of claim 124, further comprising:

means for transmitting a CSI report including the CSI to the BS in response to the CSI report transmission request.

128. The UE of claim 124, further comprising:

means for starting a timer after a first duration has elapsed from an end time of the first CSI measurement resource.

129. The UE of claim 128, wherein the end time of the first CSI measurement resource is the end of the last symbol of the CSI measurement resource.

130. The UE of claim 124 or claim 128, further comprising:

means for storing the determined CSI at a memory of the UE; and

means for transmitting a CSI report including the stored CSI to the BS in response to the CSI report transmission request based on the CSI report transmission request being received while the timer is in progress.

131. The UE of claim 124 or claim 128, further comprising:

means for refraining from transmitting a CSI report based on the CSI report transmission request being received before the timer is started or after the timer expires.

132. The UE of claim 124 or claim 128, further comprising:

means for receiving, from the BS, an indication of a second CSI measurement resource that is earlier than the first CSI measurement resource; and

means for transmitting, based on the CSI report transmission request being received before the timer is started or after the timer expires, a CSI report including CSI associated with the second CSI measurement resource to the BS in response to the CSI report transmission request.

133. The UE of claim 128, wherein the duration of the timer is preconfigured.

134. The UE of claim 128, further comprising:

means for receiving a configuration for a duration of the timer from the BS.

135. The UE of claim 134, wherein receiving the configuration of the duration of the timer comprises:

means for receiving the configuration for the duration of the timer from the BS via Radio Resource Control (RRC) signaling.

136. The UE of claim 128, wherein the duration of the timer is based on information to be included in the CSI based CSI report.

137. The UE of claim 128, wherein the duration of the timer is based on at least one of a codebook type, a number of antenna ports, a Channel Quality Indicator (CQI) type, or a Precoding Matrix Indicator (PMI) type associated with CSI reporting.

138. The UE of claim 128, further comprising:

means for storing the determined CSI at a memory of the UE; and

means for removing the determined CSI from the memory based on expiration of the timer.

139. The UE of claim 124, wherein:

the means for receiving the CSI calculation request comprises:

means for receiving first Downlink Control Information (DCI) including the CSI calculation request; and is

The apparatus for receiving the CSI report transmission request includes:

means for receiving a second DCI including the CSI report transmission request.

140. The UE of claim 124, wherein the CSI computation request does not indicate any resources for transmitting CSI reports, and wherein the CSI report transmission request indicates resources for transmitting the CSI reports.

141. The UE of claim 130, wherein the means for storing the CSI comprises:

means for storing the determined CSI at the memory of the UE based on the number of stored CSI being below a limit.

142. The UE of claim 124, wherein the first CSI measurement resource comprises a channel state information-reference signal (CSI-RS) resource.

143. The UE of claim 142, wherein the CSI-RS resource is a non-zero power (NZP) CSI-RS resource.

144. The UE of claim 124, wherein the first CSI measurement resource comprises a CSI interference measurement (CSI-IM) resource.

145. The UE of claim 124, further comprising:

means for receiving a scheduling grant from the BS after the CSI calculation request and before the CSI report transmission request;

means for transmitting an uplink data transmission to the BS based on the scheduling grant.

146. The UE of claim 145, wherein the uplink data transmission is associated with ultra-reliable low latency communication (URLLC).

147. A Base Station (BS), comprising:

means for transmitting a Channel State Information (CSI) calculation request to a User Equipment (UE);

means for transmitting a CSI report transmission request associated with a first CSI measurement resource to the UE; and

means for receiving, from the UE, a CSI report associated with the first CSI measurement resource in response to the CSI report transmission request.

148. The BS of claim 147, wherein means for transmitting the CSI computation request comprises:

means for transmitting the CSI calculation request including the configuration of the first CSI measurement resource to the UE.

149. The BS of claim 147, further comprising:

means for transmitting a configuration for the first CSI measurement resource to the UE.

150. The BS of claim 147, wherein means for transmitting the CSI report transmission request comprises:

means for transmitting the CSI report transmission request after a first duration has elapsed from an end time of the first CSI measurement resource.

151. The BS of claim 150, wherein the end time of the first CSI measurement resource is the end of the last symbol of the CSI measurement resource.

152. The BS of claim 150, further comprising:

means for determining the first duration based on a CSI computation timeline.

153. The BS of claim 147, further comprising:

means for transmitting, to the UE, a configuration for a duration of a timer for associating the CSI report to the first CSI measurement resource.

154. The BS of claim 153, wherein the configuration to transmit the duration of the timer comprises:

means for transmitting the configuration for the duration of the timer to the UE via Radio Resource Control (RRC) signaling.

155. The BS of claim 153, further comprising:

means for determining a duration of the timer based on information to be included in the CSI report based on the CSI.

156. The BS of claim 153, further comprising:

means for determining a duration of the timer based on at least one of a codebook type, a number of antenna ports, a Channel Quality Indicator (CQI) type, or a Precoding Matrix Indicator (PMI) type associated with a CSI report.

157. The BS of claim 147, further comprising:

means for transmitting, to the UE, an indication of a second CSI measurement resource that is earlier than the first CSI measurement resource; and

means for receiving, from the UE, a CSI report including CSI associated with the second CSI measurement resource in response to the CSI report transmission request.

158. The BS of claim 147, wherein the CSI computation request does not indicate any resources for transmitting CSI reports, and wherein the CSI report transmission request indicates resources for transmitting the CSI reports.

159. The BS of claim 147, wherein:

the means for transmitting the CSI calculation request comprises:

means for transmitting first Downlink Control Information (DCI) including the CSI calculation request; and is provided with

The means for transmitting the CSI report transmission request comprises:

means for transmitting a second DCI including the CSI report transmission request.

160. The BS of claim 147, wherein the first CSI measurement resource comprises a channel state information-reference signal (CSI-RS) resource.

161. The BS of claim 160, wherein the CSI-RS resource is a non-zero power (NZP) CSI-RS resource.

162. The BS of claim 147, wherein the first CSI measurement resource comprises a CSI interference measurement (CSI-IM) resource.

163. The BS of claim 147, further comprising:

means for transmitting a scheduling grant to the UE after the CSI calculation request and before the CSI report transmission request;

means for receiving an uplink data transmission from the UE based on the scheduling grant.

164. The BS of claim 163, wherein the uplink data transmission is associated with ultra-reliable low latency communication (URLLC).