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 Family 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 →

Technology family

Sessions, bearers and QoS · Core Network

  1. R96 PDP context
  2. R99 ARP, GBR, Radio Access Bearer (RAB), TFT, UMTS bearer service
  3. Rel-7 IP-CAN bearer, IP-CAN session, QCI
  4. Rel-8 APN-AMBR, Dedicated EPS bearer, Default EPS bearer, EPS bearer, EPS Bearer Identity (EBI), UE-AMBR
  5. Rel-9 Evolved ARP
  6. Rel-15 5QI, GFBR, MFBR, PDU Session, QoS Flow, Session-AMBR
  7. Rel-16 MA PDU Session

Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.

Release Timeline

Detected Changes Across Releases

verified against 3GPP sources

Documented changes in 13 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.

R99 introduced

Introduced in R99 (release dating of the term; no individual change cited).

Rel-8 specification text

ARP is specified for the first time in Rel-8 as an EPS bearer and PCC QoS parameter with priority level, pre-emption capability and pre-emption vulnerability, used for admission control and bearer retention.

  • “The ARP shall contain information about the priority level (scalar), the pre-emption capability (flag) and the pre-emption vulnerability (flag).” TS 23.401 v8.18.0
  • “The QoS parameter ARP contains information about the priority level, the pre-emption capability and the pre-emption vulnerability.” TS 23.203 v8.15.0
Rel-9 specification text

ARP gained new roles in Rel-9: a reserved ARP value for emergency bearers, protection of emergency-ARP bearers from deactivation, and Evolved ARP support in GPRS/PDP context binding and mapping.

  • “The new MME shall not deactivate emergency service related EPS bearers, i.e. EPS bearers with ARP values reserved for emergency services.” TS 23.401 v9.16.0
  • “the QoS parameters shall contain an ARP value that is reserved for intra-operator use of IMS Emergency calls.” TS 23.203 v9.14.0
  • “When the PCRF performs the bearer binding the ARP information in the PCC rule shall be ignored unless the SGSN has indicated support for Evolved ARP.” TS 23.203 v9.14.0
Rel-10 specification text

In Rel-10, ARP gained new roles: it is used by the SGW/MME to identify low-priority traffic, is always carried in Downlink Data Notification, and is set or upgraded by the PCRF for MPS bearers.

  • “When the Serving GW sends a Downlink Data Notification, it shall include both EPS Bearer ID and ARP.” TS 23.401 v10.13.0
  • “The SGW determines whether a bearer is for low priority traffic or not on the basis of the bearer's ARP priority level” TS 23.401 v10.13.0
  • “For MPS service, the PCRF shall generate the corresponding PCC/QoS rule(s) with the ARP/QCI parameters as appropriate for the prioritized service.” TS 23.203 v10.10.0
Rel-11 specification text

Rel-11 changes how ARP is used: MPS-associated ARP gets congestion-control and load re-balancing exemptions, the MME may downgrade ARP pre-emption capability, and the emergency ARP text is corrected.

  • “The MME should not apply congestion control for termination requests related with an ARP associated with MPS.” TS 23.401 v11.11.0
  • “When a UE is in ECM-CONNECTED mode with a bearer having an ARP associated with MPS, the MME should not release the UE for load re-balancing” TS 23.401 v11.11.0
  • “The MME, based on local policies, can downgrade the ARP pre-emption capability, APN-AMBR or MBR (for GBR bearers) parameters received over S8” TS 23.401 v11.11.0
Rel-12 1 CR

ARP handling changed: the PCRF must keep the default bearer's ARP priority level and pre-emption capability at least as high as MPS rules, and ARP priority drives DDN throttling and paging priority.

  • “the PCRF shall ensure that the ARP priority level of the default bearer is at least as high as the highest ARP priority level used” TS 23.203 v12.11.0
  • “The Paging priority in the Paging message is set based on priority level of the ARP IE received in Downlink Data Notification” TS 23.401 v12.11.0
  • The setting EPS bearer ID/ARP for MME paging strategy TS 29.274CR1337
Rel-13 1 CR

