CSI report start location and window configuration for high Doppler CSI

Abstract

Apparatuses and methods for CSI report start location and window configuration are described. An apparatus is configured to receive information associated with a time window for CSI reporting, the time window including at least an offset from a starting position and a window size. The apparatus is configured to transmit a CSI report at an offset from the starting position and for a window size of the time window. The CSI report includes CSI for codebook refinement. Another apparatus is configured to transmit information associated with a time window for CSI reporting, the time window including at least an offset from a starting position and a window size. Another apparatus is configured to receive a CSI report at an offset from a starting position and for a window size of a time window. The CSI report includes CSI for codebook refinement.

Description

Technical Field

[0001] The present disclosure generally relates to communication systems, and more particularly to wireless communication utilizing channel state information (CSI) reporting. Background Art

[0002] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasting. A typical wireless communication system may employ a multiple access technology capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0003] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at the urban, national, regional, and even global levels. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., related to the Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Certain aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. Additionally, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the Invention

[0004] A simplified summary of one or more aspects is presented below in order to provide a basic understanding of these aspects. This summary of the invention is not an extensive overview of all contemplated aspects. The summary of the invention neither identifies key or critical elements of all aspects nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

[0005] In one aspect of the present disclosure, a method, a computer-readable medium, and a device are provided. The device is configured to receive information associated with a time window for channel state information (CSI) reporting from a network entity for use in the CSI reporting, where the time window includes at least an offset from a starting position and a window size. The device is further configured to send to the network entity the CSI report associated with the offset from the starting position and for the window size of the time window, where the CSI report includes CSI for codebook refinement.

[0006] In this aspect, the method includes: receiving information associated with a time window for channel state information (CSI) reporting from a network entity for use in the CSI reporting, where the time window includes at least an offset from a starting position and a window size. The method further includes: sending to the network entity the CSI report associated with the offset from the starting position and for the window size of the time window, where the CSI report includes CSI for codebook refinement.

[0007] In another aspect of the present disclosure, a method, a computer-readable medium, and a device are provided. The device is configured to send, for a user equipment (UE), information associated with a time window for channel state information (CSI) reporting for use in the CSI reporting, where the time window includes at least an offset from a starting position and a window size. The device is further configured to receive from the UE the CSI report associated with the offset from the starting position and for the window size of the time window, where the CSI report includes CSI for codebook refinement.

[0008] In another aspect, the method includes: sending, for a user equipment (UE), information associated with a time window for channel state information (CSI) reporting for use in the CSI reporting, where the time window includes at least an offset from a starting position and a window size. The method further includes: receiving from the UE the CSI report associated with the offset from the starting position and for the window size of the time window, where the CSI report includes CSI for codebook refinement.

[0009] To achieve the foregoing and related purposes, one or more aspects include the features described in full below and particularly pointed out in the claims. The following description and the drawings set forth in detail some illustrative features of one or more aspects. However, these features indicate only some of the various ways in which the principles of the various aspects may be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0011] Figure 2A FIG. is an illustration showing an example of a first frame in accordance with various aspects of the present disclosure.

[0012] Figure 2B FIG. is an illustration showing an example of a downlink (DL) channel within a subframe in accordance with various aspects of the present disclosure.

[0013] Figure 2C FIG. is an illustration showing an example of a second frame in accordance with various aspects of the present disclosure.

[0014] Figure 2D FIG. is an illustration showing an example of an uplink (UL) channel within a subframe in accordance with various aspects of the present disclosure.

[0015] Figure 3 FIG. is an illustration showing an example of a base station and a user equipment (UE) in an access network.

[0016] Figure 4 FIG. is an illustration showing an example of channel state information (CSI) observation and prediction boundaries in accordance with various aspects of the present disclosure.

[0017] Figure 5 FIG. is an illustration showing an example of a CSI window in accordance with various aspects of the present disclosure.

[0018] Figure 6 FIG. is an illustration showing an example of a CSI reporting window in accordance with various aspects of the present disclosure.

[0019] Figure 7 FIG. is a call flow diagram for wireless communication in accordance with various aspects of the present disclosure.

[0020] Figure 8 FIG. is an illustration showing an example of a CSI reporting configuration in accordance with various aspects of the present disclosure.

[0021] Figure 9 FIG. is an illustration showing an example of a CSI reporting configuration in accordance with various aspects of the present disclosure.

[0022] Figure 10 FIG. is an illustration showing an example of a CSI reporting configuration in accordance with various aspects of the present disclosure.

[0023] Figure 11 FIG. is a flowchart of a method for wireless communication in accordance with various aspects of the present disclosure.

[0024] Figure 12 FIG. is a flowchart of a method for wireless communication in accordance with various aspects of the present disclosure.

[0025] Figure 13 FIG. is an illustration showing an example of a hardware implementation of an example apparatus and / or network entity.

[0026] Figure 14 It is a diagram illustrating an example of a hardware implementation of an exemplary network entity. Detailed implementation

[0027] Aspects herein relate to configurations for, such as, CSI report start positions and CSI window configurations for high Doppler CSI. Some types of wireless communication (e.g., 5G NR) may be designed to implement CSI reporting, but with CSI configurations that are general and also limit scheduling flexibility for UE mobility considerations. Additionally, information for CSI reporting at the UE side may not be fully utilized, which may have an impact on resources at both the network side and the UE side. The described aspects provide flexibility in configurations for start offsets and CSI window sizes, which account for UE mobility and provide higher data rates, higher capacity, and higher spectral efficiency for CSI measurement and reporting.

[0028] The detailed implementations set forth below in connection with the accompanying drawings are descriptions of various configurations and do not represent the only configurations in which the concepts described herein may be practiced. To provide a thorough understanding of the various concepts, the detailed implementations include specific details. However, the 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.

[0029] Certain aspects of a telecommunications system are presented with reference to various apparatuses and methods. These apparatuses and methods are described in the following detailed implementations and illustrated in the drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

[0030] By way of example, an element, or any portion of an element, or any combination of elements can be implemented as a "processing system" that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on a chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described throughout this disclosure. One or more processors in the processing system can execute software. Software should be broadly construed to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof, regardless of whether it is referred to as software, firmware, middleware, microcode, hardware description language, or other terms.

[0031] Thus, in one or more example aspects, embodiments, and / or use cases, the described functionality can be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality can be stored or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media can be any available medium that can be accessed by a computer. By way of example, such computer-readable media can include random access memory (RAM), read only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium capable of storing computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0032] Although aspects, embodiments, and / or use cases are described by way of illustration with some examples in this application, additional or different aspects, embodiments, and / or use cases may arise in many different arrangements and scenarios. The aspects, embodiments, and / or use cases described herein may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, the aspects, embodiments, and / or use cases may be embodied via integrated chips and other non-module-component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchase devices, medical devices, artificial intelligence (AI)-enabled devices, etc.). Although some examples may or may not be specifically targeted at a use case or application, the examples described may have broad applicability. The aspects, embodiments, and / or use cases may range from chip-level or modular components to non-modular, non-chip-level embodiments, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the techniques herein. In some actual settings, devices incorporating the described aspects and features may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily includes multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The techniques described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated components, or disaggregated components, end-user devices, etc., of various sizes, shapes, and configurations.

[0033] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, network nodes, network entities, mobility elements of the network, radio access network (RAN) nodes, core network nodes, network elements, or network equipment (such as a base station (BS)) or one or more units (or one or more components) performing base station functions may be implemented in an aggregated or disaggregated architecture. For example, a BS (such as a Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit receive point (TRP), or cell, etc.) can be implemented as an aggregated base station (also referred to as a stand-alone BS or monolithic BS) or a disaggregated base station.

[0034] A converged base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A split base station may be configured to utilize a protocol stack that is physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed among one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0035] Base station operation or network design may consider the converged characteristics of base station functionality. For example, a split base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN, such as a network configuration advocated by the O-RAN Alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Splitting may include distributing functions across two or more units at various physical locations, as well as virtualizing the functions of at least one unit, which may achieve flexibility in network design. The various units of a split base station or a split RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0036] Figure 1 FIG. 100 is a diagram illustrating an example of a wireless communication system and an access network. The illustrated wireless communication system includes a split base station architecture. The split base station architecture may include one or more CUs 110, which may communicate directly with the core network 120 via a backhaul link, or indirectly with the core network 120 through one or more split base station units, such as a near real-time (near RT) RAN intelligent controller (RIC) 125 via an E2 link, or a non-real-time (non RT) RIC 115 associated with a service management and orchestration (SMO) framework 105, or both. The CU 110 may communicate with one or more DUs 130 via a respective midhaul link, such as an F1 interface. The DU 130 may communicate with one or more RUs 140 via a respective fronthaul link. The RU 140 may communicate with a respective UE 104 via one or more radio frequency (RF) access links. In some embodiments, the UE 104 may be served simultaneously by multiple RUs 140.

[0037] Each unit (i.e., CU 110, DU 130, RU 140, and the near RT RIC 125, non-RT RIC 115, and SMO framework 105) may include one or more interfaces or be coupled to one or more interfaces that are configured to receive or transmit signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or the associated processor or controller that provides instructions to the communication interfaces of these units may be configured to communicate with one or more of the other units via the transmission medium. For example, the units may include a wired interface that is configured to receive signals or transmit signals to one or more of the other units via a wired transmission medium. Additionally, the units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) that is configured to receive and / or transmit signals to one or more of the other units via a wireless transmission medium.

[0038] In some aspects, CU 110 may host one or more higher layer control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Service Data Adaptation Protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 110. CU 110 may be configured to handle user plane functionality (i.e., Central Unit - User Plane (CU-UP)), control plane functionality (i.e., Central Unit - Control Plane (CU-CP)), or a combination thereof. In some embodiments, CU 110 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units may communicate bidirectionally with the CU-CP units via an interface (such as an E1 interface). As needed, CU 110 may be implemented to communicate with DU 130 for network control and signaling.

[0039] DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 140. In some aspects, DU 130 may host one or more of the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and one or more high Physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation, etc.) at least partially according to a functional split (such as those defined by 3GPP). In some aspects, DU 130 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 130 or with the control functions hosted by CU 110.

[0040] Lower layer functionality may be implemented by one or more RUs 140. In some deployments, the RUs 140 controlled by the DU 130 may correspond to logical nodes that host RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.) or both, at least in part based on function splitting (such as lower layer function splitting). In such an architecture, the RU 140 may be implemented to handle over-the-air (OTA) communication with one or more UEs 104. In some embodiments, the real-time and non-real-time aspects of the control and user plane communication with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the implementation of the DU 130 and the CU 110 in a cloud-based RAN architecture (such as a vRAN architecture).

[0041] The SMO framework 105 may be configured to support the deployment and orchestration of RANs for both non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 105 may be configured to interact with a cloud computing platform (such as the Open Cloud (O-Cloud) 190) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements may include, but are not limited to, the CU 110, the DU 130, the RU 140, and the near RT RIC 125. In some embodiments, the SMO framework 105 may communicate with the hardware aspects of the 4G RAN (such as the Open eNB (O-eNB) 111) via the O1 interface. Additionally, in some embodiments, the SMO framework 105 may communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105.

[0042] The non-RT RIC 115 can be configured to include logic functions that can implement non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 125. The non-RT RIC 115 can be coupled to or communicate with the near-RT RIC 125 (such as via the A1 interface). The near-RT RIC 125 can be configured to include logic functions that can achieve near-real-time control and optimization of RAN elements and resources through an interface (such as via the E2 interface) via data collection and actions, and this interface (such as via the E2 interface) connects one or more CUs 110, one or more DUs 130, or both, and the O-eNB to the near-RT RIC 125.

