Cross-link interference information exchange

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a network node may receive a cross-link interference (CLI) report from a user equipment (UE). The network node may send CLI information indicating a CLI associated with the UE to a second network node and based at least in part on the CLI report. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Patent Application No. 17 / 934,397, filed on September 22, 2022, entitled “CROSS-LINK INTERFERENCE INFORMATION EXCHANGE” and assigned to the assignee of this application. The disclosure of the prior application is considered a part of and incorporated by reference into this patent application. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for cross-link interference information exchange. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

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

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by: improving spectrum efficiency; reducing costs; improving services; utilizing new spectrum; and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink, CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink to better integrate with other open standards; and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0007] Some aspects described herein relate to a method of wireless communication performed by an apparatus of a first network node. The method may include receiving a cross-link interference (CLI) report from a user equipment (UE). The method may include sending CLI information indicating a CLI associated with the UE to a second network node and based at least in part on the CLI report.

[0008] Some aspects described herein relate to a method of wireless communication performed by an apparatus of a first network node. The method may include receiving CLI information indicating a CLI associated with a UE from a second network node. The method may include configuring communications with one or more other UEs based at least in part on the CLI information.

[0009] Some aspects described herein relate to a method of wireless communication performed by an apparatus of a UE. The method may include receiving, from a network node, information indicating a time window associated with measurement of at least one CLI reference signal. The method may include receiving the at least one CLI reference signal. The method may include sending, to the network node, information indicating a time difference between the time window and receipt of the at least one CLI reference signal.

[0010] Some aspects described herein relate to a network node for wireless communication. The network node may include: a memory; and one or more processors, the one or more processors coupled to the memory. The one or more processors may be configured to receive a CLI report from a UE. The one or more processors may be configured to send CLI information indicating a CLI associated with the UE to a second network node and based at least in part on the CLI report.

[0011] Some aspects described herein relate to a network node for wireless communication. The network node may include: a memory; and one or more processors, the one or more processors coupled to the memory. The one or more processors may be configured to receive CLI information indicating a CLI associated with a UE from a second network node. The one or more processors may be configured to configure communications with one or more other UEs based at least in part on the CLI information.

[0012] Some aspects described herein relate to a UE for wireless communication. The UE may include: a memory; and one or more processors, the one or more processors coupled to the memory. The one or more processors may be configured to receive information indicating a time window associated with measurement of at least one CLI reference signal from a network node. The one or more processors may be configured to receive the at least one CLI reference signal. The one or more processors may be configured to send information indicating a time difference between the time window and the reception of the at least one CLI reference signal to the network node.

[0013] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network node. The set of instructions, when executed by one or more processors of the network node, may cause the network node to receive a CLI report from a UE. The set of instructions, when executed by one or more processors of the network node, may cause the network node to send CLI information indicating a CLI associated with the UE to a second network node and based at least in part on the CLI report.

[0014] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network node. The instruction set, when executed by one or more processors of the network node, may cause the network node to receive CLI information indicating a CLI associated with a UE from a second network node. The instruction set, when executed by one or more processors of the network node, may cause the network node to configure communications with one or more other UEs based at least in part on the CLI information.

[0015] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication performed by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive information indicating a time window associated with measurement of at least one CLI reference signal from a network node. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive the at least one CLI reference signal. The set of instructions, when executed by one or more processors of the UE, may cause the UE to send information indicating a time difference between the time window and the reception of the at least one CLI reference signal to the network node.

[0016] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a CLI report from a UE. The apparatus may include means for sending CLI information indicating a CLI associated with the UE to a second network node and based at least in part on the CLI report.

[0017] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving CLI information indicating a CLI associated with a UE from a second network node. The apparatus may include means for configuring communications with one or more other UEs based at least in part on the CLI information.

[0018] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving, from a network node, information indicating a time window associated with measurement of at least one CLI reference signal. The apparatus may include means for receiving the at least one CLI reference signal. The apparatus may include means for sending, to the network node, information indicating a time difference between the time window and receipt of the at least one CLI reference signal.

[0019] Aspects collectively include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices and / or processing systems as fully described herein with reference to the drawings and description and as illustrated in the drawings and description.

[0020] The features and technical advantages of examples according to the present disclosure have been outlined quite broadly above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations of the claims.

[0021] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers). The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] In order to be able to understand the above-mentioned features of the present disclosure in detail, a more specific description briefly summarized above may be obtained by reference to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings illustrate only certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0023] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0024] Figure 2 is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network according to the present disclosure.

[0025] Figure 3 is a diagram illustrating an example decomposed base station architecture according to the present disclosure.

[0026] Figure 4 is a diagram illustrating an example of full-duplex communication in a wireless network according to the present disclosure.

[0027] FIG. 5A to FIG. 5B is a diagram illustrating an example of cross-link interference (CLI) that a UE may experience.

[0028] Figure 6 is a diagram of an example associated with CLI information exchange according to the present disclosure.

[0029] Figure 7 and Figure 8 is a diagram illustrating an example process, for example, performed by a network node, according to the present disclosure.

[0030] Fig. 9 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0031] Fig.10 and Fig.11 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0032] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be construed as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of the present disclosure will be fully conveyed to those skilled in the art. It should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the disclosure disclosed herein, whether it is independently or in combination with any other aspect of the disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such a device or method practiced using other structures, functionality, or structure and functionality in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the present invention.

[0033] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0034] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applicable to other RATs, such as 3G RAT, 4G RAT and / or RATs beyond 5G (e.g., 6G).

[0035] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. The network node 110 is a network node that communicates with the UE 120. As shown in the figure, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, which means that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, the network node 110 may be a decomposed network node (sometimes referred to as a decomposed base station), which means that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0036] In some examples, the network node 110 is or includes a network node that communicates with the UE 120 via a radio access link, such as an RU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a midhaul link or communicates with the core network via a backhaul link, such as a CU. In some examples, the network node 110 (such as an aggregated network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. The network node 110 may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a DU, a RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in wireless network 100 via various types of fronthaul, midhaul, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks) using any suitable transport network.

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

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

[0039] The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive transmissions of data from an upstream node (e.g., a network node 110 or a UE 120) and transmit transmissions of data to a downstream node (e.g., a UE 120 or a network node 110). A relay station may be a UE 120 that is capable of relaying transmissions for other UEs 120. Figure 1 In the example shown in , a network node 110d (e.g., a relay network node) may communicate with a network node 110a (e.g., a macro network node) and a UE 120d to facilitate communication between the network node 110a and the UE 120d. A network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, etc.

[0040] The wireless network 100 may be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0041] The network controller 130 may be coupled to or in communication with a set of network nodes 110 and may provide coordination and control for the network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via a wireless or wired backhaul communication link. In some aspects, the network controller 130 may be, or may include, a CU or a core network device.

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

[0043] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that may communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0044] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, air interface, etc. Frequency may be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0045] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using network node 110 as an intermediary to communicate with each other). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.

[0046] The devices of the wireless network 100 may communicate using an electromagnetic spectrum that may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that, although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the “below 6 GHz” band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0047] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125 GHz–24.25 GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and thus the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz-71 GHz), FR4 (52.6 GHz-114.25 GHz), and FR5 (114.25 GHz-300 GHz). Each of these higher frequency bands falls within the EHF band.

