Inter-access network interference measurement and reporting configuration

Abstract

Methods, systems, and devices for wireless communication are described. For example, the techniques provide for configuring a network entity to transmit reference signals for cross-link interference (CLI) measurements, receive reference signals for CLI measurements, or report CLI measurements. The first network entity may send an indication of a configuration for sending a reference signal for CLI measurement to a second network entity. The first network entity may also send an indication of a configuration for monitoring or receiving the reference signal for CLI measurements to a third network entity, and the first network entity may send another indication of a configuration for reporting the CLI measurements to the third network entity. The second network entity may then transmit the reference signal, and the third network entity may receive the reference signal, perform a CLI measurement on the reference signal, and report the CLI measurement.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. patent application No. 17 / 858,521, entitled “INTER ACCESS NETWORK INTERFERENCE MEASUREMENT AND REPORT CONFIGURATION,” filed by Zhang et al. on July 6, 2022, which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following relates to wireless communications, including inter-access network interference measurement and reporting configuration. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, etc. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems), and fifth generation (5G) systems, which may be referred to as new radio (NR) systems. These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM).

[0005] A wireless multiple access communication system may include one or more network entities, each of which supports wireless communication of communication devices, which may be referred to as user equipment (UE). In some wireless communication systems, communications at different network entities may interfere. For example, communications between a first network entity and one or more UEs may interfere with communications between a second network entity and one or more UEs. Interference between network entities may be referred to as cross-link interference between network entities. Improved techniques for minimizing cross-link interference between network entities may be desirable. Summary of the invention

[0006] The described technology relates to improved methods, systems, devices and apparatuses for supporting inter-access network interference measurement and reporting configuration. For example, the described technology provides for configuring a network entity to send a reference signal for cross-link interference (CLI) measurement, receive a reference signal for CLI measurement, or report CLI measurement. A first network entity may send an indication of a configuration for sending a reference signal for CLI measurement to a second network entity. The first network entity may also send an indication of a configuration for monitoring or receiving a reference signal for CLI measurement to a third network entity, and the first network entity may send another indication of a configuration for reporting CLI measurement or reporting based on CLI measurement to the third network entity. The second network entity may then send a reference signal, and the third network entity may receive the reference signal, perform CLI measurement on the reference signal, and report the CLI measurement or report based on the CLI measurement.

[0007] A method for wireless communication at a first network entity is described. The method may include: receiving from a second network entity an indication of a configuration for sending a reference signal for interference measurement at a third network entity; sending the reference signal based on the configuration; and receiving from the second network entity a scheduling message for scheduling communications at the first network entity based on sending the reference signal.

[0008] An apparatus for wireless communication at a first network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to receive an indication of a configuration for sending a reference signal for interference measurement at a third network entity from a second network entity; send the reference signal based on the configuration; and receive a scheduling message from the second network entity to schedule communication at the first network entity based on sending the reference signal.

[0009] Another apparatus for wireless communication at a first network entity is described. The apparatus may include: means for receiving, from a second network entity, an indication of a configuration for sending a reference signal for interference measurement at a third network entity; means for sending the reference signal based on the configuration; and means for receiving, from the second network entity, a scheduling message for scheduling communications at the first network entity based on sending the reference signal.

[0010] A non-transitory computer-readable medium storing code for wireless communication at a first network entity is described. The code may include instructions executable by a processor to receive from a second network entity an indication of a configuration for sending a reference signal for interference measurement at a third network entity; send the reference signal based on the configuration; and receive from the second network entity a scheduling message for scheduling communications at the first network entity based on sending the reference signal.

[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the configuration includes a first configuration, and the reference signal includes a first reference signal set, and the method, apparatus, and non-transitory computer-readable media may also include operations, features, components, or instructions for performing the following actions: receiving an indication of a second configuration for sending a second reference signal set to one or more user equipment (UE) for access link management or beam management; and sending a second reference signal set to one or more user equipment (UE) based on the second configuration, wherein the second reference signal set may be different from the first reference signal set.

[0012] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first set of reference signals partially overlaps with the second set of reference signals. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, receiving an indication of the configuration may include operations, features, components, or instructions for receiving a quasi-co-location indication of one or more beams for the first network entity to use to send reference signals. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, receiving an indication of the configuration may include operations, features, components, or instructions for performing the following actions: receiving an indication of resources mapped to each of the one or more beams; and sending a reference signal using each of the one or more beams on the corresponding resources mapped to each beam.

[0013] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: receiving an indication of the configuration includes receiving an identifier of a resource set on which to send a reference signal, and sending the reference signal includes sending the reference signal on the resource set based on receiving the configuration. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the configuration includes an indication of a type of the resource set, the type of the resource set being periodic, aperiodic, or semi-persistent.

[0014] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: receiving an indication of the configuration includes receiving an indication of a starting position of a resource set, a number of symbols, a repetition factor, or a combination thereof. In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first network entity includes a first distributed unit, the second network entity includes a central unit or an operation, administration, and maintenance entity, and the third network entity includes a second distributed unit.

[0015] A method for wireless communication at a first network entity is described. The method may include: receiving from a second network entity an indication of a configuration for monitoring reference signals from a third network entity for interference measurement at the first network entity; receiving one or more of the reference signals sent by the third network entity for interference measurement; performing interference measurement on one or more of the reference signals; and sending a report to the second network entity based on performing the interference measurement on the one or more of the reference signals.

[0016] An apparatus for wireless communication at a first network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to receive, from a second network entity, an indication of a configuration for monitoring reference signals from a third network entity for interference measurement at the first network entity; receive one or more of the reference signals sent by the third network entity for interference measurement; perform interference measurement on one or more of the reference signals; and send a report to the second network entity based on performing the interference measurement on the one or more of the reference signals.

[0017] Another apparatus for wireless communication at a first network entity is described. The apparatus may include: means for receiving, from a second network entity, an indication of a configuration for monitoring reference signals from a third network entity for interference measurement at the first network entity; means for receiving one or more of the reference signals sent by the third network entity for interference measurement; means for performing interference measurement on one or more of the reference signals; and means for sending a report to the second network entity based on performing interference measurement on one or more of the reference signals.

[0018] A non-transitory computer-readable medium storing code for wireless communication at a first network entity is described. The code may include instructions executable by a processor to receive from a second network entity an indication of a configuration for monitoring reference signals from a third network entity for interference measurement at the first network entity; receive one or more of the reference signals sent by the third network entity for interference measurement; perform interference measurement on one or more of the reference signals; and send a report to the second network entity based on performing the interference measurement on the one or more of the reference signals.

[0019] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the configuration for monitoring a reference signal from a third network entity includes a first configuration, and the methods, apparatuses, and non-transitory computer-readable media may also include operations, features, components, or instructions for the following actions: receiving an indication of a second configuration for sending a report to the second network entity from the second network entity. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the second configuration for sending a report to the second network entity indicates a type of report, the type of report being periodic, aperiodic, or semi-persistent.

[0020] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: receiving the second configuration includes receiving an indicator of one or more events that trigger sending a report to the second network entity. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: receiving a trigger from the second network entity to perform interference measurements and sending a report to the second network entity.

[0021] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: receiving a medium access control (MAC) control element from a third network entity that triggers the first network entity to perform interference measurements and send a report to the second network entity. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, receiving an indication of the configuration may include operations, features, components, or instructions for receiving a quasi-co-location indication of one or more beams used by the first network entity to receive a reference signal.

[0022] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: identifying resources mapped to each of the one or more beams from the configuration; and receiving a reference signal using each of the one or more beams on the corresponding resources mapped to each beam. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, performing interference measurements may include operations, features, components, or instructions for: performing reference signal received power measurements on a reference signal received from a third network entity based on receiving a configuration having a format associated with reference signal received power measurements.

[0023] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, performing interference measurements may include operations, features, components, or instructions for performing reference signal strength indicator measurements on reference signals received from a third network entity based on receiving a configuration having a format associated with reference signal strength indicator measurements. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving an indication of the configuration includes receiving an identifier of a resource set to monitor for reference signals, and receiving the reference signal includes receiving the reference signal on the resource set based on the identifier of the resource set.

[0024] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the configuration indicates a type of resource set, the type of resource set being periodic, non-periodic, or semi-persistent. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the configuration indicates a starting position of the resource set, a number of symbols, a repetition factor, or a combination thereof. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first network entity includes a first distributed unit, the second network entity includes a central unit or an operation, management, and maintenance entity, and the third network entity includes a second distributed unit.

[0025] A method for wireless communication at a first network entity is described. The method may include: sending first information associated with a first configuration for sending a reference signal from a second network entity to a third network entity; sending second information associated with a second configuration for monitoring the reference signal by the third network entity; sending third information associated with a third configuration for reporting, by the third network entity, interference measurements performed on the reference signal received from the second network entity; and receiving fourth information associated with interference measurements reported by the third network entity based on sending the first information, the second information, and the third information.

[0026] An apparatus for wireless communication at a first network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to send first information associated with a first configuration for sending a reference signal from a second network entity to a third network entity; send second information associated with a second configuration for monitoring the reference signal by the third network entity; send third information associated with a third configuration for reporting, by the third network entity, interference measurements performed on the reference signal received from the second network entity; and receive fourth information associated with interference measurements reported by the third network entity based on sending the first information, the second information, and the third information.

[0027] Another apparatus for wireless communication at a first network entity is described. The apparatus may include: means for sending first information associated with a first configuration for sending a reference signal from a second network entity to a third network entity; means for sending second information associated with a second configuration for monitoring the reference signal by the third network entity; means for sending third information associated with a third configuration for reporting, by the third network entity, interference measurements performed on the reference signal received from the second network entity; and means for receiving fourth information associated with interference measurements reported by the third network entity based on sending the first information, the second information, and the third information.

[0028] A non-transitory computer-readable medium storing code for wireless communication at a first network entity is described. The code may include instructions executable by a processor to send first information associated with a first configuration for sending a reference signal from a second network entity to a third network entity; send second information associated with a second configuration for monitoring the reference signal by the third network entity; send third information associated with a third configuration for reporting interference measurements performed on the reference signal received from the second network entity by the third network entity; and receive fourth information associated with interference measurements reported by the third network entity based on sending the first information, the second information, and the third information.

[0029] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, communications at the second network entity and the third network entity are scheduled based on receiving fourth information associated with interference measurements reported by the third network entity. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, sending the first information, the second information, and the third information and receiving the fourth information may include operations, features, components, or instructions for coordinating with the fourth network entity to configure the second network entity to send a reference signal, configure the third network entity to receive the reference signal, and configure the third network entity to report interference measurements performed on the reference signal.

[0030] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for coordinating with a fourth network entity to schedule communications at the second network entity and the third network entity based on receiving fourth information associated with interference measurements reported by the third network entity. In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first network entity includes a central unit or an operations, administration, and maintenance entity, the second network entity includes a first distributed unit, and the third network entity includes a second distributed unit. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Figure 1An example of a wireless communication system supporting inter-access network interference measurement and reporting configuration according to one or more aspects of the present disclosure is illustrated.

[0032] Figure 2 An example of a wireless communication system supporting inter-access network interference measurement and reporting configuration according to one or more aspects of the present disclosure is illustrated.

[0033] Figure 3 An example of full-duplex communication according to one or more aspects of the present disclosure is illustrated.

[0034] Figure 4 An example of cross-link interference (CLI) according to one or more aspects of the present disclosure is illustrated.

[0035] Figure 5 An example of a wireless communication system supporting inter-access network interference measurement and reporting configuration according to one or more aspects of the present disclosure is illustrated.

[0036] Figure 6 An example of a process flow to support inter-access network interference measurement and reporting configuration in accordance with one or more aspects of the present disclosure is illustrated.

[0037] Figure 7 An example of a process flow to support inter-access network interference measurement and reporting configuration in accordance with one or more aspects of the present disclosure is illustrated.

[0038] Figure 8 and Fig. 9 A block diagram of an apparatus supporting inter-access network interference measurement and reporting configuration according to one or more aspects of the present disclosure is shown.

[0039] Fig.10 A block diagram of a communications manager supporting inter-access network interference measurement and reporting configuration is shown in accordance with one or more aspects of the present disclosure.

[0040] Fig.11 A diagram of a system including a device supporting inter-access network interference measurement and reporting configuration is shown in accordance with one or more aspects of the present disclosure.

[0041] Figure 12 to Figure 14 A flow chart illustrating a method of supporting inter-access network interference measurement and reporting configuration according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0042] In some wireless communication systems, communications at different network entities may interfere. For example, communications between a first network entity and one or more user equipments (UEs) may interfere with communications between a second network entity and one or more UEs. If the first network entity supports full-duplex communication, downlink communications at the first network entity may interfere with uplink communications at the second network entity. Similarly, if different network entities support time division duplex (TDD), and the first network entity uses time resources for downlink communications, while the second network entity uses the same time resources for uplink communications, downlink communications and uplink communications may interfere. Interference between network entities may be referred to as cross-link interference (CLI) between network entities. In some cases, as the number of devices in a wireless communication system increases, CLI between network entities may also increase and may reduce throughput (e.g., due to failed transmissions) and increase overhead (e.g., due to more retransmissions).

