CPU, timing and capability specification for eCSF reporting based on planned CLI in FD

Abstract

The UE may estimate a CLI channel state based on the ZP-SRS from the second UE. A network node may send a CSI-RS to the UE, and the UE may receive the CSI-RS from the network node. The UE may estimate a downlink channel state based on the CSI-RS from the network node. The UE may estimate one or more eCSF parameters based on the CLI channel state, the downlink channel state, two or more interference hypotheses, and at least one of a CPU specification, a timing specification, or a UE capability indication. The UE may send an eCSF report to the network node based on the one or more eCSF parameters, and the network node may receive the eCSF report from the UE.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims the benefit of U.S. patent application serial number 17 / 662,646, filed on May 9, 2022, entitled “CPU, TIMING, AND CAPABILITY SPECIFICATIONS FOR ECSF REPORTBASED ON PROJECTED CLI IN FD,” which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to communication systems, and more particularly, to channel state feedback from full-duplex user equipment (UE) in a wireless communication system. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies 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 a city, country, region, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5GNR 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 4G Long Term Evolution (LTE) standards. It is necessary to further improve 5G NR technology. In addition, 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 is not an extensive review of all contemplated aspects. This summary is neither intended to identify key or important elements of all aspects nor to delineate 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 a more detailed description presented later.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a user equipment (UE). The apparatus may estimate a cross-link interference (CLI) channel state based on a zero power (ZP)-sounding reference signal (SRS) (ZP-SRS) from a second UE. The apparatus may estimate a downlink channel state based on a channel state information (CSI)-reference signal (RS) (CSI-RS) from a network node. The apparatus may estimate one or more enhanced channel state feedback (eCSF) parameters based on the CLI channel state, the downlink channel state, two or more interference assumptions, and at least one of a CSI processing unit (CPU) specification, a timing specification, or a UE capability indication. The apparatus may send an eCSF report based on the one or more eCSF parameters to the network node.

[0008] In one aspect of the present disclosure, a method, a computer readable medium, and an apparatus are provided. The apparatus may be a network node. The apparatus may send a CSI-RS to a UE. The apparatus may receive an eCSF based on one or more eCSF parameters from the UE. The one or more eCSF parameters may be based on a CLI channel state, a downlink channel state, two or more interference assumptions, and at least one of a CPU specification, a timing specification, or a UE capability indication. The CLI channel state may be based on a ZP-SRS from a second UE. The downlink channel state may be based on the CSI-RS.

[0009] To achieve the aforementioned and related purposes, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail some exemplary features of one or more aspects. However, these features are only indicative of only some of the various ways in which the principles of the various aspects can 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 2Bis a diagram illustrating an example of 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 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 Examples of in-band full-duplex (IBFD) resources and sub-band frequency division duplex (FDD) resources for full-duplex communication are illustrated.

[0017] Figure 5 are diagrams illustrating various example deployment scenarios including one or more full-duplex devices.

[0018] Figure 6 is a diagram illustrating an example scenario in which a UE may experience interference.

[0019] Figure 7 is a flow chart illustrating an example process associated with codebook based downlink adaptation.

[0020] Figure 8 is a diagram illustrating an example timing specification associated with a CSF.

[0021] Fig. 9 is a flow diagram illustrating an example process related to eCSF based on a planned CLI.

[0022] Fig.10 is a flow chart illustrating an example process for providing an eCSF.

[0023] Fig.11 is a flow chart of a method of wireless communication.

[0024] Fig.12 is a flow chart of a method of wireless communication.

[0025] Fig.13 is a flow chart of a method of wireless communication.

[0026] Fig.14 is a flow chart of a method of wireless communication.

[0027] Fig.15 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities.

[0028] Fig.16 is a diagram illustrating an example of a hardware implementation of an example network entity. DETAILED DESCRIPTION

[0029] In order to provide an eCSF report, a CLI channel and one or more interference assumptions may be considered in the calculation of the eCSF report. Calculating the spectral efficiency of more than one interference assumption may result in increased processing time for the CSI report. Therefore, new specifications including new CPU specifications and new timing specifications and signaling of new UE capabilities related to eCSF may be provided. According to one or more aspects, a UE may estimate a CLI channel state based on a ZP-SRS from a second UE. A network node may send a CSI-RS to the UE, and the UE may receive the CSI-RS from the network node. The UE may estimate a downlink channel state based on the CSI-RS from the network node. The UE may estimate one or more eCSF parameters based on the CLI channel state, the downlink channel state, two or more interference assumptions, and at least one of a CPU specification, a timing specification, or a UE capability indication. The UE may send an eCSF report based on the one or more eCSF parameters to the network node, and the network node may receive the eCSF report from the UE. Therefore, eCSF may be enabled if the impact of the transmitted precoding matrix indicator (TPMI) chosen by the aggressor UE is taken into account when calculating the eCSF report.

[0030] The detailed description set forth below in conjunction with the accompanying drawings is a description of various configurations and does not represent the only configurations in which the concepts described herein can be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0031] Several aspects of telecommunication systems are presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0032] As an example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system", which includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gating logic, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout the present disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, or any combination thereof.

[0033] Therefore, in one or more example aspects, specific implementations and / or use cases, the described functions may be implemented with hardware, software, or any combination thereof. If implemented in software, the functions may be stored or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available medium that can be accessed by a computer. By way of example, such computer-readable media may 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.

[0034] Although various aspects, specific implementations and / or use cases are described in this application by the illustration of some examples, additional or different aspects, specific implementations and use cases may be generated in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, various aspects, specific implementations and / or use cases can be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, artificial intelligence (AI) enabled devices, etc.). Although some examples may or may not be specifically for use cases or applications, the described examples may have a wide range of applicability. Various aspects, specific implementations and / or use cases can be in the range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed or original equipment manufacturer (OEM) devices or systems in conjunction with one or more technologies herein. In some actual settings, the equipment combined with the various 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 include several components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.) The techniques described herein can be practiced in a wide variety of devices of various sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc.

[0035] 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, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or a network equipment (such as a base station (BS) or one or more units (or one or more components) that perform base station functionality) can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5GNB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0036] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed 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 in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a 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).

[0037] Base station operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access and backhaul (IAB) network, an open radio access network (O-RAN (network configuration such as that initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0038] Figure 1 1 is a diagram 100 illustrating an example of a wireless communication system and an access network. The illustrated wireless communication system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110 that may communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more disaggregated 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 corresponding midhaul links, such as an F1 interface. The DU 130 may communicate with one or more RUs 140 via corresponding fronthaul links. The RU 140 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0039] Each of the units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO framework 105) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively, 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 a transmission medium. For example, these units may include a wired interface configured to receive signals or send signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive and / or send signals to one or more of the other units via a wireless transmission medium.

[0040] In some aspects, CU 110 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 110. CU 110 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 110 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 110 may be implemented to communicate with DU 130 for network control and signaling.

[0041] 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 a radio link control (RLC) layer, a 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 in part according to a functional split such as those defined by 3GPP. In some aspects, DU 130 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0042] The lower layer functionality may be implemented by one or more RUs 140. In some deployments, the RU 140 controlled by the DU 130 may correspond to a logical node that hosts 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, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the implementation of the DU 130 and the CU 110 in a cloud-based RAN architecture (such as a vRAN architecture).

[0043] The SMO framework 105 may be configured to support RAN deployment and configuration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 105 may be configured to interact with a cloud computing platform (such as an 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 an O2 interface). Such virtualized network elements may include, but are not limited to, CU 110, DU 130, RU 140, and near-RT RIC 125. In some specific implementations, the SMO framework 105 may communicate with hardware aspects of the 4G RAN such as an open eNB (O-eNB) 111 via the O1 interface. Additionally, in some specific implementations, the SMO framework 105 may communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105 .

[0044] The non-RT RIC 115 may 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 may be coupled to or in communication with the near-RT RIC 125 (such as via an A1 interface). The near-RT RIC 125 may 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 an E2 interface) that connects one or more CUs 110, one or more DUs 130, or both, and O-eNBs with the near-RT RIC 125.

[0045] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 125, the non-RT RIC 115 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 125 and may be received from a non-network data source or from a network function 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 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 105 (such as via reconfiguration of O1) or via creation of RAN management policies (such as A1 policies).

