Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · QoS

ARP

Allocation and Retention Priority

QoS →

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.

Introduced
R99
Where
Core Network › 5G Core
Specifications
41 specs
Also in
Services, Radio Access Network
ARP Description Purpose What changed Neighbours 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.

What changed in its specifications

The latest release-to-release comparison of specifications that define ARP. Each summary describes the whole specification, not only this term.

TR 21.905Rel-17 → Rel-18

Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TR 21.905 →
TS 23.203Rel-16 → Rel-17

NB-IoT/eMTC support for Non-Terrestrial Networks: adds QCI characteristic for satellite access, note on GEO/LEO delays, and PCRF policy control for satellite PDN connections.

Full comparison in TS 23.203 →

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
  • 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
  • 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

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 vj20 3GPP Terminology and Definitions Rel-19 read
TS 23.179 vd50 MCPTT Functional Architecture Rel-13 read
TS 23.203 vk10 Policy and Charging Control Architecture Rel-20 read
TS 23.216 vj00 SRVCC Architecture Enhancements Rel-19 read
TS 23.379 vk40 Mission Critical Push-to-Talk Architecture Rel-20 read
TS 23.401 vk10 Evolved Packet System Architecture Rel-20 read
TS 23.468 vj00 Group Communication System Enablers for LTE Rel-19 read
TS 23.503 vk30 5G Policy and Charging Control Framework Rel-20 read
TS 23.700 vk10 AI/ML Application Layer Support Phase 2 Rel-20 read
TS 24.301 vk10 EPS NAS Mobility and Session Management Rel-20 read
TS 24.801 v810 CT1 SAE NAS Aspects for EPC Rel-8 read
TS 25.414 vj00 UTRAN Iu Interface User Plane Transport Protocols Rel-19 read
TS 25.442 vj00 Node B Implementation Specific O&M Transport via RNC Rel-19 read
TS 26.348 vj00 xMB Interface Specification Rel-19 read
TS 26.891 vg00 Media Distribution Services in 5G System Rel-16 read
TR 26.924 vj00 MTSI QoS Improvement Study Rel-19 read
TR 26.928 vj00 Study on eXtended Reality (XR) in 5G Rel-19 read
TS 29.061 vk10 Packet Domain Interworking Requirements Rel-20 read
TS 29.116 vj00 REST-based protocol for xMB reference point Rel-19 read
TS 29.213 vj30 PCC Procedures and Flows Rel-19 read
TS 29.414 vj00 Nb Interface Bearer Transport & Control Protocols Rel-19 read
TS 29.468 vj00 MB2 Reference Point Protocol Definition Rel-19 read
TS 29.513 vk10 5G PCC Signalling Flows Rel-20 read
TS 29.514 vk10 Policy Authorization Service Rel-20 read
TS 29.827 vg00 Policy and Charging for Volume Based Charging Rel-16 read
TS 29.890 vg00 CT3 5G System Technical Report Rel-16 read
TS 32.130 vj20 Network Sharing OAM&P Requirements Rel-19 read
TS 32.251 vj00 PS Domain Charging Management Rel-19 read
TS 32.293 vj00 Proxy Function in Domestic Service Provider Rel-19 read
TS 33.820 v830 H(e)NB Security Threats and Countermeasures Rel-8 read
TR 33.851 vh10 Security for Industrial IoT in 5G Rel-17 read
TS 36.300 vj20 E-UTRAN Radio Interface Protocol Architecture Rel-19 read
TS 36.305 vj00 UE Positioning in E-UTRAN Stage 2 Rel-19 read
TS 36.323 vj00 PDCP Protocol Specification Rel-19 read
TS 37.355 vj30 LTE Positioning Protocol (LPP) Rel-19 read
TS 38.214 vj50 NR Physical Layer Data Channel Procedures Rel-19 read
TS 38.300 vj40 NR and NG-RAN Overall Description Rel-19 read
TS 38.305 vj30 NG-RAN UE Positioning Stage 2 Rel-19 read
TS 38.323 vj10 PDCP Protocol Specification Rel-19 read
TS 38.455 vj30 NR Positioning Protocol A Rel-19 read
TS 38.473 vj40 F1 Application Protocol (F1AP) Rel-19 read