[0043] As described herein, a wireless communication system may support efficient techniques for facilitating CLI measurements and using these CLI measurements to make scheduling decisions. For example, the described techniques provide for configuring a network entity to send a reference signal for cross-link interference (CLI) measurements, receive a reference signal for CLI measurements, or report CLI measurements. A first network entity may send an indication of a configuration for sending a reference signal for CLI measurements to a second network entity. The first network entity may also send an indication of a configuration for monitoring or receiving the reference signal for CLI measurements to a third network entity, and the first network entity may send another indication of a configuration for reporting the CLI measurements to the third network entity. The second network entity may then send the reference signal, and the third network entity may receive the reference signal, perform CLI measurements on the reference signal, and report the CLI measurements.

[0044] Various aspects of the present disclosure are first described in the context of a wireless communication system. Examples of processes and signaling exchanges that support inter-access network interference measurement and reporting configuration are then described. Various aspects of the present disclosure are further illustrated by apparatus diagrams, system diagrams, and flow diagrams related to inter-access network interference measurement and reporting configuration, and various aspects of the present disclosure are described with reference to these diagrams.

[0045] Figure 1An example of a wireless communication system 100 supporting inter-access network interference measurement and reporting configuration according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, a new radio (NR) network, or a network operating according to other systems and radio technologies (including future systems and radio technologies not explicitly mentioned herein).

[0046] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other nomenclature. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) within which the UE 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area within which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).

[0047] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein can communicate with various types of devices, such as Figure 1 Communicate with other UEs 115 or network entities 105) as shown.

[0048] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from a second node.

[0049] In some examples, the network entities 105 may communicate with the core network 130, or communicate with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3 or other interface protocols). In some examples, the network entities 105 may communicate with each other over the backhaul communication links 120 (e.g., according to X2, Xn or other interface protocols) directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130). In some examples, the network entities 105 may communicate with each other via the midhaul communication link 162 (e.g., according to the midhaul interface protocol) or the fronthaul communication link 168 (e.g., according to the fronthaul interface protocol) or any combination thereof. The backhaul communication link 120, the midhaul communication link 162, or the fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), etc. or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

[0050] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next-generation Node B, or a Gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next-generation eNB (ng-eNB), a Home Node B, a Home Evolved Node B, or other suitable terms). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) base station architecture, which may be configured to utilize a protocol stack physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).

[0051] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system (e.g., an SMO framework), or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0052] The functional split between CU 160, DU 165, and RU 175 is flexible and may support different functionalities, depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 175. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165 such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DUs 165 and RUs 170, such that the DUs 165 may support one or more layers of the protocol stack, and the RUs 170 may support one or more different layers of the protocol stack. The DUs 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by different ones of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented based on interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 communicating over those communication links.

[0053] In some wireless communication systems (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile termination (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a collection of independent antennas for relaying communications with the UE 115, or may share the same antenna of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0054] For example, an access network (AN) or RAN may include an access node (e.g., an IAB host), communications between an IAB node 104 and one or more UEs 115. The IAB host may facilitate a connection between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, the IAB host may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB host may include a CU 160 and at least one DU 165 (e.g., and RU 170), wherein the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB host and the IAB node 104 may communicate via an F1 interface according to a protocol defining a signaling message (e.g., an F1 AP protocol). Additionally or alternatively, the CU 160 may communicate with the core network via an interface (which may be an example of a portion of a backhaul link), and may communicate with other CUs 160 (e.g., CUs 160 associated with an alternative IAB host) via an Xn-C interface (which may be an example of a portion of a backhaul link).

[0055] An IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, wireless self-backhaul capabilities, etc.). DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB host may be referred to as a parent node that communicates with one or more child nodes (e.g., an IAB host may relay for UE transmissions through one or more other IAB nodes 104). Additionally or alternatively, depending on the relay chain or configuration of the AN, an IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104. Thus, the IAB-MT entity of the IAB node 104 may provide a Uu interface for the child IAB node 104 to receive signaling from the parent IAB node 104 , and a DU interface (eg, DU 165 ) may provide a Uu interface for the parent IAB node 104 to signal to the child IAB node 104 or the UE 115 .

[0056] For example, the IAB node 104 may be referred to as a parent node that supports child IAB node communications and as a child node associated with the IAB host. The IAB host may include a CU 160 having a wired or wireless connection to the core network 130 (e.g., a backhaul communication link 120), and may act as a parent node of the IAB node 104. For example, the DU 165 of the IAB host may relay transmissions to the UE 115 via the IAB node 104, and may directly signal the transmissions to the UE 115. The CU 160 of the IAB host may signal the establishment of a communication link to the IAB node 104 via the F1 interface, and the IAB node 104 may schedule transmissions (e.g., transmissions relayed from the IAB host to the UE 115) via the DU 165. That is, data may be relayed to and from the IAB node 104 via signaling on the NR Uu interface of the MT to the IAB node 104. Communications with the IAB node 104 may be scheduled by the DU 165 of the IAB host, and communications with the IAB node 104 may be scheduled by the DU 165 of the IAB node 104 .

[0057] In the case where the techniques described herein are applied to the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support inter-access network interference measurement and reporting configurations as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

[0058] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0059] The UE 115 described herein may be capable of communicating with various types of devices such as other UEs 115 which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 shown.

[0060] The UE 115 and the network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) on one or more carriers. The term "carrier" may refer to a collection of RF spectrum resources having a physical layer structure defined to support the communication link 125. For example, a carrier for the communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communications with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between a device and any portion (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send," "receive," or "communicate" when referring to the network entity 105 may refer to any portion of a network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0061] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be located according to a channel raster for discovery by UE 115. A carrier may operate in a standalone mode, in which case initial acquisition and connection may be performed by UE 115 via the carrier, or a carrier may operate in a non-standalone mode, in which case the connection is anchored using a different carrier (e.g., a different carrier of the same or different radio access technology).

[0062] The communication link 125 shown in the wireless communication system 100 may include downlink transmissions (e.g., forward link transmissions) from the network entity 105 to the UE 115 (e.g., in a physical downlink control channel (PDCCH) or a physical downlink shared channel (PDSCH)), uplink transmissions (e.g., return link transmissions) from the UE 115 to the network entity 105 (e.g., in a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH)), or both, as well as other transmission configurations. A carrier may carry downlink communications or uplink communications (e.g., in FDD mode), or may be configured to carry downlink communications and uplink communications (e.g., in TDD mode).

[0063] A carrier may be associated with a particular bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as a "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz) of a carrier of a particular radio access technology. A device (e.g., a network entity 105, a UE 115, or both) of the wireless communication system 100 may have a hardware configuration that supports communication on a particular carrier bandwidth or may be configurable to support communication on one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent communication via carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate on a portion (e.g., a subband, a BWP) or all of a carrier bandwidth.

[0064] The signal waveform transmitted over the carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The amount of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), such that the more resource elements a device receives and the higher the order of the modulation scheme, the higher the data rate of the device may be. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0065] One or more numerologies for a carrier may be supported, where the numerologies may include subcarrier spacing (Δf) and cyclic prefixes. A carrier may be divided into one or more BWPs with the same or different numerologies. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications of a UE 115 may be constrained to one or more active BWPs.

[0066] The time interval for the network entity 105 or the UE 115 may be expressed as a multiple of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·N F ) seconds, where Δf max It can represent the maximum supported subcarrier spacing, and N F The maximum supported discrete Fourier transform (DFT) size may be indicated. Time intervals of the communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0067] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, the frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended in front of each symbol period). In some wireless communication systems 100, the time slot may be further divided into multiple micro time slots including one or more symbols. Excluding the cyclic prefix, each symbol period may include one or more (e.g., N F The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0068] A subframe, a time slot, a mini-time slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).

[0069] Physical channels may be multiplexed on a carrier according to various techniques. For example, physical control channels and physical data channels may be multiplexed on a downlink carrier using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth of a carrier or a subset of that system bandwidth. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more UEs in UE 115 may monitor or search a control region to obtain control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to a plurality of UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0070] The network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hot spots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with the network entity 105 (e.g., via a carrier), and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other cell identifier) ​​used to distinguish adjacent cells. In some examples, a cell may also refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) within which the logical communication entity operates. Depending on various factors such as the capabilities of the network entity 105, such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or may include a building, a subset of a building, or an external space between or overlapping coverage areas 110, and the like.

[0071] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0072] The wireless communication system 100 can be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 can be configured to support ultra-reliable low-latency communication (URLLC). UE 115 can be designed to support ultra-reliable, low-latency or critical functions. Ultra-reliable communication may include private communication or group communication, and may be supported by one or more services (such as push-to-talk, video or data). Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency and ultra-reliable low-latency may be used interchangeably herein.

[0073] In some examples, a UE 115 may be able to communicate directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which may support aspects of such D2D communication configured or scheduled by the network entity 105. In some examples, one or more UEs 115 in such a group may be outside of the coverage area 110 of the network entity 105, or may be unable or not configured to receive transmissions from the network entity 105 for other reasons. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, the network entity 105 may facilitate scheduling of resources for D2D communication. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105 .

[0074] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity for managing access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and at least one user plane entity for routing packets or interconnecting to an external network (e.g., a serving gateway (S-GW)), a packet data network (PDN) gateway (P-GW) or a user plane function (UPF)). The control plane entity may manage non-access layer (NAS) functions such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be delivered through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to the IP service 150 of one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0075] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Typically, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength range is about one decimeter to one meter long. UHF waves may be blocked or redirected by buildings and environmental features, which may be referred to as clusters, but these waves may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to transmission using smaller frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0076] The wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 may employ license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in unlicensed bands such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating in an unlicensed RF spectrum band, devices such as network entities 105 and UEs 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations in unlicensed bands may be based on a carrier aggregation configuration (e.g., LAA) combined with component carriers operating in licensed bands. Operations in unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and the like.

[0077] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas, which can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, the antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may have an antenna array having a set of rows and columns of antenna ports that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0078] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals conveyed via antenna elements of an antenna array so that some signals propagating in a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other direction).

[0079] The network entity 105 or UE 115 may use beam scanning techniques as part of a beamforming operation. For example, the network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be sent multiple times by the network entity 105 along different directions. For example, the network entity 105 may send signals according to different sets of beamforming weights associated with different transmission directions. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device (such as network entity 105), or by a receiving device (such as UE 115)) beam directions for later transmission or reception by the network entity 105.

[0080] Some signals, such as data signals associated with a particular receiving device, may be sent by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., a direction associated with a receiving device (such as receiving network entity 105 or receiving UE 115)). In some examples, a beam direction associated with transmission along a single beam direction may be determined based on signals sent along one or more beam directions. For example, UE 115 may receive one or more of the signals sent by network entity 105 along different directions, and may report to network entity 105 an indication of the signal received by UE 115 with the highest signal quality or other acceptable signal quality.

[0081] In some examples, transmission by a device (e.g., by network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more subbands. Network entity 105 may send a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS)), which may be precoded or non-precoded. UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel codebook, a linear combination codebook, a port selection codebook). Although these techniques are described with reference to signals sent along one or more directions by a network entity 105 (e.g., base station 140, RU 170), UE 115 may use similar techniques to send signals multiple times along different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 115), or to send signals along a single direction (e.g., to send data to a receiving device).

[0082] A receiving device (e.g., UE 115) may perform receiving operations according to multiple receiving configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a receiving device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple receiving directions by: receiving via different antenna subarrays, processing received signals according to different antenna subarrays, receiving according to different receiving beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or processing received signals according to different receiving beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different receiving configurations or receiving directions. In some examples, the receiving device may use a single receiving configuration to receive along a single beam direction (e.g., when receiving a data signal). A single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0083] The wireless communication system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, the communication at the bearer or PDCP layer may be IP-based. The RLC layer may perform packet segmentation and reassembly to communicate on a logical channel. The MAC layer may perform priority processing and multiplexing of logical channels into transport channels. The MAC layer may also use error detection technology, error correction technology, or both to support retransmission at the MAC layer to improve link efficiency. In the control plane, the RRC protocol layer may provide the establishment, configuration, and maintenance of an RRC connection that supports a radio bearer for user plane data between a UE 115 and a network entity 105 or a core network 130. At the PHY layer, a transport channel may be mapped to a physical channel.

