Description
The MCData Payload Cipher Key (DPCK) is a security key defined within the 3GPP architecture for Mission Critical Services (MCS). It is generated and managed as part of the key hierarchy established during the authentication and key agreement procedures between the User Equipment (UE) and the network. The DPCK is specifically derived for use with MCData applications to provide confidentiality protection for the payload (user data) of MCData messages, such as those used in file transfer, text messaging, or data streaming within public safety operations.
Operationally, the DPCK is used by the cryptographic functions in the UE and the MCData application server. When an MCData user sends a secured message, the application layer uses the DPCK (along with a specified encryption algorithm) to encrypt the message payload before transmission. The corresponding recipient's UE, which possesses the same DPCK (having been distributed via secure key management protocols), uses it to decrypt the payload upon receipt. The key itself is not transmitted with the message. The specific encryption algorithms (e.g., based on AES) are defined in the 3GPP security specifications.
The DPCK exists within a broader key hierarchy. It is typically derived from a longer-term anchor key, such as the KMCData, which is itself established from the primary authentication keys. This derivation uses standardized Key Derivation Functions (KDFs). The lifecycle of the DPCK—including its generation, distribution, usage, and deletion—is managed by the security functions within the MCData system, often involving the Key Management Function (KMF) or analogous entities. The separation of the payload cipher key (DPCK) from signaling protection keys is a principle of security segregation, limiting the impact of a potential key compromise.
Purpose & Motivation
DPCK was introduced with 3GPP Mission Critical Data services in Release 14 to address the stringent security requirements of public safety and critical communications. Traditional commercial cellular data security (e.g., in EPS) primarily protects the user plane between the UE and the network with keys like CK (Ciphering Key). However, MC services require end-to-end application layer security for group communications, ensuring confidentiality even within the core network and application server domain.
Its creation was motivated by the need for a dedicated, service-specific cryptographic key for MCData payload confidentiality. This approach provides greater flexibility and security compared to reusing existing access stratum keys. It allows independent key management for the MCData application, enabling features like forward secrecy (where a compromised long-term key doesn't compromise past communications) and the ability to change the payload encryption key without re-authenticating the UE to the access network. DPCK enables the secure exchange of sensitive operational data (e.g., maps, building plans, patient information) among first responders, which is a fundamental requirement for modern mission-critical operations.
What changed in its specifications
The latest release-to-release comparison of specifications that define DPCK. Each summary describes the whole specification, not only this term.
Rel-17 added MSRP group FD over MBMS procedures and GRE-in-UDP media transport with SDP negotiation for MCData IP connectivity.
Full comparison in TS 24.582 →Rel-19 adds recording admin and replay access-token claims to TS 33.180 and removes the MC user event audit and service media collection text. It also adds Annex B recommendations on client registration, authentication request handling, public key distribution, and Issuer claim verification of the access token.
Full comparison in TS 33.180 →Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Initially defined in Release 14 as part of the foundational Mission Critical Data specifications. It established the DPCK within the MCData security architecture, defining its derivation from KMCData and its purpose for encrypting MCData message payloads. This release laid the groundwork for secure data communication for public safety over LTE.
Defining Specifications
3GPP specifications that define or reference DPCK, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 24.582 vj00 | MCData Media Plane Control Protocols | Rel-19 read |
| TS 33.180 vk10 | Security of the Mission Critical Service (MCX) | Rel-20 read |