Cross-link interference management

Abstract

Various aspects of the present disclosure relate to cross-link interference (CLI) management. An apparatus, such as a radio access network (RAN) node, receives a first message that indicates subscription information including at least one first parameter associated with a configuration of a reference signal for managing a cross-link interference (CLI). The RAN node transmits, to a user equipment (UE), a second message that indicates at least one second parameter obtained based on the first parameter and associated with the configuration of the reference signal. In some examples, the at least one second parameter indicates that the UE transmit the reference signal. In some other examples, the at least one second parameter indicates that the UE perform at least one CLI measurement to obtain at least one CLI value. The RAN node receives, based on a transmission of the reference signal, a third message that indicates at least one CLI value.

Description

CROSS-LINK INTERFERENCE MANAGEMENTRELATED APPLICATION

[0001] This application claims priority to U.S. Provisional Application Serial No. 63 / 553,563 filed February 14, 2024, entitled “CROSS-LINK INTERFERENCE MANAGEMENT,” the disclosure of which is incorporated by reference herein in its entirety.TECHNICAL FIELD

[0002] The present disclosure relates to wireless communications, and more specifically to interference management.BACKGROUND

[0003] A wireless communications system may include one or more network communication devices, such as base stations, which may support wireless communications for one or more user communication devices, which may be otherwise known as user equipment (UE), or other suitable terminology. The wireless communications system may support wireless communications with one or more user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers, or the like)). Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)).SUMMARY

[0004] An article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’ or “one or both of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (e.g., A and B and C). Also,as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.” Further, as used herein, including in the claims, a “set” may include one or more elements.

[0005] A radio access network (RAN) node for wireless communication is described. The RAN node may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the RAN node may be configured to, capable of, or operable to receive, from a RAN controller, a first message that indicates subscription information including at least one first parameter associated with a configuration of a reference signal for managing a cross-link interference (CLI), transmit, to a UE, a second message that indicates at least one second parameter associated with the configuration of the reference signal, where the at least one second parameter is based on the at least one first parameter and indicates that the UE transmit the reference signal, and receive, based on a transmission of the reference signal, a third message that indicates at least one CLI value associated with the transmission of the reference signal from the UE.

[0006] A processor (e.g., a standalone processor chipset, or a component of a RAN node) for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may be configured to, capable of, or operable to receive, from a RAN controller, a first message that indicates subscription information including at least one first parameter associated with a configuration of a reference signal for managing a CLI, transmit, to a UE, a second message that indicates at least one second parameter associated with the configuration of the reference signal, where the at least one second parameter is based on the at least one first parameter and indicates that the UE transmit the reference signal, and receive, based on a transmission of the reference signal, a third message that indicates at least one CLI value associated with the transmission of the reference signal from the UE.

[0007] A method performed or performable by a RAN node for wireless communication is described. The method may include receiving, from a RAN controller, a first message that indicates subscription information including at least one first parameter associated with a configuration of areference signal for managing a CLI, transmitting, to a UE, a second message that indicates at least one second parameter associated with the configuration of the reference signal, where the at least one second parameter is based on the at least one first parameter and indicates that the UE transmit the reference signal, and receiving, based on a transmission of the reference signal, a third message that indicates at least one CLI value associated with the transmission of the reference signal from the UE.

[0008] In some implementations of the RAN node, the processor, and the method described herein, the RAN node, the processor, and the method may further be configured to, capable of, or operable to transmit, to the UE, a fourth message that indicates the UE update at least one transmission parameter for wireless communications associated with the CLI based on the third message indicating that the at least one CLI value satisfies a threshold value. Additionally, or alternatively, the update to the at least one transmission parameter for the wireless communications includes one or more of reducing a transmission power associated with the wireless communications, updating one or more time-frequency resources for the wireless communications, or updating a beam for the wireless communications, where the update to the at least one transmission parameter is based on at least one of a transmission power value for the wireless communications, a sequence of transmission power reduction values for the wireless communications, a sequence of transmission powers for the wireless communications, a synchronization signal block (SSB) index, a reference signal identifier, a reference signal resource indicator, a quasi-co-located (QCL) relationship, a transmission configuration indicator (TCI), a transmission direction, or one or more communication resources for the wireless communications. Additionally, or alternatively, the fourth message indicates that the UE update the at least one transmission parameter for the wireless communications according to a time period, where the time period includes at least one of a delay prior to updating the at least one transmission parameter for the wireless communications or duration for applying the update to the at least one transmission parameter for the wireless communications. Additionally, or alternatively, the RAN node, the processor, and the method may further be configured to, capable of, or operable to selectively update at least one transmission parameter for wireless communications associated with managing the CLI based on the third message indicating that the at least one CLI value satisfies a threshold value. Additionally, or alternatively, the at least one transmission parameter for the wirelesscommunications includes one or more of a transmission power for the wireless communications, a sequence of transmission power reduction values for the wireless communications, a sequence of transmission powers for the wireless communications, an SSB index, a reference signal identifier, a reference signal resource indicator, a QCL relationship, a TCI, a transmission direction, or one or more communication resources for the wireless communications.

[0009] Additionally, or alternatively, the RAN node, the processor, and the method may further be configured to, capable of, or operable to update the at least one transmission parameter for the wireless communications according to a time period, where the time period includes at least one of a delay prior to updating the at least one transmission parameter for the wireless communications or duration for applying the update to the at least one transmission parameter for the wireless communications. Additionally, or alternatively, the third message is associated with a parameter that has a value of a control type corresponding to managing the CLI, where the third message is received from at least one of the RAN controller or an additional RAN node. Additionally, or alternatively, the at least one CLI value includes at least one of a reference signal received power (RSRP), a received signal strength indicator (RSSI), a signal to interference plus noise ratio (SINR), or a reference signal received quality (RSRQ). Additionally, or alternatively, at least one reference signal associated with the transmission of the reference signal includes a sounding reference signal (SRS). Additionally, or alternatively, the RAN node includes at least one of a base station, a central unit (CU), a distributed unit (DU), an E2 node, or an 01 node, and where the RAN controller includes at least one of a RAN intelligent controller (RIC), a near-real-time RIC, or a non-real-time RIC.

[0010] A RAN node for wireless communication is described. The RAN node may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the RAN node may be configured to, capable of, or operable to receive, from a RAN controller, a first message that indicates subscription information including at least one first parameter associated with a configuration of a reference signal for managing a CLI, transmit, to a UE, a second message that indicates at least one second parameter associated with the configuration of the reference signal, where the at least one second parameter is based on the at least one first parameter and indicates that the UE perform at least one CLI measurement to obtain at least oneCLI value, and receive, based on the at least one CLI measurement, a third message that indicates the at least one CLI value.

[0011] A processor (e.g., a standalone processor chipset, or a component of a RAN node) for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may be configured to, capable of, or operable to receive, from a RAN controller, a first message that indicates subscription information including at least one first parameter associated with a configuration of a reference signal for managing a CLI, transmit, to a UE, a second message that indicates at least one second parameter associated with the configuration of the reference signal, where the at least one second parameter is based on the at least one first parameter and indicates that the UE perform at least one CLI measurement to obtain at least one CLI value, and receive, based on the at least one CLI measurement, a third message that indicates the at least one CLI value.

[0012] A method performed or performable by a UE for wireless communication is described. The method may include receiving, from a RAN controller, a first message that indicates subscription information including at least one first parameter associated with a configuration of a reference signal for managing a CLI, transmitting, to a UE, a second message that indicates at least one second parameter associated with the configuration of the reference signal, where the at least one second parameter is based on the at least one first parameter and indicates that the UE perform at least one CLI measurement to obtain at least one CLI value, and receiving, based on the at least one CLI measurement, a third message that indicates the at least one CLI value.

[0013] In some implementations of the RAN node, the processor, and the method described herein, the RAN node, the processor, and the method may further be configured to, capable of, or operable to determine that the at least one CLI value satisfies a threshold value, and transmit, to at least one of the RAN controller or an additional RAN node, a fourth message that indicates that the at least one CLI value satisfies the threshold value. Additionally, or alternatively, the fourth message is associated with a parameter with a value of at least one of a report type corresponding to managing the CLI or an insert type corresponding to managing the CLI. Additionally, or alternatively, the RAN node, the processor, and the method may further be configured to, capable of, or operable to activate, based on transmitting the fourth message, one or more timers associatedwith suspending a CLI measurement procedure associated with the UE, and suspend the CLI measurement procedure associated with the UE until expiry of the one or more timers. Additionally, or alternatively, the RAN node, the processor, and the method may further be configured to, capable of, or operable to receive a fifth message that indicates the one or more timers, where a value of the one or more timers corresponds to respective parameters associated with the CLI measurement procedure associated with the UE. Additionally, or alternatively, the RAN node, the processor, and the method may further be configured to, capable of, or operable to at least partially resume the CLI measurement procedure associated with the UE upon expiry of the one or more timers.

[0014] Additionally, or alternatively, the RAN node, the processor, and the method may further be configured to, capable of, or operable to terminate the CLI measurement procedure associated with the UE upon expiry of the one or more timers. Additionally, or alternatively, the one or more timers include one or more time-to-wait timers. Additionally, or alternatively, the at least one CLI value is associated with at least one reference signal transmission corresponding to a first network entity different from a second network entity that serves the UE. Additionally, or alternatively, the at least one second parameter indicates a periodicity for performing the at least one CLI measurement. Additionally, or alternatively, the at least one second parameter indicates a threshold value associated with the at least one CLI value, where the third message is received based on the at least one CLI value satisfying the threshold value. Additionally, or alternatively, the at least one CLI value includes at least one of an RSRP, an RSSI, an SINR, or an RSRQ. Additionally, or alternatively, the at least one CLI measurement is associated with at least one SRS, where the at least one second parameter is obtained based on the at least one first parameter. Additionally, or alternatively, the RAN node includes at least one of a base station, a CU, a DU, an E2 node, or an 01 node, where the RAN controller includes at least one of a RIC, a near-real-time RIC, or a non- real-time RIC.

[0015] A RAN controller for wireless communication is described. The RAN controller may be configured to, capable of, or operable to perform one or more operations as described herein. Lor example, the RAN controller may be configured to, capable of, or operable to transmit, to at least one RAN node, a first message that indicates subscription information including at least one parameter associated with a configuration of a reference signal for managing a CLI, where the at least one parameter indicates at least one of that a UE transmit the reference signal or that the UEperform at least one CLI measurement to obtain at least one CLI value, and receive, based on the configuration of the reference signal, a second message that indicates the at least one CLI value associated with the UE.

[0016] A processor (e.g., a standalone processor chipset, or a component of a RAN controller) for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may be configured to, capable of, or operable to transmit, to at least one RAN node, a first message that indicates subscription information including at least one parameter associated with a configuration of a reference signal for managing a CLI, where the at least one parameter indicates at least one of that a UE transmit the reference signal or that the UE perform at least one CLI measurement to obtain at least one CLI value, and receive, based on the configuration of the reference signal, a second message that indicates the at least one CLI value associated with the UE.

[0017] A method performed or performable by a RAN controller for wireless communication is described. The method may include transmitting, to at least one RAN node, a first message that indicates subscription information including at least one parameter associated with a configuration of a reference signal for managing a CLI, where the at least one parameter indicates at least one of that a UE transmit the reference signal or that the UE perform at least one CLI measurement to obtain at least one CLI value, and receiving, based on the configuration of the reference signal, a second message that indicates the at least one CLI value associated with the UE.

[0018] In some implementations of the RAN controller, the processor, and the method described herein, the at least one parameter indicates that the UE transmit the reference signal, where the at least one CLI value is associated with at least one of the UE or a transmission of the reference signal. Additionally, or alternatively, the RAN controller, the processor, and the method may further be configured to, capable of, or operable to transmit, to the at least one RAN node, a third message that indicates that at least one of the at least one RAN node or the UE update at least one transmission parameter for wireless communications associated with managing the CLI based on the at least one CLI value satisfying a threshold value. Additionally, or alternatively, the update to the at least one transmission parameter for the wireless communications includes one or more of reducing a transmission power associated with the wireless communications, updating one or more time-frequency resources for the wireless communications, or updating a beam for the wirelesscommunications, where the update to the at least one transmission parameter is based on at least one of a transmission power value for the wireless communications, a sequence of transmission power reduction values for the wireless communications, a sequence of transmission powers for the wireless communications, an SSB index, a reference signal identifier, a reference signal resource indicator, a QCL relationship, a TCI, a transmission direction, or one or more communication resources for the wireless communications.

[0019] Additionally, or alternatively, the RAN controller, the processor, and the method may further be configured to, capable of, or operable to receive, from the at least one RAN node, a fourth message that indicates feedback corresponding to the update to the at least one transmission parameter for wireless communications associated with managing the CLI. Additionally, or alternatively, the third message is associated with a parameter that has a value of a control type corresponding to managing the CLI. Additionally, or alternatively, the at least one parameter indicates that the UE perform the at least one CLI measurement to obtain the at least one CLI value, where the at least one CLI value is associated with a first network entity different from a second network entity that serves the UE. Additionally, or alternatively, the RAN controller, the processor, and the method may further be configured to, capable of, or operable to receive, from the at least one RAN node, a third message that indicates that the at least one CLI value satisfies a threshold value. Additionally, or alternatively, the third message is associated with a parameter with a value of at least one of a report type corresponding to managing the CLI or an insert type corresponding to managing the CLI.

[0020] Additionally, or alternatively, the RAN controller, the processor, and the method may further be configured to, capable of, or operable to transmit a fourth message that indicates one or more timers associated with suspending a CLI measurement procedure associated with the UE, where a value of the one or more timers corresponds to respective parameters associated with the CLI measurement procedure associated with the UE. Additionally, or alternatively, the one or more timers include one or more time-to-wait timers. Additionally, or alternatively, the at least one parameter indicates a periodicity for performing the at least one CLI measurement. Additionally, or alternatively, the at least one parameter indicates a threshold value associated with the at least one CLI value. Additionally, or alternatively, the RAN controller, the processor, and the method may further be configured to, capable of, or operable to receive, from the at least one RAN node, a thirdmessage that indicates at least one additional parameter associated with at least one of a capability of the at least one RAN node to perform a CLI management procedure, a configuration of a communication scheme associated with at least one of time division duplexing (TDD) information or sub-band full-duplex (SBFD) information, or configuration information associated with the UE, and determine the at least one parameter of the first message based on the at least one additional parameter. Additionally, or alternatively, the at least one CLI value includes at least one of an RSRP, an RSSI, an SINR, or an RSRQ. Additionally, or alternatively, the reference signal includes an SRS. Additionally, or alternatively, the at least one RAN node includes at least one of a base station, a CU, a DU, an E2 node, or an 01 node, where the RAN controller includes at least one of a RIC, a near-real-time RIC, or a non-real-time RIC.BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figures 1 and 2 illustrate examples of wireless communications systems in accordance with aspects of the present disclosure.

[0022] Figure 3 illustrates an example of a RAN architecture diagram, in accordance with aspects of the present disclosure.

[0023] Figure 4 illustrates an example of a RAN layer diagram, in accordance with aspects of the present disclosure.

[0024] Figures 5 through 8 illustrate examples of signaling diagrams, in accordance with aspects of the present disclosure.

[0025] Figure 9 illustrates an example of a RAN node in accordance with aspects of the present disclosure.

[0026] Figure 10 illustrates an example of a processor in accordance with aspects of the present disclosure.

[0027] Figure 11 illustrates an example of a RAN controller in accordance with aspects of the present disclosure.

[0028] Figures 12 and 13 illustrate flowcharts of a method performed by a RAN node in accordance with aspects of the present disclosure.

[0029] Figure 14 illustrates a flowchart of a method performed by a RAN controller in accordance with aspects of the present disclosure.DETAILED DESCRIPTION

[0030] A wireless communications system may implement a framework including one or more devices and interfaces supporting exchange of signaling for a RAN. For example, the framework may include one or more RAN nodes communicating with a RAN controller via one or more wired or wireless interfaces. A RAN node may include a base station, a CU of a base station, and / or a DU of a base station. A RAN controller may include a near-real time RIC and / or a non-real time RIC. The RAN controller may exchange signaling with the one or more RAN nodes via the one or more wired or wireless interfaces. The interfaces may include an E2 interface or an 01 interface (e.g., wired and / or wireless interfaces for an open-RAN (0-RAN) framework). An E2 interface provides for communication (e.g., signaling) between the near-real-time RIC and one or more of the RAN nodes, while the 02 interface provides for communication (e.g., signaling) between the non-real- time RIC and one or more RAN nodes, which is described in further detail with respect to Figure 3.

[0031] A UE and a RAN node can transmit or receive signaling using communication resources. For example, the UE and / or the RAN node may split (e.g., allocate, distribute) communication resources between uplink transmissions and downlink transmissions in the time domain, which may be referred to as a TDD communication scheme. In the TDD communication scheme, transmission and reception of signals occur at different times within a same frequency band. Different time resources within a transmission frame, which may be referred to as time slots and may be further divided into symbols, may be allocated to uplink and / or downlink transmissions. In some examples, the uplink and downlink resource allocation are synchronized across RAN nodes to avoid interference from one RAN node (e.g., when transmitting a downlink transmission) to another nearby RAN node (e.g., when receiving an uplink transmission) and / or interference between UEs in communication with the RAN nodes. However, if one or more RAN nodes use techniques for dynamic allocation of uplink and downlink resources, then the transmissions to and from different RAN nodes and / or UEs in communication with the RAN nodes may cause interference. Interference at a device (e.g., the RAN node and / or a UE) that is caused by another device (e.g., another RAN node and / or another UE) may be referred to as CLI. For example, a UE may be transmitting signaling with a transmission beam that is spatially directed towards a nearbyUE while the nearby UE is receiving different signaling in a same frequency band. The other UE may receive a portion of the signaling transmitted by the UE when receiving the different signaling, which may degrade the signal quality of the received signaling and may cause high signaling overhead and inefficient use of communication resources due to retransmissions resulting from communication errors caused by the interference.

[0032] To reduce latency and provide for greater signaling throughput, the RAN nodes and / or the UEs may implement SBFD operation. SBFD operation provides for a frequency band to be split into sub-bands for concurrent transmission and reception within a same time slot or using the same symbols. For example, a UE may transmit uplink signaling to a RAN node using a sub-band of a frequency band, while another UE concurrently (e.g., within a same duration of symbols or within a same slot) receives downlink signaling from a RAN node using a different sub-band of the frequency band. SBFD operation might induce additional interference between RAN nodes and / or UEs if a RAN node transmits downlink signaling to a UE with a transmission beam directed spatially towards another RAN node and / or another UE while the other RAN node is receiving uplink signaling or while the other UE is transmitting the uplink signaling on the same timefrequency resources. The interference caused by SBFD operation may lead to high signaling overhead and inefficient use of communication resources due to retransmission resulting from transmission, reception, and / or decoding errors caused by the interference.

[0033] As described herein, to reduce interference in a wireless communications system, such as CLI, a RAN node may exchange signaling with one or more UEs to coordinate CLI measurement and CLI management at the RAN node and / or at the UEs for UE-to-UE CLI. For example, a RAN controller may transmit a message indicating subscription information to at least one RAN node. The subscription information may include at least one parameter for a configuration of a reference signal for managing CLI. In some examples, the parameter may indicate for the RAN node to indicate to the UE to transmit a reference signal (e.g., an SRS). A RAN node may indicate to the UE to transmit the reference signal via another parameter in a second message. The UE may transmit the reference signal, and the RAN node may receive a third message that indicates at least one CLI value from another RAN node and / or from a RAN controller. In some other examples, the parameter may indicate for the RAN node to indicate to the UE to perform at least one CLI measurement (e.g., on a reference signal transmission) to obtain at least one CLI value. A RANnode may indicate to the UE to perform the CLI measurement via another parameter in a second message. The UE may perform the CLI measurement and may transmit a CLI report that includes the CLI measurement (e.g., to a RAN node).

[0034] Aspects of the present disclosure are described in the context of a wireless communications system. Reference is made herein to communicating data or information, such as signaling communication resources and / or communications that are transmitted or received between devices. It is to be appreciated that other terms may be used interchangeably with communicating, such as signaling, transmitting, receiving, outputting, forwarding, retrieving, obtaining, and so forth.

[0035] Figure 1 illustrates an example of a wireless communications system 100 in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more network equipment (NE) 102, one or more UE 104, and a core network (CN) 106. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE- Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a NR network, such as a 5G network, a 5G- Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network. In other implementations, the wireless communications system 100 may be any combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G, for example, 6G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.

[0036] The one or more NE 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the NE 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a network function, a network entity, network infrastructure (or infrastructure), a RAN, a NodeB, an eNodeB (eNB), a next-generation NodeB (gNB), or other suitable terminology. An NE 102 and a UE 104 may communicate via a communication link, which may be a wireless or wired connection (e.g., interface). For example, an NE 102 and a UE 104 may perform wireless communication (e.g.,receive signaling, transmit signaling) over a Uu interface, which may be an examples of a wireless or over the air interface. A wired interface may include a physical connection between one or more devices, such as an ethernet cable or a fiber-optic cable, among other examples.

[0037] An NE 102 may provide a geographic coverage area for which the NE 102 may support services for one or more UEs 104 within the geographic coverage area. For example, an NE 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or more radio access technologies. In some implementations, an NE 102 may be moveable, for example, a satellite associated with a non-terrestrial network (NTN). In some implementations, different geographic coverage areas associated with the same or different radio access technologies may overlap, but the different geographic coverage areas may be associated with different NE 102.

[0038] The one or more UEs 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of-Things (loT) device, an Internet-of- Everything (loE) device, or machine-type communication (MTC) device, among other examples.

[0039] A UE 104 may be able to support wireless communication directly with other UEs 104 over a communication link. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.

[0040] An NE 102 may support communications with the CN 106, or with another NE 102, or both. For example, an NE 102 may interface with other NE 102 or the CN 106 through one or more backhaul links (e.g., SI, N2, N6, or another network interface). In some implementations, the NE 102 may communicate with each other directly. In some other implementations, the NE 102 may communicate with each other indirectly (e.g., via the CN 106). In some implementations, one ormore NE 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs).

[0041] The CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 may be an evolved packet core (EPC), or a 5G core (5GC), which may include a control plane (CP) entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management functions (AMF)) and a user plane (UP) entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a UP function (UPF)). In some implementations, the CP entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for the one or more UEs 104 served by the one or more NE 102 associated with the CN 106.

[0042] The CN 106 may communicate with a packet data network over one or more backhaul links (e.g., via an SI, N2, N6, or another network interface). The packet data network may include an application server. In some implementations, one or more UEs 104 may communicate with the application server. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the CN 106 via an NE 102. The CN 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server using the established session (e.g., the established PDU session). The PDU session may be an example of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106).

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

