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 from a RAN controller that indicates subscription information including a first parameter indicative of configuration information for a user equipment (UE) and a second parameter indicative of a condition and an action to perform for managing a CLI based on the condition. The RAN node transmits a second message to the UE that indicates the first parameter. The RAN node detects a trigger event associated with one or more of the condition or the action indicated by the subscription information based on the configuration information. The trigger event is associated with the UE. The RAN node selectively performs the action for managing the CLI based on determining that the condition is met upon detection of the trigger event.

Description

CROSS-LINK INTERFERENCE MANAGEMENTRELATED APPLICATION

[0001] This application claims priority to U.S. Provisional Application Serial No. 63 / 553,567 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 indicative of configuration information associated with a UE and at least one second parameter indicative of a condition and an action to perform for managing a cross-link interference (CLI) based on the condition, transmit, to the UE, a second message that indicates the at least one first parameter indicative of the configuration information, detect, based on the configuration information, a trigger event associated with one or more of the condition or the action, and selectively perform the action for managing the CLI based on the condition and the trigger event.

[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 indicative of configuration information associated with a UE and at least one second parameter indicative of a condition and an action to perform for managing a CLI based on the condition, transmit, to the UE, a second message that indicates the at least one first parameter indicative of the configuration information, detect, based on the configuration information, a trigger event associated with one or more of the condition or the action, and selectively perform the action for managing the CLI based on the condition and the trigger event.

[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 indicative of configurationinformation associated with a UE and at least one second parameter indicative of a condition and an action to perform for managing a CLI based on the condition, transmitting, to the UE, a second message that indicates the at least one first parameter indicative of the configuration information, detecting, based on the configuration information, a trigger event associated with one or more of the condition or the action, and selectively performing the action for managing the CLI based on the condition and the trigger event.

[0008] In some implementations of the RAN node, the processor, and the method described herein, the configuration information indicates that the UE perform at least one CLI measurement to obtain at least one CLI value, and to detect the trigger event, the RAN node, the processor, and the method may further be configured to, capable of, or operable to receive, from the UE, a third message including the at least one CLI value, where the condition includes the at least one CLI value exceeding a threshold value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the RAN node, the processor, and the method may further be configured to, capable of, or operable to transmit, to at least one of the RAN controller or an additional RAN node, a fourth message based on the at least one CLI value exceeding the threshold value, where the fourth message indicates at least one of a difference between the at least one CLI value and the threshold value, the at least one CLI value, a beam associated with the at least one CLI value, or at least one time-frequency resource associated with the at least one CLI value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the RAN node, the processor, and the method may further be configured to, capable of, or operable to refrain from transmitting a fourth message based on the at least one CLI value failing to exceed the threshold value, where the fourth message indicates at least one of a difference between the at least one CLI value and the threshold value, the at least one CLI value, a beam associated with the at least one CLI value, or at least one time-frequency resource associated with the at least one CLI value.

[0009] Additionally, or alternatively, to selectively perform the action for managing the CLI, the RAN node, the processor, and the method may further be configured to, capable of, or operable to transmit a fourth message that indicates at least one of a reference signal or that the UE transmit the reference signal based on the at least one CLI value exceeding the threshold value, where the fourth message indicates at least one of a difference between the at least one CLI value and the threshold value, the at least one CLI value, a beam associated with the at least one CLI value, or atleast one time-frequency resource associated with the at least one CLI value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the RAN node, the processor, and the method may further be configured to, capable of, or operable to refrain from transmitting a fourth message that indicates at least one of a reference signal or that the UE transmit the reference signal based on the at least one CLI value failing to exceed the threshold value, where the fourth message indicates at least one of a difference between the at least one CLI value and the threshold value, the at least one CLI value, a beam associated with the at least one CLI value, or at least one time-frequency resource associated with the at least one CLI value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the RAN node, the processor, and the method may further be configured to, capable of, or operable to transmit a fourth message that indicates at least one of a reference signal or that the UE transmit the reference signal, where the reference signal is associated with a transmission power that satisfies a transmit power threshold corresponding to the threshold value based on the at least one CLI value exceeding the threshold value.

[0010] Additionally, or alternatively, to selectively perform the action for managing the CLI, the RAN node, the processor, and the method may further be configured to, capable of, or operable to transmit a fourth message that indicates at least one of a reference signal or that the UE transmit the reference signal, where a transmission power associated with the reference signal is maintained based on the at least one CLI value failing to exceed the threshold value. Additionally, or alternatively, the at least one CLI value includes at least one of an RSRP, an RS SI, an SINR, or an RSRQ. Additionally, or alternatively, the configuration information indicates that the UE transmit a reference signal, where to detect the trigger event, the RAN node, the processor, and the method may further be configured to, capable of, or operable to receive, from at least one of the RAN controller or an additional RAN node, a third message including at least one CLI value associated with a transmission of the reference signal, where the condition includes the at least one CLI value exceeding a threshold value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the RAN node, the processor, and the method may further be configured to, capable of, or operable to determine to perform at least one action based on the at least one CLI value exceeding the threshold value, and transmit, to the UE, a fourth message that indicates the UE update at least one transmission parameter for wireless communications associated with managingthe CLI, where the update to the at least one transmission parameter includes at least one of reducing a transmission power associated with the wireless communications, refraining from using one or more time-frequency resources for the wireless communications, or refraining from using a beam for the wireless communications.

[0011] Additionally, or alternatively, to transmit the fourth message, the RAN node, the processor, and the method may further be configured to, capable of, or operable to determine a time period associated with the update to the at least one transmission parameter, 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, to selectively perform the action for managing the CLI, the RAN node, the processor, and the method may further be configured to, capable of, or operable to determine not to perform at least one action based on the at least one CLI value exceeding the threshold value, and refrain from transmitting, to the UE, a fourth message that indicates the UE update a transmission parameter for wireless communications associated with the CLI, where the update to the transmission parameter includes at least one of reducing a transmission power associated with the wireless communications, refraining from using one or more time-frequency resources for the wireless communications, or refraining from using a beam for the wireless communications. 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, the reference signal includes a sounding reference signal (SRS).

[0012] Additionally, or alternatively, the RAN node, the processor, and the method may further be configured to, capable of, or operable to receive, from the RAN controller, a third message including a request for information associated with at least one of the UE or the RAN node, where at least one of the at least one first parameter or the at least one second parameter is based on the information associated with the at least one of the UE or the RAN node, and transmit, in response to the request, at least one of a fourth message that indicates the information associated with the at least one of the UE or the RAN node or a fifth message that indicates a failure to obtain the information associated with the at least one of the UE or the RAN node, where the informationincludes at least one of time division duplexing (TDD) information, sub-band full-duplex (SBFD) information, reference signal information, or information associated with the CLI. Additionally, or alternatively, the subscription information includes at least one third parameter that indicates a type of the first message is a policy type. 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, 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.

[0013] 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. For 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 first parameter indicative of configuration information associated with a UE and at least one second parameter indicative of a condition and an action to perform for managing a CLI based on the condition, and receive, from the at least one RAN node, a second message that indicates the action for managing the CLI is performed based on the condition and a trigger event associated with the UE, where the trigger event is associated with one or more of the condition or the action indicated by the subscription information.

[0014] 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 first parameter indicative of configuration information associated with a UE and at least one second parameter indicative of a condition and an action to perform for managing a CLI based on the condition, and receive, from the at least one RAN node, a second message that indicates the action for managing the CLI is performed based on the condition and a trigger event associated with the UE, where the trigger event is associated with one or more of the condition or the action indicated by the subscription information.

[0015] 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 first parameter indicative of configurationinformation associated with a UE and at least one second parameter indicative of a condition and an action to perform for managing a CLI based on the condition, and receiving, from the at least one RAN node, a second message that indicates the action for managing the CLI is performed based on the condition and a trigger event associated with the UE, where the trigger event is associated with one or more of the condition or the action indicated by the subscription information.

[0016] In some implementations of the RAN controller, the processor, and the method described herein, the configuration information indicates that the UE perform at least one CLI measurement to obtain at least one CLI value, where the trigger event includes the at least one RAN node receiving a third message including the at least one CLI value, where the condition includes the at least one CLI value exceeding a threshold value. Additionally, or alternatively, the second message indicates at least one of a difference between the at least one CLI value and the threshold value, the at least one CLI value, a beam associated with the at least one CLI value, or at least one time-frequency resource associated with the at least one CLI value. Additionally, or alternatively, the second message includes one or more of a first reference signal or an indication that the UE transmits a second reference signal, where the first reference signal and the second reference signal are associated with a transmission power that satisfies a transmission power threshold corresponding to 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 configuration information indicates that the UE transmit a reference signal, where the trigger event includes the at least one RAN node receiving a third message including at least one CLI value associated with a transmission of the reference signal, where the condition includes the at least one CLI value exceeding a threshold value. Additionally, or alternatively, the condition includes the at least one CLI value exceeding the threshold value, where the second message is associated with the UE updating at least one transmission parameter for wireless communications associated with the CLI, where the update to the at least one transmission parameter includes at least one of reducing a transmission power associated with the wireless communications, refraining from using one or more time-frequency resources for the wireless communications, or refraining from using a beam for the wireless communications. 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.

[0017] 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 including a request for information associated with at least one of the UE or the at least one RAN node, where at least one of the at least one first parameter or the at least one second parameter is based on the information associated with the at least one of the UE or the at least one RAN node, and receive, in response to the request, at least one of a fourth message that indicates the information associated with the at least one of the UE or the at least one RAN node or a fifth message that indicates a failure to obtain the information associated with the at least one of the UE or the at least one RAN node, where the information associated with the at least one of the UE or the at least one RAN node includes at least one of a TDD information, a SBFD information, reference signal information, or information associated with the CLI. 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 at least one third 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 SBFD information, or configuration information associated with the UE, and determine the at least one first parameter and the at least one second parameter of the first message based on the at least one third parameter. Additionally, or alternatively, the subscription information includes at least one third parameter that indicates a type of the first message is a policy type. 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.BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

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

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

[0025] Figure 18 illustrates a flowchart of a method performed by a RAN node in accordance with aspects of the present disclosure.

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

[0027] 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.

[0028] 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 communicationscheme, 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 nearby UE 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.

[0029] 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.

[0030] 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 a RAN node. The subscription information may include one or more rules (e.g., policy rules) that define one or more conditions and one or more actions for managing CLI. For example, a rule may indicate to the RAN node to take one or more actions in response to one or more trigger events and / or for the RAN node to indicate to one or more UEs to take the actions in response to the trigger events. In response, the RAN node and / or the UE may determine whether the one or more events are triggered (e.g., one or more conditions associated with the events are satisfied). If a trigger event is detected and conditions associated with the event are satisfied (e.g., an RSRP value and / or CLI value exceed a threshold value), then the RAN node may take the one or more actions and / or may indicate for the UE to take the one or more actions, as indicated by the rule. For example, the RAN node and / or the UE may report one or more CLI values to the RAN controller and / or to a RAN node, may update one or more communication parameters (e.g., reduce a transmission power, select one or more timefrequency resources for a transmission, and / or select a beam for a transmission), and / or may transmit a reference signal. In some examples, the RAN node may transmit a report to the RAN controller upon execution of an action according to a rule.

[0031] 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.

[0032] 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.

[0033] 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.

[0034] 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.

[0035] 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 bereferred 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.

[0036] 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.

[0037] 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 or more 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).

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

[0039] 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).

[0040] 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 various frame structures (e.g., multiple frame structures). The NEs 102 and the UEs 104 may support various frame structures based on one or more numerologies.

[0041] 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.

[0042] 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.

[0043] 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. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., / r=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0044] 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, FR1may 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.

[0045] 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.

[0046] 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 resulting radiation pattern may be called a beam, which may, or may not, be unimodal and may provide for the device (e.g., UE 104, node) to amplify signals that are transmitted or received from one or more spatial directions.

[0047] 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 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.

[0048] 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 or low noise amplifier (LNA) power consumption associated with the antenna elements or antenna ports). The phrase “active for radiating energy,” as used herein, refers to a transmit function and / 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 in general, for performing intended functionality. Communicating on the active elements of an antenna panel enables generation of radiation patterns or beams.

[0049] 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 beam independently, 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 device’s physical antennas 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 assumes there will be 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.

[0050] 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 quasi co-located (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. 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. For 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, Power Angular Spectrum (PAS) of AoA, average angle of departure (AoD), PAS of AoD, transmit / receive channel correlation, transmit / 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).

[0051] An “antenna port” may be a logical port that may correspond to a beam (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 aphysical 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.

[0052] In some cases, a transmission configuration indicator (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., synchronization signal block (SSB), channel station information-reference signal (CSI-RS), and / or 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.

[0053] 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 device-dedicated 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.

[0054] 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, CSI-RS, and / or SRS). For 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 CSI-RS). 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.

[0055] 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 reference signal, 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 inthe 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.

[0056] 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).

[0057] 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.

[0058] 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.

[0059] 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 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 NE. 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.

[0060] 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.

[0061] A remote interference scenario may involve any numerical quantity of RAN nodes, where a RAN node may execute remote interference management (RIM) coordination. RAN nodes can 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.

[0062] 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 frameworkuses 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.

[0063] 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 and the 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.

[0064] 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 experiencethe 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.

[0065] 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 to 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.

[0066] 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 to 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, a UE 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.

[0067] 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 to 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 alinear 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 the frequency ranges 1 and 2, 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.

[0068] In some cases, the UE 104-a may be configured to 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.

[0069] 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 managing inter-UE CLI 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 mayprovide 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.

[0070] 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 SBED and dynamic / flexible TDD. Lor 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).

[0071] 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 CSI-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 and / or resource block (RB) muting patterns).

[0072] 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.

[0073] 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 O-RAN architecture, aspects of the methods, systems, and apparatuses as described herein may be implemented in the context of additional, or alternatively, network architectures.

[0074] 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 next generation 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.

[0075] 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 orchestration framework 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.

[0076] 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 servicessupported 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 services may 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.

[0077] The service management and orchestration framework 306 may include an O-CU- control plane (CP) 312 responsible for control plane 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-user plane (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 user plane 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).

[0078] 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 O-RU 318, which may be an RU that supports the O-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 O-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 O-RU 318. Additionally, or alternatively, the O-RU 318 may be connected to the O-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 O-RU 318 and / or O-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 O-DU 310, the O-eNB 308, and the O-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 304.

[0079] 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.

[0080] 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 transportnetwork 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.

[0081] 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 than described or are not performed. In some cases, processes may include additional features not mentioned below, or further processes may be added.

[0082] 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.

[0083] 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, asubscription 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.

[0084] 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.

[0085] 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 therequest 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.

[0086] 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.

[0087] 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 subscription modification request to modify an existing subscription. At 514, the RAN node may transmit a message to the RAN controller including a subscription modification response.

[0088] 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.

[0089] 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.

[0090] 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. The information 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.

[0091] 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 SBFDconfiguration). For example, the RAN node may expose the function prior to configuring a d / f-TDD or SBFD 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.

[0092] 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).

[0093] 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 message may 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).

[0094] 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.

[0095] 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, thatinclude 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.

[0096] 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 a procedure with a type of POLICY for managing CLI, which is described in further detail with respect to Figures 6 through 14. The subscription procedure messages may include one or more of an indication of a reporting action (e.g., Action = POLICY).

[0097] 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 CLI-RSSI.

[0098] Unlike obtaining CLI-RSSI, 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 CLI-RSSI, SRS-RSRP provides a measure of CLI from a specific source (e.g., the transmitting UE), as opposed to CLI-RSSI 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, CLI-RSSI, or other measure of CLI may be referred to as a CLI or CLI value.

[0099] 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.

[0100] 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 signalingdiagram 600 may illustrate an example of a policy procedure for inter-UE 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.

[0101] The RAN controller 602 may provide various services to the RAN node 604 (e.g., REPORT, INSERT, CONTROL, POLICY, and QUERY). One or more of the services may be used for a UE-to-UE CLI management process. The different services may be adopted in different procedure instances or subscriptions, or in any combination in a single procedure instance or subscription. The POLICY service may provide for the RAN controller 602 to perform a subscription procedure signaling with the RAN node 604 to indicate policy rules to execute for CLI management. The RAN controller 602 may indicate the policy rules to the RAN node 604 as a part of a UE-to-UE CLI management process, an operation of an enhanced duplexing scheme such as dynamic and / or flexible TDD or SBFD, a resource allocation process, or the like.

