CQI and PMI reporting based on frequency selectivity

Abstract

The network node may transmit the CSI-RS to the UE. The UE may send, to the network node, a CSI report corresponding to at least one UE-selected bandwidth portion of a downlink BWP based on the CSI-RS. The CSI report may include at least one CQI for a bandwidth portion selected by the at least one UE of the downlink BWP. The downlink BWP may be associated with a full duplex operation.

Description

[0001] Cross - Reference to Related Applications

[0002] This application claims the benefit of U.S. Non - Provisional Patent Application Serial No. 18 / 066,268, entitled "FREQUENCY SELECTIVITY BASED CQI AND PMI REPORTING", filed on December 14, 2022, which is hereby incorporated by reference in its entirety. Technical Field

[0003] The present disclosure generally relates to communication systems, and more particularly to channel state information (CSI) reporting in full - duplex wireless communication systems. Background Art

[0004] 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 multiple access technologies that are 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.

[0005] 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 evolution of mobile broadband promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with 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). Some aspects of 5G NR may be based on the 4G Long - Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. These improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the Invention

[0006] A simplified summary of one or more aspects is presented below 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.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and a device are provided. The device may be a user equipment (UE). The device may receive a CSI reference signal (CSI-RS) from a network node. The device may send a CSI report corresponding to at least one UE-selected bandwidth part of a downlink bandwidth part (BWP) to the network node based on the CSI-RS.

[0008] In one aspect of the present disclosure, a method, a computer-readable medium, and a device are provided. The device may be a network node. The device may send a CSI-RS to a UE. The device may receive a CSI report corresponding to at least one UE-selected bandwidth part of a downlink BWP from the UE based on the CSI-RS.

[0009] To achieve the foregoing and related purposes, one or more aspects include the features described in detail 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 are indicative of 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 is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0012] Figure 2B is a diagram illustrating an example of downlink (DL) channels within a subframe according to various aspects of the present disclosure.

[0013] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0014] Figure 2D is a diagram illustrating an example of uplink (UL) channels within a subframe according to various aspects of the present disclosure.

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

[0016] Figure 4 Illustrates a first example and a second example of in-band full-duplex (IBFD) resources and a third example of sub-band full-duplex (SBFD) resources.

[0017] Figure 5 Is a diagram illustrating various example deployment scenarios including one or more full-duplex devices.

[0018] Figure 6 Is a diagram illustrating an example time slot format of an example SBFD time slot.

[0019] Figure 7 Is a diagram illustrating an example scenario where a UE may experience interference.

[0020] Figure 8 Is a diagram of a communication flow of a method for link adaptation.

[0021] Figure 9 Is a diagram illustrating an example CSI framework for dynamic antenna port adaptation.

[0022] Figure 10 Is a diagram illustrating an example sub-band channel quality indicator report according to one or more aspects.

[0023] Figure 11 Is a diagram of a communication flow of a method for wireless communication.

[0024] Figure 12 Is a flowchart of a method for wireless communication.

[0025] Figure 13 Is a flowchart of a method for wireless communication.

[0026] Figure 14 Is a flowchart of a method for wireless communication.

[0027] Figure 15 Is a flowchart of a method for wireless communication.

[0028] Figure 16 Is a diagram illustrating an example of a hardware implementation for an example device and / or network entity.

[0029] Figure 17 Is a diagram illustrating an example of a hardware implementation for an example network entity. Detailed Description

[0030] In the case where the channel does not experience significant frequency selectivity, for most subbands, the offset between the subband (or "subband") CQI and the wideband CQI (e.g., the wideband may correspond to the entire downlink BWP) can be zero or close to zero. Both differential subband CQI reporting and absolute subband CQI reporting can be associated with reporting overhead (e.g., 2 bits for differential reporting and 4 bits for absolute reporting). However, in the case where the channel has low frequency selectivity (i.e., the channel conditions do not change significantly across the spectrum), the bits used for subband CQI reporting may be redundant.

[0031] According to one or more aspects, a network node may send CSI-RS to a UE. The UE may send a CSI report corresponding to at least one UE-selected bandwidth part of the downlink BWP to the network node based on the CSI-RS. Thus, the CSI overhead can be reduced. In addition, less subband CQI and / or precoding matrix indicator (PMI) processing may be performed at the UE, which can result in lower power consumption at the UE.

[0032] The detailed description set forth below in connection with the accompanying drawings is a description of various configurations and does 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 description includes 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.

[0033] Several aspects of a telecommunications system are presented with reference to various apparatuses and methods. These apparatuses and methods are described in the following detailed description and illustrated in the drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements can 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.

[0034] 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, system on a chip (SoC), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic components, 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, executable files, execution threads, procedures, functions, or any combination thereof, regardless of whether it is referred to as software, firmware, middleware, microcode, hardware description language, or other terms.

[0035] 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 on a computer-readable medium as one or more instructions or code. 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 that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0036] While aspects, embodiments, and / or use cases are described by way of 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, aspects, embodiments, and / or use cases may be implemented 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.). While some examples may or may not be specifically targeted at a use case or application, the examples described may have broad applicability. 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 practical settings, devices incorporating the aspects and features described 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.

[0037] 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 can 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.

[0038] A centralized base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A split base station may be configured to utilize a protocol stack 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).

[0039] Base station operation or network design may consider the aggregation 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 initiated by the O-RAN Alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). The splitting may include distributing functions across two or more units at various physical locations, as well as virtualizing the function of at least one unit, which may enable 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.

[0040] 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 a 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.

[0041] 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 an 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.

[0042] 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 utilize an interface that is configured to convey 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 specific implementations, CU 110 may be logically divided 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 the E1 interface. As needed, CU 110 may be implemented to communicate with DU 130 for network control and signaling.

[0043] 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, Medium 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 function 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 utilize an interface that is configured to convey signals with other layers (and modules) hosted by DU 130 or with the control functions hosted by CU 110.

[0044] Lower layer functionality can be implemented by one or more RUs 140. In some deployments, the RUs 140 controlled by the DU 130 can 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 partially based on function splitting such as lower layer function splitting. In such an architecture, the RU 140 can 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 plane communication and user plane communication with the RU 140 can be controlled by the corresponding DU 130. In some scenarios, this configuration can enable the implementation of the DU 130 and CU 110 in a cloud-based RAN architecture (such as a vRAN architecture).

[0045] The SMO framework 105 can 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 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operation and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 105 can 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 can include, but are not limited to, the CU 110, DU 130, RU 140, and near RT RIC 125. In some embodiments, the SMO framework 105 can 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 can communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 105 can also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105.

[0046] The non-RT RIC 115 can be configured to include logic functions that enable 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 enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via the E2 interface), which connects one or more CUs 110, one or more DUs 130, or both, and the O-eNB to the near-RT RIC 125.

[0047] In some embodiments, 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 enrichment 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 via the SMO framework 105 (such as via reconfiguration of O1) or via creation of RAN management policies (such as A1 policies).

[0048] At least one of CU 110, DU 130, and RU 140 may be referred to as base station 102. Thus, base station 102 may include one or more of 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 base station 102). Base station 102 provides an access point to core network 120 for UE 104. Base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Small cells include femto cells, pico cells, and micro cells. 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 referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include an uplink (UL) (also referred to as a reverse link) transmission from UE 104 to RU 140 and / or a downlink (DL) (also referred to as a forward link) transmission from RU 140 to 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 via one or more carriers. For each carrier allocated in carrier aggregation of up to a total of Yx MHz (x component carriers) for transmission in each direction, 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 DL and UL (e.g., more or fewer carriers may be allocated for DL compared to UL). Component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carriers may be referred to as secondary cells (SCells).

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

[0050] 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, for example, in an unlicensed spectrum such as the 5 GHz unlicensed spectrum. 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.

[0051] 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 (interchangeably) referred to 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 - 300 GHz) identified by the International Telecommunication Union (ITU) as the "millimeter wave" band.

