ARP

Allocation and Retention Priority

QoS →
Introduced in R99 Also in: Services, Radio Access Network

ARP is a 3GPP QoS parameter that prioritizes the establishment and retention of bearers during admission control and congestion to ensure critical services receive precedence.

Category
QoS
Introduced
R99
Where
Core Network › 5G Core
Also touches
2 segments
Specifications
41 specs
ARP Description Purpose Related Classification Detected Changes Specifications

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.

Classification

Part ofPCRF
Related approachesQCIPCC

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (5 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 3 changes

In Release 15, the Allocation and Retention Priority (ARP) function was enhanced to explicitly utilize the ARP priority level for influencing packet handling decisions. This change mandated that the ARP priority level be considered alongside the QCI (QoS Class Identifier) when managing packets. Furthermore, corrections were applied to the specifications to ensure the accurate and consistent application of this ARP priority level.

  • Use of ARP priority level in addition to QCI for packet handling TS 23.203CR1110
  • Use of ARP priority level in addition to QCI for packet handling TS 23.401CR3359
  • Corrections for ARP priority level TS 23.401CR3446
Rel-17 2 changes

In Release 17, the ARP function was enhanced in two specific areas. First, it introduced the capability for the MME to apply ARP Priority Levels based on its local configuration. Second, it defined specific handling procedures for the Allocation and Retention Priority when supporting IMS voice services in a home-routed roaming scenario.

  • ARP PL applied by MME per local configruation TS 23.401CR3648
  • Handling of ARP for IMS voice service in home routed roaming TS 23.401CR3695

Explore further

Broader topics and technologies where ARP plays a role.

Defining Specifications

3GPP specifications that define or reference ARP, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TR 21.905 vj00 3GPP Technical Terms and Definitions Rel-19
TS 23.179 vd50 MCPTT Functional Architecture Rel-13
TS 23.203 vj20 Policy and charging control architecture Rel-19
TS 23.216 vj00 SRVCC Architecture Enhancements Rel-19
TS 23.379 vk00 MCPTT Functional Architecture Rel-20
TS 23.401 vj50 Evolved Packet System (EPS) Stage 2 Description Rel-19
TS 23.468 vj00 Group Communication System Enablers for LTE Rel-19
TS 23.503 vk00 5G Policy and Charging Control Framework Rel-20
TS 23.700 vk00 XR Services Application Enablement Layer Rel-20
TS 24.301 vj60 NAS protocol for Evolved Packet System Rel-19
TS 24.801 v810 CT1 SAE NAS Aspects for EPC Rel-8
TS 25.414 vj00 UTRAN Iu Interface User Plane Transport Protocols Rel-19
TS 25.442 vj00 Node B Implementation Specific O&M Transport via RNC Rel-19
TS 26.348 vj00 xMB Interface Specification Rel-19
TS 26.891 vg00 Media Distribution Services in 5G System Rel-16
TR 26.924 vj00 MTSI QoS Improvement Study Rel-19
TR 26.928 vj00 Study on eXtended Reality (XR) in 5G Rel-19
TS 29.061 vj00 Packet Domain Interworking for PLMN Rel-19
TS 29.116 vj00 REST-based protocol for xMB reference point Rel-19
TS 29.213 vj20 PCC Signalling Flows and QoS Mapping Rel-19
TS 29.414 vj00 Nb Interface Bearer Transport & Control Protocols Rel-19
TS 29.468 vj00 MB2 Reference Point Protocol Definition Rel-19
TS 29.513 vj40 5G PCC Signalling Flows & QoS Mapping Rel-19
TS 29.514 vj40 5G System; Policy Authorization Service; Stage 3 Rel-19
TS 29.827 vg00 Policy and Charging for Volume Based Charging Rel-16
TS 29.890 vg00 CT3 5G System Technical Report Rel-16
TS 32.130 vj20 Network Sharing OAM&P Requirements Rel-19
TS 32.251 vj00 PS Domain Charging Management Rel-19
TS 32.293 vj00 Proxy Function in Domestic Service Provider Rel-19
TS 33.820 v1830 Home NodeB/eNodeB Security Architecture Rel-8
TR 33.851 vh10 Security for Industrial IoT in 5G Rel-17
TS 36.300 vj00 E-UTRAN Radio Interface Protocol Architecture Overview Rel-19
TS 36.305 vj00 UE Positioning in E-UTRAN Stage 2 Rel-19
TS 36.323 vj00 PDCP Protocol Specification Rel-19
TS 37.355 vj20 LTE Positioning Protocol (LPP) Rel-19
TS 38.214 vj10 NR Physical Layer Procedures for Data Rel-19
TS 38.300 vj00 NG-RAN Overall Description Rel-19
TS 38.305 vj00 NG-RAN UE Positioning Stage 2 Rel-19
TS 38.323 vj00 Packet Data Convergence Protocol (PDCP) Rel-19
TS 38.455 vj10 NR Positioning Protocol A (NRPPa) Rel-19
TS 38.473 vj10 5G F1 Application Protocol (F1AP) Rel-19
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.