WO2024100637A1 - Cross-link interference (cli) management via combined beams and aggressor selection - Google Patents

Abstract

Various aspects of the present disclosure relate to the selection of combined beams and/or aggressor nodes during cross-link interference (CLI) management within a wireless communications system. For example, a network node (e.g., a victim node) that is experiencing CLI can identify or select preferred Transmitting or Receiving beams (Tx-Rx beams) from other nodes, as well as identify or select a set of other nodes (e.g., a set of aggressor nodes) allowed to interfere (or otherwise share resources) with the victim node.

Description

Lenovo Docket No. SMM920220211-WO-PCT 1 CROSS-LINK INTERFERENCE (CLI) MANAGEMENT VIA COMBINED BEAMS AND AGGRESSOR SELECTION CROSS-REFERENCE TO RELATED APPLICATIONS [0001] This application claims priority to U.S. Provisional Patent Application No. 63/477,911, filed on December 30, 2022, entitled CROSS-LINK INTERFERENCE (CLI) MANAGEMENT VIA COMBINED BEAMS AND AGGRESSOR SELECTION, which is incorporated by reference in its entirety. TECHNICAL FIELD [0002] The present disclosure relates to wireless communications, and more specifically to supporting cross-link interference (CLI) management between nodes of a wireless communications network. BACKGROUND [0003] A wireless communications system may include one or multiple network communication devices, such as base stations, which may be otherwise known as an eNodeB (eNB), a next-generation NodeB (gNB), or other suitable terminology. Each network communication device, such as a base station, may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE), or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers). Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)). Attorney Docket No.793MS0032PC Lenovo Docket No. SMM920220211-WO-PCT 2 [0004] Often, neighboring nodes network cells or UEs) can utilize different Time Division Duplex (TDD) downlink (DL) and/or uplink (UL) patterns during network communications. However, the different TDD patterns can cause CLI, where the UL transmission of one node interferes with the DL reception of another node (e.g., a neighbor node). Typically, nodes, such as gNBs, may exchange and/or coordinate their TDD DL-UL configurations over communications interfaces, where UEs experiencing CLI can perform CLI measurements. Example CLI measurements include SRS-RSRP (Sounding Resource Signal-Reference Signal Received Power) measurement over the SRS resources of a node providing the interference (e.g., unintended transmissions) to the UEs, CLI-RSSI (Received Signal Strength Indicator) measurement of a total received power observed over the RSSI resources, and so on. SUMMARY [0005] The present disclosure relates to methods, apparatuses, and systems that support CLI management, where a node (e.g., a UE or gNB) that is experiencing CLI can identify or select preferred Transmitting or Receiving beams (Tx-Rx beams) from other nodes, as well as identify or select a set of other nodes allowed to interfere (or otherwise share resources) with the node. [0006] Some implementations of the method and apparatuses described herein may further include a network entity comprising a processor and a memory coupled with the processor, the processor configured to cause the network entity to identify a victim node and a set of aggressor nodes associated with the victim node, configure the victim node with a set of non-overlapping CLI measurement resources associated with reception at the victim node, and configure each aggressor node of the set of aggressor nodes with one or more non-overlapping CLI reference signal (RS) resources associated with transmission by the set of aggressor nodes. [0007] In some implementations of the method and apparatuses described herein, the processor is further configured to receive, in response to sending a request to the victim Attorney Docket No.793MS0032PC Lenovo Docket No. SMM920220211-WO-PCT 3 node, a report that indicates CLI based on the set of non-overlapping CLI measurement resources and the non-overlapping CLI RS resources. [0008] In some implementations of the method and apparatuses described herein, the report is received from the victim node via uplink control information (UCI) over a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH). [0009] In some implementations of the method and apparatuses described herein, the report is received from the victim node via a MAC-CE (Medium Access Control-Control Element). [0010] In some implementations of the method and apparatuses described herein, the report is received from the victim node via Over-the-Air (OTA) connections or backhaul connections between the victim node and the network entity. [0011] In some implementations of the method and apparatuses described herein, the report includes indices or CLI measurements for one or more of CLI measurement resources having lowest or highest CLI-RSRP or CLI-RSSI, or indices or CLI measurements for one or more of preferred transmission beams or reception beams or one or more of restricted transmission beams or reception beams. [0012] In some implementations of the method and apparatuses described herein, the victim node and the set of aggressor nodes include UEs. [0013] In some implementations of the method and apparatuses described herein, the victim node and the set of aggressor nodes include network entities. [0014] In some implementations of the method and apparatuses described herein, the network entity is supported by one aggressor node of the set of aggressor nodes as a network configuration entity. [0015] In some implementations of the method and apparatuses described herein, the set of non-overlapping CLI measurement resources includes SRS-RSRP, SRS-RSSI, or CSI-IM (channel state information-interference measurement). Attorney Docket No.793MS0032PC Lenovo Docket No. SMM920220211-WO-PCT 4 [0016] In some implementations of method and apparatuses described herein, the set of non-overlapping CLI RS resources includes SRS, SSB (Synchronization Signal Block), CD-SSB (cell-defining-SSB), NCD-SSB (non-cell-defining-SSB), or NZP CSI-RS (non-zero power channel state information-reference signal). [0017] In some implementations of the method and apparatuses described herein, the processor is further configured to identify the victim node and the set of aggressor nodes based on one or more of factors, including: physical locations of the victim node and the set of aggressor nodes, distances between the victim node and the set of aggressor nodes, time- frequency resource allocations for the victim node and the set of aggressor nodes, pathloss and CSI measurements performed by the victim node and the set of aggressor nodes, and/or beam or radio link failures detected by the victim node. [0018] In some implementations of the method and apparatuses described herein, each CLI measurement resource of the set of CLI measurement resources is associated with a unique subset of CLI RS resources configured at the set of aggressor nodes over the same time-frequency resources. [0019] In some implementations of the method and apparatuses described herein, the victim node identifies a set of receive beams for measuring CLI based on receive beams used for receiving other downlink signals or other uplink signals. [0020] In some implementations of the method and apparatuses described herein, the network entity configures the victim node to receive an indication of a set of receive beams for measuring CLI. [0021] In some implementations of the method and apparatuses described herein, the set of aggressor nodes identifies a set of transmit beams for transmitting CLI RS based on transmit beams used when transmitting other downlink signals or other uplink signals. [0022] In some implementations of the method and apparatuses described herein, the network entity configures the set of aggressor nodes to receive an indication of a set of transmit beams for transmitting CLI RS. Attorney Docket No.793MS0032PC Lenovo Docket No. SMM920220211-WO-PCT 5 [0023] In some implementations of method and apparatuses described herein, the network entity configures the set of non-overlapping CLI measurement resources or the set of non-overlapping CLI RS resources in a periodic, aperiodic, or semi-persistent manner. [0024] Some implementations of the method and apparatuses described herein may further include a method performed by a network entity, the method comprising identifying a victim node and a set of aggressor nodes associated with the victim node, configuring the victim node with a set of non-overlapping CLI measurement resources associated with reception at the victim node, and configuring each aggressor node of the set of aggressor nodes with one or more non-overlapping CLI reference signal (RS) resources associated with transmission by the set of aggressor nodes. [0025] In some implementations of the method and apparatuses described herein, the method further includes receiving, in response to sending a request to the victim node, a report that indicates CLI measurements based on the set of non-overlapping CLI measurement resources and the non-overlapping CLI RS resources. [0026] Some implementations of the method and apparatuses described herein may further include a network node, comprising a processor and a memory coupled with the processor, the processor configured to cause the network node to receive, from a network entity, a configuration that identifies a set of non-overlapping CLI measurement resources associated with receiving beams at the network node, perform CLI measurements using the set of non-overlapping CLI measurement resources, and transmit, to the network entity, a report that indicates the performed CLI measurements based on the set of non-overlapping CLI measurement resources. [0027] In some implementations of the method and apparatuses described herein, each CLI measurement resource of the set of non-overlapping CLI measurement resources is associated with a unique subset of CLI RS resources configured at the set of aggressor nodes over the same time-frequency resources. [0028] In some implementations of the method and apparatuses described herein, the the network node is a victim node that receives interfering signals from multiple aggressor nodes. Attorney Docket No.793MS0032PC Lenovo Docket No. SMM920220211-WO-PCT 6 [0029] In some implementations of method and apparatuses described herein, the network node is a UE. [0030] In some implementations of the method and apparatuses described herein, the network node is another network entity. [0031] Some implementations of the method and apparatuses described herein may further include a method performed by a network node associated with a set of aggressor nodes, the method comprising receiving, from a network entity, a configuration that identifies a set of non-overlapping CLI measurement resources associated with receiving beams at the network node, performing CLI measurements using the set of non-overlapping CLI measurement resources, and transmitting, to the network entity, a report that indicates the performed CLI measurements based on the set of non-overlapping CLI measurement resources. [0032] In some implementations of the method and apparatuses described herein, the network node is a victim node that receives interfering signals from multiple aggressor nodes. BRIEF DESCRIPTION OF THE DRAWINGS [0033] FIG.1 illustrates an example of a wireless communications system that supports CLI management between nodes, in accordance with aspects of the present disclosure. [0034] FIG.2 illustrates an example of a diagram that supports CLI management between two aggressor nodes and one victim node in accordance with aspects of the present disclosure. [0035] FIG.3 illustrates an example of a diagram that supports a dynamic TDD system between network entities in accordance with aspects of the present disclosure. [0036] FIGs.4A-4B illustrate examples of diagrams that support different CLI management scenarios in accordance with aspects of the present disclosure. Attorney Docket No.793MS0032PC Lenovo Docket No. SMM920220211-WO-PCT 7 [0037] FIG.5 illustrates an example a diagram that supports a Frequency Division Multiplexed (FDMxd) CLI resources configuration in accordance with aspects of the present disclosure. [0038] FIG.6 illustrates an example of a diagram that supports a Time Division Multiplexed (TDMxd) CLI resources configuration in accordance with aspects of the present disclosure. [0039] FIG.7 illustrates an example of a diagram that supports signaling between nodes and a network configuration entity in accordance with aspects of the present disclosure. [0040] FIG.8 illustrates an example of a diagram that supports a network entity CLI management scenario in accordance with aspects of the present disclosure. [0041] FIG.9 illustrates an example of a block diagram of a device that supports providing CLI management in accordance with aspects of the present disclosure. [0042] FIG.10 illustrates a flowchart of a method that supports configuring network nodes to perform CLI measurements in accordance with aspects of the present disclosure. [0043] FIG.11 illustrates a flowchart of a method that supports measuring CLI via a victim node in accordance with aspects of the present disclosure. DETAILED DESCRIPTION [0044] As described herein, the management of CLI between network nodes (e.g., UE to UE and/or network entity to network entity) of a wireless communications system can involve exchanges of information between nodes such as exchanges of TDD DL-UL configurations between the network nodes. Such exchanges of information can inefficiently utilize network resources and/or be performed by entities not experiencing issues due to CLI. [0045] However, based on the technology described herein, the network node (e.g., a victim node) that is experiencing CLI can identify or select preferred Transmitting or Attorney Docket No.793MS0032PC Lenovo Docket No. SMM920220211-WO-PCT 8 Receiving beams (Tx-Rx beams) from nodes, as well as identify or select a set of other nodes (e.g., a set of aggressor nodes) allowed to interfere (or otherwise share resources) with the victim node. [0046] Thus, the management of CLI, such as the control of processes to mitigate the CLI, can be performed by or via the point of view of the victim node, which is experiencing the CLI. Such CLI management at the victim node can provide efficient selection of Tx or Rx beams and/or selection of interfering nodes (e.g., aggressor nodes), among other benefits. [0047] Aspects of the present disclosure are described in the context of a wireless communications system. Aspects of the present disclosure are further illustrated and described with reference to device diagrams and flowcharts. [0048] FIG.1 illustrates an example of a wireless communications system 100 that supports CLI management between network nodes in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more network entities 102, one or more UEs 104, a core network 106, and a packet data network 108. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a 5G network, such as an NR network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi- Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc. [0049] The one or more network entities 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the network entities 102 described herein may be or include or may be referred to as a network node, a Attorney Docket No.793MS0032PC Lenovo Docket No. SMM920220211-WO-PCT 9 base station, a network element, a radio network (RAN), a base transceiver station, an access point, a NodeB, an eNodeB (eNB), a next-generation NodeB (gNB), or other suitable terminology. A network entity 102 and a UE 104 may communicate via a communication link 110, which may be a wireless or wired connection. For example, a network entity 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface. [0050] A network entity 102 may provide a geographic coverage area 112 for which the network entity 102 may support services (e.g., voice, video, packet data, messaging, broadcast, etc.) for one or more UEs 104 within the geographic coverage area 112. For example, a network entity 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies. In some implementations, a network entity 102 may be moveable, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas 112 may be associated with different network entities 102. Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof. [0051] The one or more UEs 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a mobile device, a wireless device, a remote device, a remote unit, a handheld device, or a subscriber device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of-Things (IoT) device, an Internet-of-Everything (IoE) device, or machine-type communication (MTC) device, among other examples. In some implementations, a UE 104 may be stationary in Attorney Docket No.793MS0032PC Lenovo Docket No. SMM920220211-WO-PCT 10 the wireless communications system some other implementations, a UE 104 may be mobile in the wireless communications system 100. [0052] The one or more UEs 104 may be devices in different forms or having different capabilities. Some examples of UEs 104 are illustrated in FIG.1. A UE 104 may be capable of communicating with various types of devices, such as the network entities 102, other UEs 104, or network equipment (e.g., the core network 106, the packet data network 108, a relay device, an integrated access and backhaul (IAB) node, or another network equipment), as shown in FIG.1. Additionally, or alternatively, a UE 104 may support communication with other network entities 102 or UEs 104, which may act as relays in the wireless communications system 100. [0053] A UE 104 may also be able to support wireless communication directly with other UEs 104 over a communication link 114. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link 114 may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface. [0054] A network entity 102 may support communications with the core network 106, or with another network entity 102, or both. For example, a network entity 102 may interface with the core network 106 through one or more backhaul links 116 (e.g., via an S1, N2, N2, or another network interface). The network entities 102 may communicate with each other over the backhaul links 116 (e.g., via an X2, Xn, or another network interface). In some implementations, the network entities 102 may communicate with each other directly (e.g., between the network entities 102). In some other implementations, the network entities 102 may communicate with each other or indirectly (e.g., via the core network 106). In some implementations, one or more network entities 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs). Attorney Docket No.793MS0032PC Lenovo Docket No. SMM920220211-WO-PCT 11 [0055] In some implementations, a entity 102 may be configured in a disaggregated architecture, which may be configured to utilize a protocol stack physically or logically distributed among two or more network entities 102, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C- RAN)). For example, a network entity 102 may include one or more of a central unit (CU), a distributed unit (DU), a radio unit (RU), a RAN Intelligent Controller (RIC) (e.g., a Near- Real Time RIC (Near-RT RIC), a Non-Real Time RIC (Non-RT RIC)), a Service Management and Orchestration (SMO) system, or any combination thereof. [0056] An RU may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmission reception point (TRP). One or more components of the network entities 102 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 102 may be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU), a virtual DU (VDU), a virtual RU (VRU)). [0057] Split of functionality between a CU, a DU, and an RU may be flexible and may support different functionalities depending upon which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combinations thereof) are performed at a CU, a DU, or an RU. For example, a functional split of a protocol stack may be employed between a CU and a DU such that the CU may support one or more layers of the protocol stack and the DU may support one or more different layers of the protocol stack. In some implementations, the CU may host upper protocol layer (e.g., a layer 3 (L3), a layer 2 (L2)) functionality and signaling (e.g., Radio Resource Control (RRC), service data adaption protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU may be connected to one or more DUsor RUs, and the one or more DUs or RUs may host lower protocol layers, such as a layer 1 (L1) (e.g., physical (PHY) layer) or an L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling and may each be at least partially controlled by the CU 160. Attorney Docket No.793MS0032PC Lenovo Docket No. SMM920220211-WO-PCT 12 [0058] Additionally, or alternatively, functional split of the protocol stack may be employed between a DU and an RU such that the DU may support one or more layers of the protocol stack and the RU may support one or more different layers of the protocol stack. The DU may support one or multiple different cells (e.g., via one or more RUs). In some implementations, a functional split between a CU and a DU, or between a DU and an RU may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU, a DU, or an RU, while other functions of the protocol layer are performed by a different one of the CU, the DU, or the RU). [0059] A CU may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU may be connected to one or more DUs via a midhaul communication link (e.g., F1, F1-c, F1-u), and a DU may be connected to one or more RUs via a fronthaul communication link (e.g., open fronthaul (FH) interface). In some implementations, a midhaul communication link or a fronthaul communication link may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 102 that are in communication via such communication links. [0060] The core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The core network 106 may be an evolved packet core (EPC), or a 5G core (5GC), which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management functions (AMF)) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for the one or more UEs 104 served by the one or more network entities 102 associated with the core network 106. [0061] The core network 106 may communicate with the packet data network 108 over one or more backhaul links 116 (e.g., via an S1, N2, N2, or another network interface). The packet data network 108 may include an application server 118. In some implementations, Attorney Docket No.793MS0032PC Lenovo Docket No. SMM920220211-WO-PCT 13 one or more UEs 104 may communicate the application server 118. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the core network 106 via a network entity 102. The core network 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server 118 using the established session (e.g., the established PDU session). The PDU session may be an example of a logical connection between the UE 104 and the core network 106 (e.g., one or more network functions of the core network 106). [0062] In the wireless communications system 100, the network entities 102 and the UEs 104 may use resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communications). In some implementations, the network entities 102 and the UEs 104 may support different resource structures. For example, the network entities 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the network entities 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, the network entities 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures). The network entities 102 and the UEs 104 may support various frame structures based on one or more numerologies. [0063] One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., ^^^^=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., ^^^^=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., ^^^^=1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., ^^^^=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., ^^^^=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., ^^^^=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix. Attorney Docket No.793MS0032PC Lenovo Docket No. SMM920220211-WO-PCT 14 [0064] A time interval of a resource a communication resource) may be organized according to frames (also referred to as radio frames). Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration. [0065] Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., ^^^^=0, ^^^^=1, ^^^^=2, ^^^^=3, ^^^^=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., ^^^^=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots. [0066] In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz – 7.125 GHz), FR2 (24.25 GHz – 52.6 GHz), FR3 (7.125 GHz – 24.25 GHz), FR4 (52.6 GHz – 114.25 GHz), FR4a or FR4-1 (52.6 GHz – 71 GHz), and FR5 Attorney Docket No.793MS0032PC Lenovo Docket No. SMM920220211-WO-PCT 15 (114.25 GHz – 300 GHz). In some the network entities 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the network entities 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data). In some implementations, FR2 may be used by the network entities 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities. [0067] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., ^^^^=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., ^^^^=1), which includes 30 kHz subcarrier spacing; and a third numerology (e.g., ^^^^=2), which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies). For example, FR2 may be associated with a third numerology (e.g., ^^^^=2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., ^^^^=3), which includes 120 kHz subcarrier spacing. [0068] As described herein, the wireless communications system 100 supports the management of CLI between network nodes. FIG.2 illustrates an example of a diagram 200 that supports CLI management between two aggressor nodes and one victim node in accordance with aspects of the present disclosure. [0069] For example, two aggressor nodes 215 are interfering with a victim node 210 (e.g., a node experiencing CLI). While the aggressor nodes 215 and the victim node 210 are depicted as UEs, the nodes can also be network entities (e.g., gNBs), or various combinations of network entities and UEs. Thus, the victim node 210 is experiencing interference (H) 220 due to unintended transmissions of its neighboring aggressor nodes 215 being received by the victim node 210. [0070] While a network entity (e.g., a base station 102) or the UE 104 can be the victim node 210 or the aggressor nodes 215, any network node or entity can be considered a victim or aggressor based on how its signals or transmissions effect other network nodes or entities. Attorney Docket No.793MS0032PC Lenovo Docket No. SMM920220211-WO-PCT 16 [0071] For example, when there is of an unintended signal at a network node (e.g., CLI), the unintended signal is the interfering signal, the node that received the unintended signal is the victim (or victim node), and the node that transmitted the unintended signal is the aggressor (or aggressor node). Thus, nodes can be defined upon the occurrence of CLI and independent of entity type (e.g., gNB versus UE) class/power level (macro gNB versus small cell gNB), and so on. [0072] The victim node 210, based on the various embodiments described herein, can identify or select one or more preferred Tx-Rx beams 220 from the aggressor nodes 215, as well as identify or select a set of the aggressor nodes 215 that are allowed to interfere (or otherwise share resources) with the victim node 210. [0073] A beam (or beamforming) can include applying a spatial filter, in analog or digital domains, when transmitting or receiving a signal by one or multiple antennas, antenna panels, antenna elements, and so on, of a network node. Therefore, the beam can refer to a spatial filter in the analog domain on a transmitting antenna or a receiving antenna, a spatial filter in the digital domain, a reference signal transmitted while applying a spatial filter, a resource associated with the reference signal, and so on. Similarly, a beam index may refer to an index or ID associated with a spatial filter, a reference signal, and/or a reference signal resource. [0074] FIG.3 illustrates an example of a diagram 300 that supports a dynamic TDD system between network entities in accordance with aspects of the present disclosure. Two aggressor nodes 315 cause CLI at a victim node 310 in slots 312 (e.g., depicted as slot #2 and slot #3). While performing CLI management processes, the victim node 310 seeks to determine a scenario where the CLI is lowest – where there is the least interference in the slots 312 due to unintended transmissions H₁ and H₂ being received in the slots 312. [0075] As an example, where each node includes two antenna elements and a normalized DFT-based Tx and Rx beams, the victim node 310 can determine resulting CLI power for different cases: Case 1, where only aggressor node 1 is active; Case 2, where only aggressor node 2 is active, and Case 3, where both aggressor nodes are active. [0076] Given that: Attorney Docket No.793MS0032PC Lenovo Docket No. SMM920220211-WO-PCT 17 ^{[0077] ^^^^} ₁ ^{= �-0.3430 - 0.0168i 0.7667 + 0.6843i} 1_{.6663 + 0.3042i 2.6355 + 0.0558i} ^{�; and [0078] ^^^^} ₂ ^{= � -1.4018 - 0.1278i 1.5217 + 0.6029i} -_{1.3601 - 1.4103i 1.0547 - 0.4569i} ^�, [0079] using a 2-DFT Matrix: Ψ = ¹ √2_� ^{1 1} 1 _{−1� = [ ^^^^1 ^^^^2], where a victim gNB Rx} beam can be depicted as ^^^^ = as

follows:

[0080] Case 1 (CLI power when only aggressor 1 is active) – C_{ase 1.1: ^^^^1 =} ^| _^^^^ ^{^^^^} _{^^^^1 ^^^^1} ^|2 _{≈ 2.80 Case}

_{≈ 0.13}

[0081] Case 2 (CLI power when only aggressor 2 is active) − C_{ase 2.1: ^^^^1 =} ^| _^^^^ ^{^^^^} _{^^^^2 ^^^^1} ^|2 _{≈ 3.10} Case 2.2: ^^^^₂ = | ^^^^ ^{^^^^} ^^^^₂ ^^^^₂|² ≈ 2.03 [0082] Case 3: (CLI power when both aggressors are active) – C_{ase 3.1: ^^^^1,1 =} ^| _^^^^ ^{^^^^} _{^^^^1 ^^^^1 + ^^^^} ^{^^^^} _{^^^^2 ^^^^1} ^|2 _{≈ 0.03 0.31} 4.41 3.20

[0083] As shown, the best case (e.g., the case with the lowest CLI at the victim node 310 is Case 3.1, when both aggressors are active and each aggressor is using the TX beam #1, i.e., ^^^^₁). Thus, instead of reducing the number of aggressor nodes, the multiple interfering signals (H) at the victim node 310 can combine destructively to result in a lower CLI power at the victim node 310. The victim node 310, therefore, can efficiently and/or optimally determine what combinations of Tx beams and/or set of aggressor nodes 315 lead to a lower or the lowest CLI power, due to destructive interference of the beams at the victim node 310. Attorney Docket No.793MS0032PC Lenovo Docket No. SMM920220211-WO-PCT 18 [0084] For example, when the 310 is receiving a critical (e.g., Ultra- Reliable Low-Latency Communication or URLLC) signal over conflicting resources with the aggressor nodes 315, then a centralized-resource-scheduler (e.g., an entity that schedules the use or resources for a communications network and/or network nodes across cells) may determine to cancel the transmission of the aggressors when they exist independently (e.g., in Case 1 and Case 2 herein), but allow or enable a joint transmission (e.g., in Case 3 herein) of Tx beams due to the combined low CLI power at the victim node 310. Of course, in other scenarios, the centralized-resource-scheduler may enable single or joint transmissions, depending on the determined CLI power due to the transmissions. [0085] FIGs.4A-4B illustrate examples of diagrams 400, 450 that support different CLI management scenarios in accordance with aspects of the present disclosure. In Figure 4A, the management of CLI can be intra-cell between UEs acting as the network nodes, where CLI occurs at a victim UE 410 due to UE-UE CLI from multiple aggressor UEs 415. A network configuration entity (NCE), which can be part of a gNB-CU (control unit), OAM (Operations Administration and Maintenance), a UE, and so on, can identify the victim UE 410 based on physical location information for the victim UE 410 and neighboring UEs acting as the aggressor UEs 415. [0086] The NCE can configure the victim UE 410 with one or more non-overlapping CLI measurement resources (e.g., SRS-RSRP) on which the victim UE 410 is to measure CLI from the aggressor UEs 415 using one or more Rx beams. The NCE can configure each aggressor UE 415 with one or more non-overlapping CLI-RS signal resources on which each aggressor UE 415 transmits CLI-RSs (e.g., SRS) using one or more Tx beams. [0087] In addition to the physical location information, the NCE can identify the victim node 410 and the aggressor nodes 415 based on distances between the nodes, time- frequency resource allocations, pathloss and channel state information (CSI) measurements, the victim UE 410 detecting a beam or a radio-link failure, and so on. [0088] In some cases, the CLI resources may be configured as periodic, aperiodic, or semi-persistence. Further, as described herein, the CLI resources may be Frequency Division Multiplexed (FDMxd), such as over non-overlapping PRBs, and/or Time Division Attorney Docket No.793MS0032PC Lenovo Docket No. SMM920220211-WO-PCT 19 Multiplexed (TDMxd), such as over time symbols, slots, subframes, and so on. [0089] Figure 4B depicts a scenario 450 where the management of CLI can be intra-cell or inter-cell, coordinated by the centralized-resource-scheduler described herein. For inter- cell CLI management, the victim UE 410 can receive interfering signals from aggressor nodes 415 within different or neighboring cells (e.g., cells supported by gNB 470 and gNB 475), which are managed by a centralized-resource-scheduler 460. [0090] For example, when the victim UE 410 is set to measure CLI from ^^^^ ≥ 1 aggressor UEs 415, the network configuration entity may configure the victim UE 410 with ^^^^ CLI measurement resources and configure each aggressor UE 415 with ^^^^ CLI-RS resources. Following the example, when ^^^^ = 2 ^{^^^^} − 1 and ^^^^ = 2 ^{^^^^−1}, the following scenarios of different combinations for ^^^^ = 2 and ^^^^ = 3 are shown: ^^^^ = ^^^^ ( ^^^^ = ^^^^, ^^^^ = ^^^^) ^^^^ = ^^^^ ( ^^^^ = ^^^^, ^^^^ = ^^^^) CLI resource indices Aggressor UEs CLI resource indices Associated aggressor 3}

[0091] In some embodiments, configuration messages can ensure that the measured CLI by the victim UE 410 for every CLI measurement resource belongs to a unique subset of the aggressor UEs 415. FIG.5 illustrates an example of a diagram 500 that supports a Frequency Division Multiplexed (FDMxd) CLI resources configuration in accordance with aspects of the present disclosure. [0092] Following the ^^^^ = 2 scenario, the victim UE 410 may be configured with three non-overlapping CLI measurement resources 510 and each aggressor UE 415 may be configured with two non-overlapping CLI-RS resources 515. For example, the measured CLI by the victim UE 410 at CLI measurement resources #1 is only from a UE 1, the measured CLI by the victim UE 510 at CLI measurement resources #2 is only from a UE 2, Attorney Docket No.793MS0032PC Lenovo Docket No. SMM920220211-WO-PCT 20 and the measured CLI by the victim UE at CLI measurement resources #3 is from both aggressor UEs 415. Of course, various configurations can be utilized. [0093] For each CLI measurement resource, the victim UE 410 and each aggressor UE 415 can be configured to perform the CLI measurements using one or multiple Tx and Rx beams, such as using a pre-configured beam-sweeping time pattern. FIG.6 illustrates an example of a diagram 600 that supports a Time Division Multiplexed (TDMxd) CLI resources configuration in accordance with aspects of the present disclosure. [0094] Like the scenario depicted in FIG.5 and following the ^^^^ = 2 scenario, the victim UE 410 may be configured with three non-overlapping CLI measurement resources 610 and each aggressor UE 415 may be configured with two non-overlapping CLI-RS resources 615. For example, the measured CLI by the victim UE 410 at CLI measurement resources #1 is only from a UE 1, the measured CLI by the victim UE 510 at CLI measurement resources #2 is only from a UE 2, and the measured CLI by the victim UE 410 at CLI measurement resources #3 is from both aggressor UEs 415. Of course, various configurations can be utilized. [0095] In some embodiments, a UE can implicitly determine which beams to use for CLI measurements, such as based on which beams a UE uses for transmitting or receiving other signals. For example, the victim UE 410 can determine which Rx beams to use to measure CLI implicitly and based on the beams used for receiving one or more downlink signals (e.g., CSI-RSs, SSBs (Synchronization Signal Blocks, such as CD-SSB (cell- defining-SSB) or NCD-SSB (non-cell-defining-SSB), or NZP CSI-RS (non-zero power channel state information-reference signal), PDSCHs (Physical Downlink Shared Channels), and/or PDCCHs (Physical Downlink Control Channels)). Similarly, the aggressor UE 415 may determine which Tx beams to use implicitly and based on the beams used for transmitting one or more uplink signals (e.g., SRS, PUSCHs, and/or PUCCHs). [0096] In other cases, the NCE (e.g., a gNB-CU or OAM) can explicitly indicate to a UE which Tx or Rx beams to use for CLI measurements. [0097] In some embodiments, after performing CLI measurements, the victim UE 410 may be configured to generate and transmit a report to a requesting network entity (e.g., a Attorney Docket No.793MS0032PC Lenovo Docket No. SMM920220211-WO-PCT 21 serving gNB that send a request the victim UE 410). The report can include the indices and/or the CLI measurements of one or more of the CLI measurement resources that have the lowest and/or the highest CLI-RSRP and/or the indices and/or the CLI measurements of one or more of the preferred and/or the restricted Tx and Rx beams. [0098] The report can be periodic, aperiodic, semi-persistence, and/or event triggered. The serving gNB, or other network entity, can forward the report to a neighbor gNB, such as via backhaul of OTA (over-the-air) for inter-cell UE-UE CLI management. The gNB(s) can use the received measurement reports to select the best Tx and Rx beams for each UE and/or mute (e.g., cancel) the transmission of one or more aggressors on shared resources. [0099] FIG.7 illustrates an example of a diagram 700 that supports signaling between nodes and a network configuration entity 710 in accordance with aspects of the present disclosure. At step 0, the NCE 710 identifies the victim node 410 and the aggressor nodes 415 (e.g., 415A to 415N). [0100] At step 1, the NCE 710 configures the CLI measurement resources and CLI RSs. The NCE 710 can perform the configurations at the victim node 410 and/or the aggressor nodes 415A-N. At step 2, the aggressor nodes 415A-N perform CLI RS transmissions with the victim node 410. At step 3, the victim node 410 performs the CLI measurements, generates a report, and transmits the report to the NCE 710 (as described herein). [0101] As described herein, the network nodes can be base stations or other network entities, such as gNBs serving different cells and managed by the centralized-resource- scheduler. FIG.8 illustrates an example of a diagram 800 that supports a network entity CLI management scenario in accordance with aspects of the present disclosure. [0102] A centralized-resource-scheduler 805 manages the scheduling of transmissions performed by various neighboring gNBs, such as a victim gNB 810 and multiple aggressor gNBs 815. An NCE, which can be part of a gNB-CU or OAM, identifies the victim gNB and the aggressor gNBs 815, based on various factors described herein. For example, the NCE can identify the nodes based on their physical locations, the distances between the Attorney Docket No.793MS0032PC Lenovo Docket No. SMM920220211-WO-PCT 22 gNBs, node time-frequency resource pathloss and CSI measurements, a victim gNB detecting a beam or a radio-link failure, and so on. [0103] The NCE can configure the victim gNB 810 with one or more CLI measurement resources (e.g., CSI-IM) on which to measure CLI from one or more of the aggressor gNBs 815 using one or more Rx beams, and can configure each aggressor gNB 815 with one or more CLI-RS signal resources (e.g., NZP CSI-RS) on which to transmit CLI RS using one or more Tx beams. [0104] In some cases, the NCE can configure the CLI resources in a periodic, aperiodic, or semi-persistent manner, and the CLI resources can be FDMxd (e.g., over non- overlapping PRBs), as shown in FIG.5, or TDMxd (e.g., over non-overlapping time symbols, slots, subframes, and so on) as shown in FIG.6. [0105] For example, when the victim gNB 810 is set to measure CLI from ^^^^ ≥ 1 aggressor gNBs 815, the NCE may configure the victim gNB 810 with ^^^^ CLI measurement resources and configure each aggressor gNB 815 with ^^^^ CLI-RS resources. Thus, when ^^^^ = 2 ^{^^^^} − 1 and ^^^^ = 2 ^{^^^^−1}, the scenarios for the different combinations for ^^^^ = 2 and ^^^^ = 3 are as follows: ^^^^ = ^^^^ ( ^^^^ = ^^^^, ^^^^ = ^^^^) ^^^^ = ^^^^ ( ^^^^ = ^^^^, ^^^^ = ^^^^) CLI r r indi A r r NB CLI r r indi A r r NBs } } } B 3}

[0106] In some embodiments, configuration messages can ensure that the measured CLI by the victim gNB 810 for every CLI measurement resource belongs to a unique subset of the aggressor gNBs 815. Following the ^^^^ = 2 scenario, the victim gNB 810 may be configured with three non-overlapping CLI measurement resources and each aggressor gNB 815 may be configured with two non-overlapping CLI-RS resources, as depicted in FIG.5 and FIG 6 herein. Further, for each CLI measurement resource, the victim gNB 810 Attorney Docket No.793MS0032PC Lenovo Docket No. SMM920220211-WO-PCT 23 and each aggressor gNB 815 may be to perform the CLI measurements using one or multiple Tx and Rx beams using a pre-configured beam-sweeping time pattern. [0107] In some embodiments, a gNB can implicitly determine which beams to use for CLI measurements, such as based on which beams a gNB uses for transmitting or receiving other signals. For example, the victim gNB 810 can determine which Rx beams to use to measure CLI implicitly and based on the beams used for receiving one or more uplink signals (e.g., SRS, PUSCH, and/or PUCCH). Similarly, the aggressor gNB 815 may determine which Tx beams to use implicitly and based on the beams used for transmitting one or more downlink signals (e.g., CSI-RSs, SSBs, PDSCHs, and/or PDCCHs). [0108] In other cases, the NCE (e.g., a gNB-CU or OAM) can explicitly indicate to a gNB the Tx or Rx beams to use for CLI measurements. [0109] In some embodiments, after performing CLI measurements, the victim gNB 810 may be configured to generate and transmit a report to the NCE and/or to the aggressor gNBs 815 via backhaul and/or OTA transmission. The report can include indices and/or the CLI measurements of one or more of the CLI measurement resources that have the lowest and/or the highest CLI-RSRP and the indices and/or the CLI measurements of one or more of the preferred and/or the restricted Tx and Rx beams. [0110] The report may be periodic, aperiodic, semi-persistence, or event triggered. The NCE and/or an aggressor gNB 815 may use the received measurement reports to select the best Tx and Rx beams and/or mute (cancel) the transmission of one or more of the aggressors on the shared resources. The victim gNB 810 may use the CLI measurements locally to determine the best Rx beams or time-frequency allocations, among other uses. [0111] FIG.9 illustrates an example of a block diagram 900 of a device 902 that supports providing CLI management in accordance with aspects of the present disclosure. The device 902 may be an example of a network entity 102 as described herein. The device 902 may support wireless communication with one or more network entities 102, UEs 104, or any combination thereof. The device 902 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 904, a memory 906, a transceiver 908, and an I/O controller 910. These Attorney Docket No.793MS0032PC Lenovo Docket No. SMM920220211-WO-PCT 24 components may be in electronic or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses). [0112] The processor 904, the memory 906, the transceiver 908, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. For example, the processor 904, the memory 906, the transceiver 908, or various combinations or components thereof may support a method for performing one or more of the operations described herein. [0113] In some implementations, the processor 904, the memory 906, the transceiver 908, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field- programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. In some implementations, the processor 904 and the memory 906 coupled with the processor 904 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 904, instructions stored in the memory 906). [0114] For example, the processor 904 may support wireless communication at the device 902 in accordance with examples as disclosed herein. The processor 904 may be configured as or otherwise support a means for identifying a victim node and a set of aggressor nodes associated with the victim node, configuring the victim node with a set of non-overlapping cross-link interference (CLI) measurement resources associated with reception at the victim node, and configuring each aggressor node of the set of aggressor nodes with one or more non-overlapping CLI reference signal (RS) resources associated with transmission by the set of aggressor nodes. [0115] As another example, the processor 904 may support wireless communication at the device 902 in accordance with examples as disclosed herein. The processor 904 may be Attorney Docket No.793MS0032PC Lenovo Docket No. SMM920220211-WO-PCT 25 configured as or otherwise support a for receiving, from a network entity, a configuration that identifies a set of non-overlapping cross-link interference (CLI) measurement resources associated with receiving beams at the network node, performing CLI measurements using the set of non-overlapping CLI measurement resources, and transmitting, to the network entity, a report that indicates the performed CLI measurements based on the set of non-overlapping CLI measurement resources. [0116] The processor 904 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some implementations, the processor 904 may be configured to operate a memory array using a memory controller. In some other implementations, a memory controller may be integrated into the processor 904. The processor 904 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 906) to cause the device 902 to perform various functions of the present disclosure. [0117] The memory 906 may include random access memory (RAM) and read-only memory (ROM). The memory 906 may store computer-readable, computer-executable code including instructions that, when executed by the processor 904 cause the device 902 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some implementations, the code may not be directly executable by the processor 904 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some implementations, the memory 906 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices. [0118] The I/O controller 910 may manage input and output signals for the device 902. The I/O controller 910 may also manage peripherals not integrated into the device M02. In some implementations, the I/O controller 910 may represent a physical connection or port to an external peripheral. In some implementations, the I/O controller 910 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®, Attorney Docket No.793MS0032PC Lenovo Docket No. SMM920220211-WO-PCT 26 UNIX®, LINUX®, or another known system. In some implementations, the I/O controller 910 may be implemented as part of a processor, such as the processor M04. In some implementations, a user may interact with the device 902 via the I/O controller 910 or via hardware components controlled by the I/O controller 910. [0119] In some implementations, the device 902 may include a single antenna 912. However, in some other implementations, the device 902 may have more than one antenna 912 (i.e., multiple antennas), including multiple antenna panels or antenna arrays, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 908 may communicate bi-directionally, via the one or more antennas 912, wired, or wireless links as described herein. For example, the transceiver 908 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 908 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 912 for transmission, and to demodulate packets received from the one or more antennas 912. [0120] FIG.10 illustrates a flowchart of a method 1000 that supports configuring network nodes to perform CLI measurements in accordance with aspects of the present disclosure. The operations of the method 1000 may be implemented by a device or its components as described herein. For example, the operations of the method 1000 may be performed by the network entity 102 as described with reference to FIGs.1 through 8. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware. [0121] At 1005, the method 1000 may include identifying a victim node and a set of aggressor nodes associated with the victim node. The operations of 1005 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1005 may be performed by a device as described with reference to FIG.1. [0122] At 1010, the method 1000 may include configuring the victim node with a set of non-overlapping CLI measurement resources associated with reception at the victim node. The operations of 1010 may be performed in accordance with examples as described Attorney Docket No.793MS0032PC Lenovo Docket No. SMM920220211-WO-PCT 27 herein. In some implementations, the operations of 1010 may be performed by a device as described with reference to FIG.1. [0123] At 1015, the method 1000 may include configuring each aggressor node of the set of aggressor nodes with one or more non-overlapping CLI RS resources associated with transmission by the set of aggressor nodes. The operations of 1015 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1015 may be performed by a device as described with reference to FIG.1. [0124] At 1020, the method 1000 may include receiving, in response to sending a request to the victim node, a report that indicates CLI measurements based on the set of non-overlapping CLI measurement resources and the non-overlapping CLI RS resources. The operations of 1020 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1020 may be performed by a device as described with reference to FIG.1. [0125] FIG.11 illustrates a flowchart of a method 1100 that supports measuring CLI via a victim node in accordance with aspects of the present disclosure. The operations of the method 1100 may be implemented by a device or its components as described herein. For example, the operations of the method 1100 may be performed by the UE 104 (or another victim node) as described with reference to FIGs.1 through 8. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware. [0126] At 1105, the method 1100 may include receiving, from a network entity, a configuration that identifies a set of non-overlapping CLI measurement resources associated with receiving beams at the network node. The operations of 1105 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1105 may be performed by a device as described with reference to FIG.1. [0127] At 1110, the method 1100 may include performing CLI measurements using the set of non-overlapping CLI measurement resources. The operations of 1110 may be Attorney Docket No.793MS0032PC Lenovo Docket No. SMM920220211-WO-PCT 28 performed in accordance with examples described herein. In some implementations, aspects of the operations of 1110 may be performed by a device as described with reference to FIG.1. [0128] At 1115, the method 1100 may include transmitting, to the network entity, a report that indicates the performed CLI measurements based on the set of non-overlapping CLI measurement resources. The operations of 1115 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1115 may be performed by a device as described with reference to FIG.1. [0129] It should be noted that the methods described herein describes possible implementations, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. Further, aspects from two or more of the methods may be combined. [0130] The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. [0131] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features Attorney Docket No.793MS0032PC Lenovo Docket No. SMM920220211-WO-PCT 29 implementing functions may also be located at various positions, including being distributed such that portions of functions are implemented at different physical locations. [0132] Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. [0133] Any connection may be properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer- readable media. [0134] As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of” or “one or more of” or “one or both of”) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both Attorney Docket No.793MS0032PC Lenovo Docket No. SMM920220211-WO-PCT 30 a condition A and a condition B without from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements. [0135] The terms “transmitting,” “receiving,” or “communicating,” when referring to a network entity, may refer to any portion of a network entity (e.g., a base station, a CU, a DU, a RU) of a RAN communicating with another device (e.g., directly or via one or more other network entities). [0136] The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term “example” used herein means “serving as an example, instance, or illustration,” and not “preferred” or “advantageous over other examples.” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described example. [0137] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein. Attorney Docket No.793MS0032PC

