Generic rights token and DRM-related service pointers in a common protected content file

• US 8,856,861 B2
• Filed: 12/20/2007
• Issued: 10/07/2014
• Est. Priority Date: 12/20/2007
• Status: Expired due to Fees

• Current Assignee: Samsung Electronics Co. Ltd.
• Original Assignee: Samsung Electronics Co. Ltd.
• Inventors: Fahn, Paul, Verma, Sanjeev
• Primary Examiner(s): Zele, Krista
• Assistant Examiner(s): VOSTAL, ONDREJ C
• Application Number:
  US11/961,432
• Publication Number:
  US 20090165080A1
• Time in Patent Office: 2,483 Days
• Field of Search: 726/1
• US Class Current: 726/1
• CPC Class Codes: G06F 17/00 Digital computing or data processing equipment or methods, specially adapted for specific functions information retrieval, database structures or file system structures therefor G06F16/00
• CPC Class Codes: G06F 21/10 Protecting distributed programs or content, e.g. vending or licensing of copyrighted material protection in video systems or pay television H04N7/16 ; Digital rights management [DRM]
• CPC Class Codes: G06F 21/31 User authentication
• CPC Class Codes: H04L 2209/603 Digital right managament [DRM]
• CPC Class Codes: H04L 63/0263 Rule management
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: H04N 2201/3246 of data relating to permitted access or usage, e.g. level of access or usage parameters for digital rights management [DRM] related to still images

Abstract

Methods and systems of rendering content on a device having a native digital rights management (DRM) system are described. A device, such as an end-user device capable of executing or playing content, acquires content in a common content format file having standardized locations for specific types of data. A generic digital rights token associated with the content is obtained by utilizing one of the standardized locations in the content format file, where the rights token contains information sufficient to allow retrieval of the rights associated with the content. Utilizing data in another of the standardized locations, it is then determined whether the device is registered in a domain. A license server directory may be accessed utilizing data in another of the standardized locations in the common content format file and a domain identifier, a device identifier, or both are transmitted to the license server directory. A native DRM system trigger is received and, upon activation of the trigger, a native DRM license is acquired, thereby enabling rendering of the content in the common content format file on the device.

Claims

1. A method of rendering content at least on a first device having a first native digital rights management (DRM) system and on a second device having a second native DRM system, the method comprising:

acquiring the content on the first device and on the second device in a common content format file comprising a domain manager pointer to a domain manager, a rights archive pointer to a rights archive, and a license server directory pointer to a license server directory;

determining whether the first device and the second device are registered in the same domain by accessing the domain manager utilizing the domain manager pointer in the common content format file;

accessing the license server directory comprising a memory device maintaining one or more native license server identifiers, wherein the license server directory is access utilizing the license server directory pointer in the common content format file;

transmitting a first domain identifier, a second domain identifier, a first device identifier and a second device identifier to the license server directory;

obtaining from the license server directory a native license server identifier for the content; and

receiving at the first device and at the second device a native DRM system trigger from a native license server associated with the native license server identifier, wherein the native DRM system trigger is transmitted if the native license server determines that each device has a license to render the content, thereby enabling rendering of the content in the common content format file on the first device and on the second device using a first native DRM system client software module on the first device and a second native DRM system client software module one the second device; and

wherein the first native DRM system and the second native DRM system are components in an interoperable, multiple-DRM system, the first native DRM system being different from the second native DRM system.

2. The method as recited in claim 1 further comprising obtaining a generic rights token by accessing the rights archive utilizing the rights archive pointer in the common content format file.

3. The method as recited in claim 1 further comprising executing an interoperable domain client on the first device and on the second device, the interoperable domain client performing operations on the common content format file.

4. The method as recited in claim 1 wherein receiving a native DRM system trigger further comprises invoking a native DRM system client software module one the first device and on the second device.

5. The method as recited in claim 1 further comprising determining whether the content may be shared by the first device and by the second device in the same domain.