[0084] The wireless communication system 100 may support effective techniques for facilitating CLI measurements and using these CLI measurements to make scheduling decisions to improve throughput. For example, the techniques provide for configuring the network entity 105 to send a reference signal for CLI measurements, receive a reference signal for CLI measurements, or report CLI measurements. The first network entity 105 may send an indication of a configuration for sending a reference signal for CLI measurements to the second network entity 105. The first network entity 105 may also send an indication of a configuration for monitoring or receiving a reference signal for CLI measurements to the third network entity 105, and the first network entity 105 may send another indication of a configuration for reporting CLI measurements to the third network entity 105. The second network entity 105 may then send a reference signal, and the third network entity 105 may receive the reference signal, perform CLI measurements on the reference signal, and report the CLI measurements.

[0085] Figure 2An example of a network architecture 900 (e.g., a decomposed base station architecture, a decomposed RAN architecture) supporting inter-access network interference measurement and reporting configurations according to one or more aspects of the present disclosure is illustrated. The network architecture 200 may illustrate an example for implementing one or more aspects of the wireless communication system 100. The network architecture 200 may include one or more CUs 160-a, which may communicate directly with the core network 130-a via a backhaul link 120-a, or indirectly with the core network 130-a through one or more decomposed network entities 105 (e.g., a near RT RIC 175-b via an E2 link, a non-RT RIC 175-a associated with an SMO 180-a, or both). The CU 160-a may communicate with one or more DUs 165-a via corresponding midhaul communication links 162-a (e.g., an F1 interface). The DU 165-a may communicate with one or more RUs 170-a via corresponding fronthaul communication links 168-a. The RU 170-a may communicate with a corresponding UE 115-a via one or more communication links 125-a. In some implementations, a UE 115-a may be served by multiple RUs 170-a simultaneously.

[0086] Each of the network entities 105 of the network architecture 200 (e.g., CU 160-a, DU 165-a, RU 170-a, non-RT RIC 175-a, near-RT RIC 175-b, SMO 180-a, open cloud (O-Cloud) 205, open eNB (O-eNB) 210) may include one or more interfaces or may be coupled to one or more interfaces configured to receive or send signals (e.g., data, information) via a wired or wireless transmission medium. Each network entity 105 or an associated processor (e.g., a controller) that provides instructions to an interface of the network entity 105 may be configured to communicate with one or more of the other network entities 105 via a transmission medium. For example, these network entities 105 may include a wired interface that is configured to receive signals on a wired transmission medium or to send signals to one or more of the other network entities 105 on a wired transmission medium. Additionally or alternatively, the network entity 105 may include a wireless interface, which may include a receiver, a transmitter, or a transceiver (e.g., an RF transceiver) configured to receive signals on a wireless transmission medium, or to send signals to one or more of the other network entities 105 on a wireless transmission medium, or both.

[0087] In some examples, CU 160-a may host one or more higher layer control functions. Such control functions may include RRC, PDCP, SDAP, etc. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by CU 160-a. CU 160-a may be configured to process user plane functionality (e.g., CU-UP), control plane functionality (e.g., CU-CP), or a combination thereof. In some examples, CU 160-a may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 160-a may be implemented to communicate with DU 165-a for network control and signaling.

[0088] DU 165-a may correspond to a logical unit that includes one or more functions (e.g., base station functions, RAN functions) for controlling the operation of one or more RUs 170-a. In some examples, DU 165-a may at least partially host one or more of the RLC layer, the MAC layer, and one or more aspects of the PHY layer (e.g., a high PHY layer, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, etc.), which depends at least in part on functional divisions, such as those defined by the Third Generation Partnership Project (3GPP). In some examples, DU 165-a may also host one or more low PHY layers. Each layer may be implemented with an interface that is configured to communicate signals with other layers hosted by DU 165-a or with control functions hosted by CU 160-a.

[0089] In some examples, lower layer functionality may be implemented by one or more RUs 170-a. For example, a RU 170-a controlled by a DU 165-a may correspond to a logical node that hosts RF processing functions or low PHY layer functions (e.g., performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.) or both based at least in part on functional splitting (such as lower layer functional splitting). In this architecture, RU 170-a may be implemented to handle over-the-air (OTA) communications with one or more UEs 115-a. In some specific implementations, real-time and non-real-time aspects of control and user plane communications with RU 170-a may be controlled by the corresponding DU 165-a. In some examples, this configuration may enable DU 165-a and CU 160-a to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0090] The SMO 180-a may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, the SMO 180-a 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 (e.g., an O1 interface). For virtualized network entities 105, the SMO 180-a may be configured to interact with a cloud computing platform (e.g., O-Cloud 205) via a cloud computing platform interface (e.g., an O2 interface) to perform network entity lifecycle management (e.g., to instantiate virtualized network entities 105). Such virtualized network entities 105 may include, but are not limited to, CU 160-a, DU 165-a, RU 170-a, and near-RT RIC 175-b. In some specific implementations, the SMO 180-a may communicate with components configured according to a 4G RAN (e.g., via an O1 interface). Additionally or alternatively, in some implementations, the SMO 180-a can communicate directly with one or more RUs 170-a via an O1 interface. The SMO 180-a can also include a non-RT RIC 175-a configured to support the functionality of the SMO 180-a.

[0091] The non-RT RIC 175-a may be configured to include logic functions that implement non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) or machine learning (ML) workflows (including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 175-b). The non-RT RIC 175-a may be coupled to or communicate with the near-RT RIC 175-b (e.g., via an A1 interface). The near-RT RIC 175-b may be configured to include logic functions that implement near real-time control and optimization of RAN elements and resources via data collection and actions on an interface connecting one or more CUs 160-a, one or more DUs 165-a, or both, and the O-eNB 210 to the near-RT RIC 175-b (e.g., via an E2 interface).

[0092] In some examples, in order to generate an AI / ML model to be deployed in the near-RT RIC 175-b, the non-RT RIC 175-a may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 175-b and may be received from a non-network data source or from a network function at the SMO 180-a or the non-RT RIC 175. In some examples, the non-RT RIC 175-a or the near-RT RIC 175-b may be configured to tune RAN behavior or performance. For example, the non-RT RIC 175-a may monitor long-term trends and patterns of performance and employ an AI model or ML model to perform corrective actions through the SMO 180-a (e.g., via reconfiguration of O1) or via the generation of a RAN management policy (such as an A1 policy).

[0093] Some UEs 115 or network entities 105 in the wireless communication system 100 and the wireless communication system 200 may be configured to adopt an operating mode that reduces power consumption, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not transmit and receive concurrently). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power saving techniques for the network entity 105 or UE 115 include entering a power saving deep sleep mode when not engaged in active communications, operating over a limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some network entities 105 or UE 115 may be configured to operate using a narrowband protocol type that is associated with a defined portion or range (e.g., a subcarrier or resource block (RB) set) within a carrier, within a guard band of a carrier, or outside a carrier.

[0094] As a supplement or alternative to half-duplex mode, some network entities 105 or UE 115 may support full-duplex mode. Full-duplex mode may refer to a mode that supports bidirectional communication via simultaneous transmission and reception. This bidirectional communication may be referred to as full-duplex communication. Full-duplex communication is a technology that can theoretically double the link capacity by enabling a radio network node to transmit and receive simultaneously on the same frequency and time resources. Full-duplex breaks the half-duplex operation constraints in which transmission and reception are different in time or frequency. Full-duplex network nodes, such as network entities 105, UE 115 or both in a cellular network, can use the same radio resources to communicate with two half-duplex panels simultaneously in uplink and downlink. For example, UE 115 may send uplink transmissions from one panel at UE 115, and UE 115 may receive downlink transmissions at another panel at UE 115. Similarly, the network entity 105 may receive uplink transmissions at one panel at the network entity 105 , and the network entity 105 may send downlink transmissions from another panel at the network entity 105 .

[0095] Thus, a device equipped with multiple TRPs that support the ability to transmit and receive simultaneously using the same time-frequency radio resources (e.g., different associated aspects of uplink or downlink transmissions and processes in frequency range 2 (FR2)) may be referred to as a full-duplex capable device (e.g., a full-duplex UE 115 or a full-duplex network entity 105). The device may also be capable of operating in full-duplex mode and retreating to half-duplex mode. In some cases, full-duplex capability may be conditioned on beam separation and other factors (e.g., self-interference between downlink and uplink and clutter echoes at the device). However, full-duplex communications may provide latency reduction (e.g., because it is possible to receive downlink signals in uplink-only time slots, which may achieve latency savings), spectral efficiency enhancement (e.g., per cell or per UE 115), more efficient resource utilization, and coverage enhancement with continuous uplink or downlink transmission or repetition.

[0096] Figure 3An example of full-duplex communication 300 according to one or more aspects of the present disclosure is illustrated. In a first example 300-a, a UE 115 may support full-duplex communication (e.g., operate in full-duplex mode), and the UE 115 may receive a downlink signal from a first network entity 105 (e.g., a cell or a transmit and receive point (TRP)) and send an uplink signal to a second network entity 105. The first example 300-a may be an example of multi-TRP communication of a UE 115 using full-duplex operation. For the first example 300-a, full-duplex operation may be disabled at the network entity. In a second example 300-b, the network entity 105 may support full-duplex communication (e.g., operate in full-duplex mode), and the network entity 105 may send a downlink signal to a first UE 115 and receive an uplink signal from a second UE 115. In the second example 300-b, full-duplex operation may be enabled at the network entity 105 and may be disabled at the UE 115 (e.g., for IAB). In the third example 300-c, both the network entity 105 and the UE 115 may support full-duplex communication (e.g., operate in full-duplex mode). Some communication networks may use a combination of the illustrated examples (e.g., the network entity 105 may support full-duplex to different UEs, where at least one UE supports full-duplex operation with different network entities). The network entity 105 may send downlink signals to the UE 115 and receive uplink signals from the UE 115, and the UE 115 may receive downlink signals from the network entity 105 and send uplink signals to the network entity 105. In the third example 300-c, full-duplex operation may be enabled at the network entity 105 and the UE 115.

[0097] Figure 4 An example of a CLI 400 in accordance with one or more aspects of the present disclosure is illustrated. Communications between a network entity 105-b and one or more UEs 115 may interfere with communications between a network entity 105-a and one or more other UEs 115. The network entity 105-b may be referred to as an aggressor, and the network entity 105-a may be referred to as a victim.

[0098] In some aspects, it may be appropriate for the wireless communication system to support techniques for managing inter-network entity interference or CLI. For example, if the victim network entity 105 measures strong inter-network entity interference, it may be appropriate to support inter-network entity messaging to mitigate inter-network entity interference. Inter-network entity interference may occur when one or more network entities 105 support full-duplex communication (e.g., where downlink transmissions from network entity 105-b may interfere with uplink transmissions to network entity 105-a). In addition, inter-network entity interference may occur when network entity 105 operates in half-duplex mode with flexible or misaligned TDD (e.g., a flexible TDD session). For example, inter-network entity interference may occur when network entity 105-b sends a downlink transmission in the same time slot or time resource in which network entity 105-a receives an uplink transmission.

[0099] Techniques described herein provide signaling that supports mitigation of interference between network entities. In one aspect, for different temporal behaviors, it may be appropriate to define configuration signaling (e.g., periodic, semi-persistent, or aperiodic signaling) to configure a transmitting network entity to transmit a reference signal (e.g., using a reference signal configuration) and to configure a receiving network entity 105 to receive a reference signal (e.g., using a reference signal configuration) and report CLI measurements (e.g., using an interference reporting configuration).

[0100] The signaling configurations for facilitating interference measurement between network entities may be used when the interference between network entities is high or exceeds a certain threshold. For example, these signaling configurations may be used when there is interference between network entities 105 supporting full-duplex communication or network entities 105 supporting half-duplex communication (e.g., interference between communications in different directions). In addition, the configurations may be added for CU to CU Xn signaling (e.g., if the base station or DU is under or served by different CUs) or for base station to CU or DU to CU F1 signaling (e.g., if the base station or DU is under or served by the same CU). For example, the configurations may support messaging between network entities and may signal between network entities (e.g., DU to CU or CU to CU signaling).

