Mesh-managing data across a distributed set of devices

• US 9,135,279 B2
• Filed: 12/20/2012
• Issued: 09/15/2015
• Est. Priority Date: 05/04/2007
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Moromisato, George P., Edelstein, Noah B., Parasnis, Abhay V., Andrews, Anthony D., Ozzie, Raymond E., Devlin, William D., Sagar, Akash J.
• Primary Examiner(s): Moise, Emmanuel L
• Assistant Examiner(s): KOROBOV, VITALI A
• Application Number:
  US13/723,179
• Publication Number:
  US 20130110801A1
• Time in Patent Office: 999 Days
• Field of Search: 709/203, 709/204, 709/217, 709/205, 719/331
• US Class Current: 1/1
• CPC Class Codes: G06F 16/178 Techniques for file synchronisation in file systems
• 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: H04L 67/025 for remote control or remote monitoring of applications
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching

Abstract

Data files, applications and/or corresponding user interfaces may be accessed at a device that collaborates in a mesh. The mesh may include any number or type of devices that collaborate in a network. Data, applications and/or corresponding user interfaces may be stored within a core object that may be shared over the mesh. Information in the core object may be identified with a corresponding user such that a user may use any collaborating device in the mesh to access the information. In one example, the information is stored remotely from a device used to access the information. A remote source may store the desired information or may determine the storage location of the desired information in the mesh and may further provide the desired information to a corresponding user.

Claims

1. A method performed on any client computing device of a plurality of client computing devices that are each associated with a user, the method comprising:

receiving a request to access a core object that is stored at any of a plurality of storage locations that includes cloud storage and each of the plurality of client computing devices, and where the core object is owned by the user, and where the core object comprises data, an application corresponding to the data, and a user interface corresponding to the application;

determining, in response to the received request, a storage location of the plurality of storage locations at which the core object is stored; and

accessing, by the user via the any of the plurality of client computing devices, the stored core object from the determined storage location.

2. The method of claim 1 where a representation of at least a portion of the core object is available to the user via each of the plurality of client computing devices regardless of whether or not the core object itself is stored on the each of the plurality of client computing devices.

3. The method of claim 1 where the accessing is based at least in part on an identifier of the user.

4. The method of claim 1 where the accessing includes executing the application program.

5. The method of claim 4 where the determined storage location is distinct from the any client computing device.

6. At least one computer storage hardware device storing instructions that, when executed by any client computing device of a plurality of client computing devices that are each associated with a user, cause the any computing device to perform a method comprising:

receiving a request to access a core object that is stored at any of a plurality of storage locations that includes cloud storage and each of the plurality of client computing devices, and where the core object is owned by the user, and where the core object comprises data, an application corresponding to the data, and a user interface corresponding to the application;

determining, in response to the received request, a storage location of the plurality of storage locations at which the core object is stored; and

accessing, by the user via the any of the plurality of client computing devices, the stored core object from the determined storage location.

7. The at least one computer storage hardware device of claim 6 where a representation of at least a portion of the core object is available to the user via each of the plurality of client computing devices regardless of whether or not the core object itself is stored on the each of the plurality of client computing devices.

8. The at least one computer storage hardware device of claim 6 where the accessing is based at least in part on an identifier of the user.

9. The at least one computer storage hardware device of claim 6 where the accessing includes executing the application program.

10. The at least one computer storage hardware device of claim 9 where the determined storage location is distinct from the any client computing device.

11. Any client computing device of a plurality of client computing devices that are each associated with at least one user, the any computing device comprising at least one software module, the any client computing device and the at least one software module together configured for performing actions comprising:

receiving a request to access a core object that is stored at any of a plurality of storage locations that includes cloud storage and each of the plurality of client computing devices, and where the core object is owned by the user, and where the core object comprises data, an application corresponding to the data, and a user interface corresponding to the application;

determining, in response to the received request, a storage location of the plurality of storage locations at which the core object is stored; and

accessing, by the user via the any of the plurality of client computing devices, the stored core object from the determined storage location.

12. The any computing device of claim 11 where a representation of at least a portion of the core object is available to the user via each of the plurality of client computing devices regardless of whether or not the core object itself is stored on the each of the plurality of client computing devices.

13. The any computing device of claim 11 where the accessing is based at least in part on an identifier of the user.

14. The any computing device of claim 11 where the accessing includes executing the application program, or where the determined storage location is distinct from the any client computing device.