[0048] Considering the above examples, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0049] In some aspects, the network node 110 may include a communications manager 150. As described in more detail elsewhere herein, the communications manager 150 may receive a cross-link interference (CLI) report from the UE; and send, to a second network node and based at least in part on the CLI report, CLI information indicating a CLI associated with the UE. In some aspects, the communications manager 150 may receive, from the second network node, CLI information indicating a CLI associated with the UE; and configure communications with one or more other UEs based at least in part on the CLI information. Additionally or alternatively, the communications manager 150 may perform one or more other operations described herein.

[0050] In some aspects, UE 120 may include a communication manager 140. As described in greater detail elsewhere herein, the communication manager 140 may receive information indicating a time window associated with measurement of at least one CLI reference signal from a network node; receive at least one CLI reference signal; and send information indicating a time difference between the time window and reception of the at least one CLI reference signal to the network node. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0051] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 The examples described are different.

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

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

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

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

[0056] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or may be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0057] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and sent to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, with reference to Figures 4 to 11 ) any aspects of any of the methods described herein.

[0058] At the network node 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component (shown as DEMOD) of the modem 232), detected by the MIMO detector 236 (where applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink communication and / or uplink communication. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform operations described herein (e.g., with reference to Figures 4 to 11 ) any aspects of any of the methods described herein.

[0059] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other components of the network node 110 may perform one or more techniques associated with exchanging CLI information, as described in more detail elsewhere herein. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the Figure 7 The process 700 Figure 8 The process of 800 Fig. 9 900 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after compilation, conversion, and / or interpretation) by one or more processors of network node 110 and / or UE 120, may cause the one or more processors, UE 120, and / or network node 110 to perform or direct, for example Figure 7 The process 700 Figure 8 The process of 800 Fig. 9 The process 900 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0060] In some aspects, the network node 110 includes means for receiving a CLI report from the UE; and / or means for sending CLI information indicating a CLI associated with the UE to a second network node and based at least in part on the CLI report. Means for the network node 110 to perform operations described herein may include, for example, one or more of the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0061] In some aspects, the network node 110 includes a component for receiving CLI information indicating a CLI associated with the UE from a second network node; and / or a component for configuring communications with one or more other UEs based at least in part on the CLI information. The components for the network node 110 to perform operations described herein may include, for example, one or more of the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0062] In some aspects, the UE 120 includes means for receiving information indicating a time window associated with measurement of at least one CLI reference signal from a network node; means for receiving at least one CLI reference signal; and / or means for sending information indicating a time difference between the time window and the reception of at least one CLI reference signal to the network node. Means for the UE 120 to perform operations described herein may include, for example, one or more of the communications manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0063] Although Figure 2 The blocks in the 2000 and 2010 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0064] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 The examples described are different.

[0065] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station or network equipment can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) that perform base station functionality can be implemented as an aggregated base station (also referred to as an independent base station or a monolithic base station) or a decomposed base station. "Network entity" or "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

[0066] An aggregated base station (e.g., an aggregated network node) may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station (e.g., a decomposed network node) may be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, a CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other network nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), and the like.

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

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

[0069] Each of the units (including CU 310, DU 330, RU 340) and the near-RT RIC 325, non-RT RIC 315, and SMO framework 305 may include or be coupled to one or more interfaces, the one or more interfaces being configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to one or more communication interfaces of the corresponding unit may be configured to communicate with one or more of the other units via a transmission medium. In some examples, each of the units may include a wired interface and a wireless interface, the wired interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, the wireless interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, or both.

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

[0071] Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a MAC layer, and one or more high physical (PHY) layers, at least in part, according to a functional partition such as that defined by 3GPP. In some aspects, one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc. In some aspects, the DU 330 may further host one or more low PHY layers, such as one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming or physical random access channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

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

[0073] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RTRIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of the one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

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

[0075] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to regulate RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0076] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The examples described are different.

[0077] Figure 4400, 405, 410 and 415 are diagrams illustrating examples of full-duplex communication in a wireless network according to the present disclosure. "Full-duplex communication" in a wireless network refers to simultaneous bidirectional communication between devices in the wireless network. For example, a UE or network node operating in full-duplex mode may send uplink communication and receive downlink communication at the same time (e.g., in the same time slot or the same symbol). "Half-duplex communication" in a wireless network refers to unidirectional communication (e.g., only downlink communication or only uplink communication) between devices at a given time (e.g., in a given time slot or a given symbol). Half-duplex communication may be performed, for example, using frequency division duplex (FDD) and / or time division duplex (TDD). For example, in FDD mode, a UE may simultaneously (e.g., in the same frame, time slot and / or symbol) use a first frequency region (or channel) for uplink communication and a second frequency region (or channel) for downlink communication. In TDD mode, the UE may send uplink communications and receive downlink communications in a single frequency region but at different time intervals (eg, frames, time slots, and / or symbols).

[0078] like Figure 4 As shown, examples 400 and 405 illustrate examples of in-band full-duplex (IBFD) communications. In IBFD, a UE may send uplink communications to a base station and receive downlink communications from a base station on the same time and frequency resources. As shown in example 400, in a first example of IBFD, the time resources and frequency resources used for uplink communications may completely overlap with the time resources and frequency resources used for downlink communications. As shown in example 405, in a second example of IBFD, the time resources and frequency resources used for uplink communications may partially overlap with the time resources and frequency resources used for downlink communications.

[0079] like Figure 4 As further shown, examples 410 and 415 illustrate examples of sub-band full-duplex (SBFD) communications, which may also be referred to as "sub-band frequency division duplex (SBFDD)" or "flexible duplex." In SBFD, a UE may send uplink communications to a base station and receive downlink communications from a base station at the same time but on different frequency resources. For example, the different frequency resources may be sub-bands of a frequency band such as a time division duplex band. In this case, the frequency resources used for downlink communications may be separated from the frequency resources used for uplink communications in the frequency domain by one or more guard bands.

[0080] As indicated above, Figure 4 are provided as examples. Other examples can be found in relation to Figure 4 The examples described are different.

[0081] FIG. 5A to FIG. 5B5 are diagrams illustrating examples 500, 510, 520 of cross-link interference (CLI) that may be experienced by a UE. For example, a UE may experience interference that causes reception performance degradation in various scenarios. For example, a first UE (e.g., UE 120-1) receiving one or more downlink transmissions from a network node (e.g., network node 110-1) may experience inter-cell CLI caused by downlink transmissions from a nearby network node (e.g., network node 110-2) in a different cell, intra-cell CLI caused by uplink transmissions from other UEs (e.g., UE 120-2) in the same cell (e.g., when the network node communicating with the other UEs is operating in IBFD mode or SBFD mode), and / or inter-cell CLI caused by uplink transmissions from other UEs in neighboring cells. For example, when transmissions from nearby network nodes and / or nearby UEs are received at the first UE, CLI may be experienced at the first UE, which may interfere with reception of desired downlink transmissions at the first UE. In addition, in a case where the first UE is configured to operate in full-duplex mode (e.g., supporting concurrent or simultaneous uplink transmission and downlink reception), the first UE may experience self-interference due to uplink transmissions leaking into the receive port and / or objects in the environment surrounding the first UE reflecting the uplink transmissions back to the receive port.

