Cross Link Interference

Description

Cross Link Interference (CLI) is a specific interference phenomenon inherent to Time Division Duplexing (TDD) based radio access networks, such as 5G NR. In TDD, the same frequency band is used for both uplink (UL) and downlink (DL) transmissions, separated in time. CLI occurs when the transmission direction (UL or DL) is not perfectly synchronized across neighboring cells or between a base station (gNB) and user equipment (UE). For instance, a strong uplink transmission from a UE in one cell can interfere with the downlink reception of a UE in a neighboring cell if their slot configurations are misaligned. This is particularly problematic in 5G NR, which supports flexible and dynamic TDD slot formats that can be adjusted per cell based on traffic demand, increasing the potential for cross-link conflicts.

The architecture for managing CLI involves coordination mechanisms between network nodes. Key components include the gNB, UEs, and the core network functions that facilitate interference measurement and coordination policies. The process works through CLI measurement and reporting. A gNB can configure a UE to measure specific CLI reference signals, such as the Sounding Reference Signal (SRS) from another UE for uplink-to-downlink interference, or the Channel State Information Reference Signal (CSI-RS) from a neighboring gNB for downlink-to-uplink interference. The UE reports these measurements, allowing the serving gNB to assess the interference level and take mitigation actions.

Mitigation strategies form the core of CLI handling. These include inter-cell coordination via the Xn interface, where gNBs exchange slot format information and potentially align their TDD patterns to minimize conflicting transmission directions. More advanced techniques involve power control, where the transmit power of interfering uplink signals is reduced, or spatial filtering using beamforming to direct energy away from victim receivers. In 3GPP specifications, CLI management is integral to features like dynamic TDD, integrated access and backhaul (IAB), and sidelink communications, ensuring robust performance in dense and heterogeneous network deployments.

Purpose & Motivation

CLI exists because the spectral efficiency advantages of TDD come with the cost of potential intra-frequency interference between cells with unsynchronized transmission directions. Traditional Frequency Division Duplexing (FDD) systems use separate bands for uplink and downlink, inherently avoiding this problem. However, TDD is favored in 5G and beyond for its flexibility in allocating time resources asymmetrically between uplink and downlink to match bursty data traffic. This flexibility, especially with dynamic slot format configuration per cell, introduces the risk of severe interference that can degrade throughput and increase packet error rates.

The creation of standardized CLI measurement and mitigation procedures in 3GPP was motivated by the deployment of dense 5G networks, particularly in mid-band spectrum (e.g., 3.5 GHz). In such environments, cells are closer together, and interference scenarios are more frequent and severe. Prior to formal CLI handling, networks relied on static TDD configurations or large guard bands, which were inefficient. The 3GPP standards from Release 15 onwards introduced explicit CLI frameworks to enable the full benefits of dynamic TDD without catastrophic interference, thereby unlocking higher capacity and more efficient spectrum use in 5G NR.