Repository with security class and method for use thereof

• US 20030208447A1
• Filed: 06/18/2003
• Published: 11/06/2003
• Est. Priority Date: 11/23/1994
• Status: Active Grant

• Current Assignee: ContentGuard Holdings, Inc. (Pendrell Corporation)
• Original Assignee: Xerox Corporation (Xerox Holdings Corp.)
• Inventors: Stefik, Mark J., Pirolli, Peter L.T.
• Granted Patent: US 6,957,193 B2
• Time in Patent Office: Days
• US Class Current: 705/51
• CPC Class Codes: A61B 2017/0046 with a releasable handle; with handle and operating part separable for prosthetic joint-implanting tools A61F2/4603
• CPC Class Codes: A61B 2034/301 for introducing or steering flexible instruments inserted into the body, e.g. catheters or endoscopes
• CPC Class Codes: A61B 2090/031 torque limiting
• CPC Class Codes: A61B 2090/376 using X-rays, e.g. fluoroscopy
• CPC Class Codes: A61B 34/30 Surgical robots
• CPC Class Codes: A61B 34/37 Master-slave robots A61B34/35 takes precedence
• CPC Class Codes: A61M 25/0113 Mechanical advancing means, e.g. catheter dispensers
• 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 2211/007 Encryption, En-/decode, En-/decipher, En-/decypher, Scramble, (De-)compress
• CPC Class Codes: G06F 2221/2115 Third party
• CPC Class Codes: G06F 2221/2135 Metering
• CPC Class Codes: G06Q 10/101 Collaborative creation, e.g. joint development of products or services
• CPC Class Codes: G06Q 20/12 specially adapted for electronic shopping systems
• CPC Class Codes: G06Q 20/1235 with control of digital rights management [DRM]
• CPC Class Codes: G06Q 20/3674 involving authentication
• CPC Class Codes: G06Q 30/00 Commerce
• CPC Class Codes: G06Q 30/0185 Product, service or business identity fraud
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: G06Q 30/0283 Price estimation or determination
• CPC Class Codes: G06Q 30/04 Billing or invoicing
• CPC Class Codes: G06Q 30/06 : Buying, selling or leasing transactions
• CPC Class Codes: G06Q 30/0601 : Electronic shopping [e-shopping]
• CPC Class Codes: G06Q 50/184 : Intellectual property management
• CPC Class Codes: H04L 12/14 : Charging , metering or billing arrangements for data wireline or wireless communications
• CPC Class Codes: H04L 12/1403 : Architecture for metering, charging or billing
• CPC Class Codes: H04L 12/146 : using digital cash
• CPC Class Codes: H04L 12/1485 : Tariff-related aspects
• CPC Class Codes: H04L 12/1496 : involving discounts
• CPC Class Codes: H04L 2209/56 : Financial cryptography, e.g. electronic payment or e-cash
• CPC Class Codes: H04L 2209/603 : Digital right managament [DRM]
• CPC Class Codes: H04L 2463/101 : applying security measures for digital rights management data processing systems or methods, specially adapted for commerce, e.g. marketing, shopping, billing, auctions or e-commerce G06Q30/00
• CPC Class Codes: H04L 61/00 : Network arrangements, protocols or services for addressing or naming
• CPC Class Codes: H04L 61/45 : Network directories; Name-to-address mapping
• 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/0442 : wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption cryptographic mechanisms or cryptographic arrangements for public-key encryption H04L9/30
• CPC Class Codes: H04L 63/0464 : using hop-by-hop encryption, i.e. wherein an intermediate entity decrypts the information and re-encrypts it before forwarding it
• CPC Class Codes: H04L 63/0807 : using tickets, e.g. Kerberos cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213
• CPC Class Codes: H04L 63/0823 : using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 63/10 : for controlling access to devices or network resources
• CPC Class Codes: H04L 63/102 : Entity profiles
• CPC Class Codes: H04L 63/104 : Grouping of entities
• CPC Class Codes: H04L 63/105 : Multiple levels of security
• CPC Class Codes: H04L 63/123 : received data contents, e.g. message integrity
• CPC Class Codes: H04L 9/3213 : using tickets or tokens, e.g. Kerberos network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807
• CPC Class Codes: H04L 9/3297 : involving time stamps, e.g. generation of time stamps
• CPC Class Codes: H04L 9/40 : Network security protocols
• CPC Class Codes: H04N 21/23412 : for generating or manipulating the scene composition of objects, e.g. MPEG-4 objects
• 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/2543 : Billing , e.g. for subscription services payment schemes, architectures or protocols G06Q20/00; e-commerce G06Q30/00; arrangements for billing for the use of broadcast information or broadcast-related information H04H60/21
• CPC Class Codes: H04N 21/26613 : for generating or managing keys in general key distribution for secret or secure communication involving central third party, e.g. key distribution center [KDC] or trusted third party [TTP] H04L9/083; network support of key management H04L63/06; key management for network security in communication control or processing H04W12/04
• 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
• CPC Class Codes: H04N 21/6332 : directed to client
• CPC Class Codes: H04N 21/6377 : directed to server one-way streaming services wherein the source is controlled by the destination H04L65/613
• CPC Class Codes: H04N 21/835 : Generation of protective data, e.g. certificates protecting software against unauthorised usage in a vending or licensing environment G06F21/10
• CPC Class Codes: H04N 21/8355 : involving usage data, e.g. number of copies or viewings allowed
• CPC Class Codes: H04N 21/83555 : using a structured language for describing usage rules of the content, e.g. REL
• CPC Class Codes: H04N 7/16 : Analogue secrecy systems; Analogue subscription systems
• CPC Class Codes: Y10S 707/99939 : Privileged access
• CPC Class Codes: Y10S 707/99945 : Object-oriented database structure processing