[0101] Figure 5 An example of a wireless communication system 500 supporting inter-access network interference measurement and reporting configuration according to one or more aspects of the present disclosure is illustrated. The wireless communication system 500 includes a CU or an organization, administration, and maintenance (OAM) entity 505, which may be a reference Figures 1 to 4 The wireless communication system 500 also includes DU 510-a and DU 510-b, which may be reference Figures 1 to 4An example of a DU or network entity 105 as described. Although the wireless communication system 500 illustrates that DU 510-a and DU 510-b are served by (e.g., connected to or configured by) a CU or OAM 505 (e.g., the same CU), the same or similar techniques may be applied if DU 510-a and DU 510-b are served by different CUs or OAMs. The wireless communication system 500 may implement various aspects of the wireless communication system 100. For example, the wireless communication system 500 may support effective techniques for facilitating CLI measurements and using these CLI measurements to make scheduling decisions to improve throughput. Each DU in DU 510 may include one or more RUs or be coupled to one or more RUs. For example, transmissions performed by DU 510 may be sent by RU functionality included in the DU, or by one or more RUs coupled to DU 510.

[0102] The techniques described herein provide for configuring the network entity 105 to send a reference signal for a CLI measurement, receive a reference signal for a CLI measurement, or report a CLI measurement. The CU or OAM 505 may send an indication of a configuration 515 for sending a reference signal for a CLI measurement to the DU 510-b. The CU or OAM 505 may also send an indication of a configuration 520 for monitoring or receiving a reference signal for a CLI measurement to the DU 510-a, and the CU or OAM 505 may send another indication of a configuration 525 for reporting a CLI measurement or reporting based on the CLI measurement to the DU 510-a. The DU 510-b may then send a reference signal 530, and the DU 510-a may receive the reference signal 530, perform a CLI measurement on the reference signal 530, and report the CLI measurement (e.g., to the CU or OAM 505). The reference signal sent by DU 510-b can be a channel state information (CSI) reference signal (CSI-RS), a synchronization signal block (SSB), or other downlink reference signal.

[0103] Configuration 515 may be referred to as an inter-network entity interference measurement configuration (e.g., measurement reference signal resource configuration), an RS-Config information element (IE), or an inter-network entity RS-Config IE. Configuration 515 may be similar to a configuration for configuring a sounding reference signal (SRS) transmission from UE 115. Configuration 515 may define a list of reference signal resources and a list of reference signal resource sets, and each resource set may define a reference signal resource set. The CU or OAM 505 may use a configured non-periodic reference signal resource trigger (e.g., Layer 1 (L1) downlink control information (DCI)) to trigger the transmission of the reference signal resource set. Configuration 515 may be different from a configuration for DU 510-b to send a reference signal to one or more UEs 115 for access link management or beam management. In addition, the reference signal 530 sent by DU 510-b for inter-network entity interference measurement may partially overlap, completely overlap, or not overlap with the reference signal sent by DU 510-b for access link management or beam management.

[0104] In some examples, the configuration 515 may include multiple fields or other IEs that provide information or parameters for DU 510-b to use to send reference signal 530. For example, the configuration 515 may include (e.g., in the RS-Config field) an RS-ResourceSetToReleaseList field, an RS-ResourceSetToAddModList field, an RS-ResourceToReleaseList field, an RS-ResourceToAddModList field, or a tpc-Accumulation field (e.g., providing transmit power control (TPC) information). The configuration 515 may also include (e.g., in the RS-ResourceSet field) an RS-ResourceSetId field, an RS-ResourceIdList field, or a resourceType field. In some examples, resourceType may indicate that DU 510-b will send reference signal 530 non-periodically on the corresponding resource set, and configuration 515 may also include an aperiodicRS-ResourceTrigger field, a csi-RS / SSB field (e.g., indicating a resource ID of a channel state information (CSI) reference signal (CSI-RS) or synchronization signal block (SSB) corresponding to a beam used by DU510-b to send reference signal 530), a slotOffset field, and an aperiodicRS-ResourceTriggerList field. In some examples, resourceType may indicate that DU 510-b will send reference signal 530 semi-persistently on the corresponding resource set, and configuration 515 may also indicate associatedCSI-RS / SSB. In some examples, resourceType may indicate that DU 510-b will send reference signal 530 periodically on the corresponding resource set, and configuration 515 may also indicate associatedCSI-RS / SSB.

[0105] Configuration 515 may also include (e.g., in the RS-Resource field) RS-ResourceId, nrofRS-Ports field (e.g., indicating the number of reference signal ports), ptrs-PortIndex field, resourceMapping field (e.g., including startPosition field, nrofSymbols field and repetitionFactor field), freqDomainPosition field, freqDomainShift field, resourceType field, sequenceId field and TCI-State field. Similar to the resourceType field in the RS-ResourceSet field of configuration 515, the resourceType field in the RS-Resource field may indicate that DU 510-b will send reference signal 530 on the corresponding resource non-periodically, semi-persistently (e.g., when the configuration 515 may indicate periodicity and offset), or periodically (e.g., when the configuration 515 may indicate periodicity and offset).

[0106] Configuration 520 may also be referred to as an inter-network entity interference measurement configuration (e.g., measurement reference signal resource configuration), an RS-Config information element (IE), or an inter-network entity RS-Config IE. The CU or OAM 505 may use configuration 520 to configure DU 510-a to monitor or receive a reference signal from DU 510-b. In some cases, configuration 520 may be similar to an access link management configuration for DU 510-a to monitor a reference signal (e.g., SRS) from UE 115. In such cases, the CU or OAM 505 may add quasi-co-location (QCL) information to the access link management configuration to generate configuration 520. For example, the CU or OAM 505 may add QCL information indicating one or more beams used by DU 510-a to receive reference signal 530 (e.g., adding receive QCL information in an SRS resource for CLI for the UE to perform CLI measurements using the indicated receive beams). One or more parameters in configuration 520 may be used to configure DU 510 - a for both L1 and Layer 3 (L3) CLI measurements, but using separately configured resources.

[0107] In some examples, configuration 520 may include added QCL information, a receive panel identifier (e.g., identifying a panel used by DU510-a to receive reference signal 530), RS-ResourceConfigCLI field, RS-Resource field, RS-SCS SubcarrierSpacing field, qcl-info SEQUENCE(SIZE(1..maxNrofAP-CSI-RS-ResourcesPerSet))of TCI-StateId field. Additionally or alternatively, configuration 520 may include (e.g., in the RS-ResourceConfigInter-gNBCLI field) an rs-ResourceId RS-ResourceId field, an rs-SCSSubcarrierSpacing field, a startPRB INTEGER(0..2169) field, an nrofPRBs INTEGER(4..maxNrofPhysicalResourceBlocksPlus1) field, a startPosition INTEGER(0..13) field, an nrofSymbols INTEGER(1..14) field, an rssi-PeriodicityAndOffset field, an RS-PeriodicityAndOffset field, or a qcl-info SEQUENCE(SIZE(1..maxNrofAP-RS-ResourcesPerSet))OF TCI-StateId field.

[0108] Configuration 525 may also be referred to as an inter-network entity interference reporting configuration and may be the same as configuration 520, signaled together with configuration 520, or signaled separately from configuration 520. Configuration 525 may include periodic, aperiodic, semi-persistent, and eventTriggered fields corresponding to selections of PeriodicalReportConfig, AperiodicalReportConfig, semi-persistentReportConfig, EventTriggerConfig fields, respectively.

[0109] In one example, configuration 525 may configure DU 510-a to report CLI measurements periodically (e.g., either event-triggered or event-based). In this example, configuration 525 may include an Inter-gNBCLI-EventTriggerConfig field, which may include an eventId field, a reportInterval field, a reportAmount field, and a maxReportInter-gNBCLI field. The eventId field may include an eventI1 field, which may include an i1-Threshold field, a reportOnLeave field, a hysteresis field, and a timeToTrigger field. Configuration 525 may also include an Inter-gNBCLI-PeriodicalReportConfig field, which may include a reportInterval field, a reportAmount field, a reportQuantityInter-gNBCLI field, and a maxReportInter-gNBCLI field. Configuration 525 may also include a MeasTriggerQuantityInter-gNBCLI field, which may include an srs-RSRP field and an Inter-gNBCLI-RSSI field. Configuration 525 may also include a MeasReportQuantityInter-gNBCLI field.

[0110] In another example, the configuration 525 may configure the DU 510-a to report CLI measurements aperiodically. In this example, the configuration 525 may define the inter-gNB-AperiodicTriggerStateList IE. The inter-gNB-AperiodicTriggerStateList IE may include an ASN1START field, a TAG-CSI-APERIODICTRIGGERSTATELIST-START field, an Inter-gNB-AperiodicTriggerStateList field (e.g., defining a trigger state linked to one or more report configuration identifiers for measuring reference signal resource sets between network entities), an Inter-gNB-AperiodicTriggerState field (e.g., including an associatedReportConfigInfoList field and an AssociatedReportConfigInfo field), and an Inter-gNB-AssociatedReportConfigInfo field (e.g., including a reportConfigId field and an RS-Resource field).

[0111] In yet another example, the configuration 525 may configure the DU 510-a to semi-persistently report CLI measurements. In this example, the CU or OAM 505 and the DU 510-a may support a medium access control (MAC) control element (MAC-CE) to activate or deactivate semi-persistent network entity inter-CLI reporting on the PUCCH, which is linked to the ReportConfigId for the inter-gNB reference signal resource set. Therefore, the wireless communication system 500 may support activation or deactivation of semi-persistent inter-gNB reporting on the PUCCH via over-the-air (OTA) signaling (e.g., MAC-CE). That is, the wireless communication system 500 may add a MAC-CE activation or deactivation of semi-persistent inter-gNB CLI reporting on the PUCCH via OTA, which is linked to the ReportConfigId for the inter-gNB reference signal resource set. The CU or OAM505 may generate a MAC-CE to activate or deactivate reporting of CLI measurements so that the MAC-CE is the same as the MAC-CE from the UE 115. Additionally or alternatively, the wireless communication system 500 may define backhaul messaging for inter-gNB semi-persistent CLI measurement activation or deactivation request. The CU or OAM 505 may then send backhaul messaging to the DU 510-a to trigger the DU 510-a to report CLI measurements.

[0112] Figure 6 An example of a process flow 600 for supporting inter-access network interference measurement and reporting configuration according to one or more aspects of the present disclosure is illustrated. The process flow 600 includes a CU or OAM 605, which may be a reference Figures 1 to 5 The process flow 600 also includes DU 610-a and DU 610-b, which may be reference Figures 1 to 5 An example of a DU or network entity. Figure 6 In the example of , DU 610-a and DU 610-b may be served by CU or OAM 605 (e.g., the same CU). Process flow 600 may implement aspects of wireless communication system 500. For example, process flow 600 may support efficient techniques for facilitating CLI measurements and using these CLI measurements to make scheduling decisions to improve throughput.

[0113] In the following description of process flow 600, signaling exchanged between CU or OAM 605, DU 610-a, and DU 610-b may be exchanged in an order different from the example order shown, or operations performed by CU or OAM 605, DU 610-a, and DU 610-b may be performed in a different order or at a different time. Some operations may also be omitted from process flow 600, and other operations may be added to process flow 600.

[0114] At 615, the CU or OAM 605 may send an indication of a configuration for sending reference signals for CLI measurements at DU 610-a, and DU 610-b may receive the indication. The CU or OAM 605 may also send an indication of another configuration for sending reference signals to one or more UEs 115 for access link management or beam management, and DU 610-b may receive the indication. The reference signals for access link management or beam management may completely overlap, partially overlap, or not overlap with the reference signals for CLI measurements. Alternatively, DU 610-b may be configured to send reference signals for access link management or beam management, and DU 610-a may be configured to receive reference signals for access link measurement or beam management, perform CLI measurements on these reference signals, and report the CLI measurements (e.g., to the CU or OAM 605).

[0115] At 620, the CU or OAM 605 may send an indication of a configuration for monitoring a reference signal from DU 610-b for CLI measurement at DU 610-a, and DU 610-a may receive the indication. At 625, the CU or OAM 605 may send an indication of a configuration for sending a report (e.g., based on CLI measurement) to the CU or OAM 605, and DU 610-b may receive the indication. The configuration for sending a report may be referred to as a report configuration and may indicate a type of report, which may be periodic, aperiodic, or semi-persistent. In some examples, DU 610-a may receive an indicator of one or more events in the report configuration that triggers sending a report to the CU or OAM 605. At 630, DU 610-b may send a reference signal for CLI measurement, and DU 610-a may receive the reference signal for CLI measurement.

