Distributed management framework for personal attributes
AssigneeYOUnite, Inc.
InventorsMark Fitzpatrick, Anthony Siress
Life of this patent
Estimating the term…
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.
Claims20
A method comprising:
- maintaining first attributes associated with a first entity of a plurality of entities and second attributes associated with a second entity of the plurality of entities;
- linking the first entity with a second entity;
- providing first destinations, associated with the first entity, for the second attributes;
- granting first permissions for the first attributes to the second entity;
- providing second destinations, associated with the second entity, for the first attributes;
- granting second permissions for the second attributes to the first entity;
- facilitating the propagation of shared attributes to the destinations through the permissions;
- managing subsequent changes of attributes to create a syndicated distributed secure data exchange.
A method comprising:
- granting to a second entity first permissions for first attributes associated with a first entity;
- granting to the first entity second permissions for second attributes associated with the second entity;
- facilitating the propagation of shared attributes through permissions;
- changing first permissions for the first attributes to third permissions for third attributes associated with the first entity;
- recalling propagated shared attributes in accordance with the third permissions.
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 he 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.
Dependencies are inferred from the claim text.