Management systems, servers, and programs

Abstract

The goal is to enable a device to efficiently execute multiple tasks, even when it is instructed to do so separately. [Solution] The server comprises: a first receiving unit that receives from the outside a first execution instruction instructing a first device to perform a predetermined task, a first task; a first transmitting unit that, upon receiving the first execution instruction, transmits a first execution request to the first device requesting the execution of the first task; a second receiving unit that, after receiving the first execution instruction, receives from the outside a second execution instruction instructing both the first device and a second device different from the first device to perform a predetermined task, a second task; and a second transmitting unit that, upon receiving the second execution instruction, transmits a second execution request to the first device and the second device requesting the execution of the second task.

Description

Technical Field

[0001] The present invention relates to a server that manages the processing order of a plurality of tasks executed by a device.

Background Art

[0002] Patent Document 1 describes a device management system including a management server, one or more management clients, and one or more devices. The management server can create a batch task in which one or more stages of tasks are defined for one or more devices. The management server executes a task execution instruction to the management client. The management client divides one or more tasks defining the batch task to be executed into subtasks for each device to be executed. The management client causes the divided subtasks to be executed simultaneously for each of the one or more devices.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] The batch task described in Patent Document 1 is a task that executes a plurality of tasks in a concatenated manner. On the other hand, it is also conceivable that an administrator executes tasks separately without concatenating a plurality of tasks. Patent Document 1 does not consider the case where the execution of a plurality of tasks is separately instructed.

[0005] An object of the present invention is to efficiently execute a plurality of tasks on a device even when the execution of the plurality of tasks is separately instructed.

Means for Solving the Problems

[0006] To achieve the above objective, the management system of the present invention is a management system comprising a plurality of devices that perform a predetermined task, the plurality of devices including a first device and a second device, and a server, wherein the server includes a first receiving unit that receives from the outside a first execution instruction instructing the first device to perform a first task which is the predetermined task, a first transmitting unit that, upon receiving the first execution instruction, transmits a first execution request to the first device requesting the execution of the first task, a second receiving unit that, after receiving the first execution instruction, receives from the outside a second execution instruction instructing both the first device and a second device different from the first device to perform a second task which is the predetermined task, and the second execution instruction The device comprises a second transmitting unit that transmits a second execution request to the first device and the second device requesting the execution of the second task, wherein the first device comprises a first task execution unit that executes the first task in response to the receipt of the first execution request, and the first device and the second device each comprises a second task execution unit that executes the second task in response to the receipt of the second execution request, and the second transmitting unit does not transmit the second execution request to the first device while the first device is executing the first task, transmits the second execution request to the second device that is not executing the first task, and transmits the second execution request to the first device after the first device has completed the execution of the first task.

[0007] Furthermore, in order to achieve the above objective, the program of the present invention is a program executed by a control unit of a server which is communicatively connected to a plurality of devices which perform a predetermined task, and which includes a first device and a second device, and the control unit is configured to perform a first execution instruction from an external source which instructs the first device to perform a first task which is the predetermined task, a first receiving process which, in response to the receipt of the first execution instruction, transmits a first execution request to the first device which requests the execution of the first task, and after the first execution instruction is received, the first device and the second device which is different from the first device The system performs a second receiving process which receives from an external source a second execution instruction which instructs both the first and second devices to perform a second task which is a predetermined task, and a second transmitting process which, upon receiving the second execution instruction, transmits a second execution request which requests the execution of the second task to both the first device and the second device, wherein the second transmitting process does not transmit the second execution request to the first device while the first device is performing the first task, transmits the second execution request to the second device which is not performing the first task, and transmits the second execution request to the first device after the first device has completed the execution of the first task.

[0008] Furthermore, in order to achieve the above objective, the server of the present invention is a plurality of devices that perform predetermined tasks, and is a server that is communicatively connected to the plurality of devices, including a first device and a second device, and includes: a first receiving unit that receives from the outside a first execution instruction that instructs the first device to perform a first task which is the predetermined task; a first transmitting unit that, upon receiving the first execution instruction, transmits a first execution request to the first device requesting the execution of the first task; and after the first execution instruction is received, transmits the first execution instruction to both the first device and the second device which is different from the first device. The device comprises a second receiving unit that receives from an external source a second execution instruction that instructs the execution of a second task which is a predetermined task, and a second transmitting unit that, upon receiving the second execution instruction, transmits a second execution request to the first device and the second device requesting the execution of the second task, wherein the second transmitting unit does not transmit the second execution request to the first device while the first device is executing the first task, transmits the second execution request to the second device which is not executing the first task, and transmits the second execution request to the first device after the first device has completed the execution of the first task. [Effects of the Invention]

[0009] According to the present invention, even when the device is instructed to perform multiple tasks separately, it can efficiently execute multiple tasks. [Brief explanation of the drawing]

[0010] [Figure 1] This is a block diagram showing the configuration of the management system. [Figure 2] This is a functional configuration diagram of the management system. [Figure 3] This diagram shows the contents stored in the administrator database. [Figure 4] This diagram shows the contents of the device list. [Figure 5]This is the first part of the diagram showing the changes in the contents of the execution list. [Figure 6] This is the latter half of the diagram showing the changes in the contents of the execution list. [Figure 7] This diagram shows the changes in the contents stored in the state management database. [Figure 8] This is a flowchart explaining the processes that the server will execute. [Figure 9] This is a sequence diagram illustrating the first stage of a procedure in which multiple administrators perform multiple tasks. [Figure 10] This sequence diagram illustrates the second stage of the procedure for multiple administrators to perform multiple tasks. [Figure 11] This sequence diagram illustrates the third stage of the procedure for multiple administrators to perform multiple tasks. [Figure 12] This sequence diagram illustrates the fourth stage of the procedure for multiple administrators to perform multiple tasks. [Modes for carrying out the invention]

[0011] The management system according to this embodiment will now be described. The management system 1 shown in Figure 1 comprises a server 100, an administrator terminal 200A, an administrator terminal 200B, a printer 300A, a printer 300B, a printer 400A, and a printer 400B. Printers 300A and 300B are connected to network 3. Printers 400A and 400B are connected to network 4. Networks 3 and 4 are, for example, Local Area Networks (LANs). Server 100, administrator terminals 200A and 200B, network 3, and network 4 are connected to the Internet NT. Server 100, administrator terminals 200A and 200B, printers 300A and 300B, printer 400A, and printer 400B communicate with each other via the Internet NT, network 3, and network 4. When referring to both printer 300A and printer 300B collectively, they should be abbreviated as "printer 300." When referring to both printer 300A, printer 300B, printer 400A, and printer 400B collectively, they should be abbreviated as "printer 300·400." The same applies to administrator terminals.

