Individualized data sharing

• US 8,463,813 B2
• Filed: 06/03/2010
• Issued: 06/11/2013
• Est. Priority Date: 04/12/2007
• Status: Active Grant

• Current Assignee: YOUnite Inc.
• Original Assignee: YOUnite Inc.
• Inventors: Siress, Anthony, Fitzpatrick, Mark
• Primary Examiner(s): NGUYEN, CAM LINH T
• Application Number:
  US12/793,597
• Publication Number:
  US 20110137946A1
• Time in Patent Office: 1,104 Days
• Field of Search: 707/694, 707/702, 707/781, 707/782, 707/783, 707/784, 707/785, 707/787
• US Class Current: 707/781
• 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 21/6227 where protection concerns the structure of data, e.g. records, types, queries
• CPC Class Codes: H04L 63/101 Access control lists [ACL]
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06

Abstract

Granting permissions for attributes in a distributed data store involves implementing a federated control system. The system can include dynamic permissions granted to content blobs. Acknowledgment of dynamic permissions facilitates identification of users that receive content to enable restoring data on a machine following data loss. Acceptance of dynamic permissions can further facilitate automatic updates to data, or providing content blobs in response to changes in user attributes.

Claims

1. A method executed on a processor, the method comprising:

maintaining a passive permission table indicative of first one or more attributes of a first user to which a second user has permission;

receiving acknowledgement from the second user of acceptance of a dynamic permission to a content blob including second one or more attributes of the first user;

maintaining a dynamic permission table indicative of the second one or more attributes of the first user to which the second user has permission;

maintaining permissions in the dynamic permission table to facilitate reblobulation from the second user of the second one or more attributes associated with the dynamic permissions.

2. The method of claim 1, further comprising the first user storing the first one or more attributes.

3. The method of claim 1, further comprising the first user configuring a risk profile scheme.

4. The method of claim 1, further comprising the first user granting passive permission to the user account associated with the second user for the first one or more attributes.

5. The method of claim 4, wherein the passive permissions are granted in accordance with a risk profile scheme.

6. The method of claim 1, further comprising the first user receiving requests for additional permissions in accordance with a federated control mechanism.

7. The method of claim 1, further comprising the first user storing the second one or more attributes.

8. The method of claim 1, further comprising the first user granting dynamic permission to the second user for the second one or more attributes.

9. The method of claim 1, further comprising the first user sending the dynamic permission to the second user.

10. The method of claim 1, further comprising the first user getting the acknowledgement from the second user of acceptance of the dynamic permission.

11. The method of claim 1, further comprising the first user sending the content blob to the second user.

12. The method of claim 1, further comprising reblobulating a machine of the first user from another machine, the other machine associated with the user account of the second user in accordance with the dynamic permission table.

13. The method of claim 1, further comprising obtaining attributes from users having permission to the attributes.

14. A system comprising:

a permission server;

a passive permission table;

a dynamic permission table;

wherein, in operation;

the permission server receives passive permissions from a first user granting permission to first one or more attributes of the first user;

the permission server saves the passive permissions in the passive permission table;

the permission server receives from a second user acknowledgement of acceptance of a dynamic permission from the first user to second one or more attributes of the first user;

receiving a request from the second user for the second one or more attributes;

facilitating provisioning of the second one or more attributes from the first user to the second user;

receiving a request from the first user for the second one or more attributes;

facilitating reblobulation of the second one or more attributes from the second user to the first user.

15. The system of claim 14, further comprising a client associated with the first user that sends the passive permissions to the permission server.

16. The system of claim 14, further comprising a client associated with the first user that sends the dynamic permissions to the permission server.

17. The system of claim 14, further comprising a client associated with the second user that sends the acknowledgement of acceptance of dynamic permission to the permission server.

18. The system of claim 14, further comprising a client associated with the first user that sends the request for the second one or more attributes.

19. The system of claim 14, further comprising a federated control mechanism.

20. A system comprising:

a processor;

means for implementing a user risk profile scheme;

a federated control mechanism for automatically associating attributes of a first user with third party fields;

means for content blobulation from a first user to a second user, the content blobulation being in accordance with the user risk profile scheme, with the federated control mechanism ensuring proper association between content blob attributes and the third party fields;

means for content reblobulation from the second user to the first user.