Subband-based cross-link interference measurement reporting

By introducing a subband-based CLI measurement and reporting framework between the UE and network nodes, the problem of the UE being unable to detect different CLIs is solved, achieving more effective CLI mitigation and improving UE performance.

CN121039997APending Publication Date: 2025-11-28QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202480028440.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-05-11
Filing Date
2024-04-16
Publication Date
2025-11-28

AI Technical Summary

Technical Problem

In the prior art, user equipment (UE) cannot detect different cross-link interference (CLI) on different narrow frequency resources in each measurement subband, which makes it impossible for network nodes to effectively perform CLI mitigation, thereby affecting UE performance.

Method used

A subband-based CLI measurement and reporting framework is introduced, in which the UE and network node receive and transmit subband configurations to achieve subband-based CLI measurement and reporting, enabling the network node to mitigate different CLIs.

Benefits of technology

By supporting subband-based CLI measurements and reporting, network nodes can perform CLI mitigation more accurately, improving the overall performance of the UE and reducing the impact of CLI on the UE.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN121039997A_ABST
    Figure CN121039997A_ABST
Patent Text Reader

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive a subband configuration for inter-UE cross-link interference (CLI) measurements. The UE may transmit a subband-based CLI report indicating the subband-based inter-UE CLI measurement based at least in part on the subband configuration for the inter-UE CLI measurement. Numerous other aspects are described.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This Patent Application claims priority to U.S. Patent Application No. 18 / 315,983, filed May 11, 2023, entitled “SUBBAND BASED CROSS-LINK INTERFERENCE MEASUREMENT REPORTING,” and assigned to the assignee hereof. The disclosure of the priority application is considered part of and is incorporated by reference into this Patent Application. TECHNICAL FIELD

[0003] Aspects of the present disclosure relate generally to wireless communication and to techniques and apparatuses for subband-based cross-link interference (CLI) measurement reporting. BACKGROUND

[0004] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems can employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). 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, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3 GPP).

[0005] A wireless network can include one or more network nodes that support communications for wireless communication devices, such as a user equipment (UE) or multiple UEs. A UE can communicate with a network node via downlink communications and uplink communications. “Downlink” (or “DL”) refers to communications from network nodes to UEs, and “uplink” (or “UL”) refers to communications from UEs to network nodes. Some wireless networks can support device-to-device communications, such as via a local link (e.g., a sidelink (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, among others).

[0006] The above multiple access technologies have been adopted in various telecommunication standards to provide common protocols that enable different UEs to communicate on a municipal, national, regional, and / or global level. New Radio (NR), which can be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink, CP-OFDM and / or single-carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, and support beamforming, multiple input multiple output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR, and other radio access technologies remain useful. SUMMARY

[0007] In some implementations, an apparatus for wireless communication at a user equipment (UE) includes a memory and one or more processors coupled to the memory, the apparatus configured to: receive a sub-band configuration for inter-UE cross-link interference (CLI) measurement; and transmit a sub-band based CLI report indicating a sub-band based inter-UE CLI measurement based at least in part on the sub-band configuration for inter-UE CLI measurement.

[0008] In some implementations, an apparatus for wireless communication at a network node includes a memory and one or more processors coupled to the memory, the apparatus configured to: transmit a sub-band configuration for CLI measurement; and receive a sub-band based CLI report indicating a sub-band based inter-UE CLI measurement based at least in part on the sub-band configuration for inter-UE CLI measurement.

[0009] In some implementations, a method of wireless communication performed by a UE includes receiving a sub-band configuration for inter-UE CLI measurement; and transmitting a sub-band based CLI report indicating a sub-band based inter-UE CLI measurement based at least in part on the sub-band configuration for inter-UE CLI measurement.

[0010] In some implementations, a method of wireless communication performed by a network node includes transmitting a sub-band configuration for CLI measurement; and receiving a sub-band based CLI report indicating a sub-band based inter-UE CLI measurement based at least in part on the sub-band configuration for inter-UE CLI measurement.

[0011] In some implementations, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a UE, cause the UE to receive a sub-band configuration for inter-UE CLI measurement; and transmit a sub-band based CLI report indicating a sub-band based inter-UE CLI measurement based at least in part on the sub-band configuration for inter-UE CLI measurement.

[0012] In some implementations, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a network node, cause the network node to transmit a sub-band configuration for CLI measurement; and receive a sub-band based CLI report indicating a sub-band based inter-UE CLI measurement based at least in part on the sub-band configuration for inter-UE CLI measurement.

[0013] In some implementations, an apparatus for wireless communication includes means for receiving a sub-band configuration for inter-device CLI measurement; and means for transmitting a sub-band based CLI report indicating a sub-band based inter-device CLI measurement based at least in part on the sub-band configuration for inter-device CLI measurement.

[0014] In some implementations, an apparatus for wireless communication includes means for transmitting a sub-band configuration for CLI measurement; and means for receiving a sub-band based CLI report indicating a sub-band based inter-UE CLI measurement based at least in part on the sub-band configuration for inter-UE CLI measurement.

[0015] Aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, network entity, network node, wireless communication device, and / or processing system as substantially described with reference to and as illustrated by the drawings and specification.

[0016] The foregoing has outlined rather broadly the features and technical advantages of examples according to the disclosure in order that the detailed description that follows can be better understood. Additional features and advantages will be described below. The disclosed conception and specific examples can be readily utilized as bases for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both their organization and method of operation, together with associated advantages will be better understood from the following description when considered in connection with the accompanying drawings. Each of the figures is provided for the purpose of illustration and description, and is not intended as a definition of the limits of the claims.

[0017] While aspects are described in the present disclosure by illustration to some examples, those skilled in the art will understand that such aspects can be implemented in many different arrangements and scenarios. Techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, and / or artificial intelligence devices). Aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-level components. Devices incorporating described aspects and features can include additional components and features for implementation and practice of claimed and described aspects. For example, transmission and reception of wireless signals can include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or summers). It is intended that aspects described herein can be practiced in a wide variety of devices, components, systems, distributed arrangements, and / or end-user devices of varying sizes, shapes, and constitution. BRIEF DESCRIPTION OF DRAWINGS

[0018] To more fully understand the above-described features of the present disclosure, a further description can be had by reference to the various aspects, wherein some of the aspects are illustrated in the appended drawings. It is noted, however, that the appended drawings are not intended to be exhaustive or limiting of the present disclosure and that they are to be considered with the above description and not as limiting of the scope of the present disclosure. Identical reference numerals can identify identical or like elements throughout the various drawings.

[0019] Figure 1 is a diagram illustrating an example of a wireless network, in accordance with the present disclosure.

[0020] Figure 2 is a diagram illustrating an example of a network node communicating with user equipment (UE) in a wireless network, in accordance with the present disclosure.

[0021] Figure 3 is a diagram illustrating an example disaggregated base station architecture, in accordance with the present disclosure.

[0022] Figure 4 is a diagram illustrating an example of full duplex (FD) communication, in accordance with the present disclosure.

[0023] Figure 5 is a diagram illustrating an example of FD communication, in accordance with the present disclosure.

[0024] Figures 6 to 8 is a diagram illustrating an example of cross-link interference (CLI), in accordance with the present disclosure.

[0025] Figures 9 to 11 FIG. 1 is a diagram illustrating an example of a subband-based CLI measurement report, in accordance with aspects of the present disclosure.

[0026] Figures 12 to 13 FIG. 2 is a diagram illustrating an example process of a subband-based CLI measurement report, in accordance with aspects of the present disclosure.

[0027] Figures 14 to 15 FIG. 3 is a diagram of an example apparatus for wireless communication, in accordance with aspects of the present disclosure. DETAILED DESCRIPTION

[0028] A user equipment (UE) can send a cross-link interference (CLI) report to a network node to indicate a CLI to the network node. Depending on whether the CLI satisfies a threshold, the network node can perform CLI mitigation. The CLI on different narrower frequency resources of each measurement subband can be different due to frequency selectivity and the transmitting frequency resources being relatively close to lower or higher frequency resources of a band or uplink subband. However, the UE can not be configured to detect different CLIs on different narrower frequency resources of each measurement subband, and thus, the UE cannot report the CLI to the network node with such granularity. As a result, the network node can not perform CLI mitigation accordingly for the different CLIs, resulting in degraded performance of the UE.

[0029] Various aspects generally relate to subband-based CLI interference measurement reporting. Some aspects more specifically relate to subband-based CLI interference measurement reporting for subband full duplex (SBFD) and dynamic time division duplex (TDD). In some examples, a UE can receive, from a network node, a subband configuration for inter-UE CLI measurement. In some examples, the subband configuration for inter-UE CLI measurement can be commonly applicable to network node SBFD operation, partially or fully overlapping full duplex operation, and / or dynamic TDD operation. In some examples, the UE can transmit, to the network node, a subband-based CLI report indicating a subband-based inter-UE CLI measurement based at least in part on the subband configuration for inter-UE CLI measurement. In some examples, the UE can use a common framework to support subband-based CLI measurement and reporting, which can be commonly used by both SBFD and / or dynamic TDD.

[0030] Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, by supporting a common framework for subband-based CLI measurement and reporting, the described techniques can be used to perform subband-based CLI measurement and reporting for SBFD and / or dynamic TDD. A UE can report different CLIs on different narrower frequency resources of each measurement subband. A network node can perform CLI mitigation based at least in part on the different CLIs, which can improve the overall performance of the UE (e.g., the UE can experience less CLI due to the common framework supporting subband-based CLI measurement and reporting).

[0031] Various aspects of the disclosure are described more fully below with reference to the accompanying drawings. This disclosure may, however, be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided as illustrative examples so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. As such, various aspects of the disclosure can take many different forms with the scope of the disclosure being substantially limited only by the appended claims. It will be appreciated that the aspects of the disclosure disclosed herein can be implemented in one or more elements of a claim or claims. For example, an apparatus can be implemented using any number of the aspects disclosed herein.

[0032] Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as “elements”). These elements can be implemented using hardware, software, or combinations thereof, depending on the particular application and design constraints imposed on the overall system.

[0033] Although terminology commonly associated with 5G or new radio (NR) radio access technology (RAT) can be used in this document to describe various aspects, aspects of the disclosure can be applied to other RATs, such as 3G RAT, 4G RAT, and / or 5G later (e.g., 6G) RAT.

[0034] Figure 1is a diagram illustrating an example of a wireless network 100, in accordance with this disclosure. The wireless network 100 can be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or can include elements of a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, among others. The wireless network 100 can include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), one UE 120, or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. A network node 110 is a network node that communicates with the UE 120. As illustrated, the network node 110 can include one or more network nodes. For example, the network node 110 can be an aggregated network node, meaning that the aggregated network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single Radio Access Network (RAN) node (e.g., within a single device or unit). As another example, the network node 110 can be a disaggregated network node (sometimes referred to as a disaggregated base station), meaning that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed among two or more nodes, such as one or more Central Units (CUs), one or more Distributed Units (DUs), or one or more Radio Units (RUs).

[0035] In some examples, the network node 110 is or includes a network node (such as a RU) that communicates with UEs 120 via radio access links. In some examples, the network node 110 is or includes a network node (such as a DU) that communicates with other network nodes 110 via a front-haul link or a mid-haul link. In some examples, the network node 110 is or includes a network node (such as a CU) that communicates with other network nodes 110 via a mid-haul link or with a core network via a backhaul link. In some examples, the network node 110 (such as an aggregated network node 110 or a disaggregated network node 110) can include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. The network node 110 can include, for example, a NR base station, a LTE base station, a NodeB, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a DU, a RU, a CU, a mobility element of a network, a core network node, a network element, network equipment, a RAN node, or combinations thereof. In some examples, the network nodes 110 can interconnect to one another or to one or more other network nodes 110 in the wireless network 100 by various types of front-haul interfaces, mid-haul interfaces, and / or backhaul interfaces, such as direct physical connections, an air interface, or virtual networks.

[0036] In some examples, a network node 110 can provide communication coverage for a particular geographic area. In Third Generation Partnership Project (3GPP), the term "cell" can refer to a coverage area of a network node 110 and / or a network node subsystem serving the coverage area, depending on the context in which the term is used. A network node 110 can be a macro cell, a pico cell, a femto cell, and / or a another type of cell. A macro cell can cover a relatively large geographic area (e.g., several kilometers in radius) and can allow unrestricted access by UEs 120 with service subscriptions. A pico cell can cover a relatively small geographic area and can allow unrestricted access by UEs 120 with service subscriptions. A femto cell can cover a relatively small geographic area (e.g., a home) and can allow restricted access by UEs 120 associated with the femto cell, such as UEs 120 in a closed subscriber group (CSG). A network node 110 for a macro cell can be referred to as a macro network node. A network node 110 for a pico cell can be referred to as a pico network node. A network node 110 for a femto cell can be referred to as a femto network node or a home network node. In Figure 1 In the illustrated example, network node 110a can be a macro network node for a macro cell 102a, network node 110b can be a pico network node for a pico cell 102b, and network node 110c can be a femto network node for a femto cell 102c. A network node can support one or more (e.g., three) cells. In some examples, cells can not necessarily be stationary, and the geographic area of the cells can move according to the location of a mobile network node 110 (e.g., a mobile network node).