[0044] One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., / r=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., / r=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., / r=l) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., / r=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., / r=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., / r=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0045] A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames). Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

[0046] Additionally, or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (e.g., / r=0, jU=l, / r=2, / r=3, / r=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot may include 12 symbols. Therelationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., / r=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0047] In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or more operating frequency bands, such as frequency range designations frequency range 1 (FR1) (410 megahertz (MHz) - 7.125 gigahertz (GHz)), frequency range 1 (FR2) (24.25 GHz - 52.6 GHz), frequency range 3 (FR3) (7.125 GHz - 24.25 GHz), frequency range 4 (FR4) (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and frequency range 5 (FR5) (114.25 GHz - 300 GHz). In some implementations, the NEs 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data). In some implementations, FR2 may be used by the NEs 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.

[0048] FR1 may be associated with one or more numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., / r=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., / r=l), which includes 30 kHz subcarrier spacing; and a third numerology (e.g., / r=2), which includes 60 kHz subcarrier spacing. FR2 may be associated with one or more numerologies (e.g., at least 2 numerologies). For example, FR2 may be associated with a third numerology (e.g., / r=2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., / r=3), which includes 120 kHz subcarrier spacing.

[0049] In some examples, the terms antenna, panel, and antenna panel are used interchangeably. An antenna panel may be hardware that is used for transmitting and / or receiving radio signals at frequencies lower than 6 GHz (e.g., FR1), or higher than 6 GHz (e.g., FR2 or millimeter wave (mmWave)). In some examples, an antenna panel may include an array of antenna elements, where an antenna element is connected to hardware, such as a phase shifter that provides for a control module to apply spatial parameters for transmission and / or reception of signals. The resultingradiation pattern may be called a beam, which may, or may not, be unimodal and may provide for the device (e.g., a UE 104, node) to amplify signals that are transmitted or received from one or more spatial directions.

[0050] In some examples, an antenna panel may, or may not, be virtualized as an antenna port. An antenna panel may be connected to a baseband processing module through a radio frequency (RF) chain for each of transmission (e.g., egress) and reception (e.g., ingress) directions. A capability of a device in terms of the number of antenna panels, a duplexing capability of the device, beamforming capabilities of the device, and so on, may, or may not, be transparent to other devices. In some examples, capability information may be communicated via signaling, or, in some other examples, capability information may be provided to devices without signaling. In the case that such information is available to other devices, such as a CU, the information can be used for signaling or local decision making.

[0051] In some examples, an antenna panel may be a physical or logical antenna array including a set of antenna elements or antenna ports that share a common or a significant portion of an RF chain (e.g., in-phase / quadrature (I / Q) modulator, analog to digital (A / D) converter, local oscillator, phase shift network). The antenna panel may be a logical entity with physical antennas mapped to the logical entity. The mapping of physical antennas to the logical entity may be up to implementation. Communicating (e.g., receiving or transmitting) on at least a subset of antenna elements or antenna ports active for radiating energy, also referred to herein as active elements, of an antenna panel includes biasing or powering on of the RF chain which results in current drain or power consumption at the device (e.g., node) associated with the antenna panel (e.g., including power amplifier / low noise amplifier (ENA) power consumption associated with the antenna elements or antenna ports). The phrase “active for radiating energy,” as used herein, may refer to either a transmit function or a receive function. Accordingly, an antenna element that is active for radiating energy may be coupled to a transmitter to transmit RF energy or to a receiver to receive RF energy, either simultaneously or sequentially, or may be coupled to a transceiver for performing intended functionality. Communicating on the active elements of an antenna panel enables generation of radiation patterns or beams.

[0052] In some examples, depending on implementation, a “panel” can have at least one of the following functionalities as an operational role of Unit of antenna group to control a transmit beamindependently, Unit of antenna group to control a transmission power independently, Unit of antenna group to control a transmission timing independently. The “panel” may be transparent to another node (e.g., next hop neighbor node). For one or more conditions, another node or network entity can assume the mapping between physical antennas of a device to the logical entity “panel” may not be changed. For example, the condition may include until the next update or report from device or include a duration of time over which the NE 102 determines there is no change to the mapping. A device may report a device capability with respect to the “panel” to the NE 102. The device capability may include at least the number of “panels.” In some implementations, the device may support transmission from one beam within a panel. In some cases, with multiple panels, more than one beam (e.g., one beam per panel) may be used for transmission. In some other implementations, more than one beam per panel may be supported and / or used for transmission.

[0053] In some examples, an antenna port is defined such that the channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed. Two antenna ports are said to be QCL if the large-scale properties of the channel over which a symbol on one antenna port is conveyed can be inferred from the channel over which a symbol on the other antenna port is conveyed. The large-scale properties include one or more of delay spread, Doppler spread, Doppler shift, average gain, average delay, and spatial receive parameters, among other examples. Two antenna ports may be quasi-located with respect to a subset of the large-scale properties and different subset of large-scale properties may be indicated by a QCL type. The QCL type can indicate which channel properties are the same between the two reference signals (e.g., on the two antenna ports). Thus, the reference signals can be linked to each other with respect to what the device can assume about their channel statistics or QCL properties.

[0054] Lor example, QCL type may take one of the following values. Other QCL types may be defined based on combination of one or large-scale properties, including, but not limited to, QCL- TypeA, QCL-TypeB, QCL-TypeC, and QCL-TypeD. QCL-TypeA may include a Doppler shift, Doppler spread, average delay, and / or delay spread. QCL-TypeB may include Doppler shift and / or Doppler spread. QCL-TypeC may include Doppler shift and / or average delay. QCL-TypeD may include spatial receive or reception parameters. Spatial receive or reception parameters may include one or more of an angle of arrival (AoA,) Dominant AoA, average AoA, angular spread, PowerAngular Spectrum (PAS) of AoA, average angle of departure (AoD), PAS of AoD, transmit and / or receive channel correlation, transmit and / or receive beamforming, spatial channel correlation etc. The QCL-TypeA, QCL-TypeB and QCL-TypeC may be applicable for carrier frequencies, but the QCL-TypeD may be applicable in higher carrier frequencies (e.g., mmWave, FR2 and beyond), where the device may not be able to perform omni-directional transmission (e.g., the device would form beams for directional transmission). A QCL-TypeD between two reference signals A and B, the reference signal A is considered to be spatially co-located with reference signal B and the device may assume that the reference signals A and B can be received with the same spatial filter (e.g., with the same receive beamforming weights).

[0055] An “antenna port” may be a logical port that may correspond to a beam (e.g., resulting from beamforming) or may correspond to a physical antenna on a device. In some examples, a physical antenna may map directly to a single antenna port, in which an antenna port corresponds to a physical antenna. Additionally, or alternatively, a set or subset of physical antennas, or antenna set or antenna array or antenna sub-array, may be mapped to one or more antenna ports after applying complex weights, a cyclic delay, or both to the signal on each physical antenna. The physical antenna set may have antennas from a single module or panel or from multiple modules or panels. The weights may be fixed as in an antenna virtualization scheme, such as cyclic delay diversity (CDD). The procedure used to derive antenna ports from physical antennas may be specific to a device implementation and transparent to other devices.

[0056] In some cases, a TCI state associated with a target transmission can indicate parameters for configuring a QCL relationship between the target transmission (e.g., target reference signal of demodulation reference signal (DMRS) ports of the target transmission during a transmission occasion) and one or more source reference signals (e.g., SSB, channel station informationreference signal (CSLRS), and / or an SRS) with respect to QCL type parameters indicated in the corresponding TCI state. The TCI describes which reference signals are used as QCL source, and what QCL properties can be derived from each reference signal. A device can receive a configuration of a set of TCI states for a serving cell for transmissions on the serving cell (e.g., between a serving gNB and a smart repeater). In some examples, a TCI state includes at least one source reference signal to provide a reference for determining QCL and / or spatial filter.

[0057] In some cases, an uplink TCI state is provided if a device is configured with separate downlink and / or uplink TCI by radio resource control (RRC) signaling. The uplink TCI state may include a source reference signal which provides a reference for determining uplink spatial domain transmission filter for the uplink transmission (e.g., dynamic-grant / configured-grant based physical uplink shared channel (PUSCH), dedicated physical uplink control channel (PUCCH) resources) in a component carrier (CC) or across a set of configured CCs and / or bandwidth parts (BWPs). In some cases, a joint downlink and / or uplink TCI state is provided if the device is configured with joint downlink and / or uplink TCI by RRC signaling (e.g., configuration of joint TCI or separate downlink and / or uplink TCI is based on RRC signaling). The joint downlink and / or uplink TCI state refers to at least a common source reference signal used for determining both the downlink QCL information and the uplink spatial transmission filter. The source reference signal determined from the indicated joint, or common, TCI state provides QCL Type-D indication (e.g., for a devicededicated physical downlink control channel (PDCCH) and / or physical downlink shared channel (PDSCH)) and is used to determine am uplink spatial transmission filter (e.g., for UE-dedicated PUSCH and / or PUCCH) for a CC or across a set of configured CCs and / or BWPs. In some examples, the uplink spatial transmission filter is derived from the reference signal of downlink QCL Type D in the joint TCI state. The spatial setting of the uplink transmission may be according to the spatial relation with a reference to the source reference signal configured with QCL type set to ‘QCL-typeD’ in the joint TCI state.

[0058] In some cases, a spatial relation information associated with a target transmission can indicate parameters for configuring a spatial setting between the target transmission and a reference signal (e.g., SSB, CSLRS, and / or SRS). Lor example, the device may transmit the target transmission with the same spatial domain filter used for reception the reference signal (e.g., downlink reference signal including an SSB and / or CSLRS). In some other examples, the device may transmit the target transmission with the same spatial domain transmission filter used for the transmission of the reference signal (e.g., uplink reference signal including an SRS). A device can receive a configuration of a set of spatial relation information configurations for a serving cell for transmissions on the serving cell.

[0059] In some cases, an uplink TCI state is provided if a device is configured with separate downlink and / or uplink TCI by RRC signaling. The uplink TCI state may include a source referencesignal, which provides a reference for determining an uplink spatial domain transmission filter for the uplink transmission (e.g., dynamic-grant and / or configured-grant based PUSCH, dedicated PUCCH resources) in a CC or across a set of configured CCs and / or BWPs. In some cases, a joint downlink and / or uplink TCI state is provided if the device is configured with joint downlink and / or uplink TCI by RRC signaling (e.g., configuration of joint TCI or separate downlink and / or uplink TCI is based on RRC signaling). The joint downlink and / or uplink TCI state refers to at least a common source reference signal used for determining both the downlink QCL information and the uplink spatial transmission filter. The source reference signal determined from the indicated joint, or common, TCI state provides QCL Type-D indication (e.g., for device-dedicated PDCCH and / or PDSCH) and is used to determine uplink spatial transmission filter (e.g., for UE-dedicated PUSCH and / or PUCCH) for a CC or across a set of configured CCs and / or BWPs. In one example, the uplink spatial transmission filter is derived from the reference signal of downlink QCL Type D in the joint TCI state. The spatial setting of the uplink transmission may be according to the spatial relation with a reference to the source reference signal configured with QCL type set to ‘QCL- typeD’ in the joint TCI state.

[0060] According to implementations, one or more of the NEs 102 and the UEs 104 are operable to implement various aspects of the techniques described with reference to the present disclosure. Different NEs 102 may exchange signaling with UEs 104, causing CLI between the NEs 102 and / or the UEs 104, which is described in further detail with respect to Figure 2. In some examples, to reduce CLI between UEs 104 in the wireless communications system 100, a RAN controller at the CN 106 may initiate one or more subscription procedures at the NEs 102 (e.g., RAN nodes). The RAN controller may exchange signaling with one or more NEs 102 to coordinate CLI measurement and CLI management at the one or more NEs 102 and the one or more UEs 104. For example, a RAN controller may transmit a message indicating subscription information to at least one NE 102. The subscription information may include at least one parameter for a configuration of a reference signal for managing CLI. In some examples, the parameter may indicate for the NE 102 to indicate to a UE 104 to transmit a reference signal (e.g., an SRS). AN NE 102 may indicate to the UE 104 to transmit the reference signal via another parameter in a second message. The UE 104 may transmit the reference signal, and the NE 102 may receive a third message that indicates at least one CLI value from another NE 102 and / or from a RAN controller.In some other examples, the parameter may indicate for the NE 102 to indicate to the UE 104 to perform at least one CLI measurement (e.g., on a reference signal transmission) to obtain at least one CLI value. AN NE 102 may indicate to the UE 104 to perform the CLI measurement via another parameter in a second message. The UE 104 may perform the CLI measurement and may transmit a CLI report that includes the CLI measurement (e.g., to an NE 102).

[0061] Figure 2 illustrates an example of a wireless communications system 200 in accordance with aspects of the present disclosure. In some examples, the wireless communications system 200 implements aspects of the wireless communications system 100. For example, the wireless communications system 200 includes a UE 104-a, and a UE 104-b, and one or more CNs 106, which may be examples of UEs 104 and CNs 106 as described with reference to Figure 1. The wireless communications system 200 may also include a RAN node 202-a and a RAN node 202-b, where the RAN nodes may be examples of an NE 102 as described with reference to Figure 1, such as a base station, a CU of a base station, and / or a DU of a base station.

[0062] The UE 104-a may transmit signaling, including control signaling, data, or both, to a RAN node 202-a via an uplink wireless communications link 204. The RAN node 202-b may transmit signaling, including control signaling, data, or both, to a UE 104-b via a downlink wireless communications link 206. Although the wireless communications system 200 is illustrated as including two UEs and two RAN nodes, the wireless communications system 200 may include any numerical quantity of UEs, RAN nodes, and / or other wireless devices. In some examples, the RAN node 202-a and / or the RAN node 202-b may be wired or wirelessly connected to each other and / or to the CNs 106. The wired or wireless connections may be referred to as interfaces 208, or network interfaces. There may be one or more different types of interfaces 208, which is described in further detail with respect to Figure 3.

[0063] In some examples, the RAN node 202-a, the RAN node 202-b, the UE 104-a, and / or the UE 104-b may implement a TDD communications scheme. For example, the RAN node 202-a, the RAN node 202-b, the UE 104-a, and / or the UE 104-b may split one or more time domain communication resources into downlink resources and uplink resources. Downlink resources may include one or more resources in the time domain (e.g., slots and / or symbols) that are allocated for communication from a UE to a RAN node or an NE. Uplink resources include one or more resources in the time domain that are allocated for communication to a UE from a RAN node or anNE. For a TDD communication scheme, at any point in time a RAN node (e.g., the RAN node 202- a and / or the RAN node 202-b) may transmit signaling using a defined frequency resource to a wireless device, including the UE 104-a and / or the UE 104-b, or vice-versa, but not both. That is, a RAN node may coordinate with a UE, such that the RAN node and the UE are not concurrently or simultaneously transmitting signaling (e.g., using a same time resource). Additionally, or alternatively, the RAN node may coordinate with another RAN node, such that the RAN nodes are not concurrently or simultaneously transmitting and / or receiving signaling. Interference at a RAN node may be caused by the RAN node receiving a portion of signaling from another RAN node sending a downlink transmission in a nearby coverage area (e.g., cell). Conventional wireless communication systems may employ a static TDD communication scheme, in which patterns for transmitting according to the TDD communication scheme are synchronized across wireless devices (e.g., using identical patterns) to avoid interference at a RAN node that is receiving an uplink transmission. The pattern may include one or more uplink and / or downlink slot configurations that specify one or more symbols within the slot as allocated for an uplink transmission, allocated for a downlink transmission, or both, among other allocations.

[0064] In some examples, an atmospheric ducting phenomenon caused by lower densities at higher altitudes in Earth’s atmosphere cause a reduced refractive index, resulting in signals bending back towards the Earth. A signal trapped in an atmospheric duct can reach distances far greater than normal. In TDD networks with a same uplink and / or downlink slot configuration, and in the absence of atmospheric ducting, a guard period is used to avoid the interference between uplink and downlink transmissions in different cells. A guard period is a time period, or delay, inserted between transmission of symbols. However, when the atmospheric ducting phenomenon happens, radio signals can travel a relatively long distance (e.g., greater than a threshold distance), and the propagation delay may exceed the guard period. Consequently, the downlink signals of a RAN node 202-a may interfere with uplink signals of another RAN node 202-b that is relatively far away (e.g., greater than a threshold distance) from the RAN node 202-a. Such interference is termed as remote interference. The farther the RAN node 202-a is from the RAN node 202-b, the more uplink symbols of the RAN node 202-b may be impacted.

[0065] A remote interference scenario may involve any numerical quantity of RAN nodes, where a RAN node may execute remote interference management (RIM) coordination. RAN nodescan be grouped into semi-static sets, where respective cells of the RAN nodes are assigned set identifiers and configured with a RIM reference signal (RIM-RS) and communication resources for the set identifier. An interfering RAN node (e.g., a RAN node causing interference at another RAN node) can be configured with multiple set identifiers and respective RAN nodes experiencing interference can be configured with multiple set identifiers, where each cell may have at most one set identifier for an interfering RAN node and one set identifier for a RAN node that is interfered with. Consequently, a RAN node may be an interfering RAN node and may experience interference at a same time.

[0066] To mitigate, or reduce, remote interference, a network (e.g., the CNs 106) may enable RIM frameworks for coordination between RAN nodes. The coordination communication in RIM frameworks can be wireless-based and / or backhaul-based. The backhaul-based RIM framework uses any combination of wireless interfaces and backhaul interfaces for signaling, while in the wireless framework, the communication is via wireless interfaces (e.g., over the air). Backhaul interfaces may be examples of wired interfaces. In both frameworks, RAN nodes that are being interfered with may simultaneously transmit an identical RIM reference signal carrying the set identifier for the interfered RAN nodes over the air. In the wireless framework, upon reception of the RIM reference signal from the set for the interfered RAN nodes, interfering RAN nodes undertake RIM measures and send back a RIM reference signal carrying the set identifier for the interfering RAN nodes. The RIM reference signal sent by the interfering RAN node provides information regarding whether the atmospheric ducting phenomenon exists. The interfered RAN nodes may determine the atmospheric ducting phenomenon terminates if the interfered RAN node fails to receive a reference signal from an interfering RAN node.

[0067] In the RIM backhaul framework, upon reception of the RIM reference signal from the set for the interfering RAN nodes, interfering RAN nodes undertake RIM measures and establish backhaul coordination towards RAN nodes that are experiencing interference. The backhaul messages are sent from individual interfering RAN nodes to individual RAN nodes experiencing the interference, where the signaling is transparent to the CNs 106. The RIM backhaul messages from the interfering RAN nodes to the RAN nodes experiencing the interference carry the indication about the detection, or lack of detection, of a RIM reference signal. Based on the indication from the backhaul message, the interfering RAN nodes determine whether the atmospheric ducting andthe consequent remote interference have terminated. In both frameworks, upon determining that the atmospheric ducting has terminated, the RAN nodes that were experiencing the interference may cancel further transmissions of the RIM reference signal.

[0068] In some cases, one or more wireless communications systems may implement a dynamic TDD communication scheme. For a dynamic TDD communication scheme, different TDD patterns may be used by RAN nodes in different cells resulting in interference between an uplink transmission in a cell and a downlink transmission in another cell, which may be referred to as CLI 210. For example, if the RAN node 202-b and the UE 104-b are communicating using a TDD pattern that is different than a TDD pattern the RAN node 202-a and the UE 104-a are using to communicate, then the UE 104-b may experience the CLI 210 from a transmission between the UE 104-a and the RAN node 202-a. Additionally, or alternatively, the RAN node 202-a may experience the CLI 210 from a transmission between the RAN node 202-b and the UE 104-b. The CLI 210 may cause decoding and / or reception errors at the RAN node 202-a and / or the UE 104-b, resulting in high signaling overhead due to an increase in retransmissions, as well as increased processing during decoding.

[0069] In some examples, to mitigate the CLI 210, a RAN node 202-a and a RAN node 202-b can exchange and coordinate an intended TDD pattern via communications over one or more interfaces 208, including, but not limited to an Xn interface or an Fl interface. An Xn interface provides for communication between base stations, while an Fl interface provides for communication between a CU and a DU within a base station. One or more UEs experiencing interference (e.g., the UE 104-b) can be configured or operable to perform CLI measurements. In some examples, there may be multiple different types of CLI measurements, such as two different types of CLI measurements. The types of CLI measurements may include an RSRP measurement and an RSSI measurement, among others.

[0070] In some examples, the RAN node 202-a, the RAN node 202-b, the UE 104-a, and / or the UE 104-b may implement SBFD operation, where multiple wireless devices may be configured or operable to transmit uplink signals in a sub-band using symbols allocated for a downlink transmission, or vice-versa. In some examples, multiple wireless devices within a cell (e.g., a coverage area of a RAN node) implementing SBFD operation may result in the CLI 210, such as due to beamforming at mmWave frequencies and / or beamforming configurations. For example, aUE 104-a may transmit an uplink signal via the uplink wireless communications link 204 with a transmit beam that is spatially directed toward a UE 104-b, and the UE 104-b may receive a downlink signal via the downlink wireless communications link 206 using same, or overlapping, time-frequency resources as the uplink signal and with a receive beam spatially directed toward the UE 104-a. The uplink signal may cause the CLI 210 at for the downlink signal.

[0071] The CLI 210 may be reduced, or eliminated, by signaling and coordination among wireless devices (e.g., the UE 104-a, the UE 104-b, the RAN node 202-a, and / or the RAN node 202 -b). For example, a UE 104-a may be provided configuration information of a reference signal (e.g., an SRS) from a UE 104-b. The UE 104-a may be configured or operable to measure the SRS and report one or more measurements, such as an RSRP of the SRS (SRS-RSRP), to a serving base station (e.g., the RAN node 202-a). In some examples, an SRS-RSRP may be defined as a linear average of a power contribution (e.g., in watts) of resource elements (REs) carrying SRSs. The SRS-RSRP is measured over configured REs within a considered measurement frequency bandwidth in one or more configured measurement time occasions. For example, for FR1 (e.g., frequency bands below 6 GHz), the reference point for the SRS-RSRP may be an antenna connector of a UE. In some other examples, for frequency range 2 (e.g., mmWave transmissions), SRS-RSRP may be measured based on the combined signal from antenna elements corresponding to a given receiver branch. For FR1 and FR2, if a UE implements receiver diversity, then a reported SRS- RSRP value may not be lower than a corresponding SRS-RSRP of respective receiver branches.

[0072] In some cases, the UE 104-a may be configured or operable to measure an RSSI for the CLI 210 (CLI-RSSI), which may be defined as a linear average of a total received power (e.g., in watts) observed in one or more configured symbols (e.g., orthogonal frequency division multiplexing (OFDM) symbols) of one or more configured measurement time resources, in a configured measurement bandwidth from respective sources, including co-channel serving and nonserving cells, adjacent channel interference, thermal noise etc. For FR1, the reference point for the CLI-RSSI may be the antenna connector of the UE. For FR2, CLI-RSSI may be measured based on the combined signal from antenna elements corresponding to a respective receiver branch. For FR1 and FR2, if the UE implements receiver diversity, then the reported CLI-RSSI value may not be lower than a corresponding CLI-RSSI of respective receiver branches.