[0043] In some specific implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 125, the non-RT RIC 115 can receive parameters or external rich information from an external server. Such information can be utilized by the near-RT RIC 125 and can be received from non-network data sources or from network functions at the SMO framework 105 or the non-RT RIC 115. In some examples, the non-RT RIC 115 or the near-RT RIC 125 can be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 can monitor long-term trends and patterns of performance and employ an AI / ML model to perform corrective actions through the SMO framework 105 (such as via reconfiguration of O1) or via creating RAN management policies (such as A1 policies).

[0044] At least one of the CU 110, DU 130, and RU 140 may be referred to as the base station 102. Thus, the base station 102 may include one or more of the CU 110, DU 130, and RU 140 (each component is indicated by a dashed line to indicate that each component may or may not be included in the base station 102). The base station 102 provides an access point to the core network 120 for the UE 104. The base station 102 may include a macro cell (high-power cellular base station) and / or a small cell (low-power cellular base station). Small cells include femtocells, picocells, and microcells. A network including both small cells and macro cells may be referred to as a heterogeneous network. The heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group called a closed subscriber group (CSG). The communication link between the RU 140 and the UE 104 may include an uplink (UL) (also referred to as a reverse link) transmission from the UE 104 to the RU 140 and / or a downlink (DL) (also referred to as a forward link) transmission from the RU 140 to the UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be through one or more carriers. For each carrier allocated in carrier aggregation with a total of up to Yx MHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use a spectrum with a bandwidth of up to Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.). These carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to the DL and UL (e.g., more or fewer carriers may be allocated for the DL compared to the UL). The component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as the primary cell (PCell) and the secondary component carriers may be referred to as secondary cells (SCells).

[0045] Some UEs 104 may use a device-to-device (D2D) communication link 158 to communicate with each other. The D2D communication link 158 may use the DL / UL wireless wide area network (WWAN) spectrum. The D2D communication link 158 may use one or more sidelink channels, such as the physical sidelink broadcast channel (PSBCH), the physical sidelink discovery channel (PSDCH), the physical sidelink shared channel (PSSCH), and the physical sidelink control channel (PSCCH). D2D communication may be through various wireless D2D communication systems, such as Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0046] The wireless communication system may further include a Wi-Fi AP 150 that communicates with the UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, e.g., in the 5 GHz unlicensed spectrum, etc. When communicating in the unlicensed spectrum, the UE 104 / AP 150 may perform a Clear Channel Assessment (CCA) before communication to determine whether the channel is available.

[0047] The electromagnetic spectrum is generally subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as Frequency Range Designation FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). Although a part of FR1 is greater than 6 GHz, in various documents and articles, FR1 is generally referred to (interchangeably) as the "sub-6 GHz" band. Regarding FR2, a similar naming issue sometimes occurs, which is generally (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the Extremely High Frequency (EHF) band (30 GHz to 300 GHz) identified by the International Telecommunication Union (ITU) as the "millimeter wave" band.

[0048] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as Frequency Range Designation FR3 (7.125 GHz to 24.25 GHz). The bands falling within FR3 may inherit FR1 characteristics and / or FR2 characteristics, and thus can effectively extend the features of FR1 and / or FR2 to the mid-band frequencies. In addition, higher bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as Frequency Range Designation FR2-2 (52.6 GHz - 71 GHz), FR4 (71 GHz - 114.25 GHz), and FR5 (114.25 GHz - 300 GHz). Each of these higher bands falls within the EHF band.

[0049] Considering the above aspects, unless otherwise specifically stated, if the term "sub-6 GHz" etc. is used in this article, it may broadly represent frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, if the term "millimeter wave" etc. is used in this article, it may broadly represent frequencies that can include mid-band frequencies, can be within FR2, FR4, FR2-2, and / or FR5, or can be within the EHF band.

[0050] Base station 102 and UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. Base station 102 may transmit beamformed signal 182 to UE 104 in one or more transmission directions. UE 104 may receive the beamformed signal from base station 102 in one or more reception directions. UE 104 may also transmit beamformed signal 184 to base station 102 in one or more transmission directions. Base station 102 may receive the beamformed signal from UE 104 in one or more reception directions. Base station 102 / UE 104 may perform beam training to determine the optimal reception direction and transmission direction for each of base station 102 / UE 104. The transmission direction and reception direction of base station 102 may be the same or may not be the same. The transmission direction and reception direction of UE 104 may be the same or may not be the same.

[0051] Base station 102 may include and / or be referred to as gNB, Node B, eNB, access point, base station transceiver, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmission reception point (TRP), network node, network entity, network equipment, or some other suitable term. Base station 102 may be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, an aggregated (monolithic) base station with a baseband unit (BBU) (including CU and DU) and an RU, or may be implemented as a disaggregated base station including one or more of CU, DU, and / or RU. A set of base stations including disaggregated base stations and / or aggregated base stations may be referred to as a next generation (NG) RAN (NG-RAN).

[0052] The core network 120 may include an Access and Mobility Management Function (AMF) 161, a Session Management Function (SMF) 162, a User Plane Function (UPF) 163, a Unified Data Management (UDM) 164, one or more Location Servers 168, and other functional entities. The AMF 161 is a control node that processes signaling between the UE 104 and the core network 120. The AMF 161 supports registration management, connection management, mobility management, and other functions. The SMF 162 supports session management and other functions. The UPF 163 supports packet routing, packet forwarding, and other functions. The UDM 164 supports the generation of Authentication and Key Agreement (AKA) credentials, user identity handling, access authorization, and subscription management. One or more Location Servers 168 are illustrated as including a Gateway Mobile Location Center (GMLC) 165 and a Location Management Function (LMF) 166. However, in general, one or more Location Servers 168 may include one or more location / locationing servers, which may include one or more of the GMLC 165, LMF 166, a Position Determination Entity (PDE), a Serving Mobile Location Center (SMLC), a Mobile Positioning Center (MPC), etc. The GMLC 165 and LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE location information. The LMF 166 receives measurements and assistance information from the NG-RAN and the UE 104 via the AMF 161 to calculate the location of the UE 104. The NG-RAN may utilize one or more positioning methods to determine the location of the UE 104. Positioning the UE 104 may involve signal measurements, position estimation, and an optional speed calculation based on these measurements. The signal measurements may be performed by the UE 104 and / or the serving base station 102. The measured signals may be based on a Satellite Positioning System (SPS) 170 (e.g., a Global Navigation Satellite System (GNSS), a Global Positioning System (GPS), a Non-Terrestrial Network (NTN), or one or more of other satellite positioning / locationing systems), an LTE signal, a Wireless Local Area Network (WLAN) signal, a Bluetooth signal, a Terrestrial Beacon System (TBS), sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), an NR Enhanced Cell ID (NR E-CID) method, an NR signal (e.g., multi-round-trip time (multi-RTT), DL Angle of Departure (DL-AoD), DL Time Difference of Arrival (DL-TDOA), UL Time Difference of Arrival (UL-TDOA), and UL Angle of Arrival (UL-AoA) positioning), and / or one or more of other systems / signals / sensors.

[0053] Examples of the UE 104 include cellular telephones, smart phones, Session Initiation Protocol (SIP) telephones, laptop computers, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, utility meters, gas pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other device with similar functionality. Some of the UEs in the UE 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). The UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, cellular phone, user agent, mobile client, client, or some other suitable term. In some scenarios, the term UE may also apply to one or more accessory devices, such as in a device cluster arrangement. One or more of these devices may access the network jointly and / or access the network individually.

[0054] Refer again to Figure 1, in some aspects, the UE 104 may include a CSI reporting and measurement component 198 (“component 198”) configured to receive information associated with a time window for channel state information (CSI) reporting from a network entity for CSI reporting, where the time window includes at least an offset from a starting position and a window size. Component 198 is also configured to send to the network entity a CSI report associated with the offset from the starting position and for the window size of the time window, where the CSI report includes CSI for codebook refinement. In some aspects, to receive information, component 198 may be configured to receive an RRC configuration of multiple offset-window size pairs, and receive in a medium access control (MAC) control element (MAC-CE) or downlink (DL) control information (DCI) an indication of an offset-window size pair to be used as the offset and window size from the multiple offset-window size pairs in the RRC configuration. In some aspects, to receive information, component 198 may be configured to receive an RRC configuration of multiple offsets and window sizes, and receive in the MAC-CE or DCI an indication of an offset to be used as the offset from the multiple offsets in the RRC configuration. In some aspects, component 198 may be configured to receive from the network entity at the offset from the starting position and during a time window having a window size a pre-coded communication having a CSI report based on CSI including CSI for codebook refinement. In certain aspects, the base station 102 may include a CSI reporting and measurement component 199 (“component 199”) configured to send for a user equipment (UE) information associated with a time window for channel state information (CSI) reporting for CSI reporting, where the time window includes at least an offset from a starting position and a window size. Component 199 is also configured to receive from the UE a CSI report associated with the offset from the starting position and for the window size of the time window, where the CSI report includes CSI for codebook refinement. In some aspects, to send information, component 199 may be configured to send an RRC configuration of multiple offset-window size pairs, and send in the MAC-CE or DCI an indication of an offset-window size pair to be used as the offset and window size from the multiple offset-window size pairs in the RRC configuration. In some aspects, to send information, component 199 may be configured to send an RRC configuration of multiple offsets and window sizes, and send in the MAC-CE or DCI an indication of an offset to be used as the offset from the multiple offsets in the RRC configuration. In some aspects, component 199 may be configured to send for the UE at the offset from the starting position and during a time window having a window size a pre-coded communication having a CSI report based on CSI including CSI for codebook refinement. Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar domains, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.In addition, while the following description may focus on UE-side prediction of channels / CSI, the concepts herein may also apply to network-side prediction.

[0055] Figure 2A FIG. 200 which is an illustration of an example of a first subframe within a 5G NR frame structure. Figure 2B FIG. 230 which is an illustration of an example of a DL channel within a 5G NR subframe. Figure 2C FIG. 250 which is an illustration of an example of a second subframe within a 5G NR frame structure. Figure 2D FIG. 280 which is an illustration of an example of a UL channel within a 5G NR subframe. The 5G NR frame structure can be frequency division duplexing (FDD) (wherein for a particular set of subcarriers (carrier system bandwidth), the subframes within that set of subcarriers are dedicated to either DL or UL), or can be time division duplexing (TDD) (wherein for a particular set of subcarriers (carrier system bandwidth), the subframes within that set of subcarriers are dedicated to both DL and UL). In Figure 2A 、 Figure 2C the examples provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (where most are DL), where D is DL, U is UL, and F is flexibly usable between DL / UL, and subframe 3 is configured with slot format 1 (where all are UL). While subframes 3, 4 are shown as having slot formats 1, 28 respectively, any particular subframe can be configured with any of the various available slot formats 0 - 61. Slot formats 0, 1 are all-DL, all-UL respectively. The other slot formats 2 - 61 include a mixture of DL, UL, and flexible symbols. The UE is configured with the slot format by receiving a slot format indicator (SFI) (configured dynamically by DL control information (DCI) or semi-statically / statically by radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0056] Figures 2A to 2DA frame structure is illustrated, and aspects of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10 ms) may be divided into 10 equal-sized subframes (1 ms). Each subframe may include one or more time slots. The subframe may also include mini-slots, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each time slot may include 14 symbols, and for extended CP, each time slot may include 12 symbols. The symbols on the DL may be cyclic prefix orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. The symbols on the UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and the parameter set. The parameter set defines the subcarrier spacing (SCS) (see Table 1). The symbol length / duration may be scaled with 1 / SCS.