[0037] In some aspects, the term “base station” or “network node” can refer to an aggregated base station, a disaggregated base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a “base station” or “network node” can refer to a CU, a DU, a RU, a near real-time (near-RT) RAN intelligent controller (RIC), or a non-RT RIC, or a combination thereof. In some aspects, the term “base station” or “network node” can refer to one device configured to perform one or more functions, such as those described herein in connection with network node 110. In some aspects, the term “base station” or “network node” can refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of multiple different devices (which can be located in the same geographic location or different geographic locations) can be configured to perform at least a portion of a function, or to perform at least a portion of a function repeatedly, and the term “base station” or “network node” can refer to any one or more of these different devices. In some aspects, the term “base station” or “network node” can refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions can be instantiated on a single device. In some aspects, the term “base station” or “network node” can refer to one of a base station function, but not another base station function. In this way, a single device can include more than one base station.

[0038] Wireless network 100 can include one or more relay stations. A relay station is a network node that can receive a transmission of data from an upstream node (e.g., a network node 110 or a UE 120) and send a transmission of the data to a downstream node (e.g., a UE 120 or a network node 110). A relay station can be a UE 120 that can relay transmissions for other UEs 120. In Figure 1 In the example shown in FIG. 1, network node 110d (e.g., a relay network node) can communicate with network node 110a (e.g., a macro network node) and UE 120d in order to facilitate communication between network node 110a and UE 120d. A network node 110 that relays communications can be referred to as a relay station, a relay base station, a relay network node, a relay node, a repeater, or the like.

[0039] Wireless network 100 can be a heterogeneous network that includes network nodes 110 of different types, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, and / or the like. These different types of network nodes 110 can have different transmit power levels, different coverage areas, and / or different impacts on interference. For example, macro network nodes can have a high transmit power level (e.g., 5 to 40 Watts), while pico network nodes, femto network nodes, and relay network nodes can have relatively lower transmit power levels (e.g., 0.1 to 2 Watts).

[0040] A network controller 130 can couple to or communicate with a set of network nodes 110 and can provide coordination and control for the network nodes 110. The network controller 130 can communicate with the network nodes 110 via a backhaul communication link or communication links. The network nodes 110 can also communicate with one another, e.g., directly or indirectly via wireless backhaul communication links or wired backhaul communication links. In some aspects, the network controller 130 can be a CU or core network device, or can include a CU or core network device.

[0041] The UEs 120 can be dispersed throughout the wireless network 100, and each UE 120 can be stationary or mobile. A UE 120 can include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. A UE 120 can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicular component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, a UE function of a network node, and / or any other suitable device configured to communicate via a wireless or wired medium.

[0042] Some UEs 120 can be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs. MTC or eMTC UEs can include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags, that can communicate with a network node, another device (e.g., remote device), or some other entity. A

[0043] In general, any number of wireless networks 100 can be deployed in a given geographic area. Each wireless network 100 can support a particular RAT and can operate on one or more frequencies. A RAT can be referred to as a radio technology, an air interface, or the like. A frequency can be referred to as a carrier, a frequency channel, or the like. In

[0044] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly using one or more sidelink channels (e.g., without using network node 110 as an intermediary to communicate with one another). For example, UE 120 can perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110. Some communications between a UE 120 and a network node 110 can be transmitted indirectly via one or more network nodes 110 (e.g., macro RAN node, network controller, core network node, and / or the like). For example, communications between a UE 120 and a network node 110 can be transmitted indirectly via one or more backhaul links. Two or more UEs 120 can communicate directly using one or more sidelink channels (e.g., without using network node 110 as an intermediary to communicate with one another). For example, UEs 120 can be within a proximity threshold distance of one another, can be members of a vehicle-to-everything (V2X) group, and / or the like.

[0045] Devices of wireless network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various classes, bands, channels, and so on, according to frequency or wavelength. For example, devices of wireless network 100 can communicate using one or more operating bands. 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). It should be understood that, although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in various documents and articles. A similar nomenclatural issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite the fact that it falls into a range identified by the International Telecommunications Union (ITU) as “Extremely High Frequency” (EHF) bands (30 GHz - 300 GHz).

[0046] The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified operating bands for these mid-band frequencies as frequency range designation FR3 (7.125 GHz - 24.25 GHz). Bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and thus can effectively extend the features of FR1 and / or FR2 to mid-band frequencies. Moreover, even higher bands are currently under exploration to extend 5G NR operations beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4-a or FR4-1 (52.6 GHz - 71 GHz), FR4 (52.6 GHz - 114.25 GHz), and FR5 (114.25 GHz - 300 GHz). Each of these higher bands falls within the EHF band.

[0047] With the above examples in mind, unless specifically stated otherwise, it should be understood that the term “Sub-6 GHz” or the like is used herein to generically refer to frequencies that can be below 6 GHz, can be within FR1, or can include mid-band frequencies. Further, unless specifically stated otherwise, it should be understood that the term “millimeter wave” or the like is used herein to generically refer to frequencies that can include mid-band frequencies, can be within FR2, FR4, FR4-a, or FR4-1, and / or FR5, or can be within the EHF band. It is contemplated that frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0048] In some aspects, a UE (e.g., UE 120) can include a communications manager 140. As described in more detail elsewhere herein, the communications manager 140 can receive a sub-band configuration for inter-UE CLI measurement; and transmit a sub-band based CLI report indicating sub-band based inter-UE CLI measurements based at least in part on the sub-band configuration for inter-UE CLI measurement. Additionally, or alternatively, the communications manager 140 can perform one or more other operations described herein.

[0049] In some aspects, a network node (e.g., network node 110) can include a communications manager 150. As described in more detail elsewhere herein, the communications manager 150 can transmit a sub-band configuration for CLI measurement; and receive a sub-band based CLI report indicating sub-band based inter-UE CLI measurements based at least in part on the sub-band configuration for inter-UE CLI measurement. Additionally, or alternatively, the communications manager 150 can perform one or more other operations described herein.

[0050] As indicated above, Figure 1 are provided as examples. Other examples can differ from what is described with respect to Figure 1 the examples described with respect to

[0051] Figure 2 is a diagram illustrating an example 200 of a network node 110 communicating with a UE 120 in the wireless network 100, in accordance with the present disclosure. The network node 110 can be equipped with a set of antennas 234a through 234t, such as T antennas (T > 1). The UE 120 can be equipped with a set of antennas 252a through 252r, such as R antennas (R > 1). The network node 110 of example 200 includes one or more radio front end components, such as antennas 234 and modem 232. In some examples, the network node 110 can include an interface, communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 can not include radio frequency components that facilitate direct communication with UEs 120, such as one or more CUs or one or more DUs.

[0052] At the network node 110, a transmit processor 220 can receive data, from a data source 212, intended for the UE 120 (or a set of UEs 120). The transmit processor 220 can select one or more modulation and coding schemes (MCSs) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from that UE 120. The network node 110 can process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCSs selected for the UE 120 and can provide data symbols for the UE 120. The transmit processor 220 can process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling) and provide overhead symbols and control symbols. The transmit processor 220 can generate reference symbols for reference signals (e.g., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)) and synchronization signals (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)). A transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and / or the reference symbols, if applicable, and can provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems), shown as modems 232a through 232t. Each output symbol stream can be provided to a modulator component (shown as MOD) of a modem 232 using a respective modulator component. Each modem 232 can process a respective output symbol stream (e.g., for OFDM) using a respective modulator component to obtain an output sample stream. Each modem 232 can further process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream using a respective modulator component to obtain a downlink signal. The modems 232a through 232t can transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas), shown as antennas 234a through 234t.

[0053] At the UE 120, a set of antennas 252 (shown as antennas 252a through 252r) can receive the downlink signals from network nodes 110 and / or other network nodes 110 and can provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a through 254r). For example, each received signal can be provided to a demodulator component (shown as DEMOD) of a modem 254. Each modem 254 can use a respective demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) a received signal to obtain input samples. Each modem 254 can use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 can obtain received symbols from modems 254, can perform MIMO detection on the received symbols if applicable, and can provide detected symbols. A receive processor 258 can process (e.g., demodulate and decode) the detected symbols, can provide decoded data for the UE 120 to a data sink 260, and can provide decoded control information and system information to a controller / processor 280. The term “controller / processor” can refer to one or more controllers, one or more processors, or combinations thereof. A channel processor can determine reference signal received power (RSRP) parameters, received signal strength indicator (RSSI) parameters, reference signal received quality (RSRQ) parameters, and / or CQI parameters, among other examples. In some examples, one or more components of UE 120 can be included in a housing 284.

[0054] A network controller 130 can include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 can include, for example, one or more devices in a core network. The network controller 130 can communicate with the network node 110 via the communication unit 294.

[0055] One or more antennas (e.g., antennas 234a through 234t and / or antennas 252a through 252r) can include or be included in one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, among other examples. An antenna panel, antenna group, set of antenna elements, and / or antenna array can include one or more antenna elements (within a single housing or multiple housings), a set of co-planar antenna elements, a set of non-co-planar antenna elements, and / or one or more antenna elements coupled to one or more transmit and / or receive components (such as, for example, one or more components in the transceiver 288 and / or the transceiver 254) in a device. Figure 2 ​

[0056] On the uplink, at UE 120, a transmit processor 264 can receive and process data from a data source 262 and control information (e.g., for reports comprising RSRP, RSSI, RSRQ, and / or CQI) from controller / processor 280. Transmit processor 264 can generate reference symbols for one or more reference signals. The symbols from transmit processor 264 can be precoded by a TX MIMO processor 266 if applicable, further processed by modems 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to network node 110. In some examples, modems 254 of UE 120 can include modulators and demodulators. In some examples, UE 120 includes a transceiver. The transceiver can include any combination of antenna 252, modems 254, MIMO detector 256, receive processor 258, transmit processor 264, and / or TX MIMO processor 266. The transceiver can be used by a processor (e.g., controller / processor 280) and memory 282 to perform aspects of any of the methods described herein (for example, with reference to Figures 9 to 15 ) and / or with respect to other processes described herein.

[0057] At network node 110, the uplink signals from UE 120 and / or other UEs can be received by antennas 234, processed by modems 232 (e.g., demodulator components (shown as DEMOD) of modems 232), detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information transmitted by UE 120. Receive processor 238 can provide the decoded data to a data sink 239 and the decoded control information to controller / processor 240. Network node 110 can include communication unit 244 and can communicate with network controller 130 via communication unit 244. Network node 110 can include scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, modems 232 of network node 110 can include modulators and demodulators. In some examples, network node 110 includes a transceiver. The transceiver can include any combination of antenna 234, modems 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver can be used by a processor (e.g., controller / processor 240) and memory 242 to perform aspects of any of the methods described herein (for example, with reference to Figures 9 to 15 ) and / or with respect to other processes described herein.

[0058] Controller / processor 240 of network node 110, controller / processor 280 of UE 120, and / orFigure 2 Any other component may perform one or more techniques associated with subband-based CLI measurement reporting, as described in more detail elsewhere herein. For example, the controller / processor 240 of network node 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component that can execute or direct, for example Figure 12 Process 1200 Figure 13 The operation of process 1300 and / or other processes as described herein. Memory 242 and memory 282 may store data and program code for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, one or more instructions may cause one or more processors, UE 120 and / or network node 110 to perform or direct, for example, when executed by one or more processors of network node 110 and / or UE 120 (e.g., directly executed, or executed after compilation, transformation and / or interpretation). Figure 12 Process 1200 Figure 13 The operation of process 1300 and / or other processes as described herein. In some examples, the execution instructions may include run instructions, transform instructions, compile instructions and / or interpret instructions, etc.

[0059] In some aspects, the UE (e.g., UE 120) includes: components for receiving subband configurations for inter-UE CLI measurements; and / or components for transmitting subband-based CLI reports indicating subband-based inter-UE CLI measurements, at least in part based on the subband configurations for inter-UE CLI measurements. Components for the UE to perform the operations described herein may include, for example, one or more of the following: a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0060] In some aspects, a network node (e.g., network node 110) includes means for transmitting a subband configuration for CLI measurement; and / or means for receiving a subband-based CLI report indicating subband-based inter-UE CLI measurements based at least in part on the subband configuration for inter-UE CLI measurement. The means for the network node to perform operations described herein can include, for example, one or more of the communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

