ProSe Per-Packet Priority

Description

ProSe Per-Packet Priority (PPPP) is a fundamental Quality of Service (QoS) parameter defined within the 3GPP architecture for Proximity-based Services (ProSe), specifically for sidelink communication (e.g., PC5 interface). It operates by assigning a numerical priority value to each individual data packet generated by a ProSe-enabled User Equipment (UE) for direct communication with another UE. This priority value is an integer, typically ranging from 1 (highest priority) to 8 (lowest priority) as defined in the relevant specifications, and is included within the packet's protocol data unit.

The PPPP value is a key input for the Medium Access Control (MAC) layer's scheduling and resource selection procedures on the sidelink. In both network-scheduled (mode 1) and UE autonomous (mode 2) resource allocation modes, the PPPP influences how the UE contends for and utilizes sidelink resources. A packet with a higher priority (lower PPPP number) will be scheduled for transmission before packets with lower priority. This influences the logical channel prioritization process, buffer status reporting, and the selection of the appropriate resource pool configured for a given priority range. The network can pre-configure resource pools that are mapped to specific PPPP levels, ensuring high-priority traffic uses resources with more favorable characteristics, such as lower latency or higher reliability.

Architecturally, PPPP is associated with a ProSe Per-Packet Priority Profile, which is configured in the UE, often via provisioning or policy control. The application layer or a ProSe function within the UE assigns the PPPP based on the nature of the service (e.g., public safety voice, video, or data). This mechanism is decoupled from traditional EPS bearer-based QoS, as sidelink communication may occur outside network coverage. PPPP's role is critical in managing congestion in dense D2D scenarios, such as public safety operations or vehicle-to-everything (V2X) platooning, where it ensures that life-critical alerts or control messages are not delayed by less important background data traffic.

Purpose & Motivation

PPPP was introduced to address the specific QoS demands of direct Device-to-Device communication, which traditional cellular QoS models (based on EPS bearers between UE and network) could not adequately support. Prior to ProSe, QoS was managed end-to-end via the core network. For sidelink communications, especially out-of-coverage or at the edge of coverage, a distributed, per-packet prioritization mechanism was necessary. The primary problem it solves is the deterministic prioritization of traffic in a decentralized radio environment where multiple UEs contend for a shared sidelink resource pool.

Its creation was motivated heavily by public safety and mission-critical communication requirements, which were a key driver for ProSe standardization. In disaster scenarios where network infrastructure may be compromised, first responders using D2D modes need guaranteed transmission for emergency alerts and command communications. PPPP provides this by ensuring that a 'lifeline' voice packet from a firefighter is always treated as more important than a non-urgent data update from another device. It also supports the evolution of V2X services, where a brake warning message from a car must have absolute priority over a periodic beacon message to prevent accidents. PPPP thus enables service differentiation in a purely peer-to-peer radio link, a capability that was absent in pre-Rel-13 LTE.

Key Features

• Per-packet granularity for QoS on the sidelink (PC5 interface)
• 8-level priority scale (1=highest, 8=lowest) for traffic differentiation
• Direct influence on MAC layer scheduling and resource selection in UE
• Mapping to specific sidelink resource pools for isolation and guaranteed performance
• Operational in both network-coverage (mode 1) and out-of-coverage (mode 2) scenarios
• Independent of traditional EPS bearer QoS, tailored for direct D2D communication

Evolution Across Releases

Defining Specifications