[0116] At 635, DU 610-a may perform CLI measurement on the reference signal received from DU 610-b. At 640, DU 610-a may report to CU or OAM 605 based on the CLI measurement, and CU or OAM 605 may receive the CLI measurement from DU 610-a. In some examples, the format of the configuration for monitoring the reference signal for CLI measurement may be associated with RSRP measurement, and DU 610-a may perform RSRP measurement on the reference signal from DU 610-b based on receiving the configuration with the format associated with RSRP measurement. In some examples, the format of the configuration for monitoring the reference signal may be associated with RSSI measurement, and DU 610-a may perform RSSI measurement on the reference signal received from DU 610-b based on receiving the configuration with the format associated with RSSI measurement.

[0117] In some examples, the CU or OAM 605 may send a trigger to receive a reference signal for CLI measurement, perform CLI measurement, or send a report based on the CLI measurement, and the DU 610-a may receive the trigger to receive a reference signal for CLI measurement, perform CLI measurement, or send a report based on the CLI measurement. In some examples, the DU 610-a may receive a MAC-CE from the DU 610-b, which triggers the DU 610-a to receive a reference signal for CLI measurement, perform CLI measurement, or send a report based on the CLI measurement.

[0118] In some examples, in a configuration for sending a reference signal for CLI measurement, the CU or OAM 605 may send a QCL indication of one or more beams or beam weights for DU 610-b to use to send a reference signal for CLI measurement, and DU 610-b may receive the QCL indication. In addition, in a configuration for monitoring or receiving a reference signal for CLI measurement, the CU or OAM 605 may send a QCL indication of one or more beams for DU 610-a to use to receive a reference signal for CLI measurement, and DU 610-a may receive the QCL indication. Then DU 610-b may send a reference signal based on the QCL indication received in the configuration for sending a reference signal for CLI measurement, and DU 610-a may receive the reference signal based on the QCL indication received in the configuration for monitoring or receiving a reference signal for CLI measurement.

[0119] In some examples, the CU or OAM 605 may send an indication of resources mapped to each of the one or more beams (e.g., corresponding resources on which one or more reference signals for CLI measurement are to be sent using the corresponding beam), and the DU 610-b may receive the indication. In addition, the DU 610-a may identify resources mapped to each of the one or more beams from the configuration for receiving the reference signal. For example, the CU or OAM 605 may send an indication of resources mapped to each of the one or more beams, and the DU 610-a may receive the indication. The DU 610-b may then send a reference signal on the corresponding resource using each of the one or more beams indicated in the configuration for sending the reference signal (e.g., the beam mapped to the corresponding resource), and the DU 610-a may receive the reference signal on the corresponding resource using each of the one or more beams indicated in the configuration for receiving the reference signal.

[0120] In some examples, the CU or OAM 605 may send an identifier of a resource set on which a reference signal for CLI measurement is to be sent, and the DU 610-b may receive the identifier. In addition, in a configuration for monitoring a reference signal, the CU or OAM 605 may send an identifier of a resource set on which a reference signal is to be monitored, and the DU 610-a may receive the identifier. Then the DU 610-b may send a reference signal on a resource set indicated (e.g., by an identifier) ​​in the configuration for sending a reference signal and the configuration for receiving a reference signal, and the DU 610-a may receive the reference signal. In some examples, the configuration for sending a reference signal for CLI measurement, the configuration for monitoring a reference signal, or both may include an indication of a type of resource set, which is periodic, aperiodic, or semi-persistent. In some examples, the configuration for sending a reference signal for CLI measurement, the configuration for monitoring a reference signal, or both may include an indication of a starting position, a number of symbols, or a repetition factor of a resource set.

[0121] At 645, the CU or OAM 605 may schedule communications at DU 610-a and DU 610-b based on the CLI measurements. For example, the CU or OAM 605 may send a scheduling message to schedule communications at DU 610-a (e.g., between DU 610-a and one or more UEs 115) based on the CLI measurements, and DU 610-a may receive the scheduling message. In addition, the CU or OAM 605 may send a scheduling message to schedule communications at DU 610-b (e.g., between DU 610-b and one or more UEs 115) based on the CLI measurements, and DU 610-b may receive the scheduling message.

[0122] Figure 7 An example of a process flow 700 for supporting inter-access network interference measurement and reporting configuration according to one or more aspects of the present disclosure is illustrated. The process flow 700 includes a CU or OAM 705-a and a CU or OAM 705-b, which may be reference Figures 1 to 5 The process flow 700 also includes DU 710-a and DU 710-b, which may be reference Figures 1 to 5 An example of a DU or network entity 105 is shown. Figure 7In the example of , DU 710-a may be served by CU or OAM 705-a, and DU 710-b may be served by CU or OAM 705-b (e.g., DU 710-a and DU 710-b may be served by different CUs or OAMs). Process flow 700 may implement aspects of wireless communication system 500. For example, process flow 700 may support efficient techniques for facilitating CLI measurements and using these CLI measurements to make scheduling decisions to improve throughput.

[0123] In the following description of process flow 700, signaling exchanged between CU or OAM 705-a, CU or OAM 705-b, DU 710-a, and DU 710-b may be exchanged in an order different from the example order shown, or operations performed by CU or OAM 705-a, CU or OAM 705-b, DU 710-a, and DU 710-b may be performed in a different order or at a different time. Some operations may also be omitted from process flow 700, and other operations may be added to process flow 700.

[0124] At 715, the CU or OAM 705-a may send an indication of a configuration for sending reference signals for CLI measurements at the DU 710-a, and the DU 710-b may receive the indication. The CU or OAM 705-a may also send an indication of another configuration for sending reference signals to one or more UEs 115 for access link management or beam management, and the DU 710-b may receive the indication. The reference signals for access link management or beam management may completely overlap, partially overlap, or not overlap with the reference signals for CLI measurements. Alternatively, the DU 710-b may be configured to send reference signals for access link management or beam management, and the DU 710-a may be configured to receive reference signals for access link measurement or beam management, perform CLI measurements on these reference signals, and report the CLI measurements (e.g., to the CU or OAM 705-a).

[0125] At 720, the CU or OAM 705-a may send an indication of a configuration for monitoring a reference signal from DU 710-b for CLI measurement at DU 710-a, and DU 710-a may receive the indication. At 725, the CU or OAM 705-a may send an indication of a configuration for sending a report (e.g., based on CLI measurement) to the CU or OAM 705-a, and DU 710-b may receive the indication. The configuration for sending a report may be referred to as a report configuration and may indicate a type of report, which may be periodic, non-periodic, or semi-persistent. In some examples, DU 710-a may receive an indicator of one or more events in the report configuration that triggers sending a report to the CU or OAM 705-a. At 730, DU 710-b may send a reference signal for CLI measurement, and DU 710-a may receive the reference signal for CLI measurement.

[0126] At 735, DU 710-a may perform CLI measurement on the reference signal received from DU 710-b. At 740, DU 710-a may report to CU or OAM 705-a based on the CLI measurement, and CU or OAM 705-a may receive the CLI measurement from DU 710-a. In some examples, the format of the configuration for monitoring the reference signal for CLI measurement may be associated with RSRP measurement, and DU 710-a may perform RSRP measurement on the reference signal from DU 710-b based on receiving the configuration with the format associated with RSRP measurement. In some examples, the format of the configuration for monitoring the reference signal may be associated with RSSI measurement, and DU 710-a may perform RSSI measurement on the reference signal received from DU 710-b based on receiving the configuration with the format associated with RSSI measurement.

[0127] In some examples, the CU or OAM 705-a may send a trigger to receive a reference signal for CLI measurement, perform CLI measurement, or send a report based on the CLI measurement, and the DU 710-a may receive the trigger to receive a reference signal for CLI measurement, perform CLI measurement, or send a report based on the CLI measurement. In some examples, the DU 710-a may receive a MAC-CE from the DU 710-b, which triggers the DU 710-a to receive a reference signal for CLI measurement, perform CLI measurement, or send a report based on the CLI measurement.

[0128] In some examples, in a configuration for sending a reference signal for CLI measurement, the CU or OAM 705-b may send a QCL indication of one or more beams or beam weights for DU 710-b to use to send a reference signal for CLI measurement, and the DU 710-b may receive the QCL indication. In addition, in a configuration for monitoring or receiving a reference signal for CLI measurement, the CU or OAM 705-a may send a QCL indication of one or more beams for DU 710-a to use to receive a reference signal for CLI measurement, and the DU 710-a may receive the QCL indication. Then, the DU 710-b may send a reference signal based on the QCL indication received in the configuration for sending a reference signal for CLI measurement, and the DU 710-a may receive the reference signal based on the QCL indication received in the configuration for monitoring or receiving a reference signal for CLI measurement.

[0129] In some examples, the CU or OAM 705-b may send an indication of resources mapped to each of the one or more beams (e.g., corresponding resources on which one or more reference signals for CLI measurement are to be sent using the corresponding beam), and the DU 710-b may receive the indication. In addition, the DU 710-a may identify resources mapped to each of the one or more beams from a configuration for receiving a reference signal. For example, the CU or OAM 705-a may send an indication of resources mapped to each of the one or more beams, and the DU 710-a may receive the indication. The DU 710-b may then send a reference signal on the corresponding resource using each of the one or more beams indicated in the configuration for sending a reference signal (e.g., a beam mapped to the corresponding resource), and the DU 710-a may receive the reference signal on the corresponding resource using each of the one or more beams indicated in the configuration for receiving a reference signal.

[0130] In some examples, the CU or OAM 705-b may send an identifier of a resource set on which a reference signal for CLI measurement is to be sent, and the DU 710-b may receive the identifier. In addition, in a configuration for monitoring a reference signal, the CU or OAM 705-a may send an identifier of a resource set on which a reference signal is to be monitored, and the DU 710-a may receive the identifier. Then the DU 710-b may send a reference signal on a resource set indicated (e.g., by an identifier) ​​in the configuration for sending a reference signal and the configuration for receiving a reference signal, and the DU 710-a may receive the reference signal. In some examples, the configuration for sending a reference signal for CLI measurement, the configuration for monitoring a reference signal, or both may include an indication of a type of resource set, which is periodic, aperiodic, or semi-persistent. In some examples, the configuration for sending a reference signal for CLI measurement, the configuration for monitoring a reference signal, or both may include an indication of a starting position, a number of symbols, or a repetition factor of a resource set.

[0131] At 745, the CU or OAM 705-a may coordinate with the CU or OAM 705-b to schedule communications at the DU 710-a and the DU 710-b based on the CLI measurements. For example, the CU or OAM 705-a may schedule communications at the DU 710-a based on the CLI measurements, and the CU or OAM 705-a may send the CLI measurements to the CU or OAM 705-b. The CU or OAM 705-b may then schedule communications at the DU 710-b based on the CLI measurements. In addition to coordinating to schedule communications at the DU 710-a and the DU 710-b, the CU or OAM 705-a and the CU or OAM 705-b may also coordinate to trigger the DU 710-b to send a reference signal, trigger the DU 710-a to receive a reference signal, or trigger the DU 710-a to report the CLI measurements (e.g., or report based on the CLI measurements). For example, the CU or OAM 705-a may send information to the CU or OAM 705-b to trigger the DU 710-b to send a reference signal. Additionally or alternatively, the CU or OAM 705-b may send information to the CU or OAM 705-a to trigger the DU 710-a to receive the reference signal, perform CLI measurements on the reference signal, and report the CLI measurements to the CU or OAM 705-a.

[0132] Figure 8A block diagram 800 of a device 805 supporting inter-access network interference measurement and reporting configuration according to one or more aspects of the present disclosure is shown. The device 805 may be an example of aspects of the network entity 105 as described herein. The device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. The device 805 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0133] The receiver 810 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of the device 805. In some examples, the receiver 810 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 810 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0134] The transmitter 815 may provide means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 805. For example, the transmitter 815 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 815 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 815 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 815 and the receiver 810 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0135] The communication manager 820, the receiver 810, the transmitter 815, or various combinations thereof or various components thereof may be examples of means for performing various aspects of inter-access network interference measurement and reporting configuration as described herein. For example, the communication manager 820, the receiver 810, the transmitter 815, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0136] In some examples, the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting means for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0137] Additionally or alternatively, in some examples, the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting means for performing the functions described in the present disclosure).

[0138] In some examples, the communication manager 820 can be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 810, the transmitter 815, or both. For example, the communication manager 820 can receive information from the receiver 810, transmit information to the transmitter 815, or be integrated with the receiver 810, the transmitter 815, or both to obtain information, output information, or perform various other operations as described herein.