[0061] Although Figure 2 The blocks in FIG. 14 are illustrated as distinct components only for the sake of clarity, and numerous implementations of the blocks can be found in single hardware, software, or combined components. For example, the functions described for transmit processor 264, receive processor 258, and / or TX MIMO processor 266 can be performed by controller / processor 280 or under the control of the controller / processor.

[0062] As indicated above, Figure 2 are provided as examples. Other examples can differ from what is described with respect to the examples Figure 2 described with respect to the examples

[0063] Deployments of communication systems, such as 5G NR systems, can be arranged in a variety of ways with various components or constituent parts. In a 5G NR system or network, a network node, network entity, mobility element of a network, RAN node, core network node, network element, base station, or network equipment can be implemented in an aggregated architecture or a disaggregated architecture. For example, a base station, such as a Node B (NB), an evolved NB (eNB), an NR base station, a 5G NB, an access point (AP), a TRP, or a cell, or one or more units (or one or more components) performing base station functionality can be implemented as an aggregated base station (also referred to as a standalone base station or a monolithic base station) or a disaggregated base station. A “network entity” or “network node” can refer to a disaggregated base station or one or more units of a disaggregated base station, such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof.

[0064] Aggregated base stations (e.g., aggregated network nodes) can be configured to utilize radio protocol stacks that are physically or logically integrated within a single RAN node (e.g., within a single device or unit). Disaggregated base stations (e.g., disaggregated network nodes) can be configured to utilize protocol stacks that are physically or logically distributed between two or more units, such as one or more CUs, one or more DUs, or one or more RUs. In some examples, a CU can be implemented within a network node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually spread across one or more other network nodes. The DUs can be implemented to communicate with one or more RUs. Each of the CUs, DUs, and RUs can also be implemented as virtual units, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), among other examples.

[0065] Base station type operations or network designs can take into account the aggregated nature of base station functionality. For example, disaggregated base stations can be utilized in IAB networks, open radio access networks (O-RAN (such as network configurations initiated by the O-RAN Alliance)), or virtualized radio access networks (vRAN, also referred to as cloud radio access networks (C-RAN)) to facilitate scaling of a communication system by separating base station functionality into one or more units that can be deployed individually. Disaggregated base stations can include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which can enable flexibility in network design. The various units of a disaggregated base station can be configured for wired or wireless communication with at least one other unit of the disaggregated base station.

[0066] Figure 3 FIG. 1 is a diagram illustrating an example disaggregated base station architecture 300, in accordance with the present disclosure. The disaggregated base station architecture 300 can include a CU 310 that can communicate directly with a core network 320 via a backhaul link, or indirectly through one or more disaggregated control units, such as a near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 can communicate with one or more DUs 330 via respective fronthaul links, such as over F1 interfaces. Each of the DUs 330 can communicate with one or more RUs 340 via respective front-haul links. Each of the RUs 340 can communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, the UEs 120 can be simultaneously served by multiple RUs 340.

[0067] Each of the units (including CU 310, DU 330, RU 340), as well as the near-RT RIC 325, non-RT RIC 315, and SMO framework 305, can include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each of the units, or an associated processor or controller of the unit, that provides instructions to one or more communication interfaces of the respective unit, can be configured to communicate with one or more of the other units via the transmission media. In some examples, each of the units can include a wired interface configured to receive or transmit signals to one or more of the other units through a wired transmission medium, and a wireless interface that can include a receiver, a transmitter, or a transceiver (such as a RF transceiver) configured to receive or transmit signals to one or more of the other units through a wireless transmission medium, or both.

[0068] In some aspects, the CU 310 can host one or more higher layer control functions. Such control functions can include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, among others. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 310. The CU 310 can be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP) functionality), control plane functionality (e.g., central unit-control plane (CU-CP) functionality), or a combination thereof. In some implementations, the CU 310 can be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bi-directionally with the CU-CP units via an interface, such as an El interface. The CU 310 can be implemented to communicate with the DU 330 for network control and signaling, as desired.

[0069] Each DU 330 can correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 can 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 in accordance with a functional split, such as a functional split defined by 3 GPP. In some aspects, the one or more high PHY layers can be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation, among other examples. In some aspects, the DU 330 can also host one or more low PHY layers, such as implemented by one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, or physical random access channel (PRACH) extraction and filtering, among other examples. Each layer (which can also be referred to as a module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0070] Each RU 340 can implement low layer functionality. In some deployments, the RUs 340 controlled by the DUs 330 can correspond to logical nodes that host RF processing functions or low PHY layer functions based on a functional split (e.g., a functional split defined by 3 GPP), such as a low layer functional split, such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, among other examples. In such an architecture, each RU 340 can be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RUs 340 can be controlled by the corresponding DUs 330. In some scenarios, this configuration can enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0071] The SMO framework 305 can be configured to support RAN deployment and orchestration of non-virtualized network elements and virtualized network elements. For non- virtualized network elements, the SMO framework 305 can be configured to support deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface, such as an Ol interface. For virtualized network elements, the SMO framework 305 can be configured to interact with a cloud computing platform, such as an Open Cloud (O-Cloud) platform 390, to perform network element lifecycle management, such as instantiating virtualized network elements, via a cloud computing platform interface, such as an 02 interface. Such virtualized network elements can include, but are not limited to, CUs 310, DUs 330, RUs 340, non-RT RICs 315, and near-RT RICs 325. In some implementations, the SMO framework 305 can communicate with hardware aspects of a 4G RAN, such as an Open eNB (O-eNB) 311, via an Ol interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of the one or more RUs 340 via a respective Ol interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support functionality of the SMO framework 305.

[0072] The non-RT RIC 315 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and update, or policy-based steering of applications / features in the near-RT RIC 325. The non-RT RIC 315 can be coupled to, or in communication with, the near-RT RIC 325, such as via an Al interface. The near-RT RIC 325 can be configured to include logical functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions by an interface, such as via an E2 interface, that connects one or more CUs 310, one or more DUs 330, or both, and an O-eNB with the near-RT RIC 325.

[0073] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 325, the non-RT RIC 315 can receive parameters or external enrichment information from an external server. Such information can be utilized by the near-RT RIC 325 and can be received at the SMO framework 305 or the non-RT RIC 315 from non-network data sources or from network functions. In some examples, the non-RT RIC 315 or the near-RT RIC 325 can be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 can monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305, such as reconfiguration via the Ol interface, or through creation of RAN management policies, such as Al interface policies.

[0074] As indicated above, Figure 3 are provided as examples. Other examples can differ from what is described Figure 3 with respect to the examples described in this regard.

[0075] Full-duplex (FD) operation can involve in-band full-duplex (IBFD) operation, in which transmission and reception can occur on the same time and frequency resources. Based at least in part on full or partial overlap, downlink direction and uplink direction can share the same IBFD time / frequency resources. Alternatively, FD operation can involve SBFD operation (or flexible duplexing), in which transmission and reception can occur simultaneously but on different frequency resources. Downlink resources can be separated from uplink resources in the frequency domain. In SBFD operation, frequency overlap of downlink and uplink can not occur.

[0076] Figure 4 is a diagram illustrating example 400 of FD communication in accordance with the present disclosure.

[0077] As shown by reference number 402, downlink resources 404 and uplink resources 406 can share the same IBFD time / frequency resources based at least in part on full overlap. As shown by reference number 408, downlink resources 410 and uplink resources 412 can share the same IBFD time / frequency resources based at least in part on partial overlap. As shown by reference number 414, downlink resources 416 and uplink resources 420 can be associated with the same time but different frequencies. Downlink resources 416 and uplink resources 420 can be separated by a guard band 418.

[0078] As indicated above, Figure 4 are provided as examples. Other examples can differ from what is described Figure 4 with respect to the examples described in this regard.

[0079] Figure 5is a diagram illustrating an example 500 of FD communication in accordance with the present disclosure.

[0080] As shown by reference 502, an FD network node (e.g., network node 110a) can communicate with a half-duplex (HD) UE. The FD network node can experience a CLI from another FD network node (e.g., network node 110d). The CLI from another FD network node can be an inter-network node CLI. The FD network node can experience self-interference (SI). The FD network node can receive an uplink transmission from a first HD UE (e.g., UE 120a) and the FD network node can transmit a downlink transmission to a second HD UE (e.g., UE 120e). The FD network node can receive the uplink transmission and transmit the downlink transmission on the same time slot (e.g., simultaneous reception / transmission). The second HD UE can experience a CLI from the first HD UE (e.g., inter-UE CLI).

[0081] As shown by reference 504, an FD network node (e.g., network node 110a) can communicate with an FD UE. The FD network node can experience a CLI from another FD network node (e.g., network node 110d). The FD network node can experience SI. The FD network node can transmit a downlink transmission to a first FD UE (e.g., UE 120a) and the FD network node can receive an uplink transmission from the first FD UE at the same time as the downlink transmission. The FD network node can transmit a downlink transmission to a second FD UE (e.g., UE 120e). The second HD UE can experience a CLI from the first HD UE. The first UE can experience SI.

[0082] As shown by reference 506, a first FD network node (e.g., network node 110a), which can be associated with multiple transmission reception points (TRPs), can communicate with a SBFD UE. The first FD network node can experience a CLI from a second FD network node (e.g., network node 110d). The first FD network node can receive an uplink transmission from a first SBFD UE (e.g., UE 120a). The second FD network node can transmit a downlink transmission to both the first SBFD UE and a second SBFD UE (e.g., UE 120e). The second SBFD UE can experience a CLI from the first SBFD UE. The first SBFD UE can experience SI.

[0083] As shown by reference number 508, the SBFD slot can be associated with non-overlapping uplink / downlink subbands. The SBFD slot can be associated with simultaneous transmission / reception of downlink / uplink on a subband basis. Within the component carrier bandwidth, the uplink resources 512 can be between the first downlink resources 510 and the second downlink resources 514 in the frequency domain. The first downlink resources 510, the second downlink resources 514, and the uplink resources 512 can all be associated with the same time.

[0084] SBFD operation can increase uplink duty cycle, which can result in latency reduction (e.g., downlink signals can be received in uplink-only slots, which can enable latency savings) and uplink coverage improvement. SBFD operation can improve system capacity, resource utilization, and / or spectral efficiency. SBFD operation can enable flexible and dynamic uplink / downlink resource adaptation according to uplink / downlink traffic in a robust manner.

[0085] As indicated above, Figure 5 are provided as examples. Other examples can differ from what is described with respect to Figure 5 the examples described with respect to

[0086] When a UE operates in HD mode and a network node operates in SBFD / IBFD mode, there can be various sources of interference for the UE. The UE can experience inter-cell interference from other network nodes. The UE can experience intra-cell CLI, which can be interference from UEs in the same cell. The UE can experience inter-cell CLI, which can be interference from UEs in neighboring cells. Further, when the UE is an FD UE, the UE can experience SI (e.g., the UE’s downlink transmissions can cause interference to the uplink transmissions associated with the UE, or vice versa). In the case of FD with subband non-overlap, inter-UE CLI handling can address intra-subband CLI and / or inter-subband CLI.

[0087] Figure 6 is a diagram illustrating an example 600 of CLI in accordance with the present disclosure.

[0088] As Figure 6As shown, in a dynamic TDD scenario, the first network node 110a in the first cell 602 can receive uplink transmissions from the first UE 120a. The second network node 110d in the second cell 604 can transmit downlink transmissions to the second UE 120e. The second UE 120e can experience interference from the first UE 120a. In other words, the first UE 120a can cause interference to the second UE 120e, where the interference can be based at least in part on the uplink transmissions from the first UE 120a. The interference can be inter-cell, inter-UE CLI. Further, the first network node 110a can experience inter-network node (e.g., inter-gNB) CLI from the second network node 110d.

[0089] As indicated above, Figure 6 are provided by way of example. Other examples can differ from those described. Figure 6 without departing from the scope of the disclosure.

[0090] Figure 7 is a diagram illustrating an example 700 of CLI according to the present disclosure.

[0091] As Figure 7As shown, in the SBFD scenario, the first network node 110a in the first cell 702 can receive an uplink transmission from the first UE 120a in the first cell 702. The first network node 110a can transmit a downlink transmission to the fourth UE 120b in the first cell 702. The first UE 120a can cause inter-subband (SB) intra-cell CLI to the fourth UE 120b based at least in part on the uplink transmission of the first UE 120a. The second network node 110d in the second cell 704 can receive an uplink transmission from the third UE 120c in the second cell 704. The second network node 110d can transmit a downlink transmission to the second UE 120e in the second cell 704. The third UE 120c can cause SB inter-cell intra-CLI to the second UE 120e based at least in part on the uplink transmission of the third UE 120c. The uplink transmission of the third UE 120c can cause SB inter-cell intra-CLI to the downlink transmission of the second UE 120e. Further, the first UE 120a in the first cell 702 can cause SB inter-cell inter-UE CLI to the second UE 120e in the second cell 704 based at least in part on the uplink transmission of the first UE 120a. The uplink transmission of the first UE 120a can cause SB inter-cell inter-UE CLI to the downlink transmission of the second UE 120e. Further, the first network node 110a can cause SB inter-gNB CLI to the second network node 110d, and vice versa. The downlink transmission of the first network node 110a can cause SB inter-gNB CLI to the uplink transmission of the second network node 110d. The downlink transmission of the second network node 110d can cause SB inter-gNB CLI to the uplink transmission of the first network node 110a.

