Channel status information triggering and reporting

Abstract

The method relates to a wireless communication system 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 calculation 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

Technical Field

[0001] 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 obtain channel state information from a user equipment (e.g., without unnecessarily blocking other uplink scheduling during channel state information calculation).

[0002] introduction

[0003] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, etc. These systems may be capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). A wireless multiple-access communication system may include several base stations (BSs), each of which simultaneously supports communication for multiple communication devices (e.g., user equipment (UE)).

[0004] In order to meet the growing demand for extended mobile broadband connectivity, wireless communication technology is progressing from long term evolution (LTE) technology to next generation 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, such as from low frequency bands below about 1 gigahertz (GHz) and mid-frequency bands from about 1 GHz to about 6 GHz, to high frequency bands, such as millimeter wave (mmWave) bands. 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 decoding technology may also bring benefits.

[0005] A brief overview of some examples

[0006] The following summarizes some aspects of the present disclosure to provide a basic understanding of the technology discussed. This summary is not an exhaustive overview of all conceived features of the present disclosure, and is neither intended to identify the key or decisive elements of all aspects of the present disclosure, nor to attempt to define the scope of any or all aspects of the present disclosure. Its only purpose is to give some concepts of one or more aspects of the present disclosure in an overview form as a prelude to a more detailed description given later.

[0007] Some aspects of the present disclosure implement and provide mechanisms and techniques that enable a UE to determine CSI at the request of a BS and provide it to the BS. For example, when the BS requests CSI from the UE, the UE can provide a CSI report without the BS allocating and scheduling uplink resources for CSI report transmission. This allows 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 the CSI report. The BS may instead divide the process into discrete steps instead of simultaneously triggering the generation of a CSI report and scheduling UL resources for transmitting the CSI report in an uplink (UL) grant. These steps may include triggering the generation of a CSI report by sending a CSI calculation request to the UE and requesting the transmission of a CSI report by sending a CSI report transmission request to the UE. The CSI calculation request may cause the UE to determine the CSI, but may not schedule any UL resources for transmitting the CSI report. The UE may store the CSI in anticipation of receiving 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 (eg, resources in a physical uplink shared channel) specified by the BS.

[0008] For example, in one aspect of the present disclosure, a wireless communication method 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 calculation 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.

[0009] In another example, aspects may include a wireless communication method 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 receipt or transmission of the CSI report may be preceded by a CSI report request. The method may also optionally include receiving a CSI calculation request and / or identifying a first CSI measurement resource. The first CSI measurement resource may be based on the CSI calculation request.

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

[0011] In an additional aspect of the present disclosure, a UE includes a processor and a transceiver. The transceiver is configured to receive a CSI calculation request from a BS. The processor is configured to identify a first CSI measurement resource based on the CSI calculation 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 calculation request.

[0012] In an additional aspect of the present disclosure, a BS includes a processor and a transceiver. The transceiver is configured to transmit a CSI calculation request to a UE. The transceiver is further configured to transmit a CSI report transmission request associated with a 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.

[0013] In an additional aspect of the present disclosure, a non-transitory computer-readable medium having program code recorded thereon is disclosed. The program code includes code for causing a UE to receive a CSI calculation request from a BS. The program code further includes code for causing the UE to identify a first CSI measurement resource based on the CSI calculation 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.

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

[0015] In an additional aspect of the present disclosure, a UE includes means for receiving a CSI calculation request from a BS. The UE further includes means for identifying a first CSI measurement resource based on the CSI calculation 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 calculation request.

[0016] In an additional aspect of the present disclosure, a BS includes a device for transmitting a CSI calculation request to a UE. The BS further includes a device for transmitting a CSI report transmission request associated with a first CSI measurement resource to the UE. The BS further includes a device for receiving a CSI report associated with the first CSI measurement resource from the UE in response to the CSI report transmission request.

[0017] After studying the following description of specific exemplary embodiments in conjunction with the accompanying drawings, other aspects, features and embodiments will be apparent to those of ordinary skill in the art. Although each feature may be discussed below for certain embodiments and accompanying drawings, all embodiments may include one or more of the advantageous features discussed herein. In other words, although one or more embodiments may be discussed to have certain advantageous features, one or more such features may also be used according to the various embodiments discussed herein. In a similar manner, although exemplary embodiments may be discussed below as device, system or method embodiments, it should be appreciated that such exemplary embodiments may be implemented in various devices, systems, and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1

[0013] A wireless communication network in accordance with some aspects of the present disclosure is illustrated.

[0020] Figure 2A Channel state information (CSI) request and resource allocation methods according to some aspects of the present disclosure are illustrated.

[0021] Figure 2B Resource allocation methods according to some aspects of the present disclosure are illustrated.

[0022] Figure 3 CSI request and resource allocation methods according to some aspects of the present disclosure are illustrated.

[0023] Figure 4 is an exemplary sequence diagram illustrating a communication sequence according to some aspects of the present disclosure.

[0024] Figure 5 is a flow chart of wireless communications according to some aspects of the present disclosure.

[0025] Figure 6 is a block diagram of an exemplary base station (BS) according to some aspects of the present disclosure.

[0026] Figure 7 is a block diagram of an exemplary user equipment (UE) according to some aspects of the present disclosure.

[0027] Figure 8 is a flow chart of wireless communications according to some aspects of the present disclosure.

[0028] Fig. 9 is a flow chart of wireless communications according to some aspects of the present disclosure.

[0029] Detailed Description

[0030] The detailed description set forth below in conjunction with the accompanying 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. This detailed description includes specific details in order to provide a thorough understanding of the various concepts. However, it will be apparent to those 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 to avoid obscuring such concepts.

[0031] A base station (BS) may request channel state information (CSI) from a UE to determine the current state of a channel used for communication between the BS and the UE based on CSI measurement resources. The CSI measurement resources may be, for example, non-zero power channel state information reference signals (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 associated CSI measurement resources and schedule uplink resources for the UE to transmit the resulting CSI report. Uplink scheduling is typically scheduled (transmitted before the actual scheduling time). Because the CSI calculation at the UE may take a lot of time, the BS may account for the CSI calculation time and transmit DCI (including CSI measurement and reporting triggers) even earlier than the CSI report scheduling resources (e.g., up to about 11 time slots in advance, depending on the subcarrier spacing). In this way, there may be a considerable duration between the time when the CSI request is transmitted to the UE and the CSI report scheduling resources. Since uplink scheduling is expected to be in order, the BS may not schedule the UE for another uplink transmission between the time the UE receives a CSI request and the time the UE transmits a CSI report. This effectively gives CSI data a higher priority than other types of data, making Ultra-Reliable Low Latency Communication (URLLC) difficult for the UE.

[0032] The present disclosure generally relates to wireless communication systems (also referred to as wireless communication networks). In various embodiments, various techniques and devices 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.

[0033] OFDMA network can realize 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 Universal Mobile Telecommunications System (UMTS). Specifically, Long Term Evolution (LTE) is a version of UMTS that uses E-UTRA. UTRA, E-UTRA, GSM, UMTS and LTE are described in documents provided by an organization named "3rd Generation Partnership Project" (3GPP), while cdma2000 is described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). These various radio technologies and standards are known or under development. For example, the 3rd Generation Partnership Project (3GPP) is a collaboration between various telecommunications association groups that aims to define a globally applicable third generation (3G) mobile phone specification. 3GPP Long Term Evolution (LTE) is a 3GPP project aimed at improving the UMTS mobile phone standard. 3GPP may define specifications for next generation mobile networks, mobile systems, and mobile devices. The present disclosure focuses on the evolution of wireless technologies from LTE, 4G, 5G, NR and beyond with shared access to wireless spectrum between networks using a set of new and different radio access technologies or radio air interfaces.

[0034] Specifically, 5G networks envision diverse deployments, diverse spectrum, and diverse services and devices that can 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 also considered. 5G NR will be able to scale to provide coverage for: (1) ultra-high density (e.g., about 1M nodes / km) 2 ), ultra-low complexity (e.g., about tens of bits / second), ultra-low energy (e.g., about 10+ years of battery life), and deep coverage capable of reaching challenging locations; (2) including mission-critical control 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 users with a wide range of mobility or lack of mobility; and (3) with enhanced mobile broadband, including extremely high capacity (e.g., about 10 Tbps / km 2 ), extreme data rates (e.g., multi-Gbps rates, 100+Mbps user experience rates), and deep cognition with advanced discovery and optimization.

[0035] The 5G NR communication system can be implemented to use an optimized OFDM-based waveform with a scalable parameter set and transmission time interval (TTI). Additional features may also include a common, flexible framework to use a dynamic low-latency time time division duplex (TDD) / frequency division duplex (FDD) design to efficiently multiplex services and features; and utilize advanced wireless technologies such as massive multiple input multiple output (MIMO), robust millimeter wave (mmWave) transmission, advanced channel decoding, and device-centric mobility. The scalability of parameter design in 5G NR (and the scaling of subcarrier spacing (SCS)) can efficiently solve the operation of diversified services across diverse spectrums and diverse deployments. For example, in various outdoor and macro coverage deployments less than 3GHz FDD / TDD implementations, the subcarrier spacing can occur at 15kHz, such as on bandwidths (BW) such as 5, 10, and 20MHz. For other various outdoor and small cell coverage deployments of TDD greater than 3GHz, the subcarrier spacing can occur at 30kHz on 80 / 100MHzBW. For various other indoor broadband implementations, subcarrier spacing may occur at 60kHz over 160MHz BW using TDD over the unlicensed portion of the 5GHz band. Finally, for various deployments transmitting using the mmWave component with TDD at 28GHz, subcarrier spacing may occur at 120kHz over 500MHz BW.