ARP gained new roles: S-GW sends ARP in Downlink Data Notification, MME maps ARP priority level to paging priority, and PCRF modifies ARP for flows sharing priority.

  • “One Paging Priority level can be used for multiple ARP priority level values. The mapping of ARP priority level values to Paging Priority level (or levels) is configured by operator policy.” TS 23.401 v13.14.0
  • “the PCRF shall try to make authorization and policy decisions taking the priority sharing indicator into account and modify the ARP of these PCC/QoS rules” TS 23.203 v13.10.0
  • ARP Value in Downlink Data Notification message TS 29.274CR1589
Rel-14 1 CR

PCC specification 23.203 added PCRF authorization of default EPS bearer QCI and ARP (immediate or deferred) and AF-suggested ARP pre-emption values, changing how ARP is controlled.

  • “It shall be possible for the PCRF to authorize the QCI and ARP of the default EPS bearer to be enforced by the PCEF” TS 23.203 v14.6.0
  • “The AF may also provide suggested pre-emption capability and vulnerability values per media flow to the PCRF.” TS 23.203 v14.6.0
  • Deferred default EPS bearer QCI and ARP change TS 23.203CR1068
Rel-15 1 CR

In Rel-15 the eNodeB may be configured to use the ARP priority level in addition to QCI for packet handling, and ARP is specified for the 5G System (paging priority, QoS flows).

  • “the eNodeB can be configured to also use a bearer's ARP priority level in addition to the QCI to determine the relative priority” TS 23.401 v15.13.0
  • “The decision by the AMF whether to include Paging Priority in the Paging Message is based on the ARP value” TS 23.501 v15.13.0
  • Use of ARP priority level in addition to QCI for packet handling TS 23.401CR3359
Rel-16 specification text

ARP handling was extended in Rel-16: RLOS bearers get a reserved lower-priority ARP, ARP semantics were refined to cover QoS Flow handover, and PCF derives ARP for MCS and priority sharing.

  • “the PCRF provides the PDN GW with the QoS parameters, based on operator policy, including an ARP value reserved for the Restricted Local Operator Services” TS 23.401 v16.14.0
  • “The ARP pre-emption capability defines whether a QoS Flow may get resources that were already assigned to another QoS Flow with a lower priority.” TS 23.501 v16.20.0
  • “the PCF shall ensure that the ARP priority level of the default QoS flow is at least as high as the highest ARP priority level” TS 29.512 v16.23.0
Rel-17 1 CR

Rel-17 adds ARP override handling: the MME or V-SMF may override the ARP received from the HPLMN for IMS voice in home-routed roaming, and the MME may downgrade ARP priority level.

  • “the V-SMF, based on local policy, may override the ARP received from HPLMN over N16 if the ARP indicates priority not in line with the local policy in VPLMN” TS 23.501 v17.15.0
  • “the MME, based on local policy, can override the ARP (i.e. ARP priority level, ARP pre-emption capability, ARP pre-emption vulnerability) received over S8” TS 23.401 v17.11.0
  • Handling of ARP for IMS voice service in home routed roaming TS 23.401CR3695
Rel-18 specification text

VPLMN QoS constraints and PCF-authorized default QoS now include 5QI Priority Level alongside ARP, and ARP use in default QoS for groups, paging priority and packet marking was added.

  • “The QoS constraints may contain 5QI(s), 5QI Priority Level and ARP for the QoS Flow associated with the default QoS rule” TS 23.501 v18.12.0
  • “delivery of priority indication during the Paging procedure is provided by inclusion of the ARP in the N11 interface "N1N2MessageTransfer" message” TS 23.501 v18.12.0
  • “StreamRank: set to zero for ARP priority values 1-8; set to one for other ARP values.” TS 23.501 v18.12.0
Rel-19 specification text

In TS 23.501, NG-RAN Paging Priority for RRC_INACTIVE UEs is now derived from the ARP plus a service priority (RAN Paging Priority, values 1 to 256), and the PCF's ARP modification for IMS signalling now depends on UDR data.

  • “the NG-RAN determines Paging Priority based on the ARP associated with the QoS Flow as provisioned by the operator policy and the service priority” TS 23.501 v19.9.0
  • “the PCF modifies the ARP of the QoS Flow used for IMS signalling” TS 23.501 v19.9.0
  • “or based on the ARP of the PDU Session context, the following handling applies:” TS 23.501 v19.9.0

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