Cross-link interference management

Abstract

Various aspects of the present disclosure relate to cross-link interference (CLI) management. A radio access network (RAN) node receives a message from a RAN controller that indicates subscription information including at least one parameter indicative of a condition and an action for managing CLI based on the condition. The RAN node detects a trigger event associated with one or more of the condition or the action. The RAN node selectively performs the action for managing the CLI based on the condition being met in response to the trigger event. In some examples, the RAN node transmits a message to the RAN controller that indicates the action for managing CLI is performed.

Description

CROSS-LINK INTERFERENCE MANAGEMENTRELATED APPLICATION

[0001] This application claims priority to U.S. Provisional Application Serial No. 63 / 548,924 filed February 2, 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] Some implementations of the method and apparatuses described herein may further include a radio access network (RAN) node for wireless communication to receive (e.g., obtain, retrieve), from a RAN controller, subscription information including at least one parameter indicative of a condition and an action for managing cross-link interference (CLI) based on the condition, detect 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 being met in response to the trigger event.

[0006] In some implementations of the method and apparatuses described herein, to detect the trigger event, the RAN node measures at least one CLI value, where the condition includes the at least one CLI value satisfying (e.g., being greater than, exceeding) a threshold value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the RAN node transmits, to at least one of the RAN controller or an additional RAN node, a message based on the at least one CLI value satisfying the threshold value, and where the 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 refrains from transmitting a message based on the at least one CLI value failing to satisfy (e.g., being less than, not exceeding) the threshold value, and where the 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 transmits a message including a reference signal based on the at least one CLI value satisfying the threshold value, and where the message indicates at least one of a difference between the at least one CLI value and the thresholdvalue, 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.

[0007] Additionally, or alternatively, to selectively perform the action for managing the CLI, the RAN node refrains from transmitting a message including a reference signal based on the at least one CLI value failing to satisfy the threshold value, and where the 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 transmits, using a transmission power that satisfies a transmit power threshold corresponding to the threshold value, a message including a reference signal based on the at least one CLI value satisfying the threshold value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the RAN node transmits, based on maintaining a transmission power, a message including a reference signal based on the at least one CLI value failing to satisfy the threshold value. 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, to detect the trigger event, the RAN node measures at least one RSRP value, and where the condition includes the at least one RSRP value satisfying a threshold value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the RAN node performs at least one action based on the at least one RSRP value satisfying the threshold value, and where the at least one action includes to reduce a transmission power associated with transmission of a message, to select one or more time-frequency resources for the transmission of the message, or to select a beam for the transmission of the message.

[0008] Additionally, or alternatively, to selectively perform the action for managing the CLI, the RAN node refrains from performing at least one action based on the at least one RSRP value failing to satisfy the threshold value, and where the at least one action includes to reduce a transmission power associated with transmission of a message, to select one or more time-frequency resources for the transmission of the message, or to select a beam for the transmission of the message. Additionally, or alternatively, to detect the trigger event, the RAN node receives a message indicating at least one CLI value associated with at least one CLI measurement, and wherethe condition includes the at least one CLI value satisfying a threshold value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the RAN node performs at least one action based on the at least one CLI value satisfying the threshold value, and where the at least one action includes to reduce a transmission power associated with transmission of an additional message, to select one or more time-frequency resources for the transmission of the additional message, or to select a beam for the transmission of the additional message. Additionally, or alternatively, to selectively perform the action for managing the CLI, the RAN node refrains from performing at least one action based on the at least one CLI value failing to satisfy the threshold value, and where the at least one action includes to reduce a transmission power associated with transmission of an additional message, to select one or more time-frequency resources for the transmission of the additional message, or to select a beam for the transmission of the additional message. Additionally, or alternatively, the at least one CLI value includes at least one of an RSRP, an RS SI, an SINR, or an RSRQ.

[0009] Additionally, or alternatively, to detect the trigger event, the RAN node receives a message indicating a metric indicative of a time-frequency resource usage, and where the condition includes the metric indicative of the time-frequency resource usage satisfying a threshold value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the RAN node transmits, to at least one of the RAN controller or an additional RAN node, an additional message that indicates the metric indicative of the time-frequency resource usage based on the metric indicative of the time-frequency resource usage satisfying the threshold value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the RAN node refrains from transmitting, to at least one of the RAN controller or an additional RAN node, an additional message that indicates the metric indicative of the time-frequency resource usage based on the metric indicative of the time-frequency resource usage failing to satisfy the threshold value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the RAN node performs the action for managing the CLI, and transmits, to the RAN controller, a message that indicates the action for managing the CLI is performed.

[0010] Additionally, or alternatively, to detect the trigger event, the RAN node obtains at least one of at least one CLI value or at least one RSRP value, and where the at least one parameter is indicative of the trigger event. Additionally, or alternatively, to detect the trigger event, the RANnode performs at least one CLI measurement associated with the at least one CLI value according to a periodicity, and where the at least one parameter indicates the periodicity. Additionally, or alternatively, to detect the trigger event, the RAN node performs a set of CLI measurements to obtain the at least one CLI value, and where the at least one CLI value corresponds to at least one of an average CLI value of the set of CLI measurements or a maximum CLI value of the set of CLI measurements. Additionally, or alternatively, to detect the trigger event, the RAN node performs a set of CLI measurements to obtain a set of CLI values, and where the trigger event is detected based on a threshold numerical quantity of consecutive CLI values satisfying a threshold value, and where the at least one parameter indicates the threshold numerical quantity of consecutive CLI values. Additionally, or alternatively, to detect the trigger event, the RAN node performs a set of CLI measurements to obtain a set of CLI values, and where the trigger event is detected based on a threshold numerical quantity of CLI values in a threshold numerical quantity of consecutive CLI values satisfying a threshold value, and where the at least one parameter indicates the threshold numerical quantity of CLI values and the threshold numerical quantity of consecutive CLI values. Additionally, or alternatively, the subscription information includes at least one additional parameter that indicates a type of a message including the subscription information 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, and where the RAN controller includes at least one of a RAN intelligent controller (RIC), a near-real-time RIC, or a non-real-time RIC.

[0011] Some implementations of the method and apparatuses described herein may further include a processor for wireless communication to receive (e.g., obtain, retrieve), from a RAN controller, subscription information including at least one parameter indicative of a condition and an action for managing CLI based on the condition, detect 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 being met in response to the trigger event.

[0012] In some implementations of the method and apparatuses described herein, to detect the trigger event, the processor measures at least one CLI value, and where the condition includes the at least one CLI value satisfying a threshold value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the processor transmits, to at least one of the RAN controller or a RAN node, a message based on the at least one CLI value satisfying the thresholdvalue, and where the 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 processor refrains from transmitting a message based on the at least one CLI value failing to satisfy the threshold value, and where the 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 processor transmits a message including a reference signal based on the at least one CLI value satisfying the threshold value, and where the 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.

[0013] Additionally, or alternatively, to selectively perform the action for managing the CLI, the processor refrains from transmitting a message including a reference signal based on the at least one CLI value failing to satisfy the threshold value, and where the 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 processor transmits, using a transmission power that satisfies a transmit power threshold corresponding to the threshold value, a message including a reference signal based on the at least one CLI value satisfying the threshold value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the processor transmits, based on maintaining a transmission power, a message including a reference signal based on the at least one CLI value failing to satisfy 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, to detect the trigger event, the processor measures at least one RSRP value, and where the condition includes the at least one RSRP value satisfying a threshold value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the processor performs at least one actionbased on the at least one RSRP value satisfying the threshold value, and where the at least one action includes to reduce a transmission power associated with transmission of a message, to select one or more time-frequency resources for the transmission of the message, or to select a beam for the transmission of the message.

[0014] Additionally, or alternatively, to selectively perform the action for managing the CLI, the processor refrains from performing at least one action based on the at least one RSRP value failing to satisfy the threshold value, and where the at least one action includes to reduce a transmission power associated with transmission of a message, to select one or more time-frequency resources for the transmission of the message, or to select a beam for the transmission of the message. Additionally, or alternatively, to detect the trigger event, the processor receives a message indicating at least one CLI value associated with at least one CLI measurement, and where the condition includes the at least one CLI value satisfying a threshold value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the processor performs at least one action based on the at least one CLI value satisfying the threshold value, and where the at least one action includes to reduce a transmission power associated with transmission of an additional message, to select one or more time-frequency resources for the transmission of the additional message, or to select a beam for the transmission of the additional message. Additionally, or alternatively, to selectively perform the action for managing the CLI, the processor refrains from performing at least one action based on the at least one CLI value failing to satisfy the threshold value, and where the at least one action includes to reduce a transmission power associated with transmission of an additional message, to select one or more time-frequency resources for the transmission of the additional message, or to select a beam for the transmission of the additional message. Additionally, or alternatively, the at least one CLI value includes at least one of an RSRP, an RSSI, an SINR, or an RSRQ.

[0015] Additionally, or alternatively, to detect the trigger event, the processor receives a message indicating a metric indicative of a time-frequency resource usage, and where the condition includes the metric indicative of the time-frequency resource usage satisfying a threshold value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the processor transmits, to at least one of the RAN controller or a RAN node, an additional message that indicates the metric indicative of the time-frequency resource usage based on the metric indicative of thetime-frequency resource usage satisfying the threshold value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the processor refrains from transmitting, to at least one of the RAN controller or a RAN node, an additional message that indicates the metric indicative of the time-frequency resource usage based on the metric indicative of the time-frequency resource usage failing to satisfy the threshold value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the processor performs the action for managing the CLI, and transmits, to the RAN controller, a message that indicates the action for managing the CLI is performed.

[0016] Additionally, or alternatively, to detect the trigger event, the processor obtains at least one of at least one CLI value or at least one RSRP value, and where the at least one parameter is indicative of the trigger event. Additionally, or alternatively, to detect the trigger event, the processor performs at least one CLI measurement associated with the at least one CLI value according to a periodicity, and where the at least one parameter indicates the periodicity. Additionally, or alternatively, to detect the trigger event, the processor performs a set of CLI measurements to obtain the at least one CLI value, and where the at least one CLI value corresponds to at least one of an average CLI value of the set of CLI measurements or a maximum CLI value of the set of CLI measurements. Additionally, or alternatively, to detect the trigger event, the processor performs a set of CLI measurements to obtain a set of CLI values, and where the trigger event is detected based on a threshold numerical quantity of consecutive CLI values satisfying a threshold value, and where the at least one parameter indicates the threshold numerical quantity of consecutive CLI values. Additionally, or alternatively, to detect the trigger event, the processor performs a set of CLI measurements to obtain a set of CLI values, and where the trigger event is detected based on a threshold numerical quantity of CLI values in a threshold numerical quantity of consecutive CLI values satisfying a threshold value, and where the at least one parameter indicates the threshold numerical quantity of CLI values and the threshold numerical quantity of consecutive CLI values. Additionally, or alternatively, the subscription information includes at least one additional parameter that indicates a type of a message including the subscription information is a policy type. Additionally, or alternatively, the processor includes at least one of a base station, a CU, a DU, an E2 node, or an 01 node, and where the RAN controller includes at least one of an RIC, a near-real-time RIC, or a non-real-time RIC.

[0017] Some implementations of the method and apparatuses described herein may further include a method performed by a RAN node, the method including receiving (e.g., obtaining, retrieving), from a RAN controller, subscription information including at least one parameter indicative of a condition and an action for managing CLI based on the condition, detecting 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 being met in response to the trigger event.

[0018] In some implementations of the method and apparatuses described herein, detecting the trigger event further includes measuring at least one CLI value, and where the condition includes the at least one CLI value satisfying a threshold value. Additionally, or alternatively, selectively performing the action for managing the CLI further includes transmitting, to at least one of the RAN controller or an additional RAN node, a message based on the at least one CLI value satisfying the threshold value, and where the 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 further includes refraining from transmitting a message based on the at least one CLI value failing to satisfy the threshold value, and where the 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 further includes transmitting a message including a reference signal based on the at least one CLI value satisfying the threshold value, and where the 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.