Claims

Lenovo Docket No. SMM920220211-WO-PCT 31 CLAIMS What is claimed is: 1. A network entity, comprising: a processor; and a memory coupled with the processor, the processor configured to cause the network entity to: identify a victim node and a set of aggressor nodes associated with the victim node; configure the victim node with a set of non-overlapping cross-link interference (CLI) measurement resources associated with reception at the victim node; and configure each aggressor node of the set of aggressor nodes with one or more non-overlapping CLI reference signal (RS) resources associated with transmission by the set of aggressor nodes. 2. The network entity of claim 1, wherein the processor is further configured to receive, in response to sending a request to the victim node, a report that indicates CLI measurements based on the set of non-overlapping CLI measurement resources and the non-overlapping CLI RS resources. 3. The network entity of claim 2, wherein the report is received from the victim node via uplink control information (UCI) over a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH). 4. The network entity of claim 2, wherein the report is received from the victim node via a MAC-CE (Medium Access Control-Control Element). Attorney Docket No.793MS0032PC Lenovo Docket No. SMM920220211-WO-PCT 32 5. The network entity of claim the report is received from the victim node via Over-the-Air (OTA) connections or backhaul connections between the victim node and the network entity. 6. The network entity of claim 2, wherein the report includes: indices or CLI measurements for one or more of CLI measurement resources having lowest or highest CLI-RSRP (Reference Signal Received Power) or CLI- RSSI (Received Signal Strength Indicator); or indices or CLI measurements for one or more of preferred transmission beams or reception beams or one or more of restricted transmission beams or reception beams. 7. The network entity of claim 1, wherein the victim node and the set of aggressor nodes include User Equipment (UEs) or network entities. 8. The network entity of claim 1, wherein the network entity is supported by one aggressor node of the set of aggressor nodes as a network configuration entity. 9. The network entity of claim 1, wherein the set of non-overlapping CLI measurement resources includes SRS-RSRP (Sounding Reference Signal-Reference Signal Received Power), SRS-RSSI (Sounding Reference Signal-Received Signal Strength Indicator), or CSI-IM (channel state information-interference measurement). 10. The network entity of claim 1, wherein the set of non-overlapping CLI RS resources includes SRS, CD-SSB (cell-defining Synchronization Signal Block), NCD-SSB (non-cell-defining-SSB), or NZP CSI-RS (non-zero power channel state information- reference signal). 11. The network entity of claim 1, wherein the processor identifies the victim node and the set of aggressor nodes based on one or more of factors, including: physical locations of the victim node and the set of aggressor nodes; Attorney Docket No.793MS0032PC Lenovo Docket No. SMM920220211-WO-PCT 33 distances between the victim the set of aggressor nodes; time-frequency resource allocations for the victim node and the set of aggressor nodes; pathloss and CSI measurements performed by the victim node and the set of aggressor nodes; or beam or radio link failures detected by the victim node. 12. The network entity of claim 1, wherein each CLI measurement resource of the set of CLI measurement resources is associated with a unique subset of CLI RS resources configured at the set of aggressor nodes over the same time-frequency resources. 13. The network entity of claim 1, wherein the victim node identifies a set of receive beams for measuring CLI based on receive beams used for receiving other downlink signals or other uplink signals. 14. The network entity of claim 1, wherein the network entity configures the victim node to receive an indication of a set of receive beams for measuring CLI. 15. The network entity of claim 1, wherein the set of aggressor nodes identifies a set of transmit beams for transmitting CLI RS based on transmit beams used when transmitting other downlink signals or other uplink signals. 16. The network entity of claim 1, wherein the network entity configures the set of aggressor nodes to receive an indication of a set of transmit beams for transmitting CLI RS. Attorney Docket No.793MS0032PC Lenovo Docket No. SMM920220211-WO-PCT 34 17. The network entity of claim the network entity configures the set of non-overlapping CLI measurement resources or the set of non-overlapping CLI RS resources in a periodic, aperiodic, or semi-persistent manner. 18. A method performed by a network entity, the method comprising: identifying a victim node and a set of aggressor nodes associated with the victim node; configuring the victim node with a set of non-overlapping cross-link interference (CLI) measurement resources associated with reception at the victim node; and configuring each aggressor node of the set of aggressor nodes with one or more non-overlapping CLI reference signal (RS) resources associated with transmission by the set of aggressor nodes. 19. A network node, comprising: a processor; and a memory coupled with the processor, the processor configured to cause the network node to: receive, from a network entity, a configuration that identifies a set of non-overlapping cross-link interference (CLI) measurement resources associated with receiving beams at the network node; perform CLI measurements using the set of non-overlapping CLI measurement resources; and transmit, to the network entity, a report that indicates the performed CLI measurements based on the set of non-overlapping CLI measurement resources. Attorney Docket No.793MS0032PC Lenovo Docket No. SMM920220211-WO-PCT 35 20. A processor for wireless comprising: at least one controller coupled with at least one memory and configured to cause the processor to: identify a victim node and a set of aggressor nodes associated with the victim node; configure the victim node with a set of non-overlapping cross-link interference (CLI) measurement resources associated with reception at the victim node; and configure each aggressor node of the set of aggressor nodes with one or more non-overlapping CLI reference signal (RS) resources associated with transmission by the set of aggressor nodes. Attorney Docket No.793MS0032PC