[0052] 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 - 24.25 GHz). The bands falling within FR3 may inherit the characteristics of FR1 and / or FR2, 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.

[0053] Considering the above aspects, unless otherwise specifically stated, if the term "sub-6 GHz" etc. is used in this document, 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 document, 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.

[0054] 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 and transmission directions for each of base station 102 / UE 104. The transmission and reception directions of base station 102 may be the same or may not be the same. The transmission and reception directions of UE 104 may be the same or may not be the same.

[0055] Base station 102 may include and / or be referred to as a 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 and 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 a CU and a DU) and an RU, or as a disaggregated base station including one or more of a CU, a DU, and / or an 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).

[0056] 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, generally speaking, 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 measurement 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, location estimation, and 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 / location 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 departure angle (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL arrival angle (UL-AoA) positioning), and / or one or more of other systems / signals / sensors.

[0057] Examples of the UE 104 include cellular phones, smart phones, Session Initiation Protocol (SIP) phones, 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, electricity 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, cell phone, user agent, mobile client, client, or some other suitable term. In some scenarios, the term UE may also apply to one or more companion devices, such as in a device constellation arrangement. One or more of these devices may access the network jointly and / or access the network individually.

[0058] Referring again to Figure 1 , in some aspects, the UE 104 may include a CSI component 198, which may be configured to receive CSI-RS from a network node. The CSI component 198 may be configured to send a CSI report corresponding to at least one UE-selected bandwidth part of the downlink BWP to the network node based on the CSI-RS. In some aspects, the base station 102 may include a CSI component 199, which may be configured to send CSI-RS to the UE. The CSI component 199 may be configured to receive a CSI report corresponding to at least one UE-selected bandwidth part of the downlink BWP from the UE based on the CSI-RS. Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar fields, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0059] Figure 2A is a diagram 200 illustrating an example of a first subframe within the 5G NR frame structure. Figure 2B is a diagram 230 illustrating an example of a DL channel within a 5G NR subframe. Figure 2C is a diagram 250 illustrating an example of a second subframe within the 5G NR frame structure. Figure 2DFIG. 280 is an illustration of an example of UL channels 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 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 example 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). Although 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 the received slot format indicator (SFI) (configured dynamically by downlink 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.

[0060] Figures 2A to 2D The frame structure is illustrated, and aspects of the present disclosure can be applicable to other wireless communication technologies that may have different frame structures and / or different channels. One frame (10 ms) can be divided into 10 equal - sized subframes (1 ms). Each subframe can include one or more slots. A subframe can also include mini - slots, which can include 7, 4, or 2 symbols. Each slot can include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each slot can include 14 symbols, and for extended CP, each slot can include 12 symbols. The symbols on the DL can be cyclic prefix orthogonal frequency division multiplexing (CP - OFDM) symbols. The symbols on the UL can 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 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 can scale with 1 / SCS.

[0061]

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

[0063] For normal CP (14 symbols / slot), different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Thus, for normal CP and parameter set μ, there are 14 symbols / slot and 2μ slots / subframe. The subcarrier spacing can be equal to 2μ * 15 kHz, where μ is from parameter set 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 slot and parameter set μ = 2 with 4 slots per subframe is provided. The 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 can have a specific parameter set and CP (normal or extended).

[0064] A resource grid can be used to represent the frame structure. Each slot includes a resource block (RB) (also known as a physical RB (PRB)) that extends over 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.

[0065] As Figure 2A illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. The RS can include demodulation RS (DM-RS) (indicated as R for one 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 can also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

[0066] Figure 2BIllustrates examples of various DL channels within a subframe of a frame. 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), where each CCE includes six Resource Element Groups (REGs), and each REG includes 12 consecutive Resource Elements (REs) in the OFDM symbols of an RB. The PDCCH within a BWP can be referred to as a Control Resource Set (CORESET). The UE is configured to monitor PDCCH candidates in the PDCCH search space (e.g., common search space, UE-specific search space) during PDCCH monitoring occasions on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs can be located at higher and / or lower frequencies on the channel bandwidth. The Primary Synchronization Signal (PSS) can be in symbol 2 of a specific subframe of the frame. The PSS is used by the UE 104 to determine subframe / symbol timing and the physical layer identity. The Secondary Synchronization Signal (SSS) can be in symbol 4 of a specific subframe of the 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 can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The Physical Broadcast Channel (PBCH) carrying the Master Information Block (MIB) can be logically grouped with the PSS and 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 sent via the PBCH (such as System Information Blocks (SIBs)), and paging messages.

[0067] As Figure 2C Illustrated, some of the REs carry DM-RS (indicated as R for a specific configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS can be transmitted in the previous one or two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is transmitted and depending on the specific PUCCH format used, the PUCCH DM-RS can be transmitted in different configurations. The UE can transmit a Sounding Reference Signal (SRS). The SRS can be transmitted in the last symbol of a subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the teeth of the comb. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

[0068] Figure 2DIllustrates examples of various UL channels within a subframe of a frame. 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.

[0069] Figure 3 Is a block diagram of a base station 310 in an access network communicating with a UE 350. In the DL, Internet Protocol (IP) packets can be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a media 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), radio access technology (RAT) - to - 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.

[0070] 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 the signal constellation based on various modulation schemes such as binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase phase shift keying (M-PSK), and M-quadrature amplitude modulation (M-QAM). The encoded and modulated symbols are then split into parallel streams. Each stream is then 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 can be used to determine the encoding and modulation schemes, as well as for spatial processing. The channel estimates can be derived from reference signals transmitted by the UE 350 and / or channel condition feedback. Each spatial stream is then provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx modulates a radio frequency (RF) carrier with the corresponding spatial stream for transmission.

[0071] 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 on each subcarrier, as well as the reference signals, 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. The soft decisions are then 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.

[0072] 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.

[0073] 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.

[0074] 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 may modulate an RF carrier with a corresponding spatial stream for transmission.

[0075] 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 the information to the RX processor 370.

[0076] 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.

[0077] At least one of TX processor 368, RX processor 356, and controller / processor 359 may be configured to perform aspects related to Figure 1 CSI component 198 of

[0078] At least one of TX processor 316, RX processor 370, and controller / processor 375 may be configured to perform aspects related to Figure 1 CSI component 199 of

[0079] Figure 4 Illustrates a first example 400 and a second example 410 of in-band full-duplex (IBFD) resources and a third example 420 of sub-band full-duplex (SBFD) resources. In IBFD, signals can be transmitted and received in overlapping time and overlapping frequencies. As shown in the first example 400, the time and frequency allocation of UL resource 402 may completely overlap with the time and frequency allocation of DL resource 404. In the second example 410, the time and frequency allocation of UL resource 412 may partially overlap with the time and frequency allocation of DL resource 414.

[0080] IBFD is contrasted with sub-band frequency-division duplexing (FDD), where uplink and downlink resources can overlap in time using different frequencies, as shown in the third example 420. In the third example 420, UL resource 422 is separated from DL resource 424 by a guard band 426. The guard band can be a frequency resource provided between UL resource 422 and DL resource 424, or a gap in the frequency resource. Separating the UL frequency resource from the DL frequency resource using a guard band can help reduce self-interference. UL resources and DL resources that are adjacent to each other correspond to a guard band width of 0. Since the output signal (e.g., from the UE transmitter) can extend outside the UL resource, the guard band can reduce the interference experienced by the UE. Sub-band FDD may also be referred to as "flexible duplexing".

[0081] Figure 5FIG. 500 is a diagram illustrating various example deployment scenarios that include one or more full-duplex devices. A full-duplex device (or a device operating in full-duplex mode) can transmit and receive simultaneously. FIG. 510 illustrates an example deployment scenario that includes at least one full-duplex network node and two half-duplex UEs. Operating in full-duplex mode, the first network node 512 can transmit to the second UE 518 and receive from the first UE 516 simultaneously. Full-duplex operation can create SI at the first network node 512. In particular, at the first network node 512, the downlink transmission to the second UE 518 can cause interference to the uplink reception from the first UE 516. In addition, the uplink transmission from the first UE 516 to the first network node 512 can cause cross-link interference (CLI) to the downlink reception of the second UE 518 from the first network node 512. In addition, the transmission from the second network node 514 can cause CLI to the uplink reception at the first network node 512.

[0082] FIG. 530 illustrates an example deployment scenario that includes at least one full-duplex network node and at least one full-duplex UE / customer premises equipment (CPE). The first network node 532 can communicate with the first UE / CPE 536 in full-duplex mode. In other words, uplink and downlink transmissions can occur simultaneously between the first network node 532 and the first UE / CPE 536. At the same time, the first network node 532 can transmit to the second UE / CPE 538. The downlink transmissions to both the first UE / CPE 536 and the second UE / CPE 538 can cause SI to the uplink reception from the first UE / CPE 536 at the first network node 532. In addition, the uplink transmission from the first UE / CPE 536 can cause SI to the downlink reception at the first UE / CPE 536 and can cause CLI to the downlink reception at the second UE / CPE 538. In addition, the transmission from the second network node 534 can cause CLI to the uplink reception at the first network node 532.

[0083] FIG. 550 illustrates an example deployment scenario including two half-duplex network nodes (or two transmit receive points (TRPs)) and at least one full-duplex UE / CPE. The first UE / CPE 556 may operate in full-duplex mode. In particular, the first UE / CPE 556 may transmit to the first network node 552 and receive from the second network node 554 simultaneously. Thus, the uplink transmission from the first UE / CPE 556 to the first network node 552 may cause SI to the downlink reception at the first UE / CPE 556. In addition, the second network node 554 may transmit to the second UE / CPE 558 while transmitting to the first UE / CPE 556. The downlink transmission from the second network node 554 to both the first UE / CPE 556 and the second UE / CPE 558 may cause CLI to the uplink reception at the first network node 552. In addition, the uplink transmission from the first UE / CPE 456 to the first network node 552 may cause CLI to the downlink reception at the second UE / CPE 558.

[0084] Figure 6 FIG. is an illustration of an example time slot format exemplifying an example SBFD time slot 600. The SBFD time slot 600 may be a "DL+UL" ("D+U") time slot, where the frequency band may be used for both UL transmission and DL transmission. As shown, the SBFD time slot 600 may accommodate one or more DL control channels 602, SRS resources 604 (e.g., for a first UE (UE1) and a second UE (UE2)), one or more UL control channels 606, one or more DL data channels 608 for UE1, one or more DL data channels 610 for UE2, and / or a PUSCH 612 for UE1. The "D+U" time slot (e.g., the SBFD time slot 600) may include DL symbols that do not allow UL transmission, UL symbols that do not allow DL transmission, or full-duplex (e.g., "D+U") symbols. In addition, DL and UL transmissions may occur in an overlapping frequency band (e.g., IBFD) or adjacent frequency bands (e.g., SBFD). In particular, in a given "D+U" symbol in the "D+U" time slot, a half-duplex UE may transmit in the UL frequency band or receive in the DL frequency band, while a full-duplex UE may transmit in the UL frequency band and / or receive in the DL frequency band in the same time slot.

[0085] Figure 7FIG. 700 is a diagram illustrating an example scenario in which a UE may experience interference. In the scenario illustrated in FIG. 710, a first UE 714 and a second UE 716 that may be located in the same cell corresponding to a first network node 712 may operate in a half-duplex mode. In addition, the first network node 712 may operate in a full-duplex mode (e.g., IBFD or sub-band FDD). As illustrated in FIG. 710, an uplink transmission from the first UE 714 to the first network node 712 may cause in-cell CLI on the downlink reception from the first network node 712 at the second UE 716. In addition, the second UE 716 may also experience inter-cell interference from a second network node 718.

[0086] In the scenario illustrated in FIG. 750, a first UE 754 and a second UE 756 that may be located in different adjacent cells corresponding to a first network node 752 and a second network node 758, respectively, may operate in a half-duplex mode. As illustrated in FIG. 750, an uplink transmission from the first UE 754 to the first network node 752 may cause inter-cell CLI on the downlink reception from the second network node 758 at the second UE 756.

[0087] In addition, as described above, a UE operating in a full-duplex mode may experience SI.

[0088] In one or more configurations, a CSI reporting configuration (also referred to as a CSI reporting setting) may include one or more of the following: a non-zero power (NZP) CSI-RS resource configuration for channel measurement, a CSI-RS resource for interference measurement (IM) (CSI-IM), an NZP CSI-RS configuration for IM, a codebook configuration, or a reporting type configuration (e.g., periodic reporting, semi-persistent reporting, aperiodic reporting, etc.). The NZP CSI-RS resource configuration for channel measurement may correspond to an NZP CMR set among a plurality of NZP channel measurement resource (CMR) sets. The NZP CMR set may include a plurality of NZP CMRs. In addition, the CSI-IM may correspond to a CSI-IM resource set among a plurality of CSI-IM resource sets. The CSI-IM resource set may include a plurality of CSI-IM resources. In addition, the NZP CSI-RS configuration for IM may correspond to an NZP IMR set among a plurality of NZP interference measurement resource (IMR) sets. The NZP IMR set may include a plurality of NZP IMRs. There may be a resource-wise association between the NZP CMR and the CSI-IM resource. In addition, each CSI-IM resource may be associated with all IMRs.

[0089] In addition, the codebook configuration may specify a codebook type (e.g., type I - single panel, type I - multi-panel, type II, etc.). The codebook type may be associated with an antenna configuration (e.g., (N1, N2) or (Ng , N1, N2) configuration and DFT beam restriction, where N1 can be the number of columns of antenna elements in the panel, N2 can be the number of rows of antenna elements in the panel, and N g can be the number of panels) and is associated with RI restriction.

[0090] In one or more configurations, the CSI reporting configuration can be the RRC configured for each BWP. Additionally, the resource set can have Ks resources (Ks is a positive integer), where each of the Ks resources can include the same number of CSI-RS ports. For example, for Ks = 1, each resource can contain at most 32 CSI-RS ports. For Ks = 2, each resource can contain at most 16 CSI-RS ports. Additionally, for 2 < Ks <= 8, each resource can contain at most 8 CSI-RS ports. Generally speaking, in some configurations, the P-port (P is a positive integer) resource can have ports labeled from 3000 to 300(P - 1).

[0091] For the codebook configuration, different types of PMI codebook reports can be available. For example, the PMI codebook report types can include type I - single panel, type I - multi-panel, type II - single panel, type II - port selection, or type II - enhanced port selection. Additionally, for the antenna configuration, the supported configuration of the antenna element configuration (N1, N2) and the number of panels (N g ) as well as the corresponding number of CSI-RS antenna ports (per resource) (which can be equal to 2 * N g * N1 * N2) can be specified. For example, Table 5.2.2.2.1-2 of Technical Specification (TS) 38.214 can specify the supported configurations of (N1, N2) and (O1, O2), and Table 5.2.2.2.2-1 of TS 38.214 can specify the supported configurations of (N g , N1, N2) and (O1, O2).

[0092] In one or more configurations, the CSI report can be one of two types. In particular, the type I CSI report can be a single-slot report. The CSI report can include up to 2 parts: Part 1 can include the RI / C SI-RS resource indicator (CRI) and the CQI of the first codeword, and Part 2 can include the PMI and the CQI of the second codeword (e.g., when RI is greater than 4). For the type I CSI report, periodic / semi-persistent / aperiodic reporting can be supported. The type I CSI report can be carried via PUCCH and / or PUSCH (PUCCH and / or PUSCH can be short or long). Additionally, the type I subband CSI report can be carried via PUSCH and / or long PUCCH.

[0093] In addition, a type II CSI report may also include up to two parts: Part 1 may include RI, CQI, and an indication of the number of non-zero wideband amplitude coefficients for each layer, and Part 2 may include the PMI corresponding to the indicated non-zero wideband amplitude coefficients for each layer as reported in Part 1. Part 1 may be associated with a fixed payload size, and each field in Part 1 may be encoded separately. Thus, Part 1 can be used to identify the number of information bits in Part 2. For type II CSI reports, semi-persistent / aperiodic reporting may be supported. The type II CSI report may be carried via long PUCCH (Part 1 but not Part 2) and / or PUSCH (Part 1 and Part 2).

[0094] In some configurations, the reported CSI parameters may not be multiplexed across PUCCH or PUSCH transmissions. Additionally, CSI reports on long PUCCH and PUSCH may be calculated independently. Whether a UE can be configured with type II CSI reports on both long PUCCH and PUSCH may depend on the UE capabilities. Further, when carrying the type II CSI report via long PUCCH or PUSCH, the layer 1 reference signal received power (L1-RSRP) and the resource indicator for beam management may be mapped to Part 1.

[0095] Figure 8 FIG. 800 is a diagram of a communication flow of a method for link adaptation. At 806, network node 804 may transmit CSI-RS (which may be M t -port CSI-RS) (Mt is a positive integer) for UE 802. At 808, UE 802 may perform DL channel estimation based on the CSI-RS. At 810, UE 802 may calculate CSI parameters including RI, PMI, and / or CQI. In particular, for M r ×M t downlink channel matrix (H) and codebooks from rank 1 to rank R: {{P1(0),..., P1(L1 - 1)},..., {P R (0),..., P R (L R - 1)}} (M r may be the number of receive antennas (or antenna elements) and M t may be the number of transmit antennas (or antenna elements)), UE 802 may select a pre-coder (associated with PMI index i*) and a rank (R*) for a given codebook: (R*, i*) = argmax r，i SE est (H, P r (i)), where SE est (H, P r (i)) may refer to the SE that UE 802 can achieve with H and Pr (i) Spectrum efficiency estimation performed under given conditions. Thus, the optimal rank can be R* and the optimal precoder can be P R *(i*). The CQI calculation at UE 802 can be conditional on the optimal rank and precoder:

[0096] At 812, UE 802 can send a CSI report to network node 804. The CSI report can include RI, PMI, and / or CQI. At 814, network node 804 can perform UE scheduling and can determine the rank, precoding matrix, and / or modulation and coding scheme (MCS) based on the CSI report. At 816, network node 804 can send PDCCH / PDSCH for UE 802 based on UE scheduling and the determined rank, precoding matrix, and / or MCS.

[0097] Figure 9 is a diagram illustrating an example CSI framework 900 for dynamic antenna port adaptation. As shown, the CSI report configuration can include a resource setting 904 and a codebook configuration 906. The resource setting 904 can correspond to a CSI-RS resource 908 (e.g., 32 ports). In addition, the codebook configuration 906 can include beam and RI limitations 910 for different antenna port configurations (e.g., (N1, N2) configuration).

[0098] Thus, the UE can be configured with multiple codebooks in the CSI report configuration 902. Each codebook can be associated with an antenna port configuration (e.g., (N1, N2) configuration), which can include beam limitations and RI limitations. Resources for CSI measurement can be shared among the configured codebooks. In addition, the UE can send a CSI report to the network node. The CSI report can include CSI parameters associated with a subset of the codebooks. Thus, the UE can calculate the CSI parameters for each codebook and can sort the CSI parameters (e.g., based on spectrum efficiency). Then, the UE can report one best CSI parameter or a subset of the best CSI parameters in the same CSI report.

[0099] In some configurations, the subband CQI can be a differential CQI relative to the wideband CQI (e.g., having a length of 2 bits). For example, Table 5.2.2.1-1 can specify the mapping from subband differential CQI values to offset values, where the offset values can indicate the index offset between the subband CQI index and the wideband CQI index. In some other configurations, the subband CQI can be a subband absolute CQI (e.g., having a length of 4 bits).

[0100] In the case where the channel does not experience significant frequency selectivity, for most subbands, the offset between the subband CQI and the wideband CQI can be zero or close to zero. Both differential subband CQI reporting and absolute subband CQI reporting can be associated with reporting overhead (e.g., 2 bits for differential reporting and 4 bits for absolute reporting). However, in the case where the channel has low frequency selectivity (i.e., the channel conditions do not vary significantly across the spectrum), the bits used for subband CQI reporting may be redundant.

[0101] Accordingly, in some aspects, the UE can implicitly report that the channel has low frequency selectivity. Then, the UE can avoid explicitly reporting subband CQI and / or PMI when transmitting the CSI report. Thus, the bits associated with subband CQI and / or PMI reporting can be saved, resulting in more efficient CSI-RS report compression.

[0102] On the other hand, in a full-duplex network, the channel quality can have certain characteristics. For example, on average, the channel may become better as the separation between the DL subband and the UL subband increases. Accordingly, frequency selectivity can be reported on a per-subband basis.

[0103] Therefore, in some aspects, the UE can implicitly indicate the low frequency selectivity of the channel to the network node. Thus, the CSI overhead can be reduced. In addition, less subband CQI and / or PMI processing can be performed at the UE, which can result in lower power consumption at the UE.

[0104] Figure 10 FIG. 1000 is a diagram illustrating an example subband CQI report according to one or more aspects.

[0105] In one configuration, the UE can be configured with a set of subband sizes and a certain number of subbands for each sub-BWP / subband such that the UE can select the subbands for which the UE can explicitly report CQI and / or PMI. In some configurations, the UE can be restricted to certain combinations of subbands for which CQI and / or PMI can be explicitly reported. The subbands in each combination can be within the corresponding sub-BWP. The UE can indicate to the network node the combination selected by the UE before transmitting the CSI report including CQI and / or PMI. For example, in the case where there are 4 options corresponding to 4 possible combinations of subbands, the UE can send a 2-bit indication to the network node to indicate the selected option. In some configurations, the reporting can be performed via a two-stage UCI message. In particular, the UE can indicate, via a first-stage UCI message, the combination of the selected subbands for which CQI and / or PMI are to be (explicitly) reported. Then, the UE can report the subband CQI and / or PMI of the subbands in the selected combination via a second-stage UCI message.

[0106] As shown in Figure 1010, the combination of subbands selected by the UE may include 5 subbands that do not cover the entire wideband. These 5 subbands may include 2 subbands in the first sub-BWP (sub-BWP1), 2 subbands in the second sub-BWP (sub-BWP2), and 1 subband in the third sub-BWP (sub-BWP3). The UE may explicitly report CQI and / or PMI for these 5 subbands but not for other subbands in the CSI report.

[0107] In some configurations, from the perspective of the UE, the combination of subbands selected by the UE can be used as an indication of the preferred RBs (for transmission and / or reception). For example, the 5 subbands shown in Figure 1010 may correspond to the RBs preferred by the UE. Based on this understanding, the network node may use these RBs for transmission to the UE.

[0108] In some configurations, a table (e.g., pre-specified or based on RRC configuration) can be defined to provide the possible subband sizes and the number of subbands for each bandwidth. Table 2 below can be an example of such a table.

[0109]

[0110] Table 2. Subband sizes and the number of subbands for different bandwidths

[0111] In addition to this table, the UE can be (pre-)configured with multiple possible subband configurations. Figure 1030 can illustrate 3 example pre-configured subband configurations, where 4 subbands can be specified according to each configuration in the configuration. The UE can explicitly report the CQI and / or PMI of the 4 subbands associated with the subband configuration selected by the UE. Therefore, the UE can indicate the subband configuration selected by the UE to the network node before sending the CSI report including CQI and / or PMI.

[0112] In some configurations, a UE configured to report subband CQI / PMI with a specific subband size may discard or combine subbands in the CSI report according to the variability of the CQI / PMI on the subbands. Therefore, in addition to reporting the CQI / PMI values in the CSI report, the UE can also report the subband size. In some configurations, a two-stage UCI message can be used for reporting. For example, the UE can indicate the size (and possibly the location) of the subbands for which CQI and / or PMI are to be explicitly reported via the first-stage UCI message. Then, the UE can report the subband CQI and / or PMI of the subbands via the second-stage UCI message.

[0113] For example, in a case where all sub-bands have the same CQI as the wideband, it may be sufficient to report the CQI / PMI of one sub-band having the same size (bandwidth) as the entire wideband. In another example, as shown in diagram 1050, the UE may split the wideband into two sub-bands, where the first sub-band may have the same CQI / PMI as the wideband, while the second sub-band may have a different CQI / PMI.

[0114] Figure 11 Diagram 1100 is a diagram of the communication process 1100 of a method of wireless communication. The UE 1102 may implement aspects of the UE 104 / 350. Additionally, the network node 1104 may implement aspects of the base station 102 / 310. In some configurations, at 1106, the UE 1102 may send an indication of the downlink sub-band configuration selected by the UE to the network node 1104 before sending a CSI report at 1112.

[0115] In some configurations, at 1108, the UE 1102 may send an indication of a plurality of bandwidths corresponding to a plurality of UE-selected bandwidth parts (e.g., sub-bands) in the downlink BWP to the network node 1104.

[0116] At 1110, the network node 1104 may send CSI-RS to the UE 1102.

[0117] At 1112, the UE 1102 may send a CSI report corresponding to at least one UE-selected bandwidth part of the downlink BWP to the network node 1104 based on the CSI-RS.

[0118] In one configuration, the CSI report at 1112 may include at least one CQI of at least one UE-selected bandwidth part of the downlink BWP.

[0119] In one configuration, at least one UE-selected bandwidth part of the downlink BWP may correspond to at least one downlink sub-band associated with the UE-selected downlink sub-band configuration among a plurality of available downlink sub-band configurations.

[0120] In one configuration, at least one UE-selected bandwidth part of the downlink BWP may include a plurality of downlink sub-bands associated with the UE-selected downlink sub-band configuration.

[0121] In one configuration, each available downlink sub-band configuration among a plurality of available downlink sub-band configurations may be associated with a specified number of sub-bands specifying the sub-band size.

[0122] In one configuration, a plurality of available downlink sub-band configurations may be pre-configured.

[0123] In one configuration, multiple available downlink sub-band configurations may be configured at the UE 1102 based on RRC signaling from the network node 1104.

[0124] In one configuration, at least one UE-selected bandwidth part of a downlink BWP may include a single UE-selected bandwidth part corresponding to the entire downlink BWP.

[0125] In one configuration, at least one UE-selected bandwidth part of a downlink BWP may include multiple UE-selected bandwidth parts in the downlink BWP. The CSI report at 1112 may include the corresponding CQI of each UE-selected bandwidth part among the multiple UE-selected bandwidth parts.

[0126] In one configuration, the downlink BWP may be associated with full-duplex operation.

[0127] Figure 12 FIG. 1200 is a flowchart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104 / 350 / 1102; apparatus 1604). At 1202, the UE may receive CSI-RS from a network node. For example, 1202 may be performed by Figure 16 component 198 in. Refer to Figure 11 , at 1110, the UE 1102 may receive CSI-RS from the network node 1104.