[0019] Additionally, or alternatively, selectively performing the action for managing the CLI further includes refraining from transmitting a message including a reference signal based on the at least one CLI value failing to satisfy the threshold value, and where the 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 resourceassociated with the at least one CLI value. Additionally, or alternatively, selectively performing the action for managing the CLI further includes transmitting, using a transmission power that satisfies a transmit power threshold corresponding to the threshold value, a message including a reference signal based on the at least one CLI value satisfying the threshold value. Additionally, or alternatively, selectively performing the action for managing the CLI further includes transmitting, based on maintaining a transmission power, a message including a reference signal based on the at least one CLI value failing to satisfy 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, detecting the trigger event further includes measuring at least one RSRP value, and where the condition includes the at least one RSRP value satisfying a threshold value. Additionally, or alternatively, selectively performing the action for managing the CLI further includes performing at least one action based on the at least one RSRP value satisfying the threshold value, and where the at least one action includes to reduce a transmission power associated with transmission of a message, to select one or more time-frequency resources for the transmission of the message, or to select a beam for the transmission of the message.

[0020] Additionally, or alternatively, selectively performing the action for managing the CLI further includes refraining from performing at least one action based on the at least one RSRP value failing to satisfy the threshold value, and where the at least one action includes to reduce a transmission power associated with transmission of a message, to select one or more time-frequency resources for the transmission of the message, or to select a beam for the transmission of the message. Additionally, or alternatively, detecting the trigger event further includes receiving a message indicating at least one CLI value associated with at least one CLI measurement, and where the condition includes the at least one CLI value satisfying a threshold value. Additionally, or alternatively, selectively performing the action for managing the CLI further includes performing at least one action based on the at least one CLI value satisfying the threshold value, and where the at least one action includes to reduce a transmission power associated with transmission of an additional message, to select one or more time-frequency resources for the transmission of the additional message, or to select a beam for the transmission of the additional message. Additionally, or alternatively, selectively performing the action for managing the CLI further includes refraining from performing at least one action based on the at least one CLI value failing to satisfy thethreshold value, and where the at least one action includes to reduce a transmission power associated with transmission of an additional message, to select one or more time-frequency resources for the transmission of the additional message, or to select a beam for the transmission of the additional message. Additionally, or alternatively, the at least one CLI value includes at least one of an RSRP, an RS SI, an SINR, or an RSRQ.

[0021] Additionally, or alternatively, detecting the trigger event further includes receiving a message indicating a metric indicative of a time-frequency resource usage, and where the condition includes the metric indicative of the time-frequency resource usage satisfying a threshold value. Additionally, or alternatively, selectively performing the action for managing the CLI further includes transmitting, to at least one of the RAN controller or an additional RAN node, an additional message that indicates the metric indicative of the time-frequency resource usage based on the metric indicative of the time-frequency resource usage satisfying the threshold value. Additionally, or alternatively, selectively performing the action for managing the CLI further includes refraining from transmitting, to at least one of the RAN controller or an additional RAN node, an additional message that indicates the metric indicative of the time-frequency resource usage based on the metric indicative of the time-frequency resource usage failing to satisfy the threshold value. Additionally, or alternatively, selectively performing the action for managing the CLI further includes performing the action for managing the CLI and transmitting, to the RAN controller, a message that indicates the action for managing the CLI is performed.

[0022] Additionally, or alternatively, detecting the trigger event further includes obtaining at least one of at least one CLI value or at least one RSRP value, and where the at least one parameter is indicative of the trigger event. Additionally, or alternatively, detecting the trigger event further includes performing at least one CLI measurement associated with the at least one CLI value according to a periodicity, and where the at least one parameter indicates the periodicity. Additionally, or alternatively, detecting the trigger event further includes performing a set of CLI measurements to obtain the at least one CLI value, and where the at least one CLI value corresponds to at least one of an average CLI value of the set of CLI measurements or a maximum CLI value of the set of CLI measurements. Additionally, or alternatively, detecting the trigger event further includes performing a set of CLI measurements to obtain a set of CLI values, and where the trigger event is detected based on a threshold numerical quantity of consecutive CLI valuessatisfying a threshold value, and where the at least one parameter indicates the threshold numerical quantity of consecutive CLI values. Additionally, or alternatively, detecting the trigger event further includes performing a set of CLI measurements to obtain a set of CLI values, and where the trigger event is detected based on a threshold numerical quantity of CLI values in a threshold numerical quantity of consecutive CLI values satisfying a threshold value, and where the at least one parameter indicates the threshold numerical quantity of CLI values and the threshold numerical quantity of consecutive CLI values. Additionally, or alternatively, the subscription information includes at least one additional parameter that indicates a type of a message including the subscription information 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, and where the RAN controller includes at least one of an RIC, a near-real-time RIC, or a non-real-time RIC.

[0023] Some implementations of the method and apparatuses described herein may further include a RAN controller for wireless communication to transmit (e.g., output, send), to a RAN node, subscription information including at least one parameter indicative of a condition and an action for managing CLI based on the condition, and receive (e.g., obtain, retrieve), from the RAN node, an indication that the action for managing CLI is performed based on the condition being met in response to a trigger event, where the trigger event is associated with one or more of the condition or the action.

[0024] In some implementations of the method and apparatuses described herein, the trigger event includes the RAN node measuring at least one CLI value, and the condition includes the at least one CLI value satisfying a threshold value. Additionally, or alternatively, the indication 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, the indication includes a reference signal that 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 indication includes a reference signal associated with a transmission power that satisfies a transmit power threshold corresponding to the threshold value.

[0025] 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 trigger event includes the RAN node measuring at least one RSRP value, and the condition includes the at least one RSRP value satisfying a threshold value. Additionally, or alternatively, the indication is associated with at least one of a reduction in transmission power, one or more time-frequency resources, or a beam. Additionally, or alternatively, the trigger event includes the RAN node receiving a third message indicating at least one CLI value associated with at least one CLI measurement, and the condition includes the at least one CLI value satisfying a threshold value. Additionally, or alternatively, the indication is associated with at least one of a reduction in transmission power, one or more timefrequency resources, or to a beam. Additionally, or alternatively, the at least one CLI value includes at least one of an RSRP, an RSSI, an SINR, or an RSRQ.

[0026] Additionally, or alternatively, the trigger event includes the RAN node receiving a third message indicating a metric indicative of a time-frequency resource usage, and the condition includes the metric indicative of the time-frequency resource usage satisfying a threshold value. Additionally, or alternatively, the indication indicates the metric indicative of the time-frequency resource usage. Additionally, or alternatively, the at least one parameter is indicative of the trigger event, and where the trigger event includes at least one of obtaining at least one CLI value or obtaining at least one RSRP value. Additionally, or alternatively, the subscription information includes at least one additional parameter that indicates a type of a message including the subscription information 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, and where the RAN controller includes at least one of an RIC, a near-real-time RIC, or a non-real-time RIC.

[0027] Some implementations of the method and apparatuses described herein may further include a method performed by a RAN controller, the method including transmitting (e.g., outputting, sending), to a RAN node, subscription information including at least one parameter indicative of a condition and an action for managing CLI on the condition, and receiving, from the RAN node, an indication that the action for managing CLI is performed based on the condition being met in response to a trigger event, where the trigger event is associated with one or more of the condition or the action.

[0028] In some implementations of the method and apparatuses described herein, the trigger event includes the RAN node measuring at least one CLI value, and the condition includes the at least one CLI value satisfying a threshold value. Additionally, or alternatively, the indication 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, the indication includes a reference signal that 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 indication includes a reference signal associated with a transmission power that satisfies a transmit power threshold corresponding to the threshold value.

[0029] 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 trigger event includes the RAN node measuring at least one RSRP value, and the condition includes the at least one RSRP value satisfying a threshold value. Additionally, or alternatively, the indication is associated with at least one of a reduction in transmission power, one or more time-frequency resources, or a beam. Additionally, or alternatively, the trigger event includes the RAN node receiving a third message indicating at least one CLI value associated with at least one CLI measurement, and the condition includes the at least one CLI value satisfying a threshold value. Additionally, or alternatively, the indication is associated with at least one of a reduction in transmission power, one or more timefrequency resources, or to a beam. Additionally, or alternatively, the at least one CLI value includes at least one of an RSRP, an RSSI, an SINR, or an RSRQ.

[0030] Additionally, or alternatively, the trigger event includes the RAN node receiving a third message indicating a metric indicative of a time-frequency resource usage, and the condition includes the metric indicative of the time-frequency resource usage satisfying a threshold value. Additionally, or alternatively, the indication indicates the metric indicative of the time-frequency resource usage. Additionally, or alternatively, the at least one parameter is indicative of the trigger event, and where the trigger event includes at least one of obtaining at least one CLI value or obtaining at least one RSRP value. Additionally, or alternatively, the subscription information includes at least one additional parameter that indicates a type of a message including thesubscription information 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, and 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

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

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

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

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

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

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

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

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

[0039] Figure 17 illustrates a flowchart of a method performed by a RAN controller in accordance with aspects of the present disclosure.DETAIEED DESCRIPTION

[0040] A wireless communications system may implement a framework including one or more devices and interfaces supporting exchange (e.g., transmission, reception, output) of signaling for a RAN. For example, the framework may include one or more RAN nodes communicating with aRAN 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.

[0041] A UE and a RAN node can transmit or receive signaling using communication resources. For example, the UE and / or the RAN node may split (e.g., allocate, distribute) communication resources between uplink transmissions and downlink transmissions in the time domain, which may be referred to as a TDD communication scheme. In the TDD communication scheme, transmission and reception of signals occur at different times within a same frequency band. Different time resources within a transmission frame, which may be referred to as time slots and may be further divided into symbols, may be allocated to uplink and / or downlink transmissions. In some examples, the uplink and downlink resource allocation are synchronized across RAN nodes to avoid interference from one RAN node (e.g., when transmitting a downlink transmission) to another nearby RAN node (e.g., when receiving an uplink transmission). 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 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 RAN node may be transmitting signaling with a transmission beam that is spatially directed towards a nearby RAN node while the nearby RAN node is receiving different signaling in a same frequency band. The other RAN node may receive a portion of the signaling transmitted by the RAN node 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.

[0042] 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 RAN node may receive uplink signaling from one or more UEs using a sub-band of a frequency band, while another RAN node concurrently (e.g., within a same duration of symbols or within a same slot) transmits downlink signaling to one or more UEs using a different sub-band of the frequency band. SBFD operation might induce additional interference between RAN nodes if a RAN node transmits downlink signaling with a transmission beam directed spatially towards another RAN node while the other RAN node is receiving uplink signaling on the same time-frequency 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.

[0043] As described herein, to reduce CLI in a wireless communications system, a RAN controller may exchange signaling with one or more RAN nodes to coordinate CLI measurement and CLI management at the RAN nodes. 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. In response, the RAN node 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, as indicated by the rule. For example, the RAN node may report one or more CLI values to the RAN controller and / or to another RAN node, may update one or more communication parameters (e.g., reduce a transmission power, select one or more time-frequency 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.

[0044] Aspects of the present disclosure are described in the context of a wireless communications system.

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

[0046] 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, 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 fiberoptic cable, among other examples.

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

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

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

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

[0051] 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 mobilitymanagement 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.

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

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

[0054] 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 cyclicprefix. 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.

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

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

[0057] 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) (410megahertz (MHz) - 7.125 gigahertz (GHz)), frequency range 1 (FR2) (24.25 GHz - 52.6 GHz), frequency range 3 (FR3) (7.125 GHz - 24.25 GHz), frequency range 4 (FR4) (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and frequency range 5 (FR5) (114.25 GHz - 300 GHz). In some implementations, the NEs 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data). In some implementations, FR2 may be used by the NEs 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.

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

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