[0139] According to examples as disclosed herein, the communication manager 820 may support wireless communications at a first network entity. For example, the communication manager 820 may be configured to or otherwise support a means for receiving, from a second network entity, an indication of a configuration for sending a reference signal for interference measurement at a third network entity. The communication manager 820 may be configured to or otherwise support a means for sending a reference signal based on the configuration. The communication manager 820 may be configured to or otherwise support a means for receiving, from a second network entity, a scheduling message for scheduling communications at the first network entity based on sending the reference signal.

[0140] Additionally or alternatively, according to examples as disclosed herein, the communication manager 820 may support wireless communications at the first network entity. For example, the communication manager 820 may be configured to or otherwise support a component for receiving, from the second network entity, an indication of a configuration for monitoring a reference signal from a third network entity for interference measurement at the first network entity. The communication manager 820 may be configured to or otherwise support a component for receiving one or more of the reference signals sent by the third network entity for interference measurement. The communication manager 820 may be configured to or otherwise support a component for performing interference measurement on one or more of the reference signals. The communication manager 820 may be configured to or otherwise support a component for sending a report to the second network entity based on performing interference measurement on one or more of the reference signals.

[0141] Additionally or alternatively, according to examples as disclosed herein, the communication manager 820 may support wireless communications at the first network entity. For example, the communication manager 820 may be configured to or otherwise support a component for sending first information associated with a first configuration for sending a reference signal from the second network entity to the third network entity. The communication manager 820 may be configured to or otherwise support a component for sending second information associated with a second configuration for monitoring the reference signal by the third network entity. The communication manager 820 may be configured to or otherwise support a component for sending third information associated with a third configuration for reporting, by the third network entity, interference measurements performed on the reference signal received from the second network entity. The communication manager 820 may be configured to or otherwise support a component for receiving fourth information associated with interference measurements reported by the third network entity based on sending the first information, the second information, and the third information.

[0142] By including or configuring a communication manager 820 according to examples as described herein, a device 805 (e.g., a processor controlling or otherwise coupled to a receiver 810, a transmitter 815, a communication manager 820, or a combination thereof) may support techniques for reducing processing, reducing power consumption, and more efficiently utilizing communication resources. Specifically, the device 805 may support techniques for using configuration signaling to facilitate CLI measurements and scheduling based on CLI measurements. Thus, communications at the device 805 or other devices may be scheduled based on CLI measurements to prevent or mitigate CLI, thereby reducing processing, reducing power consumption, and more efficiently utilizing communication resources due to CLI reduction.

[0143] Fig. 9A block diagram 900 of a device 905 supporting inter-access network interference measurement and reporting configuration according to one or more aspects of the present disclosure is shown. The device 905 may be an example of aspects of the device 805 or the network entity 105 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. The device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0144] The receiver 910 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of the device 905. In some examples, the receiver 910 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 910 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0145] The transmitter 915 may provide a means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 905. For example, the transmitter 915 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 915 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 915 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 915 and the receiver 910 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0146] The device 905 or its various components may be examples of components for performing various aspects of inter-access network interference measurement and reporting configuration as described herein. For example, the communication manager 920 may include a CLI configuration manager 925, a reference signal manager 930, a scheduler 935, a CLI measurement manager 940, a CLI report manager 945, or any combination thereof. The communication manager 920 may be an example of various aspects of the communication manager 820 as described herein. In some examples, the communication manager 920 or its various components may be configured to use or otherwise cooperate with the receiver 910, the transmitter 915, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 920 may receive information from the receiver 910, transmit information to the transmitter 915, or be integrated with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.

[0147] According to examples as disclosed herein, the communication manager 920 may support wireless communication at the first network entity. The CLI configuration manager 925 may be configured as or otherwise support means for receiving, from the second network entity, an indication of a configuration for sending a reference signal for interference measurement at a third network entity. The reference signal manager 930 may be configured as or otherwise support means for sending a reference signal based on the configuration. The scheduler 935 may be configured as or otherwise support means for receiving, from the second network entity, a scheduling message for scheduling communication at the first network entity based on sending the reference signal.

[0148] Additionally or alternatively, according to examples as disclosed herein, the communication manager 920 may support wireless communications at the first network entity. The CLI configuration manager 925 may be configured to or otherwise support a component for receiving, from the second network entity, an indication of a configuration for monitoring a reference signal from a third network entity for interference measurement at the first network entity. The reference signal manager 930 may be configured to or otherwise support a component for receiving one or more of the reference signals sent by the third network entity for interference measurement. The CLI measurement manager 940 may be configured to or otherwise support a component for performing interference measurement on one or more of the reference signals. The CLI report manager 945 may be configured to or otherwise support a component for sending a report to the second network entity based on performing interference measurement on one or more of the reference signals.

[0149] Additionally or alternatively, according to examples as disclosed herein, the communication manager 920 may support wireless communications at the first network entity. The CLI configuration manager 925 may be configured to or otherwise support a component for sending first information associated with a first configuration for sending a reference signal from the second network entity to the third network entity. The CLI configuration manager 925 may be configured to or otherwise support a component for sending second information associated with a second configuration for monitoring the reference signal by the third network entity. The CLI configuration manager 925 may be configured to or otherwise support a component for sending third information associated with a third configuration for reporting, by the third network entity, interference measurements performed on the reference signal received from the second network entity. The CLI reporting manager 945 may be configured to or otherwise support a component for receiving fourth information associated with interference measurements reported by the third network entity based on sending the first information, the second information, and the third information.

[0150] Fig.10 A block diagram 1000 of a communication manager 1020 supporting inter-access network interference measurement and reporting configuration according to one or more aspects of the present disclosure is shown. The communication manager 1020 may be an example of aspects of the communication manager 820, the communication manager 920, or both as described herein. The communication manager 1020 or its various components may be examples of means for performing various aspects of the inter-access network interference measurement and reporting configuration as described herein. For example, the communication manager 1020 may include a CLI configuration manager 1025, a reference signal manager 1030, a scheduler 1035, a CLI measurement manager 1040, a CLI reporting manager 1045, an access link manager 1050, a beam manager 1055, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of the protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0151] According to examples as disclosed herein, the communication manager 1020 may support wireless communication at the first network entity. The CLI configuration manager 1025 may be configured as or otherwise support means for receiving, from the second network entity, an indication of a configuration for sending a reference signal for interference measurement at a third network entity. The reference signal manager 1030 may be configured as or otherwise support means for sending a reference signal based on the configuration. The scheduler 1035 may be configured as or otherwise support means for receiving, from the second network entity, a scheduling message for scheduling communication at the first network entity based on sending the reference signal.

[0152] In some examples, the configuration includes a first configuration, and the reference signal includes a first reference signal set, and the access link manager 1050 may be configured to or otherwise support means for receiving an indication of a second configuration for sending a second reference signal set to one or more user equipment (UE) for access link management or beam management. In some examples, the configuration includes a first configuration, and the reference signal includes a first reference signal set, and the reference signal manager 1030 may be configured to or otherwise support means for sending a second reference signal set to one or more UEs based on the second configuration, wherein the second reference signal set is different from the first reference signal set.

[0153] In some examples, the first set of reference signals partially overlaps with the second set of reference signals.

[0154] In some examples, to support receiving an indication of the configuration, beam manager 1055 may be configured or otherwise support means for receiving a quasi-co-located indication of one or more beams for the first network entity to use to send a reference signal.

[0155] In some examples, to support receiving an indication of the configuration, beam manager 1055 can be configured or otherwise support means for receiving an indication of resources mapped to each of the one or more beams. In some examples, to support receiving an indication of the configuration, reference signal manager 1030 can be configured or otherwise support means for transmitting a reference signal using each of the one or more beams on respective resources mapped to each beam.

[0156] In some examples, receiving an indication of the configuration includes receiving an identifier of a resource set on which to send a reference signal, and sending the reference signal includes sending the reference signal on the resource set based on receiving the configuration.

[0157] In some examples, the configuration includes an indication of a type of resource set, the type of resource set being periodic, aperiodic, or semi-persistent.

[0158] In some examples, receiving an indication of the configuration includes receiving an indication of a starting position of a resource set, a number of symbols, a repetition factor, or a combination thereof.

[0159] In some examples, the first network entity includes a first distributed unit, the second network entity includes a central unit or an operations, administration, and maintenance entity, and the third network entity includes a second distributed unit.

[0160] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1020 may support wireless communications at the first network entity. In some examples, the CLI configuration manager 1025 may be configured to or otherwise support a component for receiving, from the second network entity, an indication of a configuration for monitoring a reference signal from a third network entity for interference measurement at the first network entity. In some examples, the reference signal manager 1030 may be configured to or otherwise support a component for receiving one or more of the reference signals sent by the third network entity for interference measurement. The CLI measurement manager 1040 may be configured to or otherwise support a component for performing interference measurement on one or more of the reference signals. The CLI report manager 1045 may be configured to or otherwise support a component for sending a report to the second network entity based on performing interference measurement on one or more of the reference signals.

[0161] In some examples, the configuration for monitoring a reference signal from a third network entity includes a first configuration, and CLI configuration manager 1025 may be configured as or otherwise support means for receiving, from the second network entity, an indication of a second configuration for sending a report to the second network entity.

[0162] In some examples, the second configuration for sending the report to the second network entity indicates a type of report, which is periodic, aperiodic, or semi-persistent.

[0163] In some examples, receiving the second configuration includes receiving an indicator of one or more events that trigger sending a report to the second network entity.

[0164] In some examples, CLI measurement manager 1040 may be configured or otherwise support means for receiving a trigger from a second network entity to perform interference measurements and sending a report to the second network entity.

[0165] In some examples, CLI measurement manager 1040 may be configured or otherwise support means for receiving a medium access control (MAC) control element from a third network entity that triggers a first network entity to perform interference measurements and send a report to a second network entity.

[0166] In some examples, to support receiving an indication of the configuration, beam manager 1055 may be configured or otherwise support means for receiving a quasi-co-located indication of one or more beams for the first network entity to use to receive a reference signal.

[0167] In some examples, beam manager 1055 can be configured or otherwise support means for identifying resources mapped to each of the one or more beams from the configuration. In some examples, reference signal manager 1030 can be configured or otherwise support means for receiving a reference signal using each of the one or more beams on a corresponding resource mapped to each beam.

[0168] In some examples, to support performing interference measurements, CLI measurement manager 1040 may be configured as or otherwise support components for performing reference signal received power measurements on a reference signal received from a third network entity based on receiving a configuration having a format associated with reference signal received power measurements.

[0169] In some examples, to support performing interference measurements, CLI measurement manager 1040 may be configured as or otherwise support means for performing reference signal strength indicator measurements on a reference signal received from a third network entity based on receiving a configuration having a format associated with reference signal strength indicator measurements.

[0170] In some examples, receiving an indication of the configuration includes receiving an identifier of a resource set to monitor for a reference signal. In some examples, receiving the reference signal includes receiving the reference signal on the resource set based on the identifier of the resource set.

[0171] In some examples, the configuration indicates a type of resource set, which is periodic, aperiodic, or semi-persistent.

[0172] In some examples, the configuration indicates a starting position of a resource set, a number of symbols, a repetition factor, or a combination thereof.

[0173] In some examples, the first network entity includes a first distributed unit, the second network entity includes a central unit or an operations, administration, and maintenance entity, and the third network entity includes a second distributed unit.

[0174] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1020 may support wireless communications at the first network entity. In some examples, the CLI configuration manager 1025 may be configured to or otherwise support a component for sending first information associated with a first configuration for sending a reference signal from the second network entity to the third network entity. In some examples, the CLI configuration manager 1025 may be configured to or otherwise support a component for sending second information associated with a second configuration for monitoring a reference signal by the third network entity. In some examples, the CLI configuration manager 1025 may be configured to or otherwise support a component for sending third information associated with a third configuration for reporting, by the third network entity, interference measurements performed on a reference signal received from the second network entity. In some examples, the CLI reporting manager 1045 may be configured to or otherwise support a component for receiving fourth information associated with interference measurements reported by the third network entity based on sending the first information, the second information, and the third information.

[0175] In some examples, scheduler 1035 may be configured or otherwise support means for scheduling communications at the second network entity and the third network entity based on receiving fourth information associated with interference measurements reported by the third network entity.

[0176] In some examples, to support sending first information, second information, and third information and receiving fourth information, the CLI configuration manager 1025 may be configured as or otherwise support a component for coordinating with a fourth network entity to configure the second network entity to send a reference signal, configure the third network entity to receive the reference signal, and configure the third network entity to report interference measurements performed on the reference signal.

