Security in peer to peer synchronization applications

• US 20070067349A1
• Filed: 08/24/2005
• Published: 03/22/2007
• Est. Priority Date: 08/24/2005
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Novik, Lev, Jhaveri, Vivek
• Granted Patent: US 7,930,346 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/1834 implemented based on peer-to-peer networks, e.g. gnutella p2p communication protocols H04L67/104
• CPC Class Codes: G06F 16/256 in federated or virtual databases
• CPC Class Codes: G06F 16/273 Asynchronous replication or reconciliation
• 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: H04L 63/101 Access control lists [ACL]

Abstract

The claimed subject matter provides a system and/or a method that facilitates synchronizing data within a data storage system. An interface component can leverage a synchronization technique within the data storage system. A sync component can provide a secure peer to peer data synchronization based at least in part upon the synchronization technique to allow a tiered access to the synchronized data.

Claims

1. A system that facilitates synchronizing data within a data storage system, comprising:

an interface component that leverages a synchronization technique within the data storage system; and

a sync component that provides a secure peer to peer data synchronization based at least in part upon the synchronization technique to allow at least one user a tiered access to the synchronized data.

2. The system of claim 1, the synchronization technique utilizes a track component that captures a data change to an entity within the data storage system to facilitate synchronizing data between two disparate systems maintaining sets of data.

3. The system of claim 1, the tiered access includes at least one role and associated access permission.

4. The system of claim 3, the role and associated access permission is one of the following:

1) a manager that can read data, write data, modify data, add data, invite a user, and revoke a permission;

     2) a writer that can read data, write data, modify data, and add data;

     3) a reader that can read data; and

     4) a contributor that can read data and add data.

5. The system of claim 1, the secure peer to peer data synchronization is a synchronized community with at least one replica, wherein the replica is a synchronized folder that belongs to a user within the community.

6. The system of claim 1, further comprising manual sync component that allows a user to manual synchronize data.

7. The system of claim 1, further comprising an automatic synchronization component that provides an automatic synchronization of data elected to the peer to peer data synchronization.

8. The system of claim 1, further comprising a user sync manager component that provides at least one of the following:

a synchronized relationship;

a synchronized container;

an invitation to a user to participate in synchronization;

an acceptance of an invitation;

a participation in a community;

a removal of a user; and

a maintenance of a membership list.

9. The system of claim 1, the sync component implements a management of a complex synchronization relationship based a synchronization technology.

10. The system of claim 9, the complex synchronization relationship is at least one of a setup;

a tear-down; and

a security management.

11. The system of claim 9, the synchronization technology relates to at least one of a suitable data synchronization technique;

and a synchronization technique related to the data storage system.

12. The system of claim 1, further comprising a peer to peer sync application that runs as a local system to expose at least one operation to an application.

13. The system of claim 12, the operation can be at least one of the following:

create a share at a specified container;

create a permission to a container;

add a permission to a container;

validate an owner of a container;

set a group membership based on a list; and

delete a share created on a container.

14. The system of claim 12, the peer to peer sync application runs live as an application to schedule synchronization and provide progress notification.

15. The system of claim 1, the data storage system is a database-based system that defines at least one of an item, a sub-item, a property, and a relationship to represent information as a complex type.

16. The system of claim 15, the data storage system includes at least one of a container structure, and an item that is an instance of a type and the item can be stored within the data storage system in a single global extent of items.

17. A computer-implemented method that facilitates synchronizing data within a data storage system, comprising:

identifying data within a data storage system that is to be synchronized;

inviting at least one user to participate with a synchronization relationship; and

assigning at least one accessibility level to the at least one user within the synchronization relationship.

18. The method of claim 17, further comprising:

leveraging an existing synchronization technique within the data storage system; and

creating at least one replica within a peer to peer synchronization community.

19. The method of claim 18, further comprising the replica announcing at least one of a presence in the synchronization community;

and an intention to depart the synchronization community by synchronizing a request.

20. A computer-implemented system that facilitates synchronizing data within a data storage system, comprising:

means for leveraging a synchronization technique within the data storage system; and

means for providing a secure peer to peer data synchronization based at least in part upon the synchronization technique to allow multiple users a tiered access to the synchronized data.