JP2013152545A - Application execution device, system and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To reduce battery consumption of a mobile terminal and accelerate processing for an application which is executed in the mobile terminal without modification of the application itself.SOLUTION: Application data indicating a memory state and a status state when executing an application is shared between a mobile terminal 11 and a server 20. An execution of an application 12 in the mobile terminal 11 ends when an operation end is inputted for the mobile terminal 11, and an execution of an application 22 starts in a virtual mobile terminal 21 of the server 20 on the basis of the shared application data. The execution of the application 22 in the virtual mobile terminal 21 ends when an operation start is inputted for the mobile terminal 11, and the execution of the application 12 starts in the mobile terminal 11 on the shared application data.

Description

  The present invention relates to execution of an application program in a mobile (mobile) terminal such as a smartphone or a tablet terminal, and particularly relates to a technology that enables background processing of an application executed on a mobile terminal to be executed by a server.

  Mobile terminals such as smartphones and tablet terminals operate with power from a secondary battery (battery) such as a lithium-ion battery, and various applications (AP; applications) under process management and memory management by a mobile OS (operating system) (Also called an application program). In a typical mobile terminal, a screen of one application is displayed on the display of the terminal as a front-end job, but at the same time, background processing of various applications can be executed. For example, in a mobile terminal using an Android (registered trademark) OS that is one of mobile OSs, a component called Activity corresponding to GUI (graphical user interface) processing of an application is mounted and screen processing is executed. Even after the screen of the application disappears from the display, processing can continue in the background.

  FIG. 9 is a diagram for explaining background processing of an application in a mobile terminal. In the example shown here, the application 12 executed in the mobile terminal 11 connects to the website 90 via the network, acquires information from the website 90, performs processing, and displays the processing result on the screen. It is. The mobile terminal 11 is also provided with a storage (storage device) 13 including a memory card such as a flash memory.

  When the application 12 is activated by a user operation (step 101), the application 12 is executed as a front-end job, accesses the website 90 to acquire information, and displays the processing result on the screen. The user can use this application 12 (step 102). When the end of the user operation is input (step 103), the application 12 disappears from the display screen of the mobile terminal 11, but continues the background processing and continues to acquire information from the website 90 (step). 104). The user operation end is input by, for example, selecting an end in the GUI of the application or starting another application. Information acquisition in the background processing is performed by, for example, a polling operation. Thereafter, when the user performs an operation of resuming the application (step 105), the application 12 again performs processing for acquiring information from the website 90 and displaying the result on the screen as a front-end job (step 106). This state continues until the next user operation end (step 107) is input.

  As the number of applications installed on mobile terminals increases, the amount of background processing to be executed also increases, causing problems such as acceleration of battery consumption of mobile terminals and reduction of processing speed. In general, in a mobile OS, a special program called a task manager that controls the execution of an application is implemented (for example, see Non-Patent Document 1), and the operation (for example, start and stop) of the application is controlled by the task manager. It has become so. An application that is assumed to be installed on a mobile terminal is called a mobile application. When a general mobile application stops the operation of the application completely, in order to be able to start the application again from the state immediately before the stop, the data of the execution memory at the time of the stop (so-called memory image) ) And data persistence processing for saving application status information in the storage 13, and data restoration processing for expanding the data saved in the storage 13 to the execution memory and reading the status information is performed when the application is resumed. It is configured as follows. Hereinafter, the execution memory data and the status information are collectively referred to as application data. By executing the persistence process and the restoration process, when the application is resumed, the memory state and status state are the same as when the application was stopped. Therefore, the application resumes execution from the state at the time when the application was stopped. .

  FIG. 10 is a diagram illustrating execution of an application in a mobile terminal including a task manager. The application 12 executed on the mobile terminal 11 is the same as that described in FIG. The mobile terminal 11 includes a storage 13 and a task manager 14. When the application 12 is activated by a user operation (step 111) and executed as a front-end job, the application 12 acquires information from the website 90 and displays a processing result on the screen. Use is enabled (step 112). When the user operation end is input (step 113), the task manager 14 detects the user operation end input (step 114) and ends the operation of the application 12 (step 115). By the data perpetuation process, the application data is stored in the storage 13 (step 116).

  Thereafter, when an instruction to restart the application 12 is input by a user operation (step 117), the application data is restored from the storage 13 (step 118), and the application 12 resumes its operation from the state previously ended in step 115. Then, information acquisition from the website 90 is executed (step 119). The application 12 continues execution until the next user operation end (step 120) is input.

  However, when the application 12 is completely terminated by the task manager 14, background processing is not performed, so that power consumption can be reduced, but the latest information is not given to the application 12 when the application 12 is restarted. . For this reason, all of the information generated during the period when the application 12 was stopped must be acquired from the website 90, and the processing for the acquired data must be performed in a lump. As a result, the speed feeling peculiar to the mobile application is lost, and in particular, it takes time to display the latest data.