[0177] In some examples, scheduler 1035 may be configured or otherwise support means for coordinating with a fourth network entity to schedule communications at the second network entity and the third network entity based on receiving fourth information associated with interference measurements reported by the third network entity.

[0178] In some examples, the first network entity includes a central unit or an operations, administration, and maintenance entity, the second network entity includes a first distributed unit, and the third network entity includes a second distributed unit.

[0179] Fig.11A diagram of a system 1100 including a device 1105 supporting inter-access network interference measurement and reporting configuration according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of a device 805, a device 905, or a network entity 105 as described herein, or include components thereof. The device 1105 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1105 may include components that support output and acquisition of communications, such as a communication manager 1120, a transceiver 1110, an antenna 1115, a memory 1125, a code 1130, and a processor 1135. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1140).

[0180] The transceiver 1110 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, the transceiver 1110 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1110 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1105 may include one or more antennas 1115, which may be capable of sending or receiving wireless transmissions (e.g., concurrently). The transceiver 1110 may also include a modem for modulating a signal, thereby providing a modulated signal for transmission (e.g., via one or more antennas 1115, via a wired transmitter), for receiving a modulated signal (e.g., from one or more antennas 1115, from a wired receiver), and for demodulating a signal. The transceiver 1110 or transceiver 1110 and one or more antennas 1115 or wired interfaces (where applicable) may be examples of transmitter 815, transmitter 915, receiver 810, receiver 910, or any combination thereof or any components thereof as described herein. In some examples, the transceiver may be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0181] The memory 1125 may include RAM and ROM. The memory 1125 may store computer-readable, computer-executable code 1130 including instructions that, when executed by the processor 1135, cause the device 1105 to perform various functions described herein. The code 1130 may be stored in a non-transitory computer-readable medium such as a system memory or another type of memory. In some cases, the code 1130 may not be directly executable by the processor 1135, but (for example, when compiled and executed) may cause the computer to perform the functions described herein. In some cases, the memory 1125 may also include a BIOS, etc., which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0182] The processor 1135 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some cases, the processor 1135 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1135. The processor 1135 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 1125) to enable the device 1105 to perform various functions (e.g., functions or tasks supporting inter-access network interference measurement and reporting configuration). For example, the device 1105 or a component of the device 1105 may include a processor 1135 and a memory 1125 coupled to the processor 1135, and the processor 1135 and the memory 1125 are configured to perform the various functions described herein. Processor 1135 can be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can host functionality (e.g., by executing code 1130) to perform the functions of device 1105.

[0183] In some examples, bus 1140 may support communications of a protocol layer (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1140 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of device 1105, or communications performed between different components of device 1105 that may be co-located or located in different locations (e.g., where device 1105 may refer to a system in which one or more of communication manager 1120, transceiver 1110, memory 1125, code 1130, and processor 1135 may be located in one of the different components or divided between the different components).

[0184] In some examples, communication manager 1120 may manage aspects of communications with core network 130 (e.g., via one or more wired or wireless backhaul links). For example, communication manager 1120 may manage delivery of data communications for client devices such as one or more UEs 115. In some examples, communication manager 1120 may manage communications with other network entities 105 and may include a controller or scheduler for controlling communications with UE 115 in collaboration with other network entities 105. In some examples, communication manager 1120 may support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network entities 105.

[0185] According to examples as disclosed herein, the communication manager 1120 may support wireless communications at a first network entity. For example, the communication manager 1120 may be configured to or otherwise support a means for receiving, from a second network entity, an indication of a configuration for sending a reference signal for interference measurement at a third network entity. The communication manager 1120 may be configured to or otherwise support a means for sending a reference signal based on the configuration. The communication manager 1120 may be configured to or otherwise support a means for receiving, from a second network entity, a scheduling message for scheduling communications at the first network entity based on sending the reference signal.

[0186] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1120 may support wireless communications at the first network entity. For example, the communication manager 1120 may be configured to or otherwise support a component for receiving, from the second network entity, an indication of a configuration for monitoring a reference signal from a third network entity for interference measurement at the first network entity. The communication manager 1120 may be configured to or otherwise support a component for receiving one or more of the reference signals sent by the third network entity for interference measurement. The communication manager 1120 may be configured to or otherwise support a component for performing interference measurement on one or more of the reference signals. The communication manager 1120 may be configured to or otherwise support a component for sending a report to the second network entity based on performing interference measurement on one or more of the reference signals.

[0187] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1120 may support wireless communications at the first network entity. For example, the communication manager 1120 may be configured to or otherwise support a component for sending first information associated with a first configuration for sending a reference signal from the second network entity to the third network entity. The communication manager 1120 may be configured to or otherwise support a component for sending second information associated with a second configuration for monitoring the reference signal by the third network entity. The communication manager 1120 may be configured to or otherwise support a component for sending third information associated with a third configuration for reporting, by the third network entity, interference measurements performed on the reference signal received from the second network entity. The communication manager 1120 may be configured to or otherwise support a component for receiving fourth information associated with interference measurements reported by the third network entity based on sending the first information, the second information, and the third information.

[0188] By including or configuring the communication manager 1120 according to the examples described herein, the device 1105 can support techniques for reducing processing, reducing power consumption, and more efficiently utilizing communication resources. Specifically, the device 1105 can support techniques for using configuration signaling to facilitate CLI measurements and scheduling based on CLI measurements. Thus, communications at the device 1105 or other devices can be scheduled based on CLI measurements to prevent or mitigate CLI, thereby reducing processing, reducing power consumption, and more efficiently utilizing communication resources due to CLI reduction.

[0189] In some examples, the communication manager 1120 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1110, one or more antennas 1115 (e.g., where applicable), or any combination thereof. Although the communication manager 1120 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1120 may be supported or performed by the processor 1135, the memory 1125, the code 1130, the transceiver 1110, or any combination thereof. For example, the code 1130 may include instructions that are executable by the processor 1135 to cause the device 1105 to perform various aspects of the inter-access network interference measurement and reporting configuration as described herein, or the processor 1135 and the memory 1125 may be otherwise configured to perform or support such operations.

[0190] Fig.12 A flowchart illustrating a method 1200 for supporting inter-access network interference measurement and reporting configuration according to one or more aspects of the present disclosure is shown. The operations of the method 1200 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1200 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 11In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0191] At 1205, the method may include receiving, from the second network entity, an indication of a configuration for sending a reference signal for interference measurement at a third network entity. The operations of 1205 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1205 may be performed by Fig.10 The CLI configuration manager 1025 executes.

[0192] At 1210, the method may include sending a reference signal based on the configuration. The operations of 1210 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1210 may be performed by reference to Fig.10 The reference signal manager 1030 is used to perform the above operations.

[0193] At 1215, the method may include receiving a scheduling message from the second network entity to schedule communications at the first network entity based on sending the reference signal. The operations of 1215 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1215 may be performed by Fig.10 The scheduler 1035 executes.

[0194] Fig.13 A flowchart illustrating a method 1300 for supporting inter-access network interference measurement and reporting configuration according to one or more aspects of the present disclosure is shown. The operations of the method 1300 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1300 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 11 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0195] At 1305, the method may include receiving, from the second network entity, an indication of a configuration for monitoring a reference signal from a third network entity for interference measurement at the first network entity. The operations of 1305 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1305 may be performed by Fig.10 The CLI configuration manager 1025 executes.

[0196] At 1310, the method may include receiving one or more reference signals sent by a third network entity for interference measurement. The operations of 1310 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1310 may be performed by reference to Fig.10 The reference signal manager 1030 is used to perform the above operations.

[0197] At 1315, the method may include performing interference measurements on one or more of the reference signals. The operations of 1315 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1315 may be performed by Fig.10 The CLI measurement manager 1040 is used to execute.

[0198] At 1320, the method may include sending a report to the second network entity based on performing interference measurements on one or more of the reference signals. The operations of 1320 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1320 may be performed by Fig.10 The CLI report manager 1045 is used to execute.

[0199] Fig.14 A flowchart illustrating a method 1400 for supporting inter-access network interference measurement and reporting configuration according to one or more aspects of the present disclosure is shown. The operations of the method 1400 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1400 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 11 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0200] At 1405, the method may include sending first information associated with a first configuration for sending a reference signal from the second network entity to the third network entity. The operations of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed by Fig.10 The CLI configuration manager 1025 executes.

[0201] At 1410, the method may include sending second information associated with a second configuration for monitoring a reference signal by a third network entity. The operations of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed by Fig.10 The CLI configuration manager 1025 executes.

[0202] At 1415, the method may include sending third information associated with a third configuration for reporting, by the third network entity, interference measurements performed on a reference signal received from the second network entity. The operations of 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed by Fig.10 The CLI configuration manager 1025 executes.

[0203] At 1420, the method may include receiving fourth information associated with interference measurements reported by a third network entity based on sending the first information, the second information, and the third information. The operations of 1420 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1420 may be performed as described in reference to Fig.10 The CLI report manager 1045 is used to execute.

[0204] The following provides an overview of various aspects of the disclosure:

[0205] Aspect 1: A method for wireless communication at a first network entity, the method comprising: receiving an indication of a configuration for sending a reference signal for interference measurement at a third network entity from a second network entity; sending the reference signal based at least in part on the configuration; and receiving a scheduling message from the second network entity for scheduling communication at the first network entity based at least in part on sending the reference signal.

[0206] Aspect 2: A method according to Aspect 1, wherein the configuration includes a first configuration and the reference signal includes a first reference signal set, the method further comprising: receiving an indication of a second configuration for sending a second reference signal set to one or more user equipment (UE) for access link management or beam management; and sending the second reference signal set to the one or more UEs based at least in part on the second configuration, wherein the second reference signal set is different from the first reference signal set.

[0207] Aspect 3: The method according to aspect 2, wherein the first reference signal set partially overlaps with the second reference signal set.

[0208] Aspect 4: The method according to any one of Aspects 1 to 3, wherein receiving the indication of the configuration includes: receiving a quasi-co-location indication of one or more beams for the first network entity to use to send the reference signal.

[0209] Aspect 5: A method according to Aspect 4, wherein receiving the indication of the configuration includes: receiving an indication of resources mapped to each of the one or more beams; and sending the reference signal using each of the one or more beams on the corresponding resources mapped to each beam.

[0210] Aspect 6: A method according to any one of Aspects 1 to 5, wherein receiving the indication of the configuration includes receiving an identifier of a resource set on which the reference signal is to be sent, and sending the reference signal includes sending the reference signal on the resource set at least in part based on receiving the configuration.

[0211] Aspect 7: The method according to aspect 6, wherein the configuration includes an indication of a type of the resource set, the type of the resource set being periodic, aperiodic or semi-persistent.

[0212] Aspect 8: The method according to any one of aspects 6 to 7, wherein receiving the indication of the configuration includes receiving an indication of a starting position, a number of symbols, a repetition factor, or a combination thereof of the resource set.

[0213] Aspect 9: The method according to any one of aspects 1 to 8, wherein the first network entity comprises a first distributed unit, the second network entity comprises a central unit or an operation, administration and maintenance entity, and the third network entity comprises a second distributed unit.

[0214] Aspect 10: A method for performing wireless communications at a first network entity, the method comprising: receiving from a second network entity an indication of a configuration for monitoring reference signals from a third network entity for interference measurement at the first network entity; receiving one or more of the reference signals sent by the third network entity for the interference measurement; performing the interference measurement on the one or more of the reference signals; and sending a report to the second network entity based at least in part on performing the interference measurement on the one or more of the reference signals.

[0215] Aspect 11: The method according to Aspect 10, wherein the configuration for monitoring the reference signal from the third network entity includes a first configuration, and the method further includes: receiving from the second network entity an indication of a second configuration for sending the report to the second network entity.

[0216] Aspect 12: The method according to aspect 11, wherein the second configuration for sending the report to the second network entity indicates a type of the report, the type of the report being periodic, aperiodic or semi-persistent.

[0217] Aspect 13: The method according to any one of aspects 11 to 12, wherein receiving the second configuration comprises receiving an indicator of one or more events that trigger sending the report to the second network entity.

[0218] Aspect 14: The method according to any one of aspects 10 to 13, the method further comprising: receiving a trigger from the second network entity to perform the interference measurement and send the report to the second network entity.

[0219] Aspect 15: According to the method according to any one of Aspects 10 to 14, the method also includes: receiving a medium access control (MAC) control element from the third network entity that triggers the first network entity to perform the interference measurement and send the report to the second network entity.

[0220] Aspect 16: The method according to any one of aspects 10 to 15, wherein receiving the indication of the configuration includes: receiving a quasi-co-location indication of one or more beams for the first network entity to use to receive the reference signal.

