JP7619059B2 - Management system and communication device - Google Patents

Description

This disclosure relates to a management system and a communication device.

A system is already known in which a server device acquires setting information for configuring an image forming device from a management device, and provides the acquired setting information to the image forming device in response to an inquiry from the image forming device. According to this system, a setting unit of the image forming device acquires setting information sent from the server device, and configures the image forming device using the acquired information (see, for example, Patent Document 1).

JP 2019-148957 A

In conventional systems, the server device actively operates to achieve smooth functioning related to settings from the management device to the image forming device. However, this technology requires the construction of a dedicated server device, and the operating costs of the server device are high.

On the other hand, if a general-purpose intermediate device is used instead of a dedicated server device, the intermediate device cannot realize the diverse functions required for different applications that can be realized by using a dedicated server device.

Therefore, according to one aspect of the present disclosure, it is desirable to provide a technology that allows an administrator to easily grasp the execution status of a task in a system in which a first communication device requests a second communication device to execute a task via a general-purpose intermediate device.

A management system according to one aspect of the present disclosure includes a first communication device and a second communication device. The first communication device and the second communication device are configured to be able to access cloud storage. The first communication device is configured to execute a first process related to the cloud storage. The second communication device is configured to execute a second process related to the cloud storage.

The first process involves writing request data requesting the execution of a task to cloud storage.

The second process includes repeatedly referencing the cloud storage and, when the request data is written to the cloud storage, executing a task according to the request data, or having the third communication device execute the task through communication with the third communication device. The second process further includes writing status data describing the execution status of the task to the cloud storage.

The first process further includes repeatedly referring to the cloud storage and determining the execution status of the task based on the status data in the cloud storage. The first process further includes displaying a screen on the display device that explains the execution status of the task, and updating the screen based on the determined execution status of the task.

According to one aspect of the present disclosure, in a system in which a first communication device requests a second communication device to execute a task via cloud storage, which is a general-purpose intermediate device, an administrator can easily grasp the status of task execution through a screen displayed on a display device.

According to one aspect of the present disclosure, a communication device for realizing a management system may be provided. The communication device according to one aspect of the present disclosure includes a communication unit capable of accessing cloud storage, and a processing unit configured to execute processing related to the cloud storage. The processing related to the cloud storage includes repeatedly referencing the cloud storage via the communication unit, and, when request data requesting execution of a task is written to the cloud storage, executing a task according to the request data.

The processing related to the cloud storage further includes gradually notifying the task execution requester of the task execution status by writing status data describing the task execution status to the cloud storage multiple times before and after the task execution is completed.

If a management system is configured using such a communication device, the source of a task execution request can grasp the task execution status in detail via cloud storage, which is a general-purpose intermediate device, and can convey the execution status in detail to the administrator, for example by displaying the execution status to the administrator.

A communication device according to one aspect of the present disclosure includes a communication unit capable of accessing cloud storage and a processing unit configured to execute processing related to the cloud storage. The communication unit is further configured to be capable of communicating with one or more managed devices within a local area network.

Processing related to cloud storage includes repeatedly referencing the cloud storage via the communication unit, and when request data requesting execution of a task is written to the cloud storage, communicating with one or more managed devices within the local area network and causing the one or more managed devices to execute a task according to the request data.

The processing related to the cloud storage further includes gradually notifying the task execution requester of the task execution status by writing status data describing the task execution status to the cloud storage multiple times before and after the task execution is completed on one or more managed devices.

If a management system is constructed using such a communication device, even if the managed devices cannot directly access cloud storage, the source of the task execution request can request the managed devices to execute a task, and furthermore, the execution status can be displayed to the administrator, providing the administrator with detailed information about the execution status.

A communication device according to one aspect of the present disclosure includes a communication unit capable of accessing cloud storage and a processing unit configured to execute processing related to the cloud storage. The processing related to the cloud storage includes writing request data requesting execution of a task to the cloud storage via the communication unit.

The processing related to the cloud storage further includes repeatedly referencing the cloud storage and determining the execution status of the task based on status data describing the execution status of the task that is written to the cloud storage from a device that executes processing according to the request data. The processing related to the cloud storage further includes displaying a screen describing the execution status of the task on a display device, and updating the screen based on the determined execution status of the task.

This type of communication device can request an external device to execute a task via cloud storage, which is a general-purpose intermediate device, and can also grasp the execution status of the task and provide the administrator with detailed information about the execution status by displaying the execution status.

FIG. 1 is a block diagram showing an overall configuration of a management system. FIG. 2A is a block diagram showing the configuration of a master, FIG. 2B is a block diagram showing the configuration of a client, and FIG. 2C is a block diagram showing the configuration of a first type terminal device. FIG. 3A is a block diagram showing the configuration of a second type terminal device, and FIG. 3B is a block diagram showing the configuration of a cloud server. FIG. 4 is a schematic sequence diagram relating to the operation of the management system. FIG. 5A is a diagram showing the configuration of a schedule task table, and FIG. 5B is a diagram showing the configuration of an instant task table. 11 is a sequence diagram illustrating the operation of the master and the cloud connector when creating a file transmission task and a setting task for the cloud connector. FIG. 11 is a flowchart showing an instant task-related process executed by a cloud connector. FIG. 11 is a sequence diagram illustrating the operations of a master, a client, and a first type terminal device when a file transmission task is created for the first type terminal device. FIG. 11 is a sequence diagram illustrating the operations of a master, a client, and a first type terminal device when creating a setting task for the first type terminal device. 13 is a flowchart showing an instant task relay process executed by a control unit of a client. FIG. 13 is a functional block diagram showing the functions of a master regarding an instant task. 11 is a flowchart showing a creation and registration process executed by a control unit of the master. FIG. 13A is a flowchart showing an acquisition and update process that is repeatedly executed by the control unit of the master, and FIG. 13B is a flowchart showing a display control process that is repeatedly executed by the control unit of the master. 14A and 14B are diagrams illustrating examples of the configuration of a task management screen. 11 is a flowchart showing a screen update process executed by a control unit of a master. FIG. 13 is a diagram illustrating an example of a configuration of a details screen.

Exemplary embodiments of the present disclosure will now be described with reference to the drawings.
[Overall configuration]
A management system 1 according to an exemplary embodiment of the present disclosure is a network system configured to manage terminal devices 4 and 5 arranged at multiple locations via a cloud server 6 through cooperation between a master 2 and a client 3 .

The master 2 illustrated in FIG. 1 is configured to be able to communicate with a terminal device 4 installed at a first base via a local area network. The master 2 is further configured to be able to communicate with a cloud server 6 via a wide area network.

The client 3 is configured to be able to communicate with a terminal device 4 installed at a second location via a local area network. The client 3 is further configured to be able to communicate with a cloud server 6 via a wide area network. The terminal device 5 installed at a third location is configured to be able to communicate with the cloud server 6 via a wide area network.

The local area network may include, for example, at least one of a wireless LAN and a wired LAN. The wide area network may include, for example, the Internet. A local area network may be constructed in the third location. In this case, the terminal device 5 may be connected to the wide area network via the local area network in the third location.

The terminal device 4 does not have the ability to use the cloud services provided by the cloud server 6. In other words, each terminal device 4 does not have the function of communicating with the cloud server 6. Below, this terminal device 4 is particularly referred to as a first type terminal device 4. On the other hand, the terminal device 5 is a terminal device that has the ability to use the cloud services provided by the cloud server 6. In other words, the terminal device 5 has the function of communicating with the cloud server 6. Below, this terminal device 5 is particularly referred to as a second type terminal device 5.

The first type terminal device 4 installed at the second base is managed by the master 2 via the client 3 and the cloud server 6. The second type terminal device 5 installed at the third base is managed by the master 2 via the cloud server 6, not via the client 3.

The terminal devices 4 and 5 managed by the master 2 may be, for example, a group of terminal devices managed by an organization such as a company. In this case, each base may be an activity base of the organization. In one example, the first base where the master 2 exists may be an office that has the management department of the organization. The other second and third bases may be branch offices of the organization that are distant from the first base.

