Cross-link interference (CLI) management via combined beam and aggressor selection

Abstract

Aspects of the present disclosure relate to selection of combined beams and / or aggressor nodes during cross-link interference (CLI) management within a wireless communication system. For example, a network node (e.g., a victim node) that is experiencing CLI may identify or select preferred transmit or receive beams (Tx-Rx beams) from other nodes, and identify or select a set of other nodes (e.g., a set of aggressor nodes) that are allowed to interfere with the victim node (or otherwise share resources with the victim node).

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] 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 ANDAGGRESSOR SELECTION,” the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present disclosure relates to wireless communications, and more particularly to cross-link interference (CLI) management between nodes supporting a wireless communications network. Background Art

[0004] A wireless communication system may include one or more network communication devices (such as base stations), which may also be referred to as eNodeBs (eNBs), next generation NodeBs (gNBs), or other appropriate terms. Each network communication device (such as a base station) may support wireless communication for one or more user communication devices, which may also be referred to as user equipment (UEs) or other appropriate terms. A wireless communication system may support wireless communication with one or more user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)). Additionally, a wireless communication system may support wireless communication across various radio access technologies, including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, and other appropriate radio access technologies beyond 5G (e.g., sixth generation (6G)).

[0005] Typically, during network communications, neighboring nodes (e.g., network cells or UEs) may utilize different time division duplex (TDD) downlink (DL) and / or uplink (UL) modes. However, different TDD modes may result in CLI, where the UL transmission of one node interferes with the DL reception of another node (e.g., a neighboring node). Typically, nodes (such as gNBs) may exchange and / or coordinate their TDD DL-UL configurations over a communication interface, where a UE experiencing CLI may perform CLI measurements. Example CLI measurements include SRS-RSRP (Sounding Resource Signal - Reference Signal Received Power) measurements on the SRS resources of the node providing interference (e.g., unintended transmissions) to the UE, CLI-RSSI (Received Signal Strength Indicator) measurements of the total received power observed on RSSI resources, etc. Summary of the Invention

[0006] The present disclosure relates to methods, apparatus, and systems that support CLI management, wherein a node (e.g., a UE or gNB) experiencing CLI can identify or select preferred transmit or receive beams (Tx-Rx beams) from other nodes, as well as identify or select a set of other nodes that are allowed to interfere with the node (or otherwise share resources with the node).

[0007] Some implementations of the methods and apparatus described herein may also include a network entity comprising a processor and a memory coupled to 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, for the victim node, a set of non-overlapping CLI measurement resources associated with reception at the victim node; and configure, for each aggressor node in the set of aggressor nodes, one or more non-overlapping CLI reference signal (RS) resources associated with transmissions by the set of aggressor nodes.

[0008] In some implementations of the methods and apparatus described herein, the processor is further configured to receive a report in response to sending a request to the victim node, the report indicating CLI measurements based on the set of non-overlapping CLI measurement resources and the non-overlapping CLIRS resources.

[0009] In some implementations of the methods and apparatus 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).

[0010] In some implementations of the methods and apparatus described herein, the report is received from the victim node via a MAC-CE (Media Access Control - Control Element).

[0011] In some implementations of the methods and apparatus described herein, the report is received from the victim node via an over-the-air (OTA) connection or a backhaul connection between the victim node and a network entity.

[0012] In some implementations of the methods and apparatus described herein, the report includes an index or CLI measurement of one or more CLI measurement resources among the CLI measurement resources having the lowest or highest CLI-RSRP or CLI-RSSI; or an index or CLI measurement of one or more of the preferred transmit beams or receive beams, or one or more of the restricted transmit beams or receive beams.

[0013] In some implementations of the methods and apparatus described herein, the set of victim nodes and aggressor nodes includes a UE.

[0014] In some implementations of the methods and apparatus described herein, the set of victim nodes and aggressor nodes comprises a network entity.

[0015] In some implementations of the methods and apparatus described herein, the network entity is supported by an aggressor node from a set of aggressor nodes that are network configuration entities.

[0016] In some implementations of the methods and apparatus described herein, the set of non-overlapping CLI measurement resources includes SRS-RSRP, SRS-RSSI, or CSI-IM (Channel State Information - Interference Measurement).

[0017] In some implementations of the methods and apparatus described herein, the set of non-overlapping CLI RS resources includes SRS, SSB (synchronization signal block), CD-SSB (cell-defined SSB), NCD-SSB (non-cell-defined SSB), or NZP CSI-RS (non-zero power channel state information-reference signal).

[0018] In some implementations of the methods and apparatus described herein, the processor is further configured to identify the set of victim nodes and aggressor nodes based on one or more of factors, including: a physical location of the set of victim nodes and aggressor nodes, a distance between the victim nodes and the set of aggressor nodes, a time-frequency resource allocation for the set of victim nodes and aggressor nodes, path loss and CSI measurements performed by the set of victim nodes and aggressor nodes, and / or beam or radio link failures detected by the victim nodes.

[0019] In some implementations of the methods and apparatus described herein, each CLI measurement resource in the set of CLI measurement resources is associated with a unique subset of CLIRS resources configured at the set of aggressor nodes on the same time-frequency resources.

[0020] In some implementations of the methods and apparatus described herein, the victim node identifies a set of receive beams for measuring CLI based on receive beams used to receive other downlink signals or other uplink signals.

[0021] In some implementations of the methods and apparatus described herein, a network entity configures the victim node to receive an indication of a set of receive beams for measuring CLI.

[0022] In some implementations of the methods and apparatus described herein, the set of aggressor nodes identifies a set of transmit beams for transmitting CLIRS based on transmit beams used when transmitting other downlink signals or other uplink signals.