[0221] Aspect 17: According to the method of Aspect 16, the method also includes: identifying resources mapped to each of the one or more beams from the configuration; and receiving the reference signal using each of the one or more beams on the corresponding resources mapped to each beam.

[0222] Aspect 18: A method according to any one of Aspects 10 to 17, wherein the format of the configuration for monitoring the reference signal is associated with a reference signal received power measurement, and wherein performing the interference measurement includes: performing a reference signal received power measurement on the reference signal received from the third network entity based at least in part on receiving the configuration having a format associated with the reference signal received power measurement.

[0223] Aspect 19: A method according to any one of Aspects 10 to 18, wherein the format of the configuration for monitoring the reference signal is associated with a reference signal strength indicator measurement, and wherein performing the interference measurement includes: performing a reference signal strength indicator measurement on the reference signal received from the third network entity based at least in part on receiving the configuration having the format associated with the reference signal strength indicator measurement.

[0224] Aspect 20: A method according to any one of Aspects 10 to 19, wherein receiving the indication of the configuration includes receiving an identifier of a resource set to monitor the reference signal; and receiving the reference signal includes receiving the reference signal on the resource set based at least in part on the identifier of the resource set.

[0225] Aspect 21: The method according to aspect 20, wherein the configuration indicates a type of the resource set, the type of the resource set being periodic, aperiodic or semi-persistent.

[0226] Aspect 22: The method according to any one of Aspects 20 to 21, wherein the configuration indicates a starting position, a number of symbols, a repetition factor, or a combination thereof of the resource set.

[0227] Aspect 23: A method according to any one of aspects 10 to 22, wherein the first network entity comprises a first distributed unit, the second network entity comprises a central unit or an operation, administration and maintenance entity, and the third network entity comprises a second distributed unit.

[0228] Aspect 24: A method for performing wireless communications at a first network entity, the method comprising: sending first information associated with a first configuration for sending a reference signal from a second network entity to a third network entity; sending second information associated with a second configuration for monitoring the reference signal by the third network entity; sending third information associated with a third configuration for reporting, by the third network entity, interference measurements performed on the reference signal received from the second network entity; and receiving fourth information associated with the interference measurement reported by the third network entity based at least in part on sending the first information, the second information, and the third information.

[0229] Aspect 25: The method according to aspect 24 further comprises: scheduling communications at the second network entity and the third network entity based at least in part on receiving the fourth information associated with the interference measurement reported by the third network entity.

[0230] Aspect 26: A method according to any one of Aspects 24 to 25, wherein sending the first information, the second information and the third information and receiving the fourth information includes: coordinating with a fourth network entity to configure the second network entity to send the reference signal, configure the third network entity to receive the reference signal and configure the third network entity to report the interference measurement performed on the reference signal.

[0231] Aspect 27: According to the method according to Aspect 26, the method also includes: coordinating with the fourth network entity to schedule communications at the second network entity and the third network entity based at least in part on receiving the fourth information associated with the interference measurement reported by the third network entity.

[0232] Aspect 28: A method according to any one of Aspects 24 to 27, wherein the first network entity comprises a central unit or an operation, administration and maintenance entity, the second network entity comprises a first distributed unit, and the third network entity comprises a second distributed unit.

[0233] Aspect 29: An apparatus for wireless communication at a first network entity, 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 a method according to any one of Aspects 1 to 9.

[0234] Aspect 30: An apparatus for wireless communication at a first network entity, the apparatus comprising at least one means for performing the method according to any one of aspects 1 to 9.

[0235] Aspect 31: A non-transitory computer-readable medium storing code for wireless communication at a first network entity, the code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 9.

[0236] Aspect 32: An apparatus for wireless communication at a first network entity, 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 a method according to any one of Aspects 10 to 23.

[0237] Aspect 33: An apparatus for wireless communication at a first network entity, the apparatus comprising at least one means for performing a method according to any one of aspects 10 to 23.

[0238] Aspect 34: A non-transitory computer-readable medium storing code for wireless communication at a first network entity, the code comprising instructions executable by a processor to perform the method according to any one of aspects 10 to 23.

[0239] Aspect 35: An apparatus for wireless communication at a first network entity, 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 a method according to any one of Aspects 24 to 28.

[0240] Aspect 36: An apparatus for wireless communication at a first network entity, the apparatus comprising at least one means for performing a method according to any one of aspects 24 to 28.

[0241] Aspect 37: A non-transitory computer-readable medium storing code for wireless communication at a first network entity, the code comprising instructions executable by a processor to perform the method according to any one of aspects 24 to 28.

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

[0243] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0244] The information and signals described herein may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0245] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed with a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0246] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions may be stored as one or more instructions or codes on a computer-readable medium, or sent on a computer-readable medium. Other examples and specific implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that the various parts of the functions are implemented at different physical locations.

[0247] Computer-readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that facilitates computer program to be transported from one place to another.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage device or other magnetic storage device, or can be used for carrying or storing desired program code member and can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure Any other non-transient medium.Moreover, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, optical fiber cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, optical fiber cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, includes CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0248] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

[0249] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, and similar actions. Additionally, "determining" may include receiving (such as receiving information), accessing (such as accessing data in a memory), and similar actions. Additionally, "determining" may include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

[0250] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between the similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label, regardless of the second or other subsequent reference labels.

[0251] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "having advantages over other examples." The specific embodiments include specific details to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

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

Claims

1. An apparatus for wireless communication at a first network entity, the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receiving, from the second network entity, an indication of a configuration for sending a reference signal for interference measurement at a third network entity; transmitting the reference signal based at least in part on the configuration; as well as A scheduling message is received from the second network entity that schedules communications at the first network entity based at least in part on sending the reference signal.

2. The apparatus of claim 1 , wherein the configuration comprises a first configuration and the reference signal comprises a first reference signal set, and the instructions are further executable by the processor to cause the apparatus to: receiving an indication of a second configuration for transmitting a second set of reference signals to one or more user equipments (UEs) for access link management or beam management; and The second set of reference signals is sent to the one or more UEs based at least in part on the second configuration, wherein the second set of reference signals is different from the first set of reference signals. The apparatus of claim 2 , wherein the first set of reference signals partially overlaps with the second set of reference signals.

4. The apparatus of claim 1 , wherein the instructions for receiving the indication of the configuration are executable by the processor to cause the apparatus to: Receive a quasi-co-located indication of one or more beams for use by the first network entity to send the reference signal.

5. The apparatus of claim 4, wherein the instructions for receiving the indication of the configuration are executable by the processor to cause the apparatus to: receiving an indication of resources mapped to each of the one or more beams; and The reference signal is transmitted using each beam of the one or more beams on corresponding resources mapped to each beam.

6. The apparatus of claim 1 , wherein receiving the indication of the configuration comprises receiving an identifier of a resource set on which the reference signal is to be sent, and sending the reference signal comprises sending the reference signal on the resource set based at least in part on receiving the configuration.

7. The apparatus of claim 6, wherein the configuration comprises an indication of a type of the resource set, the type of the resource set being periodic, aperiodic, or semi-persistent.

8. The apparatus of claim 6, wherein receiving the indication of the configuration comprises receiving an indication of a starting position, a number of symbols, a repetition factor, or a combination thereof of the resource set.

9. The apparatus of claim 1, wherein the first network entity comprises a first distributed unit, the second network entity comprises a central unit or an operation, administration, and maintenance entity, and the third network entity comprises a second distributed unit.

10. An apparatus for wireless communication at a first network entity, the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receiving, from a second network entity, an indication of a configuration for monitoring a reference signal from a third network entity for interference measurement at the first network entity; receiving one or more of the reference signals sent by the third network entity for the interference measurement; performing the interference measurement on the one or more of the reference signals; as well as Sending a report to the second network entity is based at least in part on performing the interference measurement on the one or more of the reference signals.

11. The apparatus of claim 10, wherein the configuration for monitoring a reference signal from the third network entity comprises a first configuration, and the instructions are further executable by the processor to cause the apparatus to: An indication of a second configuration for sending the report to the second network entity is received from the second network entity.

12. The apparatus of claim 11, wherein the second configuration for sending the report to the second network entity indicates a type of the report, the type of the report being periodic, aperiodic, or semi-persistent.

13. The apparatus of claim 11, wherein receiving the second configuration comprises receiving an indicator of one or more events that trigger sending the report to the second network entity.

14. The apparatus of claim 10, wherein the instructions are further executable by the processor to cause the apparatus to: receiving a trigger from the second network entity to perform the interference measurement and sending the report to the second network entity.

15. The apparatus of claim 10, wherein the instructions are further executable by the processor to cause the apparatus to: A medium access control (MAC) control element is received from the third network entity that triggers the first network entity to perform the interference measurement and send the report to the second network entity.

16. The apparatus of claim 10, wherein the instructions for receiving the indication of the configuration are executable by the processor to cause the apparatus to: A quasi-co-located indication of one or more beams for use by the first network entity to receive the reference signal is received.

17. The apparatus of claim 16, wherein the instructions are further executable by the processor to cause the apparatus to: identifying, from the configuration, resources mapped to each of the one or more beams; and The reference signal is received using each beam of the one or more beams on corresponding resources mapped to each beam.

18. The apparatus of claim 10, wherein the instructions for performing the interference measurement are executable by the processor to cause the apparatus to: A reference signal received power measurement is performed on the reference signal received from the third network entity based at least in part on receiving the configuration having a format associated with reference signal received power measurement.

19. The apparatus of claim 10, wherein the instructions for performing the interference measurement are executable by the processor to cause the apparatus to: A reference signal strength indicator measurement is performed on the reference signal received from the third network entity based at least in part on receiving the configuration having the format associated with reference signal strength indicator measurement.

20. The apparatus of claim 10, wherein: Receiving the indication of the configuration comprises receiving an identifier of a set of resources to monitor the reference signal; and Receiving the reference signal includes receiving the reference signal on the set of resources based at least in part on the identifier of the set of resources.

21. The apparatus of claim 20, wherein the configuration indicates a type of the resource set, the type of the resource set being periodic, aperiodic, or semi-persistent.

22. The apparatus of claim 20, wherein the configuration indicates a starting position of the resource set, a number of symbols, a repetition factor, or a combination thereof.

23. The apparatus of claim 10, wherein the first network entity comprises a first distributed unit, the second network entity comprises a central unit or an operations, administration, and maintenance entity, and the third network entity comprises a second distributed unit.

24. An apparatus for wireless communication at a first network entity, the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: sending first information associated with a first configuration for sending a reference signal from the second network entity to the third network entity; sending second information associated with a second configuration for monitoring the reference signal by the third network entity; sending third information associated with a third configuration for reporting, by the third network entity, interference measurements performed on the reference signal received from the second network entity; as well as Fourth information associated with the interference measurement reported by the third network entity is received based at least in part on sending the first information, the second information, and the third information.

25. The apparatus of claim 24, wherein the instructions are further executable by the processor to cause the apparatus to: Communications at the second network entity and the third network entity are scheduled based at least in part on receiving the fourth information associated with the interference measurement reported by the third network entity.

26. The apparatus of claim 24, wherein the instructions for sending the first information, the second information, and the third information and receiving the fourth information are executable by the processor to cause the apparatus to: Coordinate with a fourth network entity to configure the second network entity to send the reference signal, configure the third network entity to receive the reference signal, and configure the third network entity to report the interference measurements performed on the reference signal.

27. The apparatus of claim 26, wherein the instructions are further executable by the processor to cause the apparatus to: Coordinate with the fourth network entity to schedule communications at the second network entity and the third network entity based at least in part on receiving the fourth information associated with the interference measurement reported by the third network entity.

28. The apparatus of claim 24, wherein the first network entity comprises a central unit or an operations, administration, and maintenance entity, the second network entity comprises a first distributed unit, and the third network entity comprises a second distributed unit.

29. A method for wireless communication at a first network entity, the method comprising: receiving, from the second network entity, an indication of a configuration for sending a reference signal for interference measurement at a third network entity; transmitting the reference signal based at least in part on the configuration; as well as A scheduling message is received from the second network entity that schedules communications at the first network entity based at least in part on sending the reference signal.

30. The method of claim 29, wherein the configuration comprises a first configuration and the reference signal comprises a first reference signal set, the method further comprising: receiving an indication of a second configuration for transmitting a second set of reference signals to one or more user equipments (UEs) for access link management or beam management; as well as The second set of reference signals is sent to the one or more UEs based at least in part on the second configuration, wherein the second set of reference signals is different from the first set of reference signals.

Images