[0082] For example, Figure 5A As shown, example 500 includes a first UE (e.g., UE 120-1) operating in half-duplex mode and communicating with a first network node (e.g., network node 110-1) operating in IBFD or SBFD mode. For example, as shown in example 500, the first network node may operate in IBFD or SBFD mode to support concurrent downlink transmissions to the first UE and uplink receptions from a second UE (e.g., UE 120-2). In example 500, a first interference source at the first UE may be an inter-cell CLI 502 caused by a downlink transmission performed by a second network node (e.g., network node 110-2) in a nearby or neighboring cell. Additionally, as shown at 504, a second interference source at the first UE may be an intra-cell CLI caused by an uplink transmission from the second UE.

[0083] like Figure 5AAs further shown, in example 510, a first UE (e.g., UE 120-1) may operate in half-duplex mode and communicate with a first network node (e.g., network node 110-1) operating in half-duplex mode. However, in this case, a second UE (e.g., UE 120-2) may communicate with a second network node (e.g., network node 110-2) in a neighboring cell. In some cases, uplink transmissions in one cell may occur during the same transmission time interval as downlink transmissions in another cell, resulting in inter-cell CLI. For example, as shown at 512, a first UE may receive a downlink transmission from a first network node, and a second UE may concurrently send an uplink transmission to the second network node, which may result in CLI interfering with downlink reception at the first UE.

[0084] Additionally or alternatively, such as Figure 5B As shown, in example 520, a first UE (e.g., UE 120-1) may experience both intra-cell CLI 504 and inter-cell CLI 512 when communicating with a first network node (e.g., network node 110-1). For example, a second UE (e.g., UE 120-2) may cause inter-cell CLI 512 by sending uplink communications to the second network node (e.g., network node 110-2) concurrently with the first UE receiving downlink communications from the first network node. Additionally, a third UE (e.g., UE 120-3) may cause intra-cell CLI 504 by sending uplink communications to the first network node concurrently with the first UE receiving downlink communications from the first network node.

[0085] As indicated above, FIG. 5A to FIG. 5B are provided as examples. Other examples can be found in the FIG. 5A to FIG. 5B Different than described.

[0086] As described above, there are various scenarios in which a UE may experience inter-cell CLI, intra-cell CLI, self-interference, and / or other interference that may degrade downlink reception performance at the UE. Therefore, the network node may configure the UE to obtain measurements related to the interference experienced at the UE and report these measurements to the network node (e.g., to enable the network node to select appropriate downlink beams, resource allocations, and / or other communication parameters to mitigate the interference experienced at the UE). For example, the network node may configure static, semi-static, semi-persistent, or periodic measurement resources for the UE (e.g., using radio resource control (RRC) messages), and the UE may report interference measurements to the network node in a CLI report (e.g., via L3 signaling, uplink medium access control (MAC) control element (MAC-CE), physical uplink control channel (PUCCH), or physical uplink shared channel (PUSCH), etc.). In some aspects, these interference measurements or CLI measurements may include RSRP measurements and / or RSSI measurements performed using a sounding reference signal (SRS) resource configuration parameter (e.g., SRS-ResourceConfigCLI-r16) for measuring RSRP associated with a periodic SRS resource, or an RSSI resource configuration parameter (e.g., RSSI-ResourceConfigCLI-r16) for configuring the UE to measure RSSI based on energy in a given bandwidth. Additionally or alternatively, the UE may be configured to measure a demodulation reference signal (DMRS) or other signal when performing a CLI measurement.

[0087] The CLI report may enable the network node to adjust communication parameters with the UE to resolve CLI (e.g., by selecting downlink resource allocations and other communication parameters including downlink beams to mitigate CLI). This may include, for example, adjusting communication parameters of the downlink UE experiencing CLI and / or adjusting communication parameters of other UEs causing CLI within the cell. However, in the event that a UE experiences inter-cell CLI (which may be caused by another network node and / or a UE communicating with another network node), the network node may not be able to adjust the communication parameters of the device causing the inter-cell CLI. This limits the network node to communication parameter adjustments within its own cell, and may limit the CLI mitigation that can be provided by the network node because it limits the options for communication parameter adjustments to devices within the network node's cell. This may result in more frequent CLI measurements, increased reporting overhead, and / or increased network and processing resource usage because the UE and network node communicate with each other to adjust communication parameters in an effort to mitigate CLI.

[0088] Some techniques and apparatus described herein enable CLI information exchange between network nodes, which may enable a network node to communicate CLI information to another network node. For example, a first network node may receive a CLI report from a first UE indicating the CLI of a second UE communicating with a second network node. The first network node may send (e.g., via a backhaul or over-the-air (OTA) interface) CLI information indicating the CLI to the second network node, and the second network node may configure communications with the second UE based at least in part on the CLI information. Thus, the exchange of CLI information between network nodes enables the network nodes to work together, thereby providing additional options for adjusting communication parameters to mitigate inter-cell CLI. In this manner, CLI information may be used by multiple network nodes to adjust communication parameters of UEs in different cells to mitigate CLI between UEs operating in different cells. This may reduce the frequency of CLI measurements and reports, which may reduce the overhead caused by CLI reports, and save network and / or processing resources that might otherwise be consumed by more limited CLI communication adjustment capabilities.

[0089] Figure 6 is a diagram of an example 600 associated with CLI information exchange according to the present disclosure. Figure 6 As shown, multiple network nodes may communicate with multiple UEs. For example, a first network node associated with a first cell (e.g., network node 110-1) may communicate with a first UE (e.g., UE 120-1), and a second network node associated with a second cell (e.g., network node 110-2) may communicate with a second UE (e.g., UE 120-2). Each of these network nodes may include one or more base stations 110, one or more CUs, one or more DUs, one or more RUs, one or more core network nodes, one or more network servers, one or more application servers and / or one or more access and mobility management functions (AMFs), etc. In some aspects, the first UE and the first network node may be part of a wireless network (e.g., wireless network 100). The first UE and the first network node may be in a Figure 6 The illustrated operations are preceded by establishing a wireless connection.In some aspects, the first network node and the second network node may be associated with the same operator or different operators.

[0090] As indicated by reference numeral 605, the first network node may send CLI report configuration information, and the first UE may receive the CLI report configuration information. In some aspects, the first UE may receive the configuration information via one or more of radio resource control (RRC) signaling, one or more medium access control (MAC) control elements (CEs), and / or downlink control information (DCI), etc. In some aspects, the configuration information may include: an indication of one or more configuration parameters for selection by the UE (e.g., known to the UE and / or previously indicated by the first network node or another network device), and / or explicit configuration information for the UE to configure the UE, etc.

[0091] In some aspects, the configuration information may indicate that the UE is to measure the CLI associated with the set of communications resources in the manner described herein (eg, using configured time, frequency, and / or spatial resources).

[0092] In some aspects, the first network node may send information indicating a time window associated with measurement of at least one CLI reference signal separately from or together with the CLI reporting configuration information, and the UE may receive the information separately from or together with the CLI reporting configuration information. For example, the first network node may signal a specific time window in which a reference signal (e.g., SRS) is expected to arrive at the first UE. In this case, the UE may estimate the arrival of the reference signal and configure itself for monitoring within the time window.