Examples of terminal devices 4 and 5 include printers, scanners, and digital multifunction peripherals that integrate these functions. The master 2 and client 3 are configured, for example, by installing a dedicated computer program on a personal computer.

[Device configuration]
2A includes a control unit 11, a communication unit 12, a display unit 13, an input unit 14, and a storage unit 15. The control unit 11 includes a CPU 21 and a memory 22. The CPU 21 as a processor executes processing in accordance with a computer program stored in the storage unit 15. The memory 22 is used as a work memory when the above processing is executed.

The memory unit 15 includes storage such as a solid state drive (SSD) and a hard disk drive (HDD), and stores various computer programs and data. The memory unit 15 stores a main management program 15a. The main management program 15a is a computer program for causing the CPU 21 to realize the management functions to be realized by the master 2. The processing mainly performed by the control unit 11 described below may be understood to be realized by processing executed by the CPU 21 in accordance with the computer program.

The communication unit 12 is connected to the local area network of the base where the master 2 exists, and is further connected to a wide area network. The communication unit 12 may be connected to the wide area network via a router (not shown). The display unit 13 is configured to display various screens for a user who operates the master 2. An example of the display unit 13 is a liquid crystal display. Examples of the various screens include a screen for displaying log information and status information of the managed terminal devices 4 and 5, and a screen for remotely operating the terminal devices 4 and 5 according to an operation signal from the user.

The input unit 14 includes one or more input devices, such as a keyboard and a pointing device, for inputting operation signals from a user who operates the master 2. The control unit 11 operates according to the operation signals input through the input unit 14.

The client 3 shown in FIG. 2B includes a control unit 31, a communication unit 32, a display unit 33, an input unit 34, and a storage unit 35. The control unit 31 includes a CPU 41 and a memory 42. The CPU 41 as a processor executes processing according to a computer program stored in the storage unit 35.

The storage unit 35 stores a sub-management program 35a. The sub-management program 35a is a computer program for causing the CPU 41 to realize functions related to the management functions of the master 2 that should be realized by the client 3. The processing mainly performed by the control unit 31 described below may be understood to be realized by processing executed by the CPU 41 in accordance with the computer program.

The communication unit 32 is connected to the local area network of the base where the client 3 exists, and is further connected to a wide area network. The communication unit 32 may be connected to the wide area network via a router (not shown). The display unit 33 includes, for example, a liquid crystal display, and is configured to display various screens for the user operating the client 3. The input unit 34 has one or more input devices for inputting operation signals from the user operating the client 3. The control unit 31 operates according to the operation signals input through the input unit 34.

The first type terminal device 4 shown in FIG. 2C includes a control unit 51, a communication unit 52, a display unit 53, and an input unit 54. When the first type terminal device 4 is a digital multifunction device, the first type terminal device 4 can further include a printing unit 55 and a reading unit 56. The first type terminal device 4 may include only one of the printing unit 55 and the reading unit 56.

The control unit 51 includes a CPU 61 and a memory 62. The memory 62 can include a non-volatile memory such as a RAM or a flash memory, and can store computer programs, setting data, and the like.

The CPU 61 as a processor performs overall control of the entire first type terminal device by executing processing according to a computer program stored in the memory 62. The processing mainly performed by the control unit 51 described below may be understood to be realized by processing performed by the CPU 61 according to the computer program.

The communication unit 52 is connected to the local area network of the base where the first type terminal device 4 exists so as to be able to communicate with the master 2 or client 3 present there. The display unit 53 includes, for example, an LCD display, and is configured to display various screens for the user who operates the first type terminal device 4. The input unit 54 includes one or more input devices, such as a touch panel on an LCD display, for inputting operation signals from the user.

The printing unit 55 is configured to be controlled by the control unit 51 and to print an image on a sheet. Examples of the printing unit 55 include an inkjet printer and a laser printer. According to this embodiment, status information such as the remaining amount of coloring material and log information such as the number of printed sheets are provided to the master 2 from the first type terminal device 4 via the client 3 and the cloud server 6 in a manner described below. The reading unit 56 is configured to be controlled by the control unit 51 and to read a reading target such as a printed matter.

The second type terminal device 5 shown in FIG. 3A includes a control unit 71, a communication unit 72, a display unit 73, and an input unit 74. When the second type terminal device 5 is a digital multifunction device, the second type terminal device 5 can further include a printing unit 75 and a reading unit 76. The second type terminal device 5 may include only one of the printing unit 75 and the reading unit 76.

The control unit 71 includes a CPU 81 and a memory 82. The memory 82 can include a non-volatile memory such as a flash memory, and can store computer programs, setting data, and the like in the non-volatile memory.

The CPU 81 as a processor performs overall control of the entire device by executing processing according to a computer program stored in the memory 82. A communication program 82a is stored in the memory 82. The communication program 82a is a program for using a cloud service provided by the cloud server 6. The processing mainly performed by the control unit 71 described below may be understood to be realized by processing executed by the CPU 81 according to the computer program.

The communication unit 72 is connected to a wide area network so as to be able to communicate with the cloud server 6. If a local area network is constructed at the third location, the communication unit 72 may be connected to the wide area network via the local area network. The display unit 73 includes, for example, a liquid crystal display. The input unit 74 includes one or more input devices for inputting operation signals from the user.

The printing unit 75 is configured to be controlled by the control unit 71 and to print an image on a sheet. According to this embodiment, status information such as the remaining amount of coloring material and log information such as the number of printed sheets are provided to the master 2 from the second type terminal device 5 via the cloud server 6 in a manner described below. The reading unit 76 is configured to be controlled by the control unit 71 and to read a reading target such as a printed matter.

The cloud server 6 shown in FIG. 3B includes a control unit 91, a communication unit 92, a first storage 93, and a second storage 94. The control unit 91 includes a CPU 101 and a memory 102.

The CPU 101 as a processor executes processing according to a computer program stored in the memory 102. The processing executed by the CPU 101 includes processing for causing the cloud server 6 to function as cloud storage. The processing mainly performed by the control unit 91 described below may be understood to be realized by processing executed by the CPU 101 according to the computer program.

The above cloud storage includes table storage and object storage. By executing the above process by the control unit 91, the first storage 93 functions as table storage and the second storage 94 functions as object storage.

The exemplary first storage 93 functions as a NoSQL data store and is configured to store tables that are made up of a collection of schema-less entities. Each entity in a table is made up of a set of properties, and each property is made up of a key and a value pair.

The exemplary second storage 94 functions as an object storage that can read and write any text files and binary files as objects from the outside using the HTTP/HTTPS protocol.

Microsoft's Azure (registered trademark) is known as a cloud service that provides the above-mentioned table storage and object storage. Cloud server 6 can operate in the same manner as such a cloud service.

[Sequence Overview]
Next, an operational sequence related to management will be outlined with reference to Fig. 4. In the preparation stage, a main management program 15a is installed in the master 2. A process in accordance with the main management program 15a is executed by the control unit 11 of the master 2, and a cloud profile is set (S01).

In the client 3 and the second type terminal device 5, as described below, a polling operation for the cloud server 6 and an update operation of information held in the cloud server 6 are executed. Setting the cloud profile (S01) includes setting cloud parameters. The cloud parameters include a period for the polling operation (hereinafter referred to as the "polling period") and a period for the information update operation (hereinafter referred to as the "information update period"). Setting the cloud profile (S01) further includes setting a shared access signature (SAS: Shared Access Signature) for using the cloud service.

The cloud profile is set, for example, according to a setting operation performed by the main administrator, who is the user of the master 2, via the input unit 14. The SAS is set individually for each of the first storage 93 and the second storage 94, i.e., the table storage and the object storage.