[0012] <Server Configuration> Server 100 is a physical or virtual server installed by the printer manufacturer. A virtual server is, for example, a cloud server using a cloud service such as Amazon Web Services (AWS). Server 100 is equipped with a CPU 110, non-volatile memory 120, volatile memory 130, and a communication interface 140. Hereafter, the interface will be abbreviated as "IF".

[0013] The CPU 110 is a arithmetic unit that performs data processing.

[0014] The non-volatile memory 120 is, for example, a ROM. The non-volatile memory 120 includes a control program 122, an administrator database 124, a device database 126, and a state management database 128. Hereinafter, the database is abbreviated as "DB".

[0015] The control program 122 is a program provided by the printer manufacturer and controls the server 100. When the server 100 is a virtual server, the printer manufacturer installs the server 100 by uploading the control program 122 onto the cloud. The control program 122 includes source code for executing the processes of the flowchart shown in FIG. 8. The control program 122 may be a single program or may be composed of a plurality of programs.

[0016] The administrator DB 124 stores a list of administrators of the printers managed by the management system 1. The device DB 126 stores a list of printers managed by the management system 1. The state management DB 128 stores the states of the printers managed by the management system 1. Details of the administrator DB 124, the device DB 126, and the state management DB 128 will be described later.

[0017] The volatile memory 130 is, for example, a RAM. The volatile memory 130 temporarily stores data generated by the processing of the CPU 110.

[0018] The communication IF 140 is connected to the Internet NT and communicates with each external device such as the administrator terminal 200, the printer 300, and the printer 400.

[0019] <Configuration of the administrator terminal> The administrator terminal 200 is used by the printer administrator. The administrator terminal 200 is, for example, a personal computer (PC). The administrator terminal 200 comprises a CPU 210, non-volatile memory 220, volatile memory 230, communication interface 240, display 250, and touch panel 260. The CPU 210 and volatile memory 230 have the same functions as the CPU 110 and volatile memory 130, respectively.

[0020] The non-volatile memory 220 includes an operating system 222 and a browser 224. Hereafter, the operating system will be abbreviated as "OS". OS 222 is a program that controls the administrator terminal 200, and is, for example, Windows (registered trademark). The browser 224 is software for viewing web pages.

[0021] The communication interface 240 is connected to the Internet NT and communicates with external devices such as server 100, printer 300, and printer 400.

[0022] The display 250 shows screens such as the management screen, which will be described later. The touch panel 260 receives touch input from the administrator and sends a signal corresponding to the touch input to the CPU 210. The touch panel 260 is, for example, an LCD panel.

[0023] <Functional Configuration of the Management System> Referring to Figure 2, the functional configuration of the management system 1 will be explained. The administrator terminal 200 has the function of requesting the front end of the server 100 to send screen data, such as the management screen described later. Furthermore, the administrator terminal 200 has the function of sending a task creation request to the front end requesting the creation of tasks to be executed by the printers 300 and 400. Tasks include, for example, updating the printer firmware, updating settings, and performing backups.

[0024] Server 100 comprises a front end, an administrator authentication unit, an administrator DB 124, a task control unit, a device DB 126, a status management DB 128, and a printer communication control unit. If Server 100 is a physical server, the front end, administrator authentication unit, task control unit, and printer communication control unit are realized by the CPU 110 executing a control program 122. If Server 100 is a virtual server, each component may be configured to cooperate as separate modules. In this case, each component may be realized by a separate program.

[0025] The front end comprises a terminal communication control unit and a UI control unit. The terminal communication control unit controls communication with the administrator terminal 200 and has the function of sending screen data and notifications regarding the execution results of tasks to the administrator terminal 200. The UI control unit controls the transmission of screen data in response to requests from the administrator terminal 200.

[0026] The administrator authentication unit works in conjunction with the administrator DB124 to authenticate the administrator information included in the authentication request received from the frontend. The administrator authentication unit then sends the authentication result to the frontend.

[0027] As shown in Figure 3, the administrator DB124 stores the administrator ID, password, and privileges in an associated manner. The administrator ID is a string that identifies the administrator. The password is a string that represents the key required for the administrator to log in to the administration screen. The password is a hashed value obtained by adding an arbitrary string called a salt to the plaintext password set by the administrator. In this embodiment, for convenience, the password will be described as a plaintext password.

[0028] Permissions are strings that indicate the functions that an administrator is permitted to perform. The string "View" indicates the administrator's ability to log in to the administration screen and view the execution status of tasks on printers 300 and 400. The string "Exe" indicates the ability to instruct printers 300 and 400 to execute tasks. In Figure 3, administrators with administrator ID "Admin1" and administrator ID "Admin2" are permitted to instruct tasks to be executed, but administrator with administrator ID "Admin3" is not permitted to instruct tasks to be executed.

[0029] Let's return to Figure 2 for explanation. The task control unit has the function of creating tasks in cooperation with device DB126. The task control unit has the function of managing the execution status of tasks in cooperation with the printer communication control unit and device DB126. The task control unit has the function of managing whether printers 300 and 400 are in a state to accept task execution requests in cooperation with the printer communication control unit and state management DB128. The task control unit sends the task execution results to the front end.

[0030] Device DB126 includes device list 126A and execution list 126B. Device list 126A, shown in Figure 4, stores the device ID, administrator ID, model name, and version in association with each other. The device ID is a string that identifies the printer, for example, the serial number. In this embodiment, the device ID that identifies printer 300A is "Device1", the device ID that identifies printer 300B is "Device2", and the device ID that identifies printer 400A is "Device3". The administrator ID is a string that identifies the administrator who manages the printer. Figure 3 shows that the administrator with administrator ID "Admin1" and the administrator with administrator ID "Admin2" jointly manage the printer with device ID "Device2", i.e., printer 300B. The model name is a string that indicates the model of the printer. The version is a string that indicates the version of the printer's firmware.

[0031] Figures 5 and 6 show the changes in the contents of the execution list 126B. The execution list 126B stores the task ID, administrator ID, device ID, execution task, and task status in association with each other. The task ID is a string that distinguishes tasks instructed by different task creation requests. If a single task creation request instructs tasks targeting multiple printers, i.e., multiple tasks, the same task ID is assigned to all tasks. The administrator ID is a string that identifies the administrator who sent the task creation request. The device ID is a string that identifies the printer to which the task is executed.

