Device management program, information processing apparatus, and device management method

Abstract

To provide a technology capable of efficiently managing tasks of multiple devices.SOLUTION: An information processing apparatus sequentially issues execution instructions for each of one or more tasks to a device corresponding to the respective tasks among multiple devices. The information processing apparatus acquires the execution status of the target tasks of the execution instructions in the multiple devices in response to the execution instructions. If there is a specific-state device among the multiple devices, the information processing apparatus excludes the specific-state device from at least one of the one or more tasks to which the specific-state device is associated. A specific-state device is a device that is unable to complete the task targeted by the execution instruction.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present disclosure relates to techniques for having multiple devices perform tasks. [Background technology]

[0002] Patent Document 1 discloses a technique in which an image processing device receives a firmware update instruction from a management server and performs a firmware update. In this technique, the image processing device obtains firmware from the management server by making an inquiry to the management server and performs the update. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2017-016393 Summary of the Invention [Problem to be solved by the invention]

[0004] When a management server is configured to manage tasks (eg, firmware updates) for multiple devices, it is desirable to manage multiple devices efficiently. One aspect of the present disclosure provides a technique that allows for efficient management of tasks for multiple devices. [Means for solving the problem]

[0005] According to one aspect of the present disclosure, there is provided a device management program executable by a computer of an information processing device. The information processing device is capable of communicating with a plurality of devices. The device management program causes the computer to execute a first execution instruction process, an acquisition process, and a device exclusion process.

[0006] The first execution instruction process is a process for a group of instructions including one or more tasks. Each of the one or more tasks is associated with at least one of the plurality of devices that is to execute the task as an execution target device. The first execution instruction process is for each of the one or more tasks, and issues an execution instruction for the task to the execution target device associated with the task in sequence in a predetermined task order.

[0007] The acquisition process acquires the execution status of the group of instructions in the plurality of devices in response to the first execution instruction process. The device exclusion process excludes a specific state device from the task group to be excluded if there is a specific state device among the plurality of devices based on the execution status acquired by the acquisition process. The specific state device is a device in a specific state that cannot successfully complete a group of instructions. The task group to be excluded is at least one task, among the one or more tasks, to which the specific state device is associated.

[0008] Such a device management program allows for efficient management of tasks for multiple devices, and for example, allows an administrator to easily grasp devices in a specific state.

[0009] Excluding a specific state device from a task group to be excluded may be canceling the state associated with the specific state device in the task group to be excluded. In other words, excluding a specific state device from a task group to be excluded may be removing the specific state device from the targets of execution instructions for the task group to be excluded in the first execution instruction process. The device exclusion process may exclude the specific state device from all tasks included in the task group to be excluded, or may exclude the specific state device from some of all tasks included in the task group to be excluded.

[0010] For each task, the corresponding execution target devices may be managed in a list (or table, etc.). The list may be displayed on the information processing device, and the administrator may be able to check (e.g., visually confirm) the list. Excluded specific state devices may be managed in a separate list (or separate table, etc.). The administrator may be able to check (e.g., visually confirm) the separate list.

