Computing system for managing data

• US 9,172,708 B2
• Filed: 06/23/2011
• Issued: 10/27/2015
• Est. Priority Date: 06/23/2011
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Kimchi, Gur, Barga, Roger, Gupta, Vinay, Apter, Zachary, Paparizos, Stelios
• Primary Examiner(s): Dalencourt, Yves
• Application Number:
  US13/167,461
• Publication Number:
  US 20120331090A1
• Time in Patent Office: 1,587 Days
• Field of Search: 709201-226, 707204-222, 726 56- 65, 726/115
• US Class Current: 1/1
• CPC Class Codes: G06Q 30/0267 Wireless devices
• 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/104 Grouping of entities
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/1046 Joining mechanisms
• CPC Class Codes: H04L 67/1068 Discovery involving direct consultation or announcement among potential requesting and potential source peers

Abstract

Various embodiments are described for systems and methods for managing data. The system may include a device group configured for peer-to-peer communications, the device group including a computing device and one or more peer computing devices. The system includes a cross device application programming interface (API) that is implemented as a device group API client executed on the computing device and each of the peer computing devices. Each device group API client includes a permissions module that is configured to determine whether a request satisfies a device-group-specific permission for access to data stored on any device associated with the device group. Upon authorization of the request, a file storage module is configured to retrieve and output the requested file.

Claims

1. A computing system for managing data comprising, a cross device application programming interface (API) including:

a device group API client executed on a computing device associated with a device group, the API client including;

a device discovery module configured to discover one or more peer computing devices associated with the device group;

a peer-to-peer (P2P) module configured to engage in P2P communications with each of the one or more peer computing devices of the device group via respective device group API clients executed on the one or more peer computing devices;

a file storage module configured to enable the device group API client to access files stored in a distributed file store locally on the computing device and/or remotely on the one or more peer computing devices using communications sent via the P2P module, the file storage module configured to receive a request from a computer program, via the device group API client, to access a requested file stored in the distributed file store;

a permissions module configured to determine whether the request satisfies a device-group-specific permission for access permission of data stored on any device associated with the device group, and if so, to authorize the request to access the requested file, else to deny the request to access the requested file; and

upon authorization of the request by the permissions module, the file storage module being configured to retrieve the requested file from the distributed file store and output the requested file to the computer program;

wherein the device discovery module is configured to dynamically discover a non-member computing device not presently associated with the device group that satisfies at least one device group criterion, and to add the non-member computing device to the device group.

2. The computing system of claim 1, wherein the device group is a first device group having a first set of device-group-specific permissions, and the device group API client is a first device group API client, the permissions module of the first device group API client configured to determine whether the request satisfies the first set of device-group-specific permissions, and if so, to authorize the request to access the requested file, else to deny the request to access the requested file, the system further comprising a second device group having a second set of device-group-specific permissions, the computing device being a member of the second device group and including a second device group API client that includes a permissions module, the permissions module of the second device group API client configured to determine whether the request satisfies the second set of device-group-specific permissions, and if so, to authorize the request to access the requested file, else to deny the request to access the requested file.

3. The computing system of claim 1, wherein the requested file comprises user data from at least one of a plurality of user data categories, the user data categories selected from the group consisting of application usage history, browser history, media data, contact data, calendar data and social network data, and the permissions module is configured to allow a user to set a privacy setting for each of the user data categories.

4. The computing system of claim 3, wherein the device group API client includes an ad module configured to gather aggregated user data from the computing device and at least one of the peer computing devices, send an ad request including the aggregated user data to an ad engine on a remote server, the aggregated user data authorized to be sent according to the device-group-specific permission, the ad module also configured to receive an ad in response to the ad request, and display the ad on the computing device and/or the at least one of the peer computing devices.

5. The computing system of claim 1, wherein the permissions module is further configured to grant a partial access privilege to enable access to only a portion of the data in a file, and/or to enable access to the data in the file only for authorized uses, if the request satisfies the device-group-specific permission.

6. The computing system of claim 1, wherein the computer program is a media player and the requested file is a media file, and the device group API client includes a search module configured to search for the media file in the distributed file store, and, if the request satisfies the device-group-specific permission, stream the requested file to the media player via the P2P module.

7. The computing system of claim 1, wherein the at least one device group criterion comprises a location of the non-member computing device being within a pre-defined range.

