Introduction to the DRM world
It is common for some content providers to require content to be distributed to users protected by DRM encryption. Nowadays, it is possible to reproduce content with DRM natively from some browsers (HTML5) and native apps.

To give DRM support to most users it is necessary to apply a multi-DRM strategy since the DRM support of browsers and device manufacturers is very varied. The DRM available on the platform, their compatibility and distribution strategy are specified below:

· Apple Fairplay : As its name says, this DRM is owned by Apple and its devices / browser are only compatible with this DRM. Apple mobile devices like iPhone and iPad can only decode / play DRM content from iOS version 11.2 or higher. Before that version, it is only possible to play through native applications, that is, content consumed through the device's browser cannot be played in iOS versions less than 11.2.
In the case of Mac computer users using Chrome, they are compatible with Widevine DRM as well.

· Google Widevine: A few years ago Google acquired the Widevine company in charge of developing DRM technology and was in charge of giving it compatibility in most devices / OS / browser administered by the company. Google Widevine is the most supported DRM starting with the popular Chrome on Desktop and Android 5+.

· Microsoft Playready: In the case of devices or browsers owned by Microsoft, they are compatible with the proprietary DRM called Playready. This is specified in the case of Internet Explorer 11+ and Edge browsers.

When it comes to distributing streaming encrypted with DRM to different devices / browsers, it is not only necessary to encrypt with different DRM but also to distribute with different streaming protocols, the combination according to devices / browser is detailed below:

· iOS = HLS + Apple Fairplay : Consumption from Safari or another browser from versions lower than iOS 11.2 is not supported.

· OSX + Safari = HLS + Fairplay : In the case of Mac computers, it is possible to consume content encrypted with DRM in the browser, in case of Safari HLS and DRM Fairplay must be distributed.

· OSX + Chrome = MPEG-Dash + Google Widevine : Unlike mobile phones, on Mac computers it is possible to consume DRM with Chrome's specifications, that is, Streaming in MPEG-Dash format + Google Widevine DRM encryption.

· Windows + Edge or IE11 or higher = MPEG-Dash + Microsft Playready : In the case of Windows operating systems and Microsoft browsers, the distribution strategy varies to the combination of MPEG-Dash + Playready, it is supported by Microsoft.

· Windows + Chrome = MPEG-Dash + Google Widevine : If the user navigates with Chrome on Windows, streaming content must be distributed with MPEG-Dash + Google Widevine.

· Android 5 or higher = MPEG-Dash + Google Widevine : All devices with Android OS (from Google) are compatible with DRM Widevine and MPEG-Dash distribution.

DRM on Platform

Mediastream Platform supports multiple DRM content with content delivery in HLS and MPEG-Dash for VOD content . The Mediastream Player evaluates which device, operating system and browser the user is in and then send the content with the correct streaming format and DRM. In case the user navigates from an unsupported combination, the Player will show an error message to the user. You can customize the error message.

To be able to issue Apple Fairplay DRM, an authority certificate issued by Apple is required. This certificate is issued to distributors who demonstrate authorization or ownership to distribute the content. It is necessary to have an Apple development account and request the "Deployment Package". More info in the following link .

Configuration by Category

To enable DRM in your Platform account it is necessary to configure the DRM module and upload the certificate issued by Apple. DRM can then be enabled by Content Category dynamically and disabled when not needed.
There are 3 options when enabling DRM:
· Enable for all devices: The content will be sent encrypted to all devices, in case the device does not support DRM, a message will be displayed to the user.

· Enable for compatible devices only: The content will be sent with DRM only to compatible devices. Unsupported devices will be sent DRM-free content. Example: iPhone with iOS lower than 11.2

· Disable: Content with DRM is not sent.

SDK

In case you want to use the Mediastream Platform SDK for your native applications, it is also possible to use DRM automatically, that is, depending on the SDK it is the combination of DRM that will be used.

conclusion

Distributing DRM is complex and not agile to implement due to the multiple combinations of devices, operating systems and browsers on the market. Mediastream recommends avoiding DRM implementation and only implementing when strictly necessary. There are content security options such as Geofencing, Access Token, among others. That, although they are not as effective as DRM, the user experience is noticeably better.

We hope this documentation is useful to you. Please do not hesitate to contact us in case of doubts, suggestions or complaints.

Atte.

Team Mediastream.

Did this answer your question?