[0102] In some examples, at 606, a control entity (e.g., an 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, including, but not limited to, CLI management processes. The subscription procedure may include one or more of subscription signaling, subscription modification signaling, and the like.

[0103] In some cases, at 608, the RAN node 604 and / or the RAN controller 602 may exchange one or more messages for a subscription procedure with a type of REPORT. The messages may include information and / or parameters for measuring and reporting one or more CLI values to a RAN controller 602.

[0104] In some examples, the subscription procedure may include signaling related to transmission of a report indicating CLI information, such as by including an indication that a value to be reported is a CLI (e.g., key performance measurement (KPM) = CLI), or an indication of whattriggers a CLI reporting message (e.g., a trigger condition for CLI reporting). A KPM may be specified for measurements and reporting for a RAN node 604 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 a RAN controller 602, among other functionalities. The “KPM Monitor” RAN function may provide REPORT services, such as measurements by a RAN node 604, measurements for a UE 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, 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.

[0105] 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.

[0106] 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 CLI reporting. 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 theRSSI 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.

[0107] 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.

[0108] 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 procedure signaling. In some other cases, the parameters may be communicated as an OCTET STRING in thesubscription 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.

[0109] 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.

[0110] 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 CLImeasurements. 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.

[0111] 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.

[0112] 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 value of T from information indicated in the subscription procedure, configured by the network and / orOAM, 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).

[0113] 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.

[0114] 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, aRAN node 604, a group of RAN nodes 604, a cell, a group of cells, a UE 104, a group of UEs 104, or the like.

[0115] At 610, the RAN node 604 and / or the RAN controller 602 may exchange one or more messages for a subscription procedure with a type of POLICY. The RAN controller 602 may send, in one or more messages in the subscription procedure, information for a UE-to-UE CLI management policy to be executed at the RAN node 604 and / or a UE 104. The subscription procedure messages may include one or more of an indication of a policy action (e.g., Action = POLICY). Additionally, or alternatively, the subscription procedure may indicate one or more policy rules for managing CLI by the RAN node 604. A policy rule may indicate to the RAN node 604 to take one or more actions in response to one or more triggering events (e.g., if one or more conditions associated with the triggering events are satisfied). In addition, the process based on the POLICY service may include a RAN node 604 reporting or indicating to the RAN controller 602 that an action is performed according to a policy rule.

[0116] At 612, the RAN node 604 and / or the UE 104 may detect a trigger event associated with a policy rule. For example, in response to the subscription procedure signaling at 610, the RAN node 604 and / or the UE 104 may determine whether the one or more events are triggered (e.g., one or more conditions associated with the events are satisfied).

[0117] At 614, the RAN node 604 and / or the UE 104 may selectively perform an action according to the policy rule (e.g., may determine to perform the action and / or may not perform an action). For example, if the events are triggered, then the RAN node 604 and / or the UE 104 may take the one or more actions as indicated by the rule. At 616, the RAN node 604 and / or the UE 104 may continue an associated procedure. For example, if the RAN node 604 and / or the UE 104 is configured with a reporting procedure, then the RAN node 604 and / or the UE 104 may continue with the reporting procedure. Additionally, or alternatively, the process based on the POLICY service may include a reporting to the RAN controller 602 once the RAN node 604 and / or the UE 104 takes an action according to a policy rule.

[0118] In some examples, at 618, the RAN node 604 may transmit a RAN controller indication to the RAN controller 602. In variations, the RAN node 604 may automatically send a report to the RAN controller 602 upon taking an action according to a subscription based on the POLICYservice, which may be defined and / or preconfigured, indicated by the subscription, or determined by the RAN node 604. In some other variations, a reporting message may be specified or indicated as an action in one or more policy rules according to the subscription. A policy rule may indicate to the RAN node 604 to send a report to the RAN controller 602 upon taking an action according to the policy rule. In some other variations, additional subscription signaling, which may, or may not, be included in the same subscription procedure, may indicate for the RAN node 604 to send a report if an action is taken according to the indicated policy rules.

