JP2014164567A - Processor, distributed processing method and distributed processing program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a mechanism for controlling the distributed processing environment of an application in accordance with the situation of a communication environment.SOLUTION: When a call to the component of internal processing is made from the component of a user interface, a mobile terminal 20 determines whether to execute the processing of the component of internal processing by a mobile terminal 20 or by a server 30 in accordance with the situation of communication, and switches the call destination of the call between the mobile terminal 20 and the server 30 in accordance with the result of determination. When the call destination is switched to the mobile terminal 20, the mobile terminal 20 controls the mobile terminal 20 to execute unexecuted methods among methods stored in a queue 25, and when the call destination is switched to a server 30, the mobile terminal 20 controls the server 30 to execute the unexecuted methods among the methods stored in the queue 25.

Description

  The present invention relates to a processing apparatus, a distributed processing method, and a distributed processing program.

  Conventionally, background processing of running applications has been performed, and various background processing is realized even for applications that run on terminals such as mobile terminals (hereinafter referred to as “apps for mobile terminals”) (For example, refer nonpatent literature 1).

  For example, in the Android (registered trademark) representative of an operating system (hereinafter referred to as “mobile OS”) that operates an application for mobile terminals, a background process of the application for mobile terminals is implemented in a component called Service. It is a mechanism that can continue processing in the background even after the GUI operation (Activity) of the application is stopped.

Egawa Takashi, Takebata Susumu, Yamada Susumu, Asano Koichi, Yamaoka Toshio, Fujii Daisuke, Fujita Taisuke, Sano Tetsuro “Introduction to Google Android Programming”, 163 pages, ASCII Media Works, ISBN: 4048679562, July 1, 2009

  However, as the number of applications installed on the mobile terminal increases, the various background processes that are executed also increase, and the increase in these background processes affects the decrease in the processing speed of the terminal. It is causing problems. This problem is more noticeable in mobile terminals that do not have high performance. For this reason, it becomes a subject to improve the processing speed in a terminal, without a user being conscious.

  Therefore, the present invention has been made to solve the above-described problems of the prior art, and an object thereof is to improve the processing speed in the terminal.

  In order to solve the above-described problems and achieve the object, a processing device according to the present invention is implemented by separating a first component that executes processing related to a user interface and a second component that executes internal processing. In the processing device that executes the application being executed, the processing method executed by the processing device, or a server that is connected to the processing device via a network and that implements a component corresponding to the second component is executed. When a call to the second component is made from the first component and the queue that stores the method of the second processing, the processing of the second component is executed in the processing device according to the communication status Or whether to execute in the server, and the result of the determination Accordingly, when the call destination of the call is switched to the processing device by the switching unit that switches the call destination of the call between the processing device and the server, the method stored in the queue Among the methods stored in the queue, when the call destination is switched to the server by the switching unit, the processing device is controlled to execute the unexecuted method. A control unit that controls to execute a method; and a storage unit that stores a method of the executed process in the queue after the processing of the component is executed by the processing device or the server. To do.

  In addition, the distributed processing method according to the present invention is executed in a processing device that executes an application in which a first component that executes processing related to a user interface and a second component that executes internal processing are separately mounted. A distributed processing method, wherein the processing device is a server on which a method of processing executed by the processing device or a component connected to the processing device via a network and corresponding to the second component is mounted A queue for storing a method of processing executed by the first component, and when the first component is called to the second component, the processing of the second component is performed according to a communication situation. Determine whether to run on the device or on the server A switching step of switching a call destination of the call between the processing device and the server according to a result of the determination, and when the call destination is switched to the processing device by the switching step, Of the stored methods, control is performed to execute an unexecuted method in the processing device, and when the call destination is switched to the server by the switching step, among the methods stored in the queue, the A control step of controlling the server to execute an unexecuted method, and a storage step of storing the method of the executed process in the queue after the processing of the component is executed by the processing device or the server. It is characterized by including.

  The distributed processing program according to the present invention is executed in a processing device that executes an application in which a first component that executes processing related to a user interface and a second component that executes internal processing are separately mounted. When a computer connected via a network to a server on which a component corresponding to the second component is mounted is called from the first component to the second component, the communication status is changed. Accordingly, it is determined whether the processing of the second component is executed in the processing device or the server, and the call destination of the call is determined as the processing device and the server according to the result of the determination. A switching step for switching between and a call by the switching step. When the destination is switched to the processing device, the processing method executed by the processing device or the method stored in the queue that stores the processing method executed by the server is selected. The device is controlled to execute an unexecuted method, and when the call destination is switched to the server by the switching step, an unexecuted method is executed on the server among the methods stored in the queue. And a storage step of storing a method of the executed processing in the queue after the processing of the component is executed by the processing device or the server.

  The processing device, the distributed processing method, and the distributed processing program according to the embodiment can improve the processing speed in the terminal and provide a mechanism for controlling the distributed processing environment of the application according to the state of the communication environment.

