Method, manufacture, and apparatus for content protection using authentication data

• US 9,239,912 B1
• Filed: 06/25/2012
• Issued: 01/19/2016
• Est. Priority Date: 12/12/2011
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Dorwin, David Kimbal, Scherkus, Andrew, Kaiser, Christian
• Primary Examiner(s): Zele, Krista
• Assistant Examiner(s): FORMAN, JAMES Q
• Application Number:
  US13/532,734
• Time in Patent Office: 1,303 Days
• Field of Search: 726/29
• US Class Current: 1/1
• CPC Class Codes: G06F 11/3003 Monitoring arrangements specially adapted to the computing system or computing system component being monitored
• CPC Class Codes: G06F 21/105 Arrangements for software license management or administration, e.g. for managing licenses at corporate level
• CPC Class Codes: G06F 21/1062 Editing
• CPC Class Codes: G06F 21/1073 Conversion
• CPC Class Codes: G06F 21/50 Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
• CPC Class Codes: G06F 21/60 Protecting data
• CPC Class Codes: G06F 21/602 Providing cryptographic facilities or services
• CPC Class Codes: G06F 21/62 Protecting access to data via a platform, e.g. using keys or access control rules
• CPC Class Codes: G06F 21/6209 to a single file or object, e.g. in a secure envelope, encrypted and accessed using a key, or with access control rules appended to the object itself
• CPC Class Codes: G06F 40/143 Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD]
• CPC Class Codes: G06T 11/00 2D [Two Dimensional] image generation
• CPC Class Codes: G11B 20/00086 Circuits for prevention of unauthorised reproduction or copying, e.g. piracy indicating unauthorised use of record carriers in general G11B23/28; scrambling for television signal recording H04N5/913; network architectures or network protocols for network security H04L63/00; cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
• CPC Class Codes: H04L 2209/603 Digital right managament [DRM]
• CPC Class Codes: H04L 2463/101 applying security measures for digital rights management
• CPC Class Codes: H04L 2463/103 applying security measure for protecting copyright
• CPC Class Codes: H04L 47/801 Real time traffic
• CPC Class Codes: H04L 47/805 QOS or priority aware
• CPC Class Codes: H04L 63/00 Network architectures or network communication protocols for network security cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00; network architectures or network communication protocols for wireless network security H04W12/00; security arrangements for protecting computers or computer systems against unauthorised activity G06F21/00
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/06 for supporting key management in a packet data network cryptographic mechanisms or cryptographic arrangements for key management H04L9/08
• CPC Class Codes: H04L 63/0876 : based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
• CPC Class Codes: H04L 63/102 : Entity profiles
• CPC Class Codes: H04L 65/1101 : Session protocols
• CPC Class Codes: H04L 65/1108 : Web based protocols, e.g. webRTC
• CPC Class Codes: H04L 65/613 : for the control of the source by the destination control signals issued by the client directed to the server or network components specially adapted for selective content distribution H04N21/637
• CPC Class Codes: H04L 65/762 : at the source reformatting of additional data in video distribution servers H04N21/2355
• CPC Class Codes: H04L 65/80 : Responding to QoS
• CPC Class Codes: H04L 9/0631 : Substitution permutation network [SPN], i.e. cipher composed of a number of stages or rounds each involving linear and nonlinear transformations, e.g. AES algorithms
• CPC Class Codes: H04L 9/0861 : Generation of secret information including derivation or calculation of cryptographic keys or passwords
• CPC Class Codes: H04L 9/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 Class Codes: H04N 21/2347 : involving video stream encryption
• CPC Class Codes: H04N 21/24 : Monitoring of processes or resources, e.g. monitoring of server load, available bandwidth, upstream requests monitoring of server performance or load G06F11/34; arrangements for observation, testing or troubleshooting for broadcast or for distribution combined with broadcast H04H20/12
• CPC Class Codes: H04N 21/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 Class Codes: H04N 21/25833 : involving client hardware characteristics, e.g. manufacturer, processing or storage capabilities allocation of resources considering hardware capabilities in multiprogramming arrangements G06F9/5044; allocation of resources considering software capabilities in multiprogramming arrangements G06F9/5055
• CPC Class Codes: H04N 21/41407 : embedded in a portable device, e.g. video client on a mobile phone, PDA, laptop constructional details of equipment or arrangements specially adapted for portable computer application G06F1/1626; arrangements specially adapted for mobile receivers in broadcast systems H04H20/57
• CPC Class Codes: H04N 21/4405 : involving video stream decryption
• CPC Class Codes: H04N 21/4516 : involving client characteristics, e.g. Set-Top-Box type, software version or amount of memory available