[0093] The UE may configure itself based at least in part on the configuration information.In some aspects, the UE may be configured to perform one or more operations described herein based at least in part on the CLI report configuration information.

[0094] As indicated by reference numeral 610, the first UE may measure the CLI. For example, the first UE may measure the CLI based at least in part on the CLI reporting configuration information, as described herein. As shown, while the first UE is measuring the CLI, the second UE may send an uplink communication to the second network node. In this case, the first UE may determine a measure of the CLI based at least in part on the uplink communication. For example, as described herein, the CLI may be based at least in part on an RSRP measurement and / or an RSSI measurement of a reference signal (such as an SRS or DMRS, etc.) included in the uplink communication from the second UE. In this example, the measured CLI may be an inter-UE CLI.

[0095] In some aspects, based at least in part on the first UE's measurement of the reference signal, the first UE may determine a time difference between a time window (e.g., provided by the first network node) and reception of the reference signal. For example, the first network node may have identified the time window (e.g., in symbol form), and the first UE may determine a timing difference between arrival of the reference signal and the time window, which may indicate a downlink signal arrival time. When provided to the first network node as described herein, the difference between the timing window and arrival of the reference signal may facilitate alignment of communication timing between the first network node and the first UE (e.g., to reduce CLI).

[0096] In some aspects, the first UE may determine a power backoff recommendation based at least in part on a reference signal. For example, in a case where the second UE is communicating using a particular CLI resource, the first UE may determine that a power backoff for the second UE reduces the CLI below a CLI threshold such that the first UE may then receive downlink communications from the first network node while the second UE transmits after the power backoff. In some aspects, the power backoff recommendation may be based at least in part on an MCS or a transport block (TB) size associated with downlink communications from the first network node to the first UE. For example, a higher MCS and / or a higher TB size may indicate a higher quality link between the first UE and the first network node, which may indicate that a lower power backoff will be sufficient to reduce the CLI below the CLI threshold; conversely, a lower MCS and / or a lower TB size may indicate a lower quality link between the first UE and the first network node, which may indicate that a higher power backoff would be preferred to reduce the CLI below the CLI threshold.

[0097] As indicated by reference numeral 615, the first UE may send a CLI report and the first network node may receive the CLI report. For example, the CLI report may be sent as described herein and may include CLI information indicating the CLI experienced by the first UE. In some aspects, the first UE may provide (included in the CLI report or separate from the CLI report) information regarding a power backoff recommendation or a timing difference, as described herein.

[0098] For example, the first UE may provide information indicating a time difference between arrival of a downlink communication from the first network node and arrival of a reference signal from the second UE.As another example, the first UE may provide information indicating a power backoff recommendation for the second UE.

[0099] In some aspects, the time difference, power backoff recommendation, and / or other information associated with the CLI report may be used by the first network node to schedule communications with the first UE. For example, in the event that the first network node determines, based at least in part on the CLI report and / or other information described herein, that channel conditions measured by the first UE are unlikely to be resolved by reconfiguring and / or rescheduling communications with other UEs, the first network node may reconfigure and / or reschedule communications with the first UE. In some aspects, reconfiguration and / or rescheduling of communications with the first UE may be performed in addition to or in lieu of exchanging CLI information to reconfigure / reschedule communications with one or more other UEs.

[0100] As indicated by reference numeral 620, the first network node may determine CLI information. For example, based at least in part on a CLI report received from the first UE (e.g., including CLI-related information such as power backoff recommendation and / or time difference), the first network node may determine CLI information to send to the second network node.

[0101] In some aspects, the first network node may determine a CLI resource identifier associated with a minimum CLI value based at least in part on the CLI report. For example, the CLI report may indicate a CLI resource identifier (e.g., a CLI resource identifier, a reference signal identifier, a beam identifier, and / or a time and frequency resource) at which the first UE experiences the minimum CLI. The CLI resource identifier associated with the minimum CLI may be included in the CLI information to enable the second network node to avoid using the CLI resource identifier for communicating with other UEs, which may mitigate the use of the CLI resource identifier for communicating between the first network node and the first UE. In some aspects, the CLI information may indicate a number of CLI resources (e.g., beams, reference signal identifiers) associated with the CLI measurement of the first UE. For example, the number of CLI resources may be based at least in part on a first number of transmit beams associated with the first UE and a second number of receive beams associated with the second UE associated with the CLI. Additionally or alternatively, the CLI information may include multiple reference signal identifiers. Providing CLI information including the number of CLI resources, beams, and / or reference signal identifiers may enable the second network node to cause one or more UEs associated with the beams and / or reference signals (e.g., which may include the second UE) to perform CLI reporting in an effort to avoid CLI of one or more other UEs as well as the first UE. For example, the CLI information may indicate 5 CLI resources measured by the first UE, and the second network node may configure the second UE to measure 4 CLI resources for each of the 5 CLI resources of the first UE, resulting in 20 (e.g., 5×4=20) CLI resources being measured by the second UE (e.g., beam scanning of the CLI resources by the second UE).

[0102] As indicated by reference numeral 625, the first network node may send CLI information and the second network node may receive the CLI information. For example, the CLI information may be sent via a backhaul interface or an OTA interface between the network nodes. In some aspects, a separate OTA or backhaul interface (e.g., an inter-network node interface, such as an inter-DU interface or an inter-CU interface, etc.) may be used to exchange CLI information, which may include reporting of a layer 1 or layer 2 inter-UE CLI configuration, as described herein.

[0103] In some aspects, the first network node may send information identifying a CLI resource identifier.For example, the CLI resource identifier may identify at least one reference signal identifier and / or a beam identifier, as described herein.

[0104] In some aspects, the first network node may send information indicating a time difference between a scheduled downlink communication arriving at the first UE and a CLI reference signal arrival time. In some aspects, the first network node may send information indicating a power backoff recommendation. For example, the first UE may have provided a power backoff recommendation to the first network node, as described herein. In some aspects, the first network node may determine a power backoff recommendation in a manner similar to that of the first UE (e.g., based on a CLI report), as described herein.

[0105] As shown by reference numeral 630, the second network node configures communications with the second UE based at least in part on the CLI information. For example, the second network node may send and the second UE may receive communication parameters that cause the second UE to use different parameters to communicate with the second network node in an effort to avoid causing CLI for downlink communications to the first UE. Changes to the communication parameters may include, for example, changing transmit power, time, frequency, and / or spatial resources used for communications between the second network node and the second UE.

[0106] In some aspects, the second network node may configure communications with the second UE based at least in part on a CLI resource identifier associated with the CLI information (e.g., included in the CLI information or sent separately from the CLI information). For example, the CLI resource identifier may indicate one or more reference signal identifiers and / or beam identifiers associated with the CLI experienced by the first UE. In some aspects, the CLI information may indicate a number of beams associated with the UE's CLI measurements. In some aspects, the second network node may send CLI configuration information to the second UE to cause the UE to perform CLI measurements associated with the number of beams indicated in the CLI information received from the first network node. In this manner, the second network node may trigger CLI reporting for one or more UEs, which may further facilitate selection of communication resources to mitigate CLI.

