RAT/Frequency Selection Priority

Description

RAT/Frequency Selection Priority (RFSP) is a core network parameter, defined as an index (RFSP Index), that is mapped to UE-specific behavior for idle mode and connected mode mobility. The core network, specifically the Mobility Management Entity (MME) in EPS or the Access and Mobility Management Function (AMF) in 5GC, assigns an RFSP Index to a UE based on its subscription profile (from the Unified Data Management, UDM), the requested network slice, or local operator policies. This index is then provided to the radio access network (E-UTRAN or NG-RAN) via the S1 or N2 interface. The RAN uses the RFSP Index to select and apply a specific set of mobility policies, known as RFSP in Mobility Control (RFSP-in-MC), which are pre-configured in the RAN nodes (e.g., eNBs, gNBs).

These RFSP-in-MC policies dictate how the RAN should handle the UE in terms of cell reselection priorities (for idle/inactive UEs) and handover parameters (for connected UEs). For idle mode, the RFSP Index influences the absolute priorities broadcast in System Information Blocks (SIBs) for different frequency layers and RATs (e.g., giving NR a higher priority than LTE for a premium subscriber). For connected mode, it can affect the thresholds and hysteresis used in measurement reporting and handover decisions, effectively biasing the UE towards or away from certain cells. The RAN translates the abstract RFSP Index into concrete radio resource control (RRC) parameters sent to the UE.

The architecture involves close interaction between the core network's subscriber database, the control plane network functions (MME/AMF), and the RAN. The UDM/HSS stores the Subscribed RFSP Index as part of the user's subscription data. During attachment or session establishment, the MME/AMF may derive a new RFSP Index based on the subscribed index, the network slice selection, and local policy. This dynamic derivation allows for real-time traffic steering. The index itself is an integer (typically in a range like 1-256), where each value corresponds to a specific policy set configured by the operator in both the core and the RAN.

How it works in practice involves several steps. First, at UE attachment, the AMF/MME determines the RFSP Index. It then includes this index in the UE context established with the gNB/eNB. The gNB/eNB, which has a locally configured table mapping RFSP Index values to specific mobility control parameters, applies the corresponding policy. For example, RFSP Index 5 might map to a policy that sets the priority of 5G NR band n78 to '7' (high) and LTE band 3 to '3' (low) for idle mode reselection. This steers UEs with that index to prefer 5G. The network can also update the RFSP Index for a connected UE via a UE Context Modification procedure, allowing for dynamic policy changes based on changing network conditions or service requirements.

Purpose & Motivation

RFSP was created to provide the network with a powerful and standardized tool for intelligent traffic steering and mobility management. Before mechanisms like RFSP, network control over UE cell selection was largely limited to broadcasting static priorities in SIBs, which applied uniformly to all UEs in a cell. This was insufficient for implementing subscriber-differentiated services, efficient load balancing, or service-aware network slicing. RFSP solves this by introducing a UE-specific, network-assigned policy index that can be tailored to individual subscribers or service flows.

The primary problems RFSP addresses are inefficient resource utilization and the inability to align mobility with business or service logic. For instance, an operator might want to steer machine-type communication (MTC) devices to robust but lower-capacity 2G/3G layers, while steering premium smartphone users to high-capacity 4G/5G layers. Without RFSP, this would require complex and non-standard workarounds. RFSP provides a clean, standardized interface between the core network's subscriber/service awareness and the RAN's radio resource control.

Historically introduced in 3GPP Release 9 for LTE/EPS, RFSP's importance grew with the advent of network slicing and 5G's service-based architecture. It enables the core network to communicate the 'context' of a UE (e.g., that it is part of a massive IoT slice or an enhanced mobile broadband slice) to the RAN, so the RAN can apply appropriate mobility behaviors. This allows the network to optimize for different, often conflicting, goals simultaneously—such as maximizing throughput for some users while maximizing battery life or coverage for others—all within a single, shared RAN infrastructure.

Key Features

• Network-assigned index (RFSP Index) derived from subscription, slice, and policy
• Enables UE-specific cell reselection and handover parameter control
• Interface between core network policy (MME/AMF) and RAN mobility execution
• Supports dynamic updates during a UE's connection
• Fundamental for service-aware mobility and network slicing realization
• Uses pre-configured mapping (RFSP-in-MC) in RAN nodes to translate index to RRC parameters

Evolution Across Releases

Defining Specifications