Allocation and Retention Priority (ARP) in LTE/EPS: Priority, Pre-emption, and Bearer Control

The Allocation and Retention Priority (ARP) is a bearer-level QoS parameter that contains the following information:

  • Priority Level — defines the relative importance of a bearer establishment or bearer-modification request when network resources are limited. It enables the network to determine whether a requested bearer can be admitted or must be rejected, and may also be used to determine which existing bearer can be pre-empted. Although ARP applies to both GBR and non‑GBR bearers, it is typically used for admission control of GBR traffic because GBR bearers require resource reservation.

  • Pre-emption Capability — indicates whether a bearer with this ARP is permitted to preempt (remove) another lower priority bearer (with pre-emption vulnerability) in order to obtain its resources.

  • Pre-emption Vulnerability — indicates whether a bearer with this ARP can itself be preempted by another higher-priority bearer (with pre-emption capability) so that its resources can be released.

  • The pre-emption capability and the pre-emption vulnerability can be either set to 'yes' or ‘no'

    EPS supports 15 ARP priority levels, numbered 1 to 15, where a lower value indicates a higher priority. A VoIP call for emergency services is assigned a lower ARP value than a regular VoIP call, giving it higher priority. Pre-emption can be used during handover to drop existing lower-priority bearers when there is a resource limitation. Another example of pre-emption is a disaster situation, where ARP can be used to prioritize emergency calls by dropping bearers with lower priority (higher ARP values).

    The ARP priority scale (1–15) is divided into two bands based on which network is authorized to assign that priority level.

    Priority levels 1–8 are reserved for services that the serving network — the operator currently providing service to the UE — has authorized for prioritized treatment. In practice, this authorization is only straightforward when the serving network has its own PCEF in the signalling path, i.e., in local breakout roaming or when the UE is on its home network. In home-routed roaming, however, the PCEF sits in the home network's PGW, and all PCC rules — including ARP — are supplied by the home PCRF; the visited network has no PCEF of its own to inject a competing policy. Serving-network-authorized ARP in this case is achieved mainly through special procedures such as Emergency Attach, where the serving network locally breaks out an emergency PDN connection and applies its own locally configured ARP value, bypassing home-routing entirely. Beyond such cases, using levels 1–8 during home-routed roaming generally depends on a pre-existing roaming agreement between the two operators, since there is no live signalling path for the visited network to assert this priority otherwise.

    Priority levels 9–15 are reserved for services that the home network has authorized. This band is the normal case for roaming subscribers: the home PCRF derives the ARP value from the subscriber's profile in the HSS and, in home-routed roaming, sends it via the home PCEF; in local breakout, it is instead relayed to the visited network's PCRF over the S9 interface, which passes it to the local PCEF.

    This split exists to prevent future conflicts: by keeping the 1–8 band reserved for serving-network authorization, later 3GPP releases can define specific use cases — such as emergency or public-safety services — within that range without colliding with home-network-authorized priorities in the 9–15 band. The split is a coordination convention rather than a hard technical restriction: levels 1–8 may still be used in general roaming situations if the home and visited operators have a roaming agreement ensuring consistent use of those levels.

Leave a Reply

Your email address will not be published. Required fields are marked *