8. The computing system of claim 1, wherein the at least one device group criterion comprises a social distance of a user of the non-member computing device being within a pre-defined distance.

9. The computing system of claim 1, wherein the at least one device group criterion comprises an ownership designation of the non-member computing device being associated with a user of the computing device or a user of one of the peer computing devices.

10. A method for managing data, the method comprising, at a computing device:

forming a device group that includes the computing device and at least one peer computing device;

establishing peer-to-peer communication between the computing device and the at least one peer computing device;

storing files in a distributed file store locally on the computing device and/or remotely on the at least one peer computing device;

receiving a request from a computer program to access a requested file stored in the distributed file store;

determining whether the request satisfies a device-group-specific permission for access permission of data stored on any device associated with the device group, and if so, then authorizing the request to access the requested file, else denying the request to access the requested file;

if the request is authorized, then retrieving the requested file from the distributed file store and outputting the requested file to the computer program; and

dynamically discovering a non-member computing device that is not presently associated with the device group, and that satisfies at least one device group criterion, and adding the non-member computing device to the device group.

11. The method of claim 10, wherein the request is a first request, the requested file is a first requested file, the distributed file store is a first distributed file store, and the device group is a first device group having a first set of device-group-specific permissions for the first device group, the method further comprising:

forming a second device group of which the computing device is a member, the second device group having a second set of device-group-specific permissions for access permission of data stored on any device associated with the second device group;

storing files in a second distributed file store locally on the computing device and/or remotely on a peer computing device;

receiving a second request from the computer program to access a second requested file stored in the second distributed file store; and

determining whether the second request satisfies the second set of device-group-specific permissions and if so, then authorizing the second request to access the second requested file, else denying the second request to access the second requested file.

12. The method of claim 10, wherein the requested file comprises user data from at least one of a plurality of user data categories, the user data categories selected from the group consisting of application usage history, browser history, media data, contact data, calendar data and social network data, the method further comprising setting a privacy setting for each of the user data categories.

13. The method of claim 10, further comprising:

gathering aggregated user data from the computing device and the at least one peer computing device;

authorizing the aggregated user data to be sent according to the device-group-specific permission;

sending an ad request including the aggregated user data to an ad engine on a remote server;

receiving the ad in response to the ad request; and

displaying the ad on the computing device and/or the peer computing device.

14. The method of claim 10, wherein the requested file is a media file, further comprising:

receiving the request from a media player;

searching for the media file in the distributed file store; and

if the request satisfies the device-group-specific permission, then streaming the media file to the media player.

15. The method of claim 10, wherein the at least one device group criterion comprises a location of the non-member computing device being within a pre-defined range.

16. The method of claim 10, wherein the at least one device group criterion comprises a social distance of a user of the non-member computing device being within a pre-defined distance.

17. The computing system of claim 10, wherein the at least one device group criterion comprises an ownership designation of the non-member computing device being associated with a user of the computing device and/or the at least one peer computing device.

18. A method for managing data, the method comprising, at a computing device:

forming a first device group that includes the computing device and a first peer computing device;

forming a second device group that includes the computing device and a second peer computing device;

establishing peer-to-peer communication between the computing device and the first peer computing device;

establishing peer-to-peer communication between the computing device and the second peer computing device;

storing files in a first distributed file store locally on the computing device and remotely on the first peer computing device;

storing files in a second distributed file store locally on the computing device and remotely on the second peer computing device;

receiving a request from a computer program to access a requested file located in the first distributed file store or the second distributed file store;

searching for the requested file in the first distributed file store and the second distributed file store;

if the requested file is located in the first distributed file store, then determining whether the request satisfies a first device-group-specific permission for access permission of data stored on any device associated with the first device group, and if so, then authorizing the request to access the requested file, else denying the request to access the requested file;

if the requested file is located in the second distributed file store, then determining whether the request satisfies a second device-group-specific permission for access permission of data stored on any device associated with the second device group, and if so, then authorizing the request to access the requested file, else denying the request to access the requested file; and

if the request is authorized, then retrieving the requested file from the first distributed file store or the second distributed file store, and outputting the requested file to the computer program; and

dynamically discovering a non-member computing device that is not presently associated with the first device group or the second device group, and that satisfies at least one device group criterion, and adding the non-member computing device to the first device group.