Multi-device system
The multi-device system addresses cloud failure disruptions by redistributing cloud applications to local devices, ensuring continuous operation and stable service levels while optimizing resource use and fee reporting.
Patent Information
- Application Number
- JP2023072208
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-04-26
- Publication Date
- 2024-11-08
AI Technical Summary
Existing multi-device systems that rely on cloud services face operational disruptions when failures occur on the cloud side or in communication with the cloud, leading to service interruptions.
A multi-device system with a management device that redistributes cloud applications to local devices upon detecting cloud failures, allowing continued operation by switching connections to locally held applications, and manages resource allocation based on device capabilities.
Ensures continuous system operation during cloud failures by executing cloud applications locally, stabilizing service levels, and minimizing service fee losses by accurately reporting usage to the cloud provider.
Smart Images

Figure 2024157698000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a multi-device system having a plurality of devices. [Background technology]
[0002] A multi-device system has been put into practical use, in which multiple devices work in cooperation with each other while using applications on the cloud. However, in this configuration, if a failure occurs on the cloud side or in communication with the cloud, the service will be stopped. For this reason, a method has been proposed that allows a device to use a specific service even if a failure occurs in the access point to which the device is connected (for example, Patent Document 1). [Prior art documents] [Patent documents]
[0003] [Patent Document 1] Patent Publication No. 2021-087162 Summary of the Invention [Problem to be solved by the invention]
[0004] In the method described in Patent Document 1, when an abnormality is detected in an access point connected to a device, the communication connection destination of the device is switched to another access point for using a specific function. However, with this method, if it is not possible to connect to another access point or if a failure occurs on the cloud side, operation cannot be continued.
[0005] An object of one aspect of the present invention is to enable a multi-device system that uses a cloud to continue operation even if a failure occurs on the cloud side or in communication with the cloud. [Means for solving the problem]
[0006] A multi-device system according to one aspect of the present invention includes a plurality of devices and a management device that manages the plurality of devices, and operates using a service provided by a cloud. Any of the plurality of devices holds an application program for implementing the service within the multi-device system. When the management device detects an abnormality in the cloud or in communication with the cloud, the management device instructs each of the plurality of devices to change the connection destination from the cloud to a device that holds the application program. Each of the plurality of devices accesses the application program in response to an instruction from the management device. Effect of the Invention
[0007] According to the above-described aspect, in a multi-device system that uses a cloud, even if a failure occurs on the cloud side or in communication with the cloud, the system can continue to operate. [Brief description of the drawings]
[0008] [Figure 1] FIG. 1 is a diagram illustrating an example of a multi-device system according to an embodiment of the present invention. [Diagram 2] FIG. 2 is a diagram illustrating an example of management data (device management data, cloud application management data, and service usage data) held by a management device. [Diagram 3] 2 is a diagram showing an example of management data (service usage data and application data management data) held by a cloud management server; FIG. [Figure 4] 11 is a flowchart illustrating an example of a process of a multi-device system. [Diagram 5] 13 is a flowchart illustrating an example of a process for acquiring cloud information. [Figure 6] 11 is a flowchart illustrating an example of a process for acquiring device information. [Figure 7]11 is a flowchart illustrating an example of a process for detecting a state of a cloud. [Figure 8] 11 is a flowchart illustrating an example of a process for checking a cloud application in a local environment. [Figure 9] 11 is a flowchart illustrating an example of a process for selecting a device that runs a cloud application. [Figure 10] 11 is a flowchart illustrating an example of a process for relocating a cloud application in a multi-device system. [Figure 11] 13 is a flowchart illustrating an example of a process for notifying each device of a connection destination of a resident application. [Figure 12] 13 is a flowchart illustrating an example of a process for changing a connection destination of a resident application from the cloud to a local connection. [Figure 13] 11 is a flowchart illustrating an example of a process for collecting usage information indicating a usage status of a service in a local environment. [Figure 14] 11 is a flowchart illustrating an example of a process for detecting the state of a cloud when a cloud application is running in a local environment. [Figure 15] 13 is a flowchart illustrating an example of a process for changing a connection destination of a resident application from a local connection to a cloud connection. [Figure 16] 13 is a flowchart illustrating an example of a process for notifying a management server of a service usage status. [Figure 17] FIG. 11 is a sequence diagram illustrating an example of a process of a multi-device system. [Figure 18] FIG. 1 is a diagram (part 1) showing an embodiment of the operation of a multi-device system. [Figure 19] FIG. 2 is a diagram (part 2) showing an embodiment of the operation of the multi-device system. [Figure 20] FIG. 3 is a diagram (part 3) showing an example of the operation of the multi-device system. [Figure 21] FIG. 4 is a diagram showing an example of the operation of the multi-device system; DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0009] Fig. 1 shows an example of a multi-device system according to an embodiment of the present invention. As shown in Fig. 1, the multi-device system 100 according to the embodiment of the present invention includes a plurality of devices 10 (10a to 10d). The plurality of devices 10 are configured to be able to communicate with each other. For example, the plurality of devices 10 are connected to a local area network (LAN).
[0010] Each device 10 includes a processor, a memory, and a storage. An operating system (OS) and one or more application programs are stored in the memory or storage. The processor controls the operation of the device 10 by executing the application programs on the OS. In the following description, the application programs stored in advance in the memory or storage of the device itself may be referred to as "resident applications 11."
[0011] One of the multiple devices 10 has a function for managing the other devices. In this embodiment, the device 10a has a function for managing the devices 10b to 10d. Therefore, in the following description, the device 10a may be referred to as the "management device 10a."
[0012] The management device 10a includes a management tool 12. The management tool 12 holds management data and manages the state of the cloud 200 and the state of communication between the multi-device system 100 and the cloud 200. The management tool 12 also manages the state of each device 10 (here, devices 10b to 10d). The management tool 12 is realized, for example, by a processor implemented in the management device 10a executing a management program.
[0013] Each device 10 other than the management device 10a (i.e., devices 10b to 10d) includes an agent tool 13. The agent tool 13 acquires metrics information of its own device and notifies the management tool 12 of the same. The metrics information indicates the resource configuration and free space within the own device. The agent tool 13 is realized by a processor implemented in the device 10 executing an agent program.
[0014] The device 10 can access the cloud 200 via a network 300. Here, the network 300 is, for example, a public line. The device 10 operates by using a service provided by the cloud 200 as necessary. That is, the device 10 operates by using an application on the cloud 200 as necessary. At this time, a resident application 11 implemented in the device 10 uses an application on the cloud 200. Alternatively, the resident application 11 requests a process to an application on the cloud 200 and receives the process result.
[0015] The cloud 200 includes an application server 210 and a management server 220. The application server 210 includes an application program for providing a requested service. In response to an access from the device 10, the application server 210 executes a specified application program and provides a processing result. That is, the application server 210 provides a service in response to an access from the device 10. In the following description, an application program held by the application server 210 of the cloud 200 may be referred to as a "cloud app (or cloud app APP)."
[0016] The management server 220 manages the state of the cloud 200, and also notifies the management device 10a of the state of the cloud 200. At this time, the management server 220 may notify the management device 10a of the state of the cloud 200 in response to an inquiry from the management device 10a, or may notify the management device 10a of the state of the cloud 200 spontaneously.
[0017] In this way, each of the multiple devices 10 constituting the multi-device system 100 uses an application on the cloud 200. At this time, the management server 220 may request a service usage fee from the multi-device system 100. In this case, the usage fee for the cloud app is calculated based on, for example, the usage time of the cloud app or the number of accesses to the cloud app.
[0018] However, if a failure occurs in the cloud 200 or in communication with the cloud 200, the multi-device system 100 may not be able to continue operation. For this reason, the multi-device system 100 acquires a cloud app from the cloud 200 in advance and stores it in one of the devices 10. Then, when a failure occurs in the cloud 200 or in communication with the cloud 200, each device 10 continues operation by using the cloud app stored in the multi-device system 100.
[0019] However, if the resources (particularly memory capacity or storage capacity) of each device 10 are small, it may be impossible or undesirable to have a cloud app held by one device 10. Therefore, the cloud app is divided into multiple parts and distributed to multiple different devices 10 as necessary. In the example shown in Fig. 1, cloud application APP_1 is divided into cloud application component APP_1x and cloud application component APP_1y, which are held by device 10b and device 10c, respectively.
[0020] When device 10 uses a cloud app stored in multi-device system 100, management tool 12 counts the usage time or the number of accesses. After the failure is restored, management tool 12 notifies cloud 200 of the usage time or the number of accesses of the cloud app in multi-device system 100. This allows the cloud service provider to receive a service usage fee.
[0021] 2 shows an example of management data in the management device 10a held by the management tool 12. In this embodiment, the management tool 12 holds device management data, cloud application management data, and service usage data.
[0022] FIG. 2(a) shows an example of device management data. The device management data represents information related to resources of each device 10 constituting the multi-device system 100. The operation information represents whether the device is operating or not. The memory capacity and storage capacity represent the memory and storage capacities of the device. The free memory and free storage represent the free memory and storage capacities of the device. The connection destination information represents the connection destination when the device uses a cloud app. For example, when accessing the cloud 200 to receive a service, the connection destination information represents the cloud 200 or the application server 210. Also, when using a cloud app stored in the multi-device system 100, the connection destination information represents the device 10 that stores the cloud app.
[0023] 2(b) shows an example of cloud application management data. Here, the cloud application management data represents information for managing cloud applications held in the multi-device system 100. Furthermore, when a cloud application is divided into multiple cloud application components and held by different devices 10, the cloud application management data is managed for each cloud application component.
[0024] The abnormality flag indicates whether or not there is an abnormality with respect to the cloud app. The required memory and required storage indicate the memory size and storage size required to execute and store the cloud app, respectively. The holding device indicates the device 10 that holds the cloud app. The destination device indicates the device on which the cloud app is preferably run. For example, it is preferable for the cloud app to be executed on a device 10 with a large amount of free memory / free storage. However, when the multi-device system 100 is receiving the services of the cloud 200, the destination device is not specified. The data ID identifies the data referenced by the cloud app or the processing result data generated by the cloud app. The start date and time and the end date and time indicate the date and time when the execution of the cloud app started and ended in the multi-device system 100.
[0025] FIG. 2(c) shows an example of service usage data. The service usage data represents information related to the use of a service provided by a cloud app in the multi-device system 100. The service ID identifies a service provided by executing the cloud app. In this embodiment, one cloud app corresponds to one service ID. Also, even when a cloud app is divided into multiple cloud app components and distributed to multiple devices 10, the service ID identifies the service corresponding to one cloud app.
[0026] The status indicates whether the service (or the cloud app) is being used within the multi-device system 100. The operating time indicates the time the service (or the cloud app) has been used within the multi-device system 100. The number of accesses indicates the number of times the service (or the cloud app) has been accessed within the multi-device system 100. The last notification date and time indicates the date and time when the management tool 12 last notified the management server 220 of the status of the multi-device system 100.
[0027] The management tool 12 periodically updates the device management data, the cloud application management data, and the service usage data, or may update the device management data, the cloud application management data, and the service usage data every time a predetermined event occurs.
[0028] 3 shows an example of management data held by the management server 220 of the cloud 200. In this embodiment, the management server 220 holds service usage data and application data management information.
[0029] FIG. 3(a) shows an example of service usage data held in the cloud 200. As described above, the service ID identifies a service provided by executing a cloud app. The environment indicates whether a cloud app corresponding to the service is being executed in the multi-device system 100 that is being executed on the cloud 200. The operating time and the number of accesses are as described with reference to FIG. 2(c). However, the usage status within the multi-device system 100 is notified from the management device 10a. The update date and time indicates the date and time when the service usage data was updated.
[0030] 3(b) shows an example of application data management information. The application data management information identifies data referenced by a cloud application corresponding to the service or data generated by the cloud application. The start date and time and the end date and time respectively indicate the date and time when the use of the service (or the cloud application) started and ended.
[0031] 4 is a flowchart showing an example of the processing of the multi-device system 100. The processing of this flowchart is executed periodically, for example. At the start of the processing of this flowchart, it is determined whether the management tool 12 is operating normally. If the management tool 12 is not operating normally, the administrator of the multi-device system 100 is notified of this. It is assumed that at the start of the processing of this flowchart, the multi-device system 100 is operating using a service provided by the cloud 200.
[0032] In S1, the management tool 12 acquires cloud information indicating the settings of the cloud 200 and the services provided by the cloud 200. In S2, the management tool 12 collects device information indicating the state of each device 10 in the multi-device system 100. In S3 to S4, the management tool 12 detects the state of the cloud 200. If the cloud 200 is operating normally, the processing of the multi-device system 100 returns to S1. That is, while the cloud 200 is operating normally, the processing of S1 to S3 is repeatedly executed. On the other hand, if an abnormality in the cloud 200 is detected, the processing of the multi-device system 100 proceeds to S5.
[0033] In S5, the management tool 12 checks the placement of the cloud app in the local environment (i.e., the multi-device system 100). In S6, the management tool 12 selects a device that should execute the cloud app in the local environment. In S7, the management tool 12 transmits an instruction to the corresponding device 10 to rearrange the cloud app as necessary. This causes the rearrangement of the cloud app to be performed. In S8, the management tool 12 notifies each device 10 of the connection destination of the resident app 11 implemented in each device 10. In S9, each device 10 changes the settings in its own device based on the connection destination notified by the management tool 12. In S10, the management tool 12 collects usage information that indicates the usage status of the service in the local environment. In S11 to S12, the management tool 12 detects the state of the cloud 200. Then, when the abnormality of the cloud 200 continues, the processing of the multi-device system 100 returns to S5. That is, while the abnormal state continues, the processing of S5 to S11 is repeatedly executed. On the other hand, if the cloud 200 has recovered to a normal state, the process of the multi-device system 100 proceeds to S13.
[0034] In S13, the multi-device system 100 resumes the connection to the cloud 200. In S14, the management tool 12 notifies the management server 220 of the usage status of the cloud app in the local environment. In addition, the management tool 12 transmits to the cloud 200 processing result data obtained by executing the cloud app in the local environment.
[0035] In this way, when an abnormality occurs in the cloud 200, the multi-device system 100 executes the cloud app held in the local environment to continue operation. Therefore, even during a period when the services of the cloud 200 cannot be received, the multi-device system 100 can continue operation in the same manner as when the cloud 200 is normal. Furthermore, since a fault countermeasure is implemented in a single cloud without implementing a multi-cloud system, the service level is stabilized. In addition, when the cloud 200 is restored to a normal state, the usage status of the cloud app in the local environment is notified to the management server 220. Therefore, the cloud operator can reduce losses related to the usage fees for the cloud app.
[0036] 5 is a flowchart illustrating an example of a process for acquiring cloud information. The process of this flowchart corresponds to S1 illustrated in FIG.
[0037] If necessary, the cloud 200 changes the settings for connection to the application server 210 or the management server 220. Furthermore, the cloud 200 changes the services it provides if necessary.
[0038] In S21, the management tool 12 inquires of the management server 220 as to whether or not there has been a change in the settings, etc., of the cloud 200. If there has been a change, in S22, the management tool 12 acquires cloud information indicating the change in the settings, etc., of the cloud 200 from the management server 220.
[0039] 6 is a flowchart showing an example of a process for collecting device information. The process of this flowchart corresponds to S2 shown in FIG.
[0040] In S31, the agent tool 13 of each device 10 acquires device information of its own device. The device information includes metrics information indicating the amount of free memory and free storage, etc. The device information also includes information for identifying cloud applications held by the own device. In S32, the agent tool 13 of each device 10 transmits the acquired device information to the management tool 12. In S33, the management tool 12 updates the device management data shown in FIG. 2(a) based on the device information transmitted from each agent tool 13. In this way, the management tool 12 manages the state of each device 10 constituting the multi-device system 100 based on the device information transmitted from each agent tool 13.
[0041] 7 is a flowchart showing an example of a process for detecting the state of the cloud 200. The process of this flowchart corresponds to S3 shown in FIG.
[0042] In S41 to S42, the management tool 12 checks the connection with the cloud 200. For example, the management tool 12 may check the connection with the cloud 200 by sending a test message to the management server 220 and checking whether or not a response can be received. If an abnormality occurs in the connection with the cloud 200, the management tool 12 sets the connection abnormality flag to "1" in S43. If the connection with the cloud 200 is normal, the process of S43 is skipped.
[0043] In S44 to S45, the management tool 12 checks the status of the cloud app running on the cloud 200. For example, the management tool 12 may transmit a test request to the application server 210 and check the status of the cloud app running on the cloud 200 based on the response result. Then, when an abnormality occurs in the cloud app running on the cloud 200, the management tool 12 sets the service abnormality flag to "1" in S46. Note that, when the cloud app is running normally on the cloud 200, the process of S46 is skipped.
[0044] In this way, when an abnormality occurs in the connection with the cloud 200, the connection abnormality flag is set to "1." Also, when an abnormality occurs in the cloud 200, the service abnormality flag is set to "1." Then, when the connection abnormality flag and / or the service abnormality flag is "1," the processing of the multi-device system 100 proceeds to S5 shown in FIG.
[0045] 8 is a flowchart illustrating an example of a process for checking a cloud application in a local environment. The process of this flowchart corresponds to S5 in FIG.
[0046] In S51 to S52, the management tool 12 checks which device 10 holds the cloud application. At this time, the management tool 12 inquires, for example, of the agent tool 13 of each device 10 about the cloud application (or cloud application component) held by that device. In this case, in response to the inquiry, each agent tool 13 notifies the management tool 12 of information indicating the cloud application (or cloud application component) held by that device. Then, in S53, the management tool 12 updates the "held device" of the cloud application management data shown in FIG. 2(b) in response to the notification from each agent tool 13. Note that when the required cloud application is not held in the multi-device system 100, the management tool 12 notifies the administrator of the multi-device system 100 of that effect in S54.
[0047] 9 is a flowchart illustrating an example of a process for selecting a device that executes a cloud application. The process of this flowchart corresponds to S6 in FIG.
[0048] In S61, the management tool 12 determines whether the placement of the cloud app in the multi-device system 100 is appropriate. For example, when the free memory amount and the free storage amount of the device 10 that holds the cloud app are larger than respective predetermined thresholds, the device 10 can properly execute the cloud app, and therefore the current placement of the cloud app is determined to be appropriate. The free memory amount and the free storage amount of each device 10 are recorded in the device management data shown in FIG. 2(a).
[0049] If the placement of the cloud application is not appropriate, in S62 to S63, the management tool 12 selects the device 10 with the largest amount of free memory / free storage as the device that should execute the cloud application. Note that if the management tool 12 also manages the CPU load of each device 10, the management tool 12 may select the device that should execute the cloud application by taking into consideration the CPU load in addition to the amount of free memory / free storage. In other words, the management tool 12 selects the device that should execute the cloud application according to the resource margin of each device 10.
[0050] When a device on which the cloud application should be executed is selected, the management tool 12 updates the "destination device" of the cloud application management data shown in Fig. 2(b) in S64. When a device on which the cloud application should be executed cannot be selected, the management tool 12 notifies the administrator of the multi-device system 100 of that fact in S65.
[0051] 9, in S61, it is determined whether the current placement of cloud apps in the multi-device system 100 is appropriate, but the embodiment of the present invention is not limited to this procedure. That is, the management tool 12 may select the optimal device 10 in S62 without executing the process of S61.
[0052] 10 is a flowchart showing an example of a process for relocating a cloud application in the multi-device system 100. The process of this flowchart corresponds to S7 shown in FIG.
[0053] In S71, the management tool 12 transmits an instruction for transferring the cloud application to the corresponding device 10 in accordance with the selection in S62 of the flowchart shown in Fig. 9. Specifically, the management tool 12 creates a transfer instruction for transferring the cloud application (or cloud application component) corresponding to the "holding device" to the "destination device" recorded in the cloud application management data shown in Fig. 2(b). Then, this transfer instruction is given to the "holding device" and the "destination device."
[0054] In S72, the device 10 that has received the transfer instruction from the management tool 12 transmits or receives the designated cloud app. That is, the "holding device" transmits the designated cloud app to the "destination device." The "destination device" stores the cloud app received from the "holding device" in its own storage.
[0055] In this way, in the multi-device system 100, when the cloud 200 service is no longer available, the optimal device for executing the cloud app in the local environment is selected based on the amount of free resources of each device 10. Here, the amount of free resources of each device 10 is constantly changing. Therefore, by introducing this procedure, the service by the cloud app is appropriately provided, and it is also possible to prevent the performance of the device 10 from deteriorating due to an excessive load.
[0056] Note that, when it is determined in S61 of the flowchart shown in Fig. 9 that the current placement of the cloud app in the multi-device system 100 is appropriate, there is no need to execute the process shown in Fig. 10 (i.e., the rearrangement process shown in S7 of the flowchart shown in Fig. 4). In this case, the cloud app is not moved to another device, but is retained in the same device. However, in this specification, "relocation" includes retaining the cloud app in the same device 10.
[0057] 11 is a flowchart showing an example of a process for notifying each device 10 of a connection destination of the resident application 11. The process of this flowchart corresponds to S8 shown in FIG.
[0058] In S81, the management tool 12 identifies the device 10 that uses the cloud app. It is assumed that the management tool 12 manages which cloud app is used by each of the resident applications 11 of each device 10. The management tool 12 then notifies each of the devices 10 that uses the cloud app of information identifying a device that holds the cloud app used by the resident application 11 as a connection destination of the resident application 11. At this time, the information identifying the device that holds the cloud app after the relocation is notified to the corresponding device.
[0059] 12 is a flowchart showing an example of a process for changing the connection destination of the resident application 11 from the cloud to the local. The process of this flowchart corresponds to S9 shown in FIG.
[0060] In S91, the agent tool 13 of each device 10 changes the connection destination of the resident application 11 of the device from the cloud 200 to the corresponding cloud application in the multi-device system 100 in accordance with the notification from the management tool 12. In S92, each device 10 starts communication with the new connection destination. At this time, the agent tool 13 of each device 10 starts monitoring the usage status of the cloud application in the multi-device system 100. In S93, in accordance with the notification from the agent tool 13 of each device 10, the management tool 12 determines whether the communication with the new connection destination is normal. As a result, if the communication with the new connection destination is not normal, the management tool 12 notifies the administrator of the multi-device system 100 of that effect in S94.
[0061] 13 is a flowchart showing an example of a process for collecting usage information that indicates the usage status of a service in a local environment. The process of this flowchart corresponds to S10 shown in FIG.
[0062] In S101, the agent tool 13 of each device 10 monitors the usage status of the service by its own device. At this time, the agent tool 13 counts the usage time and / or the number of accesses of the cloud app held in the multi-device system 100. Then, the agent tool 13 notifies the management tool 12 of the monitoring result. In S102, the management tool 12 updates the service usage data shown in FIG. 2(c) based on the notification from each agent tool 13. That is, the management tool 12 manages the operation time and / or the number of accesses of each service (i.e., each cloud app).
[0063] 14 is a flowchart showing an example of a process for detecting the state of the cloud 200 when a cloud application is running in the local environment. The process of this flowchart corresponds to S11 shown in FIG.
[0064] The processing of S111 to S116 is almost the same as S41 to S46 shown in Fig. 7. However, when communication with the cloud 200 is restored to a normal state, the management tool 12 resets the connection abnormality flag to "0" in S113. Also, when the cloud 200 is restored to a normal state, the management tool 12 resets the service abnormality flag to "0" in S116. Then, if both the connection abnormality flag and the service abnormality flag are "0", the management tool 12 instructs each device 10 to change the connection destination. Then, the processing of the multi-device system 100 moves to S13 in the flowchart shown in Fig. 4.
[0065] 15 is a flowchart showing an example of a process for changing the connection destination of the resident application 11 from local to cloud. The process of this flowchart corresponds to S13 shown in FIG.
[0066] In S121, the agent tool 13 of each device 10 changes the connection destination of the resident application 11 of the device from the cloud application in the multi-device system 100 to the cloud 200 in accordance with an instruction from the management tool 12. Then, in S122, the agent tool 13 stops the cloud application held in the device in accordance with an instruction from the management tool 12. In S123, the agent tool 13 obtains processing result data by the cloud application and transmits it to the management tool 12. Thereafter, when using a service provided by the cloud 200, the device 10 accesses the cloud 200.
[0067] 16 is a flowchart showing an example of processing for notifying the service usage status to the management server 220. The processing of this flowchart corresponds to S14 shown in FIG.
[0068] In S131, the management tool 12 detects the usage status of the service in the local environment by referring to the service usage data shown in FIG. 2(c). The service usage data is updated by repeatedly executing S5 to S11 of the flowchart shown in FIG. 4 during the period in which the service is provided in the local environment. Then, the management tool 12 notifies the management server 220 of the usage status of the service in the local environment. This allows the management server 220 to grasp the amount of the service of the cloud 200 that the multi-device system 100 has used in the local environment. Therefore, the management server 220 can appropriately bill the multi-device system 100 for the service fee.
[0069] In S132, the management tool 12 transmits processing result data obtained by executing the cloud application in the local environment to the cloud 200. This allows the cloud 200 to continue processing by taking over the computation results in the local environment.
[0070] 17 is a sequence diagram showing an example of processing of the multi-device system 100. Note that S1 to S14 shown in FIG. 17 correspond to steps with the same numbers used in the flowchart shown in FIG.
[0071] The management device 10a (i.e., the management tool 12) communicates with the management server 220 of the cloud 200 and periodically acquires cloud information. The management device 10a also communicates with the agent tool 13 of each device 10 and periodically acquires device information. Then, upon detecting an abnormality in the cloud 200 or an abnormality in communication with the cloud 200, the multi-device system 100 transitions to a local operation mode in which a cloud app is executed in a local environment.
[0072] The management device 10a checks the placement of the cloud app in the local environment. The management device 10a also checks the resource status of each device 10 by referring to the device management data shown in FIG. 2(a). Then, the management device 10a selects a device 10 that executes the cloud app in the local environment. At this time, for example, the device 10 with the largest free resources (free memory, free storage, CPU computing capacity, etc.) is selected.
[0073] Each device 10 relocates the cloud app in response to the selection made by the management device 10a. Also, each device 10 changes the connection destination of the resident app 11 of its own device in response to a notification from the management device 10a. Then, each device 10 operates while using the cloud app in the local environment. After that, the management device 10a monitors the usage status of the service in the local environment. At this time, the management device 10a monitors the operating time or the number of accesses of the cloud app implemented in the multi-device system 100.
[0074] During the period when the cloud application is executed in the local environment, the management device 10a periodically monitors the state of the cloud 200. Then, when the cloud 200 recovers to a normal state, the management device 10a instructs each device 10 to resume connection to the cloud 200. As a result, each device 10 changes the connection destination of the resident application 11 of the device to the cloud 200. Also, each device 10 stops the cloud application implemented in the device. Furthermore, the management device 10a notifies the management server 220 of the cloud 200 of the usage status of the service during the period when the cloud application was running in the local environment. Therefore, the management server 220 can know the time or number of times the service was used in the local environment. After that, each device 10 operates by using the service provided by the cloud 200.
[0075] 18 to 21 show an example of the operation of the multi-device system 100. In this example, as shown in FIG. 18, a resident application of each device 10 requests processing from a cloud application APP_1 to receive a service. The cloud application APP_1 requests processing from a cloud application APP_2 to receive a service. The cloud application APP_1 is divided into cloud application components APP_1x and APP_1y, which are implemented in the devices 10b and 10c, respectively. However, when the cloud 200 is operating normally, the cloud application components APP_1x and APP_1y are not executed in the multi-device system 100.
[0076] As described above, the management device 10a constantly monitors whether the cloud 200 and the communication with the cloud 200 are normal. When the management device 10a detects an abnormality, the multi-device system 100 transitions to a local operation mode in which the cloud application is executed in a local environment.
[0077] 19, an abnormality occurs in the cloud application APP_1 in the cloud 200. It is assumed that the cloud application APP_2 is normal, and the communication between the multi-device system 100 and the cloud 200 is also normal.
[0078] In this case, the management device 10a sets the service abnormality flag corresponding to the cloud application APP_1 to "1" in S46 of the flowchart shown in FIG. 7. Next, the management device 10a selects the device 10 that should execute the cloud application components APP_1x and APP_1y in S61 to S62 of the flowchart shown in FIG. 9. In this embodiment, it is assumed that the device 10b has sufficient free resources to execute the cloud application component APP_1x, but the device 10c does not have sufficient free resources to execute the cloud application component APP_1y. It is also assumed that the device 10d has sufficient free resources. Then, the device 10b and the device 10d are selected as the devices that should execute the cloud application components APP_1x and APP_1y, respectively.
[0079] In response to the above selection, the management device 10a instructs the device 10c to transmit the cloud application component APP_1y to the device 10d. Then, in response to the instruction from the management device 10a, the device 10c transmits the cloud application component APP_1y held by itself to the device 10d. Then, the device 10d installs the received cloud application component APP_1y in its own storage. After this, the management device 10a instructs each device 10 of the connection destination of the resident application.
[0080] The resident application of each device 10 accesses the cloud application according to the connection destination notified by the management device 10a. In this embodiment, as shown in FIG. 20, the resident application of each device 10 requests processing from the cloud application component APP_1x implemented in the device 10b to receive the service. The cloud application component APP_1x requests processing from the cloud application component APP_1y implemented in the device 10d to receive the service. The cloud application component APP_1y requests processing from the cloud application APP2 implemented in the cloud 200 to receive the service.
[0081] The agent tool of each device 10 monitors the usage status of services in the local environment. For example, the agent tool of device 10b monitors access to cloud application component APP_1x, and the agent tool of device 10d monitors access to cloud application component APP_1y. These monitoring results are then collected by the management device 10a. This allows the multi-device system 100 to continue operating in the same manner as when the cloud 200 is normal (i.e., the state shown in FIG. 18).
[0082] When the cloud 200 is restored to a normal state, the management device 10a changes the connection destination of the resident apps of each device 10 to the cloud 200. In addition, the devices 10b and 10d stop the cloud application components APP_1x and APP_1y implemented in their own devices, respectively, in response to an instruction from the management device 10a, as shown in FIG. 21. Furthermore, the management device 10a notifies the cloud 200 of the usage status of the service in the local environment, and transmits to the cloud 200 processing result data obtained by executing the cloud app in the local environment. This allows the cloud 200 to grasp the amount of use of the service of the cloud 200 by the multi-device system 100 in the local environment, and also allows the cloud 200 to take over the processing result data by the cloud app in the multi-device system 100. After this, the resident apps of each device 10 access the cloud 200. [Explanation of symbols]
[0083] 10(10b~10d) devices 10a Managed Devices 11 Resident apps 12 Administrative Tools 13 Agent Tools 100 Multi-Device System 200 Cloud 210 Application Server 220 Management Server 300 Network
Claims
1. A multi-device system comprising a plurality of devices and a management device for managing the plurality of devices, the multi-device system operating using a service provided by a cloud, any one of the plurality of devices holds an application program for implementing the service within the multi-device system; when the management device detects an abnormality in the cloud or in communication with the cloud, instructs each of the plurality of devices to change a connection destination from the cloud to a device that stores the application program; Each of the plurality of devices accesses the application program in response to an instruction from the management device. A multi-device system comprising:
2. The management device includes: selecting a device to execute the application program from among the plurality of devices based on a resource state of each of the plurality of devices when an abnormality in the cloud or in communication with the cloud is detected; relocating said application program to a selected device; Each of the plurality of devices accesses the relocated application program. The multi-device system according to claim 1 .
3. the application program is composed of a plurality of application program components, the plurality of application program parts are held by different devices of the plurality of devices; The management device relocates the application program parts to different devices among the plurality of devices based on a resource state of each of the plurality of devices.
3. The multi-device system according to claim 2.
4. When the management device detects recovery from an abnormality in the cloud or in communication with the cloud, the management device changes a connection destination of the plurality of devices from the application program to the cloud. The multi-device system according to claim 1 .
5. The management device includes: monitoring the usage of the application program within the multi-device system; When recovery from an abnormality in the cloud or in communication with the cloud is detected, the usage status is notified to the cloud. The multi-device system according to claim 1 .
6. The usage status indicates the operating time or the number of accesses of the application program in the multi-device system.
6. The multi-device system according to claim 5.
7. When the management device detects recovery from an abnormality in the cloud or in communication with the cloud, the management device transmits processing result data by the application program in the multi-device system to the cloud. The multi-device system according to claim 1 .
Citation Information
Patent Citations
Server, information processing system, and control method
JP2021087162A