[0060] In some examples, an antenna panel may be virtualized as an antenna port. In some other examples, an antenna panel 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 a number of antenna panels, a duplexing capability of the device, beamforming capabilities of thedevice, and so on, may or may not be transparent to other devices. In some examples, capability information may be communicated via signaling. In some other examples, the capability information may be provided to devices without signaling. If the capability information is available to other devices, such as a CU, then the capability information can be used for signaling or local decision making.

[0061] 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 (e.g., greater than a threshold) of an RF chain (e.g., in-phase / quadrature (I / Q) modulator, analog to digital (A / D) converter, local oscillator, phase shift network). The antenna panel may be a logical entity with physical antennas mapped to the logical entity. The mapping of physical antennas to the logical entity may be up to implementation. Communicating (e.g., receiving or transmitting) on at least a subset of antenna elements or antenna ports active for radiating energy, also referred to herein as active elements, of an antenna panel includes biasing or powering on of the RF chain, which results in current drain or power consumption at the device (e.g., node) associated with the antenna panel (e.g., including power amplifier / low noise amplifier (LNA) power consumption associated with the antenna elements or antenna ports). The phrase “active for radiating energy,” as used herein is not limited to a transmit function but also encompasses a receive function. Accordingly, an antenna element that is active for radiating energy may be coupled to a transmitter to transmit RF energy or to a receiver to receive RF energy, either simultaneously or sequentially, or may be coupled to a transceiver for performing intended functionality. Communicating on the active elements of an antenna panel enables generation of radiation patterns or beams.

[0062] In some examples, 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 or 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 a mapping between physical antennas of a device to a logical entity panel may not change. For example, the condition may include until the next update or report from a 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 leastthe number of panels. In some examples, the device may support transmission from one beam within a panel. In some cases, such as for devices with multiple panels, a device may use more than one beam (e.g., one beam per panel) for transmission. In some other examples, a device may support and / or use more than one beam per panel for transmission.

[0063] In some examples, a channel over which a symbol on an antenna port is conveyed can be inferred from a channel over which another symbol on the same antenna port is conveyed. Two antenna ports are said to be quasi co-located (QCL) if 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 thereference signals A and B can be received with the same spatial filter (e.g., with the same receive beamforming weights).

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

[0065] 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 sounding reference signal (SRS)) with respect to QCL type parameters indicated in the corresponding TCI state. The TCI state describes which reference signals are used as a 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.

[0066] 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 or 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 isconfigured 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.

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

[0068] 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 theuplink spatial transmission filter. The source reference signal determined from the indicated joint, or common, TCI state provides QCL Type-D indication (e.g., for device-dedicated PDCCH and / or PDSCH) and is used to determine uplink spatial transmission filter (e.g., for UE-dedicated PUSCH and / or PUCCH) for a CC or across a set of configured CCs and / or BWPs. In one example, the uplink spatial transmission filter is derived from the reference signal of downlink QCL Type D in the joint TCI state. The spatial setting of the uplink transmission may be according to the spatial relation with a reference to the source reference signal configured with QCL type set to ‘QCL- typeD’ in the joint TCI state.

[0069] 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, which is described in further detail with respect to Figure 2. In some examples, to reduce CLI between NEs 102 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. For example, a RAN controller may transmit a message indicating subscription information to an NE 102. The subscription information may include one or more parameters that indicate rules for CLI management and a parameter that indicates the subscription information is for a policy type of subscription.

[0070] In some examples, the rules (e.g., policy rules) 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. In response, the RAN node 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, as indicated by the rule. For example, the RAN node may report one or more CLI values to the RAN controller and / or to another RAN node, may update one or more communication parameters (e.g., reduce a transmission power, select one or more time-frequency resources for a transmission, and / or select a beam for a transmission), and / or may transmit areference signal. In some examples, the RAN node may transmit a report to the RAN controller upon execution of an action according to a rule.

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

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

[0073] 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 RANnode 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.

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

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

[0076] To mitigate, or reduce, remote interference, a network (e.g., the CNs 106) may enable RIM frameworks for coordination between RAN nodes. The coordination communication in RIM frameworks can be wireless-based and / or backhaul-based. The backhaul-based RIM framework uses any combination of wireless interfaces and backhaul interfaces for signaling, while in the wireless framework, the communication is via wireless interfaces (e.g., over the air). Backhaul interfaces may be examples of wired interfaces. In both frameworks, RAN nodes that are being interfered with may simultaneously transmit an identical RIM reference signal carrying the set identifier for the interfered RAN nodes over the air. In the wireless framework, upon reception of the RIM reference signal from the set for the interfered RAN nodes, interfering RAN nodes undertake RIM measures, andmeasures 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.

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

[0078] 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 CLI 210 from a transmission between the UE 104-a and the RAN node 202-a. Additionally, or alternatively, the RAN node 202-a may experience 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.

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

[0080] In some examples, the RAN node 202-a, the RAN node 202-b, the UE 104-a, and / or the UE 104-b may implement SBFD operation, where multiple wireless devices may be configured or operable to transmit uplink signals in a sub-band using symbols allocated for a downlink transmission, or vice-versa. In some examples, multiple wireless devices within a cell (e.g., a coverage area of a RAN node) implementing SBFD operation may result in 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 CLI 210 at for the downlink signal.

[0081] 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 measure the SRS and report one or more measurements, such as an RSRP of the SRS (SRS-RSRP), to a serving base station (e.g., the RAN node 202-a). In some examples, an SRS-RSRP may be defined as a linear average of a power contribution (e.g., in watts) of resource elements carrying SRSs. The SRS-RSRP is measured over configured resource elements 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.

[0082] In some cases, the UE 104-a may be configured to measure an RSSI for 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 non-serving 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.

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

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

[0085] 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 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 maybe 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) CSI-RSs and / or zero power (ZP)-CSI-RSs, 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 CSI-RS 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 resource elements (RE) and / or resource block (RB) muting patterns).

[0086] In some examples, the CNs 106 (e.g., a RAN controller) may introduce a framework for managing 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 12. 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.

[0087] 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 asdescribed with reference to Figures 1 and 2. For example, the RAN architecture diagram 300 may illustrate examples of interfaces between different RAN nodes, such as a base station, a CU of a base station, a DU of a base station, and a control entity or RAN controller. The control entity may be an example of a near-real-time RIC 302 and / or a non-real-time RIC 304. Although Figure 3 illustrates an example of an 0-RAN architecture, aspects of the methods, systems, and apparatuses as described herein may be implemented in the context of additional, or alternatively, network architectures.

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

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

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

[0091] 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 beimplemented 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.

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

[0093] 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 a RAN controller 502 and a RAN node 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.

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

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

[0096] 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), asubsequent 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.

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

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

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

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

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

[0102] 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 theRAN 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.

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

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

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

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

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

[0108] 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 what triggers 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 504 and / or a CN (e.g., for network functions). An associated service model may support a RAN node 504 (e.g., a base station, a CU at a base station, and / or a DU at a base station). The RAN node 504 may host a RAN function “KPM Monitor” performing functionalities, such as exposure of available measurements from the RAN node 504, and / or reporting of measurements subscribed from a RAN controller 502, among other functionalities. The “KPM monitor” RAN function may provide REPORT services, such as measurements by a RAN node 504, measurements for a UE or a group of UEs, UE-specific condition-based measurements, and / or common condition-based measurements, among otherservices. 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 504), information of the condition that triggered the KPM signaling, information of a status of the RAN node 504, 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.

[0109] In some examples, the subscription information may indicate for the RAN node 504 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 504 may measure CLI (e.g., may obtain one or more CLI values). For example, the RAN node 504 may determine a periodicity timer is expired, which may trigger CLI reporting.

[0110] In some examples, the RAN controller 502 may indicate, through the subscription procedure signaling, information on what CLI measure for the RAN node 504 to include in the CLI reporting. For example, the RAN controller 502 may indicate to the RAN node 504 to report an RSSI as a measure of CLI. The RAN controller 502 may further indicate resources on which the RSSI is to be measured. The RAN controller 502 may indicate to a first set of RAN nodes, including the RAN node 504, 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 504 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 502 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, resourcesassociated 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.

[0111] In some examples, the RAN controller 502 may indicate to the RAN node 504 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 502 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.

[0112] 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 the subscription procedure signaling. The OCTET STRING may then be decoded by the RAN node 504 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 502 may indicate to the RAN node 504 to report an RSSI, an SINR, an RSRQ, and / or an RSRP as a measure of CLI.

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

[0114] In some other examples, the RAN controller 502 may indicate for the RAN node 504 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 504 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 504 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 502 may indicate to the RAN node 504 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 502 may indicate to the RAN node 504 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 502 may indicate to the RAN node 504 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 504 through the subscription procedure signaling, configured by the network, preconfigured, or otherwise defined, determined by implementation, or any combination thereof.

[0115] In some examples, the CLI report may be used for taking a CLI mitigation action. For example, the RAN controller 502 may make use of a CONTROL service signaling to indicate to the RAN node 504, or other RAN nodes a threshold distance from the RAN node 504, 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 refrainingfrom communicating using one or more beams that cause excessive CLI, avoiding or refraining from communicating using a set of time-frequency resources, such that another RAN node may use the set of time-frequency resources for communications without experiencing excessive CLI, or any combination thereof.

[0116] In some examples, a CLI report from a RAN node 504 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 504 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 504 or a UE served by the RAN node 504. The RAN node 504 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 504 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 504 may determine the value of T from information indicated in the subscription procedure, configured by the network and / or 0AM, determined according to a signal strength associated with the signal or the UE experiencing the CLI, determined based on an implementation, or any combination thereof. In some examples, the RAN node 504 may indicate the threshold value in the CLI report or other signaling. The RAN node 504 may round the value of Y to the nearest value in an enumerated set as configured or specified. In some examples, the RAN controller 502 may use the value of Y, as reported by a RAN node 504, 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).

[0117] In some examples, the parameters include an indication of associated beams. For example, the RAN node 504 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.

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

[0119] 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 12. The subscription procedure messages may include one or more of an indication of a reporting action (e.g., Action = POLICY).

[0120] 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 / or the signaling diagram 500. The signaling diagram 600 may illustrate an example of a framework defining one or more rules or conditions for CLI management between a RAN controller 602 and a RAN node 604. The RAN controller 602 and the RAN node 604 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.

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

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

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

[0124] 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 CLI management policy to be executed at the RAN node 604. The subscription procedure messages may include one or moreof 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.

[0125] At 612, the RAN node 604 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 may determine whether the one or more events are triggered (e.g., one or more conditions associated with the events are satisfied).

[0126] At 614, the RAN node 604 may perform an action according to the policy rule. For example, if the events are triggered, then the RAN node 604 may take the one or more actions as indicated by the rule. At 616, the RAN node 604 may continue an associated procedure. For example, if the RAN node 604 is configured with a reporting procedure, then the RAN node 604 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 takes an action according to a policy rule.

[0127] In some examples, at 618, the RAN node 604 may transmit action reporting signaling 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 POLICY service, 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.

[0128] 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 thesignaling diagram 600. The signaling diagram 700 may illustrate an example of a framework defining one or more rules or conditions for CLI management between a RAN controller 702 and a RAN node 704. The RAN controller 702 and the RAN node 704 may be examples of corresponding devices (e.g., a RAN node 202 and a CN 106, respectively) as described with reference to Figures 1 through 4. Alternative examples of the following may be implemented, where some processes are performed in a different order than described or are not performed. In some cases, processes may include additional features not mentioned below, or further processes may be added.

[0129] 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, including, but not limited to, CLI management processes.

