RIGHTS-BASED SYSTEM

• US 20190138742A1
• Filed: 08/10/2018
• Published: 05/09/2019
• Est. Priority Date: 08/02/2011
• Status: Active Grant

• Current Assignee: API Market, Inc.
• Original Assignee: API Market, Inc.
• Inventors: Roever, Stefan, Watson, David
• Granted Patent: US 10,706,168 B2
• Time in Patent Office: Days
• 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/335 for accessing specific resources, e.g. using Kerberos tickets
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: G06F 2221/2137 Time limited access, e.g. to a computer or data
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/12 Applying verification of the received information cryptographic mechanisms or cryptographic arrangements for data integrity or data verification H04L9/32

Abstract

A rights-based system is described in which vouchers are employed for creating, managing, distributing, and redeeming rights in digital contexts. A voucher is a digital, possession-based rights representation. An authorization component of the system validates the vouchers and issues corresponding tokens. Access to digital resources is provided in response to presentation of the tokens which are validated by matching voucher refresh values to corresponding values maintained by the system. New refresh values are generated and inserted in the vouchers each time they are redeemed.

Claims

1. (canceled)

2. A computer-implemented method for conducting an anonymous transaction in a distributed rights-based system operating in a network, the distributed rights-based system including a plurality of instances of a first component configured to validate rights objects and issue corresponding tokens, and a second component configured to validate the tokens and provide access to protected resources, the method comprising:

receiving a first rights object representing a right to access a first protected resource, the first protected resource corresponding to a first entity;

transmitting a request for a first access token to at least one of the instances of the first component, the request for the first access token including a copy of the first rights object;

receiving the first access token from the at least one of the instances of the first component in response to validation of the copy of the first rights object, the first access token including a refresh value generated and stored to an instance of a database by the at least one of the instances of the first component;

updating the first rights object with the refresh value, thereby invalidating other existing copies of the first rights object;

storing the first rights object for a second entity;

transmitting a request to access the first protected resource to the second component, the request to access the first protected resource including the first access token; and

accessing the first protected resource in response to validation of the first access token by the second component, thereby effecting transfer of ownership of the first protected resource from the first entity to the second entity without reference to identity information specifically identifying the first entity.

3. The method of claim 2, wherein the first rights object is received from a first wallet component of the rights-based system, the first wallet component being associated with the first entity, and wherein storing the first rights object for the second entity comprises storing the first rights object using a second wallet component of the rights-based system, the second wallet component being configured to enable the second entity to manage a corresponding set of rights objects.

4. The method of claim 3, wherein the first rights object is received from the first wallet component via an escrow component of the rights-based system, the escrow component being configured to coordinate trades of the rights objects.

5. The method of claim 4, further comprising transmitting a copy of a second rights object to the escrow component as part of a trade involving the first rights object and the second rights object.

6. The method of claim 3, further comprising transmitting the first rights object to a third wallet component of the rights-based system, thereby enabling transfer of ownership of the first protected resource from the second entity to the third entity without reference to identity information specifically identifying the second entity.

7. The method of claim 2, wherein the first rights object represents one or both of a currency and an encryption key.

8. The method of claim 2, wherein the protected resource is a digital image, digital video content, a digital object, a digital service, or digital currency.

9. A computer-implemented method for conducting an anonymous transaction in a distributed rights-based system operating in a network, the distributed rights-based system including a plurality of instances of a first component configured to validate rights objects and issue corresponding tokens, a second component configured to validate the tokens and provide access to protected resources, and a plurality of wallet components configured to enable corresponding entities to manage corresponding sets of the rights objects, the method comprising:

transmitting a first rights object from a first wallet component associated with a first entity to a second wallet component associated with a second entity, the first rights object representing a right to access a first protected resource, the right to access the first protected resource being owned by the first entity;

transmitting a request for a first access token from the second wallet component to at least one of the instances of the first component, the request for the first access token including a copy of the first rights object;

validating the copy of the first rights object using the at least one instance of the first component;

generating and storing a refresh value to an instance of a database using the at least one instance of the first component;

transmitting the first access token and the refresh value from the at least one instance of the first component to the second wallet component;

updating the first rights object with the refresh value, thereby invalidating other existing copies of the first rights object, and thereby effecting transfer of ownership of the right to access the first protected resource from the first entity to the second entity without reference to identity information specifically identifying the first entity;

storing the first rights object using the second wallet component;

transmitting a request to access the first protected resource from the second wallet component to the second component, the request to access the first protected resource including the first access token;

validating the first access token using the second component; and

accessing the first protected resource using the second wallet component.

12. The method of claim 9, further comprising transmitting the first rights object from the second wallet component to a third wallet component of the rights-based system, thereby enabling transfer of ownership of the right to access the first protected resource from the second entity to a third entity associated with the third wallet component without reference to identity information specifically identifying the second entity.

13. The method of claim 9, wherein the first rights object represents one or both of a currency and an encryption key.

14. The method of claim 9, wherein the protected resource is a digital image, digital video content, a digital object, a digital service, or digital currency.

10. The method of claim 10, wherein the first rights object is transmitted from the first wallet component to the second wallet component via an escrow component of the rights-based system, the escrow component being configured to coordinate trades of the rights objects.

11. The method of claim 10, further comprising transmitting a copy of a second rights object from the second wallet component to the escrow component as part of a trade involving the first rights object and the second rights object.

15. A computer-implemented method for conducting an anonymous transaction in a distributed rights-based system operating in a network, the distributed rights-based system including at least one instance of a first component configured to validate rights objects and issue corresponding tokens, a second component configured to validate the tokens and provide access to protected resources, a first wallet component configured to enable a first entity to manage a corresponding sets of the rights objects, and a second wallet component configured to enable a second entity to manage a corresponding set of the rights objects, the method comprising:

receiving, with the at least one instance of the first component, a request from the second wallet component for a first access token, the request for the first access token including a copy of a first rights object, the first rights object representing a right to access a first protected resource, the right to access the first protected resource being owned by the first entity;

validating the copy of the first rights object using the at least one instance of the first component;

generating and storing a refresh value in an instance of a database using the at least one instance of the first component;

transmitting the first access token and the refresh value from e at least one instance of the first component to the second wallet component, the refresh value being for use by the second wallet component in updating the first rights object, thereby invalidating other existing copies of the first rights object, and thereby effecting transfer of ownership of the right to access the first protected resource from the first entity to the second entity without reference to identity information specifically identifying the first entity;

receiving, with the second component, a request from the second wallet component to access the first protected resource, the request to access the first protected resource including the first access token;

validating the first access token using the second component; and

providing access by the second wallet component to the first protected resource.

16. The method of claim 15, further comprising:

receiving the first rights object from the first wallet component with an escrow component of the rights-based system, the escrow component being configured to coordinate trades of the rights objects; and

transmitting the first rights object from the escrow component to the second wallet component.

17. The method of claim 16, further comprising receiving a copy of a second rights object from the second wallet component with the escrow component as part of a trade involving the first rights object and the second rights object.

18. The method of claim 15, wherein the first rights object represents one or both of a currency and an encryption key.

19. The method of claim 15, wherein the protected resource is a digital image, digital video content, a digital object, a digital service, or digital currency.