[0073] In some examples, the UE 104-a may be within a same serving cell as the UE 104-b, and the CLI 210 may be referred to as intra-cell CLI. In some other examples, the UE 104-a may be within a different serving cell as the UE 104-b, and the CLI 210 may be referred to as inter-cell CLI. In some cases, such as for inter-UE CLI management for SBFD operation, a UE 104-b experiencing the CLI 210 may measure an RSSI within a downlink sub-band, may measure an RSRP of an interfering UE 104-a within an uplink sub-band, and / or may measure an RSSI within the uplink sub-band. The UE 104-b may report the CLI measurements by including separate measurement resources and / or reports for respective downlink sub-bands, by including a measurement resource and / or report for a single downlink sub-band, and / or by including a measurement resource and / or report for non-contiguous resources across downlink sub-bands. Including separate measurement resources and / or reports for respective downlink sub-bands may provide for flexible configuration of measurement reporting in one or more downlink sub-bands but consumes multiple CLI measurement resources from a UE capability budget. Including a measurement resource and / or report for a single downlink sub-band reduces measurement resources, but also reduces RAN node configuration flexibility, and may not account for whether or not the CLI is asymmetric across multiple downlink sub-bands. Including a measurement resource and / or report for non-contiguous resources across downlink sub-bands reduces measurement resources, and may maintain RAN node configuration flexibility, while accounting for CLI asymmetry. In some examples, the CLI measurements may be used to identify an interfering UE 104-a, such as if orthogonal resources are allocated for different UEs.

[0074] In some examples, one or more UEs may perform co-channel CLI measurement and reporting, which may be defined for dynamic and / or flexible TDD and / or common for both SBFD and dynamic / flexible TDD. For example, UE-to-UE co-channel CLI measurement may be defined by a measurement resource and / or reporting configuration, measurement and / or reporting details (e.g., including UE processing delay), relevant information exchange between base stations, and / or usage of measurement at a base station, among other factors. In some examples, UE-to-UE cochannel CLI measurement may use one or more existing channels, signals, and / or measurement resources (e.g., SRS resources for SRS-RSRP measurement and / or CLI-RSSI resources for CLI- RSSI measurement).

[0075] In some examples, one or more RAN nodes (e.g., the RAN node 202-a and the RAN node 202-b, which may be examples of base stations) may also experience inter-cell CLI and / or the CLI 210 (e.g., due to SBFD operation). In variations, one or more RAN nodes and / or one or more base stations may perform co-channel CLI measurement and / or channel measurement, which may be defined for dynamic and / or flexible TDD and / or common for both SBFD and dynamic / flexible TDD. In some examples, base station-to-base station (e.g., RAN node-to-RAN node) co-channel CLI measurement may use one or more existing downlink channels, signals, and / or measurement resources (e.g., SSB, non-zero-power (NZP) CSLRSs and / or zero power (ZP)-CSLRSs, a DMRS for PDCCH and / or PDSCH, CSI-interference measurement (IM), RSSI measurement resource, etc.). The RAN nodes and / or base stations may perform beam level (e.g., based on measurement results per SSB resource and / or per CSLRS resource) CLI measurement. Additionally, or alternatively, the RAN nodes and / or the base stations may exchange configuration for a NZP CSL RS and / or an SSB for CLI measurement and / or channel measurement. Additionally, or alternatively, the RAN nodes and / or the base stations may implement transparent uplink resource muting (e.g., by avoiding scheduling transmissions on a measurement resource) and / or nontransparent uplink resource muting (e.g., by defining an uplink resource muting pattern with one or more RE muting patterns and / or resource block (RB) muting patterns).

[0076] In some examples, the CNs 106 (e.g., a RAN controller) may introduce a framework for managing the CLI 210 among RAN nodes and UEs, where enhanced duplexing methods, including SBFD operations, are implemented. The framework is described in further detail with respect to Figures 5 through 8. In some cases, the framework is compatible with the O-RAN framework and service models, where the O-RAN framework is further described with reference to Figure 2. Additionally, or alternatively, the framework may be compatible with other communication frameworks, including, but not limited to, evolved RAN architectures (e.g., 5G, 6G, etc.). In variations, the framework may use the interfaces 208, where a control entity or RAN controller is a part of a RAN network, the CNs 106, any combination of both, or a converged RAN-CN architecture. Additionally, or alternatively, signaling among the RAN nodes and / or the control entity may be realized over a new interface such as an E2 or 01 interface, according to an architecture compliant with the O-RAN architecture.

[0077] Figure 3 illustrates an example of a RAN architecture diagram 300 in accordance with aspects of the present disclosure. In some examples, the RAN architecture diagram 300 may implement, or be implemented by, aspects of the wireless communications system 100 and the wireless communications system 200. The RAN architecture diagram 300 may be implemented by a RAN node and a RAN controller, which may be examples of the corresponding devices as described with reference to Figures 1 and 2. For example, the RAN architecture diagram 300 may illustrate examples of interfaces between different RAN nodes, such as a base station, a CU of a base station, a DU of a base station, and a control entity or RAN controller. The control entity may be an example of a near-real-time RIC 302 and / or a non-real-time RIC 304. Although Figure 3 illustrates an example of an 0-RAN architecture, aspects of the methods, systems, and apparatuses as described herein may be implemented in the context of additional, or alternatively, network architectures.

[0078] A control entity and / or a RAN controller may refer to a near-real-time RIC 302, a non- real-time RIC 304, or any combination of both, a subset of either, or any other control entity in the RAN, one or more CNs, or any combination of both, or a network with a converged RAN-CN architecture. Similarly, a network interface in the present disclosure may be any type of network interface, such as a next generation (NG) interface, an Xn interface, an E2 interface, and / or an 01 interface. An NG interface may be a network interface between a NG core (NGC) and the RAN. In some examples, a service management and orchestration framework 306 may define one or more interfaces between different RAN devices. In some examples, base stations may communicate information for CLI management indirectly through NG interfaces to a CN function, such as an AMF, and / or directly through an Xn interface.

[0079] A RAN may include a non-real-time RIC 304, which is an element of 0-RAN architecture that controls other RAN elements and resources. The non-real-time RIC 304 may use artificial intelligence and machine learning to control RAN elements and resources. A response time of the non -real-time RIC 304 may be relatively large (e.g., greater than a threshold) when compared with a response time of a near-real-time RIC 302. A near-real-time RIC 302 controls other RAN elements and resources for events and resources with a relatively short response time (e.g., 10 milliseconds (ms), less than a threshold value). The non-real-time RIC 304 and the near-real-time RIC 302 may be connected via an Al interface. The service management and orchestrationframework 306 may include an O-eNB 308, which may be an eNB that supports the 0-RAN architecture, and an 0-DU 310, which may be a DU that supports the 0-RAN architecture. The O-eNB 308 and the 0-DU 310 may be connected via an 01 interface. The O-eNB 308 may additionally, or alternatively, be connected to the near-real-time RIC 302 via an E2 interface.

[0080] In some examples, E2 functions are grouped into RIC services and E2 supported services. Example RIC services include, but are not limited to, REPORT services, INSERT services, CONTROL services, POLICY services and / or QUERY services supported by RIC functional procedures (e.g., RIC subscription, RIC subscription modification, RIC subscription modification required, RIC subscription delete, RIC subscription delete required, RIC indication, RIC control, RIC query). Example E2 support services include, but are not limited to, interface management services supported by global procedures (e.g., E2 setup, E2 reset, E2 node configuration update, E2 removal, reporting of general error situations) and RAN function services supported by global procedures (e.g., RIC service update, RIC service query). In some cases, a near- real-time RIC 302 may use one or more RIC services provided by an E2 node. The RIC services may include a REPORT service in which a near-real-time RIC 302 uses an RIC subscription procedure and / or RIC subscription modification procedure to request that an E2 node sends a REPORT message to the near-real-time RIC 302, and the associated procedure continues at the E2 Node after each occurrence of a defined RIC subscription procedure event trigger. Additionally, or alternatively, the RIC services may include an INSERT service in which a near-real-time RIC 302 uses an RIC subscription procedure and / or RIC subscription modification procedure to request that an E2 node sends an INSERT message to the near-real-time RIC 302 and suspends an associated procedure at the E2 node after each occurrence of a defined RIC subscription procedure event trigger. Additionally, or alternatively, the RIC services may include a CONTROL service in which a near-real-time RIC 302 sends a CONTROL message to E2 node to initiate a new associated procedure or to resume a previously suspended associated procedure in the E2 node. Additionally, or alternatively, the RIC services may include a POLICY service in which a near-real-time RIC 302 uses an RIC subscription procedure and / or RIC subscription modification procedures to request that E2 node executes a specific POLICY during functioning of the E2 node after each occurrence of a defined RIC subscription procedure event trigger. Additionally, or alternatively, the RIC servicesmay include a QUERY service in which a near-real-time RIC 302 sends a QUERY message to an E2 node to retrieve RAN-related and / or UE-related information from the E2 node.

[0081] The service management and orchestration framework 306 may include an O-CU-CP 312 responsible for CP communication and signaling. The CP is a portion of a network that controls how data is exchanged (e.g., including a RRC layer), such as by defining a network topology or information for routing data packets. The O-CU-CP 312 may be connected to the near-real-time RIC 302 and / or other nodes of the service management and orchestration framework 306 (e.g., the O-eNB 308, 0-DU 310, and / or an O-CU-UP 314) via an 01 interface. The service management and orchestration framework 306 may include a O-CU-UP 314 that configures and controls the CU UP entities. The UP controls the creation of data packets (e.g., at a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and / or a medium access control (MAC) layer).

[0082] In some examples, the service management and orchestration framework 306 may include a Y1 interface for indicating analytics information from the near-real-time RIC 302 to one or more Y 1 consumers 316. The service management and orchestration framework 306 may include an 0-RU 318, which may be an RU that supports the 0-RAN architecture, as well as an O-cloud 320. The O-cloud 320 includes one or more hardware and software components that provide cloud computing capabilities to execute the RAN functions. The O-cloud 320 may be connected to one or more other devices in the service management and orchestration framework 306 via an interface 02 for the o-cloud 320. Similarly, the 0-RU 318 may be connected to one or more other devices in the service management and orchestration framework 306 via an open fronthaul (FH) management plane (M-Plane) interface that provides for one or more direct logical interfaces between management systems and the 0-RU 318. Additionally, or alternatively, the 0-RU 318 may be connected to the 0-DU by an open FH control user synchronization (CUS)-plane interface. The CUS plane is any combination of the CP, the UP, and a synchronization plane. The synchronization plane refers to traffic between the 0-RU 318 and / or 0-DU 310 to a synchronization controller. In some examples, a RAN node may refer to any of the devices and / or components illustrated in Figure 3, including, but not limited to, the 0-DU 310, the O-eNB 308, and the 0-DU. Similarly, the RAN controller, or control entity, may refer to any of the devices and / or components illustrated in Figure 3, including, but not limited to, the near-real-time RIC 302 and / or the non-real-time RIC

[0083] Figure 4 illustrates an example of a RAN layer diagram 400 in accordance with aspects of the present disclosure. In some examples, the RAN layer diagram 400 may implement, or be implemented by, aspects of the wireless communications system 100, the wireless communications system 200, and the RAN architecture diagram 300. The RAN layer diagram 400 may be implemented by a RAN node and a RAN controller, which may be examples of the corresponding devices as described with reference to Figures 1 through 3. For example, the RAN layer diagram 400 may illustrate examples of communication layers for signaling between one or more devices in a wireless communications system, such as a RAN node, a RAN controller, and / or a UE, among other devices.

[0084] In variations, communications among RAN nodes and / or a RAN controller may occur at a radio network layer 402. A protocol stack may include the radio network layer 402 and a transport network layer 404. The transport network layer 404 may be further divided into a transport layer 406, a network layer 408, a data link layer 410, and / or a physical layer 412. The transport layer 406 (e.g., the fourth layer (L4)) manages end-to-end communication and data flow control between devices on a network. The transport layer 406 performs error detection, error correction, and / or segmentation of a data transmission into data packets. The network layer 408 (e.g., the third layer (L3)) manages logical addressing, routing, and forwarding of data packets between devices. The data link layer 410 (e.g., the second layer (L2)) manages access to a physical medium for a transmission. The physical layer 412 (e.g., the first layer (LI)) managers the physical connection and transmission of raw binary data over a physical medium.

[0085] Figure 5 illustrates an example of signaling diagram 500 in accordance with aspects of the present disclosure. In some examples, the signaling diagram 500 may implement aspects of the wireless communications system 100, the wireless communications system 200, the RAN architecture diagram 300, and / or the RAN layer diagram 400. The signaling diagram 500 may illustrate an example of a framework for CLI measurement and reporting between one or more UEs, a RAN controller 502, and one or more RAN nodes 504. The RAN controller 502 and the RAN node 504 may be examples of corresponding devices (e.g., a RAN node 202 and a CN 106, respectively) as described with reference to Figures 1 through 4. Alternative examples of the following may be implemented, where some processes are performed in a different order thandescribed or are not performed. In some cases, processes may include additional features not mentioned below, or further processes may be added.

[0086] In some examples, a control entity (e.g., an RIC), which may additionally, or alternatively, be referred to as a RAN controller 502, may initiate a subscription procedure with a RAN node 504. The subscription procedure may include subscription information that includes parameters for monitoring and / or controlling one or more processes at a RAN node 504, including, but not limited to, CLI management processes. A subscription procedure may include one or more of subscription signaling, subscription modification signaling, subscription deletion signaling, and the like.

[0087] At 506, the RAN controller may transmit a message to the RAN node 504 including a subscription request. The subscription request may include subscription information indicating one or more parameters. The parameters may include a request identifier, a function identifier, a subscription details information element (IE), a subscription start-time, a subscription end-time, or a subscription duration. The request identifier may be a local identifier used to identify a functional procedure among a set of functional procedures initiated by a RAN node 504, a RAN controller 502, or both. Messages in a same procedure may use a same request identifier. That is, messages that follow the subscription request message may include a same value for a request identifier parameter to indicate that the messages are associated with the subscription procedure or the subscription request message. The RAN controller 502 and / or the RAN node 504 may determine the request identifier. The request identifier may include one or more of a requestor identifier, an instance identifier, or the like.

[0088] The function identifier may be unique for a RAN node 504, the RAN controller 502, or both. The function identifier may be associated with a function, such as a CLI management process, a duplexing enhancement process, a resource allocation process, a RAN control process, or the like. The subscription details IE may include details of the subscription request. The subscription details IE may include a list of one or more event trigger definitions (e.g., respective event triggers represented as an OCTET STRING or an IE indicating a condition that is evaluated to trigger one or more associated actions) and / or a list of one or more actions indicated by an action IE. The action IE may include an action identifier used to identify an associated action within the subscription procedure, an action type (e.g., REPORT, INSERT, POLICY, or the like), an action definition (e.g.,an OCTET STRING or an IE indicating a definition of the associated action according to a preconfiguration, a network configuration, a signaling among network entities, or the like), a subsequent action, which may include a subsequent action type (continue, resume, wait, halt, etc.) and / or a wait time in ms, seconds, or like, and / or an action execution order. In some examples, a condition that may trigger one or more actions for a CLI management process may be a CLI value exceeding a threshold, a wait timer expiring, or both. The subscription start-time and the subscription end-time or duration may indicate a time period during which the subscription is considered valid by the RAN controller 502.

[0089] In response to the subscription request, at 508, the RAN node may transmit a message to the RAN controller including a subscription response. The subscription response may include an indication that the non-real-time RIC 304 accepts one or more of the actions indicated by the subscription request message. The subscription response message may include one or more of the request identifier indicating the subscription response is associated with (e.g., for a same subscription as) the subscription request, the function identifier indicating the subscription response is associated with a function, a subset of action identifiers (e.g., including a subset of zero) for respective actions that are admitted or accepted by the RAN node 504, a subset of action identifiers (e.g., including a subset of zero) of the action identifiers associated with actions that are rejected (e.g., not admitted or accepted) by the RAN node 504, and / or one or more reasons or causes for the RAN node 504 not admitting or accepting the actions.

[0090] In some examples, upon accepting the actions by transmitting the subscription response, the RAN node 504 may execute the one or more actions that the RAN node 504 indicated as admitted or accepted. For example, the RAN node 504 may determine that one or more events are triggered according to the event trigger definitions provided in the subscription request. The conditions associated with the event trigger definitions may be examined during the subscription validity period as indicated by the subscription start-time and the subscription end-time or duration.

[0091] In some cases, at 510, the RAN node may transmit a message to the RAN controller including a subscription modification indication that indicates to the RAN controller that the RAN node is requesting an update to subscription information included in the subscription request at 506. At 512, the RAN controller may transmit a message to the RAN node including a subscriptionmodification request to modify an existing subscription. At 514, the RAN node may transmit a message to the RAN controller including a subscription modification response.

[0092] In some other cases, at 516, the RAN node may transmit a message to the RAN controller including a subscription deletion indication that indicates to the RAN controller that the RAN node is requesting for the subscription to be deleted and / or otherwise terminated. At 518, the RAN controller may transmit a message to the RAN node including a subscription deletion request. At 520, the RAN node may transmit a message to the RAN controller including a subscription deletion response. The subscription deletion response may include an indication of whether the request message is accepted (e.g., subscription deletion accept indication) and the subscription is deleted and / or may include an indication that the RAN node 504 failed to delete the subscription (e.g., a subscription deletion failure indication). The subscription deletion accept indication and the subscription deletion failure indication may indicate a full or partial admission or a full or partial rejection of the associated request, respectively.

[0093] In some cases, a message in subscription procedure signaling may include one or more parameters in addition to, or as an alternative to, the aforementioned identifier parameters. For example, the message may include identity information associated with the RAN controller 502 (e.g., a node identifier and / or an application identifier) and / or identity information associated with the subscription (e.g., a subscription identifier, a procedure instance identifier, and / or a process identifier). In some examples, one or more messages in the subscription procedure signaling may include identifier parameters, subscription details, parameters indicating the validity period of the subscription, and the like.

[0094] Prior to initiating the subscription procedure, the RAN controller 502 may determine information about services, functions, etc. provided by the RAN node 504. In some examples, the information may be provided to the RAN controller 502 by an operations, administration, and maintenance (0AM) configuration or 0AM signaling. In some other examples, the information may be exposed (e.g., provided or otherwise indicated) to the RAN controller 502 by the RAN node 504 via signaling on an interface, such as an E2 interface. The signaling may include an indication of a RAN node capability, service, or function for CLI management, an enhanced duplexing such as dynamic and / or flexible TDD, SBFD, or the like, a resource allocation process that uses CLI management, an existing CLI measured or detected by the RAN node 504, and / or the like. Theinformation provided by the RAN node 504 or other RAN nodes 504 within a threshold distance from the RAN node 504 may trigger the RAN node 504 to initiate a subscription procedure with the RAN node 504 and / or the other RAN nodes 504 for CLI management. In some other examples, another entity in the network, such as a network management entity, may receive the aforementioned indication (e.g., function exposure) from a RAN entity, such as the RAN node 504, and may indicate to an NE to initiate the subscription procedure. Thus, the RAN controller 502 may be triggered indirectly by information provided by the RAN node 504. In variations, signaling via an interface between the RAN node 504 and the RAN controller 502 may have a relationship with a cell configuration for the RAN node 504, UEs served by the RAN node 504, and the like. The configurations may be RRC configurations, higher layer configurations, LI and / or L2 signaling, or any combination thereof.

[0095] In some cases, the RAN node 504 exposes a function for CLI management in association with an enhanced duplexing configuration (e.g., a dynamic / flexible TDD (d / f-TDD) or SBED configuration). Lor example, the RAN node may expose the function prior to configuring a d / f-TDD or SBED configuration. The RAN node may proceed with configuring one or more UEs with d / f- TDD or SBFD operation upon establishing the subscription with the RAN controller 502. In some other examples, the RAN node 504 may expose the function and / or proceed with establishing the subscription upon configuring one or more UEs with d / f-TDD or SBFD.

[0096] In some other cases, the RAN node 504 may send a subscription modification indication (e.g., a subscription modification required message) to the RAN controller 502 in association with a change in an enhanced duplexing configuration (e.g., d / f-TDD or SBFD). For example, the RAN node 504 may send the message upon changing the configuration for one or more UEs. The message may be sent before or after the change in the configuration. In some examples, the RAN node 504 may change the configuration upon a successful modification of the associated subscription (e.g., upon receiving a subscription modification request from the RAN controller 502 and / or sending a subscription modification response to the RAN controller 502).

[0097] In some other cases, the RAN node 504 may send a subscription deletion indication (e.g., a subscription deletion required message) to the RAN controller 502 in association with terminating an enhanced duplexing configuration (e.g., d / f-TDD or SBFD). For example, the RAN node may send the message upon terminating the configuration for one or more UEs. The messagemay be sent before or after the termination of the configuration. In some realizations, the RAN node 504 may terminate the configuration before or after a successful deletion of the associated subscription (e.g., upon receiving a subscription deletion request from the RAN controller 502 and / or sending a subscription deletion response to the RAN controller 502).

[0098] In some other cases, the RAN node 504 may change the function exposure in association with a change or a termination of a configuration. For example, the RAN node 504 may expose a function with one or more parameters modified, compared to a prior exposure of the same or a similar function, in association with the change and / or termination of the configuration. In some other examples, the RAN node 504 may expose that the function is no longer available upon the change and / or termination of a configuration.

[0099] In variations, signaling between the RAN node 504 and the RAN controller 502 may include a copy of one or more IES, such as RRC configuration IES and / or Xn or NG IES, that include information related to a function or a subscription. For example, a function exposure message or a subscription procedure message may include a copy of a d / f-TDD configuration IE, an SBFD configuration IE, or the like. In some examples, the IE may be an RRC IE, such as a TDD Config-Common IE, a TDD Config-Dedicated IE, an SBFD Config IE, or the like. In some other examples, the IE may be an Xn IE or an NG IE, such as an Intended TDD Config IE, an Intended SBFD Config IE, or the like. The copy of the IE may be communicated as an OCTET STRING according to a message copy service for the interface (e.g., an E2 interface) between the RAN node 504 and the RAN controller 502.

