Subscriber Profile ID for RAT/Frequency Priority

Description

The Subscriber Profile ID for RAT/Frequency Priority (SPID) is a crucial parameter within the 3GPP architecture for managing network selection and traffic steering. It is a numeric identifier, typically ranging from 1 to 256, stored in the subscriber's profile within the Home Subscriber Server (HSS) or a similar database. This ID is not directly visible to the user but is used by the network to reference a specific set of operator-defined policies. These policies dictate the priority order in which a User Equipment (UE) should attempt to camp on or hand over to different Radio Access Technologies (e.g., LTE, WCDMA, GSM) and specific frequency bands within those technologies.

When a UE attaches to the network, the SPID is retrieved from the HSS and sent to the Mobility Management Entity (MME) in the Evolved Packet Core (EPC) or the Access and Mobility Management Function (AMF) in the 5G Core (5GC). The core network node then provides this SPID, along with the associated RAT/Frequency Selection Priority (RFSP) index, to the Radio Access Network (RAN). In 4G, this is communicated to the eNodeB via the S1 interface; in 5G, it is sent to the gNodeB via the NG interface. The RAN node uses this information to make intelligent decisions regarding idle mode cell reselection and connected mode handovers.

The primary mechanism involves mapping the SPID to an RFSP index, which is a localized table within the RAN node. This table contains the actual priority values for each RAT and frequency carrier. For instance, an operator might configure SPID=10 to map to an RFSP index that gives the highest priority to LTE Band 3, a medium priority to LTE Band 20, and the lowest priority to UMTS. This allows for granular, subscription-based traffic management. The RAN applies these priorities when the UE is in idle mode to influence which cell it selects, and in connected mode to bias handover decisions, ensuring subscribers are directed to the network layer that best matches their service plan and the operator's traffic distribution goals.

Purpose & Motivation

SPID was introduced to solve the challenge of subscriber-specific network steering in a multi-RAT, multi-frequency environment. Prior to its introduction, network selection and handover were primarily based on radio measurements (e.g., signal strength) and static, cell-level configurations that applied uniformly to all users. This approach was inefficient for managing network congestion, implementing service-tier differentiation (e.g., premium vs. basic subscribers), and optimizing spectrum utilization. Operators lacked a dynamic, subscriber-aware tool to direct traffic.

The creation of SPID was motivated by the need for more sophisticated policy-based traffic management. It allows operators to define business and technical rules at the subscriber level and enforce them through the RAN. For example, an operator can use SPID to ensure that high-value enterprise subscribers are always kept on the highest-capacity LTE carriers, while other subscribers might be steered to other bands or even 3G during peak congestion. It also facilitates the introduction of new technologies and frequency bands; an operator can gradually migrate specific user groups to a new 5G layer by assigning them a SPID with a high priority for 5G frequencies. This subscriber-centric approach is fundamental for efficient network operation, quality of service differentiation, and strategic spectrum management.

Key Features

• Subscriber-specific network priority assignment
• Mapping to RAT/Frequency Selection Priority (RFSP) indices
• Control over both idle mode reselection and connected mode handover
• Storage in the HSS/UDM as part of the subscriber profile
• Signaling from core network (MME/AMF) to RAN (eNodeB/gNodeB)
• Enables service-tier differentiation and congestion management

Evolution Across Releases

Defining Specifications