[0130] 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 other services in a same or separate subscriptions. A POLICY service provided by the RAN or converged RAN-CN may be used for 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.

[0131] At 710, the RAN node 704 may detect an event trigger. At 712, the RAN node 704 may test one or more event trigger conditions. For example, a POLICY service may implement one or more of triggering events, actions, or RAN parameters. For example, 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 thelike. The RAN parameters may include one or more parameters to be controlled by the RAN controller 602 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 610, 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 604 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 602, 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.

[0132] In some examples, a triggering event may be of type message event. The RAN node 604 may determine that an event is triggered (e.g., a trigger event condition is satisfied) upon receiving a message. While the RAN node 604 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 602 (e.g., an indication message including a report or a message copy), a message from another RAN node 604 on a network interface (e.g., a message on an Xn interface including an IE), a message from a UE (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 604 over-the-air. In some other examples, a triggering event may be of type call process breakpoint. The RAN node 604 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 604 (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 604.

[0133] In some other examples, a triggering event may be of type RAN node information change. The RAN node 604 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 604. If no change in information associated with the RAN node 604 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 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 604 may determine that an event is triggered (e.g., a trigger event condition is satisfied) upon detecting a change in information associated with a UE connected to the RAN node 604. 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, a change of L1 / L2 communication parameters associated with the UE, a higher-layer change associated with the UE, a mobility change associated with the UE, or a UE identifier changed or removed.

[0134] In some examples, testing the event trigger conditions may include determining the event trigger conditions are satisfied for a detected event trigger. At 714, the RAN node 604 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.

[0135] At 716, the RAN node 604 may determine an action based on a policy rule. For example, if the conditions are satisfied, then the RAN node 604 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 (e.g., is not indicative of a satisfactory performance of the network). Examples of actions by the RAN node 604 include, but are not limited to, reducing a transmission power to reduce or mitigate CLI, constraining communications on a resource or beam to mitigate CLI, sending a message including a CLI value to the RAN controller 602, sending a message including a CLI value to another RAN node 604, 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, lifting a criteria for communications on aresource or beam when the communications do not cause excessive CLI, modifying a subscription or configuration. A policy rule may be indicated to the RAN node 604 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 / OAM, 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. Various RAN parameters may pertain to triggering events, conditions, actions, among others.

[0136] 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 604 to determine whether to execute an associated policy actions. If a policy condition is not met, the RAN node 604 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.

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

[0138] At 722, the RAN node 604 may execute the action. For example, the RAN node 604 may execute an action based on the policy rule based on the determination at 716 (e.g., if the trigger event condition is satisfied and the condition is satisfied). Additionally, or alternatively, the RAN node 604 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.

[0139] Figure 8 illustrates an example of signaling diagram 800 in accordance with aspects of the present disclosure. In some examples, the signaling diagram 800 may implement aspects of the wireless communications system 100, the wireless communications system 200, the RAN architecture diagram 300, the RAN layer diagram 400, the signaling diagram 500, the signalingdiagram 600, and / or the signaling diagram 700. The signaling diagram 800 may illustrate an example of a framework defining one or more rules or conditions for CLI management between a RAN controller 802 and a RAN node 804. The RAN controller 802 and the RAN node 804 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.

[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 804, including, but not limited to, CLI management processes.

[0141] At 808, the RAN controller 802 and the RAN node 804 may exchange one or more messages for a subscription procedure with a type of POLICY, as described with reference to Figure 6. For example, the subscription procedure may indicate one or more of a trigger event, an action, and / or one or more RAN parameters.

[0142] In some examples, at 810, the RAN node 804 may detect an event trigger based on measuring one or more CLI values. For example, the POLICY service may be implemented to report an excessive CLI to a RAN controller 802. The RAN controller 802 and / or the RAN node 804 may perform subscription procedure signaling that indicates one or more of for the RAN node 804 to perform a measurement to obtain a CLI value, 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 802.

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

[0144] In some cases, at 816, the RAN node 804 may transmit a report indicating CLI to the RAN controller 802. 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 may report an excessive CLI).

[0145] In variations, a policy rule may be indicated to the RAN node 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 obtaining a CLI measurement. In response, the RAN node 804 may detect an event trigger each time, or some of the times, that the RAN node 804 obtains a CLI measurement. Obtaining a CLI measurement may include measuring a CLI value, computing a CLI value, receiving a message including a CLI value, or the like. The CLI value may be an RSRP, CSLRSRP, SSB-RSRP, SRS- RSRP, RSRQ, RSSI, CLI-RSSI, or the like. The first RAN parameter may indicate a reference signal (e.g., CSLRS, SSB) to obtain an RSRP (e.g., CSLRSRP, SSB-RSRP) or resources to obtain an RSSI. The first RAN parameter may further indicate how to obtain the CLI value, as described with reference to Figure 5.

[0146] 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, CSL RSRP, SSB-RSRP, SRS-RSRP, RSRQ, RSSI, CLI-RSSI, or the like). Additionally, or alternatively, the third RAN parameter may indicate to the RAN node 804 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, or any combination thereof. A fourth RAN parameter may indicate the action of reporting a KPM to a RAN controller 802. An identifier and / or address of the RAN controller 802 may further be indicated to the RAN node 804. A fifth RAN parameter may indicatethat the KPM is the CLI value obtain earlier (e.g., an RSRP, CSI-RSRP, SSB-RSRP, SRS-RSRP, RSRQ, RSSI, CLI-RSSI, or the like). Additionally, or alternatively, the fifth RAN parameter may indicate for the RAN node 804 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 Figure 5. A sixth RAN parameter may indicate at least one of a default action or no action if the policy condition is not satisfied.

[0147] 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 the signaling diagram 800. The signaling diagram 900 may illustrate an example of a framework defining one or more rules or conditions for CLI management between a RAN controller 902 and one or more RAN nodes 904 (e.g., a RAN node 1 and a RAN node 2). The RAN controller 902 and the RAN nodes 904 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.

[0148] In some examples, although the signaling diagram 900 illustrates two RAN nodes 904, the processes may be performed by any numerical quantity of RAN nodes 904 (e.g., one RAN node 904, more than two RAN nodes 904). For example, the processes described as being performed by the RAN node 1 may additionally, or alternatively, be performed by the RAN node 2.

[0149] At 906, the RAN node 1, the RAN controller 902, and / or the RAN node 2 may perform initial processes. The initial processes may be for a subscription procedure, including exchanging signaling related to the subscription procedure.

[0150] At 908, the RAN controller 902 and the RAN node 1 may perform a subscription procedure with a type of POLICY. For example, the RAN controller 902 and the RAN node 1 may exchange signaling, as described with reference to Figures 5 through 8. The subscription proceduremay include one or more of a subscription signaling, a subscription modification signaling, and the like. The RAN controller 902 may transmit, in one or more messages in the subscription procedure, information indicating one or more policy rules, trigger events, and / or RAN parameters for CLI management. The subscription procedure signaling may indicate for the RAN node 1 to perform a measurement to obtain a CLI value, to compare the CLI value to a threshold value, and if the CLI value satisfies the threshold value (e.g., exceeds or is above the threshold value), then to report one or more CLI values (e.g., excessive CLI, CLI measurements, average CLI, etc.) to another RAN node 904 (e.g., RAN node 2).

[0151] In some examples, the subscription procedure signaling may indicate one or more RAN parameters. For example, the subscription procedure signaling may indicate a first RAN parameter with a value indicating that the event trigger is obtaining a CLI measurement. In response, at 910, the RAN node 1 may detect an event trigger based on measuring CLI values. For example, the RAN node 1 may detect an event trigger every time, or some of the times, that the RAN node 1 obtains a CLI measurement. Obtaining a CLI measurement may include measuring a CLI value, computing a CLI value, receiving a message including a CLI value, or the like. The CLI value may be an RSRP, CSLRSRP, SSB-RSRP, SRS-RSRP, RSRQ, RSSI, CLI-RSSI, or the like. The first RAN parameter may indicate a reference signal (e.g., CSLRS, SSB) to obtain an RSRP (e.g., CSLRSRP, SSB- RSRP) or resources to obtain an RSSI. The first RAN parameter may further indicate how to obtain the CLI value.

[0152] Additionally, or alternatively, the subscription procedure signaling may include a second RAN parameter with a value that indicates that the event trigger condition is a CLI value (e.g., obtained at 910) satisfying a threshold value. Satisfying the threshold value may include the CLI value being greater than, or exceeding, the 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, a CSLRSRP threshold, an SSB-RSRP threshold, an SRS- RSRP threshold, an RSRQ threshold, an RSSI threshold, a CLLRSSI threshold, or the like). Additionally, or alternatively, the value of the third RAN parameter may indicate to the RAN node 1 to obtain the threshold value according to a preconfigured or defined value, a configuration by the network and / or an 0AM, an implementation, a condition of the cells provided by the RAN node 1 , or any combination thereof.

[0153] Additionally, or alternatively, the subscription procedure signaling may include a fourth RAN parameter with a value that indicates the action of reporting a KPM to one or more other RAN nodes 904 (e.g., the RAN node 2) and / or other NEs. The address of the RAN nodes 904 and / or other NEs may further be indicated to the RAN node 1. In some cases, the value of the fourth RAN node parameter indicates another RAN node 904 (e.g., the RAN node 2) via an identifier and / or address associated with the RAN node 904. The other RAN node (e.g., the RAN node 2) may be associated with the reference signal (e.g., CSI-RS, SSB) measured to obtain the CLI value. In some other cases, multiple other RAN nodes 904 may be indicated via a sequence of identifiers and / or addresses associated with the RAN nodes 904 or a group identifiers and / or addresses associated with the group of RAN nodes 904. In some other cases, 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.

[0154] Additionally, or alternatively, the subscription procedure signaling may include a fifth RAN parameter with a value that indicates that the KPM is the CLI value obtain by the RAN node 1 at 910 (e.g., an RSRP, CSI-RSRP, SSB-RSRP, SRS-RSRP, RSRQ, RSSI, CLI-RSSI, or the like). Additionally, or alternatively, the value of the fifth RAN parameter may indicate 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. 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.

[0155] In some cases, at 912, 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 914, 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.

[0156] In some cases, at 916, the RAN node 1 may transmit a report indicating CLI to the RAN node 2. Additionally, or alternatively, the RAN node 1 may transmit the report indicating CLI to one or more additional RAN nodes (e.g., in addition to, or as an alternative to, the RAN node 1) and / or to the RAN controller 902. The signaling indicating the CLI may be an example of CLI reporting, as described with reference to Figure 5.

[0157] 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 framework for CLI management between a RAN controller 1002 and one or more RAN nodes 1004 (e.g., a RAN node 1 and a RAN node 2). The RAN controller 1002 and the RAN nodes 1004 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.

[0158] In some examples, although the signaling diagram 1000 illustrates two RAN nodes 1004, the processes may be performed by any numerical quantity of RAN nodes 1004 (e.g., one RAN node 1004, more than two RAN nodes 1004). For example, the processes described as being performed by the RAN node 1 may additionally, or alternatively, be performed by the RAN node 2.

[0159] At 1006, the RAN node 1, the RAN controller 1002, and / or the RAN node 2 may perform initial processes. The initial processes may be for a subscription procedure, including exchanging signaling related to the subscription procedure.

[0160] At 1008, the RAN controller 1002 and the RAN node 1 may perform a subscription procedure with a type of POLICY. For example, the RAN controller 1002 and the RAN node 1 may exchange signaling, as described with reference to Figure 5. The subscription procedure may include one or more of a subscription signaling, a subscription modification signaling, and the like. The RAN controller 902 may transmit, in one or more messages in the subscription procedure, information for CLI management by the RAN node 1. The subscription procedure signaling may indicate for the RAN node 1 to receive an indication of excessive CLI from a RAN controller 1002, another RAN node, or any combination thereof, to determine whether a CLI value satisfies a threshold value (e.g., exceeds the threshold value), and to take an action to mitigate the CLI based on the CLI value (e.g., to reduce a transmission power associated with a signal or channel thatcauses the CLI, to constrain the use of a set of resources associated with the CLI, constrain the use of one or more beams that cause the CLI).

