DRM addition authentication

• US 10,506,288 B2
• Filed: 03/24/2016
• Issued: 12/10/2019
• Est. Priority Date: 03/27/2015
• Status: Active Grant

• Current Assignee: PRJ Holding Company LLC
• Original Assignee: Piksel Incorporated
• Inventors: Valsecchi, Stefano, Tornielli, Giorgio
• Primary Examiner(s): Bruckart, Benjamin R
• Assistant Examiner(s): Nguyen, Tien M
• Application Number:
  US15/561,751
• Publication Number:
  US 20180091857A1
• Time in Patent Office: 1,356 Days
• 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/1073 Conversion
• CPC Class Codes: H04L 9/08 Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords network architectures or network communication protocols for supporting key management in a packet data network H04L63/06
• CPC Class Codes: H04N 21/2541 Rights Management protecting software against unauthorised usage in a vending or licensing environment G06F21/10; security in data switching network management H04L41/28; security management or policies for network security H04L63/20; access security in wireless networks H04W12/08
• CPC Class Codes: H04N 21/4627 Rights management associated to the content security in data switching network management H04L41/28; security management or policies for network security H04L63/20; access security in wireless networks H04W12/08

Abstract

There is provided a client device comprising a content protection decoder according to a first standard, comprising: a receiver for receiving an asset associated with content protection; a creation module for creating a content protection for the asset in accordance with the first standard, and including a parameter identifying information additional to the information associated with said standard; an interface for transmitting a request for a license to a license server based on said standard, the request including that parameter, and for receiving a license in response; and a controller for accessing content associated with the asset using the license. There is also provided a license server configured to: receive a license key request in accordance with a standard from a client device; transmit the request to a processing function associated with the standard; receive a parameter associated with the standard from the processing function; parse the parameter to retrieve additional information; process the additional information; access a license in accordance with the standard based on the parsed information; and transmit the accessed license in accordance with the standard to the client device.

Claims

1. A client device comprising a content protection decoder according to a first standard, comprising:

a receiver for receiving an asset associated with content protection according to a second standard different than the first standard;

a header creation block for creating a header for the asset in accordance with the first standard, the header including information associated with the first standard and a parameter comprising information additional to the information associated with the first standard;

an interface for transmitting a request, including the header, for a license to a license server based on the first standard, and for receiving a license in response, wherein the additional information is used for obtaining the license; and

a controller for accessing content associated with the asset using the license.

2. The client device of claim 1 wherein the first standard is a Widevine digital rights management standard.

3. The client device of claim 2 wherein the creation module creates a Widevine digital rights management header, and the parameter is the ContentID field of the Widevine digital rights management header.

4. The client device of claim 3 wherein the ContentID field comprises information associated with a content protection standard of the received asset, wherein such information is not located in a Widevine digital rights management header.

5. The client device of claim 1 wherein the additional information is for a verification check to be performed by the license server.

6. The client device of claim 1 wherein the additional information includes one of a user identification, a device identification, a time of day, and a location.

7. The client device of claim 1 wherein the receiver receives the asset associated with content protection of the second standard.

8. The client device of claim 7 wherein the second standard is one of a Widevine digital rights management standard, Marlin digital rights management standard, and PlayReady digital rights management standard.

9. The client device of claim 1 wherein the receiver receives the asset as an MPEG-DASH message protected according to the common encryption (CENC) standard.

10. The client device of claim 1 further comprising:

a video player, wherein the asset is associated with video content.

11. A method of generating a license in a license server, the method comprising the steps, at the license server, of:

receiving a license key request in accordance with a first standard, being a Widevine digital rights management standard, from a client device;

transmitting the license key request to a processing function associated with the first standard;

receiving a parameter, being the Widevine digital rights management standard, associated with the first standard from the processing function and the parameter is a ContentID field of a Widevine header;

parsing the parameter to retrieve additional information;

performing a verification using the additional data;

in response to a successful verification, retrieving a license in accordance with the first standard based on the retrieved additional information; and

transmitting the retrieved license in accordance with the first standard to the client device.

12. The method of claim 11 wherein the additional information is processed by performing a verification based on the additional information, and the retrieval of the license is dependent on the verification.

13. The method of claim 12 wherein the verification is associated with one of identification of a user, identification of a user device, identification of a time of day, and identification of a location.

14. The method of claim 12, wherein in dependence on the verification based on the additional information being successful, retrieving the license is enabled.

16. A non-transitory computer readable medium encoding a computer program, which when executed on a computing device, performs the method of claim 11.

15. A method of generating a license request in a client device providing content protection according to a first standard, the method comprising:

receiving an asset associated with content protection according to a second standard different than the first standard;

creating a header for the asset in accordance with the first standard, the header including a parameter comprising information additional to that associated with the first standard, comprising;

determining that a generic content protection tag is available in a manifest file of the received asset and a KeyID is available in the generic content protection tag;

in response to the determining the generic content protection tag of the manifest file of the received asset or the KeyID in the generic content protection tag is available, then searching for a content protection tag for each digital right management (DRM) supported technology identified in the manifest file of the received asset;

wherein the searching comprises;

determining that there is a PlayReady content protection tag associated with the received asset in the received manifest file;

in response to the determining that there is the PlayReady content protection tag, searching for a KeyID in a PlayReadyObject attribute of the PlayReady content protection tag containing a PlayReady header;

in response to the determining that there is no PlayReady content protection tag, but there is a content protection tag for Marlin in the received manifest file, searching the KeyID in a Marlin header that is contained in the content protection tag for Marlin;

in response to the determining that neither the PlayReady content protection tag nor the Marlin content protection tag is available and there are remaining DRM technologies being supported, extending the search for KeyID in content protection tags corresponding to the remaining supported DRM technologies;

based on the searching, the KeyID in the manifest file associated with the received asset is located;

once the KeyID is located, creating a Widevine header with KeyID and ContentID fields both populated, by transferring the located KeyID to the KeyID field of the created Widevine header, and by creating a ContentID field using the KeyID field;

transmitting a request, including the header, for a license to a license server based on the first standard, the request including the parameter, and for receiving a license in response; and

accessing content associated with the asset using the license.

17. A non-transitory computer readable medium for storing computer program code which, when executed on a computing device, performs the method of claim 15.

18. A license server, configured to:

receive a license key request in accordance with a first standard, being a Widevine digital rights management standard, from a client device;

transmit the license key request to a processing function associated with the first standard;

receive a parameter, being the Widevine digital rights management standard, associated with the first standard from the processing function and the parameter is a content ID field of a Widevine header;

parse the parameter to retrieve additional information;

perform a verification using the additional data;

in response to a successful verification, retrieve a license in accordance with the first standard based on the retrieved additional information; and

transmit the accessed license in accordance with the first standard to the client device.