FIG. 1 is a diagram illustrating an example of a configuration of a system according to the first embodiment. FIG. 2 is a diagram for explaining the configuration of the mobile terminal and the server according to the first embodiment. FIG. 3 is a diagram illustrating a configuration example of an application of a conventional mobile terminal. FIG. 4 is a diagram illustrating a configuration example of an application of the mobile terminal according to the first embodiment. FIG. 5 is a diagram illustrating an implementation example of the mobile terminal and the server according to the first embodiment. FIG. 6 is a sequence diagram showing a processing procedure when executing a conventional application. FIG. 7 is a sequence diagram showing a processing procedure of application execution processing of the mobile terminal according to the first embodiment. FIG. 8 is a sequence diagram showing a processing procedure of execution processing by a conventional callback. FIG. 9 is a sequence diagram showing a processing procedure of execution processing by callback of the mobile terminal according to the first embodiment. FIG. 10 is a diagram illustrating a computer that executes a distributed processing program.

  Exemplary embodiments of a processing device, a distributed processing method, and a distributed processing program according to the present invention will be described below in detail with reference to the accompanying drawings. In addition, this invention is not limited by this embodiment.

[First embodiment]
In the following embodiments, the configuration of the system according to the first embodiment and the flow of processing by the impact evaluation apparatus will be described in order, and finally the effects of the first embodiment will be described. FIG. 1 is a diagram illustrating an example of a configuration of a system according to the first embodiment. The system according to the first embodiment includes a network 10, a plurality of mobile terminals 20, and a plurality of servers 30. Each mobile terminal 20 and each server 30 are connected via the network 10.

  Here, the network 10 is, for example, 3G (3rd Generation), LTE (Long Term Evolution), WiFi (Wireless Fidelity), or the like. The mobile terminal 20 is connected to the Internet such as a mobile phone, a PHS (Personal Handyphone System), a PDA (Personal Digital Assistant), a tablet PC (Personal Computer), etc., and connected to an inquiry server or other user terminals. Any device can be used as long as it can transmit and receive information. In addition, the computer is not limited to a mobile terminal, and a computer installed in a home or office may be used.

  One or more mobile terminals 20 and one or more servers 30 are connected to the network 10. Each mobile terminal 20 is a physical device that is driven by a secondary battery such as a lithium ion battery and is connected to the network 10 by wire or wirelessly. For example, the server 30 can be configured on a cloud platform. In the present embodiment, distributed processing is realized by causing the background processing of the application (AP) in the mobile terminal 20 to be executed on the server 30.

  In the present embodiment, the user interface (view and control) component and the internal processing (model) component can be easily divided as an application of the mobile terminal 20 by a design pattern such as MVC (Model View Control; MVC). Suppose it is possible. Here, the existing execution environment in the mobile terminal 20 is modified based on the present invention, an equivalent execution environment is introduced in the server 30, and the application of the mobile terminal 20 can be installed and executed in the environment of the server 30. I have to.

  Further, for example, the mobile terminal 20 is connected to the Internet, such as a mobile phone, a PHS (Personal Handyphone System), a PDA (Personal Digital Assistant), a tablet PC (Personal Computer), etc., and connected to an inquiry server or other user terminals. Any device can be used as long as it can transmit and receive information. In addition, the computer is not limited to a mobile terminal, and a computer installed in a home or office may be used. Communication in each mobile terminal 20 and each server 30 is not limited to wireless communication, and may be wired communication.

  FIG. 2 shows a logical configuration of the mobile terminal 20 and the server 30 in the present embodiment. In the mobile terminal 20, an execution environment 21 realized by the mobile OS is provided, and the application 22 is positioned above the execution environment 21. As functions in the execution environment 21, a switching unit 21a, a control unit 21b, and a storage unit 21c are provided.

  Whether the switching unit 21a executes the processing of the internal processing component in the mobile terminal 20 or the server 30 depending on the communication status when a call is made from the user interface component to the internal processing component. The call destination is switched between the mobile terminal 20 and the server 30 according to the determination result.

  For example, the switching unit 21a estimates the communication status by, for example, measuring a communication speed or radio wave intensity, or acquiring information identifying whether communication is possible or not from the outside. Then, the switching unit 21 a switches the call destination of the call between the mobile terminal 20 and the server 30 according to the estimated communication status. For example, the switching unit 21 a switches the call destination to the server 30 if communication is possible, and switches the call destination to the mobile terminal 20 if communication is not possible. The switching unit 21 a switches the call destination to the server 30 if the communication speed is equal to or higher than a predetermined threshold, and switches the call destination to the mobile terminal 20 if the communication speed is equal to or lower than the predetermined threshold.

  When the call destination is switched to the mobile terminal 20 by the switching unit 21a, the control unit 21b performs control so that an unexecuted method is executed in the mobile terminal 20 among the methods stored in the queue 25. When the call destination is switched to the server 30 by the unit 21a, control is performed so that an unexecuted method is executed in the server 30 among the methods stored in the queue 25.

  After the component processing is executed by the own device or the server 30, the storage unit 21 c stores the executed component processing method in the queue 25. The storage unit 21c stores information indicating whether the method is executed by the mobile terminal 20 or the server 30 together with the method of the executed process.

  The application 22 is based on the MVC design pattern, and includes a view and control component and a model component. Below the execution environment 21, as hardware components, various sensors 23 such as a GPS (Global Positioning System) sensor, a battery fuel gauge, an acceleration sensor, and the application 22 are related. A storage (storage device) 24 for storing data and the like is provided.

  The storage 24 is configured by, for example, a memory card having a flash memory. Similarly, the server 30 is provided with an execution environment 31 realized by the OS, and an application 32 equivalent to the application 22 of the mobile terminal 20 is located above the execution environment 31. Below the execution environment 21, a virtual sensor 33 that simulates a sensor as a hardware component, and a storage (storage device) 34 that stores data and the like related to the execution of the application 32 are provided. The storage 34 is configured by, for example, an HDD (Hard Disk Device).

  In a conventional mobile terminal, functions of function calls (or method calls) and inter-process communication from view and control components in an application to model components are provided in the execution environment. In the present embodiment, a switching unit 21 a that is a mechanism for dynamically switching a call destination (and a communication destination) is added to this function in the execution environment 21 of the mobile terminal 20. Specifically, the switching unit 21a that dynamically switches the call destination (and the communication destination) dynamically switches the call destination (and the communication destination) of the model function according to the state of the communication environment of the mobile terminal 20. Here, as the wireless communication status of the terminal, for example, the communication speed of the line, the radio wave intensity, etc., as well as the identification of whether communication is possible, and the like can be mentioned.

  In addition, the mobile terminal 20 has a queue 25 that stores a model function and arguments to be called in order when the call destination is switched. By using this queue 25 according to the application characteristics, the same result can be obtained regardless of whether it is executed by the server 30 or the mobile terminal 20. Here, as application characteristics, whether to use a callback, whether the model has an internal state (holds), setting of a model (internal processing), and the like can be considered.

  In addition, the process of switching the call destination is determined every time the process is executed. If it is determined that the processing is to be performed on the server 30 side, the call destination is designated as a model on the server 30 side, and the model is processed on the server 30 side. At this time, if there are processes accumulated in the queue 25, the processes in the queue 25 are executed after calling them first. If it is determined that the process is to be performed by the mobile terminal 20, the application can be executed even offline by designating the call destination as a model on the mobile terminal 20 side and causing the call to be processed locally.

  Next, a specific example of a conventional application configuration will be described by taking as an example the case where the mobile OS configuring the execution environment 21 in the mobile terminal 20 is an Android (registered trademark) OS. FIG. 3 shows a configuration of a conventional application that operates on the mobile OS in this case. Since AndroidOS is assumed here, the application 22 includes an Activity component that corresponds to a view and a control and is responsible for a user interface, and a Service component that corresponds to a model and is responsible for background processing.

  In the Android application, Activity corresponds to a view control, and Service corresponds to a model component. Activity also shares user interface processing, and Service shares background processing. In addition, Activity is bound to an interface that defines a function of a service to be called by a Binder Driver in the kernel 26.

  In addition, the kernel 26 as an execution environment is provided with a Binder Driver that executes a method call (for example, a call from an Activity component to a Service component) and inter-process communication. 3 and the subsequent drawings, it is described that the sensor 23 and the storage 24 are provided in the kernel 26 of the mobile terminal 20, and the virtual sensor 33 and the storage 34 are provided in the kernel 36. However, these do not mean that sensors, virtual sensors, and storage are provided as physical devices in the kernel, but means that sensors, virtual sensors, and storage can be accessed via the kernel. Yes.

  Next, specific examples of application configurations of the mobile terminal 20 and the server 30 according to the present embodiment will be described with reference to FIG. As shown in FIG. 4, the Binder Driver in the kernel 26 in the mobile terminal 20 according to the present embodiment is remodeled so as to be compatible with the distributed execution method of the present invention, and the modified Binder equivalent to the mobile terminal 20 in the server 30 Install OS environment with Driver. Further, the same application 32 as the application 22 in the mobile terminal 20 is also installed in the environment of the server 30.

  Originally, it is assumed that the Activity component and the Service component of the same application exist in the same terminal, but with the modified Binder Driver as described above, the activity of the mobile terminal 20 can be changed via a network such as the Internet. It is possible to bind to the service of the server 30. The Binder Driver of the mobile terminal 20 functions as a switching unit 21a that switches a method call destination. Furthermore, by synchronizing the storages 24 and 34 between the mobile terminal 20 and the server 30 and also synchronizing the sensor information, the server 30 can grasp and use the context of the mobile terminal 20. As a result, the Service component on the server 30 side can obtain an execution result equivalent to the Service component of the mobile terminal 20.

  FIG. 5 shows an implementation example of software based on the existing technology for realizing the synchronization of the storages 24 and 34 between the mobile terminal 20 and the server 30. Both the mobile terminal 20 and the server 30 have libraries on the kernels 26 and 36 as software layers, and the applications 22 and 32 are located on the libraries. In the mobile terminal 20, the library includes a general-purpose library libc and a unique library ECS that realizes a cache operation.

  In the kernel 26, as a file-related function, a Fuse (File system in Userspace) which is one module of VFS (Virtual File System) and Linux (registered trademark) is mounted. When accessing the file, the application 22 accesses the VFS using the file API. This access is sent from the VFS to the library via Fuse, and as a result, storage synchronization is achieved between the storage 24 of the mobile terminal 20 and the storage 34 of the server 30 via the library. In the example shown here, storage synchronization for application-specific files such as SQL Lite is realized by building a file system that combines a local cache and NFS (Network File System). In addition to those shown here, many methods are known for synchronizing the local storage and the remote storage. Therefore, the storages 24 and 34 may be synchronized using these methods. .

  The process shown in FIG. 6 shows a process when a conventional Binder Driver that has not been modified is used. The Activity requests the use of the service from the object Context as in the conventional Android (Step S101), and obtains a handler for calling the service (Step S102).

  Activity calls a method of Service via Binder Driver (step 103). The Binder Driver relays the calling instruction to the Service (Step 104), acquires the execution result of the Service (Step 105), and returns it to the Activity (Step 106).

  Next, application execution processing of the mobile terminal 20 according to the first embodiment will be described. FIG. 7 is a sequence diagram showing a processing procedure of application execution processing of the mobile terminal 20 according to the first embodiment. FIG. 7 shows processing when a modified Binder Driver is used.

  As shown in FIG. 7, Activity requests the use of a service from an object called Context as in conventional Android (step S201), and obtains a handler for calling the service (step S202). And Activity calls the method of Service via Binder Driver (step 203). At this time, the Binder Driver evaluates the communication status and determines whether or not to process on the server 30 side (step S204).

  In step S204, when the Binder Driver determines that it should be processed by the server 30, the Binder Driver checks the queue 25 for a call that is not executed on the mobile terminal 20 (step S205), and a method (hereinafter referred to as a pre-execution method). ) Is received (step S206). If there is a call, the pre-execution method is first called (step S207), and the call command is relayed to the service in the server 30 (step S208). Then, the service of the server 30 returns an execution result to the Binder Driver of the mobile terminal 20 via the Binder Driver (Steps S209 and S210). Here, the mobile terminal 20 discards the execution result of the service of the server 30.

  After that, as in the case where the call of the pre-execution method is not in the queue 25, the server 30 sends the call instruction determined to be processed by the mobile terminal 20 to the terminal as in the conventional Binder Driver function. Relaying to a certain service (step S211), the service in the server 30 returns the execution result of the service of the mobile terminal 20 via the Binder Driver (steps S212 and 213).

  If it is determined in step S204 that the mobile terminal 20 should process, the queue 25 is checked to see if there is a call that has not been executed in the mobile terminal 20 (step S214), and a response to the pre-execution method is received (step S214). Step S215). As a result, if there is a call, the advance call is first executed (step S216), and the execution result is returned to the Binder Driver (step S217). Here, the mobile terminal 20 discards the execution result. That is, in the case of execution on the mobile terminal 20 and the case of execution on the server 30, since the execution results of the pre-call accumulated in the queue 25 have already been received, the acquired execution results Each may be discarded.

  After that, as in the case where the call of the pre-execution method is not in the queue 25, the call that is determined to be processed by the mobile terminal 20 is transmitted to the service in the mobile terminal 20 as in the conventional Binder Driver function. (Step S218), and returns the execution result of Service to the Binder Driver (Steps S219 and S220).

  Thereafter, the Binder Driver determines whether or not to save the call executed this time in the queue 25 based on a predetermined condition (step S221). For example, the Binder Driver determines whether the method to be put in the queue 25 corresponds to one of a method for setting an application, a method for which the application has a state, or a method for registering a callback function.

  As a result, if it is determined to save in the queue 25, the method is put in the queue 25 (step S222), and the execution result is returned to Activity. That is, by storing only methods that match the above conditions in the queue 25, the execution result can be prevented from changing even when the calling location is switched to the mobile terminal 20 or the server 30, while the application The efficiency of the can be improved. For example, for an application having an internal state, the processing result changes when the calling location is changed. Therefore, the same execution result is obtained even if the calling location is changed by putting the process in the queue 25. To be able to. In order to simplify the processing, the above determination processing may be omitted and all the methods may be put in the queue 25.

  In the process of step S222, the queue 25 stores processing target information indicating which of the mobile terminal 20 and the server 30 has executed the method, together with the method executed this time. That is, at the time of calling the pre-execution method (steps S207 and 216), it can be determined from the processing target information whether the method stored in the queue 25 is not executed on the mobile terminal 20 or the server 30 side. I have to. On the other hand, if it is determined in step S222 that the method is not stored in the queue 25, the execution result is returned to Activity without entering the method in the queue 25 (step S223).

  In the above description, when Activity calls a service method via the Binder Driver, if the Binder Driver evaluates the communication status and determines that the server 30 should process, the server 30 queues 25. The case where the method stored in was executed was explained. However, the present invention is not limited to this. Methods stored in the queue 25, particularly those executed by the server 30, may be executed when the network state is changed. For example, as a main case, the server 30 may execute what is put in the queue 25 when the network is disconnected when the network 10 is connected.

  Next, execution using a callback will be described with reference to FIGS. 8 and 9. Execution using callback means that an object generated by the caller is saved in advance for a call that mainly takes time and a result is assumed to be returned asynchronously. It is one of the execution methods that return asynchronous results via

  First, an example of a call using a conventional callback object will be described with reference to FIG. As shown in FIG. 8, Activity requests the use of a service from an object called Context as in the conventional Android (Step S301), and acquires a handler for calling Service (Step S302).

  Then, Activity requests the Service to register the callback object (Step S303). Then, the Service stores the callback object in the memory (Step S304). Activity calls the callback usage method (step S305). Then, the Service returns a reception response to Activity (Step S306).

  Thereafter, after actually performing the processing, the Service notifies the callback usage method of the processing result (Step S307), and returns the execution result to the Activity via the callback method (Step S308).

  Next, an example of a call using a callback object in this embodiment will be described with reference to FIG. In FIG. 9, description will be made on the assumption that communication is interrupted (offline) when a callback object is registered, communication is present when calling, and an offload is performed. As shown in FIG. 9, first, Activity requests the use of a service from an object called Context as in the conventional Android (Step S401), and obtains a handler for calling Service (Step S402).

  Then, Activity requests the Binder Driver to register a callback object (Step S403). Then, the Binder Driver makes a request to the Service (step S404) and registers a callback object in the queue 25 (step S405). Then, the Service stores the callback object in the memory (Step S406). That is, when the callback object is registered, the callback object cannot be registered on the server 30 side due to communication disconnection. At this time, since the type of method includes a callback object, the method is also stored in the queue 25 as described above.

  Next, when a call is made to the Service method (step S407), it is determined whether the processing should be performed on the server 30 side (step S408). At this time, since there is communication, execution on the server 30 is determined. At that time, the Binder Driver first checks the pre-execution method of the queue 25 (step S409), accepts the callback registration response, and extracts the callback object registration method registered in the queue 25 of the mobile terminal 20 earlier. (Step S410). The Binder Driver of the mobile terminal 20 first registers the callback object with the Binder Driver on the server 30 side (Step S411), and relays the calling instruction to the Service in the server 30 (Step S412).

  Then, the service of the server 30 returns a registration result to the Binder Driver of the mobile terminal 20 via the Binder Driver (Steps S413 and S414), and registers a callback object in the memory (Step S415). Subsequently, the service of the mobile terminal 20 calls a callback usage method and relays it to the service via the Binder Driver on the server 30 side (step S416).

  Then, the Service of the server 30 returns an acceptance response to the Binder Driver of the mobile terminal 20 via the Binder Driver (Steps S417 and 418). Thereafter, the Service on the server 30 side actually performs processing, then notifies the callback usage method of the processing result (Step S419), and returns the execution result to Activity through the callback method (Steps S420 to 423). .

