Holly wood studios place mandatory requirements on
streaming service providers that premium content remain
protected at all stages of handling, from content preparation to
playback on an end-user’s device.
Digital rights management (DRM) is a crucial element in
securing content and dictates exactly who can access your
content and how. Nearly all streaming providers are aware of
this, but many are challenged in navigating the fragmented
DRM technology market that requires multi-DRM support,
and unclear about the criteria they should prioritize when
evaluating DRM solutions.
SINGLE INTEGRATION PLATFORMS:
SERVE ALL SCREENS
Your ally in both cutting cost and freeing up resources,
licensing services streamline the process for supporting a
cross-section of the major DRM technologies including Google
Widevine, Microsoft PlayReady, and FairPlay Streaming.
However, any deep evaluation must also look to the
robustness of the license delivery infrastructure. Buffering
and performance lag are anathema to end-users perpetuated
by slow or poor connectivity. In a worst-case scenario,
disruption to vulnerable infrastructure risks license server
failure, causing severe downtime.
MULTI-DRM BACKED BY
MAXIMUM UPTIME INFRASTRUCTURE
Vendor considerations are no longer just a matter of what DRM
systems are supported. As licensing is a central component of any
premium studio content service, it is also important that a DRM
provider never impedes your overall service’s playback operation
by acting as a point of failure, and also minimizes its footprint on
stream start times.
Earlier this year, a server outage affecting users of Amazon
Web Services (AWS) S3 and dependent services in AWS’ US-EAST1
brought widespread disruption and downtime to a large number
of internet services with vulnerable infrastructure. However,
castLabs’ DRMtoday licensing service remained unaffected even
though it utilizes these servers. (A more detailed account on this is
available on our website blog at go2sm.com/castlabsaws.)
How did some online services experience mass downtime and
others remain unaffected? Many, including DRMtoday, employ
failover mechanisms built into the infrastructure as a safeguard
to maintain uptime while a failed server is brought back online.
DRMtoday’s infrastructure acts as a License Delivery Network
(LDN), a configuration similar to how a CDN streams content, that
delivers downtime safeguards. The network consists of a number
of cloud-based license server nodes and potentially a number of
offline nodes, e.g. when using our DRMtoday Onboard service,
which synchronises with the LDN periodically.
Dependable DRM: License
Delivery Network In The Cloud
Representation of the License Delivery Network
inclusive of online and offline nodes