Introduction into HTML5 Encrypted media extension.

1. Video in HTML 5
How to deliver protected content with Encrypted Media Extensions
@DorinManoli

2. Ericsson Media First
• MediaFirst is a E2E cloud-based IPTV platform
• Bringing together Pay TV and OTT
• Connected and integrated experience across all screens
• Smart content suggestion. Multiple users in the same
household can receive tailored recommendations and
content feeds
• Unified content search

3. Embedding video in a web page.
• Early days of the internet there were no native support for video content.
• Video could be played by installing Plug-ins (Active X)
• Windows Media Player
• QuickTime
• Flash
• Silverlight
• <embed src=“movie.swf " >
• <object data="movie.swf" type="application/x-shockwave-flash"></object>
• It comes with a “price”
• Numerous security flaws

4. Protecting our content
Digital rights management (DRM)

5. HTML 5 <video> tag
• HTML 5 introduces built-in support for playing video.
• <video> tag should be natively supported by any browser
• Should eliminate security threats from 3rd party plugins
• HTML5 does not specify what should be the video coding format.
• Patents (unknown patents) concern raised by browser vendors.
• Ogg and Vorbis from Theora
• WebM from Google.
• Definition of the ideal format
• Good compression, low decode processor use, good image quality
• Royalty free
• A hardware decoder should exist

6. <video> in action
<video src="http://v2v.cc/~j/theora_testsuite/320x240.ogg" controls>
Your browser does not support the <code>video</code> element.
</video>
<video controls>
<source src="foo.ogg" type="video/ogg">
<source src="foo.mp4" type="video/mp4">
Your browser does not support the <code>video</code> element.
</video>
More examples here:
https://developer.mozilla.org/en-US/docs/Web/Guide/HTML/Using_HTML5_audio_and_video

7. HTML 5 and Digital rights management
• How to distribute copyrighted protected content in HTML 5?
• Encrypted Media Extensions (EME) has been defined.
• Keys System – content protection mechanism.
• Content Decryption Module (CDM) – A client side mechanism that
enables the playback of encrypted media.
• License server – Service that interacts with CDM to provide keys to
decrypt media.
• Packaging service – Encodes and encrypts media for distribution.
• EME today
• Currently implemented by all major browsers. (IE, Chrome, Firefox and
Safari)
• It enables adaptive bitrate streaming.
• Must implement Clear Key : Browser interoperability.

8. HTML 5 and Digital rights management
how does it work?
• More : http://w3c.github.io/encrypted-media/#examples

9. Related technologies
• Media Source Extension (MSE)
• This specification extends HTMLMediaElement to allow JavaScript to generate
media streams for playback. Allowing JavaScript to generate streams facilitates a
variety of use cases like adaptive streaming and time shifting live streams.
• Dynamic Adaptive Streaming
• MPEG-DASH
• HLS

10. Q & A
@DorinManoli