[0023] In some implementations of the methods and apparatus described herein, a network entity configures a set of aggressor nodes to receive an indication of a set of transmit beams for transmitting CLIRS.

[0024] In some implementations of the methods and apparatus described herein, a network entity configures a set of non-overlapping CLI measurement resources or a set of non-overlapping CLIRS resources in a periodic, aperiodic, or semi-persistent manner.

[0025] Some implementations of the methods and apparatus described herein may also 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, for the victim node, a set of non-overlapping CLI measurement resources associated with reception at the victim node; and configuring, for each aggressor node in the set of aggressor nodes, one or more non-overlapping CLI reference signal (RS) resources associated with transmissions by the set of aggressor nodes.

[0026] In some implementations of the methods and apparatus described herein, the method further includes receiving a report in response to sending the request to the victim node, the report indicating CLI measurements based on the set of non-overlapping CLI measurement resources and the non-overlapping CLIRS resources.

[0027] Some implementations of the methods and apparatus described herein may also include a network node comprising a processor and a memory coupled to the processor, the processor configured to cause the network node to: receive a configuration from a network entity, the configuration identifying a set of non-overlapping CLI measurement resources associated with a receive beam at the network node; perform CLI measurements using the set of non-overlapping CLI measurement resources; and send a report to the network entity indicating the CLI measurements performed based on the set of non-overlapping CLI measurement resources.

[0028] In some implementations of the methods and apparatus described herein, each CLI measurement resource in the set of non-overlapping CLI measurement resources is associated with a unique subset of CLIRS resources configured at the set of aggressor nodes on the same time-frequency resources.

[0029] In some implementations of the methods and apparatus described herein, the network node is a victim node that receives interfering signals from multiple aggressor nodes.

[0030] In some implementations of the methods and apparatus described herein, the network node is a UE.

[0031] In some implementations of the methods and apparatus described herein, the network node is another network entity.

[0032] Some implementations of the methods and apparatus described herein may also include a method performed by a network node associated with a set of aggressor nodes, the method comprising: receiving a configuration from a network entity, the configuration identifying a set of non-overlapping CLI measurement resources associated with receive beams at the network node; performing CLI measurements using the set of non-overlapping CLI measurement resources; and sending a report to the network entity, the report indicating the CLI measurements performed based on the set of non-overlapping CLI measurement resources.

[0033] In some implementations of the methods and apparatus described herein, the network node is a victim node that receives interfering signals from multiple aggressor nodes. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] Figure 1 An example of a wireless communication system supporting CLI management between nodes according to aspects of the present disclosure is illustrated.

[0035] Figure 2 Illustrated is an example of a graph supporting CLI management between two aggressor nodes and one victim node, according to aspects of the present disclosure.

[0036] Figure 3 Illustrated is an example of a diagram supporting a dynamic TDD system between network entities according to aspects of the present disclosure.

[0037] Figures 4A to 4B Illustrated are examples of diagrams supporting different CLI management scenarios according to aspects of the present disclosure.

[0038] Figure 5 Illustrated is an example of a diagram supporting frequency division multiplexing (FDMxd) CLI resource configuration according to aspects of the present disclosure.

[0039] Figure 6 Illustrated is an example of a diagram supporting time division multiplexing (TDMxd) CLI resource configuration according to aspects of the present disclosure.

[0040] Figure 7 An example of a diagram illustrating signaling between a support node and a network configuration entity according to aspects of the present disclosure is illustrated.

[0041] Figure 8 Illustrated is an example of a diagram supporting a network entity CLI management scenario according to aspects of the present disclosure.

[0042] Figure 9 Illustrated is an example of a block diagram of a device that supports providing CLI management according to aspects of the present disclosure.

[0043] Figure 10Illustrated is a flow chart supporting a method of configuring a network node to perform CLI measurements according to aspects of the present disclosure.

[0044] Figure 11 A flow chart illustrating a method of supporting measurement of CLI via a victim node according to aspects of the present disclosure is illustrated. DETAILED DESCRIPTION

[0045] As described herein, CLI management between network nodes of a wireless communication system (e.g., UE to UE and / or network entity to network entity) may involve the exchange of information between the nodes, such as the exchange of TDD DL-UL configurations between the network nodes. This exchange of information may inefficiently utilize network resources and / or be performed by entities that are not experienced with CLI issues.

[0046] However, based on the techniques described herein, a network node that is experiencing CLI (e.g., a victim node) can identify or select preferred transmit or receive 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) that are allowed to interfere with the victim node (or otherwise share resources with the victim node).

[0047] Thus, management of CLI (such as control of the process of mitigating CLI) can be performed by or from the perspective of a victim node experiencing 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.

[0048] Aspects of the present disclosure are described in the context of a wireless communication system.Aspects of the present disclosure are further illustrated and described with reference to device diagrams and flow charts.

[0049] Figure 1An example of a wireless communication system 100 that supports CLI management between network nodes according to aspects of the present disclosure is illustrated. The wireless communication 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 communication system 100 may support various radio access technologies. In some implementations, the wireless communication 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 communication system 100 may be a 5G network, such as an NR network. In other implementations, the wireless communication system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technologies, including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), or IEEE 802.20. The wireless communication system 100 may support radio access technologies other than 5G. Additionally, the wireless communication system 100 may support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).

[0050] One or more network entities 102 may be dispersed throughout a geographic area to form a wireless communication system 100. One or more of the network entities 102 described herein may be, include, or be referred to as a network node, a base station, a network element, a radio access network (RAN), a base transceiver station, an access point, a NodeB, an eNodeB (eNB), a next generation NodeB (gNB), or other suitable terminology. The network entity 102 and the UE 104 may communicate via a communication link 110, which may be a wireless or wired connection. For example, the network entity 102 and the UE 104 may perform wireless communication (e.g., receive signaling, send signaling) over a Uu interface.

