Handling Protected Content in the Service Provider
.gif) |
This is preliminary documentation and subject to change.
This topic documents a feature of the Windows Media Device Manager SDK. We recommend that you migrate your application to use the Windows Portable Devices API. For more information, see the Windows Portable Devices SDK.
You can build a service provider that can send DRM-protected content to a device built on Portable Device DRM (PDDRM), but you cannot build a service provider that can send DRM-protected content to devices built on Windows Media DRM 10 for Portable Devices. These devices use MTP, and you cannot build your own MTP service provider.
The only extra step that a service provider must take to send DRM material to a PDDRM device is to get a Microsoft-issued certificate/key pair. See Tools for Development to learn where to get this certificate/key. The licenses issued to these devices will be simplified licenses that only support simple playback of purchased content; they will not support time-expiring licenses. This license will be created for you by the secure content provider (provided by Microsoft for WMA/WMV files) and stored in the header of the file sent to the service provider. You will not have to take any special steps for protected files.
After sending the protected file, Windows Media Device Manager will call the service provider to request a special license storage file from the device. Windows Media Device Manager will add a copy of the new license to this file, and return it to the service provider to send back to the device. However, even if the service provider fails to find or return this file, the device should still be able to play the protected file by using the license copy in the file header.
See Also