[0128] At 1204, the UE may send a CSI report corresponding to at least one UE-selected bandwidth part of the downlink BWP to the network node based on the CSI-RS. For example, 1204 may be performed by Figure 16 component 198 in. Refer to Figure 11 , at 1112, the UE 1102 may send a CSI report corresponding to at least one UE-selected bandwidth part of the downlink BWP to the network node 1104 based on the CSI-RS.

[0129] Figure 13 FIG. 1300 is a flowchart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104 / 350 / 1102; apparatus 1604). At 1306, the UE may receive CSI-RS from a network node. For example, 1306 may be performed by Figure 16 component 198 in. Refer to Figure 11 , at 1110, the UE 1102 may receive CSI-RS from the network node 1104.

[0130] At 1308, the UE may send a CSI report corresponding to at least one UE-selected bandwidth part of the downlink BWP to the network node based on the CSI-RS. For example, 1308 may be performed byFigure 16 is performed by component 198 in Figure 11 At 1112, the UE 1102 may send a CSI report corresponding to at least one UE-selected bandwidth part of the downlink BWP to the network node 1104 based on the CSI-RS.

[0131] In one configuration, referring to Figure 11 the CSI report at 1112 may include at least one CQI of at least one UE-selected bandwidth part of the downlink BWP.

[0132] In one configuration, at least one UE-selected bandwidth part of the downlink BWP may correspond to at least one downlink subband associated with the UE-selected downlink subband configuration among multiple available downlink subband configurations.

