GENERIC RIGHTS TOKEN AND DRM-RELATED SERVICE POINTERS IN A COMMON PROTECTED CONTENT FILE

• US 20090165080A1
• Filed: 12/20/2007
• Published: 06/25/2009
• Est. Priority Date: 12/20/2007
• Status: Active Grant

• Current Assignee: Samsung Electronics Co. Ltd.
• Original Assignee: Samsung Electronics Co. Ltd.
• Inventors: VERMA, Sanjeev, FAHN, Paul
• Granted Patent: US 8,856,861 B2
• Time in Patent Office: Days
• 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 on a device having a native digital rights management (DRM) system, the method comprising:

acquiring content in a common content format file having first data, second data, and third data, wherein the first data is a generic rights token containing information to allow retrieval of rights associated with the content;

determining whether the device is registered in a domain utilizing the second data in the common content format file;

accessing a license server directory utilizing the third data in the common content format file;

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

receiving a native DRM system trigger; and

acquiring a native DRM license, thereby enabling rendering of the content in the common content format file on the device.

2. A method as recited in claim 1 further comprising obtaining the generic rights token by utilizing a fourth data in the common content format file.

3. A method as recited in claim 2 wherein obtaining the generic rights token further comprises accessing a rights archive server utilizing a rights archive server pointer stored in the fourth data in the common content format file.

4. A method as recited in claim 1 further comprising executing an interoperable domain client on the device.

5. A method as recited in claim 1 further comprising accessing a domain manager server using the second data in the common content format file.

6. A method as recited in claim 1 wherein receiving a native DRM system trigger further comprises invoking a native DRM system client on the device.

7. A method as recited in claim 1 wherein acquiring a native DRM license further comprises invoking a native DRM system client on the device.

8. A method as recited in claim 1 further comprising determining whether the content may be shared by devices in the domain.

9. A method as recited in claim 1 further comprising receiving a device identifier from a domain manager.

10. A method as recited in claim 1 wherein the first data, the second data, the third data and the content are in standardized locations in the common content format file.

11. A method as recited in claim 2 wherein the fourth data is in a standardized location in the common content format file.

12. A digital rights management (DRM) system comprising:

a device storing an interoperable domain client for enabling multiple DRM interoperability and a native DRM client;

a common content format file having a domain manager pointer, a license server directory pointer, and content protected using a native DRM;

a rights archive having a generic rights storage area, a domain identifier storage area, and a content identifier storage area;

a domain manager having a domain identifier storage area and a device identifier storage area; and

a license server directory having a DRM identifier storage area and a native license server identifier storage area for enabling mapping of a DRM identifier with a native license server.

13. A system as recited in claim 12 further comprising:

a generic rights token having a first information to identify the content being licensed and a second information to identify the rights associated with rendering the content.

14. A system as recited in claim 12 wherein the license server directory further comprises:

a domain identifier storage area, a device identifier storage area, content identifier storage area, and a rights description storage area.

15. A system as recited in claim 12 further comprising:

a content provider server for providing protected content for rendering on the device using a native DRM system.

16. A system as recited in claim 15 further comprising one or more native license servers, a license server being associated with a content provider server.

17. A system as recited in claim 12 wherein the common content format file further comprises a rights archive pointer.

18. A system as recited in claim 12 wherein the common content format file further comprises a generic rights token.

19. A method of acquiring a license to execute content on a device, the method comprising:

receiving a request from the device, the request including a native DRM identifier and a generic rights token relating to the content;

identifying a native license server from the native DRM identifier; and

transmitting a URL of the native license server to the device, thereby enabling the native license server to create a license in the native DRM license format.

20. A method as recited in claim 19 wherein the transmitting step comprises transmitting the generic rights token to the native license server, thereby enabling the native license server to create a license in the native DRM license format.

21. A method as recited in claim 20 wherein contacting the native license server further comprises transmitting a generic rights token.

22. A method as recited in claim 19 further comprising transmitting a common protected content format file having standardized locations for a generic rights token and a protected content to the device.

23. A method as recited in claim 22 wherein the common protected content format file further comprises a standardized location for a domain manager pointer.

24. A method as recited in claim 22 wherein the common protected content format file further comprises a standardized location for a rights archive pointer.

25. A program storage device readable by a machine tangibly embodying a program of instructions executable by the machine to perform a method of rendering content on a device having a native digital rights management (DRM) system, the method comprising:

acquiring content in a common content format file having first data, second data, and third data, wherein the first data is a generic rights token containing information to allow retrieval of rights associated with the content;

determining whether the device is registered in a domain utilizing the second data in the common content format file;

accessing a license server directory utilizing the third data in the common content format file;

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

receiving a native DRM system trigger; and

acquiring a native DRM license, thereby enabling rendering of the content in the common content format file on the device.

26. A device capable of rendering content, the device comprising:

a common content format file having a generic rights token and a content, the content protected using a native digital rights management (DRM) system, and wherein the generic rights token and the content are in a plurality of standardized locations; and

a native DRM system client software module for enabling rendering of content using the native DRM system.

27. A device as recited in claim 26 wherein the common content format file further comprises a rights archive pointer in one of the plurality of standardized locations that points to a rights archive server.

28. A device as recited in claim 26 wherein the common content format file further comprises a domain manager pointer in one of the plurality of standardized locations that points to a domain manager server.

29. A device as recited in claim 26 wherein the common content format file further comprises a license server directory pointer in one of the plurality of standardized locations that points to a license server directory server.

30. A device as recited in claim 26 wherein the generic rights token contains information to allow retrieval of rights associated with the content.

31. A device as recited in claim 26 further comprising an interoperable domain client software module for enabling multiple DRM system interoperability on the device.

32. A device as recited in claim 31 wherein the interoperable domain client accesses a rights archive server if the common content format file does not contain a generic rights token.

33. A device as recited in claim 31 wherein the interoperable domain client downloads the generic rights token from the rights archive server onto the device.

34. A device as recited in claim 31 wherein the interoperable domain client registers content rights with a native DRM license server.