[0100] In some examples, the subscription procedure may be a procedure with a type of REPORT for CLI reporting by one or more RAN nodes. The subscription procedure messages may include one or more of an indication of a reporting action (e.g., Action = REPORT). Additionally, or alternatively, the subscription procedure may be a procedure with a type of CONTROL for managing CLI at one or more RAN nodes. The subscription procedure messages may include one or more of an indication of a reporting action (e.g., Action = CONTROL). Additionally, or alternatively, the subscription procedure may be a procedure with a type INSERT for managing CLI during a REPORT procedure and / or a CONTROL procedure at one or more RAN nodes. The subscription procedure messages may include one or more of an indication of a reporting action (e.g., Action = INSERT). Additionally, or alternatively, the subscription procedure may be aprocedure with a type of POLICY for managing CLI. The subscription procedure messages may include one or more of an indication of a reporting action (e.g., Action = POLICY).

[0101] In some examples, the RAN node 504 and / or the RAN controller 502 may exchange the subscription signaling to address base station-to-base station (e.g., RAN node-to-RAN node) CLI management through various services and interfaces, such as REPORT, INSERT, CONTROL, POLICY services on an E2 and / or 01 interface, and signaling on conventional point-to-point RAN interfaces, such as Xn and NG. Additionally, or alternatively, the RAN node 504 and / or the RAN controller 502 may exchange subscription procedure signaling to address UE-to-UE CLI management via a UE, such that the UE that transmits reference signals and measures the CLI. For managing UE-to-UE CLI, the RAN node 504 may configure one or more UEs to transmit a reference signal (e.g., an SRS) and / or to perform a measurement to obtain a CLI value for reporting. The CLI value may be an RSRP or an RSSI. For obtaining an RSRP as a measure of CLI, the UE may perform a measurement on a reference signal, such as an SRS transmitted by another UE, in which case the RSRP is referred to as SRS-RSRP. In order to perform the measurement, the UE may be configured with information of the SRS, such as RSR resources, SRS sequence, and the like. Additionally, or alternatively, for obtaining an RSSI as a measure of CLI, the UE may perform a measurement on a set of time-frequency resources. The quantity may be referred to as CLLRSSI.

[0102] Unlike obtaining CLLRSSI, obtaining SRS-RSRP may include the measuring UE acquiring information for an SRS configuration. If the transmitting UE and the measuring UE are in different cells, then there may be inter-cell coordination of the SRS configuration information. Furthermore, unlike CLLRSSI, SRS-RSRP provides a measure of CLI from a specific source (e.g., the transmitting UE), as opposed to CLLRSSI that provides a measure of CLI from each source in the vicinity that transmits a signal on the measured resources. In some cases, a first UE served by a first RAN node is subject to CLI from a second UE served by a second RAN node. If the first UE measures an SRS-RSRP as a measure of the CLI, then the first UE is to be configured, by the first RAN node, with information of an SRS transmitted by the second UE. Therefore, the second UE is also to be configured, by the second RAN node, with information of the SRS. The configurations may include a direct or indirect coordination (e.g., through a RAN controller 502). An SRS-RSRP, CLLRSSI, or other measure of CLI may be referred to as a CLI or CLI value.

[0103] In various embodiments, some or all the information of the SRS configuration may be indicated by subscription information and / or subscription signaling. In various embodiments, some of all the information for the CLI measurement and reporting configuration may be indicated by subscription information and / or subscription signaling. In various embodiments, the RAN node 504 may report a CLI value to a RAN controller 502 upon detecting an event related to the CLI measurement and reporting. In various embodiments, the RAN node 504 may be indicated, through a control signaling, to execute a CLI management action, which may include a change in a parameter, a configuration, or a signaling with one or more UEs.

[0104] Figure 6 illustrates an example of signaling diagram 600 in accordance with aspects of the present disclosure. In some examples, the signaling diagram 600 may implement aspects of the wireless communications system 100, the wireless communications system 200, the RAN architecture diagram 300, the RAN layer diagram 400, and the signaling diagram 500. The signaling diagram 600 may illustrate an example of an inter-UE framework for CLI measurement and reporting between a RAN controller 602, a RAN node 604, and a UE 104. The RAN controller 602, the RAN node 604, and the UE 104 may be examples of corresponding devices (e.g., a RAN node 202, a CN 106, and a UE 104, respectively) as described with reference to Figures 1 through 4.Alternative examples of the following may be implemented, where some processes are performed in a different order than described or are not performed. In some cases, processes may include additional features not mentioned below, or further processes may be added.

[0105] In some examples, at 606, a control entity (e.g., a RIC), which may additionally, or alternatively, be referred to as a RAN controller 602, may initiate a subscription procedure with a RAN node 604. The subscription procedure may include subscription information that includes parameters for monitoring and / or controlling one or more processes at a RAN node 604 and / or the UE 104, including, but not limited to, CLI management processes.

[0106] At 608, the RAN controller 602 and the RAN node 604 may exchange one or more messages for a subscription procedure with a type of REPORT. A subscription procedure may include one or more of subscription signaling, subscription modification signaling, subscription deletion signaling, and the like. In some examples, the RAN controller 602 may send, in one or more messages in the subscription procedure, subscription information including one or more parameters for CLI reporting by the RAN node 604 and / or the UE 104 to the RAN controller 602. The subscription procedure messages may include one or more of an indication of a reporting action(e.g., Action = REPORT), an indication that the value to be reported is a CLI (e.g., key performance measurement (KPM) = CLI), or an indication of what triggers a CLI reporting message (e.g., a trigger condition for CLI reporting).

[0107] A KPM may be specified for measurements and reporting for a RAN and / or a CN (e.g., for network functions). An associated service model may support a RAN node 604 (e.g., a base station, a CU at a base station, and / or a DU at a base station). The RAN node 604 may host a RAN function “KPM Monitor” performing functionalities, such as exposure of available measurements from the RAN node 604, and / or reporting of measurements subscribed from the RAN controller 602, among other functionalities. The “KPM Monitor” RAN function may provide REPORT services, such as measurements by a RAN node 604, measurements by a UE 104, measurements for a UE 104 or a group of UEs, UE-specific condition-based measurements, and / or common condition-based measurements, among other services. Various message formats may be specified or configured for a KPM IE. In some examples, a KPM IE may include one or more values of a KPM (e.g., CLI, excess CLI, signal strength, signal quality, or the like). For example, the values of a KPM may include RSRP, CSI-RSRP, SSB-RSRP, SRS-RSRP, RSRQ, RSSI, or the like. The KPM IE may further include one or more of information of associated resources in the time domain, frequency domain, code domain, spatial domain (e.g., beams), information of how the associated measurements are performed, information of associated signaling (e.g., identifier parameters indicating a subscription, a function, a procedure instance, a RAN node 604), information of the condition that triggered the KPM signaling, information of a status of the RAN node 604, information of a status of the UE 104, a subsequent action after the KPM signaling, or the like. In variations, the term KPM = CLI may imply that a KPM IE with one or more values of a CLI (e.g., CLI, excess CLI, signal strength, signal quality, or the like) is communicated in a KPM IE that may include one or more parameters conveying the information.

[0108] In some examples, the subscription information may indicate for the RAN node 604 to perform a periodic reporting of CLI. For example, a parameter included in the subscription information may indicate a value of a periodicity for the CLI reporting. The RAN node 604 may measure CLI (e.g., may obtain one or more CLI values). For example, the RAN node 604 may determine a periodicity timer is expired, which may trigger CLI reporting.

[0109] In some examples, the RAN controller 602 may indicate, through the subscription procedure signaling, information on what CLI measure for the RAN node 604 to include in the CLIreporting. For example, the RAN controller 602 may indicate to the RAN node 604 to report an RSSI as a measure of CLI. The RAN controller 602 may further indicate resources on which the RSSI is to be measured. The RAN controller 602 may indicate to a first set of RAN nodes, including the RAN node 604, to avoid using the resources for transmissions by the set RAN nodes, the UEs served by the set of RAN nodes, or both. The RAN node 604 may measure RSSI associated with transmissions from a second set of RAN nodes, UEs served by the second set of RAN nodes, or both. In some examples, the RAN controller 602 may indicate the resources as one or more of resources in the time domain (e.g., one or more symbols, slots, subframes, and / or frames), resources in the frequency domain (e.g., one or more subcarriers, physical RBs (PRBs), RB groups (RBGs), sub-bands, BWPs, CCs, and / or frequency bands), resources in the spatial domain (e.g., one or more beams, beam groups, and / or directions), resources in a code domain, resources (e.g., in time, frequency, spatial, and / or code domains) associated with one or more signals or channels, resources associated with a stream, a quality of service (QoS) flow, a radio bearer, or the like, and / or resources associated with a network slice. A beam or beam group may be indicated by a relationship with a reference signal (e.g., a reference signal identifier, an SSB index, and / or a QCL relationship). A signal or channel may be indicated by a configuration identifier, resource identifier, or the like associated with the signal or channel.

[0110] In some examples, the RAN controller 602 may indicate to the RAN node 604 to report an RSRP associated with a reference signal that is transmitted by a second RAN node, UEs served by the second RAN node, or both. The RAN controller 602 may further indicate to the second RAN node to transmit the reference signal or configure UEs served by the second RAN node to transmit the reference signal. In some cases, the reference signal may be a downlink reference signal such as a synchronization signal, an SSB, and / or a CSI-RS transmitted by the second RAN node. In some other cases, or the reference signal may be an uplink reference signal such an SRS transmitted by one or more UEs served by the second RAN node.

[0111] The reference signal may be indicated by parameters describing a reference signal type (e.g., synchronization signal, SSB, CSI-RS, SRS, etc.), reference signal resources (e.g., in a time domain, a frequency domain, a spatial domain, and / or a code domain), a pattern in the time-domain (e.g., periodic, semi-persistent, aperiodic, and / or event-triggered) and / or a frequency-domain (e.g., comb pattern and / or SRS switching pattern), a sequence seed, and the like. In some cases, the parameters may be defined individually in the formats of the messages in the subscription proceduresignaling. In some other cases, the parameters may be communicated as an OCTET STRING in the subscription procedure signaling. The OCTET STRING may then be decoded by the RAN node 604 at the transport layer, RRC layer, or the like. In some other cases, any combination of fields in the message format and information in OCTET STRING fields may be used for indicating the parameters. If a parameter is indicated in both the message format and information in OCTET STRING fields, the value in the message may take precedence over the value conveyed through the OCTET STRING field, or vice versa, as configured or defined (e.g., by the 0AM or the network), indicated by a signaling, or any combination thereof. The OCTET STRING field may be obtained by a message copy service. In some examples, the RAN controller 602 may indicate to the RAN node 604 to report an RSSI, an SINR, an RSRQ, and / or an RSRP as a measure of CLI.

[0112] The RAN controller 602 may indicate, through the subscription procedure signaling information on how to measure CLI. For example, the RAN controller 602 may indicate to the RAN node 604 to configure a UE to perform a CLI measurement and may configure the RAN node 604 and / or the UE to examine the measured CLI to determine whether an event is triggered. The RAN controller 602 may indicate for the RAN node 604 to determine whether the measured CLI reported by the UE exceeds one or more threshold values (e.g., a threshold RSSI, a threshold SINR, a threshold RSRQ, and / or a threshold RSRP). Additionally, or alternatively, the RAN controller 602 may indicate a periodicity for performing CLI measurements at the UE, which may or may not be equal to a periodicity for CLI reporting.

[0113] In some other examples, the RAN controller 602 may indicate for the RAN node 604 to configure a UE to perform multiple CLI measurements and for the RAN node 604 and / or the UE to examine an average or a maximum of the measured CLI values for determining whether an event is triggered. For example, the RAN node 604 may receive an indication of a numerical quantity, N, of CLI measurements to perform for computing an average or maximum. Additionally, or alternatively, the RAN node 604 may receive an indication of a periodicity for performing the CLI measurements. The periodicity may be indicated in units of slots, subframes, frames, ms, seconds, or the like. In some other examples, the RAN controller 602 may indicate to the RAN node 604 that an event is triggered if one or more CLI values exceed a threshold for a minimum numerical quantity, N, of consecutive CLI measurements. In some other examples, the RAN controller 602 may indicate to the RAN node 604 that an event is triggered if a minimum numerical quantity, M,of CLI values exceed a threshold value in a numerical quantity, N, of consecutive CLI measurements. In variations, the RAN controller 602 may indicate to the RAN node 604 to report a single CLI value, an average CLI value, a maximum CLI value, a subset of N CLI values, or a set of CLI values obtained from the measurements. In some cases, values of periodicity, threshold, N, M, and the like may be indicated to the RAN node 604 through the subscription procedure signaling, configured by the network, preconfigured, or otherwise defined, determined by implementation, or any combination thereof.

[0114] In some examples, the CLI report may be used for taking a CLI mitigation action. For example, the RAN controller 602 may make use of a CONTROL service signaling to indicate to the RAN node 604, or other RAN nodes a threshold distance from the RAN node 604, to perform a CLI mitigation action and / or to indicate to a UE to perform a CLI mitigation action. For example, CLI mitigation actions may include, but are not limited to, reducing a transmission power when transmitting a signal that causes excessive CLI, avoiding or refraining from communicating using one or more beams that cause excessive CLI, avoiding or refraining from communicating using a set of time-frequency resources, such that another RAN node and / or the UE may use the set of timefrequency resources for communications without experiencing excessive CLI, or any combination thereof.

[0115] In some examples, a CLI report from a UE to a RAN node 604 and / or from the RAN node 604 to the RAN controller 602 may include one or more parameters. The parameters may include one or more values of CLI (e.g., X decibel-milliwatts (dBm)). The RAN node 604 may obtain a CLI value by one or more measurements as indicated by the subscription procedure, indicated by a network and / or 0AM configuration, preconfigured or otherwise defined, determined by an implementation, or any combination thereof. A relatively large CLI value (e.g., greater than or above a threshold value) may indicate an excessive CLI experienced by the RAN node 604 or the UE (e.g., a UE served by the RAN node 604). The RAN node 604 may round the CLI value (e.g., the value of X) to the nearest value in an enumerated set as configured or specified. In some cases, the parameters may include one or more values of excess CLI (e.g., Y decibels (dB)). The RAN node 604 may report an excess CLI value Y above a threshold value, T dB, in addition to, or as an alternative to, reporting the absolute CLI value (e.g., X dBm). The excess CLI value may be obtained by subtracting T from X (e.g., Y = X — T). The RAN node 604 may determine the valueof T from information indicated in the subscription procedure, configured by the network and / or OAM, determined according to a signal strength associated with the signal or the UE experiencing the CLI, determined based on an implementation, or any combination thereof. In some examples, the RAN node 604 may indicate the threshold value in the CLI report or other signaling. The RAN node 604 may round the value of Y to the nearest value in an enumerated set as configured or specified. In some examples, the RAN controller 602 may use the value of Y, as reported by a RAN node 604, to request a reduction of a transmission power by Y dB via CONTROL signaling (e.g., for a REPORT, CONTROL service and an INSERT, CONTROL service).

[0116] In some examples, the parameters include an indication of associated beams. Lor example, the RAN node 604 may associate a CLI value and / or excess CLI value with respective beams or spatial directions, which may indicate that the CLI or excess CLI is experienced when receiving signals through the beams or spatial directions. A beam or spatial direction may be indicated by a beam index, a reference signal index, a reference signal resource identifier, a QCL relationship, a direction, or any combination thereof.

[0117] In some examples, the parameters include an indication of associated resources. A CLI value and / or an excess CLI value may be associated with one or more communication resources, which may indicate that the CLI or excess CLI is experienced when receiving signals or channels that occur on, or overlap with, those communication resources. The communication resources may be indicated as one or more of resources in a time domain (e.g., one or more symbols, slots, subframes, and / or frames), resources in the frequency domain (e.g., one or more subcarriers, PRBs, RBGs, sub-bands, BWPs, CCs, and / or frequency bands), resources in the spatial domain (e.g., one or more beams, beam groups, and / or directions), resources in a code domain, resources (e.g., in a time domain, a frequency domain, a spatial domain, and / or a code domain) associated with one or more signals or channels, resources associated with a stream, a QoS flow, a radio bearer, or the like, and / or resources associated with a network slice. A beam or beam group may be indicated by a relationship with a reference signal (e.g., a reference signal identifier, a synchronization signal and / or SSB index, or a QCL relationship). A signal or channel may be indicated by a configuration identifier, a resource identifier, or the like associated with the signal or channel. Additionally, or alternatively, a CLI report may include one or more identifier parameters that indicate anassociation with one or more of a subscription, a configuration, a function, a procedure instance, a RAN node 604, a group of RAN nodes, a cell, a group of cells, a UE, a group of UEs, or the like.

[0118] In some examples, the subscription information may indicate for the RAN node 604 to indicate to the UE 104 to perform a periodic reporting of CLI and / or may indicate for the RAN node 604 to perform a periodic reporting of CLI. For example, a parameter included in the subscription information may indicate a value of a periodicity for the CLI reporting. At 610, the RAN node 604 and the UE 104 may transmit and / or receive a CLI reporting configuration. The CLI reporting configuration may indicate the periodicity (e.g., may include a parameter with a value that indicates the periodicity). The UE 104 may set a periodicity timer to a value indicated in the CLI reporting configuration.

[0119] At 612, the UE 104 may measure CLI. For example, the UE 104 may obtain one or more CLI values. A RAN controller 602 performs subscription procedure signaling with a RAN node 604 and another RAN node. The RAN node 604 configures a CLI measurement and reporting for a UE 104 served by the RAN node 604. The other RAN node configures a reference signal, such as an SRS, for another UE served by the other RAN node, which is described in further detail with respect to Figure 7. The UE 104 performs a CLI measurement on the reference signal from the other UE (e.g., at 612). In some examples, at 614, the UE 104 may compare a CLI value to a threshold value. The UE 104 sends a CLI report including a measured CLI value, in accordance with the configuration from the RAN node 604, periodically or upon determining that the CLI value is above a threshold. For example, at 616, the UE 104 may transmit a CLI report to the RAN node 604. In some cases, the UE 104 may transmit the CLI report if the CLI value satisfies (e.g., exceeds, is greater than, is above) a threshold value and / or if the UE 104 determines a periodicity timer is expired. That is, the periodicity timer expiring and / or the CLI value satisfying the threshold value may trigger CLI reporting from the UE 104 to the RAN node 604. In variations, the RAN node 604 can indicate the periodicity and / or the threshold value in the CLI reporting configuration at 610.

[0120] In some examples, the UE 104 may report the CLI value to the RAN node 604 without comparing the CLI value to a threshold value. For example, at 616, the UE 104 may transmit a CLI report to the RAN node 604 without comparing a CLI value in the report to a threshold value. In some examples, the RAN node 604 may perform the comparison in addition to, or as an alternative to, the UE 104 comparing the CLI values to the threshold value. For example, at 618, the RAN node 604 may compare the CLI value to a threshold value. At 620, the RAN node 604 may transmit aRAN controller CLI indication to the RAN controller 602 that indicates a CLI value and / or indicates that the CLI value satisfies (e.g., exceeds, is greater than, is above) the threshold value. In some examples, the RAN controller 602 and / or the RAN node 604 may indicate, through the subscription procedure signaling at 608 and / or through the CLI reporting configuration at 610, information on what CLI measure for the RAN node 604 and / or the UE 104 to include in the CLI reporting at 616 and at 620.

[0121] For example, the RAN controller 602 may indicate to the RAN node 604 to report and / or may indicate to the RAN node 604 to instruct the UE 104 to report an RSSI as a measure of CLI. The RAN controller 602 may further indicate resources on which the RSSI is to be measured. The RAN controller 602 may indicate to a first set of RAN nodes, including the RAN node 604, to avoid using the resources for transmissions by the set RAN nodes, the UEs served by the set of RAN nodes, or both. Then, the RAN node 604 may configure a UE 104 to measure RSSI associated with transmissions from UEs 104 served by a second set of RAN nodes. In some examples, the RAN controller 602 may indicate the resources as one or more of resources in the time domain (e.g., one or more symbols, slots, subframes, and / or frames), resources in the frequency domain (e.g., one or more subcarriers, PRBs, RBGs, sub-bands, BWPs, CCs, and / or frequency bands), resources in the spatial domain (e.g., one or more beams, beam groups, and / or directions), resources in a code domain, resources (e.g., in time, frequency, spatial, and / or code domains) associated with one or more signals or channels, resources associated with a stream, a quality of service (QoS) flow, a radio bearer, or the like, and / or resources associated with a network slice. A beam or beam group may be indicated by a relationship with a reference signal (e.g., a reference signal identifier, an SSB index, and / or a QCL relationship). A signal or channel may be indicated by a configuration identifier, resource identifier, or the like associated with the signal or channel.

[0122] In some examples, the RAN controller 602 may indicate to the RAN node 604 to report and / or may indicate to the RAN node 604 to instruct the UE 104 to report an RSRP associated with one or more reference signals that are transmitted by one or more UEs served by a second RAN node. The RAN controller 602 may further indicate to configure the UEs to transmit the reference signal. In some cases, the reference signal may be an uplink reference signal, such an SRS transmitted by one or more UEs served by the second RAN node.

[0123] The reference signal may be indicated by parameters describing a reference signal type (e.g., SRS), reference signal resources (e.g., in a time domain, a frequency domain, a spatialdomain, and / or a code domain), a pattern in the time-domain (e.g., periodic, semi-persistent, aperiodic, and / or event-triggered) and / or a frequency-domain (e.g., comb pattern and / or SRS switching pattern), a sequence seed, and the like. In some cases, the parameters may be defined individually in the formats of the messages in the subscription procedure signaling. In some other cases, the parameters may be communicated as an OCTET STRING in the subscription procedure signaling at 608. The OCTET STRING may then be decoded by the RAN node 604 at the transport layer, RRC layer, or the like. In some other cases, any combination of fields in the message format and information in OCTET STRING fields may be used for indicating the parameters. If a parameter is indicated in both the message format and information in OCTET STRING fields, the value in the message may take precedence over the value conveyed through the OCTET STRING field, or vice versa, as configured or defined (e.g., by the 0AM or the network), indicated by a signaling, or any combination thereof. The OCTET STRING field may be obtained by a message copy service. In some examples, the RAN controller 602 may indicate to the RAN node 604 and / or may indicate to the RAN node 604 to instruct the UE 104 to report an RSSI, an SINR, an RSRQ, and / or an RSRP as a measure of CLI.

[0124] The RAN controller 602 may indicate, through the subscription procedure signaling at 608, information on how to measure CLI. For example, the RAN controller 602 may indicate to the RAN node 604 to configure the UE 104 to perform a CLI measurement and to configure the UE 104 to examine the measured CLI and / or for the RAN node 604 to examine the CLI measured by the UE to determine whether an event is triggered. The RAN controller 602 may indicate for the RAN node 604 and / or the UE 104 to determine whether the measured CLI exceeds one or more threshold values (e.g., a threshold RSSI, a threshold SINR, a threshold RSRQ, and / or a threshold RSRP). Additionally, or alternatively, the RAN controller 602 may indicate a periodicity for performing CLI measurements, which may or may not be equal to a periodicity for CLI reporting.

