Intra Frequency Reselection Indication

Description

Intra Frequency Reselection Indication (IFRI) is a network-controlled mobility feature introduced in 5G New Radio (NR) to optimize idle and inactive mode mobility. It operates within the Radio Resource Control (RRC) protocol layer, specifically in system information blocks (SIBs) like SIB2 and SIB4, and in dedicated RRC signaling such as the RRCRelease message. The network broadcasts or unicasts an IFRI parameter, which is a boolean flag or an enumerated value, to instruct the User Equipment (UE) on whether it is allowed to perform cell reselection measurements and procedures on the current serving frequency. When IFRI is set to a restrictive state (e.g., 'not allowed'), the UE is mandated to camp on the current cell without attempting intra-frequency reselection, even if measurement rules like the S-criterion are met. This overrides the UE's autonomous cell reselection algorithm, which traditionally relies solely on measured reference signal received power (RSRP) or quality (RSRQ) compared to broadcast thresholds.

The primary architectural role of IFRI is within the Radio Access Network (RAN), governed by the gNB. The gNB's Radio Resource Management (RRM) function evaluates network conditions—such as load balancing requirements, cell stability, or the presence of ultra-reliable low-latency communication (URLLC) slices—to decide when to apply IFRI. The indication is then embedded in the relevant RRC message's mobility control information field. Upon receiving IFRI, the UE's RRC entity interprets the command and configures the lower layers (Layer 1 and Layer 2) accordingly, potentially disabling intra-frequency measurement gaps or ignoring intra-frequency neighbor cell lists. This ensures the UE remains anchored to a specific cell, which is crucial for maintaining session continuity for certain services or for network planning purposes.

IFRI's operation is tightly integrated with other mobility mechanisms like cell barring and cell reservation. While cell barring completely prohibits access, IFRI is more granular, selectively restricting reselection while still allowing normal camped procedures. It works in conjunction with inter-frequency and inter-RAT reselection controls, allowing the network to steer traffic precisely. For example, in a scenario with a macro cell and underlying small cells on the same frequency, the network might use IFRI to prevent UEs from ping-ponging between small cells, thereby reducing RRC connection re-establishment requests and conserving UE battery life. The feature is a key enabler for enhanced network-controlled mobility, shifting from reactive, measurement-based decisions to proactive, policy-driven network management.

Purpose & Motivation

IFRI was created to address the limitations of purely measurement-driven cell reselection in 5G networks, which can lead to suboptimal mobility performance. In earlier 3GPP releases (pre-Rel-17), UEs in RRC_IDLE or RRC_INACTIVE states autonomously decided to reselect to a better intra-frequency cell based on broadcast parameters like Qrxlevmin and Sintrasearch. This decentralized approach, while simple, often resulted in excessive reselections (ping-pong) in dense urban or heterogeneous network layouts, causing increased signaling load, higher battery consumption, and potential service interruptions. The network had limited direct control to stabilize cell boundaries or prioritize certain cells for specific traffic types.

The introduction of IFRI in Rel-17 provides the network with explicit signaling to override UE autonomy for intra-frequency reselection. This solves problems related to mobility robustness, especially for services requiring consistent cell attachment, such as those using network slicing for industrial IoT or vehicular communications. By preventing unnecessary reselections, IFRI reduces the number of RRC state transitions and location update procedures, thereby decreasing core network signaling overhead. It also allows operators to implement more sophisticated traffic steering and load balancing policies, ensuring that UEs remain on cells that are optimally configured for their subscribed services or network slice instances.