Digital rights management system based on hardware identification

• US 20060064756A1
• Filed: 09/17/2004
• Published: 03/23/2006
• Est. Priority Date: 09/17/2004
• Status: Abandoned Application

• Current Assignee: Inventec Appliances Corporation (Inventec Corporation)
• Original Assignee: Inventec Appliances Corporation (Inventec Corporation)
• Inventors: Ebert, Robert F.
• Application Number:
  US10/943,392
• Publication Number:
  US 20060064756A1
• Time in Patent Office: Days
• US Class Current: 726/26
• CPC Class Codes: G06F 21/101 by binding digital rights to specific entities
• CPC Class Codes: G06F 21/1063 Personalisation
• CPC Class Codes: G06F 21/123 by using dedicated hardware, e.g. dongles, smart cards, cryptographic processors, global positioning systems [GPS] devices
• CPC Class Codes: G06F 21/125 by manipulating the program code, e.g. source code, compiled code, interpreted code, machine code
• CPC Class Codes: G06F 21/73 by creating or determining hardware identification, e.g. serial numbers

Abstract

A method for digital rights management is provided. The method is used for managing the right to use a digital software application having a main code component including application code and data resources. The method generates a security component including a hardware identification attribute and appends the security component to the main code component to form a software application package. When the software application package is installed on a hardware device, the security component enables the software application only if the hardware identification attribute is also present in the hardware device.

Claims

1. A method for digital rights management comprising:

providing a main code component having application code and data resources;

generating a security component including a hardware identification attribute; and

appending the security component to the main code component to form a software application package, such that when the software application package is installed on a hardware device, the software application is enabled if the hardware identification attribute is also present in the hardware device, and is disabled if the hardware identification attribute is not present in the hardware device.

2. The method of claim 1 wherein generating the security component comprises automatically determining the hardware identification attribute.

3. The method of claim 2 wherein automatically determining the hardware identification attribute comprises reading the hardware identification attribute stored in the hardware device.

4. The method of claim 2 wherein automatically determining the hardware identification attribute comprises matching a user identification with a database comprising hardware identification attributes associated with respective user identifications.

5. The method of claim 1 wherein the security component is a digital hardware signature generated using a data set and a first key.

6. The method of claim 5 wherein the data set comprises the hardware identification attribute.

7. The method of claim 5 wherein the digital hardware signature is validated by a second key stored on the hardware device.

8. The method of claim 5 wherein the digital hardware signature is validated by an encrypted authorization key, which in turn is validated by a second key stored on the hardware device.

9. The method of claim 5 wherein the data set used for generating the digital hardware signature comprises an application signature.

10. The method of claim 1 wherein the software application package is a downloadable executable file.

11. The method of claim 10 wherein the executable file is a PalmOS resource file (.prc).

12. The method of claim 1, wherein the security component is merged with the main code component such that the main code component cannot be separately executed even if the main code component is non-encrypted or decrypted.

13. The method of claim 1 wherein the hardware device is portable.

14. The method of claim 1 wherein the hardware device is a removable ROM or RAM device.

15. A software application comprising:

a main code component including application code and data resources; and

a security component appended to the main code component and including a hardware identification attribute such that the software application is enabled if installed on a hardware device having a matching hardware identification attribute and disabled if installed on any other hardware device.

16. The software application of claim 15 wherein the security component comprises a digital hardware signature generated using a data set and a first key.

17. The software application of claim 16 wherein the data set comprises the hardware identification attribute.

18. The software application of claim 16 wherein the digital signature is validated by a second key stored on the hardware device.

19. The software application of claim 16 wherein the digital signature is validated by an encrypted authorization key, which in turn is validated by a second key stored on the hardware device.

20. The software application of claim 16 wherein the data set used for generating the digital signature comprises an application signature.

21. The software application of claim 15 wherein the main code and the security component are packaged in a downloadable executable file.

22. The software application of claim 21 wherein the executable file is a PalmOS resource file (.prc).

23. The software application of claim 15 wherein the software application is wholly unexecutable when disabled.

24. The software application of claim 15 wherein the software application is partially executable when disabled.

25. The software application of claim 15 wherein the hardware identification attribute is unique to the hardware device.

26. The software application of claim 15 wherein the security component is merged with the main code component such that the main code component cannot be separately executed even if the main code component is non-encrypted or decrypted.

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

a hardware device including a hardware identification attribute; and

a software application having a main code component and a security component appended to the main code component, the security component including a matching hardware identification attribute, such that the software application is enabled if installed on the hardware device and disabled if installed on a hardware device that does not include the matching hardware identification attribute.

28. The DRM system of claim 27 wherein the hardware identification attribute is unique to the hardware device, such that the software application is disabled if installed on any other hardware device.

29. The DRM system of claim 27 wherein the hardware device is portable.

30. The DRM system of claim 29 wherein the portable hardware device is handheld.

31. The DRM system of claim 27 wherein the hardware device is a removable ROM or RAM device.

32. The DRM system of claim 27 wherein the hardware identification attribute is a persistent attribute of the hardware device.

33. The DRM system of claim 32 wherein the persistent attribute is a serial number of the hardware device.

34. The DRM system of claim 32 wherein the persistent attribute is stored in a ROM memory element of the hardware device.

35. The DRM system of claim 27 wherein the security component is merged with the main code component such that the main code component cannot be separately executed even if the main code component is non-encrypted or decrypted.

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

a first server configured to receive a set of user data and determine a hardware identification attribute therefrom; and

a second server configured to generate, upon a request from the first server, a digital hardware signature based on the set of user data and including the hardware identification attribute, and either of the first server or second servers being configured to append the digital hardware signature to a software application to form a software application package which is executable on a hardware device only when the hardware device has a matching hardware identification attribute.

37. The DRM system of claim 36 wherein the first server is an Electronic Software Distribution server storing the software application component, and the second server is a digital signature server storing private keys for generating the digital hardware signature.

38. The DRM system of claim 37 wherein the digital signature server is configured to return the generated digital hardware signature to the Electronic Software Distribution server to form the software application package.

39. The DRM system of claim 36 wherein the first server is connected to a user interface.

40. The DRM system of claim 39 wherein the user interface is a Web browser.

41. The DRM system of claim 36 wherein the first server is configured to distribute the software application package to a user.

42. The DRM system of claim 36 wherein the set of user data comprises a user identification, and the hardware identification attribute is determined by matching the user identification to a database comprising hardware identification attributes associated with respective user identifications.