Description
Content Protection Information Exchange (CPIX) is a specification introduced in 3GPP Release 19 that defines a standardized format and protocol for exchanging content protection information between different entities in a media delivery ecosystem. It is specified in TS 26.512 (5G Media Streaming) and TS 26.804 (Study on Media Handling for Multisource Media). CPIX addresses the need for interoperable key exchange and digital rights management (DRM) signaling when media content is protected and delivered across multiple systems, such as content preparation, packaging, and delivery networks. It enables secure communication of encryption keys, license information, and protection policies between content owners, service providers, and client devices.
Architecturally, CPIX operates at the intersection of media security and media delivery. It defines an XML-based schema for content protection information, which includes elements such as encryption keys, key identifiers (KIDs), initialization vectors (IVs), and DRM-specific metadata. This information is typically exchanged between a key server (e.g., a DRM license server) and a content packager or between a packager and a delivery network. CPIX provides a common language for these exchanges, ensuring that different DRM systems and media workflows can interoperate without proprietary adaptations. It supports both live and on-demand content, and can handle multiple DRM systems simultaneously, which is essential for multi-DRM environments where a single piece of content must be playable on devices with different DRM capabilities.
The specification defines a set of messages and protocols for requesting and delivering content protection information. For example, a content packager may request encryption keys from a key server using a CPIX request message, and the key server responds with a CPIX response containing the keys and associated metadata. These messages are typically transported over HTTP/TLS, ensuring confidentiality and integrity. CPIX also supports key rotation and updates, allowing keys to be changed periodically without interrupting playback, which is important for live streaming and long-duration content. The format is extensible, allowing additional DRM-specific information to be included as needed.
CPIX is designed to be DRM-agnostic, meaning it can carry information for various DRM systems such as Widevine, PlayReady, and FairPlay. This is achieved through a flexible schema that allows DRM-specific data to be embedded within the CPIX document. By providing a standardized exchange format, CPIX reduces the complexity of integrating multiple DRM systems into a single media workflow. It also enhances security by enabling consistent key management practices across different components of the media delivery chain.
In the 3GPP context, CPIX complements other media security specifications, such as those for 5G Media Streaming and mission-critical services. It ensures that content protection information can be exchanged reliably and securely, which is a prerequisite for premium content delivery over 5G networks. As media consumption increasingly shifts to mobile and immersive formats, CPIX plays a crucial role in enabling secure, interoperable, and scalable content protection.
Purpose & Motivation
CPIX was created to solve the problem of interoperability in content protection information exchange across different media systems and DRM technologies. Before Rel-19, there was no standardized way to exchange encryption keys and protection metadata between content packagers, key servers, and delivery networks. Each DRM vendor and media workflow used proprietary formats, leading to integration challenges, increased costs, and potential security gaps. As 5G media services proliferated, the need for a common, secure, and extensible format became urgent.
The specification addresses several key issues. First, it provides a unified schema for content protection information, enabling different systems to understand and process the data without custom adaptations. Second, it supports multiple DRM systems, allowing a single content asset to be protected for various client devices. Third, it defines secure transport mechanisms, ensuring that sensitive key material is exchanged confidentially. Fourth, it supports key rotation and updates, which are essential for live and long-duration content. Finally, it is extensible, allowing future DRM features to be incorporated without breaking existing implementations.
Historically, content protection has been a fragmented area, with different industries and regions adopting different DRM solutions. 3GPP's introduction of CPIX in Rel-19 represents a significant step toward harmonization, leveraging the organization's expertise in mobile media delivery. By standardizing the exchange of content protection information, CPIX reduces friction in the media supply chain, enhances security, and enables new business models for premium content over 5G networks.
What changed in its specifications
The latest release-to-release comparison of specifications that define CPIX. Each summary describes the whole specification, not only this term.
Service chaining, multiple service locations, downlink and uplink streaming procedures, metrics, and CMCD reporting.
Full comparison in TS 26.512 →Rel-19 adds CMCD reporting, multi-source media delivery, content steering, QoS enhancements, and QUIC-based streaming.
Full comparison in TS 26.804 →Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference CPIX, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 26.512 vj30 | 5G Media Streaming Protocols and APIs | Rel-19 read |
| TS 26.804 vk10 | 5G Media Delivery Architecture Extensions | Rel-20 read |