[0036] The scalable parameter design of 5G NR facilitates scalable TTI to meet diverse latency and quality of service (QoS) requirements. For example, shorter TTIs can be used for low latency and high reliability, while longer TTIs can be used for higher spectral efficiency. Efficient multiplexing of long TTIs and short TTIs allows transmissions to start on symbol boundaries. 5G NR also contemplates a self-contained integrated subframe design with UL / downlink scheduling information, data, and acknowledgment in the same subframe. The self-contained integrated subframe supports communications in unlicensed or contention-based shared spectrum, and supports 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.

[0037] Various other aspects and features of the present disclosure are further described below. It should be apparent that the teachings herein can be embodied in a variety of forms, and any specific structure, function, or both disclosed herein are representative and non-restrictive. Based on the teachings herein, it should be appreciated by those of ordinary skill in the art that the aspects disclosed herein can be implemented independently of any other aspects and two or more of these aspects can be combined in various ways. For example, any number of aspects set forth herein can be used to implement a device or practice a method. In addition, other structures, functionality, or structures and functionality that are supplementary to or different from one or more aspects set forth herein can be used to implement such a device or practice such a method. For example, the method can be implemented as a part of a system, device, device, and / or as an instruction stored on a computer-readable medium for execution on a processor or computer. Not only that, an aspect can include at least one element of a claim.

[0038] A base station (BS) in 5G NR may request channel state information from a user equipment (UE). The BS may use CSI to determine the operating condition or state of a channel to assist communication between the BS and the UE and / or obtain interference measurements. The BS may request the UE to perform channel estimation and / or interference measurements 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 the number of time slots between the time the grant is transmitted and the time the UE is scheduled to transmit a CSI report 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 the scheduling offset of a UL grant not associated with an A-CSI trigger to account for the time it takes the UE to prepare the requested CSI report.

[0039] 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 inefficiency, CSI data is actually given higher priority than other types of uplink data, which may be problematic for ultra-reliable latency communications (URLLC). Therefore, the various aspects and embodiments described herein provide techniques that allow and enable the BS to request CSI without the BS allocating and scheduling 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 a CSI report but before scheduling the CSI, thereby satisfying an ordered PUSCH transmission scheduling report.

[0040] The present disclosure provides a technology for UE to determine and provide CSI to BS. In some scenarios, UE may provide CSI to the BS at the request of BS. UE's provisioning of CSI may be performed when BS does not reserve uplink resources for CSI reporting when it requests the CSI. This allows UE to transmit other types of uplink data (e.g., URLLC data) after receiving a request for CSI but before transmitting CSI report. BS may instead divide the process into discrete steps, rather than triggering the generation of CSI report and scheduling UL resources for transmitting CSI report in UL grant at the same time. These steps may include triggering the generation of CSI report by sending CSI calculation request to UE and requesting the transmission of CSI report by sending CSI report transmission request to UE. BS may transmit CSI calculation request as downlink control information (DCI) message (referred to as calculating DCI only) in PDCCH. Additionally or alternatively, BS may transmit CSI report transmission request as part of DCI message (referred to as reporting DCI only) in PDCCH at a later time. Computing only the DCI may trigger the UE to generate a CSI report. However, in some instances, doing so may not schedule any UL resources for the transmission of the CSI report. The UE may generate a CSI report and store it in anticipation of receiving a report-only DCI. Once the UE receives a report-only DCI indicating which CSI report to transmit, the UE may transmit the stored CSI report using the UL resources specified in the report-only DCI (e.g., resources in a physical uplink shared channel (PUSCH)). In one example, the report-only DCI includes a CSI request field that includes a value mapped to a CSI triggering state. The CSI triggering state may be associated with one or more CSI reporting configurations. Each CSI reporting configuration may reference a CSI measurement resource that the BS is requesting for reporting.

[0041] For example, according to various aspects of the present disclosure, a BS may request a UE to calculate CSI by transmitting a first CSI calculation request to the UE (e.g., as a DCI message in a PDCCH). The first CSI calculation request may indicate one or more CSI measurement resources on which the UE may measure the CSI, but may not indicate any resources for transmitting CSI reports by the UE. Based on the first CSI calculation request, the UE may then identify CSI measurement resources, which may be, for example, channel state information reference signal (CSI-RS) resources and / or channel state information interference measurement (CSI-IM) resources. Based on the (all) CSI measurement resources, the UE may perform channel estimation and / or interference measurement, but the UE may store the resulting CSI in a memory within the UE instead of immediately transmitting the results to the BS. During the CSI calculation 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 uplink data based on the scheduling grant. At a later time, the BS may transmit a first CSI report transmission request to the UE (e.g., as a DCI message on the PDCCH) 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 to transmit the report.

[0042] In some aspects, the UE may maintain multiple CSIs corresponding to different CSI calculation requests and CSI measurement resources stored in its memory. For example, at a time after transmitting a 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 the memory without removing the CSI corresponding to the first CSI calculation request. The UE may store and maintain multiple CSIs in its memory, which may be useful, for example, when the gap between the CSI calculation 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 on the number of CSIs that the UE can store, and the UE may delete the stored CSI or not store the newly calculated CSI if the number of CSIs in the memory exceeds the limit.

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

[0044] Aspects may include further timing-related features. For example, the UE may start (or reset) a timer after a certain period (or duration) has elapsed from the 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 can determine the CSI. The timer duration may be preconfigured (e.g., preconfigured to a value defined in a third generation partnership project (3GPP) specification). Additionally or alternatively, the timer value may be semi-statically configured by the BS (e.g., via RRC signaling) or dynamically indicated by the BS (e.g., as part of a CSI calculation request or via a MAC CE). The timer duration may be based on information that the UE is to include in the CSI report (e.g., CSI report content) (e.g., the timer duration may be larger when the UE is to include more information or more complex information in the CSI report).

[0045] The timer duration may also be based on the codebook type, number of antenna ports, channel quality indicator (CQI) type, and / or precoding matrix indicator (PMI) type associated with the CSI report. In general, the CSI report content may vary depending on the codebook type to be used for CSI calculation, the number of antenna ports associated with the CSI measurement resources, and / or the type of CQI and / or PMI to be reported. In other words, the CSI calculation time may vary depending on the CSI report content.

[0046] The time period during which the timer runs may correspond to the time period during which the current CSI report should be transmitted to the BS in response to receiving the CSI report transmission request. For example, if the CSI report transmission request arrives while the timer is running, the UE may transmit the most recently calculated CSI in the CSI report. However, if the UE receives the CSI report transmission request before the timer is started, the UE may not yet 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 the CSI transmission request is received before the timer is started or after the timer has expired—the UE may transmit CSI that may not be current (e.g., the most recently stored—now stale—CSI, or previously stored CSI based on an older CSI calculation request and corresponding CSI measurement resource) or placeholder data (which does not have useful CSI) in the CSI report. The transmission of stale CSI or useless CSI is to satisfy the CSI report transmission request because the UE will transmit as scheduled by the BS.

[0047] Transmitting older 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) acknowledgment. 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 may determine whether the CSI report is valid. In general, the BS will not cause the UE to make a CSI report transmission request outside the period when the UE's report timer is running. Alternatively, the UE may completely ignore the CSI report transmission request (i.e., refrain from transmitting the CSI report), for example, when the CSI transmission request only includes a grant for transmitting the CSI report. In some aspects, the UE may remove the stored CSI from the memory based on the expiration of the timer.

[0048] In some aspects, resource occupancy reporting rules may be updated to reflect aspects of the present disclosure. 5G NR provides rules for UEs to determine resources (e.g., the maximum number of central processing units (CPUs) and / or the maximum number of synchronous memory resources) for implementing two-step CSI triggering (with separate CSI calculation requests and CSI report transmission requests) and reporting its capabilities associated with the two-step CSI triggering. According to the present disclosure, CPU resources are occupied for a duration of Z symbols from the end of the last symbol of the PDCCH (or control resource set (CORESET)) on which a CSI calculation request (e.g., only DCI is calculated), where Z is the minimum gap between the time when the CSI calculation request is transmitted and the time when the UE can provide a CSI report. In other words, Z symbols are the amount of time used to complete the CSI calculation. The value of Z may vary depending on the capabilities of the UE. The UE may determine the value of Z based on the CPU resource occupancy rules and report the value of Z to the BS. For example, a UE with high processing power may report a smaller Z value than a UE with low processing power. Memory resources may be occupied for Z+T from the end of the last symbol of the PDCCH (or control resource set (CORESET)) on which a CSI calculation request (e.g., only DCI calculation) is carried exp duration of code elements, where Z is defined as above for CPU occupancy and T exp is the duration of the window during which the UE waits for a CSI report transmission request (i.e., the timer duration discussed above, in which the UE can provide the BS with the most recently calculated CSI). The memory resources occupied by CSI operations become free upon expiration of this window or after the UE transmits a CSI report to the BS (in response to receiving a CSI request report transmission during this window).

[0049] Various aspects of the present disclosure may provide many benefits. For example, various aspects of the present disclosure enable the BS to schedule the UE to transmit uplink data in the 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 for reporting CSI. This may enable the UE to better communicate URLLC data (e.g., with lower latency) because by locking the UE to determine and transmit CSI without interruption, CSI data is no longer de facto prioritized.