[0046] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Therefore, the base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component is indicated by a dotted line to indicate that each component may be included in the base station 102 or may not be included in the base station). The base station 102 provides an access point to the core network 120 for the UE 104. The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). 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. A 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 uplink (UL) (also known as reverse link) transmission from UE 104 to RU 140 and / or downlink (DL) (also known as 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 pass through one or more carriers. For each carrier allocated in a carrier aggregation of up to Yx MHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use a spectrum of up to Y MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.) bandwidth. The 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 to DL compared to UL). The component carrier 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 carrier may be referred to as a secondary cell (SCell).

[0047] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL wireless wide area network (WWAN) spectrum. The D2D communication link 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). The D2D communication may be through a variety of 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.

[0048] The wireless communication system may also include a Wi-Fi AP 150 that communicates with a UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, for example, in a 5 GHz unlicensed spectrum, etc. When communicating in an unlicensed spectrum, the UE 104 / AP 150 may perform a clear channel assessment (CCA) to determine whether a channel is available prior to communication.

[0049] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the “sub-6 GHz” band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0050] 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.125GHz–24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6GHz–71GHz), FR4 (71GHz–114.25GHz), and FR5 (114.25GHz–300GHz). Each of these higher frequency bands falls within the EHF band.

[0051] In view of the above, unless otherwise specifically stated, if the term "sub-6 GHz" or the like is used herein, it may broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, if the term "millimeter wave" or the like is used herein, it may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.

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

[0053] The base station 102 may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), a network node, a network entity, a network equipment, or some other suitable term. The 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 a RU, or as a decomposed base station including one or more of a CU, a DU, and / or a RU. A set of base stations that may include decomposed base stations and / or aggregated base stations may be referred to as a next generation (NG) RAN (NG-RAN).

[0054] 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. AMF 161 is a control node that handles signaling between UE 104 and core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, and subscription management. One or more location servers 168 are illustrated as including a gateway mobile location center (GMLC) 165 and a location management function (LMF) 166. However, in general, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, LMF 166, positioning determination entity (PDE), serving mobile location center (SMLC), mobile positioning center (MPC), etc. GMLC 165 and LMF 166 support UE location services. GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. LMF 166 receives measurement and assistance information from NG-RAN and UE 104 via AMF 161 to calculate the positioning of UE 104. NG-RAN may determine the positioning of UE 104 using one or more positioning methods. Positioning UE 104 may involve signal measurements, position estimation, and optional speed calculation based on these measurements. Signal measurements may be performed by UE 104 and / or serving base station 102. The measured signals may be based on a satellite positioning system (SPS) 170 (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / location systems), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, 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, NR signals (e.g., multi-round trip time (multi-RTT), DL angle of departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning), and / or one or more of other systems / signals / sensors.

[0055] Examples of UE 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, 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, electric meters, gas pumps, large or small kitchen appliances, healthcare equipment, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as stations, mobile stations, subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, user agents, mobile clients, clients, or some other suitable terminology. In some scenarios, the term UE may also be applied to one or more supporting devices, such as in a device cluster arrangement. One or more of these devices may access the network collectively and / or individually.

[0056] Reference again Figure 1 In some aspects, the UE 104 may include an eCSF component 198, which may be configured to estimate the CLI channel state based on the ZP-SRS from the second UE. The eCSF component 198 may be configured to estimate the downlink channel state based on the CSI-RS from the network node. The eCSF component 198 may be configured to estimate one or more eCSF parameters based on the CLI channel state, the downlink channel state, two or more interference assumptions, and at least one of the CPU specification, timing specification, or UE capability indication. The eCSF component 198 may be configured to send an eCSF report based on one or more eCSF parameters to the network node. In some aspects, the base station 102 may include an eCSF component 199, which may be configured to send the CSI-RS to the UE. The eCSF component 199 may be configured to receive an eCSF based on one or more eCSF parameters from the UE. The one or more eCSF parameters may be based on the CLI channel state, the downlink channel state, two or more interference assumptions, and at least one of the CPU specification, timing specification, or UE capability indication. The CLI channel state may be based on the ZP-SRS from the second UE. The downlink channel state may be based on the CSI-RS. Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas such as LTE, LTE-A, CDMA, GSM and other wireless technologies.

[0057] Figure 2AFIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G NR subframe. Figure 2C FIG250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2D FIG280 is a diagram illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL, or may be time division duplex (TDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL. Figure 2A , Figure 2C In the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are full DL and full UL, respectively. Other slot formats 2-61 include a mix of DL, UL and flexible symbols. The slot format is configured for the UE via a received slot format indicator (SFI) (dynamically configured via DL control information (DCI) or semi-statically / statically configured via radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0058] FIG. 2A to FIG. 2DThe frame structure is illustrated, and various aspects of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 subframes of equal size (1ms). Each subframe may include one or more time slots. A subframe may also include a microslot, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For a normal CP, each time slot may include 14 symbols, and for an extended CP, each time slot may include 12 symbols. The symbol on the DL may be a CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbol. The symbol on the UL may be a CP-OFDM symbol (for high throughput scenarios) or a discrete Fourier transform (DFT) extended OFDM (DFT-s-OFDM) symbol (also known as a single carrier frequency division multiple access (SC-FDMA) symbol) (for power-limited 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) and effectively defines the symbol length / duration, which is equal to 1 / SCS.

[0059]

[0060] 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 μ timeslots / subframe. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is parameter set 0 to 4. Therefore, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=4 is 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example is provided for a normal CP with 14 symbols per slot and a parameter set μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is about 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 2B ). Each BWP may have a specific parameter set and CP (normal or extended).

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

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

[0063] Figure 2B Examples of various DL channels within a subframe of a frame are illustrated. A physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring opportunity on a CORESET, wherein the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identification. A secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and the 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 number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not sent via the PBCH (such as a system information block (SIB)), and paging messages.

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

[0065] Figure 2D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and 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 may additionally be used to carry buffer status reports (BSRs), power headroom reports (PHRs), and / or UCI.

[0066] Figure 3375. The Controller / Processor 375 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 may 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 medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with transmission of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with 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 through HARQ, priority handling, and logical channel prioritization.

[0067] The transmit (TX) processor 316 and 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) coding / 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 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be separated into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially pre-coded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes, as well as for spatial processing. Channel estimates may be derived based on reference signals and / or channel condition feedback sent by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier with a corresponding spatial stream for transmission.

[0068] At the UE 350, each receiver 354Rx receives a signal through its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to a 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 can perform spatial processing on the information to recover any spatial stream destined for the UE 350. If multiple spatial streams are destined for the UE 350, they can be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the signal constellation point most likely to be sent by the base station 310. These soft decisions can be based on channel estimates calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by the base station 310. The data and control signals are then provided to the controller / processor 359, which implements layer 3 and layer 2 functionality.

[0069] The controller / processor 359 may be associated with a memory 360 that stores program codes 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 ACK and / or NACK protocols to support HARQ operations.

[0070] Similar to the functionality described in conjunction 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 transmission of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0071] Channel estimates derived by the channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select appropriate coding 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 separate transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

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

[0073] The controller / processor 375 may be associated with a memory 376 that stores program codes 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 ACK and / or NACK protocols to support HARQ operations.

[0074] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform operations related to Figure 1 The eCSF component 198 combines various aspects.

[0075] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform operations related to Figure 1 The eCSF component 199 combines various aspects.

[0076] Full-duplex communications may be in the same frequency band. Uplink and downlink communications may be in different frequency sub-bands, in the same frequency sub-band, or in partially overlapping frequency sub-bands.

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