[0107] In some aspects, the second network node may configure communications with the second UE based at least in part on downlink parameters. For example, the downlink parameters may be based at least in part on an MCS or TB size associated with communications between the first UE and the first network node. As described herein, the MCS and TB size may indicate the quality of the link between the first network node and the first UE, which may enable the second network node to configure communication parameters with the second UE differently. For example, if the quality of the link between the first network node and the first UE is relatively high, the second network node may make relatively small changes to the communication parameters of the second UE. If the quality of the link between the first network node and the first UE is relatively low, the second network node may make relatively large changes to the communication parameters of the second UE.

[0108] In some aspects, the second network node may receive, from the first network node, information indicating, for the first UE, a time difference between reception of a downlink communication sent to the UE and reception of a CLI reference signal by the UE. As described herein, the second network node may use the time difference to schedule communications with the second UE to mitigate CLI experienced by the first UE. In some aspects, the second network node may receive a power backoff recommendation for the second UE. As described herein, the second network node may use the power backoff recommendation to configure the second UE to use less power for transmission on resources indicated by the power backoff recommendation.

[0109] In some aspects, the first UE, the first network node, the second network node, and the second UE may continue to exchange CLI information in order to determine communication parameters that mitigate the CLI experienced by the UE. For example, the second network node and the second UE may perform operations similar to those described as performed by the first UE and the first network node, resulting in a two-way CLI information exchange that enables the network node to determine a resource configuration that mitigates the CLI of the corresponding UE. In addition, the network node may perform similar operations with other UEs communicating with the network node, and may exchange information with other network nodes associated with the UE that contributes to the CLI of the UE of the corresponding network node.

[0110] As shown in example 600, the exchange of CLI information between network nodes enables the network nodes to work together and provide options for adjusting communication parameters to mitigate inter-cell CLI. In this way, CLI information can be used by multiple network nodes to adjust communication parameters of UEs in different cells to mitigate CLI between UEs operating in different cells. This can reduce the frequency of CLI measurements and reporting, which can reduce the overhead caused by CLI reporting, and save network and / or processing resources that might otherwise be consumed by more limited CLI communication adjustment capabilities.

[0111] As indicated above, Figure 6are provided as examples. Other examples can be found in relation to Figure 6 The examples described are different. For example, although Figure 6 Only two UEs are depicted in the figure, but any number of other UEs may communicate with the first network node and / or the second network node and may result in additional CLI (intra-cell and inter-cell) for the first UE. In some aspects, other communications (such as sidelink communications) may also result in CLI for the first UE, which may be indicated in the CLI report. In the case where the sidelink communications are configured by the network node, the network node may reconfigure the sidelink communications parameters in a manner similar to the reconfiguration of uplink communications described herein.

[0112] Although various transmissions of different types of CLI-related information (e.g., CLI reports, power backoff recommendations, and / or time differences, etc.) are described herein, CLI-related information may be exchanged between a network node and a UE in one or more communications. For example, a first UE may communicate all CLI-related information to a first network node via a CLI report. As another example, a first UE may communicate different CLI-related information to a first network node, respectively (e.g., in separate communications for CLI reports, power backoff recommendations, and / or time differences, etc.). Similarly, CLI information communicated between network nodes may be included in one communication or in multiple separate communications.

[0113] Figure 7 is a diagram illustrating an example process 700 performed, for example, by a network node in accordance with the present disclosure. Example process 700 is an example in which a network node (eg, network node 110) performs operations associated with CLI information exchange.

[0114] like Figure 7 As shown, in some aspects, process 700 may include receiving a CLI report from a UE (block 710). For example, a network node (e.g., using Fig.10 The communications manager 150 and / or receiving component 1002 depicted in FIG. 1004 may receive a CLI report from a UE, as described above.

[0115] like Figure 7 As further shown, in some aspects, process 700 may include sending CLI information indicating a CLI associated with the UE to a second network node and based at least in part on the CLI report (block 720). Fig.10 The communications manager 150 and / or sending component 1004 depicted in FIG. 1 may send CLI information indicating a CLI associated with the UE to the second network node and based at least in part on the CLI report, as described above.

[0116] Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0117] In a first aspect, sending the CLI information includes sending the CLI information via a backhaul interface with the second network node.

[0118] In a second aspect, alone or in combination with the first aspect, sending the CLI information comprises sending the CLI information via an air interface with the second network node.

[0119] In a third aspect, alone or in combination with one or more of the first and second aspects, the first network node is associated with the first CU and the second network node is associated with the second CU.

[0120] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the first network node is a first DU and the second network node is a second DU.

[0121] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, process 700 includes determining a CLI resource identifier associated with a minimum CLI value based at least in part on the CLI report; and sending information identifying the CLI resource identifier to a second network node.

[0122] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the CLI resource identifier is associated with at least one of a reference signal identifier or a beam identifier.

[0123] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the CLI information indicates a number of beams associated with the CLI measurement of the UE.

[0124] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, process 700 includes: sending information indicating a time window associated with measurement of at least one CLI reference signal to a UE; and receiving information indicating a time difference between arrival of a downlink communication from a first network node and arrival of at least one CLI reference signal from the UE.

[0125] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, process 700 includes scheduling communications with the UE based at least in part on information indicating the time difference.

[0126] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, process 700 includes sending information indicating the time difference to the second network node.

[0127] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, process 700 includes: receiving a power backoff recommendation for another UE associated with a second network node from a UE; and sending information indicating the power backoff recommendation to the second network node.

[0128] although Figure 7 An example block diagram of process 700 is shown, but in some aspects, process 700 may include Figure 7 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 700 may be performed in parallel.

[0129] Figure 8 is a diagram illustrating an example process 800 performed, for example, by a network node in accordance with the present disclosure. The example process 800 is an example in which a network node (eg, network node 110) performs operations associated with CLI information exchange.

[0130] like Figure 8 As shown, in some aspects, process 800 may include receiving CLI information indicating a CLI associated with the UE from a second network node (block 810). For example, the network node (e.g., using Fig.10 The communications manager 150 and / or receiving component 1002 depicted in FIG. 1004 may receive CLI information indicating a CLI associated with the UE from a second network node, as described above.

[0131] like Figure 8 As further shown, in some aspects, process 800 may include configuring communications with one or more other UEs based at least in part on the CLI information (block 820). Fig.10 The communications manager 150 and / or configuration component 1010 depicted in FIG. 10A may configure communications with one or more other UEs based at least in part on the CLI information, as described above.

[0132] Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0133] In a first aspect, receiving CLI information includes receiving CLI information via a backhaul interface with a second network node.

[0134] In a second aspect, alone or in combination with the first aspect, receiving CLI information comprises receiving CLI information via an air interface with the second network node.

[0135] In a third aspect, alone or in combination with one or more of the first and second aspects, the first network node is associated with the first CU and the second network node is associated with the second CU.

[0136] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the first network node is a first DU and the second network node is a second DU.

[0137] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, process 800 includes receiving information identifying a CLI resource identifier from a second network node, and configuring communications includes configuring communications based at least in part on the CLI resource identifier.

[0138] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the CLI resource identifier is associated with at least one of a reference signal identifier or a beam identifier.

