ACTION-7 Use cases

There are three use cases I describe below for ACTION-7. All of them result in the same basic flow of messages between the various components.

Upon video selection, the CDM is engaged and there are three key exchanges:
* The first key exchange determines that authentication is needed.
* The second key exchange provides information to the application about how the authentication should be done.
* The third key exchange provides the required credentials to the key server and retrieves the final content key.

I included a variation of the authentication mechanism where in the second key exchange the app redirects to an authentication web site provided to the CDM by the key server, instead of gathering the credentials directly.

I published the diagrams via Google Docs. Hopefully everyone can access them. I can move them elsewhere as needed.

-------------------
Use case #1 -- Video Search Engine
This is a video search engine site which incorporates a player. The user enters search terms and is provided with a selection of matching videos from possibly unknown sources. These sources may use various key systems. The application has no way of knowing in general what server to authenticate to or which key servers will be contacted prior to playback. The URI to the video is a raw content link or playlist, not a link to a publishers website (if there is such a site).

Version #1
https://docs.google.com/drawings/pub?id=15dnxQHHSTY64YSnMSihfBa9w-oxCVuOsFUBOfBMJDVY&w=960&h=720

Version #2
https://docs.google.com/drawings/pub?id=1Zlk6R8Lz1iI_NHIcMs-2DNBkED2qjLZpYYsQ6ymxVfI&w=960&h=720

-------------------
Use case #2 -- Online Storage Player
This is an online storage site which provides a video playback feature allowing users to upload secured content or just playlists. The user opens up their private storage area and selects a video or playlist from among those they have uploaded. The application has no way of knowing in general what server to authenticate to or which key servers will be contacted prior to playback.

https://docs.google.com/drawings/pub?id=1ybZ1tDbrwO9jX372nSpJuQKnAzdtSTJ5dmVuZLwM4kA&w=960&h=720

-------------------
Use case #3 -- Social Media Player
This is an social networking site which allows for users to share links to secured content and play back the content in a branded player provided by the site. The application has no way of knowing in general what server to authenticate to or which key servers will be contacted prior to playback. The URI to the video is a raw content link or playlist, not a link to a publishers website (if there is such a site).

https://docs.google.com/drawings/pub?id=1H4wHvOxdrhU9aTqQG-2mZIPzZtgmag_GvNMcfXpeBRU&w=960&h=720


Joe Steele
steele@adobe.com<mailto:steele@adobe.com>

Received on Monday, 10 December 2012 02:02:16 UTC