[0050] Although various aspects and embodiments are described in this application by explanation of some examples, it will be understood by those skilled in the art that additional implementations and use cases can be generated in many different arrangements and scenarios. The innovation described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, each embodiment and / or use can be generated via an integrated chip embodiment and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment, AI-enabled devices, etc.). Although some examples may or may not be specifically for each use case or application, the wide applicability of the described innovation may occur. The scope of each implementation can range from chip-level or module 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 innovation. In some practical environments, the equipment incorporating the various aspects and features described may also necessarily include additional components and features for implementing and practicing the claimed and described embodiments. For example, the transmission and reception of wireless signals necessarily include several components for analog and digital purposes (e.g., hardware components, including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / 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, etc., of various sizes, shapes, and configurations.

[0051] Figure 1 A wireless communication network 100 according to some aspects of the present disclosure is illustrated. The network 100 may be a 5G network. The network 100 includes several base stations (BSs) 105 (respectively labeled 105a, 105b, 105c, 105d, 105e, and 105f) and other network entities. The BS 105 may be a station that communicates with a UE 115, and may also be referred to as an evolved B node (eNB), a next generation eNB (gNB), an access point, and the like. Each BS 105 may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" may refer to the particular geographic coverage area of ​​the BS 105 and / or the BS subsystem that serves the coverage area, depending on the context in which the term is used.

[0052] BS105 may provide communication coverage for macro cells or small cells (such as pico cells or femto cells), and / or other types of cells. Macro cells generally cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UEs that have service subscriptions with a network provider. Small cells (such as pico cells) generally cover a relatively small geographic area and may allow unrestricted access by UEs that have service subscriptions with a network provider. Small cells (such as femto cells) generally also cover a relatively small geographic area (e.g., a residence) and, in addition to unrestricted access, may provide restricted access to UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs of users in the residence, etc.). A BS for a macro cell may be referred to as a macro BS. A BS for a small cell may be referred to as a small cell BS, a pico BS, a femto BS, or a home BS. In Figure 1 In the example shown in , BS105d and 105e can be conventional macro BSs, while BS105a-105c can be macro BSs enabled with one of three-dimensional (3D), full-dimensional (FD), or massive MIMO. BS105a-105c can utilize its higher dimensional MIMO capabilities to utilize 3D beamforming in both elevation and azimuth beamforming to increase coverage and capacity. BS105f can be a small cell BS, which can be a home node or a portable access point. BS105 can support one or more (e.g., two, three, four, etc.) cellular cells.

[0053] Network 100 may support synchronous or asynchronous operation. For synchronous operation, each BS may have similar frame timing, and transmissions from different BSs may be approximately aligned in time. For asynchronous operation, each BS may have different frame timing, and transmissions from different BSs may not be aligned in time.

[0054] Each UE 115 may be dispersed throughout the wireless network 100, and each UE 115 may be stationary or mobile. Each UE may take a variety of forms and form factor ranges. UE 115 may also be referred to as a terminal, a mobile station, a subscriber unit, a station, and the like. UE 115 may be a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a cordless phone, a wireless local loop (WLL) station, and the like. In one aspect, UE 115 may be a device including a universal integrated circuit card (UICC). On the other hand, UE may be a device that does not include a UICC. In some aspects, UE 115 that does not include a UICC may also be referred to as an IoT device or an Internet of Everything (IoE) device. UE 115a-115d is an example of a mobile smart phone type device that accesses the network 100. UE 115 may also be a machine specifically configured for connected communications (including machine type communications (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT), etc.). UE 115e-115h are examples of various machines configured for communication that access network 100. UE 115i-115k are examples of vehicles equipped with wireless communication devices configured for communication that access network 100. UE 115 may be able to communicate with any type of BS (whether macro BS, small cell, etc.). Figure 1 In the figure, the lightning beam (e.g., communication link) indicates wireless transmission between UE 115 and serving BS 105, desired transmission between BSs 105, backhaul transmission between BSs, or sidelink transmission between UEs 115, and serving BS 105 is a BS designated to serve UE 115 on downlink (DL) and / or uplink (UL).

[0055] In operation, BSs 105a-105c may use 3D beamforming and coordinated spatial techniques such as coordinated multipoint (CoMP) or multi-connectivity to serve UEs 115a and 115b. Macro BS 105d may perform backhaul communications with BSs 105a-105c, and small cell BS 105f. Macro BS 105d may also transmit multicast services subscribed to and received by UEs 115c and 115d. Such multicast services may include mobile TV 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.

[0056] The BSs 105 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 of the BSs 105 (e.g., which may be examples of gNBs or access node controllers (ANCs)) may interface with the core network via a backhaul link (e.g., NG-C, NG-U, etc.) and may perform radio configuration and scheduling for communication with the UE 115. In various examples, the BSs 105 may communicate with each other directly or indirectly (e.g., through the core network) over a backhaul link (e.g., X1, X2, etc.), which may be a wired or wireless communication link.

[0057] The network 100 may also support mission-critical communications with ultra-reliable and redundant links for mission-critical devices, such as UE 115e, which may be a drone. The redundant communication links with UE 115e may include links from macro BSs 105d and 105e, and links from small cell BS 105f. Other machine-type devices, such as UE 115f (e.g., a thermometer), UE 115g (e.g., a smart meter), and UE 115h (e.g., a wearable device), may communicate directly with a BS, such as small cell BS 105f and macro BS 105e, through the network 100, or in a multi-step configuration by communicating with another user device that relays its information to the network, such as UE 115f communicating temperature measurement information to smart meter UE 115g, which is then reported to the network through small cell BS 105f. The network 100 may also provide additional network efficiency through dynamic, low latency TDD / FDD communications, such as V2V, V2X, C-V2X communications between UE 115i, 115j or 115k and other UEs 115, and / or vehicle-to-infrastructure (V2I) communications between UE 115i, 115j or 115k and BS 105.

[0058] In some implementations, the network 100 communicates using an OFDM-based waveform. An OFDM-based system may divide the system BW into multiple (K) orthogonal subcarriers, which are also commonly referred to as subcarriers, frequency modulations, frequency slots, etc. 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 depend on the system BW. The system BW may also be divided into subbands. In other instances, the subcarrier spacing and / or the duration of the TTI may be scalable.

[0059] In some aspects, 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 network 100. DL refers to the transmission direction from BS105 to UE 115, and UL refers to the transmission direction from UE 115 to BS105. The communication may take the form of a radio frame. A radio frame may be divided into a plurality of subframes or time slots, such as about 10. Each time 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 a UL subframe in a 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., a DL subframe) may be used for DL ​​transmission, and another subset of subframes in a radio frame (e.g., a UL subframe) may be used for UL transmission.

[0060] DL subframes and UL subframes may be further divided into several regions. For example, each DL or UL subframe may have a predefined region for the transmission of reference signals, control information, and data. Reference signals are predetermined signals that facilitate communication between BS105 and UE 115. For example, reference signals may have a specific pilot pattern or structure, wherein pilot tones may span an operating BW or frequency band, and each pilot tone may be positioned at a predefined time and a predefined frequency. For example, BS105 may transmit a reference signal (CRS) and / or a channel state information-reference signal (CSI-RS) that varies from cell to cell to enable UE 115 to estimate a DL channel. Similarly, UE 115 may transmit a sounding reference signal (SRS) to enable BS105 to estimate an UL channel. Control information may include resource assignments and protocol controls. Data may include protocol data and / or operational data. In some aspects, BS105 and UE 115 may communicate using self-contained subframes. Self-contained subframes may include a portion for DL ​​communication and a portion for UL communication. A self-contained subframe may be DL-centric or UL-centric. A DL-centric subframe may include a duration for DL ​​communication that is longer than a duration for UL communication. A UL-centric subframe may include a duration for UL communication that is longer than a duration for DL ​​communication.

[0061] In some aspects, network 100 may be an NR network deployed on a licensed spectrum. BS 105 may transmit synchronization signals (e.g., including a primary synchronization signal (PSS) and a secondary synchronization signal (SSS)) in network 100 to facilitate synchronization. BS 105 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 instances, BS 105 may broadcast PSS, SSS, and / or MIB in the form of a synchronization signal block (SSB) on a physical broadcast channel (PBCH), and may broadcast RMSI and / or OSI on a physical downlink shared channel (PDSCH).

[0062] In some aspects, a UE 115 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 UE 115 may then receive the SSS. The SSS may enable radio frame synchronization and may provide a cell identity value that may be combined with the 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.

[0063] After receiving the PSS and SSS, the UE 115 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, the UE 115 may receive the 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.

[0064] After obtaining the MIB, RMSI and / or OSI, the UE 115 may perform a random access procedure to establish a connection with the BS 105. The random access procedure (or RACH procedure) may be a single-step or multi-step process. In some examples, the random access procedure may be a four-step random access procedure. For example, the UE 115 may transmit a random access preamble, and the BS 105 may respond with a random access response. The random access response (RAR) may include a detected random access preamble identifier (ID) corresponding to the random access preamble, timing advance (TA) information, UL grant, temporary cell radio network temporary identifier (C-RNTI), and / or a backoff indicator. Upon receiving the random access response, the UE 115 may transmit a connection request to the BS 105 and the BS 105 may respond with a connection response. The connection response may indicate a contention resolution method. 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 UE 115 may transmit a random access preamble and a connection request in a single transmission, and the BS 105 may respond by transmitting a random access response and a connection response in a single transmission.

[0065] After establishing the connection, UE 115 and BS 105 can enter a normal operation phase, wherein operation data can be exchanged. For example, BS 105 can schedule UE 115 for UL and / or DL ​​communication. BS 105 can transmit UL and / or DL ​​scheduling grants to UE 115 via PDCCH. Scheduling grants can be transmitted in the form of DL control information (DCI). BS 105 can transmit DL communication signals (e.g., carrying data) to UE 115 via PDSCH according to the DL scheduling grant. UE 115 can transmit UL communication signals to BS 105 via PUSCH and / or PUCCH according to the UL scheduling grant.

[0066] 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 parts). The BS 105 may dynamically assign the UE 115 to operate on a certain BWP (e.g., a certain part of the system BW). The assigned BWP may be referred to as an active BWP. The UE 115 may monitor the active BWP to find signaling information from the BS 105. The BS 105 may schedule the UE 115 to perform UL or DL ​​communications in the active BWP. In some aspects, the BS 105 may assign a BWP pair within a CC to the UE 115 for UL and DL communications. For example, the BWP pair may include a BWP for UL communication and a BWP for DL ​​communication.

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

