Priority Information Element

Description

The Priority Information Element (PIE) is not a single, monolithic entity but a conceptual field embedded within various 3GPP protocol messages and data structures. Its value conveys a priority level that network nodes use to make real-time decisions about handling traffic. The PIE appears in multiple layers and domains: at the NAS (Non-Access Stratum) level within signaling messages like Service Request or PDN Connectivity Request; at the AS (Access Stratum) for Radio Resource Control (RRC); within QoS parameters of an EPS/5GS bearer (Allocation and Retention Priority, ARP); and in IMS signaling (e.g., SIP headers for emergency calls or MCPTT).

When a User Equipment (UE) initiates a service, such as an emergency call or a high-priority Mission Critical service, it includes a specific PIE value in the relevant signaling message. For example, in 5GS, the UE sets the "5GSM priority" value in the PDU SESSION ESTABLISHMENT REQUEST. The network nodes, including the Access and Mobility Management Function (AMF), Session Management Function (SMF), and the gNodeB, inspect this PIE. Based on configured policies, the network applies priority handling. This can mean prioritizing the RRC connection establishment for that UE over other UEs, accepting the session establishment request even under congestion (high ARP priority level), and scheduling radio resources for its bearers with higher precedence.

The PIE works in conjunction with other QoS mechanisms. In the core network, the ARP parameter, which contains a priority level, pre-emption capability, and pre-emption vulnerability, is a key instantiation of the PIE concept for bearers. A high-priority ARP can trigger the Policy and Charging Rules Function (PCRF/PCF) to apply specific QoS policies. In the RAN, the QoS Flow Identifier (QFI) and 5QI (5G QoS Identifier) are mapped to priority levels that influence packet scheduling algorithms at the gNodeB. The end-to-end effect is that a data flow marked with a high priority PIE experiences lower latency, higher reliability, and a greater chance of successful session establishment during network congestion compared to best-effort traffic.

Purpose & Motivation

The PIE exists to solve the fundamental problem of resource scarcity and contention in shared mobile networks. Without a standardized mechanism to differentiate traffic importance, all sessions would be treated equally (best-effort), making it impossible to guarantee performance for services where timeliness and reliability are critical. This is unacceptable for public safety (emergency calls, first responder communications), network control signaling (which must get through to maintain network operation), and other operator-defined premium services.

Historically, early cellular systems had limited support for prioritization. The concept evolved significantly with the introduction of IMS and all-IP networks in 3GPP Rel-7 and later with LTE/EPC. The need for a consistent, end-to-end priority marking mechanism became acute with the standardization of IMS Emergency Calls, which require pre-emption and guaranteed access. The PIE provides this common "language of priority" that can be understood from the UE, through the RAN, across the core network, and into the service layer (IMS).

Furthermore, the drive for network slicing and support for diverse vertical industries (e.g., automotive, industrial IoT) in 5G amplified the need for sophisticated priority handling. Different slices and services have vastly different latency and reliability requirements. The PIE, especially as part of the 5QI and QoS profile, allows the network to dynamically apply the appropriate resource management strategy on a per-session or per-flow basis. It is a key enabler for the "priority service" feature defined in 3GPP, ensuring that authorized users and services can receive enhanced performance as defined by the operator's policy and regulatory mandates.

Key Features

• Embedded in multiple protocol layers (NAS, AS, IMS) for end-to-end priority signaling
• Governs RRC connection establishment priority and radio resource scheduling
• Integral part of the Allocation and Retention Priority (ARP) parameter for bearer management
• Used to derive QoS Class Identifier (QCI) / 5G QoS Identifier (5QI) characteristics
• Supports pre-emption (high-priority sessions can bump lower-priority ones) and pre-emption vulnerability
• Essential for IMS Emergency Session establishment and Mission Critical Services (MCPTT, MCVideo)

Evolution Across Releases

Defining Specifications