Then, cloud parameters according to the set cloud profile are uploaded from the master 2 to the first storage 93 of the cloud server 6 (S02) and written to the first storage 93 (S03). The cloud parameters, including the polling period and the information update period, are written to the first storage 93 as table entities.

Furthermore, at least a portion of the cloud profile is exported from the master 2 as a client profile, i.e., data to be read by the client 3 (S04). The client profile may include, for example, the cloud parameters described above.

The exported client profile is provided to the client 3. The client profile may be provided to the client 3 by any method. For example, the client profile may be sent from the master 2 to the client 3 by email or other method. Also, for example, the client profile may be provided by the main administrator to the sub-administrator who is the user of the client 3. More specifically, for example, the main administrator may store the client profile in an information processing terminal owned by the main administrator and send the client profile to another information processing terminal owned by the sub-administrator, so that the sub-administrator can transfer the client profile from the other information processing terminal to the client 3. The main administrator may send the client profile from his/her own information processing terminal to the client 3. Also, for example, the main administrator may store the client profile in a specified storage and provide the storage to the sub-administrator, so that the sub-administrator can transfer the client profile from the storage to the client 3.

The sub-administrator operates the client 3 to install the sub-management program 35a on the client 3 (S06). At this time, the client profile provided from the master 2 is imported by the sub-administrator's operation, and cloud parameters and SAS according to the client profile are set on the client 3 (S05).

After the above installation and settings, the client 3 is configured to be able to use the cloud server 6. As a result, the client 3 is configured to be able to transmit information to the master 2 via the cloud server 6. Specifically, the client 3 is configured to be able to execute relay operations between the master 2 and the first type terminal device 4 via the cloud server 6, such as sending task execution instructions from the master 2 to the first type terminal device 4 and transmitting log information and status information from the first type terminal device 4 to the master 2.

Meanwhile, the SAS is registered in the second type terminal device 5 by an input operation by the device administrator who is the administrator of the second type terminal device 5 (S07). The control unit 71 of the second type terminal device 5 in which the SAS is registered executes processing in accordance with the communication program 82a. The control unit 71 executing processing in accordance with the communication program 82a is hereinafter referred to as the "cloud connector." The cloud connector references the cloud parameters written by the master 2 in the first storage 93 of the cloud server 6 (S08). The cloud connector acquires these cloud parameters and sets them in its own device (S08).

When the initial settings (S05 to S08) of the client 3 and the second type terminal device 5 (cloud connector), including the settings of the cloud parameters and SAS described above, are completed, the client 3 and the second type terminal device 5 execute a scheduled task that periodically updates the information stored in the first storage 93 of the cloud server 6 according to the set information update period.

The schedule task begins with registering device information in the first storage 93 (S09, S10). The first storage 93 has a schedule task table as one of its tables. As shown in FIG. 5A, the schedule task table is made up of a group of entities including properties of a first key, a second key, a request parameter, a response parameter, a notification source, a progress status, and a device ID.

The schedule task table has three entities related to "log," "status," and "registration" for each of the terminal devices 4 and 5, and the information in the entities is updated by the client 3 that manages the corresponding first-type terminal device 4 or the cloud connector of the corresponding second-type terminal device 5 (S09, S10).

The "notification source" property in an entity indicates who updated the entity; when the entity is updated by client 3, the "notification source" property is updated to the value "client", and when the entity is updated by the cloud connector, the "notification source" property is updated to the value "device".

The entity related to "log" is a log entity having the value "log" of the first key, and describes in the response parameters one piece of log information of the terminal device 4, 5 corresponding to the device ID described as the value of the second key. The device ID is an ID unique to each of the terminal devices 4, 5.

When the corresponding terminal device is a printer or digital multifunction device, the log information may include information on the total number of pages printed by the corresponding terminal device. The log information may include, as a print history, information on the user who issued the print command and the number of pages printed for each print job.

As illustrated in the lower part of FIG. 5A, the response parameters may include, for example, JSON data. For example, the log information may be described in JSON format by associating the object identifier (OID) used in the management information base (MIB) of the corresponding parameter with its value. The descriptions "x.x.x.x.x...", "y.y.y.y..." in the lower part of FIG. 5A correspond to abstract representations of object identifiers. The response parameters in the initial state before being updated may exist as request parameters in which an initial value is associated with an object identifier. According to the example in the lower part of FIG. 5A, the initial value "%MIB(y.y.y.y.y...)%" associated with the OID "y.y.y.y.y..." has been rewritten to the value "4" by the update.

An entity related to "status" is a status entity that has the value "status" of the first key, and describes in the response parameters the status information of one of the terminal devices 4, 5 corresponding to the device ID described as the value of the second key. When the corresponding terminal device is a printer or digital multifunction device, the status information may include information on the remaining amount of coloring material in the corresponding terminal device and error information such as paper jams. As with the log entity, the response parameters in the status entity may be described in JSON format.

The entity related to "registration" is a registration entity that has the value "registration" of the first key, and describes in the response parameters one piece of device information of the terminal device 4, 5 that corresponds to the device ID described as the value of the second key. In the response parameters, multiple item values that explain the basic configuration of the device are described as device information.

In the schedule task table, the entity of the cloud connector of the second type terminal device 5 is updated by the cloud connector (S09). The entity of the first type terminal device 4 is updated by the client 3 connected to the same local area network as the first type terminal device 4 (S10). That is, the client 3 updates the entity for each first type terminal device 4 under the client 3. The identification information of the client 3 that has the first type terminal device 4 under its control is written as part of the device information in the registered entity of the first type terminal device 4.

By processing the control unit 31 according to the sub-management program 35a, the client 3 communicates with each first-type terminal device 4 in the local area, obtains information necessary for updating device information from each first-type terminal device 4, and can update the registration entity of the corresponding first-type terminal device 4 (S10).

The client 3 periodically communicates with each of the subordinate first type terminal devices 4 within the local area to obtain corresponding log information and status information, and can update the log entities and status entities of each of the first type terminal devices 4 in the first storage 93 of the cloud server 6 (S10).

The cloud connector of the second type terminal device 5 can periodically access the cloud server 6 and update its own log entity and status entity in the first storage 93 so as to update its own log information and status information (S09).

The master 2 also functions as a client 3. That is, the master 2 can be understood to function as a client 3 with respect to the first type terminal device 4 at the first base. Specifically, the master 2, like the client 3, can update the registration entities, log entities, and status entities of each of the subordinate first type terminal devices 4 in the first storage 93 of the cloud server 6.

The master 2 can further periodically access the cloud server 6 to refer to the log entities, status entities, and registration entities of the terminal devices 4 and 5 in the first storage 93, and, based on these references, execute a process of storing the log information, status information, and device information of each of the terminal devices 4 and 5 in the memory unit 15 (S11).

Furthermore, the master 2 can display a list of the registered terminal devices 4 and 5 on the screen of the display unit 13, and can display log information and status information of the terminal devices 4 and 5, in accordance with an operation signal from the user via the input unit 14 (S11). In this way, the management system 1 is configured to be able to remotely monitor the status of the terminal devices 4 and 5 used at multiple locations from one location where the master 2 is installed.

In addition, according to the management system 1, instant tasks, which are non-periodic tasks other than scheduled tasks, are executed by the terminal devices 4 and 5 based on a request from the master 2. The master 2 requests the corresponding terminal devices 4 and 5 to execute an instant task by registering an entity of the instant task in the first storage 93 (S13). For example, a firmware update in the terminal devices 4 and 5 is realized as one of the instant tasks.

The master 2 can accept an instant task execution request operation from the user of the master 2 according to an operation signal from the user via the input unit 14 (S12) and register the corresponding entity (S13).

The first storage 93 includes an instant task table as shown in FIG. 5B. The instant task table, like the schedule task table, is made up of a group of entities including properties of a first key, a second key, a request parameter, a response parameter, a notification source, a progress status, and a device ID.