[0161] In some examples, the RAN controller 1002 performs subscription procedure signaling with a RAN node 2 (e.g., the RAN node experiencing the CLI) and a RAN node 1 (e.g., the RAN node causing the CLI). For example, the RAN controller 1002 and the RAN node 2 perform subscription procedure signaling, as described with reference to Figure 5. The RAN controller 1002 and the RAN node 1 perform subscription procedure signaling. In some examples, the RAN node 2 detects an excessive CLI and reports the excessive CLI to the RAN controller 1002 (e.g., as part of a REPORT subscription procedure, as part of a POLICY subscription procedure, as described with reference to Figures 6 through 9, and / or in other CLI reporting signaling). At 1010, the RAN controller 1002 transmits a report to the RAN node 1 indicating one or more CLI values. For example, the report indicates to the RAN node 1 that an excessive CLI is detected. In response, the RAN node 1 may take a CLI mitigation action.

[0162] In some other examples, the RAN controller 1002 performs subscription procedure signaling with a RAN node 2 and a RAN node 1. The RAN controller 1002 and the RAN node 2 perform subscription procedure signaling, as described with reference to Figure 5. The RAN controller 1002 and the RAN node 1 perform subscription procedure signaling. The RAN node 2 detects an excessive CLI and reports the excessive CLI to the RAN node 1. For example, at 1012, the RAN node 2 transmits a report to the RAN node 1 indicating one or more CLI values. For example, the report indicates to the RAN node 1 that an excessive CLI is detected. In response, the RAN node 1 determines whether to take a CLI mitigation action.

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

[0164] In some examples, the subscription procedure signaling at 1008 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 RSRP, CSLRSRP, SSB-RSRP, SRS-RSRP, RSRQ, RSSI, CLI-RSSI, or the like). The first RAN parameter may indicate a reference signal (e.g., CSLRS, SSB) from which an RSRP (e.g., CSI-RSRP, SSB- RSRP) is obtained or resources from which an RSSI (e.g., CLI-RSSI) is obtained.

[0165] 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 may determine a value of excess CLI. The threshold may be an RSRP threshold value, a CSI-RSRP threshold value, an SSB-RSRP threshold value, an SRS-RSRP threshold value, an RSRQ threshold value, an RSSI threshold value, a CLI-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 1 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 2 and / or the RAN controller 1002 at 1012 and 1010, respectively, may indicate a value of excess CLI explicitly, in which case the RAN node 1 may not compare the CLI value to a threshold value to determine whether the CLI is excessive. That is, the report indicating CLI at 1010 and 1012 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.

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

[0167] In some examples, a policy rule for CLI management may indicate to the RAN node 1 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 1 that the CLI can be mitigated byreducing a transmission power. In some cases, the report indicating CLI may include an amount of excess CLI, for example X dB. In response, the RAN node 1 may reduce the transmission power for downlink signals and / or channels by X dB. The RAN node 1 may respond by transmitting a message to the RAN controller 1012 and / or to the RAN node 2 including an indication that the RAN node 1 reduced the transmission power and / or the signals or channels on which the transmission power reduction is applied.

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

[0169] In some examples, an amount of power reduction may be indicated through the subscription procedure signaling. For 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 1 may reduce the transmission power by X dB on all or some signals and / or channels upon receiving a report indicating CLI that requests a transmission power reduction (e.g., without an explicit indication of X dB). In some other examples, a sequence of power reduction values [XI, X2, ...] or a sequence of transmission powers [Pl, P2, ...] may be indicated through the subscription procedure signaling (e.g., one or more parameters in subscription information). Then, the RAN node 1 may reduce the transmission power by X[i] dB or reduce the transmission power from P[z] to P[z- 1] (or P[z+1]), on all or some signals and / or channels, where the index z may be decremented or incremented by the RAN node 1 upon applying an associated policy rule.

[0170] In some cases, a minimum and / or maximum transmission power may be preconfigured or defined, configured by the operator, indicated through the subscription procedure, and / or determined by implementation. If the RAN node 1 is requested to reduce the transmission power to less than the minimum, then the RAN node 1 may decline the request fully or partially and respond by sending a message to the RAN controller 902 and / or to the RAN node 2. In some other cases, the RAN node 1 may determine that the CLI can be mitigated by avoiding communications through one or more beams. The RAN controller 902 and / or the RAN node 2 may indicate beams that causeexcessive CLI in another cell. In response, the RAN node 2 may avoid or refrain from communicating using the indicated beams and / or cancel communications scheduled for the indicated beams. The RAN node may respond by transmitting a message including an indication that communications on the beams, or the subset of the beams, are constrained. In variations, a beam may be indicated by a synchronization signal and / or SSB index, reference signal identifier, reference signal resource indicator, QCL relationship, TCI, direction, or the like.

[0171] In some cases, the RAN node 1 may determine that the CLI can be mitigated by avoiding or refraining from communicating using one or more communication resources. In some examples, the RAN node 1 may avoid or refrain from communicating on the resources or a subset of the resources. The RAN node 1 may respond by sending a message to the RAN controller 1002 and / or the RAN node 2 including an indication that communication on the resources, or the subset of the resources, 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.

[0172] In variations, the RAN 1 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, at 1014, the RAN node 1 may detect event trigger based on receiving the report indicating the CLI (e.g., from the RAN controller 1002 and / or from the RAN node 2). At 1016, if the reported CLI satisfies a threshold value, then the RAN node 1 may determine an amount of excessive CLI. That is, the RAN node 1 may determine a difference between a CLI value reported at 1010 and / or at 1012 and a threshold value. At 1018, the RAN node 1 may determine one or more communicationparameters 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 1020, if the RAN node 1 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 1 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, such as maintaining a transmission power for a transmission.

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

[0174] In some examples, such as to reduce, or prevent, the underutilization of communication resources, a RAN node 1 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 ora constraint for using beams or resources, but a RAN node 1 may not know when to revert to an original transmission power or use of beams or resources. The RAN node 1 may reverse a transmission power reduction, fully or partially, if the RAN node 1 does not receive control signaling for a duration. In some examples, the RAN node 1 may increase the transmission power by Y dB, where Y dB is an amount of transmission power reduction according to an earlier CLI mitigation action, which may be referred to as a full reversal of power reduction. In some other examples, the RAN node 1 may increase the transmission power 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 1 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.

[0175] In variations, the RAN node 1 may reverse a constraint on using beams or resources, fully or partially, if the RAN node 1 does not receive control signaling for a duration. A full reversal may be realized by using the beams or resources for subsequent communications. A partial reversal may be realized by using a subset or the beams or resources for subsequent communications. The RAN node 1 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 1 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 may be interpreted as reducing the transmission power to zero on the beam or resource. Therefore, the RAN node 1 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 1 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 1 may proceed with further increasing the transmission power on the beam or resource. The RAN node 1 may repeat the process of gradually increasing the transmission power until the RAN node 1 receives control signaling that indicates an excess CLI on the beam or resource and / or until the RAN node 1 reverts the transmission power to a transmission power used prior to performing the CLI management action.

[0176] In some examples, a capability of the RAN node 1 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 1 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 / 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 1002. For example, if the RAN controller 1002 does not receive an excess CLI report from the RAN node 2 for a duration, then the RAN controller 1002 may perform one or more control signaling procedures with the RAN node 1 to provide for the RAN node 1 to increase a reduced transmission power, use a constrained beam or resource, or both.

[0177] At 1022, the RAN node 1 may execute the action. For example, the RAN node 1 may execute the action determined at 1018 or at 1020.

[0178] 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 framework defining one or more rules or conditions for CLI management between a RAN controller 1102 and one or more RAN nodes 1104 (e.g., a RAN node 1 and a RAN node 2). The RAN controller 1102 and the RAN nodes 1104 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.

[0179] In some examples, although the signaling diagram 1100 illustrates two RAN nodes 1104, the processes may be performed by any numerical quantity of RAN nodes 1104 (e.g., one RAN node 1104, more than two RAN nodes 1104). For example, the processes described as being performed by the RAN node 1 may additionally, or alternatively, be performed by the RAN node 2.

[0180] At 1106, the RAN node 1, the RAN controller 1102, and / or the RAN node 2 may perform initial processes. The initial processes may be for a subscription procedure, including exchanging signaling related to the subscription procedure.

[0181] At 1108, the RAN controller 1102 and the RAN node 1 may perform a subscription procedure with a type of POLICY. For example, the RAN controller 1102 and the RAN node 1 may exchange signaling, as described with reference to Figures 5 through 10. The subscription procedure may include one or more of a subscription signaling, a subscription modification signaling, and the like. The RAN controller 1102 may transmit, in one or more messages in the subscription procedure, information indicating one or more policy rules, trigger events, and / or RAN parameters for CLI management. The subscription procedure signaling may indicate for the RAN node 1 to perform a measurement to obtain a CLI value, compare the CLI value with a threshold, an if the CLI value is above the threshold, then to transmit an associated reference signal as an indication of excessive CLI, or to increase the power of an associated reference signal by the amount of the excess CLI.

[0182] 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 obtaining a CLI measurement. In response, the RAN node 1 may detect an event trigger every time, or some of the times, that RAN node 1 obtains a CLI measurement. For example, at 1110, the RAN node 1 may detect an event trigger based on measuring one or more CLI values. Obtaining a CLI measurement may include measuring a CLI value, computing a CLI value, receiving a message including a CLI value, or the like. The CLI value may be an RSRP, CSLRSRP, SSB-RSRP, SRS-RSRP, RSRQ, RSSI, CLI-RSSI, or the like. The first RAN parameter may indicate a reference signal (e.g., CSLRS, SSB) to obtain an RSRP (e.g., CSLRSRP, SSB-RSRP) or resources to obtain an RSSI. The first RAN parameter may further indicate how to obtain the CLI value.

[0183] 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. 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, a CSLRSRP threshold value, an SSB-RSRP threshold value, an SRS-RSRPthreshold value, an RSRQ threshold value, an RSSI threshold value, a CLI-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 / OAM, an implementation, a condition of the cells provided by a RAN node 1104, or any combination thereof.

[0184] 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 reference signal that indicates to one or more other RAN nodes 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 detects that the CLI value is above the threshold by X dB, then the RAN node 1 may determine to increase the transmission power of the second reference signal by X dB. Since 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 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.

[0185] 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. For example, if the RAN node 1 has increased the transmission power of the secondreference signal by X dB earlier in accordance with the policy action, then the RAN node 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.

[0186] In some cases, at 1112, if the CLI satisfies a threshold value, then the RAN node 1 may determine to transmit reference signal and / or increase transmission power of reference signal transmission. In some other cases, at 1114, 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.

[0187] In some cases, at 1116, the RAN node 1 may transmit a reference signal and / or increase a transmission power of a reference signal.

[0188] 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 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, and / or the signaling diagram 1100. The signaling diagram 1200 may illustrate an example of a framework defining one or more rules or conditions for CLI management between a RAN controller 1202 and a RAN node 1204. The RAN controller 1202 and the RAN node 1204 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.

[0189] In some examples, at 1206, the RAN node 1204 and the RAN controller 1202 may perform initial processes. The initial processes may be for a subscription procedure, including exchanging signaling related to the subscription procedure.