[0139] In a seventh aspect, either alone or in combination with one or more of aspects 1 to 6, the CLI information indicates the number of beams associated with the CLI measurement of the UE, and process 800 includes sending CLI configuration information to another UE among one or more other UEs indicating that the other UE will perform CLI measurements associated with the number of beams associated with the UE.

[0140] In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, process 800 includes receiving, from a second network node, information for a UE indicating a time difference between reception of a downlink communication sent to the UE and reception of a CLI reference signal by the UE.

[0141] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, process 800 includes scheduling communications with another UE of one or more other UEs based at least in part on information indicating a time difference.

[0142] In a tenth aspect, either alone or in combination with one or more of the first to ninth aspects, process 800 includes: receiving a power backoff recommendation for another UE among one or more other UEs from a second network node; and configuring communication with the other UE based at least in part on the power backoff recommendation.

[0143] In an eleventh aspect, either alone or in combination with one or more of aspects one to ten, configuring communications comprises configuring communications based at least in part on one or more downlink parameters, the one or more downlink parameters comprising at least one of: a modulation and coding scheme, or a transport block size.

[0144] although Figure 8 An example block diagram of process 800 is shown, but in some aspects, process 800 may include Figure 8 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 800 may be performed in parallel.

[0145] Fig. 9 9 is a diagram illustrating an example process 900 performed, for example, by a UE in accordance with the present disclosure. Example process 900 is an example in which a UE (eg, UE 120) performs operations associated with CLI information exchange.

[0146] like Fig. 9 As shown, in some aspects, process 900 may include receiving information from a network node indicating a time window associated with measurement of at least one CLI reference signal (block 910). Fig.11 The communications manager 140 and / or receiving component 1102 depicted in FIG. 100 may receive information from a network node indicating a time window associated with measurement of at least one CLI reference signal, as described above.

[0147] like Fig. 9 As further shown, in some aspects, process 900 may include receiving at least one CLI reference signal (block 920). For example, a UE (e.g., using Fig.11 The communications manager 140 and / or receiving component 1102 depicted in FIG. 10A may receive at least one CLI reference signal as described herein.

[0148] like Fig. 9 As further shown, in some aspects, process 900 may include sending information indicating a time difference between a time window and reception of at least one CLI reference signal to a network node (block 930). Fig.11 The communication manager 140 and / or the sending component 1104 depicted in FIG. 1 may send information indicating a time difference between the time window and the receipt of at least one CLI reference signal to the network node, as described above.

[0149] Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0150] In a first aspect, process 900 includes sending, to a network node, a power backoff recommendation for another UE associated with another network node.

[0151] In a second aspect, alone or in combination with the first aspect, process 900 includes determining a power backoff recommendation based at least in part on at least one CLI reference signal.

[0152] In a third aspect, alone or in combination with one or more of the first and second aspects, the power backoff recommendation is based at least in part on: a modulation and coding scheme, or a transport block size.

[0153] although Fig. 9 An example block diagram of process 900 is shown, but in some aspects, process 900 may include Fig. 9 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 900 may be performed in parallel.

[0154] Fig.10 1 is a diagram of an example device 1000 for wireless communication according to the present disclosure. Device 1000 may be a network node, or a network node may include device 1000. In some aspects, device 1000 includes a receiving component 1002 and a sending component 1004, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 1000 may communicate with another device 1006 (such as a UE, a base station, or another wireless communication device) using receiving component 1002 and sending component 1004. As further shown, device 1000 may include a communication manager 150. Communication manager 150 may include one or more of determining component 1008 or configuring component 1010, etc.

[0155] In some aspects, the apparatus 1000 may be configured to perform the Figures 4 to 6 Additionally or alternatively, the apparatus 1000 may be configured to perform one or more processes described herein, such as Figure 7 The process of 700 Figure 8 In some aspects, Fig.10 The device 1000 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig.10 One or more of the components shown may be combined with Figure 2Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0156] The receiving component 1002 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1006. The receiving component 1002 may provide the received communications to one or more other components of the device 1000. In some aspects, the receiving component 1002 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to the one or more other components of the device 1000. In some aspects, the receiving component 1002 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of the described network nodes.

[0157] The transmitting component 1004 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1006. In some aspects, one or more other components of the device 1000 may generate communications and may provide the generated communications to the transmitting component 1004 for transmission to the device 1006. In some aspects, the transmitting component 1004 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1006. In some aspects, the transmitting component 1004 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described network nodes. In some aspects, the transmit component 1004 can be co-located with the receive component 1002 in a transceiver.

[0158] Receiving component 1002 can receive a CLI report from the UE.Sending component 1004 can send, to a second network node and based at least in part on the CLI report, CLI information indicative of a CLI associated with the UE.

[0159] Determining component 1008 can determine a CLI resource identifier associated with a minimum CLI value based at least in part on the CLI report.

[0160] Sending component 1004 can send information identifying the CLI resource identifier to the second network node.

[0161] Transmitting component 1004 can transmit information indicating a time window associated with measurement of at least one CLI reference signal to the UE.

[0162] Receiving component 1002 may receive, from a UE, information indicating a time difference between arrival of a downlink communication from a first network node and arrival of at least one CLI reference signal.

[0163] Transmitting component 1004 can transmit information indicative of the time difference to the second network node.

[0164] Receiving component 1002 can receive, from a UE, a power backoff recommendation for another UE associated with a second network node.

[0165] Transmitting component 1004 can transmit information indicating a power backoff recommendation to the second network node.

[0166] Receiving component 1002 can receive CLI information from a second network node indicating a CLI associated with the UE.Configuring component 1010 can configure communications with one or more other UEs based at least in part on the CLI information.

[0167] Receiving component 1002 can receive information identifying a CLI resource identifier from a second network node.

[0168] Receiving component 1002 may receive, from the second network node, information for the UE indicating a time difference between reception of a downlink communication sent to the UE and reception of a CLI reference signal by the UE.

[0169] Receiving component 1002 can receive, from a second network node, a power backoff recommendation for another UE of the one or more other UEs.

[0170] Configuration component 1010 can configure communications with another UE based at least in part on the power backoff recommendation.

[0171] Fig.10 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.10 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.10 Two or more components shown may be implemented in a single component, or Fig.10 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.10 The illustrated set of component(s) may be described as being executable by Fig.10 Another collection of components shown performs one or more functions.

[0172] Fig.111 is a diagram of an example device 1100 for wireless communication according to the present disclosure. Device 1100 may be a UE, or a UE may include device 1100. In some aspects, device 1100 includes a receiving component 1102 and a sending component 1104, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 1100 may communicate with another device 1106 (such as a UE, a base station, or another wireless communication device) using receiving component 1102 and sending component 1104. As further shown, device 1100 may include a communication manager 140. Communication manager 140 may include a determination component 1108, etc.

[0173] In some aspects, the apparatus 1100 may be configured to perform the Figures 4 to 6 Additionally or alternatively, the apparatus 1100 may be configured to perform one or more processes described herein, such as Fig. 9 The process 900. In some aspects, Fig.11 The device 1100 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig.11 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0174] The receiving component 1102 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1106. The receiving component 1102 may provide the received communications to one or more other components of the device 1100. In some aspects, the receiving component 1102 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to the one or more other components of the device 1100. In some aspects, the receiving component 1102 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described UE.

