Description
The ProSe Encryption Key (PEK) is a fundamental security element within the 3GPP Proximity Services (ProSe) architecture, first standardized in Release 12. It is specifically used to provide confidentiality protection for user data transmitted directly between UEs over the sidelink PC5 reference point. The PEK is generated and managed as part of the ProSe security context. Typically, this context is established during the ProSe Direct Discovery or Direct Communication authorization and key establishment procedures, which may involve the ProSe Function in the network. The key is derived using key derivation functions (KDFs) specified in 3GPP TS 33.303, often from a root key like the ProSe Key (PK). Once derived, the PEK is provided to the involved UEs. In the protocol stack, the PEK is used by the Packet Data Convergence Protocol (PDCP) layer, as specified in TS 36.323 for LTE-based ProSe and its equivalents for NR sidelink. The PDCP layer uses the PEK to perform encryption (and potentially integrity protection, though that may use a separate key) on the user plane packets before they are transmitted over the PC5 interface. The receiving UE's PDCP layer uses the same PEK to decrypt the data. The lifecycle of the PEK, including its derivation, activation, usage, and deletion, is strictly controlled by the UE's security management functions to prevent key reuse and ensure forward secrecy. Its role is critical in scenarios like public safety D2D communication and V2X, where direct UE-to-UE links must be as secure as network-relayed connections.
Purpose & Motivation
The PEK was introduced to address the security requirements of direct Device-to-Device (D2D) communication, a cornerstone of Proximity Services (ProSe). Before ProSe, all UE communication was routed through the network infrastructure (e.g., eNB, gNB), which inherently provided a point for applying standard cellular security mechanisms. The introduction of direct PC5 communication for public safety, commercial D2D, and later V2X created a new attack surface where eavesdroppers could intercept transmissions between nearby devices. Traditional cellular security keys (like K_{eNB}) were not applicable to this direct link. The PEK solves this by providing a dedicated encryption key for the PC5 user plane. Its creation was motivated by the need for secure off-network communication, essential for first responders when cellular infrastructure is damaged. It also enables secure V2X applications where vehicles exchange safety messages (e.g., collision warnings) directly, requiring strong confidentiality to protect driver privacy and prevent spoofing attacks. The PEK fills the security gap for direct communication, ensuring that ProSe services meet the stringent confidentiality requirements expected from 3GPP systems.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (3 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-12, normative work from Rel-17.
In Release 17, the primary new introduction for the PEK function was support for TLS version 1.3 to protect data transfer between the UE and the ProSe Function over the PC3 reference point. This update modernized the security protocol used for procedures like service authorization and configuration data transfer. Additionally, corrections were made to related documentation and restricted discovery procedures for 4G ProSe.
Explore further
Broader topics and technologies where PEK plays a role.
Defining Specifications
3GPP specifications that define or reference PEK, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 33.303 vj00 | ProSe Security Specification for EPS | Rel-19 |
| TS 36.323 vj00 | PDCP Protocol Specification | Rel-19 |