 Hi, today we will talk about digital rights management or DRM in video and whether the video is played back from a mobile device or desktop or smart TV, there are steps and technologies behind that allow for premium content to be played back safely and decrypted. So video is actually encrypted and there is a whole process behind to make sure that the person that is consuming and plays back the video is authorized to do so. So I've created a graph here of the different steps in a DRM system and the first one is actually the users. So the users log in via authentication to get access to a catalog. That's the first step. One step logged in and they are browsing the catalog, they can make a video selection. So they choose a video, which means that a request is created for a content type to be played back then that video selection request, so probably as a content ID is conjunction added to the requesting device ID, which basically is sort of a signature. So more than an identification, it's a long, you don't think of it as a string, think of it as a sequence of bytes that are unique to the requesting device. So we have two pieces for now, the content ID that the user has chosen plus the signature of the requesting device. The next step is that the video is fetched from storage, so like a CDN and the video we divide up here into segments that represent the different quality levels that the video can play back at depending on the user connection and requesting device. So for example, if it's a mobile device, it will have a lower quality because you don't need 4k on a small screen, whereas for example, if it was a tablet, you're going to have a bigger kind of screen size, so your quality will increase also in function of your internet speed. So once the video is fetched from storage, the license of it is checked via the browser component that kind of reads the type of DRM system, there are multiple types, which was used to encrypt this video, and you can encrypt either the segments or the metadata. So once the DRM component in the browser receives the request for the license check to play back a specific video, what it then does is contacts the DRM license server and it says, okay, is this user, which was out here and that has selected a specific video on that device, is it allowed to actually play back that video? So this information gets aggregated together in the DRM license proxy server, which checks the user credentials. It also has a license database, which includes information like the content ID, so the video selection here, device ID, which we can kind of associate to the requesting device, so the client signature, it has key ID, which was brought out from the manifest of the video or what describes all these segments and how they are related together, and you can include the policies and also permissions, so all this information is stored in a license DB, which then the proxy server contacts to actually get that information for the license. So we then check if the users on that device can view the video and this is the job of the proxy server and the license database, usually set up by the service provider, which is different from the content provider. And once the DRM license proxy server has made a decision whether the user is allowed to watch on device that he's requesting to, it then serves back the license to the DRM browser component, which then uses the key from that license to decrypt part of the video and actually play it back. So there are a couple of steps, let's go through them again. The first step is that the user logs in, they are authored, they select a video on a specific device, then the video is fetched from storage, so from the CDN, which is a server close to the users, where the video is saved, it is then sent to the browser, the browser DRM component then asks for a license check, the DRM license proxy server verifies that the user is authorized, it also checks with a license DB, which contains different information like the key ID and the content ID, and all of these together tell whether the user is allowed to watch a specific piece of content on a device. If the user has that permission, then the license server sends back to the DRM browser component the key to decrypt the content and play back. So hopefully that was kind of a general introduction. Thank you.