PlayReady Hardware-Secured AV1 Decoding Profile

This article provides an overview of Microsoft PlayReady's implementation profile for hardware-secured AV1 decoding, detailing how premium 4K and HDR video streams are protected within modern silicon architectures. It outlines the core architectural components, cryptographic boundaries, bitstream parsing rules, and Trusted Execution Environment (TEE) specifications required to achieve PlayReady Security Level 3000 (SL3000) compliance using the AV1 codec.

Security Level 3000 (SL3000) Requirement

To process high-value content such as 4K UHD, HDR, and early-window releases encoded in AV1, Microsoft PlayReady mandates Security Level 3000 (SL3000). At this tier, all cryptographic operations, key management, video elementary stream handling, and video decoding must take place inside a hardware-isolated environment. Software-only protections (SL2000) are insufficient for hardware-secured AV1 deployment.

Cryptographic Boundary and the TEE

The implementation profile requires a strict hardware root of trust, typically implemented via a Trusted Execution Environment (TEE) or a dedicated Secure Processor Unit (SPU).

• Key Handling: Content encryption keys (CEKs) are derived and unmasked strictly within the secure boundary. Keys are never exposed to the host operating system or non-secure memory.
• Payload Decryption: The encrypted AV1 bitstream is passed directly into secure memory buffers. Decryption occurs inside the secure enclave using standard cryptographic accelerators supporting AES-128 in either Counter (cenc) or Cipher Block Chaining with 10% pattern protection (cbcs) mode.

AV1 Bitstream Parsing and Sample Format

AV1 structures media into Open Bitstream Units (OBUs). Under PlayReady’s hardware profile:

1. Header Parsing: Unencrypted metadata, such as Sequence Header OBUs and Temporal Delimiter OBUs, may be parsed outside the TEE depending on the platform's media framework, provided that doing so does not leak secure key material or compromise buffer security.
2. Encrypted OBUs: Tile Group OBUs and Frame OBUs containing protected media payloads must be parsed and processed entirely within the secure environment.
3. Subsample Mapping: PlayReady follows ISO/IEC 23001-7 Common Encryption standards. The implementation must accurately process subsample encryption mappings, where clear headers (OBU headers and sizes) alternate with protected video data payloads.

Secure Media Pipeline and Decoding Engine

Once decrypted, the raw AV1 elementary stream must transition directly to the hardware decoder without crossing into unsecured system memory.

• Protected Video Path (PVP): The hardware AV1 decoder must have dedicated Direct Memory Access (DMA) channels to protected memory regions (such as TrustZone-protected DRAM or Carveout memory).
• Decoded Surface Protection: Uncompressed YUV or RGB frames produced by the AV1 hardware decoder must remain inside protected memory. Neither user-mode nor kernel-mode host operating system processes can read these decoded video surfaces.
• Display Output Protection: The display pipeline must enforce hardware-level content protection. If an external display interface is used (such as HDMI or DisplayPort), HDCP 2.2 or higher must be engaged prior to rendering decoded frames.

Silicon and OEM Integration Considerations

For silicon vendors and OEMs implementing this profile:

• Hardware Decoders: The integrated AV1 hardware decoding block must natively interface with the platform's secure memory firewall.
• Firmware Validation: PlayReady Device Porting Kits (PK) must be compiled with hardware DRM configurations enabled, linking OEM-specific TEE drivers that support AV1 sample processing.
• Revocation and Recovery: The hardware profile requires persistent, tamper-proof non-volatile storage for replay detection and revocation status checks to guard against key rollback attacks.