[0057]

[0058] Table 1: Parameter Set, SCS, and CP

[0059] For normal CP (14 symbols / slot), the different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 time slots per subframe, respectively. For extended CP, parameter set 2 allows 4 time slots per subframe. Thus, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μ time slots / subframe. The subcarrier spacing may be equal to 2 μ * 15 kHz, where μ is parameter sets 0 to 4. Thus, the subcarrier spacing for parameter set μ = 0 is 15 kHz, and the subcarrier spacing for parameter set μ = 4 is 240 kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figures 2A to 2D An example of normal CP with 14 symbols per time slot and parameter set μ = 2 with 4 time slots per subframe is provided. The time slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency division multiplexed (see Figure 2B ). Each BWP may have a specific parameter set and CP (normal or extended).

[0060] A resource grid may be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as a physical RB (PRB)) that extends 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0061] As Figure 2A Illustrated, some of the REs in a RE carry reference (pilot) signals (RS) for a UE. The RS may include demodulation RS (DM-RS) (designated as R for a particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE. The RS may also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

[0062] Figure 2B Examples of various DL channels within a subframe of a frame are illustrated. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six resource element groups (REGs), each REG including 12 consecutive resource elements in the OFDM symbols of an RB. The PDCCH within a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring occasion on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. The primary synchronization signal (PSS) may be in symbol 2 of a particular subframe of a frame. The PSS is used by the UE 104 to determine subframe / symbol timing and the physical layer identity. The secondary synchronization signal (SSS) may be in symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE may determine the physical cell identifier (PCI). Based on the PCI, the UE may determine the location of the DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) may be logically grouped with the PSS and the SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the system frame number (SFN) and the number of RBs in the system bandwidth. The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (such as system information blocks (SIBs)), and paging messages.

[0063] As Figure 2CAs illustrated, some of the REs in the RE carry DM-RS (designated as R for a specific configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE can send the DM-RS of the physical uplink control channel (PUCCH) and the DM-RS of the physical uplink shared channel (PUSCH). The PUSCH DM-RS can be sent in the previous one or two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS can be sent in different configurations. The UE can send the sounding reference signal (SRS). The SRS can be sent in the last symbol of the subframe. The SRS can have a comb structure, and the UE can send the SRS on one of the combs in the comb structure. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

[0064] Figure 2D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH can be located at the position indicated in one configuration. The PUCCH carries uplink control information (UCI), such as a scheduling request, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and a hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and can additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0065] Figure 3It is a block diagram of the communication between the base station 310 and the UE 350 in the access network. In the DL, Internet Protocol (IP) packets can be provided to the controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes the Radio Resource Control (RRC) layer, and layer 2 includes the Service Data Adaptation Protocol (SDAP) layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the Medium Access Control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with the broadcast of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and re-ordering of RLC data PDUs; and MAC layer functionality associated with the mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0066] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to signal constellations based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The encoded and modulated symbols may then be split into parallel streams. Subsequently, each stream may be mapped to OFDM subcarriers, multiplexed with reference signals (e.g., pilots) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a stream of time-domain OFDM symbols. The OFDM stream is precoded in space to generate multiple spatial streams. Channel estimates from the channel estimator 374 may be used to determine the encoding and modulation schemes, as well as for spatial processing. The channel estimates may be derived from reference signals transmitted by the UE 350 and / or channel state feedback. Then, each spatial stream may be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier with the corresponding spatial stream for transmission.

[0067] At the UE 350, each receiver 354Rx receives signals via its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to the receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 may perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they may be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then uses a fast Fourier transform (FFT) to convert the OFDM symbol stream from the time domain to the frequency domain. The frequency-domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols and reference signals on each subcarrier are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions may be based on the channel estimates computed by the channel estimator 358. Then, the soft decisions are decoded and deinterleaved to recover the data and control signals originally transmitted by the base station 310 on the physical channel. The data and control signals are then provided to the controller / processor 359, which implements layer 3 and layer 2 functionality.

[0068] The controller / processor 359 may be associated with a memory 360 that stores program code and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using the ACK and / or NACK protocols to support HARQ operations.

[0069] Similar to the functionality described in connection with DL transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with the transfer of upper layer PDUs, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with the mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0070] Channel estimates derived by the channel estimator 358 based on reference signals or feedback transmitted by the base station 310 may be used by the TX processor 368 to select appropriate decoding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via a separate transmitter 354Tx. Each transmitter 354Tx modulates an RF carrier with a corresponding spatial stream for transmission.

[0071] UL transmissions are processed at the base station 310 in a manner similar to that described in connection with the receiver functionality at the UE 350. Each receiver 318Rx receives signals via its corresponding antenna 320. Each receiver 318Rx recovers the information modulated onto the RF carrier and provides this information to the RX processor 370.

[0072] The controller / processor 375 may be associated with a memory 376 that stores program code and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using the ACK and / or NACK protocols to support HARQ operations.

[0073] At least one of TX processor 368, RX processor 356, and controller / processor 359 may be configured to perform aspects associated with Figure 1 the CSI reporting and measurement component 198 of Figure 1 . At least one of TX processor 316, RX processor 370, and controller / processor 375 may be configured to perform aspects associated with Figure 1 the CSI reporting and measurement component 199 of Figure 1 .

[0074] Some types of wireless communication (e.g., 5G NR) may be designed to implement CSI reporting, but utilize CSI configurations that are general and also limit scheduling flexibility for UE mobility considerations. Accordingly, the information for CSI reporting at the UE side may not be fully utilized, which may have an impact on resources at both the network side and the UE side.

[0075] Aspects presented herein may provide enhanced functionality for supporting improved CSI reporting. Aspects presented herein may include, but are not limited to, configurations for starting offset and CSI window size that provide scheduling flexibility, utilize UE side measurements, and account for UE mobility, such as medium / high rate (e.g., type II Doppler), which is implemented by a network entity for specific codebook refinement. Additionally, the aspects presented provide higher data rates, higher capacity, and higher spectral efficiency for CSI reporting and measurement. For example, a UE may receive information associated with a time window (e.g., having an offset from a starting position and a window size) for CSI reporting from a network entity. The received information may be used for the configuration of the offset from the starting position and / or the configuration of the window size or related thereto for CSI reporting. The aspects described enable a UE to send CSI for codebook refinement in a CSI report, where the CSI report is associated with an offset from a starting position and is for the window size of a time window.

[0076] Figure 4 FIG. 400 is a diagram illustrating an example of CSI observation and prediction boundaries in various aspects. FIG. 400 includes time slots 402, measurement windows 404, and different window sizes (WCSI) of a total CSI window, shown as window size 406 (WCSIA), window size 408 (WCSIB), and window size 410 (WCSIC), shown with respect to time.

[0077] For aspects of CSI reporting and measurement for codebook refinement at high / medium rates, UE-side prediction can be utilized, and a down-selection can be performed for one of the following alternatives: the UE predicts the channel / CSI after time slot nref using a reference resource, the UE predicts the channel / CSI in the time slot n in which the CSI is reported, etc. For aspects of CSI reporting and measurement for codebook refinement at high / medium rates, where UE-side prediction can be utilized, a down-selection can be performed for one of the following alternatives: a time slot index 'l' greater than or equal to nref (where nref is the CSI reference resource time slot and can be a boundary), a time slot index l greater than or equal to n (where n is the reporting time slot and can be a boundary), etc.

[0078] Reference Figure 4 Referring to the illustration 400 and time slot 402 of, the CSI report is shown for time slot n, and the length of the DD / TD basis vectors is shown as N4 (where the basis vectors can have a length in the time domain but no span / window). As described and referred to herein, N4 can be a nomenclature / name given to the length of the reporting window for CSI. The measurement window 404, which is a CSI-RS measurement window in the illustrated aspect, can have a length / size [k, k + Wmeas – 1] representing the window in which CSI-RS occasions are measured for calculating the CSI report, where k can be a time slot index and Wmeas can be the measurement window length (e.g., in time slots). The CSI reporting window can have a length / size of [l, l + WCSI – 1] and can be associated with the CSI report in time slot n (e.g., transmitted via PUSCH), where l can be a time slot index and WCSI can be the reporting window length (in time slots). It should be noted that CSI can refer to resources in the time domain, and the location of the CSI reference resource can be represented as nref (time slot index).

[0079] In the context of the down-selection for a specific configuration, various aspects are now described. In a first configuration, the time slot for nref (e.g., the CSI reference resource time slot) can be used as a boundary. In such a configuration, various aspects can stipulate that:

[0080] (a): l + WCSI – 1 ≤ nref;

[0081] (b): l ≥ nref; and / or

[0082] (c): l < nref, and l + WCSI – 1 > nref.

[0083] In a second configuration, the time slot for n (e.g., the reporting time slot) can be used as a boundary. In such a configuration, various aspects can stipulate that:

[0084] (a): l + WCSI – 1 ≤ n;

[0085] (b): l ≥ n; and / or

[0086] (c): l < n, and l + WCSI – 1 > n.

[0087] In the third configuration, the end time slot of Wmeas (e.g., k + Wmeas – 1) can be used as a boundary. In such a configuration, various aspects may specify that:

[0088] (a): l + WCSI – 1 ≤ k + Wmeas – 1 (in the special case: l = k, WCSI = Wmeas);

[0089] (b): l ≥ k + Wmeas – 1; and / or

[0090] (c): l < k + Wmeas – 1, and l + WCSI – 1 > k + Wmeas – 1 (in the special case: l = k, l + WCSI = n; and / or l = k, l + WCSI > n).

[0091] In the configurations described above for illustration 400, the first configuration, the second configuration, and the third configuration can distinguish which time slots can be the boundaries of the past / observed and the future / predicted. It should also be noted that (a) the first configuration, the second configuration, and the third configuration can be used for only observation, (b) the first configuration, the second configuration, and the third configuration can be used for only prediction, and (c) the first configuration, the second configuration, and the third configuration can be used for both observation and prediction.

[0092] Figure 5 Illustration 500 is an illustration of an example of a CSI window in various aspects. Illustration 500 can be Figure 4 another aspect of illustration 400 in. Illustration 500 illustrates configuration 502 for a CSI window and configuration 510 for a CSI window, each configuration being shown as time slots relative to time.

[0093] As illustrated, configuration 502 includes an example time window 504 with a window size WCSI of N4 spanning many time slots and a corresponding offset (L) not shown for illustrative clarity. As described above for Figure 4Similar to that described in FIG. 400, CSI-RS occasions (e.g., CSI-RS received by a UE from a network entity such as a base station or a part thereof) occur in time slots up to the time slot for nref (e.g., CSI reference resource time slot). In various aspects, the CSI-RS can be counted and / or measured by the UE, and following a latency for the UE to process and generate a CSI report (report x), the CSI report can be sent (e.g., via PUSCH) to the network entity. The network entity can apply precoding based on the precoder reported in the CSI report, and then the network entity can send the scheduled DL communication (e.g., via PDSCH) with the applied precoding. Configuration 502 also shows a subsequent CSI report (report x+1) that can be aligned with report x in a similar process as corresponding to the reporting periodicity (shown for an example schedule).