[0092] As indicated above, Figure 7 are provided as examples. Other examples can differ from what is described Figure 7 with respect to the examples described.

[0093] Figure 8 is a diagram illustrating an example 800 of CLI according to the present disclosure.

[0094] As Figure 8As shown, in the fully overlapping FD scenario, the first network node 110a in the first cell 802 can receive an uplink transmission from the first UE 120a in the first cell 802. The first network node 110a can transmit a downlink transmission to the fourth UE 120b in the first cell 802. The first UE 120a can cause intra-cell CLI to the fourth UE 120b based at least in part on the uplink transmission of the first UE 120a. The second network node 110d in the second cell 804 can receive an uplink transmission from the third UE 120c in the second cell 804. The second network node 110d can transmit a downlink transmission to the second UE 120e in the second cell 804. The third UE 120c can cause intra-cell CLI to the second UE 120e based at least in part on the uplink transmission of the third UE 120c. Further, the first UE 120a in the first cell 702 can cause inter-cell CLI to the second UE 120e in the second cell 804 based at least in part on the uplink transmission of the first UE 120a. Further, the first network node 110a can cause in-band inter-gNB CLI to the second network node 110d, and vice versa.

[0095] As indicated above, Figure 8 are provided by way of example. Other examples can differ from those described. Figure 8 without departing from the spirit and scope of the disclosure.

[0096] A UE can transmit a CLI report to a network node to indicate a CLI to the network node. Depending on whether the CLI satisfies a threshold, the network node can perform CLI mitigation. Due to frequency selectivity and the transmission frequency resource being relatively close to a lower or higher frequency resource of a band or uplink subband, the CLI on different narrower frequency resources of each measurement subband can be different. However, the UE can not be configured to detect different CLIs on different narrower frequency resources of each measurement subband, and thus, the UE cannot report the CLI to the network node with such granularity. As a result, the network node can not perform CLI mitigation on the different CLIs accordingly, resulting in a performance degradation of the UE.

[0097] In various aspects of the techniques and apparatuses described herein, a UE can receive, from a network node, a subband configuration for inter-UE CLI measurement. The subband configuration for inter-UE CLI measurement can be collectively applicable to network node SBFD operation, partially or fully overlapping full duplex operation, and / or dynamic TDD operation. The UE can transmit, to the network node, a subband-based CLI report indicating subband-based inter-UE CLI measurement based at least in part on the subband configuration for inter-UE CLI measurement. The UE can support subband-based CLI measurement and reporting using a common framework, which can be commonly used by both SBFD and / or dynamic TDD. For dynamic / flexible TDD, a narrower frequency granularity of CLI reporting can be considered for layer 1 (L1) or layer 2 (L2) (L1 / L2) based UE-to-UE co-channel CLI measurement and reporting. Thus, the UE can report different CLIs on different narrower frequency resources of each measurement subband. The network node can perform CLI mitigation based at least in part on the different CLIs, which can improve overall performance of the UE (e.g., the UE can experience less CLI due to the common framework supporting subband-based CLI measurement and reporting).

[0098] In some aspects, the subband configuration for inter-UE CLI measurement can be configured via channel state information (CSI) reporting fields. Subband information can be implicitly derived from other subband-specific fields in the CSI, such as precoding matrix indicator (PMI) or channel quality indicator (CQI). The subband size can be related to a downlink bandwidth part (BWP). The subband-based CLI reporting can be triggered when CQI or PMI is requested. Further, the UE can be configured to measure CLI on downlink and / or uplink subbands.

[0099] Figure 9 is a diagram illustrating an example 900 associated with subband-based CLI measurement reporting, in accordance with the present disclosure. As shown, the example 900 includes communication between a UE (e.g., UE 120) and a network node (e.g., network node 110). In some aspects, the UE and network node can be included in a wireless network, such as wireless network 100. Figure 9

[0100] ​As shown by reference number 902, the UE can receive, from the network node, a subband configuration for inter-UE CLI measurement. The subband configuration for inter-UE CLI measurement can be commonly applicable to network node SBFD operation, partially or fully overlapping full duplex operation, or dynamic TDD operation (e.g., downlink resources and uplink resources can be dynamically adjusted). The subband configuration for inter-UE CLI measurement can be associated with measurement of one or more downlink subbands or uplink subbands, or measurement of multiple downlink subbands and uplink subbands in SBFD operation. The subband configuration for inter-UE CLI measurement can be associated with measurement of different CLI levels per different sub-subband within a downlink or uplink subband. The subband configuration for inter-UE CLI measurement can be associated with measurement of different CLI levels per different resource block set or measurement subband in dynamic TDD operation.

[0101] In some aspects, for inter-UE inter-subband CLI measurement, a framework can be defined to support a narrower frequency granularity for CLI measurement and reporting commonly used for both SBFD and dynamic TDD. SBFD can use the framework to measure per downlink subband based CLI or per uplink subband based CLI. SBFD can use the framework to measure different CLI levels per different sub-subband within each downlink or uplink subband. Dynamic TDD can use the framework to measure different CLI levels per different resource block (RB) set or measurement subband.

[0102] In some aspects, due to frequency selectivity and the relative proximity of the transmission frequency resources to lower or higher frequency resources of the band or uplink subband, the CLI on different narrower frequency resources of each measurement subband can be different. Thus, the framework can support subband based measurement and reporting that can be commonly used by both SBFD and / or dynamic TDD.

[0103] In some aspects, the subband configuration for inter-UE CLI measurement can be associated with one or more fields in a CSI report configuration, and the one or more fields can indicate a number of subbands and a subband size. In some aspects, the subband configuration for inter-UE CLI measurement can be associated with one or more fields in an information element (IE) for CLI report configuration. In some aspects, the subband configuration for inter-UE CLI measurement can be based at least in part on a PMI or CQI subband configuration, and the subband based CLI reporting can be based at least in part on the PMI or CQI subband configuration. In some aspects, the subband configuration for inter-UE CLI measurement can be based at least in part on a modified PMI or CQI subband configuration, and the modified PMI or CQI subband configuration can indicate a scalar field to indicate one or more of a number of subbands or a subband size.

[0104] In some aspects, a common framework for supporting subband-based CLI reporting for FD and / or dynamic TDD can be defined. For subband-based CLI reporting, the subband configuration for CLI measurement can be configured as a field in a CSI-ReportConfig IE (or IE for CLI reporting configuration). The CSI-ReportConfig IE can include a CLI format indicator (cli-FormatIndicator) that can be associated with a CLI reporting band (cli-ReportingBand). The CLI reporting band can be associated with multiple subbands (e.g., subband 3, subband 4, subband 5, etc.).

[0105] In some aspects, the subband configuration for inter-UE CLI measurement can be based at least in part on a reused PMI or CQI subband configuration (e.g., when the CLI is captured in an existing CQI report). When a network node configures a UE to report a CLI, to save overhead, the UE can implicitly reuse the PMI / CQI subband configuration to report the CLI. When no field is indicated for a separate CLI subband configuration, the PMI / CQI subband configuration can be reused, or the PMI / CQI subband configuration can be reused based at least in part on an indication from the network node.

[0106] In some aspects, the subband configuration for inter-UE CLI measurement can be based at least in part on a modified PMI / CQI subband configuration (e.g., when the CLI is captured in an existing CQI report). A scalar can be added to the PMI / CQI subband configuration (e.g., the number of subbands multiplied by 2 or multiplied by 0.5, or the subband size multiplied by 2 or multiplied by 0.5, which can save overhead). The scalar can be added to a scalar field. An explicit indication field for a separate CLI subband configuration can not be needed and a network node indication can not be needed.

[0107] In some aspects, the wideband CLI reporting can be a default configuration, and the subband-based CLI reporting can be based at least in part on reception of a configuration of subbands for inter-UE CLI measurement. In some aspects, the subband-based CLI reporting can be associated with a subband size. The subband size can be associated with a UE downlink BWP size, or the subband size can be associated with a UE downlink BWP size and a downlink subband size for SBFD operation. In some aspects, the subband size can be associated with a CLI subband size. The CLI subband size can be smaller than a PMI or CQI subband size, and multiple CLI subbands within a PMI or CQI subband can collectively be used for CQI CLI interference calculation. The CLI subband size can be larger than a PMI or CQI subband size, and for each CQI CLI interference calculation, a same CLI can be assumed across multiple PMI or CQI subbands.

[0108] In some aspects, the default configuration can be wideband CLI reporting. The subband size can be related to a UE downlink BWP size. The subband size can be related to a UE downlink BWP size and a downlink subband size for SBFD operation. The CLI subband size can be the same or different than a PMI / CQI subband size (e.g., when CLI is captured in CQI metrics as additional interference). When the CLI subband size is smaller than the CQI subband size, multiple CLI subbands (e.g., all CLI subbands) within each CQI subband can collectively be used for CQI interference calculation. When the CLI subband size is larger than the CQI subband size, for each subband CQI calculation, a same CLI can be assumed across multiple CQI subbands (e.g., all CQI subbands). When the CLI subband size is approximately equal to the CQI subband size, there can be no ambiguity.

[0109] In some aspects, the subband-based inter-UE CLI measurement can be based at least in part on a subband size equal to a CSI PMI or CQI subband size, based at least in part on a request for reporting subband PMI or CQI. In some aspects, a UE can be requested to report subband PMI / CQI. In this case, CLI can be implicitly measured with subband CLI having a subband size equal to a CSI PMI / CQI subband size, which can improve accuracy of channel measurement.

[0110] In some aspects, subband-based CLI reporting can be for SBFD operation and can report a CLI for one or more downlink subbands or uplink subbands, or for multiple downlink subbands and uplink subbands. In some aspects, subband-based CLI reporting can be based at least in part on implicit measurement and reporting of each downlink subband and uplink subband, and the implicit measurement and reporting of each downlink subband and uplink subband can be based at least in part on a semi-static SBFD configuration in a SBFD symbol or slot. In some aspects, subband-based CLI reporting can be based at least in part on implicit measurement and reporting of uplink subbands, and the implicit measurement and reporting of uplink subbands can be based at least in part on a semi-static SBFD configuration in a SBFD symbol or slot. In some aspects, subband-based CLI reporting can be based at least in part on implicit measurement and reporting of each downlink subband, and the implicit measurement and reporting of each downlink subband can be based at least in part on a semi-static SBFD configuration in a SBFD symbol or slot.

[0111] In some aspects, subband-based CLI reporting can be based at least in part on explicit measurement and reporting of downlink or uplink subbands that are explicitly configured to the network node, and the explicit measurement and reporting can be based at least in part on a CLI or CSI reporting configuration. The explicit measurement and reporting can be based at least in part on a configuration of unequal or equal subband sizes for downlink subbands and uplink subbands, and a bitmap can indicate one or more subbands for the explicit measurement and reporting. The UE can receive, from the network node, a configuration of different subband sizes associated with the unequal or equal subband sizes, where the configuration can indicate a subband number and a corresponding subband size. In some aspects, the UE can receive, from the network node, a MAC control element (MAC-CE) or a downlink control information (DCI) including a flag field to indicate whether the subband-based CLI reporting is based at least in part on: implicit measurement and reporting of each downlink subband and uplink subband, implicit measurement and reporting of uplink subbands, and / or implicit measurement and reporting of each downlink subband.

[0112] In some aspects, for inter-UE subband-inter CLI measurement, in a first method, the victim UE can measure RSSI and / or signal-to-interference-plus-noise ratio (SINR) within a downlink subband. In a second method, the victim UE can measure RSRP of the aggressor UE within an uplink subband. In a third method, the victim UE can measure RSSI within an uplink subband. When the uplink subband is confined within a downlink BWP, the restriction of measuring the CLI only within the downlink BWP can not prohibit the UE from measuring the CLI in the uplink subband.