[0133] In one configuration, at least one UE-selected bandwidth part of the downlink BWP may include multiple downlink subbands associated with the UE-selected downlink subband configuration.

[0134] In one configuration, at 1302, the UE may send an indication of the UE-selected downlink subband configuration to the network node before sending the CSI report. For example, 1302 may be performed by Figure 16 component 198 in Figure 11 At 1112, the UE1102 may send an indication of the UE-selected downlink subband configuration to the network node 1104 before sending the CSI report at 1112.

[0135] In one configuration, the multiple available downlink subband configurations may be pre-configured.

[0136] In one configuration, referring to Figure 11 the multiple available downlink subband configurations may be configured based on RRC signaling from the network node 1104.

[0137] In one configuration, each available downlink subband configuration among the multiple available downlink subband configurations may be associated with a specified number of subbands specifying the subband size.

[0138] In one configuration, at least one UE-selected bandwidth part of the downlink BWP may include a single UE-selected bandwidth part corresponding to the entire downlink BWP.

[0139] In one configuration, at least one UE-selected bandwidth part of the downlink BWP may include multiple UE-selected bandwidth parts in the downlink BWP. Referring to Figure 11, the CSI report at 1112 may include the corresponding CQI of each UE-selected bandwidth part among multiple UE-selected bandwidth parts.