An entity in the instant task table (hereinafter referred to as an instant task entity) is an entity in which "instant task" is entered as the value of the first key. The property of the second key in the instant task entity has a transaction ID as its value. The transaction ID is a unique ID for each instant task that occurs at the same time, and is used to distinguish between the entities of multiple instant tasks that occur at the same time.

The device ID of the terminal device 4, 5 to which the instance task is requested is described as a value in the device ID property of the instant task entity. When an instant task is requested to multiple first type terminal devices 4 under the client 3, the device ID of each of the multiple first type terminal devices 4 is described in the device ID property.

The request parameters in the instant task entity contain data as values that describe the content of the processing to be executed as an instant task. The processing content is described, for example, as JSON data.

If the instant task requested to be executed by the master 2 is a firmware update for the terminal devices 4 and 5, the master 2 stores the firmware update file in the second storage 94, which functions as an object storage (S14). In this case, the request parameters describe the URL of the storage destination of the firmware update file.

The cloud connector of the second type terminal device 5 accesses the first storage 93 of the cloud server 6 at the set polling period and determines whether a new entity of an instant task that the device should execute has been registered in the instant task table (S15).

If a new entity is registered, the cloud connector communicates receipt of the instant task request to the master 2 by updating the value of the progress property of the corresponding instant task entity in the first storage 93 from "Requested" to "In Progress" (S15).

To check the status, Master 2 periodically refers to the instant task entity in the first storage 93 (S18). By periodically referring to the instant task entity, Master 2 can confirm that the instant task request has been received based on the updated value of the progress status property.

When executing an instant task, the cloud connector of the second type terminal device 5 refers to the request parameters of the instant task entity (S15). If the data file required to execute the instant task exists in the second storage 94 based on the referenced request parameters, the cloud connector downloads the data file from the second storage 94 based on the storage destination URL described in the request parameters (S16) and executes the instant task.

When the instant task is completed, the cloud connector of the second type terminal device 5 changes the value of the progress status property from "in progress" to "completed" and updates the corresponding instant task entity in the first storage 93 to write the processing result as a response parameter (S17).

Similarly to the cloud connector of the second type terminal device 5, the client 3 also accesses the first storage 93 of the cloud server 6 at the set polling period and determines whether or not a new entity of an instant task to be executed by the subordinate first type terminal device 4 is registered in the instant task table (S19). Hereinafter, each of the subordinate first type terminal devices 4, one or more first type terminal devices 4 that are set as instant task execution targets in the instant task table (i.e., one or more first type terminal devices 4 whose device ID is described in the device ID property) will be referred to as an "instant task execution target".

If a new entity has been registered, the client 3 updates the corresponding instant task entity in the first storage 93 so as to update the value of the progress property from "Requested" to "In Progress" (S19). The client 3 further obtains data files required for execution of the instant task from the second storage 94 as necessary by referencing the request parameters (S20).

Then, the client 3 instructs the instant task execution targets to execute the instant task via the local area network (S21). At this time, the client 3 transfers the data files required for the execution obtained from the second storage 94 to each instant task execution target (S21).

When the execution of the instant task is completed for all instant task execution targets, the client 3 updates the corresponding instant task entity in the first storage 93 so as to change the value of the progress status property from "in progress" to "completed" and write the processing result as a response parameter (S22). By updating this entity, the client 3 notifies the master 2 of the execution progress and processing result of the instant task for the instant task execution targets via the first storage 93 of the cloud server 6 (S22).

To check the status, the master 2 refers to the instant task entity in the first storage 93, and by finding that the value of the progress status property has been updated to "Completed", it confirms that the instant task has been completed, and writes the processing result to the memory unit 15 (S23).

The master 2 can further display the processing results on the screen of the display unit 13. When the master 2 confirms that the registered instant task has been completed on all of the target terminal devices 4 and 5, in other words, that the instant task is no longer necessary (S24), it deletes the instant task entity that is no longer necessary from the first storage 93 (S25), and deletes the data file (e.g., a firmware update file) in the second storage 94 that was used for the instant task (S26).

In this way, the management system 1 is configured to be able to remotely control the terminal devices 4 and 5 used at multiple locations from one location where the master 2 is installed by registering and updating instant task entities in the first storage 93 of the cloud server 6, and further by transferring data files via the second storage 94.

[Detailed description of instant task]
Next, the instant tasks will be described in detail. In addition to the firmware update task described above, the instant tasks include a file transmission task and a setting task.

The file transmission task is a task in which the master 2 transmits a specified data file to the terminal devices 4 and 5, and the terminal devices 4 and 5 receive and store the data file from the master 2. The setting task is a task in which the terminal devices 4 and 5 change the setting values of the operating parameters of their own devices according to the setting file provided by the master 2.

With regard to the file transmission task and the setting task, the second type terminal device 5, in other words the cloud connector, operates as shown in FIG. 6.

The master 2 creates a file transmission task or a setting task based on an instruction from a user via the input unit 14. The master 2 then accesses the cloud server 6 to register the corresponding instant task entity in the instant task table of the first storage 93, and uploads the data files required to execute the task to the second storage 94.

When the destination of a task execution request is a second type terminal device 5, the device ID of the second type terminal device 5 that is the destination of the execution request is described in the device ID property of the instant task entity. The request parameters describe the content of the task to be executed in JSON format, as well as the storage URL of the data file required to execute the task.

In the case of a file transmission task, the data file stored in the second storage 94 by uploading is the data file to be transmitted, for example, a data file in the memory unit 15 of the master 2 specified by the user. In the case of a setting task, the data file stored is a setting file that describes the setting values of each operating parameter to be set at the destination of the task execution request.

Since the cloud server 6 is a server that provides a general-purpose storage function on a wide area network, even if the master 2 registers a new instant task entity in the first storage 93, this is not actively communicated from the cloud server 6 to the terminal devices 4 and 5. The registration of a new instant task entity is detected by a polling operation that is periodically executed by the cloud connector.

The cloud connector (control unit 71) periodically executes the instant task-related processing shown in FIG. 7, including the polling operation, at a polling period that is set in advance as a cloud parameter by the master 2.

When instant task-related processing starts, the cloud connector accesses the first storage 93 of the cloud server 6 using a preset SAS for the first storage 93, refers to the instant task table in the first storage 93, and acquires task information (S110). Acquiring the task information corresponds to acquiring a group of instant task entities in the instant task table from the first storage 93.

Next, the cloud connector determines whether there is a new instant task entity addressed to itself to be processed based on the acquired task information (S120). The cloud connector determines whether there is an instant task entity addressed to itself in the instant task table, in which the progress status value is "request" and the device ID of the own device is described in the device ID property. The new instant task entity is registered in the instant task table with "request" described as the progress status, indicating that the task is in a request to execute state.

When the cloud connector determines that there is no new instant task entity addressed to itself (No in S120), it ends the instant task-related processing. In this case, the cloud connector executes the instant task-related processing again when the next polling timing arrives.

On the other hand, if it is determined that a new instant task entity addressed to itself exists (Yes in S120), the cloud connector changes the progress status value of the target entity in the first storage 93 from "Requested" to "In Progress" (S130). This change is made to notify the master 2 that the request has been accepted and the corresponding processing has started at the execution request destination.

The target entity here is a new instant task entity addressed to the self that was determined to exist in S120. Here, the processing from S130 onwards will be explained on the assumption that the target entity is one new instant task entity. However, the target entity may include multiple new instant task entities in some cases. When multiple new instant task entities are included, it may be understood that the processing for one new instant task entity from S130 onwards described below is executed for each of the multiple new instant task entities.

Following processing of S130, the cloud connector determines whether the target entity is an entity of a file transmission task based on the task information obtained from the first storage 93 (S150).

When it is determined that the target entity is an entity of a file transmission task (Yes in S150), the cloud connector downloads and acquires the corresponding data file stored in the second storage 94 of the cloud server 6 based on the storage destination URL of the data file described in the request parameters of the target entity (S160). The SAS for the second storage 94 is used for the download.