Abstract

A trusted system having at least one repository for controlling use of digital works in accordance with usage rights associated with the digital works. A request to use a digital work in accordance with usage rights associated with the digital work is received. The usage rights specify a manner of use and an access specification indicating a security class. A security level of a repository controlling the requested use is determined. The request is granted and the user is permitted to exercise the manner of use specified in the usage rights associated with the digital work if the security level of the repository corresponds to the security class of the access specification specified in the usage rights associated with the digital work.

Claims

1. In a trusted system having at least one repository for controlling use of digital works in accordance with usage rights associated with the digital works, a method comprising:

receiving a request to use a digital work in accordance with usage rights associated with the digital work, the usage rights specifying a manner of use and an access specification indicating a security class;

determining a security level of a repository controlling the requested use; and

if the security level of the repository corresponds to the security class of the access specification specified in the usage rights associated with the digital work, granting the request and permitting exercise of the manner of use specified in the usage rights associated with the digital work in accordance with the usage rights.

2. A method as recited in claim 1, wherein the security class specified by the access specification indicates a minimum security level of a repository that can exercise the manner of use specified in the usage rights.

3. A method as recited in claim 1, wherein the security class specified by the access specification indicates a security level of a repository that can exercise the manner of use specified in the usage rights.

4. A method as recited in claim 1, wherein the manner of use is copying the digital work to the repository.

5. A method as recited in claim 1, wherein the manner of use is rendering the digital work with the repository.

6. A method as recited in claim 1, wherein the digital work is a software program and the manner of use is executing the software program.

7. A method as recited in claim 1, wherein the access specification is expressed with a grammar.

8. A method as recited in claim 1, wherein the digital work is encrypted and further comprising the step of decrypting the digital work prior to exercising the manner of use.

9. A method as recited in claim 8, wherein a digital certificate is used for identification of the repository.

10. A method as recited in claim 8, wherein the physical integrity of the repository is secured.

11. A method as recited in claim 8, wherein digital works cannot be stored on removable storage.

12. A method as recited in claim 6, wherein said executing step comprises running the computer program in a dedicated address space and preventing access to any memory containing system code or other digital works.

13. A method as recited in claim 1, wherein digital works are accessed only through a transmission transaction protocol.

14. A method as recited in claim 1, wherein sensors are disposed on said repository to record attempts at physical and electronic tampering with the repository, and further comprising the step of preventing performance of transaction when tampering is detected and reporting the detected tampering to a designated device.

15. A method as recited in claim 1, further comprising:

detecting any attempts at tampering with the repository; and

if level of attempts at tampering with the repository exceeds a predetermined threshold, causing the repository to save only document description records and destroying any digital identifiers of documents.

16. A method as recited in claim 1, wherein the predetermined threshold defines a number of attempts at tampering and wherein said level is a number of attempts at tampering.

17. A method as recited in claim 15, further comprising modifying any certificates of authenticity to indicate that the security of the repository has been compromised.

18. A method as recited in claim 15, further comprising erasing the contents of designated documents if the level of attempts at tampering with the repository exceed the predetermined threshold.

19. A method as recited in claim 15, further comprising the repository communicating attempts at tampering to another device.