[0051] The network entity 102 may provide a geographic coverage area 112 for which it 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, the network entity 102 and the UEs 104 may support wireless communication of signals associated with the services (e.g., voice, video, packet data, messaging, broadcast, etc.) based on one or more radio access technologies. In some implementations, the network entity 102 may be mobile, such as 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 different geographic coverage areas 112 may be associated with different network entities 102. The 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.

[0052] One or more UEs 104 may be dispersed throughout the geographic area of the wireless communication system 100. The 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, etc. Additionally or alternatively, the UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine Type Communication (MTC) device, etc. In some implementations, the UE 104 may be stationary within the wireless communication system 100. In some other implementations, the UE 104 may be mobile within the wireless communication system 100.

[0053] One or more UEs 104 may be devices of different forms or with different capabilities. Figure 1 Some examples of UE 104 are shown in FIG. Figure 1 As shown, the UE 104 may be able to communicate with various types of devices, such as a network entity 102, other UEs 104, or a network device (e.g., a core network 106, a packet data network 108, a relay device, an integrated access and backhaul (IAB) node, or another network device), such as Figure 1 Additionally or alternatively, the UE 104 can support communications with other network entities 102 or UEs 104 that can act as relays in the wireless communication system 100 .

[0054] The UE 104 may also be capable of supporting wireless communications directly with other UEs 104 via a communication link 114. For example, the UE 104 may support wireless communications directly with another UE 104 via 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, the UE 104 may support wireless communications directly with another UE 104 via a PC5 interface.

[0055] The network entities 102 may support communication with the core network 106 or with another network entity 102, or both. For example, the network entities 102 may interface with the core network 106 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). The network entities 102 may communicate with each other via the backhaul links 116 (e.g., via X2, Xn, or another network interface). In some implementations, the network entities 102 may communicate directly with each other (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). The ANC may communicate with one or more UEs 104 via one or more other access network transport entities, which may be referred to as radio heads, smart radio heads, or transmission reception points (TRPs)).

[0056] In some implementations, the network entity 102 can be configured with a decomposed architecture that can be configured to utilize a protocol stack that is physically or logically distributed between 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, the network entity 102 can include one or more of the following: 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.

[0057] The RU may also be referred to as a radio head, smart radio head, remote radio head (RRH), remote radio unit (RRU), or transmission reception point (TRP). In a disaggregated RAN architecture, one or more components of the network entity 102 may be collocated, or one or more components of the network entity 102 may be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 of the disaggregated RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0058] The functional split between the CU, DU, and RU can be flexible, and different functions can be supported depending on the functions performed at the CU, DU, or RU (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof). For example, a functional split of the protocol stack can be adopted between the CU and the DU, such that the CU can support one or more layers of the protocol stack, and the DU can support one or more different layers of the protocol stack. In some implementations, the CU can host upper protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functions and signaling (e.g., Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU can be connected to one or more DUs or RUs, and one or more DUs or RUs can host lower protocol layers, such as Layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, media access control (MAC) layer) functions and signaling, and each DU or RU can be at least partially controlled by the CU 160.

[0059] Additionally or alternatively, a functional split of the protocol stack may be employed between the DU and the 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 more different cells (e.g., via one or more RUs). In some implementations, the functional split between the CU and the DU or between the DU and the RU may be within the protocol layer (e.g., some functions for a protocol layer may be performed by one of the CU, DU, or RU, while other functions of the protocol layer may be performed by different ones of the CU, DU, or RU).

[0060] The CU can be further functionally split into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. The CU can be connected to one or more DUs via a medium-range communication link (e.g., F1, F1-c, F1-u), and the DU can be connected to one or more RUs via a fronthaul communication link (e.g., an open fronthaul (FH) interface). In some implementations, the medium-range communication link or the fronthaul communication link can be implemented according to an interface (e.g., a channel) between layers of a protocol stack supported by the corresponding network entity 102 communicating via such a communication link.

[0061] 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 control plane entities that manage access and mobility (e.g., mobility management entity (MME), access and mobility management function (AMF)), and user plane entities that route packets or interconnections to external networks (e.g., serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)). In some implementations, the control plane entities may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearer, signaling bearer, etc.) for one or more UEs 104 served by one or more network entities 102 associated with the core network 106.

[0062] The core network 106 can communicate with the packet data network 108 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). The packet data network 108 can include an application server 118. In some implementations, one or more UEs 104 can communicate with the application server 118. The UE 104 can establish a session (e.g., a protocol data unit (PDU) session, etc.) with the core network 106 via the network entity 102. The core network 106 can use the established session (e.g., the established PDU session) to route traffic (e.g., control information, data, etc.) between the UE 104 and the application server 118. The PDU session can 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).

[0063] In the wireless communication system 100, the network entity 102 and the UE 104 may use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communications). In some implementations, the network entity 102 and the UE 104 may support different resource structures. For example, the network entity 102 and the UE 104 may support different frame structures. In some implementations, such as in 4G, the network entity 102 and the UE 104 may support a single frame structure. In some other implementations, such as in 5G and other suitable radio access technologies, the network entity 102 and the UE 104 may support various frame structures (i.e., multiple frame structures). The network entity 102 and the UE 104 may support various frame structures based on one or more digital technologies.