[0113] In some aspects, subband-based CLI reporting for SBFD can be used to report a CLI per downlink or uplink subband. In some aspects, only one configuration can be supported. In a first option, a UE can implicitly measure and report each downlink and uplink subband (e.g., when using the first, second, and third methods) based at least in part on a semi-static SBFD configuration (e.g., time / frequency configuration) in a SBFD symbol / slot. In the first option, no specific subband configuration can be needed in the reporting configuration. In a second option, a UE can implicitly measure and report uplink subbands (e.g., when using only the second or third method) based at least in part on a semi-static SBFD configuration in a SBFD symbol / slot. In the second option, no specific subband configuration can be needed in the reporting configuration. In a third option, a UE can implicitly measure and report each downlink subband (e.g., when using only the first method) based at least in part on a semi-static SBFD configuration in a SBFD symbol / slot. In the third option, no specific subband configuration can be needed in the reporting configuration. In a fourth option, a UE can explicitly measure and report downlink / uplink subbands explicitly configured by a network node based at least in part on a CLI / CSI reporting configuration. Unequal / equal subband size (e.g., 40 MHz downlink subband size and 20 MHz uplink subband size for SBFD) configurations for measurement and reporting can be supported. In the fourth option, a network node can need to configure different subband sizes (e.g., subband numbers with corresponding subband sizes in the reporting configuration). A bitmap can be used to indicate one or more subbands for subband-based CLI reporting.

[0114] In some aspects, multiple configurations can be supported. A flag field can be added in a triggering MAC-CE or DCI to indicate that the subband-based CLI reporting is associated with a specific option (e.g., the first, second, or third option (e.g., when the fourth option is not configured)), where different options can be pre-defined in the specification. A default subband configuration can be configured via RRC signaling.

[0115] In some aspects, different subband-based CLI reports can be associated with different reporting quantities or metrics, and the subband-based CLI reporting can be based at least in part on a per-subband and per-reporting quantity or CLI metric reporting configuration. The UE can receive, from the network node, a per-subband and per-reporting quantity or CLI metric configuration for two CLI reporting configurations. A first CLI reporting configuration can be for downlink subband RSSI and can be associated with a first CLI metric. A second CLI reporting configuration can be for uplink subband RSRP and can be associated with a second CLI metric. The per-subband and per-reporting quantity or CLI metric configuration can be associated with implicit measurement and reporting of each downlink subband and uplink subband, implicit measurement and reporting of uplink subbands, or implicit measurement and reporting of each downlink subband. Different subband sizes can be configured in the CSI or CLI reporting configuration, and different subband sizes can be associated with a reporting quantity of a corresponding subband size and a corresponding CLI metric.

[0116] In some aspects, a subband configuration for CLI measurement can support downlink / uplink subband reporting for SBFD. Different subband CLI reports can report different reporting quantities or metrics. For subband-based CLI measurement and reporting, a per-subband per-metric or reporting quantity configuration can be supported. In a first alternative, the network node can configure two CLI reporting configurations. A first CLI reporting configuration can be for downlink subband RSSI and a second CLI reporting configuration can be for uplink subband RSRP, and each of the two CLI reporting configurations can be associated with a different CLI metric. In a second alternative, the first method, the second method, and the third method (e.g., implicit measurement and reporting) can be supported, but with a predefined CLI metric. In a third alternative, the network node can configure different subband sizes. For example, the network node can configure, in a CSI / CLI reporting configuration of a reporting configuration, a subband number with a corresponding subband size and a corresponding reporting quantity or metric.

[0117] As shown by reference number 904, the UE can transmit, to the network node, a subband-based CLI report indicating subband-based inter-UE CLI measurements based at least in part on the subband configuration for inter-UE CLI measurements. The subband-based CLI report can indicate a CLI that can vary between different frequency resources associated with different measurement subbands. The network node can perform CLI mitigation based at least in part on the subband-based CLI report, which can improve performance of the UE.

[0118] As indicated above, Figure 9 are provided as examples. Other examples can differ from what is described Figure 9 with respect to the examples described.

[0119] Figure 10 is a diagram illustrating an example 1000 associated with subband-based CLI measurement reporting, in accordance with the present disclosure.

[0120] As shown by reference number 1002, dynamic TDD can use a framework to measure different CLI levels per different RB set or measurement subband. As shown by reference number 1004, SBFD can use a framework to measure per downlink subband-based CLI or per uplink subband-based CLI. As shown by reference number 1006, SBFD can use a framework to measure different CLI levels per different sub-subband within each downlink or uplink subband.

[0121] As indicated above, Figure 10 is provided as an example. Other examples can differ from what is described Figure 10 with respect to the examples described.

[0122] Figure 11 is a diagram illustrating an example 1100 associated with subband-based CLI measurement reporting, in accordance with the present disclosure.

[0123] As Figure 11 indicated above, a subband configuration for CLI measurement can be configured as a field in a CSI-ReportConfig IE. The CSI-ReportConfig IE can include a cli-FormatIndicator, which can be associated with a cli-ReportingBand. The cli-ReportingBand can be associated with multiple subbands (e.g., subband 3, subband 4, subband 5, etc.).

[0124] As indicated above, Figure 11 is provided as an example. Other examples can differ from what is described Figure 11 with respect to the examples described.

[0125] Figure 12 is a diagram illustrating an example process 1200 performed, for example, by a UE, in accordance with the present disclosure. Example process 1200 is an example where the UE (e.g., UE 120) performs operations associated with subband-based CLI measurement reporting.

[0126] As Figure 12 indicated above, in some aspects, process 1200 can include receiving a subband configuration for inter-UE CLI measurement (block 1210). For example, the UE (e.g., using controller / processor 375) can receive a subband configuration for inter-UE CLI measurement. Figure 14The depicted receiving component 1402 and / or communication manager 1406 can receive a subband configuration for inter-UE CLI measurement, as described above.

[0127] As further shown in Figure 12 As further shown in Figure 14 The depicted transmitting component 1404 and / or communication manager 1406 can transmit a subband-based CLI report indicating subband-based inter-UE CLI measurements based at least in part on the subband configuration for inter-UE CLI measurement, as described above.

[0128] Process 1200 can include additional aspects, such as any single aspect or any combination of aspects described below and / or in connection with one or more other processes described elsewhere herein.

[0129] In a first aspect, the subband configuration for inter-UE CLI measurement is generally applicable to one or more of network node SBFD operation, partial or full overlap full duplex operation, or dynamic TDD operation.

[0130] In a second aspect, alone or in combination with the first aspect, the subband configuration for inter-UE CLI measurement is associated with one or more of measurement of one or more downlink or uplink subbands, or measurement of multiple downlink and uplink subbands in SBFD operation, measurement of different CLI levels per different sub-subband within a downlink or uplink subband, or measurement of different CLI levels per different set of resource blocks or measurement subband in dynamic TDD operation.

[0131] In a third aspect, alone or in combination with one or more of the first and second aspects, the CLI varies between different frequency resources associated with different measurement subbands.

[0132] In a fourth aspect, alone or in combination with one or more of the first through third aspects, the subband configuration for inter-UE CLI measurement is associated with one or more fields in a CSI report configuration, and the one or more fields indicate a number of subbands and a subband size.

[0133] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the subband configuration for inter-UE CLI measurement is associated with one or more fields in an information element for a CLI report configuration.

[0134] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the subband configuration for inter-UE CLI measurement is based at least in part on a PMI or CQI subband configuration, and the subband-based CLI reporting is based at least in part on the PMI or CQI subband configuration.

[0135] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the subband configuration for inter-UE CLI measurement is based at least in part on a modified PMI or CQI subband configuration, and the modified PMI or CQI subband configuration indicates a scalar field to indicate one or more of a number of subbands or a subband size.

[0136] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, a wideband CLI report is a default configuration, and the subband-based CLI reporting is based at least in part on a reception of a subband configuration for inter-UE CLI measurement.

[0137] In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the subband-based CLI reporting is associated with a subband size, and the subband size is associated with a UE downlink BWP size or the subband size is associated with a UE downlink BWP size and a downlink subband size for SBFD operation.

[0138] In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the subband size is associated with a CLI subband size.

[0139] In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the CLI subband size is smaller than a PMI or CQI subband size, and a plurality of CLI subbands within the PMI or CQI subband are collectively used for CQI CLI interference calculation.

[0140] In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, the CLI subband size is larger than a PMI or CQI subband size, and for each CQI CLI interference calculation, a same CLI is assumed across a plurality of PMI or CQI subbands.

[0141] In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, the subband-based inter-UE CLI measurement is based at least in part on a subband size that is equal to a CSI PMI or CQI subband size, based at least in part on a request to report subband PMI or CQI.

[0142] In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, the subband-based CLI reporting is for SBFD operation and is for reporting a CLI for one or more downlink subbands or uplink subbands, or for multiple downlink subbands and uplink subbands.

[0143] In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, the subband-based CLI reporting is based at least in part on implicit measurement and reporting of each downlink subband and uplink subband, and the implicit measurement and reporting of each downlink subband and uplink subband is based at least in part on a semi-static SBFD configuration in a SBFD symbol or slot.

[0144] In a sixteenth aspect, alone or in combination with one or more of the first through fifteenth aspects, the subband-based CLI reporting is based at least in part on implicit measurement and reporting of an uplink subband, and the implicit measurement and reporting of the uplink subband is based at least in part on a semi-static SBFD configuration in a SBFD symbol or slot.

[0145] In a seventeenth aspect, alone or in combination with one or more of the first through sixteenth aspects, the subband-based CLI reporting is based at least in part on implicit measurement and reporting of each downlink subband, and the implicit measurement and reporting of each downlink subband is based at least in part on a semi-static SBFD configuration in a SBFD symbol or slot.

[0146] In an eighteenth aspect, alone or in combination with one or more of the first through seventeenth aspects, the subband-based CLI reporting is based at least in part on explicit measurement and reporting of a downlink or uplink subband explicitly configured to the network node, and the explicit measurement and reporting is based at least in part on a CLI or CSI reporting configuration.

[0147] In a nineteenth aspect, alone or in combination with one or more of the first through eighteenth aspects, the explicit measurement and reporting is based at least in part on a configuration of unequal or equal subband sizes for downlink subbands and uplink subbands, and a bitmap indicates one or more subbands for the explicit measurement and reporting.

[0148] In a twentieth aspect, alone or in combination with one or more of the first through nineteenth aspects, the process 1200 includes receiving a configuration of different subband sizes associated with unequal or equal subband sizes, and the configuration indicates a subband number and a corresponding subband size.

[0149] In a twenty-first aspect, alone or in combination with one or more of the first through twentieth aspects, the process 1200 includes receiving a MAC-CE or DCI, the MAC-CE or DCI including a flag field, the flag field indicating whether the subband-based CLI reporting is based at least in part on one of: implicit measurement and reporting of each downlink subband and uplink subband, implicit measurement and reporting of uplink subband, or implicit measurement and reporting of each downlink subband.

[0150] In a twenty-second aspect, alone or in combination with one or more of the first through twenty-first aspects, different subband-based CLI reports are associated with different reporting quantities or metrics, and the subband-based CLI reporting is based at least in part on a per-subband and per-reporting quantity or CLI metric reporting configuration.

[0151] In a twenty-third aspect, alone or in combination with one or more of the first through twenty-second aspects, the process 1200 includes receiving a per-subband and per-reporting quantity or CLI metric reporting configuration for two CLI reporting configurations, and a first CLI reporting configuration is for downlink subband RSSI and is associated with a first CLI metric, and a second CLI reporting configuration is for uplink subband RSRP and is associated with a second CLI metric.

[0152] In a twenty-fourth aspect, alone or in combination with one or more of the first through twenty-third aspects, the per-subband and per-reporting quantity or CLI metric reporting configuration is associated with one of: implicit measurement and reporting of each downlink subband and uplink subband, implicit measurement and reporting of uplink subband, or implicit measurement and reporting of each downlink subband.

[0153] In a twenty-fifth aspect, alone or in combination with one or more of the first through twenty-fourth aspects, different subband sizes are configured in a CSI or CLI reporting configuration, and different subband sizes are associated with a corresponding subband size and a reporting quantity of a corresponding CLI metric.

[0154] Although Figure 12 Example blocks of the process 1200 are illustrated, but in some aspects, the process 1200 can include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted. Additionally, or alternatively, two or more of the blocks of the process 1200 can be performed in parallel. Figure 12 The depicted blocks of the process 1200 can be performed in any suitable order. Additionally or alternatively, the process 1200 can include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted.

[0155] Figure 13is a diagram illustrating an example process 1300 that can be performed, for example, by a network node, in accordance with aspects of the present disclosure. Example process 1300 is an example where a network node (e.g., network node 110) performs operations associated with subband-based CLI measurement reporting.

[0156] As further shown in Figure 13 some aspects, process 1300 can include transmitting a subband configuration for CLI measurement (block 1310). For example, the network node (e.g., using transmission component 1504 and / or communication manager 1506, depicted) can transmit a subband configuration for CLI measurement, as described above. Figure 15

