Mesh-Managing Data Across A Distributed Set of Devices

• US 20080276181A1
• Filed: 05/04/2007
• Published: 11/06/2008
• Est. Priority Date: 05/04/2007
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Devlin, William D., Moromisato, George P., Ozzie, Raymond E., Andrews, Anthony D., Edelstein, Noah B., Parasnis, Abhay V., Sagar, Akash J.
• Granted Patent: US 7,853,669 B2
• Time in Patent Office: Days
• US Class Current: 715/740
• 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 comprising:

associating a plurality of devices with a user;

storing a core object at a remote location; and

projecting the core object to at least one device of the plurality of devices in a view.

2. The method of claim 1 wherein the core object includes a data file, an application corresponding to the data file, and a user interface.

3. The method of claim 2 wherein the projecting includes:

launching the application corresponding to the data file at the at least one device; and

displaying an interface corresponding to the application responsive to the launching at the at least one device,

wherein the application is stored at a location remote from the at least one device.

4. The method of claim 2 wherein the core object is associated with the user.

5. The method of claim 4 wherein the core object is stored on any of the devices in the plurality of devices.

6. The method of claim 4 wherein the core object is not stored on any device in the plurality of devices.

7. The method of claim 2 wherein the view includes a graphical user interface comprising a representation of the core object.

8. The method of claim 2 further comprising:

receiving an input selection of a data file in the core object from a first device in the plurality of devices; and

launching on the first device an application in the core object corresponding to the data file based on the user,

wherein the launched application is stored remotely from the first device.

9. The method of claim 8 further comprising:

displaying on the first device the view containing a representation of the core object; and

displaying a user interface corresponding to the data file responsive to the launching,

wherein the application is not stored on the at least one device.

10. The method of claim 9 further comprising:

receiving a user identifier corresponding to the user; and

determining a match between the user and the core object;

wherein the launching includes launching the application on the first device based on determining the match.

11. The method of claim 10 wherein the launching includes launching the application only if a match is determined between the user and the core object.

12. The method of claim 9 further comprising:

receiving a selection of the data file from a second device in the plurality of devices; and

launching on the second device an application in the core object corresponding to the data file,

wherein the launched application is stored remotely from the first device and the second device.

13. The method of claim 12 further comprising:

receiving a user identifier corresponding to the user from the second device; and

determining a match between the user and the core object based on the user identifier,

wherein launching the application on the second device includes launching the application on the second device based on the determining.

14. The method of claim 13 wherein launching the application on the second device includes launching the application on the second device only if a match is determined between the user and the core object.

15. A method of accessing data comprising:

projecting a view to a first device in a plurality of devices, the view containing a representation of the plurality of devices;

receiving a request for a data file on the first device, the data file being associated with a corresponding application, at least one of the data file or the corresponding application not being stored on the first device;

determining a location of the at least one of the data file or the corresponding application not stored on the first device; and

launching the data file and the corresponding application at the first device from the determined location.

16. The method of claim 15 wherein the corresponding application is not stored on the first device, the step of launching including launching the corresponding application at the first device.

17. The method of claim 16 wherein the corresponding application is not stored on any device in the plurality of devices.

18. The method of claim 16 further comprising projecting the view to a second device in the plurality of devices, the second device not storing at least one of the data file or the corresponding application.

19. The method of claim 18 further comprising:

receiving a user command at the second device; and

modifying the data file at the second device responsive to the user command;

automatically modifying the data file at the first device responsive to modifying the data file at the second device.

20. A system for storing a core object associated with a user comprising a plurality of devices, the core object being stored remotely from the plurality of devices and comprising a data file, an application corresponding to the data file, and a user interface, wherein any one device in the plurality of devices receives a view of the core object and launches the data file and corresponding application responsive to an input command via the view of the core object.