Then, the cloud connector saves the downloaded data file in the memory 82 of its own device (S160). Furthermore, the cloud connector changes the progress status value of the target entity in the first storage 93 from "In progress" to "Completed". The cloud connector also updates the target entity by writing the task processing results in JSON format to the response parameters of the target entity (S165). Then, the instant task related processing is terminated.

On the other hand, if it is determined that the target entity is not an entity for a file transmission task but an entity for a setting task (No in S150 and Yes in S170), the cloud connector downloads and acquires the setting file stored in the second storage 94 of the cloud server 6 based on the storage URL of the data file described in the request parameters of the target entity (S181).

Then, the cloud connector changes the setting values of the operating parameters of its own device based on the acquired configuration file (S185). When the setting change is complete, the cloud connector changes the progress status value of the target entity in the first storage 93 from "In progress" to "Completed," and further updates the target entity by writing the processing result in JSON format to the response parameter (S189).

The update in S189 is performed to notify the master 2 via the cloud server 6 that the task has been completed and the processing result. The cloud connector then ends the instant task-related processing.

If the target entity is neither a file transmission task nor a settings task (No in S170), the cloud connector executes processing according to the request parameters of the target entity (S190) and terminates the instant task-related processing.

A task execution request to the first type terminal device 4 is processed by the client 3 as follows. Figure 8 shows the operation of the client 3 with respect to a file transmission task. Figure 9 shows the operation of the client 3 with respect to a setting task.

When Master 2 creates a file transmission task or a setting task, it registers the corresponding instant task entity in the instant task table in the first storage 93 and uploads the data files required to execute the task to the second storage 94.

At this time, "Request" is written as the progress status in the instant task entity. The device ID of the first type terminal device 4 to which the task execution request is to be made is written in the device ID property of the instant task entity. There may be multiple device IDs written. In other words, the master 2 can write the device IDs of all or some of the first type terminal devices 4 managed by one client 3 in one instant task entity in accordance with user operations from the input unit 14, so as to specify all or some of the multiple first type terminal devices 4 managed by one client 3 as the execution request destinations.

An instant task entity for a setting task in which the device IDs of multiple first-type terminal devices 4 are described can be interpreted as an entity for a task that collectively sets multiple first-type terminal devices 4. The request parameters are described as JSON data that describes the contents of the task, including the storage URL of the data file required to execute the task, similar to the file transmission task and setting task for the second-type terminal device 5 described above.

To process the instant task entity registered by the above-mentioned operation by the master 2, the client 3 periodically executes the instant task relay process shown in FIG. 10, which includes a polling operation. The execution period of the instant task relay process corresponds to the polling period set as a cloud parameter by the master 2.

When the instant task relay process starts, the control unit 31 of the client 3 uses the SAS for the first storage 93 to refer to the instant task table in the first storage 93 and obtains task information, similar to the process of S110 (S210).

Then, the control unit 31 determines whether there is a new instant task entity addressed to itself to be processed based on the acquired task information (S220). The control unit 31 can determine whether there is an instant task entity in the instant task table addressed to itself, in which the progress status value is "Request" and the device ID property lists all or part of the device IDs of the first type terminal devices 4 managed by the control unit 31.

When the control unit 31 determines that there is no new instant task entity addressed to itself (No in S220), it ends the instant task relay process shown in FIG. 10 and waits until the next polling timing arrives. When the next polling timing arrives, the control unit 31 executes the instant task relay process again.

On the other hand, if it is determined that a new instant task entity addressed to itself exists (Yes in S220), the control unit 31 changes the progress status value of the target entity in the first storage 93 from "Requested" to "In Progress" (S230). As explained in relation to the processing of S130, the target entity here is the new instant task entity addressed to itself that was determined to exist in S220. Here again, the subsequent processing contents will be explained on the assumption that the target entity is one new instant task entity. However, the target entity may include multiple new instant task entities in some cases.

Following the processing at S230, the control unit 31 determines whether the target entity is an entity of a file transmission task based on the task information obtained from the first storage 93 (S250).

When it is determined that the target entity is an entity of a file transmission task (Yes in S250), the control unit 31 downloads and acquires the data file of the storage destination URL described in the request parameter of the target entity from the second storage 94 of the cloud server 6 (S261). When downloading, the SAS for the second storage 94 is used.

Furthermore, the control unit 31 transmits the acquired data file to the target terminal device together with an instruction to execute a task to save the data file via the local area network (S263). The target terminal device here corresponds to the instant task execution target described above, and is one or more first-type terminal devices 4 whose device IDs are described in the device ID properties of the target entity.

Each of the first type terminal devices 4 can have in memory 62 a computer program necessary for communication with the client 3, and the control unit 51 of the first type terminal device 4 can communicate with the client 3 in accordance with this computer program and execute processing based on instructions from the client 3.

When the control unit 31 has completed sending the data file to the target terminal device, it changes the value of the progress status of the target entity in the first storage 93 from "in progress" to "completed" (S265). The control unit 31 further updates the target entity by writing the processing result in the response parameter (S265).

When the target terminal device includes multiple first type terminal devices 4, the update of the target entity in S265 is executed when the transmission of the data file to all first type terminal devices 4 corresponding to the target terminal devices is completed. At this time, the control unit 31 updates the target entity so as to write the processing result for each first type terminal device 4 corresponding to the target terminal device in the response parameter.

For example, if the transfer of a data file to some of the group of first-type terminal devices 4 corresponding to the target terminal device fails, the control unit 31 can write the corresponding error information to the response parameters as the processing result. The failure of the data file transfer can occur due to a shutdown of the first-type terminal device 4, a communication abnormality, etc.

In such a case where the transfer of the data file fails, the control unit 31 can formally determine that the transmission of the data file to the corresponding first type terminal device 4 has been completed at the point in time when the control unit 31 gives up on the retry of transferring the data file.

When the control unit 31 determines that the target entity is not an entity of a file transmission task but an entity of a setting task (No in S250 and Yes in S270), it downloads and obtains the setting file stored in the second storage 94 of the cloud server 6 based on the storage destination URL described in the request parameters of the target entity (S281).

Then, before transmitting the configuration file to the target terminal device, the control unit 31 negotiates with the target terminal device regarding the transmission of the configuration file by communication through the local area network (S283).

When the target terminal device includes multiple first-type terminal devices 4, negotiation is performed individually with each of these multiple first-type terminal devices 4. The negotiation is an agreement regarding the method of transmitting the configuration file to the first-type terminal device 4. For example, the control unit 31 can negotiate with the first-type terminal device 4 to confirm the file format supported by the corresponding first-type terminal device 4 and to agree with the first-type terminal device 4 to transmit the configuration file in the file format supported by the first-type terminal device 4.

Then, the control unit 31 transmits the configuration file acquired from the cloud server 6 to the target terminal device via the local area network based on the prior agreement made through negotiation, together with an instruction to execute a task for setting operating parameters according to the configuration file (S285).

When the target terminal device includes multiple first-type terminal devices 4, the control unit 31 transmits a configuration file to each of the multiple first-type terminal devices 4. The control unit 31 can transmit a configuration file to each of the multiple first-type terminal devices 4 in a file format agreed upon in an individual negotiation.

After sending the configuration file, the control unit 31 determines whether the configuration in the target terminal device is complete by inquiring of the target terminal device (S287). If the target terminal device includes multiple first-type terminal devices 4, the control unit 31 can determine that the configuration in the target terminal device is complete when the configuration in all of the multiple first-type terminal devices 4 corresponding to the target terminal device is complete.

When the target terminal device includes multiple first-type terminal devices 4, the control unit 31 can determine whether the settings in the target terminal device have been completed by inquiring about the setting values of the operating parameters of each of the first-type terminal devices 4 and determining whether the setting values have been changed according to the setting file.

The control unit 31 waits until the setting on the target terminal device is completed, and when it determines that the setting is completed (Yes in S287), it changes the progress status value of the target entity in the first storage 93 from "In progress" to "Completed", and further updates the target entity by writing the processing result in the response parameter (S289).

