MCData Payload Cipher Key

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.

Key Features

• Provides confidentiality for MCData application payloads (user data)
• Derived from the MCData service anchor key (KMCData) as part of a key hierarchy
• Used with standardized encryption algorithms (e.g., AES) in defined modes
• Managed and distributed via secure key management protocols (e.g., via KMF)
• Enables end-to-end application layer security for mission-critical data
• Supports security segregation by separating payload protection from signaling protection

Evolution Across Releases

Defining Specifications