20. A method as recited in claim 15, further comprising activating an alarm when tampering is detected.

21. A method as recited in claim 1, further comprising maintaining communications with a remote security systems.

22. A method as recited in claim 21, wherein said communications comprise at least one of reporting transactions, reporting sensor readings, and reporting attempts to circumvent security of the repository.

23. A method as recited in claim 1, further comprising a user interface for permitting a user to communicate with the repository.

24. A method as recited in claim 23, wherein the user interface and the repository are embedded on the same device.

25. A method as recited in claim 1, further comprising recording the history of transactions with the repository.

26. A method as recited in claim 1, wherein the repository is password protected.

27. A method as recited in claim 1, further comprising preventing setting of a clock of the repository without authorization.

28. A method as recited in claim 1, wherein the digital work is a bond or a stock certificate.

56. A method as recited in claim 1, wherein the digital work is a bond or a stock certificate.

29. A trusted system having at least one repository for controlling use of digital works in accordance with usage rights associated with the digital works, said system comprising:

means for receiving a request to use a digital work in accordance with usage rights associated with the digital work, the usage rights specifying a manner of use and an access specification indicating a security class;

means for determining a security level of a repository controlling the requested use; and

means for granting the request and permitting exercise of the manner of use specified in the usage rights associated with the digital work in accordance with the usage rights if the security level of the repository corresponds to the security class of the access specification specified in the usage rights associated with the digital work.

30. A system as recited in claim 29, wherein the security class specified by the access specification indicates a minimum security level of a repository that can exercise the manner of use specified in the usage rights.

31. A system as recited in claim 29, wherein the security class specified by the access specification indicates a security level of a repository that can exercise the manner of use specified in the usage rights.

32. A system as recited in claim 29, wherein the manner of use is copying the digital work to the repository.

33. A system as recited in claim 29, wherein the manner of use is rendering the digital work with the repository.

34. A system as recited in claim 29, wherein the digital work is a software program and the manner of use is executing the software program by means for executing.

35. A system as recited in claim 29, wherein the access specification is expressed with a grammar.

36. A system as recited in claim 29, wherein the digital work is encrypted and further comprising means for decrypting the digital work prior to exercising the manner of use.

37. A system as recited in claim 29, wherein a digital certificate is used for identification of the repository.

38. A system as recited in claim 36, wherein the physical integrity of the repository is secured.

39. A system as recited in claim 36, wherein digital works cannot be stored on removable storage.

40. A system as recited in claim 34, wherein said means for executing comprises means for running the computer program in a dedicated address space and means for preventing access to any memory containing system code or other digital works.

41. A system as recited in claim 29, wherein digital works are accessed only through a transmission transaction protocol.

42. A system as recited in claim 29, wherein sensors are disposed on said repository to record attempts at physical and electronic tampering with the repository, and further comprising means for preventing performance of transactions when tampering is detected and means for reporting the detected tampering to a designated device.

43. A system as recited in claim 29, further comprising:

means for detecting any attempts at tampering with the repository; and

means for causing the repository to save only document description records and destroying any digital identifiers of documents if a level of attempts at tampering with the repository exceeds a predetermined threshold.

44. A system as recited in claim 29, wherein the predetermined threshold defines a number of attempts at tampering and wherein said level is a number of attempts at tampering.

45. A system as recited in claim 43, further comprising means for modifying any certificates of authenticity to indicate that the security of the repository has been compromised.

46. A system as recited in claim 43, further comprising means for erasing the contents of designated documents if the level of attempts at tampering with the repository exceed the predetermined threshold.

47. A system as recited in claim 43, wherein the repository comprises means for communicating attempts at tampering to another device.

48. A system as recited in claim 43, further comprising means for activating an alarm when tampering is detected.

49. A system as recited in claim 29, further comprising means for maintaining communications with a remote security system.

50. A system as recited in claim 49, wherein said means for maintaining communications comprises at least one of means for reporting transactions, means for reporting sensor readings, and means for reporting attempts to circumvent security of the repository.

51. A system as recited in claim 29, further comprising user interface means for allowing a user to communicate with the repository.

52. A system as recited in claim 51, wherein said user interface means and said repository are embedded in the same device.

53. A system as recited in claim 29, further comprising means for recording the history of transactions with the repository.

54. A system as recited in claim 29, further comprising means for password protecting the repository.

55. A system as recited in claim 29, further comprising means for preventing setting of a clock of the repository without authorization.