[0032] An execution task is a string that identifies the function of the task. For example, the string "SendFile" indicates a file transmission task in which server 100 sends a file containing configuration values ​​to the printer and instructs the printer to update the configuration values. Other execution tasks include the string "FirmUpdate," which indicates a firmware update task in which the printer is instructed to update its firmware, and the string "Backup," which indicates a backup task in which the printer is instructed to create backup data. Backup data is, for example, the data of print jobs stored in printers 300 and 400. If printers 300 and 400 have a scanning function, the backup data may also be scan data showing scanned images.

[0033] The task status is a string that identifies the execution status of a task on the printer. For example, the string "Working" indicates that the printer is executing the task identified by the execution task. The string "Waiting (LOCK)" indicates that the printer is executing a different task and is unable to execute the task identified by the execution task. The string "Completed" indicates that the printer has successfully executed and completed the task identified by the execution task. The string "Attention" indicates that the execution status of a task requires the administrator's attention. For example, if the firmware is already the latest version, even if instructed to execute a firmware update task, there is no need to execute the firmware update task, so "Attention" is stored in execution list 126B. The string "Error" (not shown) indicates that the printer completed the execution of the task identified by the execution task, but failed.

[0034] Figure 7 shows the changes in the contents stored in the state management DB 128. The state management DB 128 stores device IDs and device states in association with each other. The device ID is the same string as the device ID stored in device list 126A. The device state is a string that indicates whether the printer is in a state to accept task execution requests or not. Specifically, the string "UNLOCK" indicates that the printer is not executing a task and is in a state to accept task execution requests. The string "LOCK" indicates that the printer is executing a task and is in a state to not accept task execution requests.

[0035] Let's return to Figure 2 for explanation. The printer communication control unit has the function of controlling communication with printers 300 and 400, sending task execution requests to printers 300 and 400, and receiving result notifications from printers 300 and 400 indicating the task execution status.

[0036] Printers 300 and 400 execute tasks in response to receiving task execution requests. Printers 300 and 400 send result notifications to server 100.

[0037] <Processing performed by the server> Referring to Figure 8, the process executed by the CPU 110 of the server 100 will be explained. More specifically, the process shown in the flowchart of Figure 8 is executed by the task control unit. The process shown in the flowchart of Figure 8 is started when a task creation request is received from the administrator terminal 200. If task creation requests are received from multiple administrator terminals 200, the process shown in the flowchart of Figure 8 is executed in parallel. The task creation request includes an execution task, which is a string that identifies the function of the task; a device ID that identifies the printer on which the task will be executed; and an administrator ID that identifies the administrator who sent the task creation request.

[0038] Furthermore, at the time a task creation request is received, the server 100 and the administrator terminal 200 have established bidirectional communication that enables push notifications, which are notifications that the server 100 voluntarily sends to the administrator terminal 200 without receiving a request from the administrator terminal 200. The server 100 and the administrator terminal 200 have established bidirectional communication, for example, using the Websocket protocol. In a modified example, the server 100 and the administrator terminal 200 may have established a constant connection using the XMPP protocol as bidirectional communication.

[0039] In S15, the execution list 126B is generated. Specifically, the task control unit generates a task ID using a string that has not yet been used as a task ID at that time. The task control unit associates the task ID with the administrator ID included in the task creation request, the device ID, and the task to be executed, and stores this association at the end of the execution list 126B. In this embodiment, the task status is left blank when the task ID is generated.

[0040] In S20, it is determined whether or not a result notification indicating the task execution status has been received from printers 300 and 400. If it is determined that no result notification has been received (S20: NO), in S25, the target device that is the printer on which the task will be executed is selected. Specifically, from the execution list 126B, the device ID whose task status is blank or "Waiting (LOCK)" is selected.

[0041] In S30, it is determined whether the device status of the target device is "LOCK". Specifically, the device status associated with the device ID of the target device is read from the status management DB128, and it is determined whether it is "LOCK" or not.

[0042] If the device status of the target device is determined to be "LOCK" (S30:YES), in S33, the task status of the target device in execution list 126B is updated to "Waiting (LOCK)". Specifically, the task status "Waiting (LOCK)" is stored in the execution list 126B, associated with the device ID of the target device. After completing the processing in S33, CPU 110 proceeds to the processing in S50.

[0043] If the device status of the target device is determined to be "UNLOCK" rather than "LOCK" (S30:NO), then in S35, the device status of the target device in the status management DB128 is updated to "LOCK". Specifically, the device status "LOCK" is stored in the status management DB128, associated with the device ID of the target device.

[0044] In S40, the task status of the target device in execution list 126B is updated to "Working". Specifically, the task status "Working" is stored in the execution list 126B, associated with the device ID of the target device. In S45, a task execution request is sent to the target device to request the execution of the task. In S50, the task status of the target device is notified via bidirectional communication. If S50 is executed after S45, "Working" is notified as the task status. If S50 is executed after S33, "Waiting (LOCK)" is notified as the task status.

[0045] If it is determined that a result notification has been received (S20:YES), S55 determines whether or not the result notification was received from an executed device. An executed device is a device that has completed tasks. A completed task is a task that has been completed before S55 is executed. Specifically, in S55, if there is a task (completed task) in the execution list 126B that has a task status of "Completed" or "Error" associated with a device ID that identifies the printer that sent the result notification, it is determined that the result notification was received from an executed device. If it is determined that the result notification was not received from an executed device (S55:NO), the CPU 110 proceeds to processing S75.

[0046] If it is determined that the result notification was received from an executed device (S55:YES), S58 determines whether the administrator of the running task indicated by the result notification is different from the administrator of the completed task. Specifically, if the administrator ID of the running task stored in execution list 126B does not match the administrator ID of the completed task, it is determined that the administrators are different. If the administrator ID of the running task stored in execution list 126B does not match the administrator ID of the completed task, for example, a task creation request is sent separately by two administrators using different administrator terminals 200. If it is determined that the administrators are the same (S58:NO), the CPU 110 proceeds to processing S75.

[0047] If it is determined that the administrators are different (S58:YES), then in S60, it is determined whether the completed task and the running task are tasks related to the same function. For example, if "SendFile" is stored as a completed task in execution list 126B and also as a running task, then it is determined that the completed task and the running task are tasks related to the same function. If it is determined that the completed task and the running task are not tasks related to the same function (S60:NO), then CPU 110 proceeds to processing in S75.

