Description
The PC5 QoS Identifier (PQI) is a scalar value that serves as a reference to a standardized QoS profile defined in 3GPP specifications for communications over the PC5 reference point. The PC5 interface enables direct communication between User Equipments (UEs), known as sidelink communication, which is pivotal for Vehicle-to-Everything (V2X), public safety, and commercial D2D services. Each PQI value corresponds to a specific combination of QoS parameters, including resource type (e.g., Guaranteed Bit Rate or Non-GBR), priority level, packet delay budget, packet error rate, and optionally, a default maximum data burst volume and averaging window.
In operation, when an application on a UE initiates a communication session over PC5, it requests a certain QoS level. This request is often translated into a PQI value. The PQI is used during the PC5 unicast link establishment or modification procedures, as defined in specifications like TS 23.287. The initiating UE signals the desired PQI to the peer UE. Both UEs then use this identifier to locally derive the full set of QoS characteristics from the standardized table. This derivation informs critical functions such as packet classification, marking, scheduling, and admission control on the sidelink radio bearers.
The architecture leverages PQI to abstract complex QoS parameter sets into a simple integer, simplifying signaling and ensuring consistency. The QoS profile referenced by a PQI dictates how the data flow should be treated across the protocol layers, particularly at the Access Stratum (AS). For example, a PQI associated with a high-priority, low-latency resource type will influence how the MAC layer schedules transmissions and selects resources in the sidelink resource pool, potentially using more reliable modulation and coding schemes or more frequent transmission opportunities.
PQI is a cornerstone of the QoS framework for NR sidelink and evolved LTE sidelink (when used in a 5G context). It works in tandem with the PQFI (PC5 QoS Flow ID). While the PQI defines the "what"—the QoS characteristics template—the PQFI identifies the "which"—the specific data flow instance to which those characteristics are applied. This separation allows multiple flows (each with a unique PQFI) to share the same PQI if they have identical QoS requirements, or to have different PQIs if their requirements differ. Management entities, such as the ProSe Function or the 5G Core Network's Policy Control Function (PCF), can provision or authorize the use of specific PQI values for different services or applications, enabling network-controlled QoS even for direct UE-to-UE communication.
Purpose & Motivation
The PQI was created to standardize and streamline QoS management for direct PC5-based communication, which became essential with the introduction of advanced V2X services in 3GPP Release 14 and its significant enhancement in the 5G context from Release 16. Earlier D2D mechanisms lacked a comprehensive, standardized QoS identifier, making it difficult to ensure predictable and interoperable service quality across different manufacturers' devices, especially for life-critical applications like autonomous driving.
It solves the problem of complex and inefficient signaling of full QoS parameter sets for every communication session. Without PQI, UEs would need to negotiate and signal numerous individual parameters (delay budget, error rate, etc.) each time, increasing signaling overhead and setup latency. PQI condenses this information into a single, well-known index, drastically simplifying session establishment and modification. This efficiency is crucial for dynamic V2X environments where communication sessions may be brief and established rapidly.
The motivation stems from the need to extend the robust QoS framework of 5G, which uses the 5QI for Uu interface, to the sidelink interface. This ensures a unified approach to service quality across all access types. PQI allows the network to exert policy control over sidelink communications by authorizing which PQI values a UE can use for specific services. It addresses the limitations of earlier ProSe Per-Packet Priority (PPPP), which was a simpler priority indicator, by providing a full set of QoS characteristics necessary to support the diverse and stringent requirements of 5G-enabled verticals like automotive and industrial IoT.
What changed in its specifications
The latest release-to-release comparison of specifications that define PQI. Each summary describes the whole specification, not only this term.
Rel-19 added real-time flight path reporting, QoS-based flight route selection, no-transmit zone management, and supporting APIs/procedures for UAS applications.
Full comparison in TS 23.255 →Rel-19 adds NEF-assisted pre-flight planning, USS changeover, and network-assisted detect-and-avoid to TS 23.256. It also adds no-transmit zone enforcement for UAV UEs and altitude reporting.
Full comparison in TS 23.256 →Technology family
Sidelink, D2D and V2X · Services
- Rel-12 EPC-level ProSe Discovery, ProSe, ProSe Direct Communication, ProSe Direct Discovery, PSBCH, PSCCH, PSDCH, PSSCH, Sidelink
- Rel-13 PPPP, ProSe UE-to-Network Relay, Remote UE
- Rel-14 RSU
- Rel-15 PPPR
- Rel-16 NR sidelink communication, PC5 QoS Flow, PQI
- Rel-17 5G ProSe Direct Communication, 5G ProSe Direct Discovery, 5G ProSe Remote UE, 5G ProSe UE-to-Network Relay, NR sidelink discovery, SRAP
- Rel-18 5G ProSe UE-to-UE Relay, NR SL CA, Sidelink Positioning, SL-PRS, U2U Relay UE, U2U Remote UE
- Rel-19 5G ProSe Intermediate UE-to-Network Relay
- PQI counterpart in another generation: PPPP
“The Priority Level for NR PC5 has the same format and meaning as the Priority value of the ProSe Per-Packet Priority (PPPP) for LTE PC5 defined in TS 23.285 [8].” TS 23.287
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 sourcesDocumented changes in 4 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.
TS 23.287 first defines PQI as a special 5QI referencing standardized PC5 QoS characteristics, with a standardized PQI-to-characteristics mapping table for NR-based V2X sidelink communication.
- “A PQI is a special 5QI, as defined in clause 5.7.2.1 of TS 23.501 [6], and is used as a reference to PC5 QoS characteristics” TS 23.287 v16.7.0
- “Standardized PQI values have one-to-one mapping to a standardized combination of PC5 QoS characteristics as specified in Table 5.4.4-1.” TS 23.287 v16.7.0
TS 24.554 first specifies PQI use for 5G ProSe: PC5 QoS profiles contain a PQI, 5QI-to-PQI mapping rules, and relay UE PQI determination for PC5 QoS flows.
- “the PC5 QoS profile containing a PQI;” TS 24.554 v17.10.0
- “a mapping between a 5QI value and a 5G ProSe PQI value over PC5 for traffic relayed over the PC5 interface;” TS 24.554 v17.10.0
- “shall determine the PQI based on the QoS mapping rules configured in clause 5.2.5;” TS 24.554 v17.10.0
PQI use was extended in Rel-18: new PQI values for A2X over PC5, default PQI configuration for MC services over 5G ProSe, PQI determination for UE-to-UE relay hops, and PQI mapping rules for RSPP ranging/sidelink positioning.
- New PQI values for A2X communication over PC5 reference point TS 23.256CR0109
- “This leaf node indicates the default PQI value (as specified in 3GPP TS 23.304 [25]) for the group call signalling for MCPTT.” TS 24.483 v18.4.0
- “shall determines the PQI for the first hop PC5 QoS control and PQI for the second hop PC5 QoS control based on its implementation;” TS 24.554 v18.11.0
Multi-hop layer-3 UE-to-network relay procedures newly specify how PQI is determined for end-to-end PC5 QoS and PC5 QoS flows via QoS mapping, and how it is updated.
- “shall determine the PQI of the end-to-end PC5 QoS based on the QoS mapping rules configured in clause 5.2.8;” TS 24.554 v19.6.0
- “shall determine the PQI of the PC5 QoS flow based on the PQI of the end-to-end PC5 QoS” TS 24.554 v19.6.0
- “shall further update the end-to-end PC5 QoS parameters with the updated PQI value” TS 24.554 v19.6.0
Defining Specifications
3GPP specifications that define or reference PQI, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.255 vk10 | UAS Application Enabler Architecture | Rel-20 read |
| TS 23.256 vj50 | UAS Support Architecture Enhancements | Rel-19 read |
| TS 23.287 vk00 | 5G V2X Architecture Enhancements | Rel-20 read |
| TS 23.304 vk10 | 5G Proximity Services (ProSe) Stage 2 | Rel-20 read |
| TR 23.764 vh10 | Study on V2X Application Layer Enhancements | Rel-17 read |
| TS 24.281 vk10 | MCVideo Signalling Control | Rel-20 read |
| TS 24.282 vk10 | MCData Signalling Control Protocols | Rel-20 read |
| TS 24.379 vk10 | MCPTT Call Control Protocol | Rel-20 read |
| TS 24.481 vj30 | MCS Group Management Protocol | Rel-19 read |
| TS 24.483 vk10 | Mission Critical Services Management Objects | Rel-20 read |
| TS 24.484 vk10 | Mission Critical Services Configuration Management | Rel-20 read |
| TS 24.514 vj30 | Ranging & Sidelink Positioning in 5GS | Rel-19 read |
| TS 24.554 vk10 | 5G ProSe Protocols and Procedures | Rel-20 read |
| TS 24.587 vj30 | V2X Services Protocols for 5G System | Rel-19 read |
| TR 26.806 vi00 | Technical Report on Smartly Tethering AR Glasses | Rel-18 read |
| TR 26.928 vj00 | Study on eXtended Reality (XR) in 5G | Rel-19 read |
| TS 32.277 vj20 | Charging Management for Proximity Services (ProSe) | Rel-19 read |
| TR 32.846 vh00 | Charging for ProSe in 5GS | Rel-17 read |
| TS 38.300 vj40 | NR and NG-RAN Overall Description | Rel-19 read |
| TS 38.321 vj40 | NR MAC Protocol Specification | Rel-19 read |