[0140] In one configuration, at 1304, the UE may send an indication of multiple bandwidths corresponding to multiple UE-selected bandwidth parts in the downlink BWP to a network node. For example, 1304 may be performed by Figure 16 component 198 in. Refer to Figure 11 , at 1108, UE 1102 may send an indication of multiple bandwidths corresponding to multiple UE-selected bandwidth parts in the downlink BWP to network node 1104.

[0141] In one configuration, the downlink BWP may be associated with full-duplex operation.

[0142] Figure 14 is a flowchart 1400 of a method for wireless communication. The method may be performed by a network node (e.g., base station 102 / 310; network node 1104; network entity 1602). At 1402, the network node may send CSI-RS to the UE. For example, 1402 may be performed by Figure 17 component 199 in. Refer to Figure 11 , at 1110, network node 1104 may send CSI-RS to UE 1102.

[0143] At 1404, the network node may receive a CSI report corresponding to at least one UE-selected bandwidth part of the downlink BWP from the UE based on the CSI-RS. For example, 1404 may be performed by Figure 17 component 199 in. Refer to Figure 11 , at 1112, network node 1104 may receive a CSI report corresponding to at least one UE-selected bandwidth part of the downlink BWP from UE 1102 based on the CSI-RS.

[0144] Figure 15 is a flowchart 1500 of a method for wireless communication. The method may be performed by a network node (e.g., base station 102 / 310; network node 1104; network entity 1602). At 1506, the network node may send CSI-RS to the UE. For example, 1506 may be performed by Figure 17 component 199 in. Refer to Figure 11 , at 1110, network node 1104 may send CSI-RS to UE 1102.

[0145] At 1508, the network node may receive a CSI report corresponding to at least one UE-selected bandwidth part of the downlink BWP from the UE based on the CSI-RS. For example, 1508 may be performed byFigure 17 is performed by component 199 in Figure 11 At 1112, network node 1104 may receive a CSI report corresponding to at least one UE-selected bandwidth part of the downlink BWP from UE 1102 based on CSI-RS.