[0125] In some other examples, the RAN controller 602 may indicate for the RAN node 604 and / or the UE 104 to perform multiple CLI measurements and examine an average or a maximum of the measured CLI values for determining whether an event is triggered. For example, the RAN node 604 may receive an indication of a numerical quantity, N, of CLI measurements to perform for computing an average or maximum. Additionally, or alternatively, the RAN node 604 may receive an indication of a periodicity for performing the CLI measurements. The periodicity may be indicated in units of slots, subframes, frames, milliseconds, seconds, or the like. In some otherexamples, the RAN controller 602 may indicate to the RAN node 604 that an event is triggered if one or more CLI values exceed a threshold for a minimum numerical quantity, N, of consecutive CLI measurements. In some other examples, the RAN controller 602 may indicate to the RAN node 604 that an event is triggered if a minimum numerical quantity, M, of CLI values exceed a threshold value in a numerical quantity, N, of consecutive CLI measurements. In variations, the RAN controller 602 may indicate to the RAN node 604 to report a single CLI value, an average CLI value, a maximum CLI value, a subset of N CLI values, or a set of CLI values obtained from the measurements. In some cases, values of periodicity, threshold, N, M, and the like may be indicated to the RAN node 604 through the subscription procedure signaling, configured by the network, preconfigured, or otherwise defined, determined by implementation, or any combination thereof.

[0126] In some examples, a CLI report from a RAN node 604 and / or from a UE 104 may include one or more parameters. The parameters may include one or more values of CLI (e.g., X decibel-milliwatts (dBm)). The RAN node 604 may obtain a CLI value by one or more measurements as indicated by the subscription procedure, indicated by a network and / or 0AM configuration, preconfigured or otherwise defined, determined by an implementation, or any combination thereof. A relatively large CLI value (e.g., greater than or above a threshold value) may indicate an excessive CLI experienced by the RAN node 604 or a UE served by the RAN node 604. The RAN node 604 may round the CLI value (e.g., the value of X) to the nearest value in an enumerated set as configured or specified. In some cases, the parameters may include one or more values of excess CLI (e.g., Y dB). The RAN node 604 may report an excess CLI value Y above a threshold value, T dB, in addition to, or as an alternative to, reporting the absolute CLI value (e.g., X dBm). The excess CLI value may be obtained by subtracting T from X (e.g., Y = X — T). The RAN node 604 may determine the value of T from information indicated in the subscription procedure, configured by the network and / or 0AM, determined according to a signal strength associated with the signal or the UE experiencing the CLI, determined based on an implementation, or any combination thereof. In some examples, the RAN node 604 may indicate the threshold value in the CLI report or other signaling. The RAN node 604 may round the value of Y to the nearest value in an enumerated set as configured or specified. In some examples, the RAN controller 602 may use the value of Y, as reported by a RAN node 604, to request a reduction of a transmission power by Y dB via CONTROL signaling.

[0127] In some examples, the parameters include an indication of associated beams. For example, the RAN node 604 may associate a CLI value and / or excess CLI value with respective beams or spatial directions, which may indicate that the CLI or excess CLI is experienced when receiving signals through the beams or spatial directions. A beam or spatial direction may be indicated by a beam index, a reference signal index, a reference signal resource identifier, a QCL relationship, a direction, or any combination thereof.

[0128] In some examples, the parameters include an indication of associated resources. A CLI value and / or an excess CLI value may be associated with one or more communication resources, which may indicate that the CLI or excess CLI is experienced when receiving signals or channels that occur on, or overlap with, those communication resources. The communication resources may be indicated as one or more of resources in a time domain (e.g., one or more symbols, slots, subframes, and / or frames), resources in the frequency domain (e.g., one or more subcarriers, PRBs, RBGs, sub-bands, BWPs, CCs, and / or frequency bands), resources in the spatial domain (e.g., one or more beams, beam groups, and / or directions), resources in a code domain, resources (e.g., in a time domain, a frequency domain, a spatial domain, and / or a code domain) associated with one or more signals or channels, resources associated with a stream, a QoS flow, a radio bearer, or the like, and / or resources associated with a network slice. A beam or beam group may be indicated by a relationship with a reference signal (e.g., a reference signal identifier, a synchronization signal and / or SSB index, or a QCL relationship). A signal or channel may be indicated by a configuration identifier, a resource identifier, or the like associated with the signal or channel. Additionally, or alternatively, a CLI report may include one or more identifier parameters that indicate an association with one or more of a subscription, a configuration, a function, a procedure instance, a RAN node 604, a group of RAN nodes, a cell, a group of cells, a UE 104, a group of UEs, or the like.

[0129] At 622, the RAN controller 602 may receive and process the CLI measurements. In some examples, the CLI report from the UE 104 to the RAN node 604 and / or from the RAN node 604 to the RAN controller 602 may be used for taking a CLI mitigation action. For example, the RAN controller 602 may make use of a CONTROL service signaling to indicate to the RAN node 604, or other RAN nodes a threshold distance from the RAN node 604, to perform a CLI mitigation action and / or to indicate for a RAN node 604 to indicate to a UE 104 to perform a CLI mitigation action. For example, CLI mitigation actions may include, but are not limited to, reducing atransmission power when transmitting a signal that causes excessive CLI, avoiding or refraining from communicating using one or more beams that cause excessive CLI, avoiding or refraining from communicating using a set of time-frequency resources, such that another RAN node may use the set of time-frequency resources for communications without experiencing excessive CLI, or any combination thereof.

[0130] Figure 7 illustrates an example of signaling diagram 700 in accordance with aspects of the present disclosure. In some examples, the signaling diagram 700 may implement aspects of the wireless communications system 100, the wireless communications system 200, the RAN architecture diagram 300, the RAN layer diagram 400, the signaling diagram 500, and the signaling diagram 600. The signaling diagram 700 may illustrate an example of an inter-UE framework for CLI measurement and reporting between a RAN controllers 702, one or more RAN nodes 704 (e.g., a RAN node 1 and a RAN node 2), and one or more UEs 104 (e.g., a UE 1 and a UE 2). The RAN controller 702 and the RAN node 704 may be examples of corresponding devices (e.g., a RAN node 202 and a CN 106, respectively) as described with reference to Figures 1 through 4. Alternative examples of the following may be implemented, where some processes are performed in a different order than described or are not performed. In some cases, processes may include additional features not mentioned below, or further processes may be added.

[0131] In some examples, although the signaling diagram 700 illustrates two RAN nodes 704 and two UEs, the processes may be performed by any numerical quantity of RAN nodes 704 (e.g., one RAN node 704, more than two RAN nodes 704) and any numerical quantity of UEs 104 (e.g., one UE 104, more than two UEs 104). For example, the processes described as being performed by the RAN node 1 may additionally, or alternatively, be performed by the RAN node 2. Similarly, the processes described as being performed by the UE 1 may additionally, or alternatively, be performed by the UE 2.

[0132] At 706, the RAN node 1, the RAN node 2, the UE 1, the UE 2, and / or the RAN controller 702 may perform initial processes. The initial processes may be for a subscription procedure, including exchanging signaling related to the subscription procedure, as described with reference to Figures 5 and 6.

[0133] At 708, the RAN controller 702 and the RAN node 1 may perform a subscription procedure with a type of REPORT. For example, the RAN controller 702 and the RAN node 1 may exchange signaling, as described with reference to Figures 5 and 6. The subscription procedure mayinclude one or more of a subscription signaling, a subscription modification signaling, and the like. The RAN controller 702 may transmit, in one or more messages in the subscription procedure, information for CLI reporting by the RAN node 1 to the RAN controller 702 and / or information for CLI reporting by the UE 1 to the RAN node 1. For example, the RAN controller 702 may transmit a message that indicates subscription information including at least one parameter indicating a configuration of a reference signal for managing CLI. Additionally, or alternatively, the subscription procedure messages may include one or more of an indication of a reporting action (e.g., Action = REPORT) or an indication that the value to be reported is a CLI (e.g., KPM = CLI). Additionally, or alternatively, the subscription procedure messages may include a parameter that indicates for the RAN node 1 to indicate to the UE 1 to perform at least one CLI measurement to obtain at least CLI value.

[0134] In some examples, the subscription procedure may indicate a trigger condition or trigger event for CLI reporting. For example, the RAN controller 702 may indicate to the RAN node 1 and / or to configure the UE 1 to send a CLI report periodically, upon a measured CLI exceeding a threshold, or both. In some cases, the RAN controller 702 may indicate to the RAN node 1, through the subscription procedure signaling, a value for a periodicity, a value for a CLI threshold, or both.

[0135] At 710, the RAN node 1 may exchange CLI reporting configuration signaling with the UE 1. For example, the CLI reporting configuration signaling may indicate for the UE 1 to perform at least one CLI measurement to obtain at least CLI value. The CLI reporting configuration may additionally, or alternatively, indicate a periodicity for performing a CLI measurement and / or report, one or more parameters that define how to perform the measurement and / or information to include in the report, among other information.

[0136] At 712, the RAN controller 702 and the RAN node 2 may perform a subscription procedure. For example, the subscription procedure may inform the RAN node 2 of one or more SRS parameters for a reference signal transmission by a UE 2. The subscription procedure may include a parameter that indicates for the RAN node 2 to indicate that the UE 2 transmit the reference signal (e.g., an SRS).

[0137] At 714, the RAN node 2 may exchange SRS configuration signaling with the UE 2. Although SRS configuration signaling is described, the configuration signaling may be configuration signaling for any type of reference signal. In some examples, an SRS is an uplink reference signal that a UE 104 may transmit for channel measurement and / or interferencemeasurement. The SRS may be used for measuring the uplink channel from the UE 104 to a serving base station. The SRS may also be used for UE-to-UE CLI measurements to a UE 1 (e.g., a UE being impacted by interference) from a UE 2 (e.g., a UE causing interference) provided that the UE 1 is informed of the configuration parameters of the SRS that the UE 2 transmits. Then, the measured signal strength of the SRS (e.g., SRS-RSRP) may be considered as the measure of the CLI, which can be reported to the network, used for CLI mitigation, and so on.

[0138] The SRS configuration parameters may include parameters of time-frequency resources allocated to the SRS, sequence parameters, and so on. In some cases, such as for intra-cell CLI, when two UEs are served by a same base station, the base station may send, to the UE 2, an SRS configuration including SRS parameter values for SRS transmission and send, to the UE 1 , a CLI measurement and reporting configuration including, in part, the SRS parameter values. The UE 1 uses the information to measure and report CLI in accordance with the configuration. However, for inter-cell CLI, when the two UEs are served by different base stations, the SRS parameter values for measuring and reporting CLI are exchanged between the base stations.

[0139] In various examples, the SRS parameter values may be set through the subscription procedure signaling between the RAN controller 702 and the RAN node 2. In some examples, the SRS parameters may be set by the RAN node 2 and indicated to the RAN controller 702. In some other examples, the RAN controller 702 indicates the SRS parameter values to the RAN node 2. In some other examples, a handshaking or negotiation signaling may be used by the RAN node 2 and the RAN controller 702 to agree on SRS parameter values. Then, the RAN node 2 configures the UE 2 with an SRS with the SRS parameter values.

[0140] The RAN controller 702 further indicates the SRS parameter values to the RAN node 1 through a subscription procedure signaling for CLI measurement and reporting. The RAN node 1 then uses the information to configure the UE 1 with a CLI measurement and reporting in association with the SRS parameter values. The UE 1 measures and reports the CLI value, which may be an SRS-RSRP as configured by the base station (e.g., the RAN node 1). A relatively large numerical quantity of SRS parameters (e.g., greater than a threshold) indicate radio resources, such as REs, on which the SRS is transmitted. In some examples, the parameters indicated by SRS- Resource and SRS-ResourceSet IES may include one or more resource type parameters (e.g., aperiodic, semi-persistent, periodic), one or more usage parameters (e.g., beam management, codebook, non-codebook, antenna switching), one or more power control parameters (e.g., alpha,pO, path-loss reference signal, power control adjustment states), a parameter indicating a numerical quantity of ports (e.g., 1, 2, 4, etc.), one or more parameters indicating a resource mapping in a time domain (e.g., starting position, repetition), one or more parameters indicating a resource mapping in a frequency domain (e.g., position, shift, comb pattern, frequency hopping, partial frequency sounding), one or more parameters indicating beam and / or spatial relation information (e.g., QCL), or one or more parameters indicating a relationship with other reference signals (e.g., CSI-RS, SSB), among others. In various realizations, one or more SRS parameters may be indicated to the UE 1 and the UE 2 through respective configurations from the RAN node 1 and the RAN node 2.

[0141] At 716, the UE 2 may transmit one or more SRSs over the air to the RAN node 2, the RAN controller 702, the RAN node 1, and / or the UE 1. For example, the UE 2 may broadcast the SRSs, or any other reference signal type, over the air to one or more surrounding or nearby devices.

[0142] At 718, the UE 1 may measure the CLI. The UE 1 may measure the CLI according to the CLI reporting configuration received at 710. For example, if the CLI reporting configuration indicates for the UE 1 to measure the CLI, then the UE 1 may perform the CLI measurements, as described with reference to Figure 6. In some examples, at 720, the UE 1 may compare a CLI value obtained from the CLI measurements to a threshold value and / or may detect an expiry of the timer. The CLI values satisfying (e.g., exceeding, being greater than, being above) the threshold value may trigger transmission of a CLI report. Additionally, or alternatively, a timer expiring may trigger transmission of the CLI report. The UE 1 may reset the timer each time a CLI report is sent, such that the CLI reports are transmitted according to a periodicity. The threshold value and / or the periodicity may be indicated by the RAN node 1 in the CLI reporting configuration 710 and / or in any other signaling.

[0143] At 722, the UE 1 transmits a CLI report to the RAN node 1. The CLI report may include any numerical quantity of CLI values, an average CLI value, a maximum CLI value, etc., as described with reference to Figure 6. Example content of the CLI report may include the measurements as described with reference to Figure 6.

[0144] In some examples, at 724, the RAN node 1 may compare a CLI value obtained from the CLI measurements at the UE 1 (e.g., in the CLI report) to a threshold value and / or may detect an expiry of the timer, as described with reference to Figure 6. The CLI values satisfying (e.g., exceeding, being greater than, being above) the threshold value may trigger transmission of a CLI report to a RAN controller 702.

[0145] For example, at 726, the RAN node 704 transmits a RAN controller CLI indication to the RAN controller 702. The RAN controller CLI indication may include a CLI value, and the RAN node 704 may transmit the RAN controller CLI indication to the RAN controller 702 periodically or upon determining that the CLI value is above a threshold.

[0146] At 728, the RAN controller 702 receives the RAN controller CLI indication and processes one or more CLI measurements indicated by the RAN controller CLI indication. For example, the RAN controller 702 determines, based on the CLI report from the RAN node 1, whether to indicate to the RAN node 2 and / or the UE 2 to take one or more CLI mitigation actions. If affirmative, the RAN controller 702 uses a CONTROL service to send, to the RAN node 2, a CONTROL REQUEST message indicating to the RAN node 2 and / or the UE 2 to take the CLI mitigation actions. For example, at 730, the RAN controller 702 may transmit a control request to the RAN node 2. In response, at 732, the RAN node 2 may determine whether to apply one or more control parameters. That is, the RAN node 2 may selectively update one or more transmission parameters (e.g., control parameters) for wireless communications to manage the CLI. The control parameters may be included in the control request at 730. Applying the control parameters may include accepting the indication in the CONTROL REQUEST message and executing the indicated actions.

[0147] For example, at 734 in example A, if RAN node 2 accepts the request, then the RAN node 2 may apply one or more control parameters or transmission parameters for communications at the RAN node 2 and / or at the UE 104. At 736, the RAN node 2 may transmit, to the RAN controller 702, a CONTROL ACKNOWLEDGE message indicating that the request for the CLI mitigation actions were accepted and applied fully or partially.

[0148] In some other examples, at 738 in example B, the RAN node 2 may send, to the RAN controller 702, a CONTROL FAILURE message indicating that the request for the CLI mitigation actions were not accepted or applied fully or partially. In variations, the RAN controller 702 may send a message to the RAN node 2 to provide an update on the status of the CLI mitigation actions executed through the RAN controller 702 (e.g., through a signaling between the RAN controller 702 and the other RAN node). The information may then be used by the RAN node 2 for radio resource allocation or CLI management purposes.

[0149] In variations, a RAN node 704 and / or a UE 104 may cause interference and experience interference concurrently (e.g., at a same time). Therefore, in some examples, the subscriptionprocedure between the RAN controller 702 and a RAN nodes 704 may indicate to the RAN node 1, the RAN node 2, the UE 1, and / or the UE 2 to both send a CLI report and process control requests to manage CLI. In some examples, the subscription procedure signaling may indicate multiple actions. For example, the subscription procedure signaling may indicate a report type and a control type (e.g., Action = REPORT and Action = CONTROL).

[0150] In some examples, the control request (e.g., including the CONTROL REQUEST message) from the RAN controller 702 to the RAN node 2 may indicate to the RAN node 2 and / or the UE 2 to perform an action for managing CLI. For example, the control request may set or modify one or more transmission parameters that may affect the CLI. In some cases, the RAN controller 702 may indicate to the RAN node 2 that the CLI can be mitigated by reducing an uplink transmission power associated with a UE or a group of UEs served by the RAN node 2. For example, the control request may include an amount of excess CLI, for example X dB. In response, the RAN node 2 may indicate to the UEs (e.g., the UE 2) to reduce the transmission power for uplink signals and / or channels by X dB. The RAN node 2 may respond by transmitting a CONTROL ACKNOWLEDGE message including an indication that the control request was accepted and successfully applied. Additionally, or alternatively, the CONTROL ACKNOWLEDGE message may include an indication of the amount X dB by which the RAN node 2 indicates to the UEs to reduce the transmission power.

[0151] In some other examples, the control request may include an amount of excess CLI, for example X dB. In response, the RAN node 2 may indicate to the UEs to reduce the transmission power on some uplink signals and / or channels by X dB. The RAN node 2 may respond by transmitting a CONTROL ACKNOWLEDGE message including an indication that the control request was accepted and successfully applied on the signals and channels. Additionally, or alternatively, the CONTROL ACKNOWLEDGE message may include an indication of the amount X dB by which the RAN node 2 indicates to the UEs to reduce the transmission power on the signals and channels. The CONTROL ACKNOWLEDGE message may also include an indication of the signals and channels on which the power reduction is applied, such as when a transmission power of a signal or channel may not be reduced (e.g., for an SRS or an uplink control channel, including a PUCCH).

[0152] In some other examples, the control request may include an amount of excess CLI (e.g., X dB). In response, the RAN node 2 may indicate to the UEs (e.g., including the UE 2) to reducethe transmission power on all or some uplink signals and / or channels by Y dB. The value of applied power reduction Y may, or may not, be equal to the value of the requested power reduction X. The RAN node 2 may respond by transmitting a CONTROL ACKNOWLEDGE message including an indication that the control request was accepted and successfully applied on the signals and channels, in addition to an indication of the amount Y dB by which the RAN node 2 and / or the UEs reduces the transmission power.

[0153] In some other examples, the control request message may include an amount of excess CLI (e.g., X dB). In response, the RAN node 2 may indicate to the UEs (e.g., including the UE 2) to reduce the transmission power on all or some uplink signals and / or channels by Y dB, which is not equal to X dB. The RAN node 2 may respond by transmitting a CONTROL FAILURE message including an indication that the control request was not fully applied. Additionally, or alternatively, the CONTROL FAILURE message may include an indication of the amount, Y dB, by which the RAN node 2 indicate to the UEs to reduce the transmission power. In some other examples, the control request may include an amount of excess CLI (e.g., X dB). In response, the RAN node 2 may determine not to indicate to the UEs to reduce the transmission power. The RAN node 2 may respond by transmitting a CONTROL FAILURE message including an indication that the control request was not accepted.

[0154] In some other examples, the control request may include an indication to reduce a transmission power. In response, the RAN node 2 may indicate to the UEs (e.g., including the UE 2) to reduce the transmission power on all or some uplink signals and / or channels by Y dB. The RAN node 2 may respond by transmitting a CONTROL ACKNOWLEDGE message including an indication that the control request was accepted and successfully applied. Additionally, or alternatively, the CONTROL ACKNOWLEDGE message may include an indication of the amount, Y dB, by which the RAN node 2 indicates to the UEs to reduce the transmission power. The RAN node 2 may send multiple messages (e.g., two messages) to convey the information. The messages may include a CONTROL ACKNOWLEDGE message and / or a CONTROL FAILURE message indicating whether the request from the RAN controller 702 was accepted and successfully applied, and an indication (REPORT) message indicating additional information such as X dB, Y dB, and / or the signals or channels on which power reduction is applied.

[0155] In some examples, an amount of power reduction may be indicated through the subscription procedure signaling. In one example, a power reduction of X dB is indicated throughthe subscription procedure signaling (e.g., as a parameter in subscription information). Then, the RAN node 2 may indicate to the UEs to reduce the transmission power by X dB on all or some signals and / or channels upon receiving a control request that requests a transmission power reduction, without an explicit indication of X dB. In some other examples, a sequence of power reduction values [XI, X2, ...] or a sequence of transmission powers [Pl, P2, ...] may be indicated through the subscription procedure signaling (e.g., one or more parameters in subscription information). Then, the RAN node 2 may indicate to the UEs to reduce the transmission power by X[i] dB or indicate to the UEs to reduce the transmission power from P[i] to P[i- 1 ] (or P[i+ 1 ]), on all or some signals and / or channels, where the index i may be decremented or incremented by the RAN node 2 and / or the UEs upon receiving a control request that requests a transmission power reduction.

[0156] In some cases, a minimum and / or maximum transmission power may be preconfigured or otherwise defined, configured by the operator, indicated through the subscription procedure, and / or determined by implementation. If the RAN node 2 is requested to reduce the transmission power to less than the minimum, then the RAN node 2 may decline the request fully or partially and respond by sending a CONTROL FAILURE message. In some other cases, the RAN controller 702 may indicate to the RAN node 2 that the CLI can be mitigated by avoiding communications through one or more beams. The RAN controller 702 may indicate beams that cause excessive CLI in another cell based on CLI reports from other RAN nodes.