[0048] If it is determined that a completed task and a running task are tasks relating to the same function (S60: YES), in S65 the task status of the completed task is updated to "Attention". Specifically, in the execution list 126B, the task status of completed tasks that have the task status "Completed" or "Error" stored in association with the device ID that identifies the printer that sent the result notification is updated to "Attention".

[0049] In S70, the administrator's terminal of the completed task is notified by email that the task status of the completed task has changed. In a modified example, if bidirectional communication is established with the administrator's terminal of the completed task, a push notification may be executed. In this embodiment, if it is determined that the administrators are different (S58: NO), the process in S70 is not executed. If two task creation requests are sent by the same administrator, the administrator is likely to instruct the execution of the task knowing that the settings will be overwritten. Therefore, it is possible to prevent unnecessary notifications from being sent to the administrator.

[0050] In S75, the task status of the running task is updated based on the content of the result notification. In S80, the device status associated with the device ID that identifies the printer that sent the result notification is updated to "UNLOCK". In S85, the task status of the running task is notified via bidirectional communication.

[0051] In S90, it is determined whether all printer tasks have been completed. Specifically, if the task status of all tasks with the same task ID generated in S15 is either "Completed," "Attention," or "Error," then it is determined that all printer tasks have been completed. If all printer tasks have not been completed (S90:NO), the process returns to S20.

[0052] If it is determined that all printer tasks have been completed (S90:YES), in S95, a task completion notification indicating that all printer tasks have been completed is sent to the administrator terminal 200, and the process shown in Figure 8 ends.

[0053] <Specific Cases> Referring to Figures 9-12, the processing flow when both an administrator using administrator terminal 200A and an administrator using administrator terminal 200B request the execution of a task for jointly managed printers 300 and 400 will be explained. Server 100 has not received a task creation request, and nothing is stored in the execution list 126B. Printers 300A, 300B, 400A, and 400B are not executing any tasks, and the status management DB 128 is in the state shown in Figure 7(0).

[0054] At T10, the administrator terminal 200A accepts the administrator ID "Admin1" and password "Pass1" from the administrator using the administrator terminal 200A. At T15, the administrator terminal 200A temporarily stores the administrator ID "Admin1" and password "Pass1" in the volatile memory 230. At T20, the administrator terminal 200A sends a login request to the server 100, including the administrator ID "Admin1" and password "Pass1". Furthermore, at T20, the administrator terminal 200A also sends a connection request to establish bidirectional communication with the server 100 according to the Websocket protocol.

[0055] In T25, server 100 performs authentication based on the administrator ID "Admin1" and password "Pass1" included in the login request. In the authentication process, if the administrator ID "Admin1", password "Pass1", and permission "View" are associated and stored in the administrator DB 124, authentication is deemed successful. If authentication is deemed successful, in T30, server 100 generates management screen data and sends it to administrator terminal 200A. Specifically, server 100 extracts printer information for device IDs "Device1" and "Device2" associated with administrator ID "Admin1" from device list 126A and generates management screen data showing a list of printers managed by the administrator with administrator ID "Admin1". Furthermore, in T30, server 100 establishes bidirectional communication with administrator terminal 200A according to the Websocket protocol.

[0056] The administrator terminal 200A displays the management screen on the display 250. The management screen (not shown in the diagram) displays a list of printers managed by the administrator with administrator ID "Admin1" and buttons for selecting a task to execute. In T35, the administrator terminal 200A accepts the selection of printer 300A and printer 300B as the printers to execute the task on from the administrator using the administrator terminal 200A. Furthermore, in T35, the administrator terminal 200A accepts the selection of a file transfer task as the task to be executed.

[0057] In T40, administrator terminal 200A sends a task creation request to server 100. The task creation request includes the task to be executed "SendFile", the device ID of printer 300A "Device1", the device ID of printer 300B "Device2", administrator ID "Admin1", and password "Pass1".

[0058] In T45, server 100 performs authentication based on the administrator ID "Admin1" and password "Pass1" included in the task creation request. In the authentication process, if the administrator ID "Admin1", password "Pass1", and authority "Exe" are associated and stored in the administrator DB 124, authentication is deemed successful. If authentication is deemed successful, in T50, server 100 generates execution list 126B (S15). Specifically, server 100 associates the new task ID "Task1", ​​the administrator ID "Admin1" included in the task creation request, the device ID "Device1", and the task to be executed "SendFile", and stores them in execution list 126B. Furthermore, server 100 associates the task ID "Task1", ​​the administrator ID "Admin1", the device ID "Device2", and the task to be executed "SendFile", and stores them in execution list 126B. The task status is left blank.

[0059] If the administrator ID included in the task creation request is "Admin3", the administrator DB124 does not store the administrator ID "Admin3" associated with the privilege "Exe", so the server 100 determines that authentication has failed. If authentication fails, the processes from T50 onwards are not executed, and the server 100 notifies the administrator terminal 200A that authentication has failed.

[0060] At T55, the server 100 selects printer 300A as the target device (S25) and updates the device status of printer 300A to "LOCK" (S35). At T60, the server 100 updates the task status of printer 300A to "Working" (S40) and sends a task execution request to printer 300A (S45). At T65, the server 100 pushes the task status of printer 300A, "Working," to the administrator terminal 200A. On the administrator terminal 200A, the display 250 shows that printer 300A is executing a file transfer task.

[0061] In T70, printer 300A starts executing a task. Specifically, printer 300A receives a file containing configuration values ​​and updates them. These configuration values ​​are, for example, the default print settings when printer 300A is instructed to print. The configuration values ​​may also be the password for logging into the web server function of printer 300A, which has an embedded web server. In other words, the configuration values ​​may also be settings related to the maintenance and management of printer 300A.

[0062] In step T75, server 100 selects printer 300B as the target device (S25) and updates the device status of printer 300B to "LOCK" (S35). In step T80, server 100 updates the task status of printer 300B to "Working" (S40) and sends a task execution request to printer 300B (S45). In step T85, server 100 pushes the task status of printer 300B to administrator terminal 200A. Administrator terminal 200A displays that printer 300B is executing a file transfer task.

[0063] In T90, printer 300B initiates the execution of a task. Specifically, printer 300B receives a file containing configuration values ​​and updates those values.

[0064] At the time T80 was executed, execution list 126B was in the state shown in Figure 5(1). State management DB 128 was in the state shown in Figure 7(1).

