Buyers' Guide to DRM 2017
Now that you know the acronyms and how the plumbing works, let’s see how EME has fundamentally changed the number of DRMs that most streaming publishers will need to support.
Working With EME
When DRM is tied to a plug-in, the DRM works on any browser that supports the plug-in. So if you protected your content with Adobe Access via the Flash Player, Adobe Access worked within any browser that supported Flash.
In contrast, with EME, each platform decides which DRM to support. The major browsers all support different DRM technologies. Not surprisingly, Microsoft supports its PlayReady technology in Internet Explorer and Edge, Google supports Widevine in Chrome, and Apple supports FairPlay in Safari. Firefox supports both Adobe Access and Widevine. As a practical matter, this means that technologies like DivX, VCAS, or Marlin, which aren’t integrated into any browser, are unavailable for browser-based distribution without a separately downloaded player, which are increasingly anathema in an HTML5-centric world.
Moving from desktops to mobile players, when securely distributing to the mobile devices, you have two options: browser-based playback and playback within an app. In terms of browser-based playback, the vendors remain true to form: Apple supports FairPlay in iOS 6+, Google supports Widevine Classic in Android 3+ and Widevine Modular in Android 4.3+, while Microsoft supports PlayReady on the Windows Phone.
Of course, apps provide much more freedom of choice. For example, Figure 5 shows the App compatibility matrix provided by BuyDRM, which enables PlayReady on all mobile devices, with Marlin, the open-standard DRM solution, on iOS and Android devices. Basically, browser-based playback enables one DRM per platform, while an app usually lets you select from multiple DRMs.
Fig 5: Using an app broadens your DRM choices on mobile platforms. (Image courtesy of BuyDRM)
In OTT, PlayReady dominates, with support on most platforms except Apple TV, which of course only supports FairPlay. Widevine is also available on Google devices like Chromecast and Android TV, but not Amazon Fire TV, which uses PlayReady. Most smart TVs support PlayReady, and a smattering also support Widevine and Marlin. Both Xbox and PlayStation support PlayReady, and the Sony devices also support Marlin.
Choosing a DRM and Licensing Partner
By this point, you probably understand that to choose a DRM technology, first you choose the playback platform, and then you see which DRM or DRMs it supports. To support all the major browsers on computers, you’ll need to support multiple DRMs. In addition, since EME doesn’t yet support 100 percent of target viewers, any DRM strategy based around EME will have to enable fallback to a plug-in-based DRM, usually either Adobe Access via Flash or PlayReady via Silverlight. Complicating this fallback strategy is Adobe’s decision to make Access primarily available only within its own Primetime platform, so if you’re not a Primetime user, you may not be able to offer fallback to Flash.
On mobile platforms, you have to decide whether to produce an app or to distribute via the browser, with the former offering much greater flexibility regarding DRM choice. Once you move into OTT and Smart TVs, it’s a device-by-device determination: Identify the device that you want to serve, and then identify the supported DRM or DRMs.
DRM Licensing Options
After choosing the target platforms and identifying the DRM technologies you must support, you should choose a licensing provider, which involves multiple factors, including whether to go direct with those vendors that support (or require it), or to use a licensing partner. Obviously, the DRMs supported by a potential partner is a major consideration, and a partial list of service providers is shown in Table 2. Note that this is a fast-moving market, so check with the service provider before making any decisions.
As an aside, though Netflix has licensed FairPlay from Apple for the playback of DASH-encoded files using EME and MSE, only the content owner appears to have that privilege.
Online video platforms (OVPs) like Brightcove, Kaltura, and Ooyala offer various DRM technologies to enable native EME support in current browsers, fallback to Silverlight or Flash for older browsers, and software development kits (SDKs) to assist with delivery to mobile and other devices.
Similarly, in 2016, Adobe introduced the Adobe Primetime HTH TVSDK, which uses the native EME-driven DRM of each browser. Adobe also announced a partnership with ExpressPlay to provide a cloud service for issuing licenses in all required DRMs, which became available in late 2016. Customers may use the Adobe cloud for DRM licensing or use a limited set of license administrators in conjunction with the Adobe Primetime TVSDK on the client. Essentially, if you’re distributing your content through an OVP or similar platform, that service or platform should be able to provide either the necessary DRM or an easy path to integrating third-party service providers like those shown in Table 2.
Again, as mentioned, Adobe has stated that it will no longer support third-party DRM resellers, which could mean some changes to Table 2 regarding Adobe Access in 2017 or beyond.
Packaging Your Content With DRM
For developers managing their own distribution and player development, the integration of DRM into your encoding and packaging workflow is another major factor, and different services take different approaches. For example, castLabs, owner of DRMtoday, offers a cloud service that can input over 100 audio/video codecs and output DRM-protected packaging for DASH, Smooth Streaming, and HLS, complete with closed caption support.
If you’re encoding in a third-party cloud service, check which DRM providers it directly supports. For example, Encoding.com supplies Widevine licensing directly but integrates with BuyDRM to manage PlayReady licensing. BuyDRM also has deployments in Amazon Web Services, Akamai, Brightcove (Zencoder), Encoding.com, and Google Cloud. If you’re encoding your own content, check if the vendor can supply encoding/ packaging capabilities for your chosen platform, whether Windows, Linux, or the cloud.
Check whether your service providers or partners support dynamic encryption, as opposed to static, which can simplify your workflows and save storage costs. For example, the Wowza Streaming Engine can dynamically encrypt and package live and VOD content for delivery via Apple HLS, Microsoft’s Smooth Streaming, and DASH with PlayReady and Verimatrix VCAS DRMs using three third-party DRM service providers: BuyDRM, EZDRM, and Verimatrix (Figure 6).
Fig 6: The DRM capabilities of the Wowza Streaming Engine add dynamic, multiple format encryption and packaging with support from multiple vendors.
With dynamic encryption, which is available from other vendors, including Microsoft Azure, only a single copy of the unencrypted content needs to reside on the server. In contrast, with the static packaging model, you would have to create and store the final encrypted packages for all technologies for all content, multiplying your storage costs. The potential downside of dynamic packaging is a slight playback latency, which will vary by technology provider.
Pay TV-Oriented DRM Services
If you’re a pay TV service provider also distributing to streaming and other clients, there are several other alternatives you should consider. For example, Verimatrix sells DRM and other products into the broadcast and pay TV markets. Since many of its customers are expanding into streaming delivery, Verimatrix created the MultiRights OTT service, which manages its core VCAS DRM for delivery of services to iOS, Android, legacy desktop browsers, and STBs. It adds Widevine for Chrome and other proprietary environments, and PlayReady for integrated license management for Smooth Streaming and DASH service delivery to closed Xbox and Windows environments.
Nagra, developer of the AnyCast Security Services Platform for Digital TV service providers, takes a different approach. Rather than use third-party DRM platforms to support computers, mobile devices, and other CE platforms, Nagra has extended its own DRM technology to these platforms via secure players and other technologies.
Similarly, Cisco VideoGuard Everywhere (VGE) allows pay TV services to securely extend playback beyond the STB to computers, mobile devices, and gaming consoles. In addition to allowing access to the DRM technologies, with VGE Cisco assumes responsibility for integrating all components of the video service solution. This includes having different DRM systems, monitoring the integrity of the service after deployment, and responding to identified service breaches.
Business Models and Pricing
When choosing DRMs and providers, be sure to check that the combination supports both your target platforms and planned business models. If your model is streaming to online clients, that should be fairly simple, as virtually all DRMs and DRM providers support this. On the other hand, if you’ll be implementing a subscription model, or the ability to download and play the content offline, or download it on your computer and then sideload it to another device, you could have issues.
Beyond business models, you should price both startup and ongoing costs, particularly those involved with supporting additional platforms, which varies significantly from provider to provider. For example, many service providers in Table 2 offer SDKs to create Android and iOS apps, but some are available at a nominal fee, while others are quite expensive. When comparing prices, you should know all platforms that you intend to support, and how you intend to support them (app or browser). Then you should price out each module or service required to get that done, plus minimum monthly fees and perlicense costs. Remember to factor in the potential storage costs as well.
The Player Side
As a final note, if you’re using an off-the-shelf (OTS) player like JW Player, understand that it may not currently support all DRMs. As an example, the only DRMs JW Player supports for DASH playback are Widevine and PlayReady. So check with your OTS player developer to determine which DRMs it supports.
In addition, before choosing a DRM provider, ask if your player developer has relationships with any providers that will simplify the integration. For example, JW Player has partnerships with Vualto and BuyDRM for each provider’s multi-DRM protocol. Similarly, if you use castLabs’ PRESTOplay for Browsers (formerly the DASH Everywhere player), sister company DRMtoday is a natural DRM provider. Finally, if you’ll create apps for mobile platforms, check which of your candidate suppliers offer SDKs to speed their development.
Author’s note: The author wishes to thank Christopher Levy, CEO of BuyDRM, for technical assistance with this article.
This article appears in the March 2017 issue of Streaming Media magazine.
Related Articles
Piracy will always be a problem, but new advances in DRM and watermarking are making headway in the never-ending global battle.
28 Sep 2018
While publishers wait for a single content encryption system that works across all browsers, standards bodies debate the future of EME. Here's what rights management will look like in a post-plugin world.
25 Oct 2017
The move away from plugins like Flash and Silverlight has made video delivery easier, but it's also made DRM more complicated. Here's what DRM looks like today, along with a discussion of the leading DRM technologies and DRM service providers
12 Jul 2016
A simple guide through the complex landscape of multiple DRM technologies. Learn what DRM is, and how to choose and deploy the best solution for each platform.
25 Mar 2016
Companies and Suppliers Mentioned