[Effect of the first embodiment]
As described above, when the mobile terminal 20 according to the first embodiment is called from the user interface component to the internal processing component, the mobile terminal 20 moves the processing of the internal processing component according to the communication status. It is determined whether it is executed at the terminal 20 or the server 30, and the call destination of the call is switched between the mobile terminal 20 and the server 30 according to the determination result. Then, when the call destination is switched to the mobile terminal 20, the mobile terminal 20 performs control so that an unexecuted method is executed in the mobile terminal 20 among the methods stored in the queue 25, and the switching unit 21 a When the call destination is switched to the server 30 by the control, the server 30 is controlled to execute an unexecuted method among the methods stored in the queue 25. Then, after the component processing is executed by the mobile terminal 20 or the server 30, the processing method of the executed component is stored in the queue 25. As a result, it is possible to provide a mechanism for controlling the distributed processing environment of the application according to the state of the communication environment.

  In addition, it is possible to perform switching control such that a service operating in the mobile terminal is dynamically executed on the server 30 side such as a cloud according to the state of the communication environment. As a result, it is possible to increase the speed by using abundant resources (lines, memories, etc.) of the server. In addition, by using the queue 25, it is possible to prevent the execution result from being changed due to a change in the calling location. In addition, it is possible to realize seamless execution of a plurality of execution environments that are switched and used without interruption of processing due to switching of execution environments, reset of intermediate states of processing results, and the like.

  In particular, when wireless communication is performed with the mobile terminal 20 in a mobile environment such as an Android service, the mobile terminal 20 is easily affected by the performance of the mobile terminal 20 and restrictions on the wireless communication environment. As described above, the processing performance higher than that of the mobile terminal can be obtained without being aware of the switching of the execution environment.

