DISTRIBUTED MANAGEMENT FRAMEWORK FOR PERSONAL ATTRIBUTES

• US 20090125523A1
• Filed: 11/07/2008
• Published: 05/14/2009
• Est. Priority Date: 04/04/2005
• Status: Abandoned Application

• Current Assignee: YOUnite Inc.
• Original Assignee: YOUnite Inc.
• Inventors: Siress, Anthony, Fitzpatrick, Mark
• Application Number:
  US12/267,520
• Publication Number:
  US 20090125523A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/11 File system administration, e.g. details of archiving or snapshots file system backup G06F11/14
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 21/60 Protecting data
• 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/6245 Protecting personal data, e.g. for financial or medical purposes
• CPC Class Codes: G06F 2221/2141 Access rights, e.g. capability lists, access control lists, access tables, access matrices
• CPC Class Codes: G06F 2221/2145 Inheriting rights or properties, e.g., propagation of permissions or restrictions within a hierarchy
• CPC Class Codes: Y10S 707/99939 Privileged access

Abstract

A technique for distributed management of attributes includes propagating attributes based upon attribute-granularity permissions. An example of a system according to the technique may include a server, coupled to a first client and a second client, that includes a module that receives attribute data from the first client; a permissions database where first permissions associated with the first client are set at the individual attribute level for the second client; an engine for updating the permissions database and for validating the first permissions for the second client; and an engine for distributing first client updates based on validated permissions to destinations associated with the one or more second destination stores.

Claims

1. A system comprising:

a first client that includes;

a first attribute data store;

one or more first destination stores;

an engine for identifying attribute updates to the first data store, for generating a permissions-based transaction including the data associated with the updates, and for transmitting the updated data associated with the permissions-based transaction;

a second client that includes;

a second attribute data store;

one or more second destination stores;

an engine for identifying permissions-based updates to the first data store, generating a transaction including the data associated with the permissions-based updates, and for transmitting the data associated with the permissions-based updates;

a server, coupled to the first client and the second client, that includes;

a module that receives attribute data from the first client;

a permissions database where first permissions associated with the first client are set at the individual attribute level for the second client;

an engine for updating the permissions database and for validating the first permissions for the second client;

an engine for distributing first client updates based on validated permissions to destinations associated with the one or more second destination stores.

2. The system of claim 1, wherein the first client further includes an address book plugin.

3. The system of claim 1, wherein the first client further includes a personal attribute record (PAR) database.

4. The system of claim 1, wherein the first client further includes a shared PIM database.

5. The system of claim 1, wherein the second client further includes an address book plugin.

6. The system of claim 1, wherein the second client further includes a personal attribute record (PAR) database.

7. The system of claim 1, wherein the second client further includes a shared PIM database.

8. The system of claim 1, wherein the first client further includes a transaction history database.

9. The system of claim 1, wherein the second client further includes a transaction history database.

10. The system of claim 1, wherein the first client further includes an installer that includes PIM plugins.

11. The system of claim 1, wherein the second client further includes an installer that includes PIM plugins.