[0011] The first execution instruction process may be performed repeatedly. Specifically, when a task instructed to be executed by the first execution instruction process is successfully completed on an execution target device, the task may be unassociated with the execution target device. The first execution instruction process may be performed repeatedly until the instruction group reaches a predetermined first state. The first state may be a state in which the association of the execution target device with all tasks in the instruction group is unassociated (i.e., excluded). [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 1 is a block diagram of a management system according to an embodiment. [Figure 2] FIG. 10 is an explanatory diagram of a main list in an initial state before the start of task management processing. [Figure 3] FIG. 10 is an explanatory diagram of the main list, the postponed device list, and the rejected device list in the first scene after the start of the task management process. [Figure 4] FIG. 10 is an explanatory diagram of the main list in a second scene after the start of the task management process, which is after the first scene. [Figure 5] This is a variation of the main list in the second scene. [Figure 6] 10 is a flowchart of a task management process. [Figure 7] 10 is a flowchart of an execution status reflection process. [Figure 8] 10 is a flowchart of a postponement cancellation process. [Figure 9] 10 is a flowchart of a rejection cancellation process. DETAILED DESCRIPTION OF THE INVENTION

[0013] Exemplary embodiments of the present disclosure will now be described. [1. Embodiment] (1-1) Overview of the management system 1 includes a management system 1 according to this embodiment, which includes a management apparatus 100 and a plurality of devices, including a first device 10, a second device 20, a third device 30, a fourth device 40, and a fifth device 50.

[0014] Each of the multiple devices may take any form. For example, each of the multiple devices may take the form of an electronic device equipped with a computer configured to perform various processes according to a program (e.g., firmware). Specifically, each of the multiple devices may take the form of a so-called peripheral device. More specifically, each of the multiple devices may take the form of, for example, an image forming device or an image reading device. The image forming device forms (i.e., prints) an image on a print medium. The image reading device reads an image of an original document and generates data of the read image. In this embodiment, for simplicity of explanation, the following explanation will be continued assuming that all of the multiple devices take the form of an image forming device.

[0015] The management device 100 can communicate with each of the multiple devices via the network 200. The network 200 may have any configuration. The network 200 may include a WAN and / or a LAN. The network 200 may include a wireless communication network. The management device 100 and the multiple devices may be connected to the network 200 by wire or wirelessly.

[0016] The management device 100 can manage multiple devices via a network 200. Management by the management device 100 includes causing each device to execute an arbitrary task. The management device 100 of this embodiment can cause multiple devices to execute one or more tasks. The tasks are provided in the form of, for example, a computer program or a command. The tasks of this embodiment include updating firmware 16 provided in each of the multiple devices.

[0017] (1-2) Configuration of management device The management device 100 includes a control unit 101, a display unit 102, an input unit 103, a storage unit 104, and a communication unit 105. These components of the management device 100 may be physically housed in a single housing, or may be distributed across multiple housings.

[0018] The display unit 102 visually displays various types of information. The display unit 102 includes, for example, a liquid crystal display or a similar display device. The input unit 103 accepts various input operations by a user of the management device 100 (hereinafter referred to as an administrator). The input unit 103 includes, for example, a keyboard, a mouse, or a similar input interface.

[0019] The control unit 101 includes a computer including a CPU 101a and a memory 101b. The CPU 101a executes processing according to a program loaded into the memory 101b. The memory 101b may include, for example, a semiconductor memory such as a ROM, a RAM, an NVRAM, or a flash memory.

[0020] The storage unit 104 has a configuration that is an example of a non-transitory computer-readable storage medium. The storage unit 104 is a component for storing programs executed by the CPU 101a and various data. The storage unit 104 may have a storage such as an HDD (Hard Disk Drive) or an SSD (Solid State Drive).

[0021] In this embodiment, a device management program 104b is stored in the storage unit 104. An operating system (not shown) is also stored in the storage unit 104. The device management program 104b and the operating system are installed in the management apparatus 100.

[0022] Management of multiple devices by the management apparatus 100 is basically realized by the control unit 101 executing the device management program 104b. Task management processing (FIG. 6), execution status reflection processing (FIG. 7), postponement cancellation processing (FIG. 8), and refusal cancellation processing (FIG. 9), which will be described later, are parts of the device management program 104b.

[0023] The memory unit 104 may store a set of instructions 104a. The set of instructions 104a includes one or more tasks to be executed by multiple devices. The set of instructions 104a may be stored in the memory unit 104, for example, by an administrator performing a predetermined input operation via the input unit 103. In other words, the administrator can arbitrarily set desired tasks to be executed by multiple devices as the set of instructions 104a in the management device 100 (i.e., store the set of instructions in the memory unit 104).

[0024] In this embodiment, as an example, it is assumed that three tasks, namely, task A, task B, and task C, are set as the instruction set 104a. Tasks A to C are all tasks (i.e., programs) for updating firmware 16 of multiple devices.

[0025] The storage unit 104 or the memory 101b may store a main list (see FIG. 2), a deferred device list (FIG. 3), and a rejected device list (FIG. 3), which will be described later. The main list is prepared by an administrator. The deferred device list and rejected device list may be generated by processing of the device management program 104b. The administrator can visually check the contents of the main list, deferred device list, and rejected device list, for example, via the display unit 102.

[0026] The communication unit 105 is a communication interface for accessing the network 200. The management device 100 (specifically, the control unit 101) can connect to the network 200 via the communication unit 105, and can thereby communicate with a plurality of devices.

[0027] The administrator may access the management device 100 via an information processing device that is separate from the management device 100 and that can communicate with the management device 100. That is, the administrator may set the set of instructions 104a together with the main list in the information processing device. The information processing device may be able to transmit the set of instructions 104a and the main list to the management device 100. The management device 100 may be able to store the transmitted set of instructions 104a and main list in the storage unit 104. The administrator may be able to instruct the management device 100 to execute the device management program 104b from the information processing device. The administrator may be able to monitor the status of the main list, deferred device list, and rejected device list in the management device 100 using the information processing device.

[0028] (1-3) Device configuration As described above, the first device 10 is an image forming apparatus and has at least a printing function. As shown in Fig. 1, the first device 10 includes a control unit 11, a display unit 12, an input unit 13, a communication unit 14, and a printing unit 15.

[0029] The display unit 12 visually displays various types of information. The display unit 102 includes, for example, a liquid crystal display or a similar display device. The input unit 13 accepts various input operations by the user of the first device 10. The input unit 13 may include, for example, an input interface such as a numeric keypad, various buttons, and switches.

[0030] The control unit 11 includes a CPU 11a and a memory 11b. The memory 11b may include semiconductor memory such as ROM, RAM, NVRAM, or flash memory. Firmware 16 for implementing various functions of the first device 10, data, and the like are stored in the nonvolatile memory such as ROM or flash memory in the memory 11b. The CPU 11a performs overall control of the first device 10 by executing processes in accordance with the firmware 16.

[0031] The communication unit 14 is a communication interface for accessing the network 200. The first device 10 (specifically, the control unit 11) can connect to the network 200 via the communication unit 14, and can thereby communicate with the management apparatus 100.

[0032] The printing unit 15 has, for example, an inkjet or electrophotographic printing mechanism, and prints an image on a print medium. The other second to fifth devices 20 to 50 basically have the same hardware configuration as the first device 10.

[0033] (1-4) Main list The main list illustrated in FIG. 2 can be set by an administrator, as described above. The main list is set to cause each task in the set of instructions 104a to be executed by an execution target device. The execution target device is a device that should execute the corresponding task. Instructions to each device to execute the set of instructions 104a (i.e., instructions to execute tasks A to C) are given in accordance with the main list. Each device executes the instructed task in response to receiving an execution instruction for each task.

[0034] The instruction to execute a task may be given in any manner. The instruction to execute a task may include, for example, sending a task execution command. The task execution command may include a program required to execute the task. The task execution command may include only a portion of the program required to execute the task. Specifically, the task execution command may include an instruction to execute the task and other information, but may not include the actual program required to execute the task (e.g., an exe file for firmware update). In this case, in response to receiving the instruction to execute the task, the device may download and execute the necessary program separately from the management device 100 or another information processing device.

[0035] 2, the main list has a specified device list for each task included in the instruction set 104a. The specified device list is associated with an execution target device. The specified device list is associated with an execution target device along with device information related to the execution target device. The device information includes, for example, an ID and an IP address.

[0036] In FIG. 2, "Device 001" indicates the first device 10, "Device 002" indicates the second device 20, "Device 003" indicates the third device 30, "Device 004" indicates the fourth device 40, and "Device 005" indicates the fifth device 50.

[0037] In each specified device list, an instruction order is defined for each execution target device. The instruction order is the order in which execution instructions are given within the specified device list. Task execution instructions are given to the execution target devices sequentially according to the instruction order.

[0038] More specifically, the main list in this embodiment has a task A defining device list, a task B defining device list, and a task B defining device list. The task A defining device list is associated with execution target devices that are to execute task A. The execution target devices for task A include, for example, first to fifth devices 10 to 50. The task B defining device list is associated with execution target devices that are to execute task B. The execution target devices for task B include, for example, first, second, and fourth devices 10, 20, and 40. The task C defining device list is associated with execution target devices that are to execute task C. The execution target devices for task C include, for example, second and fifth devices 20 and 50.

[0039] In the task A defined device list, the execution target devices are listed in ascending order (i.e., from the earliest to the latest) according to the order of instructions. That is, the first device 10 is first in the order of instructions, and the fifth device 50 is fifth in the order of instructions. The same is true for the task B defined device list and the task C defined device list, and also for the additional device list (see FIG. 4) described later. The order of instructions may be determined in any way. The order of instructions may also be determined randomly.

[0040] In this embodiment, when simply referring to a "default device list," it refers to the task A default device list, the task B default device list, and / or the task C default device list. When simply referring to an "additional device list," it refers to the task A default device list, the task B default device list, and / or the task C default device list shown in Fig. 4. When simply referring to a "device list," it refers to at least one of all the default device lists and / or additional device lists included in the main list.

[0041] A task order is determined in the main list. The task order is the order in which task execution instructions are given to the execution target devices. In this embodiment, the task order is as follows: task A is first, task B is second, and task C is third. Task execution instructions are given sequentially according to this task order.

[0042] That is, first, an instruction to execute task A is given. Specifically, according to the task A definition device list, instructions to execute task A are given to the execution target devices of task A in the order of instructions. Next, an instruction to execute task B is given. Specifically, according to the task B definition device list, instructions to execute task B are given to the execution target devices of task B in the order of instructions. Next, an instruction to execute task C is given. Specifically, according to the task C definition device list, instructions to execute task C are given to the execution target devices of task C in the order of instructions. Such a series of execution instructions for tasks A to C according to the main list is referred to as a first execution instruction process (FIG. 6; S120). This first execution instruction process can be executed repeatedly, as described below. Note that the task order may be determined in any way. The task order may be determined randomly. The task order and the above-mentioned instruction order can be set arbitrarily by the administrator.

[0043] When a device receives an instruction to execute a task, the device executes the task automatically or in response to a user operation. However, in this embodiment, the device can postpone or reject the execution of the task in response to the execution instruction, for example, in response to a user operation.

[0044] For example, in response to receiving an instruction to execute a task from the management apparatus 100, the device may issue a notification indicating that the instruction has been received. The notification may be issued in any manner. For example, the notification may include displaying a predetermined message on the display unit 12.

[0045] The task may then be executed in response to the notification, either when the user does nothing or when the user performs a predetermined first input operation indicating an intention to accept the execution instruction. On the other hand, the user may be able to instruct in response to the notification to postpone or reject the execution of the task.

[0046] Regarding postponement, for example, the user can instruct postponement of task execution by performing a predetermined second input operation via the input unit 13. When postponement of task execution is instructed, the device sets the status of the device to a "postponed state" for the task. Alternatively (or in addition), the device may notify the management apparatus 100 that the device has been set to the "postponed state" (i.e., that the user has indicated an intention to postpone) together with attribute information. The attribute information includes information indicating the task instructed to be postponed and postponement information indicating the postponement period.

[0047] The postponement information may include any information. For example, the postponement information may include information that directly or indirectly indicates the end of the postponement period, i.e., the execution timing when the task should be executed. The execution timing may be, for example, the date and / or time when the postponement period ends. In the following description, a "postponed device" refers to a device that is set to a "postponed state," i.e., a device for which a task postponement has been instructed.

[0048] When the deferral period has elapsed, the device clears the "deferred state" of the task. After the deferral period has elapsed, the deferred device may execute the instructed task according to the execution instruction it previously received. Alternatively, even after the deferral period has elapsed, the device may suspend execution of the task until it receives another execution instruction.

[0049] Regarding refusal, for example, the user can instruct refusal of task execution by performing a predetermined third input operation via the input unit 13. When refusal of task execution is instructed, the device sets the status of the device to a "rejected state" for the task. Alternatively (or in addition), the device may notify the management apparatus 100 that it has been set to a "rejected state" (i.e., that the user has expressed an intention to reject) together with information indicating the task.

[0050] The user of the device may instruct postponement or rejection for each task individually, or may instruct postponement or rejection for all tasks associated with the device in the instruction set 104a.

[0051] After the first execution instruction process, the management apparatus 100 acquires the execution status of each task in the main list on the execution target device. The execution status includes, for example, completed, incomplete, postponed, rejected, and not executable.

[0052] "Completed" in the execution status means that the instructed task has been completed. "Incomplete" in the execution status means that the device is normal and the execution instruction has been received normally, but the instructed task has not yet been completed. "Postponed" in the execution status means that the device is set to a "postponed state." "Rejected" in the execution status means that the device is set to a "rejected state." "Cannot be executed" in the execution status means that the task cannot be executed and / or the execution instruction cannot be received due to factors such as a device abnormality, a communication abnormality, no communication connection, or the device not being powered on.

[0053] The management apparatus 100 excludes from the corresponding device list any execution target device whose execution status is "completed." In addition, in this embodiment, as will be described later, execution target devices whose execution status is "postponed" (i.e., postponed devices) and execution target devices whose execution status is "rejected" (i.e., rejected devices) are also excluded from the corresponding device list.

[0054] However, deferred devices are added separately to a deferred device list (see FIG. 3), and rejected devices are added separately to a rejected device list (see FIG. 3). The deferred device list and rejected device list are separate from the main list.

[0055] In this embodiment, the first execution instruction process is repeated until all execution target devices are removed from the main list. The first execution instruction process may be repeated at regular time intervals. The first execution instruction process may be executed again, for example, when a predetermined re-execution requirement is satisfied after the previous execution.

[0056] Even if all target devices are removed from the main list, there may still be deferred devices in the deferred device list and rejected devices in the rejected device list.

[0057] The process of the management apparatus 100 when a postponement or rejection is instructed by the execution target device will be specifically described with reference to FIG. 3 illustrates, as an example, a case in which the second device 20 is instructed to postpone at least task A, and the fourth device 40 is instructed to reject at least task A. That is, this illustrates a case in which the second device 20 is a postponement device and the fourth device 40 is a rejection device.

[0058] In this case, the second device 20 and the fourth device 40 are excluded from the main list. Specifically, with regard to the second device 20, the second device 20 is excluded from all device lists in the main list to which the second device 20 is associated (the task A defined device list, the task B defined device list, and the task C defined device list in FIG. 3).

[0059] The excluded second device 20 is then added to a separate postponed device list. Specifically, device information, unexecuted task information, and postponement information of the second device 20 are registered. The unexecuted task information indicates which task in the main list has been excluded from the specified device list. In other words, the unexecuted task information indicates which task in the main list has been set to be executed, or in other words, which task among the tasks to be executed has not yet been executed.

[0060] Regarding the fourth device 40, the fourth device 40 is excluded from all device lists (the task A defining device list and the task B defining device list in FIG. 3) in the main list to which the fourth device 40 is associated. Then, the excluded fourth device 40 is added separately to a rejected device list. Specifically, device information and unexecuted task information of the fourth device 40 are registered.

[0061] In this embodiment, when a postponement instruction is issued for at least one of the tasks instructed to be executed in a certain execution target device, the postponed device is deleted from all device lists associated with the execution target device (i.e., the postponed device) in the main list. The same applies when a refusal instruction is issued.

[0062] However, it is not necessary to remove all postponed devices from the main list. For example, if postponement can be instructed for each task, the execution target device may be removed only from the task instructed to be postponed. In this case, only the task instructed to be postponed may be registered as an unexecuted task for the execution target device in the postponed device list.

[0063] Also, for example, the deferred device may be removed only from the device list of the earliest task among the multiple tasks for which the deferred device remains in the main list. More specifically, if the execution of the second (or subsequent) task among the multiple tasks for which the deferred device remains does not require the completion of the first task, the deferred device may remain in the device list of the second (or subsequent) task. These are merely examples, and it may be determined as appropriate from which device list among the multiple device lists in which the deferred device exists to remove the deferred device.

[0064] The same applies to the case where a rejected device is removed from the main list. That is, the device list from which the deferred device is removed from among the multiple device lists in which the rejected device exists may be determined appropriately in the same manner as in the above example regarding the deferred device.

[0065] In this embodiment, when a postponement is instructed, the device may be maintained in the main list without being added to the postponed device list. Specifically, if the remaining time until the specified execution timing (i.e., the end of the postponement period) is equal to or less than the time threshold, the device is maintained in the main list without being added to the postponed device list. In this case, however, the instruction order of the postponed device in question is lowered from its current position in the main list. On the other hand, if the remaining time is greater than the time threshold, the device is added to the postponed device list and removed from the main list in the manner described above.

[0066] In the deferred device list, a deferred device whose execution time has arrived is restored to the main list. At this time, if the original default device list before the exclusion still exists, the device is restored there. Note that "still exists" means that the device to be executed still remains.

[0067] 3, when the execution timing of the second device 20 in the postponed device list arrives, if the prescribed device lists for each of tasks A to C remain in the main list, the second device 20 is restored to those prescribed device lists. At this time, the second device 20 may be restored to any position (in any instruction order) in the prescribed device list.

[0068] On the other hand, if there is a task for which the original default device list no longer exists, at least a new additional device list for that task is added, and the deferred devices are registered in that additional device list together with their device information.

[0069] If the default device list does not exist for even one of the unexecuted tasks, an additional device list may be added for all the unexecuted tasks. This is called a first pattern.

[0070] On the other hand, a situation may occur in which the default device list remains for some of the unexecuted tasks, while the default device list does not remain for the other tasks. In this case, the deferred devices may be restored to the default device list for the tasks that have a default device list. Then, an additional device list may be added only to the tasks that do not have a default device list. This is called the second pattern.

[0071] 4 shows an example of the first pattern. FIG. 4 shows an example in which the execution timing for the second device 20 arrives in a state in which the task A prescribed device list does not exist. In this example, when the execution timing arrives, prescribed device lists exist for tasks B and C, but the prescribed device list does not exist for task A. Therefore, additional device lists are newly added for all unexecuted tasks A to C of the second device 20, and the second device 20 is registered therein (i.e., revived). Specifically, a task A additional device list for executing task A, a task B additional device list for executing task B, and a task C additional device list for executing task C are newly added. Then, the second device 20 is registered in each of them.

[0072] 5 shows an example of the second pattern. FIG. 5 shows an example in which the execution timing of the second device 20 arrives when the task A prescribed device list does not exist. In this example, when the execution timing arrives, the prescribed device list for task A does not exist, but the prescribed device lists for tasks B and C exist. For tasks B and C, the second device 20 is restored to the existing prescribed device lists. On the other hand, for task A, a new task A additional device list is added, and the second device 20 is registered therein (i.e., restored).

[0073] Regarding a rejected device, in response to the rejected device being registered in the rejected device list, the management apparatus 100 notifies the administrator that the rejected device has been registered. This notification may be made in any manner. For example, this notification may be made by displaying a message indicating that the device has been rejected on the display unit 12.

[0074] The administrator can recognize the existence of a rejected device through this notification or by the administrator's own confirmation operation, etc. The administrator can restore the rejected device to the main list by performing a restore operation via the input unit 103.

[0075] 3, when the execution timing of the fourth device 40 in the rejected device list arrives, if the default device lists for tasks A and B remain in the main list, the administrator can restore the fourth device 40 to those default device lists by performing a restore operation. At this time, the fourth device 40 can be restored to any position in the default device list.

[0076] On the other hand, when restoring a rejected device to the main list, either the first or second pattern described above may be applied. 4 shows an example in which a rejected device is restored according to the first pattern. In FIG. 4, the default device list remains for task B, but the default device list does not remain for task A. Therefore, for all unexecuted tasks A and B of the fourth device 40, new additional device lists are added, and the fourth device 40 is registered (i.e., restored) there.

[0077] If an added device list already exists, the fourth device 40 is added to it. However, a separate added device list may be newly added for the fourth device 40. The same applies when restoring a delayed device to the added device list.

[0078] 5 shows an example in which a denied device is restored according to the second pattern. In FIG. 5, since the specified device list for task A no longer exists, the fourth device 40 is restored to the task A additional device list. On the other hand, since the task B specified device list remains for task B, the fourth device 40 is restored to the task B specified device list.

[0079] (1-5) Task management processing The task management process executed by the control unit 101 of the management device 100 to realize the various functions according to the main list described above will be described with reference to Fig. 6. The control unit 101 (more specifically, the CPU 101a) starts the task management process when it receives a request to execute the task management process. The execution request can be made by, for example, an administrator via the input unit 103.

[0080] When the control unit 101 starts the task management process, it performs a first execution instruction process in S110. As already described in detail, the first execution instruction process is to issue an instruction to execute a task to an associated execution target device for each device list (i.e., each task) included in the main list.

[0081] After the first execution instruction process ends, the control unit 101 performs an execution status acquisition process in S120. Specifically, the execution status of the task instructed to be executed in each execution target device for which the execution instruction was given in S110 is acquired. The execution status acquired here is, for example, the aforementioned completed, incomplete, postponed, rejected, or not executable. The execution status may be acquired in any manner. For example, the control unit 101 may acquire the execution status by communicating with the device itself. Alternatively, the device may be configured to transmit information indicating the execution status, and the execution status may be acquired from that information.

[0082] In S130, the control unit 101 performs an execution status reflection process. The execution status reflection process is a process for reflecting the execution status acquired in S120 in the main list (in other words, updating the main list). Details of the execution status reflection process are as shown in FIG. 7.

[0083] When the control unit 101 moves to the execution status reflection process, in S210, if there is an execution target device that has completed the instructed task and if that execution target device remains in the device list for the task in the main list, it deletes that execution target device from that device list.

[0084] In S220, the control unit 101 determines whether a new postponed device has occurred. If a new postponed device has not occurred, the process proceeds to S280. If a new postponed device has occurred, the process proceeds to S230.

[0085] In S230, the control unit 101 determines whether or not there is a postponed device among the newly postponed devices whose remaining time until the execution timing after postponement is less than or equal to the time threshold. If there is no postponed device whose remaining time is less than or equal to the time threshold, the process proceeds to S250. If there is a postponed device whose remaining time is less than or equal to the time threshold, the process proceeds to S240.

[0086] In S240, the control unit 101 performs a ranking change process. Specifically, the control unit 101 lowers the ranking of a postponed device in the device list associated with the postponed device whose remaining time is less than or equal to the time threshold in the main list from its current ranking. In other words, a postponed device whose remaining time is less than or equal to the time threshold is not registered in the postponed device list, and its ranking in the device list is lowered. The extent to which the ranking is lowered may be determined as appropriate. For example, the device may be lowered to the bottom of the device list.

[0087] In S250, the control unit 101 determines whether or not there is a postponed device among the new postponed devices whose remaining time is greater than the time threshold. If there is no postponed device whose remaining time is greater than the time threshold, the process proceeds to S280. If there is a postponed device whose remaining time is greater than the time threshold, the process proceeds to S260.

[0088] In S260, the control unit 101 registers the corresponding postponed device in the postponed device list. Specifically, as described above, the control unit 101 registers the device information, unexecuted task information, and postponement information of the corresponding postponed device in the postponed device list (see FIG. 3).

[0089] In S270, the control unit 101 removes the corresponding postponed device from the main list. In S270, all of the postponed devices included in the main list may be excluded. In this case, in S260, all tasks that include the devices in the main list may be registered in the delayed device list as unexecuted task information.

[0090] Alternatively, in S270, some of the postponed devices included in the main list may be excluded. Specifically, for example, among the device lists in which the postponed device is included, the postponed device may be excluded only from the device list that is first in the task order. In this case, in S260, only the task corresponding to that first device list may be registered in the delayed device list as unexecuted task information.

[0091] In S280, the control unit 101 determines whether a new rejected device has occurred. If a new rejected device has not occurred, this process ends and the process proceeds to S140 (FIG. 6). If a new rejected device has occurred, the process proceeds to S290.

[0092] In S290, the control unit 101 registers the corresponding rejected device in the rejected device list. Specifically, as described above, the control unit 101 registers the device information and unexecuted task information of the corresponding rejected device in the rejected device list (see FIG. 3).

[0093] In S300, the control unit 101 removes the corresponding rejected device from the main list. In S300, all of the rejected devices included in the main list may be excluded. In this case, in S290, all tasks that include the devices in the main list may be registered in the rejected device list as unexecuted task information.

[0094] Alternatively, in S300, some of the rejected devices included in the main list may be excluded in the same manner as in S270. In this case, in S290, only the task corresponding to the first device in the list may be registered in the rejected device list as unexecuted task information. Returning to FIG. 6 , in S140, the control unit 101 deletes the device list from which all execution target devices have been deleted from the main list. In S150, the control unit 101 determines whether or not a device list remains in the main list. If no device list remains in the main list, this process ends. If at least one device list remains, this process proceeds to S160. In S160, the control unit 101 waits until a re-execution requirement is met. The re-execution requirement may be determined in any manner. For example, the re-execution requirement may be that a certain amount of time has elapsed from a predetermined timing after the start of the first execution instruction process in S110 (for example, the end of S140). If the re-execution requirement is met, this process proceeds to S110. Note that if a device list remains in the main list in S150, the process may proceed to S110 without performing the process of S160.

[0095] (1-6) Postponement cancellation process Next, the postponement cancellation process will be described with reference to Fig. 8. The postponement cancellation process is a process for causing a postponed device registered in the postponed device list to execute a task. The control unit 101 repeatedly executes the postponement cancellation process, for example, periodically.

[0096] When the control unit 101 starts the postponement cancellation process, it determines in S410 whether or not a postponed device is registered in the postponed device list. If a postponed device is not registered in the postponed device list (including the case where the postponed device list itself does not exist), the control unit 101 ends this postponement cancellation process. If a postponed device is registered in the postponed device list, this process proceeds to S420.

[0097] In S420, the control unit 101 determines whether or not there is a postponed device whose execution timing has arrived among the registered postponed devices. If there is no postponed device whose execution timing has arrived, the control unit 101 ends this postponement cancellation process. If there is a postponed device whose execution timing has arrived, this process proceeds to S430.

[0098] In S430, the control unit 101 performs a revival process. The revival process is a process of restoring a postponed device whose execution timing has arrived to the main list. Once the postponed device is restored to the main list, a task execution instruction is issued to that device by the first execution instruction process of S110. The revival process of S430 includes the processes of S431 to S433, as shown in FIG. 8.

[0099] In S431, the control unit 101 determines whether all unexecuted tasks associated with the postponed device whose execution timing has arrived are still present in the main list. If all unexecuted tasks are still present in the main list, the process proceeds to S432. In S432, the control unit 101 restores the postponed device to the device list of the unexecuted task in the main list. If, in S431, there is an unexecuted task for which a corresponding device list does not still exist, the process proceeds to S433. In S433, the control unit 101 newly adds an additional device list for each unexecuted task to the main list. Then, the delayed device is registered in each additional device list (see FIG. 4).

[0100] The restoration process of S430 corresponds to the first pattern described above. The restoration process of S430 may be performed according to the second pattern described above. (1-7) Rejection cancellation process Next, the rejection cancellation process will be described with reference to Fig. 9. The rejection cancellation process is a process for causing a rejected device registered in the rejected device list to execute a task. When a rejected device is registered in the rejected device list, the control unit 101 executes the rejection cancellation process at a predetermined timing. The rejection cancellation process may be executed, for example, in response to determining that a new rejected device has appeared in S280 of Fig. 7.

[0101] When the control unit 101 starts the rejection cancellation process, it performs the rejected device notification process in S510. That is, as described above, it notifies the administrator that the rejected device has been registered. In S520, the control unit 101 accepts a task execution request to the rejected device. The execution request is made, for example, by the above-mentioned revival operation or a direct instruction operation. The direct instruction operation is an operation that instructs the rejected device to execute a task without restoring the rejected device to the main list.

[0102] In S530, the control unit 101 determines whether an execution request was made in S520. If an execution request was not made, this process ends. If an execution request was made, this process proceeds to S540.

[0103] In S540, the control unit 101 performs the revival process or the second execution instruction process depending on the specific content of the execution request. Specifically, if the execution request is made by a revival operation, the control unit 101 performs the revival process. The revival process may be performed in the same manner as S430 in FIG. 8, for example. That is, the revival process of S540 may be performed by replacing "postponed device" with "rejected device" in S430 in FIG. 8. Alternatively, the revival process of S540 may be performed according to the second pattern described above.

[0104] On the other hand, when the execution request is made by a direct instruction operation, the control unit 101 performs a second execution instruction process, which instructs the rejected device that is the target of the execution request to execute the uncompleted task without restoring the rejected device to the main list.

[0105] (1-8) Correspondence of words The management device 100 corresponds to an example of an information processing device in the present disclosure. The control unit 101 corresponds to an example of a computer in the present disclosure. The additional device list corresponds to an example of an additional command group in the present disclosure. The postponed state and the rejected state correspond to an example of a specific state in the present disclosure. The prescribed device list (all of the first to third prescribed device lists in FIG. 3) to which the postponed device (second device 20 in FIG. 3) and / or rejected device (fourth device 40 in FIG. 3) are associated, as illustrated in FIG. 3, corresponds to an example of an excluded task group in the present disclosure.

[0106] S120 corresponds to an example of a first execution instruction process in the present disclosure. S130 corresponds to an example of an acquisition process in the present disclosure. S260 and S290 each correspond to an example of a device exclusion process in the present disclosure. S140 corresponds to an example of a task deletion process in the present disclosure. The process of S520 corresponds to an example of a reception process in the present disclosure.

[0107] 2. Other Embodiments Although the embodiments of the present disclosure have been described above, the present disclosure is not limited to the above-described embodiments and can be implemented in various modified forms.

[0108] (2-1) In the above embodiment, the command set 104a includes three tasks A to C. However, the command set 104a may include two or fewer tasks or four or more tasks. Furthermore, the tasks A to C in the above embodiment are tasks for updating firmware. However, the tasks to be executed by the device may be of any content.

[0109] (2-2) In the postponement cancellation process (FIG. 8), instead of the revival process (S430), a second execution instruction process may be performed for the postponed device, that is, a process similar to the second execution instruction process of S540 in FIG. 9. Specifically, in S430, an instruction to execute the uncompleted task may be sent to the postponed device that is the target of the execution request, without restoring the postponed device to the main list.

[0110] (2-3) The main list may be in any form. For example, the main list may comprise a single list (or table). The list may contain device information for each execution target device and information on the task to be executed. Then, in the first execution instruction process, the execution of the associated task may be instructed sequentially for each execution target device according to the list.

[0111] (2-4) In the above embodiment, postponed devices and rejected devices are shown as examples of specific-state devices of the present disclosure. However, specific-state devices of the present disclosure are not limited to postponed devices and rejected devices. For example, a device whose execution status is the aforementioned "unexecutable" may also be considered a specific-state device of the present disclosure, and the technology of the present disclosure may be applied to it. Specifically, a "unexecutable" device may also be excluded from the main list. Then, similar to a rejected device, the device may be restored to the main list at an appropriate time, for example, by an administrator's operation, or a task execution instruction may be issued without restoring the device to the main list.

[0112] (2-5) Multiple functions possessed by one component in the above embodiments may be realized by multiple components, or one function possessed by one component may be realized by multiple components. Also, multiple functions possessed by multiple components may be realized by one component, or one function realized by multiple components may be realized by one component. Also, part of the configuration of the above embodiments may be omitted. [Explanation of symbols]

[0113] 1...management system, 10-50...1st to 5th devices, 11...control unit, 12...display unit, 13...input unit, 14...communication unit, 15...printing unit, 16...firmware, 100...management device, 101...control unit, 101a...CPU, 101b...memory, 102...display unit, 103...input unit, 104...storage unit, 104a...instruction group, 104b...device management program, 105...communication unit, 200...network.

Claims

1. A device management program executable by a computer of an information processing device configured to be able to communicate with a plurality of devices, The computer, a first execution instruction process for processing a group of instructions including one or more tasks, wherein at least one of the plurality of devices that is to execute the task is associated with each of the one or more tasks as an execution target device, and for each of the one or more tasks, an instruction to execute the task is given to the execution target device associated with the task in sequence in a predetermined task order; an acquisition process of acquiring an execution status of the group of instructions in the plurality of devices in response to the first execution instruction process; a device exclusion process for excluding a specific state device, which is a device in a specific state that cannot normally complete the group of instructions, from an exclusion target task group, which is at least one task associated with the specific state device among the one or more tasks, when the specific state device is present among the plurality of devices based on the execution status acquired by the acquisition process; A device management program that runs

2. 2. The device management program according to claim 1, the first execution instruction process is repeatedly executed for each of the one or more tasks on the execution target devices for which the task has not been completed until the task is completed on all of the associated execution target devices; Device management program.

3. 3. The device management program according to claim 1, the group of excluded tasks includes all tasks, among the one or more tasks, that are associated with the specific state device and that have not yet been completed in the specific state device; Device management program.

4. 3. The device management program according to claim 1, In the device exclusion process, when two or more incomplete tasks are associated with the specific state device, and when the execution of a second task of the two or more tasks in the task order does not require the completion of a first task, the second task is not included in the group of tasks to be excluded, and the association of the specific state device is maintained. Device management program.

5. 3. The device management program according to claim 1, The computer, a second execution instruction process for instructing the specific state device excluded from the task group to be excluded by the device exclusion process to execute the task corresponding to the task group to be excluded; A device management program that runs

6. 3. The device management program according to claim 1, The computer, a restoration process for re-associating the specific state device, which has been excluded from the group of excluded tasks by the device exclusion process, with the group of excluded tasks as the device to be executed; A device management program that runs

7. 7. The device management program according to claim 6, The computer, a task deletion process for deleting the task from the set of instructions when the task has been completed in all of the associated execution target devices; Execute the revival process generates an additional set of instructions when any of the tasks in the group of tasks to be excluded has been deleted by the task deletion process, and the additional set of instructions includes the task deleted by the task deletion process and associated with the specific state device; the first execution instruction process includes, in response to generation of the additional group of instructions, issuing again an instruction to execute the task to the specific state device associated with the task included in the additional group of instructions. Device management program.

8. 8. The device management program according to claim 7, When any of the tasks in the group of tasks to be excluded has been deleted by the task deletion process, the restoration process generates the additional group of instructions including all of the tasks included in the group of tasks to be excluded. Device management program.

9. 3. The device management program according to claim 1, the specific state device includes a refusal device that is a device that has refused to execute at least one of the one or more tasks; The device management program is installed on the computer. a notification process for notifying a user of the information processing device that the rejected device exists; A device management program that runs

10. 6. The device management program according to claim 5, the specific state device includes a refusal device that is a device that has refused to execute at least one of the one or more tasks; The device management program is installed on the computer. a reception process for receiving an execution request from a user of the information processing device; Execute The second execution instruction process is executed in response to the acceptance of the execution request. Device management program.

11. 7. The device management program according to claim 6, the specific state device includes a refusal device that is a device that has refused to execute at least one of the one or more tasks; The device management program is installed on the computer. a reception process for receiving an execution request from a user of the information processing device; Execute The restoration process is executed in response to the acceptance of the execution request. Device management program.

12. 6. The device management program according to claim 5, the specific state device includes a postponement device that indicates that execution of at least one of the one or more tasks is to be postponed until a predetermined execution timing; the second execution instruction process is executed in response to the arrival of the execution timing; Device management program.

13. 7. The device management program according to claim 6, the specific state device includes a postponement device that indicates that execution of at least one of the one or more tasks is to be postponed until a predetermined execution timing; The restoration process is executed in response to the arrival of the execution timing. Device management program.

14. 3. The device management program according to claim 1, In the set of instructions, an instruction order for issuing the execution instructions to the execution target device associated with each task is determined for each task, the first execution instruction process performs the execution instructions in order according to the instruction order; the specific state device includes a postponement device that indicates that execution of at least one of the one or more tasks is to be postponed until a predetermined execution timing; the device exclusion process excludes the postponed device from the processing target of the device exclusion process when the remaining time until the execution timing is equal to or less than a time threshold; The device management program further includes: executes a rank change process for lowering the rank of the postponed device in the instruction order from its current rank in each of the excluded task group; Device management program.

15. An information processing device configured to be able to communicate with a plurality of devices and including a control unit, The control unit an execution instruction process for processing a group of instructions including one or more tasks, wherein at least one of the plurality of devices that is to execute the task is associated with each of the one or more tasks as an execution target device, and for each of the one or more tasks, an instruction to execute the task is given to the execution target device associated with the task in sequence in a predetermined task order; an acquisition process for acquiring execution statuses of the group of instructions in the plurality of devices in response to the execution instruction process; a device exclusion process for excluding a specific state device, which is a device in a specific state that cannot normally complete the group of instructions, from an exclusion target task group, which is at least one task associated with the specific state device among the one or more tasks, when the specific state device is present among the plurality of devices based on the execution status acquired by the acquisition process; An information processing device configured to execute the above.

16. issuing, for each of one or more tasks, an instruction to execute the task to a device among the plurality of devices that is associated with the task; acquiring an execution status of the task that is the target of the execution instruction in the plurality of devices in response to the execution instruction; based on the acquired execution status, when there is a specific state device among the plurality of devices that is a device in a specific state that cannot normally complete the task that is the target of the execution instruction, excluding the specific state device from at least one task to which the specific state device is associated, among the one or more tasks; A device management method comprising:

Images