In order to apply PallyCon Multi-DRM service, you must first perform packaging processes to encrypt your contents. The below documents describe a variety of content packaging methods, including PallyCon Packager, AWS Elemental Media Services, Wowza Streaming Engine, and PallyCon Packaging Services.
subgraph Content Service Site
A[Source Content] --> B(Encoder)
B -->|Encoded Content| C(PallyCon Packager
DASH/HLS Stream| D(CDN
subgraph PallyCon Service
Info| E(Key Management
E -->|Encryption Key| C
Packaging Callback Guide
PallyCon cloud server requests customer’s service site for the identity value of the content during the packaging process for content encryption. The service site can set the content ID through the callback web page.
CLI Packager Guide
PallyCon CLI Packager is a content packager which supports command line interface of Windows and Linux. This document explains how to use the PallyCon CLI Packager.
CPIX API Guide
Describes how to use CPIX API that can easily integrate PallyCon Multi-DRM with encoder / transcoder solutions that support CPIX-based key exchange.
AWS Elemental Integration
PallyCon service supports the content packaging integration using the SPEKE API provided by AWS Elemental Media Service. This document explains how to use the API to work with AWS Elemental Media Services.
Wowza Integration Guide
PallyCon Wowza SDK is a plugin module of Wowza Streaming Engine that supports streaming service with DASH (CENC) and HLS (FPS or NCG) content by packaging original MP4 video or live stream in real time. This document explains how to use the Wowza plug-in provided by the SDK.
Bitmovin Encoder Integration Guide
When using Bitmovin encoding service, multi DRM packaging is possible through CPIX or SPEKE API integration with PallyCon KMS(Key Management Server). This document explains how to create DASH/HLS content with multi-DRM using examples written based on the Bitmovin Java SDK.