[0190] At 1208, the RAN controller 1202 and the RAN node 1204 may perform a subscription procedure with a type of POLICY. For example, the RAN controller 1202 and the RAN node 1204 may exchange signaling, as described with reference to Figures 5 through 11. The subscription procedure may include one or more of a subscription signaling, a subscription modification signaling, and the like. The RAN controller 1202 may transmit, in one or more messages in the subscription procedure, information indicating one or more policy rules, trigger events, and / or RAN parameters for CLI management. The subscription procedure signaling may indicate for the RAN node 1204 to perform a measurement on a reference signal to obtain an RSRP value, to compare the RSRP value with a threshold value, and if the RSRP value satisfies (e.g., exceeds, is above, is greater than) the threshold, then to perform a CLI mitigation action (e.g., reduce a transmission power by the excess RSRP, or constrain communications on a resource, or constrain the use of a beam).

[0191] In some examples, the RAN controller 1202 performs subscription procedure signaling with a RAN node that experiences CLI and a RAN node that causes CLI (e.g., the RAN node 1204). The RAN controller 1202 and the RAN node that experiences CLI perform subscription procedure signaling according to Figure 11. The RAN controller 1202 and the RAN node that causes CLI (e.g., the RAN node 1204) perform subscription procedure signaling, at 1208. The RAN node that experiences CLI detects an excessive CLI and transmits a second reference signal or increases a transmission power of the reference signal, as described with reference to Figure 11.

[0192] The RAN node 1204 measures an RSRP on the second reference signal from the RAN node that experiences CLI and detects that the RSRP exceeds a threshold value. For example, at 1210, the RAN node 1204 may detect an event trigger based on measuring one or more RSRP values. In response, the RAN node 1204 takes a CLI mitigation action, as described with reference to Figure 10. For example, at 1214, if the RSPR value satisfies a threshold value, then the RAN node 1204 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 1212 if the RAN node 1204 determines 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 1204 may determine no action and / or a default action. In someexamples, 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.

[0193] 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., CSI-RSRP, SSB- RSRP) exceeds a threshold. 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 1204 may use the value of the threshold to determine whether the reported CLI is above the threshold.

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

[0195] At 1216, the RAN node 1204 may execute the action. For example, the RAN node 1204 may execute the action determined at 1212 or at 1214.

[0196] 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, andso 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.

[0197] In some examples, separate RAN parameter identifiers may indicate various types of CLI values (e.g., CSI-RSRP, SSB-RSRP, CLI-RSSI). 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., CSI-RSRP, SSB-RSRP, CLI-RSSI). In some other examples, separate RAN parameter identifiers may indicate various types of CLI thresholds (e.g., CSI-RSRP, SSB-RSRP, 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., CSI-RSRP, SSB-RSRP, 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., CSI-RSRP, SSB-RSRP, 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., CSI-RSRP, SSB-RSRP, 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).

[0198] 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 rulemay 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 OAM, indicated by a signaling from the RAN nodes and / or other RAN and / or CN entities, determined by implementation, or any combination thereof.

[0199] Figure 13 illustrates an example of a RAN node 1300 in accordance with aspects of the present disclosure. The RAN node 1300 may include a processor 1302, a memory 1304, a controller 1306, and a transceiver 1308. The processor 1302, the memory 1304, the controller 1306, or the transceiver 1308, 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.

[0200] The processor 1302, the memory 1304, the controller 1306, or the transceiver 1308, 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.

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

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

[0203] In some implementations, the processor 1302 and the memory 1304 coupled with the processor 1302 may be configured to cause the RAN node 1300 to perform one or more of the functions described herein (e.g., executing, by the processor 1302, instructions stored in the memory 1304). For example, the processor 1302 may support wireless communication at the RAN node 1300 in accordance with examples as disclosed herein. The RAN node 1300 may be configured to or operable to support a means for receiving, from a RAN controller, subscription information including at least one parameter indicative of a condition and an action for managing CLI based on the condition, detecting 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 being met in response to the trigger event.

[0204] Additionally, the RAN node 1300 may be configured to support any one or combination of detecting the trigger event further includes measuring at least one CLI value, and where the condition includes the at least one CLI value satisfying a threshold value. Additionally, or alternatively, selectively performing the action for managing the CLI further includes transmitting, to at least one of the RAN controller or an additional RAN node, an additional message based on the at least one CLI value satisfying the threshold value, and where the additional 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 further includes refraining from transmitting an additional message based on the at least one CLI value failing to satisfy the threshold value, and where the additional message indicates at least one of a difference between the at least one CLIvalue 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 further includes transmitting an additional message including a reference signal based on the at least one CLI value satisfying the threshold value, and where the additional 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.

[0205] Additionally, or alternatively, selectively performing the action for managing the CLI further includes refraining from transmitting an additional message including a reference signal based on the at least one CLI value failing to satisfy the threshold value, and where the additional 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 further includes transmitting, using a transmission power that satisfies a transmit power threshold corresponding to the threshold value, an additional message including a reference signal based on the at least one CLI value satisfying the threshold value. Additionally, or alternatively, selectively performing the action for managing the CLI further includes transmitting, based on maintaining a transmission power, an additional message including a reference signal based on the at least one CLI value failing to satisfy 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, detecting the trigger event further includes measuring at least one RSRP value, and where the condition includes the at least one RSRP value satisfying a threshold value. Additionally, or alternatively, selectively performing the action for managing the CLI further includes performing at least one action based on the at least one RSRP value satisfying the threshold value, and where the at least one action includes to reduce a transmission power associated with transmission of an additional message, to select one or more time-frequency resources for the transmission of the additional message, or to select a beam for the transmission of the additional message.

[0206] Additionally, or alternatively, selectively performing the action for managing the CLI further includes refraining from performing at least one action based on the at least one RSRP value failing to satisfy the threshold value, and where the at least one action includes to reduce a transmission power associated with transmission of an additional message, to select one or more time-frequency resources for the transmission of the additional message, or to select a beam for the transmission of the additional message. Additionally, or alternatively, detecting the trigger event further includes receiving an additional message indicating at least one CLI value associated with at least one CLI measurement, and where the condition includes the at least one CLI value satisfying a threshold value. Additionally, or alternatively, selectively performing the action for managing the CLI further includes performing at least one action based on the at least one CLI value satisfying the threshold value, and where the at least one action includes to reduce a transmission power associated with transmission of another additional message, to select one or more time-frequency resources for the transmission of the other additional message, or to select a beam for the transmission of the other additional message. Additionally, or alternatively, selectively performing the action for managing the CLI further includes refraining from performing at least one action based on the at least one CLI value failing to satisfy the threshold value, and where the at least one action includes to reduce a transmission power associated with transmission of another additional message, to select one or more time-frequency resources for the transmission of the other additional message, or to select a beam for the transmission of the other additional message. Additionally, or alternatively, the at least one CLI value includes at least one of an RSRP, an RS SI, an SINR, or an RSRQ.

[0207] Additionally, or alternatively, detecting the trigger event further includes receiving an additional message indicating a metric indicative of a time-frequency resource usage, and where the condition includes the metric indicative of the time-frequency resource usage satisfying a threshold value. Additionally, or alternatively, selectively performing the action for managing the CLI further includes transmitting, to at least one of the RAN controller or an additional RAN node, another additional message that indicates the metric indicative of the time-frequency resource usage based on the metric indicative of the time-frequency resource usage satisfying the threshold value. Additionally, or alternatively, selectively performing the action for managing the CLI further includes refraining from transmitting, to at least one of the RAN controller or an additional RANnode, another additional message that indicates the metric indicative of the time-frequency resource usage based on the metric indicative of the time-frequency resource usage failing to satisfy the threshold value. Additionally, or alternatively, selectively performing the action for managing the CLI further includes performing the action for managing the CLI and transmitting, to the RAN controller, an additional message that indicates the action for managing the CLI is performed.

[0208] Additionally, or alternatively, detecting the trigger event further includes obtaining at least one of at least one CLI value or at least one RSRP value, and where the at least one parameter is indicative of the trigger event. Additionally, or alternatively, detecting the trigger event further includes performing at least one CLI measurement associated with the at least one CLI value according to a periodicity, and where the at least one parameter indicates the periodicity.Additionally, or alternatively, detecting the trigger event further includes performing a set of CLI measurements to obtain the at least one CLI value, and where the at least one CLI value corresponds to at least one of an average CLI value of the set of CLI measurements or a maximum CLI value of the set of CLI measurements. Additionally, or alternatively, detecting the trigger event further includes performing a set of CLI measurements to obtain a set of CLI values, and where the trigger event is detected based on a threshold numerical quantity of consecutive CLI values satisfying a threshold value, and where the at least one parameter indicates the threshold numerical quantity of consecutive CLI values. Additionally, or alternatively, detecting the trigger event further includes performing a set of CLI measurements to obtain a set of CLI values, and where the trigger event is detected based on a threshold numerical quantity of CLI values in a threshold numerical quantity of consecutive CLI values satisfying a threshold value, and where the at least one parameter indicates the threshold numerical quantity of CLI values and the threshold numerical quantity of consecutive CLI values. Additionally, or alternatively, the subscription information includes at least one additional parameter that indicates a type of the 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, and where the RAN controller includes at least one of an RIC, a near-real- time RIC, or a non-real-time RIC.

[0209] Additionally, or alternatively, the RAN node 1300 may support at least one memory (e.g., the memory 1304) and at least one processor (e.g., the processor 1302) coupled with the at least one memory and configured to cause the RAN node 1300 to receive, from a RAN controller,subscription information including at least one parameter indicative of a condition and an action for managing CLI based on the condition, detect 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 being met in response to the trigger event.

[0210] Additionally, the RAN node 1300 may be configured to support at least one memory (e.g., the memory 1304) and at least one processor (e.g., the processor 1302) coupled with the at least one memory and configured to cause the RAN node 1300 to detect the trigger event, the RAN node 1300 measures at least one CLI value, and where the condition includes the at least one CLI value satisfying a threshold value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the RAN node 1300 transmits, to at least one of the RAN controller or an additional RAN node 1300, an additional message based on the at least one CLI value satisfying the threshold value, and where the additional 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 1300 refrains from transmitting an additional message based on the at least one CLI value failing to satisfy the threshold value, and where the additional 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 1300 transmits an additional message including a reference signal based on the at least one CLI value satisfying the threshold value, and where the additional 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.

[0211] Additionally, or alternatively, to selectively perform the action for managing the CLI, the RAN node 1300 refrains from transmitting an additional message including a reference signal based on the at least one CLI value failing to satisfy the threshold value, and where the additional 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 onetime-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 1300 transmits, using a transmission power that satisfies a transmit power threshold corresponding to the threshold value, an additional message including a reference signal based on the at least one CLI value satisfying the threshold value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the RAN node 1300 transmits, based on maintaining a transmission power, an additional message including a reference signal based on the at least one CLI value failing to satisfy 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, to detect the trigger event, the RAN node 1300 measures at least one RSRP value, and where the condition includes the at least one RSRP value satisfying a threshold value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the RAN node 1300 performs at least one action based on the at least one RSRP value satisfying the threshold value, and where the at least one action includes to reduce a transmission power associated with transmission of an additional message, to select one or more time-frequency resources for the transmission of the additional message, or to select a beam for the transmission of the additional message.

[0212] Additionally, or alternatively, to selectively perform the action for managing the CLI, the RAN node 1300 refrains from performing at least one action based on the at least one RSRP value failing to satisfy the threshold value, and where the at least one action includes to reduce a transmission power associated with transmission of an additional message, to select one or more time-frequency resources for the transmission of the additional message, or to select a beam for the transmission of the additional message. Additionally, or alternatively, to detect the trigger event, the RAN node 1300 receives an additional message indicating at least one CLI value associated with at least one CLI measurement, and where the condition includes the at least one CLI value satisfying a threshold value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the RAN node 1300 performs at least one action based on the at least one CLI value satisfying the threshold value, and where the at least one action includes to reduce a transmission power associated with transmission of another additional message, to select one or more time-frequency resources for the transmission of the other additional message, or to select a beam for the transmission of the other additional message. Additionally, or alternatively, to selectively performthe action for managing the CLI, the RAN node 1300 refrains from performing at least one action based on the at least one CLI value failing to satisfy the threshold value, and where the at least one action includes to reduce a transmission power associated with transmission of another additional message, to select one or more time-frequency resources for the transmission of the other additional message, or to select a beam for the transmission of the other additional message. Additionally, or alternatively, the at least one CLI value includes at least one of an RSRP, an RS SI, an SINR, or an RSRQ.