[0094] Similarly, as illustrated, configuration 510 includes CSI-RS occasions (e.g., CSI-RS received by a UE from a network entity such as a base station or a part thereof) that occur in time slots up to the time slot for nref as in configuration 502, where in various aspects, the CSI-RS can be counted and / or measured by the UE, and following a latency for the UE to process and generate a CSI report (report x), the CSI report can be sent (e.g., via PUSCH) to the network entity, as in configuration 502. The network entity can apply precoding based on the precoder reported in the CSI report, and then the network entity can send the scheduled DL communication (e.g., via PDSCH) with the applied precoding. Configuration 502 also shows a subsequent CSI report (report x+1) that can be aligned with report x in configuration 510 in a similar process as corresponding to the reporting periodicity. However, the window size WCSI illustrated in configuration 510 is shown as N4 = 2, which is a smaller window size WCSI in configuration 510 than N4 in configuration 502.

[0095] Figure 6 FIG. 600 is a diagram that illustrates an example of a CSI reporting window in various aspects. FIG. 600 is also shown as time slots with respect to time and includes a time window for CSI reporting, which can be based on a start offset 602 (L) that can be an offset with respect to the time slot for nref and a window size 604 (WCSI) that can be at least partially based on the N4 and / or Tunit parameters, and during this time window, the network entity (e.g., a base station or a component of a base station) can send DL information (e.g., via PDSCH) using the CSI report (e.g., via codebook refinement). In various aspects, the window size (WCSI) can be the product of N4 and Tunit (e.g., the granularity of the time slot for CSI reporting). As an illustrative example, FIG. 600 shows N4 = 6 and Tunit = 2.

[0096] In various aspects, the start offset 602 (L) and / or the window size 604 (WCSI) can be configured in various ways / layers, jointly and / or separately (e.g., RRC, MAC-CE, DCI, etc.; which can be configured hierarchically via downselection) based on and / or associated with information related to the following: CSI / DL trigger, the number B of CSI-RS observations and / or the distance d of CSI-RS observations, the time slot for nref (CSI reference time slot), the CSI reporting time slot n, and / or the like, as described in the example aspects below and as shown in their associated figures. In one example, the starting position can be a time slot l≥nref (e.g., the CSI reference resource time slot, which can be used as a boundary), as illustrated in diagram 600; however, in another example, the starting position can be a time slot l≥n (e.g., the CSI reporting time slot, which can be used as a boundary).

[0097] Figure 7 Is a call flow diagram 700 for wireless communication in various aspects. The call flow diagram 700 illustrates, according to various aspects, for example, the CSI reporting start position and window configuration for high Doppler CSI.

[0098] In the illustrated aspect, the UE 702 sends information 706 associated with the time window for, for example, a CSI report 710 to be sent by the UE 702 to a network node (e.g., BS 704, such as one or more components of a gNB or base station as shown). In various aspects, the information 706 can include information associated with the offset from the starting position and / or the window size, from which the offset and / or window size can be identified, derived, calculated, etc. to obtain its configuration. However, in other aspects, the information 706 can include, for example, values configured for the offset from the starting position and / or the window size.

[0099] In various aspects, the information 706 received by the UE 702 and transmitted by the base station 704 may, but is not limited to, be conveyed via RRC, MAC-CE, DCI, and / or the like to obtain the configuration of the CSI report 710. In various aspects, the information 706 may be received by the UE 702 and transmitted by the base station 704 as one or more communications that may be conveyed jointly or separately (e.g., hierarchically by downselection) to / at the UE 702. In various aspects, the information 706 may include, but is not limited to, an offset (e.g., L) from a starting position and / or a window size (e.g., N4) associated with the time window for the CSI report 710 to be configured. In various aspects, receiving the information 706 may include receiving the offset from the starting position and the window size separately via RRC. In various aspects, receiving the information 706 may include receiving an RRC configuration of multiple offset-window size pairs and receiving, in the MAC-CE or DCI, an indication of the offset-window size pair to be used as the offset and the window size from among the multiple offset-window size pairs in the RRC configuration. In various aspects, receiving the information 706 may include receiving an RRC configuration of multiple offset values and window size values and receiving, in the MAC-CE or DCI, an indication of the offset value to be used as the offset from among the multiple offset values in the RRC configuration together with a previously configured window size. In various aspects, the offset from the starting position may correspond to a relative slot-level offset to a DL trigger, a CSI reference slot, or a CSI reporting slot.

[0100] In various aspects, the information 706 may include information associated with the offset from the starting position and / or the window size from which the offset and / or the window size may be identified, derived, calculated, etc. to obtain its configuration. For example, the association between the window size and the pilot length may be a linear association that may be based on the product of the number of receptions of the CSI-RS at the UE 702 and a linear parameter that may be defined or provided as part of the information 706, or may be a list association where the window size may correspond to a range of the number of receptions of the CSI-RS at the UE 702. In various aspects, the information 706 may include a minimum value and / or a maximum value of the window size, and the CSI report 710 may include a window size based on the measurement of the CSI-RS at the UE 702 during a measurement window (e.g., distance d or size Wmeas), e.g., to obtain the configuration of the window size. In various aspects, the information 706 may include an index value for a set of parameter combinations, each of which may include an associated window size and frequency parameter. In such aspects, the window size associated with the parameter combination corresponding to the index value in the set of parameter combinations may be selected by the UE 702 as the window size. In various aspects, each parameter combination in the set of parameter combinations may also include a time-domain base parameter corresponding to the respective associated window size.

[0101] In one configuration, the UE 702 may generate (at 708) a prediction of the channel state, which may be based on measurements of CSI-RS during a measurement window that may start at a CSI trigger, and the UE 702 may generate a CSI report 710 to include the CSI. In such a configuration, the CSI may include a prediction of the channel state, and the CSI report 710 may include the measurements of CSI-RS during the measurement window. That is, the CSI may include the prediction of the channel state at the UE 702, e.g., as made by the UE 702, and the CSI report 710 may include the measurements of CSI-RS at the UE 702 during the measurement window. In aspects, the window size may be included in the CSI report 710 as a parameter in the PMI information. In aspects, the generation of the CSI report 710 may be associated with the processing latency at the UE 702.

[0102] The CSI report 710 generated (e.g., at 708) by the UE may be sent to the base station 704 for applying the precoder included in the CSI report 710. The base station 704 may apply (at 712) the reported precoder based on the CSI report, e.g., for codebook refinement, which may correspond to a rate greater than or equal to a rate threshold, e.g., for high Doppler CSI, experienced by the UE. In aspects, the application of the precoder may be associated with the application latency at the base station 704.

[0103] Following the application of the precoder (at 712), a communication 714 with precoding (e.g., as applied) that may be based on the CSI report (which may include the CSI for codebook refinement) may be sent by the base station 704 and received by the UE 702. The UE 702 may thus receive, at an offset from a starting position and during a time window having a window size, the communication 714 with the applied precoding, where the applied precoding may be based on the CSI report 710 that may include the CSI for codebook refinement. The communication 714 may start at an offset from the starting position and be sent by the base station 704 and received by the UE 702 during a time window having a window size. In aspects, the communication 714 may be via the PDSCH and / or the like.

[0104] The following is now described in the context of as described above Figure 6 、 Figure 7 of Figure 8 、 Figure 9 、 Figure 10 。

[0105] Figure 8FIG. 800 is a diagram illustrating an example of CSI report configuration according to various aspects of the present disclosure. FIG. 800 includes a UE 802 and a base station 804. In various aspects, the UE 802 and the base station 804 may be configured to perform offset (L) and window size (N4) configuration from a starting position as described herein, for example, with respect to Figure 6 , Figure 7 . For example, the offset (L) and the window size (N4) from the starting position may be configured separately or jointly in DL signaling. In various aspects, the offset (L) from the starting position may be defined as a relative slot-level offset to a PDSCH trigger (CSI trigger), a CSI reference slot (nref), a CSI reporting slot, etc., as illustrated by way of example in Figure 6 .

[0106] In one configuration, for example, for a separate RRC configuration, configuration 805 may be sent from the base station 804 and received by the UE 802 with a value for the offset (L) from the starting position. In this configuration, configuration 806 may be sent from the base station 804 and received by the UE 802 with a value for the window size (N4). Configuration 805 and / or configuration 806 may be included in DL signaling such as one or more RRC messages, as illustrated. In some aspects, any combination of RRC, MAC-CE, or DCI signaling may be utilized to provide values for L and N4 to the UE 802.

[0107] In one configuration, for example, for a joint RRC configuration, configuration 808 may be sent from the base station 804 and received by the UE 802 with a value for the offset (L) from the starting position and with a value for the window size (N4). Configuration 808 may be included in DL signaling such as an RRC configuration, as illustrated. In some aspects, any combination of RRC, MAC-CE, or DCI signaling may be utilized to provide values for L and N4 to the UE 802.

[0108] In some configurations, the configuration of the offset (L) and / or the window size (N4) from the starting position may be performed hierarchically, for example, via a downselection (a joint RRC configuration with multiple values for downselection or an indication of a specific value in control signaling such as MAC-CE or DCI).

[0109] In one such configuration, an RRC configuration 810 with an offset (L) and window size (N4) pair set may be sent from the base station 804 and received by the UE 802. That is, the base station may send RRC signaling to the UE to configure a number of candidate L and N4 pairs for the UE 802. Subsequently, a configuration 812 may be sent from the base station 804 and received by the UE 802, for example, via a MAC-CE or DCI, with a downselection for a specific pair in the set of the offset (L) and window size (N4). That is, the MAC-CE or DCI may further downselect within the configured candidates and designate / identify one pair as the offset (L) and window size (N4) for the UE 802 to use for CSI reporting. As an example, this configuration is shown in diagram 800 as a set or number of L / N4 pairs each associated with an index value. The indexed L / N4 pairs may be provided from the base station 804 to the UE 802 via RRC, and subsequent MAC-CE / DCI may select the index value corresponding to a specific L / N4 pair, which may then be configured as the offset (L) and window size (N4).

[0110] In another such configuration, an RRC configuration 814 with an offset (L) and window size (N4) set may be sent from the base station 804 and received by the UE 802. That is, RRC signaling from the base station 804 may configure a number of candidate L values and values for N4 for the UE (e.g., L and N4 are configured separately in the RRC signaling). Subsequently, a configuration 816 may be sent from the base station 804 and received by the UE 802, for example, via a MAC-CE or DCI, with a downselection for a specific L value in the set of the offset (L). That is, the MAC-CE or DCI may further downselect within the configured L candidates and designate / identify a value for the offset (L) (where the window size (N4) was previously configured via RRC). As an example, this configuration is shown in diagram 800 as a set or number of L values each associated with an index value. The indexed L values may be provided from the base station 804 to the UE 802 via RRC, and subsequent MAC-CE / DCI may select the index value corresponding to a specific L value, which may then be configured as the offset (L) associated with the previously configured window size (N4).

[0111] In various aspects, the configuration of diagram 800 may be utilized by the UE 802 when generating and sending a CSI report (e.g., at 708; Figure 7 CSI report 710) to perform codebook refinement (at 712) at the base station 804 and for subsequent communication (e.g., communication 714) with pre-coded decoding reported / applied at an offset (L) from a starting position and during a time window with a window size (N4).