[0068] Figure 2AA CSI request and resource allocation method 200A according to some aspects of the present disclosure is illustrated. When using an aperiodic CSI request to request CSI from a UE 115, the BS 105 may include an A-CSI trigger 202 (e.g., as part of a DCI) in a PDCCH transmission during time slot S0 212. In an example, the DCI may include a CSI request field that includes 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 reference a CSI measurement resource that the BS 105 is requesting for a CSI report. An uplink grant may be included along with the A-CSI trigger 202 to indicate which UL resources 206 the UE 115 is to use in the PUSCH when transmitting a CSI report to the BS 105. The BS may indicate that the reported CSI may be based on the 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 resources are a set of resource elements (spanning a number of subcarriers in frequency and a number of symbols in time) in which the UE 115 can perform measurements. When the CSI measurement resources 204 are CSI-RS or NZP CSI-RS resources, the BS 105 can transmit the CSI-RS in the CSI measurement resources 204 for the UE 115 to determine the channel response. When the CSI measurement resources 204 are CSI-IM resources, the UE 115 can measure interference from the CSI measurement resources 204. The BS can indicate (e.g., as part of an uplink grant) a scheduling offset 208 (which can be referred to as Y) that indicates the gap between the time when the A-CSI trigger is transmitted and the time when the CSI report should be transmitted on the PUSCH. The BS 105 may have to reserve the UL resources 206 several slots in advance (e.g., before transmitting the A-CSI trigger 202 in slot S0 212), and the BS 105 is expected to perform ordered uplink scheduling. As a result, from the end time of the CSI measurement resource 204 to the time when the UE 115 transmits the CSI report on the UL resource 206, the BS 105 shall not schedule the UE 115 to transmit any additional UL data during the gap time. The gap between the CSI measurement resource 204 and the transmission of the CSI report (e.g., PUSCH transmission) on the UL resource 206 may be referred to as Y'. For example, the BS 105 shall not schedule the UE 115 to transmit any additional UL data in the remainder of the time slot S0 212 or in the time slot S1 214, the time slot S2 216, the time slot S3 218, or the time slot S4 220. Thus, the UE 115 shall not transmit other types of UL data until after the CSI report is transmitted during the time slot S5 222. As a result, the CSI data is actually given a higher priority than other types of data, which may be problematic for the UE 115 participating in URLLC communication.

[0069] Figure 2B A resource allocation method 200B according to some aspects of the present disclosure is illustrated. Figure 2A , the UL grant 250—without A-CSI trigger—is included in the PDCCH transmission. Since the UE 115 is not occupied to determine CSI, the UE 115 can use the UL resources 252 to transmit data (e.g., on the PUSCH) sooner after the UL grant 250 compared to the method 200A. Here, the UE 115 can transmit data on the UL resources 252 after a period N2, which is defined as the gap 254 between the end of the PDCCH transmission (i.e., the UL grant 250) and the start of the scheduled UL resources 252 (e.g., PUSCH). In this example, the UL grant 250 is received in time slot S0 260, and the UE can transmit UL data in the next time slot, time slot S1 262.

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

[0071] SCS(kHz) <![CDATA[Z2 (symbol)]]> 15 40 30 72 60 141 120 152

[0072] Table 1

[0073] For low latency CSI (eg, wideband type 1 CSI with up to 4 antenna ports), Z may be set to a smaller value than Z2, but may still be quite large (eg, long duration).

[0074] If the A-CSI trigger is not included along with the UL grant, the minimum scheduling offset depends on the SCS and may be approximately N2, as illustrated below in Table 2 for various SCS values.

[0075] SCS(kHz) <![CDATA[N2 (symbol)]]> 15 10 30 12 60 23 120 36

[0076] Table 2

[0077] In some aspects, the CSI calculation time Z or Z2 and the UE PUSCH preparation time (in the absence of A-CSI triggering) N2 can be as described in the following document: 3GPP document TS 38.214 Release 16, April 2020, entitled "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for data", Sections 5.4 and 6.4 ("3GPP TS 38.214 document"), which is incorporated herein by reference.

[0078] The much larger timeline for method 200A (when A-CSI triggering is included along with UL grant) compared to method 200B (when A-CSI triggering is not included) creates several scheduling issues. For example, BS 105 may be interested in acquiring CSI for a large number of antenna ports and / or sub-band CQI and PMI, which will be high latency CSI following the longer Z2 timeline described above. And PUSCH resources for CSI transmission need to be reserved several slots in advance, such as in Figure 2A (e.g., 6 time slots in advance when an SCS value of 30 kHz is used) and as illustrated in Table 1. As a result, UL data shall not be transmitted in any reserved time slot. 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 the A-CSI trigger are transmitted and the CSI report is scheduled. Therefore, if the UE 115 has URLLC data ready for transmission, the transmission of the URLLC data will be delayed, which may be undesirable because the latency requirements for the URLLC transmission may not be met. The scheduling problem may be due to both the time it takes the UE 115 to determine the requested CSI, and the joint signaling of the A-CSI trigger and UL grant in a single PDCCH as in method 200A.

[0079] Figure 3A CSI request and resource allocation method 300 according to some aspects of the present disclosure is illustrated. The method 300 solves some of the problems caused by jointly signaling an A-CSI trigger and an UL grant in a single PDCCH as in method 200A. Instead of jointly signaling an A-CSI trigger and an UL grant in a single PDCCH, the method 300 divides the process into discrete steps: triggering the generation of a CSI report by sending a CSI calculation request 302 to the UE (e.g., as a DCI in the PDCCH), and requesting the transmission of the CSI report by sending a CSI report transmission request 310 to the UE (e.g., as a DCI in the PDCCH). The BS 105 may include information indicating which downlink resources 304 (e.g., CSI-RS or CSI-IM) the UE 115 may use to measure CSI within the CSI calculation request 302 (e.g., in a CSI request field). However, the CSI calculation request 302 may not include any indication of which uplink resources to use to transmit the CSI report. Although Figure 3 CSI measurement resource 304 is illustrated as being located at a time after CSI calculation request 302, but it should be understood that in other examples CSI measurement resource 304 (e.g., a semi-persistent resource configured by RRC) may be located at a time before CSI calculation request 302. UE 115 may determine CSI and store the results (e.g., in Figure 4-8 340 ), but refrains from immediately transmitting CSI. Instead, the UE 115 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 an example of the method 300, the BS 105 may schedule the UE 115 to transmit uplink data in the remainder of time slot S0 340, time slot S1 342, time slot S2 344, and time slot S3 346. During time slot S4 348, the UE 115 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 time slot S5 350, the UE 115 may transmit the CSI report. BS 105 may not transmit CSI report transmission request 310 until the CSI calculation timeline expires, which is defined by Z" 306, where Z" is the minimum gap between CSI measurement resources 304 and CSI report transmission request. Z" 306 provides time for UE 115 to perform CSI calculations, rather than Figure 2A and 2B Once UE 115 receives CSI report transmission request 310, it may also report CSI using a shortened timeline corresponding to the timeline described above. Figure 2BN2 described in and using the sample values ​​in Table 2 above.

[0080] The minimum gap Z" 306 may be a predetermined duration known to the BS 105 and the UE 115. For example, the minimum gap Z" 306 may be defined by a wireless communication standard, such as 3GPP. In some aspects, the minimum gap Z" 306 may be defined as the minimum gap from the end of the last codeword of the CSI measurement resource 304 to the beginning of the earliest codeword 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 calculation request 302 to the beginning of the earliest codeword of the PDCCH (or CORESET) carrying the CSI report transmission request 310. As discussed above, in some instances, the CSI measurement resource 304 may be located at a time before the CSI calculation request 302. When the CSI measurement resource 304 is located before the CSI calculation request 302, the minimum gap Z" 306 can be defined as the minimum gap from the end of the PDCCH (or CORESET) carrying the CSI calculation request 302 to reduce the implementation complexity at the UE 115.

[0081] Method 300 may be used as in Figure 4-9 The timer mechanism described in determines which CSI (if any) to transmit as part of the channel state report. For example, the UE 115 may start a timer at the end 320 of the Z" 306 timeline, and the timer may run for a duration 308 and expire at the end 322 of the duration 308. The timer duration may be preconfigured (e.g., configured to a value defined in a 3GPP specification). Alternatively, the timer value may be configured by the BS 105 (e.g., via RRC signaling) or indicated by the BS 105 (e.g., as part of the CSI calculation request 302). The timer duration may be based on information that the UE 115 is to include in the CSI report (e.g., the CSI report content) (e.g., the timer duration may be larger 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, CSI based on codebook type II may be associated with a longer processing or calculation time (and therefore associated with a longer timer duration) than CSI based on codebook type I.

[0082] In some aspects, the minimum gap Z″ 306 may be defined using a similar mechanism as described in Section 5.4 of 3GPP TS 38.214 document. For example, the UE 115 may define a minimum gap Z″ 306 in symbol Z″ ref Start the timer at Z″ref is defined as the period of time (e.g., T″) that has elapsed since the last symbol of the PDCCH (or CORESET) that carries the CSI calculation request 302 that triggers the CSI calculation. wait，CSI ) starts from the next DL symbol. Duration T″ wait，CSI It can be expressed as follows:

[0083] T″ wait,CSI =Z″×(2048+144)×κ2 -μ ×T c , (1)