[0157] As further shown in Figure 13 some aspects, process 1300 can include receiving a subband-based CLI report indicating subband-based inter-UE CLI measurements based at least in part on the subband configuration for inter-UE CLI measurement (block 1320). For example, the network node (e.g., using reception component 1502 and / or communication manager 1506, depicted) can receive a subband-based CLI report indicating subband-based inter-UE CLI measurements based at least in part on the subband configuration for inter-UE CLI measurement, as described above. Figure 15

[0158] Process 1300 can include additional aspects, such as any single aspect or any combination of aspects described below and / or in connection with one or more other processes described elsewhere herein.

[0159] In a first aspect, the subband configuration for inter-UE CLI measurement is generally applicable to one or more of network node SBFD operation, partial or full overlap full duplex operation, or dynamic TDD operation.

[0160] In a second aspect, alone or in combination with the first aspect, the subband configuration for inter-UE CLI measurement is associated with one or more of measurement of one or more downlink or uplink subbands, or measurement of multiple downlink and uplink subbands in SBFD operation, measurement of different CLI levels per different sub-subband within a downlink or uplink subband, or measurement of different CLI levels per different set of resource blocks or measurement subband in dynamic TDD operation.

[0161] In a third aspect, alone or in combination with one or more of the first and second aspects, the CLI varies between different frequency resources associated with different measurement subbands.

[0162] ​​In a fourth aspect, alone or in combination with one or more of the first through third aspects, the subband configuration for inter-UE CLI measurement is associated with one or more fields in a CSI report configuration, and the one or more fields indicate a number of subbands and a subband size.

[0163] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the subband configuration for inter-UE CLI measurement is associated with one or more fields in an information element for a CLI report configuration.

[0164] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the subband configuration for inter-UE CLI measurement is based at least in part on a PMI or CQI subband configuration, and the CLI report based on subbands is based at least in part on the PMI or CQI subband configuration.

[0165] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the subband configuration for inter-UE CLI measurement is based at least in part on a modified PMI or CQI subband configuration, and the modified PMI or CQI subband configuration indicates a scalar field to indicate one or more of a number of subbands or a subband size.

[0166] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, a wideband CLI report is a default configuration, and the CLI report based on subbands is based at least in part on a reception of the subband configuration for inter-UE CLI measurement.

[0167] In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the CLI report based on subbands is associated with a subband size, and the subband size is associated with a UE downlink BWP size or the subband size is associated with a UE downlink BWP size and a downlink subband size for SBFD operation.

[0168] In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the subband size is associated with a CLI subband size.

[0169] In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the CLI subband size is smaller than a PMI or CQI subband size, and a number of CLI subbands within the PMI or CQI subband are collectively used for CQI CLI interference computation.

[0170] In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, the CLI subband size is greater than the PMI or CQI subband size, and the same CLI is assumed over multiple PMI or CQI subbands for each CQI CLI interference calculation.

[0171] In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, the subband-based inter-UE CLI measurement is based at least in part on a subband size that is equal to a CSI PMI or CQI subband size, based at least in part on a request to report subband PMI or CQI.

[0172] In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, the subband-based CLI reporting is for SBFD operation, and is for reporting CLI for one or more downlink subbands or uplink subbands, or for multiple downlink subbands and uplink subbands.

[0173] In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, the subband-based CLI reporting is based at least in part on implicit measurement and reporting of each downlink subband and uplink subband, and the implicit measurement and reporting of each downlink subband and uplink subband is based at least in part on a semi-static SBFD configuration in a SBFD symbol or slot.

[0174] In a sixteenth aspect, alone or in combination with one or more of the first through fifteenth aspects, the subband-based CLI reporting is based at least in part on implicit measurement and reporting of uplink subbands, and the implicit measurement and reporting of uplink subbands is based at least in part on a semi-static SBFD configuration in a SBFD symbol or slot.

[0175] In a seventeenth aspect, alone or in combination with one or more of the first through sixteenth aspects, the subband-based CLI reporting is based at least in part on implicit measurement and reporting of each downlink subband, and the implicit measurement and reporting of each downlink subband is based at least in part on a semi-static SBFD configuration in a SBFD symbol or slot.

[0176] In an eighteenth aspect, alone or in combination with one or more of the first through seventeenth aspects, the subband-based CLI reporting is based at least in part on explicit measurement and reporting of downlink or uplink subbands that are explicitly configured to the network node, and the explicit measurement and reporting is based at least in part on a CLI or CSI reporting configuration.

[0177] In a nineteenth aspect, alone or in combination with one or more of the first through eighteenth aspects, the explicit measurement and reporting is based at least in part on a configuration of unequal or equal subband sizes for the downlink subbands and the uplink subbands, and the bitmap indicates one or more subbands for the explicit measurement and reporting.

[0178] In a twentieth aspect, alone or in combination with one or more of the first through nineteenth aspects, the process 1300 includes transmitting a configuration of different subband sizes associated with unequal or equal subband sizes, and the configuration indicates a subband number and a corresponding subband size.

[0179] In a twenty-first aspect, alone or in combination with one or more of the first through twentieth aspects, the process 1300 includes transmitting a MAC-CE or DCI, the MAC-CE or DCI including a flag field to indicate whether the subband-based CLI reporting is based at least in part on one of: implicit measurement and reporting for each downlink subband and uplink subband, implicit measurement and reporting for uplink subbands, or implicit measurement and reporting for each downlink subband.

[0180] In a twenty-second aspect, alone or in combination with one or more of the first through twenty-first aspects, different subband-based CLI reports are associated with different reporting quantities or metrics, and the subband-based CLI reporting is based at least in part on a per-subband and per-reporting quantity or CLI metric reporting configuration.

[0181] In a twenty-third aspect, alone or in combination with one or more of the first through twenty-second aspects, the process 1300 includes transmitting a per-subband and per-reporting quantity or CLI metric reporting configuration for two CLI reporting configurations, and a first CLI reporting configuration is for a downlink subband RSSI and is associated with a first CLI metric, and a second CLI reporting configuration is for an uplink subband RSRP and is associated with a second CLI metric.

[0182] In a twenty-fourth aspect, alone or in combination with one or more of the first through twenty-third aspects, the per-subband and per-reporting quantity or CLI metric reporting configuration is associated with one of: implicit measurement and reporting for each downlink subband and uplink subband, implicit measurement and reporting for uplink subbands, or implicit measurement and reporting for each downlink subband.

[0183] In a twenty-fifth aspect, alone or in combination with one or more of the first through twenty-fourth aspects, different subband sizes are configured in a CSI or CLI reporting configuration, and the different subband sizes are associated with a corresponding subband size and a reporting quantity for a corresponding CLI metric.

[0184] although Figure 13 An example box of process 1300 is shown, but in some respects, process 1300 may include... Figure 13 The boxes depicted may be fewer, different, or arranged differently compared to additional boxes. Alternatively, two or more boxes in the process 1300 may be executed in parallel.

[0185] Figure 14 This is a diagram of an example device 1400 for wireless communication according to the present disclosure. Device 1400 may be a UE, or a UE may include device 1400. In some aspects, device 1400 includes a receiving component 1402, a transmitting component 1404, and / or a communication manager 1406 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 1406 is combined with... Figure 1 The described communication manager 140. As shown, device 1400 can communicate with another device 1408 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 1402 and transmitting component 1404.

[0186] In some respects, device 1400 can be configured to perform the functions described herein. Figures 9 to 11 One or more operations described herein. Additionally or alternatively, the apparatus 1400 may be configured to perform one or more processes described herein, such as Figure 12 The process is 1200. In some respects, Figure 14 The illustrated device 1400 and / or one or more components may include a combination Figure 2 One or more components of the UE described. Additionally or alternatively, Figure 14 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more of the components in a set of components may be implemented at least partially as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0187] The reception component 1402 can receive communications, such as reference signals, control information, data communications, or any combination thereof, from the device 1408. The reception component 1402 can provide received communications to one or more other components of the device 1400. In some aspects, the reception component 1402 can perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and can provide the processed signals to the one or more other components of the device 1400. In some aspects, the reception component 1402 can include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or any combination thereof, as described with reference to the UE. Figure 2 The reception component 1402 can receive communications, such as reference signals, control information, data communications, or any combination thereof, from the device 1408. The reception component 1402 can provide received communications to one or more other components of the device 1400. In some aspects, the reception component 1402 can perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and can provide the processed signals to the one or more other components of the device 1400. In some aspects, the reception component 1402 can include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or any combination thereof, as described with reference to the UE.

[0188] The transmission component 1404 can transmit communications, such as reference signals, control information, data communications, or any combination thereof, to the device 1408. In some aspects, one or more other components of the device 1400 can generate communications and can provide the generated communications to the transmission component 1404 for transmission to the device 1408. In some aspects, the transmission component 1404 can perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and can transmit the processed signals to the device 1408. In some aspects, the transmission component 1404 can include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or any combination thereof, as described with reference to the UE. Figure 2 The transmission component 1404 can transmit communications, such as reference signals, control information, data communications, or any combination thereof, to the device 1408. In some aspects, one or more other components of the device 1400 can generate communications and can provide the generated communications to the transmission component 1404 for transmission to the device 1408. In some aspects, the transmission component 1404 can perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and can transmit the processed signals to the device 1408. In some aspects, the transmission component 1404 can include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or any combination thereof, as described with reference to the UE.

[0189] The communications manager 1406 can support the operations of the reception component 1402 and / or the transmission component 1404. For example, the communications manager 1406 can receive information associated with configuring reception of communications by the reception component 1402 and / or transmission of communications by the transmission component 1404. Additionally, or alternatively, the communications manager 1406 can generate control information and / or provide control information to the reception component 1402 and / or the transmission component 1404 to control the reception and / or transmission of communications.

[0190] The reception component 1402 can receive a subband configuration for inter-UE CLI measurement. The transmission component 1404 can transmit a subband-based CLI report indicating subband-based inter-UE CLI measurement based at least in part on the subband configuration for inter-UE CLI measurement.

[0191] Figure 14 The number and arrangement of components shown in FIG. 14 are provided as an example. In practice, there can be additional components, fewer components, different components, or differently arranged components than those depicted in FIG. 14. Figure 14The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 14 The two or more components shown can be implemented within a single component, or Figure 14 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 14 The set of (one or more) components shown is executable and described as being composed of Figure 14 Another set of components shown performs one or more functions.

[0192] Figure 15 This is a diagram of an example device 1500 for wireless communication according to the present disclosure. Device 1500 may be a network node, or a network node may include device 1500. In some aspects, device 1500 includes a receiving component 1502, a transmitting component 1504, and / or a communication manager 1506 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, the communication manager 1506 is combined with... Figure 1 The described communication manager 150. As shown, device 1500 can communicate with another device 1508 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 1502 and transmitting component 1504.

[0193] In some respects, device 1500 can be configured to perform the functions described herein. Figures 9 to 11 One or more operations described herein. Additionally or alternatively, the apparatus 1500 may be configured to perform one or more processes described herein, such as Figure 13 The process is 1300. In some respects, Figure 15 The illustrated device 1500 and / or one or more components may include a combination Figure 2 One or more components of the described network node. Additionally or alternatively, Figure 15 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more of the components in a set of components may be implemented at least partially as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0194] The reception component 1502 can receive communications, such as reference signals, control information, data communications, or any combination thereof, from the device 1508. The reception component 1502 can provide received communications to one or more other components of the apparatus 1500. In some aspects, the reception component 1502 can perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and can provide the processed signals to the one or more other components of the apparatus 1500. In some aspects, the reception component 1502 can be collocated with the transmission component 1504 in a transceiver. The transmission component 1504 can transmit communications, such as reference signals, control information, data communications, or any combination thereof, to the device 1508. In some aspects, one or more other components of the apparatus 1500 can generate communications and can provide the generated communications to the transmission component 1504 for transmission to the device 1508. In some aspects, the transmission component 1504 can perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and can transmit the processed signals to the device 1508. In some aspects, the transmission component 1504 can include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or any combination thereof, as described with reference to the network node. Figure 2 The reception component 1502 and / or the transmission component 1504 can include one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or any combination thereof, as described with reference to the network node. In some aspects, the reception component 1502 and / or the transmission component 1504 can be collocated in a transceiver.

[0195] The transmission component 1504 can transmit communications, such as reference signals, control information, data communications, or any combination thereof, to the device 1508. In some aspects, one or more other components of the apparatus 1500 can generate communications and can provide the generated communications to the transmission component 1504 for transmission to the device 1508. In some aspects, the transmission component 1504 can perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and can transmit the processed signals to the device 1508. In some aspects, the transmission component 1504 can include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or any combination thereof, as described with reference to the network node. Figure 2 The transmission component 1504 can transmit communications, such as reference signals, control information, data communications, or any combination thereof, to the device 1508. In some aspects, one or more other components of the apparatus 1500 can generate communications and can provide the generated communications to the transmission component 1504 for transmission to the device 1508. In some aspects, the transmission component 1504 can perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and can transmit the processed signals to the device 1508. In some aspects, the transmission component 1504 can include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or any combination thereof, as described with reference to the network node.