[0146] In one configuration, referring to Figure 11 the CSI report at 1112 may include at least one CQI of at least one UE-selected bandwidth part of the downlink BWP.

[0147] In one configuration, at least one UE-selected bandwidth part of the downlink BWP may correspond to at least one downlink subband associated with a UE-selected downlink subband configuration among multiple available downlink subband configurations.

[0148] In one configuration, at least one UE-selected bandwidth part of the downlink BWP may include multiple downlink subbands associated with a UE-selected downlink subband configuration.

[0149] In one configuration, at 1502, the network node may receive an indication of a UE-selected downlink subband configuration from the UE before receiving the CSI report. For example, 1502 may be performed by Figure 17 component 199 in Figure 11 At 1106, network node 1104 may receive an indication of a UE-selected downlink subband configuration from UE 1102 before receiving the CSI report at 1112.

[0150] In one configuration, the multiple available downlink subband configurations may be pre-configured.

[0151] In one configuration, referring to Figure 11 the multiple available downlink subband configurations may be configured based on RRC signaling from network node 1104.

[0152] In one configuration, each available downlink subband configuration among the multiple available downlink subband configurations may be associated with a specified number of subbands specifying a subband size.

[0153] In one configuration, at least one UE-selected bandwidth part of the downlink BWP may include a single UE-selected bandwidth part corresponding to the entire downlink BWP.

[0154] In one configuration, at least one UE-selected bandwidth part of the downlink BWP may include multiple UE-selected bandwidth parts in the downlink BWP. Referring to Figure 11, the CSI report at 1112 may include the respective CQI of each UE-selected bandwidth part among a plurality of UE-selected bandwidth parts.

[0155] In one configuration, at 1504, the network node may receive an indication of a plurality of bandwidths corresponding to a plurality of UE-selected bandwidth parts in the downlink BWP from the UE. For example, 1504 may be performed by Figure 17 component 199 in. Refer to Figure 11 , at 1108, the network node 1104 may receive an indication of a plurality of bandwidths corresponding to a plurality of UE-selected bandwidth parts in the downlink BWP from the UE1102.

[0156] In one configuration, the downlink BWP may be associated with full-duplex operation.

