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
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (70 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, the ARP function was enhanced to support the subscription and notification of resource allocation outcomes, including specific service procedures for this capability. It introduced the explicit use of the ARP priority level in addition to the QCI for packet handling, alongside corrections to ensure its proper implementation. Furthermore, the release added support for priority services, including MCVideo, and enabled resource reservation for services sharing the same priority level.
- Subscription and notification of resources allocation outcome, data model TS 29.514CR0007
- Subscription to resources allocation outcome, service procedures TS 29.514CR0008
- Notification of resource allocation outcome, service procedures TS 29.514CR0009
- Support of Priority Services TS 29.514CR0023
- 23.401 PCEF Support for Data Off phase 2 TS 23.401CR3289
- Use of ARP priority level in addition to QCI for packet handling TS 23.401CR3359
+ 10 more changes
In Release 16, the ARP function was enhanced to support new priority mechanisms including User Requested Priority, MCS Priority Level, and a Priority Sharing Indication. It also introduced specific procedures for emergency sessions via the SBI Message Priority mechanism and corrections for pre-emption conditions in sidelink resource allocation. Furthermore, PCC rule support was extended to handle the newly defined MCS Priority Levels.
- User requested priority in 23.379 TS 23.379CR0196
- Communication priority for functional aliases TS 23.379CR0217
- MCS Priority Level TS 29.513CR0099
- Priority Sharing Indication TS 29.514CR0126
- PCC support for MCS Priority Levels TS 23.503CR0267
- UE Radio Capability ID allocation in EPS TS 23.401CR3527
+ 5 more changes
In Release 17, enhancements to the ARP function included the application of ARP priority levels by the MME per local configuration and clarified the handling of ARP for the IMS voice service in home routed roaming scenarios. The release also introduced PCRF control of MPS for Data Transport Service and provided corrections and clarifications on priority rules and resource allocation failure procedures.
- Multimedia Priority Service (MPS) Phase 2 support for Data Transport Service TS 23.401CR3620
- Multimedia Priority Service (MPS) Phase 2 support for Data Transport Service TS 23.503CR0507
- PCRF control of MPS for DTS TS 29.213CR0743
- Introduction of new bands and bandwidth allocation for LTE-based 5G terrestrial broadcast TS 36.300CR1360
- Priority of the user for initiating/receiving calls TS 23.379CR0240
- ARP PL applied by MME per local configruation TS 23.401CR3648
+ 11 more changes
In Release 18, the Allocation and Retention Priority (ARP) function was enhanced to support pre-emptive or high priority and commencement mode within the remotely initiated call request procedure. It also saw updates for priority alignment, including the alignment of the mps-PriorityAccess cause in RRC Resume and the support for 5QI Priority Level in QoS constraints. Furthermore, corrections were made to priority-based QoE measurements and to the handling of priority users in discontinuous coverage overload control scenarios.
- Update to remotely initiated call request procedure to support pre-emptive or high priority and commencement mode TS 23.379CR0307
- Redundant steering mode Resource allocation notification to AF TS 29.514CR0598
- Discontinuous coverage overload control priority users term alignment TS 23.401CR3757
- Support for 5QI Priority Level in QoS constraints TS 23.503CR0757
- Correction on contiguous RB based resource allocation TS 38.214CR0550
- Correction on SL partial sensing for interlaced RB allocation and MCSt TS 38.214CR0559
+ 6 more changes
In Release 19, the enhancements to ARP primarily focused on extending priority mechanisms for Mission Critical Services (MPS), specifically for Messaging and SMS. This included introducing support for MPS priority paging for Mobile-Terminated SMS and enabling MT SMS over NAS with priority for messaging. Additionally, the release introduced procedures for the AF (Application Function) to trigger PCEF (Policy and Charging Enforcement Function) failure checking, adding new detection conditions for the PCRF and PCF.
- Support of MPS priority for Messaging TS 23.503CR1343
- 24.301 MPS for Messaging Paging Priority TS 24.301CR4169
- Initial paging with priority in EPS TS 24.301CR4444
- Add a new condition for the PCRF detecting PCEF failure in time TS 29.213CR0751
- Update the procedure of AF trigger the PCEF failure checking TS 29.213CR0753
- Add a new condition for the PCF detecting PCEF failure in time TS 29.513CR0605
+ 8 more changes
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.
| Specification | Title | Release |
|---|---|---|
| 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 |