DRM - Asset protection
A “license” means a relatively small data packet that is needed to view/play the content. It contains the key for decrypting the content, accompanied by rules that apply for that content. For example, a license could tell the player to limit playback to a certain time frame or a certain number of views. Using our API, you can configure the restrictions that you want to apply to your content.
See also: DRM Introduction
Axinom DRM is intended as a DRM solution for video content. However, its components - Key Service and License Service - are agnostic to the type of clients and content. Audio streams included as audio tracks together with a video can be protected without any issues. This applies to all DRM technologies that we provide: Widevine, PlayReady, and FairPlay.
In case of pure audio files to which you would like to apply a typical video DRM solution, simulate them to be videos. For example, you can generate a dummy video of the same length as your audio, consisting the standard video settings. Then encode it as if it were a regular video. Note that your player should be built in a way that it would not display the video stream and would only play audio.
For encoding, you can use Axinom Encoding or any other encoding software, e.g. Shaka Packager.
We are required to enforce output protection levels (OPL) when our content is played. Does Axinom DRM support this?
Yes. However, support for output protection differs between DRM technologies (PlayReady, Widevine, FairPlay Streaming). Using Axinom DRM, you can apply simple output protection across all technologies or address each technology separately and use it to its full extent.
Yes, you can protect your live streaming content also. When you are protecting VOD content, you have the possibility to protect your content beforehand. But when you are DRM protecting the live streaming content, you have to create, encode, package, and encrypt the content at the same time while the customer is viewing the video. You can refer to Media Live Setup to get an idea on how to achive it wiith Axinom DRM.
What is the difference between using "begin_date" / "expiration_date and “start_datetime"/ "expiration_datetime" in the Axinom License service message and the entitlement message?
The “Begin_date” and the “expiration_date” is mentioned in the Axinom License service message. So the “Begin_date” and “expiration_date” is specifying the active period of the “Axinom License service message”. If the Message is inactive, License Service will reject the request. The License service message consists some inner messages. Entitlement message is specified inside the License service message.
The “start_datetime” and “expiration_datetime” is mentioned inside the entitlement message, as a property for the license configuration. So “start_datetime” and “expiration_datetime” specifies the active period of the license. If “Axinom License service message” is active, regardless of the license active period, license will get generated. But license can be used only within the specified time period inside the “License configuration”.