[System configuration]
In addition, among the processes described in the present embodiment, all or part of the processes described as being automatically performed can be manually performed, or the processes described as being performed manually can be performed. All or a part can be automatically performed by a known method. In addition, the processing procedures, control procedures, specific names, and information including various data and parameters shown in the above-described document and drawings can be arbitrarily changed unless otherwise specified.

  Further, each component of each illustrated apparatus is functionally conceptual, and does not necessarily need to be physically configured as illustrated. That is, the specific form of distribution / integration of each device is not limited to the one shown in the figure, and all or a part of the distribution / integration may be functionally or physically distributed in arbitrary units according to various loads or usage conditions. Can be integrated and configured.

[program]
FIG. 10 is a diagram illustrating that information processing by the distributed processing program according to the disclosed technique is specifically realized using a computer. As illustrated in FIG. 10, the computer 1000 includes, for example, a memory 1010, a CPU (Central Processing Unit) 1020, a hard disk drive interface 1030, a disk drive interface 1040, a serial port interface 1050, a video adapter 1060, A network interface 1070. Each part of the computer 1000 is connected by a bus 1080.

  The memory 1010 includes a ROM 1011 and a RAM 1012 as illustrated in FIG. The ROM 1011 stores a boot program such as BIOS (Basic Input Output System). The hard disk drive interface 1030 is connected to the hard disk drive 1031 as illustrated in FIG. The disk drive interface 1040 is connected to the disk drive 1041 as illustrated in FIG. For example, a removable storage medium such as a magnetic disk or an optical disk is inserted into the disk drive 1041. The serial port interface 1050 is connected to, for example, a mouse 1051 and a keyboard 1052 as illustrated in FIG. The video adapter 1060 is connected to a display 1061, for example, as illustrated in FIG.

  Here, as illustrated in FIG. 10, the hard disk drive 1031 stores, for example, an OS 1091, an application program 1092, a program module 1093, and program data 1094. That is, the distributed processing program according to the disclosed technology is stored in, for example, the hard disk drive 1031 as the program module 1093 in which a command to be executed by the computer is described.

  Data used for information processing by the distributed processing program is stored as program data 1094 in, for example, the hard disk drive 1031. The CPU 1020 reads out the program module 1093 and the program data 1094 stored in the hard disk drive 1031 to the RAM 1012 as necessary, and executes various procedures.

  Note that the program module 1093 and the program data 1094 related to the distributed processing program are not limited to being stored in the hard disk drive 1031. For example, the program module 1093 and the program data 1094 may be stored in a removable storage medium. In this case, the CPU 1020 reads data via a removable storage medium such as a disk drive. Similarly, the program module 1093 and the program data 1094 related to the distributed processing program may be stored in another computer connected via a network (LAN (Local Area Network), WAN (Wide Area Network), etc.). good. In this case, the CPU 1020 reads various data by accessing another computer via the network interface.

