Multi-DRM Concepts and Terms
PallyCon Multi DRM service is a cloud-based SaaS (Solution as a Service) which consists of packaging solutions that apply DRM to contents, DRM license issuance service, and client solutions for DRM contents playback.
graph LR; subgraph Content Service A[Source Content] --> B(Encoder) B -->|Encoded Content| C(DRM Packager) C -->|Encrypted<br>DASH/HLS Stream| D(CDN<br>Storage) end subgraph PallyCon Service C -->|Packaging<br>Info| E(PallyCon Multi DRM<br>License Server) E --> |Encryption Key| C end subgraph End User D --> |Encrypted<br>DASH/HLS Stream| F(Client<br>Player) E --> |DRM License| F end
This document describes various concepts and terminology related to PallyCon Multi DRM service.
It is a cloud-based content security service operated by INKA Entworks. It consists of PallyCon Multi DRM service to prevent unauthorized use of content, and PallyCon forensic watermarking service to track the source of illegal distribution of the content.
It means the content service site of PallyCon’s customer. Multi-DRM and/or forensic watermarking services provided by PallyCon are applied to the service sites.
A unique ID for the customer service site (content service) to which the PallyCon service is applied. It is created automatically when you signup to PallyCon service or add site, and it is used to identify the target in all integration processes such as content packaging, DRM licensing, and watermarking service.
It is an AES256 key used to encrypt data in various processes of PallyCon service integration. When a site ID is created, a unique key for the site is automatically generated.
This key is used for additional security and control in the process of using content packagers or generating license tokens. Similar to site key, access key is created together with site ID.
All date / time information processed by the PallyCon service (for example, the date of DRM license issue or packaging operation) is based on GMT (Greenwich Mean Time). In PallyCon console site, date / time information can be converted into customer’s time zone by using ‘Timezone’ setting when displaying various data. Even if the setting is changed, the actual date / time data recorded in the database will not be changed, and the time data input of various integration APIs must be based on GMT regardless of the time zone setting of the console.
DRM (Digital Rights Management)
It is a technology that restricts the illegal use of various digital contents and controls the use of the contents of the authorized users according to the intention of the copyright owner. It consists of encryption technology for content protection and license management technology for usage rights control.
It means application of multiple DRM technologies for each client platform to support DRM in various PC, mobile and OTT client environments. Please refer to Supported Environments page for DRM and streaming protocol support information according to client environment.
The process of applying DRM by encrypting the original contents. There are pre-packaging method that serves pre-packaged contents to users and real-time packaging method which processes packaging at the time of contents playback.
For a detailed description of DRM packaging, see the Content Packaging Guide.
In order for the client to play DRM-applied content, a license must be obtained from the DRM server. A DRM license consists of a cryptographic key used to decrypt content and usage control information (such as duration and supported environment). PallyCon supports token and proxy method according to the way of checking user’s rights during license issuance process.
When a client plays content, the service site generates a license token according to the specification and delivers it to the client. The client sends the token to the PallyCon cloud server to receive the DRM license.
For more information about license token, please refer to the Guide.
An authentication token used for content packaging key integration via CPIX API. A unique token is generated for each service site, and this token should be added to the API-specific key request URL such as PallyCon CPIX API or SPEKE API. Please refer to the Developer Guide for details.