Abstract

A method, apparatus, and manufacture for content protection using authentication data. 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. Upon determining that the media content is protected, the application is employed to get a key and/or a license for the protected media content such that authentication data is employed to authorize the client. The authentication data includes at least one of a software token or a cookie. The application is employed to instruct the media engine to play the media content. The key and/or the license is sent from the application to the media engine.

Claims

1. A method, comprising:

receiving and storing a web authentication token as a result of logging into a website;

subsequent to storing the web authentication token, employing a media stack that is part of a client browser to initiate playback of media content accessed via a hypertext markup language (HTML) media element;

employing the media stack to determine whether the media content is protected;

generating, responsive to a determination by the media stack that the media content is protected, a request message requesting a license for playback of the media content;

combining the web authentication token into the generated request message by encrypting the web authentication token into the request message, the combining comprising;

integrating the web authentication token into the generated request message; and

digitally signing the request message having the integrated web authentication token;

sending the request message with the encrypted web authentication token to a server;

receiving the license for playback of the media content from the server in response to the request message; and

sending the received license to the media stack.

2. The method of claim 1, wherein the web authentication token includes web authentication credentials.

3. The method of claim 1, wherein the web authentication token includes a domain cookie.

4. The method of claim 1, wherein determining whether the media content is protected includes at least one of determining whether the media content is encrypted or determining whether the media content is protected by a license.

5. The method of claim 1, further comprising:

obtaining a decrypted content key from the license by performing decryption such that the decryption employs at least a portion of the web authentication token.

6. The method of claim 1, further comprising:

employing the server to extract the web authentication token from the generated request message; and

employing the server to determine whether the user is authorized based on the extracted web authentication token.

7. The method of claim 1, wherein the web authentication token includes authentication data used by the server to verify that a user is authorized to playback the media content.

8. The method of claim 1, wherein the license for playback of the media content from the server comprises:

receiving a decryption key for decrypting the media content.

9. The method of claim 1, wherein the license for playback of the media content from the server comprises:

receiving a decryption key for decrypting the media content.

10. A client device, comprising:

a memory component for storing data; and

a processing component that is configured to execute the stored data to perform actions comprising;

receiving and storing a web authentication token as a result of logging into a website;

subsequent to storing the web authentication token, employing a media stack that is part of a client browser to initiate playback of media content accessed via a hypertext markup language (HTML) media element;

employing the media stack to determine whether the media content is protected;

generating, responsive to a determination by the media stack that the media content is protected, a request message requesting a license for playback of the media content;

combining the web authentication token into the generated request message by encrypting the web authentication token into the request message, the combining comprising;

integrating the web authentication token into the generated request message; and

digitally signing the request message having the integrated web authentication token;

sending the request message with the encrypted web authentication token to a server;

receiving the license for playback of the media content from the server in response to the request message; and

sending the received license to the media stack.

11. The client device of claim 10, wherein the web authentication token includes a domain cookie.

12. A manufacture, including a non-transitory processor-readable storage medium having processor-executable code encoded therein, which when executed by one or more processors, performs actions comprising:

receiving and storing a web authentication token as a result of logging into a website;

subsequent to storing the web authentication token, employing a media stack that is part of a client browser to initiate playback of media content accessed via a hypertext markup language (HTML) media element;

employing the media stack to determine whether the media content is protected;

generating, responsive to a determination by the media stack that the media content is protected, a request message requesting a license for playback of the media content;

combining the web authentication token into the generated request message by encrypting the web authentication token into the request message, the combining comprising;

integrating the web authentication token into the generated request message; and

digitally signing the request message having the integrated web authentication token;

sending the request message with the encrypted web authentication token to a server;

receiving the license for playback of the media content from the server in response to the request message; and

sending the received license to the media stack.

13. The manufacture of claim 12, wherein the web authentication token includes a domain cookie.