[0065] At T95, the administrator terminal 200B accepts the administrator ID "Admin2" and password "Pass2" from the administrator using the administrator terminal 200B. At T100, the administrator terminal 200B temporarily stores the administrator ID "Admin2" and password "Pass2" in the volatile memory 230. At T105, the administrator terminal 200B sends a login request to the server 100, including the administrator ID "Admin2" and password "Pass2". Furthermore, at T105, the administrator terminal 200B also sends a connection request to establish bidirectional communication with the server 100 according to the Websocket protocol.

[0066] At T110, server 100 performs authentication based on the administrator ID "Admin2" and password "Pass2" included in the login request. During the authentication process, it is determined that authentication was successful because the administrator ID "Admin2", password "Pass2", and permission "View" are associated and stored in the administrator DB 124. At T115, server 100 generates management screen data and sends it to administrator terminal 200B. Specifically, server 100 extracts printer information for device IDs "Device2" and "Device3" associated with administrator ID "Admin2" from device list 126A and generates management screen data showing a list of printers managed by the administrator with administrator ID "Admin2". Furthermore, at T115, server 100 establishes bidirectional communication with administrator terminal 200B according to the Websocket protocol.

[0067] The administrator terminal 200B displays the management screen on the display 250. The management screen, which is not shown in the diagram, displays a list of printers managed by the administrator with administrator ID "Admin2" and buttons for selecting a task to execute. At T120, the administrator terminal 200B accepts the selection of printer 300B and printer 400A as the printers to execute the task on from the administrator using the administrator terminal 200B. Furthermore, at T120, the administrator terminal 200B accepts the selection of a file transfer task as the task to execute. At T125, the administrator terminal 200B sends a task creation request to the server 100. The task creation request includes the task to execute "SendFile", the device ID of printer 300A "Device2", the device ID of printer 400A "Device3", the administrator ID "Admin2", and the password "Pass2".

[0068] In T130, server 100 performs authentication based on the administrator ID "Admin2" and password "Pass2" included in the task creation request. In the authentication process, since the administrator ID "Admin2", password "Pass2", and authority "Exe" are associated and stored in the administrator DB 124, it is determined that authentication was successful, and in T135, server 100 generates execution list 126B (S15). Specifically, server 100 associates the new task ID "Task2", the administrator ID "Admin2" included in the task creation request, the device ID "Device2", and the task to be executed "SendFile", and stores them in execution list 126B. Furthermore, server 100 associates the task ID "Task2", the administrator ID "Admin2", the device ID "Device3", and the task to be executed "SendFile", and stores them in execution list 126B. The task status is left blank.

[0069] In T140, server 100 selects printer 300B as the target device (S25). Since the device status of printer 300B is "LOCK" (S30: YES), in T140, server 100 updates the task status of printer 300B to "Waiting (LOCK)" (S33). In T145, server 100 pushes the task status of printer 300B, "Waiting (LOCK)", to administrator terminal 200B. On administrator terminal 200B, display 250 shows that printer 300B is currently executing a task by an administrator other than the administrator using administrator terminal 200B, and therefore cannot execute a task by the administrator using administrator terminal 200B.

[0070] At T150, the server 100 selects printer 400A as the target device (S25) and updates the device status of printer 400A to "LOCK" (S35). At T155, the server 100 updates the task status of printer 400A to "Working" (S40) and sends a task execution request to printer 400A (S45). At T160, the server 100 pushes the task status of printer 400A, "Working," to the administrator terminal 200B. On the administrator terminal 200B, the display 250 shows that printer 400A is executing a file transfer task.

[0071] In T165, printer 400A starts executing a task. Specifically, printer 400A receives a file containing configuration values ​​and updates those values.

[0072] At the time T155 was executed, execution list 126B was in the state shown in Figure 5(2). State management DB 128 was in the state shown in Figure 7(2).

[0073] In T170, printer 300A successfully executes and completes a file transfer task performed by the administrator using administrator terminal 200A. In T175, printer 300A sends a result notification "Completed" to server 100.

[0074] At T180, since the server 100 determines that printer 300A is not an executed device (S55: NO), it updates the task status of the file transfer task performed by the administrator using administrator terminal 200A to "Completed" (S75). At T185, the server 100 updates the device status of printer 300A to "UNLOCK" (S80). At T190, the server 100 pushes the task status of printer 300A to administrator terminal 200A, indicating that it has successfully completed the file transfer task. On administrator terminal 200A, the display 250 shows that printer 300A has successfully completed the file transfer task.

[0075] In T195, printer 300B successfully executes and completes a file transfer task performed by the administrator using administrator terminal 200A. In T200, printer 300B sends a result notification "Completed" to server 100.

[0076] At T205, Server 100 determines that Printer 300B is not an executed device (S55: NO) and updates the task status of the file transfer task performed by the administrator using Administrator Terminal 200A to "Completed" (S75). At T210, Server 100 updates the device status of Printer 300A to "UNLOCK" (S80). At T215, Server 100 pushes a notification to Administrator Terminal 200A that Printer 300B's task status is "Completed". At T220, Server 100 determines that all printer tasks have been completed because the task status of all tasks with task ID "Task1" is "Completed" (S90: YES), and sends a task completion notification to Administrator Terminal 200A via push notification (S95). On Administrator Terminal 200A, Display 250 displays that Printer 300B successfully executed the file transfer task and that all printer tasks have been completed.

[0077] At the time T210 is executed, execution list 126B is in the state shown in Figure 5(3). State management DB 128 is in the state shown in Figure 7(3).

[0078] At T225, the server 100 selects printer 300B again as the target device (S25) and updates the device status of printer 300B to "LOCK" (S35). At T230, the server 100 updates the task status of printer 300B to "Working" (S40) and sends a task execution request to printer 300B (S45). At T235, the server 100 pushes the task status of printer 300B to the administrator terminal 200B. On the administrator terminal 200B, the display 250 shows that printer 300B is executing a file transfer task.

[0079] In the T240, printer 300B initiates the execution of a task. Specifically, printer 300B receives a file containing configuration values ​​and updates those values.

[0080] At the time T230 is executed, execution list 126B is in the state shown in Figure 6(4). State management DB 128 is in the state shown in Figure 7(4).

[0081] In T245, printer 400A successfully executes and completes a file transfer task performed by the administrator using administrator terminal 200B. In T250, printer 400A sends a result notification "Completed" to server 100.

[0082] At T255, since printer 400A is not an executed device (S55: NO), server 100 updates the task status of the file transfer task performed by the administrator using administrator terminal 200B to "Completed" (S75). At T260, server 100 updates the device status of printer 400A to "UNLOCK" (S80). At T265, server 100 pushes the task status of printer 400A to administrator terminal 200B. On administrator terminal 200B, display 250 shows that printer 400A has successfully completed the file transfer task.