[0084] Where Z" represents Z" 306 in units of OFDM symbols, k is a constant, μ represents the SCS configuration, and Tc represents the time unit in NR. In some examples, the μ parameter may be defined as the SCS configuration for PDCCH (denoted as μ PDCCH ) and the SCS configuration for CSI-RS (denoted as μ CSI-RS ), which can be expressed as min(μ PDCCH , μ CSI-RS ). The μ parameter may be independent of the SCS configuration for PUSCH since no PUSCH resources are scheduled in the DCI carrying the CSI calculation request 302.

[0085] If the CSI report transmission request 310 arrives while the timer is running (as illustrated herein), the UE 115 may transmit the most recently calculated CSI (based on the CSI measurement resources 304) in the CSI report. However, if the UE 115 receives the CSI report transmission request 310 before the timer is started, the UE 115 may not have been able to complete the requested channel estimation and / or interference measurement or the UE 115 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 calculated CSI data is now stale or that the UE 115 may have missed an earlier CSI report request. In either case—when the CSI transmission request 310 is received before the timer is started or after the timer has expired—the UE 115 may transmit CSI that may not be current (e.g., the most recently stored—now stale—CSI, or previously stored CSI based on an older CSI calculation request and corresponding CSI measurement resources) or placeholder data in the CSI report. The transmission of stale CSI is to satisfy the CSI report transmission request because the UE will transmit as scheduled by the BS. Transmission of 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) acknowledgment. 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 ACK due to the CSI report transmission request failing to comply with the CSI reporting timeline. In this case, the BS105 may determine that the CSI report is not based on the most recent CSI calculation request. Alternatively, the UE may completely ignore the CSI report transmission request (i.e., suppress transmission of the CSI report), for example, when the CSI transmission request only includes a grant for transmitting the CSI report. In some aspects, the UE 115 may remove the stored CSI from memory based on expiration of a timer.

[0086] Figure 4 is an exemplary sequence diagram illustrating a method 400 of communication between BS 105 and UE 115 according to some aspects of the present disclosure. The method 400 may be implemented in the same manner as described above with reference to Figure 3 The method 300 discussed above has a similar mechanism. As illustrated, the method 400 includes several enumeration actions, but various embodiments of the method 400 may include additional actions before, after, and between these enumeration actions. In some embodiments, one or more of these enumeration actions may be omitted or performed in a different order.

[0087] At step 402, the BS 105 may transmit a first CSI calculation request (also referred to as a calculation trigger) to the UE 115, which may include an indication of CSI measurement resources on which the UE 115 should perform CSI measurements. The BS 105 may transmit the first CSI calculation request as a downlink control information (DCI) message (also referred to herein as a calculation-only DCI) in the PDCCH, and the first CSI calculation request may not include any grant of UL resources for transmitting the CSI report. In other words, the first CSI calculation request may not include any scheduling information for transmitting the CSI report.

[0088] At step 404, UE 115 may identify a first CSI measurement resource based on the CSI calculation request. The first CSI measurement resource may correspond to a CSI-RS (e.g., NZP CSI-RS) resource that UE 115 may use for channel response measurement and / or a CSI-IM resource that UE 115 may use for interference measurement. The first CSI measurement resource may be located at a time after the first CSI calculation request. Alternatively, the first CSI measurement resource may be located at a time before the CSI calculation request (e.g., in the case where the CSI will be based on a periodic or semi-persistent CSI-RS configured via RRC).

[0089] At step 406, UE 115 may determine a first CSI based on the first CSI measurement resource. The UE may perform channel and / or interference measurements to determine the CSI. UE 115 may store the resulting CSI in a memory of the UE 115. While UE 115 is calculating the first CSI and / or after UE 115 calculates the first CSI, UE 115 may receive a scheduling grant (e.g., for URLLC data) from BS 105 and may transmit uplink data based on the scheduling grant. In some instances, UE 115 may maintain multiple CSIs corresponding to different CSI calculation requests and CSI measurement resources stored in its memory (e.g., Figure 7 704). UE 115 may store and maintain multiple CSIs in its memory. In some instances, there may be a limit on 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 the memory exceeds the limit.

[0090] In step 408, UE 115 may receive a channel state report transmission request associated with the first CSI measurement resource from BS 105 (e.g., as a DCI message on the PDCCH). The channel state report transmission request may indicate that UE 115 may transmit a report including the first CSI calculated based on the first CSI measurement resource. The CSI report transmission request may indicate which uplink resources (e.g., PUSCH resources) UE 115 may use to transmit the report. In one example, the channel state report transmission request (e.g., reporting only DCI) includes a CSI request field that includes a value mapped to a CSI triggering state. The CSI triggering state may be associated with a CSI report configuration that references the first CSI measurement resource to be used for reporting CSI. Accordingly, UE 115 may determine that BS 105 is requesting CSI for the first CSI measurement resource.

[0091] At step 410, UE 115 may transmit a channel state report including the first CSI to BS 105. In some examples, UE 115 may adopt the following method 500 ( Figure 5 4. The timer described in detail in FIG. 4A determines which of the stored CSIs (if any) to transmit to BS 105 in response to the CSI transmission request, as described below in step 418.

[0092] At step 412 , the BS 105 may transmit a second CSI calculation request in a similar manner as the first calculation request.

[0093] At step 414, BS 115 may identify a second CSI measurement resource in a manner similar to the first CSI measurement resource. UE 115 may perform channel and / or interference measurements to determine CSI. While UE 115 is calculating CSI based on the second CSI measurement resource and / or after UE 115 calculates the CSI, UE 115 may receive a scheduling grant (e.g., for URLLC data) from BS 105 and may transmit uplink data based on the scheduling grant. UE 115 may store the CSI determined based on the second CSI measurement resource in a memory (e.g., Figure 7 As described in step 406, the number of CSIs that UE 115 can store may be limited. For example, if the limit has been reached, UE 115 may delete older CSI (e.g., CSI from step 406) or refrain from storing newly calculated CSI.

[0094] At step 416, UE 115 may determine and store second CSI based on the second CSI measurement resource.

[0095] At step 418, UE 115 may receive a second channel state report transmission request (e.g., as a DCI message on the PDCCH) associated with the second CSI measurement resource from BS 105. The second channel state report transmission request may indicate that UE 115 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) UE 115 may use to transmit the report.

[0096] In some instances, UE 115 may employ a timer mechanism to determine whether to transmit the second CSI, the first CSI, or a different CSI as requested by BS 105, or to transmit no CSI. For example, UE 115 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 may be (approximately) the minimum gap between the end time of the second CSI measurement resource and the time at which UE 115 may determine the second CSI. The timer duration may be preconfigured (e.g., configured to a value defined in a 3GPP specification). Alternatively, the timer value may be indicated by BS 105 (e.g., via RRC signaling) or configured by BS 105 (e.g., as part of a CSI calculation request). The timer duration may be based on information that UE 115 is to include in the second CSI report (e.g., the timer duration may be larger 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.

[0097] In some instances, the time period during which the timer is running may correspond to a time period during which a second CSI report should be transmitted to the BS 105 in response to receiving a second CSI report transmission request. For example, if the second CSI report transmission request arrives while the timer is running, the UE 115 may transmit the second CSI (i.e., the most recently calculated CSI) in the CSI report. However, if the UE 115 receives the second CSI report transmission request before the timer is started, the UE 115 may not yet 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 is started or after the timer has expired—the UE 115 may transmit CSI that may not be current (e.g., the most recently stored—now stale—CSI, or previously stored CSI based on an older CSI calculation request and corresponding CSI measurement resource). For example, the UE 115 may determine to transmit the first CSI that it determined and stored in step 406. The UE 115 may also determine to transmit 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 a HARQ acknowledgment. Alternatively, the UE 115 may completely ignore the second CSI report transmission request (i.e., refrain from transmitting the CSI report), for example, if the second CSI transmission request only includes a grant for transmitting the CSI report. In some instances, the UE 115 may also remove the stored CSI from the memory based on the expiration of a timer.

[0098] At block 420, UE 115 may optionally transmit a second channel state report including the CSI (or placeholder data) that it determined to include after step 418 (eg, in the uplink resources indicated in the second CSI report transmission request).

[0099] Figure 5 5 is a flow chart of a wireless communication method 500 according to some aspects of the present disclosure. Aspects of the method may be performed by a UE 115 alone or in conjunction with a BS 105.

[0100] At block 502, UE 115 may receive a CSI calculation request from BS 105 (e.g., in a DCI message on a PDCCH), such as Figure 6-9 The CSI calculation request may not include any resources for UL transmission of CSI data.

[0101] At block 504, UE 115 may identify a CSI measurement resource based on the CSI calculation request. The CSI measurement resource may correspond to a CSI-RS (e.g., NZP CSI-RS) resource that UE 115 may use for channel response measurement and / or a CSI-IM resource that UE 115 may use for interference measurement. The first CSI measurement resource may be located at a time after the first CSI calculation request. Alternatively, the first CSI measurement resource may be located at a time before the CSI calculation 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, UE 115 may perform blocks 506 and 510 in parallel.

[0102] In block 506, the UE 115 starts a timer after Z" symbols, where Z" is the minimum gap between the end of the CSI measurement resources (e.g., CSI-RS resources and / or CSI-IM resources) and the start of the CSI report transmission request (e.g., the fastest time that the UE 115 can complete determining the CSI). Once Z" symbols have elapsed, the UE 115 starts (or resets) a timer during which it expects to receive a CSI report transmission request. The timer may help the UE 115 determine which of the stored CSI (if any) to transmit to the BS in response to the CSI transmission request, as described herein. The timer duration may be preconfigured (e.g., configured to a value defined in a 3GPP specification). Alternatively, the timer value may be indicated by the BS 105 (e.g., via RRC signaling) or configured by the BS 105 (e.g., as part of a CSI calculation request). The timer duration may be based on information that the UE 115 is to include in the CSI report (e.g., the timer duration may be larger 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.

[0103] At block 510, UE 115 determines CSI based on the CSI measurement resources. UE 115 may perform channel and / or interference measurements on the CSI measurement resources. For example, if the CSI measurement resources include CSI-RS measurement resources, UE 115 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 measurement, UE 115 may transmit UL data (e.g., URLLC data unrelated to the CSI data) to BS 105. For example, BS 105 may transmit UL data (e.g., URLLC data unrelated to the CSI data) to BS 105 during this time (e.g., during Figure 3306) transmits an UL grant to UE 115, and UE 115 may transmit uplink data to BS 105 (e.g., on the PUSCH). Figure 5 It is explained that UE 115 determines CSI after receiving the CSI calculation request, but it should be understood that in other examples, the CSI calculation request may refer to a CSI measurement resource (e.g., a semi-persistent CSI resource configured by RRC) at a time before the CSI calculation request. Accordingly, when UE 115 receives the CSI calculation request, the UE 115 may have already started or completed CSI calculation.

[0104] At block 512, UE 115 may receive a CSI report transmission request. If UE 115 has not received the request, UE 115 may remain in this block until it receives the request. Once UE 115 receives the CSI report transmission, UE 115 may proceed to block 514.

[0105] At block 514, the UE 115 determines whether the CSI report transmission request was received before the timer (of block 508) started, which may indicate that the UE 115 did not have time to complete determining the CSI. If the CSI report transmission request was received before the timer started, the UE 115 proceeds to block 518. Otherwise, the UE 115 proceeds to block 516.

[0106] At block 516, the UE 115 determines that the timer (of block 508) is currently ongoing. If the timer is ongoing, the UE 115 proceeds to block 520. If the timer is not ongoing (i.e., it expired), the CSI determined by the UE at block 510 may be stale, and the UE 115 proceeds to block 518.

[0107] At block 518, the UE 115 may transmit older CSI (e.g., previously stored CSI based on an earlier CSI calculation request and an earlier corresponding CSI measurement resource) or placeholder data in the CSI report based on the CSI report transmission request arriving too early (as determined at block 514) or too late (as determined at block 516). Transmitting older CSI or placeholder data may be appropriate when, for example, the transmission on which the CSI transmission request arrived also included a grant to transmit uplink shared channel (UL-SCH) data or a hybrid automatic repeat request (HARQ) acknowledgment. Alternatively, the UE 115 may completely ignore the CSI report transmission request (i.e., refrain from transmitting the CSI report), for example, if the CSI transmission request only includes a grant to transmit the CSI report.

[0108] At block 520, the UE 115 may transmit a CSI report based on the current CSI.

[0109] Figure 6 is a block diagram of an exemplary BS 600 according to some aspects of the present disclosure. BS 600 may be as described above. Figure 1 105 in the network 100 discussed in . 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, for example, via one or more buses.

[0110] The processor 602 may have various features as a special-purpose type of processor. For example, these features may include a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a 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, for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0111] The memory 604 may include cache memory (e.g., cache memory of the processor 602), RAM, MRAM, ROM, PROM, EPROM, EEPROM, flash memory, solid-state memory devices, one or more hard disk drives, memristor-based arrays, other forms of volatile and non-volatile memory, or a combination of different types of memory. In some aspects, the memory 604 may include a non-transitory computer-readable medium. The 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., Figure 6-9 ) instructions. Instructions 606 may also be referred to as program code. Program code may be used to cause the wireless communication device to perform these operations, for example, by causing one or more processors (such as processor 602) to control or command the wireless communication device to do so. The terms "instructions" and "code" should be interpreted 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, etc. "Instructions" and "code" may include a single computer-readable statement or many computer-readable statements.