[0157] In some examples, the control request may include an indication of one or more beams [Bl, B2, ...] that cause excessive interference. In response, the RAN node 2 may indicate to the UEs to avoid or refrain from communicating using the indicated beams and / or cancel communications scheduled for the indicated beams. The RAN node 2 may respond by transmitting a CONTROL ACKNOWLEDGE message including an indication that the control request was accepted and successfully applied. Additionally, or alternatively, the CONTROL ACKNOWLEDGE message may include an indication of the one or more beams [Bl, B2, ...] that the RAN node 2 indicated to the UEs to refrain from using for communications. In some other examples, the control request may include an indication of one or more beams [Bl, B2, ...] that cause excessive interference. In response, the RAN node 2 may indicate to the UEs to avoid or refrain from communicating using a subset of the indicated beams. The RAN node 2 may respond by transmitting a CONTROL ACKNOWLEDGE message including an indication that the controlrequest was partially accepted and applied. Additionally, or alternatively, the CONTROL ACKNOWLEDGE message may include an indication of the subset of the beams that the RAN node 2 indicated to the UEs to refrain from using for communications. In some other examples, the control request may include an indication of one or more beams [Bl, B2, ...] that cause excessive interference. In response, the RAN node 2 may indicate to the UEs to avoid or refrain from communicating using a subset of the indicated beams. The RAN node 2 may respond by transmitting a CONTROL FAILURE message including an indication that the control request was not fully accepted and applied. Additionally, or alternatively, the CONTROL FAILURE message may include an indication of the subset of the beams that the RAN node 2 indicated to the UEs to refrain from using for communications. In some other examples, the control request may include an indication of one or more beams [Bl, B2, ...] that cause excessive interference. In response, the RAN node 2 may indicate to the UEs to not avoid or refrain from communicating using the indicated beams. The RAN node 2 may respond by transmitting a CONTROL FAILURE message including an indication that the control request was not accepted. In variations, a beam may be indicated by a synchronization signal and / or SSB index, reference signal identifier, reference signal resource indicator, QCL relationship, TCI, direction, or the like.

[0158] In some cases, the RAN controller 702 may indicate to the RAN node 2 that the CLI can be mitigated by avoiding or refraining from communicating with the UEs using one or more communication resources. The RAN controller 702 may indicate communication resources that cause excessive CLI in another cell based on CLI reports from other RAN nodes. For example, the control request may include an indication of one or more resources [Rl, R2, ...] that cause excessive interference. In response, the RAN node 2 may indicate to the UEs to avoid or refrain from communicating using the indicated resources. The RAN node 2 may respond by transmitting a CONTROL ACKNOWLEDGE message including an indication that the control request was accepted and successfully applied. Additionally, or alternatively, the CONTROL ACKNOWLEDGE message may include an indication of the one or more resources [Rl, R2, ...] that the RAN node 2 indicated to the UEs to refrain from using for communications. In some other examples, the control request may include an indication of one or more resources [Rl, R2, ...] that cause excessive interference. In response, the RAN node 2 may indicate to the UEs to avoid or refrain from communicating using a subset of the indicated resources. The RAN node 2 may respond by transmitting a CONTROL ACKNOWLEDGE message including an indication that thecontrol request was partially accepted and applied. Additionally, or alternatively, the CONTROL ACKNOWLEDGE message may include an indication of the subset of the resources that the RAN node 2 indicated to the UEs to refrain from using for the communications.

[0159] In some other examples, the control request may include an indication of one or more resources [Rl, R2, ...] that cause excessive interference. In response, the RAN node 2 may indicate to the UEs to avoid or refrain from communicating on a subset of the indicated resources. The RAN node 2 may respond by transmitting a CONTROL FAILURE message including an indication that the control request was not fully accepted and applied. Additionally, or alternatively, the CONTROL FAILURE message may include an indication of the subset of the resources that the RAN node 2 indicated to the UEs to refrain from using for communications. In some other examples, the control request may include an indication of one or more resources [Rl, R2, ...] that cause excessive interference. In response, the RAN node 2 may indicate to the UEs not to avoid or refrain from communicating using the indicated resources. The RAN node 2 may respond by transmitting a CONTROL FAILURE message including an indication that the control request was not accepted.

[0160] In some cases, the RAN controller 702 may indicate the communication resources to the RAN node 2 and / or the RAN node 2 may indicate the communication resources to the UE 2 as one or more of resources in a time domain (e.g., one or more symbols, slots, subframes, and / or frames), resources in the frequency domain (e.g., one or more subcarriers, PRBs, RBGs, sub-bands, BWPs, CCs, and / or frequency bands), resources in the spatial domain (e.g., one or more beams, beam groups, and / or directions), resources in a code domain, resources (e.g., in a time domain, a frequency domain, a spatial domain, and / or a code domain) associated with one or more signals or channels, resources associated with a stream, a QoS flow, a radio bearer, or the like, and / or resources associated with a network slice. A beam or beam group may be indicated by a relationship with a reference signal (e.g., a reference signal identifier, a synchronization signal and / or SSB index, or a QCL relationship). A signal or channel may be indicated by a configuration identifier, a resource identifier, or the like associated with the signal or channel.

[0161] In variations, the RAN controller 702 may indicate to the RAN node 2 that the CLI can be mitigated by any combination of the examples described herein. Similarly, the RAN node 2 may indicate to the U E2 that the CLI can be mitigated by any combination of the examples described herein. In some cases, the control request may include an indication of a transmission powerreduction on one or more beams. In some other cases, the control request may include an indication of a transmission power reduction on one or more resources in a time domain and / or a frequency domain. In some other cases, the control request may include an indication of one or more beams and / or one or more resources that cause excessive CLI. In some other cases, the control request may include an indication of a transmission power reduction on one or more beams and / or one or more resources. In response to receiving the control request, the RAN node 2 may accept the request fully or partially and respond by a CONTROL ACKNOLWEDGE message or a CONTROL FAILURE message, accordingly. Additionally, or alternatively, the RAN node 2 may send additional information, such as an amount of power reduction, constrained beams, constrained resources, and the like in the CONTROL ACKNOWLEDGE message, the CONTROL failure message, or a separate indication (e.g., REPORT) message.

[0162] In various examples, when a UE 104 or a group of UEs 104 is served by a RAN node 704, the RAN controller 702 and / or other network entities, such as other RAN nodes 704, may reference the UE 104 or the group of UEs 104 by a UE identifier or a UE group identifier. The UE identifier or the UE group identifier may be assigned and / or established through a signaling between the RAN node 704 and the RAN controller 702 or another network entity. Then, the UE identifier or the UE group identifier may be used in other communications to reference an associated UE 104 or group of UEs 104. For example, the UE identifier or the UE group identifier may be used in a signaling among the RAN nodes 704 and / or the RAN controller 702 for associating a configuration such as an SRS, CLI reporting, resource allocation, or the like, to the UE 104 or the group of UEs 104. In variations, a determination of a UE 104 transmitting a reference signal and / or performing a CLI measurement and reporting procedure may be based on the identifier of the UE 104 indicated in a parameter (e.g., a second parameter) in configuration signaling to the UE 104.

[0163] In some examples, a UE identifier may be assigned to a UE 104. The UE identifier may be selected to be unique among each UE 104 served by the RAN nodes in a geographic location, the RAN nodes 704 connected to a common RAN controller 702, or the like. In some examples, a UE group identifier may be assigned to a group of UEs 104. The UEs 104 may be grouped according to a location proximity, a common configuration, a group-common signaling, a use of similar beams or resources, or the like. The grouping of the UEs 104 may be determined by the RAN node 704 serving the UEs 104. In some examples, when the UE 104 performs a handover from a cell by aRAN node 704 to another cell by another RAN node 704, the UE identifier associated with the UE 104 may remain unchanged. In some examples, the UE identifier remains unchanged if the UE moved to another cell in a same area or connected to a same RAN controller 702.

[0164] In some cases, when the RAN node 2 receives the control request indicating an action for the RAN node 2 and / or the UE 2 to perform for CLI mitigation, the RAN node 2 may accept the request, fully or partially, and indicate for the UE 2 to perform the action (e.g., reduce a transmission power, constrain communications on beams and / or resources, and the like). The RAN node 2 may indicate a timing for applying the changes as preconfigured or otherwise defined, configured by the 0AM or the network, indicated through the subscription procedure signaling, determined by an implementation, or any combination thereof. For example, the RAN node 2 may indicate for the UE 2 to apply the changes without a delay after receiving and processing the control request. The RAN node 2 may reserve a duration for processing the control request. In some other examples, the RAN node 2 may indicate for the UE 2 to apply the changes after a duration, T, from a time of receiving or processing the control request. That is, the UE 2 may wait to update a transmission parameter until after a time period (e.g., a delay). The RAN node 2 may indicate for the UE 2 to reduce a transmission power or constrain communications on beams or resources after the duration T, providing for the UE 2 to perform and complete any communications that were scheduled or configured prior to receiving and processing the control request. The RAN node 2 may, or may not, indicate for the UE 2 to apply the changes during the duration T. The duration T may be indicated in units of slots, subframes, frames, ms, seconds, or the like. In some examples, the RAN node 2 may indicate for the UE 2 to apply the changes indefinitely, for example, as long as the associated subscription is valid, as long as the associated subscription is not modified, and / or until another control request indicates to the UE 2 and / or the RAN node 2 to override the applied changes. Additionally, or alternatively, in some examples, the RAN node 2 may indicate for the UE 2 to apply the changes for a duration, P. The duration P may be preconfigured or otherwise defined, configured by the 0AM or the network, indicated through the subscription procedure signaling, determined by an implementation, or any combination thereof.

[0165] In some examples, such as to reduce, or prevent, the underutilization of communication resources, a RAN node 704 may perform an action upon failing to receive control signaling for a duration. For example, a temporary excess CLI may cause a reduction of the transmission power or a constraint for using beams or resources, but a RAN node 704 may not know when to indicate to aUE 104 to revert to an original transmission power or use of beams or resources. A RAN node 1 may send a CLI report to the RAN controller 702, followed by the RAN controller 702 sending control signaling to a RAN node 2 to indicate for the UE 2 to perform a CLI mitigation action. The RAN node 2 may accept the control signaling and indicate to the UE 2 to perform the CLI mitigation action (e.g., reduce a transmission power or limit communications on defined beams or resources). The RAN node 2 may not receive other control signaling associated with the CLI mitigation action. If the excess CLI that triggered the CLI mitigation action is temporary, then the UE 2 maintaining the CLI mitigation action may result in underutilization of radio resources by the UE 2.

[0166] In some cases, the RAN node 2 may indicate for the UE 2 to reverse a transmission power reduction associated with a UE 104, fully or partially, if the RAN node 2 does not receive control signaling for a duration. In some examples, the RAN node 2 may indicate for a UE 104 (e.g., the UE 2) to increase a transmission power by Y dB, where Y dB is an amount of transmission power reduction according to an earlier CLI mitigation action, which may be referred to as a full reversal of power reduction. In some other examples, the RAN node 2 may increase the transmission power of a UE 104 by Z dB, where Z is less than Y and is a fraction of an earlier transmission power reduction, which may be referred to as a partial reversal of power reduction. In some other examples, the RAN node 2 may perform multiple partial reversals of power reduction upon not receiving associated control signaling for a duration or a portion of a duration, such as for additive-increase multiplicative-decrease (AIMD) control methods that aim at combining prompt response to a problem while utilizing a gradual return to normal operation once the problem is addressed.

[0167] In variations, the RAN node 2 may reverse a constraint at a UE 104 (e.g., the UE 2) on using beams or resources, fully or partially, if the RAN node 2 does not receive control signaling for a duration. A full reversal may be realized by using the beams or resources for subsequent communications. A partial reversal may be realized by using a subset or the beams or resources for subsequent communications. The RAN node 2 may perform multiple partial reversals by using a larger subset of the beams or resources that were constrained according to an earlier CLI mitigation action upon not receiving control signaling for a duration or a portion of a duration. The RAN node 2 may configure the UE 2 to use any combination of the methods for performing one or more partial reversals. It should be noted that a constraint on the use of a beam or resource may be interpreted asreducing the transmission power to zero on the beam or resource. Therefore, the RAN node 2 may realize a method of partial reversal by using a constrained beam or resource at a relatively low transmission power (e.g., a transmission power that satisfies a threshold value). Then, if the RAN node 2 does not receive a request to reduce the transmission power for a duration (e.g., control signaling that indicates an excess CLI on the beam or resource), then the RAN node 2 may proceed with further indicating for the UE 2 to increase the transmission power on the beam or resource. The RAN node 2 may repeat the process of gradually increasing the transmission power at the UE 2 until the RAN node 2 receives control signaling that indicates an excess CLI on the beam or resource and / or until the RAN node 2 reverts the transmission power to a transmission power used prior to performing the CLI management action.

[0168] In some examples, a capability of the RAN node 2 and / or the UE 2 to perform a full or partial reversal of a CLI mitigation action may be configured by the network and / or 0AM, indicated in the subscription procedure signaling, or determined by implementation. If the RAN node 2 and / or the UE 2 are capable of performing the full or partial reversal of the CLI mitigation action, then the behavior and various parameters (e.g., the length of the duration or the method of full / partial reversal), may be configured by the network / OAM, indicated in the subscription procedure signaling, or determined by implementation. Alternatively, or additionally, a full and / or partial reversal behavior may be implemented by the RAN controller 702. For example, if the RAN controller 702 does not receive an excess CLI report from the RAN node 1 for a duration, then the RAN controller 702 may perform one or more control signaling procedures with the RAN node 2 to provide for the RAN node 2 to increase a reduced transmission power, use a constrained beam or resource, or both at the UE 2 and / or at the RAN node 2.

[0169] Figure 8 illustrates an example of signaling diagram 800 in accordance with aspects of the present disclosure. In some examples, the signaling diagram 800 may implement aspects of the wireless communications system 100, the wireless communications system 200, the RAN architecture diagram 300, the RAN layer diagram 400, the signaling diagram 500, the signaling diagram 600, and the signaling diagram 700. The signaling diagram 800 may illustrate an example of an inter-UE framework for CLI measurement and reporting between a RAN controllers 802, one or more RAN nodes 804 (e.g., a RAN node 1 and a RAN node 2), and one or more UEs 104 (e.g., a UE 1 and a UE 2). The RAN controller 802, the UE 104, and the RAN node 804 may be examples of corresponding devices (e.g., a RAN node 202, a UE 104, and a CN 106, respectively) asdescribed with reference to Figures 1 through 4. Alternative examples of the following may be implemented, where some processes are performed in a different order than described or are not performed. In some cases, processes may include additional features not mentioned below, or further processes may be added.

[0170] In some examples, although the signaling diagram 800 illustrates two RAN nodes 804 and two UEs 104, the processes may be performed by any numerical quantity of RAN nodes 804 (e.g., one RAN node 804, more than two RAN nodes 804) and any numerical quantity of UEs 104 (e.g., one UE 104, more than two UEs 104). For example, the processes described as being performed by the RAN node 1 may additionally, or alternatively, be performed by the RAN node 2. Similarly, the processes described as being performed by the UE 1 may additionally, or alternatively, be performed by the UE 2.

[0171] At 806, the RAN node 1, the RAN node 2, the UE 1, the UE 2, and / or the RAN controller 802 may perform initial processes. The initial processes may be for a subscription procedure, including exchanging signaling related to the subscription procedure. The subscription procedure may include one or more of a subscription signaling, a subscription modification signaling, and the like. For example, the subscription procedure may be an example of an INSERT, CONTROL service and / or a configuration for CLI reporting and / or SRS transmission, as described with reference to Figure 6.

[0172] The RAN controller 802 may transmit, in one or more messages in the subscription procedure, information for CLI reporting by the RAN node 1 to the RAN controller 702 and / or by the UE 1 to the RAN node 1 through an INSERT service. The subscription procedure messages may include one or more of the following an indication of a reporting and / or insert action (e.g., Action = INSERT) and / or an indication that the value to be reported is a CLI (e.g., KPM = CLI).Additionally, or alternatively, the subscription procedure may indicate an event or condition that triggers CLI reporting. For example, the RAN controller 802 may indicate to the RAN node 1 and / or for the RAN node 1 to indicate to the UE 1 to send a CLI report periodically, upon CLI exceeding a threshold value, or both. The RAN controller 802 may indicate to the RAN node 1, through the subscription procedure signaling, a value for a periodicity, a value for a CLI threshold, or any combination thereof.

[0173] Additionally, or alternatively, at 806, the RAN controller 802 and the RAN node 2 may perform a subscription procedure (e.g., with a type of REPORT, CONTROL, INSERT, etc.). Forexample, the subscription procedure may inform the RAN node 2 of a configuration for CLI reporting and / or SRS transmission, as described with reference to Figure 7.

[0174] At 808, the UE 2 may transmit one or more SRSs over the air to the RAN node 2, the RAN controller 702, the RAN node 1, and / or the UE 1. For example, the UE 2 may broadcast the SRSs, or any other reference signal type, over the air to one or more surrounding or nearby devices.

[0175] At 810, the UE 1 and the RAN node 1 may perform CLI measurement and reporting, as described with reference to Figure 7 (e.g., at 718, 720, 722, and 724). For example, the RAN node 1 may receive a CLI report from the UE 1 , where the CLI report indicates a value of CLI that satisfies (e.g., exceeds, is above, is greater than) a threshold value. In some examples, at 812, the RAN node 1 may start a wait timer and suspend a procedure instance. For example, the RAN node 1 may start a wait timer upon sending an indication message of type INSERT that includes a CLI value measured and reported by the UE 1. In some examples, the timer for suspending a procedure instance (e.g., CLI measurement procedure) may be referred to as a wait timer and / or a time-to-wait timer. The wait timer may be set to the maximum duration that a RAN node 804 is expected to wait after sending an INSERT message to the RAN controller 802. The value of this timer may be indicated in the subscription procedure signaling. In some examples, a value of wait time may be indicated by the subscription procedure signaling with type INSERT. In response, a RAN node 804 may set the wait timer to the indicated value of wait time and start counting down after sending an associated INSERT message.

[0176] In some other examples, multiple values of wait time may be indicated by the subscription procedure signaling with type INSERT, where respective values of wait time are associated with one or more parameters for measuring the CLI (e.g., a CLI measure, a method of measuring the CLI, resources or beams associated with the CLI measurement, a UE or UE group, or the like). In response, the RAN node 804 may set the wait timer to the wait time associated with the one or more parameters after sending an INSERT message that includes a CLI report in association with one or more of the one or more parameters. In some other examples, multiple values of wait time may be obtained by a relationship indicated by the subscription procedure, configured by the network and / or 0AM, specified by the standard, determined by an implementation, or any combination thereof. In response, the RAN node 1 may calculate a value of wait time based on the subscription, configuration, specification, and / or implementation, and then set the wait timer to the calculated wait time after sending an INSERT message that includes an associated CLI value.

[0177] In some examples, one or more subsequent actions may be indicated by the subscription procedure, configured by the network and / or 0AM, preconfigured or otherwise defined, determined by an implementation, or any combination thereof. In response, if the RAN node 1 sends an INSERT message, then the RAN node 1 may determine a subsequent action based on the subscription, configuration, specification, and / or implementation, and then perform the subsequent action upon failing to receive signaling in response to the INSERT message before an associated wait timer expires. At 814, the RAN node 1 may transmit a RAN controller CLI indication of a type, INSERT.

[0178] In some examples, at 816, the RAN controller 802 may receive and process the CLI measurements. For example, the RAN controller 802 may process the reported CLI and determine one or more actions for the RAN node 2, the RAN node 1 , the UE 2, and / or the UE 1 to perform to manage CLI. At 818, the RAN controller 802 may transmit a control request to the RAN node 2. At 820, the RAN node 2 and the UE 2 may perform a control procedure, as described with reference to Figure 7 (e.g., at 730, 732, 734, 736, and / or 738). For example, the RAN node 2 may exchange (e.g., transmit and / or receive) CONTROL procedure signaling with the UE 2. The RAN controller 802 may transmit a control request to the RAN node 2. The RAN node 2 may process the request and determine whether to accept the request. If the RAN node 2 determines to accept the request, then the RAN node 2 attempts to apply the indicated action. If the RAN node 2 accepts the request and successfully applies the indicated action, then the RAN node 2 may respond by sending a CONTROL ACKNOWLEDGE message to the RAN controller 802 indicating that the request was accepted and successful. Otherwise, the RAN node 2 may respond by sending a CONTROL FAILURE message to the RAN controller 802 indicating that the request was not accepted or not successfully applied, as described with reference to Figure 7.

[0179] In variations, a RAN node 804 and / or a UE 104 may cause interference and experience interference concurrently (e.g., at a same time). Therefore, in some examples, the subscription procedure between the RAN controller 702 and a RAN nodes 804 may indicate to the RAN node 1, the RAN node 2, the UE 1, and / or the UE 2 to both send a CLI report and process control requests to manage CLI. In some examples, the subscription procedure signaling may indicate multiple actions. For example, the subscription procedure signaling may indicate a report type and a control type (e.g., Action = INSERT and Action = CONTROL). In some examples, signaling for anINSERT subscription procedure may include signaling similar to signaling of a REPORT subscription procedure and / or a CONTROL subscription procedure.

[0180] At 822, the RAN controller 802 may exchange (e.g., transmit and / or receive) CONTROL procedure signaling with the RAN node 1. For example, if the RAN controller 802 determines an action for the RAN node 2, the RAN node 1, the UE 2, and / or the UE 1, then the RAN controller 802 may send a CONTROL REQUEST message to the RAN node 2 and / or the RAN node 1 including information on an action for the RAN node 2, the RAN node 1, the UE 2, and / or the UE 1 to perform for managing CLI. The action may be to reduce a transmission power at a UE 104 and / or at a RAN node 804, reduce, terminate, or cancel communications on resources in a time domain, a frequency domain, and / or a spatial domain, or the like at a UE 104 and / or at a RAN node 804. For example, at 824 in example A of a control procedure for the RAN node 1 , the RAN controller 802 may transmit a control request to the RAN node 1. The control request may include a CONTROL REQUEST message, as described with reference to Figure 7. In response, at 826, the RAN node 1 may cancel a timer and resume a CLI measurement procedure and / or reception of a CLI measurement from a UE 1. For example, the RAN node 1 may resume a CLI measurement procedure suspended at 812. At 828, the RAN node 1 may transmit an acknowledge message that indicates acceptance of the control request message.

[0181] In some other examples, such as for example B, the subsequent action is ‘resume’ or ‘continue.’ In response, when the wait timer expires, the RAN node 1 may resume a procedure instance that was suspended upon sending the INSERT message. For example, at 830 the RAN node 1 may determine a timer expires and resume a procedure instance (e.g., a CLI measurement and / or UE reporting procedure). A CLI measurement procedure at a UE 1 and / or a RAN node 1 may be the procedure instance suspended at 812. At 832, the RAN node 1 may transmit a CLI management failure indication.

[0182] In example C, the subsequent action is ‘halt’ or ‘terminate.’ In response, when the wait timer expires, the RAN node 1 may halt a procedure instance that was suspended upon sending the INSERT message. For example, at 834 the RAN node 1 may determine a timer expires and suspend or cancel a CLI measurement procedure. The CLI measurement procedure performed by the RAN node 1 and / or the UE 1 may be the CLI measurement procedure suspended at 812. At 836, the RAN node 1 may transmit a CLI management failure indication. In some cases, the subsequent action is ‘suspend.’ In response, when the wait timer expires, the RAN node 1 may continue suspending aprocedure instance that was suspended upon sending the INSERT message. This subsequent action may be similar to setting an infinite wait timer.