[0083] In T270, printer 300B successfully executes and completes the file transfer task performed by the administrator using administrator terminal 200B. Therefore, the settings updated by the administrator using administrator terminal 200A when T195 was completed have been updated again by the administrator using administrator terminal 200B. In T275, printer 300B sends a result notification "Completed" to server 100.

[0084] As shown in Figure 6(4), the execution list 126B stores the administrator ID "Admin1", device ID "Device2", execution task "SendFile", and task status "Completed" in association with each other. In other words, it stores a completed task performed by an administrator using administrator terminal 200A, which is different from administrator terminal 200B. Therefore, in T280, server 100 determines that printer 300B is an executed device (S55:YES), and that the administrator of the running task and the administrator of the completed task are different (S58:YES). Furthermore, both the running task and the completed task are file transmission tasks. Therefore, in T280, server 100 determines that the completed task and the running task are tasks related to the same function (S60:YES), and updates the task status of the completed task for printer 300B to "Attention" (S65).

[0085] In T285, server 100 notifies administrator terminal 200A via email (S70) of the task status "Attention" for completed tasks of printer 300B. After the administrator using administrator terminal 200A launches the email application, the administrator terminal 200A displays text on display 250 prompting the administrator to pay attention to the task execution status.

[0086] At T290, Server 100 updates the task status of the running task on Printer 300B to "Completed" (S75). At T295, it updates the device status of Printer 300B to "UNLOCK" (S80). At T300, Server 100 pushes a notification to Administrator Terminal 200B that the task status of the running task on Printer 300B is "Completed". At T305, Server 100 determines that all printer tasks have been completed because the task status of all tasks with task ID "Task2" is "Completed" (S90:YES), and sends a task completion notification to Administrator Terminal 200B via push notification (S95). On Administrator Terminal 200B, Display 250 displays that Printer 300B successfully executed the file transfer task and that all printer tasks have been completed.

[0087] <Effects of the Example> (1) According to this embodiment, the server 100 receives a task creation request from the administrator terminal 200A instructing the printer 300B to execute a file transmission task (T40). In response to receiving the task creation request from the administrator terminal 200A, the server 100 sends a task execution request to the printer 300B requesting the execution of the file transmission task (T80). After receiving the task creation request from the administrator terminal 200A, the server 100 receives a task creation request from the administrator terminal 200A instructing both the printer 300B and the printer 400A to execute a file transmission task (T125). In response to receiving the task creation request from the administrator terminal 200B, the server 100 sends task execution requests to both the printer 300B and the printer 400A requesting the execution of the file transmission task (T155, T230). While printer 300B is executing a file transfer task by an administrator using administrator terminal 200A (solid line portion of printer 300B in Figures 9-11), server 100 does not send a task execution request to printer 300B requesting the execution of a file transfer task by an administrator using administrator terminal 200B. Instead, it sends a task execution request to printer 400A, which is not executing a file transfer task by an administrator using administrator terminal 200A (T155). After printer 300B has completed the file transfer task by an administrator using administrator terminal 200A (after T195), server 100 sends a task execution request (T230). Therefore, even if multiple tasks are instructed to be executed separately, the device can efficiently execute multiple tasks.

[0088] If a device with limited processing power, such as a printer, is performing a task such as a firmware update, and a large number of other task execution requests occur simultaneously, the load on the device may exceed its processing capacity. In this embodiment, while the printer 300B is performing a file transfer task by an administrator using the administrator terminal 200A, no task execution requests are sent, thus reducing the load on the printer 300B.

[0089] (2) According to this embodiment, the status management DB 128 of the server 100 stores either the string "UNLOCK" indicating that the printer is in a state to accept task execution requests, or the string "LOCK" indicating that the printer is in a state to not accept task execution requests, associated with the device ID that identifies the printer. While the printer 300B is executing a file transmission task by an administrator using the administrator terminal 200A (solid line portion of printer 300B in Figures 9-11), the status management DB 128 stores the string "LOCK" associated with the device ID "Device2" that identifies the printer 300B (Figure 7(1)). While the printer 300B is not executing a file transmission task by an administrator using the administrator terminal 200A, the status management DB 128 stores the string "UNLOCK" associated with the device ID "Device2" (Figures 7(0), (3), (5)). If the string "LOCK" is stored in the status management DB128 associated with the device ID "Device2" (S30:YES), the server 100 does not send a task execution request to the printer 300B requesting the execution of a file transfer task by an administrator using the administrator terminal 200B. If the string "UNLOCK" is stored in the status management DB128 associated with the device ID "Device2" (S30:NO), the server 100 sends a task execution request to the printer 300B (T230). Therefore, the server 100 can appropriately determine whether the printers 300 and 400 are in a state to accept task execution requests.

[0090] (3) According to this embodiment, if the string "LOCK" is stored in the status management DB 128 in association with the device ID "Device2" (S30:YES), the server 100 pushes a task status "Waiting (LOCK)" indicating that the printer 300B is unable to execute the task (T145). If the string "UNLOCK" is stored in the status management DB 128 in association with the device ID "Device2" (S30:NO), the server 100 pushes a task status "Working" indicating that the printer is executing the task (T235). Therefore, the administrator using the administrator terminal 200B can understand why the task execution has not started on the printer 300B.

[0091] (4) According to this embodiment, the server 100 transmits the task execution status of the printers 300 and 400 to the administrator terminal 200 (S85). The task execution status includes "Completed," which indicates that the printer has successfully executed and completed the task identified by the execution task; "Attention," which indicates that the administrator needs to be alerted about the task execution status; and "Error," which indicates that the printer has failed to complete the task identified by the execution task. Therefore, an administrator using the administrator terminal 200 can confirm whether the task has been successfully executed or not. Even if there is a possibility that the task may not be successfully executed, it is possible to switch the content of the notification to the administrator by providing two types of notifications: "Attention" and "Error."

[0092] (5) According to this embodiment, when the printer 300B completes the execution of a file transmission task by an administrator using the administrator terminal 200A (T195), the server 100 pushes the task status of the printer 300B, "Completed", to the administrator terminal 200A (T215). Subsequently, when the printer 300B completes the execution of a file transmission task by an administrator using the administrator terminal 200B (T270), the server 100 notifies the administrator terminal 200A by email of the task status of the completed task by the administrator using the administrator terminal 200A, "Attention", for the printer 300B (T285).