[0157] Figure 16FIG. 1600 is a diagram illustrating an example of a hardware implementation for apparatus 1604. Apparatus 1604 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, apparatus 1604 may include a cellular baseband processor 1624 (also referred to as a modem) coupled to one or more transceivers 1622 (e.g., cellular RF transceivers). The cellular baseband processor 1624 may include on-chip memory 1624'. In some aspects, apparatus 1604 may also include one or more subscriber identity module (SIM) cards 1620 and an application processor 1606, which is coupled to a secure digital (SD) card 1608 and a screen 1610. The application processor 1606 may include on-chip memory 1606'. In some aspects, apparatus 1604 may also include a Bluetooth module 1612, a WLAN module 1614, an SPS module 1616 (e.g., GNSS module), one or more sensor modules 1618 (e.g., an atmospheric pressure sensor / altimeter; motion sensors such as an inertial measurement unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio aided detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1626, a power source 1630, and / or a camera 1632. The Bluetooth module 1612, the WLAN module 1614, and the SPS module 1616 may include on-chip transceivers (TRX) (or in some cases, only receivers (RX)). The Bluetooth module 1612, the WLAN module 1614, and the SPS module 1616 may include their own dedicated antennas and / or communicate using antenna 1680. The cellular baseband processor 1624 communicates with UE 104 and / or with a RU associated with network entity 1602 via one or more antennas 1680 through transceiver 1622. The cellular baseband processor 1624 and the application processor 1606 may each separately include computer-readable media / memory 1624', 1606'. The additional memory module 1626 may also be considered computer-readable media / memory. Each computer-readable media / memory 1624', 1606', 1626 may be non-transitory. The cellular baseband processor 1624 and the application processor 1606 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 1624 / application processor 1606, causes the cellular baseband processor 1624 / application processor 1606 to perform the various functions described above. The computer-readable media / memory may also be used to store data manipulated by the cellular baseband processor 1624 / application processor 1606 when executing the software.The cellular baseband processor 1624 / application processor 1606 can be a component of the UE 350 and can include the memory 360 and / or at least one of the TX processor 368, RX processor 356, and controller / processor 359. In one configuration, the device 1604 can be a processor chip (modem and / or application) and include only the cellular baseband processor 1624 and / or application processor 1606, and in another configuration, the device 1604 can be the entire UE (e.g., see. Figure 3 of 350) and include additional modules of the device 1604.

[0158] As discussed above, the component 198 is configured to receive CSI-RS from a network node. The component 198 is configured to send a CSI report corresponding to at least one UE-selected bandwidth part of the downlink BWP to the network node based on the CSI-RS. The component 198 can be within the cellular baseband processor 1624, application processor 1606, or both the cellular baseband processor 1624 and application processor 1606. The component 198 can be one or more hardware components specifically configured to perform the stated processes / algorithms, implemented by one or more processors configured to perform the stated processes / algorithms, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. As shown, the device 1604 can include various components configured for various functions. In one configuration, the device 1604 (and particularly the cellular baseband processor 1624 and / or application processor 1606) includes means for receiving CSI-RS from a network node. The device 1604 (and particularly the cellular baseband processor 1624 and / or application processor 1606) includes means for sending a CSI report corresponding to at least one UE-selected bandwidth part of the downlink BWP to the network node based on the CSI-RS.

[0159] In one configuration, the CSI report may include at least one CQI of at least one UE-selected bandwidth part of a downlink BWP. In one configuration, at least one UE-selected bandwidth part of a downlink BWP may correspond to at least one downlink subband associated with a UE-selected downlink subband configuration among a plurality of available downlink subband configurations. In one configuration, at least one UE-selected bandwidth part of a downlink BWP may include a plurality of downlink subbands associated with a UE-selected downlink subband configuration. In one configuration, apparatus 1604 (and in particular the cellular baseband processor 1624 and / or the application processor 1606) includes means for sending an indication of the UE-selected downlink subband configuration to a network node before transmitting the CSI report. In one configuration, the plurality of available downlink subband configurations may be preconfigured. In one configuration, the plurality of available downlink subband configurations may be configured based on RRC signaling from a network node. In one configuration, each available downlink subband configuration among the plurality of available downlink subband configurations may be associated with a specified number of subbands specifying a subband size. In one configuration, at least one UE-selected bandwidth part of a downlink BWP may include a single UE-selected bandwidth part corresponding to the entire downlink BWP. In one configuration, at least one UE-selected bandwidth part of a downlink BWP may include a plurality of UE-selected bandwidth parts in the downlink BWP. The CSI report may include the respective CQI of each UE-selected bandwidth part among the plurality of UE-selected bandwidth parts. In one configuration, apparatus 1604 (and in particular the cellular baseband processor 1624 and / or the application processor 1606) includes means for sending an indication of a plurality of bandwidths corresponding to a plurality of UE-selected bandwidth parts in the downlink BWP to a network node. In one configuration, the downlink BWP may be associated with full-duplex operation.

[0160] The means may be component 198 of apparatus 1604 configured to perform the functions recited by the means. As described above, apparatus 1604 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Thus, in one configuration, the means may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions recited by the means.

[0161] Figure 17FIG. 1700 is a diagram illustrating an example of a hardware implementation for a network entity 1702. The network entity 1702 can be a BS, a component of a BS, or can implement BS functionality. The network entity 1702 can include at least one of a CU 1710, a DU 1730, or an RU 1740. For example, depending on the layer functionality handled by component 199, the network entity 1702 can include the CU 1710; both the CU 1710 and the DU 1730; each of the CU 1710, the DU 1730, and the RU 1740; the DU 1730; both the DU 1730 and the RU 1740; or the RU 1740. The CU 1710 can include a CU processor 1712. The CU processor 1712 can include on-chip memory 1712'. In some aspects, the CU 1710 can also include an additional memory module 1714 and a communication interface 1718. The CU 1710 communicates with the DU 1730 via an intermediate link such as an F1 interface. The DU 1730 can include a DU processor 1732. The DU processor 1732 can include on-chip memory 1732'. In some aspects, the DU 1730 can also include an additional memory module 1734 and a communication interface 1738. The DU 1730 communicates with the RU 1740 via a fronthaul link. The RU 1740 can include an RU processor 1742. The RU processor 1742 can include on-chip memory 1742'. In some aspects, the RU 1740 can also include an additional memory module 1744, one or more transceivers 1746, an antenna 1780, and a communication interface 1748. The RU 1740 communicates with a UE 104. The on-chip memories 1712', 1732', 1742' and the additional memory modules 1714, 1734, 1744 can each be considered a computer-readable medium / memory. Each computer-readable medium / memory can be non-transitory. Each of the processors 1712, 1732, 1742 is responsible for general processing, including executing software stored on the computer-readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the processor when executing the software.

[0162] As discussed above, component 199 is configured to send CSI-RS to the UE. Component 199 is configured to receive a CSI report corresponding to at least one UE-selected bandwidth part of the downlink BWP from the UE based on the CSI-RS. Component 199 may be within one or more processors of one or more of CU1710, DU 1730, and RU 1740. Component 199 may be one or more hardware components specifically configured to perform the stated processes / algorithms, implemented by one or more processors configured to perform the stated processes / algorithms, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. Network entity 1702 may include various components configured for various functions. In one configuration, network entity 1702 may include components for sending CSI-RS to the UE. Network entity 1702 includes components for receiving a CSI report corresponding to at least one UE-selected bandwidth part of the downlink BWP from the UE based on the CSI-RS.

[0163] In one configuration, the CSI report may include at least one CQI for at least one UE-selected bandwidth part of the downlink BWP. In one configuration, at least one UE-selected bandwidth part of the downlink BWP may correspond to at least one downlink subband associated with the UE-selected downlink subband configuration among multiple available downlink subband configurations. In one configuration, at least one UE-selected bandwidth part of the downlink BWP may include multiple downlink subbands associated with the UE-selected downlink subband configuration. In one configuration, network entity 1702 includes components for receiving an indication of the UE-selected downlink subband configuration from the UE before receiving the CSI report. In one configuration, the multiple available downlink subband configurations may be pre-configured. In one configuration, the multiple available downlink subband configurations may be configured based on RRC signaling from a network node. In one configuration, each available downlink subband configuration among the multiple available downlink subband configurations may be associated with a specified number of subbands specifying a subband size. In one configuration, at least one UE-selected bandwidth part of the downlink BWP may include a single UE-selected bandwidth part corresponding to the entire downlink BWP. In one configuration, at least one UE-selected bandwidth part of the downlink BWP may include multiple UE-selected bandwidth parts in the downlink BWP. The CSI report may include the corresponding CQI for each UE-selected bandwidth part among the multiple UE-selected bandwidth parts. In one configuration, network entity 1702 includes components for receiving an indication of multiple bandwidths corresponding to multiple UE-selected bandwidth parts in the downlink BWP from the UE. In one configuration, the downlink BWP may be associated with full-duplex operation.

[0164] A component can be a component 199 of network entity 1702 configured to perform the functions recited by the component. As described above, network entity 1702 can include a TX processor 316, an RX processor 370, and a controller / processor 375. Thus, in one configuration, a component can be the TX processor 316, the RX processor 370, and / or the controller / processor 375 configured to perform the functions recited by the component.

[0165] Re-reference Figures 4 to 17 , the network node can send CSI-RS to the UE. The UE can send a CSI report corresponding to at least one UE-selected bandwidth part of the downlink BWP to the network node based on the CSI-RS. Thus, the CSI overhead can be reduced. In addition, less subband CQI and / or PMI processing can be performed at the UE, which can result in lower power consumption at the UE.

[0166] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is merely 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 can be rearranged. Additionally, some blocks can 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.

[0167] 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 generic 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, and elements recited in the singular are not intended to mean "one and only one" but rather "one or more." Terms such as "if," "when," and "while" do not imply 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 rather simply imply that the action will occur if the condition is met, without 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" means 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 them," including any combination of A, B, and / or C, may include multiple As, multiple Bs, or multiple Cs. 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 them" can 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 contain 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 transmits data to a second device, the data may be received / transmitted 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 the elements of the various aspects described throughout this disclosure that are known or later will be known to those of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public, whether or not such disclosure is explicitly recited in the claims. The words "module," "mechanism," "element," "device," etc. shall not be used in place of 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..."

[0168] 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.

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

[0170] Aspect 1 is a method for wireless communication at a UE, the method comprising: receiving CSI-RS from a network node; and transmitting a CSI report corresponding to at least one UE-selected bandwidth part of a downlink BWP to the network node based on the CSI-RS.

[0171] Aspect 2 is the method according to aspect 1, wherein the CSI report includes a CQI of the at least one UE-selected bandwidth part of the downlink BWP.

[0172] Aspect 3 is the method according to any one of aspects 1 and 2, wherein the at least one UE-selected bandwidth part of the downlink BWP corresponds to at least one downlink subband associated with a UE-selected downlink subband configuration among a plurality of available downlink subband configurations.

[0173] Aspect 4 is the method according to aspect 3, wherein the at least one UE-selected bandwidth part of the downlink BWP includes a plurality of downlink subbands associated with the UE-selected downlink subband configuration.

[0174] Aspect 5 is the method according to any one of aspects 3 and 4, the method further comprising: transmitting an indication of the UE-selected downlink subband configuration to the network node before transmitting the CSI report.

[0175] Aspect 6 is the method according to any one of aspects 3 to 5, wherein the plurality of available downlink subband configurations are pre-configured.

[0176] Aspect 7 is the method according to any one of aspects 3 to 5, wherein the plurality of available downlink subband configurations are configured based on RRC signaling from the network node.

[0177] Aspect 8 is the method according to any one of aspects 3 to 7, wherein each available downlink subband configuration among the plurality of available downlink subband configurations is associated with a specified number of subbands specifying a subband size.

[0178] Aspect 9 is the method according to any one of Aspects 1 and 2, wherein the at least one UE-selected bandwidth part of the downlink BWP includes a single UE-selected bandwidth part corresponding to the entire downlink BWP.

[0179] Aspect 10 is the method according to any one of Aspects 1 and 2, wherein the at least one UE-selected bandwidth part of the downlink BWP includes a plurality of UE-selected bandwidth parts in the downlink BWP, and the CSI report includes the corresponding CQI of each UE-selected bandwidth part among the plurality of UE-selected bandwidth parts.

[0180] Aspect 11 is the method according to Aspect 10, the method further comprising: sending an indication of a plurality of bandwidths corresponding to the plurality of UE-selected bandwidth parts in the downlink BWP to the network node.

[0181] Aspect 12 is the method according to any one of Aspects 1 to 11, wherein the downlink BWP is associated with full-duplex operation.

[0182] Aspect 13 is a method for wireless communication at a network node, the method comprising: sending CSI-RS to a UE; and receiving, based on the CSI-RS, a CSI report corresponding to at least one UE-selected bandwidth part of a downlink BWP from the UE.

[0183] Aspect 14 is the method according to Aspect 13, wherein the CSI report includes the CQI of the at least one UE-selected bandwidth part of the downlink BWP.

[0184] Aspect 15 is the method according to any one of Aspects 13 and 14, wherein the at least one UE-selected bandwidth part of the downlink BWP corresponds to at least one downlink subband associated with a UE-selected downlink subband configuration among a plurality of available downlink subband configurations.

[0185] Aspect 16 is the method according to Aspect 15, wherein the at least one UE-selected bandwidth part of the downlink BWP includes a plurality of downlink subbands associated with the UE-selected downlink subband configuration.

[0186] Aspect 17 is the method according to any one of Aspects 15 and 16, the method further comprising: receiving an indication of the UE-selected downlink subband configuration from the UE before receiving the CSI report.

[0187] Aspect 18 is the method according to any one of Aspects 15 to 17, wherein the plurality of available downlink subband configurations are pre-configured.

[0188] Aspect 19 is the method according to any one of Aspects 15 to 17, wherein the plurality of available downlink subband configurations are configured based on RRC signaling from the network node.

[0189] Aspect 20 is the method according to any one of Aspects 15 to 19, wherein each of the plurality of available downlink subband configurations is associated with a specified number of subbands specifying a subband size.

[0190] Aspect 21 is the method according to any one of Aspects 13 and 14, wherein the at least one UE-selected bandwidth part of the downlink BWP includes a single UE-selected bandwidth part corresponding to the entire downlink BWP.

[0191] Aspect 22 is the method according to any one of Aspects 13 and 14, wherein the at least one UE-selected bandwidth part of the downlink BWP includes a plurality of UE-selected bandwidth parts in the downlink BWP, and the CSI report includes a respective CQI for each of the plurality of UE-selected bandwidth parts.

[0192] Aspect 23 is the method according to Aspect 22, the method further comprising: receiving, from the UE, an indication of a plurality of bandwidths corresponding to the plurality of UE-selected bandwidth parts in the downlink BWP.

[0193] Aspect 24 is the method according to any one of Aspects 13 to 23, wherein the downlink BWP is associated with full-duplex operation.

[0194] Aspect 25 is a device for wireless communication, the device including at least one processor, the at least one processor being coupled to a memory, and at least partially based on information stored in the memory, the at least one processor being configured to implement the method according to any one of Aspects 1 to 24.

[0195] Aspect 26 can be combined with Aspect 25 and further includes a transceiver coupled to the at least one processor.

[0196] Aspect 27 is a device for wireless communication, the device including components for implementing any one of Aspects 1 to 24.

[0197] Aspect 28 is a non-transitory computer-readable storage medium storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of Aspects 1 to 24.

[0198] Various aspects have been described herein. These aspects, and others, are within the scope of the following claims.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: a memory; and at least one processor coupled to the memory, and at least partially based on information stored in the memory, the at least one processor is configured to: receive a channel state information reference signal (CSI-RS) from a network node; and send, based on the CSI-RS, a channel state information (CSI) report corresponding to at least one UE-selected bandwidth part of a downlink bandwidth part (BWP) to the network node.

2. The apparatus according to claim 1, wherein the CSI report includes at least one channel quality indicator (CQI) of the at least one UE-selected bandwidth part of the downlink BWP.

3. The apparatus according to claim 1, wherein the at least one UE-selected bandwidth part of the downlink BWP corresponds to at least one downlink subband associated with a UE-selected downlink subband configuration among a plurality of available downlink subband configurations.

4. The apparatus according to claim 3, wherein the at least one UE-selected bandwidth part of the downlink BWP includes a plurality of downlink subbands associated with the UE-selected downlink subband configuration.

5. The apparatus according to claim 3, the at least one processor is configured to: send an indication of the UE-selected downlink subband configuration to the network node before sending the CSI report.

6. The apparatus according to claim 3, wherein the plurality of available downlink subband configurations are pre-configured.

7. The apparatus according to claim 3, wherein the plurality of available downlink subband configurations are configured based on radio resource control (RRC) signaling from the network node.

8. The apparatus according to claim 3, wherein each of the plurality of available downlink subband configurations is associated with a specified number of subbands specifying a subband size.

9. The apparatus according to claim 1, wherein the at least one UE-selected bandwidth part of the downlink BWP includes a single UE-selected bandwidth part corresponding to the entire downlink BWP.

10. The apparatus according to claim 1, wherein the at least one UE-selected bandwidth part of the downlink BWP includes a plurality of UE-selected bandwidth parts in the downlink BWP, and the CSI report includes corresponding channel quality indicators (CQIs) of each of the plurality of UE-selected bandwidth parts.

11. The apparatus according to claim 10, the at least one processor is further configured to: send an indication of a plurality of bandwidths corresponding to the plurality of UE-selected bandwidth parts in the downlink BWP to the network node.

12. The apparatus according to claim 1, wherein the downlink BWP is associated with full-duplex operation.

13. The device according to claim 1, wherein the device further comprises: A transceiver coupled to the at least one processor, the transceiver being configured to receive the CSI-RS and transmit the CSI report.

14. A method for wireless communication at a user equipment (UE), the method comprising: Receiving, from a network node, a channel state information reference signal (CSI-RS); And Transmitting, based on the CSI-RS, a channel state information (CSI) report corresponding to at least one UE-selected bandwidth part of a downlink bandwidth part (BWP) to the network node.

15. The method according to claim 14, wherein the CSI report comprises at least one channel quality indicator (CQI) of the at least one UE-selected bandwidth part of the downlink BWP.

16. An apparatus for wireless communication at a network node, the apparatus comprising: A memory; And At least one processor, the at least one processor being coupled to the memory and, at least in part based on information stored in the memory, the at least one processor being configured to: Transmit a channel state information reference signal (CSI-RS) to a user equipment (UE); and Receive, based on the CSI-RS, a channel state information (CSI) report corresponding to at least one UE-selected bandwidth part of a downlink bandwidth part (BWP) from the UE.

17. The apparatus according to claim 16, wherein the CSI report comprises at least one channel quality indicator (CQI) of the at least one UE-selected bandwidth part of the downlink BWP.

18. The apparatus according to claim 16, wherein the at least one UE-selected bandwidth part of the downlink BWP corresponds to at least one downlink subband associated with a UE-selected downlink subband configuration among a plurality of available downlink subband configurations.

19. The apparatus according to claim 18, wherein the at least one UE-selected bandwidth part of the downlink BWP comprises a plurality of downlink subbands associated with the UE-selected downlink subband configuration.

20. The apparatus according to claim 18, wherein the at least one processor is configured to: Receive, from the UE, an indication of the UE-selected downlink subband configuration before receiving the CSI report.

21. The apparatus according to claim 18, wherein the plurality of available downlink subband configurations are pre-configured.

22. The apparatus according to claim 18, wherein the plurality of available downlink subband configurations are configured based on radio resource control (RRC) signaling from the network node.

23. The apparatus according to claim 18, wherein each of the plurality of available downlink subband configurations is associated with a specified number of subbands specifying a subband size.

24. The apparatus according to claim 16, wherein the at least one UE-selected bandwidth part of the downlink BWP comprises a single UE-selected bandwidth part corresponding to the entire downlink BWP.

25. The apparatus according to claim 16, wherein the at least one UE-selected bandwidth part of the downlink BWP comprises a plurality of UE-selected bandwidth parts in the downlink BWP, and the CSI report comprises respective channel quality indicators (CQIs) of each of the plurality of UE-selected bandwidth parts in the downlink BWP.

26. The apparatus according to claim 25, wherein the at least one processor is further configured to: receive from the UE an indication of a plurality of bandwidths corresponding to the plurality of UE-selected bandwidth parts in the downlink BWP.

27. The apparatus according to claim 16, wherein the downlink BWP is associated with full-duplex operation.

28. The apparatus according to claim 16, wherein the apparatus further comprises: A transceiver coupled to the at least one processor, the transceiver being configured to transmit the CSI-RS and receive the CSI report.

29. A method for wireless communication at a network node, the method comprising: transmitting a channel state information reference signal (CSI-RS) to a user equipment (UE); and receiving, based on the CSI-RS, a channel state information (CSI) report from the UE corresponding to at least one UE-selected bandwidth part of a downlink bandwidth part (BWP).

30. The method according to claim 29, wherein the CSI report comprises at least one channel quality indicator (CQI) of the at least one UE-selected bandwidth part of the downlink BWP.

Images