[0175] The transmitting component 1104 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1106. In some aspects, one or more other components of the device 1100 may generate communications and may provide the generated communications to the transmitting component 1104 for transmission to the device 1106. In some aspects, the transmitting component 1104 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1106. In some aspects, the transmitting component 1104 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the transmit component 1104 can be co-located with the receive component 1102 in a transceiver.

[0176] Receiving component 1102 can receive information indicating a time window associated with measurement of at least one CLI reference signal from a network node. Receiving component 1102 can receive at least one CLI reference signal. Sending component 1104 can send information indicating a time difference between the time window and reception of at least one CLI reference signal to the network node.

[0177] Transmitting component 1104 can transmit, to the network node, a power backoff recommendation for another UE associated with another network node.

[0178] Determining component 1108 can determine a power backoff recommendation based at least in part on at least one CLI reference signal.

[0179] Fig.11 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.11 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.11 Two or more components shown may be implemented in a single component, or Fig.11 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.11 The illustrated set of component(s) may be described as being executable by Fig.11 Another collection of components shown performs one or more functions.

[0180] The following provides an overview of some aspects of the disclosure:

[0181] Aspect 1: A method of wireless communication performed by an apparatus of a first network node, the method comprising: receiving a CLI report from a UE; and sending CLI information indicating a CLI associated with the UE to a second network node and based at least in part on the CLI report.

[0182] Aspect 2: The method according to aspect 1, wherein sending the CLI information comprises: sending the CLI information via a backhaul interface with the second network node.

[0183] Aspect 3: The method according to any one of aspects 1 to 2, wherein sending the CLI information comprises: sending the CLI information via an air interface with the second network node.

[0184] Aspect 4: The method according to any one of aspects 1 to 3, wherein the first network node is associated with a first CU and the second network node is associated with a second CU.

[0185] Aspect 5: The method according to any one of aspects 1 to 4, wherein the first network node is a first DU and the second network node is a second DU.

[0186] Aspect 6: According to any one of aspects 1 to 5, the method also includes: determining a CLI resource identifier associated with a CLI value based at least in part on the CLI report; and sending information identifying the CLI resource identifier to the second network node.

[0187] Aspect 7: The method according to aspect 6, wherein determining the CLI resource identifier includes: determining the CLI resource identifier based at least in part on the CLI value being a minimum CLI value among CLI values ​​indicated in the CLI report.

[0188] Aspect 8: The method according to aspect 6, wherein the CLI resource identifier is associated with at least one of a reference signal identifier or a beam identifier.

[0189] Aspect 9: A method according to any one of Aspects 1 to 8, wherein the CLI information indicates a number of CLI resources associated with the CLI measurement of the UE, and wherein the number of CLI resources is at least partially based on a first number of transmit beams associated with the UE and a second number of receive beams associated with a second UE associated with the CLI.

[0190] Aspect 10: According to the method described in any one of Aspects 1 to 9, the method further includes: sending information indicating a time window associated with measurement of at least one CLI reference signal to the UE; and receiving information indicating a time difference between the arrival of a downlink communication from the first network node and the arrival of the at least one CLI reference signal from the UE.

[0191] Aspect 11: The method according to aspect 10, the method further comprising: scheduling communication with the UE based at least in part on the information indicating the time difference.

[0192] Aspect 12: The method according to aspect 10, further comprising: sending the information indicating the time difference to the second network node.

[0193] Aspect 13: According to any one of aspects 1 to 12, the method further includes: receiving a power backoff recommendation for another UE associated with the second network node from the UE; and sending information indicating the power backoff recommendation to the second network node.

[0194] Aspect 14: The method according to any one of aspects 1 to 13, wherein the CLI information includes at least one CLI reference signal measurement resource configuration for at least one UE including the UE.

[0195] Aspect 15: A method of wireless communication performed by an apparatus of a first network node, the method comprising: receiving CLI information indicating a CLI associated with a UE from a second network node; and configuring communication with one or more other UEs based at least in part on the CLI information.

[0196] Aspect 16: The method according to aspect 15, wherein the CLI information includes at least one CLI reference signal measurement resource configuration for at least one UE including the UE.

[0197] Aspect 17: The method according to aspect 15, wherein receiving the CLI information comprises: receiving the CLI information via a backhaul interface with the second network node.

[0198] Aspect 18: The method according to any one of aspects 15 to 17, wherein receiving the CLI information comprises: receiving the CLI information via an air interface with the second network node.

[0199] Aspect 19: The method according to any one of aspects 15 to 18, wherein the first network node is associated with a first CU and the second network node is associated with a second CU.

[0200] Aspect 20: The method according to any one of aspects 15 to 19, wherein the first network node is a first DU and the second network node is a second DU.

[0201] Aspect 21: The method according to any one of Aspects 15 to 20, the method further comprising: receiving information identifying a CLI resource identifier from the second network node; and wherein configuring the communication comprises: configuring the communication based at least in part on the CLI resource identifier.

[0202] Aspect 22: The method according to aspect 21, wherein the CLI resource identifier is associated with at least one of a reference signal identifier or a beam identifier.

[0203] Aspect 23: A method according to any one of Aspects 15 to 22, wherein the CLI information indicates a number of CLI resources associated with the CLI measurement of the UE, and wherein the number of CLI resources is based at least in part on a first number of transmit beams associated with the UE and a second number of receive beams associated with another UE among the one or more other UEs associated with the CLI.

[0204] Aspect 24: The method according to aspect 23, wherein the method further comprises: sending CLI configuration information to the other UE indicating that the other UE is to perform CLI measurements associated with the number of CLI resources.

[0205] Aspect 25: According to the method according to any one of aspects 15 to 24, the method also includes: receiving, from the second network node, information indicating to the UE a time difference between reception of a downlink communication sent to the UE and reception of a CLI reference signal by the UE.

[0206] Aspect 26: The method according to aspect 25, the method also includes: scheduling communication with another UE of the one or more other UEs based at least in part on the information indicating the time difference.

[0207] Aspect 27: According to any one of Aspects 15 to 26, the method also includes: receiving a power backoff recommendation for another UE among the one or more other UEs from the second network node; and configuring communication with the other UE based at least in part on the power backoff recommendation.

[0208] Aspect 28: A method according to Aspect 27, wherein configuring the communication includes: configuring the communication based at least in part on one or more downlink parameters, the one or more downlink parameters including at least one of the following: modulation and decoding scheme, or transport block size.

[0209] Aspect 29: A method of wireless communication performed by a device of a UE, the method comprising: receiving information indicating a time window associated with measurement of at least one CLI reference signal from a network node; receiving the at least one CLI reference signal; and sending information indicating a time difference between the time window and the reception of the at least one CLI reference signal to the network node.

[0210] Aspect 30: The method according to aspect 29, further comprising: sending a power backoff recommendation for another UE associated with another network node to the network node.

[0211] Aspect 31: The method according to aspect 30, the method further comprising: determining the power backoff recommendation based at least in part on the at least one CLI reference signal.

[0212] Aspect 32: The method according to aspect 31, wherein the power backoff recommendation is based at least in part on: a modulation and coding scheme, or a transport block size.

[0213] Aspect 33: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 14.

[0214] Aspect 34: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 15 to 28.

[0215] Aspect 35: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 29 to 32.