Hiroto Kaneko, “Measures against running out of battery for smartphones and mobile phones”, Nikkei PC, July 11, 2011, 62-69

  In a mobile terminal, when background processing of an application is executed, battery consumption is accelerated correspondingly, and problems such as a decrease in processing speed of an application running on the front end occur. On the other hand, if the application is stopped without executing the background processing by the task manager or the like, a large amount of processing must be executed when the application is restarted. This causes a problem.

  An object of the present invention is to provide an application execution device, system, and program that can reduce battery consumption in a mobile terminal and achieve high-speed processing of an application without modifying the application itself.

  A first application execution device of the present invention performs application state control in an application execution device that executes an application operable on a mobile OS, and stores application data indicating a memory state and status information when the application is executed. An application based on application data that is shared with other application execution devices and ends the application on the application execution device and shared with the other application execution devices when an application operation end is input. Is provided, and a cooperation function unit that starts the application based on the shared application data when an operation start of the application is input is provided.

  The second application execution device of the present invention is an application execution device that virtually executes an application operable on the mobile OS, performs application state control, and indicates application data indicating a memory state and status information when the application is executed. Is shared with other application execution devices, the application is started based on the shared application data when there is a first notification from the other application execution devices, and the It is characterized by having a cooperation function means for ending the execution of the application when the notification of 2 is received.

  An application execution system according to the present invention is an application execution system in which a first processing apparatus that executes an application operable on a mobile OS and a second processing apparatus are connected via a network. The application state is controlled in the first processing device, the application data indicating the memory state and status information at the time of execution of the application is shared with the second processing device, and the operation end of the application is input The first processing device is terminated, the first notification is transmitted to the second processing device, and when the application operation start is input, the second processing device is The first processing device based on the shared application data and transmitting the second notification The second processing device performs state control relating to virtual execution of the application in the second processing device, and transfers application data to and from the first processing device. And when the first notification is received from the first processing device, the application is started in the second processing device based on the shared application data, and the second notification is received from the first processing device. And a second link function means for ending the execution of the application in the second processing apparatus when there is a second link.

  In the present invention, the application is modified by adopting the above configuration and enabling application data to be shared between the application execution device and another application execution device or between the mobile terminal and the server. In addition, the background processing of the application can be seamlessly shifted to the server side, and battery consumption on the mobile terminal side can be reduced. In particular, when background processing is processing such as polling communication that performs communication regardless of the presence or absence of data, battery consumption of the mobile terminal can be greatly reduced. Further, according to the present invention, the restart of the application on the mobile terminal can be performed at the same speed as the operation in the background application.