[0064] One or more digital technologies may be supported in the wireless communication system 100, and the digital technologies may include subcarrier spacing and cyclic prefixes. A first digital technology (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 digital technology (e.g., μ = 0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second digital technology (e.g., μ = 1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third digital technology (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 digital technology (e.g., μ = 3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth digital technology (e.g., μ = 4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0065] The time intervals of resources (e.g., communication resources) can be organized according to frames (also referred to as radio frames). Each frame can have a duration, for example, a duration of 10 milliseconds (ms). In some implementations, each frame can include multiple subframes. For example, each frame can include 10 subframes, and each subframe can have a duration, for example, a duration of 1 ms. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

[0066] Additionally or alternatively, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe can include a certain number (e.g., quantity) of time slots. The number of time slots in each subframe can also depend on one or more digital technologies supported in the wireless communication system 100. For example, a first digital technology, a second digital technology, a third digital technology, a fourth digital technology, and a fifth digital technology (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with corresponding subcarrier spacings of 15kHz, 30kHz, 60kHz, 120kHz, and 240kHz can utilize a single time slot per subframe, two time slots per subframe, four time slots per subframe, eight time slots per subframe, and 16 time slots per subframe, respectively. Each time slot can include a certain number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of time slots for a subframe can depend on the digital technology. For a conventional cyclic prefix, a time slot can include 14 symbols. For an extended cyclic prefix (e.g., for a 60 kHz subcarrier spacing), a slot may include 12 symbols. For both a normal cyclic prefix and an extended cyclic prefix, the relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame may depend on the digital technology. It should be understood that references to a first digital technology (e.g., μ = 0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0067] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, frequency channels, etc. based on frequency or wavelength. For example, the wireless communication system 100 can support one or more operating frequency bands, such as the 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 (114.25 GHz-300 GHz). In some implementations, the network entity 102 and the UE 104 can perform wireless communications on one or more operating frequency bands. In some implementations, FR1 can be used by the network entity 102 and the UE 104, as well as other devices or apparatuses, for cellular communication traffic (e.g., control information, data). In some implementations, FR2 can be used by the network entity 102 and the UE 104, as well as other devices or apparatuses, for short-range, high data rate capabilities.

[0068] FR1 may be associated with one or more digital technologies (e.g., at least three digital technologies). For example, FR1 may be associated with a first digital technology (e.g., μ = 0) including a subcarrier spacing of 15 kHz, a second digital technology (e.g., μ = 1) including a subcarrier spacing of 30 kHz, and a third digital technology (e.g., μ = 2) including a subcarrier spacing of 60 kHz. FR2 may be associated with one or more digital technologies (e.g., at least two digital technologies). For example, FR2 may be associated with a third digital technology (e.g., μ = 2) including a subcarrier spacing of 60 kHz, and a fourth digital technology (e.g., μ = 3) including a subcarrier spacing of 120 kHz.

[0069] As described herein, wireless communication system 100 supports CLI management between network nodes. Figure 2 Illustrated is an example of a diagram 200 supporting CLI management between two aggressor nodes and one victim node, according to aspects of the present disclosure.

[0070] For example, two aggressor nodes 215 are interfering with victim node 210 (e.g., a node experiencing CLI). Although aggressor nodes 215 and victim node 210 are depicted as UEs, these nodes can also be network entities (e.g., gNBs), or various combinations of network entities and UEs. Victim node 210 is experiencing interference (H) 220 because it receives unexpected transmissions from its neighboring aggressor node 215.

[0071] While a network entity (eg, base station 102) or UE 104 can be a victim node 210 or an aggressor node 215, any network node or entity can be considered a victim or aggressor based on how its signals or transmissions affect other network nodes or entities.

[0072] For example, when an unexpected signal is received at a network node (e.g., CLI), the unexpected signal is an interference signal, the node that receives the unexpected signal is a victim (or victim node), and the node that transmits the unexpected signal is an aggressor (or aggressor node). Therefore, a node can be defined when CLI occurs, regardless of entity type (e.g., gNB vs. UE), category / power class (macro gNB vs. small cell gNB), etc.

[0073] Based on various embodiments described herein, the victim node 210 may identify or select one or more preferred Tx-Rx beams 220 from the aggressor node 215, as well as identify or select a set of aggressor nodes 215 that are allowed to interfere with the victim node 210 (or otherwise share resources with the victim node).

[0074] Beaming (or beamforming) may include applying a spatial filter in the analog or digital domain when transmitting or receiving a signal by one or more antennas, antenna panels, antenna elements, etc. of a network node. Thus, a beam may refer to a spatial filter in the analog domain on a transmit antenna or a receive antenna, a spatial filter in the digital domain, a reference signal transmitted when applying the spatial filter, a resource associated with the reference signal, etc. 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.

[0075] Figure 3 An example of a diagram 300 supporting a dynamic TDD system between network entities according to aspects of the present disclosure is illustrated. Two aggressor nodes 315 cause CLI at a victim node 310 in time slots 312 (e.g., depicted as time slots #2 and #3). When performing the CLI management process, the victim node 310 attempts to determine the scenario where the CLI is lowest (due to the least interference in time slot 312 due to the unexpected transmissions H1 and H2 being received in time slot 312).

[0076] For example, where each node includes two antenna elements and normalized DFT-based Tx and Rx beams, the victim node 310 may determine the 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.

[0077] Given that:

[0078] and

[0079]

[0080] Using the 2-DFT matrix: Where the victim gNB Rx beam can be depicted as u=ψ1, and the CLI power in different cases is determined as follows:

[0081] Case 1 (CLI power when only aggressor 1 is active) -

[0082] Case 1.1: I1=|u H H1ψ1| 2 ≈2.80

[0083] Case 1.2: I2=|u H H1ψ2| 2 ≈0.13

[0084] Case 2 (CLI power when only aggressor 2 is active) -

[0085] Case 2.1: I1=|u H H2ψ1| 2 ≈3.10

[0086] Case 2.2: I2=|u H H2ψ2| 2 ≈2.03

[0087] Case 3: (CLI power when both aggressors are active) -

[0088] Case 3.1: I 1，1 =|u H H1ψ1+u H H2ψ1| 2 ≈0.03

[0089] Case 3.2: I 1，2 =|u H H1ψ1+u H H2ψ2| 2 ≈0.31

[0090] Case 3.3: I 2，1 =|u H H1ψ2+u H H2ψ1| 2 ≈4.41

[0091] Case 3.4: I 2，2 =|u H H1ψ2+u H H2ψ2| 2 ≈3.20

[0092] As shown, the best case scenario (e.g., when both aggressors are active and each aggressor is using TX beam #1, i.e., ψ1) with the lowest CLI at the victim node 310 is case 3.1. Therefore, rather than reducing the number of aggressor nodes, multiple interfering signals (H) at the victim node 310 can destructively combine to result in a lower CLI power at the victim node 310. Thus, the victim node 310 can efficiently and / or optimally determine which combinations of Tx beams and / or aggressor nodes 315 result in a lower or lowest CLI power due to destructive interference of beams at the victim node 310.

[0093] For example, when the victim node 310 receives a critical (e.g., ultra-reliable low-latency communication or URLLC) signal via a resource that conflicts with the aggressor node 315, a centralized resource scheduler (e.g., an entity that schedules the use or resources of a communication network and / or network nodes across cells) may determine to cancel the aggressor's transmission when the aggressor exists alone (e.g., Cases 1 and 2 herein), but allow or enable joint transmission of the Tx beams (e.g., Case 3 herein) due to the combined low CLI power at the victim node 310. Of course, in other cases, the centralized resource scheduler may enable individual or joint transmissions based on the CLI power determined due to the transmission.

[0094] Figures 4A to 4B Illustrated are examples of diagrams 400, 450 that support different CLI management scenarios according to aspects of the present disclosure. Figure 4A In the embodiment of the present invention, the management of CLI can be within a cell between UEs acting as network nodes, where CLI occurs at the victim UE 410 due to UE-UE CLI from multiple aggressor UEs 415. The network configuration entity (NCE) (which can be part of the gNB-CU (control unit), OAM (operation administration and maintenance), UE, etc.) can identify the victim UE 410 based on the physical location information of the victim UE 410 and the neighboring UEs acting as aggressor UEs 415.

[0095] The NCE may configure one or more non-overlapping CLI measurement resources (e.g., SRS-RSRP) for the victim UE 410, on which the victim UE 410 will use one or more Rx beams to measure the CLI from the aggressor UE 415. The NCE may configure one or more non-overlapping CLI-RS signal resources for each aggressor UE 415, on which each aggressor UE 415 will use one or more Tx beams to transmit a CLI-RS (e.g., SRS).

[0096] In addition to physical location information, the NCE can also identify the victim node 410 and the aggressor node 415 based on the distance between the nodes, time-frequency resource allocation, path loss and channel state information (CSI) measurements, victim UE 410 detection of beam or radio link failure, etc.

[0097] In some cases, CLI resources can be configured as periodic, aperiodic, or semi-persistent. In addition, as described herein, CLI resources can be frequency division multiplexed (FDMxd), such as on non-overlapping PRBs, and / or time division multiplexed (TDMxd), such as on non-overlapping time symbols, time slots, subframes, etc.

[0098] Figure 4BScenario 450 is depicted in which CLI management can be intra-cell or inter-cell, coordinated by the centralized resource scheduler described herein. For inter-cell CLI management, a victim UE 410 may receive interfering signals from an aggressor node 415 in different or adjacent cells (e.g., cells supported by gNB 470 and gNB 475) managed by the centralized resource scheduler 460.

[0099] For example, when the victim UE 410 is configured to measure CLI from N≥1 aggressor UEs 415, the network configuration entity may configure K CLI measurement resources for the victim UE 410 and L CLI-RS resources for each aggressor UE 415. As shown in the following example, when K=2 N -1 and L=2 N-1 The following scenarios are shown for different combinations of N=2 and N=3:

[0100]

[0101]

[0102] Table 1

[0103] In some embodiments, the configuration message may ensure that the CLI measured by the victim UE 410 for each CLI measurement resource belongs to a unique subset of the aggressor UEs 415 . Figure 5 Illustrated is an example of a diagram 500 supporting frequency division multiplexing (FDMxd) CLI resource configuration according to aspects of the present disclosure.

[0104] In the case of N=2, 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 CLI measured by the victim UE 410 at CLI measurement resource #1 is only from UE 1, the CLI measured by the victim UE 510 at CLI measurement resource #2 is only from UE 2, and the CLI measured by the victim UE 410 at CLI measurement resource #3 is from two aggressor UEs 415. Of course, various configurations may be utilized.

[0105] For each CLI measurement resource, the victim UE 410 and each aggressor UE 415 may be configured to perform CLI measurements using one or more Tx and Rx beams, such as using a pre-configured beam sweep time pattern. Figure 6 Illustrated is an example of a diagram 600 supporting time division multiplexing (TDMxd) CLI resource configuration according to aspects of the present disclosure.

[0106] like Figure 5 In the depicted scenario, and with N=2, 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 CLI measured by the victim UE 410 at CLI measurement resource #1 is only from UE 1, the CLI measured by the victim UE 510 at CLI measurement resource #2 is only from UE 2, and the CLI measured by the victim UE 410 at CLI measurement resource #3 is from both aggressor UEs 415. Of course, various configurations may be utilized.

[0107] In some embodiments, the UE may implicitly determine which beams to use for CLI measurement, such as based on which beams the UE uses to transmit or receive other signals. For example, the victim UE 410 may implicitly determine which Rx beams to use for measuring CLI based on the beams used to receive one or more downlink signals (e.g., CSI-RS, SSB (synchronization signal block, 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), PDSCH (physical downlink shared channel) and / or PDCCH (physical downlink control channel)). Similarly, the aggressor UE 415 may implicitly determine which Tx beams to use based on the beams used to transmit one or more uplink signals (e.g., SRS, PUSCH and / or PUCCH).

[0108] In other cases, the NCE (e.g., gNB-CU or OAM) may explicitly indicate to the UE which Tx or Rx beams to use for CLI measurements.

[0109] In some embodiments, after performing the CLI measurement, the victim UE 410 may be configured to generate a report and send it to a requesting network entity (e.g., a serving gNB that sends a request message to the victim UE 410). The report may include an index and / or CLI measurement of one or more of the CLI measurement resources with the lowest and / or highest CLI-RSRP, and / or an index and / or CLI measurement of one or more of the preferred and / or restricted Tx and Rx beams and / or beams.

[0110] Reporting can be periodic, aperiodic, semi-continuous, and / or event-triggered. The serving gNB or other network entity can forward the reports to neighboring gNBs, such as via OTA (over-the-air) backhaul, 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) transmissions of one or more aggressors on shared resources.

[0111] Figure 7 An example of a diagram 700 illustrating signaling between a support node and a network configuration entity 710 according to aspects of the present disclosure is shown. At step 0, the NCE 710 identifies a victim node 410 and aggressor nodes 415 (eg, 415A to 415N).

[0112] In step 1, the NCE 710 configures CLI measurement resources and CLI RS. The NCE 710 may perform the configuration at the victim node 410 and / or the aggressor nodes 415A to 415N. In step 2, the aggressor nodes 415A to 415N perform CLI RS transmission with the victim node 410. In step 3, the victim node 410 performs CLI measurement, generates a report, and sends the report to the NCE 710 (as described herein).

[0113] As described herein, a network node may be a base station or other network entity such as a gNB serving different cells and managed by a centralized resource scheduler. Figure 8 Illustrated is an example of a diagram 800 supporting a network entity CLI management scenario according to aspects of the present disclosure.

[0114] The centralized resource scheduler 805 manages the scheduling of transmissions performed by various neighboring gNBs, such as the victim gNB 810 and multiple aggressor gNBs 815. The NCE (which can be part of the gNB-CU or the Operation and Management Administration) identifies the victim gNB and the aggressor gNB 815 based on various factors described herein. For example, the NCE can identify the nodes based on their physical location, the distance between gNBs, the node's time-frequency resource allocation, path loss and CSI measurements, the victim gNB's detection of beam or radio link failure, etc.

[0115] The NCE may configure one or more CLI measurement resources (e.g., CSI-IM) for the victim gNB 810 (on which one or more Rx beams are used to measure CLI from one or more aggressor gNBs 815), and may configure one or more CLI-RS signal resources (e.g., NZP CSI-RS) for each aggressor gNB 815 (on which one or more Tx beams are used to transmit CLI RS).

[0116] In some cases, the NCE may configure CLI resources in a periodic, aperiodic, or semi-persistent manner, and the CLI resources may be FDMxd (e.g., on non-overlapping PRBs), such as Figure 5 As shown, or can be TDMxd (e.g., on non-overlapping time symbols, time slots, subframes, etc.), as shown Figure 6 shown.

[0117] For example, when the victim gNB 810 is configured to measure CLI from N≥1 aggressor gNBs 815, the NCE may configure K CLI measurement resources for the victim gNB 810 and L CLI-RS resources for each aggressor gNB 815. N -1 and L=2 N-1 When N=2 and N=3, the different combinations are as follows:

[0118]

[0119]

[0120] Table 2

[0121] In some embodiments, the configuration message may ensure that the CLI measured by the victim gNB 810 for each CLI measurement resource belongs to a unique subset of the aggressor gNB 815. In the case of N=2, 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 described herein. Figure 5 and Figure 6 Furthermore, for each CLI measurement resource, the victim gNB 810 and each aggressor gNB 815 may be configured to perform CLI measurements using one or more Tx and Rx beams using a pre-configured beam sweep time pattern.

[0122] In some embodiments, the gNB can implicitly determine which beams to use for CLI measurement, such as based on which beams the gNB uses to transmit or receive other signals. For example, the victim gNB 810 can implicitly determine which Rx beams to use for CLI measurement based on the beams used to receive one or more uplink signals (e.g., SRS, PUSCH, and / or PUCCH). Similarly, the aggressor gNB 815 can implicitly determine which Tx beams to use based on the beams used to transmit one or more downlink signals (e.g., CSI-RS, SSB, PDSCH, and / or PDCCH).

[0123] In other cases, the NCE (e.g., gNB-CU or OAM) may explicitly indicate to the gNB the Tx or Rx beam to be used for CLI measurements.

[0124] In some embodiments, after performing the CLI measurement, the victim gNB 810 may be configured to generate a report and send the report via backhaul and / or OTA transmission to the NCE and / or the aggressor gNB 815. The report may include indices and / or CLI measurements of one or more of the CLI measurement resources with the lowest and / or highest CLI-RSRP, and indices and / or CLI measurements of one and / or more of the preferred and / or restricted Tx and Rx beams.

[0125] Reporting can be periodic, aperiodic, semi-continuous, or event-triggered. The NCE and / or aggressor gNB 815 can use the received measurement reports to select the best Tx and Rx beams and / or mute (cancel) transmissions of one or more aggressors on shared resources. The victim gNB 810 can use CLI measurements locally to determine the best Rx beam or time-frequency allocation, among other uses.

[0126] Figure 9 An example of a block diagram 900 of a device 902 that supports providing CLI management according to aspects of the present disclosure is illustrated. The device 902 can be an example of a network entity 102 as described herein. The device 902 can support wireless communications with one or more network entities 102, UEs 104, or any combination thereof. The device 902 can include components for bidirectional communication, including components for sending and receiving communications (such as a processor 904, a memory 906, a transceiver 908, and an I / O controller 910). These components can be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., a bus).

[0127] The processor 904, memory 906, transceiver 908, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of the present disclosure described herein. For example, the processor 904, memory 906, transceiver 908, or various combinations thereof, or components thereof, may support a method for performing one or more of the operations described herein.

[0128] In some implementations, the processor 904, memory 906, transceiver 908, or various combinations or components thereof may be implemented in hardware (e.g., in a communications management circuit system). 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, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured as or otherwise supports components for performing the functions described in this disclosure. In some implementations, the processor 904 and the memory 906 coupled to the processor 904 may be configured to perform one or more functions described herein (e.g., execution of instructions stored in the memory 906 by the processor 904).

[0129] For example, according to examples disclosed herein, the processor 904 can support wireless communications at the device 902. The processor 904 can be configured to or otherwise support components for: identifying a victim node and a set of aggressor nodes associated with the victim node; configuring, for the victim node, a set of non-overlapping cross-link interference (CLI) measurement resources associated with reception at the victim node; and configuring, for each aggressor node in the set of aggressor nodes, one or more non-overlapping CLI reference signal (RS) resources associated with transmissions by the set of aggressor nodes.

[0130] As another example, according to examples disclosed herein, the processor 904 may support wireless communications at the device 902. The processor 904 may be configured to or otherwise support means for: receiving a configuration from a network entity that identifies a set of non-overlapping cross-link interference (CLI) measurement resources associated with a receive beam at a network node; performing CLI measurements using the set of non-overlapping CLI measurement resources; and sending a report to the network entity that indicates the CLI measurements performed based on the set of non-overlapping CLI measurement resources.

[0131] 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, discrete gate or transistor logic components, discrete hardware components, 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, the 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., memory 906) to cause the device 902 to perform various functions of the present disclosure.

[0132] The memory 906 may include random access memory (RAM) and read-only memory (ROM). The memory 906 may store computer-readable, computer-executable code, which includes instructions that, when executed by the processor 904, cause the device 902 to perform the various functions described herein. The code may be stored in a non-transient computer-readable medium such as system memory or another type of memory. In some implementations, the code may not be directly executed by the processor 904, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, the memory 906 may also include a basic I / O system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral device components or devices.

[0133] The I / O controller 910 can manage input and output signals for the device 902. The I / O controller 910 can also manage peripheral devices that are not integrated into the device 2402. In some implementations, the I / O controller 910 can represent a physical connection or port to an external peripheral device. In some implementations, the I / O controller 910 can utilize an operating system, such as

[0134] Or other known operating systems. In some implementations, I / O controller 910 can be implemented as part of a processor such as processor M04. In some implementations, a user can interact with device 902 via I / O controller 910 or via hardware components controlled by I / O controller 910.

[0135] 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 sending or receiving multiple wireless transmissions. The transceiver 908 may communicate bidirectionally via 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 bidirectionally with another wireless transceiver. The transceiver 908 may also include a modem for modulating packets to provide the modulated packets to one or more antennas 912 for transmission, and demodulating packets received from one or more antennas 912.

[0136] Figure 10 A flowchart of a method 1000 for supporting configuring a network node to perform CLI measurements according to aspects of the present disclosure is illustrated. The operations of the method 1000 may be implemented by the apparatus described herein or components thereof. For example, the operations of the method 1000 may be implemented by reference to Figures 1 to 8The network entity 102 performs the described functions. In some implementations, the device may execute a set of instructions to control the functional elements of the device to perform the described functions. Additionally or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0137] At 1005, 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 according to the examples described herein. In some implementations, aspects of the operations of 1005 may be described with reference to Figure 1 The device is used to perform the above.

[0138] At 1010, method 1000 may include configuring a set of non-overlapping CLI measurement resources associated with reception at the victim node for the victim node. The operations of 1010 may be performed according to examples described herein. In some implementations, aspects of the operations of 1010 may be described with reference to Figure 1 The device is used to perform the above.

[0139] At 1015, method 1000 may include configuring, for each aggressor node in the set of aggressor nodes, one or more non-overlapping CLIRS resources associated with transmissions by the set of aggressor nodes. The operations of 1015 may be performed according to examples described herein. In some implementations, aspects of the operations of 1015 may be described with reference to Figure 1 The device is used to perform the above.

[0140] At 1020, method 1000 may include receiving a report in response to sending a request to the victim node, the report indicating CLI measurements based on a set of non-overlapping CLI measurement resources and non-overlapping CLIRS resources. The operations of 1020 may be performed according to examples described herein. In some implementations, aspects of the operations of 1020 may be described with reference to Figure 1 The device is used to perform the above.

[0141] Figure 11 A flowchart of a method 1100 for supporting measurement of CLI via a victim node according to aspects of the present disclosure is illustrated. The operations of the method 1100 may be implemented by the apparatus described herein or components thereof. For example, the operations of the method 1100 may be implemented by reference to Figures 1 to 8 The UE 104 (or another victim node) performs the described functions. In some implementations, the device may execute a set of instructions to control the functional elements of the device to perform the described functions. Additionally or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0142] At 1105, method 1100 may include receiving a configuration from a network entity that identifies a set of non-overlapping CLI measurement resources associated with a receive beam at a network node. The operations of 1105 may be performed according to examples described herein. In some implementations, aspects of the operations of 1105 may be described with reference to Figure 1 The device is used to perform the above.

[0143] At 1110, method 1100 may include performing CLI measurements using a set of non-overlapping CLI measurement resources. The operations of 1110 may be performed according to examples described herein. In some implementations, aspects of the operations of 1110 may be described with reference to Figure 1 The device is used to perform the above.

[0144] At 1115, method 1100 may include sending a report to a network entity indicating the CLI measurements performed based on the set of non-overlapping CLI measurement resources. The operations of 1115 may be performed according to examples described herein. In some implementations, aspects of the operations of 1115 may be described with reference to Figure 1 The device is used to perform the above.

[0145] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified, and that other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0146] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed using 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 DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0147] 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 via a computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. Features that implement the functions may also be physically located in various locations, including being distributed so that portions of the functions are implemented at different physical locations.

[0148] Computer readable medium includes non-transient computer storage medium and communication medium, and communication medium includes any medium that promotes that computer program is transferred from one place to another place.Non-transient storage medium can be any available medium that can be accessed by general-purpose or special-purpose computer.As an example and not limitation, non-transient computer readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, magnetic disk storage device or other magnetic storage device, or can be used for carrying or storing desired program code parts in the form of instruction or data structure and can be by general-purpose or special-purpose computer, or any other non-transient medium that general-purpose or special-purpose processor accesses.

[0149] Any connection may be appropriately referred to as a computer-readable medium. For example, if the software is sent from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology (such as infrared, radio, and microwave), the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology (such as infrared, radio, and microwave) is included in the definition of computer-readable medium. Disks and optical discs as used herein include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, where disks typically reproduce data magnetically, while optical discs reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0150] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items beginning with a phrase such as "at least one of" or "one or more of" or "one or both of") means an inclusive list, so 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). Furthermore, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on." Furthermore, as used herein (including in the claims), a "set" may include one or more elements.

