Description
Allocation and Retention Priority (ARP) is a critical Quality of Service (QoS) parameter defined within the 3GPP architecture, specifically within the Policy and Charging Control (PCC) framework. It operates as a scalar value, typically comprising a priority level (1-15, with 1 being highest), a pre-emption capability flag, and a pre-emption vulnerability flag. The ARP is not a bearer-level parameter used for dynamic scheduling (like QCI), but rather a subscription-level or session-level parameter applied during bearer establishment and lifecycle management. Its primary function is invoked by the Policy and Charging Rules Function (PCRF) and enforced by the Policy and Charging Enforcement Function (PCEF) in the core network, in coordination with the Radio Access Network (RAN) during Radio Resource Management (RRM).
Architecturally, ARP is integral to the bearer establishment and modification procedures. When a new bearer request arrives (e.g., for a voice call or data session), the network performs admission control. The ARP value of the requesting bearer is compared against the ARP values of existing bearers and the available resource capacity. A bearer with a higher priority ARP (lower numerical value) is more likely to be granted resources. Conversely, during network congestion, the ARP determines which bearers may be pre-empted (released) to free up resources for higher-priority traffic. The pre-emption capability flag indicates if a bearer can pre-empt others, while the pre-emption vulnerability flag indicates if a bearer can be pre-empted.
How ARP works involves a multi-step decision process. First, the Home Subscriber Server (HSS) stores subscriber-specific ARP values as part of the subscriber profile. During session initiation, the PCRF retrieves this information or applies dynamic policy rules to assign an ARP to the IP-CAN (IP Connectivity Access Network) session or dedicated bearer. This ARP is then communicated to the PCEF (e.g., in the PGW for 4G/5G) via the Gx interface. The PCEF includes the ARP in the bearer setup request sent to the access network. In the RAN, the eNB/gNB uses the ARP, alongside other parameters like QCI and GBR, to make final admission decisions and manage radio bearer prioritization during handovers and congestion events.
Its role extends across the entire network lifecycle, from initial attach to mobility and session termination. It ensures that mission-critical services, such as IMS emergency calls, operator signaling, and high-priority enterprise services, are always granted network access even when the network is under load. This makes ARP a cornerstone for network reliability, efficient resource utilization, and the delivery of differentiated services, forming a static priority layer upon which dynamic QoS mechanisms operate.
Purpose & Motivation
ARP was introduced to solve the fundamental problem of managing limited and shared network resources in a multi-service environment. Prior to standardized QoS mechanisms like ARP, networks struggled to intelligently prioritize traffic, leading to potential service degradation for all users during congestion or the inability to guarantee resources for essential services. The creation of ARP was motivated by the need for a standardized, policy-driven method to control which sessions get access to the network (allocation) and which sessions are maintained when capacity is strained (retention).
Historically, as mobile networks evolved from voice-centric (2G) to multi-service packet-switched networks (3G and beyond), the variety of traffic—from best-effort web browsing to latency-sensitive VoIP—demanded a more sophisticated admission control strategy than simple first-come, first-served. ARP addresses the limitations of such simplistic approaches by providing a pre-defined, operator-configurable priority scheme. This allows network operators to implement business rules and service-level agreements directly into the network's resource management logic, ensuring revenue-generating or legally mandated services are protected.
Furthermore, ARP solves the specific challenge of service continuity during handovers and network failures. By providing a clear priority indicator, it enables the network to make consistent decisions about which sessions to preserve when a user moves between cells or when a network element is overloaded. This purpose is critical for maintaining user experience and meeting regulatory requirements for services like emergency communications, which must be allocated resources with absolute priority under all network conditions.
Key Features
- Defines a priority level (1-15) for bearer admission and retention
- Includes pre-emption capability and vulnerability flags for congestion management
- Used statically during bearer setup and modification, not for dynamic packet scheduling
- Integrates with the PCC architecture via the PCRF and PCEF
- Stored in subscriber profiles on the HSS for subscription-based prioritization
- Enforced during Radio Resource Management (RRM) in the RAN for access control
Evolution Across Releases
Introduced ARP as a fundamental QoS parameter within the UMTS QoS architecture defined in TS 23.107. The initial capability provided a basic priority mechanism for PDP context activation and management, featuring priority level, pre-emption capability, and pre-emption vulnerability. It enabled differentiated handling of traffic flows during network admission control and congestion scenarios in the core and RAN.
Defining Specifications
| Specification | Title |
|---|---|
| TS 21.905 | 3GPP TS 21.905 |
| TS 23.179 | 3GPP TS 23.179 |
| TS 23.203 | 3GPP TS 23.203 |
| TS 23.216 | 3GPP TS 23.216 |
| TS 23.379 | 3GPP TS 23.379 |
| TS 23.401 | 3GPP TS 23.401 |
| TS 23.468 | 3GPP TS 23.468 |
| TS 23.503 | 3GPP TS 23.503 |
| TS 23.700 | 3GPP TS 23.700 |
| TS 24.301 | 3GPP TS 24.301 |
| TS 24.801 | 3GPP TS 24.801 |
| TS 25.414 | 3GPP TS 25.414 |
| TS 25.442 | 3GPP TS 25.442 |
| TS 26.348 | 3GPP TS 26.348 |
| TS 26.891 | 3GPP TS 26.891 |
| TS 26.924 | 3GPP TS 26.924 |
| TS 26.928 | 3GPP TS 26.928 |
| TS 29.061 | 3GPP TS 29.061 |
| TS 29.116 | 3GPP TS 29.116 |
| TS 29.213 | 3GPP TS 29.213 |
| TS 29.414 | 3GPP TS 29.414 |
| TS 29.468 | 3GPP TS 29.468 |
| TS 29.513 | 3GPP TS 29.513 |
| TS 29.514 | 3GPP TS 29.514 |
| TS 29.827 | 3GPP TS 29.827 |
| TS 29.890 | 3GPP TS 29.890 |
| TS 32.130 | 3GPP TR 32.130 |
| TS 32.251 | 3GPP TR 32.251 |
| TS 32.293 | 3GPP TR 32.293 |
| TS 33.820 | 3GPP TR 33.820 |
| TS 33.851 | 3GPP TR 33.851 |
| TS 36.300 | 3GPP TR 36.300 |
| TS 36.305 | 3GPP TR 36.305 |
| TS 36.323 | 3GPP TR 36.323 |
| TS 37.355 | 3GPP TR 37.355 |
| TS 38.214 | 3GPP TR 38.214 |
| TS 38.300 | 3GPP TR 38.300 |
| TS 38.305 | 3GPP TR 38.305 |
| TS 38.323 | 3GPP TR 38.323 |
| TS 38.455 | 3GPP TR 38.455 |
| TS 38.473 | 3GPP TR 38.473 |