[Others]
Note that the distributed processing program described in the present embodiment can be distributed via a network such as the Internet. The control program can also be executed by being recorded on a computer-readable recording medium such as a hard disk, a flexible disk (FD), a CD-ROM, an MO, and a DVD, and being read from the recording medium by the computer.

DESCRIPTION OF SYMBOLS 10 Network 20 Mobile terminal 21, 31 Execution environment 21a Switching part 21b Control part 21c Storage part 22, 32 Application 23 Sensor 24, 34 Storage 30 Server 33 Virtual sensor

Claims (7)

In a processing apparatus that executes an application in which a first component that executes processing related to a user interface and a second component that executes internal processing are separately mounted,
A queue that stores a method of processing executed by the processing device, or a method of processing executed by a server that is connected to the processing device via a network and has a component corresponding to the second component;
When a call is made from the first component to the second component, it is determined whether the processing of the second component is executed in the processing device or the server depending on the communication status A switching unit that switches a call destination of the call between the processing device and the server according to a result of the determination;
When the switching unit is switched to the processing device by the switching unit, control is performed so that an unexecuted method is executed in the processing device among the methods stored in the queue, and the calling unit is controlled by the switching unit. Is switched to a server, among the methods stored in the queue, a control unit that controls to execute an unexecuted method in the server;
After the processing of the component is executed by the processing device or the server, a storage unit that stores a method of the executed processing in the queue;
A processing apparatus comprising: Storage for storing data related to the execution of the application;
A synchronization unit for synchronizing data between the storage of the processing device and the storage of the server;
The processing apparatus according to claim 1, further comprising:   The switching unit acquires one or more of information on communication speed, information on radio wave intensity, and identification information for identifying whether communication is possible or not, and estimates the communication status using the acquired information The processing device according to claim 1, wherein the processing device determines whether the processing of the second component is executed in the processing device or the server according to the communication status. .   The storage unit determines whether the method of the executed process corresponds to one that places an application setting, one that has an internal state, or one that registers a callback function. The processing apparatus according to claim 1, wherein the method is stored in the queue.   The said storage part stores the information which shows whether it is the said processing apparatus or the said server that performed this method with the method of the performed process. The processing apparatus as described in one. A distributed processing method executed in a processing device that executes an application in which a first component that executes processing related to a user interface and a second component that executes internal processing are separately implemented,
The processing device stores a method of processing executed by the processing device or a method of processing executed by a server that is connected to the processing device via a network and has a component corresponding to the second component. With a queue to
When a call is made from the first component to the second component, it is determined whether the processing of the second component is executed in the processing device or the server depending on the communication status And a switching step of switching a call destination of the call between the processing device and the server according to a result of the determination;
When the call destination is switched to the processing device by the switching step, control is performed so that an unexecuted method is executed in the processing device among the methods stored in the queue. Is switched to a server, among the methods stored in the queue, a control process for controlling to execute an unexecuted method in the server;
After the processing of the component is executed by the processing device or the server, a storing step of storing a method of the executed processing in the queue;
The distributed processing method characterized by including. A component corresponding to the second component that is executed in a processing device that executes an application in which a first component that executes processing related to a user interface and a second component that executes internal processing are separately mounted. To a computer connected via a network to a server with
When a call is made from the first component to the second component, it is determined whether the processing of the second component is executed in the processing device or the server depending on the communication status A switching step of switching a call destination of the call between the processing device and the server according to a result of the determination;
When the call destination is switched to the processing device by the switching step, the method of the process executed by the processing device or the method stored in the queue that stores the method of the processing executed by the server is stored. Of these, when the processing device is controlled to execute an unexecuted method and the call destination is switched to the server by the switching step, among the methods stored in the queue, the unexecuted method is executed on the server. A control step that controls the execution of the method;
After the processing of the component is executed by the processing device or the server, a storage step of storing a method of the executed processing in the queue;
A distributed processing program characterized by causing

Images