Method, manufacture, and apparatus for configuring multiple content protection systems

Patent metadata

Field	Value
Publication number	US-9785759-B1
Application number	US-201213532738-A
Country	US
Kind code	B1
Filing date	Jun 25, 2012
Priority date	Dec 12, 2011
Publication date	Oct 10, 2017
Grant date	Oct 10, 2017

Abstract

A method, apparatus, and manufacture for configuring multiple content protection systems is provided. A client media player is employed to determine whether media content is protected. The client media player includes an application, and further includes a media engine that is a distinct program from the application. At least one type of content protection system supported by the media engine is determined. The application is employed to get a key and/or a license for the protected media content in accordance with the determined type of content protection system. The application is employed to instruct the media engine to play the media content. The key and/or the license for the determined type of content protection system is sent from the application to the media engine.

First claim

What is claimed is:

1. A method, comprising:
employing a client media player to determine whether media content is protected, wherein the client media player includes an application, and further includes a media engine that is a distinct program from the application;
determining at least one type of content protection system supported by the media engine by employing the application to poll the media engine to determine at least one type of content protection system supported by the media engine;
employing the application to acquire a key and/or a license for the protected media content in accordance with the determined type of content protection system;
employing the application to instruct the media engine to play the media content; and
sending the key and/or the license from the application to the media engine.

2. The method of claim 1 , wherein the application is configured to be capable of employing a plurality of different types of content protection systems, and to employ the determined at least one type of content protection system supported by the media engine to acquire the key and/or license via a framework; and wherein the application employs the framework to acquire the key and/or license regardless of which of the content protection systems is used to acquire the key and/or license.

3. The method of claim 1 , wherein
the application includes an application programming interface (API) for acquiring the key and/or the license, wherein the API is generic to the particular content protection system employed, and wherein employing the application to acquire the key and/or the license is accomplished using the API.

4. The method of claim 1 , wherein employing the application to get the key and/or the license for the protected media content in accordance with the determined type of content protection system includes, depending on the determined type of content protection system, at least one of: acquiring the key and/or the license from a server in accordance with the determined type of content protection system, retrieving the key and/or the license from the application in accordance with the determined type of content protection system, retrieving the key and/or license locally in accordance with the determined type of content protection system, or acquiring the key and/or the license from a local network in accordance with the determined type of content protection system.

5. The method of claim 1 , wherein employing the application to get the key and/or the license for the protected media content includes acquiring the key and/or the license from a server via a digital rights management system, wherein determining at least one type of content protection system supported by the media engine includes employing at least one digital rights management system supported by the media engine, and wherein employing the application to acquire a key and/or a license for the protected media content in accordance with the determined type of content protection system includes employing the application to acquire a key and/or a license for the protected media content in accordance with the determined type of digital rights management system.

6. The method of claim 1 , wherein determining whether the media content is protected is accomplished by the application, and wherein the application is employed to instruct the media engine to the play the media content after the application is employed to get the key and/or the license for the protected media content.

7. The method of claim 1 , wherein determining whether the media content is protected is accomplished by the media engine after the media engine is instructed to play the media content.

8. The method of claim 1 , wherein the application is a web application running in a client browser, wherein the web application includes HyperText Markup Language (HTML) and/or a scripting language, and wherein the media engine is a media stack that is part of the client browser.

9. The method of claim 8 , wherein the media content is accessed via an HTML media element, and wherein employing the application to instruct the media engine to play the media content includes:
parsing the web application;
if the web application includes an auto play attribute for the HTML media element employing the client browser to cause the media stack to play the media content;
else
instructing the media engine to play the media content in a time and manner that is in accordance with web application.

10. The method of claim 1 , wherein employing the application to poll the media engine is accomplished by polling the media engine, one content protection system at a time, as to whether the polled content protection system is supported by the media engine, and ceasing the polling if the polled content protection system is supported by the media engine.

11. The method of claim 10 , wherein polling the media engine is accomplished in a preference order of content protection systems.

12. A client device, comprising:
a memory component for storing data; and
a processing component that is configured to execute data that enables actions, including:
employing a client media player to determine whether media content is protected, wherein the client media player includes an application, and further includes a media engine that is a distinct program from the application;
determining at least one type of content protection system supported by the media engine by employing the application to poll the media engine to determine at least one type of content protection system supported by the media engine;
employing the application to acquire a key and/or a license for the protected media content in accordance with the determined type of content protection system;
employing the application to instruct the media engine to play the media content; and
sending the key and/or the license from the application to the media engine.

13. The client device of claim 12 , wherein the processing unit is further configured to employ the application to get the key and/or the license for the protected media content in accordance with the determined type of content protection system such that getting the key and/or license for the protected media content includes at least one of: acquiring the key and/or the license from a server in accordance with the determined type of content protection system, retrieving the key and/or the license from the application in accordance with the determined type of content protection system, retrieving the key and/or license locally in accordance with the determined type of content protection system, or acquiring the key and/or the license from a local network in accordance with the determined type of content protection system.

14. The client device of claim 12 , wherein the application is configured to be capable of employing a plurality of different types of content protection systems, and to employ the determined at least one type of content protection system supported by the media engine to acquire the key and/or license via a framework; and wherein the application is configured to employ the framework to acquire the key and/or license regardless of which of the content protection systems is used to acquire the key and/or license.

15. The client device of claim 12 , wherein
the application includes an application programming interface (API) for acquiring the key and/or the license, wherein the API is generic to the particular content protection system employed, and wherein the employing the application to acquire the key and/or the license is accomplished using the API.

16. A

Assignees

• Dorwin David Kimbal
• Scherkus Andrew
• Kaiser Christian
• Lacey Stephen John
• Lacey Nabila
• Google Inc

Inventors

• Dorwin David Kimbal
• Scherkus Andrew
• Kaiser Christian
• Lacey Stephen John

Classifications

• H04L9/0861

  Generation of secret information including derivation or calculation of cryptographic keys or passwords · CPC title

• H04N21/25825

  involving client display capabilities, e.g. screen resolution of a mobile phone (optimising the visualisation of content during browsing in the Internet G06F16/9577; processing of terminal status or physical abilities in wireless networks H04W8/22; authentication in wireless network security H04W12/06) · CPC title

• G06F21/602

  Providing cryptographic facilities or services · CPC title

• H04L9/32

  including means for verifying the identity or authority of a user of the system {or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials} · CPC title

• G06F21/60

  Protecting data · CPC title