[0216] Aspect 36: A device for wireless communication, the device comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 1 to 14.

[0217] Aspect 37: A device for wireless communication, the device comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 15 to 28.

[0218] Aspect 38: A device for wireless communication, the device comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 29 to 32.

[0219] Aspect 39: An apparatus for wireless communication, the apparatus comprising at least one component configured to perform the method according to one or more of aspects 1 to 14.

[0220] Aspect 40: An apparatus for wireless communication, the apparatus comprising at least one component configured to perform the method according to one or more of aspects 15 to 28.

[0221] Aspect 41: An apparatus for wireless communication, the apparatus comprising at least one component configured to perform the method according to one or more of aspects 29 to 32.

[0222] Aspect 42: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 14.

[0223] Aspect 43: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 15 to 28.

[0224] Aspect 44: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 29 to 32.

[0225] Aspect 45: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 14.

[0226] Aspect 46: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 15 to 28.

[0227] Aspect 47: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 29 to 32.

[0228] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the various aspects.

[0229] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, there is no reference to a specific software code herein to describe the operation and behavior of the system and / or method, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0230] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0231] Although the specific combination of features is set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (it includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).

[0232] Any element, action or instruction used herein should not be interpreted as key or necessary, unless explicitly described as such. In addition, as used herein, the article "one" is intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If only want to refer to a project, the phrase "only one" or similar terms will be used. In addition, as used herein, the terms "have", "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "an element with" A can also have B). In addition, the phrase "based on" is intended to represent "based at least in part", unless otherwise explicitly stated. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless explicitly stated otherwise (e.g., if used in conjunction with "either" or "only one of").

Claims

1. A first network node for wireless communication, the first network node comprising: Memory; and one or more processors coupled to the memory and configured to: receiving a cross link interference (CLI) report from a user equipment (UE); and CLI information indicative of a CLI associated with the UE is sent to a second network node and based at least in part on the CLI report. 2 . The first network node according to claim 1 , wherein the CLI information comprises at least one CLI reference signal measurement resource configuration for at least one UE including the UE.

3. The first network node of claim 1 , wherein to send the CLI information, the one or more processors are configured to: The CLI information is sent via a backhaul interface with the second network node.

4. The first network node of claim 1 , wherein to send the CLI information, the one or more processors are configured to: The CLI information is sent via an air interface with the second network node.

5. The first network node of claim 1, wherein the first network node is associated with a first central unit (CU) and the second network node is associated with a second CU.

6. The first network node of claim 1, wherein the first network node is a first distributed unit (DU) and the second network node is a second DU.

7. The first network node of claim 1 , wherein the one or more processors are further configured to: determining a CLI resource identifier associated with a CLI value based at least in part on the CLI report; and Information identifying the CLI resource identifier is sent to the second network node.

8. The first network node of claim 7, wherein to determine the CLI resource identifier, the one or more processors are configured to: The CLI resource identifier is determined based at least in part on the CLI value being a minimum CLI value among CLI values ​​indicated in the CLI report.

9. The first network node of claim 7, wherein the CLI resource identifier is associated with at least one of a reference signal identifier or a beam identifier.

10. The first network node according to claim 1, wherein the CLI information indicates a number of CLI resources associated with CLI measurement of the UE, and Wherein the number of CLI resources is based at least in part on a first number of transmit beams associated with the UE and a second number of receive beams associated with a second UE associated with the CLI.

11. The first network node of claim 1 , wherein the one or more processors are further configured to: sending, to the UE, information indicating a time window associated with measurement of at least one CLI reference signal; and Information indicative of a time difference between arrival of a downlink communication from the first network node and arrival of the at least one CLI reference signal is received from the UE.

12. The first network node of claim 11, wherein the one or more processors are further configured to: Communications with the UE are scheduled based at least in part on the information indicative of the time difference.

13. The first network node of claim 11, wherein the one or more processors are further configured to: The information indicative of the time difference is sent to the second network node.

14. The first network node of claim 1, wherein the one or more processors are further configured to: receiving, from the UE, a power backoff recommendation for another UE associated with the second network node; and Information indicative of the power backoff recommendation is sent to the second network node.

15. A first network node for wireless communication, the first network node comprising: Memory; and one or more processors coupled to the memory and configured to: receiving, from a second network node, cross-link interference (CLI) information indicating CLI associated with a user equipment (UE); and Communications with one or more other UEs are configured based at least in part on the CLI information.

16. The first network node according to claim 15, wherein the CLI information comprises at least one CLI reference signal measurement resource configuration for at least one UE including the UE.

17. The first network node of claim 15, wherein to receive the CLI information, the one or more processors are configured to: The CLI information is received via a backhaul interface with the second network node.

18. The first network node of claim 15, wherein to receive the CLI information, the one or more processors are configured to: The CLI information is received via an air interface with the second network node.

19. The first network node of claim 15, wherein the first network node is associated with a first central unit (CU) and the second network node is associated with a second CU.

20. The first network node of claim 15, wherein the first network node is a first distributed unit (DU) and the second network node is a second DU.

21. The first network node of claim 15, wherein the one or more processors are further configured to: receiving information identifying a CLI resource identifier from the second network node; and Wherein, in order to configure the communication, the one or more processors are configured to: The communication is configured based at least in part on the CLI resource identifier.

22. The first network node of claim 21, wherein the CLI resource identifier is associated with at least one of a reference signal identifier or a beam identifier.

23. The first network node according to claim 15, wherein the CLI information indicates a number of CLI resources associated with CLI measurement of the UE, and Wherein the number of CLI resources is based at least in part on a first number of transmit beams associated with the UE and a second number of receive beams associated with another UE of the one or more other UEs associated with the CLI.

24. The first network node according to claim 23, wherein the one or more processors are further configured to: CLI configuration information is sent to the other UE indicating that the other UE is to perform CLI measurements associated with the number of CLI resources.

25. The first network node of claim 15, wherein the one or more processors are further configured to: Information is received from the second network node indicating, for the UE, a time difference between reception of a downlink communication sent to the UE and reception of a CLI reference signal by the UE.

26. The first network node of claim 25, wherein the one or more processors are further configured to: Communications with another UE of the one or more other UEs are scheduled based at least in part on the information indicative of the time difference.

27. The first network node of claim 15, wherein the one or more processors are further configured to: receiving, from the second network node, a power backoff recommendation for another UE of the one or more other UEs; and Communications with the other UE are configured based at least in part on the power backoff recommendation.

28. The first network node of claim 27, wherein to configure the communication, the one or more processors are configured to: The communications are configured based at least in part on one or more downlink parameters, the one or more downlink parameters comprising at least one of: modulation and coding scheme, or Transport block size.

29. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Memory; and one or more processors coupled to the memory and configured to: receiving, from a network node, information indicating a time window associated with measurement of at least one cross-link interference (CLI) reference signal; receiving the at least one CLI reference signal; as well as Information indicating a time difference between the time window and reception of the at least one CLI reference signal is sent to the network node.

30. A method of wireless communication performed by an apparatus of a first network node, the method comprising: receiving a cross link interference (CLI) report from a user equipment (UE); as well as CLI information indicative of a CLI associated with the UE is sent to a second network node and based at least in part on the CLI report.

Images