When the target terminal device includes multiple first-type terminal devices 4, the update of the target entity in S289 is executed when the setting values indicated by the setting file are reflected in all first-type terminal devices 4 corresponding to the target terminal devices. At this time, the control unit 31 updates the target entity so as to write the processing results for each first-type terminal device 4 corresponding to the target terminal device in the response parameters.

However, if the control unit 31 fails to configure some of the group of first-type terminal devices 4 that correspond to the target terminal device, the control unit 31 can formally determine that the configuration has been completed on the corresponding first-type terminal device 4 at the point when the control unit 31 gives up on the configuration through retry. In addition, the control unit 31 can update the target entity so that error information is written as the processing result for the first-type terminal device 4 for which the configuration has failed. Thereafter, the control unit 31 ends the instant task relay processing.

In addition, if the target entity is neither a file transmission task nor a setting task entity, the control unit 31 executes processing according to the request parameters of the target entity (S290) and terminates the instant task relay processing.

Next, the processing operation of the master 2 related to instant tasks will be described with reference to Figures 11-16. The control unit 11 of the master 2 executes processing according to the main management program 15a, and functions related to instant tasks include a task registration unit 11A, an information acquisition unit 11B, and a display control unit 11C shown in Figure 11. An internal table 11D is created in the memory 22 to store data necessary for the display control unit 11C to display information via the display unit 13, and an update log of the instant task table in the first storage 93 of the cloud server 6 is recorded in the internal table 11D.

The task registration unit 11A executes the creation and registration process shown in FIG. 12 in accordance with an instant task execution request operation from the user via the input unit 14. The task registration unit 11A creates an instant task such as a file transmission task or a setting task in accordance with the operation (S410).

Creating a task corresponds to determining the content of the task, including the device ID of the destination of the execution request, and creating an instant task entity for registration in the instant task table.

The terminal devices 4, 5 to which the execution request is made are specified from a device list by the user operating the master 2. The control unit 11 can identify the terminal devices 4, 5 registered in the management system 1 by referring to the schedule task table in the first storage 93 in advance, create a device list that lists these terminal devices 4, 5, and display it on the display unit 13.

In the next step S420, the task registration unit 11A accesses the first storage 93 of the cloud server 6 using the SAS for the first storage 93, and newly registers the created instant task entity in the instant task table of the first storage 93.

In S420, if there is a data file required for executing the task, the task registration unit 11A accesses the second storage 94 of the cloud server 6 using the SAS for the second storage 94, and uploads the corresponding data file. The storage URL of the uploaded data file is written in the request parameters of the registered instant task entity before or after the upload.

In S420, the task registration unit 11A further records the registration of the instant task entity in the internal table 11D as an update log. For example, the instant task entity registered in the instant task table of the cloud server 6 is recorded in the internal table 11D as an update log together with the registration date and time. Thereafter, the task registration unit 11A ends the creation and registration process.

The information acquisition unit 11B periodically executes the acquisition and update process shown in FIG. 13A at a predetermined reference cycle. In the acquisition and update process, the information acquisition unit 11B acquires task information by referring to the instant task table in the first storage 93. As described above, the task information is a group of entities registered in the instant task table (S510).

Then, the information acquisition unit 11B updates the internal table 11D based on the acquired task information. The information acquisition unit 11B detects a group of instant task entities whose information has been updated in the instant task table based on the task information and the records in the internal table 11D, and records the update logs of the detected instant task entities in the internal table 11D (S520).

For example, the information acquisition unit 11B can determine the progress status of an instant task entity, and record the instant task entity when the progress status is updated from "requested" to "in progress" and when the progress status is updated from "in progress" to "completed" in the internal table 11D together with the update date and time as an update log. In this way, the information of the entities in the instant task table of the cloud server 6 can be stored and held in the internal table 11D of the master 2 as an update log.

The display control unit 11C repeatedly executes the display control process shown in FIG. 13B to update the task management screen displayed on the display unit 13. The task management screen is illustrated in FIGS. 14A and 14B.

By repeatedly executing the display control process, the display control unit 11C refers to the internal table 11D (S610) and repeatedly updates the display content on the task management screen (S620) based on the update log of the instant task entity recorded in the internal table 11D.

As shown in FIG. 14A, the task management screen includes a current task display area and a task log display area. The task log display area is an area that displays past tasks that have already been completed. The task log display area displays a table in which row data explaining the processing results of each task that was completed during a specified period in the past is arranged.

Each row of data in the table displayed in the task log display area has fields for "Task Type," "Status," "Start Time," "End Time," and "Target." The "Task Type" field displays a string indicating the type of task, such as "File Transmission" or "Settings."

In the "Status" field, the text string "Error" or "OK" is displayed as the result of the task's processing. "OK" indicates that the task was successfully executed, and "Error" indicates that the task failed to execute at least partially.

The "Start time" field displays the time when the task starts to be executed, and the "End time" field displays the time when the task ends to be executed. The "Target" field displays the number of terminal devices 4, 5 designated as the destination of the task execution request.

The current task display area displays a table in which, for each currently incomplete task, row data describing the corresponding task is arranged. Each row of data in the table displayed in the current task display area has fields for "Task Type," "Status," "Start Time," and "Target." The "Task Type," "Start Time," and "Target" fields display information similar to that of the row data in the task log display area. The "Status" field displays the execution status of the corresponding task.

To update the task management screen in this way, the display control unit 11C can execute the screen update process shown in FIG. 15 in S620 described above. When the screen update process starts, the display control unit 11C determines whether a new task has been created based on the update log of the internal table 11D (S710).

When it is determined that a new task has been created (Yes in S710), the display control unit 11C updates the task management screen so that the line data of the new task begins to be displayed in the current task display area (S711). As a result of the screen update, line data describing the "task type," "status," "start time," and "target" of the new task is additionally displayed in the current task display area.

If the instant task entity corresponding to the new task shows a progress status of "Requested", the "Status" field of the new task in the current task display area will show the string "Waiting" as the task's execution status. At this time, the task has not started execution, so the "Start time" field will be displayed blank.

The display control unit 11C further determines whether there is an instant task entity in the instant task table whose progress status has been changed from "requested" to "in progress" based on the update log of the internal table 11D (S720).

When it is determined that a corresponding instant task entity exists (Yes in S720), the display control unit 11C updates the task management screen so that for the task corresponding to the instant task entity whose progress status has been changed from "Requested" to "In Progress", the string "In Progress" is displayed as the task execution status in the "Status" field in the row data of the corresponding task in the current task display area (S721).

The display control unit 11C further determines whether there is an instant task entity in the instant task table whose progress status has been changed from "in progress" to "completed" based on the update log of the internal table 11D (S730).

When it is determined that a corresponding instant task entity exists (Yes in S730), the display control unit 11C deletes the row data of the task in the current task display area that corresponds to the instant task entity whose progress status has changed from "In Progress" to "Completed" (S731), and instead updates the task management screen so that the row data of this task is added to the task log display area (S735). Figure 14B illustrates an example of the task management screen after the row data in the current task display area shown in Figure 14A has been deleted and the corresponding row data has been added to the task log display area.

At S735, the display control unit 11C refers to the response parameters of the corresponding instant task entity recorded in the internal table 11D and determines whether the task has been successfully executed in all terminal devices 4, 5 to which the corresponding task execution request was made, i.e., whether there is no error information in the response parameters.

If the display control unit 11C determines that no error information exists, it updates the task management screen so that row data displaying "Task type," "Start time," and "Target" are the same as those deleted from the current task display area, "OK" is displayed as "Status," and the current time is displayed as "End time," and the task management screen is added to the task log display area. If the display control unit 11C determines that error information exists, it updates the task management screen so that row data displaying "Error" as "Status" is added to the task log display area.