[0093] The file transmission task is a task in which server 100 sends a file containing setting values ​​to the printer and instructs the printer to update the setting values. If an administrator using administrator terminal 200A has printer 300B update the setting values, and then another administrator using administrator terminal 200B has printer 300B update the setting values, the setting values ​​set by the administrator using administrator terminal 200A will be overwritten. However, if the management screen of administrator terminal 200A still displays that printer 300B has successfully completed the file transmission task, the administrator using administrator terminal 200A may misinterpret the task's execution status. In this embodiment, after the setting values ​​set by the administrator using administrator terminal 200A are overwritten, the task status "Attention" is notified to administrator terminal 200A, so that the administrator using administrator terminal 200A can recognize that attention is needed regarding the task's execution status.

[0094] (6) According to this embodiment, unlike administrators using administrator terminal 200A, when a task creation request is received by an administrator using administrator terminal 200B (T125), the server 100 notifies administrator terminal 200A by email of the task status "Attention" for the completed task of printer 300B (T285). If the administrator using administrator terminal 200B does not notify the administrator that the task status has been updated, the administrator using administrator terminal 200A is likely to misinterpret the actual task status. For example, even if the setting value has been rewritten by the administrator using administrator terminal 200B, the administrator using administrator terminal 200A is likely to misinterpret the setting value that they set as it remains unchanged. According to this embodiment, the risk of administrators misinterpreting the actual task status can be reduced.

[0095] (7) In this embodiment, the server 100 pushes the task status of the printer 300B, "Completed," to the administrator terminal 200A via bidirectional communication following Websocket (T215). Subsequently, the server 100 notifies the administrator terminal 200A by email (T285) of the task status of the completed task of the printer 300B, "Attention," which was performed by the administrator using the administrator terminal 200A. By performing notifications using different notification methods, the administrator using the administrator terminal 200A is more likely to notice that a notification has been received.

[0096] The bidirectional communication using WebSocket is disconnected when the administrator using administrator terminal 200A logs out of the management screen, and server 100 is unable to execute push notifications. According to this embodiment, even after logging out of the management screen, the administrator using administrator terminal 200A can recognize that attention is needed regarding the task execution status by checking their email.

[0097] (8) In this embodiment, the administrator DB124 stores the string "Exe" which indicates that the administrator is authorized to instruct the execution of a task, associated with the administrator ID that identifies the administrator. Therefore, the functions that the administrator is authorized to execute can be changed according to the administrator's job authority, such as when printers 300 and 400 are managed within the company.

[0098] <Variation> (1) The task creation request for T40 and the task creation request for T125 may be sent from the same administrator terminal 200A.

[0099] (2) The task creation request of T40 and the task creation request of T125 may be requests to instruct the execution of a printer firmware update task, or requests to instruct the execution of a backup task. In other words, the task creation request may contain the string "FirmUpdate" or the string "Backup" instead of the string "SendFile".

[0100] (3) The task creation request of T125 may be sent simultaneously with the server 100 sending task execution requests to printer 300A and printer 300B. In this case, the processes shown in the flowchart of Figure 8 will be executed in parallel.

[0101] (4) The task status "Attention" is not required. In this case, in S65, the task status of completed tasks is updated to "Error".

[0102] (5) The decision in S58 is not required. In other words, even if the administrator of the running task and the administrator of the completed task are the same, the process in S65 may be executed.

[0103] (6) Notifications from S70 may be push notifications via bidirectional communication following WebSocket. Notifications from S70 may be a combination of push notifications and email notifications.

[0104] (7) The contents of the execution list 126B may be deleted after a predetermined period of time has elapsed. For example, if a setting value that was set a year ago is updated, even if a notification is sent that the task status has been updated (S70), it is highly likely that this notification is unnecessary for the administrator. This modified version prevents unnecessary notifications from being sent to the administrator.

[0105] (8) It is not necessary for the server 100 and the administrator terminal 200 to establish bidirectional communication. In this case, the administrator terminal 200 receives notifications from the server 100 using a polling method. That is, the administrator terminal 200 periodically sends an HTTP request to the server 100 requesting the task status. The server 100 sends the task status to the administrator terminal 200 as an HTTP response.

[0106] <Correspondence> The firmware update task, file transfer task, and backup task are examples of "predetermined tasks." Printer 300B is an example of a "first device." Printer 400A is an example of a "second device." Server 100 is an example of a "server." CPU 110 is an example of a "control unit." Management system 1 is an example of a "management system." The task creation request in T40 is an example of a "first execution instruction," and the file transfer task resulting from the task creation request in T40 is an example of a "first task." T40 is an example of a "first reception process" executed by the "first receiving unit." The task execution request in T80 is an example of a "first execution request," and S45 is an example of a "first transmission process" executed by the "first transmitting unit." The task creation request in T125 is an example of a "second execution instruction," and the file transfer task resulting from the task creation request in T125 is an example of a "second task." T125 is an example of a "second receiving process" executed by the "second receiving unit". The task execution request in T155 and the task execution request in T230 are examples of "second execution requests", and S45 is an example of a "second transmission process" executed by the "second transmitting unit". T90 is an example of a process executed by the "first task execution unit". T165 and T240 are examples of processes executed by the "second task execution unit". Device ID is an example of "device identification information". The string "LOCK" is an example of "lock information". The string "UNLOCK" is an example of "unlock information". State management DB128 is an example of a "device state storage unit". Administrator terminal 200A is an example of a "first administrator terminal". Display 250 is an example of a "display unit". CPU 210 is an example of a "display control unit". The notifications sent by S50, S65, and S85 are examples of "status notifications," and S50 is an example of processing performed by the "first notification unit." A notification containing the task status "Waiting (LOCK)" is an example of a "waiting notification." A notification containing the task status "Working" is an example of an "execution notification." S65 and S85 are examples of processing performed by the "second notification unit." A notification containing the task status "Completed" is an example of a "first type notification."Notifications containing task status "Attention" or task status "Error" are examples of "Type 2 notifications". Notifications containing task status "Error" are examples of "failure notifications". Notifications containing task status "Attention" are examples of "caution notifications". T125 is an example of processing executed by the "first instruction unit". Administrator terminal 200B is an example of the "second administrator terminal". Push notifications via bidirectional communication following Websocket are an example of the "first notification method". Email is an example of the "second notification method". Administrator ID is an example of "administrator identification information". The string "Exe" is an example of "execution permission". Administrator DB124 is an example of "permission storage unit". [Explanation of symbols]