[0112] The channel status module 608 may be implemented via hardware, software, or a combination thereof. For example, the channel status 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, the channel status module 608 may be integrated within the modem subsystem 612. For example, the channel status 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.

[0113] The channel status module 608 may be used in various aspects of the present disclosure, for example, Figure 3-5 and Fig. 9 For example, the channel state module 608 may transmit a CSI computation request (e.g., in coordination with the 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 a computation-only DCI), and the CSI computation request may not include any grant of UL resources for transmitting the CSI report by the UE 115. In other words, the CSI computation request may not indicate any scheduling information or resources for transmitting the CSI report.

[0114] The channel state module 608 may also be configured to transmit (e.g., in coordination with the transceiver 610) to the UE 115 a channel state report transmission request (e.g., as a DCI message on the PDCCH) associated with the first CSI measurement resource. The first CSI measurement resource may include a CSI-RS (e.g., an NZP CSI-RS) resource and / or a CSI-IM resource. The channel state report transmission request may indicate that the UE 115 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 UE 115 should use when transmitting the report. In some instances, the channel state module 608 may transmit the channel state report transmission request after a first duration has elapsed from the time when the first CSI measurement resource is located (e.g., the start or end of the first CSI measurement resource). The first duration may be based on a CSI calculation timeline (e.g., as may be defined in a 3GPP specification), as described with reference to Figure 3In some examples, the channel state module 608 may also indicate to the UE 115 a configuration for a duration of a timer for associating a CSI report to a first CSI measurement resource (e.g., via RRC signaling or as part of a CSI calculation 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.

[0115] The channel state module 608 may also be configured to receive (e.g., in coordination with the transceiver 610 on the PUSCH using 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 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 channel state module 608 may transmit to the UE 115 an indication of a second CSI measurement resource that precedes the first CSI measurement resource. Depending on when the channel state module 608 transmits the 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 the CSI report transmission request while a timer is running (e.g., Figure 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 is started (which may be too early for the UE 115 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 based on the second CSI measurement resource, or placeholder data. This may occur when, for example, the BS 105 includes a grant to transmit UL-SCH data or HARQ acknowledgment together with a grant to transmit a CSI report. In some instances, the channel state module 608 may not receive a CSI report at all, for example, where the channel state module 608 has scheduled uplink resources only for CSI reporting.

[0116] In some aspects, the BS 105 may transmit (e.g., in coordination with the transceiver 610) a scheduling grant to the UE 115 after the channel state module 608 transmits the CSI calculation 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 UE 115 based on the scheduling grant.

[0117] As shown, the transceiver 610 may include a modem subsystem 612 and an RF unit 614. The transceiver 610 may be configured to communicate bidirectionally with other devices (such as UE 115 and / or 500 and / or another core network element). The modem subsystem 612 may be configured to modulate and / or encode data according to an MCS (e.g., an LDPC decoding scheme, a turbo decoding scheme, a convolutional decoding scheme, a digital beamforming scheme, etc.). The RF unit 614 may be configured to process (e.g., perform analog-to-digital conversion or digital-to-analog conversion, etc.) modulated / encoded data (e.g., PDCCH signals, DL data, scheduling grants, RRC configurations, reference signals, CSI-RS, CSI calculation requests, CSI report transmission requests, CSI calculation only DCI, CSI report only CSI, etc.) from the modem subsystem 612 (on outbound transmissions) or from another source (such as UE 115 and / or UE 700). 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 BS 105 to enable BS 105 to communicate with other devices.

[0118] The RF unit 614 may provide modulated and / or processed data (e.g., data packets (or, more generally, data messages that may include one or more data packets and other information)) to the 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.

[0119] In an example, the transceiver 610 is configured to transmit a CSI calculation 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 UE 115, and receive a CSI report associated with the first CSI measurement resource from the UE 115 in response to the CSI report transmission request.

[0120] Figure 7 700 is a block diagram of an exemplary UE 700 according to some aspects of the present disclosure. UE 700 may be as described above. Figure 1115 discussed in . 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.

[0121] 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, for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0122] 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 a combination of different types of memory. In one aspect, the memory 704 includes a non-transitory computer-readable medium. The memory 704 may store or have recorded thereon instructions 706. The instructions 706 may include instructions that, when executed by the processor 702, cause the processor 702 to perform the various aspects of the present disclosure described herein with reference to the UE 115 (e.g., Figure 6-Figure 8 Instructions 706 may also be referred to as program code, which may be broadly interpreted as including instructions as described above with reference to Figure 4 Any type of computer-readable statement in question.

[0123] The channel status module 708 may be implemented via hardware, software, or a combination thereof. For example, the channel status module 708 may be implemented as a processor, circuit, and / or instructions 706 stored in the memory 704 and executed by the processor 702. In some examples, the channel status module 708 may be integrated within the modem subsystem 712. For example, the channel status 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. The operations described as being performed by the channel status module 708 may be performed by or in conjunction with a different module (e.g., the transceiver 710).

[0124] The channel status module 708 may be used in various aspects of the present disclosure, for example, Figure 3-5 and Figure 8 For example, the channel state module 708 may be configured to receive (e.g., in coordination with the transceiver 710) a CSI calculation request from the BS 105. The channel state module 708 may receive the CSI calculation request as a downlink control information (DCI) message in the PDCCH (also referred to herein as a calculation-only DCI), and the CSI calculation request may not include any grant of UL resources for transmitting the CSI report. In other words, the CSI calculation request may not include any scheduling information for transmitting the CSI report.

[0125] The channel state module 708 may also be configured to identify a first CSI measurement resource based on the CSI calculation request. The CSI measurement resource may include a CSI-RS and / or a CSI-IM resource. The channel state module 708 may receive a configuration for the first CSI measurement resource from the BS 105 (eg, included in the CSI calculation request or received separately).

[0126] The channel state module 708 may also be configured to determine CSI based on the first CSI measurement resource (e.g., in cooperation with the processor 702). The channel state module 708 may perform channel and / or interference measurements to determine the CSI. In some instances, the channel state module 708 may store the resulting CSI in the memory 704. Thereafter, the UE 115 may continue to transmit other types of uplink data (e.g., URLLC data). For example, the UE 115 may receive a scheduling grant from the BS 105 and may transmit uplink data based on the scheduling grant. In some instances, the channel state module 708 may maintain multiple CSIs corresponding to different CSI calculation 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 before the first CSI measurement resource. The 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 the memory 704. The channel state module 708 may store and maintain multiple CSIs in its memory 704. In some instances, there may be a limit on the number of CSI that module 708 may store, and channel state module 708 may delete stored CSI or not store newly calculated CSI when the number of CSI in memory 704 exceeds the limit.

[0127] The channel state module 708 may also be configured to receive from the BS 105 (e.g., in coordination with the transceiver 710, as a DCI message on the PDCCH) a channel state report transmission request associated with the first CSI measurement resource. 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 including the CSI to the BS 105 (e.g., in coordination with the transceiver 710).

[0128] In some examples, channel status module 708 can use the method 500 ( Figure 5 ) to determine which of the stored CSI (if any) to transmit to BS 105 in response to the CSI transmission request. For example, the channel state module 708 may start (or reset) the timer after a certain period (or duration) has elapsed from the time when the first CSI measurement resource is located (e.g., the first CSI measurement resource starts or ends). The period may be (approximately) the minimum gap between the end time of the CSI measurement resource and the time when the channel state module 708 can determine the CSI. The timer duration may be preconfigured (e.g., configured to a value defined in the 3GPP specification). Alternatively, the timer value may be indicated by BS 105 (e.g., via RRC signaling) or configured by BS 105 (e.g., as part of a CSI calculation request). The timer duration may be based on the information that the channel state module 708 is to include in the CSI report (e.g., the timer duration may be larger when the 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.

[0129] The time period during which the timer is running may correspond to the time period during which the current CSI report should be transmitted to the BS 105 in response to receiving the CSI report transmission request. For example, if the CSI report transmission request arrives while the 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 the CSI report transmission request before the timer is started, the channel state module 708 may not yet 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 the CSI transmission request is received before the timer is started or after the timer expires—the channel state module 708 may transmit CSI that is not the current (e.g., previously stored) CSI. For example, the channel state module 708 may transmit CSI determined relative to the second (earlier) CSI measurement resource rather than the most recent (later) first CSI measurement resource. The 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 arrives also includes a grant to transmit UL-SCH data or a HARQ acknowledgment. Alternatively, the channel state module 708 may completely ignore the CSI report transmission request (i.e., refrain from transmitting the CSI report), for example, if the CSI transmission request only includes a grant to transmit a CSI report. In some examples, the channel state module 708 may also remove the stored CSI from the memory based on the expiration of a timer.

[0130] As shown, the transceiver 710 may include a modem subsystem 712 and an RF unit 714. The transceiver 710 may be configured to communicate bidirectionally with other devices, such as BS 105. The modem subsystem 712 may be configured to modulate and / or encode data from the memory 704 and / or the 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 or 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 out-of-band transmissions) or from another source, such as UE 115 or BS 105. The RF unit 714 may be further configured to perform analog beamforming in conjunction with digital beamforming. Although shown as 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 UE 115 to enable the UE 115 to communicate with other devices.

[0131] The RF unit 714 may provide modulated and / or processed data (e.g., data packets (or, more generally, data messages that may include one or more data packets and other information)) to the 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 may provide the 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 calculation DCI only, CSI report CSI only, 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 configure the antenna 716.

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

[0133] In an example, the transceiver 710 is configured to receive a CSI calculation request from the BS 105. The processor 702 is configured to identify a first CSI measurement resource based on the CSI calculation 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 BS 105 after the CSI calculation request.

[0134] Figure 8 800 according to some aspects of the present disclosure. Aspects of method 800 may be performed by a computing device (e.g., a processor, a processing circuit, and / or other suitable components) of a wireless communication device or other suitable means for performing the steps. For example, a wireless communication device (such as UE 115 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 be implemented as described above with reference to Figure 3-5 The method 800 described herein is similar to the mechanism in the method 300, sequence 400, and method 500. As illustrated, the method 800 includes several enumerated steps, but aspects of the method 800 may include additional steps before, after, and between the enumerated steps. In some aspects, one or more of the enumerated steps may be omitted or performed in a different order.

[0135] In block 802, the UE 115 may receive a CSI calculation request from the BS 105. The UE 115 may receive the CSI calculation request as a downlink control information (DCI) message in a PDCCH (also referred to herein as a calculation-only DCI), and the CSI calculation request may not include any grant of UL resources for transmitting a CSI report. In other words, the CSI calculation request may not include any scheduling information for transmitting a CSI report. In some instances, the UE 115 may utilize one or more components (such as a processor 702, a memory 704, a channel state module 708, a transceiver 710, a modem 712, and one or more antennas 716) to perform aspects of block 802.

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

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

[0138] In step 808, UE 115 may receive a channel state report transmission request associated with the CSI measurement resource from BS 105 (e.g., as a DCI message on the PDCCH). In one example, the channel state report transmission request (e.g., reporting only DCI) includes a CSI request field that includes 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 reference a CSI measurement resource that BS 105 is requesting for reporting. The channel state report transmission request may indicate that UE 115 should transmit a report including the CSI calculated based on the CSI measurement resource. The CSI report transmission request may indicate which uplink resources (e.g., PUSCH resources) UE 115 should use when transmitting the report. UE 115 may then transmit a channel state report including the CSI to BS 105.

[0139] In some examples, UE 115 may employ the method 500 ( Figure 5 105 to determine which of the stored CSI (if any) is to be transmitted to the BS 105 in response to the CSI report transmission request using the timer described in (explained in ). For example, the UE 115 may start (or reset) the 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) the minimum gap from the end time of the last symbol of the first CSI measurement resource or the end time of the PDCCH (or CORESET) carrying the CSI calculation request to the start time of the earliest symbol of the PDCCH (or CORESET) that may carry the CSI report transmission request, for example, as described above with reference to Figure 3 As shown in equation (1) discussed above. . The timer duration may be preconfigured (e.g., configured to a value defined in a 3GPP specification). Alternatively, the timer value may be indicated by BS 105 (e.g., via RRC signaling) or configured by BS 105 (e.g., as part of a CSI calculation request). The timer duration may be based on information that UE 115 is to include in the CSI report (e.g., the timer duration may be larger 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.

[0140] The time period during which the timer is running may correspond to the time period during which the current CSI report should be transmitted to the BS 105 in response to receiving the CSI report transmission request. For example, if the CSI report transmission request arrives while the timer is running, the UE 115 may transmit the most recently calculated CSI (i.e., based on the first CSI measurement resource) in the CSI report. However, if the UE 115 receives the CSI report transmission request before the timer is started, the UE 115 may not yet be able to complete the requested channel 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 the CSI transmission request is received before the timer is started or after the timer expires—the UE 115 may transmit CSI that is not the current (e.g., previously stored) CSI. For example, the UE 115 may transmit CSI determined relative to a second (earlier) CSI measurement resource rather than the most recent (later) first CSI measurement resource.

[0141] The UE 115 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 arrives also includes a grant for transmitting UL-SCH data or a HARQ acknowledgment. Alternatively, the UE 115 may completely ignore the CSI report transmission request (i.e., refrain from transmitting the CSI report), for example, when the CSI transmission request only includes a grant for transmitting the CSI report. In some instances, the UE 115 may also remove the stored CSI from the memory based on the expiration of a timer (because a CSI report transmission request for the CSI was not received). In some instances, the UE 115 may utilize one or more components (such as the processor 702, the memory 704, the channel state module 708, the transceiver 710, the modem 712, and one or more antennas 716) to perform aspects of block 808.

[0142] Fig. 9 900 is a flowchart of a wireless communication method 900 according to some aspects of the present disclosure. Various aspects of the method 900 may be performed by a computing device (e.g., a processor, a processing circuit, and / or other suitable components) of a wireless communication device or other suitable means for performing the steps. For example, a wireless communication device (such as BS 105 or 600) may utilize one or more components (such as a processor 602, a memory 604, a channel state module 608, a transceiver 610, a modem 612, and one or more antennas 616) to perform the steps of the method 900. The method 900 may be implemented as described above with reference to Figure 3-5The method 900 described herein may be a mechanism similar to that in the method 300, the sequence 400, and the method 500. As illustrated, the method 900 includes several enumerated steps, but aspects of the method 900 may include additional steps before, after, and between the enumerated steps. In some aspects, one or more of the enumerated steps may be omitted or performed in a different order.

[0143] In block 902, the BS 105 may transmit a CSI calculation request to the UE 115. The UE 115 may transmit the CSI calculation request as a downlink control information (DCI) message in a PDCCH (also referred to herein as a calculation-only DCI), and the CSI calculation request may not include any grant of UL resources for transmitting a CSI report by the UE 115. In other words, the CSI calculation request may not indicate any scheduling information or resources for transmitting the CSI report. In some embodiments, the CSI calculation request may include a configuration of a first CSI measurement resource, which may include a CSI-RS (e.g., an NZP CSI-RS) or a CSI-IM resource. In some embodiments, the BS 105 may transmit the configuration for the first CSI measurement resource to the UE 115 separately. In some instances, the BS 105 may utilize one or more components (such as a processor 602, a memory 604, a channel state module 608, a transceiver 610, a modem 612, and one or more antennas 616) to perform aspects of block 902.

[0144] In block 906, BS105 may transmit a channel state report transmission request associated with the first CSI measurement resource to UE 115 (e.g., as a DCI message on the PDCCH). In one example, the channel state report transmission request (e.g., reporting only DCI) includes a CSI request field that includes a value mapped to a CSI triggering state. The CSI triggering state may be associated with one or more CSI reporting configurations. Each CSI reporting configuration may reference a CSI measurement resource that 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 calculation request. The channel state report transmission request may indicate that UE 115 should transmit a report including the CSI calculated based on the first CSI measurement resource. The CSI report transmission request may indicate which uplink resources (e.g., PUSCH resources) UE 115 should use when transmitting the report. In some examples, BS 105 may transmit a channel state report transmission request after a first duration has elapsed from an end time of a first CSI measurement resource (e.g., an end of a last symbol of a CSI measurement resource). The first duration may be based on a CSI calculation timeline, as described with reference to Figure 3described. In some instances, the BS 105 may also indicate to the UE 115 the configuration of the duration of the timer for associating the CSI report to the first CSI measurement resource (e.g., via RRC signaling or as part of a CSI calculation request). The timer duration may be based on information to be included in the CSI report (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. In some instances, the BS 105 may utilize one or more components (such as a processor 602, a memory 604, a channel state module 608, a transceiver 610, a modem 612, and one or more antennas 616) to perform aspects of block 904.

[0145] At block 908, BS 105 may receive (e.g., on a PUSCH using resources indicated by BS 105 in the channel state report transmission request) 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, BS 105 may indicate to UE 115 a second CSI measurement resource that precedes the first CSI measurement resource. Depending on when UE 115 transmits the CSI report transmission request, the channel state report may instead be based on the second CSI measurement resource. For example, if UE 115 transmits the CSI report transmission request within a timer (e.g., Figure 5 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 UE 115 before the timer is started (which may be too early for the UE 115 to complete determining the CSI) or after the timer expires (which may be when the CSI is stale), the BS 105 may instead receive a CSI report based on the second CSI measurement resource, or placeholder data. This may occur when, for example, the BS 105 includes a grant to transmit UL-SCH data or HARQ acknowledgment together with a grant to transmit a CSI report. In some instances, the BS 105 may not receive a CSI report at all, for example, where the BS 105 has scheduled uplink resources only for CSI reporting.

[0146] In some examples, BS 105 may transmit a scheduling grant to UE 115 after the CSI calculation request and before the CSI report transmission request. BS 115 may then receive an uplink transmission (eg, a transmission associated with URLLC data) from UE 115 based on the scheduling grant.

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

[0148] The various illustrative blocks and modules described in conjunction with the disclosure herein may be implemented or executed 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 an alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The 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).

[0149] 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, each function may be stored on a computer-readable medium or transmitted therefrom as one or more instructions or codes. Other examples and implementations fall within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the above functions may be implemented using software, hardware, firmware, hard wiring, or any combination thereof executed by a processor. The features that implement the functions may also be physically located in various locations, including being distributed so that the various parts of the functions are implemented at different physical locations. In addition, as used herein (including in the claims), the "or" used in the enumeration of items (e.g., enumeration of items with phrases such as "at least one of" or "one or more of") indicates an inclusive enumeration, so that, for example, the enumeration of [at least one of 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).

[0150] As will be appreciated by those skilled in the art and depending on the specific application at hand, many modifications, substitutions and changes may be made to the materials, devices, configurations and methods of use of the apparatus of the present disclosure without departing from the spirit and scope of the present disclosure. In view of this, the scope of the present disclosure should not be limited to the specific embodiments illustrated and described herein (as they are merely examples of the present disclosure), but should be fully equivalent to the appended claims and their functional equivalents.

Claims

1. A wireless communication method performed by a user equipment UE, comprising: receiving a channel state information (CSI) calculation request from a network entity; identifying a first CSI measurement resource based on the CSI calculation request; determining CSI based on the first CSI measurement resource; starting a timer after a first duration has elapsed from an end time of the first CSI measurement resource; receiving, from the network entity after the CSI calculation request, a CSI report transmission request associated with the first CSI measurement resource; as well as Based on the CSI report transmission request being received while the timer is ongoing, transmitting a CSI report including the determined CSI to the network entity in response to the CSI report transmission request.

2. The method of claim 1, wherein receiving the CSI calculation request comprises: The CSI calculation request including the configuration of the first CSI measurement resource is received from the network entity.

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

4. The method of claim 1, further comprising: storing the determined CSI at a memory of the UE; as well as Based on the CSI report transmission request being received while the timer is ongoing, transmitting the CSI report including the stored CSI to the network entity in response to the CSI report transmission request.

5. The method of claim 1, further comprising: Transmitting the CSI report is refrained based on the CSI report transmission request being received before the timer is started or after the timer expires.

6. The method of claim 1, further comprising: receiving, from the network entity, an indication of a second CSI measurement resource earlier than the first CSI measurement resource; as well as Based on the CSI report transmission request being received before the timer is started or after the timer expires, transmitting a CSI report including the CSI associated with the second CSI measurement resource to the network entity in response to the CSI report transmission request.

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

8. 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: A second DCI including the CSI report transmission request is received.

9. The method of claim 1, further comprising: receiving a scheduling grant from the network entity after the CSI computation request and before the CSI report transmission request; An uplink data transmission is transmitted to the network entity based on the scheduling grant.

10. The method of claim 9, wherein the uplink data transmission is associated with Ultra Reliable Low Latency Communication (URLLC).

11. A wireless communication method performed by a network entity, comprising: transmitting a configuration of a duration of a timer for a user equipment UE to associate a channel state information CSI report to a first CSI measurement resource; transmitting a CSI calculation request for the UE; transmitting, after a first duration has elapsed from an end time of a first CSI measurement resource, a CSI report transmission request for the UE associated with the first CSI measurement resource; as well as A CSI report associated with the first CSI measurement resource is received from the UE in response to the CSI report transmission request.

12. The method of claim 11, wherein transmitting the CSI calculation request comprises: The CSI calculation request including the configuration of the first CSI measurement resource is transmitted.

13. The method of claim 11, further comprising: Transmitting a configuration for the first CSI measurement resource.

14. The method of claim 11, wherein an end time of the first CSI measurement resource is an end of a last symbol of the CSI measurement resource.

15. The method of claim 11, further comprising: The duration of the timer is determined based on information to be included in a CSI report based on the CSI.

16. The method of claim 11, further comprising: transmitting, for the UE, an indication of a second CSI measurement resource earlier than the first CSI measurement resource; as well as A CSI report including CSI associated with the second CSI measurement resource is received from the UE in response to the CSI report transmission request.

17. The method of claim 11, 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: A second DCI including the CSI report transmission request is transmitted.

18. A user equipment UE, comprising: A processor is configured to cause the UE to: receiving a channel state information (CSI) calculation request from a network entity; identifying a first CSI measurement resource based on the CSI calculation request; determining CSI based on the first CSI measurement resource; starting a timer after a first duration has elapsed from an end time of the first CSI measurement resource; receiving, from the network entity after the CSI calculation request, a CSI report transmission request associated with the first CSI measurement resource; as well as Based on the CSI report transmission request being received while the timer is ongoing, transmitting a CSI report including the determined CSI to the network entity in response to the CSI report transmission request.

19. The UE of claim 18, wherein the processor is configured to cause the UE to: The CSI calculation request including the configuration of the first CSI measurement resource is received from the network entity.

20. The UE of claim 18, wherein the processor is further configured to cause the UE to: A configuration for the first CSI measurement resource is received from the network entity.

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

22. The UE of claim 18, further comprising a memory, wherein: The processor is further configured to cause the UE to: storing the determined CSI at the memory; as well as Based on the CSI report transmission request being received while the timer is in progress, transmitting to the network entity in response to the CSI report transmission request a CSI report including the stored CSI The CSI report.

23. The UE of claim 18, wherein the processor is further configured to: Transmitting the CSI report is refrained based on the CSI report transmission request being received before the timer is started or after the timer expires.

24. The UE of claim 18, wherein the processor is further configured to cause the UE to: receiving, from the network entity, an indication of a second CSI measurement resource earlier than the first CSI measurement resource; and Based on the CSI report transmission request being received before the timer is started or after the timer expires, transmitting a CSI report including the CSI associated with the second CSI measurement resource to the network entity in response to the CSI report transmission request.

25. A network entity, comprising: a processor configured to cause the network entity to: transmitting a configuration of a duration of a timer for a user equipment UE to associate a channel state information CSI report to a first CSI measurement resource; transmitting a CSI calculation request for the UE; transmitting, after a first duration has elapsed from an end time of a first CSI measurement resource, a CSI report transmission request for the UE associated with the first CSI measurement resource; as well as A CSI report associated with the first CSI measurement resource is received from the UE in response to the CSI report transmission request.

26. The network entity of claim 25, wherein the processor is configured to cause the network entity to: The CSI calculation request including the configuration of the first CSI measurement resource is transmitted.

27. The network entity of claim 25, wherein the processor is further configured to cause the network entity to: Transmitting a configuration for the first CSI measurement resource.

28. The network entity of claim 25, wherein an end time of the first CSI measurement resource is an end of a last symbol of the CSI measurement resource.

29. A user equipment UE, comprising: means for receiving a channel state information (CSI) calculation request from a network entity; 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; means for starting a timer after a first duration has elapsed from an end time of the first CSI measurement resource; means for receiving, from the network entity, a CSI report transmission request associated with the first CSI measurement resource subsequent to the CSI calculation request; as well as Means for transmitting, based on the CSI report transmission request being received while the timer is ongoing, a CSI report including the determined CSI to the network entity in response to the CSI report transmission request.

30. A network entity, comprising: means for transmitting a configuration of a duration of a timer for a user equipment UE to associate a channel state information CSI report to a first CSI measurement resource; means for transmitting a CSI calculation request for the UE; means for transmitting, after a first duration has elapsed from an end time of a first CSI measurement resource, a CSI report transmission request for the UE associated with the first CSI measurement resource; as well as means for receiving a CSI report associated with the first CSI measurement resource from the UE in response to the CSI report transmission request.

Images