[0213] Additionally, or alternatively, to detect the trigger event, the RAN node 1300 receives an additional message indicating a metric indicative of a time-frequency resource usage, and where the condition includes the metric indicative of the time-frequency resource usage satisfying a threshold value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the RAN node 1300 transmits, to at least one of the RAN controller or an additional RAN node 1300, another additional message that indicates the metric indicative of the time-frequency resource usage based on the metric indicative of the time-frequency resource usage satisfying the threshold value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the RAN node 1300 refrains from transmitting, to at least one of the RAN controller or an additional RAN node 1300, another additional message that indicates the metric indicative of the time-frequency resource usage based on the metric indicative of the time-frequency resource usage failing to satisfy the threshold value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the RAN node 1300 performs the action for managing the CLI, and transmits, to the RAN controller, an additional message that indicates the action for managing the CLI is performed.

[0214] Additionally, or alternatively, to detect the trigger event, the RAN node 1300 obtains at least one of at least one CLI value or at least one RSRP value, and where the at least one parameter is indicative of the trigger event. Additionally, or alternatively, to detect the trigger event, the RAN node 1300 performs at least one CLI measurement associated with the at least one CLI value according to a periodicity, and where the at least one parameter indicates the periodicity.Additionally, or alternatively, to detect the trigger event, the RAN node 1300 performs a set of CLI measurements to obtain the at least one CLI value, and where the at least one CLI value corresponds to at least one of an average CLI value of the set of CLI measurements or a maximum CLI value of the set of CLI measurements. Additionally, or alternatively, to detect the trigger event,the RAN node 1300 performs a set of CLI measurements to obtain a set of CLI values, and where the trigger event is detected based on a threshold numerical quantity of consecutive CLI values satisfying a threshold value, and where the at least one parameter indicates the threshold numerical quantity of consecutive CLI values. Additionally, or alternatively, to detect the trigger event, the RAN node 1300 performs a set of CLI measurements to obtain a set of CLI values, and where the trigger event is detected based on a threshold numerical quantity of CLI values in a threshold numerical quantity of consecutive CLI values satisfying a threshold value, and where the at least one parameter indicates the threshold numerical quantity of CLI values and the threshold numerical quantity of consecutive CLI values. Additionally, or alternatively, the subscription information includes at least one additional parameter that indicates a type of a message including the subscription information is a policy type. Additionally, or alternatively, the RAN node 1300 includes at least one of a base station, a CU, a DU, an E2 node, or an 01 node, and where the RAN controller includes at least one of an RIC, a near-real-time RIC, or a non-real-time RIC.

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

[0216] In some implementations, the RAN node 1300 may include at least one transceiver 1308. In some other implementations, the RAN node 1300 may have more than one transceiver 1308. The transceiver 1308 may represent a wireless transceiver. The transceiver 1308 may include one or more receiver chains 1310, one or more transmitter chains 1312, or any combination thereof.

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

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

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

[0220] The processor 1400 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 1400) 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).

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

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

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

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

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

[0226] The processor 1400 may support wireless communication in accordance with examples as disclosed herein. The processor 1400 may be configured to or operable to support at least one controller (e.g., the controller 1402) coupled with at least one memory (e.g., the memory 1404) and configured to cause the processor to receive, from a RAN controller, subscription information including at least one parameter indicative of a condition and an action for managing CLI based on the condition, detect 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 being met in response to the trigger event.

[0227] Additionally, the processor 1400 may be configured to or operable to support any one or combination of the at least one controller is configured to cause the processor to detect the trigger event, the processor 1400 measures at least one CLI value, and where the condition includes the at least one CLI value satisfying a threshold value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the processor 1400 transmits, to at least one of the RANcontroller or a RAN node, an additional message based on the at least one CLI value satisfying the threshold value, and where the additional 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 processor 1400 refrains from transmitting an additional message based on the at least one CLI value failing to satisfy the threshold value, and where the additional 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 processor 1400 transmits an additional message including a reference signal based on the at least one CLI value satisfying the threshold value, and where the additional 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.

[0228] Additionally, or alternatively, to selectively perform the action for managing the CLI, the processor 1400 refrains from transmitting an additional message including a reference signal based on the at least one CLI value failing to satisfy the threshold value, and where the additional 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 processor 1400 transmits, using a transmission power that satisfies a transmit power threshold corresponding to the threshold value, an additional message including a reference signal based on the at least one CLI value satisfying the threshold value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the processor 1400 transmits, based on maintaining a transmission power, an additional message including a reference signal based on the at least one CLI value failing to satisfy 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, to detect the trigger event, the processor 1400 measures at least one RSRP value, and where the condition includes the at least oneRSRP value satisfying a threshold value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the processor 1400 performs at least one action based on the at least one RSRP value satisfying the threshold value, and where the at least one action includes to reduce a transmission power associated with transmission of an additional message, to select one or more time-frequency resources for the transmission of the additional message, or to select a beam for the transmission of the additional message.

[0229] Additionally, or alternatively, to selectively perform the action for managing the CLI, the processor 1400 refrains from performing at least one action based on the at least one RSRP value failing to satisfy the threshold value, and where the at least one action includes to reduce a transmission power associated with transmission of an additional message, to select one or more time-frequency resources for the transmission of the additional message, or to select a beam for the transmission of the additional message. Additionally, or alternatively, to detect the trigger event, the processor 1400 receives an additional message indicating at least one CLI value associated with at least one CLI measurement, and where the condition includes the at least one CLI value satisfying a threshold value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the processor 1400 performs at least one action based on the at least one CLI value satisfying the threshold value, and where the at least one action includes to reduce a transmission power associated with transmission of another additional message, to select one or more time-frequency resources for the transmission of the other additional message, or to select a beam for the transmission of the other additional message. Additionally, or alternatively, to selectively perform the action for managing the CLI, the processor 1400 refrains from performing at least one action based on the at least one CLI value failing to satisfy the threshold value, and where the at least one action includes to reduce a transmission power associated with transmission of another additional message, to select one or more time-frequency resources for the transmission of the other additional message, or to select a beam for the transmission of the other additional message. Additionally, or alternatively, the at least one CLI value includes at least one of an RSRP, an RS SI, an SINR, or an RSRQ.

[0230] Additionally, or alternatively, to detect the trigger event, the processor 1400 receives an additional message indicating a metric indicative of a time-frequency resource usage, and where the condition includes the metric indicative of the time-frequency resource usage satisfying a thresholdvalue. Additionally, or alternatively, to selectively perform the action for managing the CLI, the processor 1400 transmits, to at least one of the RAN controller or a RAN node, another additional message that indicates the metric indicative of the time-frequency resource usage based on the metric indicative of the time-frequency resource usage satisfying the threshold value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the processor 1400 refrains from transmitting, to at least one of the RAN controller or a RAN node, another additional message that indicates the metric indicative of the time-frequency resource usage based on the metric indicative of the time-frequency resource usage failing to satisfy the threshold value. Additionally, or alternatively, to selectively perform the action for managing the CLI, the processor 1400 performs the action for managing the CLI, and transmits, to the RAN controller, an additional message that indicates the action for managing the CLI is performed.

[0231] Additionally, or alternatively, to detect the trigger event, the processor 1400 obtains at least one of at least one CLI value or at least one RSRP value, and where the at least one parameter is indicative of the trigger event. Additionally, or alternatively, to detect the trigger event, the processor 1400 performs at least one CLI measurement associated with the at least one CLI value according to a periodicity, and where the at least one parameter indicates the periodicity.Additionally, or alternatively, to detect the trigger event, the processor 1400 performs a set of CLI measurements to obtain the at least one CLI value, and where the at least one CLI value corresponds to at least one of an average CLI value of the set of CLI measurements or a maximum CLI value of the set of CLI measurements. Additionally, or alternatively, to detect the trigger event, the processor 1400 performs a set of CLI measurements to obtain a set of CLI values, and where the trigger event is detected based on a threshold numerical quantity of consecutive CLI values satisfying a threshold value, and where the at least one parameter indicates the threshold numerical quantity of consecutive CLI values. Additionally, or alternatively, to detect the trigger event, the processor 1400 performs a set of CLI measurements to obtain a set of CLI values, and where the trigger event is detected based on a threshold numerical quantity of CLI values in a threshold numerical quantity of consecutive CLI values satisfying a threshold value, and where the at least one parameter indicates the threshold numerical quantity of CLI values and the threshold numerical quantity of consecutive CLI values. Additionally, or alternatively, the subscription information includes at least one additional parameter that indicates a type of a message including thesubscription information is a policy type. Additionally, or alternatively, the processor 1400 includes at least one of a base station, a CU, a DU, an E2 node, or an 01 node, and where the RAN controller includes at least one of an RIC, a near-real-time RIC, or a non-real-time RIC.

[0232] Figure 15 illustrates an example of a RAN controller 1500 in accordance with aspects of the present disclosure. The RAN controller 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.

[0233] 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 thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0234] 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 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 execute computer-readable instructions stored in the memory 1504 to cause the RAN controller 1500 to perform various functions of the present disclosure.

[0235] 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 controller 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 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.

[0236] In some implementations, the processor 1502 and the memory 1504 coupled with the processor 1502 may be configured to cause the RAN controller 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 controller 1500 in accordance with examples as disclosed herein. The RAN controller 1500 may be configured to or operable to support a means for transmitting, to a RAN node, subscription information including at least one parameter indicative of a condition and an action for managing CLI based on the condition, and receiving, from the RAN node, an indication that the action for managing CLI is performed based on the condition being met in response to a trigger event, where the trigger event is associated with one or more of the condition or the action.

[0237] Additionally, the RAN controller 1500 may be configured to or operable to support any one or combination of the trigger event includes the RAN node measuring at least one CLI value, and the condition includes the at least one CLI value satisfying a threshold value. Additionally, or alternatively, the indication 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 indication includes a reference signal that 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 indication includes a reference signal associated with a transmission power that satisfies a transmit power threshold corresponding to the threshold value.

[0238] 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 trigger event includes the RAN node measuring at least one RSRP value, and the condition includes the at least one RSRP value satisfying a threshold value. Additionally, or alternatively, the indication is associated with at least one of a reduction in transmission power, one or more time-frequency resources, or a beam. Additionally, or alternatively, the trigger event includes the RAN node receiving a third messageindicating at least one CLI value associated with at least one CLI measurement, and the condition includes the at least one CLI value satisfying a threshold value. Additionally, or alternatively, the indication is associated with at least one of a reduction in transmission power, one or more timefrequency resources, or to a beam. Additionally, or alternatively, the at least one CLI value includes at least one of an RSRP, an RSSI, an SINR, or an RSRQ.

[0239] Additionally, or alternatively, the trigger event includes the RAN node receiving a third message indicating a metric indicative of a time-frequency resource usage, and the condition includes the metric indicative of the time-frequency resource usage satisfying a threshold value. Additionally, or alternatively, the indication indicates the metric indicative of the time-frequency resource usage. Additionally, or alternatively, the at least one parameter is indicative of the trigger event, and where the trigger event includes at least one of obtaining at least one CLI value or obtaining at least one RSRP value. Additionally, or alternatively, the subscription information includes at least one additional parameter that indicates a type of a message including the subscription information 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, and where the RAN controller includes at least one of an RIC, a near-real-time RIC, or a non-real-time RIC.