[0119] 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 / or the signaling diagram 600. The signaling diagram 700 may illustrate an example of a policy procedure for inter-UE CLI measurement and reporting between a RAN controller 702, a RAN node 704, and a UE 104. The RAN controller 702, the RAN node 704, and the UE 104 may be examples of corresponding devices (e.g., a CN 106, a RAN node 202, 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.

[0120] In some examples, at 706, a control entity (e.g., an RIC), which may additionally, or alternatively, be referred to as a RAN controller 702, 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 subscription information that includes parameters for monitoring and / or controlling one or more processes at a RAN node 704 and / or at a UE 104, including, but not limited to, UE-to-UE CLI management processes.

[0121] At 708, the RAN controller 702 and the RAN node 704 may exchange one or more messages for a subscription procedure with a type of POLICY, as described with reference to Figure 6. A subscription may use a POLICY service separately or in combination with other services such as REPORT, INSERT, and CONTROL. For example, signaling and behavior according to the above examples may be combined with signaling and behavior based on otherservices in a same or separate subscriptions. A POLICY service provided by the RAN or converged RAN-CN may be used for UE-to-UE CLI management by augmenting an existing ‘style’ such as policy for radio resource allocation, policy for radio access control, policy for measurement reporting configuration control, policy for beamforming configuration control, or the like. Additionally, or alternatively, a new policy service style may be introduced for radio resource management, enhanced duplexing operation, interference management, or the like.

[0122] A POLICY service may implement one or more of triggering events, actions, or RAN parameters. In some variations, the triggering event may initiate the POLICY service by a message event, a call process breakpoint, a RAN node information change, a UE information change, or the like. The POLICY may include one or more actions, where respective actions are identified by an action identifier, an action name, an action description, or the like. The RAN parameters may include one or more parameters to be controlled by the RAN controller 702 in association with the policy, triggering event, and / or action. The triggering events, actions, and / or RAN parameters may be defined and / or preconfigured, indicated by the subscription procedure signaling at 710, or determined according to a configuration by the network and / or 0AM. The RAN parameters may be used to define the policy condition and / or RAN imperative policy, among others. An imperative policy may refer to a type of policy that explicitly specifies actions or behaviors for the RAN node 704 to follow. Imperative policies may be considered prescriptive and provide clear instructions on how one or more aspects of the network should be managed or controlled. Key characteristics of imperative policies may include explicit instructions near-real-time control, enforcement by a RAN controller 702, and dynamic adaptation for performance optimization, resource utilization, or other operational objectives. The term “imperative policies” may be used in contrast with “declarative policies” that focus more on specifying desired outcomes or goals without explicitly detailing step- by-step instructions for achieving them.

[0123] At 710, the RAN node 704 may transmit signaling to the UE 104 indicating one or more configurations. In some examples, the signaling can include RRC signaling. The configurations can include, but are not limited to, one or more TDD and / or SBFD configurations for communications (e.g., transmission and reception of signaling) according to a TDD communication scheme and / or an SBFD communication scheme, one or more SRS configurations, and / or one or more CLI reporting configurations.

[0124] In some examples, an SRS is an uplink reference signal that a UE 104 may transmit for channel measurement and / or interference measurement. 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 (e.g., a UE 1) being impacted by interference from another UE (e.g., a UE 2) causing interference provided that the UE is informed of the configuration parameters of the SRS that the other UE 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.

[0125] The SRS configuration can include one or more parameters, such as parameters of timefrequency 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.

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

[0127] The RAN controller 702 further indicates the SRS parameter values to at least one RAN node 704 (e.g., a RAN node 1 and / or a RAN node 2) through a subscription procedure signaling for CLI measurement and reporting. The RAN node 704 then uses the information to configure a UE 104 (e.g., a 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 704). A relatively large numerical quantity of SRSparameters (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 one or more UEs 104 (e.g., the UE 1 and the UE 2) through respective configurations from RAN nodes (e.g., the RAN node 1 and the RAN node 2).

[0128] 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.

[0129] 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 704serving the UEs 104. In some examples, when the UE 104 performs a handover from a cell by a RAN 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.

[0130] At 712, the RAN node 704 and / or the UE 104 may detect a trigger event. At 714, the RAN node 704 and / or the UE 104 may test one or more event trigger conditions. In some examples, a triggering event may be of type message event. The RAN node 704 may determine that an event is triggered (e.g., a trigger event condition is satisfied) upon receiving a message. While the RAN node 704 does not receive the message, the trigger event condition is not satisfied. Examples of messages include, but are not limited to, a message from a RAN controller 702 (e.g., an indication message including a report or a message copy), a message from another RAN node 704 on a network interface (e.g., a message on an Xn interface including an IE), a message from a UE 104 (e.g., a UCI message received on a PUCCH or PUSCH, a MAC-CE message, an RRC message), a message from a core network function (e.g., a message on an NG interface from an AMF), or a message from another RAN node 704 over-the-air. In some other examples, a triggering event may be of type call process breakpoint. The RAN node 704 may determine that an event is triggered (e.g., a trigger event condition is satisfied) upon detecting a change in a breakpoint of a call process. If there is no change to the breakpoint in the call process, then the trigger event condition is not satisfied. Examples of call processes and breakpoints include, but are not limited to, a statistics of resource usage associated with a radio resource of the RAN node 704 (e.g., a flexible symbol and / or slot, a sub-band for full-duplex operation, or a beam) and / or a CLI value measured or obtained by the RAN node 704.

[0131] In some other examples, a triggering event may be of type RAN node information change. The RAN node 704 may determine that an event is triggered (e.g., a trigger event condition is satisfied) upon detecting a change in information associated with the RAN node 704. If no change in information associated with the RAN node 704 is detected, then the trigger event condition is not satisfied. Examples include, but are not limited to, a change in a cell configuration (e.g., a resource configuration, a channel configuration, a cell common TDD configuration, an SBFD configuration), a change in cell neighbor relations, or a change in a slice configuration. In some other examples, a triggering event may be of type UE information change. The RAN node 704 may determine that anevent is triggered (e.g., a trigger event condition is satisfied) upon detecting a change in information associated with a UE 104 connected to the RAN node 704. If no change in information associated with the UE is detected, then the trigger event condition is not satisfied. Examples include, but are not limited to, a change of an RRC configuration of the UE 104 (e.g., a change in a UE-specific, dedicated TDD configuration or a UE-specific, dedicated SBFD configuration), a change of L1 / L2 communication parameters associated with the UE 104 as indicated by LI and / or L2 signaling (e.g., a dynamic change in a TDD configuration or an SBFD configuration), a higher-layer change associated with the UE 104, a mobility change associated with the UE 104, a UE identifier changed or removed, or a UE 104 joining or leaving a group of UEs with a UE group identifier.

[0132] In some examples, testing the event trigger conditions (e.g., at 714) includes determining the event trigger conditions are satisfied for a detected event trigger. At 716, the RAN node 704 may test one or more policy conditions. For example, the subscription procedure signaling at 708 may indicate one or more conditions for respective trigger events, such as a CLI value of one or more CLI measurements satisfying (e.g., exceeding) a threshold value, an RSRP value of one or more RSRP measurements satisfying (e.g., exceeding), or the like.

[0133] At 718, the RAN node 704 may determine an action based on a policy rule. For example, if the conditions are satisfied, then the RAN node 704 may determine an action based on the subscription procedure signaling at 708 indicating the action. In some examples, a policy condition being satisfied triggers a policy action and is not indicative of a satisfactory performance of the network. Examples of actions by the RAN node 704 include, but are not limited to, reducing a transmission power to reduce or mitigate CLI, transmitting signaling to a UE 104 to reduce an uplink transmission power to mitigate CLI, constraining communications on a resource or beam to mitigate CLI (e.g., by refraining from using a resource or beam for communications), sending a message including a CLI value to the RAN controller 702, sending a message including a CLI value to another RAN node 704, increasing a transmission power of a reference signal to indicate that an excessive CLI is detected, transmitting signaling to a UE 104 to increasing a transmission power of a reference signal to indicate that an excessive CLI is detected, increasing a transmission power of a signal when the signal does not cause excessive CLI, transmitting signaling to a UE 104 to increase a transmission power of an uplink signal when the signal does not cause excessive CLI, lifting a criteria for communications on a resource or beam when the communications do not causeexcessive CLI, and modifying a subscription or configuration, where the CLI is UE-to-UE CLI and / or other CLL

[0134] A policy rule may be indicated to the RAN node 704 through one or more parameters, which are referred to as RAN parameters. A RAN parameter may be specified by a unique preconfigured or otherwise defined RAN parameter identifier, configured by the network and / or 0AM, indicated by a signaling, determined by an implementation, or any combination thereof. The RAN parameter identifier may be an integer number, or otherwise it may include any combination of parameters that uniquely indicate the associated RAN parameter. V arious RAN parameters may pertain to triggering events, conditions, actions, among others.

[0135] A format may be specified to provide the policy conditions and associated policy actions. A condition-action policy rule may be defined as a sequence of RAN parameters that indicate a policy action identifier, a policy condition, and / or a policy action. A policy action is described as a list of test conditions. If configured, one or more policy conditions may be evaluated by the RAN node 704 to determine whether to execute an associated policy actions. If a policy condition is not met, the RAN node 704 may execute a default action or follow a default behavior. A policy action is described as a list of RAN parameters and / or their values.

[0136] For example, at 720, the RAN node 704 may determine no action and / or a default action. The RAN node 704 may determine no action and / or a default action based on the condition not being satisfied. Additionally, or alternatively, at 722, the RAN node 704 may determine no action and / or a default action. The RAN node 704 may determine no action and / or a default action based on the trigger event condition not being satisfied.

[0137] At 724, the RAN node 704 and / or the UE 104 may execute the action. For example, the RAN node 704 may execute an action and / or may instruct a UE 104 to execute an action via signaling based on the policy rule based on the determination at 718 (e.g., if the trigger event condition is satisfied and the condition is satisfied). Additionally, or alternatively, the RAN node 704 may execute no action and / or a default action based on the condition not being satisfied and / or based on the trigger event condition not being satisfied.

[0138] 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 thewireless 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 / or the signaling diagram 700. The signaling diagram 800 may illustrate an example of a policy procedure for inter-UE CLI measurement and reporting between a RAN controller 802, a RAN node 804, and a UE 104. The RAN controller 802, the RAN node 804, and the UE 104 may be examples of corresponding devices (e.g., a CN 106, a RAN node 202, 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.

[0139] In practical scenarios in a cellular network, a RAN node 804 and / or a UE 104 experiencing CLI in an interference scenario may also be causing CLI due to reciprocity of the wireless channel. Therefore, the subscription procedure between the RAN controller 802 and the RAN node 804 may include policy rules for managing interference as both the device (e.g., RAN node 804 and / or UE 104) causing the interference and experiencing the interference, including reporting excessive interference, and reducing a transmission power and / or constraining transmission and / or reception resources or beams. However, for simplicity, example embodiments are presented separately for a RAN node 1 serving a UE 1 , which is a UE experiencing CLI in a CLI scenario, and a RAN node 2 serving a UE 2, which is a UE causing the CLI.

[0140] In some examples, at 806, a control entity (e.g., an RIC), which may additionally, or alternatively, be referred to as a 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 subscription information that includes parameters for monitoring and / or controlling one or more processes at a RAN node 1 and / or at a UE 1, including, but not limited to, UE-to-UE CLI management processes.

[0141] At 808, the RAN controller 802 and the RAN node 1 may exchange one or more messages for a subscription procedure with a type of POLICY, as described with reference to Figures 6 and 7. At 810, the RAN node 1 may transmit signaling to the UE 1 indicating one or more configurations. In some examples, the signaling can include RRC signaling. The configurations can include, but are not limited to, one or more TDD and / or SBFD configurations for communications(e.g., transmission and reception of signaling) according to a TDD communication scheme and / or an SBFD communication scheme, one or more SRS configurations, and / or one or more CLI reporting configurations.

[0142] At 812, the RAN node 1 and / or the UE 1 can transmit and receive communications. The communications can include wireless communications, such as data transmissions and / or control signaling. In some examples, the RAN node 1 and the UE 1 communicate according to TDD and / or SBFD communications schemes.

[0143] At 814, the UE 1 receives one or more SRSs over the air (e.g., indicated by the dotted line). For example, a UE 2 may broadcast the SRSs, or any other reference signal type, over the air to one or more surrounding or nearby devices, including the UE 1.

[0144] At 816, the UE 1 transmits a CLI report to the RAN node 1. For example, the UE 1 measures one or more CLI values and reports the CLI values to the RAN node 1. In variations, the UE 1 may measure the CLI values according to a CLI reporting configuration received at 810. 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. 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 5. Example content of the CLI report may include the measurements as described with reference to Figure 5.

[0145] In some examples, the subscription information at 808 may indicate for the RAN node 1 to indicate to the UE 1 to perform a periodic reporting of CLI and / or may indicate for the RAN node 1 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 UE 1 and / or the RAN node 1 may measure CLI to obtain one or more CLI values. For example, the UE 1 performs a CLI measurement on the reference signal (e.g., the SRSs received at 814) from another UE. The UE 1 sends a CLI report including a measured CLI value, in accordance with the configuration from the RAN node 1 , periodically or upon determining that the measured CLI value is satisfies a threshold. For example, the UE 104 may transmit the CLI report if a measured CLI value satisfies (e.g., exceeds, is greater than, is above) a threshold value and / or if the UE 104determines a periodicity timer is expired. In variations, the RAN node 1 can indicate the periodicity and / or the threshold value in a CLI reporting configuration at 810.

[0146] In some examples, the RAN controller 802 and / or the RAN node 1 may indicate, through the subscription procedure signaling at 808 and / or through the configuration signaling at 810, information on what CLI measure for the RAN node 804 and / or the UE 1 to include in a CLI report (e.g., at 816). For example, the RAN controller 802 may indicate to the RAN node 1 to report and / or may indicate to the RAN node 804 to instruct the UE 1 to report an RSSI as a measure of CLI. The RAN controller 802 may further indicate resources on which the RSSI is to be measured. The RAN controller 802 may indicate to a first set of RAN nodes, including the RAN node 1, to avoid using the resources for transmissions by a second set of RAN nodes, the UEs served by the second set of RAN nodes, or both. Then, the RAN node 1 may configure a UE 104 to measure RSSI associated with transmissions from UEs 104 served by the second set of RAN nodes. In some examples, the RAN controller 802 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 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.

[0147] In some examples, the RAN controller 802 may indicate to the RAN node 1 to report and / or may indicate to the RAN node 1 to instruct the UE 1 to report an RSRP associated with one or more reference signals that are transmitted by one or more UEs served by a RAN node 2. The RAN controller 802 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 RAN node 2.

[0148] 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 808. The OCTET STRING may then be decoded by the RAN node 1 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 802 may indicate to the RAN node 1 and / or may indicate to the RAN node 1 to instruct the UE 1 to report an RS SI, an SINR, an RSRQ, and / or an RSRP as a measure of CLI.

[0149] The RAN controller 802 may indicate, through the subscription procedure signaling at 808, information on how to measure CLI. For example, the RAN controller 802 may indicate to the RAN node 1 to configure the UE 1 to perform a CLI measurement and to configure the UE 1 to examine the measured CLI and / or for the RAN node 1 to examine the CLI measured by the UE 1 to determine whether an event is triggered. The RAN controller 802 may indicate for the RAN node 1 and / or the UE 1 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 802 may indicate a periodicity for performing CLI measurements, which may or may not be equal to a periodicity for CLI reporting.

[0150] In some other examples, the RAN controller 802 may indicate for the RAN node 1 and / or the UE 1 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 1 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 1 may receive an indication of a periodicity for performing the CLI measurements. The periodicity may be indicatedin units of slots, subframes, frames, milliseconds, seconds, or the like. In some other examples, the RAN controller 802 may indicate to the RAN node 1 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 802 may indicate to the RAN node 1 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 802 may indicate to the RAN node 1 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 1 through the subscription procedure signaling, configured by the network, preconfigured, or otherwise defined, determined by implementation, or any combination thereof.

[0151] In some examples, a CLI report from a RAN node 1 and / or from a UE 1 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 1 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 1 or the UE 1 served by the RAN node 1. The RAN node 1 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 1 and / or the UE 1 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 1 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 1 experiencing the CLI, determined based on an implementation, or any combination thereof. In some examples, the RAN node 1 and / or the UE 1 may indicate the threshold value in the CLI report or other signaling. The RAN node 1 and / or the UE 1 may round the value of Y to the nearest value in an enumerated set as configured or specified.In some examples, the RAN controller 802 may use the value of Y, as reported by a RAN node 1 and / or the UE 1 , to request a reduction of a transmission power by Y dB via CONTROL signaling.

[0152] In some examples, the parameters include an indication of associated beams. For example, the RAN node 1 and / or a UE 1 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.

[0153] 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 804, a group of RAN nodes, a cell, a group of cells, a UE 104, a group of UEs, or the like.

[0154] At 818, the RAN node 1 may detect a trigger event. At 820, the RAN node 1 determines an action based on a policy rule. For example, if the conditions are satisfied, then the RAN node 1 may determine an action based on the subscription procedure signaling at 808 indicating the action. Examples of actions by the RAN node 1 and / or the UE 1 include, but are not limited to, sending amessage including a CLI value to the RAN controller 802 and / or sending a message including a CLI value to another RAN node 804. At 822, the RAN node 1 may determine no action and / or a default action. The RAN node 1 may determine no action and / or a default action based on the condition not being satisfied. Additionally, or alternatively, at 824, the RAN node 1 may determine no action and / or a default action. The RAN node 1 may determine no action and / or a default action based on the trigger event condition not being satisfied.

[0155] At 826, the RAN node 1, the RAN controller 802, and / or the UE 1 may execute the action. For example, the RAN node 1 may execute an action and / or may instruct a UE 104 to execute an action via signaling based on the policy rule based on the determination at 820 (e.g., if the trigger event condition is satisfied and the condition is satisfied). Additionally, or alternatively, the RAN node 1 may execute no action and / or a default action based on the condition not being satisfied and / or based on the trigger event condition not being satisfied. For example, the RAN node 1 and / or the UE 1 may transmit a CLI report to the RAN controller 802 and / or to a RAN node 2.

[0156] Figure 9 illustrates an example of signaling diagram 900 in accordance with aspects of the present disclosure. In some examples, the signaling diagram 900 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, the signaling diagram 700, and / or the signaling diagram 800. The signaling diagram 900 may illustrate an example of a policy procedure for inter-UE CLI measurement and reporting between a RAN controller 902, a RAN node 904, and a UE 104. The RAN controller 902, the RAN node 904, and the UE 104 may be examples of corresponding devices (e.g., a CN 106, a RAN node 202, 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.

[0157] In practical scenarios in a cellular network, a RAN node 904 and / or a UE 104 experiencing CLI in an interference scenario may also be causing CLI due to reciprocity of the wireless channel. Therefore, the subscription procedure between the RAN controller 902 and the RAN node 904 may include policy rules for managing interference as both the device (e.g., RAN node 904 and / or UE 104) causing the interference and experiencing the interference, includingreporting excessive interference, and reducing a transmission power and / or constraining transmission and / or reception resources or beams. However, for simplicity, example embodiments are presented separately for a RAN node 1 serving a UE 1 , which is a UE experiencing CLI in a CLI scenario, and a RAN node 2 serving a UE 2, which is a UE causing the CLI.

[0158] In some examples, at 906, a control entity (e.g., an RIC), which may additionally, or alternatively, be referred to as a RAN controller 902, 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 subscription information that includes parameters for monitoring and / or controlling one or more processes at a RAN node 2 and / or at a UE 2, including, but not limited to, UE-to-UE CLI management processes.

[0159] At 908, the RAN controller 902 and the RAN node 2 may exchange one or more messages for a subscription procedure with a type of POLICY, as described with reference to Figures 6 and 7. At 910, the RAN node 2 may transmit signaling to the UE 2 indicating one or more configurations. In some examples, the signaling can include RRC signaling. The configurations can include, but are not limited to, one or more TDD and / or SBFD configurations for communications (e.g., transmission and reception of signaling) according to a TDD communication scheme and / or an SBFD communication scheme and / or one or more SRS configurations.

[0160] At 912, the RAN node 2 and / or the UE 2 can transmit and receive communications. The communications can include wireless communications, such as data transmissions and / or control signaling. In some examples, the RAN node 2 and the UE 2 communicate according to TDD and / or SBFD communications schemes.

[0161] At 914, the UE 2 transmits one or more SRSs over the air (e.g., indicated by the dotted line) to a RAN node 2, a RAN controller 902, a RAN node 1, and / or a 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, including a UE 1.

[0162] At 916, the RAN node 2 may detect a trigger event. At 918, the RAN node 2 determines an action based on a policy rule. For example, if the conditions are satisfied, then the RAN node 2 may determine an action based on the subscription procedure signaling at 908 indicating the action. Examples of actions by the RAN node 2 and / or the UE 2 include, but are not limited to, reducing atransmission power and / or constraining one or more transmission or reception beams or resources. At 920, the RAN node 2 may determine no action and / or a default action. The RAN node 2 may determine no action and / or a default action based on the condition not being satisfied. Additionally, or alternatively, at 922 the RAN node 2 may determine no action and / or a default action. The RAN node 2 may determine no action and / or a default action based on the trigger event condition not being satisfied.

[0163] At 924, the RAN node 2, the RAN controller 902, and / or the UE 2 may execute the action. For example, the RAN node 2 may execute an action and / or may instruct a UE 2 to execute an action via signaling based on the policy rule based on the determination at 918 (e.g., if the trigger event condition is satisfied and the condition is satisfied). Additionally, or alternatively, the RAN node 2 may execute no action and / or a default action based on the condition not being satisfied and / or based on the trigger event condition not being satisfied. For example, the RAN node 2 and / or the UE 2 may reduce a transmission power for wireless communications, refrain from using (e.g., constrain) one or more time-frequency resources for the wireless communications, or refraining from using a beam for the wireless communications.

[0164] Figure 10 illustrates an example of signaling diagram 1000 in accordance with aspects of the present disclosure. In some examples, the signaling diagram 1000 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, the signaling diagram 700, the signaling diagram 800, and / or the signaling diagram 900. The signaling diagram 1000 may illustrate an example of a policy procedure for inter-UE CLI measurement and reporting between a RAN controller 1002, a RAN node 1004, and a UE 104. The RAN controller 1002, the RAN node 1004, and the UE 104 may be examples of corresponding devices (e.g., a CN 106, a RAN node 202, 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.

[0165] In practical scenarios in a cellular network, a RAN node 1004 and / or a UE 104 experiencing CLI in an interference scenario may also be causing CLI due to reciprocity of the wireless channel. Therefore, the subscription procedure between the RAN controller 1002 and theRAN node 1004 may include policy rules for managing interference as both the device (e.g., RAN node 1004 and / or UE 104) causing the interference and experiencing the interference, including reporting excessive interference, and reducing a transmission power and / or constraining transmission and / or reception resources or beams. However, for simplicity, example embodiments are presented separately for a RAN node 1 serving a UE 1 , which is a UE experiencing CLI in a CLI scenario, and a RAN node 2 serving a UE 2, which is a UE causing the CLI.

[0166] In some examples, at 1006, a control entity (e.g., an RIC), which may additionally, or alternatively, be referred to as a RAN controller 1002, 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 subscription information that includes parameters for monitoring and / or controlling one or more processes at a RAN node 1 and / or at a UE 1, including, but not limited to, UE-to-UE CLI management processes.

[0167] At 1008, the RAN controller 1002 and the RAN node 1 may exchange one or more messages for a subscription procedure with a type of POLICY, as described with reference to Figures 6 and 7. For example, the signaling can include a parameter indicating an action type of POLICY, one or more parameters indicating policy rules, and / or one or more parameters indicating UE configuration information for the UE 1. The information can include information for configuring a UE or group of UEs (e.g., including the UE 1) to perform a measurement to obtain and report a CLI value. The policy rules can include instructions for the RAN node 1 and / or the UE 1 to compare a measured CLI value to a threshold value. For example, the UE 1 may be configured to or operable to determine whether a CLI value is above the threshold upon obtaining the CLI value. This is an example of an event trigger condition examined at the UE 1 instead of the RAN node 1. Various other example embodiments may configure a UE 1 to assist the RAN node 1 similarly with evaluating an event trigger condition, evaluating a policy condition, executing a policy action, and so on. If the CLI value satisfies the threshold value (e.g., exceeds, is greater than, is above), then the RAN node 1 can report excessive CLI to the RAN controller 1002.

[0168] At 1010, the RAN node 1 may transmit signaling to the UE 1 indicating one or more configurations. In some examples, the signaling can include RRC signaling. The configurations can include, but are not limited to, one or more TDD and / or SBFD configurations for communications (e.g., transmission and reception of signaling) according to a TDD communication scheme and / oran SBFD communication scheme, one or more SRS configurations, and / or one or more CLI reporting configurations. The configurations can include some or all of the configuration information from the subscription procedure signaling at 1008. For example, one or more parameters in the configuration signaling at 1010 are obtained from the subscription procedure signaling at 1008.

[0169] At 1012, the UE 1 receives one or more SRSs over the air (e.g., indicated by the dotted line). For example, a UE 2 may broadcast the SRSs, or any other reference signal type, over the air to one or more surrounding or nearby devices, including the UE 1.

[0170] At 1014, the UE 1 measure CLI. At 1016, the UE 1 transmits a CLI report. The UE 1 may measure and report the CLI according to the configuration signaling at 1010, as described with reference to Figure 8. 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 5. Example content of the CLI report may include the measurements as described with reference to Figure 5.

[0171] At 1018, the RAN node 1 may detect a trigger event. For example, the RAN node 1 may detect an event trigger based on measuring one or more CLI values and / or evaluating one or more CLI values reported by the UE 1. The POLICY service may be implemented to report an excessive CLI to a RAN controller 1002. The RAN controller 1002 and / or the RAN node 1004 may perform subscription procedure signaling that indicates one or more of for the RAN node 1004 to perform a measurement to obtain a CLI value, to indicate to a UE 1 to perform a measurement to obtain a CLI value and report the measurement to the RAN node 1 , to compare the CLI value to a threshold value, and if the CLI value is above the threshold, then report excessive CLI to the RAN controller 1002.

[0172] In some cases, at 1020, if the CLI satisfies a threshold value, then the RAN node 1 may determine to send a report indicating the CLI. In some other cases, at 1022, if the CLI fails to satisfy a threshold value, then the RAN node 1 may determine to perform no action (e.g., not to send the report) and / or a default action.

[0173] In some cases, at 1024, the RAN node 1 may transmit a report indicating CLI to the RAN controller 1002. The signaling indicating the CLI may be an example of CLI reporting, as described with reference to Figure 5. The CLI reporting may differ from a REPORT service CLIreporting in that the signaling format may be different (e.g., the format used in the subscription to indicate a policy rule for reporting an excessive CLI). Another difference may be a flexibility to combine a reporting policy rule with other policy rules (e.g., the RAN node 1 may report an excessive CLI).

[0174] In variations, a policy rule may be indicated to the RAN node 1 through one or more parameters, which are referred to as RAN parameters. Various RAN parameters may correspond to triggering events, conditions, actions, and so on. In some cases, a RAN parameter or a value associated with the RAN parameter may include a sequence of parameters or values associated with the parameters. Thus, a reference to a RAN parameter or the value of the RAN parameter that make an indication does not preclude realizations where a sequence of RAN parameters or the values of the RAN parameters make the indication. A first RAN parameter may indicate that the event trigger is receiving a CLI report from a UE 1 or a group of UEs. The CLI report is associated with the subscription, an SRS configured based on information conveyed by the subscription, a duplexing process (e.g., SBFD configuration and / or TDD configuration), or the like. In response, the RAN node 1 may detect an event trigger each time, or some of the times, that the RAN node 1 receives the CLI report. The CLI value may be an SRS-RSRP, CLI-RSSI, or the like. The first RAN parameter may indicate a reference signal (e.g., SRS) to obtain an SRS-RSRP or resources to obtain a CLI-RSSI. The first RAN parameter may further indicate how to obtain the CLI value, as described with reference to Figures 5 and 8.

[0175] A second RAN parameter may indicate that the event trigger condition is the CEI value exceeding a threshold. A third RAN parameter may indicate the threshold (e.g., an RSRP, RSSI, or the like). Additionally, or alternatively, the third RAN parameter may indicate to the RAN node 1 the threshold is preconfigured and / or defined, a configuration by the network and / or 0AM, an implementation, a condition of the cells provided by the RAN node 1 , or any combination thereof. A fourth RAN parameter may indicate the action of reporting a KPM to a RAN controller 1002. An identifier and / or address of the RAN controller 1002 may further be indicated to the RAN node 1. A fifth RAN parameter may indicate that the KPM is the CEI value obtain earlier (e.g., an SRS-RSRP, CLI-RSSI, or the like). Additionally, or alternatively, the fifth RAN parameter may indicate for the RAN node 1 to obtain the KPM based on the CLI value (e.g., through a conversion of units, applying an additive and / or multiplicative factor, or the like). The content of the CLI report isdescribed with reference to Figures 5 and 8. A sixth RAN parameter may indicate at least one of a default action or no action if the policy condition is not satisfied. A seventh RAN parameter may indicate one or multiple UE identifiers or UE group identifiers to which the policy rule is to apply. If no UE identifiers or UE group identifiers are indicated, the policy rule may apply to any or all UEs served by the RAN node 1, as preconfigured or defined, configured by the network and / or OAM, indicated by other signaling, and / or determined according to an implementation.

[0176] Figure 11 illustrates an example of signaling diagram 1100 in accordance with aspects of the present disclosure. In some examples, the signaling diagram 1100 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, the signaling diagram 700, the signaling diagram 800, the signaling diagram 900, and / or the signaling diagram 1000. The signaling diagram 1100 may illustrate an example of a policy procedure for inter-UE CLI measurement and reporting between a RAN controller 1102, a RAN node 1104, and a UE 104. The RAN controller 1102, the RAN node 1104, and the UE 104 may be examples of corresponding devices (e.g., a CN 106, a RAN node 202, 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.

[0177] In practical scenarios in a cellular network, a RAN node 1104 and / or a UE 104 experiencing CLI in an interference scenario may also be causing CLI due to reciprocity of the wireless channel. Therefore, the subscription procedure between the RAN controller 1102 and the RAN node 1104 may include policy rules for managing interference as both the device (e.g., RAN node 1104 and / or UE 104) causing the interference and experiencing the interference, including reporting excessive interference, and reducing a transmission power and / or constraining transmission and / or reception resources or beams. However, for simplicity, example embodiments are presented separately for a RAN node 1 serving a UE 1 , which is a UE experiencing CLI in a CLI scenario, and a RAN node 2 serving a UE 2, which is a UE causing the CLI.

[0178] In some examples, at 1106, a control entity (e.g., an RIC), which may additionally, or alternatively, be referred to as a RAN controller 1102, may perform initial processes. The initialprocesses may be for a subscription procedure, including exchanging signaling related to the subscription procedure. The subscription procedure may include subscription information that includes parameters for monitoring and / or controlling one or more processes at a RAN node 1 and / or at a UE 1, including, but not limited to, UE-to-UE CLI management processes.

[0179] At 1108, the RAN controller 1102 and the RAN node 1 may exchange one or more messages for a subscription procedure with a type of POLICY, as described with reference to Figures 6 and 7. For example, the signaling can include a parameter indicating an action type of POLICY, one or more parameters indicating policy rules, and / or one or more parameters indicating UE configuration information for the UE 1. The information can include information for configuring a UE or group of UEs (e.g., including the UE 1) to perform a measurement to obtain and report a CLI value. The policy rules can include instructions for the RAN node 1 and / or the UE 1 to compare a measured CLI value to a threshold value. For example, the UE 1 may be configured to or operable to determine whether a CLI value is above the threshold upon obtaining the CLI value. This is an example of an event trigger condition examined at the UE 1 instead of the RAN node 1. Various other example embodiments may configure a UE 1 to assist the RAN node 1 similarly with evaluating an event trigger condition, evaluating a policy condition, executing a policy action, and so on. If the CLI value satisfies the threshold value (e.g., exceeds, is greater than, is above), then the RAN node 1 can report excessive CLI to the RAN controller 1102.

[0180] At 1110, the RAN node 1 may transmit signaling to the UE 1 indicating one or more configurations. In some examples, the signaling can include RRC signaling. The configurations can include, but are not limited to, one or more TDD and / or SBFD configurations for communications (e.g., transmission and reception of signaling) according to a TDD communication scheme and / or an SBFD communication scheme, one or more SRS configurations, and / or one or more CLI reporting configurations. The configurations can include some or all of the configuration information from the subscription procedure signaling at 1108. For example, one or more parameters in the configuration signaling at 1110 are obtained from the subscription procedure signaling at 1108.

[0181] At 1112, the UE 1 receives one or more SRSs over the air (e.g., indicated by the dotted line). For example, a UE 2 may broadcast the SRSs, or any other reference signal type, over the air to one or more surrounding or nearby devices, including the UE 1.

[0182] At 1114, the UE 1 measure CLI. At 1116, the UE 1 transmits a CLI report. The UE 1 may measure and report the CLI according to the configuration signaling at 1110, as described with reference to Figure 8. 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 5. Example content of the CLI report may include the measurements as described with reference to Figure 5.

[0183] At 1118, the RAN node 1 may detect a trigger event. For example, the RAN node 1 may detect an event trigger based on measuring one or more CLI values and / or evaluating one or more CLI values reported by the UE 1. The POLICY service may be implemented to report an excessive CLI to a RAN node 2. The RAN controller 1102 and / or the RAN node 1 may perform subscription procedure signaling that indicates one or more of for the RAN node 1 to perform a measurement to obtain a CLI value, to indicate to a UE 1 to perform a measurement to obtain a CLI value and report the measurement to the RAN node 1 , to compare the CLI value to a threshold value, and if the CLI value is above the threshold, then report excessive CLI to the RAN node 2.

[0184] In some cases, at 1120, if the CLI satisfies a threshold value, then the RAN node 1 may determine to send a report indicating the CLI. In some other cases, at 1122, if the CLI fails to satisfy a threshold value, then the RAN node 1 may determine to perform no action (e.g., not to send the report) and / or a default action.

[0185] In some cases, at 1124, the RAN node 1 may transmit a report indicating CLI to the RAN node 2. The signaling indicating the CLI may be an example of CLI reporting, as described with reference to Figure 5. The CLI reporting may differ from a REPORT service CLI reporting in that the signaling format may be different (e.g., the format used in the subscription to indicate a policy rule for reporting an excessive CLI). Another difference may be a flexibility to combine a reporting policy rule with other policy rules (e.g., the RAN node 1 may report an excessive CLI).

[0186] A first RAN parameter may indicate that the event trigger is receiving a CLI report from a UE 1 or a group of UEs. The CLI report is associated with the subscription, an SRS configured based on information conveyed by the subscription, a duplexing process (e.g., SBFD configuration and / or TDD configuration), or the like. In response, the RAN node 1 may detect an event trigger each time, or some of the times, that the RAN node 1 receives the CLI report. The CLI value may be an SRS-RSRP, CLI-RSSI, or the like. The first RAN parameter may indicate a reference signal(e.g., SRS) to obtain an SRS-RSRP or resources to obtain a CLI-RSSI. The first RAN parameter may further indicate how to obtain the CLI value, as described with reference to Figures 5 and 8. A second RAN parameter may indicate that the event trigger condition is the CLI value exceeding a threshold. A third RAN parameter may indicate the threshold (e.g., an RSRP, RSSI, or the like). Additionally, or alternatively, the third RAN parameter may indicate to the RAN node 1 the threshold is preconfigured and / or defined, a configuration by the network and / or OAM, an implementation, a condition of the cells provided by the RAN node 1 , or any combination thereof.

[0187] A fourth RAN parameter may indicate the action of reporting a KPM to one or more additional RAN nodes 1104, including the RAN node 2, and / or other network entities. An identifier and / or address of the RAN nodes 1104 and / or other network entities may further be indicated to the RAN node 1. In some examples, the fourth RAN parameter indicates one other RAN node 1104 (e.g., the RAN node 2) via an identifier and / or address associated with the RAN node 1104. The RAN node 1104 may be associated with the reference signal (e.g., SRS) measured to obtain the CLI value. In some other examples, multiple RAN nodes 1104 may be indicated via a sequence of identifiers and / or addresses associated with the RAN nodes 1104 or a group identifier and / or address associated with the group of RAN nodes 1104. In some other examples, another RAN or CN entity (e.g., an AMF) may be indicated via an identifier and / or address or associated with the RAN and / or CN entity.

[0188] A fifth RAN parameter may indicate that the KPM is the CLI value obtain earlier (e.g., an SRS-RSRP, CLI-RSSI, or the like). Additionally, or alternatively, the fifth RAN parameter may indicate for the RAN node 1 to obtain the KPM based on the CLI value (e.g., through a conversion of units, applying an additive and / or multiplicative factor, or the like). The content of the CLI report is described with reference to Figures 5 and 8. A sixth RAN parameter may indicate at least one of a default action or no action if the policy condition is not satisfied. A seventh RAN parameter may indicate one or multiple UE identifiers or UE group identifiers to which the policy rule is to apply. If no UE identifiers or UE group identifiers are indicated, the policy rule may apply to any or all UEs served by the RAN node 1, as preconfigured or defined, configured by the network and / or OAM, indicated by other signaling, and / or determined according to an implementation.

[0189] Figure 12 illustrates an example of signaling diagram 1200 in accordance with aspects of the present disclosure. In some examples, the signaling diagram 1200 may implement aspects ofthe 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, the signaling diagram 700, the signaling diagram 800, the signaling diagram 900, the signaling diagram 1000, and / or the signaling diagram 1100. The signaling diagram 1200 may illustrate an example of a policy procedure for inter-UE CLI measurement and reporting between a RAN controller 1202, one or more RAN nodes 1204, and a UE 104. The RAN controller 1202, the RAN nodes 1204, and the UE 104 may be examples of corresponding devices (e.g., a CN 106, a RAN node 202, 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.

[0190] In practical scenarios in a cellular network, a RAN node 1204 and / or a UE 104 experiencing CLI in an interference scenario may also be causing CLI due to reciprocity of the wireless channel. Therefore, the subscription procedure between the RAN controller 1202 and the RAN node 1204 may include policy rules for managing interference as both the device (e.g., RAN node 1204 and / or UE 104) causing the interference and experiencing the interference, including reporting excessive interference, and reducing a transmission power and / or constraining transmission and / or reception resources or beams. However, for simplicity, example embodiments are presented separately for a RAN node 1 serving a UE 1 , which is a UE experiencing CLI in a CLI scenario, and a RAN node 2 serving a UE 2, which is a UE causing the CLI.

[0191] In some examples, at 1206, a control entity (e.g., an RIC), which may additionally, or alternatively, be referred to as a RAN controller 1202, 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 subscription information that includes parameters for monitoring and / or controlling one or more processes at a RAN node 2 and / or at a UE 2, including, but not limited to, UE-to-UE CLI management processes.

[0192] At 1208, the RAN controller 1202 and the RAN node 2 may exchange one or more messages for a subscription procedure with a type of POLICY, as described with reference to Figures 6 and 7. For example, a RAN controller 1202 and a RAN node 2 perform a subscription procedure signaling that indicates for the RAN node 2 to receive an indication of excessive CLIfrom a RAN controller 1202, another RAN node 1204 (e.g., the RAN node 1), or both. Additionally, or alternatively, the subscription procedure indicates for the RAN node 2 to determine a value of excess CLI. Additionally, or alternatively, the subscription procedure indicates for the RAN node 2 to take an action to mitigate the CLI based on the excess CLI value (e.g., indicate to the UE 2 to reduce the transmission power associated with a signal or channel that causes the CLI, constrain the use of a set of UE resources associated with the CLI, and / or constrain the use of one or multiple UE beams that cause the CLI).

[0193] At 1210, the RAN node 2 may transmit signaling to the UE 2 indicating one or more configurations. In some examples, the signaling can include RRC signaling. The configurations can include, but are not limited to, one or more TDD and / or SBFD configurations for communications (e.g., transmission and reception of signaling) according to a TDD communication scheme and / or an SBFD communication scheme and / or one or more SRS configurations.

[0194] At 1212, the UE 2 transmits one or more SRSs over the air (e.g., indicated by the dotted line) to a RAN node 2, a RAN controller 1202, a RAN node 1, and / or a 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, including a UE 1.

[0195] In some examples, the RAN controller 1202 performs subscription procedure signaling with a RAN node 1 (e.g., the RAN node experiencing the CLI) and a RAN node 2 (e.g., the RAN node causing the CLI). For example, the RAN controller 1202 and the RAN node 1 perform subscription procedure signaling, as described with reference to Figures 5 and 6. Additionally, or alternatively, the RAN controller 1202 and the RAN node 2 perform subscription procedure signaling. In some examples, the RAN node 1 detects an excessive CLI and reports the excessive CLI to the RAN controller 1202 (e.g., as part of a REPORT subscription procedure, as part of a POLICY subscription procedure, as described with reference to Figures 6 through 11, and / or in other CLI reporting signaling).

[0196] In some examples, at 1214, the RAN controller 1202 may report an excessive CLI to the RAN node 2. For example, the RAN node 1 can report a CLI measurement with an excessive CLI value (e.g., a CLI value that exceeds a threshold value) to the RAN controller 1202, as described with reference to Figure 10, and the RAN controller 1202 can report the excessive CLI to the RANnode 2. In some other examples, the RAN controller 1202 performs subscription procedure signaling with a RAN node 2 and a RAN node 1. The RAN controller 1202 and the RAN node 1 perform subscription procedure signaling, as described with reference to Figures 5 and 6. The RAN controller 1202 and the RAN node 2 perform subscription procedure signaling. The RAN node 1 detects an excessive CLI and reports the excessive CLI to the RAN node 2. For example, at 1212, the RAN node 1 transmits a report to the RAN node 2 indicating one or more CLI values. For example, the report indicates to the RAN node 2 that an excessive CLI is detected. That is, the RAN node 1 can report a CLI measurement with an excessive CLI value (e.g., a CLI value that exceeds a threshold value) directly to the RAN node 2, as described with reference to Figure 11. In some cases, the reporting of an excessive CLI value satisfies a trigger event. In response, the RAN node 2 determines whether to take a CLI mitigation action.

[0197] Combining the policy-based subscriptions with other subscriptions (e.g., REPORT, INSERT, CONTROL, QUERY, etc.) are not precluded. For example, the subscription with the RAN node 2 may be realized through REPORT or INSERT services. Similarly, the subscription with the RAN node 1 may be realized through a CONTROL service.

[0198] In some examples, the subscription procedure signaling at 1208 includes one or more RAN parameters. For example, the subscription procedure signaling may include a first RAN parameter with a value that indicates that the event trigger is receiving a message indicating an excessive CLI. The message may include a CLI value of an excess CLI value (e.g., an SRS-RSRP, CLLRSSI, or the like). The first RAN parameter may indicate a reference signal (e.g., SRS) from which an RSRP (e.g., SRS-RSRP) is obtained or resources from which an RSSI (e.g., CLLRSSI) is obtained.

[0199] Additionally, or alternatively, the subscription procedure signaling may include a second RAN parameter with a value that indicates a threshold value by which the RAN node 2 may determine a value of excess CLI. The threshold may be an RSRP threshold value, an RSSI threshold value, or the like. Additionally, or alternatively, a value for the threshold may be preconfigured or defined, configured by the network and / or 0AM, indicated by a signaling, determined by an implementation, or any combination thereof. The RAN node 2 may use the value of the threshold to determine whether the reported CLI is above the threshold. Additionally, or alternatively, signaling from the RAN node 1 and / or the RAN controller 1202 at 1214 and 1216, respectively, may indicatea value of excess CLI explicitly, in which case the RAN node 2 may not compare the CLI value to a threshold value to determine whether the CLI is excessive. That is, the report indicating CLI at 1214 and 1216 may include an indication of an amount of CLI that exceeds a threshold value and / or any other explicit indication that the CLI value exceeds and / or satisfies a threshold value.

[0200] Additionally, or alternatively, the subscription procedure signaling may include a third RAN parameter with a value that indicates one or more CLI mitigation actions (e.g., indicating to the UE 2 to reduce a transmission power or constraining communications on beam or resources of the UE 2). Additionally, or alternatively, the subscription procedure signaling may include a fourth RAN parameter with a value that indicates a timing for applying one or more changes (e.g., taking the CLI mitigation actions). Additionally, or alternatively, the subscription procedure signaling may include a fifth RAN parameter, or an additional policy rule, with a value that indicates whether and how the CLI mitigation actions may be reversed at a later time. Additionally, or alternatively, the subscription procedure signaling may include a sixth RAN parameter with a value that indicate a default action or no action if the policy condition is not satisfied. Additionally, or alternatively, the subscription procedure signaling may include a seventh RAN parameter that indicates one or more UE identifiers or UE group identifiers to which the policy rule is to apply. If no UE identifiers or UE group identifiers are indicated, the policy rule may apply to any or all UEs served by the RAN node 2, as preconfigured or defined, configured by the network and / or 0AM, indicated by other signaling, and / or determined according to an implementation.

[0201] In some examples, a policy rule for CLI management may indicate to the RAN node 2 to perform an action for managing CLI by setting or modifying parameters that may affect the CLI. For example, the policy rule may indicate to the RAN node 2 that the CLI can be mitigated by reducing an uplink transmission power associated with a UE 104 or a group of UEs 104 served by the RAN node 2 (e.g., including the UE 2). In some cases, the report indicating CLI may include an amount of excess CLI, for example X dB. In response, the RAN node 2 may indicate to the UEs 104 to reduce the transmission power for uplink signals and / or channels by X dB. The RAN node 2 may respond by transmitting a message to the RAN controller 1212 and / or to the RAN node 1 including an indication that the RAN node 2 and / or the UEs 104 reduced the transmission power and / or the signals or channels on which the transmission power reduction is applied.

[0202] In some other examples, the report indicating CLI may include an amount of excess CLI (e.g., X dB). In response, the RAN node 2 may indicate to the UEs 104 to reduce the 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 message to the RAN controller 1212 and / or to the RAN node 1 including an indication of the amount Y dB by which the RAN node 2 and / or the UEs 104 reduced the transmission power and / or the signals or channels on which the transmission power reduction is applied.

[0203] 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 through the subscription procedure signaling (e.g., as a parameter in subscription information). Then, the RAN node 2 may indicate to the UEs 104 to reduce the transmission power by X dB on all or some signals and / or channels. 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 104 to reduce the transmission power by X[i] dB or 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 104 upon applying an associated policy rule.

[0204] In some cases, the RAN node 2 may determine that the CLI can be mitigated by avoiding or refraining from communicating using one or more communication resources and / or beams associated with a UE 104 or group of UEs 104 (e.g., including the UE 2). In some examples, the RAN node 2 may avoid or refrain from communicating with the UEs 104 on the resources or a subset of the resources. In some other examples, the RAN node 2 may avoid or refrain from communicating with the UEs 104 on the beams or a subset of the beams. The RAN node 2 may respond by sending a message to the RAN controller 1202 and / or the RAN node 1 including an indication that communication on the resources and / or beams, or the subset of the resources and / or beams, are constrained. In some cases, the communication resources include 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.

[0205] In variations, the RAN node 2 may determine that the CLI can be mitigated by any combination of the examples described herein (e.g., a transmission power reduction on one or more beams, a transmission power reduction on one or more resources in time and / or frequency domains, a transmission power reduction on one or more beams and / or one or more resources). For example, the RAN node 2 may detect event trigger based on receiving the report indicating the CLI (e.g., from the RAN controller 1202 and / or from the RAN node 1). At 1218, if the reported CLI satisfies a threshold value, then the RAN node 2 may determine an amount of excessive CLI. That is, the RAN node 2 may determine a difference between a CLI value reported at 1214 and / or at 1216 and a threshold value. At 1220, the RAN node 2 may determine one or more transmission parameters to update (e.g., a transmission power reduction on one or more beams associated with a UE 2, a transmission power reduction on one or more resources in time and / or frequency domains associated with a UE 2, a transmission power reduction on one or more beams and / or one or more resources associated with a UE 2). In some other cases, at 1222, if the RAN node 2 determines the CLI value fails to satisfy the threshold value (e.g., is below the threshold value and / or does not exceed the threshold value), then the RAN node 2 may determine no action and / or a default action. In some examples, no action and / or the default action may include maintaining (e.g., not updating and / or modifying) one or more communication parameters at the UE 2 and / or the RAN node 2, such as maintaining a transmission power for a transmission.

[0206] In some cases, when the RAN node 2 receives the report indicating CLI at 1214 and / or at 1216, the RAN node 2 may follow 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 apply the changes without a delay after (e.g., immediately after) receiving and processing the report indicating CLI. The RAN node 2 may reserve a duration for processing the report indicating CLI. In some other examples, the RAN node 2 may apply the changes after a duration, T, from a time of receiving or processing the report indicating CLI. The RAN node 2 may indicate for one or more UEs 104 to reduce a transmission power or constrain communications with the UEs 104 on one or more beams or resources (e.g., refrain from using) after the duration T, providing for the RAN node 2 to perform and complete any communications that were scheduled or configured prior to receiving and processing the report indicating CLI. The RAN node 2 may, or may not, 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 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 report indicating CLI indicates to the RAN node 2 to override the applied changes. Additionally, or alternatively, in some examples, the RAN node 2 may 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.

[0207] In some examples, such as to reduce, or prevent, the underutilization of communication resources, a RAN node 2 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 2 and / or a UE 2 may not know when to revert to an original transmission power or use of beams or resources. The RAN node 2 may reverse a transmission power reduction, fully or partially, if the RAN node 2 does not receive control signaling for a duration. In some examples, the RAN node 2 may increase the transmission power of one or more UEs 104 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 one or more UEs 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.

[0208] In variations, the RAN node 2 may reverse a constraint on using beams or resources with UEs 104, fully or partially, if the RAN node 2 does not receive control signaling that indicates an excessive CLI 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 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 in association with one or more UEs 104 may be interpreted as reducing the transmission power of the UEs 104 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 increasing the transmission power on the beam or resource. The RAN node 2 may repeat the process of gradually increasing the transmission power 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.

[0209] In some examples, a capability of the RAN node 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 is 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 and / or 0AM, 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 1202. Lor example, if the RAN controller 1202 does not receive an excess CLI report from the RAN node 1 for a duration, then the RAN controller 1202may 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 at one or more UEs 104, use a constrained beam or resource with one or more UEs 104, or both.

[0210] At 1224, the RAN node 2 and / or the UE 2 may execute the action. For example, the RAN node 2 may execute an action and / or may instruct a UE 2 to execute an action via signaling based on the policy rule based on the determination at 1220 (e.g., if the trigger event condition is satisfied and the condition is satisfied). For example, the RAN node 2 and / or the UE 2 may reduce a transmission power for wireless communications, refrain from using (e.g., constrain) one or more time-frequency resources for the wireless communications, or refraining from using a beam for the wireless communications. Additionally, or alternatively, the RAN node 2 may execute no action and / or a default action based on the condition not being satisfied and / or based on the trigger event condition not being satisfied.

[0211] Figure 13 illustrates an example of signaling diagram 1300 in accordance with aspects of the present disclosure. In some examples, the signaling diagram 1300 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, the signaling diagram 700, the signaling diagram 800, the signaling diagram 900, the signaling diagram 1000, the signaling diagram 1100, and / or the signaling diagram 1200. The signaling diagram 1300 may illustrate an example of a policy procedure for inter-UE CLI measurement and reporting between a RAN controller 1302, a RAN node 1304, and a UE 104. The RAN controller 1302, the RAN node 1304, and the UE 104 may be examples of corresponding devices (e.g., a CN 106, a RAN node 202, 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.

[0212] In practical scenarios in a cellular network, a RAN node 1304 and / or a UE 104 experiencing CLI in an interference scenario may also be causing CLI due to reciprocity of the wireless channel. Therefore, the subscription procedure between the RAN controller 1302 and the RAN node 1304 may include policy rules for managing interference as both the device (e.g., RAN node 1304 and / or UE 104) causing the interference and experiencing the interference, includingreporting excessive interference, and reducing a transmission power and / or constraining transmission and / or reception resources or beams. However, for simplicity, example embodiments are presented separately for a RAN node 1 serving a UE 1 , which is a UE experiencing CLI in a CLI scenario, and a RAN node 2 serving a UE 2, which is a UE causing the CLI.

[0213] In some examples, at 1306, a control entity (e.g., an RIC), which may additionally, or alternatively, be referred to as a RAN controller 1302, 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 subscription information that includes parameters for monitoring and / or controlling one or more processes at a RAN node 1 and / or at a UE 1, including, but not limited to, UE-to-UE CLI management processes.

[0214] At 1308, the RAN controller 1302 and the RAN node 1 may exchange one or more messages for a subscription procedure with a type of POLICY, as described with reference to Figures 6 and 7. For example, the signaling can include a parameter indicating an action type of POLICY, one or more parameters indicating policy rules, and / or one or more parameters indicating UE configuration information for the UE 1.

[0215] In some examples, the subscription procedure signaling indicates information to the RAN node 1 to configure a UE 1 or a group of UEs 104 to perform a measurement to obtain a CLI value, determine whether the CLI value exceeds a threshold value, and, if the CLI does exceed the threshold value, then configure the UE 1 to transmit a designated reference signal as an indication of excessive CLI, or increase the power of a designated reference signal by the amount of the excess CLI. In variations, the designated reference signal is different from the SRS transmitted by a UE 104 causing interference (e.g., a UE 2). The designated reference signal indicates an excessive CLI to RAN nodes 1304 or UEs 104 within a geographic location and over the air. In some other examples, the subscription procedure signaling indicates to the RAN node 1 to configure a UE 1 or a group of UEs 104 to perform a measurement to obtain and report a CLI value, to determine whether the CLI value exceeds a threshold value, and, if the CLI does exceed the threshold value, then for the RAN node 1 transmit a designated reference signal as an indication of excessive CLI, or increase the power of a designated reference signal by the amount of the excess CLI. The reference signal transmitted by the RAN node 1 may be a CSI-RS, an SSB, an NCD-SSB, a RIM-RS, or thelike. The designated reference signal indicates an excessive CLI to RAN nodes 1304 or UEs 104 within a geographic location and over the air.

[0216] In some examples, the subscription procedure signaling may indicate one or more RAN parameters. For example, the subscription procedure signaling may include a first RAN parameter with a value that indicates that the event trigger is receiving a CLI report including a CLI value from one or more UEs 104 (e.g., the UE 1) and / or obtaining a CLI value through a measurement. The CLI report is associated with the subscription, an SRS configured based on information conveyed by the subscription, a duplexing process, or the like. In response, the UEs 104 and / or the RAN node 1 may detect an event trigger every time, or some of the times, that RAN node 1 obtains a CLI measurement. The CLI value may be an SRS-RSRP, a CLI-RSSI, or the like. The first RAN parameter may indicate a reference signal (e.g., SRS) to obtain an SRS-RSRP or resources to obtain a CLI-RSSI. The first RAN parameter may further indicate how to obtain the CLI value.Additionally, or alternatively, the first RAN parameter or an additional RAN parameter may further indicate whether the measurement is performed by the UEs 104 or the RAN node 1.

[0217] Additionally, or alternatively the subscription procedure signaling may include a second RAN parameter with a value that indicates that the event trigger condition is the CLI value exceeding a threshold value. Additionally, or alternatively the subscription procedure signaling may include a third RAN parameter with a value that indicates the threshold value (e.g., an RSRP threshold value, an RSSI threshold value, or the like). Additionally, or alternatively, the third RAN parameter may indicate to the RAN node 1 to obtain the threshold value based on a preconfigured or defined value, a configuration by the network and / 0AM, an implementation, a condition of the cells provided by a RAN node 1304, a channel state associated with a channel with the UE 1 or the group of UEs 104, or any combination thereof.

[0218] Additionally, or alternatively the subscription procedure signaling may include a fourth RAN parameter with a value that indicates the action of transmitting (e.g., broadcasting) a second, designated reference signal that indicates to one or more other RAN nodes 1304 and / or UEs 104 in the vicinity that an excessive CLI has been detected. The second reference signal may be associated with the reference signal or resources used to measure the CLI. Additionally, or alternatively, the fourth RAN parameter may indicate the action of changing the transmission power of the second reference signal. The amount by which the transmission power is increased may be identical to(e.g., or otherwise obtained based on) the value by which the measured CLI value exceeds the threshold. For example, if the RAN node 1 and / or the UE 1 detects that the CLI value is above the threshold by X dB, then the RAN node 1 and / or the UE 1 may determine to increase the transmission power of the second reference signal by X dB. Since the UE 1 and / or the RAN node 1 is indicated to transmit the second reference signal or increase a transmission power upon detecting an excessive CLI, the RAN node 1 and / or the UE 1 may implement techniques to reverse the action once the measured CLI is not detected excessive according to a later measurement (e.g., the RAN node 1 may stop or terminate transmission of the second reference signal or reduces a transmission power). The reversal of the action may be preconfigured or defined, configured by the network and / or OAM, indicated by a signaling, determined by an implementation, or any combination thereof. Additionally, or alternatively, the reversal of the action may be indicated via an additional policy or additional RAN parameters within a same policy.

[0219] Additionally, or alternatively the subscription procedure signaling may include a fifth RAN parameter with a value that indicates the action of not transmitting (e.g., broadcasting) the second reference signal or decreasing a transmission power if the CLI value does not exceed the threshold. This may indicate to one or more other RAN nodes in the vicinity that an associated CLI is not excessive. The amount by which the transmission power is decreased may be set to a default value or the value of the transmission power prior to an earlier increase in accordance with the policy action. Lor example, if the UE 1 and / or the RAN node 1 has increased the transmission power of the second reference signal by X dB earlier in accordance with the policy action, then the RAN node 1 and / or the UE 1 may decrease the current transmission power of the second reference signal by X dB, such that it is restored to its previous or default value. Additionally, or alternatively the subscription procedure signaling may include a sixth RAN parameter with a value that indicates a default action or no action if the policy condition is not satisfied. A seventh RAN parameter may indicate one or multiple UE identifiers or UE group identifiers to which the policy rule is to apply. If no UE identifiers or UE group identifiers are indicated, the policy rule may apply to any or all UEs served by the RAN node 1, as preconfigured or defined, configured by the network and / or OAM, indicated by other signaling, and / or determined according to an implementation.

[0220] At 1310, the RAN node 1 may transmit signaling to the UE 1 indicating one or more configurations. In some examples, the signaling can include RRC signaling. The configurations caninclude, but are not limited to, one or more TDD and / or SBFD configurations for communications (e.g., transmission and reception of signaling) according to a TDD communication scheme and / or an SBFD communication scheme, one or more SRS configurations, one or more CLI reporting configurations, and / or one or more reference signal configurations. The configurations can include some or all of the configuration information from the subscription procedure signaling at 1308. For example, one or more parameters in the configuration signaling at 1310 are obtained from the subscription procedure signaling at 1308.

[0221] At 1312, the UE 1 receives one or more SRSs over the air (e.g., indicated by the dotted line). For example, a UE 2 may broadcast the SRSs, or any other reference signal type, over the air to one or more surrounding or nearby devices, including the UE 1.

[0222] At 1314, the UE 1 and / or the RAN node 1 detects a CLI measurement event trigger. For example, the UE 1 and / or the RAN node 1 can measure CLI based on the SRSs or other signaling.The UE 1 can transmits a CLI report to the RAN node 1. The UE 1 may measure and report the CLI according to the configuration signaling at 1310, as described with reference to Figure 8. The RAN node 1 can detect an event trigger based on measuring one or more CLI values and / or evaluating one or more CLI values reported by the UE 1.

[0223] In some cases, at 1316, if the CLI satisfies a threshold value, then the RAN node 1 may determine to transmit a reference signal, indicate for the UE 1 to transmit a reference signal, increase a transmission power of a reference signal, and / or indicate for the UE 1 to increase a transmission power of a reference signal. In some other cases, at 1318, if the CLI fails to satisfy a threshold value, then the RAN node 1 and / or the UE 1 may determine to perform no action (e.g., maintain a transmission power of a reference signal) and / or a default action.

[0224] In some cases, at 1320, the UE 1 may transmit a reference signal and / or may increase a transmission power of a reference signal according to the determination at 1316. In some other cases, at 1322, the RAN node 1 may transmit a reference signal and / or may increase a transmission power of a reference signal according to the determination at 1316.

[0225] Figure 14 illustrates an example of signaling diagram 1400 in accordance with aspects of the present disclosure. In some examples, the signaling diagram 1400 may implement aspects of the wireless communications system 100, the wireless communications system 200, the RANarchitecture diagram 300, the RAN layer diagram 400, the signaling diagram 500, the signaling diagram 600, the signaling diagram 700, the signaling diagram 800, the signaling diagram 900, the signaling diagram 1000, the signaling diagram 1100, the signaling diagram 1200, and / or the signaling diagram 1300. The signaling diagram 1400 may illustrate an example of a policy procedure for inter-UE CLI measurement and reporting between a RAN controller 1402, a RAN node 1404, and a UE 104. The RAN controller 1402, the RAN node 1404, and the UE 104 may be examples of corresponding devices (e.g., a CN 106, a RAN node 202, 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.

[0226] In practical scenarios in a cellular network, a RAN node 1404 and / or a UE 104 experiencing CLI in an interference scenario may also be causing CLI due to reciprocity of the wireless channel. Therefore, the subscription procedure between the RAN controller 1402 and the RAN node 1404 may include policy rules for managing interference as both the device (e.g., RAN node 1404 and / or UE 104) causing the interference and experiencing the interference, including reporting excessive interference, and reducing a transmission power and / or constraining transmission and / or reception resources or beams. However, for simplicity, example embodiments are presented separately for a RAN node 1 serving a UE 1 , which is a UE experiencing CLI in a CLI scenario, and a RAN node 2 serving a UE 2, which is a UE causing the CLI.

[0227] In some examples, at 1406, a control entity (e.g., an RIC), which may additionally, or alternatively, be referred to as a RAN controller 1402, 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 subscription information that includes parameters for monitoring and / or controlling one or more processes at a RAN node 2 and / or at a UE 2, including, but not limited to, UE-to-UE CLI management processes.

[0228] At 1408, the RAN controller 1402 and the RAN node 2 may exchange one or more messages for a subscription procedure with a type of POLICY, as described with reference to Figures 6 and 7. For example, the signaling can include a parameter indicating an action type ofPOLICY, one or more parameters indicating policy rules, and / or one or more parameters indicating UE configuration information for the UE 2.

[0229] In some examples, the subscription procedure signaling indicates information to the RAN node 2 to configure a UE 2 or a group of UEs 104 to perform a measurement on a designated reference signal and obtain an RSRP value, determine whether the RSRP value exceeds a threshold value, and, if the RSRP does exceed the threshold value, then report the excess RSRP to the RAN node 2 and / or take a CLI mitigation action (e.g., reduce a transmission power by the amount of the excess RSRP, constrain communications on a resource, and / or constrain the use of a beam). In variations, the designated reference signal is different from the SRS transmitted by a UE 104 causing interference (e.g., a UE 2). The designated reference signal indicates an excessive CLI to RAN nodes 1404 or UEs 104 within a geographic location and over the air. In some other examples, the subscription procedure signaling indicates to the RAN node 2 to perform a measurement to obtain a RSRP value, determine whether the RSRP value exceeds a threshold value, and, if the RSRP does exceed the threshold value, then for the RAN node 2 performs a CLI mitigation action (e.g., indicate to a UE 2 or a group of UEs 104 to reduce a transmission power by the amount of the excess RSRP, constrain communications on a UE resource, and / or constrain the use of a UE beam). The reference signal may be a CSLRS, an SSB, an NCD-SSB, a RIM-RS, or the like. The designated reference signal indicates an excessive CLI to RAN nodes 1404 or UEs 104 within a geographic location and over the air.

[0230] In some cases, the RAN controller 1402 performs subscription procedure signaling with a RAN node 1 and a RAN node 2. The RAN controller 1402 and the RAN node 1 perform subscription procedure signaling, as described with reference to Figure 13. The RAN controller 1402 and the RAN node 2 perform subscription procedure signaling at 1408. The victim UE 1 or the RAN node 1 detects an excessive CLI and transmits the reference signal or increases a transmission power for a reference signal. The UE 2 or the RAN node 2 measures an RSRP on the reference signal from the UE 1 or the RAN node 1 and detects that the RSRP value exceeds a threshold. In response, the UE 2 or the aggressor RAN node 2 takes a CLI mitigation action.

[0231] In some examples, the subscription procedure signaling may indicate one or more RAN parameters. For example, the subscription procedure signaling may include a first RAN parameter with a value that indicates that the event trigger is detecting that an RSRP (e.g., CSLRSRP, SSB-RSRP, SRS-RSRP, and / or RIM-RSRP) exceeds a threshold. The first RAN parameter or an additional RAN parameter may further indicate whether the measurement and / or comparison is performed by a UE 104 or a RAN node 1404. Additionally, or alternatively, the subscription procedure signaling may include a second RAN parameter with a value that indicates the threshold value for the RSRP value. Additionally, or alternatively, a value for the threshold may be preconfigured or defined, configured by the network and / or 0AM, indicated by a signaling, determined by an implementation, or any combination thereof. The RAN node 1404 may use the value of the threshold to determine whether the reported CLI is above the threshold.

[0232] Additionally, or alternatively, the subscription procedure signaling may include a third RAN parameter with a value that indicates one or more CLI mitigation actions (e.g., reducing a transmission power or constraining communications on beam or resources, as described with reference to Figure 12). Additionally, or alternatively, the subscription procedure signaling may include a fourth RAN parameter with a value that indicates a timing for applying the changes (e.g., taking the CLI mitigation actions, as described with reference to Figure 12). Additionally, or alternatively, the subscription procedure signaling may include a fifth RAN parameter, or an additional policy rule, with a value that indicates whether and how the CLI mitigation actions may be reversed at a later time, as described with reference to Figure 12. Additionally, or alternatively, the subscription procedure signaling may include a sixth RAN parameter with a value that indicates a default action or no action if the policy condition is not satisfied. The RAN node 1204 may perform one or more interference mitigation actions according to a timing for applying the changes and / or an automatic reversal of the mitigation actions, as described with reference to Figure 10. Additionally, or alternatively, the subscription procedure signaling may include a seventh RAN parameter that indicates one or more UE identifiers or UE group identifiers to which the policy rule is to apply. If no UE identifiers or UE group identifiers are indicated, the policy rule may apply to any or all UEs served by the RAN node 2, as preconfigured or defined, configured by the network and / or 0AM, indicated by other signaling, and / or determined according to an implementation.

[0233] At 1410, the RAN node 2 may transmit signaling to the UE 2 indicating one or more configurations. In some examples, the signaling can include RRC signaling. The configurations can include, but are not limited to, one or more TDD and / or SBFD configurations for communications(e.g., transmission and reception of signaling) according to a TDD communication scheme and / or an SBFD communication scheme and / or one or more SRS configurations.

[0234] At 1412, the UE 2 transmits one or more SRSs over the air (e.g., indicated by the dotted line) to a RAN node 2, a RAN controller 1402, a RAN node 1, and / or a 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, including a UE 1.

[0235] In some cases, at 1414, a UE 104 (e.g., the UE 1) and / or a RAN node 1404 (e.g., a RAN node 1) may transmit a reference signal and / or may increase a transmission power of a reference signal, as described with reference to Figure 13. At 1416, the UE 2 and / or the RAN node 2 detect an RSRP measurement event trigger. The RSRP measurement event trigger can include an RSRP measurement satisfying (e.g., exceeding, being greater than, being above) a threshold value.

[0236] In some examples, at 1418, if the RSPR value satisfies a threshold value, then the RAN node 2 and / or the UE 2 determines one or more communication parameters to update (e.g., a transmission power reduction on one or more beams, a transmission power reduction on one or more resources in time and / or frequency domains, a transmission power reduction on one or more beams and / or one or more resources). In some other cases, at 1420 if the RSRP value fails to satisfy the threshold value (e.g., is below the threshold value and / or does not exceed the threshold value), then the RAN node 2 and / or the UE 2 may determine no action and / or a default action. In some examples, no action and / or a default action may include maintaining (e.g., not updating and / or modifying) one or more communication parameters, such as maintaining a transmission power for a transmission.

[0237] At 1422, the RAN node 2 and / or the UE 2 may execute the action. For example, the RAN node 2 and / or the UE 2 may execute the action determined at 1418 or at 1420. In some cases, the RAN node 2 may determine that the CLI can be mitigated by avoiding or refraining from communicating using one or more communication resources and / or beams associated with a UE 104 or group of UEs 104 (e.g., including the UE 2). In some examples, the RAN node 2 may avoid or refrain from communicating with the UEs 104 on the resources or a subset of the resources. In some other examples, the RAN node 2 may avoid or refrain from communicating with the UEs 104 on the beams or a subset of the beams. The RAN node 2 may respond by sending a message to theRAN controller 1402 and / or the RAN node 1 including an indication that communication on the resources and / or beams, or the subset of the resources and / or beams, are constrained. In some cases, the communication resources include 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.

[0238] In variations, the RAN node 2 may determine that the CLI can be mitigated by any combination of the examples described herein (e.g., a transmission power reduction on one or more beams, a transmission power reduction on one or more resources in time and / or frequency domains, a transmission power reduction on one or more beams and / or one or more resources). For example, the RAN node 2 may detect event trigger based on receiving the report indicating the CLI (e.g., from the RAN controller 1402 and / or from the RAN node 1). At 1418, if the reported CLI satisfies a threshold value, then the RAN node 2 may determine an amount of excessive CLI. That is, the RAN node 2 may determine a difference between a CLI value reported at 1414 and / or at 1416 and a threshold value. At 1420, the RAN node 2 may determine one or more transmission parameters to update (e.g., a transmission power reduction on one or more beams associated with a UE 2, a transmission power reduction on one or more resources in time and / or frequency domains associated with a UE 2, a transmission power reduction on one or more beams and / or one or more resources associated with a UE 2). In some other cases, at 1422, if the RAN node 2 determines the CLI value fails to satisfy the threshold value (e.g., is below the threshold value and / or does not exceed the threshold value), then the RAN node 2 may determine no action and / or a default action. In some examples, no action and / or the default action may include maintaining (e.g., not updatingand / or modifying) one or more communication parameters at the UE 2 and / or the RAN node 2, such as maintaining a transmission power for a transmission.

[0239] In some cases, when the RAN node 2 receives the report indicating CLI at 1414 and / or at 1416, the RAN node 2 may follow 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 apply the changes without a delay after (e.g., immediately after) receiving and processing the report indicating CLI. The RAN node 2 may reserve a duration for processing the report indicating CLI. In some other examples, the RAN node 2 may apply the changes after a duration, T, from a time of receiving or processing the report indicating CLI. The RAN node 2 may indicate for one or more UEs 104 to reduce a transmission power or constrain communications with the UEs 104 on one or more beams or resources (e.g., refrain from using) after the duration T, providing for the RAN node 2 to perform and complete any communications that were scheduled or configured prior to receiving and processing the report indicating CLI. The RAN node 2 may, or may not, 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 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 report indicating CLI indicates to the RAN node 2 to override the applied changes. Additionally, or alternatively, in some examples, the RAN node 2 may 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.

[0240] In some examples, such as to reduce, or prevent, the underutilization of communication resources, a RAN node 2 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 2 and / or a UE 2 may not know when to revert to an original transmission power or use of beams or resources. The RAN node 2 may reverse a transmission power reduction, fully or partially, if the RAN node 2 does not receive control signaling for a duration. In some examples, the RAN node 2 may increase the transmission power of one or more UEs 104 by Y dB, where Y dB is an amount of transmission power reductionaccording 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 one or more UEs 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 additiveincrease 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.

[0241] In variations, the RAN node 2 may reverse a constraint on using beams or resources with UEs 104, fully or partially, if the RAN node 2 does not receive control signaling that indicates an excessive CLI 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 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 in association with one or more UEs 104 may be interpreted as reducing the transmission power of the UEs 104 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 increasing the transmission power on the beam or resource. The RAN node 2 may repeat the process of gradually increasing the transmission power 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.

[0242] In some examples, a capability of the RAN node 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 is capable ofperforming 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 and / or 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 1402. For example, if the RAN controller 1402 does not receive an excess CLI report from the RAN node 1 for a duration, then the RAN controller 1402 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 at one or more UEs 104, use a constrained beam or resource with one or more UEs 104, or both.

[0243] At 1424, the RAN node 2 and / or the UE 2 may execute the action. For example, the RAN node 2 may execute an action and / or may instruct a UE 2 to execute an action via signaling based on the policy rule based on the determination at 1420 (e.g., if the trigger event condition is satisfied and the condition is satisfied). For example, the RAN node 2 and / or the UE 2 may reduce a transmission power for wireless communications, refrain from using (e.g., constrain) one or more time-frequency resources for the wireless communications, or refraining from using a beam for the wireless communications. Additionally, or alternatively, the RAN node 2 may execute no action and / or a default action based on the condition not being satisfied and / or based on the trigger event condition not being satisfied.

[0244] In variations, a policy rule may include a set of parameters that convey the policy information, such as event triggers, event trigger conditions, policy conditions, policy actions, and so on. A parameter may be referred to as a RAN parameter, which may be indicated by a unique RAN parameter identifier. RAN parameter identifiers may be preconfigured an / or defined.However, when referring to a RAN parameter herein, a RAN parameter may include a sequence of RAN parameters, a of which possibly indicated by a RAN parameter identifier. The RAN parameter may be indicated by a sequence of RAN parameter identifiers.

[0245] In some examples, separate RAN parameter identifiers may indicate various types of CLI values (e.g., SRS-RSRP and / or CLLRSSI). Additionally, or alternatively, the RAN parameter indicating a type of CLI value may include a first RAN parameter indicating a CLI value and a second RAN parameter indicating a type (e.g., SRS-RSRP and / or CLLRSSI). In some other examples, separate RAN parameter identifiers may indicate various types of CLI thresholds (e.g.,SRS-RSRP and / or CLI-RSSI). Additionally, or alternatively, the RAN parameter indicating a type of CLI threshold may include a third RAN parameter indicating a CLI threshold and a fourth RAN parameter indicating a type (e.g., SRS-RSRP and / or CLI-RSSI). The fourth RAN parameter may take similar values as the second RAN parameter. This may lead to specifying a smaller number of RAN parameters, hence providing for more flexible implementation. In some other examples, separate RAN parameter identifiers may indicate various types of KPM for a CLI report (e.g., SRS- RSRP and / or CLI-RSSI). Additionally, or alternatively, the RAN parameter indicating a type of KPM may include a fifth RAN parameter indicating a KPM and a sixth RAN parameter indicating its type (e.g., SRS-RSRP and / or CLI-RSSI). Here, the fourth RAN parameter may take similar values as the second RAN parameter or the fourth RAN parameter in the previous examples. In some other examples, separate RAN parameter identifiers may indicate various CLI mitigation actions. Additionally, or alternatively, a seventh RAN parameter may indicate an action and an eighth RAN parameter may indicate an action. Further RAN parameters in the sequence may then provide further details of the CLI mitigation action (e.g., a transmission power reduction, a constraint on use of beams, a constraint on use of resources, whether the resources are in the time domain or the frequency domain or both, and so on).

[0246] In one or more implementations, multiple policy rules are defined. For example, a first policy rule may indicate to perform a CLI mitigation action, and a second policy rule may indicate to report the CLI mitigation action taken by the RAN node 1204. In some other examples, a third policy rule may indicate to report an excessive CLI to the RAN controller 1202, a fourth policy rule may indicate to report the excessive CLI to one or more other RAN nodes or RAN and / or CN entities, and / or a fifth policy rule may indicate to transmit a reference signal or increase a transmission power in an over-the-air transmission. Various other examples may be constructed by combining policy rules indicated to one or more RAN nodes through one or more subscription procedures. Additionally, or alternatively, various examples may include signaling based on a POLICY service, with one or more policy rules, combined with other services such as REPORT, INSERT, and CONTROL. The combinations may be preconfigured or defined, configured by the network and / or 0AM, indicated by a signaling from the RAN nodes and / or other RAN and / or CN entities, determined by implementation, or any combination thereof.

[0247] In various examples, such as for inter-base station or inter-UE CLI management, the RAN controller 1402 may use a QUERY service. The RAN controller 1402 may send a QUERY REQUEST message to a RAN node 1404, where the message includes information that the RAN controller 1402 requests from the RAN node 1404. The information may be associated with the RAN node 1404 or a UE 104 served by the RAN node 1404. The RAN controller 1402 sets a wait timer while awaiting a response from the RAN node 1404. The RAN node 1404 performs validation and attempts to retrieve the requested information. If the RAN node 1404 successfully validates and retrieves the requested information, then the RAN node 1404 may then send a QUERY RESPONSE message including the retrieved information. If the RAN node 1404 fails to validate the request or fails to retrieve the requested information, then the RAN node 1404 may then send a QUERY FAILURE message along with the cause for failure. In various examples, one or more RAN parameters may be specified by the standard for a QUERY service in association with a duplexing process or a CLI management process. The RAN parameters can include information of a configuration associated with a cell (e.g., cell-specific (common) TDD configuration, cell-specific (common) SBFD configuration), information of a configuration associated with a UE 104 or a group of UEs 104 (e.g., UE-specific (dedicated) TDD configuration, UE-specific (dedicated) SBFD configuration, SRS configuration), and / or non-configuration information associated with a cell, a UE 104, or a group of UEs 104 (e.g., inter-base station CLI, inter-UE CLI).

[0248] Figure 15 illustrates an example of a RAN node 1500 in accordance with aspects of the present disclosure. The RAN node 1500 may include a processor 1502, a memory 1504, a controller 1506, and a transceiver 1508. The processor 1502, the memory 1504, the controller 1506, or the transceiver 1508, 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.

[0249] The processor 1502, the memory 1504, the controller 1506, or the transceiver 1508, 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 thereofconfigured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0250] The processor 1502 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 1502 may be configured to or operable to operate the memory 1504. In some other implementations, the memory 1504 may be integrated into the processor 1502. The processor 1502 may be configured to or operable to execute computer-readable instructions stored in the memory 1504 to cause the RAN node 1500 to perform various functions of the present disclosure.

[0251] The memory 1504 may include volatile or non-volatile memory. The memory 1504 may store computer-readable, computer-executable code including instructions when executed by the processor 1502 cause the RAN node 1500 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as the memory 1504 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.

[0252] In some implementations, the processor 1502 and the memory 1504 coupled with the processor 1502 may be configured to or operable to cause the RAN node 1500 to perform one or more of the functions described herein (e.g., executing, by the processor 1502, instructions stored in the memory 1504). For example, the processor 1502 may support wireless communication at the RAN node 1500 in accordance with examples as disclosed herein. The RAN node 1500 may be configured to or operable 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 is obtained 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 at least one of the UE or the transmission of the reference signal.

[0253] Additionally, the RAN node 1500 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.

[0254] Additionally, or alternatively, the RAN node 1500 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 1500 may be configured to or operable to support updating 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 onetransmission parameter for the wireless communications or duration for applying the update to the at least one transmission parameter for the wireless communications.

[0255] 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. 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.

[0256] In some implementations, the processor 1502 and the memory 1504 coupled with the processor 1502 may be configured to or operable to cause the RAN node 1500 to perform one or more of the functions described herein (e.g., executing, by the processor 1502, instructions stored in the memory 1504). For example, the processor 1502 may support wireless communication at the RAN node 1500 in accordance with examples as disclosed herein. The RAN node 1500 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 indicative of configuration information associated with a UE and at least one second parameter indicative of a condition and an action to perform for managing a CLI based on the condition, transmitting, to the UE, a second message that indicates the at least one first parameter indicative of the configuration information, detecting, based on the configuration information, a trigger event associated with one or more of the condition or the action, and selectively performing the action for managing the CLI based on the condition and the trigger event.

[0257] Additionally, the RAN node 1500 may be configured to or operable to support any one or combination of the configuration information indicates that the UE perform at least one CLI measurement to obtain at least one CLI value, where detecting the trigger event includes receiving, from the UE, a third message including the at least one CLI value, where the condition includes the at least one CLI value exceeding a threshold value. Additionally, or alternatively, selectively performing the action for managing the CLI includes transmitting, to at least one of the RAN controller or an additional RAN node, a fourth message based on the at least one CLI valueexceeding the threshold value, where the fourth message indicates at least one of a difference between the at least one CLI value and the threshold value, the at least one CLI value, a beam associated with the at least one CLI value, or at least one time-frequency resource associated with the at least one CLI value. Additionally, or alternatively, selectively performing the action for managing the CLI includes refraining from transmitting a fourth message based on the at least one CLI value failing to exceed the threshold value, where the fourth message indicates at least one of a difference between the at least one CLI value and the threshold value, the at least one CLI value, a beam associated with the at least one CLI value, or at least one time-frequency resource associated with the at least one CLI value.

[0258] Additionally, or alternatively, selectively performing the action for managing the CLI includes transmitting a fourth message that indicates at least one of a reference signal or that the UE transmit the reference signal based on the at least one CLI value exceeding the threshold value, where the fourth message indicates at least one of a difference between the at least one CLI value and the threshold value, the at least one CLI value, a beam associated with the at least one CLI value, or at least one time-frequency resource associated with the at least one CLI value.Additionally, or alternatively, selectively performing the action for managing the CLI includes refraining from transmitting a fourth message that indicates at least one of a reference signal or that the UE transmit the reference signal based on the at least one CLI value failing to exceed the threshold value, where the fourth message indicates at least one of a difference between the at least one CLI value and the threshold value, the at least one CLI value, a beam associated with the at least one CLI value, or at least one time-frequency resource associated with the at least one CLI value. Additionally, or alternatively, selectively performing the action for managing the CLI includes transmitting a fourth message that indicates at least one of a reference signal or that the UE transmit the reference signal, where the reference signal is associated with a transmission power that satisfies a transmit power threshold corresponding to the threshold value based on the at least one CLI value exceeding the threshold value. Additionally, or alternatively, selectively performing the action for managing the CLI includes transmitting a fourth message that indicates at least one of a reference signal or that the UE transmit the reference signal, where a transmission power associated with the reference signal is maintained based on the at least one CLI value failing to exceed thethreshold value. Additionally, or alternatively, the at least one CLI value includes at least one of an RSRP, an RS SI, an SINR, or an RSRQ.

[0259] Additionally, or alternatively, the configuration information indicates that the UE transmit a reference signal, where detecting the trigger event includes receiving, from at least one of the RAN controller or an additional RAN node, a third message including at least one CLI value associated with a transmission of the reference signal, where the condition includes the at least one CLI value exceeding a threshold value. Additionally, or alternatively, selectively performing the action for managing the CLI includes determining to perform at least one action based on the at least one CLI value exceeding the threshold value, and transmitting, to the UE, a fourth message that indicates the UE update at least one transmission parameter for wireless communications associated with managing the CLI, where the update to the at least one transmission parameter includes at least one of reducing a transmission power associated with the wireless communications, refraining from using one or more time-frequency resources for the wireless communications, or refraining from using a beam for the wireless communications.

[0260] Additionally, or alternatively, transmitting the fourth message includes determining a time period associated with the update to the at least one transmission parameter, 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, selectively performing the action for managing the CLI includes determining not to perform at least one action based on the at least one CLI value exceeding the threshold value, and refraining from transmitting, to the UE, a fourth message that indicates the UE update a transmission parameter for wireless communications associated with the CLI, where the update to the transmission parameter includes at least one of reducing a transmission power associated with the wireless communications, refraining from using one or more time-frequency resources for the wireless communications, or refraining from using a beam for the wireless communications. 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.

[0261] Additionally, or alternatively, the RAN node 1500 may be configured to or operable to support receiving, from the RAN controller, a third message including a request for informationassociated with at least one of the UE or where at least one of the at least one first parameter or the at least one second parameter is based on the information associated with the at least one of the UE or the RAN node, and transmitting, in response to the request, at least one of a fourth message that indicates the information associated with the at least one of the UE or the at least one RAN node or a fifth message that indicates a failure to obtain the information associated with the at least one of the UE or the at least one RAN node, where the information includes at least one of TDD information, SBFD information, reference signal information, or information associated with the CLI. Additionally, or alternatively, the subscription information includes at least one third parameter that indicates a type of the first message is a policy type. 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.

[0262] Additionally, or alternatively, the RAN node 1500 may support at least one memory (e.g., the memory 1504) and at least one processor (e.g., the processor 1502) coupled with the at least one memory and configured to or operable to cause the RAN node 1500 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, wherein the at least one second parameter is obtained 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 at least one of the UE or the transmission of the reference signal.

[0263] Additionally, the RAN node 1500 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 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, 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 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.

[0264] 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. Additionally, or alternatively, the RAN node includes at least one of a base station, a CU, a DU, anE2 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.

[0265] Additionally, or alternatively, the RAN node 1500 may support at least one memory (e.g., the memory 1504) and at least one processor (e.g., the processor 1502) coupled with the at least one memory and configured to or operable to cause the RAN node 1500 to: receive, from a RAN controller, a first message that indicates subscription information including at least one first parameter indicative of configuration information associated with a UE and at least one second parameter indicative of a condition and an action to perform for managing a CLI based on the condition, transmit, to the UE, a second message that indicates the at least one first parameter indicative of the configuration information, detect, based on the configuration information, a trigger event associated with one or more of the condition or the action, and selectively perform the action for managing the CLI based on the condition and the trigger event.

[0266] Additionally, the RAN node 1500 may be configured to or operable to support any one or combination of the configuration information indicates that the UE perform at least one CLI measurement to obtain at least one CLI value, and to detect the trigger event, the at least one processor is configured to or operable to receive, from the UE, a third message including the at least one CLI value, where the condition includes the at least one CLI value exceeding a threshold value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the at least one processor is configured to or operable to transmit, to at least one of the RAN controller or an additional RAN node, a fourth message based on the at least one CLI value exceeding the threshold value, where the fourth message indicates at least one of a difference between the at least one CLI value and the threshold value, the at least one CLI value, a beam associated with the at least one CLI value, or at least one time-frequency resource associated with the at least one CLI value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the at least one processor is configured to or operable to refrain from transmitting a fourth message based on the at least one CLI value failing to exceed the threshold value, where the fourth message indicates at least one of a difference between the at least one CLI value and the threshold value, the at least one CLI value, a beam associated with the at least one CLI value, or at least one time-frequency resource associated with the at least one CLI value.

[0267] Additionally, or alternatively, to selectively perform the action for managing the CLI, the at least one processor is configured to or operable to transmit a fourth message that indicates at least one of a reference signal or that the UE transmit the reference signal based on the at least one CLI value exceeding the threshold value, where the fourth message indicates at least one of a difference between the at least one CLI value and the threshold value, the at least one CLI value, a beam associated with the at least one CLI value, or at least one time-frequency resource associated with the at least one CLI value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the at least one processor is configured to or operable to refrain from transmitting a fourth message that indicates at least one of a reference signal or that the UE transmit the reference signal based on the at least one CLI value failing to exceed the threshold value, where the fourth message indicates at least one of a difference between the at least one CLI value and the threshold value, the at least one CLI value, a beam associated with the at least one CLI value, or at least one time-frequency resource associated with the at least one CLI value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the at least one processor is configured to or operable to transmit a fourth message that indicates at least one of a reference signal or that the UE transmit the reference signal, where the reference signal is associated with a transmission power that satisfies a transmit power threshold corresponding to the threshold value based on the at least one CLI value exceeding the threshold value.

[0268] Additionally, or alternatively, to selectively perform the action for managing the CLI, the at least one processor is configured to or operable to transmit a fourth message that indicates at least one of a reference signal or that the UE transmit the reference signal, where a transmission power associated with the reference signal is maintained based on the at least one CLI value failing to exceed 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 configuration information indicates that the UE transmit a reference signal, where to detect the trigger event, the at least one processor is configured to or operable to receive, from at least one of the RAN controller or an additional RAN node, a third message including at least one CLI value associated with a transmission of the reference signal, where the condition includes the at least one CLI value exceeding a threshold value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the at least one processor is configured to or operable to determine toperform at least one action based on the at least one CLI value exceeding the threshold value, and transmit, to the UE, a fourth message that indicates the UE update at least one transmission parameter for wireless communications associated with managing the CLI, where the update to the at least one transmission parameter includes at least one of reducing a transmission power associated with the wireless communications, refraining from using one or more time-frequency resources for the wireless communications, or refraining from using a beam for the wireless communications.

[0269] Additionally, or alternatively, to transmit the fourth message, the at least one processor is configured to or operable to determine a time period associated with the update to the at least one transmission parameter, 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, to selectively perform the action for managing the CLI, the at least one processor is configured to or operable to determine not to perform at least one action based on the at least one CLI value exceeding the threshold value, and refrain from transmitting, to the UE, a fourth message that indicates the UE update a transmission parameter for wireless communications associated with the CLI, where the update to the transmission parameter includes at least one of reducing a transmission power associated with the wireless communications, refraining from using one or more time-frequency resources for the wireless communications, or refraining from using a beam for the wireless communications. 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.

[0270] Additionally, or alternatively, the at least one processor is configured to or operable to receive, from the RAN controller, a third message including a request for information associated with at least one of the UE or the RAN node, where at least one of the at least one first parameter or the at least one second parameter is based on the information associated with the at least one of the UE or the RAN node, and transmit, in response to the request, at least one of a fourth message that indicates the information associated with the at least one of the UE or the RAN node or a fifth message that indicates a failure to obtain the information associated with the at least one of the UE or the RAN node, where the information includes at least one of TDD information, SBFDinformation, reference signal information, or information associated with the CLI. Additionally, or alternatively, the subscription information includes at least one third parameter that indicates a type of the first message is a policy type. 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.

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

[0272] In some implementations, the RAN node 1500 may include at least one transceiver 1508. In some other implementations, the RAN node 1500 may have more than one transceiver 1508. The transceiver 1508 may represent a wireless transceiver. The transceiver 1508 may include one or more receiver chains 1510, one or more transmitter chains 1512, or any combination thereof.

[0273] A receiver chain 1510 may be configured to or operable to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 1510 may include one or more antennas to receive a signal over the air or wireless medium. The receiver chain 1510 may include at least one amplifier (e.g., an LNA) configured to amplify the received signal. The receiver chain 1510 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 1510 may include at least one decoder for decoding the demodulated signal to receive the transmitted data.

[0274] A transmitter chain 1512 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 1512 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 1512 may also include at least one power amplifier configured to amplify the modulated signal toan appropriate power level suitable for transmission over the wireless medium. The transmitter chain 1512 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0275] Figure 16 illustrates an example of a processor 1600 in accordance with aspects of the present disclosure. The processor 1600 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 1600 may include a controller 1602 configured to perform various operations in accordance with examples as described herein. The processor 1600 may optionally include at least one memory 1604, which may be, for example, an L1 / L2 / L3 cache. Additionally, or alternatively, the processor 1600 may optionally include one or more arithmetic-logic units (ALUs) 1606. 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).

[0276] The processor 1600 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 1600) 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).

[0277] The controller 1602 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 1600 to cause the processor 1600 to support various operations in accordance with examples as described herein. For example, the controller 1602 may operate as a control unit of the processor 1600, generating control signals that manage the operation of various components of the processor 1600. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.

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

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

[0280] The memory 1604 may store computer-readable, computer-executable code including instructions that, when executed by the processor 1600, cause the processor 1600 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 1602 and / or the processor 1600 may be configured to execute computer-readable instructions stored in the memory 1604 to cause the processor 1600 to perform various functions. For example, the processor 1600 and / or the controller 1602 may be coupled with or to the memory 1604, the processor 1600, and the controller 1602, and may be configured to perform various functions described herein. In some examples, the processor 1600 may include multiple processors and the memory 1604 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.

[0281] The one or more ALUs 1606 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 1606 may reside within or on a processor chipset (e.g., the processor 1600). In some other implementations, the one or more ALUs 1606 may reside external to the processor chipset (e.g., the processor 1600). One or more ALUs 1606 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 1606 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 1606 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 1606 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not-AND (NAND), enabling the one or more ALUs 1606 to handle conditional operations, comparisons, and bitwise operations.

[0282] The processor 1600 may support wireless communication in accordance with examples as disclosed herein. The processor 1600 may be configured to or operable to support at least one controller (e.g., the controller 1602) coupled with at least one memory (e.g., the memory 1604) 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 is obtained 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 at least one of the UE or the transmission of the reference signal.

[0283] Additionally, the processor 1600 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 wirelesscommunications, 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 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.

[0284] 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. Additionally, or alternatively, the processor includes at least one of a base station, a CU, a DU, an E2 node, or an 01node, where the RAN controller includes at least one of an RIC, a near-real-time RIC, or a non-real- time RIC.

[0285] The processor 1600 may support wireless communication in accordance with examples as disclosed herein. The processor 1600 may be configured to or operable to support at least one controller (e.g., the controller 1602) coupled with at least one memory (e.g., the memory 1604) 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 indicative of configuration information associated with a UE and at least one second parameter indicative of a condition and an action to perform for managing a CLI based on the condition, transmit, to the UE, a second message that indicates the at least one first parameter indicative of the configuration information, detect, based on the configuration information, a trigger event associated with one or more of the condition or the action, and selectively perform the action for managing the CLI based on the condition and the trigger event.

[0286] Additionally, the processor 1600 may be configured to or operable to support any one or combination of the configuration information indicates that the UE perform at least one CLI measurement to obtain at least one CLI value, where to detect the trigger event, the at least one controller is configured to receive, from the UE, a third message including the at least one CLI value, where the condition includes the at least one CLI value exceeding a threshold value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the at least one controller is configured to transmit, to at least one of the RAN controller or an additional processor, a fourth message based on the at least one CLI value exceeding the threshold value, where the fourth message indicates at least one of a difference between the at least one CLI value and the threshold value, the at least one CLI value, a beam associated with the at least one CLI value, or at least one time-frequency resource associated with the at least one CLI value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the at least one controller is configured to refrain from transmitting a fourth message based on the at least one CLI value failing to exceed the threshold value, where the fourth message indicates at least one of a difference between the at least one CLI value and the threshold value, the at least one CLI value, a beam associated with the at least one CLI value, or at least one time-frequency resource associated with the at least one CLI value.

[0287] Additionally, or alternatively, to selectively perform the action for managing the CLI, the at least one controller is configured to transmit a fourth message that indicates at least one of a reference signal or that the UE transmit the reference signal based on the at least one CLI value exceeding the threshold value, where the fourth message indicates at least one of a difference between the at least one CLI value and the threshold value, the at least one CLI value, a beam associated with the at least one CLI value, or at least one time-frequency resource associated with the at least one CLI value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the at least one controller is configured to refrain from transmitting a fourth message that indicates at least one of a reference signal or that the UE transmit the reference signal based on the at least one CLI value failing to exceed the threshold value, where the fourth message indicates at least one of a difference between the at least one CLI value and the threshold value, the at least one CLI value, a beam associated with the at least one CLI value, or at least one timefrequency resource associated with the at least one CLI value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the at least one controller is configured to transmit a fourth message that indicates at least one of a reference signal or that the UE transmit the reference signal, where the reference signal is associated with a transmission power that satisfies a transmit power threshold corresponding to the threshold value based on the at least one CLI value exceeding the threshold value.

[0288] Additionally, or alternatively, to selectively perform the action for managing the CLI, the at least one controller is configured to transmit a fourth message that indicates at least one of a reference signal or that the UE transmit the reference signal, where a transmission power associated with the reference signal is maintained based on the at least one CLI value failing to exceed 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 configuration information indicates that the UE transmit a reference signal, where to detect the trigger event, the at least one controller is configured to receive, from at least one of the RAN controller or an additional processor, a third message including at least one CLI value associated with a transmission of the reference signal, where the condition includes the at least one CLI value exceeding a threshold value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the at least one controller is configured to determine to perform at least one action based on the at leastone CLI value exceeding the threshold value, and transmit, to the UE, a fourth message that indicates the UE update at least one transmission parameter for wireless communications associated with managing the CLI, where the update to the at least one transmission parameter includes at least one of reducing a transmission power associated with the wireless communications, refraining from using one or more time-frequency resources for the wireless communications, or refraining from using a beam for the wireless communications.

[0289] Additionally, or alternatively, to transmit the fourth message, the at least one controller is configured to determine a time period associated with the update to the at least one transmission parameter, 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, to selectively perform the action for managing the CLI, the at least one controller is configured to determine not to perform at least one action based on the at least one CLI value exceeding the threshold value, and refrain from transmitting, to the UE, a fourth message that indicates the UE update a transmission parameter for wireless communications associated with the CLI, where the update to the transmission parameter includes at least one of reducing a transmission power associated with the wireless communications, refraining from using one or more time-frequency resources for the wireless communications, or refraining from using a beam for the wireless communications. 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.

[0290] Additionally, or alternatively, the at least one controller is configured to receive, from the RAN controller, a third message including a request for information associated with at least one of the UE or at least one of the at least one first parameter or the at least one second parameter is based on the information associated with the at least one of the UE or the processor, and transmit, in response to the request, at least one of a fourth message that indicates the information associated with the at least one of the UE or the processor or a fifth message that indicates a failure to obtain the information associated with the at least one of the UE or the information includes at least one of TDD information, SBFD information, reference signal information, or information associated with the CLI. Additionally, or alternatively, the subscription information includes at least one thirdparameter that indicates a type of the first message is a policy type, where 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.

[0291] Figure 17 illustrates an example of a RAN controller 1700 in accordance with aspects of the present disclosure. The RAN controller 1700 may include a processor 1702, a memory 1704, a controller 1706, and a transceiver 1708. The processor 1702, the memory 1704, the controller 1706, or the transceiver 1708, 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.

[0292] The processor 1702, the memory 1704, the controller 1706, or the transceiver 1708, 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.

[0293] The processor 1702 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 1702 may be configured to operate the memory 1704. In some other implementations, the memory 1704 may be integrated into the processor 1702. The processor 1702 may be configured to execute computer-readable instructions stored in the memory 1704 to cause the RAN controller 1700 to perform various functions of the present disclosure.

[0294] The memory 1704 may include volatile or non-volatile memory. The memory 1704 may store computer-readable, computer-executable code including instructions when executed by the processor 1702 cause the RAN controller 1700 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as the memory 1704 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 computerprogram 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.

[0295] In some implementations, the processor 1702 and the memory 1704 coupled with the processor 1702 may be configured to cause the RAN controller 1700 to perform one or more of the functions described herein (e.g., executing, by the processor 1702, instructions stored in the memory 1704). For example, the processor 1702 may support wireless communication at the RAN controller 1700 in accordance with examples as disclosed herein. The RAN controller 1700 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 first parameter indicative of configuration information associated with a UE and at least one second parameter indicative of a condition and an action to perform for managing a CLI based on the condition, and receiving, from the at least one RAN node, a second message that indicates the action for managing the CLI is performed based on the condition and a trigger event associated with the UE, where the trigger event is associated with one or more of the condition or the action indicated by the subscription information.

[0296] Additionally, the RAN controller 1700 may be configured to or operable to support any one or combination of the configuration information indicates that the UE perform at least one CLI measurement to obtain at least one CLI value, where the trigger event includes the at least one RAN node receiving a third message including the at least one CLI value, where the condition includes the at least one CLI value exceeding a threshold value. Additionally, or alternatively, the second message indicates at least one of a difference between the at least one CLI value and the threshold value, the at least one CLI value, a beam associated with the at least one CLI value, or at least one time-frequency resource associated with the at least one CLI value. Additionally, or alternatively, the second message includes one or more of a first reference signal or an indication that the UE transmits a second reference signal, where the first reference signal and the second reference signal are associated with a transmission power that satisfies a transmission power threshold corresponding to 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 configuration information indicates that the UE transmit a reference signal, where the trigger event includes the at least one RAN node receiving a third message including at least one CLI valueassociated with a transmission of the reference signal, where the condition includes the at least one CLI value exceeding a threshold value. Additionally, or alternatively, the condition includes the at least one CLI value exceeding the threshold value, where the second message is associated wit...

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 indicative of configuration information associated with a user equipment (UE) and at least one second parameter indicative of a condition and an action to perform for managing a cross-link interference (CLI) based at least in part on the condition; transmit, to the UE, a second message that indicates the at least one first parameter indicative of the configuration information; detect, based at least in part on the configuration information, a trigger event associated with one or more of the condition or the action; and selectively perform the action for managing the CLI based at least in part on the condition and the trigger event.

2. The RAN node of claim 1 , wherein the configuration information indicates that the UE perform at least one CLI measurement to obtain at least one CLI value, and wherein to detect the trigger event, the at least one processor is operable to cause the RAN node to receive, from the UE, a third message comprising the at least one CLI value, wherein the condition comprises the at least one CLI value exceeding a threshold value, and 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.

3. The RAN node of claim 2, wherein to selectively perform the action for managing the CLI, the at least one processor is operable to cause the RAN node to transmit, to at least one of the RAN controller or an additional RAN node, a fourth message based at least in part on the at least one CLI value exceeding the threshold value, and wherein the fourth message indicates at least one of a difference between the at least one CLI value and the threshold value, the at least one CLIvalue, a beam associated with the at least one CLI value, or at least one time-frequency resource associated with the at least one CLI value.

4. The RAN node of claim 2, wherein to selectively perform the action for managing the CLI, the at least one processor is operable to cause the RAN node to refrain from transmitting a fourth message based at least in part on the at least one CLI value failing to exceed the threshold value, and wherein the fourth message indicates at least one of a difference between the at least one CLI value and the threshold value, the at least one CLI value, a beam associated with the at least one CLI value, or at least one time-frequency resource associated with the at least one CLI value.

5. The RAN node of claim 2, wherein to selectively perform the action for managing the CLI, the at least one processor is operable to cause the RAN node to transmit a fourth message that indicates at least one of a reference signal or that the UE transmit the reference signal based at least in part on the at least one CLI value exceeding the threshold value, and wherein the fourth message indicates at least one of a difference between the at least one CLI value and the threshold value, the at least one CLI value, a beam associated with the at least one CLI value, or at least one time-frequency resource associated with the at least one CLI value.

6. The RAN node of claim 2, wherein to selectively perform the action for managing the CLI, the at least one processor is operable to cause the RAN node to refrain from transmitting a fourth message that indicates at least one of a reference signal or that the UE transmit the reference signal based at least in part on the at least one CLI value failing to exceed the threshold value, and wherein the fourth message indicates at least one of a difference between the at least one CLI value and the threshold value, the at least one CLI value, a beam associated with the at least one CLI value, or at least one time-frequency resource associated with the at least one CLI value.

7. The RAN node of claim 2, wherein to selectively perform the action for managing the CLI, the at least one processor is operable to cause the RAN node to transmit a fourth message that indicates at least one of a reference signal or that the UE transmit the reference signal, and wherein the reference signal is associated with a transmission power that satisfies a transmit power threshold corresponding to the threshold value based at least in part on the at least one CLI value exceeding the threshold value.

8. The RAN node of claim 2, wherein to selectively perform the action for managing the CLI, the at least one processor is operable to cause the RAN node to transmit a fourth message that indicates at least one of a reference signal or that the UE transmit the reference signal, wherein a transmission power associated with the reference signal is maintained based at least in part on the at least one CLI value failing to exceed the threshold value.

9. The RAN node of claim 1, wherein the configuration information indicates that the UE transmit a reference signal, and wherein to detect the trigger event, the at least one processor is operable to cause the RAN node to receive, from at least one of the RAN controller or an additional RAN node, a third message comprising at least one CLI value associated with a transmission of the reference signal, and wherein the condition comprises the at least one CLI value exceeding a threshold value.

10. The RAN node of claim 9, wherein to selectively perform the action for managing the CLI, the at least one processor is operable to cause the RAN node to: determine to perform at least one action based at least in part on the at least one CLI value exceeding the threshold value, 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, and wherein the reference signal comprises a sounding reference signal (SRS); and transmit, to the UE, a fourth message that indicates the UE update at least one transmission parameter for wireless communications associated with managing the CLI, wherein the update to the at least one transmission parameter comprises at least one of reducing a transmission power associated with the wireless communications, refraining from using one or more time-frequency resources for the wireless communications, or refraining from using a beam for the wireless communications.

11. The RAN node of claim 10, wherein to transmit the fourth message, the at least one processor is operable to cause the RAN node to determine a time period associated with the update to the at least one transmission parameter, 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 orduration for applying the update to the at least one transmission parameter for the wireless communications.

12. The RAN node of claim 9, wherein to selectively perform the action for managing the CLI, the at least one processor is operable to cause the RAN node to: determine not to perform at least one action based at least in part on the at least one CLI value exceeding the threshold value; and refrain from transmitting, to the UE, a fourth message that indicates the UE update a transmission parameter for wireless communications associated with the CLI, wherein the update to the transmission parameter comprises at least one of reducing a transmission power associated with the wireless communications, refraining from using one or more time-frequency resources for the wireless communications, or refraining from using a beam for the wireless communications.

13. The RAN node of claim 1, wherein the at least one processor is further operable to cause the RAN node to: receive, from the RAN controller, a third message comprising a request for information associated with at least one of the UE or the RAN node, wherein at least one of the at least one first parameter or the at least one second parameter is based at least in part on the information associated with the at least one of the UE or the RAN node; and transmit, in response to the request, at least one of a fourth message that indicates the information associated with the at least one of the UE or the RAN node or a fifth message that indicates a failure to obtain the information associated with the at least one of the UE or the RAN node, wherein the information comprises at least one of time division duplexing information, subband full-duplex information, reference signal information, or information associated with the CLI.

14. A method performed by a radio access network (RAN) node, the method comprising: receiving, from a RAN controller, a first message that indicates subscription information comprising at least one first parameter indicative of configuration information associated with a user equipment (UE) and at least one second parameter indicative of a condition and an action to perform for managing a cross-link interference (CLI) based at least in part on the condition; transmitting, to the UE, a second message that indicates the at least one first parameter indicative of the configuration information;detecting, based at least in part on the configuration information, a trigger event associated with one or more of the condition or the action ; and selectively performing the action for managing the CLI based at least in part on the condition and the trigger event.

15. 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 first parameter indicative of configuration information associated with a user equipment (UE) and at least one second parameter indicative of a condition and an action to perform for managing a cross-link interference (CLI) based at least in part on the condition; and receive, from the at least one RAN node, a second message that indicates the action for managing the CLI is performed based at least in part on the condition and a trigger event associated with the UE, wherein the trigger event is associated with one or more of the condition or the action indicated by the subscription information.

16. The RAN controller of claim 15, wherein the configuration information indicates that the UE perform at least one CLI measurement to obtain at least one CLI value, wherein the trigger event comprises the at least one RAN node receiving a third message comprising the at least one CLI value, wherein the condition comprises the at least one CLI value exceeding a threshold value, and 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.

17. The RAN controller of claim 16, wherein the second message indicates at least one of a difference between the at least one CLI value and the threshold value, the at least one CLI value, a beam associated with the at least one CLI value, or at least one time-frequency resource associated with the at least one CLI value.

18. The RAN controller of claim 16, wherein the second message comprises one or more of a first reference signal or an indication that the UE transmits a second reference signal, and wherein the first reference signal and the second reference signal are associated with a transmission power that satisfies a transmission power threshold corresponding to the threshold value.

19. The RAN controller of claim 15, wherein the configuration information indicates that the UE transmit a reference signal, and wherein the trigger event comprises the at least one RAN node receiving a third message comprising at least one CLI value associated with a transmission of the reference signal, and wherein the condition comprises the at least one CLI value exceeding a threshold value, 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, and wherein the reference signal comprises a sounding reference signal (SRS).

20. A method performed by a radio access network (RAN) controller, the method comprising: transmitting, to at least one RAN node, a first message that indicates subscription information comprising at least one first parameter indicative of configuration information associated with a user equipment (UE) and at least one second parameter indicative of a condition and an action to perform for managing a cross-link interference (CLI) based at least in part on the condition; and receiving, from the at least one RAN node, a second message that indicates the action for managing the CLI is performed based at least in part on the condition and a trigger event associated with the UE, wherein the trigger event is associated with one or more of the condition or the action indicated by the subscription information.

Images