AAXS DRM External CEK Workflow

This workflow is a departure from most existing DRM systems, as it does not require the use of any central repository or Content Key Management System (CKMS). However, for customers that desire AAXS to work with their existing CKMS, AAXS provides a feature called “External CEK”, in which the CEK is supplied externally at packaging and license issuance time.

  1. (Package) The AAXS Java SDK is provided with a CEK and a CEK ID.
  2. (Package) The CEK is used to encrypt content.
  3. (Package) The CEK ID is inserted into the content’s DRM metadata.
  4. The device attempts to play content by requesting a license from the AAXS server.
  5. (Licensing) The AAXS server extracts the CEK ID from the content metadata.
  6. The AAXS server retrieves the CEK from the CKMS.
  7. (Licensing) The AAXS server issues to the device a license that contains the CEK.

On this page