[0151] When referring to a network entity, the terms "send," "receive," or "transmit" may refer to any part of a network entity of a RAN (e.g., base station, CU, DU, RU) that communicates with another device (e.g., directly or via one or more other network entities).

[0152] The description herein in conjunction with the accompanying drawings describes example configurations and does not represent all examples that can be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "superior to other examples." The detailed description includes specific details to facilitate understanding of the described techniques. However, these techniques can 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 examples.

[0153] The description herein is provided to enable one of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure will be readily apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but should be construed in the widest sense consistent with the principles and novel features disclosed herein.

Claims

1. A network entity, comprising: processor; as well as a memory coupled to the processor, the processor being configured to cause the network entity to: Identifying a victim node and a set of aggressor nodes associated with the victim node; configuring, for the victim node, a set of non-overlapping cross-link interference (CLI) measurement resources associated with reception at the victim node; as well as Each aggressor node in the set of aggressor nodes is configured with one or more non-overlapping CLI reference signal (RS) resources associated with transmissions by the set of aggressor nodes.

2. The network entity of claim 1 , wherein the processor is further configured to receive a report in response to sending a request to the victim node, the report indicating CLI measurements based on the set of non-overlapping CLI measurement resources and the non-overlapping CLIRS 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 MAC-CE (Media Access Control-Control Element).