It is a block diagram which shows an example of the whole structure of the system with which the application execution method of one Embodiment of this invention is applied. (A) is a block diagram showing a logical configuration of a mobile terminal, and (b) is a block diagram showing a logical configuration of a virtual mobile terminal mounted on a server. It is a figure explaining the seamless transfer of application execution from a mobile terminal to a virtual mobile terminal. It is a sequence diagram explaining the process of seamless transfer of application execution from a mobile terminal to a virtual mobile terminal. It is a figure explaining the seamless transfer of application execution from a virtual mobile terminal to a mobile terminal. It is a sequence diagram explaining the process of seamless transfer of application execution from a virtual mobile terminal to a mobile terminal. It is a figure explaining the example of mounting of a mobile terminal and a virtual mobile terminal. It is a figure which shows an example of an accounting model. It is a sequence diagram which shows the background process of the application in a mobile terminal. It is a sequence diagram which shows application execution in a mobile terminal provided with a task manager.

  Next, embodiments of the present invention will be described with reference to the drawings.

  FIG. 1 shows the overall configuration of a system to which an application execution method according to an embodiment of the present invention is applied. A plurality of mobile terminals 11 are connected to the network 10. Each mobile terminal 11 is a device having a physical entity that is driven by a secondary battery and connected to the network 10 wirelessly. The network 10 is also connected to a server 20 and a website 90 arranged in a data center or the like. In the server 20, a plurality of virtual mobile terminals 21 are constructed as a virtual execution environment so as to have a one-to-one relationship with the mobile terminals 11, for example. The server 20 here can be configured as, for example, on a cloud platform. In the present embodiment, the application (AP) background processing in the mobile terminal 11 is executed seamlessly with the virtual mobile terminal 21 on the server 20, and further between the mobile terminal 11 and the virtual mobile terminal 21. By constructing the data sharing mechanism, the background processing on the mobile terminal 11 is suppressed and the battery consumption of the mobile terminal 11 is reduced. Further, since the background processing itself is executed by the virtual mobile terminal 21 and the result is made available to the mobile terminal 11 by data sharing, the latest data can be used immediately when the application execution on the mobile terminal 11 is resumed. As a result, the processing speed of the application is improved and the application can be started at high speed.

  FIG. 2A shows an example of the logical configuration of the mobile terminal 11. The mobile terminal 11 is controlled by a mobile OS (not shown), and an application 12 that operates on the mobile OS is installed. In addition, a cooperation function 15 for seamlessly executing background processing between the mobile terminal 11 and the virtual mobile terminal 21 to realize data sharing is implemented in the mobile terminal 11 as a program independent of the application 12. . The mobile terminal 11 is also provided with a storage (storage device) 13 including a memory card such as a flash memory as a storage device controlled by the mobile OS. The storage 13 may be one in which a file system in the mobile OS is constructed, or one that stores data or the like in another form.

  Here, the cooperation function 15 will be described. The linkage function 15 can be realized as one of libraries in the mobile OS, for example, and is an extension of the task manager function in the mobile terminal shown in FIG. The linkage function 15 includes (1) a function for grasping whether the operation state of the application 12 is a front-end operation, a background operation, or an end operation, and (2) an application for instructing the application 12 to start and end A state control function, (3) a function of acquiring application data for the persistence processing of the application 12, and (4) data sharing or data synchronization between the mobile terminal 11 and the virtual mobile terminal 21 is actually executed. A storage sharing function 16 that performs the processing, and (5) a data reflection function that writes application data to the storage 13 for the persistence process. These functions are each implemented as a function block in the linkage function 15.

  FIG. 2B shows a logical configuration of the virtual mobile terminal 21 constructed in the server 20. The virtual mobile terminal 21 implements functions equivalent to the mobile terminal 11 under a virtual execution environment, and is controlled by an OS equivalent to the mobile OS of the mobile terminal 11, and an application 22 that runs on this OS is installed. Has been. The application 22 is the same as the application 12 of the mobile terminal 11 (at least executes the same process regarding the background process). In addition, the virtual mobile terminal 21 cooperates with the cooperation function 15 of the mobile terminal 11 to seamlessly execute background processing between the mobile terminal 11 and the virtual mobile terminal 21 to realize data sharing 25. However, it is implemented as a program independent of the application 22. The linkage function 25 also includes a storage sharing function 26 that actually executes data synchronization or data sharing between the mobile terminal 11 and the virtual mobile terminal 21. The storage 23 is for storing data including application data in the virtual mobile terminal 21, and a file system in the OS in the virtual mobile terminal 21 may be constructed, or data in other forms Etc. may be stored. For example, the storage 23 is secured as a storage area in an HDD (hard disk device) provided in the server 20.

  The linkage function 25 is the same as the linkage function 15 but is implemented in the virtual mobile terminal 21 that performs only background processing of the application, and thus includes functions related to the front-end operation of the application. You don't have to.

  Next, the operation of executing the application in the present embodiment will be described with reference to FIGS. Here, the applications 12 and 22 are both in a case where a perpetuation process for writing application data to the storages 13 and 23 is instructed from the cooperation functions 15 and 25 and a start-up is instructed. It is assumed that a restoration process for reading application data from the storages 13 and 23 can be executed. Currently, an application operating under a mobile OS is generally provided with a persistence processing and restoration processing function. Here, as shown in FIG. 9 and FIG. 10, an example is an application that connects to the website 90 via the network, acquires information from the website 90, performs processing, and displays the processing result on the screen. Will be described.

  First, a seamless transition of application execution from the mobile terminal 11 to the virtual mobile terminal 21 on the server 20 will be described with reference to FIGS. 3 and 4. Here, the background processing operation of the application in the mobile terminal 11 is executed on the server 20 side, thereby reducing the battery consumption in the mobile terminal 11.

  The application 12 is activated by a user operation on the mobile terminal 11 (step 131 in FIG. 4). The application 12 is executed as a front-end job, accesses the website 90 to acquire information, and obtains the processing result of the mobile terminal 11. Display on the screen. The user can use this application 12 (step 132). When the user operation end is input (step 133), the linkage function 25 detects the user operation end input (step 134), and ends the operation of the application 12 as indicated by [1] in FIG. 3 (step 135). As shown in [2] of FIG. 3, the cooperation function 15 executes data perpetuation processing, and application data is stored in the storage 13 (step 136). Here, considering the application data stored in the storage 13, the application data is transferred to a storage device of a processing device different from the mobile terminal 11, and the processing data is restored from the storage device in the processing device. Assuming that the same processing as that of the application 12 is executed based on the application data, the execution of the application 12 is eventually migrated from the mobile terminal 11 to a processing device different from the mobile terminal 11. In this embodiment, assuming that the processing device different from the mobile terminal 11 is the virtual mobile terminal 21 on the server 20, the application 12 is migrated to the virtual mobile terminal 21.

  For this migration, the cooperation function 15 of the mobile terminal 11 acquires the application data stored in the storage 13 (step 137), and transmits the application data to the cooperation function 25 of the virtual mobile terminal 21 on the server 20 via the network 10. Then, the application data is notified (step 138). In response to this, the cooperation function 25 of the virtual mobile terminal 21 reflects the received application data in the storage 23 (step 139). As a result, as shown in [2 ′] in FIG. 3, the information stored in the storages 13 and 23 regarding the application data is synchronized between the mobile terminal 11 and the virtual mobile terminal 21, and the mobile terminal 11 and the virtual mobile terminal are synchronized. The terminal 21 shares application data as information. The notification of application data in step 138 means that the virtual mobile terminal 21 is instructed to start the application 22 based on the application data ([3] in FIG. 3). Therefore, the cooperation function 25 activates the application 22 as shown in [4] of FIG. 3 (step 140), the application 22 restores application data from the storage 23 (step 141), and starts execution (step 142). ). Here, the application 22 executes the same process as the background process in the application 12 and continues to acquire information from the website 90.

  With the above processing, application migration from the mobile terminal 11 to the virtual mobile terminal 21 is realized. Here, the application data representing the execution result when the application 12 ends on the mobile terminal 11 side and the memory image at that time are synchronized between the storage 13 of the mobile terminal 11 and the storage 23 of the virtual mobile terminal 21. Thereafter, the application data is restored in the virtual mobile terminal 21 and the application 22 is activated. In other words, the application program code itself is not subject to migration. Since the memory state at the end of the application in the mobile terminal 11 is restored in the virtual mobile terminal 21, the virtual mobile terminal 21 can continue the operation of the application.

  Next, using FIG. 5 and FIG. 6, a process when the application 11 is restarted in the mobile terminal 11 will be described assuming that the application 22 is executed in the virtual mobile terminal 21 as described above. In this case, application execution seamlessly transitions from the virtual mobile terminal 21 to the mobile terminal 11.

  As shown in step 142 in FIG. 4, it is assumed that the application 22 is executing a process of acquiring information from the website 90 on the virtual mobile terminal 21. Here, as shown in [1] in FIG. 5, when an application activation instruction is input to the mobile terminal 11 by a user operation (step 151 in FIG. 6), the cooperation function 15 of the mobile terminal 11 starts this user operation. Is detected (step 152), and application data is requested to the cooperation function 25 of the virtual mobile terminal 22 (step 153). This application data request is also an application termination instruction to the virtual mobile terminal 21 as shown in [2] of FIG. As a result, the cooperation function 25 of the virtual mobile terminal 21 ends the operation of the application 22 (step 154). As shown in [3] of FIG. 5, the cooperation function 25 executes data perpetuation processing, and application data is stored in the storage 23 (step 155). Next, the cooperation function 25 acquires application data stored in the storage 23 (step 156), and notifies the application data to the cooperation function 15 of the mobile terminal 11 via the network 10 (step 157). In response to this, the cooperation function 15 of the mobile terminal 11 reflects the received application data in the storage 13 (step 158). As a result, as shown in [3 ′] in FIG. 5, the information stored in the storages 23 and 13 regarding the application data is synchronized between the virtual mobile terminal 21 and the mobile terminal 11, and the virtual mobile terminal 21 and the mobile The terminal 11 shares application data as information. After the information is synchronized, the cooperation function 15 activates the application 12 as shown in [4] of FIG. 5 (step 159), and the application 12 restores the application data from the storage 13 (step 160). With the above processing, application migration from the virtual mobile terminal 21 to the mobile terminal 11 is realized. At this stage, the application 12 is not running on the front end on the mobile terminal 11. Next, when a user operation is input (step 161), the application 12 starts operation at the front end, acquires information from the website 90, and enables the user to use the application (step 162). This state continues until the next user operation end (step 163) is input.

  In the processing shown in FIGS. 5 and 6, the application program code itself is not subject to migration, and the application data is synchronized between the storage 23 of the virtual mobile terminal 21 and the storage 13 of the mobile terminal 11. Thereafter, the application data is restored in the mobile terminal 11 and the application 12 is activated. Also in this case, the operation of the application on the mobile terminal 11 can be continued.

  Next, a data synchronization and data sharing mechanism in the storages 13 and 23 in this embodiment will be described. As is clear from the above description, in order to seamlessly transfer the application execution between the mobile terminal 11 and the virtual mobile terminal 21, the operation of the application is terminated on one terminal and the persistence process is performed. The application data at the time may be transferred to the storage of the other terminal and the restoration process may be performed at the other terminal. However, each time the execution of the application is switched between the mobile terminal 11 and the virtual mobile terminal 21, the entire application data at that time is transferred to the partner terminal when the size of the application data is large. It can be a hindrance to fast startup of applications. Since the speed of application activation on the mobile terminal 11 is important for the user, in particular, it is desired to increase the efficiency and speed of application data notification from the virtual mobile terminal 21 to the mobile terminal 11.

  Therefore, in order to avoid the transmission of the entire application data at a time and improve the processing efficiency, for example, the application data is stored in a file and the file itself is transferred between the mobile terminal 11 and the virtual mobile terminal 21. It is possible to share with. In this case, the file to be shared is used as a file system, the mobile terminal 11 provides a mount point for the storage sharing function 16 in the cooperation function 15, and the virtual mobile terminal 21 provides a mount point for the storage sharing function 26 in the cooperation function 25. Mount the file to be shared on those mount points. As a specific implementation, the network storage provided separately from the mobile terminal 11 and the server 20 is mounted by the mobile OS of the mobile terminal 11 and the OS of the virtual mobile terminal 21, or the storage 23 of the virtual mobile terminal 21. Is mounted in the storage sharing function 16 of the mobile terminal 11. When the storage 23 of the virtual mobile terminal 21 is mounted on the mobile terminal 11, the mobile terminal 11 may have a cache function.

  Alternatively, only difference information or update information between application data stored in the storage 13 of the mobile terminal 11 and application data stored in the storage 23 of the virtual mobile terminal 21 is transferred between the mobile terminal 11 and the virtual mobile terminal 21. By sharing the data, the efficiency of processing can be improved by avoiding transmitting the entire application data at a time. As a form of sharing, for example, it is conceivable to transfer difference information or update information between the mobile terminal 11 and the virtual mobile terminal 21. In this case, if all the difference information is transmitted when the application 12 is activated on the mobile terminal 11, the processing may be delayed. Therefore, the difference information is appropriately timed during the period in which the application 22 is operating on the virtual mobile terminal 21. Alternatively, the update information may be transmitted to the mobile terminal 11 and the application data in the storage 13 may be updated in the mobile terminal 11 each time this transmission is performed. In the present embodiment, difference information and update information are transmitted and data update based on the difference information and update information is performed by the cooperation functions 15 and 25 that realize data sharing. Therefore, even if the application 12 is not operating on the mobile terminal 11, the application data Updates are possible. Optimize the structure of difference information and update information according to the data format targeted by the application (for example, whether it is text data, database data, still image data, or moving image data) Therefore, it is possible to shorten the time required for transmitting the difference information and the like, and to enable faster start-up and processing of the application. In addition, as a form of sharing application data difference information and update information, the above-described file system is used, difference information or update information is stored in a file implemented in the file system, and this file is virtualized with the mobile terminal 11. There is also a form in which the mobile terminal 21 shares. According to the file sharing mode, difference information or the like does not have to be actually transferred between the mobile terminal 11 and the virtual mobile terminal 21, so that the processing efficiency is improved when the file size of the difference information or the like is large. Can do.

  The mobile terminal 11 is generally connected to the network 10 by radio, and there is a possibility that the connection with the server 20 is interrupted while the mobile terminal 11 is moving. In that case, sharing of application data between the mobile terminal 11 and the virtual mobile terminal 21 fails in the middle. In preparation for such a case, the mobile terminal 11 is provided with a cache memory for temporarily storing application data as a final state holding function, and is held in the cache memory when application data sharing with the virtual mobile terminal 21 fails. The application 12 may be activated based on the application data that has been set. When the final state holding function is provided in this way, when the application data sharing fails, the result of the background process executed by the virtual mobile terminal 21 is not reflected, but the operation of the application can be ensured. Such a configuration is effective for an application in which the final status is important (for example, Twitter (registered trademark) API (application programming interface)).

  FIG. 7 shows an example of software implementation in the mobile terminal 11 and the virtual mobile terminal 21. Both the mobile terminal 11 and the virtual mobile terminal 21 have a library on the kernel as a software hierarchy, middleware on the library, and Activity is located at the top. In the mobile terminal 11, a general-purpose library libc and a linkage function 15 are arranged in the library. In the kernel, Fuse (File system in Userspace), which is one module of VFS (Virtual File System) and Linux (registered trademark), is implemented as a file-related function. The activity, which is an application, accesses the VFS by the file API when accessing the file. In the case of a normal application that does not seamlessly transfer background processing to the virtual mobile terminal 21, access to a file in the storage 13 from the application is performed using VFS. On the other hand, when using the cooperation function 15, the cooperation function 15 is accessed from VFS via Fuse. As a result, application data can be shared between the storage 13 of the mobile terminal 11 and the storage 23 of the virtual mobile terminal 21 via the linkage function 15.

  FIG. 8 is a diagram illustrating an example of application of the application execution method of the present embodiment. The application execution method of this embodiment may be applied to a resource lending service for mobile terminals. Conventionally, there is a service for charging by providing data storage on a network, but the resource lending service shown here provides an execution environment for the purpose of saving battery consumption in the mobile terminal 11. Accordingly, as a charging model, for example, charging is performed in accordance with the CPU usage time related to the background processing in the virtual mobile terminal 21 on the server 20 and the battery saving amount in the mobile terminal 11 which is saved accordingly. Conceivable. Furthermore, charging may be performed according to the storage usage on the virtual mobile terminal 21 side and the data transfer amount between the mobile terminal 11 and the virtual mobile terminal 21.

  Although the preferred embodiments of the present invention have been described above, since both the mobile terminal and the server are computers themselves as hardware, any of the functions of the mobile terminal and the server described above can also be realized by executing a program on the computer. it can.

  For example, the mobile terminal 11 is connected to the server 20 via the network, and the application data indicating the process for controlling the application state, the memory state at the time of executing the application, and the status information is stored in the computer that executes the application. Processing to be shared with the computer 20 and processing to terminate the application on the computer and cause the server 20 to continue execution of the application based on the shared application data when the operation end of the application is input. And a process for starting an application based on shared application data when an operation start of the application is input, and by executing the program. That.

  Similarly, the server 20 is connected to the mobile terminal 11 via the network, and performs a process for controlling the state of the application that is virtually executed on the computer that virtually executes the application that can be operated on the mobile terminal 11, and When there is a process of sharing application data indicating the memory state and status information with the mobile terminal 11 and a first notification from the mobile terminal 11, the application is started based on the shared application data. This can be realized by reading a program that executes the process of terminating the execution of the application when the second notification is received from the mobile terminal 11 and executing the program. Here, the first notification and the second notification are event messages transmitted from the mobile terminal 11 to the computer. For example, the first notification is an application activation instruction, and the second notification is an application message. For example, an end instruction.

