Browse Prior Art Database

Method to Capture and Recover Task Oriented Snapshots

IP.com Disclosure Number: IPCOM000237426D
Publication Date: 2014-Jun-18

Publishing Venue

The IP.com Prior Art Database

Abstract

The disclosure invents a method to generate, maintain and restore task oriented snapshots. A snapshot contains one to many applications and services.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 35% of the total text.

Page 01 of 13

Method to Capture and Recover Task Oriented Snapshots

The people have to do multi-tasking very often In their daily work. However multi-tasking can be in-efficient, because of the overhead of task switching. For example, the user is working on Task A, and the user has different applications and service opened in personal computer or mobile devices, and each application/service in a certain state with some content. Then the user has to switch to Task Bat this moment. After working on Task B for sometime, the user has a different set of applications orservices opened and they are in their own states and content. Similarly, the user might have even more tasks, Task C, Task D ….etc. Imagine when the user has many different tasks that the user has to do in the same day, the user could have many applications and services opened, each in its own state with its content for each task. It is very likely the user was not able to finish all of them till the end of day, and the user has to shut down personal computer or mobile device before the user leave office. It is also possible before end of the working day, the user just wants closed some applications and servcies to release resource on personal computer or mobile device, because the user is not using it for some time.

Now the problem occurs. After working on Task B for some time, the user have to switch back to Task A. However the user has closed all applications/services associated with Task A. The user has to re-open them one by one, and look for the state and content I left out last time to resume the work on Task A. This is obviously overhead of task switching. How can the user quickly resume all application/services in the previous state and content that they was left at?

There are various snapshot solutions, but they only address the problem of system level or application/service level snapshots. They can not solve the problem of task-switching overhead. This invention is task oriented snapshot, it largely minimizes the overhead of task-switching.

To solve above problems, this disclosure invents a method to avoid such overhead of task switching.

In this disclosure a system maintains a task database, which marks current status of each application/service associated with each task. This is called a snapshot of the task, which keeps status of all the applications/services the user has used in performing a task. Then by reading this task database, the way invented in this disclosure is able to quickly re-launch all the applications/services with the wanted state and content, when the user wants to continue working on that task some time later.

The advantage of this invention is it can capture and recover task oriented snapshots, by maintaining a task table (either saved in XML files, or store in database)

This section describes the system architecture and workflow to implement the functions mentioned above. Figure 1 outlines the system architecture. The details are described in th...