In addition, when an instruction to display details of one of the row data displayed in the task log display area is input through the input unit 14 while the task management screen is being displayed (Yes in S740), the display control unit 11C causes the display unit 13 to display a details screen instead of the task management screen (S741).

As shown in FIG. 16, the details screen is a screen that describes the processing results for each execution request destination of the task corresponding to the row data for which a detailed display instruction has been issued. If the corresponding task is a task for which the execution request destination is a second type terminal device 5, the details screen displays the processing results of the task in the second type terminal device 5 that is the execution request destination. If the corresponding task is a task for which the execution request destination is multiple first type terminal devices 4 under the client 3, the details screen displays the processing results for each first type terminal device 4.

For each execution request destination, the details screen displays, for example, the node name, product model name, status, and other detailed information of the corresponding terminal device. In the details screen, the status of each terminal device displays the character string "Complete", indicating success, if the corresponding terminal device has successfully executed the task. If an error has occurred, a character string indicating the nature of the error, such as "Connection error" or "Password error", is displayed.

The display control unit 11C displays the details screen on the display unit 13 until an operation to end the display is performed via the input unit 14 (No in S745), and when the operation to end the display is performed (Yes in S745), it closes the details screen and displays a task management screen on the display unit 13 instead (S749). At this time, the display control unit 11C displays a task management screen on the display unit 13 that describes the current execution status of the task based on the latest update log of the internal table 11D that has been updated in the background by the information acquisition unit 11B operating in parallel.

The management system 1 of this embodiment described above has the following effects. According to the management system 1 of this embodiment, a task execution request is made via a wide area network using general-purpose cloud storage, rather than a dedicated server.

The execution request destination writes the progress status to the cloud storage. Therefore, the master 2 that originates the execution request can grasp the execution status of the task being executed remotely and can communicate the task execution status to the user operating the master 2 via a screen. Therefore, the management system 1 of this embodiment is highly effective in terms of remote control and monitoring of managed devices via general-purpose cloud storage.

In particular, in this embodiment, an instant task entity corresponding to integrated data including request parameters corresponding to the task request data and progress status properties corresponding to the task status data is written from the master 2 to the cloud storage. This instant task entity is updated by the client 3 or cloud connector corresponding to the execution request destination.

By registering and updating instant task entities, it is possible to efficiently use cloud storage to realize task execution requests and transmission of execution status.

Moreover, the client 3 and the cloud connector write the task execution status to the cloud storage multiple times before and after the requested task is completed by updating the progress status of the instant task entity. In this way, the client 3 and the cloud connector gradually notify the master 2, which is the source of the task execution request, of the task execution status each time the execution status changes.

Therefore, Master 2 can display the task execution status in stages so that the user can properly grasp not only the completion of the task but also the situation before its completion through the screen.

Furthermore, when the client 3 and cloud connector recognize a new instant task entity addressed to them and start the corresponding processing, they change the progress status to "In progress", and when the task is completed, they change the progress status to "Completed".

Based on the progress status described in the instant task entity, the master 2 updates the screen displayed on the display unit 13 so that the latest task execution status is displayed. In a file transmission task, the progress status is updated based on the completion of file transmission, and in a setting task, the progress status is updated based on the reflection of settings.

In this way, in this embodiment, the conditions for updating the progress status within an entity are switched depending on the type of task, so that for multiple types of tasks, the execution status of each type of task can be communicated to the user of Master 2 at an appropriate time depending on the type of task.

Needless to say, the present disclosure is not limited to the exemplary embodiment described above, and various aspects can be adopted. For example, in the embodiment described above, the progress of a task is expressed in three stages: "Requested," "In Progress," and "Completed," but, for example, the "In Progress" stage may be expressed in multiple further subdivided stages.

For example, a client 3 having multiple first type terminal devices 4 under its control may update the progress status of an instant task entity for a task whose execution request is directed to multiple first type terminal devices 4, to indicate the uncompleted portion of the task with an expression such as "in progress (xx% remaining)" when the task has been completed by a specified percentage of the multiple first type terminal devices 4. The master 2 may be configured to display the execution status of the task based on this progress status.

For a task whose execution request is directed to multiple first-type terminal devices 4, the client 3 may operate to update the progress status of the instant task entity each time each of the first-type terminal devices 4 completes the task.

In addition, the function of one component in the above embodiments may be distributed among multiple components. The functions of multiple components may be integrated into one component. Part of the configuration of the above embodiments may be omitted. At least part of the configuration of the above embodiments may be added to or substituted for the configuration of another of the above embodiments. Any aspect included in the technical idea identified from the wording of the claims is an embodiment of the present disclosure.

1...management system, 2...master, 3...client, 4, 5...terminal device, 6...cloud server, 11, 31, 51, 71, 91...control unit, 11A...task registration unit, 11B...information acquisition unit, 11C...display control unit, 11D...internal table, 12, 32, 52, 72, 92...communication unit, 13, 33, 53, 73...display unit, 14, 34, 54, 74...input unit, 15, 35...storage unit, 15a...main management program, 21, 41, 61, 81, 101...CPU, 22, 42, 62, 82, 102...memory, 35a...sub-management program, 55, 75...printing unit, 56, 76...reading unit, 82a...communication program, 93...first storage, 94...second storage.

Claims (12)

