System and method for cross-link interference mitigation in network
The system uses NZP CSI-RS to identify and mitigate CLI in 5G networks, ensuring granular interference management and improved network performance by adapting to traffic demands and enhancing scalability.
Patent Information
- Application Number
- PCT/IN2026/050796
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-08
- Filing Date
- 2026-05-08
- Publication Date
- 2026-11-12
AI Technical Summary
Existing CLI mitigation approaches in 5G networks, particularly in dynamic TDD and SBFD systems, fail to adapt to fluctuating traffic demands, lack granular interference detection, and result in inefficient resource utilization and degraded network performance.
A system and method for CLI mitigation using standardized reference signals (NZP CSI-RS) to identify interfering beams or subbands and request targeted mitigation actions, such as power reduction or subband switching, within a disaggregated 5G architecture, enhancing scalability and adaptability.
Enables granular, beam-level CLI mitigation, minimizing network throughput impacts and improving uplink reliability and capacity by precisely identifying and addressing interference sources.
Smart Images

Figure IN2026050796_12112026_PF_FP_ABST
Abstract
Description
SYSTEM AND METHOD FOR CROSS-LINK INTERFERENCE MITIGATION IN NETWORK RESERVATION OF RIGHTS
[0001] A portion of the disclosure of this patent document contains material, which is subject to intellectual property rights such as, but are not limited to, copyright, design, trademark, Integrated Circuit (IC) layout design, and / or trade dress protection, belonging to Jio Platforms Limited (JPL) or its affiliates (hereinafter referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner.TECHNICAL FIELD
[0002] The present disclosure relates generally to the field of communication systems. More particularly, the present disclosure relates to a system and a method for cross-link interference (CLI) mitigation in a network.DEFINITION
[0003] As used in the present disclosure, the following terms are generally intended to have the meaning as set forth below, except to the extent that the context in which they are used to indicate otherwise.
[0004] The term ‘cross-link interference (CLI)’ as used herein refers to unwanted signal interference that occurs when a transmission path between two nodes (a crosslink) disrupts or overlaps with other ongoing communication links in a communication network. In particular, CLI refers to interference in a network (e.g., 5 th Generation New Radio (5G NR) network) where a downlink transmission from one gNodeB (e.g., aggressor gNB) interferes with an uplink reception of a neighboring gNB (e.g., victim gNB), due to overlapping time-frequency resources in dynamic Time Division Duplex (TDD) or Sub-Band Full Duplex (SBFD) configurations
[0005] The term ‘dynamic time division duplex (TDD)’ as used herein, refers to a duplexing mode in the 5G NR where the same frequency band is used for both uplink and downlink transmissions, with time slots dynamically allocated for either direction based on traffic demand.
[0006] The term ‘Sub-band Full Duplex (SBFD)’, as used herein, refers to a wireless communication technique that allows simultaneous transmission and reception on different sub-bands within a single frequency band, effectively combining the benefits of full duplex and frequency division.
[0007] The term ‘CLI mitigation’ as used herein refers to techniques used to reduce or eliminate Cross-Link Interference (CLI) in communication networks.
[0008] The term ‘Disaggregated RAN’ as used herein refers to a Disaggregated Radio Access Network. The Disaggregated RAN is a modern architectural approach in mobile networks, especially in 5G, where traditional RAN components are split into separate, interoperable modules. This shift enables greater flexibility, scalability, and vendor diversity compared to traditional, monolithic RAN systems.
[0009] The term ‘gNB’ as used herein refers to Next Generation Node B. The gNB is the 5G base station in the 5G NR network. It provides the radio interface between the User Equipment (UE) (e.g., smartphones, loT devices) and the 5G Core (5GC), enabling wireless communication, mobility, and data transfer.
[0010] The term ‘gNB-Central Unit (gNB-CU)’, as used herein, refers to a centralized component of a gNB that handles higher-layer protocols, such as Radio Resource Control (RRC) and Packet Data Convergence Protocol (PDCP), and manages control plane functions, including inter-gNB coordination.
[0011] The term ‘gNB-DU (Distributed Unit)’, as used herein, refers to a distributed component of a gNB that handles lower-layer protocols, such as Radio Link Control (RLC), Medium Access Control (MAC), and Physical Layer (PHY), and manages real-time radio functions like beamforming and interference measurement.
[0012] The term ‘victim cell’ or ‘victim gNB’, as used herein, refers to a gNB experiencing CLI during its uplink reception due to downlink transmissions from a neighboring gNB (aggressor gNB).
[0013] The term ‘aggressor cell’ or ‘aggressor gNB’, as used herein, refers to a gNB whose downlink transmissions cause CLI to a neighboring gNB (victim gNB) during its uplink reception.
[0014] The term ‘NZP CSLRS’ as used herein refers to Non-Zero-Power Channel State Information-Reference Signal. The NZP CSLRS refers to a reference signal transmitted by the gNB with a defined non- zero power level, used for channel state measurements, beam management, or interference measurement. NZP CSLRS is used by the victim gNB to measure CLI from the aggressor gNB.
[0015] The term ‘Fl interface’ as used herein refers to a standardized interface in 5G NR networks that connects a Central Unit (CU) and a Distributed Unit (DU) in a disaggregated RAN architecture. In particular, it acts as an interface between the gNB-CU and gNB-DU within the gNB, used for control plane (Fl-C) and user plane (FLU) communication, including the exchange of measurement configurations and mitigation instructions.
[0016] The term ‘Xn interface’ as used herein refers to a standardized interface in 5GNRand evolved LTE systems that enables communication between two gNBs (e.g., victim gNB and aggressor gNB) or between an evolved Node B (eNB) and the gNB. It plays a critical role in mobility management, handover, and dual connectivity. The Xn interface also enables inter-gNB coordination, such as exchanging NZP CSLRS configurations and CLI mitigation requests.
[0017] The term ‘Uu Interface’, as used herein, refers to an air interface between the gNB and the UE, or between two gNBs for interference measurement and mitigation signaling (e.g., via Relay UE).
[0018] The term ‘Relay UE’, as used herein, refers to a UE that relays CLI mitigation requests and responses between a victim gNB and an aggressor gNB over the Uu interface when direct Xn connectivity is unavailable.
[0019] The term ‘Beam’, as used herein, refers to a directional transmission or reception pattern formed by a gNB using beamforming techniques, identified by a specific Synchronization Signal Block (SSB) index or CSLRS resource ID.
[0020] The term ‘CLI mitigation request’, as used herein, refers to a message sent from the victim gNB to the aggressor gNB (via Xn or Relay UE) requesting specific actions to reduce CLI, such as reducing beam power, switching subbands, or adjusting timing.
[0021] The term ‘Reference Signal Received Power (RSRP)’, as used herein, refers to a measurement of the power level of a received reference signal (e.g., NZP CSI-RS), used to quantify interference strength.
[0022] The term ‘Received Signal Strength Indicator (RSSI)’, as used herein, refers to a measurement of the total received power, including interference and noise, used to assess CLI.
[0023] The term ‘Multi -Hop Coordination’, as used herein, refers to the process of forwarding CLI mitigation requests through intermediate nodes (e.g., another gNB or Relay UE) when direct Xn connectivity between victim and aggressor gNBs is unavailable.BACKGROUND
[0024] The following description of related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.
[0025] In modern telecommunication networks, especially in Time Division Duplexing (TDD) and Sub-band Full Duplex (SBFD) 5G networks, Cross-Link Interference (CLI) has emerged as a significant performance bottleneck. CLI occurs when uplink transmissions from one cell interfere with downlink transmissions in a neighboring cell, or vice versa. This interference is particularly severe in uncoordinated or dynamically scheduled TDD networks, where adjacent cells may operate in different transmission directions simultaneously.
[0026] Traditional CLI mitigation approaches, such as using static or semi-static TDD frame patterns, aim to reduce interference by pre-aligning transmission directions across cells. However, these methods sacrifice flexibility and fail to adapt to fluctuating traffic demands, resulting in underutilized resources and inefficiencies. On the other hand, more dynamic solutions often lack fine-grained interference detection and fail to accurately localize the source of interference, making them ineffective in dense, heterogeneous environments.
[0027] Thus, there is a need for a method and system that can address the shortcomings of existing solutions by enabling robust and scalable CLI mitigation mechanisms that can dynamically adapt to traffic conditions, minimize interference across cells and links, and ensure consistent quality of service (QoS) across the network. In particular, there is a need for a system that enables 5G base stations to detect, signal, and suppress cross-link interference proactively at a granular level (beam and sub-band) while working within the existing NR architecture and interfaces.OBJECTIVE OF THE PRESENT DISCLOSURE
[0028] Some of the objectives of the present disclosure, which at least one embodiment herein satisfies, are as follows:
[0029] An objective of the present disclosure is to perform granular, beam-level Cross-Link Interference (CLI) mitigation rather than generic, cell-wide power adjustments, minimizing negative impacts on network throughput.
[0030] Another objective of the present disclosure is to provide an integrated mechanism combining configuration, beam identification, and coordinated mitigation signaling.
[0031] Another objective of the present disclosure is to manage cross-link interference (CLI) mitigation in the network for beamformed systems using sub-band full duplex (SBFD) or dynamic time division duplex (TDD).
[0032] Another objective of the present disclosure is to use detailed beam-level interference measurement and signaling between neighboring base stations.
[0033] Another objective of the present disclosure is to introduce the CLI mitigation technique that works seamlessly within a disaggregated 5G architecture (CU-DU split), enhancing scalability.
[0034] Yet another objective of the present disclosure is to provide the capability for multi-hop interference mitigation coordination, supporting complex deployments.
[0035] Yet another objective of the present disclosure is to measure cross-link interference using configured reference signals (NZP CSLRS), identify precisely which beam or subband from a neighboring cell is causing interference, and then explicitly request targeted mitigation actions.
[0036] Yet another objective of the present disclosure is to enable robust crosslink interference (CLI) coordination by exchanging measurement configurations and interference information and by issuing directed mitigation commands. This improves uplink reliability and overall network capacity.
[0037] Yet another objective of the present disclosure is to provide coordination between the base stations using standard interfaces, such as Fl interface between gNB-CU and gNB-DU and Xn interface between neighboring gNBs.
[0038] Other objects and advantages of the present disclosure will be more apparent from the following description, which is not intended to limit the scope of the present disclosure.SUMMARY
[0039] In an exemplary embodiment, a method for radio interference mitigation (RIM) in a network is disclosed. The method comprises receiving, by a victim network node, one or more measurement configurations from an aggressor network node over a reference signal using a standard interface of one or more standard interfaces. The method comprises performing, by the victim network node, interference measurement based on the received measurement configuration to identify a resource causing radio interference. The method comprises preparing, by the victim network node, an interference report based on the resource identification. The method comprises generating, by the victim network node, an interference mitigation request based on the interference report. The interference mitigation request comprises an interfering beam and a suggested mitigation action to be taken to mitigate the radio interference. The method comprises communicating, by the victim network node, the generated interference mitigation request to the aggressor network node through one of the standard interface or multi-hop coordination. The method comprises performing, by the aggressor network node, the suggested mitigation action on the identified resource.
[0040] In some embodiments, the radio interference is cross-link interference (CLI). The network node is gNodeB. The mitigation request is CLI mitigation request.
[0041] In some embodiments, the one or more measurement configurations comprise non-zero-power (NZP) channel state information-reference signal (CSI-RS) configurations, zero-power CSI-RS configurations, one or more synchronization signal blocks (SSBs), and sounding reference signal (SRS). The NZP CSI-RS configurations comprise at least one of a resource identifier (ID), a time slot, frequency subband, periodicity, a CSI-RS identifier, location in time or frequency, and power.
[0042] In some embodiments, the one or more measurement configurations comprise at least one first information element (IE). The at least one first IE comprises served cell information.
[0043] In some embodiments, the one or more standard interfaces comprise a Fl interface, an Xn interface, and an air interface.
[0044] In some embodiments, the interference measurement comprises reference signal received power (RSRP) or received signal strength indicator (RSSI). The interference report comprises an interference level, an identifier of strongest interfering beam, a synchronization signal block (SSB) index, CSI-RS resource ID, time indication or frequency subband index.
[0045] In some embodiments, the CLI mitigation request comprises one or more second information elements (IES) corresponding to a victim cell identifier, an aggressor cell identifier, an interference cause or an interference level, and the suggested mitigation action. The interference level comprises high level, low level and medium level.
[0046] In some embodiments, the CLI mitigation request further comprises a beam identifier, a subband index, and a timing offset corresponding to interference, a request identifier, and a CLI severity metric. The CLI severity metric comprises measured interference power, and a signal to interference plus noise ratio (SINR).
[0047] In some embodiments, the method further comprises determining, by the victim network node, whether the interference measurement is within a predefined threshold and based on the determination, initiating, by the victim network node, the communication of the CLI mitigation request towards the aggressor network node.
[0048] In some embodiments, the suggested mitigation action comprises transmit power reduction, beam switching, beam muting, transmission timing adjustment, and duration for mitigation or periodicity for mitigation.
[0049] In some embodiments, the method further comprises performing, by the aggressor network node, the suggested mitigation action on the identified resource based on the CLI severity metric.
[0050] In some embodiments, upon performing the suggested mitigation action, communicating, by the aggressor network node, a CLI mitigation response to the victim network node. The CLI mitigation response comprises at least one third information elements (IEs) corresponding to the target cell identifier or the requestidentifier, an outcome, a mitigation identifier, a mitigation duration, and an indication of successful mitigation or unsuccessful mitigation. The outcome comprises one of mitigation action accepted, mitigation action rejected, or mitigation action partially accepted
[0051] In some embodiments, the method further comprises upon receiving the CLI mitigation response, verifying, by the victim network node, whether interference level has reduced to a reference interference level, after performing the mitigation action and based on the verification, communicating, by the victim network node, a feedback message to the aggressor network node.
[0052] In some embodiments, the method further comprises analyzing, by the aggressor network node, the feedback message to verify whether the suggested mitigation action is successful and based on the analysis, communicating, by the aggressor network node, a feedback response towards the victim network node.
[0053] In some embodiments, the feedback response further comprises an alternative action or a remedial action.
[0054] In some embodiments, the method comprises analyzing, by the victim network node, the feedback response and upon determining the unsuccessful mitigation based on the analysis of the feedback response, performing, by the victim network node, the remedial action. The remedial action comprises re-initiation of CLI mitigation.
[0055] In some embodiments, the method further comprises determining, by the aggressor network node, whether an occurrence of the CLI mitigation request is repeated more than a predefined number of times for a predefined duration and based on the determination, initiating, by the aggressor network node, a coordinated scheduling action with the victim network node.
[0056] In some embodiments, the radio interference mitigation (RIM) is managed in sub-band full duplex (SBFD) and dynamic time division duplex (TDD) network.
[0057] In some embodiments, the radio interference mitigation (RIM) is performed based on beam-level and subband-based coordination.
[0058] In another exemplary embodiment, system for radio interference mitigation (RIM) in a network is disclosed. The system comprises a victim network node. The victim network node comprises a communication unit configured to receive one or more measurement configurations from an aggressor network node over a reference signal using a standard interface of one or more standard interfaces. A processing unit is configured to perform interference measurement based on the received measurement configuration to identify a resource causing radio interference, prepare an interference report based on the resource identification, and generate an interference mitigation request based on the interference report. The interference mitigation request comprises an interfering beam and a suggested mitigation action to be taken to mitigate the radio interference. The communication unit is configured to communicate the generated interference mitigation request to the aggressor network node through one of the standard interface or multi-hop coordination. The aggressor network node is configured to perform the suggested mitigation action on the identified resource.
[0059] In yet another exemplary embodiment, a computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to execute a method for radio interference mitigation (RIM) in a network. The method comprises receiving, by a victim network node, one or more measurement configurations from an aggressor network node over a reference signal using a standard interface of one or more standard interfaces. The method comprises performing, by the victim network node, interference measurement based on the received measurement configuration to identify a resource causing radio interference. The method comprises preparing, by the victim network node, an interference report based on the resource identification. The method comprises generating, by the victim network node, an interference mitigation request based on the interference report. The interference mitigation request comprisesan interfering beam and a suggested mitigation action to be taken to mitigate the radio interference. The method comprises communicating, by the victim network node, the generated interference mitigation request to the aggressor network node through one of the standard interface or multi-hop coordination. The method comprises performing, by the aggressor network node, the suggested mitigation action on the identified resource.BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWING
[0060] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components, electronic components or circuitry commonly used to implement such components.
[0061] FIG. 1 illustrates an exemplary network architecture implementing a system for cross-link interference (CLI) mitigation in a network, in accordance with an embodiment of the present disclosure.
[0062] FIG. 2 illustrates an exemplary block diagram of the system, in accordance with an embodiment of the present disclosure.
[0063] FIG. 3 illustrates an exemplary system architecture for the CLI mitigation in the network, in accordance with an embodiment of the present disclosure.
[0064] FIG. 4 illustrates a system architecture for the CLI mitigation in the network, in accordance with an embodiment of the present disclosure.
[0065] FIG. 5 illustrates an exemplary flow diagram of a method for CLI mitigation in the network, in accordance with an embodiment of the present disclosure.
[0066] FIG. 6 illustrates an exemplary flow diagram of a method for radio interference mitigation (RIM) in the network, in accordance with an embodiment of the present disclosure.
[0067] FIG. 7 illustrates an exemplary block diagram of a computer system in which or with which embodiments of the present disclosure may be implemented.
[0068] The foregoing shall be more apparent from the following more detailed description of the disclosure.List of reference numerals100 - Network Architecture102 -User(s)104 -User Equipments (UEs)106 - Network108 - System200 - Block diagram202 - Processor(s)204 - Memory206 -Interface(s)208 - Processing Engine210 - Database212 - Processing Unit214 - Communication Unit300 - System Architecture302 - Aggressor gNodeB Central Unit (gNB-CU) 304 - Aggressor gNB- Distributed Unit (DU) 306 - Victim gNB-CU308 - Victim gNB-DU310 - CLI coordination logic312 - Measurement configuration distributor 314 - Beam-level mitigation processor316 - Beam control executor318 - Real-time beam adjustment320 - Beam level CLI coordination322 - Explicit mitigation request generator324 - Beam specific reporting handler326 - NZP CSLCLI measurement module328 - Strongest beam detector330 - Detailed interference reporter400 - System architecture402 - Intermediate gNB-CU404 - Relay User Equipment (UE)406 - XnAP interface handler408 - Fl AP interface handler410 - Interface mitigation request processor 412 - Interface mitigation action handler 414 - CLI mitigation action executor416 - Transmission beam controller418 - Air interface Transmission module 420 - Air interface Rx module422 - CLI relay module424 - Interference reporting handler426 - CLI mitigation response analyser428 - Measurement configuration handler 430 - Interference mitigation request generator 432 - CLI mitigation action verifier434 - CLI measurement engine436 - CLI request relay logic500 - Flow Diagram600 - Method Flow Diagram700 - Computer System710 - External Storage Device720 - Bus730 - Main Memory740 - Read Only Memory750 - Mass Storage Device760 - Communication Port770 - ProcessorDETAILED DESCRIPTION
[0069] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein. Example embodiments of the present disclosure aredescribed below, as illustrated in various drawings in which like reference numerals refer to the same parts throughout the different drawings.
[0070] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.
[0071] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.
[0072] Also, it is noted that individual embodiments may be described as a process that is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.
[0073] The word “exemplary” and / or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect orY1design described herein as “exemplary” and / or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive like the term “comprising” as an open transition word without precluding any additional or other elements.
[0074] Reference throughout this specification to “one embodiment” or “an embodiment” or “an instance” or “one instance” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
[0075] The terminology used herein is to describe particular embodiments only and is not intended to be limiting the disclosure. As used herein, the singular forms “a”, “an”, and “the” are intended to include the plural forms as well, unless the context indicates otherwise. It will be further understood that the terms “comprises” and / or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. As used herein, the term “and / or” includes any combinations of one or more of the associated listed items. It should be noted that the terms “mobile device”, “user equipment”, “user device”, “communication device”, “device” and similar terms are used interchangeably for the purpose of describing the invention. These terms are not intended to limit the scope of the invention or imply any specific functionality or limitations on the described embodiments. The use of theseterms is solely for convenience and clarity of description. The invention is not limited to any particular type of device or equipment, and it should be understood that other equivalent terms or variations thereof may be used interchangeably without departing from the scope of the invention as defined herein.
[0076] While considerable emphasis has been placed herein on the components and component parts of the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiment, as well as other embodiments of the disclosure, will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be interpreted merely as illustrative of the disclosure and not as a limitation.
[0077] As 5G networks continue to evolve, increasing demand for higher capacity and lower latency has led to the adoption of advanced duplexing schemes such as dynamic Time Division Duplex (TDD) and Sub-band Full Duplex (SBFD). While these techniques offer greater flexibility and spectrum efficiency, they also introduce a critical challenge of Cross-Link Interference (CLI). CLI arises when the downlink transmission from one cell interferes with the uplink reception of a neighboring cell, particularly in dense urban environments or heterogeneous network deployments.
[0078] In dynamic TDD systems, where uplink and downlink configurations can change rapidly across cells and time slots, CLI becomes increasingly unpredictable and difficult to manage. Similarly, in SBFD systems, where downlink and uplink transmissions occur simultaneously on different sub-bands, interference between adjacent cells can significantly degrade uplink performance. Existing CLI mitigation approaches, such as enforcing static or semi-static TDD patterns, limit the system's ability to adapt to traffic variations, effectively trading off performance for interference control. Other solutions that rely on broad interference detection techniques often lackthe granularity needed to identify the specific source of interference, leading to degraded network performance.
[0079] To address these challenges, the present disclosure provides a method and a system to manage cross-link interference in 5G NR networks, particularly suited for beamformed systems using sub-band full duplex or dynamic TDD. The system measures cross-link interference using configured reference signals (NZP CSI-RS), identifies precisely which beam or subband from a neighboring cell is causing interference, and then explicitly requests targeted mitigation actions (power reduction, subband switching, timing adjustment). By doing this, the system ensures granular, beam-level CLI mitigation rather than generic, cell-wide power adjustments, minimizing negative impacts on network throughput. Further, the system uses standardized reference signals (NZP CSI-RS), making integration into existing networks straightforward and cost-effective, thereby avoiding the need for new physical signals, enhancing scalability.
[0080] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.
[0081] FIG. 1 illustrates an exemplary network architecture (100) implanting a system (108) for cross-link interference (CLI) mitigation in a network, in accordance with an embodiment of the present disclosure.
[0082] As illustrated in FIG. 1, the network architecture (100) may include one or more user equipments (UEs) (104-1, 104-2, .... 104-N) associated with one or more users (102-1, 102-2, ...., 102 -N) in an environment. A person of ordinary skill in the art will understand that one or more users (102-1, 102-2, ... 102-N) may be individually referred to as the user (102) and collectively referred to as the users (102). Similarly, a person of ordinary skill in the art will understand that one or more UEs (104-1, 104-2, ....104-N) may be individually referred to as the UE (104) and collectively referred to as the UEs (104). Although three UEs (104) are depicted in FIG. 1, however, any number of the user equipments (104) may be included without departing from the scopeof the ongoing description. In an embodiment, each UE (104) may have a unique identifier attribute associated therewith. In an embodiment, the unique identifier attribute may be indicative of at least one of a Mobile Station International Subscriber Directory Number (MSISDN), International Mobile Equipment Identity (IMEI) number, an International Mobile Subscriber Identity (IMSI), a Subscriber Permanent Identifier (SUPI), and the like.
[0083] In an embodiment, the UE (104) may include smart devices operating in a smart environment, such as an Internet of Things (loT) system. In such an embodiment, the UE (104) may include, but is not limited to, smartphones, smart watches, smart sensors (e.g., mechanical, thermal, electrical, magnetic, etc.), networked appliances, networked peripheral devices, networked lighting system, communication devices, networked vehicle accessories, networked vehicular devices, smart accessories, tablets, smart television (TV), computers, a smart security system, a smart home system, other devices for monitoring or interacting with or for the users (102) and / or entities, or any combination thereof. A person of ordinary skill in the art will appreciate that the UE (104) may include, but is not limited to, intelligent, multi-sensing, network- connected devices that can integrate seamlessly with each other and / or with a central server or a cloud-computing system or any other device that is network-connected.
[0084] In an embodiment, the UE (104) may include, but is not limited to, a handheld wireless communication device (e.g., a mobile phone, a smart phone, a phablet device, and so on), a wearable computer device (e.g., a head-mounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a Global Positioning System (GPS) device, a laptop computer, a tablet computer, or another type of portable computer, a media playing device, a portable gaming system, and / or any other type of computer device with a wireless communication capabilities, and the like. In an embodiment, the UE (104) may include, but is not limited to, any electrical, electronic, electro-mechanical, or an equipment, or a combination of one or more of the above devices, such as virtual reality (VR) devices,augmented reality (AR) devices, a laptop, a general-purpose computer, a desktop, a personal digital assistant, a tablet computer, a mainframe computer, or any other computing device. In addition, the UE (104) may include one or more in-built or externally coupled accessories including, but not limited to, a visual aid device such as a camera, an audio aid, a microphone, a keyboard, and input devices for receiving input from the user (102) or an entity such as touch pad, a touch enabled screen, an electronic pen, and the like. A person of ordinary skill in the art will appreciate that the UE (104) may not be restricted to the mentioned devices and various other devices may be used.
[0085] In FIG. 1, the UE (104) may communicate with the system (108) via a network (106) to send interference information to the system (108). The system (108) is configured to perform cross-link interference (CLI) mitigation based on the interference information received from the UE (104). In an embodiment, the network (106) may include at least one of a Fifth Generation (5G) network, a Sixth Generation (6G) network, or the like. The network (106) may enable the UEs (104) to communicate with other devices in the network architecture (100) and / or with the system (108). The network (106) may include a wireless card or some other transceiver connection to facilitate this communication. In another embodiment, the network (106) may be implemented as or include any of a variety of different communication technologies such as a wide area network (WAN), a local area network (LAN), a wireless network, a mobile network, a Virtual Private Network (VPN), the Internet, the Public Switched Telephone Network (PSTN), or the like. In an embodiment, the network (106) may include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. In an embodiment, the UE (104) may be communicatively coupled with the network (106). The system (108) may receive a connection request from the UE (104). The system (108) may send an acknowledgment of the connection requestto the UE (104). The UE (104) may transmit a plurality of signals in response to the connection request. Once the connection is established, the system (108) may perform radio interference mitigation (i.e., cross-link interference (CLI) mitigation). A process of CLI mitigation is explained in greater detail in conjunction with FIGS. 2 - 7.
[0086] Although FIG. 1 shows exemplary components of the network architecture (100), in other embodiments, the network architecture (100) may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 1. Additionally, or alternatively, one or more components of the network architecture (100) may perform functions described as being performed by one or more other components of the network architecture (100).
[0087] FIG. 2 illustrates an exemplary block diagram (200) of the system (108), in accordance with an embodiment of the present disclosure.
[0088] In an embodiment, the system (108) may include one or more processor(s) (202). The one or more processor(s) (202) may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and / or any devices that process data based on operational instructions. Among other capabilities, the one or more processor(s) (202) may be configured to fetch and execute computer-readable instructions stored in a memory (204) of the system (108). The memory (204) may be configured to store one or more computer-readable instructions or routines in a non-transitory computer readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory (204) may comprise any non-transitory storage device including, for example, volatile memory such as random-access memory (RAM), or non-volatile memory such as erasable programmable read only memory (EPROM), flash memory, and the like.
[0089] In an embodiment, the system (108) may include an interface(s) (206). The interface(s) (206) may comprise a variety of interfaces, for example, interfaces for data input and output devices (I / O), storage devices, and the like. The interface(s) (206) mayfacilitate communication through the system (108). The interface(s) (206) may also provide a communication pathway for one or more components of the system (108). Examples of such components include, but are not limited to, a processing engine (208) and a database (210).
[0090] In an embodiment, the processing engine (208) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine (208). In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine (208) may be processor-executable instructions stored on a non-transitory machine-readable storage medium, and the hardware for the processing engine (208) may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine (208). In such examples, the system (108) may comprise the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the system (108) and the processing resource. In other examples, the processing engine (208) may be implemented by electronic circuitry.
[0091] In an embodiment, the database (210) may store data that may be generated as a result of functionalities implemented by any of the components of the processor (202) or the processing engine (208). In an embodiment, the database (210) may be indicative of including, but not limited to, a relational database, a distributed database, a cloud-based database, or the like. In an exemplary embodiment, the processing engine (208) may include one or more units having functions that may include, but are not limited to, testing, storage, and peripheral functions, such as a wireless communication unit for remote operation, and the like.
[0092] In an embodiment, the processing engine (208) is configured to perform radio interference mitigation (RIM) (e.g., cross-link interference (CLI) mitigation). In some embodiments, the processing engine (208) may be implemented as one or more gNBs (victim gNBs and aggressor gNBs). In an aspect, the one or more gNBs may be configured to perform radio interference mitigation (RIM) (e.g., CLI mitigation) in the network (106).
[0093] In an operative aspect, the system (108) may be part of the victim base station (e.g., victim gNB). The victim gNB comprises the processing engine (208). The processing engine (208) comprises a processing unit (212) and a communication unit (214). The processing unit (212) and the communication unit (214) are communicatively coupled to each other to perform radio interference mitigation (RIM) in the network (106).
[0094] The communication unit (214) is configured to receive one or more measurement configurations from an aggressor network node over a reference signal using a standard interface of one or more standard interfaces.
[0095] The one or more standard interfaces comprise a Fl interface, an Xn interface, and an air interface. In an aspect, the Fl interface refers to an interface defined between the central unit (CU) and the distributed unit (DU) in the network (e.g., disaggregated radio access network architecture). The Fl interface enables control and user plane communication split, facilitating flexible deployment and centralized processing. In an aspect, the Xn interface between two base stations (e.g., between two gNBs) in the network. The Xn interface supports inter-cell coordination functions such as handover, load balancing, and data forwarding. In an aspect, the air interface refers to a wireless communication link between the user equipment (UE) and the base station (gNB). The air interface enables transmission and reception of radio signals over the physical medium using defined protocols and waveforms.
[0096] To perform CLI mitigation, a gNB-central unit (CU) (also referred to as a base station) first exchanges measurement configuration details with neighbouringgNBs (such as a CU and its distributed units (DUs)) over one or more reference signals, such as downlink reference signals using standard Xn or Fl interfaces to measure interference from neighboring cells. In an aspect, the one or more measurement configurations comprise, but not limited to, Non-Zero-Power (NZP) Channel State Information-Reference Signal (CSI-RS) configurations, Zero-Power CSI-RS (ZP CSI-RS) configurations, one or more Synchronization Signal Blocks (SSBs), and Sounding Reference Signal (SRS).
[0097] In an embodiment, a Non-Zero-Power (NZP) Channel State Information-Reference Signals (CSI-RS) (NZP CSI-RS) or a zero-power CSI-RS (ZP CSI-RS) is used to exchange measurement configuration details. The NZP CSI-RS is a predefined signal that can be transmitted by the gNB and measured by other devices. The NZP CSI-RS is typically configured for UEs 104 to measure channel quality, but here the gNBs may leverage them for base station-to-base station measurement. In an aspect, the NZP CSI-RS configurations comprise at least one of a resource identifier (ID), a time slot, frequency subband, periodicity, a CSI-RS identifier, location in time or frequency, and power.
[0098] In an embodiment, the Zero-Power CSI-RS (ZP CSI-RS) resources are configured as muted reference elements, allowing the UE or network node (e.g., gNB) to measure interference and noise without desired signal transmission. The ZP CSI-RS measurements enable accurate detection and mitigation of cross-link interference (CLI) through improved resource coordination and scheduling decisions. In an embodiment, the Synchronization Signal Blocks (SSBs) are configured as reference signals to enable a UE to measure interference levels from neighboring cells or beams. The SSB measurements assist in identifying and mitigating cross-link interference (CLI) through informed scheduling and beam management. In an embodiment, the Sounding Reference Signals (SRS) are configured to enable uplink-based measurements of interference conditions across time, frequency, or spatial resources. The SRSmeasurements facilitate detection and mitigation of cross-link interference (CLI) by supporting adaptive scheduling, power control, and beam coordination.
[0099] In an embodiment, the one or more measurement configurations comprise at least one first information element (IE). The at least one first IE comprises served cell information. In an embodiment, the served cell information comprises details about the served cell, i.e., the cell currently serving the UE. The served cell information includes parameters such as cell identifier (ID) (e.g., physical cell identifier (PCI)), frequency information, bandwidth, reference signal configuration, measurement quantities related to the serving cell (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ)).
[0100] In an embodiment, the measurement configuration exchange between the gNB-CU and a gNB-DU may happen using the Fl interface. In particular, the gNB-CU of a victim cell, say Cell B, can configure its gNB-DU with measurement gaps or instructions to measure certain radio resources. For instance, the gNB-CU B may receive information (via Xn interface from gNB-CU A) about Cell A’s CSI-RS transmissions, such as a time slot, a frequency subband, a periodicity, and an identifier of the CSI-RS that Cell A may send for CLI measurement. The gNB-CU B may then use the Fl interface to send a measurement configuration message to the gNB-DU B. The measurement configuration message includes the NZP CSI-RS resource ID of Cell A and the expected periodicity / occasions. As a result, the gNB-DU B knows when to listen for that CSI-RS in an air interface during Cell A’s transmission, using its uplink receiver (which is normally idle during Cell B’s uplink (UL) slot if Cell B is not transmitting at that time, or using a spare receiver chain if simultaneously serving UL).
[0101] Similarly, the neighboring gNBs share their CSI-RS (or SSB) configurations related to interference measurement via the Xn interface. In one embodiment, when the gNB-CU A decides to initiate interference coordination, the gNB-CU A may select or dedicate an NZP CSI-RS resource for CLI measurement and signal this to gNB-CU B over the Xn interface (e.g., an Xn message containing NZP-CSI-RS config for interference measurement, including parameters like resource ID, location in time / frequency, power, etc.). This exchange of interference measurement is mutual, and both cells share their measurement signals, so each can measure the other if needed. Further, the use of Xn interface ensures that the exchange works for inter-gNB scenarios (e.g., inter-vendor or multi-operator, if Xn or another interconnect is available through a coordination function). In cases where the two cells are under the same gNB-CU (say a dual-sector gNB), the CU itself may ensure that the two DUs use known reference signals for measuring each other, effectively performing the coordination internally.
[0102] In an embodiment, the measurement configuration exchange may be done proactively, i.e., periodically or during a call setup, between the gNBs. In that case, the gNBs may inform each other of CSI-RS resources available for measuring interference. In another embodiment, the measurement configuration exchange may be done reactively, i.e., when interference is detected. In that case, a cell, such as a victim cell or victim gNB, can request the neighboring cell, such as an aggressor cell or aggressor gNB, to start transmitting a specific CSI-RS pattern for measurement. The ‘victim cell’ or ‘victim gNB’ refers to a gNB experiencing CLI during its uplink reception due to downlink transmissions from a neighboring gNB (i.e., the aggressor gNB). The ‘aggressor cell’ or ‘aggressor gNB’ refers to a gNB whose downlink transmissions cause CLI to a neighboring gNB (victim gNB) during its uplink reception. The measurement configuration exchange sets the foundation for obtaining quantitative interference metrics.
[0103] Thereafter, the processing unit is configured to perform interference measurement based on the received measurement configuration to identify a resource causing radio interference. In an aspect, the base station or network node (e.g., gNB) performs interference measurements using network-configured resources designed to capture cross-link interference (CLI) conditions, including non-zero power (NZP) channel state information-reference signal (CSI-RS) (NZP CSI-RS), reference signals(e.g., Synchronization signal block (SSB), sounding reference signal (SRS)) or muted resources (e.g., ZP CSI-RS) across defined time-frequency occasions. Further, the controlled measurement instances enable accurate estimation of interference arising from conflicting uplink and downlink transmissions, allowing the network to identify affected resources, beams, or cells. A vulnerable resource is determined by analyzing the measured interference over such configured resources and comparing the measured interference against predefined thresholds; if the interference power or signal to interference plus noise ratio (SINR) degradation exceeds the threshold, the corresponding resource (e.g., slot, symbol, physical resource block (PRB), or beam) is classified as vulnerable to CLI. Further refinement may be achieved by evaluating temporal patterns (e.g., recurring interference in specific slots) and spatial patterns (e.g., particular beams or directions), along with correlation to neighboring cell transmission configurations such as uplink / downlink switching. Based on the evaluation, the network node or base station classifies vulnerable resources and utilizes the information to perform adaptive scheduling, link direction coordination, beam management, and power control for effective CLI mitigation.
[0104] In an operative aspect, the victim gNB may perform interference measurement based on the measurement configuration received from the aggressor gNB to identify a downlink beam / SSB index / CSLRS resource ID of the neighbouring cell(s) which is causing interference to the victim gNB. In an aspect, the interference measurement comprises, but not limited to, reference signal received power (RSRP) or received signal strength indicator (RSSI).
[0105] In particular, the victim gNB may derive interference metrics such as Reference Signal Received Power (RSRP) or Received Signal Strength Indicator (RSSI) for the neighbor’s CSI-RS to identify a cell causing interference. In an embodiment, if multiple beams or reference signals are used, the victim gNB may identify which one is strongest. For example, a gNB-CU A might configure different CSI-RS resources on different beams or reuse a periodic Synchronization Signal Block(SSB) burst as measurement signals. A gNB-DU B may then report which SSB index or CSI-RS resource ID had the highest received power, indicating that the beam is likely pointing toward Cell B and causing the interference.
[0106] Further, the processing unit (212) is configured to prepare an interference report based on the resource identification. In an aspect, the interference report comprises an interference level, an identifier of strongest interfering beam, a synchronization signal block (SSB) index, CSI-RS resource ID, time indication or frequency subband index.
[0107] In an aspect, the interference report is prepared based on resource identification involves compiling measured interference metrics (e.g., power, SINR) for the resources identified as vulnerable. The report may further include timefrequency locations, affected beams or cells, and severity levels of interference. The interference report provides a structured representation that may be used by the network for decision-making and coordination. In this way, the interference report enables efficient application of mitigation actions like scheduling adjustments, beam adaptation, or power control.
[0108] The victim gNB sends the interference report to its gNB-CU (victim CU), identifying the strongest interfering beam. In an embodiment, the victim gNB reports the cell causing interference using one of a Distributed Unit (DU) to central unit (CU) reporting model and a CU to CU, DU, or Neighbor Reporting model.
[0109] In the DU to CU reporting model, a victim gNB-DU (say, gNB-DU B) may send the interference report to gNB-CU (say, gNB-CU B). The interference report includes one or more parameters, such as the measured interference level, an SSB index, and an identifier of the strongest interfering beam from an aggressor cell (say, Cell A). For instance, the interference report may comprise information such as Interferer Cell ID = A, Beam ID = 5, RSRP = X dBm. Further, in case of multiple measurements, the interference report may list the top N interfering beams, and the strongest beam among the N interfering beams may become a primary interest forimmediate mitigation. The gNB-CU B may then log the interference report and may also decide if any action needs to be taken or not based on a predefined threshold set for each of the one or more parameters and impact on a Quality of service (QoS).
[0110] In CU to CU or DU or the Neighbor Reporting model, the victim gNB-DU (say, gNB-DU B) may send the interference report directly to the aggressor gNB-CU (say, gNB-CU A) or the aggressor gNB-DU (say, gNB-DU A) or to a connected neighbour, depending on the implementation. In one approach, a gNB-CU B may communicate with the gNB-CU A over the Xn interface to inform that a beam (say, beam #5) is causing Y dB interference to a cell of the gNB-CU B. The communication can be in the form of a specific message defined as a CLI indication or as part of an Xn application protocol (AP) message (since Xn already supports various inter-cell coordination messages). Alternatively, the gNB-DU B might directly signal the neighbor’s DU or CU if a direct link exists.
[0111] Further, once the interfering beam (or subband, or time) is identified, the processing engine (208) or the victim gNB invokes a coordinated CLI mitigation.
[0112] The processing unit (212) is configured to generate an interference mitigation request based on the interference report. In an aspect, the interference mitigation request is a CLI mitigation request. In an aspect, the interference mitigation request (or CLI mitigation request) comprises an interfering beam and a suggested mitigation action to be taken to mitigate the radio interference (i.e., CLI). In an aspect, the suggested mitigation action comprises transmit power reduction, beam switching, beam muting, transmission timing adjustment, and duration for mitigation or periodicity for mitigation. In the transmit power reduction, the transmit power is reduced based on identified resources that lower the interference leakage toward victim links. The transmit power reduction helps balance link performance while minimizing cross-link interference (CLI). In the beam switching, switching to an alternative beam direction avoids transmitting toward interference-sensitive regions. Beam switching reduces spatial overlap with victim receivers and mitigates CLI. In the beam muting,transmission on specific beams is temporarily disabled to prevent interference on affected resources. The beam muting is applied selectively where severe CLI is detected. In transmission timing adjustment, transmission timing (e.g., slot or symbol alignment) is shifted to reduce overlap between conflicting uplink and downlink transmissions. The transmission timing adjustment helps to avoid peak interference instances. In the duration / periodicity for mitigation, defining how long or how frequently the mitigation actions are applied. The duration / periodicity enables adaptive and controlled application based on interference dynamics.
[0113] In an aspect, the CLI mitigation request comprises one or more second information elements (IES) corresponding to a victim cell identifier, an aggressor cell identifier, an interference cause or an interference level, and the suggested mitigation action. So, the one or more second IEs are configured to convey information associated with the interference, including at least the victim cell identifier corresponding to a cell experiencing interference, the aggressor cell identifier corresponding to a cell causing the interference, and at least one of the interference cause or the interference level indicative of a source or severity of the interference, respectively, and further comprising the suggested mitigation action specifying at least one corrective measure to alleviate the interference. In this way, the one or more second IEs enable coordinated interference mitigation between the victim network node and the aggressor network node.
[0114] In an aspect, the interference level refers to a categorized indication of the severity of cross-link interference, classified as high, medium, or low based on measured metrics such as interference power or SINK degradation. The interference level comprises high level, low level and medium level. The high level indicates severe interference requiring aggressive mitigation (e.g., muting or major rescheduling), while the medium level suggests moderate impact with selective adjustments. The low level represents minor interference where minimal or no corrective action may be sufficient.Classification of the interference level enables the network (106) to prioritize and tailor mitigation actions efficiently.
[0115] In an aspect, the CLI mitigation request further comprises a beam identifier, a subband index, and a timing offset corresponding to interference, a request identifier, and a CLI severity metric. The CLI severity metric comprises measured interference power, and a signal to interference plus noise ratio (SINK).
[0116] In particular, the victim gNB CU generates the CLI mitigation request message addressed to the aggregator gNB (i.e., the interferer). In an embodiment, the CLI mitigation request is sent to the aggregator gNB-CU over the Xn interface. In cases where both the cells (i.e, the victim cell and the aggregator / interfering cell) are under one CU, the CU may internally handle it by sending an internal function call to adjust the interfering cell’s transmission.
[0117] In an embodiment, the CLI mitigation request contains information that helps the aggregator gNB to take appropriate mitigation action to eliminate the CLI. The information includes an indication that a victim cell, say Cell B, is experiencing interference from an aggregator / interfering cell, say Cell A. In an example embodiment, the indication may be presented as a header or a cause code like Interference Mitigation Requested by Cell B due to CLI. The information may also include a target of interference suppression, which can be a beam identifier (e.g., beam #5) and optionally a physical-layer reference (like CSLRS resource 17 or SSB index 5 corresponding to that beam). In some cases, the target can be a frequency subband index if the interference is localized to a part of the spectrum (for SBFD, maybe Cell B indicates that the interference is mainly on the high subband of the carrier) and / or a time indication if relevant (for example, during micro-slot 3 of slot 10, the transmission from a particular DL is overlapping a particular UL). The information may further include a suggested mitigation action. In some embodiments, the suggested mitigation action can be implicit action, i.e., the neighbor / interfering cell, on receiving such a request, might have a default response like reduce power by X dB on that beam for thenext Y milliseconds. In some embodiments, the suggested mitigation action can be an explicit action i.e., the CLI mitigation request might include a note suggesting mitigation action to be taken such as reduce DL power on beam #5 by 3 dB or switch beam #5’s transmission to subband 2 (away from subband 1 which my UL uses) or mute beam #5 for the next 1ms or adjust your frame timing by +A to not overlap this UL grant. It should be noted that the mitigation action may be chosen based on severity, i.e., the small interference might warrant just a power tweak, while severe interference might require a brief mute or more drastic pattern change. In one embodiment, the CLI mitigation request may also include a CLI severity metric (e.g., the measured interference power or an interference-to-noise ratio) so that the aggressor gNB can scale its response appropriately. In some cases, the information may also include an optional duration or periodicity for the mitigation. For instance, the information may indicate whether this is a one-time request (mitigate now) or a persistent situation (every time you transmit beam #5 in certain conditions). However, persistent situations are generally handled by higher-level configuration if needed.
[0118] In an aspect, the processing unit configured to determine whether the interference measurement is within a predefined threshold. Based on the determination, the processing unit is configured to initiate the communication of the CLI mitigation request towards the aggressor network node. So, the victim network node evaluates the measured interference level by comparing against the predefined threshold representing an acceptable interference limit. If the interference measurement is within the threshold, no immediate action may be required; however, if the interference exceeds the threshold, it indicates harmful cross-link interference conditions. Based on the determination that the interference exceeds the threshold, the processing unit (212) initiates communication of the CLI mitigation request toward the aggressor network node, requesting appropriate mitigation actions to reduce the interference. This ensures that mitigation procedures are triggered only when necessary, enabling efficient and adaptive interference management.
[0119] In an aspect, the communication unit (214) is configured to communicate the generated interference mitigation request to the aggressor network node (e.g., aggressor gNB) through one of the standard interfaces (e.g., Fl interface or Xn interface) or multi-hop coordination. In an aspect, the multi-hop coordination refers to an exchange of CLI-related messages across multiple network nodes via intermediate nodes, rather than direct one-hop communication between the aggressor network node and the victim network node. The multi-hop signaling enables coordination of interference mitigation actions in scenarios involving indirect interference paths or multi-cell interactions. The multi-hop signaling facilitates network-wide awareness and alignment of scheduling, power control, or beam management decisions. The multi-hop signaling is useful in dense deployments where interference effects propagate beyond immediate neighboring cells.
[0120] Further, upon receiving the CLI mitigation request, the aggressor cell / gNB (i.e., Cell A) may perform the suggested mitigation action. In an aspect, the aggressor network node is configured to perform the suggested mitigation action on the identified resource.
[0121] If the message came to gNB-CU A for a gNB-DU A, the gNB-CU A instructs the gNB-DU A via Fl interface to implement the mitigation action (e.g., adjust the beam’s power or transmission pattern). If the request is directly received by gNB-DU A (which is less likely), the gNB-DU A implements it directly. In an embodiment, the aggressor gNB may also respond to the CLI Mitigation Request with an acknowledgment or status (like Action taken or Unable to comply if, for example, the beam is currently serving critical traffic and cannot be muted) back to the victim gNB.
[0122] It should be noted that the interference mitigation performed by the aggressor cell / gNB is granular, as the CLI Mitigation Request targets a specific beam and / or subband. For example, the Cell A, i.e., the gNB-CU A, can apply the power reduction only for the beam towards Cell B (users in other directions remainunaffected). Or if using SBFD, perhaps Cell A might be transmitting on an upper subband that coincides with Cell B’s uplink, so the CLI Mitigation request might ask Cell A to temporarily move that transmission to a lower subband (if available) or to use a different symbol timing. The system (108) thus enables frequency-separated full-duplex operation where cells dynamically negotiate which subbands to use for DL vs UL to avoid mutual interference. This kind of subband negotiation might be done via a sequence of CLI requests and responses, effectively coordinating a pattern, much faster and more flexible than a static network-wide configuration.
[0123] Additionally, in some network deployments, a direct Xn interface connectivity may not exist between certain interfering cells (for example, interoperator scenarios or when an intermediate relay or IAB node is used). In those cases, the system (108) may use a multi-hop signaling method for the CLI mitigation. In one embodiment, in the multi-hop signaling method, if the victim gNB (i.e., the Cell B) cannot directly reach the aggregator / interf ering gNB i.e., the Cell A via the Xn interface, the victim gNB may send the CLI Mitigation request via any available route. One option is through a chain of neighboring gNBs: e g., B -> (Xn) -> C -> (Xn) -> A, if cell C has connections to both cells B and A. The CLI Mitigation request message may carry the end target identifier (i.e., the Cell A) and can be forwarded by the intermediate cell C. It should be noted that each hop may add a little latency in the CLI mitigation. However, if the interference is persistent, the multi-hop signaling method is still worth executing. In another embodiment, the processing engine (208) or the victim gNB may use a relay UE, such as the UE (104), to perform the multi-hop signaling method for the CLI mitigation. For instance, a UE under Cell B’s coverage (or a special device) can be utilized to transmit the interference information to Cell A if, say, Cell A allows measurement reports from foreign UEs. In particular, the relay UE receives an interference indication from its serving cell, i.e., the Cell B, and forwards it to an interfering cell, i.e., the Cell A. So, even in the absence of standardXn connectivity, the system (108) ensures that coordination happens between the gNBs for the CLI mitigation using the multi-hop signaling method.
[0124] It should be noted that the gNB-CU, as it has a broader view (it can communicate with other CUs, and it can manage multiple DUs), acts as a central unit for orchestrating inter-cell communication, receiving interference reports, and generating CLI mitigation requests. The gNB-DU is responsible for performing interference measurements and executing local transmission adjustments as per the CU’s instructions. This split in the responsibilities of the gNB-CUs and the gNB-DUs is advantageous as the CUs (possibly aided by a central RAN Intelligent Controller in 0-RAN systems) can run more advanced algorithms to decide when to trigger a CLI mitigation request, using machine learning on interference patterns or negotiating trade-offs between multiple cells. Meanwhile, the DUs may be kept simple and fast, executing measurements and power changes quickly on command.
[0125] In an exemplary scenario, assume that Cell A and Cell B are operating dynamic TDD. Cell A happens to schedule a downlink burst on Beam 5 (pointing toward Cell B’s coverage area) at the same time Cell B schedules an uplink slot for one of its UEs. Cell B’s gNB-DU hears a lot of interference on its UL (its receivers pick up Cell A’s signal), So, if the system (108) uses the pre-arranged NZP CSI-RS config, Cell B’s DU may measure the interference and identify the Beam 5 of Cell A as the culprit (since that CSLRS was strongest). Cell B’s DU may then report this to Cell B’s CU, which may quickly evaluate that the interference is above the predefined thresholds. Then, Cell B’s CU may send a CLI mitigation request to Cell A’s CU over the Xn interface, indicating interference from Beam 5 and requesting power lowering. Thereafter, Cell A’s CU receives it and forwards instructions to Cell A’s DU to reduce Beam 5 power by, say, 6 dB for the upcoming transmissions. Further, Cell A’s Beam 5 power is reduced, and Cell B’s UL experiences significantly less interference, allowing the UE’s transmission to be decoded correctly. In some circumstances, Cell A may later gradually increase power back or request feedback if the interferencecondition persists, potentially leading to another coordination if needed. The process may repeat as necessary and can also be combined with other interference avoidance strategies (like scheduling adjustments).
[0126] In an aspect, the aggressor network node is configured to perform the suggested mitigation action on the identified resource based on the CLI severity metric. Appropriate interference mitigation actions or techniques are applied in accordance with the measured level of cross-link interference (CLI) on specific time-frequency or spatial resources. The CLI severity metric, which may be categorized as high, medium, or low based on interference power or SINK degradation, guides the selection and intensity of the mitigation action. For instance, resources experiencing high severity may undergo aggressive actions such as beam muting or significant transmit power reduction, whereas medium or low severity levels may trigger adaptive measures such as beam switching or minor scheduling adjustments. The severity-aware execution of action ensures efficient utilization of network resources while effectively minimizing interference impact.
[0127] Upon performing the suggested mitigation action, the aggressor network node is configured to communicate a CLI mitigation response to the victim network node. In an aspect, the CLI mitigation response is a structured message sent by the aggressor network node towards the victim network node after evaluating the CLI mitigation request, conveying whether and how the requested actions are applied.
[0128] The CLI mitigation response comprises at least one third information elements (IES) corresponding to the target cell identifier or the request identifier, an outcome, a mitigation identifier, a mitigation duration, and an indication of successful mitigation or unsuccessful mitigation. In an aspect, the CLI mitigation response includes one or more third information elements (IEs) that convey the result and details of the mitigation action taken. The IEs may include the target cell identifier or request identifier to associate the response with a specific cell or prior request, the outcome indicating what decision was made (e.g., accepted, rejected, partially applied), themitigation identifier specifying the particular mitigation scheme or action applied, the mitigation duration indicating how long the action will remain in effect, and the indication of successful or unsuccessful mitigation reflecting whether the applied action effectively reduced the interference. In essence, the response communicates back to the requesting entity what action was taken, how the mitigation action is tracked, how long the mitigation action will apply, and whether the mitigation achieved the intended interference reduction.
[0129] The outcome comprises one of mitigation action accepted, mitigation action rejected, or mitigation action partially accepted. If the mitigation action is accepted, for example, the mitigation action includes mute 4 slots for 5ms or power reduced by 10 dB for 5ms. If the action is performed i.e., muting 4 slots for 5ms or reducing power by 10 dB for 5ms, the outcome of the mitigation action is accepted. But if the mitigation action is partially accepted, i.e., suggested action is mute 4 slots for 5ms, but only 2 slots are muted for 5ms, then the outcome of the mitigation action is partially accepted. Further, if the mitigation action is rejected, the CLI mitigation response comprises a cause of the mitigation action rejection. For example, cause of the mitigation action rejection comprises unable to comply due to load.
[0130] In an aspect, the CLI mitigation response includes information elements (IES) such as, but not limited to, the target cell identifier or request identifier (to map the response to the original request), the outcome, the mitigation identifier (indicating the selected action), the mitigation duration (how long the action will be applied), and a success indication. The outcome specifies whether the mitigation action is fully accepted, rejected, or partially accepted. For example, consider Cell A requesting Cell B to reduce interference on certain slots due to high CLI. In response, Cell B sends a CLI mitigation response including: (i) the request ID linking to Cell A’s request, (ii) outcome = partially accepted, (iii) mitigation ID = transmit power reduction + beam switching, (iv) mitigation duration = 10 slots, and (v) success indication = successful.If Cell B cannot fully comply (e.g., due to its own traffic constraints), it may reject some actions while accepting others, hence marking the outcome as partially accepted.
[0131] In an aspect, upon receiving the CLI mitigation response, the processing unit configured to verify whether interference level has reduced to a reference interference level, after performing the mitigation action. So, the effectiveness of the applied mitigation action is evaluated by comparing post-mitigation interference measurements with a predefined reference interference level (e.g., threshold or target SINR). After performing the mitigation, the network node (e.g., gNB) measures the interference again on the affected resources using the same network- configured measurement resources to ensure consistency. The measurements are performed on configured reference signals (e.g., SSB, SRS, CSI-RS) or muted resources (e.g., ZP CSI-RS) over the same time-frequency locations, and metrics such as interference power, RSSI, or SINR are recalculated under the updated conditions. The newly obtained measurements are then compared with prior values or the reference threshold to determine whether the interference level has decreased to or below the desired level. If the newly obtained measurements are decreased or below the threshold level, the mitigation is considered successful; otherwise, additional or alternative mitigation actions may be triggered. The repeated measurement and comparison process ensures accurate verification of effective cross-link interference (CLI) mitigation.
[0132] Based on the verification, the communication unit is configured to communicate a feedback message to the aggressor network node. The feedback message comprises an indication of successful application of the mitigation action or the requirement of additional or alternative mitigation action.
[0133] In an aspect, upon receiving the feedback message from the victim network node (e.g., gNB), the aggressor network node is configured to analyze the feedback message to verify whether the suggested mitigation action is successful. So, the aggressor network node, after applying the mitigation action, receives the feedback message from the victim network node (e.g., gNB) indicating the observed interferencecondition. The aggressor node analyzes the feedback, which may include interference measurements, success indicators, or updated severity levels, to determine whether the applied mitigation has effectively reduced cross-link interference (CLI). If the feedback confirms improvement to the acceptable level, the mitigation is considered successful; otherwise, the aggressor node may refine or select alternative mitigation actions. This mechanism enables closed-loop coordination between network nodes for efficient interference management.
[0134] Based on the analysis, the aggressor network node is configured to communicate a feedback response towards the victim network node. In an aspect, the feedback response comprises an alternative action or a remedial action. The aggressor network node, after evaluating feedback message from the victim network node, transmits the feedback response indicating subsequent course of action. The feedback response may include an alternative action (e.g., a different mitigation technique such as beam switching instead of power reduction) if the initially applied action was ineffective or infeasible. Additionally, the response may specify a remedial action, representing corrective measures (e.g., further power reduction, extended muting duration, or timing adjustment) to address residual interference. The exchange of feedback message and response enables iterative and adaptive coordination between nodes for effective cross-link interference (CLI) mitigation.
[0135] In an aspect, the processing unit (212) configured to analyze the feedback response. Upon determining the unsuccessful mitigation based on the analysis of the feedback response, the processing unit is configured to perform the remedial action. The remedial action comprises re-initiation of CLI mitigation. The victim network node evaluates the feedback response received from the aggressor network node to determine the effectiveness of the previously applied mitigation action. The analysis may include reviewing success indicators, updated interference levels, or the nature of the action taken by the aggressor node. If the victim network node determines that the mitigation is unsuccessful (e.g., interference remains above an acceptable threshold),its processing unit initiates the remedial action. The remedial action includes reinitiating the CLI mitigation procedure, which may involve sending a new mitigation request, possibly with modified parameters, alternative actions, or stricter requirements. This ensures continued and adaptive interference management until acceptable interference levels are achieved.
[0136] Further, the aggressor network node configured to determine whether an occurrence of the CLI mitigation request is repeated more than a predefined number of times for a predefined duration. Based on the determination, the aggressor network node is configured to initiate a coordinated scheduling action with the victim network node. So, the aggressor network node monitors how frequently it receives CLI mitigation requests from the victim network node over a given time window. If the same or similar mitigation request is observed to repeat more than the predefined number of times within the predefined duration, the aggressor network node infers that the interference is persistent and not adequately resolved by isolated mitigation actions. Based on the determination, the aggressor network node initiates a coordinated scheduling action, such as aligning uplink / downlink patterns, jointly adjusting transmission timings, or reserving interference-free resources in coordination with the victim node. For example, assume Cell A (victim) repeatedly sends CLI mitigation requests to Cell B (aggressor) 5 times within 20 ms due to recurring uplink-downlink conflicts. Upon detecting that the number of CLI mitigation requests exceeds a configured threshold (e.g., 3 requests in 20 ms), Cell B determines that simple actions like temporary power reduction are insufficient. Consequently, Cell B initiates coordinated scheduling with Cell A, such as synchronizing slot configurations (e.g., aligning DL / UL slots) or reserving specific symbols for interference-free transmission, thereby reducing persistent CLI more effectively.
[0137] In an aspect, the radio interference mitigation (RIM) (i.e., CLI mitigation) is managed in sub-band full duplex (SBFD) and dynamic time division duplex (TDD) network. The system (108) enables robust cross-link interference (CLI) coordinationby exchanging measurement configurations and interference information, and by issuing directed mitigation commands, so that cells in the network operate in flexible duplex modes (including SBFD) with significantly reduced mutual interference. This improves uplink reliability (victim cells suffer less dense from neighbors) and overall network capacity (since cells need not fall back to safe static configurations except as a last resort). Thus, the deployment of advanced duplex schemes is facilitated in dense networks, paving the way for features such as cell-level full-duplex and highly dynamic TDD in the network.
[0138] In an aspect, the radio interference mitigation (RIM) is performed based on beam-level and subband- based coordination. The system (108) makes integrated use of detailed beam-level interference measurement and signaling between neighboring network node (e.g., base stations (gNBs)). Cross-link interference (CLI) is measured using configured reference signals (NZP CSI-RS), identifies precisely which beam or subband from a neighboring cell is causing interference, and then explicitly requests targeted mitigation actions (e.g., power reduction, subband switching, timing adjustment). In this way, the system (108) provides detailed, targeted beam-level or subband-level signaling combined with dynamic inter-cell mitigation requests to handle interference
[0139] Although FIG. 2 shows exemplary components of the system (108), in other embodiments, the system (108) may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 2. Additionally, or alternatively, one or more components of the system (108) may perform functions described as being performed by one or more other components of the system (108).
[0140] FIG. 3 illustrates a system architecture (300) for the CLI mitigation in the network (106), in accordance with an embodiment of the present disclosure. FIG. 3 is explained in conjunction with the FIGs. 1 and 2.
[0141] The system architecture (300) may include an aggressor gNodeB Central Unit (gNB-CU) 302, an aggressor gNB- Distributed Unit (DU) 304, a victim gNB-CU 306, and a victim gNB-DU 308. The aggressor gNB-CU 302 is a central unit of a gNB whose downlink (DL) transmissions interfere with the uplink (UL) receptions of the neighbouring aggressor gNB-DU 304. In 5G NR networks using Dynamic Time Division Duplex (TDD) or Sub-band Full Duplex (SBFD), the interference may occur due to the aggressor gNB-CU 302 DL signals overlap in time and frequency with the victim gNB-DU 308 UL signals, leading to the CLI. Further, the gNB-DU 304 may be the distributed unit of the gNB-CU 302, which is transmitting downlink signals that interfere with the victim gNB-CU 306. The victim gNB-CU 306 may be a high- lay er control entity of the 5G network that is experiencing interference on the UL reception due to the DL transmissions of the neighbouring aggressor gNB-CU 302. Further, the gNB-DU 308 may be a low-layer entity of the victim gNB-CU 306 that directly handles radio operations, including measuring the interference caused by the aggressor gNB-CU 302 downlink transmissions during its uplink reception.
[0142] In an embodiment, the aggressor gNB-CU 302 may include a CLI coordination logic 310, a measurement configuration distributor 312, and a beam-level mitigation processor 314. Further, the aggressor gNB-DU 304 may include a beam control executor 316 and a real-time beam adjustment 318. The victim gNB-CU 306 may include a beam level CLI coordination 320, an explicit mitigation request generator 322, and a beam specific reporting handler 324. Further, the victim gNB-DU 308 may include a NZP CSLCLI measurement module 326, a strongest beam detector 328, and a detailed interference reporter 330.
[0143] In an embodiment, the measurement configuration distributor 312 may distributes Non-Zero-Power Channel State Information Reference Signal (NZP CSL RS) configuration details to the victim gNB-CU 306 and the victim gNB-DU 308 or the aggressor gNB-DU 304. The configuration details may include resource Identifier (ID), time slot, frequency subband, and periodicity, enabling the victim gNB-CU 306and the victim gNB-DU 308 to measure interference from the aggressor gNB-CU 302 transmissions. The measurement configuration distributor 312 may be configured to send an NZP-CSI RS measurement configuration to a central NZP-CSI RS measurement exchange node, facilitating configuration exchange via the Xn interface to the victim gNB-CU 306.
[0144] In an embodiment, the CLI coordination logic 310 may act as a central decision-making entity for CLI management within the aggressor gNB-CU 302. The CLI coordination logic 310 may oversee CLI mitigation by receiving CLI mitigation requests from the victim gNB-CU 306 or the victim gNB-DU 308. Further, the CLI coordination logic 310 may determine appropriate responses to the CLI mitigation requests such as power reduction, subband switching. The CLI coordination logic 310 is configured to receive a mitigation execution confirmation from the beam control executor 316, providing feedback on the success of mitigation actions. Further, the CLI coordination logic 310 may interact with the measurement configuration distributor 312 to initiate the CLI coordination process.
[0145] Further, the NZP CSLCLI measurement module 326 may measure interference from the aggressor gNB-CU 302 downlink transmissions using the configured NZP CSLRS resources, capturing metrics such as RSRP or RS SI during specified time / frequency slots. The NZP CSI-CLI measurement module 326 is configured to receive CLI measurement configurations from the victim gNB-CU 306 via the Fl interface, specifying the aggressor gNB-CU 302 NZP CSLRS configuration details. Further, the NZP CSI-CLI measurement module 326 is configured to send measured configuration details to the strongest beam detector 328.
[0146] The strongest beam detector 328 may analyse interference measurements to identify the strongest interfering beam from the aggressor gNB-CU 302 and the aggressor gNB-DU 304 such as the beam with the highest RSRP, identified by SSB Index and the CSLRS Resource ID. Further, the strongest beam detector 328 isconfigured to receive interference data from NZP-CSI RS CLI Measurement module 326.
[0147] The detailed interference reporter 330 may generate the detailed interference report containing the strongest interfering beam ID such as SSB Index 5 and interference level such as the RSRP value of the aggressor gNB-CU 302 and the aggressor gNB-DU 304, forwarding it to the victim gNB-CU 306 for processing. Further, the detailed interference reporter 330 is configured to receive beam identification from the strongest beam detector 328. The detailed interference reporter 330 is configured to send the report to the victim gNB-CU 306 via the beam-specific reporting handler 324 and the enhanced Fl interface.
[0148] The beam level CLI coordination 320 may oversee the CLI mitigation process at the victim gNB-CU 306, integrating interference reports and deciding on mitigation strategies. Further, the beam level CLI coordination 320 is configured to receive the explicit beam-level interference report from the victim gNB-DU 308 via the Fl interface. The beam level CLI coordination 320 is configured to interact with the CLI mitigation request generator to initiate mitigation signalling.
[0149] The beam specific reporting handler 324 may process and formats the interference report from the victim gNB-DU 308, ensuring beam-specific details such as SSB Index or CSLRS Resource ID are accurately conveyed. The beam specific reporting handler 324 is configured to receive the report from the detailed interference reporter 330 via the Fl interface. Further, the beam specific reporting handler 324 is configured to pass the processed data to the beam-level CLI coordination 320.
[0150] Further, the explicit mitigation request generator 322 may create an explicit CLI mitigation request message specifying the interfering beam ID, suggested mitigation action such as reduce power by 3 dB, and optional subband or timing details, based on an interference report. Further, the explicit mitigation request generator 322 is configured to send the explicit CLI mitigation request including Beam ID, power / subband / timing to the aggressor gNB-CU 302 via the enhanced Xn Interface.
[0151] Further, the beam control executor 316 may execute specific CLI mitigation actions on the identified interfering beam, such as reducing transmit power, switching to a different subband, or adjusting transmission timing, as instructed by the aggressor gNB-CU 302. The beam control executor 316 is configured to receive a targeted beam mitigation command from the NZP-CSI RS measurement exchange node, specifying the beam and action such as reduce power on Beam #5 by 3 dB. Further, the beam control executor 316 is configured to send a mitigation execution confirmation back to the CLI coordination logic 310, confirming action completion.
[0152] The real-time beam adjustment 318 may represent the actual adjustment of beam transmission parameters in real-time such as lowering power on a specific SSB Index or CSLRS Resource ID, ensuring immediate interference reduction. Further, the real-time beam adjustment 318 is directly linked to the beam control executor 316, reflecting the execution outcome on the air interface.
[0153] In some embodiments, the measurement configuration distributor 312 may send NZP CSLRS configurations via an enhanced Xn Interface to the victim gNB-CU 306 and / or the victim gNB-DU 308 during NZP CSLRS measurement exchange between the aggressor gNB-CU 302 and the victim gNB-DU 308. Further, the NZP CSLCLI measurement module 326 measure CLI interference from the aggressor gNB-CU 302, and the strongest beam detector 328 identifies the strongest interfering beam of the aggressor gNB-CU 302 such as Beam #5. Further, the detailed interference reporter 330 sends an Explicit beam-level interference report to the beam level CLI coordination 320 and the beam specific reporting handler 324 of the victim gNB-CU 306 via the Fl interface. Further, the explicit mitigation request generator 322 send an Explicit CLI Mitigation Request via the Enhanced Xn Interface to the aggressor gNB-CU 302. The explicit CLI mitigation request may include action that need to be taken by the gNB-CU 302 to mitigate CLI interference such as reduce power on Beam #5 by 3 dB. Further, the CLI coordination logic 310 may process the explicit CLI mitigation request and determine the actions that need to be performed by the aggressor gNB-CU302 and / or the aggressor gNB-DU 304. The CLI coordination logic 310 may then transmit the actions that are needed to be performed by the aggressor gNB-CU 302 to the beam-level mitigation processor 314. Further, the CLI coordination logic 310 transmit the actions that are needed to be performed by the aggressor gNB-DU 304 to the beam control executor 316 via the Fl interface. Finally, the actions are executed by the real-time beam adjustment 318.
[0154] FIG. 4 illustrates a system architecture 400 for the CLI mitigation in the network 106, in accordance with an embodiment the present disclosure. FIG. 3 is explained in conjunction with the FIGs. 1, 2, and 3.
[0155] The system 400 may include the aggressor gNB-CU 302, a victim gNB-CU 306, an aggressor gNB-DU 304, a victim gNB-DU 308, an intermediate gNB-CU 402, and a relay User Equipment (UE) 404. The intermediate gNB-CU 402 may be an optional base station that supports CLI coordination where direct connectivity is unavailable. The relay UE 404 may be a UE 104 used to relay the CLI requests when network-based paths are infeasible.
[0156] In an embodiment, the aggressor gNB-CU 302 may include a XnAP interface handler 406, an interface mitigation request processor 410, the CLI coordination logic 310, an interface mitigation action handler 412, the measurement configuration distributor 312, and a F1AP interface handler 408. Further, the victim gNB-CU 306 may include an interference reporting handler 424, a CLI mitigation response analyser 426, a F1AP interface handler 408, the CLI coordination logic 310, a measurement configuration handler 428, and an interference mitigation request generator 430. The aggressor gNB-DU 304 may include a Fl AP interface handler 408, a CLI mitigation action executor 414, a transmission beam controller 416, and an air interface Transmission module 418. Further, the victim gNB-DU 308 may include the F1AP interface handler 408, a CLI mitigation action verifier 432, the air interface Rx module 420, a CLI measurement engine 434, a strongest beam detector 328, and the interference report generator 330 (also referred to as detailed interference reporter(330) as shown in FIG. 3). The relay UE 404 may include the air interface handler 420 and the CLI relay module 422. The air interface Rx module (420) may communicatively coupled with the CLI relay module (422) of the relay UE (404).
[0157] Further, the intermediate gNB-CU 402 may include the XnAP interface handler 406 and the CLI request relay logic 436.
[0158] The XnAP interface handler 406 manage signalling between the neighbouring aggressor gNB-CU 302 and the victim gNB-CU 306 via the Xn interface to exchange interference data and send mitigation requests. In an embodiment, the interface mitigation request processor 410 decodes the received CLI mitigation request and determines the corrective action required. The interference mitigation request processor (410) forwards the evaluated CLI mitigation request to the CLI coordination logic (310) to trigger the CLI action towards the interference mitigation action handler (412). Similarly, the CLI coordination logic (310) sends measurement configurations towards the measurement configuration distributor (312).
[0159] The interference mitigation action handler (412) translates CLI request into specific DU actions. Further, the interference mitigation action handler (412) sends a CLI active command towards Fl AP interface handler (408).
[0160] Further, the interface mitigation action handler 412 instructs the aggressor gNB-DU 304 to execute specific interference suppression actions such as reducing power or changing beam parameters. The Fl AP interface handler 408 may manage the communication protocols over the Fl interface between the aggressor gNB-CU 302 and the aggressor gNB-DU 304, and the victim gNB-CU 306 and the victim gNB-DU 308. In an embodiment, the interference reporting handler 424 receives interference measurement reports from the victim gNB-DU 308 via the Fl interface and forwards them to the CLI coordination logic 310. In an embodiment, the interference reporting handler 424 may process incoming interference reports from the victim gNB-DU 308 and uses the data to decide whether mitigation is necessary.
[0161] Further, the CLI mitigation response analyser 426 evaluates feedback from the victim gNB-DU 308 to verify whether mitigation actions have successfully reduced interference. The measurement configuration handler 428 manages the exchange of Non-Zero-Power Channel State Information Reference Signal (NZP CSI-RS) configurations with neighbouring gNBs over the Xn interface, allowing the victim gNB-CU 306 to measure interference from the aggressor gNB-CU 302 accurately. In an embodiment, the interference mitigation request generator 430 creates explicit CLI mitigation requests based on interference reports and processes incoming requests from other gNBs, ensuring coordinated action. The interference mitigation request generator 430 may prepares a CLI mitigation request message that includes details such as interfering beam ID, subband, and mitigation action. Further, the CLI mitigation action executor 414 implements mitigation instructions from the victim gNB-CU 306, such as reducing transmit power on specific beams or switching subband.
[0162] The transmission beam controller 416 adjusts beamforming parameters, including power levels and beam directions, to minimize interference. In an embodiment, the transmission beam controller 416 alters transmission parameters, including beamforming vectors, power, timing, or subband allocations. In an embodiment, the air interface transmission module 418 is responsible for sending downlink transmissions which may be adjusted to reduce interference. Further, the air interface transmission module 418 may manage the physical transmission of radio signals over the Uu interface, including NZP CSLRS signals used for interference measurement. Further, the CLI mitigation action verifier 432 verifies whether the interference level has reduced, after the mitigation action is taken by the aggressor gNB-CU 302. The air interface Rx module 420 handles reception of signals, including the NZP CSLRS from neighbouring cells used for interference measurement. Further, the air interface Rx module 420 may manage the physical receiving of radio signals over the Uu interface, including NZP CSI-RS signals used for interference measurement.
[0163] In an embodiment, the CLI measurement engine 434 measures interference from the aggressor gNB-CU 302 and the aggressor gNB-DU 304 by monitoring configured NZP CSI-RS resources providing raw data for analysis. Further, the strongest beam detector 328 identifies the specific beam causing the most interference (i.e., strongest interfering beam), typically by referencing identifiers like the Synchronization Signal Block (SSB) Index or CSI-RS Resource ID. The interference report generator 330 compiles detailed interference reports, including metrics like Reference Signal Received Power (RSRP) and the identified interfering beam, for transmission to the victim gNB-CU 306. Further, the CLI request relay logic 436 forwards the CLI mitigation requests and responses across the aggressor gNB-CU 302, enabling coordination in meshed or hierarchical network topologies. The CLI relay module 422 captures and retransmits the CLI mitigation requests or responses, ensuring coordination even in disjoint or inter-operator setups.
[0164] In some embodiments, the aggressor gNB-CU 302 shares its NZP CSI-RS configuration with the victim gNB-CU 306 via the Xn interface, enabling interference measurement. Further, the victim gNB-DU 308 uses the NZP CSI-RS signals to measure interference levels from the aggressor gNB-CU 302 and the aggressor gNB-DU 304. The strongest beam detector 328 pinpoints the beam causing the most interference. Further, the victim gNB-DU 308 generates an interference report and sends it to the victim gNB-CU 306 via the Fl interface. The victim gNB-CU 306 processes the report, generates a CLI Mitigation Request, and sends it to the aggressor gNB-CU 302 over the Xn interface. The aggressor gNB-CU 302 then instructs the aggressor gNB-DU 304 to execute mitigation actions, such as reducing power on the identified beam or adjusting subband usage. Further, the victim gNB-CU 306 may monitor interference levels post-mitigation and may provide feedback to confirm success.
[0165] In an aspect, the CLI relay module (422) of the relay UE (404) may function as alternative relay via the UE when no direct gNB path exists, i.e., for multihop CLI coordination if direct Xn unavailable.
[0166] FIG. 5 illustrates an exemplary flow diagram (500) of a method for crosslink interference (CLI) mitigation in the network (106), in accordance with an embodiment of the present disclosure. In an embodiment, the flow diagram (500) shows the cross-link interference coordination happening in a 5G NR network, such as the network (106) for mitigating CLI interference. The present FIG. 5 depicts the interaction between various gNBs, including a gNB DU B (victim) (308), a gNB CU B (victim controller) (306), a gNB CU A (aggressor controller) (302), a gNB DU A (aggressor) (304), a gNB CU C (intermediate node) (402), and a Relay UE (404).
[0167] In an aspect, the victim controller may a controller associated with the victim network node (e.g., victim gNB), configured to detect or receive information indicative of cross-link interference (CLI), identify at least one aggressor network node responsible for the CLI, and generate and transmit a mitigation request comprising one or more parameters associated with the detected interference.
[0168] In an aspect, the aggressor controller may be a controller associated with the aggressor network node, configured to receive the mitigation request from the victim controller, determine whether to perform a mitigation action based on the received request, and adapt at least one transmission parameter, scheduling parameter, or power parameter to mitigate the cross-link interference.
[0169] At step 502, the measurement configuration exchange is initiated using NZP CSLRS measurement signals. In particular, the aggressor cell, the gNB CU A (302), configures the NZP CSLRS measurement signals for measurement configuration exchange.
[0170] At step 504, the gNB CU A (302) shares the measurement configuration details with the neighbouring gNB, the gNB CU B (306), in the form of NZP CSLRS measurement signals using the Xn interface. The measurement configuration detailsmay comprise a cell identifier (ID), a CSI-RS resource ID, time / frequency location, and periodicity details.
[0171] At step 506, the gNB CU B (306) shares the measurement configuration details with the gNB DU B (308). The gNB DU B (308), upon receiving the configuration details, configures the NZP CSI-RS measurements.
[0172] At step 508, the gNB DU B (308), i.e., the victim gNB, starts the interference measurement.
[0173] At step 510, the gNB DU B (308) measures the CLI from the NZP CSI-RS measurements provided by the gNB CU A (302). In particular, the victim cell’s gNB-DU, i.e., gNB DU B (308), measures the interference from neighboring cells' i.e., the gNB CU A (302), downlink transmissions using the configured NZP CSI-RS.
[0174] At step 512, to facilitate the CLI measurement, the gNB DU A (304) transmits the NZP CSI-RS on a particular beam, say beam 5.
[0175] At step 514, the gNB DU B (308) measures the interference level by deriving interference metrics such as Reference Signal Received Power (RSRP) or Received Signal Strength Indicator (RSSI) for the NZP CSI-RS of the gNB DU A (304). Further, in case of multiple beams or reference signals, the victim DU, i.e., the gNB DU B (308), identifies which interfering beam is strongest among the multiple beams at step 516.
[0176] At step 518, the victim gNB DU B (308) starts reporting the strongest interfering beam to the aggressor gNB, i.e., the gNB CU A (302).
[0177] At step 520, the victim gNB-DU, i.e., the gNB DU B (308), sends an interference report to its gNB-CU, i.e., the gNB CU B (306), identifying the strongest interfering beam. The interference report comprises information, such as an interferer cell ID, a beam ID and a measured RSRP level.
[0178] At step 522, the gNB CU B (306) evaluates interference severity and decides whether an interference mitigation action is required. In an embodiment, the system (108) can be preconfigured with thresholds to avoid oversensitivity. So, the cellB’s CU, i.e., gNB CU B (306), may only send a CLI mitigation request if the interference measured exceeds a certain RSRP or causes a measurable degradation (like high uplink block error rate). This prevents unnecessary signaling when cells are in a mildly overlapping range that doesn’t actually harm the performance of the network (106). Upon evaluating that the interference mitigation action is required, the gNB CU B (306) starts a process for CLI mitigation request generation at step 524.
[0179] At step 526, the victim gNB CU B (306) sends a CLI mitigation request message to the neighboring (interfering) gNB-CU, i.e., the gNB CU A (302). The CLI mitigation request comprises interfering cell information (e.g., interferer cell ID), a target of interference suppression, which may include the beam identifier or a physicallayer reference (e.g., Beam ID, SSB or CSLRS index), and a suggested mitigation action (e.g., reduce power, change subband, timing adjustment, and the like) to be performed.
[0180] At step 528, the aggressor gNB-CU, i.e., the gNB CU A (302), evaluates the CLI mitigation request to decide whether the suggested mitigation action is feasible or not based on the current situation. If the suggested mitigation actions are found to be feasible, the gNB CU A (302) starts a process of the CLI mitigation request execution at step 530.
[0181] At step 532, the gNB CU A (302) instructs its gNB-DU, the gNB DU A (304), to take the requested mitigation action, such as reducing the transmit power of the identified beam or switching the transmission to a different subband. Upon receiving instruction, the gNB DU A (304) applies the suggested mitigation action at step 534. The mitigation action helps in mitigating CLI at step 536.
[0182] At step 538, a notification is sent to the gNB DU B (308) to inform it that the suggested mitigation action has been taken (e.g., the transmit power is reduced, or the subband is adjusted). Further, upon receiving the notification, the gNB DU B (308) starts a verification process for verifying interference mitigation at step 540.
[0183] At step 542, the gNB DU B (308) remeasures CLI to verify the reduction in interference post-mitigation action. The process of measuring interference has already been explained earlier. Hence, not explained herein for the sake of brevity. Once the CLI mitigation is confirmed, the gNB DU B (308) sends feedback to the gNB CU B (306) to confirm successful CLI mitigation at step 544. In an embodiment, the feedback may also include an updated measured RSRP level and verification of mitigation success.
[0184] At step 546, the gNB CU B (306) logs the updated measured RSRP level and verification of mitigation success. In case the mitigation is unsuccessful or insufficient, the gNB CU B (306) may reinitiate the process of CLI mitigation.
[0185] In an embodiment, a direct Xn interface connectivity may not exist between interfering cells. In that case, the system (108) may perform the multi-hop CLI coordination at step 548. In the multi-hop CLI coordination, as there is no direct interface connectivity, the gNB CU B (306) uses the intermediate node C to forward the CLI mitigation request to the gNB CU A (302). So, at step 550, the gNB CU B (306) relays the CLI mitigation request to the intermediate node C. The relayed CLI mitigation request also comprises an end target identifier (i.e., Cell A) along with the other details. The intermediate node C then forwards the CLI mitigation request to the gNB CU A (302) at step 552. The gNB CU A (302), upon receiving the CLI mitigation request, sends an acknowledgement to the intermediate node C, at step 554, corresponding to receiving the CLI mitigation request. At step 556, the intermediate node C then relays the received acknowledgement to the gNB CU B (306). This successfully completes the multi-hop CLI mitigation request at step 558.
[0186] In another embodiment, the system (108) may use the optional relay UE (402), at step 560, to forward the CLI mitigation request in case the direct Xn interface connectivity does not exist between interfering cells. In such cases, the gNB CU B (306) sends a message to the gNB DU B (308) suggesting use of the relay UE (402) for CLI mitigation request broadcasting at step 562. The gNB CU B (306), uponreceiving the message, broadcasts the CLI mitigation request to the relay UE 402 at step 564. The relay UE (402), upon receiving the CLI mitigation request, forwards the CLI mitigation request to the gNB DU A (304) at step 566. The gNB DU A (304) then forwards the CLI mitigation request received from a foreign UE, i.e., the relay UE 402, to the gNB CU A (302) at step 568. The gNB CU A (302) then sends a message to the gNB DU A (304) to apply the suggested mitigation action in the CLI mitigation request, at step 570. The gNB DU A (304) then applies the suggested mitigation action and sends confirmation to the gNB CU A (302) for application of the mitigation action at step 572. Further, the gNB CU A (302) sends the confirmation along with the mitigation response to the relay UE (402) via the gNB DU A (304) at steps 574 and 576. The relay UE 402 then forwards the mitigation response to the victim cell, i.e., to the gNB DU B (308), at step 578. The gNB DU B (308) then sends a CLI mitigation confirmation message to the gNB CU B (306), at step 580. By performing steps 560 to 580, the CLI mitigation is successfully coordinated via the relay UE (402) and ends at step 582.
[0187] In an embodiment, there might exist a persistent CLI situation. So, to overcome that, the system (108) uses a periodic CLI coordination technique at step 584. In the periodic CLI coordination technique, the gNB DU B (308) performs periodic CLI measurements at step 586 and then shares the periodic measurement report with the gNB CU B (306) at step 588. The gNB CU B (306) then generates and sends a periodic CLI mitigation request to the aggressor gNB, i.e., to the gNB CU A (302) at step 590. The gNB CU A (302) then instructs the gNB DU A (304) to perform the suggested mitigation action at step 592.
[0188] Some exemplary embodiments are described herein. Disclosed below is an exemplary implementation of a signaling procedure solution for dynamic cross-link interference mitigation that involves explicit requests, negotiation, and feedback between network nodes. The solution spans both the Fl interface (between gNB-DU and gNB-CU within a gNB) and the Xn interface (between gNBs). By utilizing thecentral unit (CU) as a coordination point, a victim cell can request an aggressor cell to take specific mitigating actions and receive confirmations. The procedure uses existing measurement infrastructure (RIM-RS detection, CLI-RSSI, etc.) but adds a controllayer handshake to rapidly alleviate interference in an on-demand manner. The modified-defined elements are: (a) a DU— >CU initiated request trigger based on interference measurements, (b) a CU — neighbor gNB request message carrying explicit mitigation instructions, (c) a response message from the neighbor indicating acceptance or alternative action, and (d) a completion indication to close the loop once the issue is resolved. The procedure goes beyond merely sharing UL / DL patterns. Instead the procedure involves actively negotiating changes. The procedure is described below.
[0189] Interference Detection at DU: The gNB-DU continuously monitors for CLI. The monitoring may be via measuring elevated interference on its uplink receivers or detecting a neighbor’s RIM-RS. Suppose DU of gNBl (victim) detects that a specific neighbor cell (aggressor, say gNB2 cell X) is causing strong interference (e.g., RIM-RS detected with high power or CLI-RSSI beyond threshold). In existing standard, the DU would send a DU-CU RIM Information IE to the CU to report the event. In our disclosure, the message is augmented with a Mitigation Request indicator and details. Essentially, the DU not only reports interference detected but also flags that it requests mitigation, including info such as the aggressor cell ID, the measured interference level (or CLI-RSSI), and perhaps the type of mitigation it seeks. This could be as simple as a Boolean, RequestMitigation=TRUE or a more specific cause value (e.g., interference level high - request action). RequestMitigation = TRUE represents a Boolean flag included in a signaling message, wherein a value of TRUE denotes that a victim entity explicitly requests initiation of the cross-link interference (CLI) mitigation procedure by the corresponding aggressor network node. Alternatively, instead of the binary indication, a more granular cause value may be provided, such as interference level high-request action, which conveys not only the need for mitigationbut also contextual information regarding the severity or nature of the interference, thereby enabling the aggressor entity to select an appropriate mitigation strategy.1. CU Aggregation and Decision: The gNB-CU (of gNBl) receives the DU’s report. The CU may be getting such reports from multiple DUs (if several cells experience CLI). It aggregates context: e.g., which neighbor gNB and cell is causing issues, how severe, and in which time frames. The CU knows its neighbors’ identities via Xn (each aggressor cell can be identified by CGI or gNB ID as provided in the DU’s message). Now, the CU decides to initiate a CLI Mitigation Request to the neighbor gNB (gNB2). This decision may consider policy (e.g., send request if interference persists beyond X milliseconds or crosses a threshold). Considering that it is warranted, gNBl’s CU prepares a request to gNB2’s CU over Xn.2. Xn: CLI Mitigation Request Message (New): the CLI mitigation request message is a signaling message transmitted by the victim network node or the victim controller to at least one aggressor network node, comprising one or more information elements indicative of detected cross-link interference (CLI), where the CLI mitigation request message includes at least a request indication and optionally one or more parameters corresponding to an interference level, interference cause, victim identifier, aggressor identifier, and a requested mitigation action, for enabling the aggressor network node to perform a mitigation procedure.For example, gNBl-CU sends a new XnAP message, CLI Mitigation Request, to gNB2-CU. This is a non-UE-associated control message (similar in spirit to Xn’s load or config update messages). The message includes: Victim Cell ID (the cell(s) of gNBl that are suffering), Aggressor Cell ID (the specific cell of gNB2 causing the interference, if known - possibly derived from RIM-RS identification or neighbor lists), Interference Details (e.g., measuredinterference power or a qualitative level like severe), and Requested Mitigation Action. The requested action could be an enumeration such as change DL scheduling, reduce transmit power, switch this frame to UL, or even mute transmissions for N ms on certain frequencies or symbols. For flexibility, the disclosure provides an IE that can indicate a recommended mitigation strategy - for example: mitigationSuggestion = {type: mute, duration: 5ms, affectedSlots: [n..m]} meaning please mute or avoid DL in the next 5ms for these specific slots. The request can also carry an Urgency or QoS indicator (critical vs. moderate) which the aggressor can use to prioritize the response.Neighbor gNB Response (Negotiation): Upon receiving the CLI Mitigation Request, the aggressor gNB’s CU (gNB2-CU) evaluates it. It checks the identified cell and the requested action against its own conditions - e.g., can it afford to pause or modify its downlink transmissions for the requested duration without violating its QoS commitments? The neighbor then sends a CLI Mitigation Response message (new XnAP message) back to the requesting gNB (gNBl-CU). The Response includes: Acknowledgment / Decision - e.g., Accepted, Rejected, or Modified. For example, if the mitigation action is accepted, the CLI mitigation response also specify Action Taken and Duration. For example: Accepted - will mute DL for slots X-Y in upcoming frame, duration 5 ms or Accepted - will lower DL power by 6 dB for the next 10 ms. If the mitigation action cannot fully comply, the CLI mitigation response might respond with Modified - e.g., Partial - will mute only half the requested slots or for a shorter duration (the message can carry the details of the alternate action). In case of Rejected mitigation action, a reason code can be given (e.g., Neighbor cell critical service ongoing or No alternative UL slot available), so that gNBl knows why. This two-message exchange (Request / Response) constitutes a negotiation phase. (Optionally, the neighbor may provide an alternative mitigation in the response which the original gNB could agree to,but to keep signaling minimal, it may be considered as a one-round negotiation where the aggressor’s response is final for that request.)Enforcement of Mitigation: If the response indicates an accepted or modified mitigation, gNB2’s CU now coordinates with its DU to enforce it. For instance, if the action is mute certain downlink slots, gNB2-CU instructs its gNB-DU (via Fl interface) to apply that pattern - likely via a CU-DU RIM Information message or a new Fl control telling the DU of gNB2 to temporarily change the UE / DL configuration for the cell. In an aspect, CU-DU RIM information message refers to a signaling message exchanged between the Central Unit (CU) and the Distributed Unit (DU), configured to convey radio interference management (RIM) information, where the CU-DU RIM information message comprises one or more information elements corresponding to inter-cell coordination parameters, interference-related information, or configuration data, and enables coordination of radio resource management, measurement reporting, or interference mitigation procedures between the CU and the DU.The existing Fl CU-DU Radio Information Transfer procedure may be improved by sending an updated pattern or RIM indication to the DU of gNB2.) Meanwhile, gNBl-CU may inform its DU of the impending relief: for example, if gNB2 agreed to mute certain subframes, gNBl can opportunistically schedule uplink heavy transmission in those subframes for its UEs (taking advantage of the clear channel). This can be done by sending a CU-DU RIM Information message to gNBl -DU indicating the neighbor’s RIM-RS status changed (or a new IE MitigationActive with parameters) so that the DU knows interference will be lower for a while. At this point, the mitigation action is in effect in the network. In an aspect, IE MitigationActive refers to an information element indicating whether the cross-link interference (CLI) mitigation procedure is currently active, where the IE comprises a status indicator and one or more associated parameters. The status indicator is configured to representan active or inactive state of mitigation, and the associated parameters include, but are not limited to, a mitigation identifier, a mitigation type, a set of applied mitigation actions, a start time, an expected or configured duration, and optionally a scope identifier corresponding to one or more affected cells or user equipments (UEs), thereby enabling coordinated tracking and management of ongoing mitigation procedures across network nodes.Monitoring and F eedback: During the mitigation period, the victim DU (gNB 1 -DU) continues to monitor the interference. In instances, the victim DU would notice an immediate drop in interference (e.g., RIM-RS no longer detected or CLI-RSSI falls to normal). The victim DU can send a quick update to its CU confirming improvement. If for some reason the expected relief did not occur (say the neighbor’s action was not effective enough), gNB 1 -DU can inform the CU (which might trigger further actions or another request with adjusted parameters). Assuming mitigation is working, once the agreed duration expires, gNB2 will resume normal transmissions.Completion and Release: After the mitigation duration, gNB 1 -DU reports the post-mitigation interference status to gNBl-CU (e.g., RIM-RS disappeared now, meaning success). The gNBl-CU can optionally send a CLI Mitigation Complete message over Xn to gNB2-CU as a courtesy, indicating that the victim considers the issue resolved (and providing any final measurements). In an aspect, the CLI mitigation complete message is a signaling message transmitted by the aggressor network node or the associated aggressor controller to the victim network node or victim controller, indicating completion of the cross-link interference (CLI) mitigation procedure, where the message comprises one or more information elements corresponding to a mitigation identifier, an outcome status, and optionally a mitigation duration, applied mitigation action, and a confirmation of successful or unsuccessful mitigation.The CLI mitigation complete message may be considered optional, if a timer was used, but the CLI mitigation complete message serves as an explicit closure of the event - especially useful if the neighbor’s mitigation was open-ended or if the neighbor node require confirmation that it can revert to full power safely. The CLI Mitigation Complete could also carry feedback like how effective the mitigation was (e.g., Interference level reduced by X dB, issue resolved), enabling the aggressor to log the event’s success. Both cells then return to routine operation. Each side will keep monitoring for any new CLI occurrences and can re-initiate the procedure if needed.
[0190] A mechanism introduces a targeted, dynamic negotiation for interference mitigation, as follows:• Victim- initiated requests: The victim cell actively requests help, rather than hoping the neighbor infers the need from pattern info. This ensures faster reaction to sudden interference spikes (e.g., a neighbor turning on a new carrier or changing its pattern).• Centralized CU coordination: the gNB-CU orchestrates the request (based on DU measurements) and communicates over Xn. The CU can intelligently decide when and whom to send requests to (especially if multiple neighbors cause interference, it can prioritize). This also means the policy and brains of the mitigation he in the CU, which can be software-upgraded, making it amenable to vendor optimization.• Explicit neighbor acknowledgment: The responding cell explicitly acknowledges the request and commits to an action (or refuses). This explicit acknowledgement removes ambiguity - the victim UE would be aware whether the neighbor will help and in what way. In contrast, simply sharing TDD patterns doesn’t guarantee a neighbor will alter its behavior (they might, but it’s not signaled).• Feedback loop: the feedback that closes the loop - either via a dedicated Complete message or via the existing RIM-RS status updates. Closing the loop confirms that the interference issue has been addressed, which is valuable for network optimization and for the victim to potentially release any special measures (for example, the victim might have shifted some UEs to a different band or paused certain uplink transmissions while waiting for relief; once interference is gone, it can resume normal scheduling). The feedback also allows measurement of how effective the neighbor’s mitigation was, which could be fed into SON (self-optimizing network) functions or future decisions (e.g., if one neighbor consistently causes CLI and often refuses requests, the operator might choose to statically re-align that neighbor’s frame configuration).• Minimal overhead, using standard interfaces: The additional messages (on Xn and Fl) are small and event-triggered. They do not require a persistent stream, just on-demand signaling when interference events occur. By piggybacking on Fl and Xn, which are already used for inter-gNB coordination, no new physical interface is needed. This design is fully in line with 3 GPP architecture - making it realistic for inclusion in the standard.
[0191] In summary, 5G network is empowered to rapidly and cooperatively mitigate cross-link interference through a clear signaling protocol.
[0192] Further, Change Request Content (F1AP & XnAP Extensions) as follows: Fl AP Changes - Support for CLI Mitigation Request• DU-initiated CLI Mitigation Request enhances the existing DU-CU Radio Information Transfer procedure to explicitly handle CLI mitigation triggers including:• The DU-CU Radio Information Transfer procedure may also be used by the gNB-DU to request interference mitigation for a serving cell experiencingcross-link interference. In this case, the DU includes a CLI Mitigation Request indication in the radio information message, identifying the interfering cell(s) and the desired mitigation assistance. In aspects, the message may be labelled as DU-CU RADIO INFORMATION TRANSFER (with CLI Mitigation Request) when carrying this indication. In an aspect, the DU-CU radio information transfer message in CLI mitigation refers to a signaling message exchanged between the Distributed Unit (DU) and the Central Unit (CU) to convey information related to cross-link interference (CLI) detection, reporting, coordination, and mitigation actions. The DU-CU radio information transfer message carries relevant information elements such as interference measurements, victim and aggressor cell identifiers, mitigation requests or instructions, and status updates. It enables coordination between the DU (which performs lower-layer measurements and real-time radio operations) and the CU (which makes higher-level decisions and coordination across cells), thereby facilitating efficient and adaptive interference mitigation within the network.• Information Elements:o For example, an IE InterferenceMitigationRequest (as part of DU-CU RIM Information or as an extension) may be added:■ Type: ENUMERATED {true} (presence of this IE itself could indicate a request).■ Semantics: If included, it signals that the DU is requesting the CU to initiate interference mitigation for the indicated Victim / Aggr cells. This IE is only applicable when RIM-RS Detection Status is detected (i.e., interference present). Extend the Aggressor Cell List to optionally include an Interference Measurement value for each aggressor cell (e.g., an integer representing CLI-RSSI or RIM-RS power). This gives the CU an idea of severity. Example:Aggressor Cell List Item::= SEQUENCE{aggressorCelllD NR-CGI,interferenceLevel INTEGER (0..63) OPTIONAL, — 0 = low, 63 = very high,mapping of measured CLI power... }In an aspect, the aggressor Cell List item defines a record identifying a cell causing cross-link interference. The list includes the aggressorCelllD (NR-CGI) to uniquely identify the interfering cell. An optional interferenceLevel (0-63) indicates the severity of interference, from low to very high (e.g., 0 indicates low interference level and 63 indicates high interference level). The measured CLI power is mapped to this scale to provide a standardized representation for mitigation decisions.The interferenceLevel may be present if InterferenceMitigationRequest is true, conveying how severe the interference is.• CU Processing: In successful operation, if the DU-CU Radio Information Transfer is initiated with a CLI Mitigation Request, the gNB-CU shall interpret the included information as a trigger to coordinate interference mitigation. The gNB-CU may then initiate appropriate inter-gNB signaling (e.g., over Xn) towards the identified aggressor gNB(s) to request interference reduction. Upon receiving the request, the CU doesn’t just store the info - it acts on it (linking to the Xn procedure). In Abnormal Conditions, if the DU sends multiple such requests in a short time, the CU can throttle them or handle accordingly (to avoid spamming neighbors).• New CU-to-DU Indication: When the neighbor responds and mitigation is arranged, the gNB-CU should inform the gNB-DU. CU-DU Radio Information Transfer may be reused.The CU-DU Radio Information Transfer procedure may be used by the gNB-CU to inform the gNB-DU of interference mitigation actions taken by a neighbor gNB. For example, the gNB-CU can signal that a particular RIM-RS has disappeared or that a certain interference will cease for a duration, enabling the DU to adjust its scheduling accordingly.
[0193] Concretely, the CU-DU RIM Information IE is extended to include an indication of Mitigation Active if relevant by reusing the RIM-RS Detection Status field, If the CU knows the neighbor agreed to mute, it could set RIM-RS Detection Status = disappeared for the Victim gNB Set ID, indicating the interference signal is (or will be) gone. Or a more explicit field may be added like MitigationDuration (e.g., DL muted for X ms). For minimal changes, setting status may be assumed to RS disappeared suffices to tell the DU that the interference should abate.
[0194] Additionally, the CU might include a Victim Cell Configuration Update (if needed) indicating the DU it can switch that cell’s pattern or ramp up its UE usage now that interference is lowered. However, this might be handled by existing dynamic scheduling in the DU once interference flags drop.
[0195] Further, ASN.l Updates (F1AP): In the ASN.1 module for F1AP, add extensions:ASN.lDUCURIMInformation ::= SEQUENCE {victimGNBSetID GNBSetID,rIMRSDetectionStatus RIMRSDetectionStatus,aggressorCellList AggressorCellList,requestMitigation NULL OPTIONAL, — presence indicates a mitigation requestiE-Extensions ProtocolExtensionContainer { {DUCURIMInformation- ExtlEs}} OPTIONALThe DUCURIMInformation sequence represents a signaling container exchanged between DU and CU for CLI mitigation coordination. The DUCURIMInformation includes the victimGNBSetID to identify the affected gNB set and the rIMRSDetectionStatus to indicate whether RIM-RS-based interference has been detected. The aggressorCellList provides details of interfering cells and their corresponding interference levels. The optional requestMitigation field, when present, explicitly signals that mitigation action is requested. Additionally, iE-Extensions allows extensibility for future parameters without impacting backward compatibility.In an aspect, requestMitigation is a flag (modeled as an optional NULL IE for simplicity - if present, it means true). It may also be defined in AggressorCellList the optional interferenceLevel as part of an extension. The CUDURIMInformation (CU to DU) can be similarly extended if signals may be wanted back any info.
[0196] XnAP Changes - Xn Procedure for Interference MitigationIn control plane procedure, Interference Mitigation Request is used in XnAP.Xn Initiating Message: CLI MITIGATION REQUEST (sent by victim gNB’s CU over Xn-C to aggressor gNB’s CU).Xn Successful Outcome: CLI MITIGATION RESPONSE (sent by aggressor gNB in reply).
[0197] Further, in an aspect, a CLI mitigation failure scenario may arise in cases of error or explicit rejection without intent to retry; however, such outcomes can begracefully conveyed within the response message using an appropriate cause value, thereby potentially eliminating the need for a separate failure message.
[0198] In Xn CLI Mitigation Request procedure, a gNB (source gNB) requests a neighboring gNB (target gNB) to apply interference mitigation measures for a specific cell or set of cells that are suffering cross-link interference. The procedure is composed of a CLI Mitigation Request message and a corresponding CLI Mitigation Response. Successful operation indicates that the source gNB sends the Request; the target gNB, upon being able to fulfill (or partially fulfill) the request, responds with a Response indicating the action. An illustration may be similar to others in XnAP: source gNB -> CLI MITIGATION REQUEST -> target gNB, then target -> CLI MITIGATION RESPONSE -> source.
[0199] Further, abnormal conditions comprises:If no response is received (timeout), or if the target cannot comply (sends negative response), the source gNB should handle it (maybe by increasing its own interference tolerance or scheduling around the interference, or potentially trying again after some time). If multiple conflicting requests arrive at a gNB (a rare case of many neighbors asking one cell to mitigate), that gNB can use its discretion or configured priority.
[0200] Information Elements for CLI Mitigation Request: a new XnAP message which is a signaling message defined by the Xn Application Protocol (XnAP) and exchanged over the Xn interface between network nodes, such as base stations, where the message comprises one or more information elements for enabling inter-node coordination, including but not limited to handover control, load management, interference coordination, and context information exchange.
[0201] XnAP message with IES as follows:o Source Cell Identifier - identifies the victim cell (the cell in source gNB that is interfered). Type: Global Cell ID (PLMN + cell ID).o Target Cell Identifier - identifies the suspected aggressor cell in the target gNB that is causing interference. If the victim only knows thegNB (not the exact cell), this could be a gNB ID with an optional Cell ID. However, since RIM-RS design uses a concept of gNB Set ID to identify groups transmitting the same RS, the source might have an identifier for the interfering gNB set. So Aggressor gNB Set ID may be included or the neighbor cell CGI if known. (For simplicity, assume cell- level identification.)Interference Cause / Level - indicates the nature of the interference. For example, an IE InterferenceCause ENUM {tddConflict, adjacentChannelLeak, unknown} to help target understand context. IE InterferenceCause ENUM represents a cause of interference, defined as an enumerated type comprising: tddConflict, indicating interference arising from time-division duplex misalignment between cells; adjacentChannelLeak, indicating interference due to leakage from transmissions in adjacent frequency channels; and unknown, indicating that the interference cause is not determined.An IE InterferenceLevel (similar to above, e.g., high / medium / low or an RSRP value).Requested Action - An IE that carries the mitigation suggestion. Structure for requested action as follows:■ MitigationType ENUM {muteDL, reduceTxPower, changePattern, other}.■ If muteDL: accompany with duration (in ms or number of frames) and possibly the pattern (which subframes or symbols to mute, if partial).■ If reduceTxPower: accompany with a dB value or percentage.■ If changePattern: a suggested new UL / DL configuration or reference to a pattern index.■ MitigationPattern as a bitmask may be defined for a subframe / frame where 1 means don’t transmit DL (like almost blank subframe indication).■ RequestedAction IE - contains the recommended interference mitigation behavior for the target cell (e.g., specific subframe blanking or power reduction).o Request ID - a transaction ID to correlate Request / Response (though XnAP may have its own transaction handling).o Criticality - (implicitly part of XnAP PDU structure, e.g., if the target doesn’t recognize this message or IE, how to handle).
[0202] Information Elements for CLI Mitigation Response include:o Target Cell Identifier / or Request ID - to correlate with the request (identifying which cell request it is responding to).o Outcome - an IE indicating result: ENUM {accepted, rejected, partially Accepted} .o If accepted or partiallyaccepted: include MitigationAcceptedAction - which details what will be done:■ e.g., muted for 5ms on slots X-Y or power reduced by X dB for Y ms. This can use similar fields as in Requested Action, to explicitly state the actual action.■ If partially accepted, it might differ from requested (e.g., requested mute 4 slots, will mute 2 slots - so the IE should reflect the actual).o If rejected: include Cause - a standard IE in many XnAP messages indicating why (could reuse cause codes or define a specific one like unableToComplyDueToLoad etc.).o Duration - if not present already in the action, an IE for how long the mitigation will last (so the source knows when to expect it to end). o Possibly MitigationlD - an identifier if may be to later refer to this specific mitigation session (for sending a completion or for logging). This could simply be the Request ID echoed back.
[0203] ASN.l Example (XnAP): Within XnAP’s ASN.1, define messages. For pseudo- ASN.1 :XnAP-PDU-Contents ::= ... — existing definitionsXnlnitiatingMessage ::= SEQUENCE {procedureCode XnProcedureCode,criticality Criticality,value CHOICE {cli-MitigationRequest CLI-MitigationRequest,CLI-MitigationRequest ::= SEQUENCE {sourceCellJD ECGI, - or NRCGI for NR celltargetCell lD ECGI,interferenceCause ENUMERATED { tddPatternConflict, adjacentChannel, unknown },interferenceLevel INTEGER (0..63) OPTIONAL,requestedAction MitigationActionlnfo,iE-ExtensionsMitigationActionlnfo ::= SEQUENCE {type ENUMERATED { mute, txPowerReduction, reconfigurePattern } , mutePattern BIT STRING (SIZE(14)) OPTIONAL, - e.g., 14 symbols or slots indicating muting (if type=mute)txPowerOffset INTEGER (-20 .0) OPTIONAL, — dB offset to reduce (if type=txPowerReduction)duration INTEGER ( 1..1000), — in msXnSuccessfulOutcome ::= SEQUENCE {procedureCode XnProcedureCode,criticality Criticality,value CHOICE {cli-MitigationResponse CLI-MitigationResponse,CLI-MitigationResponse ::= SEQUENCE {sourceCell lD ECGI,targetCell lD ECGI,outcome ENUMERATED { accepted, rejected, partially Accepted }, acceptedAction MitigationActionlnfo OPTIONAL, — present if outcome != rejectedcause Cause OPTIONAL, — present if outcome = rejected or partialXnAP Cause Values: Cause>RadioNetwork>interferenceMitigationNotPossible for rejection reasons.• Rationale: This feature allows a gNB to request a neighbor gNB to temporarily adjust its transmission to mitigate detected cross-link interference, enabling dynamic TDD interference management beyond static coordination. The change request may improve cell-edge and uplink performance when unsynchronized operation is necessary, etc.
[0204] The F1AP and XnAP protocols support the full sequence of the mechanism. The Fl interface handles the intra- gNB communication (DU reporting interference, CU instructing DU after neighbor’s response), and the Xn interface carries the inter-gNB negotiation messages. In an aspect, the inter-gNB negotiation messages refers to a set of signaling messages exchanged between two or more next-generation NodeBs (gNBs), configured to facilitate coordination and agreement on one or more operational parameters, where the messages comprise information elements corresponding to resource allocation, interference mitigation, scheduling coordination, or mobility management, and enable the gNBs to negotiate, modify, and confirm mutually acceptable configurations for optimized network performance.
[0205] In DU-CU Radio Information Transfer, the gNB-DU may include a CLI Mitigation Request when cross-link interference is detected on one of its cells. In this case, the DU-CU RADIO INFORMATION TRANSFER message shall include the identifier of the interfered (victim) cell, and a list of aggressor cells causing the interference, along with an indication that mitigation is requested. The gNB-CU, upon receiving this, shall attempt to coordinate interference mitigation with the relevant neighboring gNB(s) (see Xn interface procedures), and subsequently inform the gNB-DU of the outcome.
[0206] In DU-CU RIM Information IE, InterferenceMitigationRequest (Optional) - Boolean - indicates that the DU requests the CU to initiate remote interferencemitigation for the reported aggressor cell(s). Also in Aggressor Cell List, each list item may include an interference measurement value if available, to assist in mitigation decisions.
[0207] In an aspect, CLI Mitigation Request procedure, a source gNB requests a target gNB to apply interference mitigation actions in order to protect the source gNB’s uplink reception from cross-link interference. It consists of a CLI Mitigation Request sent by the source gNB and a CLI Mitigation Response sent by the target gNB.
[0208] Upon successful operation, the source gNB sends CLI Mitigation Request to the target gNB, indicating the affected cell(s) and suggested mitigation. The target gNB, if able to comply (fully or partially), responds with CLI Mitigation Response indicating the action taken and its extent.
[0209] In abnormal conditions, if the target gNB cannot apply any mitigation, it sends a negative response (Cause indicating the reason). If the source gNB does not receive a response within the expected time, it may assume the request is not granted and may retry or escalate. Multiple simultaneous requests to the same target gNB for the same cell should be handled by the target by either consolidating them or responding to each as per its capabilities.
[0210] In an aspect, IES for CLI Mitigation Request / Response message as follows:o Victim Cell ID - Indicates the cell in the source gNB that is suffering interference (i.e., the cell requesting protection).o Aggressor Cell ID - Indicates the cell in the target gNB that is believed to be causing the interference. This may be derived from the RIM reference signal or known neighbor relations.o Requested Action - Specifies the interference mitigation action requested. Possible values: ‘downlink mute’, ‘transmit power reduction’, ‘change TDD configuration’. Additional parameters like duration and pattern are provided in associated fields.o Outcome (in Response) - Indicates whether the target gNB will perform the requested mitigation. If ‘accepted’ or ‘partially Accepted’, the target gNB will implement the interference mitigation as described in the Response message. If ‘rejected’, the target gNB could not honor the request. And so on.
[0211] Further, in an aspect, a dynamic Cross-Link Interference Mitigation Request procedure in F1AP and XnAP is used to enable a gNB suffering uplink interference to request a neighboring gNB to temporarily adjust its downlink transmissions. This improves network performance in unsynchronized or semisynchronized TDD deployments by allowing rapid, coordinated interference mitigation beyond static frame alignment. It is particularly beneficial for dense networks and multi-operator scenarios where CLI can severely degrade uplink throughput. This ensures more robust inter-cell interference management and optimization.
[0212] FIG. 6 illustrates an exemplary flow diagram of a method (600) for radio interference mitigation (RIM) in the network (106), in accordance with an embodiment of the present disclosure.
[0213] In an aspect, the radio interference mitigation may be cross-link interference (CLI) mitigation. The radio interference mitigation (RIM) is managed in sub-band full duplex (SBFD) and dynamic time division duplex (TDD) network. Further, the radio interference mitigation (RIM) is performed based on beam-level and subband-based coordination.
[0214] At step (602), the method (600) includes receiving, by a victim network node, one or more measurement configurations from an aggressor network node over a reference signal using a standard interface of one or more standard interfaces.
[0215] In an aspect, the victim network node may be a victim gNB. The aggressor network node may be an aggressor gNB. The one or more standard interfaces comprise a Fl interface, a Xn interface, and an air interface.
[0216] In an aspect, the one or more measurement configurations comprise nonzero-power (NZP) channel state information-reference signal (CSI-RS) configurations, zero-power CSI-RS configurations, one or more synchronization signal blocks (SSBs), and sounding reference signal (SRS). The NZP CSI-RS configurations comprise at least one of a resource identifier (ID), a time slot, frequency subband, periodicity, a CSI-RS identifier, location in time or frequency, and power. Further, the one or more measurement configurations comprise at least one first information element (IE). The at least one first IE comprises served cell information.
[0217] At step (604), the method (600) includes performing, by the victim network node, interference measurement based on the received measurement configuration to identify a resource causing radio interference. In an aspect, the interference measurement comprises reference signal received power (RSRP) or received signal strength indicator (RSSI).
[0218] At step (606), the method (600) includes preparing, by the victim network node, an interference report based on the resource identification. In an aspect, the interference report comprises an interference level, an identifier of strongest interfering beam, a synchronization signal block (SSB) index, CSI-RS resource ID, time indication or frequency subband index.
[0219] At step (608), the method (600) includes generating, by the victim network node, an interference mitigation request based on the interference report. The interference mitigation request comprises an interfering beam and a suggested mitigation action to be taken to mitigate the radio interference. In an aspect, the suggested mitigation action comprises transmit power reduction, beam switching, beam muting, transmission timing adjustment, and duration for mitigation or periodicity for mitigation.
[0220] In an aspect, the interference mitigation request may be CLI mitigation request. The CLI mitigation request comprises one or more second information elements (IES) corresponding to a victim cell identifier, an aggressor cell identifier, aninterference cause or an interference level, and the suggested mitigation action. The interference level comprises high level, low level and medium level.
[0221] The CLI mitigation request further comprises a beam identifier, a subband index, and a timing offset corresponding to interference, a request identifier, and a CLI severity metric. The CLI severity metric comprises measured interference power, and a signal to interference plus noise ratio (SINK).
[0222] At step (610), the method (600) includes communicating, by the victim network node, the generated interference mitigation request to the aggressor network node through one of the standard interface or multi-hop coordination. In an aspect, the victim network node may determine whether the interference measurement is within a predefined threshold. Based on the determination, the victim network node may initiate the communication of the CLI mitigation request towards the aggressor network node.
[0223] In an aspect, the victim network node (e.g., victim gNB) may communicate the generated interference mitigation request to the aggressor network node through one of the Fl interface, Xn interface, or multi-hop signaling.
[0224] At step (612), the method (600) includes performing, by the aggressor network node, the suggested mitigation action on the identified resource. In an aspect, the aggressor network node may perform the suggested mitigation action on the identified resource based on the CLI severity metric.
[0225] In an aspect, upon performing the suggested mitigation action, the aggressor network node may communicate a CLI mitigation response to the victim network node. The CLI mitigation response comprises at least one third information elements (IES) corresponding to the target cell identifier or the request identifier, an outcome, a mitigation identifier, a mitigation duration, and an indication of successful mitigation or unsuccessful mitigation. The outcome comprises one of mitigation action accepted, mitigation action rejected, or mitigation action partially accepted.
[0226] Further, upon receiving the CLI mitigation response, the victim network node may verify whether interference level has reduced to a reference interferencelevel, after performing the mitigation action. Based on the verification, the victim network node may communicate a feedback message to the aggressor network node.
[0227] In an aspect, upon receiving the feedback message from the victim network node, the aggressor network node may analyze the feedback message to verify whether the suggested mitigation action is successful. Based on the analysis, the aggressor network node may communicate a feedback response towards the victim network node. The feedback response further comprises an alternative action or a remedial action.
[0228] Furthermore, upon receiving the feedback response from the aggressor network node, the victim network node analyzes the feedback response. Upon determining the unsuccessful mitigation based on the analysis of the feedback response, the victim network node may perform the remedial action. The remedial action comprises re-initiation of CLI mitigation.
[0229] FIG. 7 illustrates an exemplary computer system (700) in which or with which embodiments of the present disclosure may be implemented.
[0230] As shown in FIG. 7, the computer system (700) may include an external storage device (710), a bus (720), a main memory (730), a read-only memory (740), a mass storage device (750), communication port(s) (760), and a processor (770). A person skilled in the art will appreciate that the computer system may include more than one processor and communication ports. The processor (770) may include various modules associated with embodiments of the present disclosure. The communication port(s) (760) may be any of an RS-232 port for use with a modem-based dialup connection, a 10 / 100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication port(s) (760) may be chosen depending on a network, such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system connects.
[0231] The main memory (730) may be random access memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory (740) may be any static storage device(s) e.g., but not limited to, a Programmable Read OnlyMemory (PROM) chips for storing static information e.g., start-up or Basic Input / Output System (BIOS) instructions for the processor (770). The mass storage device (750) may be any current or future mass storage solution, which can be used to store information and / or instructions. Exemplary mass storage device (750) includes, but is not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and / or Firewire interfaces), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g., an array of disks.
[0232] The bus (720) communicatively couples the processor (770) with the other memory, storage, and communication blocks. The bus (720) may be, e.g., a Peripheral Component Interconnect (PCI) / PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), Universal Serial Bus (USB), or the like, for connecting expansion cards, drives, and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor (770) to the computer system.
[0233] Optionally, operator and administrative interfaces, e.g., a display, keyboard, joystick, and a cursor control device, may also be coupled to the bus (720) to support direct operator interaction with the computer system. Other operators and administrative interfaces can be provided through network connections connected through the communication port(s) (760). Components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system limit the scope of the present disclosure.
[0234] While the foregoing describes various embodiments of the invention, other and further embodiments of the disclosure may be devised without departing from the basic scope thereof. The scope of the disclosure is determined by the claims that follow. The invention is not limited to the described embodiments, versions or examples, which are included to enable a person having ordinary skill in the art to make and usethe invention when combined with information and knowledge available to the person having ordinary skill in the art.
[0235] The method and system of the present disclosure may be implemented in a number of ways. For example, the methods and systems of the present disclosure may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above-described order for the steps of the method is for illustration only, and the steps of the method of the present disclosure are not limited to the order specifically described above unless specifically stated otherwise. Further, in some embodiments, the present disclosure may also be embodied as programs recorded in a recording medium, the programs including machine-readable instructions for implementing the methods according to the present disclosure. Thus, the present disclosure also covers a recording medium storing a program for executing the method according to the present disclosure.
[0236] The present disclosure discloses a computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to execute a method for radio interference mitigation (RIM) in a network. The method comprises receiving, by a victim network node, one or more measurement configurations from an aggressor network node over a reference signal using a standard interface of one or more standard interfaces. The method comprises performing, by the victim network node, interference measurement based on the received measurement configuration to identify a resource causing radio interference. The method comprises preparing, by the victim network node, an interference report based on the resource identification. The method comprises generating, by the victim network node, an interference mitigation request based on the interference report. The interference mitigation request comprises an interfering beam and a suggested mitigation action to be taken to mitigate the radio interference. The method comprises communicating, by the victim network node, the generated interference mitigation request to the aggressor network node through one of thestandard interface or multi-hop coordination. The method comprises performing, by the aggressor network node, the suggested mitigation action on the identified resource.
[0237] The present disclosure provides significant technical enhancements by employing an integrated mechanism combining measurement configuration, beam identification, and coordinated mitigation signaling in radio interference mitigation (RIM) (i.e., cross-link interference (CLI)). The existing approach fails to pinpoint specifics sources of interference and results in degraded network performance. The present disclosure achieves efficient interference mitigation with minimal performance impact on the network. The present disclosure employs dynamic approach to allow the cells to continue flexible uplink / downlink scheduling and full duplex sub-band operation and intervenes only when the interference is detected. The integrated use of detailed beam-level interference measurement and signaling between neighboring base stations measure cross-link interference using configured reference signals (non-zero power (NZP) CSI-RS), identifies precisely which beam or subband from a neighboring cell is causing interference, and then explicitly requests targeted mitigation actions (e.g., power reduction, subband switching, timing adjustment). The present disclosure provides detailed, targeted beam-level signaling combined with dynamic inter-cell mitigation requests to handle interference.
[0238] While considerable emphasis has been placed herein on the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be implemented merely as illustrative of the disclosure and not as a limitation.ADVANTAGES OF THE PRESENT DISCLOSURE
[0239] The present disclosure provides a method and system for CLI mitigation in a network by enabling robust cross-link interference coordination. By exchanging measurement configurations and interference information, and by issuing directed mitigation commands, 5G NR cells may operate in flexible duplex modes (including SBFD) with significantly reduced mutual interferences, thereby improving uplink reliability (victim cells suffer less interference from neighbors) and overall network capacity. The system also facilitates the deployment of advanced duplex schemes in dense networks, paving the way for features like cell-level full-duplex and highly dynamic TDD in future 5G and beyond systems.
[0240] The present disclosure also provides a mechanism for measuring cross-link interference using configured reference signals (NZP CSI-RS), identifies precisely which beam or subband from a neighboring cell is causing interference, and then explicitly requests targeted mitigation actions (power reduction, subband switching, timing adjustment), providing detailed, targeted beam-level signaling combined with dynamic inter-cell mitigation requests to handle interference. This ensures granular, beam-level CLI mitigation rather than generic, cell-wide power adjustments, minimizing negative impacts on network throughput.
[0241] The present disclosure works seamlessly within disaggregated 5G architectures (CU-DU split), enhancing scalability.
[0242] The present disclosure employs standardized reference signals (NZP CSI-RS), making integration into existing networks straightforward and cost-effective.
[0243] The present disclosure also provides capability for multi-hop interference mitigation coordination, supporting complex deployments.
[0244] The additional advancements offered by the present disclosure are explained below:• Victim-initiated requests: In the present disclosure, the victim cell can actively request help, rather than hoping the neighbor infers the need from pattern information.This ensures faster reaction to sudden interference spikes (e.g., a neighbor turning on a new carrier or changing its pattern).• Centralized CU coordination: In the present disclosure, by having the gNB-CU orchestrate, the request (based on DU measurements) is communicated over Xn, and the solution fits the gNB architecture. The CU can intelligently decide when and whom to send requests to (especially if multiple neighbors cause interference, it can prioritize). This also means the policy and brains of the mitigation lie in the CU, which can be software-upgraded, making it amenable to vendor optimization.• Explicit neighbor acknowledgment: In the present disclosure, the responding cell explicitly acknowledges the request and commits to an action (or refuses). This removes ambiguity, and the victim knows whether the neighbor will help and in what way. This handshake creates a contract between the two gNBs, enabling dynamic interference management.• Feedback loop: In the present disclosure, a feedback loop is included that closes either via a dedicated Complete message or via the existing RIM-RS status updates. This confirms that the interference issue has been addressed, which is valuable for network optimization and for the victim to potentially release any special measures (for example, the victim might have shifted some UEs to a different band or paused certain uplink transmissions while waiting for relief; once interference is gone, it can resume normal scheduling). The feedback also allows measurement of how effective the neighbor’s mitigation was, which could be fed into self-optimizing network (SON) functions or future decisions (e.g., if one neighbor consistently causes CLI and often refuses requests, the operator might choose to statically re-align that neighbor’s frame configuration).• Minimal overhead, using standard interfaces: In the present disclosure, the additional messages (on Xn and Fl interfaces) are small and event triggered. They donot require a persistent stream, just on-demand signaling when interference events occur. By piggybacking on Fl and Xn interfaces, which are already used for inter-gNB coordination, no new physical interface is needed.
Claims
CLAIMS1. A method (600) for radio interference mitigation (RIM) in a network (106), the method comprising:receiving (602), by a victim network node, one or more measurement configurations from an aggressor network node over a reference signal using a standard interface of one or more standard interfaces;performing (604), by the victim network node, interference measurement based on the received measurement configuration to identify a resource causing radio interference;preparing (606), by the victim network node, an interference report based on the resource identification;generating (608), by the victim network node, an interference mitigation request based on the interference report, wherein the interference mitigation request comprises an interfering beam and a suggested mitigation action to be taken to mitigate the radio interference;communicating (610), by the victim network node, the generated interference mitigation request to the aggressor network node through one of the standard interface or multi-hop coordination; andperforming (612), by the aggressor network node, the suggested mitigation action on the identified resource.
2. The method (600) as claimed in claim 1 , wherein the radio interference is crosslink interference (CLI), wherein the network node is gNodeB, and wherein the mitigation request is CLI mitigation request.
3. The method (600) as claimed in claim 1 , wherein the one or more measurement configurations comprise non-zero-power (NZP) channel state informationreference signal (CSI-RS) configurations, zero-power CSI-RS configurations,one or more synchronization signal blocks (SSBs), and sounding reference signal (SRS), and wherein the NZP CSI-RS configurations comprise at least one of a resource identifier (ID), a time slot, frequency subband, periodicity, a CSI-RS identifier, location in time or frequency, and power.
4. The method (600) as claimed in claim 1 , wherein the one or more measurement configurations comprise at least one first information element (IE), and wherein the at least one first IE comprises served cell information.
5. The method (600) as claimed in claim 1, wherein the one or more standard interfaces comprise a Fl interface, a Xn interface, and an air interface.
6. The method (600) as claimed in claim 1 , wherein the interference measurement comprises reference signal received power (RSRP) or received signal strength indicator (RS SI), and wherein the interference report comprises an interference level, an identifier of strongest interfering beam, a synchronization signal block (SSB) index, CSI-RS resource ID, time indication or frequency subband index.
7. The method (600) as claimed in claim 2, wherein the CLI mitigation request comprises one or more second information elements (IES) corresponding to a victim cell identifier, an aggressor cell identifier, an interference cause or an interference level, and the suggested mitigation action, and wherein the interference level comprises high level, low level and medium level.
8. The method (600) as claimed in claim 2, wherein the CLI mitigation request further comprises a beam identifier, a subband index, and a timing offset corresponding to interference, a request identifier, and a CLI severity metric, and wherein the CLI severity metric comprises measured interference power, and a signal to interference plus noise ratio (SINR).
9. The method (600) as claimed in claim 1, further comprising: determining, by the victim network node, whether the interference measurement is within a predefined threshold; andbased on the determination, initiating, by the victim network node, the communication of the CLI mitigation request towards the aggressor network node.
10. The method (600) as claimed in claim 1, wherein the suggested mitigation action comprises transmit power reduction, beam switching, beam muting, transmission timing adjustment, and duration for mitigation or periodicity for mitigation.
11. The method (600) as claimed in claim 8, further comprising: performing, by the aggressor network node, the suggested mitigation action on the identified resource based on the CLI severity metric.
12. The method (600) as claimed in claim 11, further comprising: upon performing the suggested mitigation action, communicating, by the aggressor network node, a CLI mitigation response to the victim network node, wherein the CLI mitigation response comprises at least one third information elements (IES) corresponding to the target cell identifier or the request identifier, an outcome, a mitigation identifier, a mitigation duration, and an indication of successful mitigation or unsuccessful mitigation, and wherein the outcome comprises one of mitigation action accepted, mitigation action rejected, or mitigation action partially accepted.
13. The method (600) as claimed in claim 12, further comprising:upon receiving the CLI mitigation response, verifying, by the victim network node, whether interference level has reduced to a reference interference level, after performing the mitigation action; andbased on the verification, communicating, by the victim network node, a feedback message to the aggressor network node.
14. The method (600) as claimed in claim 13, further comprising:analyzing, by the aggressor network node, the feedback message to verify whether the suggested mitigation action is successful.based on the analysis, communicating, by the aggressor network node, a feedback response towards the victim network node.
15. The method (600) as claimed in claim 14, wherein the feedback response further comprises an alternative action or a remedial action.
16. The method (600) as claimed in claim 14, further comprising:analyzing, by the victim network node, the feedback response; upon determining the unsuccessful mitigation based on the analysis of the feedback response, performing, by the victim network node, the remedial action, wherein the remedial action comprises re-initiation of CLI mitigation.
17. The method (600) as claimed in claim 1, further comprising:determining, by the aggressor network node, whether an occurrence of the CLI mitigation request is repeated more than a predefined number of times for a predefined duration; andbased on the determination, initiating, by the aggressor network node, a coordinated scheduling action with the victim network node.
18. The method (600) as claimed in claim 1, wherein the radio interference mitigation (RIM) is managed in sub-band full duplex (SBFD) and dynamic time division duplex (TDD) network.
19. The method (600) as claimed in claim 1, wherein the radio interference mitigation (RIM) is performed based on beam-level and subband-based coordination.
20. A system (108) for radio interference mitigation (RIM) in a network (106), the system (108) comprising a victim network node, the victim network node comprising:a communication unit (214) configured to receive one or more measurement configurations from an aggressor network node over a reference signal using a standard interface of one or more standard interfaces;a processing unit (212) configured to:perform interference measurement based on the received measurement configuration to identify a resource causing radio interference;prepare an interference report based on the resource identification;generate an interference mitigation request based on the interference report, wherein the interference mitigation request comprises an interfering beam and a suggested mitigation action to be taken to mitigate the radio interference; andthe communication unit (214) configured to communicate the generated interference mitigation request to the aggressor network node through one of the standard interface or multi-hop coordination, wherein the aggressor network node is configured to perform the suggested mitigation action on the identified resource.
21. The system (108) as claimed in claim 20, wherein the radio interference is cross-link interference (CLI), wherein the network node is gNodeB, and wherein the mitigation request is CLI mitigation request.
22. The system (108) as claimed in claim 20, wherein the one or more measurement configurations comprise non-zero-power (NZP) channel state informationreference signal (CSI-RS) configurations, zero-power CSLRS configurations, one or more synchronization signal blocks (SSBs), and sounding reference signal (SRS), and wherein the NZP CSI-RS configurations comprise at least one of a resource identifier (ID), a time slot, frequency subband, periodicity, a CSI-RS identifier, location in time or frequency, and power.
23. The system (108) as claimed in claim 20, wherein the one or more measurement configurations comprise at least one first information element (IE), and wherein the at least one first IE comprises served cell information.
24. The system (108) as claimed in claim 20, wherein the one or more standard interfaces comprise a Fl interface, a Xn interface, and an air interface.
25. The system (108) as claimed in claim 20, wherein the interference measurement comprises reference signal received power (RSRP) or received signal strength indicator (RS SI), and wherein the interference report comprises an interference level, an identifier of strongest interfering beam, a synchronization signal block (SSB) index, CSI-RS resource ID, time indication or frequency subband index.
26. The system (108) as claimed in claim 21, wherein the CLI mitigation request comprises one or more second information elements (IES) corresponding to a victim cell identifier, an aggressor cell identifier, an interference cause or aninterference level, and the suggested mitigation action, and wherein the interference level comprises high level, low level and medium level.
27. The system (108) as claimed in claim 21, wherein the CLI mitigation request further comprises a beam identifier, a subband index, and a timing offset corresponding to interference, a request identifier, and a CLI severity metric, and wherein the CLI severity metric comprises measured interference power, and a signal to interference plus noise ratio (SINK).
28. The system (108) as claimed in claim 20, wherein the processing unit (212) configured to:determine whether the interference measurement is within a predefined threshold; andbased on the determination, initiate the communication of the CLI mitigation request towards the aggressor network node.
29. The system (108) as claimed in claim 20, wherein the suggested mitigation action comprises transmit power reduction, beam switching, beam muting, transmission timing adjustment, and duration for mitigation or periodicity for mitigation.
30. The system (108) as claimed in claim 28, wherein the aggressor network node is configured to perform the suggested mitigation action on the identified resource based on the CLI severity metric.
31. The system (108) as claimed in claim 28, wherein upon performing the suggested mitigation action, the aggressor network node is configured to communicate a CLI mitigation response to the victim network node, wherein the CLI mitigation response comprises at least one third information elements(IES) corresponding to the target cell identifier or the request identifier, an outcome, a mitigation identifier, a mitigation duration, and an indication of successful mitigation or unsuccessful mitigation, and wherein the outcome comprises one of mitigation action accepted, mitigation action rejected, or mitigation action partially accepted.
32. The system (108) as claimed in claim 30, wherein upon receiving the CLI mitigation response, the processing unit (212) configured to verify whether interference level has reduced to a reference interference level, after performing the mitigation action; andbased on the verification, the communication unit (214) is configured to communicate a feedback message to the aggressor network node.
33. The system (108) as claimed in claim 31, whereinthe aggressor network node configured to:analyze the feedback message to verify whether the suggested mitigation action is successful.based on the analysis, communicate a feedback response towards the victim network node.
34. The system (108) as claimed in claim 32, wherein the feedback response comprises an alternative action or a remedial action.
35. The system (108) as claimed in claim 32, wherein the processing unit (212) is configured to:analyze the feedback response; andupon determining the unsuccessful mitigation based on the analysis of the feedback response, perform the remedial action, wherein the remedial action comprises re-initiation of CLI mitigation.
36. The system (108) as claimed in claim 20, wherein the aggressor network node configured to:determine whether an occurrence of the CLI mitigation request is repeated more than a predefined number of times for a predefined duration; andbased on the determination, initiate a coordinated scheduling action with the victim network node.
37. The system (108) as claimed in claim 20, wherein the radio interference mitigation (RIM) is managed in sub-band full duplex (SBFD) and dynamic time division duplex (TDD) network.
38. The system (108) as claimed in claim 20, wherein the radio interference mitigation (RIM) is performed based on beam-level and subband-based coordination.
39. A computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to execute a method (600) for radio interference mitigation (RIM) in a network (106), the method comprising:receiving (602), by a victim network node, one or more measurement configurations from an aggressor network node over a reference signal using a standard interface of one or more standard interfaces;performing (604), by the victim network node, interference measurement based on the received measurement configuration to identify a resource causing radio interference;preparing (606), by the victim network node, an interference report based on the resource identification;generating (608), by the victim network node, an interference mitigation request based on the interference report, wherein the interference mitigation request comprises an interfering beam and a suggested mitigation action to be taken to mitigate the radio interference;communicating (610), by the victim network node, the generated interference mitigation request to the aggressor network node through one of the standard interface or multi-hop coordination; andperforming (612), by the aggressor network node, the suggested mitigation action on the identified resource.