5. The network entity of claim 2, wherein the report is received from the victim node via an over-the-air (OTA) connection or a backhaul connection between the victim node and the network entity.

6. The network entity of claim 2, wherein the report comprises: an index of one or more CLI measurement resources or a CLI measurement among the CLI measurement resources having the lowest or highest CLI-RSRP (reference signal received power) or CLI-RSSI (received signal strength indicator); or An index or CLI measurement of one or more of the preferred transmit or receive beams, or one or more of the restricted transmit or receive beams.

7. The network entity of claim 1, wherein the set of the victim node and the aggressor node comprises a user equipment (UE) or a network entity.

8. The network entity of claim 1, wherein the network entity is supported by an aggressor node in 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 comprises 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 comprises SRS, CD-SSB (cell-defined synchronization signal block), NCD-SSB (non-cell-defined 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 set of the victim node and the aggressor node based on one or more of factors, the factors comprising: The physical location of the set of the victim node and the aggressor node; The distance between the victim node and the set of aggressor nodes; Time-frequency resource allocation for the set of the victim node and the aggressor node; path loss and CSI measurements performed by a set of the victim node and the aggressor node; or A beam or radio link failure is detected by the victim node.

12. The network entity of claim 1, wherein each CLI measurement resource in the set of CLI measurement resources is associated with a unique subset of CLIRS resources configured at the set of aggressor nodes on the same time-frequency resources. 13 . The network entity of claim 1 , wherein the victim node identifies a set of reception beams for measuring the CLI based on reception beams used to receive 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 CLIRS 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 a CLI RS.

17. The network entity of claim 1, wherein the network entity configures the set of non-overlapping CLI measurement resources or the set of non-overlapping CLIRS 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, for the victim node, a set of non-overlapping cross-link interference (CLI) measurement resources associated with reception at the victim node; as well as Each aggressor node in the set of aggressor nodes is configured with one or more non-overlapping CLI reference signal (RS) resources associated with transmissions by the set of aggressor nodes.

19. A network node comprising: processor; as well as a memory coupled to the processor, the processor being configured to cause the network node to: receiving a configuration from a network entity, the configuration identifying a set of non-overlapping cross-link interference (CLI) measurement resources associated with receive beams at the network node; performing CLI measurements using the set of non-overlapping CLI measurement resources; as well as A report is sent to the network entity, the report indicating the CLI measurements performed based on the set of non-overlapping CLI measurement resources.

20. A processor for wireless communication, comprising: at least one controller coupled to the at least one memory and configured to cause the processor to: Identifying a victim node and a set of aggressor nodes associated with the victim node; configuring, for the victim node, a set of non-overlapping cross-link interference (CLI) measurement resources associated with reception at the victim node; as well as Each aggressor node in the set of aggressor nodes is configured with one or more non-overlapping CLI reference signal (RS) resources associated with transmissions by the set of aggressor nodes.

Images