DESCRIPTION OF SYMBOLS 10 Network 11 Mobile terminal 12,22 Application 13,23 Storage 14 Task manager 15,25 Cooperation function 16,26 Storage sharing function 20 Server 21 Virtual mobile terminal

Claims (8)

In an application execution device that executes an application operable on a mobile OS,
When performing application state control, sharing application data indicating the memory state and status information at the time of execution of the application with other application execution devices, and when the operation end of the application is input, Ending the application on the application execution device and continuing execution of the application based on the shared application data to the other application execution device, and when an operation start of the application is input, An application execution apparatus comprising: a cooperation function unit that activates the application based on the shared application data. In an application execution device that virtually executes an application operable on a mobile OS,
Application state control is performed, application data indicating a memory state and status information at the time of execution of the application is shared with another application execution device, and a first notification from the other application execution device is received. And a linkage function unit that starts the application based on the shared application data when there is, and terminates the execution of the application when a second notification is received from the other application execution device. An application execution device. In an application execution system in which a first processing device that executes an application operable on a mobile OS and a second processing device are connected via a network.
The first processing device performs state control of the application in the first processing device, and provides application data indicating a memory state and status information when the application is executed to and from the second processing device. And when the end of the operation of the application is input, the application in the first processing device is terminated and a first notification is transmitted to the second processing device, and the application When an operation start is input, a first notification is transmitted to the second processing device and the application is started in the first processing device based on the shared application data. With the cooperation function means of
The second processing device performs state control regarding virtual execution of the application in the second processing device, shares the application data with the first processing device, and the first processing device. When the first notification is received, the application is started in the second processing device based on the shared application data, and the second notification is received from the first processing device. An application execution system characterized by comprising second linkage function means for sometimes terminating execution of the application in the second processing device.   A file implemented in a file system is shared between the first processing device and the second processing device, and the application data is stored in the file to store the application data with the first processing device. The application execution system according to claim 3, which is shared with the second processing apparatus.   By sharing difference information or update information in the application data between the first processing device and the second processing device, the application data is exchanged between the first processing device and the second processing device. The application execution system according to claim 3, which is shared between the applications.   The first processing device includes a cache memory that holds a final state, and when application data sharing with the second processing device fails, based on the application data acquired in the cache memory The application execution system according to claim 3, wherein the application is activated. Connect to the server via the network and run the application on the computer
A process for controlling the state of the application;
Processing of sharing application data indicating the memory state and status information during execution of the application with the server;
A process of ending the application on the computer and continuing execution of the application based on the shared application data to the server when an operation end of the application is input;
A process of starting the application based on the shared application data when an operation start of the application is input;
A program that executes A computer that connects to a mobile terminal via a network and virtually executes an application operable on the mobile terminal.
A process for controlling the state of the virtually executed application;
A process of sharing application data indicating the memory state and status information during execution of the application with the mobile terminal;
Activating the application based on the shared application data when there is a first notification from the mobile terminal;
A process of terminating execution of the application when there is a second notification from the mobile terminal;
A program that executes

Images