[0078] IBFD is contrasted with sub-band frequency division duplex (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 resources 422 are separated from DL resources 424 by guard bands 426. The guard band can be a frequency resource provided between the UL resources 422 and the DL resources 424, or a gap in the frequency resource. Using a guard band to separate the UL frequency resources from the DL frequency resources can help reduce self-interference. UL resources and DL resources that are immediately adjacent to each other correspond to a guard band width of 0. Since the output signal (e.g., from the UE transmitter) can extend beyond the UL resource, the guard band can reduce the interference experienced by the UE. Sub-band FDD can also be referred to as "flexible duplexing".

[0079] Figure 55 is a diagram illustrating various example deployment scenarios including one or more full-duplex devices. A full-duplex device (or a device operating in full-duplex mode) may transmit and receive simultaneously. Diagram 510 illustrates an example deployment scenario including at least one full-duplex network node and two half-duplex UEs. Operating in full-duplex mode, a first network node 512 may transmit to a second UE 518 and receive from a first UE 516 simultaneously. Full-duplex operation may create SI at the first network node 512. In particular, at the first network node 512, downlink transmissions to the second UE 518 may cause interference to uplink receptions from the first UE 516. In addition, uplink transmissions from the first UE 516 to the first network node 512 may cause CLI to the downlink receptions of the second UE 518 from the first network node 512. In addition, transmissions from the second network node 514 may cause CLI to the uplink receptions at the first network node 512.

[0080] Diagram 530 illustrates an example deployment scenario including at least one full-duplex network node and at least one full-duplex UE / customer premises equipment (CPE). A first network node 532 may communicate with a first UE / CPE 536 in full-duplex mode. In other words, uplink and downlink transmissions may occur simultaneously between the first network node 532 and the first UE / CPE 536. At the same time, the first network node 532 may transmit to a second UE / CPE 538. Downlink transmissions to both the first UE / CPE 536 and the second UE / CPE 538 may cause SI to be received at the first network node 532 for uplink from the first UE / CPE 536. In addition, uplink transmissions from the first UE / CPE 536 may cause SI to be received at the first UE / CPE 536 for downlink, and may cause CLI to be received at the second UE / CPE 538 for downlink. Furthermore, the transmission from the second network node 534 may cause a CLI to be received on the uplink at the first network node 532 .

[0081] Diagram 550 illustrates an example deployment scenario including two half-duplex network nodes (or two transmit receive points (TRPs) that together may function as full-duplex network nodes) and at least one full-duplex UE / CPE. A first UE / CPE 556 may operate in full-duplex mode. In particular, the first UE / CPE 556 may simultaneously transmit to the first network node 552 and receive from the second network node 554. Thus, uplink transmissions from the first UE / CPE 556 to the first network node 552 may result in SI for downlink reception at the first UE / CPE 556. In addition, the second network node 554 may transmit to the second UE / CPE 558 at the same time as the second network node 554 transmits to the first UE / CPE 556. Downlink transmissions from the second network node 554 to both the first UE / CPE 556 and the second UE / CPE 558 may result in CLI for uplink reception at the first network node 552. Furthermore, uplink transmissions from the first UE / CPE 456 to the first network node 552 may result in a CLI for downlink reception at the second UE / CPE 558 .

[0082] Figure 6 610 is a diagram illustrating an example scenario in which a UE may experience interference. In the scenario illustrated in diagram 610, a first UE 614 and a second UE 616, which may be located in the same cell corresponding to a first network node 612, may operate in half-duplex mode. In addition, the first network node 612 may operate in full-duplex mode (IBFD or sub-band FDD). As illustrated in diagram 610, uplink transmissions from the first UE 614 to the first network node 612 may cause intra-cell CLI to downlink receptions from the first network node 612 at the second UE 616 (even in the case of sub-band FDD, CLI may also occur due to leakage). In addition, the second UE 616 may also experience inter-cell interference from the second network node 618. Therefore, between the first UE 614 and the second UE 616, the first UE 614 may be an aggressor UE, and the second UE 616 may be a victim UE.

[0083] In the scenario illustrated in diagram 650, a first UE 654 and a second UE 656, which may be located in different neighboring cells corresponding to a first network node 652 and a second network node 658, respectively, may operate in half-duplex mode. The first network node 652 and the second network node 658 may be associated with the same operator, or may be associated with different operators. As illustrated in diagram 650, an uplink transmission from the first UE 654 to the first network node 652 may cause an inter-cell CLI to a downlink reception from the second network node 658 at the second UE 656. Therefore, between the first UE 654 and the second UE 656, the first UE 654 may be an aggressor UE, and the second UE 656 may be a victim UE.

[0084] Furthermore, as described above, a UE operating in full-duplex mode may experience SI.

[0085] Figure 7 700 is a flow chart illustrating an example process 700 associated with codebook-based downlink adaptation. At 706, the network node 704 may send an RRC message for scheduling CSI-RS to the UE 702, and the UE 702 may receive the RRC message from the network node 704. At 708, the network node 704 may send an RRC message for scheduling CSI reports (hereinafter, CSI reports may also be referred to as channel state feedback (CSF)) to the UE 702, and the UE 702 may receive the RRC message from the network node 704. At 710, the network node 704 may send the CSI-RS to the UE 702, and the UE 702 may receive the CSI-RS from the network node 704. The CSI-RS may correspond to a single beam. At 712, the UE 702 may send a periodic CSI report to the network node 704, and the network node 704 may receive the periodic CSI report from the UE 702. The CSI report may be sent via UCA on PUCCH or PUSCH. Each CSI report may include at least one of RI, PMI, or CQI. Thus, the PMI may indicate to the network node 704 the precoding matrix selected by the UE 702 for downlink transmission (e.g., PDSCH transmission). Thus, at 714, the network node 704 may send to the UE 702 a PDSCH that has been precoded at the network node 704 using the precoding matrix selected by the UE 702, and the UE 702 may receive the PDSCH from the network node 704.

[0086] In various configurations, REs carrying reference signals may be configured as ZP or non-zero power (NZP). Thus, for example, an SRS carried in a ZP RE may be referred to as a ZP-SRS, a CSI-RS carried in an NZP RE may be referred to as an NZP-CSI-RS, and so on.

[0087] Figure 8 8 is a diagram illustrating example timing specifications associated with a CSF. In some configurations, certain timing specifications associated with CSI processing may be met in order to ensure that the UE has sufficient time to generate a CSI report. Figure 8 As illustrated, the PDCCH 802 may schedule / trigger a CSI-RS 804 (eg, NZP-CSI-RS) (eg, Figure 7 710) and the CSI report carried in PUSCH 806 (e.g., Figure 7 806). In some configurations, a minimum delay Z may be specified for the delay between PDCCH 802 and PUSCH 806. Additionally, another minimum delay Z′ may be specified for the delay between CSI-RS 804 and PUSCH 806.

[0088] For example, Table 1 below shows example timing specifications (Z / Z') for some configurations where ultra-low latency is to be supported. In addition, Table 2 below shows example timing specifications (Z / Z') for three different latency categories for some configurations. In particular, timing specifications Z1 / Z1' may correspond to a low latency category. Timing specifications Z2 / Z2' may correspond to a high latency category. In addition, timing specifications Z3 / Z3' may correspond to a latency category specific to beam reporting, where min() may be a minimum function, and X i May be based on reported UE capabilities.

[0089]

[0090] Table 1. CSI calculation delay specifications (ultra-low latency)

[0091]

[0092]

[0093] Table 2. CSI calculation delay specifications

[0094] In some configurations, the UE may be associated with certain UE features or capabilities regarding CSI-RS and CSI-Inferred Measurement (IM) (CSI-IM) reception for CSF. The UE may send an indication of the UE features to the network so that the network node can provide CSI-RS accordingly. UE features related to CSI-RS and CSI-IM reception for CSF may include, for example, one or more of the following: the supported maximum number of configured NZP-CSI-RS resources per component carrier (CC) ("maxConfigNumberNZP-CSI-RS-PerCC") (candidate values ​​may be {1, 2, 3, ..., 32}), the supported maximum number of ports across all configured NZP-CSI-RS resources per CC ("maxConfigNumberPortsAcrossNZP-C SI-RS-PerCC”) (candidate values ​​may be {2, 4, 8, 12, 16, 24, 32, 40, 48, ..., 256}), the supported maximum number of configured CSI-IM resources per CC (“maxConfigNumberCSI-IM-PerCC”) (candidate values ​​may be {1, 2, 4, 8, 16, 32}), the supported maximum number of simultaneous NZP-CSI-RS resources in active BWPs across all CCs (“maxNumberSimultaneousNZP-CSI-RS -ActBWP-AllCC" (candidate values ​​may be {5, 6, 7, 8, 9, 10, 12, 14, 16, ..., 62, 64} (just even numbers between 16 and 64)), the supported maximum number of simultaneous NZP-CSI-RS resources per CC ("maxNumberSimultaneousNZP-CSI-RS-PerCC") (candidate values ​​may be {1, 2, 3, ..., 32}), the supported number of CSI-RS ports in simultaneous NZP-CSI-RS resources in active BWPs across all CCs The maximum total number (“totalNumberPortsSimultaneousNZP-CSI-RS-ActBWP-AllCC”) (candidate values ​​can be {8, 16, 24, ..., 248, 256}), or the supported maximum total number of CSI-RS ports in simultaneous NZP-CSI-RS resources per CC (“totalNumberPortsSimultaneousNZP-CSI-RS-PerCC”) (candidate values ​​can be {8, 16, 24, ..., 128}).

[0095] For codebook based operation, the network node may optimize the PMI selection for the downlink of the victim UE and the transmitted PMI (TPMI) selection for the aggressor UE to minimize the impact of the inter-UE CLI. In some configurations, the CSF (e.g., PMI, RI, CQI, etc.) may be enhanced to take into account the precoder selection at the aggressor UE (i.e., TPMI selection) and the impact of the aggressor UE precoder selection on the inter-UE CLI, because the best selection for the downlink CSF parameters may depend on the TPMI selection at the aggressor UE.

[0096] Fig. 9 908, the network node 906 may configure a multi-port CLI-SRS for probing (e.g., measuring) a CLI channel to an aggressor UE 904 via an RRC message. At 910, the network node 906 may configure a victim UE 902 with CLI measurement resources via an RRC message. At 912, the network node 906 may schedule the transmission of an aperiodic CLI-SRS from the aggressor UE 904 via a DCI message (dedicated or group common (GC)). At 914, the aggressor UE 904 may transmit a CLI-SRS (e.g., a ZP-SRS, which may not be precoded). The victim UE 902 may receive the CLI-SRS transmitted by the aggressor UE 904. At 916, the victim UE 902 may perform CLI channel measurement using CLI-SRS (ZP-SRS) to obtain an estimated CLI channel “H_cli”. At 918, the network node 906 may schedule the victim UE 902 for CSI measurement and CSI reporting via a DCI message. In addition, the network node 906 may send a CSI-RS for CSF to the victim UE 902. At 920, the victim UE 902 may find CSF parameters using the estimated downlink channel “H” (which may be estimated based on the CSI-RS) and the estimated CLI channel “H_cli”. At 922, the victim UE 902 may send an enhanced CSI (eCSI) report (which may also be referred to as an eCSF or eCSF report) to the network node 906. In some configurations, one or more inference assumptions may be used to generate the eCSI report 922. Each inferred hypothesis may correspond to a respective precoder applied to the CLI-SRS 914 by the aggressor UE 904. In other words, each interference hypothesis may be associated with a TPMI / rank. Thus, multiple CLI-SRS corresponding to different interference hypotheses may be sequentially sent at 914 and measured at 916.

[0097] One or more aspects of the present disclosure may relate to CPU specifications, timing specifications (Z / Z'), and / or eCSF-related capability signaling from the UE.

[0098] Fig.10 is a flow chart illustrating an example process 1000 for providing an eCSF. Calculating the spectral efficiency of more than one interference hypothesis (i.e., more than one TPMI) may result in increased UE processing time for CSI reporting. In some configurations, the UE may indicate the CPU capability of the UE to the network. The UE may be able to concurrently identify a limited number of CSIs based on the number of CPUs.

[0099] At 1006 , UE 1002 may send a UE capability indication to network node 1004 , and network node 1004 may receive the UE capability indication from UE 1002 .

[0100] In one configuration, the UE capability indication may indicate a first UE capability associated with measuring one or more ZP-SRS resources.

[0101] In one configuration, the UE capability indication may include an independent indication of a first UE capability associated with measuring one or more ZP-SRS resources. For example, the independent indication of a first UE capability associated with measuring one or more ZP-SRS resources (e.g., a UE characteristic associated with measuring one or more ZP-SRS resources) may include an indication of one or more of the following: a supported maximum number of configured ZP-SRS resources per CC, a supported maximum number of ports across all configured ZP-SRS resources per CC, a supported maximum number of simultaneous ZP-SRS resources in an active BWP across all CCs, a supported maximum number of simultaneous ZP-SRS resources per CC, a supported maximum total number of ZP-SRS ports in simultaneous ZP-SRS resources in an active BWP across all CCs, or a supported maximum total number of ZP-SRS ports in simultaneous ZP-SRS resources per CC.

[0102] In one configuration, the UE capability indication may include a combined indication of a second UE capability associated with measuring both one or more ZP-SRS resources and one or more CSI-RS resources. For example, the combined indication of a second UE capability associated with measuring both one or more ZP-SRS resources and one or more CSI-RS resources (e.g., a UE characteristic associated with measuring both one or more ZP-SRS resources and one or more CSI-RS resources) may include an indication of one or more of the following: a supported maximum number of combinations of configured ZP-SRS resources and NZP-CSI-RS resources per CC, a supported maximum number of combinations of ports across all configured ZP-SRS resources and NZP-CSI-RS resources per CC, an active BWP across all CCs The maximum supported number of combinations of simultaneous ZP-SRS resources and NZP-CSI-RS resources in a BWP, the maximum supported number of combinations of simultaneous ZP-SRS resources and NZP-CSI-RS resources per CC, the maximum supported total number of combinations of ZP-SRS ports and NZP-CSI-RS ports in simultaneous ZP-SRS resources and NZP-CSI-RS resources in an active BWP across all CCs, or the maximum supported total number of combinations of ZP-SRS ports and NZP-CSI-RS ports in simultaneous ZP-SRS resources and NZP-CSI-RS resources per CC. Of course, the "maxConfigNumberCSI-IM-PerCC" feature may continue to be indicated.

[0103] At 1008, UE 1002 may estimate the CLI channel state based on the ZP-SRS from the second UE (ie, the aggressor UE).

[0104] At 1010 , the network node 1004 may send a CSI-RS to the UE 1002 .

[0105] At 1012 , UE 1002 may estimate downlink channel status based on CSI-RS 1010 from network node 1004 .

[0106] At 1014, the UE 1002 may estimate one or more eCSF parameters based on the CLI channel status, the downlink channel status, two or more interference hypotheses, and at least one of a CPU specification, a timing specification, or a UE capability indication.

[0107] exist Figure 7In the illustrated CSF process where no CLI channel or interference assumption is considered and except for beam reporting (i.e., reporting of L1 signal to interference plus noise ratio (SINR) (L1-SINR) / reference signal received power (RSRP)), the CPU designated for CSI reporting may be equal to the number of CSI-RS resources in the associated CSI-RS resource set. In addition, if a single interference assumption is considered, the CPU specification may be similar to Figure 7 The illustrated CSI report is used to process the eCSI report.

[0108] In a configuration where more than one interference hypothesis is considered, the number of CPUs specified may be proportional to the product (multiplication) of the number of CSI-RS resources and the number of interference hypotheses. In other words, the CPU specification may indicate a number of CPUs that is equal to the product of the number of CSI-RS resources and the number of two or more interference hypotheses. For example, for an eCSI report including 2 CSI-RS resources and 3 interference hypotheses, 6 (=2*3) CPUs may be specified for calculating the eCSF report.

[0109] In a configuration where more than one interference hypothesis is considered, the specified number of CPUs for the eCSF may be a function of both the number of CSI-RS resources and the number of interference hypotheses. However, the specified number of CPUs may be less than the product of the number of interference hypotheses and the number of CSI-RS resources (e.g., due to parallelization). In other words, the CPU specification may indicate a number of CPUs that is less than the product of the number of CSI-RS resources and the number of two or more interference hypotheses. For example, for an eCSI report including 2 CSI-RS resources and 3 interference hypotheses, 4 (=2*ceil(3 / 2), ceil() is a ceiling function) CPUs may be specified for computing the eCSF report.

[0110] In a configuration where more than one interference hypothesis is considered, a predefined additional number of CPUs may be designated for additional calculations associated with the eCSF report. In other words, the CPU specification may indicate a number of CPUs that is the sum of the number of CSI-RS resources and the predefined number. For example, for an eCSI report including 2 CSI-RS resources and 3 interference hypotheses, 3 (=2+floor(3 / 2), floor() is a floor function) CPUs may be designated for calculating the eCSF report (in this example, the predefined number may be 1).

[0111] In a configuration where more than one interference hypothesis is considered, the number of CPUs designated for eCSF calculations may be increased (incremented) by 1 to account for multi-port CLI channel measurements using ZP-SRS, compared to scenarios where CLI channels are not considered or a single interference hypothesis is considered. For example, 2 (= 1 for CSI-RS resources + 1 for ZP-SRS resources) CPUs may be designated for calculating eCSF reports.

[0112] With respect to the timing specifications (Z / Z'), the latency category selected for the eCSI report may depend on the number of interference assumptions associated with the report. In particular, a minimum delay Z may be specified for the delay between the PDCCH that schedules / trigger the eCSF report and the PUSCH that carries the eCSF report (e.g., eCSI report 922). In addition, another minimum delay Z' may be specified for the delay between a reference signal (e.g., ZP-SRS or CSI-RS) and the PUSCH that carries the eCSF report (e.g., eCSI report 922). In one or more configurations, the timing specifications provided in Table 2 above may be reused for scenarios in which the CLI channel is considered in the calculation of the eCSF report. If a single interference assumption is considered, the same latency category as for CSI reports in which no CLI channel or interference assumption is considered (such as Figure 7 The same rules as those for the CSI report illustrated in the example (e.g., rules for selecting a latency category) may be used.

[0113] In one configuration where more than one interference hypothesis is considered, the timing specification may correspond to a predefined high-latency class timing specification (eg, the Z2 / Z2' specification provided in Table 2 above).

[0114] In one configuration, the timing specification may correspond to a predefined new latency class timing specification (eg, timing specification Z4 / Z4') not provided above in Table 2. The new latency class timing specification (Z4 / Z4') may be specific to the eCSF.

[0115] In one configuration, the predefined new latency class timing specification may be based at least in part on a number of two or more interference hypotheses.

[0116] In one configuration, the predefined new latency class timing specification may be based at least in part on one or more of the SCS, the number of reports (i.e., "reportQuantity," which may specify the kind of quantity to be measured and reported (e.g., SSB RSRP, CQI, PMI, RI, etc.), or the number of CSI-RS resources. The SCS, the number of reports, and the number of CSI-RS resources may be referred to as legacy factors.

[0117] In one configuration, a new timing specification table different from the above Table 2 may be defined for timing specifications of configurations where more than one interference hypothesis is considered. In particular, the new timing specification table may depend on one or more of the legacy factors or the number of interference hypotheses.

[0118] In one configuration, each interference hypothesis of the two or more interference hypotheses may correspond to a TPMI.

[0119] At 1016 , UE 1002 may send to network node 1004 an eCSF report based on the one or more eCSF parameters.

[0120] Fig.11 1100 is a flow chart of a method of wireless communication. The method may be performed by a UE (eg, UE 104 / 350 / 1002; device 1504). At 1102, the UE may estimate a CLI channel state based on a ZP-SRS from a second UE. For example, 1102 may be performed by Fig.15 Component 198 in the implementation. Fig.10 At 1008, UE 1002 may estimate the CLI channel state based on the ZP-SRS from the second UE.

[0121] At 1104, the UE may estimate the downlink channel state based on the CSI-RS from the network node. For example, 1104 may be performed by Fig.15 Component 198 in the implementation. Fig.10 At 1012 , UE 1002 may estimate the downlink channel state based on CSI-RS 1010 from network node 1004 .

[0122] At 1106, the UE may estimate one or more eCSF parameters based on the CLI channel state, the downlink channel state, two or more interference hypotheses, and at least one of a CPU specification, a timing specification, or a UE capability indication. For example, 1106 may be performed by Fig.15 Component 198 in the implementation. Fig.10 At 1014, UE 1002 may estimate one or more eCSF parameters based on CLI channel status, downlink channel status, two or more interference hypotheses, and at least one of a CPU specification, a timing specification, or a UE capability indication.

[0123] At 1108, the UE may send an eCSF report based on one or more eCSF parameters to the network node. For example, 1108 may be performed by Fig.15 Component 198 in the implementation. Fig.10 At 1016 , UE 1002 may send an eCSF report based on one or more eCSF parameters to network node 1004 .

[0124] Fig.12 1200 is a flow chart of a method of wireless communication. The method may be performed by a UE (eg, UE 104 / 350 / 1002; device 1504). At 1204, the UE may estimate a CLI channel state based on a ZP-SRS from a second UE. For example, 1204 may be performed by Fig.15 Component 198 in the implementation. Fig.10 At 1008, UE 1002 may estimate the CLI channel state based on the ZP-SRS from the second UE.

[0125] At 1206, the UE may estimate the downlink channel state based on the CSI-RS from the network node. For example, 1206 may be performed by Fig.15 Component 198 in the implementation. Fig.10 At 1012 , UE 1002 may estimate the downlink channel state based on CSI-RS 1010 from network node 1004 .

[0126] At 1208, the UE may estimate one or more eCSF parameters based on the CLI channel state, the downlink channel state, two or more interference hypotheses, and at least one of a CPU specification, a timing specification, or a UE capability indication. For example, 1208 may be performed by Fig.15 Component 198 in the implementation. Fig.10 At 1014, UE 1002 may estimate one or more eCSF parameters based on CLI channel status, downlink channel status, two or more interference hypotheses, and at least one of a CPU specification, a timing specification, or a UE capability indication.

[0127] At 1210, the UE may send an eCSF report based on one or more eCSF parameters to a network node. For example, 1210 may be performed by Fig.15 Component 198 in the implementation. Fig.10 At 1016 , UE 1002 may send an eCSF report based on one or more eCSF parameters to network node 1004 .

[0128] In one configuration, the CPU specification may indicate a number of CPUs that is equal to the product of the number of CSI-RS resources and the number of two or more interference hypotheses.

[0129] In one configuration, the CPU specification may indicate a number of CPUs that is less than a product of a number of CSI-RS resources and a number of two or more interference hypotheses.

[0130] In one configuration, the CPU specification may indicate a number of CPUs that is the sum of the number of CSI-RS resources and the predefined number.

[0131] In one configuration, the predefined number may be one.

[0132] In one configuration, the timing specification may correspond to a predefined high-latency class timing specification.

[0133] In one configuration, the timing specification may correspond to a predefined new latency class timing specification.

[0134] In one configuration, the predefined new latency class timing specification may be based at least in part on a number of two or more interference hypotheses.

[0135] In one configuration, the predefined new latency class timing specification may be based at least in part on one or more of the SCS, the number of reports, or the number of CSI-RS resources.

[0136] In one configuration, at 1202, the UE may send a UE capability indication to a network node. For example, 1202 may be performed by Fig.15 Component 198 in the implementation. Fig.10 At 1006 , UE 1002 may send a UE capability indication to network node 1004 .

[0137] In one configuration, the UE capability indication may indicate a first UE capability associated with measuring one or more ZP-SRS resources.

[0138] In one configuration, the UE capability indication may include a separate indication of the first UE capabilities associated with measuring one or more ZP-SRS resources.

[0139] In one configuration, the UE capability indication may include a combined indication of the second UE capabilities associated with measuring both one or more ZP-SRS resources and one or more CSI-RS resources.

[0140] In one configuration, each interference hypothesis of the two or more interference hypotheses may correspond to a TPMI.

[0141] Fig.13 1300 is a flow chart of a method of wireless communication. The method may be performed by a network node (e.g., base station 102 / 310; network node 1004; network entity 1502). At 1302, the network node may send a CSI-RS to a UE. For example, 1302 may be performed by Fig.16 Component 199 in the reference Fig.10 At 1010 , the network node 1004 may send a CSI-RS to the UE 1002 .

[0142] At 1304, the network node may receive an eCSF based on one or more eCSF parameters from the UE. The one or more eCSF parameters may be based on a CLI channel state, a downlink channel state, two or more interference assumptions, and at least one of a CPU specification, a timing specification, or a UE capability indication. The CLI channel state may be based on a ZP-SRS from a second UE. The downlink channel state may be based on a CSI-RS. For example, 1304 may be based on Fig.16 Component 199 in the reference Fig.10 At 1016 , the network node 1004 receives an eCSF from the UE 1002 based on one or more eCSF parameters.

[0143] Fig.14 1400 is a flow chart of a method of wireless communication. The method may be performed by a network node (e.g., base station 102 / 310; network node 1004; network entity 1502). At 1404, the network node may send a CSI-RS to a UE. For example, 1404 may be performed by Fig.16 Component 199 in the reference Fig.10 At 1010 , the network node 1004 may send a CSI-RS to the UE 1002 .

[0144] At 1406, the network node may receive an eCSF based on one or more eCSF parameters from the UE. The one or more eCSF parameters may be based on a CLI channel state, a downlink channel state, two or more interference assumptions, and at least one of a CPU specification, a timing specification, or a UE capability indication. The CLI channel state may be based on a ZP-SRS from a second UE. The downlink channel state may be based on a CSI-RS. For example, 1406 may be Fig.16 Component 199 in the reference Fig.10 At 1016 , the network node 1004 receives an eCSF from the UE 1002 based on one or more eCSF parameters.

[0145] In one configuration, the CPU specification may indicate a number of CPUs that is equal to the product of the number of CSI-RS resources and the number of two or more interference hypotheses.

[0146] In one configuration, the CPU specification may indicate a number of CPUs that is less than a product of a number of CSI-RS resources and a number of two or more interference hypotheses.

[0147] In one configuration, the CPU specification may indicate a number of CPUs that is the sum of the number of CSI-RS resources and the predefined number.

[0148] In one configuration, the predefined number may be one.

[0149] In one configuration, the timing specification may correspond to a predefined high-latency class timing specification.

[0150] In one configuration, the timing specification may correspond to a predefined new latency class timing specification.

[0151] In one configuration, the predefined new latency class timing specification may be based at least in part on a number of two or more interference hypotheses.

[0152] In one configuration, the predefined new latency class timing specification may be based at least in part on one or more of the SCS, the number of reports, or the number of CSI-RS resources.

[0153] In one configuration, at 1402, the network node may receive a UE capability indication from the UE. For example, 1402 may be performed by Fig.16 Component 199 in the reference Fig.10 At 1006 , the network node 1004 may receive a UE capability indication from the UE 1002 .

[0154] In one configuration, the UE capability indication may indicate a first UE capability associated with measuring one or more ZP-SRS resources.

[0155] In one configuration, the UE capability indication may include a separate indication of the first UE capabilities associated with measuring one or more ZP-SRS resources.

[0156] In one configuration, the UE capability indication may include a combined indication of the second UE capabilities associated with measuring both one or more ZP-SRS resources and one or more CSI-RS resources.

[0157] In one configuration, each interference hypothesis of the two or more interference hypotheses may correspond to a TPMI.

[0158] Fig.151500 is a diagram illustrating an example of a hardware implementation for an apparatus 1504. The apparatus 1504 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1504 may include a cellular baseband processor 1524 (also referred to as a modem) coupled to one or more transceivers 1522 (e.g., a cellular RF transceiver). The cellular baseband processor 1524 may include on-chip memory 1524'. In some aspects, the apparatus 1504 may also include one or more subscriber identity module (SIM) cards 1520 and an application processor 1506 coupled to a secure digital (SD) card 1508 and a screen 1510. The application processor 1506 may include on-chip memory 1506'. In some aspects, the device 1504 may also include a Bluetooth module 1512, a WLAN module 1514, an SPS module 1516 (e.g., a GNSS module), one or more sensor modules 1518 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial management 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 1526, a power source 1530, and / or a camera 1532. The Bluetooth module 1512, the WLAN module 1514, and the SPS module 1516 may include an on-chip transceiver (TRX) (or, in some cases, only a receiver (RX)). The Bluetooth module 1512, the WLAN module 1514, and the SPS module 1516 may include their own dedicated antennas and / or communicate using antennas 1580. The cellular baseband processor 1524 communicates with the UE 104 and / or with the RU associated with the network entity 1502 through the transceiver 1522 via one or more antennas 1580. The cellular baseband processor 1524 and the application processor 1506 may each include a computer-readable medium / memory 1524', 1506', respectively. The additional memory module 1526 may also be considered as a computer-readable medium / memory. Each computer-readable medium / memory 1524', 1506', 1526 may be non-transitory. The cellular baseband processor 1524 and the application processor 1506 are each responsible for general processing, including executing software stored on a computer-readable medium / memory. The software causes the cellular baseband processor 1524 / application processor 1506 to perform the various functions described above when executed by the cellular baseband processor 1524 / application processor 1506. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 1524 / application processor 1506 when executing the software.The cellular baseband processor 1524 / application processor 1506 may be a component of the UE 350 and may include the memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the device 1504 may be a processor chip (modem and / or application) and include only the cellular baseband processor 1524 and / or the application processor 1506, while in another configuration, the device 1504 may be the entire UE (e.g., see. Figure 3 350) and includes additional modules of device 1504.

[0159] As discussed above, component 198 is configured to estimate the CLI channel state based on the ZP-SRS from the second UE. Component 198 may be configured to estimate the downlink channel state based on the CSI-RS from the network node. Component 198 may be configured to estimate one or more eCSF parameters based on the CLI channel state, the downlink channel state, two or more interference assumptions, and at least one of the CPU specification, timing specification, or UE capability indication. Component 198 may be configured to send an eCSF report based on one or more eCSF parameters to the network node. Component 198 may be in the cellular baseband processor 1524, the application processor 1506, or both the cellular baseband processor 1524 and the application processor 1506. Component 198 may be one or more hardware components that are specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium so as to be implemented by one or more processors, or some combination thereof. As shown, device 1504 may include a variety of components configured for various functions. In one configuration, the device 1504 (and specifically the cellular baseband processor 1524 and / or the application processor 1506) includes a component for estimating a CLI channel state based on a ZP-SRS from a second UE. The device 1504 (and specifically the cellular baseband processor 1524 and / or the application processor 1506) includes a component for estimating a downlink channel state based on a CSI-RS from a network node. The device 1504 (and specifically the cellular baseband processor 1524 and / or the application processor 1506) includes a component for estimating one or more eCSF parameters based on a CLI channel state, a downlink channel state, two or more interference assumptions, and at least one of a CPU specification, a timing specification, or a UE capability indication. The device 1504 (and specifically the cellular baseband processor 1524 and / or the application processor 1506) includes a component for sending an eCSF report based on one or more eCSF parameters to a network node.

[0160] In one configuration, the CPU specification may indicate a number of CPUs that is equal to the product of the number of CSI-RS resources and the number of two or more interference hypotheses. In one configuration, the CPU specification may indicate a number of CPUs that is less than the product of the number of CSI-RS resources and the number of two or more interference hypotheses. In one configuration, the CPU specification may indicate a number of CPUs that is the sum of the number of CSI-RS resources and the predefined number. In one configuration, the predefined number may be 1. In one configuration, the timing specification may correspond to a predefined high latency category timing specification. In one configuration, the timing specification may correspond to a predefined new latency category timing specification. In one configuration, the predefined new latency category timing specification may be based at least in part on the number of two or more interference hypotheses. In one configuration, the predefined new latency category timing specification may be based at least in part on one or more of the SCS, the number of reports, or the number of CSI-RS resources. In one configuration, the device 1504 (and specifically the cellular baseband processor 1524 and / or the application processor 1506) includes a component for sending a UE capability indication to a network node. In one configuration, the UE capability indication may indicate a first UE capability associated with measuring one or more ZP-SRS resources. In one configuration, the UE capability indication may include an independent indication of the first UE capability associated with measuring one or more ZP-SRS resources. In one configuration, the UE capability indication may include a combined indication of a second UE capability associated with measuring both one or more ZP-SRS resources and one or more CSI-RS resources. In one configuration, each interference hypothesis of the two or more interference hypotheses may correspond to a TPMI.

[0161] A means may be a component 198 of the apparatus 1504 configured to perform the functions recited by the means. As described above, the apparatus 1504 may include the TX processor 368, the RX processor 356, and the controller / processor 359. Thus, in one configuration, a 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.

[0162] Fig.161600 is a diagram illustrating an example of a hardware implementation for a network entity 1602. The network entity 1602 may be a BS, a component of a BS, or may implement BS functionality. The network entity 1602 may include at least one of a CU 1610, a DU 1630, or a RU 1640. For example, depending on the layer functionality handled by the component 199, the network entity 1602 may include a CU 1610; both a CU 1610 and a DU 1630; each of the CU 1610, the DU 1630, and the RU 1640; the DU 1630; both a DU 1630 and a RU 1640; or a RU 1640. The CU 1610 may include a CU processor 1612. The CU processor 1612 may include an on-chip memory 1612'. In some aspects, the CU 1610 may also include an additional memory module 1614 and a communication interface 1618. CU 1610 communicates with DU 1630 via a midhaul link such as an F1 interface. DU 1630 may include a DU processor 1632. DU processor 1632 may include on-chip memory 1632'. In some aspects, DU 1630 may also include an additional memory module 1634 and a communication interface 1638. DU 1630 communicates with RU 1640 via a fronthaul link. RU 1640 may include a RU processor 1642. RU processor 1642 may include on-chip memory 1642'. In some aspects, RU 1640 may also include an additional memory module 1644, one or more transceivers 1646, an antenna 1680, and a communication interface 1648. RU 1640 communicates with UE 104. On-chip memory 1612', 1632', 1642' and additional memory modules 1614, 1634, 1644 may each be considered a computer-readable medium / memory. Each computer readable medium / memory may be non-transitory. Each of processors 1612, 1632, 1642 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 may also be used to store data manipulated by the processor when executing the software.

[0163] As discussed above, component 199 is configured to send CSI-RS to the UE. Component 199 may be configured to receive an eCSF based on one or more eCSF parameters from the UE. One or more eCSF parameters may be based on a CLI channel state, a downlink channel state, two or more interference assumptions, and at least one of a CPU specification, a timing specification, or a UE capability indication. The CLI channel state may be based on a ZP-SRS from a second UE. The downlink channel state may be based on the CSI-RS. Component 199 may be within one or more processors of one or more of CU1610, DU 1630, and RU 1640. Component 199 may be one or more hardware components specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium so as to be implemented by one or more processors, or some combination thereof. Network entity 1602 may include a variety of components configured for various functions. In one configuration, network entity 1602 includes a component for sending CSI-RS to the UE. The network entity 1602 includes means for receiving an eCSF based on one or more eCSF parameters from a UE. The one or more eCSF parameters may be based on a CLI channel state, a downlink channel state, two or more interference assumptions, and at least one of a CPU specification, a timing specification, or a UE capability indication. The CLI channel state may be based on a ZP-SRS from a second UE. The downlink channel state may be based on a CSI-RS.

[0164] In one configuration, the CPU specification may indicate a number of CPUs that is equal to the product of the number of CSI-RS resources and the number of two or more interference hypotheses. In one configuration, the CPU specification may indicate a number of CPUs that is less than the product of the number of CSI-RS resources and the number of two or more interference hypotheses. In one configuration, the CPU specification may indicate a number of CPUs that is the sum of the number of CSI-RS resources and the predefined number. In one configuration, the predefined number may be 1. In one configuration, the timing specification may correspond to a predefined high latency category timing specification. In one configuration, the timing specification may correspond to a predefined new latency category timing specification. In one configuration, the predefined new latency category timing specification may be based at least in part on the number of two or more interference hypotheses. In one configuration, the predefined new latency category timing specification may be based at least in part on one or more of the SCS, the number of reports, or the number of CSI-RS resources. In one configuration, the network entity 1602 includes a component for receiving a UE capability indication from the UE. In one configuration, the UE capability indication may indicate a first UE capability associated with measuring one or more ZP-SRS resources. In one configuration, the UE capability indication may include an independent indication of the first UE capability associated with measuring one or more ZP-SRS resources. In one configuration, the UE capability indication may include a combined indication of a second UE capability associated with measuring both one or more ZP-SRS resources and one or more CSI-RS resources. In one configuration, each interference hypothesis of the two or more interference hypotheses may correspond to a TPMI.

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

[0166] Re-reference Figures 4 to 14, the UE may estimate the CLI channel state based on the ZP-SRS from the second UE. The network node may send a CSI-RS to the UE, and the UE may receive the CSI-RS from the network node. The UE may estimate the downlink channel state based on the CSI-RS from the network node. The UE may estimate one or more eCSF parameters based on the CLI channel state, the downlink channel state, two or more interference assumptions, and at least one of a CPU specification, a timing specification, or a UE capability indication. The UE may send an eCSF report based on the one or more eCSF parameters to the network node, and the network node may receive the eCSF report from the UE. Therefore, eCSF may be enabled while taking into account the impact of the TPMI selected by the aggressor UE when calculating the eCSF report.

[0167] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is merely an illustration of the exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart may be rearranged based on design preferences. Further, some blocks may be combined or omitted. The attached method claims provide the elements of the various blocks in a sample order, but are not limited to the specific order or hierarchy provided.

[0168] 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 apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the various aspects described herein, but should be given the full scope consistent with the language claims. Unless otherwise specified, reference to an element in the singular form does not mean "one and only one", but "one or more". Terms such as "if", "when ..." and "while" do not mean an instantaneous time relationship or reaction. That is, these phrases (such as "when ...") do not mean an instantaneous action in response to the occurrence of an action or during the occurrence of an action, but simply imply that if the conditions are met, the action will occur, but no specific or instantaneous time constraints are required for the occurrence of the action. The word "exemplary" is used herein to mean "used as an example, instance or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having advantages over other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, which may include multiple A, multiple B, or multiple C. 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 "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a set 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 the first device receives data from the second device or sends data to the second device, data may be directly received / sent between the first device and the second device, or indirectly received / sent between the first device and the second device through a collection of devices. All structural and functional equivalents of the elements of the various aspects described throughout the present disclosure that are known or will be known later to a person of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. Words such as "module", "mechanism", "element", "device" cannot replace the word "component". Therefore, no claim element will be understood as a component plus function unless the element is explicitly stated using the phrase "component for..."

[0169] As used herein, the phrase "based on" should not be interpreted as referring to 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 interpreted as "based at least on A" unless specifically stated differently.

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

[0171] Aspect 1 is a method for performing wireless communication at a UE, comprising: estimating a CLI channel state based on a ZP-SRS from a second UE; estimating a downlink channel state based on a CSI-RS from a network node; estimating one or more eCSF parameters based on the CLI channel state, the downlink channel state, two or more interference assumptions, and at least one of a CPU specification, a timing specification, or a UE capability indication; and sending an eCSF report based on the one or more eCSF parameters to the network node.

[0172] Aspect 2 is a method according to aspect 1, wherein the CPU specification indicates a number of CPUs, the number being equal to a product of a number of CSI-RS resources and a number of the two or more interference hypotheses.

[0173] Aspect 3 is a method according to aspect 1, wherein the CPU specification indicates a number of CPUs, which is less than the product of the number of CSI-RS resources and the number of the two or more interference hypotheses.

[0174] Aspect 4 is a method according to aspect 1, wherein the CPU specification indicates the number of CPUs, and the number is the sum of the number of CSI-RS resources and a predefined number.

[0175] Aspect 5 is a method according to aspect 4, wherein the predefined number is 1.

[0176] Aspect 6 is a method according to any one of aspects 1 to 5, wherein the timing specification corresponds to a predefined high-latency class timing specification.

[0177] Aspect 7 is a method according to any one of aspects 1 to 5, wherein the timing specification corresponds to a predefined new delay class timing specification.

[0178] Aspect 8 is a method according to aspect 7, wherein the predefined new delay class timing specification is based at least in part on the number of the two or more interference hypotheses.

[0179] Aspect 9 is a method according to any one of aspects 7 and 8, wherein the predefined new latency class timing specification is based at least in part on one or more of the SCS, the number of reports, or the number of CSI-RS resources.

[0180] Aspect 10 is a method according to any one of aspects 1 to 9, further comprising: sending the UE capability indication to the network node.

[0181] Aspect 11 is a method according to any one of aspects 1 to 10, wherein the UE capability indication indicates a first UE capability associated with measuring one or more ZP-SRS resources.

[0182] Aspect 12 is a method according to aspect 11, wherein the UE capability indication includes an independent indication of the first UE capability associated with measuring the one or more ZP-SRS resources.

[0183] Aspect 13 is a method according to aspect 11, wherein the UE capability indication comprises a combined indication of a second UE capability associated with measuring both the one or more ZP-SRS resources and the one or more CSI-RS resources.

[0184] Aspect 14 is a method according to any one of aspects 1 to 13, wherein each interference hypothesis of the two or more interference hypotheses corresponds to a TPMI.

[0185] Aspect 15 is a method for performing wireless communications at a network node, comprising: sending a CSI-RS to a UE; receiving an eCSF based on one or more eCSF parameters from the UE, wherein the one or more eCSF parameters are based on a CLI channel state, a downlink channel state, two or more interference assumptions, and at least one of a CPU specification, a timing specification, or a UE capability indication, wherein the CLI channel state is based on a ZP-SRS from a second UE, and the downlink channel state is based on the CSI-RS.

[0186] Aspect 16 is a method according to aspect 15, wherein the CPU specification indicates a number of CPUs, the number being equal to a product of a number of CSI-RS resources and a number of the two or more interference hypotheses.

[0187] Aspect 17 is a method according to aspect 15, wherein the CPU specification indicates a number of CPUs, which is less than a product of a number of CSI-RS resources and a number of the two or more interference hypotheses.

[0188] Aspect 18 is a method according to aspect 15, wherein the CPU specification indicates the number of CPUs, the number being the sum of the number of CSI-RS resources and a predefined number.

[0189] Aspect 19 is a method according to aspect 18, wherein the predefined number is 1.

[0190] Aspect 20 is a method according to any one of aspects 15 to 19, wherein the timing specification corresponds to a predefined high-latency class timing specification.

[0191] Aspect 21 is a method according to any one of aspects 15 to 19, wherein the timing specification corresponds to a predefined new delay class timing specification.

[0192] Aspect 22 is a method according to aspect 21, wherein the predefined new delay class timing specification is based at least in part on the number of the two or more interference hypotheses.

[0193] Aspect 23 is a method according to any one of aspects 21 and 22, wherein the predefined new latency class timing specification is based at least in part on one or more of the SCS, the number of reports, or the number of CSI-RS resources.

[0194] Aspect 24 is a method according to any one of aspects 15 to 23, further comprising: receiving the UE capability indication from the UE.

[0195] Aspect 25 is a method according to any one of aspects 15 to 24, wherein the UE capability indication indicates a first UE capability associated with measuring one or more ZP-SRS resources.

[0196] Aspect 26 is a method according to aspect 25, wherein the UE capability indication includes an independent indication of the first UE capability associated with measuring the one or more ZP-SRS resources.

[0197] Aspect 27 is a method according to aspect 25, wherein the UE capability indication comprises a combined indication of a second UE capability associated with measuring both the one or more ZP-SRS resources and the one or more CSI-RS resources.

[0198] Aspect 28 is a method according to any one of aspects 15 to 27, wherein each interference hypothesis of the two or more interference hypotheses corresponds to a TPMI.

Claims

1. An apparatus for wireless communication at a user equipment (UE), comprising: Memory; and at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor configured to: estimating a cross-link interference (CLI) channel state based on a zero power (ZP)-sounding reference signal (SRS) (ZP-SRS) from a second UE; estimating a downlink channel state based on a channel state information (CSI)-reference signal (RS) (CSI-RS) from a network node; estimating one or more enhanced channel state feedback (eCSF) parameters based on the CLI channel state, the downlink channel state, two or more interference hypotheses, and at least one of a CSI processing unit (CPU) specification, a timing specification, or a UE capability indication; as well as An eCSF report based on the one or more eCSF parameters is sent to the network node.

2. The apparatus of claim 1, wherein the CPU specification indicates a number of CPUs, the number being equal to a product of a number of CSI-RS resources and a number of the two or more interference hypotheses. 3 . The apparatus of claim 1 , wherein the CPU specification indicates a number of CPUs that is less than a product of a number of CSI-RS resources and a number of the two or more interference hypotheses. 4 . The apparatus of claim 1 , wherein the CPU specification indicates a number of CPUs, the number being a sum of a number of CSI-RS resources and a predefined number. The apparatus of claim 4 , wherein the predefined number is 1.

6. The apparatus of claim 1, wherein the timing specification corresponds to a predefined high-latency class timing specification.

7. The apparatus of claim 1, wherein the timing specification corresponds to a predefined new delay class timing specification.

8. The apparatus of claim 7, wherein the predefined new delay class timing specification is based at least in part on a number of the two or more interference hypotheses.

9. The apparatus of claim 7, wherein the predefined new delay class timing specification is based at least in part on one or more of a subcarrier spacing (SCS), a number of reports, or a number of CSI-RS resources.

10. The apparatus of claim 1, wherein the at least one processor is configured to: The UE capability indication is sent to the network node.

11. The apparatus of claim 1, wherein the UE capability indication indicates a first UE capability associated with measuring one or more ZP-SRS resources.

12. The apparatus of claim 11, wherein the UE capability indication comprises a separate indication of the first UE capabilities associated with measuring the one or more ZP-SRS resources.

13. The apparatus of claim 11, wherein the UE capability indication comprises a combined indication of a second UE capability associated with measuring both the one or more ZP-SRS resources and the one or more CSI-RS resources.

14. The apparatus according to claim 1, further comprising: A transceiver is coupled to the at least one processor, wherein each of the two or more interference hypotheses corresponds to a transmitted precoding matrix indicator (TPMI).

15. A method of wireless communication at a user equipment (UE), comprising: estimating a cross-link interference (CLI) channel state based on a zero power (ZP)-sounding reference signal (SRS) (ZP-SRS) from a second UE; estimating a downlink channel state based on a channel state information (CSI)-reference signal (RS) (CSI-RS) from a network node; estimating one or more enhanced channel state feedback (eCSF) parameters based on the CLI channel state, the downlink channel state, two or more interference hypotheses, and at least one of a CSI processing unit (CPU) specification, a timing specification, or a UE capability indication; as well as An eCSF report based on the one or more eCSF parameters is sent to the network node.

16. An apparatus for wireless communication at a network node, comprising: Memory; and at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor configured to: sending a channel state information (CSI)-reference signal (CSI-RS) to a user equipment (UE); and An enhanced channel state feedback (eCSF) based on one or more eCSF parameters is received from the UE, wherein the one or more eCSF parameters are based on a cross-link interference (CLI) channel state, a downlink channel state, two or more interference assumptions, and at least one of a CSI processing unit (CPU) specification, a timing specification, or a UE capability indication, wherein the CLI channel state is based on a zero power (ZP)-sounding reference signal (SRS) (ZP-SRS) from a second UE, and the downlink channel state is based on the CSI-RS. 17 . The apparatus of claim 16 , wherein the CPU specification indicates a number of CPUs, the number being equal to a product of a number of CSI-RS resources and a number of the two or more interference hypotheses.

18. The apparatus of claim 16, wherein the CPU specification indicates a number of CPUs that is less than a product of a number of CSI-RS resources and a number of the two or more interference hypotheses.

19. The apparatus of claim 16, wherein the CPU specification indicates a number of CPUs, the number being a sum of a number of CSI-RS resources and a predefined number.

20. The apparatus of claim 19, wherein the predefined number is 1.

21. The apparatus of claim 16, wherein the timing specification corresponds to a predefined high-latency class timing specification.

22. The apparatus of claim 16, wherein the timing specification corresponds to a predefined new delay class timing specification.

23. The apparatus of claim 22, wherein the predefined new delay class timing specification is based at least in part on a number of the two or more interference hypotheses.

24. The apparatus of claim 22, wherein the predefined new delay class timing specification is based at least in part on one or more of a subcarrier spacing (SCS), a number of reports, or a number of CSI-RS resources.

25. The apparatus of claim 16, wherein the at least one processor is configured to: The UE capability indication is received from the UE.

26. The apparatus of claim 16, wherein the UE capability indication indicates a first UE capability associated with measuring one or more ZP-SRS resources.

27. The apparatus of claim 26, wherein the UE capability indication comprises a separate indication of the first UE capabilities associated with measuring the one or more ZP-SRS resources.

28. The apparatus of claim 26, wherein the UE capability indication comprises a combined indication of a second UE capability associated with measuring both the one or more ZP-SRS resources and one or more CSI-RS resources.

29. The apparatus of claim 16, further comprising: A transceiver is coupled to the at least one processor, wherein each of the two or more interference hypotheses corresponds to a transmitted precoding matrix indicator (TPMI).

30. A method for wireless communication at a network node, comprising: Sending a channel state information (CSI)-reference signal (CSI-RS) to a user equipment (UE); as well as An enhanced channel state feedback (eCSF) based on one or more eCSF parameters is received from the UE, wherein the one or more eCSF parameters are based on a cross-link interference (CLI) channel state, a downlink channel state, two or more interference assumptions, and at least one of a CSI processing unit (CPU) specification, a timing specification, or a UE capability indication, wherein the CLI channel state is based on a zero power (ZP)-sounding reference signal (SRS) (ZP-SRS) from a second UE, and the downlink channel state is based on the CSI-RS.

Images