[0112] Figure 9 FIG. 900 is an illustration example of CSI report configurations according to various aspects of the present disclosure. FIG. 900 includes a UE 902 and a base station 904. In various aspects, the UE 902 and the base station 904 may be configured to perform, as described herein, for example, with respect to Figure 6 , Figure 7 the offset (L) and window size (N4) configurations from a starting position (CSI window length / N4 configuration based on pilot / RS measurements). For example, the CSI window length / size (N4) may be reported by the UE. That is, a UE such as UE 902 may be more aware of the rate / Doppler experienced or observed by UE 902, and thus various aspects provide that the UE determines the CSI report window length / size (N4) from within a set configured for UE 902.

[0113] As shown in FIG. 900, the configuration 906 may be sent from the base station 904 and received by the UE 902. The configuration 906 may include a minimum and / or maximum value of the window size (N4), for example, N4 assumptions from the base station 904). The UE 902 may be configured to observe and measure pilot / CSI-RS opportunities (e.g., as in Figure 6 ) and determine its N4 value based on the observation / measurement and bounded by the minimum and / or maximum value of the window size (N4). The UE 902 may then send a CSI report 908 to the base station 904 with the UE-determined value and / or the maximum value of the window size (N4). In this configuration, the CSI report 908 may include a window size that may be based on at least one measurement of CSI-RS (pilot) during a measurement window (Wmeas) at the UE 902. In such a configuration, the window size (N4) may be included in the CSI report 908 as a parameter in the precoding matrix indicator (PMI) information.

[0114] Illustration 900 also shows a configuration 910 that can be sent from base station 904 and received by UE 902. Configuration 910 can include an indication for configuring a window size (N4) based on the number of CSI-RS (pilot) occurrences. For example, more observed CSI-RS / pilots can be associated with a better ability for channel extrapolation by UE 902 / base station 904 and with a larger window. In various aspects, the distance / length (d, number of occasions NCSI, etc.) of the CSI-RS can be a basis for correlating to determine the window size (N4) based on the CSI-RS / pilot. That is, the window size (N4) can be associated with the CSI-RS / pilot length corresponding to the number of receptions of CSI-RS at UE 902 (e.g., N4 can be implicitly associated with the configured CSI-RS / pilot length). CSI-RS occasion 912 can be sent from base station 904 and received by UE 902, and UE 902 can observe / count the number of CSI-RS occasions 912. UE 902 can then determine the window size (N4) based on the observation / count for the configured CSI-RS / pilot length.

[0115] In various aspects of configuration 910, for example, to configure the window size (N4) based on the number of CSI-RS (pilot) occurrences, the association between the window size (N4) and the CSI-RS / pilot can be a linear association based on the product of the number of receptions of CSI-RS at UE 902 and a defined (e.g., known) or provided as part of the information linear parameter, can be a list association where the window size corresponds to a range of the number of receptions of CSI-RS at UE 902, etc. For example, with respect to configuration 910 and the linear association, N4 can be equal to α·NCSI, where α can be defined, e.g., known, or configured by base station 904. In other aspects, with respect to configuration 910 and the list association, an example is shown as a list in illustration 900, where N4 = 8 when the number of CSI-RS (pilot) occurrences ≤ 4, where N4 = 12 when the number of CSI-RS (pilot) occurrences > 4 and ≤ 8, and where N4 = 16 when the number of CSI-RS (pilot) occurrences > 8.

[0116] In various aspects, the configuration of illustration 900 can be utilized by UE 902 when generating and sending a CSI report (e.g., at 708; Figure 7 the CSI report 710) to perform codebook refinement at base station 904 (at 712) and for subsequent communication with pre-coding reported / applied at an offset (L) from the starting position and during a time window with window size (N4) (e.g., communication 714).

[0117] Figure 10FIG. 1000 is an illustration of an example of CSI report configuration in accordance with various aspects of the present disclosure. FIG. 1000 includes a UE 1002 and a base station 1004. In various aspects, UE 1002 and base station 1004 may be configured to perform offset (L) and window size (N4) configuration from a starting position (e.g., CSI window length / N4 associated with a parameterCombination on a time domain basis) as described herein, e.g., with respect to Figure 6 , Figure 7 . For example, the CSI window length / size (N4) may be provided to a UE such as UE 902 as a parameter of a parameter combination.