[0183] In some examples, the subsequent action is ‘partially resume.’ In response, when the wait timer expires, the RAN node 1 may partially resume a procedure instance that was suspended upon sending the INSERT message (e.g., the RAN node 1 may resume a subset of the procedure instance, resume the procedure instance in association with a subset of resources or parameters or devices, or the like). This subsequent action may be considered a tradeoff between ‘resume’ and ‘halt’ or between ‘resume’ and ‘suspend.’

[0184] In some examples, a configuration may be provided by one or more configurations in practice. An earlier configuration may provide a subset of parameters while a later configuration may provide another subset of parameters. Additionally, or alternatively, a later configuration may override values provided by an earlier configuration or a pre-configuration. A configuration may be provided by Xn and / or NG signaling, RRC signaling, MAC signaling, a physical layer signaling such as a downlink control information (DCI) message, any combination thereof, among other signaling. A configuration may include a pre-configuration or a semi-static configuration defined, configured by a vendor, and / or by a network / operator (e.g., 0AM). Respective parameter values received through configuration or indication may override previous values for a similar parameter.

[0185] Although described in the context of I AB, the proposed solutions may be applicable to wireless relay nodes and other types of wireless communication entities. LI and / or L2 control signaling may refer to control signaling in layer 1 (physical layer) or layer 2 (data link layer). Particularly, an LI and / or L2 control signaling may refer to an LI control signaling such as a DCI message or an uplink control information (UCI) message, an L2 control signaling such as a MAC message, or any combination thereof. A format and an interpretation of an LI and / or L2 control signaling may be determined by the standard, a configuration, other control signaling, or any combination thereof.

[0186] IE may refer to a configuration for L3 signaling, and higher. An IE may be included in a message from one layer to another layer or from one entity to another entity. Additionally, or alternatively, another IE may include an IE. In the present disclosure, the terms ‘IE’ and ‘message’ may be used interchangeably when the message includes the IE directly or indirectly. Any parameter discussed in this disclosure may appear, in practice, as a linear function of that parameter in signaling or specifications.

[0187] In some examples, a measurement may be performed on resources that may not be configured for reference signals, but rather a node may measure a receive signal power and obtain an RSSI, or the like. A beam indication may refer to an indication of a reference signal by an identifier or indicator, a resource associated with a reference signal, a spatial relation information including information of a reference signal or a reciprocal of a reference signal (e.g., in the case of beam correspondence). Any type of reference signal, such as a new type of CLI reference signals (CLI-RS) may be used for CLI measurements. The term ‘signaling’ in the present disclosure may refer to sending and / or receiving one or more messages. The medium for the communications may be wired and / or wireless. In some examples, the interface may be an E2 interface. The terms ‘signaling’ and ‘message’ may be used interchangeably. A RAN node in the present disclosure may refer to one or more of the following: a base station, e.g., a gNB, an eNB, a 6G NodeB; a unit in a base station, such as a CU, CU-CP, CU-UP, DU, RU, O-CU, O-CU-CP, O-CU-UP, O-DU, O-RU; an E2 node or an 01 node. A control entity may be an RIC or a platform thereof, a near-real-time RIC, a non-real-time RIC, an App such as an ‘xApp’ on a near-real-time RIC or an ‘rApp’ on a non- real-time RIC, a network function, a virtualized network function, a RAN function, a virtualized RAN function, or the like.

[0188] Despite frequent reference to specific types of reference signals, such as CSLRS, SRS, SSB, or the like, systems and methods are not limited in scope to the specific reference signals. In various realizations, other types of reference signals may be used, which may include reference signals specified for the purposes pursued in the present disclosure. Throughout the specifications, the terms “parameter” and a “value” for the parameter may be used interchangeably. A parameter may be a sequence and / or array of parameters in various realizations. In some examples, satisfying a condition or threshold is not indicative of a satisfactory condition of the network.

[0189] Figure 9 illustrates an example of a RAN node 900 in accordance with aspects of the present disclosure. The RAN node 900 may include a processor 902, a memory 904, a controller 906, and a transceiver 908. The processor 902, the memory 904, the controller 906, or the transceiver 908, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0190] The processor 902, the memory 904, the controller 906, or the transceiver 908, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0191] The processor 902 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 902 may be configured or operable to operate the memory 904. In some other implementations, the memory 904 may be integrated into the processor 902. The processor 902 may be configured or operable to execute computer-readable instructions stored in the memory 904 to cause the RAN node 900 to perform various functions of the present disclosure.

[0192] The memory 904 may include volatile or non-volatile memory. The memory 904 may store computer-readable, computer-executable code including instructions when executed by the processor 902 cause the RAN node 900 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as the memory 904 or another type of memory. Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0193] In some implementations, the processor 902 and the memory 904 coupled with the processor 902 may be configured or operable to cause the RAN node 900 to perform one or more of the functions described herein (e.g., executing, by the processor 902, instructions stored in the memory 904). For example, the processor 902 may support wireless communication at the RAN node 900 in accordance with examples as disclosed herein. The RAN node 900 may be configured to or operable to support a means for receiving, from a RAN controller, a first message that indicates subscription information including at least one first parameter associated with a configuration of a reference signal for managing a CLI, transmitting, to a UE, a second message that indicates at least one second parameter associated with the configuration of the reference signal, where the at least one second parameter indicates that the UE transmit the reference signal, and receiving, based on a transmission of the reference signal, a third message that indicates at least oneCLI value associated with at least one of the transmission of the reference signal from the UE or the transmission of the reference signal.

[0194] Additionally, the RAN node 900 may be configured to or operable to support any one or combination of transmitting, to the UE, a fourth message that indicates the UE update at least one transmission parameter for wireless communications associated with the CLI based on the third message indicating that the at least one CLI value satisfies a threshold value. Additionally, or alternatively, the update to the at least one transmission parameter for the wireless communications includes one or more of reducing a transmission power associated with the wireless communications, updating one or more time-frequency resources for the wireless communications, or updating a beam for the wireless communications, where the update to the at least one transmission parameter is based on at least one of a transmission power value for the wireless communications, a sequence of transmission power reduction values for the wireless communications, a sequence of transmission powers for the wireless communications, an SSB index, a reference signal identifier, a reference signal resource indicator, a QCL relationship, a TCI, a transmission direction, or one or more communication resources for the wireless communications. Additionally, or alternatively, the fourth message indicates that the UE update the at least one transmission parameter for the wireless communications according to a time period, where the time period includes at least one of a delay prior to updating the at least one transmission parameter for the wireless communications or duration for applying the update to the at least one transmission parameter for the wireless communications.

[0195] Additionally, or alternatively, the RAN node 900 may be configured to or operable to support selectively updating at least one transmission parameter for wireless communications associated with managing the CLI based on the third message indicating that the at least one CLI value satisfies a threshold value. Additionally, or alternatively, the at least one transmission parameter for the wireless communications includes one or more of a transmission power for the wireless communications, a sequence of transmission power reduction values for the wireless communications, a sequence of transmission powers for the wireless communications, an SSB index, a reference signal identifier, a reference signal resource indicator, a QCL relationship, a TCI, a transmission direction, or one or more communication resources for the wireless communications. Additionally, or alternatively, the RAN node 900 may be configured to or operable to supportupdating the at least one transmission parameter for the wireless communications according to a time period, where the time period includes at least one of a delay prior to updating the at least one transmission parameter for the wireless communications or duration for applying the update to the at least one transmission parameter for the wireless communications.

[0196] Additionally, or alternatively, the third message is associated with a parameter that has a value of a control type corresponding to managing the CLI, where the third message is received from at least one of the RAN controller or an additional RAN node. Additionally, or alternatively, the at least one CLI value includes at least one of a RSRP, a RSSI, a SINR, or a RSRQ. Additionally, or alternatively, at least one reference signal associated with the transmission of the reference signal includes an SRS, where the at least one second parameter is obtained based on the at least one first parameter. Additionally, or alternatively, the RAN node includes at least one of a base station, a CU, a DU, an E2 node, or an 01 node, where the RAN controller includes at least one of an RIC, a near-real-time RIC, or a non-real-time RIC.

[0197] In some implementations, the processor 902 and the memory 904 coupled with the processor 902 may be configured to or operable to cause the RAN node 900 to perform one or more of the functions described herein (e.g., executing, by the processor 902, instructions stored in the memory 904). For example, the processor 902 may support wireless communication at the RAN node 900 in accordance with examples as disclosed herein. The RAN node 900 may be configured to or operable to support a means for receiving, from a RAN controller, a first message that indicates subscription information including at least one first parameter associated with a configuration of a reference signal for managing a CLI, transmitting, to a UE, a second message that indicates at least one second parameter associated with the configuration of the reference signal, where the at least one second parameter indicates that the UE perform at least one CLI measurement to obtain at least one CLI value, and receiving, based on the at least one CLI measurement, a third message that indicates the at least one CLI value.

[0198] Additionally, the RAN node 900 may be configured to or operable to support any one or combination of determining that the at least one CLI value satisfies a threshold value, and transmitting, to at least one of the RAN controller or an additional RAN node, a fourth message that indicates that the at least one CLI value satisfies the threshold value. Additionally, or alternatively, the fourth message is associated with a parameter with a value of at least one of a report typecorresponding to managing the CLI or an insert type corresponding to managing the CLI. Additionally, or alternatively, the RAN node 900 may be configured to or operable to support activating, based on transmitting the fourth message, one or more timers associated with suspending a CLI measurement procedure associated with the UE, and suspending the CLI measurement procedure associated with the UE until expiry of the one or more timers. Additionally, or alternatively, the RAN node 900 may be configured to or operable to support receiving a fifth message that indicates the one or more timers, where a value of the one or more timers corresponds to respective parameters associated with the CLI measurement procedure associated with the UE. Additionally, or alternatively, the RAN node 900 may be configured to or operable to support at least partially resuming the CLI measurement procedure associated with the UE upon expiry of the one or more timers. Additionally, or alternatively, the RAN node 900 may be configured to or operable to support terminating the CLI measurement procedure associated with the UE upon expiry of the one or more timers. Additionally, or alternatively, the one or more timers include one or more time-to-wait timers.

[0199] Additionally, or alternatively, the at least one CLI value is associated with at least one reference signal transmission corresponding to a first network entity different from a second network entity that serves the UE. Additionally, or alternatively, the at least one second parameter indicates a periodicity for performing the at least one CLI measurement. Additionally, or alternatively, the at least one second parameter indicates a threshold value associated with the at least one CLI value, where the third message is received based on the at least one CLI value satisfying the threshold value. Additionally, or alternatively, the at least one CLI value includes at least one of a RSRP, a RSSI, a SINR, or a RSRQ. Additionally, or alternatively, the at least one CLI measurement is associated with at least one SRS. Additionally, or alternatively, the RAN node includes at least one of a base station, a CU, a DU, an E2 node, or an 01 node, where the RAN controller includes at least one of an RIC, a near-real-time RIC, or a non-real-time RIC.

[0200] Additionally, or alternatively, the RAN node 900 may support at least one memory (e.g., the memory 904) and at least one processor (e.g., the processor 902) coupled with the at least one memory and configured to or operable to cause the RAN node 900 to: receive, from a RAN controller, a first message that indicates subscription information including at least one first parameter associated with a configuration of a reference signal for managing a CLI; transmit, to aUE, a second message that indicates at least one second parameter associated with the configuration of the reference signal, where the at least one second parameter indicates that the UE transmit the reference signal; and receive, based on a transmission of the reference signal, a third message that indicates at least one CLI value associated with at least one of the transmission of the reference signal from the UE or the transmission of the reference signal.

[0201] Additionally, the RAN node 900 may be configured to or operable to support any one or combination of the at least one processor is configured to or operable to transmit, to the UE, a fourth message that indicates the UE update at least one transmission parameter for wireless communications associated with the CLI based on the third message indicating that the at least one CLI value satisfies a threshold value. Additionally, or alternatively, the update to the at least one transmission parameter for the wireless communications includes one or more of reducing a transmission power associated with the wireless communications, updating one or more timefrequency resources for the wireless communications, or updating a beam for the wireless communications, and where the update to the at least one transmission parameter is based on at least one of a transmission power value for the wireless communications, a sequence of transmission power reduction values for the wireless communications, a sequence of transmission powers for the wireless communications, an SSB index, a reference signal identifier, a reference signal resource indicator, a QCL relationship, a TCI, a transmission direction, or one or more communication resources for the wireless communications. Additionally, or alternatively, the fourth message indicates that the UE update the at least one transmission parameter for the wireless communications according to a time period, where the time period includes at least one of a delay prior to updating the at least one transmission parameter for the wireless communications or duration for applying the update to the at least one transmission parameter for the wireless communications. Additionally, or alternatively, the at least one processor is configured to or operable to selectively update at least one transmission parameter for wireless communications associated with managing the CLI based on the third message indicating that the at least one CLI value satisfies a threshold value. Additionally, or alternatively, the at least one transmission parameter for the wireless communications includes one or more of a transmission power for the wireless communications, a sequence of transmission power reduction values for the wireless communications, a sequence of transmission powers for the wireless communications, an SSBindex, a reference signal identifier, a reference signal resource indicator, a QCL relationship, a TCI, a transmission direction, or one or more communication resources for the wireless communications.

[0202] Additionally, or alternatively, the at least one processor is configured to or operable to update the at least one transmission parameter for the wireless communications according to a time period, where the time period includes at least one of a delay prior to updating the at least one transmission parameter for the wireless communications or duration for applying the update to the at least one transmission parameter for the wireless communications. Additionally, or alternatively, the third message is associated with a parameter that has a value of a control type corresponding to managing the CLI, and where the third message is received from at least one of the RAN controller or an additional RAN node. Additionally, or alternatively, the at least one CLI value includes at least one of an RSRP, an RSSI, an SINR, or an RSRQ. Additionally, or alternatively, at least one reference signal associated with the transmission of the reference signal includes an SRS, where the at least one second parameter is obtained based on the at least one first parameter. Additionally, or alternatively, the RAN node includes at least one of a base station, a CU, a DU, an E2 node, or an 01 node, and where the RAN controller includes at least one of an RIC, a near-real-time RIC, or a non-real-time RIC.

[0203] Additionally, or alternatively, the RAN node 900 may support at least one memory (e.g., the memory 904) and at least one processor (e.g., the processor 902) coupled with the at least one memory and configured to or operable to cause the RAN node 900 to: receive, from a RAN controller, a first message that indicates subscription information including at least one first parameter associated with a configuration of a reference signal for managing a CLI, transmit, to a UE, a second message that indicates at least one second parameter associated with the configuration of the reference signal, where the at least one second parameter indicates that the UE perform at least one CLI measurement to obtain at least one CLI value, and receive, based on the at least one CLI measurement, a third message that indicates the at least one CLI value.

[0204] Additionally, the RAN node 900 may be configured to or operable to support any one or combination of the at least one processor is configured to or operable to determine that the at least one CLI value satisfies a threshold value, and transmit, to at least one of the RAN controller or an additional RAN node, a fourth message that indicates that the at least one CLI value satisfies the threshold value. Additionally, or alternatively, the fourth message is associated with a parameterwith a value of at least one of a report type corresponding to managing the CLI or an insert type corresponding to managing the CLI. Additionally, or alternatively, the at least one processor is configured to or operable to activate, based on transmitting the fourth message, one or more timers associated with suspending a CLI measurement procedure associated with the UE, and suspend the CLI measurement procedure associated with the UE until expiry of the one or more timers. Additionally, or alternatively, the at least one processor is configured to or operable to receive a fifth message that indicates the one or more timers, where a value of the one or more timers corresponds to respective parameters associated with the CLI measurement procedure associated with the UE. Additionally, or alternatively, the at least one processor is configured to or operable to at least partially resume the CLI measurement procedure associated with the UE upon expiry of the one or more timers.

[0205] Additionally, or alternatively, the at least one processor is configured to or operable to terminate the CLI measurement procedure associated with the UE upon expiry of the one or more timers. Additionally, or alternatively, the one or more timers include one or more time-to-wait timers. Additionally, or alternatively, the at least one CLI value is associated with at least one reference signal transmission corresponding to a first network entity different from a second network entity that serves the UE. Additionally, or alternatively, the at least one second parameter indicates a periodicity for performing the at least one CLI measurement. Additionally, or alternatively, the at least one second parameter indicates a threshold value associated with the at least one CLI value, where the third message is received based on the at least one CLI value satisfying the threshold value. Additionally, or alternatively, the at least one CLI value includes at least one of an RSRP, an RSSI, an SINR, or an RSRQ. Additionally, or alternatively, the at least one CLI measurement is associated with at least one SRS. Additionally, or alternatively, the RAN node includes at least one of a base station, a CU, a DU, an E2 node, or an 01 node, where the RAN controller includes at least one of a RIC, a near-real-time RIC, or a non-real-time RIC.

[0206] The controller 906 may manage input and output signals for the RAN node 900. The controller 906 may also manage peripherals not integrated into the RAN node 900. In some implementations, the controller 906 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 906 may be implemented as part of the processor 902.

[0207] In some implementations, the RAN node 900 may include at least one transceiver 908. In some other implementations, the RAN node 900 may have more than one transceiver 908. The transceiver 908 may represent a wireless transceiver. The transceiver 908 may include one or more receiver chains 910, one or more transmitter chains 912, or any combination thereof.

[0208] A receiver chain 910 may be configured to or operable to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 910 may include one or more antennas to receive a signal over the air or wireless medium. The receiver chain 910 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to or operable to amplify the received signal. The receiver chain 910 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 910 may include at least one decoder for decoding the demodulated signal to receive the transmitted data.

[0209] A transmitter chain 912 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 912 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 912 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 912 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0210] Figure 10 illustrates an example of a processor 1000 in accordance with aspects of the present disclosure. The processor 1000 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 1000 may include a controller 1002 configured to perform various operations in accordance with examples as described herein. The processor 1000 may optionally include at least one memory 1004, which may be, for example, an L1 / L2 / L3 cache. Additionally, or alternatively, the processor 1000 may optionally include one or more arithmetic-logic units (ALUs) 1006. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0211] The processor 1000 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 1000) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM), and others).

[0212] The controller 1002 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 1000 to cause the processor 1000 to support various operations in accordance with examples as described herein. For example, the controller 1002 may operate as a control unit of the processor 1000, generating control signals that manage the operation of various components of the processor 1000. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.

[0213] The controller 1002 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 1004 and determine subsequent instruction(s) to be executed to cause the processor 1000 to support various operations in accordance with examples as described herein. The controller 1002 may be configured to track memory addresses of instructions associated with the memory 1004. The controller 1002 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 1002 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 1000 to cause the processor 1000 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 1002 may be configured to manage flow of data within the processor 1000. The controller 1002 may be configured to control transfer of data between registers, ALUs 1006, and other functional units of the processor 1000.