[0107] 1 Management System, 3 Network, 4 Network, 100 Server, 200A Administrator Terminal, 200B Administrator Terminal, 300A Printer, 300B Printer, 400A Printer, 400B Printer, NT Internet

Claims

1. A management system comprising a plurality of devices that perform a predetermined task, the plurality of devices including a first device and a second device, and a server, The aforementioned server, A first receiving unit receives from an external source a first execution instruction that instructs the first device to perform a first task, which is a predetermined task. A first transmission unit transmits a first execution request to the first device in response to the receipt of the first execution instruction, which requests the execution of the first task. After the first execution instruction is received, a second receiving unit receives from an external source a second execution instruction that instructs both the first device and the second device, which is different from the first device, to execute the second task, which is the predetermined task. A second transmission unit transmits a second execution request requesting the execution of the second task to the first device and the second device in response to the receipt of the second execution instruction. Equipped with, The first device is The system includes a first task execution unit that executes the first task in response to the receipt of the first execution request, The first device and the second device are, The system includes a second task execution unit that executes the second task in response to the receipt of the second execution request, The second transmitting unit is, While the first device is performing the first task, the second execution request is not sent to the first device, and the second execution request is sent to the second device that is not performing the first task. After the first device completes the execution of the first task, it sends the second execution request to the first device. Management system.

2. A management system according to claim 1, The aforementioned server further, The device state storage unit stores either lock information indicating that the device is in a state where it does not accept requests to execute the predetermined task, or unlock information indicating that the device is in a state where it accepts requests to execute the predetermined task, in association with device identification information that identifies the device. While the first device is performing the first task, the lock information is stored in the device state storage unit in association with the first device identification information, which is the device identification information that identifies the first device. While the first device is not performing the first task, the device state storage unit stores the unlocked information in association with the first device identification information. The second transmitting unit is, If the lock information is stored in the device state storage unit in association with the first device identification information, the second execution request is not sent to the first device. If the unlock information is stored in the device state storage unit in association with the first device identification information, the second execution request is sent to the first device. Management system.

3. A management system according to claim 1, Furthermore, it is equipped with a first administrator terminal, The first administrator terminal is, The device includes a display control unit that displays the content of a status notification on the display unit in response to the receipt of a status notification indicating the execution status of a task on the device. The aforementioned server further, A device state storage unit stores either lock information indicating that the device is in a state where it does not accept requests to execute the predetermined task, or unlock information indicating that the device is in a state where it accepts requests to execute the predetermined task, in association with device identification information that identifies the device. A first notification unit that transmits the status notification to the first administrator terminal, Equipped with, The first notification unit is, If the lock information is stored in the device state storage unit in association with the device identification information, a standby notification, which is a status notification indicating that the device cannot perform a task, is sent to the first administrator terminal. If the unlock information is stored in the device state storage unit in association with the device identification information, an execution notification, which is a status notification indicating that the device is performing a task, is sent to the first administrator terminal. Management system.

4. A management system according to claim 1, Furthermore, it is equipped with a first administrator terminal, The first administrator terminal is, The device includes a display control unit that displays the content of a status notification on the display unit in response to the receipt of a status notification indicating the execution status of a task on the device. The aforementioned server further, The system includes a second notification unit that transmits the status notification to the first administrator terminal. The status notification includes a first type of notification indicating that the device successfully performed the task, and a second type of notification indicating that the device may not have successfully performed the task. Management system.

5. A management system according to claim 4, The second type of notification includes a failure notification indicating that the device has failed a task, and a warning notification alerting the administrator. Management system.

6. A management system according to claim 4, The aforementioned first administrator terminal further, The system includes a first instruction unit that transmits the first execution instruction to the server, The second notification unit is, When the first device completes the execution of the first task, the first type of notification is sent to the first administrator terminal as a status notification indicating the execution status of the first task on the first device. After sending the first type of notification to the first administrator terminal, if the first device completes the execution of the second task, which is a task relating to the same function as the first task, the second type of notification is sent to the first administrator terminal as a status notification indicating the execution status of the first task on the first device. The display control unit, Upon receiving the first type of notification, the content of the first type of notification is displayed on the display unit. After the content of the first type of notification has been displayed, and after the second type of notification has been received, the content of the second type of notification is displayed on the display unit. Management system.

7. A management system according to claim 6, The second notification unit is, When the second execution instruction is received from a second administrator terminal different from the first administrator terminal, the second type of notification is sent to the first administrator terminal. Management system.

8. A management system according to claim 6, The second notification unit is, The notification of the first type is transmitted to the first administrator terminal using the first notification method. The second type of notification is transmitted to the first administrator terminal using a second notification method different from the first notification method. Management system.

9. A management system according to any one of claims 1 to 8, It includes an authorization storage unit that stores execution permissions indicating whether or not the administrator is permitted to instruct the execution of a task, in association with administrator identification information that identifies the administrator. Management system.

10. A program executed by a control unit of a server which is connected to communicate with a plurality of devices, including a first device and a second device, that perform a predetermined task, The control unit, A first receiving process receives from an external source a first execution instruction that instructs the first device to perform a predetermined task, which is a first task, A first transmission process that, upon receiving the first execution instruction, transmits a first execution request to the first device requesting the execution of the first task, After the first execution instruction is received, a second receiving process receives from an external source a second execution instruction that instructs both the first device and the second device, which is different from the first device, to execute the second task, which is the predetermined task. Upon receiving the second execution instruction, a second transmission process is performed to send a second execution request requesting the execution of the second task to the first device and the second device, Make it run, The second transmission process described above is: While the first device is performing the first task, the second execution request is not sent to the first device, and the second execution request is sent to the second device that is not performing the first task. After the first device completes the execution of the first task, it sends the second execution request to the first device. program.

11. A server that is communicatively connected to a plurality of devices, including a first device and a second device, which perform a predetermined task, A first receiving unit receives from an external source a first execution instruction that instructs the first device to perform a first task, which is a predetermined task. A first transmission unit transmits a first execution request to the first device in response to the receipt of the first execution instruction, which requests the execution of the first task. After the first execution instruction is received, a second receiving unit receives from an external source a second execution instruction that instructs both the first device and the second device, which is different from the first device, to execute the second task, which is the predetermined task. A second transmission unit transmits a second execution request requesting the execution of the second task to the first device and the second device in response to the receipt of the second execution instruction. Equipped with, The second transmitting unit is, While the first device is performing the first task, the second execution request is not sent to the first device, and the second execution request is sent to the second device that is not performing the first task. After the first device completes the execution of the first task, it sends the second execution request to the first device. server.

Images