[0118] FIG. 1000 illustrates a configuration 1006 that may be sent from base station 1004 and received by UE 1002. Configuration 1006 may include values / fields for a parameter combination index or identifier, offset L, frequency domain layer information (pv), and β (e.g., where v indicates elements of a layer ({1,2} and {3,4}), window size (N4), and number (3) of time domain (TD) bases, as shown by way of example. In various aspects, each row of parameterCombination information may indicate a value (N4) for a time window, and the selection of paramCombination may be performed via RRC configuration for each CSI report configuration.

[0119] In various aspects, the configuration of FIG. 1000 may be utilized by UE 1002 when generating and sending a CSI report (e.g., at 708; Figure 7 CSI report 710) for codebook refinement at base station 1004 (at 712) and for subsequent communication (e.g., communication 714) with pre-coding reported / applied at an offset (L) from a starting position and during a time window having a window size (N4).

[0120] Figure 11 FIG. 1100 is a flow diagram of a method of wireless communication in accordance with various aspects of the present disclosure. The method may be performed by a UE (e.g., UE 104, 702, 802, 902, 1002; apparatus 1304). At 1102, the UE receives information associated with a time window for CSI reporting from a network entity for CSI reporting, where the time window includes at least an offset from a starting position and a window size. In some aspects, 1102 may be performed by component 198.

[0121] For example, referring to Figures 6 to 10, the UE 702 (802, 902, 1002) can receive information 706 (805, 806, 808, 810, 812, 814, 816, 906, 910, 912, 1006) associated with a time window for a CSI report 710 to be sent by the UE 702 (802, 902, 1002) from a network node (e.g., a base station 704 (804, 904, 1004)). In various aspects, the information 706 (906, 910) can include information associated with an offset (L) and / or a window size (N4) from a starting position, from which the offset (L) and / or the window size (N4) can be identified, derived, calculated, etc. to obtain its configuration. However, in other aspects, the information 706 (805, 806, 808, 810, 812, 814, 816, 912, 1006) can include, for example, values configured for the offset (L) and / or the window size (N4) from the starting position. In various aspects, the information 706 (805, 806, 808, 810, 812, 814, 816, 906, 910, 912, 1006) received by the UE 702 (802, 902, 1002) and sent by the base station 704 (804, 904, 1004) can be communicated, but not limited to, via RRC, MAC-CE, DCI, and / or the like to obtain the configuration of the CSI report 710. In various aspects, the information 706 (805, 806, 808, 810, 812, 814, 816) can be received by the UE 702 (802) as one or more communications that can be communicated jointly or separately (e.g., hierarchically by downselection) to / at the UE and sent by the base station 704 (804). In various aspects, the information 706 (805, 806, 808, 810, 812, 814, 816) can include, but not limited to, the offset (e.g., L) and / or the window size (N4) from the starting position associated with the time window for the CSI report 710 to be configured. In various aspects, receiving the information 706 (805, 806) can include receiving the offset (L) and the window size (N4) from the starting position via RRC separately. In various aspects, receiving the information 706 (810, 812) can include receiving an RRC configuration of a plurality of offset-window size pairs and receiving an indication of the offset-window size pair to be used as the offset and the window size from the plurality of offset-window size pairs in the RRC configuration in MAC-CE or DCI. In various aspects, receiving the information 706 (814, 816) can include receiving an RRC configuration of a plurality of offset values (L) and window size (N4) values and receiving an indication of the offset value (L) to be used as the offset (L) from the plurality of offset values in the RRC configuration in MAC-CE or DCI together with the previously configured window size (N4).In various aspects, the offset from the starting position may correspond to a relative slot-level offset to a DL trigger, a CSI reference slot, or a CSI reporting slot (CSI trigger, nref, or n).

[0122] In various aspects, the information 706 (906, 910, 912, 1006) may include information associated with the offset (L) from the starting position and / or the window size (N4), from which the offset (L) and / or the window size (N4) can be identified, derived, calculated, etc. to obtain its configuration. For example, the association between the window size (N4) and the pilot length (NCSI, d) can be a linear association that can be based on the product of the number of receptions of the CSI-RS at the UE 702 (902) and a linear parameter (α) that can be defined or provided as part of the information 706, or can be a list association where the window size (N4) can correspond to a range of the number of receptions of the CSI-RS at the UE 702 (902). In various aspects, the information 706 (906) may include the minimum and / or maximum values of the window size (N4), and the CSI report 710 may include the window size (N4) based on the measurement of the CSI-RS during a measurement window (e.g., a distance d or a size Wmeas as in Figure 6 to obtain the configuration of the window size (N4). In various aspects, the information 706 (1006) may include an index value for a set of parameter combinations that may each include an associated window size (N4) and a frequency parameter. In such aspects, the associated window size (N4) of the parameter combination corresponding to the index value in the set of parameter combinations may be selected by the UE 702 (1002) as the window size (N4). In various aspects, each parameter combination in the set of parameter combinations may also include a time-domain base parameter corresponding to the respective associated window size (N4).

[0123] At 1104, the UE sends a CSI report to a network entity that is associated with the offset from the starting position and is for the window size of a time window, where the CSI report includes CSI for codebook refinement. In some aspects, 1104 may be performed by the component 198.

[0124] For example, referring to Figures 6 to 10, in one configuration, a CSI report 710 generated (e.g., at 708) by a UE 702 (802, 902, 1002) can be sent to and received by a base station 704 (804, 904, 1004) from the UE 702 (802, 902, 1002) for applying a precoder included in the CSI report 710. The UE 702 (802, 902, 1002) can generate (at 708) a prediction of the channel state, which can be based on measurements of CSI-RS during a measurement window (Wmeas) that can start at a CSI trigger, and the UE 702 (802, 902, 1002) can generate a CSI report 710 (908) to include the CSI. In such a configuration, the CSI can include a prediction of the channel state, and the CSI report 710 (908) can include measurements of CSI-RS during the measurement window (Wmeas). That is, the CSI can include a prediction of the channel state at the UE 702 (802, 902, 1002), e.g., as made by the UE 702 (802, 902, 1002), and the CSI report 710 (908) can include measurements of CSI-RS at the UE 702 (802, 902, 1002) during the measurement window. In aspects, the window size can be included in the CSI report 710 (908) as a parameter in the PMI information. In aspects, the generation of the CSI report 710 can be associated with a processing delay at the UE 702 (802, 902, 1002). The base station 704 (804, 904, 1004) can apply (at 712) the reported precoder based on the CSI report, e.g., for codebook refinement, which can correspond to a rate greater than or equal to a rate threshold, e.g., for high Doppler CSI, experienced by the UE. In aspects, the application of the precoder (e.g., at 712) can be associated with an application delay at the base station 704 (804, 904, 1004). Following the application of the precoder (at 712), a communication 714 having a precoding (e.g., as applied) based on the CSI report (which can include CSI for codebook refinement) can be sent by the base station 704 (804, 904, 1004) and received by the UE 702 (802, 902, 1002). The UE 702 (802, 902, 1002) can thus receive, at an offset (L) from a starting position and during a time window having a window size (N4), the communication 714 having the applied precoding from a network entity, where the applied precoding can be based on the CSI report 710 that can include CSI for codebook refinement. The communication 714 can start at an offset (L) from a starting position and be sent by the base station 704 (804, 904, 1004) and received by the UE 702 (802, 902, 1002) during a time window having a window size (N4).In various aspects, communication 714 may be via the PDSCH and / or the like.

[0125] Figure 12 FIG. 1200 is a flowchart of a method of wireless communication according to various aspects of the present disclosure. The method may be performed by a network entity or a base station (e.g., base station 102; base stations 704, 804, 904, 1004; network entity 1302). At 1202, the network entity transmits information associated with a time window for CSI reporting for a UE for CSI reporting, wherein the time window includes at least an offset from a starting position and a window size. In some aspects, 1202 may be performed by component 199.

[0126] For example, referring to Figures 6 to 10, a network node (e.g., base station 704 (804, 904, 1004)) may send information 706 (805, 806, 808, 810, 812, 814, 816, 906, 910, 912, 1006) associated with a time window for a CSI report 710 to be sent by UE 702 (802, 902, 1002) as received by UE 702 (802, 902, 1002). In various aspects, the information 706 (906, 910) may include information associated with an offset (L) from a starting position and / or a window size (N4), from which the offset (L) and / or the window size (N4) can be identified, derived, calculated, etc. to obtain its configuration. However, in other aspects, the information 706 (805, 806, 808, 810, 812, 814, 816, 912, 1006) may include, for example, values configured for the offset (L) from a starting position and / or the window size (N4). In various aspects, the information 706 (805, 806, 808, 810, 812, 814, 816) received by UE 702 (802, 902, 1002) and sent by base station 704 (804, 904, 1004) may be communicated via, but not limited to, RRC, MAC-CE, DCI, and / or the like to obtain the configuration of CSI report 710. In various aspects, the information 706 (805, 806, 808, 810, 812, 814, 816) may be received by UE 702 (802) as one or more communications that may be communicated jointly or separately (e.g., hierarchically by downselection) to / at the UE and sent by base station 704 (804). In various aspects, the information 706 (805, 806, 808, 810, 812, 814, 816) may include, but not be limited to, an offset (e.g., L) from a starting position and / or a window size (N4) associated with the time window for CSI report 710 to be configured. In various aspects, receiving the information 706 (805, 806) may include receiving the offset (L) from a starting position and the window size (N4) separately via RRC sent by base station 704 (804). In various aspects, receiving the information 706 (810, 812) may include receiving an RRC configuration of multiple offset-window size pairs and receiving an indication of the offset-window size pair to be used as the offset and the window size from the multiple offset-window size pairs in the RRC configuration in MAC-CE or DCI. In various aspects, receiving the information 706 (814, 816) may include receiving an RRC configuration of multiple offset values (L) and window size (N4) values and receiving an indication of the offset value (L) to be used as the offset (L) from the multiple offset values in the RRC configuration in MAC-CE or DCI together with a previously configured window size (N4).In various aspects, the offset from the starting position may correspond to a relative slot-level offset to a DL trigger, CSI reference slot, or CSI reporting slot (CSI trigger, nref, or n).

[0127] In various aspects, the information 706 (906, 910, 912, 1006) may include information associated with the offset (L) from the starting position and / or the window size (N4), from which the offset (L) and / or the window size (N4) can be identified, derived, calculated, etc. to obtain its configuration. For example, the association between the window size (N4) and the pilot length (NCSI, d) may be a linear association that can be based on the product of the number of receptions of CSI-RS at the UE and a linear parameter (α) that can be defined or provided as part of the information 706, or it may be a list association where the window size (N4) can correspond to a range of the number of receptions of CSI-RS at the UE. In various aspects, the information 706 (906) may include the minimum and / or maximum values of the window size (N4), and the CSI report 710 may include the window size (N4) based on the measurement of CSI-RS during a measurement window (e.g., a distance d or size Wmeas as in Figure 6 to obtain the configuration of the window size (N4). In various aspects, the information 706 (1006) may include an index value for a set of parameter combinations, each of which may include an associated window size (N4) and frequency parameter. In such aspects, the associated window size (N4) of the parameter combination corresponding to the index value in the set of parameter combinations may be selected by the UE 702 (1002) as the window size (N4). In various aspects, each parameter combination in the set of parameter combinations may also include a time-domain base parameter corresponding to the respective associated window size (N4).

[0128] At 1204, the network entity receives from the UE a CSI report associated with the offset from the starting position and the window size for a time window, where the CSI report includes CSI for codebook refinement. In some aspects, 1204 may be performed by the component 199.

[0129] For example, refer to Figures 6 to 10, in one configuration, the UE 702 (802, 902, 1002) may generate (at 708) a prediction of the channel state, which may be based on measurements of CSI-RS during a measurement window (Wmeas) that may start at a CSI trigger, and the UE 702 (802, 902, 1002) may generate a CSI report 710 (908) to include the CSI. In such a configuration, the CSI may include a prediction of the channel state, and the CSI report 710 (908) may include the measurements of CSI-RS during the measurement window (Wmeas). That is, the CSI may include the prediction of the channel state at the UE 702 (802, 902, 1002), e.g., as made by the UE 702 (802, 902, 1002), and the CSI report 710 (908) may include the measurements of CSI-RS at the UE 702 (802, 902, 1002) during the measurement window. In aspects, the window size may be included in the CSI report 710 (908) as a parameter in the PMI information. In aspects, the generation of the CSI report 710 may be associated with the processing delay at the UE 702 (802, 902, 1002). The CSI report 710 generated by the UE (e.g., at 708) may be sent to the base station 704 (804, 904, 1004) for applying the precoder included in the CSI report 710. The base station 704 (804, 904, 1004) may apply (at 712) the reported precoder based on the CSI report, e.g., for codebook refinement, which may correspond to a rate greater than or equal to a rate threshold, e.g., for high Doppler CSI, experienced by the UE. In aspects, the application of the precoder (e.g., at 712) may be associated with the application delay at the base station 704 (804, 904, 1004). Following the application of the precoder (at 712), the communication 714 with precoding (e.g., as applied) that may be based on the CSI report (which may include CSI for codebook refinement) may be sent by the base station 704 (804, 904, 1004) and received by the UE 702 (802, 902, 1002). The UE 702 (802, 902, 1002) may thus receive at an offset (L) from a starting position and during a time window with a window size (N4) from a network entity (e.g., the base station 704 (804, 904, 1004)) the communication 714 precoded by the base station 704 (804, 904, 1004) as applied, where the applied precoder may be based on the CSI report 710 that may include CSI for codebook refinement. The communication 714 may start at an offset (L) from a starting position and be sent by the base station 704 (804, 904, 1004) and received by the UE 702 (802, 902, 1002) during a time window with a window size (N4).In various aspects, communication 714 can be via PDSCH and / or the like.

[0130] Figure 13FIG. 1300 is a diagram that is an example of a hardware implementation of exemplary apparatus 1304. Apparatus 1304 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, apparatus 1304 may include a cellular baseband processor 1324 (also referred to as a modem) that is coupled to one or more transceivers 1322 (e.g., cellular RF transceivers). The cellular baseband processor 1324 may include on-chip memory 1324'. In some aspects, apparatus 1304 may also include one or more subscriber identity module (SIM) cards 1320 and an application processor 1306 that is coupled to a secure digital (SD) card 1308 and a screen 1310. The application processor 1306 may include on-chip memory 1306'. In some aspects, apparatus 1304 may also include a Bluetooth module 1312, a WLAN module 1314, an SPS module 1316 (e.g., GNSS module), one or more sensor modules 1318 (e.g., barometric pressure sensor / altimeter; motion sensors such as an inertial measurement unit (IMU), gyroscope, and / or accelerometer; light detection and ranging (LIDAR), radio assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), magnetometer, audio, and / or other technologies for positioning), additional memory modules 1326, a power source 1330, and / or a camera 1332. The Bluetooth module 1312, the WLAN module 1314, and the SPS module 1316 may include on-chip transceivers (TRX) (or in some cases, only receivers (RX)). The Bluetooth module 1312, the WLAN module 1314, and the SPS module 1316 may include their own dedicated antennas and / or communicate using antenna 1380. The cellular baseband processor 1324 communicates with UE 104 and / or with an RU associated with network entity 1302 via one or more antennas 1380 through transceiver 1322. The cellular baseband processor 1324 and the application processor 1306 may each separately include computer-readable media / memory 1324', 1306'. The additional memory module 1326 may also be considered computer-readable media / memory. Each computer-readable media / memory 1324', 1306', 1326 may be non-transitory. The cellular baseband processor 1324 and the application processor 1306 are each responsible for general processing, including executing software stored on the computer-readable media / memory. The software, when executed by the cellular baseband processor 1324 / application processor 1306, causes the cellular baseband processor 1324 / application processor 1306 to perform the various functions described above. The computer-readable media / memory may also be used to store data that is manipulated by the cellular baseband processor 1324 / application processor 1306 when executing the software.The cellular baseband processor 1324 / application processor 1306 can be components of the UE 350 and can include the memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the device 1304 can be a processor chip (modem and / or application) and include only the cellular baseband processor 1324 and / or the application processor 1306, and in another configuration, the device 1304 can be the entire UE (e.g., see Figure 3 of 350) and include additional modules of the device 1304.

[0131] As discussed above, the component 198 is configured to receive information associated with a time window for channel state information (CSI) reporting from a network entity for CSI reporting, where the time window includes at least an offset from a starting position and a window size. The component 198 is also configured to send a CSI report associated with the offset from the starting position and for the window size of the time window to the network entity, where the CSI report includes CSI for codebook refinement. To receive the information, the component 198 can be configured to receive an RRC configuration of multiple offset-window size pairs and receive an indication of the offset-window size pair to be used as the offset and the window size from the multiple offset-window size pairs in the RRC configuration in a MAC-CE or DCI. To receive the information, the component 198 can be configured to receive an RRC configuration of multiple offsets and window sizes and receive an offset indication to be used as the offset from the multiple offsets in the RRC configuration in a MAC-CE or DCI. The component 198 can be configured to receive pre-coded communication with a CSI report including CSI for codebook refinement from the network entity at the offset from the starting position and during a time window with a window size. The component 198 can be further configured to perform operations related to Figure 13 、 Figure 14 in combination with those described and / or by Figure 5 、 Figure 6 、 Figure 7 、 Figure 8 、 Figure 9 、 Figure 10Any aspect among the various aspects performed by the UE in. Component 198 can be within the cellular baseband processor 1324, within the application processor 1306, or within both the cellular baseband processor 1324 and the application processor 1306. Component 198 can be one or more hardware components specifically configured to execute the process / algorithm, implemented by one or more processors configured to execute the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. As shown, device 1304 can include various components configured for various functions. In one configuration, device 1304 and specifically the cellular baseband processor 1324 and / or the application processor 1306 include components for receiving information associated with a time window for channel state information (CSI) reporting from a network entity for CSI reporting, where the time window includes at least an offset from a starting position and a window size. In this configuration, device 1304 and specifically the cellular baseband processor 1324 and / or the application processor 1306 can also include components for sending a CSI report associated with the offset from the starting position and the window size of the time window to the network entity, where the CSI report includes CSI for codebook refinement. The application processor 1306 can include components for receiving an RRC configuration of multiple offset-window size pairs, and components for receiving, in a MAC-CE or DCI, an indication of an offset-window size pair to be used as the offset and window size from among the multiple offset-window size pairs in the RRC configuration. The application processor 1306 can include components for receiving an RRC configuration of multiple offsets and window sizes, and components for receiving, in a MAC-CE or DCI, an indication of an offset to be used as the offset from among the multiple offsets in the RRC configuration. The application processor 1306 can include components for receiving pre-coded communication with a CSI report based on CSI including CSI for codebook refinement from the network entity at an offset from the starting position and during a time window having a window size. The application processor 1306 can further include components for performing in conjunction with Figure 13 、 Figure 14 in combination with the and / or by Figure 5 、 Figure 6 、 Figure 7 、 Figure 8 、 Figure 9 、 Figure 10 any aspect among the various aspects performed by the UE in. The component can be component 198 of device 1304 configured to execute the function described by the component. As described above, device 1304 can include a TX processor 368, an RX processor 356, and a controller / processor 359. Thus, in one configuration, the component can be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to execute the function described by the component.

[0132] Figure 14 FIG. 1400 is a diagram that illustrates an example of a hardware implementation of network entity 1402. Network entity 1402 can be a BS, a component of a BS, or can implement BS functionality. Network entity 1402 can include at least one of CU 1410, DU 1430, or RU 1440. For example, depending on the layer functionality handled by component 199, network entity 1402 can include CU 1410; both CU 1410 and DU 1430; each of CU 1410, DU 1430, and RU 1440; DU 1430; both DU 1430 and RU 1440; or RU 1440. CU 1410 can include CU processor 1412. CU processor 1412 can include on-chip memory 1412'. In some aspects, CU 1410 can also include additional memory module 1414 and communication interface 1418. CU 1410 communicates with DU 1430 via an intermediate link (such as the F1 interface). DU 1430 can include DU processor 1432. DU processor 1432 can include on-chip memory 1432'. In some aspects, DU 1430 can also include additional memory module 1434 and communication interface 1438. DU 1430 communicates with RU 1440 via a fronthaul link. RU 1440 can include RU processor 1442. RU processor 1442 can include on-chip memory 1442'. In some aspects, RU 1440 can also include additional memory module 1444, one or more transceivers 1446, antenna 1480, and communication interface 1448. RU 1440 communicates with UE 104. On-chip memories 1412', 1432', 1442' and additional memory modules 1414, 1434, 1444 can each be considered computer-readable media / memories. Each computer-readable media / memory can be non-transitory. Each of processors 1412, 1432, 1442 is responsible for general processing, including executing software stored on the computer-readable media / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described above. The computer-readable media / memory can also be used to store data manipulated by the processor when executing the software.

[0133] As discussed above, component 199 is configured to send information associated with a time window for channel state information (CSI) reporting to a user equipment (UE) for CSI reporting, where the time window includes at least an offset from a starting position and a window size. Component 199 is also configured to receive from the UE a CSI report associated with the offset from the starting position and for the window size of the time window, where the CSI report includes CSI for codebook refinement. To send information, component 199 may also be configured to send an RRC configuration of multiple offset-window size pairs, and send an indication in a MAC-CE or DCI of the offset-window size pair from the multiple offset-window size pairs in the RRC configuration to be used as the offset and the window size. To send information, component 199 may also be configured to send an RRC configuration of multiple offsets and window sizes, and send an offset indication in a MAC-CE or DCI of the multiple offsets from the RRC configuration to be used as the offset. Component 199 may also be configured to send pre-coded communication with a CSI report based on CSI including CSI for codebook refinement for the UE at the offset from the starting position and during the time window having the window size. Component 199 may be further configured to perform operations associated with Figure 13 , Figure 14 in combination with those described and / or by Figure 5 , Figure 6 , Figure 7 , Figure 8 , Figure 9 , Figure 10Any aspect among the aspects performed by the UE in []. Component 199 can be within one or more processors of one or more of CU 1410, DU 1430, and RU 1440. Component 199 can be one or more hardware components specifically configured to execute the process / algorithm, implemented by one or more processors configured to execute the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. Network entity 1402 can include various components configured for various functions. In one configuration, network entity 1402 includes components for sending information associated with a time window for channel state information (CSI) reporting to a user equipment (UE) for CSI reporting, where the time window includes at least an offset from a starting position and a window size. In this configuration, network entity 1402 includes components for receiving a CSI report from the UE associated with the offset from the starting position and the window size of the time window, where the CSI report includes CSI for codebook refinement. Network entity 1402 may also include components for sending an RRC configuration of multiple offset-window size pairs, and components for sending, in a MAC-CE or DCI, an indication of an offset-window size pair from the multiple offset-window size pairs in the RRC configuration to be used as the offset and the window size. Network entity 1402 may also include components for sending an RRC configuration of multiple offsets and window sizes, and components for sending, in a MAC-CE or DCI, an offset indication from the multiple offsets in the RRC configuration to be used as the offset. Network entity 1402 may also include components for sending pre-coded communication with a CSI report based on CSI including CSI for codebook refinement for the UE at an offset from the starting position and during a time window having a window size. Network entity 1402 can include components for performing any aspect among the aspects performed by the network entity (e.g., base station) in Figure 13 , Figure 14 in combination with the and / or by Figure 5 , Figure 6 , Figure 7 , Figure 8 , Figure 9 , Figure 10 . The component can be component 199 of network entity 1402 configured to execute the functions described by the component. As described above, network entity 1402 can include TX processor 316, RX processor 370, and controller / processor 375. Thus, in one configuration, the component can be TX processor 316, RX processor 370, and / or controller / processor 375 configured to execute the functions described by the component.

[0134] Some types of wireless communication (e.g., 5G NR) may be designed to implement CSI reporting, but with CSI configurations that are general and also limit scheduling flexibility for UE mobility considerations. Accordingly, the information for CSI reporting at the UE side may not be fully utilized, which may have an impact on resources at both the network side and the UE side. Aspects presented herein may provide enhancements for supporting improved CSI reporting. Aspects presented herein may include, but are not limited to, configurations for start offset (L) and CSI window size (N4), which provide scheduling flexibility, utilize UE side measurements, and account for UE mobility, such as medium / high speed (e.g., type II Doppler), which is implemented by a network entity for specific codebook refinement. Additionally, the aspects presented provide higher data rates, higher capacity, and higher spectral efficiency for CSI reporting and measurements (including UE side measurements and determinations configured for CSI reporting), as well as configurations for reducing the length of the reporting window through a flexible / adaptive window size (N4). For example, a UE may receive information from a network entity associated with a time window for CSI reporting (e.g., having an offset (L) from a start position and a window size (N4)). The received information may be used for the configuration of the offset (L) from the start position and / or the configuration of the window size (N4) or related to them for CSI reporting. The aspects described enable the UE to send CSI for codebook refinement in a CSI report, where the CSI report is associated with an offset (L) from a start position and is for a window size (N4) of a time window.

[0135] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is illustrative of example methods. It should be understood that based on design preferences, the specific order or hierarchy of the blocks in the process / flowchart may be rearranged. Further, some blocks may be combined or omitted. The appended method claims present the elements of the various blocks in a sample order, but are not limited to the specific order or hierarchy presented.

[0136] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspects described herein, but are to be accorded the full scope consistent with the language of the claims. References to elements in the singular form do not, unless specifically stated otherwise, mean "one and only one" but rather "one or more." Terms such as "if," "when," and "while" do not denote a direct temporal relationship or reaction. That is, these phrases, such as "when...," do not mean an immediate action in response to or during the occurrence of an action, but simply imply that if the condition is met, then the action will occur, without requiring a specific or immediate time limitation for the occurrence of the action. The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" is not necessarily to be construed as preferred or having an advantage over other aspects. Unless specifically stated otherwise, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "any combination of A, B, C, or any of them," including any combination of A, B, and / or C, may include multiple A's, multiple B's, or multiple C's. Specifically, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "any combination of A, B, C, or any of them" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may include one or more members of A, B, or C. A set should be construed as a collection of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If a first device receives data from or sends data to a second device, the data may be received / sent directly between the first and second devices, or indirectly between the first and second devices through a collection of devices. All structural and functional equivalents of elements of the aspects described throughout this disclosure that are known or will later be known to those of ordinary skill in the art are hereby expressly incorporated by reference herein and are covered by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public, whether or not such disclosure is expressly recited in the claims. The words "module," "mechanism," "element," "device," etc. are not to be used as a substitute for the word "component." Thus, no claim element shall be construed as a means-plus-function unless the element is expressly recited using the phrase "means for...".

[0137] As used herein, the phrase "based on" should not be construed to mean a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) should be construed as "at least based on A", unless stated otherwise specifically.

[0138] The following aspects are merely illustrative and can be combined with other aspects or teachings described herein without limitation.

[0139] Aspect 1 is a method for wireless communication at a user equipment (UE), the method comprising: receiving, from a network entity, information associated with a time window for channel state information (CSI) reporting for the CSI reporting, wherein the time window includes at least an offset from a starting position and a window size; and transmitting, to the network entity, the CSI report associated with the offset from the starting position and for the window size of the time window, wherein the CSI report includes CSI for codebook refinement.

[0140] Aspect 2 is the method according to aspect 1, wherein the information is received via at least one of radio resource control (RRC), medium access control (MAC) control element (MAC-CE), or downlink (DL) control information (DCI), and wherein the information includes the offset from the starting position and the window size.

[0141] Aspect 3 is the method according to aspect 2, wherein the offset from the starting position corresponds to a relative slot-level offset to a DL trigger, a CSI reference slot, or a CSI reporting slot.

[0142] Aspect 4 is the method according to aspects 2 and 3, wherein receiving the information includes: receiving an RRC configuration of a plurality of offset-window size pairs; and receiving, in the MAC-CE or the DCI, an indication of an offset-window size pair of the plurality of offset-window size pairs from the RRC configuration to be used as the offset and the window size.

[0143] Aspect 5 is the method according to aspects 2 and 3, wherein the offset from the starting position and the window size are received separately via the RRC.

[0144] Aspect 6 is the method according to aspects 2 and 3, wherein receiving the information includes: receiving an RRC configuration of a plurality of offsets and the window size; and receiving, in the MAC-CE or the DCI, an indication of an offset of the plurality of offsets from the RRC configuration to be used as the offset.

[0145] Aspect 7 is the method according to aspect 1, wherein the information includes at least one of a minimum value or a maximum value of the window size, and wherein the CSI report includes the window size based on at least one measurement of a CSI reference signal (CSI-RS) at the UE during a measurement window.

[0146] Aspect 8 is the method according to aspects 1 and 7, wherein the window size is included in the CSI report as a parameter in precoding matrix indicator (PMI) information.

[0147] Aspect 9 is the method according to aspect 1, wherein the window size is associated with a pilot length, and wherein the pilot length corresponds to the number of receptions of a CSI reference signal (CSI-RS) at the UE.

[0148] Aspect 10 is the method according to aspects 1 and 9, wherein the association between the window size and the pilot length is at least one of: a linear association based on a product of the number of receptions of the CSI-RS at the UE and a defined or provided as part of the information linear parameter; or wherein the window size corresponds to a list association of ranges of the number of receptions of the CSI-RS at the UE.

[0149] Aspect 11 is the method according to aspect 1, wherein the information includes an index value for a set of parameter combinations, wherein each parameter combination in the set of parameter combinations includes an associated window size and at least one frequency parameter, and wherein the associated window size of the corresponding parameter combination in the set of parameter combinations corresponding to the index value is selected as the window size.

[0150] Aspect 12 is the method according to aspects 1 and 11, wherein each parameter combination in the set of parameter combinations further includes a time domain basis parameter corresponding to the respective associated window size.

[0151] Aspect 13 is the method according to any one of aspects 1 to 12, wherein the CSI includes a prediction of the channel state at the UE, and the CSI report includes at least one measurement of a CSI reference signal (CSI-RS) at the UE during a measurement window.

[0152] Aspect 14 is the method according to any one of aspects 1 to 13, wherein the method further includes: receiving, via at least one transceiver of the UE and from the network entity, at an offset from the starting position and during the time window having the window size, a communication having precoding based on the CSI report including the CSI for codebook refinement.

[0153] Aspect 15 is a method for wireless communication at a network entity, the method comprising: sending, for a user equipment (UE), information associated with a time window for channel state information (CSI) reporting for the CSI reporting, wherein the time window comprises at least an offset from a starting position and a window size; and receiving, from the UE, the CSI report associated with the offset from the starting position and for the window size of the time window, wherein the CSI report comprises CSI for codebook refinement.

[0154] Aspect 16 is the method according to aspect 15, wherein the information is sent via at least one of radio resource control (RRC), medium access control (MAC) control element (MAC-CE), or downlink (DL) control information (DCI), and wherein the information comprises the offset from the starting position and the window size.

[0155] Aspect 17 is the method according to aspect 16, wherein the offset from the starting position corresponds to a relative slot-level offset to a DL trigger, a CSI reference slot, or a CSI reporting slot.

[0156] Aspect 18 is the method according to aspects 16 and 17, wherein sending the information comprises: sending an RRC configuration of a plurality of offset-window size pairs; and sending, in the MAC-CE or the DCI, an indication of the offset-window size pair from the plurality of offset-window size pairs in the RRC configuration to be the offset and the window size.

[0157] Aspect 19 is the method according to aspects 16 and 17, wherein the offset from the starting position and the window size are sent separately via the RRC.

[0158] Aspect 20 is the method according to aspects 16 and 17, wherein sending the information comprises: sending an RRC configuration of a plurality of offsets and the window size; and sending, in the MAC-CE or the DCI, an indication of the offset from the plurality of offsets in the RRC configuration to be the offset.

[0159] Aspect 21 is the method according to aspect 15, wherein the information comprises at least one of a minimum value or a maximum value of the window size, and wherein the CSI report comprises the window size based on at least one measurement of a CSI reference signal (CSI-RS) during a measurement window at the UE.

[0160] Aspect 22 is the method according to aspects 15 and 21, wherein the window size is included in the CSI report as a parameter in the precoding matrix indicator (PMI) information.

[0161] Aspect 23 is the method according to aspect 15, wherein the window size is associated with a pilot length, and wherein the pilot length corresponds to the number of receptions of a CSI reference signal (CSI-RS) at the UE.

[0162] Aspect 24 is the method according to aspects 15 and 23, wherein the association between the window size and the pilot length is at least one of the following: a linear association based on a product of the number of receptions of the CSI-RS at the UE and a defined or provided as part of the information linear parameter; or wherein the window size corresponds to a list association of ranges of the number of receptions of the CSI-RS at the UE.

[0163] Aspect 25 is the method according to aspect 15, wherein the information includes an index value for a set of parameter combinations, wherein each parameter combination in the set of parameter combinations includes an associated window size and at least one frequency parameter, and wherein the associated window size of the parameter combination corresponding to the index value in the set of parameter combinations is selected as the window size.

[0164] Aspect 26 is the method according to aspects 15 and 25, wherein each parameter combination in the set of parameter combinations further includes a time domain base parameter corresponding to the respective associated window size.

[0165] Aspect 27 is the method according to any one of aspects 15 to 26, wherein the CSI includes a prediction of the channel state at the UE, and the CSI report includes at least one measurement of a CSI reference signal (CSI-RS) at the UE during a measurement window.

[0166] Aspect 28 is the method according to any one of aspects 15 to 27, wherein the method further includes: transmitting, via at least one of the antennas or transceivers of the network entity and for the UE, a communication having a precoding based on the CSI report including the CSI for codebook refinement at the offset from the starting position and during the time window having the window size.

[0167] Aspect 29 is a method for wireless communication for implementing any one of aspects 1 to 28.

[0168] Aspect 30 is a device for wireless communication, the device including components for implementing any one of aspects 1 to 28.

[0169] Aspect 31 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer-executable code which, when executed by at least one processor, causes the at least one processor to implement any one of Aspects 1 to 28.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprises: a memory; and at least one processor coupled to the memory and configured to, at least in part based on stored information stored in the memory: receive, from a network entity, information associated with a time window for channel state information (CSI) reporting for the CSI reporting, wherein the time window includes at least an offset from a starting position and a window size; and send, to the network entity, the CSI report associated with the offset from the starting position and for the window size of the time window, wherein the CSI report includes CSI for codebook refinement.

2. The apparatus according to claim 1, wherein the information is received via at least one of radio resource control (RRC), medium access control (MAC) control element (MAC-CE), or downlink (DL) control information (DCI); wherein the information includes the offset from the starting position and the window size.

3. The apparatus according to claim 2, wherein the offset from the starting position corresponds to a relative slot-level offset to a DL trigger, a CSI reference slot, or a CSI reporting slot.

4. The apparatus according to claim 2, wherein, to receive the information, the at least one processor is configured to: receive an RRC configuration of a plurality of offset-window size pairs; and receive, in the MAC-CE or the DCI, an indication of the offset-window size pair to be used as the offset and the window size from the plurality of offset-window size pairs in the RRC configuration.

5. The apparatus according to claim 2, wherein the offset from the starting position and the window size are received separately via the RRC.

6. The apparatus according to claim 2, wherein, to receive the information, the at least one processor is configured to: receive an RRC configuration of a plurality of offsets and the window size; and receive, in the MAC-CE or the DCI, an indication of the offset to be used as the offset from the plurality of offsets in the RRC configuration.

7. The apparatus according to claim 1, wherein the information includes at least one of a minimum or a maximum of the window size, and wherein the CSI report includes the window size based on at least one measurement of a CSI reference signal (CSI-RS) during a measurement window at the UE.

8. The apparatus according to claim 7, wherein the window size is included in the CSI report as a parameter in precoding matrix indicator (PMI) information.

9. The apparatus according to claim 1, wherein the window size is associated with a pilot length, wherein the pilot length corresponds to the number of receptions of a CSI reference signal (CSI-RS) at the UE.

10. The apparatus according to claim 9, wherein the association between the window size and the pilot length is at least one of the following: A linear association based on a product of the number of receptions of the CSI-RS at the UE and a linear parameter defined or provided as part of the information; or A list association where the window size corresponds to a range of the number of receptions of the CSI-RS at the UE.

11. The apparatus according to claim 1, wherein the information includes an index value for a set of parameter combinations, wherein each parameter combination in the set of parameter combinations includes an associated window size and at least one frequency parameter, and wherein the associated window size of the corresponding parameter combination in the set of parameter combinations corresponding to the index value is selected as the window size.

12. The apparatus according to claim 11, wherein each parameter combination in the set of parameter combinations further includes a time-domain basis parameter corresponding to the respective associated window size.

13. The apparatus according to claim 1, wherein the CSI includes a prediction of the channel state at the UE, and the CSI report includes at least one measurement of a CSI reference signal (CSI-RS) at the UE during a measurement window.

14. The apparatus according to claim 1, wherein the at least one processor is further configured to: Receive, at the offset from the starting position and during the time window having the window size, a pre-coded communication from the network entity having a CSI report based on the CSI including the CSI for codebook refinement.

15. An apparatus for wireless communication at a network node, the apparatus comprising: A memory; And At least one processor coupled to the memory and configured, at least in part based on stored information stored in the memory, to: Transmit, for a user equipment (UE), information associated with a time window for a channel state information (CSI) report for the CSI report, wherein the time window includes at least an offset from a starting position and a window size; and Receive, from the UE, the CSI report associated with the offset from the starting position and for the window size of the time window, wherein the CSI report includes the CSI for codebook refinement.

16. The apparatus according to claim 15, wherein the information is transmitted via at least one of radio resource control (RRC), medium access control (MAC) control element (MAC-CE), or downlink (DL) control information (DCI); Wherein the information includes the offset from the starting position and the window size.

17. The apparatus according to claim 16, wherein the offset from the starting position corresponds to a relative slot-level offset to a DL trigger, a CSI reference slot, or a CSI report slot.

18. The apparatus according to claim 16, wherein, in order to transmit the information, the at least one processor is configured to: transmit RRC configurations of a plurality of offset-window size pairs; and transmit, in the MAC-CE or the DCI, an indication of an offset-window size pair to be used as the offset and the window size from among the plurality of offset-window size pairs in the RRC configuration.

19. The apparatus according to claim 16, wherein the offset and the window size from the starting position are transmitted separately via the RRC.

20. The apparatus according to claim 16, wherein, in order to transmit the information, the at least one processor is configured to: transmit RRC configurations of a plurality of offsets and the window size; and transmit, in the MAC-CE or the DCI, an offset indication of the plurality of offsets in the RRC configuration to be used as the offset.

21. The apparatus according to claim 15, wherein the information includes at least one of a minimum value or a maximum value of the window size, and wherein the CSI report includes the window size based on at least one measurement of a CSI reference signal (CSI-RS) at the UE during a measurement window.

22. The apparatus according to claim 21, wherein the window size is included in the CSI report as a parameter in precoding matrix indicator (PMI) information.

23. The apparatus according to claim 15, wherein the window size is associated with a pilot length, and wherein the pilot length corresponds to the number of receptions of a CSI reference signal (CSI-RS) at the UE.

24. The apparatus according to claim 23, wherein the association between the window size and the pilot length is at least one of the following: a linear association based on a product of the number of receptions of the CSI-RS at the UE and a defined or provided as part of the information linear parameter; or a list association where the window size corresponds to a range of the number of receptions of the CSI-RS at the UE.

25. The apparatus according to claim 15, wherein the information includes an index value for a set of parameter combinations, wherein each parameter combination in the set of parameter combinations includes an associated window size and at least one frequency parameter, and wherein the associated window size of the corresponding parameter combination corresponding to the index value in the set of parameter combinations is selected as the window size.

26. The apparatus according to claim 25, wherein each parameter combination in the set of parameter combinations further includes a time-domain basis parameter corresponding to the respective associated window size.

27. The apparatus according to claim 15, wherein the CSI includes a prediction of a channel state at the UE, and the CSI report includes at least one measurement of a CSI reference signal (CSI-RS) at the UE during a measurement window.

28. The apparatus according to claim 15, wherein the at least one processor is further configured to: Transmit a communication with precoding based on the CSI report including the CSI for codebook refinement for the UE at the offset from the starting position and during the time window having the window size.

29. A method for wireless communication at a user equipment (UE), the method comprising: receiving, from a network entity, information associated with a time window for a channel state information (CSI) report for the CSI report, wherein the time window includes at least an offset from a starting position and a window size; and transmitting, to the network entity, the CSI report associated with the offset from the starting position and for the window size of the time window, wherein the CSI report includes CSI for codebook refinement.

30. A method for wireless communication at a network entity, the method comprising: transmitting, for a user equipment (UE), information associated with a time window for a channel state information (CSI) report for the CSI report, wherein the time window includes at least an offset from a starting position and a window size; and receiving, from the UE, the CSI report associated with the offset from the starting position and for the window size of the time window, wherein the CSI report includes CSI for codebook refinement.

Images