[0214] The memory 1004 may include one or more caches (e.g., memory local to or included in the processor 1000 or other memory, such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM,flash memory, etc. In some implementations, the memory 1004 may reside within or on a processor chipset (e.g., local to the processor 1000). In some other implementations, the memory 1004 may reside external to the processor chipset (e.g., remote to the processor 1000).

[0215] The memory 1004 may store computer-readable, computer-executable code including instructions that, when executed by the processor 1000, cause the processor 1000 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. The controller 1002 and / or the processor 1000 may be configured to execute computer-readable instructions stored in the memory 1004 to cause the processor 1000 to perform various functions. For example, the processor 1000 and / or the controller 1002 may be coupled with or to the memory 1004, the processor 1000, and the controller 1002, and may be configured to perform various functions described herein. In some examples, the processor 1000 may include multiple processors and the memory 1004 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.

[0216] The one or more ALUs 1006 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 1006 may reside within or on a processor chipset (e.g., the processor 1000). In some other implementations, the one or more ALUs 1006 may reside external to the processor chipset (e.g., the processor 1000). One or more ALUs 1006 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 1006 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 1006 may be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 1006 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not-AND (NAND), enabling the one or more ALUs 1006 to handle conditional operations, comparisons, and bitwise operations.

[0217] The processor 1000 may support wireless communication in accordance with examples as disclosed herein. The processor 1000 may be configured to or operable to support at least one controller (e.g., the controller 1002) coupled with at least one memory (e.g., the memory 1004) and configured to cause the processor to: receive, from a RAN controller, a first message that indicatessubscription information including at least one first parameter associated with a configuration of a reference signal for managing a CLI, transmit, to a UE, a second message that indicates at least one second parameter associated with the configuration of the reference signal, where the at least one second parameter indicates that the UE transmit the reference signal, and receive, based on a transmission of the reference signal, a third message that indicates at least one CLI value associated with at least one of the transmission of the reference signal from the UE or the transmission of the reference signal.

[0218] Additionally, the processor 1000 may be configured to or operable to support any one or combination of the at least one controller is configured to transmit, to the UE, a fourth message that indicates the UE update at least one transmission parameter for wireless communications associated with the CLI based on the third message indicating that the at least one CLI value satisfies a threshold value. Additionally, or alternatively, the update to the at least one transmission parameter for the wireless communications includes one or more of reducing a transmission power associated with the wireless communications, updating one or more time-frequency resources for the wireless communications, or updating a beam for the wireless communications, where the update to the at least one transmission parameter is based on at least one of a transmission power value for the wireless communications, a sequence of transmission power reduction values for the wireless communications, a sequence of transmission powers for the wireless communications, an SSB index, a reference signal identifier, a reference signal resource indicator, a QCL relationship, a TCI, a transmission direction, or one or more communication resources for the wireless communications. Additionally, or alternatively, the fourth message indicates that the UE update the at least one transmission parameter for the wireless communications according to a time period, where the time period includes at least one of a delay prior to updating the at least one transmission parameter for the wireless communications or duration for applying the update to the at least one transmission parameter for the wireless communications. Additionally, or alternatively, the at least one controller is configured to selectively update at least one transmission parameter for wireless communications associated with managing the CLI based on the third message indicating that the at least one CLI value satisfies a threshold value. Additionally, or alternatively, the at least one transmission parameter for the wireless communications includes one or more of a transmission power for the wireless communications, a sequence of transmission power reduction values for the wirelesscommunications, a sequence of transmission powers for the wireless communications, an SSB index, a reference signal identifier, a reference signal resource indicator, a QCL relationship, a TCI, a transmission direction, or one or more communication resources for the wireless communications.

[0219] Additionally, or alternatively, the at least one controller is configured to update the at least one transmission parameter for the wireless communications according to a time period, where the time period includes at least one of a delay prior to updating the at least one transmission parameter for the wireless communications or duration for applying the update to the at least one transmission parameter for the wireless communications. Additionally, or alternatively, the third message is associated with a parameter that has a value of a control type corresponding to managing the CLI, where the third message is received from at least one of the RAN controller or an additional processor. Additionally, or alternatively, the at least one CLI value includes at least one of a RSRP, a RSSI, a SINR, or a RSRQ. Additionally, or alternatively, at least one reference signal associated with the transmission of the reference signal includes an SRS, where the at least one second parameter is obtained based on the at least one first parameter. Additionally, or alternatively, the processor includes at least one of a base station, a CU, a DU, an E2 node, or an 01 node, where the RAN controller includes at least one of a RIC, a near-real-time RIC, or a non-real-time RIC.

[0220] The processor 1000 may support wireless communication in accordance with examples as disclosed herein. The processor 1000 may be configured to or operable to support at least one controller (e.g., the controller 1002) coupled with at least one memory (e.g., the memory 1004) and configured to cause the processor to: receive, from a RAN controller, a first message that indicates subscription information including at least one first parameter associated with a configuration of a reference signal for managing a CLI, transmit, to a UE, a second message that indicates at least one second parameter associated with the configuration of the reference signal, where the at least one second parameter indicates that the UE perform at least one CLI measurement to obtain at least one CLI value, and receive, based on the at least one CLI measurement, a third message that indicates the at least one CLI value.

[0221] Additionally, the processor 1000 may be configured to or operable to support any one or combination of the at least one controller is configured to determine that the at least one CLI value satisfies a threshold value, and transmit, to at least one of the RAN controller or an additional processor, a fourth message that indicates that the at least one CLI value satisfies the thresholdvalue. Additionally, or alternatively, the fourth message is associated with a parameter with a value of at least one of a report type corresponding to managing the CLI or an insert type corresponding to managing the CLI. Additionally, or alternatively, the at least one controller is configured to activate, based on transmitting the fourth message, one or more timers associated with suspending a CLI measurement procedure associated with the UE, and suspend the CLI measurement procedure associated with the UE until expiry of the one or more timers. Additionally, or alternatively, the at least one controller is configured to receive a fifth message that indicates the one or more timers, where a value of the one or more timers corresponds to respective parameters associated with the CLI measurement procedure associated with the UE. Additionally, or alternatively, the at least one controller is configured to at least partially resume the CLI measurement procedure associated with the UE upon expiry of the one or more timers. Additionally, or alternatively, the at least one controller is configured to terminate the CLI measurement procedure associated with the UE upon expiry of the one or more timers. Additionally, or alternatively, the one or more timers include one or more time-to-wait timers.

[0222] Additionally, or alternatively, the at least one CLI value is associated with at least one reference signal transmission corresponding to a first network entity different from a second network entity that serves the UE. Additionally, or alternatively, the at least one second parameter indicates a periodicity for performing the at least one CLI measurement. Additionally, or alternatively, the at least one second parameter indicates a threshold value associated with the at least one CLI value, where the third message is received based on the at least one CLI value satisfying the threshold value. Additionally, or alternatively, the at least one CLI value includes at least one of a RSRP, a RSSI, a SINR, or a RSRQ. Additionally, or alternatively, the at least one CLI measurement is associated with at least one SRS. Additionally, or alternatively, the processor includes at least one of a base station, a CU, a DU, an E2 node, or an 01 node, where the RAN controller includes at least one of an RIC, a near-real-time RIC, or a non-real-time RIC.

[0223] Figure 11 illustrates an example of a RAN controller 1100 in accordance with aspects of the present disclosure. The RAN controller 1100 may include a processor 1102, a memory 1104, a controller 1106, and a transceiver 1108. The processor 1102, the memory 1104, the controller 1106, or the transceiver 1108, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein.These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0224] The processor 1102, the memory 1104, the controller 1106, or the transceiver 1108, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0225] The processor 1102 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 1102 may be configured to operate the memory 1104. In some other implementations, the memory 1104 may be integrated into the processor 1102. The processor 1102 may be configured to execute computer-readable instructions stored in the memory 1104 to cause the RAN controller 1100 to perform various functions of the present disclosure.

[0226] The memory 1104 may include volatile or non-volatile memory. The memory 1104 may store computer-readable, computer-executable code including instructions when executed by the processor 1102 cause the RAN controller 1100 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as the memory 1104 or another type of memory. Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0227] In some implementations, the processor 1102 and the memory 1104 coupled with the processor 1102 may be configured to cause the RAN controller 1100 to perform one or more of the functions described herein (e.g., executing, by the processor 1102, instructions stored in the memory 1104). For example, the processor 1102 may support wireless communication at the RAN controller 1100 in accordance with examples as disclosed herein. The RAN controller 1100 may be configured to or operable to support a means for transmitting, to at least one RAN node, a first message that indicates subscription information including at least one parameter associated with a configuration of a reference signal for managing a CLI, where the at least one parameter indicates at least one of that a UE transmit the reference signal or that the UE perform at least one CLImeasurement to obtain at least one CLI value, and receiving, based on the configuration of the reference signal, a second message that indicates the at least one CLI value associated with the UE.

[0228] Additionally, the RAN controller 1100 may be configured to or operable to support any one or combination of the at least one parameter indicates that the UE transmit the reference signal, where the at least one CLI value is associated with at least one of the UE or a transmission of the reference signal. Additionally, or alternatively, the RAN controller 1100 may be configured to or operable to support transmitting, to the at least one RAN node, a third message that indicates that at least one of the at least one RAN node or the UE update at least one transmission parameter for wireless communications associated with managing the CLI based on the at least one CLI value satisfying a threshold value. Additionally, or alternatively, the update to the at least one transmission parameter for the wireless communications includes one or more of reducing a transmission power associated with the wireless communications, updating one or more timefrequency resources for the wireless communications, or updating a beam for the wireless communications, where the update to the at least one transmission parameter is based on at least one of a transmission power value for the wireless communications, a sequence of transmission power reduction values for the wireless communications, a sequence of transmission powers for the wireless communications, an SSB index, a reference signal identifier, a reference signal resource indicator, a QCL relationship, a TCI, a transmission direction, or one or more communication resources for the wireless communications.

[0229] Additionally, or alternatively, the RAN controller 1100 may be configured to or operable to support receiving, from the at least one RAN node, a fourth message that indicates feedback corresponding to the update to the at least one transmission parameter for wireless communications associated with managing the CLI. Additionally, or alternatively, the third message is associated with a parameter that has a value of a control type corresponding to managing the CLI.Additionally, or alternatively, the at least one parameter indicates that the UE perform the at least one CLI measurement to obtain the at least one CLI value, where the at least one CLI value is associated with a first network entity different from a second network entity that serves the UE. Additionally, or alternatively, the RAN controller 1100 may be configured to or operable to support receiving, from the at least one RAN node, a third message that indicates that the at least one CLI value satisfies a threshold value. Additionally, or alternatively, the third message is associated with a parameter with a value of at least one of a report type corresponding to managing the CLI or aninsert type corresponding to managing the CLI. Additionally, or alternatively, the RAN controller 1100 may be configured to or operable to support transmitting a fourth message that indicates one or more timers associated with suspending a CLI measurement procedure associated with the UE, where a value of the one or more timers corresponds to respective parameters associated with the CLI measurement procedure associated with the UE. Additionally, or alternatively, the one or more timers include one or more time-to-wait timers. Additionally, or alternatively, the at least one parameter indicates a periodicity for performing the at least one CLI measurement. Additionally, or alternatively, the at least one parameter indicates a threshold value associated with the at least one CLI value.

[0230] Additionally, or alternatively, the RAN controller 1100 may be configured to or operable to support receiving, from the at least one RAN node, a third message that indicates at least one additional parameter associated with at least one of a capability of the at least one RAN node to perform a CLI management procedure, a configuration of a communication scheme associated with at least one of TDD information or SBED information, or configuration information associated with the UE, and determining the at least one parameter of the first message based on the at least one additional parameter. Additionally, or alternatively, the at least one CLI value includes at least one of an RSRP, an RSSI, an SINR, or an RSRQ. Additionally, or alternatively, the reference signal includes an SRS, where the at least one second parameter is obtained based on the at least one first parameter. Additionally, or alternatively, the at least one RAN node includes at least one of a base station, a CU, a DU, an E2 node, or an 01 node, where the RAN controller includes at least one of an RIC, a near-real-time RIC, or a non-real-time RIC.

[0231] Additionally, or alternatively, the RAN controller 1100 may support at least one memory (e.g., the memory 1104) and at least one processor (e.g., the processor 1102) coupled with the at least one memory and configured to or operable to cause the RAN controller 1100 to transmit, to at least one RAN node, a first message that indicates subscription information including at least one parameter associated with a configuration of a reference signal for managing a CLI, where the at least one parameter indicates at least one of that a UE transmit the reference signal or that the UE perform at least one CLI measurement to obtain at least one CLI value, and receive, based on the configuration of the reference signal, a second message that indicates the at least one CLI value associated with the UE.

[0232] Additionally, the RAN controller 1100 may be configured to or operable to support any one or combination of the at least one parameter indicates that the UE transmit the reference signal, where the at least one CLI value is associated with at least one of the UE or a transmission of the reference signal. Additionally, or alternatively, the RAN controller transmits, to the at least one RAN node, a third message that indicates that at least one of the at least one RAN node or the UE update at least one transmission parameter for wireless communications associated with managing the CLI based on the at least one CLI value satisfying a threshold value. Additionally, or alternatively, the update to the at least one transmission parameter for the wireless communications includes one or more of reducing a transmission power associated with the wireless communications, updating one or more time-frequency resources for the wireless communications, or updating a beam for the wireless communications, where the update to the at least one transmission parameter is based on at least one of a transmission power value for the wireless communications, a sequence of transmission power reduction values for the wireless communications, a sequence of transmission powers for the wireless communications, an SSB index, a reference signal identifier, a reference signal resource indicator, a QCL relationship, a TCI, a transmission direction, or one or more communication resources for the wireless communications.

[0233] Additionally, or alternatively, the RAN controller receives, from the at least one RAN node, a fourth message that indicates feedback corresponding to the update to the at least one transmission parameter for wireless communications associated with managing the CLI.Additionally, or alternatively, the third message is associated with a parameter that has a value of a control type corresponding to managing the CLI. Additionally, or alternatively, the at least one parameter indicates that the UE perform the at least one CLI measurement to obtain the at least one CLI value, where the at least one CLI value is associated with a first network entity different from a second network entity that serves the UE. Additionally, or alternatively, the RAN controller receives, from the at least one RAN node, a third message that indicates that the at least one CLI value satisfies a threshold value. Additionally, or alternatively, the third message is associated with a parameter with a value of at least one of a report type corresponding to managing the CLI or an insert type corresponding to managing the CLI.

[0234] Additionally, or alternatively, the RAN controller transmits a fourth message that indicates one or more timers associated with suspending a CLI measurement procedure associated with the UE, where a value of the one or more timers corresponds to respective parametersassociated with the CLI measurement procedure associated with the UE. Additionally, or alternatively, the one or more timers include one or more time-to-wait timers. Additionally, or alternatively, the at least one parameter indicates a periodicity for performing the at least one CLI measurement. Additionally, or alternatively, the at least one parameter indicates a threshold value associated with the at least one CLI value. Additionally, or alternatively, the RAN controller receive, from the at least one RAN node, a third message that indicates at least one additional parameter associated with at least one of a capability of the at least one RAN node to perform a CLI management procedure, a configuration of a communication scheme associated with at least one of TDD information or SBED information, or configuration information associated with the UE, and determine the at least one parameter of the first message based on the at least one additional parameter. Additionally, or alternatively, the at least one CLI value includes at least one of an RSRP, an RS SI, an SINR, or a RSRQ. Additionally, or alternatively, the reference signal includes an SRS, where the at least one second parameter is obtained based on the at least one first parameter. Additionally, or alternatively, the at least one RAN node includes at least one of a base station, a CU, a DU, an E2 node, or an 01 node, where the RAN controller includes at least one of a RIC, a near-real-time RIC, or a non-real-time RIC.

[0235] The controller 1106 may manage input and output signals for the RAN controller 1100. The controller 1106 may also manage peripherals not integrated into the RAN controller 1100. In some implementations, the controller 1106 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 1106 may be implemented as part of the processor 1102.

[0236] In some implementations, the RAN controller 1100 may include at least one transceiver 1108. In some other implementations, the RAN controller 1100 may have more than one transceiver 1108. The transceiver 1108 may represent a wireless transceiver. The transceiver 1108 may include one or more receiver chains 1110, one or more transmitter chains 1112, or any combination thereof.

[0237] A receiver chain 1110 may be configured to or operable to receive signals (e.g., control information, data, packets) over a wireless medium. Lor example, the receiver chain 1110 may include one or more antennas to receive a signal over the air or wireless medium. The receiver chain 1110 may include at least one amplifier (e.g., an LNA) configured to or operable to amplify the received signal. The receiver chain 1110 may include at least one demodulator configured to or operable to demodulate the receive signal and obtain the transmitted data by reversing themodulation technique applied during transmission of the signal. The receiver chain 1110 may include at least one decoder for decoding the demodulated signal to receive the transmitted data.

[0238] A transmitter chain 1112 may be configured to or operable to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 1112 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to or operable to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 1112 may also include at least one power amplifier configured to or operable to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 1112 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0239] Figure 12 illustrates a flowchart of a method 1200 in accordance with aspects of the present disclosure. The operations of the method may be implemented by a RAN node as described herein. In some implementations, the RAN node may execute a set of instructions to control the function elements of the RAN node to perform the described functions. It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0240] At 1202, the method may include receiving, from a RAN controller, a first message that indicates subscription information including at least one first parameter associated with a configuration of a reference signal for managing a CLI. The operations of 1202 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1202 may be performed by a RAN node as described with reference to Figure 9.

[0241] At 1204, the method may include transmitting, to a UE, a second message that indicates at least one second parameter associated with the configuration of the reference signal, where the at least one second parameter is based on the at least one first parameter and indicates that the UE transmit the reference signal. The operations of 1204 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1204 may be performed by a RAN node as described with reference to Figure 9.

[0242] At 1206, the method may include receive, based on a transmission of the reference signal, a third message that indicates at least one CLI value associated with at least one of thetransmission of the reference signal from the UE or the transmission of the reference signal. The operations of 1206 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1206 may be performed a RAN node as described with reference to Figure 9.

[0243] Figure 13 illustrates a flowchart of a method 1300 in accordance with aspects of the present disclosure. The operations of the method may be implemented by a RAN node as described herein. In some implementations, the RAN node may execute a set of instructions to control the function elements of the RAN node to perform the described functions. It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0244] At 1302, the method may include receiving, from a RAN controller, a first message that indicates subscription information including at least one first parameter associated with a configuration of a reference signal for managing a CLI. The operations of 1302 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1302 may be performed by a RAN node as described with reference to Figure 9.

[0245] At 1304, the method may include transmitting, to a UE, a second message that indicates at least one second parameter associated with the configuration of the reference signal, where the at least one second parameter is based on the at least one first parameter and indicates that the UE perform at least one CLI measurement to obtain at least one CLI value. The operations of 1304 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1304 may be performed by a RAN node as described with reference to Figure 9.

[0246] At 1306, the method may include receiving, based on the at least one CLI measurement, a third message that indicates the at least one CLI value. The operations of 1306 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1306 may be performed a RAN node as described with reference to Figure 9.

[0247] Figure 14 illustrates a flowchart of a method 1400 in accordance with aspects of the present disclosure. The operations of the method may be implemented by a RAN controller as described herein. In some implementations, the RAN controller may execute a set of instructions to control the function elements of the RAN controller to perform the described functions. It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0248] At 1402, the method may include transmitting, to at least one RAN node, a first message that indicates subscription information including at least one parameter associated with a configuration of a reference signal for managing a CLI, where the at least one parameter indicates at least one of that a UE transmit the reference signal or that the UE perform at least one CLI measurement to obtain at least one CLI value. The operations of 1402 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1402 may be performed by a RAN controller as described with reference to Figure 11.

[0249] At 1404, the method may include receiving, based on the configuration of the reference signal, a second message that indicates the at least one CLI value associated with the UE. The operations of 1404 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1404 may be performed by a RAN controller as described with reference to Figure 11.

[0250] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

CLAIMSWhat is claimed is:

1. A radio access network (RAN) node for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and operable to cause the RAN node to: receive, from a RAN controller, a first message that indicates subscription information comprising at least one first parameter associated with a configuration of a reference signal for managing a cross-link interference (CLI); transmit, to a user equipment (UE), a second message that indicates at least one second parameter associated with the configuration of the reference signal, wherein the at least one second parameter indicates that the UE transmits the reference signal; and receive, based at least in part on a transmission of the reference signal, a third message that indicates at least one CLI value associated with the transmission of the reference signal from the UE.

2. The RAN node of claim 1, wherein the at least one processor is further operable to cause the RAN node to transmit, to the UE, a fourth message that indicates the UE update at least one transmission parameter for wireless communications associated with the CLI based at least in part on the third message indicating that the at least one CLI value satisfies a threshold value, wherein the fourth message indicates that the UE update the at least one transmission parameter for the wireless communications according to a time period, and wherein the time period comprises at least one of a delay prior to updating the at least one transmission parameter for the wireless communications or duration for applying the update to the at least one transmission parameter for the wireless communications.

3. The RAN node of claim 2, wherein the update to the at least one transmission parameter for the wireless communications comprises one or more of reducing a transmission power associated with the wireless communications, updating one or more time-frequency resources for the wireless communications, or updating a beam for the wireless communications, and wherein the update to the at least one transmission parameter is based at least in part on at leastone of a transmission power value for the wireless communications, a sequence of transmission power reduction values for the wireless communications, a sequence of transmission powers for the wireless communications, a synchronization signal block index, a reference signal identifier, a reference signal resource indicator, a quasi-co-located relationship, a transmission configuration indicator, a transmission direction, or one or more communication resources for the wireless communications.

4. The RAN node of claim 1 , wherein the at least one processor is further operable to cause the RAN node to selectively update at least one transmission parameter for wireless communications associated with managing the CLI based at least in part on the third message indicating that the at least one CLI value satisfies a threshold value, wherein the at least one transmission parameter for the wireless communications comprises one or more of a transmission power for the wireless communications, a sequence of transmission power reduction values for the wireless communications, a sequence of transmission powers for the wireless communications, a synchronization signal block index, a reference signal identifier, a reference signal resource indicator, a quasi-co-located relationship, a transmission configuration indicator, a transmission direction, or one or more communication resources for the wireless communications.

5. The RAN node of claim 4, wherein the at least one processor is further operable to cause the RAN node to update the at least one transmission parameter for the wireless communications according to a time period, and wherein the time period comprises at least one of a delay prior to updating the at least one transmission parameter for the wireless communications or duration for applying the update to the at least one transmission parameter for the wireless communications.

6. The RAN node of claim 1 , wherein the third message is associated with a parameter that has a value of a control type corresponding to managing the CLI, and wherein the third message is received from at least one of the RAN controller or an additional RAN node.

7. The RAN node of claim 1, wherein the at least one CLI value comprises at least one of a reference signal received power, a received signal strength indicator, a signal to interference plus noise ratio, or a reference signal received quality.

8. The RAN node of claim 1, wherein at least one reference signal associated with the transmission of the reference signal comprises a sounding reference signal (SRS), and wherein the at least one second parameter is obtained based at least in part on the at least one first parameter.

9. A processor for wireless communication, comprising: at least one controller coupled with at least one memory and operable to cause the processor to: receive, from a RAN controller, a first message that indicates subscription information comprising at least one first parameter associated with a configuration of a reference signal for managing a cross-link interference (CLI); transmit, to a user equipment (UE), a second message that indicates at least one second parameter associated with the configuration of the reference signal, wherein the at least one second parameter indicates that the UE transmit the reference signal; and receive, based at least in part on a transmission of the reference signal, a third message that indicates at least one CLI value associated with the transmission of the reference signal from the UE.

10. A radio access network (RAN) node for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and operable to cause the RAN node to: receive, from a RAN controller, a first message that indicates subscription information comprising at least one first parameter associated with a configuration of a reference signal for managing a cross-link interference (CLI); transmit, to a user equipment (UE), a second message that indicates at least one second parameter associated with the configuration of the reference signal, wherein the at least one second parameter indicates that the UE perform at least one CLI measurement to obtain at least one CLI value; and receive, based at least in part on the at least one CLI measurement, a third message that indicates the at least one CLI value.

11. The RAN node of claim 10, wherein the at least one processor is further operable to cause the RAN node to: determine that the at least one CLI value satisfies a threshold value; and transmit, to at least one of the RAN controller or an additional RAN node, a fourth message that indicates that the at least one CLI value satisfies the threshold value, wherein the fourth message is associated with a parameter with a value of at least one of a report type corresponding to managing the CLI or an insert type corresponding to managing the CLI.

12. The RAN node of claim 11, wherein the at least one processor is further operable to cause the RAN node to: activate, based on transmitting the fourth message, one or more timers associated with suspending a CLI measurement procedure associated with the UE; and suspend the CLI measurement procedure associated with the UE until expiry of the one or more timers.

13. The RAN node of claim 12, wherein the at least one processor is further operable to cause the RAN node to receive a fifth message that indicates the one or more timers, and wherein a value of the one or more timers corresponds to respective parameters associated with the CLI measurement procedure associated with the UE.

14. The RAN node of claim 12, wherein the at least one processor is further operable to cause the RAN node to at least partially resume the CLI measurement procedure associated with the UE upon expiry of the one or more timers.

15. The RAN node of claim 12, wherein the at least one processor is further operable to cause the RAN node to terminate the CLI measurement procedure associated with the UE upon expiry of the one or more timers.

16. The RAN node of claim 10, wherein the at least one CLI value is associated with at least one reference signal transmission corresponding to a first network entity different from a second network entity that serves the UE.

17. The RAN node of claim 10, wherein the at least one second parameter indicates a periodicity for performing the at least one CLI measurement.

18. The RAN node of claim 10, wherein the at least one second parameter indicates a threshold value associated with the at least one CLI value, and wherein the third message is received based at least in part on the at least one CLI value satisfying the threshold value.

19. The RAN node of claim 10, wherein the at least one CLI measurement is associated with at least one sounding reference signal (SRS), and wherein the at least one second parameter is obtained based at least in part on the at least one first parameter.

20. A radio access network (RAN) controller for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and operable to cause the RAN controller to: transmit, to at least one RAN node, a first message that indicates subscription information comprising at least one parameter associated with a configuration of a reference signal for managing a cross-link interference (CLI), wherein the at least one parameter indicates at least one of that a user equipment (UE) transmit the reference signal or that the UE perform at least one CLI measurement to obtain at least one CLI value; and receive, based at least in part on the configuration of the reference signal, a second message that indicates the at least one CLI value associated with the UE.

Images