DPKK

MCData Payload Protection Key

Security →
Introduced in Rel-14

DPKK is the cryptographic key used in Mission Critical Data services to encrypt and protect the payload of data communications, ensuring confidentiality and integrity for sensitive operational data.

Category
Security
Introduced
Rel-14
Where
Services
Specifications
1 specs
DPKK Description Purpose Related Classification Detected Changes Specifications

Description

The MCData Payload Protection Key (DPKK) is a security key defined within the 3GPP framework, specifically in TS 24.582, for protecting data payloads in Mission Critical Data services. It operates within the security architecture for MCX (Mission Critical Communication) services, which are designed for public safety and critical infrastructure communications. The DPKK is generated and managed as part of a key hierarchy, often derived from higher-level keys like the MCData Service Key (DSK) or other authentication credentials, to provide a dedicated key for encrypting the actual content (payload) of data messages, files, or other data transmissions. This ensures that sensitive information, such as location data, images, or text messages, remains confidential and tamper-proof during exchange over 3GPP networks.

In practice, the DPKK is applied using standardized encryption algorithms, such as AES (Advanced Encryption Standard), to secure the payload before transmission. The key is typically established during the service authorization and session setup phases, where endpoints (e.g., user equipment or servers) authenticate and negotiate security parameters. The DPKK works in conjunction with other security mechanisms, like integrity protection and key identifiers (e.g., DPKK-ID), to form a comprehensive security layer. Its usage is mandated in MCData scenarios to meet the high-security requirements of public safety communications, preventing eavesdropping and unauthorized access.

The role of DPKK extends beyond mere encryption; it integrates with the overall MCData security framework, which includes key management protocols, key distribution, and lifecycle management (e.g., key expiration and renewal). This ensures that payload protection adapts to dynamic network conditions and threat landscapes. By isolating payload encryption from other security functions, DPKK allows for efficient and scalable security implementations, supporting various MCData applications like group communications, file transfer, and data streaming in critical scenarios.

Purpose & Motivation

DPKK was introduced to address the need for robust payload security in Mission Critical Data services, which are used by public safety agencies, emergency responders, and critical infrastructure operators. Prior to its standardization, data communications in critical scenarios often relied on less specialized security measures or proprietary solutions, which could be vulnerable to attacks or lack interoperability. The creation of DPKK as part of 3GPP Release 14 was motivated by the growing adoption of LTE and 5G networks for mission-critical applications, requiring standardized, high-assurance encryption to protect sensitive data payloads from interception and manipulation.

The key problem DPKK solves is ensuring end-to-end confidentiality and integrity for data exchanged in MCData sessions, which is crucial for operational security and privacy. Without such a dedicated key, payloads might be exposed to threats in transit, compromising mission effectiveness. DPKK provides a standardized approach that integrates with 3GPP's broader security architecture, enabling seamless interoperability across different vendors and networks, and supporting regulatory compliance for public safety communications.

Classification

Specific typesDPKK-ID

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (9 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Studied in Rel-14, normative work from Rel-16.

Rel-16 4 changes

In Release 16, the DPKK function was newly introduced to provide end-to-end protection for the data payload in MCData Short Data Service (SDS) messages and file transfers sent via the media plane. This function ensures that the body of an MSRP SEND request carrying the actual SDS data or file is protected separately from the media control information. The specific procedures for applying this payload protection are defined within the release's media plane control specifications.

  • Add media plane capability to support transmission / reception via MBMS in MCData TS 24.582CR0009
  • Adding clause for media plane procedures for pre-established session for MCData TS 24.582CR0010
  • Media plane control in MCData for user plane SDS using MBMS TS 24.582CR0011
  • Adding mcdata id in signalling payload for sender of the data in MCData media plane (Session) communication TS 24.582CR0012
Rel-17 3 changes

In Release 17, the enhancements for the DPKK function were focused on enabling and refining Mission Critical Data (MCData) File Distribution via MBMS. Specifically, the release introduced MCData media plane control for FD using MBMS delivery via the MB2 interface. This was accompanied by adjustments to the handling of MSRP SEND messages received over MBMS, including corrections to the To-Path header and other small corrections within the media plane control procedures.

  • MCData media plane control for FD using MBMS delivery via MB2 TS 24.582CR0025
  • MCData - small corrections in 24.582 clause 6.5 TS 24.582CR0026
  • MCData - adjust the To-Path header of MSRP SEND messages received over MBMS TS 24.582CR0027
Rel-18 2 changes

In Release 18, the DPKK function was updated to accommodate the new capability for 5G Multicast/Broadcast Services (MBS) within the MCData media plane, as introduced by the corresponding Change Request. Furthermore, the release decoupled signaling and media plane functions for MCData IP Connectivity, which required adaptations to the key management and protection procedures for the media plane as specified in the document.

  • Addition of 5G MBS in MCData media plane TS 24.582CR0036
  • Decoupling of signalling and media plane for MCData IP Connectivity TS 24.582CR0037

Explore further

Broader topics and technologies where DPKK plays a role.

Defining Specifications

3GPP specifications that define or reference DPKK, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 24.582 vj00 MCData Media Plane Control Protocols Rel-19