[0196] The communications manager 1506 can support the operations of the reception component 1502 and / or the transmission component 1504. For example, the communications manager 1506 can receive information associated with configuring reception of communications by the reception component 1502 and / or transmission of communications by the transmission component 1504. Additionally or alternatively, the communications manager 1506 can generate control information and / or provide control information to the reception component 1502 and / or the transmission component 1504 to control the reception and / or transmission of communications.

[0197] The transmission component 1504 can transmit a subband configuration for CLI measurement. The reception component 1502 can receive a subband-based CLI report indicating subband-based inter-UE CLI measurements based at least in part on the subband configuration for inter-UE CLI measurement.

[0198] Figure 15 The number and arrangement of components shown is provided as an example. In practice, there can be additional components, fewer components, different components, or differently arranged components than those shown. Figure 15 Additional components, different components, or differently arranged components Figure 15 Two or more components shown can be implemented within a single component, Figure 15 A single component shown can be implemented as multiple, distributed components. Additionally or alternatively, Figure 15 A set of one or more components shown can perform one or more functions described as being performed by Figure 15 Another set of one or more components shown can perform one or more functions described as being performed by

[0199] An overview of some aspects of the present disclosure is provided below:

[0200] Aspect 1 : A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a subband configuration for inter-UE cross-link interference (CLI) measurement; and transmitting a subband-based CLI report indicating subband-based inter-UE CLI measurements based at least in part on the subband configuration for inter-UE CLI measurement.

[0201] Aspect 2: The method of aspect 1, wherein the subband configuration for inter-UE CLI measurement is generally applicable to one or more of network node subband full duplex (SBFD) operation, partial or full overlap full duplex operation, or dynamic time division duplex (TDD) operation.

[0202] Aspect 3: The method of any of aspects 1-2, wherein the subband configuration for inter-UE CLI measurement is associated with one or more of: measurement of one or more downlink subbands or uplink subbands, or measurement of a plurality of downlink subbands and the uplink subband in a subband full duplex (SBFD) operation; measurement of different CLI levels per different sub-subband within a downlink or uplink subband; or measurement of different CLI levels per different resource block set or measurement subband in a dynamic time division duplex (TDD) operation.

[0203] Aspect 4: The method of any of aspects 1-3, wherein CLI varies between different frequency resources associated with different measurement subbands.

[0204] Aspect 5: The method of any of aspects 1-4, wherein the subband configuration for inter-UE CLI measurement is associated with one or more fields in a channel state information (CSI) report configuration, and the one or more fields indicate a number of subbands and a subband size.

[0205] Aspect 6: The method of any of aspects 1-5, wherein the subband configuration for inter-UE CLI measurement is associated with one or more fields in an information element for a CLI report configuration.

[0206] Aspect 7: The method of any of aspects 1-6, wherein the subband configuration for inter-UE CLI measurement is based at least in part on a precoding matrix indicator (PMI) or channel quality indicator (CQI) subband configuration, and the subband-based CLI report is based at least in part on the PMI or CQI subband configuration.

[0207] Aspect 8: The method of any of aspects 1-7, wherein the subband configuration for inter-UE CLI measurement is based at least in part on a modified precoding matrix indicator (PMI) or channel quality indicator (CQI) subband configuration, and the modified PMI or CQI subband configuration indicates a scalar field to indicate one or more of a number of subbands or a subband size.

[0208] Aspect 9: The method of any of aspects 1-8, wherein a wideband CLI report is a default configuration, and the subband-based CLI report is based at least in part on a reception of the subband configuration for inter-UE CLI measurement.

[0209] Aspect 10: The method of any of aspects 1-9, wherein the subband-based CLI report is associated with a subband size, and the subband size is associated with a UE downlink bandwidth part (BWP) size or the subband size is associated with the UE downlink BWP size and a downlink subband size for subband full duplex (SBFD) operation.

[0210] Aspect 11: The method of aspect 10, wherein the subband size is associated with a CLI subband size.

[0211] Aspect 12: The method of aspect 11, wherein the CLI subband size is smaller than a precoding matrix indicator (PMI) or channel quality indicator (CQI) subband size, and a plurality of CLI subbands within a PMI or CQI subband are collectively used for CQI CLI interference computation.

[0212] Aspect 13: The method of aspect 11, wherein the CLI subband size is greater than a precoding matrix indicator (PMI) or channel quality indicator (CQI) subband size, and a same CLI is assumed across multiple PMI or CQI subbands for each CQI CLI interference calculation.

[0213] Aspect 14: The method of any of aspects 1-13, wherein the subband-based inter-UE CLI measurement is based at least in part on a subband size equal to a channel state information (CSI) precoding matrix indicator (PMI) or channel quality indicator (CQI) subband size, based at least in part on a request to report a subband PMI or CQI.

[0214] Aspect 15: The method of any of aspects 1-14, wherein the subband-based CLI reporting is for subband full duplex (SBFD) operation, and is for reporting a CLI for one or more downlink subbands or uplink subbands, or for multiple downlink subbands and the uplink subband.

[0215] Aspect 16: The method of any of aspects 1-15, wherein the subband-based CLI reporting is based at least in part on an implicit measurement and reporting of each downlink subband and uplink subband, and the implicit measurement and reporting of each downlink subband and the uplink subband is based at least in part on a SBFD configuration in a semi-static subband full duplex (SBFD) symbol or time slot.

[0216] Aspect 17: The method of any of aspects 1-16, wherein the subband-based CLI reporting is based at least in part on an implicit measurement and reporting of an uplink subband, and the implicit measurement and reporting of the uplink subband is based at least in part on a SBFD configuration in a semi-static subband full duplex (SBFD) symbol or time slot.

[0217] Aspect 18: The method of any of aspects 1-17, wherein the subband-based CLI reporting is based at least in part on an implicit measurement and reporting of each downlink subband, and the implicit measurement and reporting of each downlink subband is based at least in part on a SBFD configuration in a semi-static subband full duplex (SBFD) symbol or time slot.

[0218] Aspect 19: The method of any of aspects 1-18, wherein the subband-based CLI reporting is based at least in part on an explicit measurement and reporting of a downlink or uplink subband explicitly configured to a network node, and the explicit measurement and reporting is based at least in part on a CLI or channel state information (CSI) reporting configuration.

[0219] Aspect 20: The method of aspect 19, wherein the explicit measurement and reporting is based at least in part on a configuration of unequal or equal subband sizes for downlink and uplink subbands, and a bitmap indicates one or more subbands for the explicit measurement and reporting.

[0220] Aspect 21 : The method of aspect 20, further comprising: receiving a configuration of different subband sizes associated with the unequal or equal subband sizes, wherein the configuration indicates a subband number and a corresponding subband size.

[0221] Aspect 22: The method of any of aspects 1-21, further comprising: receiving a medium access control control element (MAC-CE) or downlink control information (DCI) including a flag field to indicate whether the subband-based CLI reporting is based at least in part on one of: implicit measurement and reporting for each downlink and uplink subband, implicit measurement and reporting for the uplink subband, or implicit measurement and reporting for each downlink subband.

[0222] Aspect 23: The method of any of aspects 1-22, wherein different subband-based CLI reports are associated with different reporting quantities or metrics, and the subband-based CLI reporting is based at least in part on a per-subband and per-reporting quantity or CLI metric reporting configuration.

[0223] Aspect 24: The method of aspect 23, further comprising: receiving the per-subband and per-reporting quantity or CLI metric reporting configuration for two CLI reporting configurations, wherein a first CLI reporting configuration is for downlink subband received signal strength indicator (RSSI) and is associated with a first CLI metric, and a second CLI reporting configuration is for uplink subband reference signal received power (RSRP) and is associated with a second CLI metric.

[0224] Aspect 25: The method of aspect 23, wherein the per-subband and per-reporting quantity or CLI metric reporting configuration is associated with one of: implicit measurement and reporting for each downlink and uplink subband, implicit measurement and reporting for the uplink subband, or implicit measurement and reporting for each downlink subband.

[0225] Aspect 26: The method of aspect 23, wherein different subband sizes are configured in a channel state information (CSI) or CLI reporting configuration, and the different subband sizes are associated with a corresponding subband size and a reporting quantity of a corresponding CLI metric.

[0226] Aspect 27: A method of wireless communication performed by a network node, the method comprising: transmitting a subband configuration for cross-link interference (CLI) measurement; and receiving a subband-based CLI report indicating a subband-based inter-UE CLI measurement based at least in part on the subband configuration for inter-UE CLI measurement.

[0227] Aspect 28: The method of aspect 27, wherein the subband configuration for inter-UE CLI measurement is generally applicable to one or more of network node subband full duplex (SBFD) operation, partial or full overlap full duplex operation, or dynamic time division duplex (TDD) operation.

[0228] Aspect 29: The method of any one of aspects 27-28, wherein the subband configuration for inter-UE CLI measurement is associated with one or more of: measurement of one or more downlink subbands or uplink subbands, or measurement of a plurality of downlink subbands and the uplink subband in a subband full duplex (SBFD) operation; measurement of different CLI levels per different sub-subband within a downlink or uplink subband; or measurement of different CLI levels per different resource block set or measurement subband in a dynamic time division duplex (TDD) operation.

[0229] Aspect 30: The method of any one of aspects 27-29, wherein CLI varies between different frequency resources associated with different measurement subbands.

[0230] Aspect 31: The method of any one of aspects 27-30, wherein the subband configuration for inter-UE CLI measurement is associated with one or more fields in a channel state information (CSI) report configuration, and the one or more fields indicate a number of subbands and a subband size.

[0231] Aspect 32: The method of any one of aspects 27-31, wherein the subband configuration for inter-UE CLI measurement is associated with one or more fields in an information element for CLI report configuration.

[0232] Aspect 33: The method of any one of aspects 27-32, wherein the subband configuration for inter-UE CLI measurement is based at least in part on a precoding matrix indicator (PMI) or channel quality indicator (CQI) subband configuration, and the subband-based CLI report is based at least in part on the PMI or CQI subband configuration.

[0233] Aspect 34: The method of any of aspects 27 through 33, wherein the subband configuration for inter-UE CLI measurement is based at least in part on a modified precoding matrix indicator (PMI) or channel quality indicator (CQI) subband configuration, and the modified PMI or CQI subband configuration indicates a scalar field to indicate one or more of a number of subbands or a subband size.

[0234] Aspect 35: The method of any of aspects 27 through 34, wherein a wideband CLI report is a default configuration, and the subband-based CLI report is based at least in part on a reception of the subband configuration for inter-UE CLI measurement.

[0235] Aspect 36: The method of any of aspects 27 through 35, wherein the subband-based CLI report is associated with a subband size, and the subband size is associated with a UE downlink bandwidth part (BWP) size or the subband size is associated with the UE downlink BWP size and a downlink subband size for subband full duplex (SBFD) operation.

[0236] Aspect 37: The method of aspect 36, wherein the subband size is associated with a CLI subband size.

[0237] Aspect 38: The method of aspect 37, wherein the CLI subband size is smaller than a precoding matrix indicator (PMI) or channel quality indicator (CQI) subband size, and a plurality of CLI subbands within a PMI or CQI subband are collectively used for CQI CLI interference calculation.

[0238] Aspect 39: The method of aspect 37, wherein the CLI subband size is larger than a precoding matrix indicator (PMI) or channel quality indicator (CQI) subband size, and a same CLI is assumed across a plurality of PMI or CQI subbands for each CQI CLI interference calculation.

[0239] Aspect 40: The method of any of aspects 27 through 39, wherein the subband-based inter-UE CLI measurement is based at least in part on a subband size equal to a channel state information (CSI) precoding matrix indicator (PMI) or channel quality indicator (CQI) subband size, based at least in part on a request to report subband PMI or CQI.

[0240] Aspect 41: The method of any of aspects 27 through 40, wherein the subband-based CLI report is for subband full duplex (SBFD) operation, and is for reporting a CLI for one or more downlink subbands or uplink subbands, or for a plurality of downlink subbands and the uplink subband.

[0241] Aspect 42: The method of any of aspects 27 through 41, wherein the subband-based CLI reporting is based at least in part on implicit measurement and reporting of each downlink subband and an uplink subband, and the implicit measurement and reporting of each downlink subband and the uplink subband is based at least in part on a semi-static subband full duplex (SBFD) configuration in a SBFD symbol or slot.

[0242] Aspect 43: The method of any of aspects 27 through 42, wherein the subband-based CLI reporting is based at least in part on implicit measurement and reporting of an uplink subband, and the implicit measurement and reporting of the uplink subband is based at least in part on a semi-static subband full duplex (SBFD) configuration in a SBFD symbol or slot.