6. The method as recited in claim 2, further comprising:

locating the domain manage pointer, the rights archive pointer, the license server directory pointer, the generic rights token and the content in standardized locations in the common content format file, wherein said standardized location in the common content format comprise a shared discrete headers area that includes a common headers storage area for maintaining pointers to multiple network services for enabling interoperability.

7. The method as recited in claim 1, wherein:

a DRM header of one DRM system of said multiple-DRM system is incompatible with a DRM header of another DRM system of said multiple-DRM system.

8. A non-transitory computer-readable medium having instructions which when executed on a computer perform a method of rendering content at least on a first device having a first native digital rights management (DRM) system and on a second device having a second native DRM system, the method comprising:

acquiring the content on the first device and on the second device in a common content format file comprising a domain manager pointer to a domain manager, a rights archive pointer to a rights archive, and a license server directory pointer to a license server directory;

determining whether the first device and the second device are registered in the same domain by accessing the domain manager utilizing the domain manager pointer in the common content format file;

accessing the license server directory utilizing the license server directory pointer in the common content format file;

transmitting a first domain identifier, a second domain identifier, a first device identifier and a second device identifier to the license server directory;

obtaining from the license server directory a native license server identifier for the content;

receiving at the first device and at the second device a native DRM system trigger from a native license server associated with the native license server identifier;

wherein the native DRM system trigger is transmitted if the native license server determines that each device has a license to render the content, thereby enabling rendering of the acquired content in the common content format file on the first device and on the second device using a native DRM system client software module on the first device and on the second device; and

wherein the first native DRM system the second native DRM system are components in an interoperable, multiple-DRM system, the first native DRM system being different from the second native DRM system.

9. A system for rendering content at least on a first device having a first native digital rights management (DRM) system and on a second device having a second native DRM system, the system comprising:

a license server directory; and

a content rendering device configured to;

acquire content on the first device having the first native DRM system and on the second device having the second native DRM system, wherein the content is acquired in a common content format file comprising a domain manager pointer to a domain manager, a rights archive pointer to a rights archive, and a license server directory pointer to the license server directory;

determine whether the first device and the second device are registered in the same domain by accessing the domain manager utilizing the domain manager pointer in the common content format file;

access the license server directory utilizing the license server directory pointer in the common content format file;

transmit a first domain identifier, a second domain identifier, a first device identifier and a second device identifier to the license server directory;

obtain from the license server directory a native license server identifier for the content;

wherein the first device and the second device each receive a native DRM system trigger from a native license server associated with the native license server identifier, wherein the native DRM system trigger is transmitted if the native license server determines that each device has a license to render the content, thereby enabling rendering of the content in the common content format file on the first device and on the second device using a first native DRM system client software module on the first device and a second native DRM system client software module on the second device; and

wherein the first native DRM system the second native DRM system are components in an interoperable, multiple-DRM system, the first native DRM system being different from the second native DRM system.

10. The system of claim 9, wherein the content rendering device is further configured to:

obtain a generic rights token by accessing the rights archive utilizing the rights archive pointer in the common content format file.

11. The system of claim 9, wherein the content rendering device is further configured to:

execute an interoperable domain client on the first device and on the second device, the interoperable domain client programing operations on the common content format file.

12. The system of claim 9, wherein receiving the native DRM system trigger invokes at least a native DRM system client software module each on the first device and on the second device.

13. The system of claim 9, wherein the content rendering device is further configured to:

determine whether the content may be shared by the first device and by the second device in the same domain.

14. The system of claim 10, wherein:

the domain manager pointer, the rights archive pointer, the license server directory pointer, the generic rights token and the content are in standardized location in the common content format file; and

said standardized location in the common content format file comprise a shared discrete headers area that includes a common headers storage area for maintaining pointers to multiple network services for enabling interoperability.

15. The system of claim 9, wherein:

a DRM header of one DRM system of said multiple-DRM system incompatible with a DRM header of another DRM system of said multiple-DRM system.