A first communication device configured to be able to access a cloud storage and configured to execute a first process related to the cloud storage, the first process including writing request data requesting execution of a task to the cloud storage;
A second communication device configured to be able to access the cloud storage and configured to execute a second process related to the cloud storage;
Equipped with
The second process includes:
repeatedly referencing the cloud storage, and when the requested data is written to the cloud storage, executing a task according to the requested data, or having a third communication device execute the task through communication with the third communication device;
writing status data describing an execution status of the task to the cloud storage;
Including,
The first process includes:
repeatedly referencing the cloud storage to determine an execution status of the task based on the status data in the cloud storage;
displaying a screen on a display device that explains the execution status of the task, and updating the screen based on the determined execution status of the task;
Further comprising:
the first communication device writes the request data to the cloud storage by writing integrated data to the cloud storage, the integrated data including the request data and the status data, the integrated data explaining that the task is in a state of being requested to be executed by the status data;
the second communication device updates the status data in the integrated data written in the cloud storage every time an execution status of the task changes, thereby writing new status data to the cloud storage;
The first communication device is a management system that determines the execution status of the task by referring to the status data in the integrated data. the third communication device is a plurality of communication devices managed by the second communication device,
2. The management system according to claim 1 , wherein the second communication device communicates with the plurality of communication devices and instructs the plurality of communication devices to execute a task according to the request data. A first communication device configured to be able to access a cloud storage and configured to execute a first process related to the cloud storage, the first process including writing request data requesting execution of a task to the cloud storage;
A second communication device configured to be able to access the cloud storage and configured to execute a second process related to the cloud storage;
Equipped with
The second process includes:
repeatedly referencing the cloud storage and, when the requested data is written to the cloud storage, causing a third communication device to execute the task through communication with the third communication device;
writing status data describing an execution status of the task to the cloud storage;
Including,
The first process includes:
repeatedly referencing the cloud storage to determine an execution status of the task based on the status data in the cloud storage;
displaying a screen on a display device that explains the execution status of the task, and updating the screen based on the determined execution status of the task;
Further comprising:
the third communication device is a plurality of communication devices managed by the second communication device,
The second communication device is
Communicating with the plurality of communication devices and instructing the plurality of communication devices to execute tasks according to the request data;
when instructing the plurality of communication devices to execute the task, writing data explaining that the task is being executed as the status data to the cloud storage;
The management system writes , when execution of the task is completed, data explaining that the task has been completed as the status data to the cloud storage. A first communication device configured to be able to access a cloud storage and configured to execute a first process related to the cloud storage, the first process including writing request data requesting execution of a task to the cloud storage;
A second communication device configured to be able to access the cloud storage and configured to execute a second process related to the cloud storage;
Equipped with
The second process includes:
repeatedly referencing the cloud storage and, when the requested data is written to the cloud storage, causing a third communication device to execute the task through communication with the third communication device;
writing status data describing an execution status of the task to the cloud storage;
Including,
The first process includes:
repeatedly referencing the cloud storage to determine an execution status of the task based on the status data in the cloud storage;
displaying a screen on a display device that explains the execution status of the task, and updating the screen based on the determined execution status of the task;
Further comprising:
the second communication device communicates with the third communication device to instruct the third communication device to execute a task according to the request data, and when instructing the third communication device to execute the task according to the request data, writes data explaining that the task is being executed as the status data to the cloud storage;
the third communication device executes a task for changing a setting value of the third communication device in accordance with the task execution instruction;
The second communication device determines that the setting value in the third communication device has been changed in accordance with an instruction to execute the task by inquiring about the setting value to the third communication device, and, if it is determined that the setting value has been changed in the third communication device, writes data explaining that the task has been completed as the status data to the cloud storage. A first communication device configured to be able to access a cloud storage and configured to execute a first process related to the cloud storage, the first process including writing request data requesting execution of a task to the cloud storage;
A second communication device configured to be able to access the cloud storage and configured to execute a second process related to the cloud storage;
Equipped with
The second process includes:
repeatedly referencing the cloud storage and, when the requested data is written to the cloud storage, causing a third communication device to execute the task through communication with the third communication device;
writing status data describing an execution status of the task to the cloud storage;
Including,
The first process includes:
repeatedly referencing the cloud storage to determine an execution status of the task based on the status data in the cloud storage;
displaying a screen on a display device that explains the execution status of the task, and updating the screen based on the determined execution status of the task;
Further comprising:
The request data includes storage location information of a data file required for executing the task,
The second communication device is
When the request data is written to the cloud storage, the data file is acquired from another cloud storage that stores a data file necessary for executing the task, based on the storage destination information included in the request data; and
communicating with the third communication device and instructing the third communication device to execute a task according to the request data, and further transferring the data file to the third communication device; when instructing the third communication device to execute the task according to the request data, writing data explaining that the task is being executed as the status data to the cloud storage;
A management system in which, when the second communication device has completed the instructions to the third communication device and the transfer of the data file, the second communication device writes data explaining that the task has been completed to the cloud storage as the status data. A first communication device configured to be able to access a cloud storage and configured to execute a first process related to the cloud storage, the first process including writing request data requesting execution of a task to the cloud storage;
A second communication device configured to be able to access the cloud storage and configured to execute a second process related to the cloud storage;
Equipped with
The second process includes:
repeatedly referencing the cloud storage and, when the requested data is written to the cloud storage, causing a third communication device to execute the task through communication with the third communication device;
writing status data describing an execution status of the task to the cloud storage;
Including,
The first process includes:
repeatedly referencing the cloud storage to determine an execution status of the task based on the status data in the cloud storage;
displaying a screen on a display device that explains the execution status of the task, and updating the screen based on the determined execution status of the task;
Further comprising:
The request data includes information for designating a target for which a task execution request is made,
The second communication device is a management system that, when the request data is written to the cloud storage and a communication device managed by the second communication device is specified as the target of the execution request in the request data, communicates as the third communication device with the communication device specified as the target of the execution request and instructs the third communication device to execute a task in accordance with the request data. 7. The management system according to claim 1 , wherein the third communication device is a communication device that belongs to the same local area network as the second communication device. A first communication device configured to be able to access a cloud storage and configured to execute a first process related to the cloud storage, the first process including writing request data requesting execution of a task to the cloud storage;
A second communication device configured to be able to access the cloud storage and configured to execute a second process related to the cloud storage;
Equipped with
The second process includes:
repeatedly referencing the cloud storage and, when the requested data is written to the cloud storage, executing a task according to the requested data;
writing status data describing an execution status of the task to the cloud storage;
Including,
The first process includes:
repeatedly referencing the cloud storage to determine an execution status of the task based on the status data in the cloud storage;
displaying a screen on a display device that explains the execution status of the task, and updating the screen based on the determined execution status of the task;
Further comprising:
The second communication device is
When the request data is written to the cloud storage, executing a task according to the request data;
When starting execution of the task, write data explaining that the task is being executed to the cloud storage as the status data;
The management system writes , when execution of the task is completed, data explaining that the task has been completed as the status data to the cloud storage. A first communication device configured to be able to access a cloud storage and configured to execute a first process related to the cloud storage, the first process including writing request data requesting execution of a task to the cloud storage;
A second communication device configured to be able to access the cloud storage and configured to execute a second process related to the cloud storage;
Equipped with
The second process includes:
repeatedly referencing the cloud storage, and when the requested data is written to the cloud storage, executing a task according to the requested data, or having a third communication device execute the task through communication with the third communication device;
writing status data describing an execution status of the task to the cloud storage;
Including,
The first process includes:
repeatedly referencing the cloud storage to determine an execution status of the task based on the status data in the cloud storage;
displaying a screen on a display device that explains the execution status of the task, and updating the screen based on the determined execution status of the task;
Further comprising:
The first communication device displays on the display device a screen explaining that the task is waiting to be executed before the task is executed, and when the task is being executed, updates the screen to explain that the task is being executed. A communication device, comprising:
A communication unit capable of accessing cloud storage;
A processing unit configured to perform processing related to the cloud storage;
Equipped with
The process related to the cloud storage includes:
repeatedly referring to the cloud storage via the communication unit, and when request data requesting execution of a task is written to the cloud storage, executing a task according to the request data;
Before and after the execution of the task is completed, status data explaining the execution status of the task is written to the cloud storage a plurality of times, thereby gradually notifying the execution request source of the task of the execution status of the task;
Including,
integrated data including the request data and the status data, the integrated data explaining that the task is in a state of being requested to be executed by the status data, is written to the cloud storage by a device other than the communication device;
The communication device, wherein the notifying includes updating the status data in the integrated data in the cloud storage each time the execution status of the task changes, and writing the new status data to the cloud storage so that it can be referenced by the other device . A communication device, comprising:
A communication unit that can access the cloud storage and is further configured to be able to communicate with one or more managed devices in a local area network;
A processing unit configured to perform processing related to the cloud storage;
Equipped with
The process related to the cloud storage includes:
repeatedly referencing the cloud storage via the communication unit, and when request data for requesting execution of a task is written to the cloud storage, communicating with the one or more managed devices in the local area network to cause the one or more managed devices to execute a task according to the request data;
writing status data explaining the execution status of the task to the cloud storage a plurality of times before and after the execution of the task is completed in the one or more managed devices, thereby gradually notifying the execution status of the task to a source of the execution request of the task;
Including,
integrated data including the request data and the status data, the integrated data explaining that the task is in a state of being requested to be executed by the status data, is written to the cloud storage by a device other than the communication device;
The communication device, wherein the notifying includes updating the status data in the integrated data in the cloud storage each time the execution status of the task changes, and writing the new status data to the cloud storage so that it can be referenced by the other device . A communication device, comprising:
A communication unit capable of accessing cloud storage;
A processing unit configured to perform processing related to the cloud storage;
Equipped with
The process related to the cloud storage includes:
writing request data requesting execution of a task to the cloud storage via the communication unit;
repeatedly referencing the cloud storage and determining an execution status of the task based on status data describing the execution status of the task that is written to the cloud storage from a device that executes a process according to the request data;
displaying a screen explaining the execution status of the task on a display device, and updating the screen based on the determined execution status of the task;
Including,
writing the request data to the cloud storage includes writing the request data to the cloud storage by writing integrated data to the cloud storage, the integrated data including the request data and the status data, the status data explaining that the task is in a state of being requested to be performed;
The status data in the integrated data in the cloud storage is updated by a device that executes a process according to the request data every time a status of the task execution changes, whereby new status data is written to the cloud storage;
A communication device , wherein determining the execution status of the task includes determining the execution status of the task by referencing the status data in the integrated data in the cloud storage .

Images