[0243] Aspect 44: The method of any of aspects 27 through 43, wherein the subband-based CLI reporting is based at least in part on implicit measurement and reporting of each downlink subband, and the implicit measurement and reporting of each downlink subband is based at least in part on a semi-static subband full duplex (SBFD) configuration in a SBFD symbol or slot.

[0244] Aspect 45: The method of any of aspects 27 through 44, wherein the subband-based CLI reporting is based at least in part on explicit measurement and reporting of a downlink or uplink subband explicitly configured to a network node, and the explicit measurement and reporting is based at least in part on a CLI or channel state information (CSI) reporting configuration.

[0245] Aspect 46: The method of aspect 45, wherein the explicit measurement and reporting is based at least in part on a configuration of unequal or equal subband sizes for downlink subbands and uplink subbands, and a bitmap indicates one or more subbands for the explicit measurement and reporting.

[0246] Aspect 47: The method of aspect 46, further comprising: transmitting a configuration of different subband sizes associated with the unequal or equal subband sizes, wherein the configuration indicates a subband number and a corresponding subband size.

[0247] Aspect 48: The method of any of aspects 27-47, further comprising: transmitting a medium access control control element (MAC-CE) or downlink control information (DCI) including a flag field to indicate whether the subband-based CLI reporting is based at least in part on one of: implicit measurement and reporting of each downlink subband and uplink subband, implicit measurement and reporting of the uplink subband, or implicit measurement and reporting of each downlink subband.

[0248] Aspect 49: The method of any of aspects 27-48, wherein different subband-based CLI reports are associated with different reporting quantities or metrics, and the subband-based CLI reporting is based at least in part on a per-subband and per-reporting quantity or CLI metric reporting configuration.

[0249] Aspect 50: The method of aspect 49, further comprising: transmitting the per-subband and per-reporting quantity or CLI metric reporting configuration for two CLI reporting configurations, wherein a first CLI reporting configuration is for downlink subband received signal strength indicator (RSSI) and is associated with a first CLI metric, and a second CLI reporting configuration is for uplink subband reference signal received power (RSRP) and is associated with a second CLI metric.

[0250] Aspect 51: The method of aspect 49, wherein the per-subband and per-reporting quantity or CLI metric reporting configuration is associated with one of: implicit measurement and reporting of each downlink subband and uplink subband, implicit measurement and reporting of the uplink subband, or implicit measurement and reporting of each downlink subband.

[0251] Aspect 52: The method of aspect 49, wherein different subband sizes are configured in a channel state information (CSI) or CLI reporting configuration, and the different subband sizes are associated with a reporting quantity of a corresponding subband size and a corresponding CLI metric.

[0252] Aspect 53: An apparatus for wireless communication at a device, the apparatus comprising: a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of aspects 1-26.

[0253] Aspect 54: An apparatus for wireless communication, the apparatus comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of Aspects 1-26.

[0254] Aspect 55: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method of one or more of Aspects 1-26.

[0255] Aspect 56: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of Aspects 1-26.

[0256] Aspect 57: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 1-26.

[0257] Aspect 58: An apparatus for wireless communication at a device, the apparatus comprising: a processor; a memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of Aspects 27-52.

[0258] Aspect 59: An apparatus for wireless communication, the apparatus comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of Aspects 27-52.

[0259] Aspect 60: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method of one or more of Aspects 27-52.

[0260] Aspect 61: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of Aspects 27-52.

[0261] Aspect 62: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 27-52.

[0262] While the forgoing examples are illustrative of the aspects provided herein, they are not meant to be exhaustive or limiting. Modifications and variations are possible in light of the above disclosures. Further, it is intended that the scope of the aspects disclosed herein encompass all techniques capable of implementing the concepts described herein.

[0263] As used herein, the term “component” is intended to be broadly interpreted to encompass hardware and / or a combination of hardware and software. “Software” shall be broadly construed to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and / or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. As used herein, a “processor” is implemented in hardware and / or a combination of hardware and software. It will be apparent that systems and / or methods described herein can be implemented in different forms of hardware and / or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not limiting of the aspects. Thus, the operation and behavior of the systems and / or methods were described herein without reference to specific software code — because it will be understood that software and hardware can be designed to implement the systems and / or methods, based on the description herein.

[0264] As used herein, depending on the context, “satisfies a threshold” can refer to a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, and / or the like.

[0265] Although specific combinations of features are set forth in the claims and / or disclosed herein, those combinations are not intended to limit the disclosure of the various aspects. Many of the features can be combined in ways not specifically recited in the claims and / or disclosed herein. The disclosure of the various aspects includes each and every combination of the features described herein. As used herein, the phrase “at least one of a list of items refers to any combination of one or more of the items in the list. As an example, “at least one of: a, b, or c” is intended to cover: a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination of items from among a, b, and c (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c, or any other ordering of a, b, and c).

[0266] No element, act or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items, and can be used interchangeably with “one or more.” Furthermore, as used herein, the term “set” and “group” are intended to include one or more items, and can be used interchangeably with “one or more.” Where only one item is intended, the phrase “only one” or similar language will be used. Also, as used herein, the term “has” and its variants are intended to be open-ended terms that do not limit the item that the term is modifying to a single item unless otherwise indicated. Further, the phrase “based on” is intended to be open-ended, and to mean “based, at least in part, on.” Finally, as used herein, the term “or” is intended to be the inclusive or, and not the exclusive or; that is, unless specified otherwise, “or” means “and / or” unless explicitly stated otherwise.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receive a subband configuration for inter-UE cross-link interference (CLI) measurement; and transmit, based at least in part on the subband configuration for inter-UE CLI measurement, a subband-based CLI report indicating subband-based inter-UE CLI measurement.

2. The apparatus of claim 1, wherein the subband configuration for inter-UE CLI measurement is generally applicable to one or more of network node subband full duplex (SBFD) operation, partial or full overlap full duplex operation, or dynamic time division duplex (TDD) operation.

3. The apparatus of claim 1, wherein the subband configuration for inter-UE CLI measurement is associated with one or more of: measurement of one or more downlink subbands or uplink subbands, or measurement of multiple downlink subbands and the uplink subband in a subband full duplex (SBFD) operation; measurement of different CLI levels per different sub-subband within a downlink or uplink subband; or measurement of different CLI levels per different resource block set or measurement subband in a dynamic time division duplex (TDD) operation.

4. The apparatus of claim 1, wherein CLI varies between different frequency resources associated with different measurement subbands.

5. The apparatus of claim 1, wherein the subband configuration for inter-UE CLI measurement is associated with one or more fields in a channel state information (CSI) report configuration, and the one or more fields indicate a number of subbands and a subband size.

6. The apparatus of claim 1, wherein the subband configuration for inter-UE CLI measurement is associated with one or more fields in an information element for CLI report configuration.

7. The apparatus of claim 1, wherein the subband configuration for inter-UE CLI measurement is based at least in part on a precoding matrix indicator (PMI) or channel quality indicator (CQI) subband configuration, and the subband-based CLI report is based at least in part on the PMI or CQI subband configuration.

8. The apparatus of claim 1, wherein the subband configuration for inter-UE CLI measurement is based at least in part on a modified precoding matrix indicator (PMI) or channel quality indicator (CQI) subband configuration, and the modified PMI or CQI subband configuration indicates a scalar field to indicate one or more of a number of subbands or a subband size.

9. The apparatus of claim 1, wherein a wideband CLI report is a default configuration, and the subband-based CLI report is based at least in part on reception of the subband configuration for inter-UE CLI measurement.

10. The apparatus of claim 1, wherein the subband-based CLI reporting is associated with a subband size, and the subband size is associated with a UE downlink bandwidth part (BWP) size, or the subband size is associated with the UE downlink BWP size and a downlink subband size for subband full duplex (SBFD) operation.

11. The apparatus of claim 10, wherein the subband size is associated with a CLI subband size.

12. The apparatus of claim 11, wherein the CLI subband size is smaller than a precoding matrix indicator (PMI) or channel quality indicator (CQI) subband size, and a plurality of CLI subbands within a PMI or CQI subband are collectively used for CQI CLI interference calculation.

13. The apparatus of claim 11, wherein the CLI subband size is larger than a precoding matrix indicator (PMI) or channel quality indicator (CQI) subband size, and a same CLI is assumed across a plurality of PMI or CQI subbands for each CQI CLI interference calculation.

14. The apparatus of claim 1, wherein the subband-based inter-UE CLI measurement is based at least in part on a subband size equal to a channel state information (CSI) precoding matrix indicator (PMI) or channel quality indicator (CQI) subband size, based at least in part on a request to report subband PMI or CQI.

15. The apparatus of claim 1, wherein the subband-based CLI reporting is for subband full duplex (SBFD) operation, and is for reporting a CLI for one or more downlink subbands or uplink subbands, or for a plurality of downlink subbands and the uplink subband.

16. The apparatus of claim 1, wherein the subband-based CLI reporting is based at least in part on implicit measurement and reporting of each downlink subband and uplink subband, and the implicit measurement and reporting of each downlink subband and the uplink subband is based at least in part on a SBFD configuration in a semi-static subband full duplex (SBFD) symbol or time slot.

17. The apparatus of claim 1, wherein the subband-based CLI reporting is based at least in part on implicit measurement and reporting of an uplink subband, and the implicit measurement and reporting of the uplink subband is based at least in part on a SBFD configuration in a semi-static subband full duplex (SBFD) symbol or time slot.

18. The apparatus of claim 1, wherein the subband-based CLI reporting is based at least in part on implicit measurement and reporting of each downlink subband, and the implicit measurement and reporting of each downlink subband is based at least in part on a SBFD configuration in a semi-static subband full duplex (SBFD) symbol or time slot.

19. The apparatus of claim 1, wherein the subband-based CLI reporting is based at least in part on explicit measurement and reporting of downlink or uplink subbands configured explicitly to the network node, and the explicit measurement and reporting is based at least in part on a CLI or channel state information (CSI) reporting configuration.

20. The apparatus of claim 19, wherein the explicit measurement and reporting is based at least in part on a configuration of unequal or equal subband sizes for downlink and uplink subbands, and a bitmap indicates one or more subbands for the explicit measurement and reporting.

21. The apparatus of claim 20, wherein the instructions stored in the memory and executable by the processor further cause the apparatus to: receive a configuration of different subband sizes associated with the unequal or equal subband sizes, wherein the configuration indicates a subband number and a corresponding subband size.

22. The apparatus of claim 1, wherein the instructions stored in the memory and executable by the processor further cause the apparatus to: receive a medium access control control element (MAC-CE) or downlink control information (DCI) including a flag field to indicate whether the subband-based CLI reporting is based at least in part on one of: implicit measurement and reporting of each downlink and uplink subband, implicit measurement and reporting of the uplink subband, or implicit measurement and reporting of each downlink subband.

23. The apparatus of claim 1, wherein different subband-based CLI reports are associated with different reporting quantities or metrics, and the subband-based CLI reporting is based at least in part on a per-subband and per-reporting quantity or CLI metric reporting configuration.

24. The apparatus of claim 23, wherein the instructions stored in the memory and executable by the processor further cause the apparatus to: receive the per-subband and per-reporting quantity or CLI metric reporting configuration for two CLI reporting configurations, wherein a first CLI reporting configuration is for downlink subband received signal strength indicator (RSSI) and is associated with a first CLI metric, and a second CLI reporting configuration is for uplink subband reference signal received power (RSRP) and is associated with a second CLI metric.

25. The apparatus of claim 23, wherein the per-subband and per-reporting quantity or CLI metric reporting configuration is associated with one of: implicit measurement and reporting of each downlink and uplink subband, implicit measurement and reporting of the uplink subband, or implicit measurement and reporting of each downlink subband.

26. The apparatus of claim 23, wherein different subband sizes are configured in a channel state information (CSI) or CLI report configuration, and the different subband sizes are associated with a corresponding subband size and a number of reports of a corresponding CLI metric.

27. An apparatus for wireless communication at a network node, the apparatus comprising: a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: transmit a subband configuration for cross-link interference (CLI) measurement; and receive a subband-based CLI report indicating subband-based inter-UE CLI measurements based at least in part on the subband configuration for inter-UE CLI measurement.

28. The apparatus of claim 27, wherein the subband configuration for inter-UE CLI measurement is generally applicable to one or more of network node subband full duplex (SBFD) operation, partial or full overlap full duplex operation, or dynamic time division duplex (TDD) operation.

29. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a subband configuration for inter-UE cross-link interference (CLI) measurement; and transmitting a subband-based CLI report indicating subband-based inter-UE CLI measurements based at least in part on the subband configuration for inter-UE CLI measurement.

30. A method of wireless communication performed by a network node, the method comprising: transmitting a subband configuration for cross-link interference (CLI) measurement; and receiving a subband-based CLI report indicating subband-based inter-UE CLI measurements based at least in part on the subband configuration for inter-UE CLI measurement. ​