[0240] Additionally, or alternatively, the RAN controller 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 cause the RAN controller 1500 to transmit, to a RAN node, subscription information including at least one parameter indicative of a condition and an action for managing CLI based on the condition, and receive, from the RAN node, an indication that the action for managing CLI is performed based on the condition being met in response to a trigger event, where the trigger event is associated with one or more of the condition or the action.

[0241] Additionally, the RAN controller 1500 1500 may be configured to support any one or combination of the trigger event includes the RAN node measuring at least one CLI value, and the condition includes the at least one CLI value satisfying a threshold value. Additionally, or alternatively, the indication 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 indication includes a reference signal that indicates at least one ofa 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 indication includes a reference signal associated with a transmission power that satisfies a transmit power threshold corresponding to the threshold value.

[0242] 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 trigger event includes the RAN node measuring at least one RSRP value, and the condition includes the at least one RSRP value satisfying a threshold value. Additionally, or alternatively, the indication is associated with at least one of a reduction in transmission power, one or more time-frequency resources, or a beam. Additionally, or alternatively, the trigger event includes the RAN node receiving a third message indicating at least one CLI value associated with at least one CLI measurement, and the condition includes the at least one CLI value satisfying a threshold value. Additionally, or alternatively, the indication is associated with at least one of a reduction in transmission power, one or more timefrequency resources, or to a beam. Additionally, or alternatively, the at least one CLI value includes at least one of an RSRP, an RSSI, an SINR, or an RSRQ.

[0243] Additionally, or alternatively, the trigger event includes the RAN node receiving a third message indicating a metric indicative of a time-frequency resource usage, and the condition includes the metric indicative of the time-frequency resource usage satisfying a threshold value. Additionally, or alternatively, the indication indicates the metric indicative of the time-frequency resource usage. Additionally, or alternatively, the at least one parameter is indicative of the trigger event, and where the trigger event includes at least one of obtaining at least one CLI value or obtaining at least one RSRP value. Additionally, or alternatively, the subscription information includes at least one additional parameter that indicates a type of a message including the subscription information 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, and where the RAN controller 1500 includes at least one of an RIC, a near-real-time RIC, or a non -real-time RIC.

[0244] The controller 1506 may manage input and output signals for the RAN controller 1500. The controller 1506 may also manage peripherals not integrated into the RAN controller 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.

[0245] In some implementations, the RAN controller 1500 may include at least one transceiver 1508. In some other implementations, the RAN controller 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.

[0246] A receiver chain 1510 may be configured 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., a low-noise amplifier (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.

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

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

[0249] At 1602, the method may include receiving, from a RAN controller, subscription information including at least one parameter indicative of a condition and an action for managing CLI based on the condition. The operations of 1602 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1602 may be performed by a RAN node as described with reference to Figure 13.

[0250] At 1604, the method may include detecting a trigger event associated with one or more of the condition or the action. The operations of 1604 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1604 may be performed by a RAN node as described with reference to Figure 13.

[0251] At 1606, the method may include selectively performing (e.g., taking) the action for managing the CLI based on the condition being met in response to the trigger event. The operations of 1606 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1606 may be performed a RAN node as described with reference to Figure 13.

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

[0253] At 1702, the method may include transmitting, to a RAN node, subscription information including at least one parameter indicative of a condition and an action for managing CLI based on the condition. The operations of 1702 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1702 may be performed by a RAN controller as described with reference to Figure 15.

[0254] At 1704, the method may include receiving, from the RAN node, an indication that the action for managing CLI is performed based on the condition being met in response to a triggerevent, where the trigger event is associated with one or more of the condition or the action. The operations of 1704 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1704 may be performed by a RAN controller as described with reference to Figure 15.

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

Claims

CLAIMSWhat is claimed is:

1. A radio access network (RAN) node for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the RAN node to: receive, from a RAN controller, subscription information comprising at least one parameter indicative of a condition and an action for managing cross-link interference based at least in part on the condition; detect a trigger event associated with one or more of the condition or the action; and selectively perform the action for managing the cross-link interference based at least in part on the condition being met in response to the trigger event.

2. The RAN node of claim 1 , wherein to detect the trigger event, the at least one processor is configured to cause the RAN node to measure at least one cross-link interference value, and wherein the condition comprises the at least one cross-link interference value satisfying a threshold value.

3. The RAN node of claim 2, wherein to selectively perform the action for managing the cross-link interference, the at least one processor is configured to cause the RAN node to: transmit, to at least one of the RAN controller or an additional RAN node, a message based at least in part on the at least one cross-link interference value satisfying the threshold value, and wherein the message indicates at least one of a difference between the at least one cross-link interference value and the threshold value, the at least one cross-link interference value, a beam associated with the at least one cross-link interference value, or at least one time-frequency resource associated with the at least one cross-link interference value; or refrain from transmitting the message based at least in part on the at least one cross-link interference value failing to satisfy the threshold value.

4. The RAN node of claim 2, wherein to selectively perform the action for managing the cross-link interference, the at least one processor is configured to cause the RAN node to:transmit a message comprising a reference signal based at least in part on the at least one cross-link interference value satisfying the threshold value, and wherein the message indicates at least one of a difference between the at least one cross-link interference value and the threshold value, the at least one cross-link interference value, a beam associated with the at least one crosslink interference value, or at least one time-frequency resource associated with the at least one cross-link interference value; or refrain from transmitting the message comprising the reference signal based at least in part on the at least one cross-link interference value failing to satisfy the threshold value.

5. The RAN node of claim 2, wherein to selectively perform the action for managing the cross-link interference, the at least one processor is configured to cause the RAN node to transmit, using a transmission power that satisfies a transmit power threshold corresponding to the threshold value, a message comprising a reference signal based at least in part on the at least one cross-link interference value satisfying the threshold value.

6. The RAN node of claim 2, wherein to selectively perform the action for managing the cross-link interference, the at least one processor is configured to cause the RAN node to transmit, based at least in part on maintaining a transmission power, a message comprising a reference signal based at least in part on the at least one cross-link interference value failing to satisfy the threshold value.

7. The RAN node of claim 1, wherein to detect the trigger event, the at least one processor is configured to cause the RAN node to measure at least one reference signal received power (RSRP) value, wherein the condition comprises the at least one RSRP value satisfying a threshold value, and wherein to selectively perform the action for managing the cross-link interference, the at least one processor is configured to cause the RAN node to: perform at least one action based at least in part on the at least one RSRP value satisfying the threshold value, and wherein the at least one action comprises to reduce a transmission power associated with transmission of a message, to select one or more time-frequency resources for the transmission of the message, or to select a beam for the transmission of the message; or refrain from performing the at least one action based at least in part on the at least one RSRP value failing to satisfy the threshold value.

8. The RAN node of claim 1, wherein to detect the trigger event, the at least one processor is configured to cause the RAN node to receive a message indicating at least one crosslink interference value associated with at least one cross-link interference measurement, wherein the condition comprises the at least one cross-link interference value satisfying a threshold value, and wherein to selectively perform the action for managing the cross-link interference, the at least one processor is configured to cause the RAN node to: perform at least one action based at least in part on the at least one cross-link interference value satisfying the threshold value, and wherein the at least one action comprises to reduce a transmission power associated with transmission of an additional message, to select one or more time-frequency resources for the transmission of the additional message, or to select a beam for the transmission of the additional message; or refrain from performing the at least one action based at least in part on the at least one crosslink interference value failing to satisfy the threshold value.

9. The RAN node of claim 1, wherein to detect the trigger event, the at least one processor is configured to cause the RAN node to receive a message indicating a metric indicative of a time-frequency resource usage, wherein the condition comprises the metric indicative of the time-frequency resource usage satisfying a threshold value, and wherein to selectively perform the action for managing the cross-link interference, the at least one processor is configured to cause the RAN node to: transmit, to at least one of the RAN controller or an additional RAN node, an additional message that indicates the metric indicative of the time-frequency resource usage based at least in part on the metric indicative of the time-frequency resource usage satisfying the threshold value; or refrain from transmitting, to at least one of the RAN controller or the additional RAN node, the additional message that indicates the metric indicative of the time-frequency resource usage based at least in part on the metric indicative of the time-frequency resource usage failing to satisfy the threshold value.

10. The RAN node of claim 1, wherein to selectively perform the action for managing the cross-link interference, the at least one processor is configured to cause the RAN node to: perform the action for managing the cross-link interference; andtransmit, to the RAN controller, a message that indicates the action for managing the crosslink interference is performed.

11. The RAN node of claim 1 , wherein to detect the trigger event, the at least one processor is configured to cause the RAN node to obtain at least one of at least one cross-link interference value or at least one reference signal received power (RSRP) value, and wherein the at least one parameter is indicative of the trigger event.

12. The RAN node of claim 11, wherein to detect the trigger event, the at least one processor is configured to cause the RAN node to perform at least one cross-link interference measurement associated with the at least one cross-link interference value according to a periodicity, and wherein the at least one parameter indicates the periodicity.

13. The RAN node of claim 11, wherein to detect the trigger event, the at least one processor is configured to cause the RAN node to perform a plurality of cross-link interference measurements to obtain the at least one cross-link interference value, and wherein the at least one cross-link interference value corresponds to at least one of an average cross-link interference value of the plurality of cross-link interference measurements or a maximum cross-link interference value of the plurality of cross-link interference measurements.

14. The RAN node of claim 11, wherein to detect the trigger event, the at least one processor is configured to cause the RAN node to perform a plurality of cross-link interference measurements to obtain a plurality of cross-link interference values, and wherein the trigger event is detected based at least in part on a threshold numerical quantity of consecutive cross-link interference values satisfying a threshold value, and wherein the at least one parameter indicates the threshold numerical quantity of consecutive cross-link interference values.

15. The RAN node of claim 11, wherein to detect the trigger event, the at least one processor is configured to cause the RAN node to perform a plurality of cross-link interference measurements to obtain a plurality of cross-link interference values, and wherein the trigger event is detected based at least in part on a threshold numerical quantity of cross-link interference values in a threshold numerical quantity of consecutive cross-link interference values satisfying a threshold value, and wherein the at least one parameter indicates the threshold numerical quantity of cross-link interference values and the threshold numerical quantity of consecutive cross-link interference values.

16. The RAN node of claim 1, wherein the subscription information comprises at least one additional parameter that indicates a type of a message comprising the subscription information is a policy type.

17. The RAN node of claim 1, wherein the RAN node comprises at least one of a base station, a central unit, a distributed unit, an E2 node, or an 01 node, and wherein the RAN controller comprises at least one of a RAN intelligent controller (RIC), a near-real-time RIC, or a non-real-time RIC.

18. A processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: receive, from a RAN controller, subscription information comprising at least one parameter indicative of a condition and an action for managing cross-link interference based at least in part on the condition; detect a trigger event associated with one or more of the condition or the action; and selectively perform the action for managing the cross-link interference based at least in part on the condition being met in response to the trigger event.

19. A method performed by a radio access network (RAN) node, the method comprising: receiving, from a RAN controller, subscription information comprising at least one parameter indicative of a condition and an action for managing cross-link interference based at least in part on the condition; detecting a trigger event associated with one or more of the condition or the action; and selectively performing the action for managing the cross-link interference based at least in part on the condition being met in response to the trigger event.

20. A radio access network (RAN) controller for wireless communication, comprising: at least one memory; andat least one processor coupled with the at least one memory and configured to cause the RAN controller to: transmit, to a RAN node, subscription information comprising at least one parameter indicative of a condition and an action for managing cross-link interference based at least in part on the condition; and receive, from the RAN node, an indication that the action for managing the crosslink interference is performed based at least in part on the condition being met in response to a trigger event, wherein the trigger event is associated with one or more of the condition or the action.

Images