JP7701672B2 - Equipment management system and equipment management program - Google Patents

Description

The present invention relates to a device management system and a device management program that remotely updates software on electronic devices.

Conventional device management systems are known that remotely update firmware, which is software for an image forming device that is an electronic device (see, for example, Patent Documents 1-3). Here, firmware updates are performed, for example, to add new functions to the image forming device or to repair defects that have occurred in the image forming device.

JP 2002-288066 A JP 2004-139572 A JP 2008-065505 A

However, conventional device management systems do not focus on the speed of firmware updates for all image forming devices that are the target of firmware updates, which results in a problem of poor usability.

The present invention therefore aims to provide a device management system and a device management program that can improve the convenience of software updates.

The device management system of the present invention provides a plurality of modes that differ from each other in at least one of the length of the period during which the update is executed once for all electronic devices that are the subject of the software update, and the ratio of the number of electronic devices on which the update is executed per unit time among all the electronic devices, and generates the update task for each of all the electronic devices in one of the modes selected from the plurality of modes.

With this configuration, the device management system of the present invention generates software update tasks for all electronic devices that are to be updated in one mode selected from multiple modes, thereby improving the convenience of software updates.

In the device management system of the present invention, the multiple modes may include a first mode and a second mode in which the length of the period is longer than that of the first mode.

With this configuration, the device management system of the present invention generates software update tasks for all electronic devices to be updated in one mode selected from the first mode and the second mode in which the length of time for all electronic devices to be updated to undergo one round of updates is longer than the first mode. This allows a user who wants updates to be performed immediately on all electronic devices to be updated to select the first mode, and allows a user who wants updates to be performed gradually on all electronic devices to be updated to ensure that the updates do not cause problems for the electronic devices to select the second mode, thereby improving the convenience of software updates.

In the device management system of the present invention, the first mode may be a mode in which the ratio does not change during the period, and the second mode may be a mode in which the ratio increases during the period.

With this configuration, the device management system of the present invention generates software update tasks for all electronic devices to be updated in one mode selected from a first mode in which the ratio of the number of electronic devices on which updates are performed per unit time among all electronic devices to be updated does not change during the period in which one set of updates is performed for all electronic devices to be updated, and a second mode in which the ratio of the number of electronic devices on which updates are performed per unit time among all electronic devices to be updated increases during the period in which one set of updates is performed for all electronic devices to be updated. This allows a user who wants updates to be performed immediately on all electronic devices to be updated to select the first mode, and allows a user who wants updates to be performed gradually on all electronic devices to be updated to confirm that the updates will not cause problems for the electronic devices to select the second mode, thereby improving the convenience of software updates.

The device management system of the present invention may generate the task so that the period is repeated, and the multiple modes may include a first mode and a second mode in which the length of the period the first time is longer than that of the first mode and the length of the period from the second time onwards is the same as that of the first mode.

With this configuration, the device management system of the present invention generates software update tasks for all electronic devices to be updated in one mode selected from the first mode and the second mode in which the length of the first cycle in which updates are performed once for all electronic devices to be updated is longer than that of the first mode and the length of the second and subsequent cycles is the same as that of the first mode. Therefore, a user who wishes updates to be performed immediately for all electronic devices to be updated can select the first mode, and a user who wishes updates to be performed gradually for all electronic devices to be updated to confirm that the updates will not cause problems for the electronic devices can select the second mode, thereby improving the convenience of software updates. In addition, since the length of the second and subsequent cycles is the same in the device management system of the present invention, after it is confirmed that the updates will not cause problems for the electronic devices, updates can be performed immediately for all electronic devices to be updated, thereby improving the convenience of software updates.

In the device management system of the present invention, the first mode may be a mode in which the ratio does not change during the period, and the second mode may be a mode in which the ratio increases during the first period and does not change during the second or subsequent periods.

With this configuration, the device management system of the present invention generates software update tasks for each of all electronic devices that are the target of updates in one mode selected from a first mode in which the ratio of the number of electronic devices on which updates are performed per unit time among all electronic devices that are the target of updates does not change during all cycles in which updates are performed on all electronic devices that are the target of updates, and a second mode in which the ratio of the number of electronic devices on which updates are performed per unit time among all electronic devices that are the target of updates increases during the first cycle and does not change during the second or subsequent cycles. This allows a user who wants updates to be performed immediately on all electronic devices that are the target of updates to select the first mode, and allows a user who wants updates to be performed gradually on all electronic devices that are the target of updates to confirm that the updates will not cause problems in the electronic devices to select the second mode, thereby improving the convenience of software updates. Furthermore, in the device management system of the present invention, the ratio of the number of electronic devices on which updates are performed per unit time among all electronic devices that are subject to updates does not change between the second and subsequent cycles in the first and second modes, so that after it is confirmed that the update will not cause problems in the electronic devices, updates can be performed quickly on all electronic devices that are subject to updates, thereby improving the convenience of software updates.

The device management system of the present invention may generate the task so that the period is repeated, and may generate the task for each of all of the electronic devices even if all of the electronic devices include an electronic device that was successfully updated during the previous period.

With this configuration, the device management system of the present invention generates an update task for each of the electronic devices to be updated, even if all of the electronic devices to be updated include electronic devices that were successfully updated in the previous period. Therefore, even if an electronic device that was successfully updated in the previous period was updated with a new version of software after the successful update, the original version of the software is updated again in the current period, and as a result, software variation between multiple electronic devices can be reduced.

The device management system of the present invention may generate the task so that the period is repeated, and may start generating the task from the next period for the electronic device that becomes the new target of the update during the period.

With this configuration, the device management system of the present invention starts generating update tasks for electronic devices that become newly subject to an update in the middle of a cycle in which updates are performed once for all electronic devices that are subject to the update, from the next cycle. This makes it easier to manage update tasks compared to a configuration in which update tasks are started to be generated for electronic devices that become newly subject to an update in the middle of a cycle at the time they become newly subject to an update.

The device management program of the present invention is characterized in that it provides a computer with a plurality of modes that differ from each other in at least one of the length of the period during which the update is executed once for all electronic devices that are the subject of the software update and the ratio of the number of electronic devices on which the update is executed per unit time among all the electronic devices, and causes the computer to generate the update task for each of all the electronic devices in one of the modes selected from the plurality of modes.

With this configuration, a computer executing the device management program of the present invention generates software update tasks for all electronic devices that are to be updated in one mode selected from multiple modes, thereby improving the convenience of software updates.

The device management system and device management program of the present invention can improve the convenience of software updates.

1 is a block diagram of an information processing system according to an embodiment of the present invention. 2 is a diagram illustrating an example of a group of image forming apparatuses in the information processing system illustrated in FIG. 1 . FIG. 2 is a block diagram of the device management system shown in FIG. 1 when configured by one computer. FIG. 4 is a diagram illustrating an example of device information illustrated in FIG. 3 . FIG. 4 is a diagram illustrating an example of a F/W package illustrated in FIG. 3 . FIG. 4 is a diagram illustrating an example of a manual F/W update task illustrated in FIG. 3 . FIG. 4 is a diagram showing an example of the automatic F/W update plan shown in FIG. 3 . 8 is a table showing specific contents of "gradual update" in the item "automatic F/W update mode" shown in FIG. 7; FIG. 4 is a diagram illustrating an example of an automatic F/W update group setting illustrated in FIG. 3 . FIG. 4 is a diagram illustrating an example of task information illustrated in FIG. 3 . FIG. 2 is a block diagram of the image forming apparatus without an intermediary shown in FIG. 1 when configured by an MFP. FIG. 2 is a block diagram of the intermediary device shown in FIG. 1 . 4 is a flowchart showing the operation of the device management system shown in FIG. 3 when a user logs in. 4 is a flowchart of a part of the operation of the device management system shown in FIG. 3 when managing a F/W package. 15 is a continuation of the flowchart shown in FIG. 14 . FIG. 16 is a diagram showing an example of a package management screen displayed on a user terminal in the operations shown in FIGS. 14 and 15. FIG. 16 is a diagram showing an example of an impact notification screen displayed on a user terminal in the operations shown in FIGS. 14 and 15. 4 is a flowchart of the operation of the device management system shown in FIG. 3 when a manual F/W update is executed. FIG. 20 is a diagram showing an example of a manual F/W update setting screen displayed on a user terminal in the operation shown in FIG. 18 . 4 is a flowchart of a part of the operation of the device management system shown in FIG. 3 when an automatic F/W update group setting is edited; 21 is a continuation of the flowchart shown in FIG. 20 . FIG. 22 is a diagram showing an example of a group setting editing screen displayed on a user terminal in the operations shown in FIGS. 20 and 21 . 4 is a flowchart of the operation of the device management system shown in FIG. 3 when executing a F/W update test. 4 is a flowchart of a part of the operation of the device management system shown in FIG. 3 when an automatic F/W update plan is edited; 25 is a continuation of the flowchart shown in FIG. 24. 26 is a continuation of the flowchart shown in FIG. 25 . A figure showing an example of a plan editing screen displayed on a user terminal during the operations shown in Figures 24 to 26. 4 is a flowchart showing the operation of the device management system shown in FIG. 3 when deleting an automatic F/W update plan. 4 is a flowchart showing the operation of the device management system shown in FIG. 3 when starting execution of an automatic F/W update. 4 is a flowchart of a part of the operation of the device management system shown in FIG. 3 when an automatic F/W update is executed. This is a continuation of the flowchart shown in Figure 30. 4 is a flowchart showing the operation of the device management system shown in FIG. 3 when managing an automatic F/W update task. FIG. 33 is a diagram showing an example of a task management screen displayed on a user terminal in the operation shown in FIG. 32 . 4 is a flowchart showing the operation of the device management system shown in FIG. 3 when an image forming apparatus is deleted from the management targets. 4 is a flowchart of the operation of the device management system shown in FIG. 3 in the case where a group to which an image forming apparatus belongs is deleted. 4 is a flowchart showing the operation of the device management system shown in FIG. 3 when pre-printing is executed on a non-intermediary image forming apparatus. 4 is a flowchart of a part of the operation of the device management system shown in FIG. 3 when an automatic F/W update task is executed on a non-intermediary image forming apparatus. This is a continuation of the flowchart shown in Figure 37. 10 is a flowchart of the operation of the intermediary device shown in FIG. 1 when periodically requesting a F/W update task from the device management system. 4 is a flowchart of a part of the operation of the device management system shown in FIG. 3 when a F/W update task is requested from the intermediary device. This is a continuation of the flowchart shown in Figure 40. 10 is a flowchart of the operation of the intermediary device shown in FIG. 1 when executing pre-printing on an image forming device managed by the intermediary device itself. 10 is a flowchart of a part of the operation of the intermediary device shown in FIG. 1 when executing an automatic F/W update task for an image forming device managed by the intermediary device itself; This is a continuation of the flowchart shown in Figure 43. 4 is a flowchart of the operation of the device management system shown in FIG. 3 in the case where a value of the "Status" item of task information of a F/W update task for an intermediate image forming apparatus is set. 4 is a flowchart of the operation of the device management system shown in FIG. 3 in the case where the progress status of a F/W update according to an automatic F/W update plan is displayed. FIG. 47 is a diagram showing an example of a progress status screen displayed on a user terminal in the operation shown in FIG. 46. 4 is a flowchart of a part of the operation of the device management system shown in FIG. 3 when updating the progress status screen. This is a continuation of the flowchart shown in Figure 48. FIG. 48 is a diagram showing an example of a change in the progress status shown on the progress status screen shown in FIG. 47.

The following describes an embodiment of the present invention with reference to the drawings.

First, we will explain the configuration of an information processing system according to one embodiment of the present invention.

Figure 1 is a block diagram of an information processing system 10 according to this embodiment.

As shown in FIG. 1, the information processing system 10 includes a device management system 20 that manages an image forming device as an electronic device. The device management system 20 is capable of executing a manual F/W update in which a task (hereinafter referred to as a "F/W update task") for updating firmware (hereinafter referred to as a "F/W update") as software for the image forming device is individually specified by a user of the device management system 20, and an automatic F/W update in which the device management system 20 automatically generates a F/W update task in response to an instruction from a user of the device management system 20. The device management system 20 may be configured with one computer or multiple computers.

The information processing system 10 includes an image forming device (hereinafter referred to as an "intermediary-free image forming device") 30 that is not only capable of accessing the device management system 20 without going through an intermediary device described below, but can also be accessed by the device management system 20 without going through an intermediary device. The information processing system 10 can include at least one other intermediary-free image forming device in addition to the intermediary-free image forming device 30. The intermediary-free image forming device other than the intermediary-free image forming device 30 may be one that is located on the same LAN (Local Area Network) as the intermediary-free image forming device 30, or one that is located on a different LAN from the LAN in which the intermediary-free image forming device 30 is located.

The information processing system 10 includes an intermediate device 40 that intermediates between the device management system 20 and the image forming device, and an image forming device 50 that is arranged on the same LAN as the LAN on which the intermediate device 40 is arranged and is intermediated between the device management system 20 and the image forming device 50 by the intermediate device 40 (hereinafter, an image forming device that is arranged on the same LAN as the LAN on which the intermediate device is arranged and is intermediated between the device management system 20 and the image forming device 50 by the intermediate device is referred to as an "intermediate image forming device"). The intermediate device 40 can access the device management system 20, but is prevented from being accessed by the device management system 20 by, for example, a firewall not shown. The information processing system 10 can include at least one intermediate image forming device that is arranged on the same LAN as the LAN on which the intermediate image forming device 50 is arranged and is intermediated between the device management system 20 and the image forming device 50 by the intermediate device 40, in addition to the intermediate image forming device 50. The information processing system 10 is arranged on a LAN different from the LAN on which the intermediary device 40 is arranged, and can include at least one intermediary device that mediates between the device management system 20 and the image forming device. The information processing system 10 is arranged on the same LAN as any intermediary device other than the intermediary device 40, and can include at least one intermediary image forming device that is mediated between the information processing system 10 and the device management system 20 by this intermediary device.

The image forming device in the information processing system 10 is, for example, an MFP (Multifunction Peripheral) or a dedicated printer. The intermediary device in the information processing system 10 is, for example, a computer such as a PC (Personal Computer).

The information processing system 10 includes a user terminal 60 that is used by a user of the device management system 20. The information processing system 10 can include at least one other user terminal in addition to the user terminal 60 that is used by a user of the device management system 20. The user terminal is configured, for example, by a computer such as a PC. Users of the device management system 20 include, for example, a person on the dealer's side who provides an image forming device to a user of the image forming device (hereinafter referred to as the "device user"), who is an administrator (hereinafter referred to as the "dealer's administrator") who manages the image forming device provided by the dealer to the device user; a person on the dealer's side who performs services such as maintenance on the image forming device provided by the dealer to the device user (hereinafter referred to as the "dealer's service person"); a person on the sales company side who provides image forming devices to device users and manages dealers, who is an administrator (hereinafter referred to as the "sales company's administrator") who manages the image forming device provided by the sales company to the device user and the image forming device provided by the dealer managed by the sales company to the device user; and a person on the sales company side who performs services such as maintenance on the image forming device provided by the sales company to the device user and the image forming device provided by the dealer managed by the sales company (hereinafter referred to as the "sales company's service person").

Figure 2 shows an example of a group of image forming devices in the information processing system 10.

As shown in FIG. 2, the image forming devices in the information processing system 10 are managed in a hierarchical structure by the device management system 20.

The hierarchical structure managed by the device management system 20 includes a delegated group 71 that corresponds to a specific sales company. The hierarchical structure managed by the device management system 20 may include a delegated group corresponding to each sales company in addition to the delegated group 71.

The hierarchical structure managed by the equipment management system 20 has a delegated group 72 corresponding to a specific dealer under a delegated group 71 corresponding to the sales company that manages this dealer. The hierarchical structure managed by the equipment management system 20 may have a delegated group corresponding to a dealer under a delegated group corresponding to the sales company that manages this dealer for each dealer.

The hierarchical structure managed by the device management system 20 has a group 73 corresponding to a specific device user under a delegated group 71 corresponding to the sales company that directly manages this device user. The hierarchical structure managed by the device management system 20 may have a group corresponding to the device user under a delegated group corresponding to the sales company that directly manages this device user for each device user.

The hierarchical structure managed by the device management system 20 includes a group 74 to which at least some of the image forming devices used by a specific device user belong, under a group 73 corresponding to this device user. For example, group 74 is a group of image forming devices that exist in a specific business establishment of the device user corresponding to group 73. The hierarchical structure managed by the device management system 20 may also include a group to which at least some of the image forming devices used by a device user that is directly managed by a sales company belong, under a group corresponding to this device user.

The hierarchical structure managed by the device management system 20 has a group 75 corresponding to a specific device user under a delegated group 72 corresponding to a dealer who directly manages this device user. The hierarchical structure managed by the device management system 20 may have a group corresponding to a device user under a delegated group corresponding to a dealer who directly manages this device user for each device user.

The hierarchical structure managed by the device management system 20 includes a group 76 to which at least some of the image forming devices used by a specific device user belong, under a group 75 corresponding to this device user. For example, group 76 is a group of image forming devices that exist in a specific business establishment of the device user corresponding to group 75. The hierarchical structure managed by the device management system 20 may also include a group to which at least some of the image forming devices used by a device user directly managed by a dealer belong, under a group corresponding to this device user.

Figure 3 is a block diagram of the device management system 20 when configured with one computer.

As shown in FIG. 3, the device management system 20 includes an operation unit 21, which is an operation device such as a keyboard or mouse through which various operations are input; a display unit 22, which is a display device such as an LCD (Liquid Crystal Display) that displays various information; a communication unit 23, which is a communication device that communicates with external devices via a network such as a LAN or the Internet, or directly by wire or wirelessly without using a network; a storage unit 24, which is a non-volatile storage device such as a semiconductor memory or HDD (Hard Disk Drive) that stores various information; and a control unit 25 that controls the entire device management system 20.

The storage unit 24 can store a device management program 24a for managing the image forming device. The device management program 24a may be installed in the device management system 20 during the manufacturing stage of the device management system 20, or may be additionally installed in the device management system 20 from an external storage medium such as a Universal Serial Bus (USB) memory, or may be additionally installed in the device management system 20 from a network.

The memory unit 24 stores authentication information 24b that indicates the information required to authenticate users of the device management system 20 for each user's identification information (hereinafter referred to as "user ID").

The memory unit 24 stores authorization information 24c that indicates the authority of a user of the device management system 20 for each user ID. The authority of a user of the device management system 20 includes, for example, the authority of the administrator of the device management system 20 (hereinafter referred to as the "system administrator"), the authority of a sales company administrator of a specific sales company, the authority of a dealer administrator of a specific dealer, the authority of a sales company service person of a specific sales company, and the authority of a dealer service person of a specific dealer.

The memory unit 24 stores address information 24d that indicates the email addresses of users of the device management system 20 for each user ID.

The storage unit 24 stores group information 24e that indicates information about groups managed by the device management system 20. The group information 24e includes, for example, information in a hierarchical structure as shown in FIG. 2.

The memory unit 24 stores device information 24f that indicates information about the image forming device managed by the device management system 20.

The memory unit 24 can store language settings 24g that indicate for each delegated group the language to be used for various outputs, such as the display language for the group setting editing screen, test progress screen, package management screen, impact notification screen, and plan editing screen described below.

The storage unit 24 is capable of storing a firmware package (hereinafter referred to as "F/W package") 24h for the image forming device. The storage unit 24 is capable of storing at least one F/W package other than the F/W package 24h.

The memory unit 24 can store a manual F/W update task 24i, which is a F/W update task in a manual F/W update. The memory unit 24 can store at least one manual F/W update task other than the manual F/W update task 24i.

The storage unit 24 can store an automatic F/W update plan 24j, which is a setting for automatically generating an automatic F/W update task, which is an F/W update task in an automatic F/W update. The storage unit 24 can store at least one automatic F/W update plan other than the automatic F/W update plan 24j that has a similar configuration to the automatic F/W update plan 24j.

The storage unit 24 can store automatic F/W update group settings 24k, which are settings for each group to which the image forming device belongs, for performing automatic F/W updates. The storage unit 24 can store automatic F/W update group settings having the same configuration as the automatic F/W update group settings 24k for each group shown in FIG. 2.

The storage unit 24 can store the automatic F/W update task 24l. The storage unit 24 can store at least one automatic F/W update task other than the automatic F/W update task 24l. The storage unit 24 can store one automatic F/W update task for each image forming device for each automatic F/W update plan.

The memory unit 24 can store a test F/W update task 24m, which is a F/W update task for testing a F/W update. The memory unit 24 can store at least one test F/W update task other than the test F/W update task 24m.

The memory unit 24 can store task information 24n that indicates various information about the F/W update task.

The control unit 25 includes, for example, a CPU (Central Processing Unit), a ROM (Read Only Memory) that stores programs and various data, and a RAM (Random Access Memory) as a volatile storage device used as a working area for the CPU of the control unit 25. The CPU of the control unit 25 executes the programs stored in the storage unit 24 or the ROM of the control unit 25.

By executing the device management program 24a, the control unit 25 realizes a login processing unit 25a that executes processing for login of users of the device management system 20, a package management unit 25b that manages F/W packages, a manual update unit 25c that executes manual F/W updates, an automatic update unit 25d that executes automatic F/W updates, a task management unit 25e that manages F/W update tasks, and a device management unit 25f that manages image forming devices.

Figure 4 shows an example of device information 24f.

As shown in FIG. 4, the device information 24f includes, for example, a device ID which is identification information of the image forming device, a group ID which is identification information of the group to which the image forming device belongs, an intermediary device ID which is identification information of the intermediary device that manages the image forming device if the image forming device is an intermediary image forming device, information indicating the model of the image forming device, information indicating whether F/W updates using the device management system 20 are permitted for the image forming device, the type of release of firmware installed in the image forming device (hereinafter, the type of firmware release is simply referred to as "release type"), and the version of firmware installed in the image forming device (hereinafter, the firmware version is referred to as "F/W version") for each image forming device. Here, the release type includes "official", which indicates that the firmware is official and not customized, and "customized", which indicates that the firmware is customized.

Figure 5 shows an example of F/W package 24h.

As shown in FIG. 5, F/W package 24h includes firmware, release type information indicating the release type of this firmware, F/W version information indicating the F/W version of this firmware, and target model information indicating the model of the image forming device targeted by this firmware (hereinafter, the model of the image forming device targeted by the firmware is referred to as the "target model").

Figure 6 shows an example of a manual F/W update task 24i.

As shown in FIG. 6, the manual F/W update task 24i includes, for example, a scheduled execution time of the manual F/W update task 24i (hereinafter, the scheduled execution time is simply referred to as the "scheduled execution time"), a target image forming device of the manual F/W update task 24i, a link for downloading the target F/W package of the manual F/W update task 24i from the device management system 20 (hereinafter, referred to as the "package download link"), and a F/W version of the firmware in the target F/W package of the manual F/W update task 24i. In the manual F/W update task 24i, the target image forming device is represented by a device ID. The configurations of manual F/W update tasks other than the manual F/W update task 24i, the configuration of the automatic F/W update task, and the configuration of the test F/W update task are also similar to the configuration of the manual F/W update task 24i.

Figure 7 shows an example of an automatic F/W update plan 24j.

As shown in FIG. 7, the automatic F/W update plan 24j includes a "target F/W package" item indicating the target F/W package for the automatic F/W update, a "target group" item indicating the target group for the automatic F/W update, an "automatic F/W update mode" item indicating the mode of the automatic F/W update, and an "enabled/disabled" item indicating whether the automatic F/W update plan 24j itself is enabled or disabled.

In the "Target F/W package" item, for example, a F/W package is specified by the identification information of the F/W package (hereinafter referred to as "package ID"). For example, in the example shown in FIG. 7, the F/W package identified by the package ID "P0001" is specified in the "Target F/W package" item.

The "Target Group" item can be set to one of three values: "All Accessible," which indicates all groups under the specified delegated group; "Exclusively Managed," which indicates all groups directly under the specified delegated group; or "Off," which specifies groups individually.

When "All Accessible" is specified in the "Target Group" item, one of the delegated groups is further specified in the "Target Group" item. For example, in the example shown in FIG. 7, "All Accessible" is specified in the "Target Group" item, and delegated group 71 is further specified in the "Target Group" item. When "All Accessible" and delegated group 71 are specified in the "Target Group" item, as shown in FIG. 2, not only groups 73 and 74 corresponding to device users directly managed by the sales company corresponding to delegated group 71, but also groups 75 and 76 corresponding to device users directly managed by a dealer managed by this sales company are subject to automatic F/W update.

When "Exclusively Managed" is specified in the "Target Group" item, one of the delegated groups is further specified in the "Target Group" item. For example, when "Exclusively Managed" and delegated group 71 are specified in the "Target Group" item, as shown in FIG. 2, groups 73 and 74 corresponding to device users directly managed by the sales company corresponding to delegated group 71 will be subject to automatic F/W updates, but groups 75 and 76 corresponding to device users directly managed by a dealer managed by this sales company will not be subject to automatic F/W updates.

If "Off" is specified in the "Target Group" item, the target groups for automatic firmware updates are further specified individually in the "Target Group" item.

The "Automatic F/W update mode" item can be specified with either "Gradual update", which performs F/W updates on all image forming devices that are targets of automatic F/W updates every four weeks by increasing the number of image forming devices that are actually targets of F/W updates every week among all image forming devices that are targets of automatic F/W updates, or "Urgent update", which performs F/W updates on all image forming devices that are targets of automatic F/W updates every week. In other words, the "Automatic F/W update mode" item is an item that specifies the speed of the F/W update. The default value for the "Automatic F/W update mode" item is "Gradual update".

Figure 8 is a table showing the specific details of "Gradual Update" in the "Automatic F/W Update Mode" item.

As shown in FIG. 8, in the first week, F/W updates are attempted for 2% of all image forming devices targeted for automatic F/W updates, by the second week, F/W updates are attempted for 15% of all image forming devices targeted for automatic F/W updates, including the image forming devices that were attempted to be updated in the first week, by the third week, F/W updates are attempted for 50% of all image forming devices targeted for automatic F/W updates, including the image forming devices that were attempted to be updated in the second week, and by the fourth week, F/W updates are attempted for all image forming devices targeted for automatic F/W updates. As shown in FIG. 8, "gradual update" is a mode in which the speed of the F/W update is increased every week. Incidentally, "immediate update" is a mode in which the speed of the F/W update does not change.

The "Enabled/Disabled" item shown in FIG. 7 can be set to either "Enabled", which indicates that the automatic F/W update plan 24j itself is enabled, or "Disabled", which indicates that the automatic F/W update plan 24j itself is disabled. Note that the default value for the "Enabled/Disabled" item is "Enabled".

Figure 9 shows an example of an automatic F/W update group setting 24k.

As shown in FIG. 9, the automatic F/W update group setting 24k includes an "automatic F/W update setting" item indicating a setting according to which automatic update plan an automatic F/W update task is to be generated, a "plan permission/prohibition" item indicating whether to permit an automatic F/W update for each automatic F/W update plan for which the group targeted by the automatic F/W update group setting 24k is the target of the automatic F/W update, a "notification setting" item indicating a user to be notified by e-mail when an event occurs related to an automatic F/W update plan for which the group targeted by the automatic F/W update group setting 24k is the target of the automatic F/W update, an "execution time zone setting" item indicating a time zone for starting execution of the F/W update in the automatic F/W update, and a "pre-print setting" item indicating a setting related to pre-printing for printing a notification that an automatic F/W update is to be executed on the image forming device targeted by the automatic F/W update before the execution of the automatic F/W update.

The "Automatic F/W update setting" item can be set to one of the following values: "ON", which indicates that an automatic F/W update task is generated according to all automatic F/W update plans; "OFF", which indicates that an automatic F/W update task is not generated according to any automatic F/W update plan; or "Selected", which indicates that an automatic F/W update task is generated according to an individually selected automatic F/W update plan. The default value for the "Automatic F/W update setting" item is "OFF".

In the "Plan Allowed/Prohibited" item, either of the values "Allowed" indicating that an automatic F/W update is permitted, or "Prohibited" indicating that an automatic F/W update is not permitted can be specified for each automatic F/W update plan for which the target group of the automatic F/W update group setting 24k is the target of the automatic F/W update. In the "Plan Allowed/Prohibited" item, the automatic F/W update plan is indicated by identification information (hereinafter referred to as "Plan ID"). For example, in the example shown in FIG. 9, at least it is indicated that an automatic F/W update using an automatic F/W update plan identified by a plan ID of "PL0001" is permitted, and that an automatic F/W update using an automatic F/W update plan identified by a plan ID of "PL0003" is not permitted. Note that the default value for the "Plan Allowed/Prohibited" item is "Prohibited".

In the "Notification Settings" item, a user is specified by, for example, a user ID. For example, in the example shown in FIG. 9, at least a user identified by a user ID of "U0001" and a user identified by a user ID of "U0005" are specified in the "Notification Settings" item. The users specified in the "Notification Settings" item are, for example, the dealer's service person and the sales company's service person.

The "execution time zone setting" item includes a "day setting" item indicating the day on which the automatic F/W update starts to be executed, and a "time zone setting" item indicating the time zone on which the automatic F/W update starts to be executed. The "day setting" item can be specified with either "every day", indicating that the automatic F/W update starts to be executed every day, or "day of the week specification", indicating that the automatic F/W update starts to be executed on a specified day of the week. When "day of the week specification" is specified in the "day setting" item, at least one day of the week on which the automatic F/W update starts to be executed is further specified in the "day setting" item. For example, in the example shown in FIG. 9, Saturday and Sunday are specified in the "day setting" item. The image forming device cannot be used while the F/W update is being executed. Therefore, it is preferable that the "execution time zone setting" item specifies a time zone on which there is little problem even if the device user is unable to use the image forming device.

The "Preprint setting" item includes a "Preprint on/off" item indicating whether preprinting is performed, and a "Language setting" item indicating the language of the notification of the target of preprinting. The "Preprint on/off" item can be specified with either "ON", indicating that preprinting is performed, or "OFF", indicating that preprinting is not performed. The default value for the "Preprint on/off" item is "OFF". The "Language setting" item can be specified with either "Language set in the delegated group to which the target group of the automatic F/W update group setting 24k belongs", indicating the language set in the language setting 24g for the delegated group to which the target group of the automatic F/W update group setting 24k belongs, or a specifically specified language. The default value for the "Language setting" item is "Language set in the delegated group to which the target group of the automatic F/W update group setting 24k belongs".

Figure 10 shows an example of task information 24n.

As shown in FIG. 10, task information 24n includes, for example, a "task ID" item indicating a task ID as identification information for the F/W update task, a "generation date and time" item indicating the date and time of generation of the F/W update task, a "task type" item indicating the type of F/W update task such as "manual F/W update task," "automatic F/W update task," "test F/W update task," etc., a "status" item indicating the status of the F/W update task, a "target device" item indicating the image forming device that is the target of the F/W update task, and, if the F/W update task is an automatic F/W update task, a "related plan" item indicating the automatic F/W update plan that generated this automatic F/W update task. The states shown in the "Status" item include, for example, "Pending", which indicates the state before the execution of the F/W update task, "Cancelled", which indicates a state in which the execution of the F/W update task has been cancelled, "Waiting for execution", which indicates a state in which the execution of the F/W update task is awaited, "Executing", which indicates a state in which the F/W update task is being executed, "Success", which indicates a state in which the F/W update by the F/W update task has been successful, and "Failed", which indicates a state in which the F/W update by the F/W update task has failed. In the task information 24n, the image forming device is represented by a device ID. In the task information 24n, the automatic F/W update plan is represented by a plan ID.

Figure 11 is a block diagram of an intermediary-free image forming device 30 configured as an MFP.

As shown in FIG. 11, the non-intermediary image forming device 30 is a computer that includes an operation unit 31, which is an input device such as buttons through which various operations are input, a display unit 32, which is a display device such as an LCD that displays various information, a printer 33, which is a printing device that prints images on a recording medium such as paper, a scanner 34, which is a reading device that reads images from a document, a fax communication unit 35, which is a fax device that performs fax communication with an external facsimile machine (not shown) via a communication line such as a public telephone line, a communication unit 36, which is a communication device that communicates with an external device via a network such as a LAN or the Internet, or directly by wire or wirelessly without using a network, a memory unit 37, which is a non-volatile memory device such as a semiconductor memory or HDD that stores various information, and a control unit 38 that controls the entire non-intermediary image forming device 30.

The storage unit 37 can store firmware 37a for controlling the no-intermediary image forming device 30. The firmware 37a may be installed in the no-intermediary image forming device 30 during the manufacturing stage of the no-intermediary image forming device 30, or may be additionally installed in the no-intermediary image forming device 30 from an external storage medium such as a USB memory, or may be additionally installed in the no-intermediary image forming device 30 from the network.

The control unit 38 includes, for example, a CPU, a ROM that stores programs and various data, and a RAM as a volatile storage device used as a working area for the CPU of the control unit 38. The CPU of the control unit 38 executes the programs stored in the storage unit 37 or the ROM of the control unit 38.

The configuration of the image forming device in the information processing system 10 is the same as the configuration of the non-intermediary image forming device 30.

Figure 12 is a block diagram of the intermediary device 40.

As shown in FIG. 12, the intermediary device 40 includes an operation unit 41, which is an operation device such as a keyboard or mouse through which various operations are input; a display unit 42, which is a display device such as an LCD that displays various information; a communication unit 43, which is a communication device that communicates with external devices via a network such as a LAN or the Internet, or directly by wire or wirelessly without using a network; a memory unit 44, which is a non-volatile memory device such as a semiconductor memory or HDD that stores various information; and a control unit 45 that controls the entire intermediary device 40.

The storage unit 44 can store an intermediary program 44a for mediating between the device management system 20 and the intermediary image forming device. The intermediary program 44a may be installed in the intermediary device 40 during the manufacturing stage of the intermediary device 40, or may be additionally installed in the intermediary device 40 from an external storage medium such as a USB memory, or may be additionally installed in the intermediary device 40 from a network.

The memory unit 44 stores device information 44b that indicates information about the image forming device that the intermediary device 40 itself mediates between the device management system 20, i.e., the image forming device that is managed by the intermediary device 40.

The memory unit 44 is capable of storing F/W package 44c. The memory unit 44 is capable of storing at least one other F/W package in addition to F/W package 44c.

The memory unit 44 is capable of storing the manual F/W update task 44d. The memory unit 44 is capable of storing at least one manual F/W update task other than the manual F/W update task 44d.

The memory unit 44 is capable of storing the automatic F/W update task 44e. The memory unit 44 is capable of storing at least one automatic F/W update task other than the automatic F/W update task 44e.

The memory unit 44 is capable of storing the test F/W update task 44f. The memory unit 44 is capable of storing at least one test F/W update task other than the test F/W update task 44f.

The control unit 45 includes, for example, a CPU, a ROM that stores programs and various data, and a RAM as a volatile storage device used as a working area for the CPU of the control unit 45. The CPU of the control unit 45 executes the programs stored in the storage unit 44 or the ROM of the control unit 45.

The control unit 45 executes the intermediary program 44a to realize a F/W update unit 45a that executes F/W updates.

The configuration of the intermediary device in the information processing system 10 is the same as the configuration of the intermediary device 40.

Next, the operation of the information processing system 10 will be described.

First, we will explain the operation of the device management system 20 when updating device information 24f.

The non-intermediary image forming device periodically transmits various information about itself, such as the release type and F/W version of the firmware installed in the device, to the device management system 20, for example, once a day. The non-intermediary image forming device also transmits various information about itself, such as the release type and F/W version of the firmware installed in the device, to the device management system 20 when it starts connecting to the device management system 20. Therefore, the device management unit 25f of the device management system 20 updates the device information 24f with the information transmitted from the non-intermediary image forming device each time information is transmitted from the non-intermediary image forming device.

The intermediary device also periodically acquires various information about the intermediary image forming device it manages, such as the release type and F/W version of the firmware installed in the intermediary image forming device, from the intermediary image forming device, for example, once a day, and transmits the acquired information to the device management system 20 each time it acquires information. Therefore, the device management unit 25f of the device management system 20 updates the device information 24f with the information transmitted from the intermediary device each time information is transmitted from the intermediary device.

Next, we will explain the operation of the device management system 20 when a user logs in.

Figure 13 is a flowchart of the operation of the device management system 20 when a user logs in.

A user of the device management system 20 can send a request to log in to the device management system 20 via a user terminal to the device management system 20. Here, this request includes information necessary for authenticating the user of the device management system 20. When the control unit 25 of the device management system 20 receives a request to log in to the device management system 20, it executes the operation shown in FIG. 13.

As shown in FIG. 13, the login processing unit 25a determines whether the information required for authenticating the user of the device management system 20, which is included in the request to log in to the device management system 20, is included in the authentication information 24b (S101).

When the login processing unit 25a determines in S101 that the information included in the request to log in to the device management system 20 is included in the authentication information 24b, it returns a notification of successful login to the user terminal that sent the request to log in to the device management system 20 (S102), and ends the operation shown in FIG. 13.

When the login processing unit 25a determines in S101 that the information included in the request to log in to the device management system 20 is not included in the authentication information 24b, it returns a login failure reply to the user terminal that sent the request to log in to the device management system 20 (S103), and ends the operation shown in FIG. 13.

Next, we will explain the operation of the device management system 20 when managing F/W packages.

Figure 14 is a flowchart of part of the operation of the device management system 20 when managing F/W packages. Figure 15 is a continuation of the flowchart shown in Figure 14.

A user who is logged in to the device management system 20 can send a request to display a screen for managing F/W packages (hereinafter referred to as the "package management screen") (hereinafter referred to as the "package management screen display request") to the device management system 20 via a user terminal (hereinafter referred to as the "target user terminal" in the explanations of Figures 14 and 15). When the control unit 25 of the device management system 20 receives the package management screen display request, it executes the operations shown in Figures 14 and 15.

As shown in Figures 14 and 15, the package management unit 25b determines whether the user who sent the package management screen display request (hereinafter referred to as the "requester" in the explanation of Figures 14 and 15) has the authority of a service person or higher, based on the user ID of the requester and the authorization information 24c (S121). Here, the authority of a service person or higher includes, for example, the authority of a dealer's service person, the authority of a sales company's service person, and the authority of an administrator or higher. The authority of an administrator or higher includes, for example, the authority of a dealer's administrator, which is higher than the authority of a dealer's service person, the authority of a dealer's administrator, the authority of a sales company's administrator, which is higher than the authority of a sales company's service person, and the authority of a system administrator, which is higher than the authority of a sales company's administrator.

When the package management unit 25b determines in S121 that the requester does not have the authority of a service person or higher, it displays on the target user terminal a message indicating that the requester does not have the authority to display the package management screen (S122), and ends the operation shown in Figures 14 and 15.

When the package management unit 25b determines in S121 that the requester has authority of a service person or higher, it causes the package management screen to be displayed on the target user terminal by transmitting package management screen data to the target user terminal (S123).

Figure 16 shows an example of a package management screen 510 displayed on a user terminal during the operations shown in Figures 14 and 15.

As shown in FIG. 16, the package management screen 510 includes a list 511 showing a list of F/W packages stored in the memory unit 24, an upload button 512 for uploading the F/W package to the device management system 20, a delete button 513 for deleting the F/W package selected in the list 511 from the device management system 20, a publish button 514 for publishing the F/W package selected in the list 511, and an unpublish button 515 for unpublishing the F/W package selected in the list 511.

For each F/W package, list 511 includes the package ID, the release type of the firmware in the F/W package, the F/W version, the target model, and a publish status indicating whether or not the package has been published.

The Delete button 513, the Publish button 514, and the Unpublish button 515 can be operated only when at least one F/W package is selected in the list 511.

As shown in Figures 14 and 15, after processing S123, the package management unit 25b determines whether the upload button 512 has been pressed (S124).

When the package management unit 25b determines in S124 that the upload button 512 has been pressed, it determines whether the requester has administrator or higher authority based on the requester's user ID and the authorization information 24c (S125). Here, administrator or higher authority includes, for example, the authority of the dealer's administrator, the authority of the sales company's administrator, which is a higher authority than the authority of the dealer's administrator, and the authority of the system administrator, which is a higher authority than the authority of the sales company's administrator. On the other hand, administrator or higher authority does not include, for example, the authority of the dealer's service person or the authority of the sales company's service person.

If the package management unit 25b determines in S125 that the requester does not have administrator or higher authority, it displays on the target user terminal a message indicating that the requester does not have the authority to upload the F/W package (S126), and executes the process of S124.

When the package management unit 25b determines in S125 that the requester has administrator or higher authority, it causes a package designation screen that allows the user to designate the F/W package to be uploaded to be displayed on the target user terminal (S127). Here, the package designation screen is a screen that is closed when the F/W package is designated.

After processing S127, the package management unit 25b determines whether a F/W package has been specified on the package designation screen (S128) until it determines that a F/W package has been specified on the package designation screen.

When the package management unit 25b determines in S128 that a F/W package has been specified on the package designation screen, it accepts the upload of the F/W package specified on the package designation screen (S129). In other words, the package management unit 25b stores the F/W package specified on the package designation screen in the storage unit 24.

After processing S129, the package management unit 25b updates the package management screen so that the information shown in the list 511 becomes the latest information (S130), and then executes processing S124.

If the package management unit 25b determines in S124 that the upload button 512 has not been pressed, it determines whether the delete button 513 has been pressed (S131).

When the automatic update unit 25d determines in S131 that the delete button 513 has been pressed, it determines whether the requester has administrator or higher authority in the same manner as in the processing of S125 (S132).

If the package management unit 25b determines in S132 that the requester does not have administrator or higher authority, it displays on the target user terminal a message indicating that the requester does not have the authority to delete the F/W package (S133), and executes the process of S124.

When the package management unit 25b determines in S132 that the requester has administrator or higher authority, it causes a screen to be displayed on the target user terminal to notify the user that the automatic F/W update will be affected (hereinafter referred to as the "impact notification screen") (S134).

Figure 17 shows an example of an impact notification screen 520 displayed on a user terminal during the operations shown in Figures 14 and 15.

As shown in FIG. 17, the impact notification screen 520 includes a message 521 indicating that the automatic F/W update will be affected, an OK button 522 for instructing the process to continue, and an NG button 523 for instructing the process to be stopped. The impact notification screen 520 is closed by pressing the OK button 522 or the NG button 523.

As shown in Figures 14 and 15, after processing S134, the automatic update unit 25d determines whether the OK button has been pressed on the impact notification screen (S135).

If the automatic update unit 25d determines in S135 that the OK button has not been pressed on the impact notification screen, it determines whether the NG button has been pressed on the impact notification screen (S136).

If the automatic update unit 25d determines in S136 that the NG button has not been pressed on the impact notification screen, it executes the process of S135.

When the package management unit 25b determines in S135 that the OK button was pressed on the impact notification screen, it deletes from the memory unit 24 the F/W package that was selected in the list 511 at the time the Delete button 513 was pressed (S137).

After processing S137, the automatic update unit 25d changes the value of the "Enable/Disable" item of the automatic F/W update plan that targets the F/W package deleted in S137 as a target for automatic F/W update to "Warning" indicating that the automatic F/W update plan is not appropriate (S138).

Next, the automatic update unit 25d sets the value of the "Status" item in task information 24n to "Cancelled" for all automatic F/W update tasks for which the value of the "Status" item in task information 24n is "Pending" among the automatic F/W update tasks related to the automatic F/W update plan that targets the F/W package deleted in S137, and executes the process of S130.

When the package management unit 25b determines in S136 that the NG button has been pressed on the impact notification screen, or determines in S131 that the Delete button 513 has not been pressed, it determines whether the Publish button 514 has been pressed (S140).

When the package management unit 25b determines in S140 that the Publish button 514 has been pressed, it determines whether the requester has administrator or higher authority in the same manner as in S125 (S141).

If the package management unit 25b determines in S141 that the requester does not have administrator or higher authority, it displays on the target user terminal a message indicating that the requester does not have the authority to publish the F/W package (S142), and executes the process of S124.

If the package management unit 25b determines in S141 that the requester has administrator or higher authority, it publishes the F/W package that was selected in the list 511 at the time the publish button 514 was pressed (S143).

After processing S143, the package management unit 25b executes processing S130.

If the package management unit 25b determines in S140 that the Publish button 514 has not been pressed, it determines whether the Unpublish button 515 has been pressed (S144).

When the automatic update unit 25d determines in S144 that the Unpublish button 515 has been pressed, it determines whether the requester has administrator or higher authority in the same manner as in the processing of S125 (S145).

If the package management unit 25b determines in S145 that the requester does not have administrator or higher authority, it displays on the target user terminal a message indicating that the requester does not have authority to unpublish the F/W package (S146), and executes the process of S124.

If the package management unit 25b determines in S145 that the requester has administrator or higher authority, it displays an impact notification screen on the target user terminal, similar to the processing in S134 (S147).

After processing S147, the automatic update unit 25d determines whether the OK button was pressed on the impact notification screen (S148).

If the automatic update unit 25d determines in S148 that the OK button has not been pressed on the impact notification screen, it determines whether the NG button has been pressed on the impact notification screen (S149).

If the automatic update unit 25d determines in S149 that the NG button has not been pressed on the impact notification screen, it executes the process of S148.

When the package management unit 25b determines in S148 that the OK button was pressed on the impact notification screen, it unpublishes the F/W package that was selected in the list 511 at the time the Unpublish button 515 was pressed (S150).

After processing S150, the automatic update unit 25d changes the value of the "Enable/Disable" item of the automatic F/W update plan that targets the F/W package unpublished in S150 as the target for automatic F/W update to "Warning" (S151).

Next, the automatic update unit 25d sets the value of the "Status" item in task information 24n to "Cancelled" for all automatic F/W update tasks for which the value of the "Status" item in task information 24n is "Pending" among the automatic F/W update tasks related to the automatic F/W update plan that targets the F/W package unpublished in S150, and executes the process of S130.

When the package management unit 25b determines in S144 that the Unpublish button 515 has not been pressed, or determines in S149 that the NG button has been pressed on the impact notification screen, it determines whether the package management screen 510 has been closed (S153).

If the package management unit 25b determines in S153 that the package management screen 510 has not been closed, it executes the process of S124.

When the package management unit 25b determines in S153 that the package management screen 510 has been closed, it ends the operations shown in Figures 14 and 15.

Next, we will explain the operation of the device management system 20 when performing a manual F/W update.

Figure 18 is a flowchart of the operation of the device management system 20 when performing a manual F/W update.

A user who is logged in to the device management system 20 can send a request for setting a manual F/W update (hereinafter referred to as a "manual F/W update setting request") to the device management system 20 via a user terminal (hereinafter referred to as the "target user terminal" in the explanation of FIG. 18). When the manual update unit 25c of the device management system 20 receives the manual F/W update setting request, it executes the operation shown in FIG. 18.

As shown in FIG. 18, the manual update unit 25c determines whether the user who sent the manual F/W update setting request (hereinafter referred to as the "requester" in the explanation of FIG. 18) has the authority of a service person or higher in the same manner as in the processing of S121 (S161).

When the manual update unit 25c determines in S161 that the requester does not have the authority of a service person or higher, it displays on the target user terminal a message indicating that the requester does not have the authority to set up a manual F/W update (S162), and ends the operation shown in FIG. 18.

When the manual update unit 25c determines in S161 that the requester has the authority of a service person or higher, it transmits data of a manual F/W update setting screen (hereinafter referred to as the "manual F/W update setting screen") to the target user terminal, thereby causing the target user terminal to display the manual F/W update setting screen (S163).

Figure 19 shows an example of a manual F/W update setting screen 530 displayed on a user terminal during the operation shown in Figure 18.

As shown in FIG. 19, the manual F/W update setting screen 530 includes a drop-down list 531 for selecting an image forming device to be the target of the manual F/W update, a drop-down list 532 for selecting an F/W package to be the target of the manual F/W update, drop-down lists 533a, 533b, 533c, 533d, and 533e for selecting the "year," "month," "day," "hour," and "minute" of the scheduled time of execution of the manual F/W update, a cancel button 534 for canceling the settings in the manual F/W update setting screen 530, and an execute button 535 for executing the settings in the manual F/W update setting screen 530. In the drop-down list 531, the image forming device is represented by a device ID. In the drop-down list 532, the F/W package is represented by a package ID. The manual F/W update setting screen 530 is a screen that is closed by pressing the cancel button 534 or the execute button 535.

As shown in FIG. 18, after processing S163, the manual update unit 25c determines whether the cancel button 534 has been pressed (S164).

When the manual update unit 25c determines in S164 that the cancel button 534 has been pressed, it ends the operation shown in FIG. 18.

If the manual update unit 25c determines in S164 that the cancel button 534 has not been pressed, it determines whether the execute button 535 has been pressed (S165).

If the manual update unit 25c determines in S165 that the execute button 535 has not been pressed, it executes the process of S164.

When the manual update unit 25c determines in S165 that the execute button 535 has been pressed, it creates in the memory unit 24 a manual F/W update task to be executed using the F/W package specified in the drop-down list 532 at the time the execute button 535 is pressed for the image forming device specified in the drop-down list 531 at the time the execute button 535 is pressed, by setting the scheduled execution time specified in the drop-down lists 533a, 533b, 533c, 533d, and 533e at the time the execute button 535 is pressed (S166).

After the process of S166, the manual update unit 25c adds information about the manual F/W update task generated in S166 to the task information 24n (S167). Here, when the manual update unit 25c adds information to the task information 24n in S167, it enters "on hold" as the value of the "Status" item in the information to be added.

After processing S167, the manual update unit 25c ends the operation shown in FIG. 18.

Next, we will explain the operation of the device management system 20 when the automatic F/W update group settings are edited.

Figure 20 is a flowchart of part of the operation of the device management system 20 when the automatic F/W update group settings are edited. Figure 21 is a continuation of the flowchart shown in Figure 20.

A user who is logged in to the device management system 20 can send a request to start editing the automatic F/W update group settings of a specific group indicated in the group information 24e (hereinafter referred to as a "group setting editing start request") to the device management system 20 via a user terminal (hereinafter referred to as the "target user terminal" in the explanations of Figures 20 and 21 and in the explanation of Figure 23 described below). When the control unit 25 of the device management system 20 receives the group setting editing start request, it executes the operations shown in Figures 20 and 21.

As shown in Figures 20 and 21, the automatic update unit 25d determines whether the user who sent the request to start editing group settings (hereinafter referred to as the "requester" in the explanations of Figures 20 and 21 and the explanation of Figure 23 described below) has the authority of a service person or higher in the same manner as the processing of S121 (S181).

When the automatic update unit 25d determines in S181 that the requester has authority of a service person or higher, it determines whether the group that is the subject of the group setting editing start request is within the scope of the requester's authority (S182).

When the automatic update unit 25d determines in S181 that the requester does not have the authority of a service person or higher, or determines in S182 that the group that is the target of the group setting editing start request is not within the scope of the requester's authority, it displays on the target user terminal (S183) that the requester does not have the authority to edit the automatic F/W update group settings for the group that is the target of the group setting editing start request, and ends the operation shown in Figures 20 and 21.

When the automatic update unit 25d determines in S182 that the group that is the target of the group setting editing start request is within the scope of the requester's authority, it causes the target user terminal to display the group setting editing screen by transmitting data of a screen for editing the automatic F/W update group settings (hereinafter referred to as the "group setting editing screen") to the target user terminal (S184).

Figure 22 shows an example of a group setting editing screen 600 displayed on a user terminal during the operations shown in Figures 20 and 21.

As shown in FIG. 22, the group setting editing screen 600 includes an area 610 for editing the "Automatic F/W update setting" item in the automatic F/W update group setting, an area 630 for editing the "Execution time zone setting" item in the automatic F/W update group setting, an area 660 for editing the "Pre-print setting" item in the automatic F/W update group setting, a cancel button 671 for canceling editing on the group setting editing screen 600, and a save button 672 for saving the edited content on the group setting editing screen 600.

Area 610 includes radio button 611 for specifying "ON" as the value of the "Automatic F/W update setting" item in the automatic F/W update group setting, radio button 612 for specifying "OFF" as the value of the "Automatic F/W update setting" item in the automatic F/W update group setting, radio button 613 for specifying "Select" as the value of the "Automatic F/W update setting" item in the automatic F/W update group setting, and area 620 which is operable only when radio button 613 is selected. Only one of radio buttons 611 to 613 is always selected.

Area 620 includes area 621 for editing the "Plan Allowed/Prohibited" item in the automatic F/W update group settings, area 622 for editing the "Notification Settings" item in the automatic F/W update group settings, and area 623 for running a F/W update test.

The area 621 includes a list 621a showing a list of automatic F/W update plans set in the "Plan Allowed/Prohibited" item in the automatic F/W update group setting, a radio button 621b for specifying "Allowed" indicating that an automatic F/W update based on the automatic F/W update plan shown in the list 621a is permitted, and a radio button 621c for specifying "Prohibited" indicating that an automatic F/W update based on the automatic F/W update plan shown in the list 621a is not permitted. In the list 621a, the automatic F/W update plans are represented by plan IDs. The automatic update unit 25d shows in the list 621a the automatic F/W update plans for which the target group of the group setting editing screen 600 is the target of the automatic F/W update, regardless of whether the automatic F/W update plan is in the enabled, disabled, or warning state. The radio button 621b and the radio button 621c are arranged for each automatic F/W update plan shown in the list 621a. Only one of radio buttons 621b and 621c will always be selected for each automatic F/W update plan.

Area 622 includes a list 622a showing a list of users that can be set in the "Notification Settings" item in the automatic F/W update group settings, a drop-down list 622b for selecting a user to add to list 622a, an add button 622c for adding a user selected in drop-down list 622b to list 622a, and a delete button 622d for deleting a user selected in list 622a from list 622a. In list 622a and drop-down list 622b, users are represented by user IDs. The automatic update unit 25d can display only users included in address information 24d in drop-down list 622b.

The area 623 includes a drop-down list 623a for selecting an automatic F/W update plan for performing a F/W update test, a drop-down list 623b for selecting an image forming device for which the F/W update test is to be performed, and a test execution button 623c for performing a F/W update test. In the drop-down list 623a, the automatic F/W update plan is represented by a plan ID. In the drop-down list 623b, the image forming device is represented by a device ID. The automatic update unit 25d can display in the drop-down list 623a only the automatic F/W update plans for which the target group of the group setting editing screen 600 is the target of the automatic F/W update, regardless of whether the automatic F/W update plan is in the enabled, disabled, or warning state. The automatic update unit 25d can display in the drop-down list 623b only the image forming devices that are the target model of the target F/Package of the automatic F/W update plan selected in the drop-down list 623a among the image forming devices that belong to the target group of the group setting editing screen 600, based on the device information 24f.

Area 630 includes area 640 for editing the "Day setting" item of the "Execution time zone setting" item in the automatic F/W update group setting, and area 650 for editing the "Time zone setting" item of the "Execution time zone setting" item in the automatic F/W update group setting.

Area 640 includes a radio button 641 for specifying "Everyday" as the value of the "Day setting" item of the "Execution time zone setting" item in the automatic F/W update group setting, a radio button 642 for specifying "Day of the week" as the value of the "Day setting" item of the "Execution time zone setting" item in the automatic F/W update group setting, and an area 643 that is operable only when radio button 642 is selected. Only one of radio buttons 641 and 642 is always selected. Area 643 includes check boxes 643a, 643b, 643c, 643d, 643e, 643f, and 643g for specifying "Monday", "Tuesday", "Wednesday", "Thursday", "Friday", "Saturday", and "Sunday" as the value of the "Day setting" item of the "Execution time zone setting" item in the automatic F/W update group setting.

Area 650 includes a drop-down list 651 for specifying the start of the time period, which is the value of the "Time Period Setting" item in the "Execution Time Period Setting" item in the automatic F/W update group settings, and a drop-down list 652 for specifying the end of the time period, which is the value of the "Time Period Setting" item in the "Execution Time Period Setting" item in the automatic F/W update group settings.

Area 660 includes area 661 for editing the "Pre-print on/off" item of the "Pre-print settings" item in the automatic F/W update group settings, and area 662 for editing the "Language settings" item of the "Pre-print settings" item in the automatic F/W update group settings.

Area 661 includes radio buttons 661a and 661b for specifying "ON" or "OFF" as the value of the "Pre-printing" item in the "Pre-printing settings" item in the automatic F/W update group settings. Only one of radio buttons 661a and 661b is always selected.

Area 662 includes a drop-down list 662a for specifying a value for the "Language setting" item of the "Pre-print setting" item in the automatic F/W update group setting. The automatic update unit 25d can display in the drop-down list 662a the "Language set in the delegated group to which the target group of the group setting editing screen 600 belongs" indicating the language set in the language setting 24g for the delegated group to which the target group belongs, and several specific languages.

As shown in Figures 20 and 21, after processing S184, the automatic update unit 25d determines whether the test execution button 623c has been pressed (S185).

When the automatic update unit 25d determines in S185 that the test execution button 623c has been pressed, it starts to execute a test F/W update for the image forming device selected in the drop-down list 623b at the time the test execution button 623c was pressed, using the target F/W package of the automatic F/W update plan selected in the drop-down list 623a at the time the test execution button 623c was pressed (S186).

When the automatic update unit 25d determines in S185 that the test execution button 623c has not been pressed, or when the processing of S186 ends, it determines whether the cancel button 671 has been pressed (S187).

If the automatic update unit 25d determines in S187 that the cancel button 671 has not been pressed, it determines whether the save button 672 has been pressed (S188).

If the automatic update unit 25d determines in S188 that the save button 672 has not been pressed, it executes the process of S185.

When the automatic update unit 25d determines in S188 that the Save button 672 has been pressed, it saves the content edited on the group setting editing screen 600 at the time the Save button 672 was pressed in the storage unit 24 as an automatic F/W update group setting (S189). Here, if the radio button 613 is not selected on the group setting editing screen 600 at the time the Save button 672 is pressed, the automatic update unit 25d does not store the values of the "Plan permitted/prohibited" item and the "Notification setting" item in the automatic F/W update group setting saved in S189.

After processing S189, if the automatic F/W update group setting saved in S189 is not a new one, i.e., an existing automatic F/W update group setting has been edited, the automatic update unit 25d determines whether the value of the "Execution time zone setting" item or the "Pre-print setting" item in the automatic F/W update group setting has been changed by saving in S189 (S190).

When the automatic update unit 25d determines in S190 that the values of the "Execution time zone setting" item and the "Pre-print setting" item in the automatic F/W update group setting have not been changed by the saving in S189, it determines whether the value of the "Automatic F/W update setting" item in the automatic F/W update group setting saved in S189 is "OFF" (S191).

When the automatic update unit 25d determines in S190 that the value of the "Execution time zone setting" item or the "Pre-print setting" item in the automatic F/W update group setting has been changed by the saving in S189, or determines in S191 that the value of the "Automatic F/W update setting" item in the automatic F/W update group setting saved in S189 is "OFF", it sets the value of the "Status" item in task information 24n to "Cancel" for all automatic F/W update tasks for which the value of the "Status" item in task information 24n is "Pending" among the automatic F/W update tasks targeted at the target group on the group setting editing screen 600 (S192).

When the automatic update unit 25d determines in S191 that the value of the "Automatic F/W Update Setting" item in the automatic F/W update group setting saved in S189 is not "OFF", it determines whether or not there is an automatic F/W update plan in which the value of the "Automatic F/W Update Setting" item in the automatic F/W update group setting saved in S189 is "Selected" and the value of the "Plan Allowed/Prohibited" item is "Prohibited" (S193).

When the automatic update unit 25d determines in S193 that there is an automatic F/W update plan in which the value of the "Automatic F/W update setting" item is "Selected" and the value of the "Plan permitted/prohibited" item is "Prohibited" in the automatic F/W update group setting saved in S189, the automatic update unit 25d sets the value of the "Status" item in task information 24n to "Cancel" for all automatic F/W update tasks in which the value of the "Status" item in task information 24n is "Pending" among the automatic F/W update tasks targeted at the target group on the group setting editing screen 600 and which are related to an automatic F/W update plan in which the value of the "Plan permitted/prohibited" item is "Prohibited" in the automatic F/W update group setting saved in S189 (S194).

When the automatic update unit 25d determines in S187 that the cancel button 671 has been pressed, or determines in S193 that there is no automatic F/W update plan in which the value of the "Automatic F/W Update Setting" item is "Selected" and the value of the "Plan Allowed/Prohibited" item is "Prohibited" in the automatic F/W update group setting saved in S189, or when the processing of S192 or S194 ends, it terminates the display of the group setting editing screen 600 on the target user terminal (S195) and terminates the operation shown in Figures 20 and 21.

The operations shown in Figures 20 and 21 are the operations of the device management system 20 when editing the automatic F/W update group settings of one specific group. However, the device management system 20 can similarly edit the automatic F/W update group settings of multiple groups simultaneously.

Figure 23 is a flowchart of the operation of the device management system 20 when performing a F/W update test.

When the automatic update unit 25d executes the process of S186 shown in Figs. 20 and 21, it causes a test progress screen showing the progress of the F/W update test to be displayed on the target user terminal as shown in Fig. 23 (S201). Here, the automatic update unit 25d thereafter displays the progress of the F/W update test on the test progress screen at appropriate times, such as when a change occurs in the progress. Note that the test progress screen can be closed by the user of the target user terminal.

After the processing of S201, the automatic update unit 25d generates a test F/W update task in the storage unit 24 to be executed using the target F/W package of the automatic F/W update plan selected in the drop-down list 623a at the time when the test execution button 623c was pressed for the image forming device selected in the drop-down list 623b at the time when the test execution button 623c was pressed (S202). Here, the test F/W update task is a F/W update task that is executed immediately when a F/W update can be executed in the target image forming device. Therefore, the automatic update unit 25d does not set a specific scheduled execution time for the test F/W update task.

After the process of S202, the automatic update unit 25d adds information about the test F/W update task generated in S202 to the task information 24n (S203). Here, when the automatic update unit 25d adds information to the task information 24n in S203, it enters "on hold" as the value of the "Status" item in the added information.

After the process of S203, the automatic update unit 25d judges whether the execution of the test F/W update task generated in S202 has ended (S204) until it is determined that the execution of the test F/W update task generated in S202 has ended. Here, the automatic update unit 25d judges that the execution of the test F/W update task generated in S202 has ended when the value of the "Status" item of the task information 24n for the test F/W update task generated in S202 becomes "Cancelled", "Success", or "Failure".

When the automatic update unit 25d determines in S204 that the execution of the test F/W update task generated in S202 has ended, it determines whether the test progress status screen has been closed (S205).

If the automatic update unit 25d determines in S205 that the test progress status screen has not been closed, it displays the results of the update performed by executing the test F/W update task generated in S202 on the test progress status screen (S206).

When the automatic update unit 25d determines in S205 that the test progress status screen is closed or when the processing of S206 ends, it notifies the requester's email address stored in the address information 24d of the results of the update resulting from the execution of the test F/W update task generated in S202 (S207), and ends the operation shown in FIG. 23.

After checking the results displayed on the test progress screen in S206 or the results notified in S207, the user can, for example, if the results displayed on the test progress screen in S206 or the results notified in S207 show that the update is successful, set the value of the "Plan permitted/prohibited" item for the automatic F/W update plan being tested to "permitted" via the group settings editing screen; if the results displayed on the test progress screen in S206 or the results notified in S207 show that the update is unsuccessful, set the value of the "Plan permitted/prohibited" item for the automatic F/W update plan being tested to "prohibited" via the group settings editing screen.

Next, we will explain the operation of the device management system 20 when the automatic F/W update plan is edited.

Figure 24 is a flowchart of part of the operation of the device management system 20 when an automatic F/W update plan is edited. Figure 25 is a continuation of the flowchart shown in Figure 24. Figure 26 is a continuation of the flowchart shown in Figure 25.

A user who is logged in to the device management system 20 can send a request to start editing an automatic F/W update plan (hereinafter referred to as a "plan editing start request") to the device management system 20 via a user terminal (hereinafter referred to as the "target user terminal" in the explanations of Figures 24 to 26). When the control unit 25 of the device management system 20 receives the plan editing start request, it executes the operations shown in Figures 24 to 26.

As shown in Figures 24 to 26, the automatic update unit 25d determines whether the user who sent the plan editing start request (hereinafter referred to as the "requester" in the explanations of Figures 24 to 26) has administrator or higher authority (S221), in the same manner as the processing of S125.

When the automatic update unit 25d determines in S221 that the requester does not have administrator or higher authority, it displays on the target user terminal a message indicating that the requester does not have authority to edit the automatic F/W update plan (S222), and ends the operations shown in Figures 24 to 26.

When the automatic update unit 25d determines in S221 that the requester has administrator or higher authority, it causes the target user terminal to display the plan editing screen by transmitting data of a screen for editing the automatic F/W update plan (hereinafter referred to as the "plan editing screen") to the target user terminal (S223).

Figure 27 shows an example of a plan editing screen 700 displayed on a user terminal during the operations shown in Figures 24 to 26.

As shown in FIG. 27, the plan editing screen 700 includes an area 710 for editing the "Target F/W package" item in the automatic F/W update plan, an area 720 for editing the "Target group" item in the automatic F/W update plan, an area 760 for editing the "Automatic F/W update mode" item in the automatic F/W update plan, an area 770 for editing the "Enable/Disable" item in the automatic F/W update plan, a cancel button 781 for canceling editing on the plan editing screen 700, and a save button 782 for saving the edited content on the plan editing screen 700.

Area 710 includes a drop-down list 711 for selecting a F/W package to be set in the "Target F/W Package" item in the automatic F/W update plan. In the drop-down list 711, the F/W packages are represented by package IDs. The automatic update unit 25d can display in the drop-down list 711 only F/W packages uploaded to the device management system 20, i.e., F/W packages stored in the storage unit 24, that have been published and have a firmware release type of "official."

Area 720 includes radio button 721 for specifying "All Accessible" as the value of the "Target Group" item in the automatic F/W update plan, radio button 722 for specifying "Exclusively Managed" as the value of the "Target Group" item in the automatic F/W update plan, radio button 723 for specifying "Off" as the value of the "Target Group" item in the automatic F/W update plan, area 730 which is operable only when radio button 721 is selected, area 740 which is operable only when radio button 722 is selected, and area 750 which is operable only when radio button 723 is selected. Only one of radio buttons 721 to 723 is always selected.

Area 730 includes a drop-down list 731 for selecting a delegated group to be set in the "Target Group" field when "All Accessible" is specified in the "Target Group" field in the automatic F/W update plan. In the drop-down list 731, the delegated groups are represented by group IDs. The automatic update unit 25d can display only delegated groups within the scope of the requester's authority in the drop-down list 731 based on the group information 24e.

Area 740 includes a drop-down list 741 for selecting a delegated group to be set in the "Target Group" item when "Exclusively Managed" is specified in the "Target Group" item in the automatic F/W update plan. In the drop-down list 741, the delegated groups are represented by group IDs. The automatic update unit 25d can display only delegated groups within the scope of the requester's authority in the drop-down list 741 based on the group information 24e.

Area 750 includes list 751 showing a list of groups that can be set in the "Target Group" item when "Off" is specified in the "Target Group" item in the automatic F/W update plan, radio button 752 for specifying "Select", which indicates that a group shown in list 751 is selected, and radio button 753 for specifying "Not Select", which indicates that a group shown in list 751 is not selected. In list 751, groups are represented by group IDs. Automatic update unit 25d shows groups within the scope of the requester's authority in list 751 based on group information 24e. Radio buttons 752 and 753 are arranged for each group shown in list 751. Only one of radio buttons 752 and 753 is always selected for each group.

Area 760 includes radio button 761 for specifying "Update immediately" as the value of the "Automatic F/W update mode" item in the automatic F/W update plan, and radio button 762 for specifying "Update gradually" as the value of the "Automatic F/W update mode" item in the automatic F/W update plan. Only one of radio buttons 761-762 is always selected.

Area 770 includes radio button 771 for specifying "enable" as the value of the "enable/disable" item in the automatic F/W update plan, and radio button 772 for specifying "disable" as the value of the "enable/disable" item in the automatic F/W update plan. Only one of radio buttons 771-772 is always selected.

As shown in Figures 24 to 26, after processing S223, the automatic update unit 25d determines whether the cancel button 781 has been pressed (S224).

If the automatic update unit 25d determines in S224 that the cancel button 781 has not been pressed, it determines whether the save button 782 has been pressed (S225).

If the automatic update unit 25d determines in S225 that the save button 782 has not been pressed, it executes the process of S224.

When the automatic update unit 25d determines in S225 that the save button 782 has been pressed, it saves the contents that were being edited on the plan editing screen 700 at the time the save button 782 was pressed as an automatic F/W update plan in the memory unit 24 (S226).

After processing S226, the automatic update unit 25d identifies the target group for the automatic F/W update based on the information shown in the "Target Group" item in the automatic F/W update plan saved in S226 (S227).

After processing S227, the automatic update unit 25d determines whether the automatic F/W update plan saved in S226 is a newly created one (S228).

When the automatic update unit 25d determines in S228 that the automatic F/W update plan saved in S226 is a newly created one, it determines whether the value of the "enabled/disabled" item in the automatic F/W update plan saved in S226 is "enabled" (S229).

When the automatic update unit 25d determines in S229 that the value of the "Enable/Disable" item in the automatic F/W update plan saved in S226 is "Enable", it determines whether or not a group whose value of the "Automatic F/W Update Setting" item in the automatic F/W update group setting is "Selected" is present in the target group for the automatic F/W update identified in S227 (S230).

When the automatic update unit 25d determines in S230 that a group for which the value of the "Automatic F/W update setting" item in the automatic F/W update group settings is "Selected" is present among the target groups for the automatic F/W update identified in S227, the automatic update unit 25d notifies the email address stored in the address information 24d of the user indicated in the "Notification setting" item in the automatic F/W update group settings of the group for which the value of the "Automatic F/W update setting" item in the automatic F/W update group settings is "Selected" among the target groups for the automatic F/W update identified in S227 that the automatic F/W update plan saved in S226 has been newly created (S231). Therefore, the user who has received the notification in S231 can set the value of the "Plan Permitted/Prohibited" item for the automatic F/W update plan saved in S226 to "Permitted" via the group setting editing screen in the automatic F/W update group settings of the group for which the value of the "Automatic F/W Update Setting" item in the automatic F/W update group settings is "Selected" among the groups targeted for the automatic F/W update identified in S227. Note that when the automatic update unit 25d notifies the user's email address in S231, which is indicated in the "Notification Setting" item in the automatic F/W update group settings of the group for which the value of the "Automatic F/W Update Setting" item in the automatic F/W update group settings is "Selected", the automatic update unit 25d adds a link to the URL (Uniform Resource Locator) of the page of the group setting editing screen for this automatic F/W update group setting to this email.

If the automatic update unit 25d determines in S228 that the automatic F/W update plan saved in S226 is not a new one, i.e., that an existing automatic F/W update plan has been edited, it clears all flags 1 to 6 (S232).

Next, the automatic update unit 25d determines whether the value of the "Target F/W package" item in the automatic F/W update plan has been changed by saving in S226 (S233).

If the automatic update unit 25d determines in S233 that the value of the "Target F/W package" item in the automatic F/W update plan has been changed by saving in S226, it sets flag 1 (S234).

Next, the automatic update unit 25d determines whether or not a group whose "Automatic F/W Update Setting" item in the automatic F/W update group setting has a value of "Selected" is present among the target groups for the automatic F/W update identified in S227 (S235).

If the automatic update unit 25d determines in S235 that a group whose "Automatic F/W Update Setting" item in the automatic F/W update group setting has a value of "Selected" is present in the group that is the target of the automatic F/W update identified in S227, it sets flags 2 and 4 (S236).

The automatic update unit 25d determines in S233 that the value of the "Target F/W package" item in the automatic F/W update plan has not been changed by the saving in S226, determines in S235 that a group in which the value of the "Automatic F/W update setting" item in the automatic F/W update group setting is "Selected" does not exist in the target group of the automatic F/W update identified in S227, or, when the processing of S236 is completed, determines whether a new group has been added to the target group of the automatic F/W update by the saving in S226 (S237).

When the automatic update unit 25d determines in S237 that a new group has been added to the target group of the automatic F/W update by saving in S226, it determines whether or not there is a group whose value in the "Automatic F/W update setting" item in the automatic F/W update group setting is "Selected" among the groups newly added to the target group of the automatic F/W update by saving in S226 (S238).

When the automatic update unit 25d determines in S238 that a group whose "Automatic F/W Update Setting" item in the automatic F/W update group setting has a value of "Selected" among the groups newly added to the target groups for the automatic F/W update by saving in S226, the automatic update unit 25d sets flag 3 (S239).

The automatic update unit 25d determines in S237 that no new group has been added to the group targeted for the automatic F/W update by saving in S226, determines in S238 that no group whose value in the "Automatic F/W update setting" item in the automatic F/W update group setting is "Selected" is included in the group newly added to the group targeted for the automatic F/W update by saving in S226, or, upon completion of the processing in S239, determines whether the value in the "Automatic F/W update mode" item in the automatic F/W update plan has been changed by saving in S226 (S240).

When the automatic update unit 25d determines in S240 that the value of the "automatic F/W update mode" item in the automatic F/W update plan has been changed by saving in S226, it sets flag 1 (S241).

Next, the automatic update unit 25d determines whether or not a group whose "Automatic F/W Update Setting" item in the automatic F/W update group setting has a value of "Selected" is present among the target groups for the automatic F/W update identified in S227 (S242).

When the automatic update unit 25d determines in S242 that a group whose "Automatic F/W Update Setting" item in the automatic F/W update group setting has a value of "Selected" is present in the group that is the target of the automatic F/W update identified in S227, it sets flags 2 and 5 (S243).

The automatic update unit 25d determines in S240 that the value of the "Automatic F/W update mode" item in the automatic F/W update plan has not been changed by the saving in S226, determines in S242 that a group in which the value of the "Automatic F/W update setting" item in the automatic F/W update group setting is "Selected" does not exist in the target group for the automatic F/W update identified in S227, or, upon completion of the processing of S243, determines whether the value of the "Enable/Disable" item in the automatic F/W update plan saved in S226 has been changed to "Enable" by the saving in S226 (S244).

When the automatic update unit 25d determines in S244 that the value of the "enabled/disabled" item in the automatic F/W update plan saved in S226 has been changed to "enabled" by saving in S226, it determines whether or not a group whose value of the "automatic F/W update setting" item in the automatic F/W update group setting is "selected" exists among the target groups for the automatic F/W update identified in S227 (S245).

If the automatic update unit 25d determines in S245 that a group whose "Automatic F/W Update Setting" item in the automatic F/W update group setting has a value of "Selected" is present in the group that is the target of the automatic F/W update identified in S227, it sets flag 6 (S246).

When the automatic update unit 25d determines in S244 that the value of the "enabled/disabled" item in the automatic F/W update plan saved in S226 has not been changed to "enabled" by saving in S226, it determines whether the value of the "enabled/disabled" item in the automatic F/W update plan saved in S226 has been changed to "disabled" by saving in S226 (S247).

When the automatic update unit 25d determines in S247 that the value of the "enabled/disabled" item in the automatic F/W update plan saved in S226 has been changed to "disabled" by saving in S226, it sets flag 1 (S248).

Next, the automatic update unit 25d determines whether or not a group whose "Automatic F/W Update Setting" item in the automatic F/W update group setting has a value of "Selected" is present among the target groups for the automatic F/W update identified in S227 (S249).

If the automatic update unit 25d determines in S249 that a group whose "Automatic F/W Update Setting" item in the automatic F/W update group setting has a value of "Selected" is present in the group that is the target of the automatic F/W update identified in S227, it sets flag 2 (S250).

The automatic update unit 25d determines in S245 whether a group whose "Automatic F/W Update Setting" item value in the automatic F/W update group setting is "Selected" does not exist in the group identified in S227 as the target of the automatic F/W update, ends the processing of S246, determines in S247 that the value of the "Enabled/Disabled" item in the automatic F/W update plan saved in S226 has not been changed to "Disabled" by saving in S226, determines in S249 that a group whose "Automatic F/W Update Setting" item value in the automatic F/W update group setting is "Selected" does not exist in the group identified in S227 as the target of the automatic F/W update, or when the processing of S250 ends, determines whether flag 2 is set (S251).

When the automatic update unit 25d determines in S251 that flag 2 is set, it sets the value of the "Plan permitted/prohibited" item for the automatic F/W update plan saved in S226 to "prohibited" in the automatic F/W update group settings of the group for which the value of the "Automatic F/W update setting" item in the automatic F/W update group settings is "Selected" among the target groups for the automatic F/W update identified in S227 (S252).

When the automatic update unit 25d determines in S251 that flag 2 is not set, or when the processing of S252 is completed, it determines whether flag 1 is set (S253).

When the automatic update unit 25d determines in S253 that flag 1 is set, it sets the value of the "Status" item in task information 24n to "Cancelled" for all automatic F/W update tasks related to the automatic F/W update plan saved in S226 and for which the value of the "Status" item in task information 24n is "Pending" (S254).

When the automatic update unit 25d determines in S253 that flag 1 is not set, or when the processing of S254 is completed, it determines whether flag 3 is set (S255).

When the automatic update unit 25d determines in S255 that flag 3 is set, it notifies the email address stored in the address information 24d of the user indicated in the "Notification setting" item of the automatic F/W update group setting of the group for which the value of the "Automatic F/W update setting" item in the automatic F/W update group setting is "Selected" among the groups newly added to the target group of the automatic F/W update by saving in S226 that this group has been newly added to the automatic F/W update plan saved in S226 (S256). Therefore, the user who has received the notification in S256 can set the value of the "Plan permission/prohibition" item for the automatic F/W update plan saved in S226 to "permit" via the group setting editing screen in the automatic F/W update group setting of the group for which the value of the "Automatic F/W update setting" item in the automatic F/W update group setting is "Selected" among the target groups of the automatic F/W update identified in S227. When the automatic update unit 25d notifies the user's email address indicated in the "Notification settings" item of the automatic F/W update group settings of a group for which the value of the "Automatic F/W update settings" item in the automatic F/W update group settings is "Selected" by sending an email in S256, the automatic update unit 25d adds a link to the URL of the page of the group settings editing screen for this automatic F/W update group setting to this email.

When the automatic update unit 25d determines in S255 that flag 3 is not set, or when the processing of S256 is completed, it determines whether any of flags 4 to 6 are set (S257).

When the automatic update unit 25d determines in S257 that any one of flags 4 to 6 is set, it creates an e-mail addressed to the e-mail address stored in the address information 24d of the user indicated in the "Notification settings" item of the automatic F/W update group settings of the group for which the value of the "Automatic F/W update settings" item in the automatic F/W update group settings is "Selected" among the groups for which the automatic F/W update is targeted identified in S227 (S258). The automatic update unit 25d attaches to this e-mail a link to the URL of the page of the group settings editing screen of the automatic F/W update group settings of the group for which the value of the "Automatic F/W update settings" item in the automatic F/W update group settings is "Selected" among the groups for which the automatic F/W update is targeted identified in S227.

When processing of S258 is completed, the automatic update unit 25d determines whether flag 4 is set (S259).

When the automatic update unit 25d determines in S259 that flag 4 is set, it adds to the body of the email created in S258 a message indicating that the F/W package has been changed in the automatic F/W update plan saved in S226 (S260).

When the automatic update unit 25d determines in S259 that flag 4 is not set, or when the processing of S260 is completed, it determines whether flag 5 is set (S261).

When the automatic update unit 25d determines in S261 that flag 5 is set, it adds to the body of the email created in S258 a message indicating that the automatic F/W update mode has been changed in the automatic F/W update plan saved in S226 (S262).

When the automatic update unit 25d determines in S261 that flag 5 is not set, or when the processing of S262 is completed, it determines whether flag 6 is set (S263).

When the automatic update unit 25d determines in S263 that flag 6 is set, it adds to the body of the email created in S258 a message indicating that the automatic F/W update plan saved in S226 has been changed to "enabled" (S264).

When the automatic update unit 25d determines in S263 that flag 6 is not set, or when the processing of S264 ends, it sends the e-mail created in S258 (S265). Therefore, the user who receives the e-mail sent in S265 can, for example, set the value of the "Plan permitted/prohibited" item for the automatic F/W update plan saved in S226 to "permitted" via the group setting editing screen in the automatic F/W update group settings of the group for which the value of the "Automatic F/W update setting" item in the automatic F/W update group settings is "selected" among the groups targeted for the automatic F/W update identified in S227.

When the automatic update unit 25d determines in S224 that the cancel button 781 has been pressed, determines in S229 that the value of the "Enable/Disable" item in the automatic F/W update plan saved in S226 is not "Enable", i.e., is "Disabled", determines in S230 that a group in which the value of the "Automatic F/W Update Setting" item in the automatic F/W update group setting is "Selected" does not exist in the target group for the automatic F/W update identified in S227, ends the processing of S231, determines in S257 that none of flags 4 to 6 are set, or ends the processing of S265, the automatic update unit 25d ends the display of the plan editing screen 700 on the target user terminal (S266) and ends the operations shown in Figures 24 to 26.

Next, we will explain the operation of the device management system 20 when deleting an automatic F/W update plan.

Figure 28 is a flowchart of the operation of the device management system 20 when deleting an automatic F/W update plan.

A user who is logged in to the device management system 20 can send a request to delete an automatic F/W update plan (hereinafter referred to as a "plan deletion request") to the device management system 20 via a user terminal (hereinafter referred to as the "target user terminal" in the explanation of FIG. 28). When the device management system 20 receives the plan deletion request, it executes the operation shown in FIG. 28.

As shown in FIG. 28, the automatic update unit 25d determines whether the user who sent the plan deletion request (hereinafter referred to as the "requester" in the explanation of FIG. 28) has administrator or higher authority (S271) in the same manner as the processing of S125.

When the automatic update unit 25d determines in S271 that the requester does not have administrator or higher authority, it displays on the target user terminal a message indicating that the requester does not have authority to delete the automatic F/W update plan (S272), and ends the operation shown in FIG. 28.

If the automatic update unit 25d determines in S271 that the requester has administrator or higher authority, it deletes the automatic F/W update plan that is the subject of the plan deletion request from the storage unit 24 (S273).

Next, the automatic update unit 25d sets the value of the "Status" item in task information 24n to "Cancelled" for all automatic F/W update tasks for which the value of the "Status" item in task information 24n is "Pending" among the automatic F/W update tasks associated in task information 24n with the automatic F/W update plan deleted in S273 (S274), and ends the operation shown in FIG. 28.

Next, we will explain the operation of the device management system 20 when starting to execute an automatic F/W update.

Figure 29 is a flowchart of the operation of the device management system 20 when starting to execute an automatic F/W update.

When an automatic F/W update plan whose "enabled/disabled" field value is "enabled" is newly saved in the storage unit 24, the automatic update unit 25d executes the operation shown in FIG. 29 for this automatic F/W update plan (hereinafter referred to as the "target automatic F/W update plan" in the explanation of FIG. 29). Furthermore, even if the value of the "enabled/disabled" field of an existing automatic F/W update plan is changed to "enabled", the automatic update unit 25d executes the operation shown in FIG. 29 for this automatic F/W update plan. Note that, if the value of the "enabled/disabled" field of an existing automatic F/W update plan is changed to "disabled", the automatic update unit 25d ends the execution of the operation shown in FIG. 29 for this automatic F/W update plan.

As shown in FIG. 29, the automatic update unit 25d determines whether or not there is a group for which the value of the "Automatic F/W Update Setting" item in the automatic F/W update group setting is "ON" among the target groups of the automatic F/W update based on the target automatic F/W update plan (hereinafter simply referred to as the "target group" in the explanation of FIG. 29) (S276). Note that the automatic update unit 25d identifies the target group based on the information indicated in the "Target Group" item in the target automatic F/W update plan.

When the automatic update unit 25d determines in S276 that there is a group among the target groups for which the value of the "Automatic F/W Update Setting" item in the automatic F/W update group settings is "ON", it starts executing an automatic F/W update based on the target automatic F/W update plan for the target groups for which the value of the "Automatic F/W Update Setting" item in the automatic F/W update group settings is "ON" (S277).

The automatic update unit 25d determines in S276 that there is no group among the target groups for which the value of the "Automatic F/W update setting" item in the automatic F/W update group settings is "ON", or, upon completion of the processing of S277, determines whether there is a group among the target groups for which the value of the "Automatic F/W update setting" item in the automatic F/W update group settings is "Selected" and the value of the "Plan permitted/prohibited" item for the target automatic F/W update plan in the automatic F/W update group settings is "Permitted" (S278).

When the automatic update unit 25d determines in S278 that there is a group among the target groups for which the value of the "Automatic F/W update setting" item in the automatic F/W update group setting is "Selected" and the value of the "Plan permitted/prohibited" item for the target automatic F/W update plan in the automatic F/W update group setting is "Permitted", it starts execution of an automatic F/W update based on the target automatic F/W update plan for groups among the target groups for which the value of the "Automatic F/W update setting" item in the automatic F/W update group setting is "Selected" and the value of the "Plan permitted/prohibited" item for the target automatic F/W update plan in the automatic F/W update group setting is "Permitted" (S279).

The automatic update unit 25d determines in S278 that there is no group among the target groups for which the value of the "Automatic F/W update setting" item in the automatic F/W update group settings is "Selected" and the value of the "Plan permitted/prohibited" item for the target automatic F/W update plan in the automatic F/W update group settings is "Permitted", or, upon completion of the processing of S279, determines whether there is a group among the target groups for which the value of the "Automatic F/W update setting" item in the automatic F/W update group settings has been changed to "ON" (S280).

When the automatic update unit 25d determines in S280 that there is a group among the target groups for which the value of the "Automatic F/W Update Setting" item in the automatic F/W update group settings has been changed to "ON", it starts executing an automatic F/W update based on the target automatic F/W update plan for the group among the target groups for which the value of the "Automatic F/W Update Setting" item in the automatic F/W update group settings has been changed to "ON" (S281).

The automatic update unit 25d determines in S280 that there is no group among the target groups for which the value of the "Automatic F/W Update Setting" item in the automatic F/W update group settings has been changed to "ON", or, upon completion of the processing of S281, determines whether there is a group among the target groups for which the value of the "Automatic F/W Update Setting" item in the automatic F/W update group settings is "Selected" and the value of the "Plan Allowed/Prohibited" item for the target automatic F/W update plan in the automatic F/W update group settings has been changed to "Allowed" (S282).

When the automatic update unit 25d determines in S282 that there is a group among the target groups for which the value of the "Automatic F/W update setting" item in the automatic F/W update group setting is "Selected" and the value of the "Plan permitted/prohibited" item for the target automatic F/W update plan in the automatic F/W update group setting has been changed to "Permitted", it starts execution of an automatic F/W update based on the target automatic F/W update plan for groups among the target groups for which the value of the "Automatic F/W update setting" item in the automatic F/W update group setting is "Selected" and the value of the "Plan permitted/prohibited" item for the target automatic F/W update plan in the automatic F/W update group setting has been changed to "Permitted" (S283).

When the automatic update unit 25d determines in S282 that there is no group among the target group in which the value of the "Automatic F/W update setting" item in the automatic F/W update group setting is "Selected" and the value of the "Plan permitted/prohibited" item for the target automatic F/W update plan in the automatic F/W update group setting has been changed to "Permitted", or when the processing of S283 is completed, it determines whether a new group has been added to the target group (S284).

When the automatic update unit 25d determines in S284 that a new group has been added to the target group, it determines whether or not there is a new group in the target group for which the value of the "Automatic F/W Update Setting" item in the automatic F/W update group setting is "ON" (S285).

When the automatic update unit 25d determines in S285 that there is a new group among the target groups for which the value of the "Automatic F/W Update Setting" item in the automatic F/W update group settings is "ON", it starts executing an automatic F/W update based on the target automatic F/W update plan for the new group among the target groups for which the value of the "Automatic F/W Update Setting" item in the automatic F/W update group settings is "ON" (S286).

The automatic update unit 25d determines in S285 that there is no new group among the target groups in which the value of the "Automatic F/W update setting" item in the automatic F/W update group settings is "ON", or, upon completion of the processing of S286, determines whether there is a new group among the target groups in which the value of the "Automatic F/W update setting" item in the automatic F/W update group settings is "Selected" and the value of the "Plan permitted/prohibited" item for the target automatic F/W update plan in the automatic F/W update group settings is "Permitted" (S287).

When the automatic update unit 25d determines in S287 that there is a new group among the target groups in which the value of the "Automatic F/W update setting" item in the automatic F/W update group setting is "Selected" and the value of the "Plan permitted/prohibited" item for the target automatic F/W update plan in the automatic F/W update group setting is "Permitted", it starts execution of an automatic F/W update based on the target automatic F/W update plan for the new group among the target groups in which the value of the "Automatic F/W update setting" item in the automatic F/W update group setting is "Selected" and the value of the "Plan permitted/prohibited" item for the target automatic F/W update plan in the automatic F/W update group setting is "Permitted" (S288).

When the automatic update unit 25d determines in S284 that no new group has been added to the target group, or determines in S287 that there is no new group in the target group in which the value of the "Automatic F/W update setting" item in the automatic F/W update group setting is "Selected" and the value of the "Plan permitted/prohibited" item for the target automatic F/W update plan in the automatic F/W update group setting is "Permitted," the automatic update unit 25d executes the process of S280.

Next, we will explain the operation of the device management system 20 when performing an automatic F/W update.

Figure 30 is a flowchart of part of the operation of the device management system 20 when performing an automatic F/W update. Figure 31 is a continuation of the flowchart shown in Figure 30.

The automatic update unit 25d executes the operations shown in Figs. 30 and 31 for each combination of a group and an automatic F/W update plan. The automatic update unit 25d terminates the operations shown in Figs. 30 and 31 when the value of the "Automatic F/W Update Setting" item in the automatic F/W update group setting of the target group of the operations shown in Figs. 30 and 31 (hereinafter, simply referred to as the "target group" in the explanation of Figs. 30 and 31) is changed to "OFF". The automatic update unit 25d also terminates the operations shown in Figs. 30 and 31 when the value of the "Automatic F/W Update Setting" item in the automatic F/W update group setting of the target group is "Selected" and the value of the "Plan Allowed/Prohibited" item for the target automatic F/W update plan of the operations shown in Figs. 30 and 31 (hereinafter, simply referred to as the "target automatic F/W update plan" in the explanation of Figs. 30 and 31) in this automatic F/W update group setting is changed to "Prohibited". The automatic update unit 25d also ends the operations shown in Figures 30 and 31 if the value of the "enabled/disabled" item in the target automatic F/W update plan is changed to "disabled."

As shown in Figures 30 and 31, the automatic update unit 25d determines the value of the "automatic F/W update mode" item of the target automatic F/W update plan (S291).

When the automatic update unit 25d determines in S291 that the value of the "Automatic F/W update mode" item of the target automatic F/W update plan is "Gradual update," it extracts, from among all image forming devices belonging to the target group, image forming devices for which F/W updates using the device management system 20 are permitted (S292). Here, the automatic update unit 25d determines the image forming devices belonging to the target group based on the device information 24f.

After processing S292, the automatic update unit 25d extracts, from among all image forming devices extracted in S292, image forming devices in which the release type of the installed firmware is "official" (S293).

Next, the automatic update unit 25d extracts, from among all the image forming devices extracted in S293, image forming devices in which the F/W version of the installed firmware is older than the firmware in the F/W package set in the "Target F/W package" item in the target automatic F/W update plan (hereinafter, simply referred to as "target firmware" in the explanation of Figures 30 and 31) (S294).

Next, the automatic update unit 25d generates an automatic F/W update task based on the target automatic F/W update plan in the storage unit 24, and sets the scheduled execution time of the automatic F/W update task so that the F/W update is executed over a period of four weeks as shown in FIG. 8 for all image forming devices extracted in S294 (S295). Here, the automatic update unit 25d sets the scheduled execution time of the automatic F/W update task within the time period indicated in the "Execution time period setting" item in the automatic F/W update group setting for the target group.

After the processing of S295, the automatic update unit 25d adds information about the automatic F/W update task generated in S295 to the task information 24n (S296). Here, when the automatic update unit 25d adds information to the task information 24n in S296, it enters "on hold" as the value of the "Status" item in the information to be added.

After processing S296, the automatic update unit 25d determines whether four weeks have passed since the start of the previous processing S295 (S297).

If the automatic update unit 25d determines in S297 that four weeks have not passed since the start of the previous process of S295, it determines whether any of the automatic F/W update tasks generated in the previous process of S295 has been canceled due to a specific cause (S298). The "cancellation due to a specific cause" in S298 includes cancellation due to a change in the value of the "execution time zone setting" item or the "pre-print setting" item in the automatic F/W update group setting (YES in S190 and S192), cancellation due to a change in the target F/W package in the automatic F/W update plan (YES in S233 and S254), and cancellation due to a change in the automatic F/W update mode in the automatic F/W update plan (YES in S240 and S254).

When the automatic update unit 25d determines in S298 that any of the automatic F/W update tasks generated in the immediately preceding S295 has been canceled due to a specific cause, it determines whether the cancellation determined to have occurred in S298 is due to a change in the automatic F/W update mode (S299).

When the automatic update unit 25d determines in S299 that the cancellation determined to have occurred in S298 is due to a change in the automatic F/W update mode, it executes the process of S291.

When the automatic update unit 25d determines in S299 that the cancellation determined to have occurred in S298 is not a cancellation due to a change in the automatic F/W update mode, it executes the process of S292.

If the automatic update unit 25d determines in S298 that none of the automatic F/W update tasks generated in the immediately preceding S295 has been canceled due to a specific cause, it executes the process of S297.

When the automatic update unit 25d determines in S291 that the value of the "Automatic F/W Update Mode" item of the target automatic F/W update plan is "Update Immediately" or determines in S297 that four weeks have passed since the start of the previous process of S295, it extracts, from all image forming devices belonging to the target group, image forming devices for which F/W updates using the device management system 20 are permitted (S300). Here, the automatic update unit 25d determines the image forming devices belonging to the target group based on the device information 24f.

After processing S300, the automatic update unit 25d extracts, from among all image forming devices extracted in S300, image forming devices in which the release type of the installed firmware is "official" (S301).

Next, the automatic update unit 25d extracts, from among all image forming devices extracted in S301, image forming devices in which the F/W version of the installed firmware is older than the target firmware (S302).

Next, the automatic update unit 25d generates an automatic F/W update task based on the target automatic F/W update plan on the storage unit 24 by setting the scheduled execution time of this automatic F/W update task so that the F/W update is executed over a period of one week for all image forming devices extracted in S302 (S303).

After the process of S303, the automatic update unit 25d adds information about the automatic F/W update task generated in S303 to the task information 24n (S304). Here, when the automatic update unit 25d adds information to the task information 24n in S304, it enters "on hold" as the value of the "Status" item in the information to be added.

After processing S304, the automatic update unit 25d determines whether one week has passed since the start of the previous processing S303 (S305).

If the automatic update unit 25d determines in S305 that one week has not passed since the start of the processing in the immediately preceding S303, it determines whether or not any of the automatic F/W update tasks generated in the immediately preceding S303 was canceled due to a specific cause (S306). The "cancellation due to a specific cause" in S306 is the same as the "cancellation due to a specific cause" in S298.

When the automatic update unit 25d determines in S306 that any of the automatic F/W update tasks generated in the immediately preceding S303 has been canceled due to a specific cause, it determines whether the cancellation determined to have occurred in S306 is due to a change in the automatic F/W update mode (S307).

When the automatic update unit 25d determines in S307 that the cancellation determined to have occurred in S306 is due to a change in the automatic F/W update mode, it executes the process of S291.

When the automatic update unit 25d determines in S307 that the cancellation determined to have occurred in S306 is not a cancellation due to a change in the automatic F/W update mode, it executes the process of S300.

If the automatic update unit 25d determines in S306 that none of the automatic F/W update tasks generated in the immediately preceding S303 has been canceled due to a specific cause, it executes the process of S305.

When the automatic update unit 25d determines in S305 that one week has passed since the start of the previous process of S303, it executes the process of S300.

As described in Figures 30 and 31, in the case of "Update Immediately," the length of one cycle for executing the generated automatic F/W update tasks for all image forming devices in the target group is always one week from the first cycle. In the case of "Update Gradually," the length of one cycle is four weeks for the first cycle, but is always one week from the second cycle onwards.

Next, we will explain the operation of the device management system 20 when managing automatic F/W update tasks.

Figure 32 is a flowchart of the operation of the device management system 20 when managing an automatic F/W update task.

A user who is logged in to the device management system 20 can send a request to display a screen for managing automatic F/W update tasks (hereinafter referred to as a "task management screen") (hereinafter referred to as a "task management screen display request") to the device management system 20 via a user terminal (hereinafter referred to as the "target user terminal" in the explanation of FIG. 32). When the automatic update unit 25d of the device management system 20 receives the task management screen display request, it executes the operation shown in FIG. 32.

As shown in FIG. 32, the automatic update unit 25d displays the task management screen on the target user terminal by transmitting data of the task management screen to the target user terminal (S311).

Figure 33 shows an example of a task management screen 810 displayed on a user terminal during the operation shown in Figure 32.

As shown in FIG. 33, the task management screen 810 includes a list 811 showing a list of automatic F/W update tasks stored in the memory unit 24, text boxes 812a, 812b, 812c, and 812d in which text is entered to be used as a search filter for searching automatic F/W update tasks, and a "Cancel selected task" button 813 for canceling an automatic F/W update task selected in the list 811.

For each automatic F/W update task, list 811 shows, for example, the task ID of the automatic F/W update task, "Status" indicating the status of the automatic F/W update task, "Serial number" which is identification information of the image forming device that is the target of the automatic F/W update task and is information set by the manufacturer of the image forming device, "Asset number" which is identification information of the image forming device that is the target of the automatic F/W update task and is information set by the device user, and "Group" which indicates the group to which the image forming device that is the target of the automatic F/W update task belongs. In list 811, the group is represented by a group ID. The automatic update unit 25d can display in the list 811 only the automatic F/W update tasks stored in the memory unit 24 that are for image forming devices that belong to a group within the scope of the authority of the user who sent the request to display the task management screen (hereinafter referred to as the "requester" in the explanation of Figure 32), as determined based on the user ID of this user (hereinafter referred to as the "requester" in the explanation of Figure 32) and the authorization information 24c and device information 24f.

Text boxes 812a, 812b, 812c, and 812d are used to input text to be used for the search filters "Status," "Serial number," "Asset number," and "Group," respectively. When multiple search filters are specified, the automatic update unit 25d executes an AND search. When text is input into any of the text boxes 812a, 812b, 812c, and 812d, the automatic update unit 25d displays in the list 811 only the automatic F/W update tasks narrowed down by the search filter corresponding to the input text.

The "Cancel selected tasks" button 813 can be operated only when only an automatic F/W update task whose "Status" item value is "Pending" is selected in the list 811.

As shown in FIG. 32, when the processing of S311 is completed, the automatic update unit 25d determines whether the "Cancel selected task" button 813 has been pressed (S312).

If the automatic update unit 25d determines that the "Cancel selected task" button 813 has not been pressed, it determines whether the task management screen 810 has been closed (S313).

If the automatic update unit 25d determines in S313 that the task management screen 810 has not been closed, it executes the process of S312.

When the automatic update unit 25d determines in S312 that the "Cancel selected task" button 813 has been pressed, it determines whether the requester has the authority of a service person or higher based on the requester's user ID and the authorization information 24c in the same manner as in S121 (S314).

If the automatic update unit 25d determines in S314 that the requester does not have the authority of a service person or higher, it displays on the target user terminal a message indicating that the requester does not have the authority to cancel the automatic F/W update task (S315), and executes the process of S312.

When the automatic update unit 25d determines in S314 that the requester has the authority of a service person or higher, it sets the value of the "Status" item in task information 24n to "Cancel" for the automatic F/W update task that was selected in list 811 at the time the "Cancel selected task" button 813 was pressed (S316), and executes the process of S312.

When the automatic update unit 25d determines in S313 that the task management screen 810 has been closed, it ends the operation shown in FIG. 32.

Next, we will explain the operation of the device management system 20 when deleting an image forming device from the managed devices.

Figure 34 is a flowchart of the operation of the device management system 20 when deleting an image forming device from the managed devices.

A user who is logged in to the device management system 20 can send a request to delete an image forming device from the managed objects (hereinafter referred to as a "device deletion request") to the device management system 20 via a user terminal (hereinafter referred to as the "target user terminal" in the explanation of FIG. 34). When the device management system 20 receives the device deletion request, it executes the operation shown in FIG. 34.

As shown in FIG. 34, the device management unit 25f determines whether the user who sent the device deletion request (hereinafter referred to as the "requester" in the explanation of FIG. 34) has administrator or higher authority (S321) in the same manner as the processing of S125.

If the device management unit 25f determines in S321 that the requester does not have the authority of an administrator or higher, it displays on the target user terminal a message indicating that the requester does not have the authority to delete the image forming device from the managed devices (S322), and ends the operation shown in FIG. 34.

If the device management unit 25f determines in S321 that the requester has administrator or higher authority, it deletes the image forming device that is the target of the device deletion request from the device information 24f (S323).

Next, the automatic update unit 25d sets the value of the "Status" item in task information 24n to "Cancelled" for all automatic F/W update tasks for which the value of the "Status" item in task information 24n is "Pending" among the automatic F/W update tasks associated in task information 24n with the image forming device deleted from device information 24f in S323 (S324), and ends the operation shown in FIG. 34.

Next, we will explain the operation of the device management system 20 when deleting a group to which an image forming device belongs.

Figure 35 is a flowchart showing the operation of the device management system 20 when deleting a group to which an image forming device belongs.

A user who is logged in to the device management system 20 can send a request to delete a group to which an image forming device belongs (hereinafter referred to as a "group deletion request") to the device management system 20 via a user terminal (hereinafter referred to as the "target user terminal" in the explanation of FIG. 35). When the device management system 20 receives the group deletion request, it executes the operation shown in FIG. 35.

As shown in FIG. 35, the device management unit 25f determines whether the user who sent the group deletion request (hereinafter referred to as the "requester" in the explanation of FIG. 35) has administrator or higher authority in a manner similar to the processing of S125 (S325).

If the device management unit 25f determines in S325 that the requester does not have administrator or higher authority, it displays on the target user terminal a message indicating that the requester does not have authority to delete the group (S326), and ends the operation shown in FIG. 35.

If the device management unit 25f determines in S325 that the requester has administrator or higher authority, it deletes the group that is the subject of the group deletion request from the group information 24e (S327).

Next, the automatic update unit 25d sets the value of the "Status" item in task information 24n to "Cancelled" for all automatic F/W update tasks for which the value of the "Status" item in task information 24n is "Pending" among the automatic F/W update tasks associated in task information 24n with the image forming apparatuses belonging to the group deleted from group information 24e in S327 (S328), and ends the operation shown in FIG. 35.

Next, we will explain the operation of the device management system 20 when performing pre-printing on a non-intermediary image forming device.

Figure 36 is a flowchart of the operation of the device management system 20 when performing pre-printing on a non-intermediary image forming device.

The automatic update unit 25d executes the operations shown in FIG. 36 for each combination of a non-intermediary image forming device and an automatic F/W update task.

As shown in FIG. 36, the automatic update unit 25d determines whether the value of the "Status" item in task information 24n for the automatic F/W update task that is the target of the operation shown in FIG. 36 (hereinafter, simply referred to as the "target automatic F/W update task" in the explanation of FIG. 36) is "pending" (S331).

When the automatic update unit 25d determines in S331 that the value of the "Status" item in the task information 24n for the target automatic F/W update task is not "Pending," the operation shown in FIG. 36 ends.

When the automatic update unit 25d determines in S331 that the value of the "Status" item in the task information 24n for the target automatic F/W update task is "Pending", it determines whether it is 12 hours before the scheduled execution time of the target automatic F/W update task (S332).

If the automatic update unit 25d determines in S332 that it is not 12 hours before the scheduled execution time of the target automatic F/W update task, it executes the process of S331.

When the automatic update unit 25d determines in S332 that it is 12 hours before the scheduled execution time of the target automatic F/W update task, it determines whether the value of the "Pre-print setting" item in the automatic F/W update group setting of the group to which the target image forming device (hereinafter simply referred to as the "target image forming device" in the explanation of FIG. 36) belongs for the operation shown in FIG. 36 is "ON" (S333). Here, the automatic update unit 25d determines the group to which the target image forming device belongs based on the device information 24f.

When the automatic update unit 25d determines in S333 that the value of the "Pre-print setting" item in the automatic F/W update group settings for the group to which the target image forming device belongs is "ON", it determines whether or not F/W updates using the device management system 20 are permitted for the target image forming device based on the device information 24f (S334).

When the automatic update unit 25d determines in S334 that a F/W update using the device management system 20 is permitted for the target image forming device, it determines whether the release type of the firmware installed in the target image forming device is "official" based on the device information 24f (S335).

When the automatic update unit 25d determines in S335 that the release type of the firmware installed in the target image forming device is "official," it determines whether the F/W version of the firmware installed in the target image forming device is older than the F/W version set in the target automatic F/W update task based on the device information 24f (S336).

When the automatic update unit 25d determines in S336 that the F/W version of the firmware installed in the target image forming device is older than the F/W version set in the target automatic F/W update task, it generates print data for a notification that the execution of the F/W update in the automatic F/W update will start at the scheduled execution time of the target automatic F/W update task (S337). Here, the automatic update unit 25d uses the language indicated in the "Language setting" item of the automatic F/W update group setting of the group to which the target image forming device belongs as the language of the notification in S337.

After processing S337, the automatic update unit 25d transmits the print data generated in S337 to the target image forming device (S338).

The automatic update unit 25d will not resend the print data generated in S337 to the target image forming device even if the transmission in S338 fails or printing on the target image forming device based on the print data transmitted in S338 fails.

The automatic update unit 25d terminates the operation shown in FIG. 36 when it determines in S333 that the value of the "Pre-print Settings" item in the automatic F/W update group settings for the group to which the target image forming device belongs is not "ON", determines in S334 that F/W updates using the device management system 20 are not permitted for the target image forming device, determines in S335 that the acquired release type of the firmware installed in the target image forming device is not "official", determines in S336 that the F/W version of the firmware installed in the target image forming device is not older than the F/W version set in the target automatic F/W update task, or when the processing of S338 is completed.

Next, we will explain the operation of the device management system 20 when executing an automatic F/W update task on a non-intermediary image forming device.

Figure 37 is a flowchart of part of the operation of the device management system 20 when executing an automatic F/W update task on a non-intermediary image forming device. Figure 38 is a continuation of the flowchart shown in Figure 37.

The automatic update unit 25d of the device management system 20 executes the operations shown in Figures 37 and 38 for each automatic F/W update task for a non-intermediary image forming device among the automatic F/W update tasks stored in the memory unit 24.

As shown in Figures 37 and 38, the automatic update unit 25d determines whether the value of the "Status" item in task information 24n for the target automatic F/W update task of the operation shown in Figures 37 and 38 (hereinafter simply referred to as the "target automatic F/W update task" in the explanation of Figures 37 and 38) is "pending" (S341).

When the automatic update unit 25d determines in S341 that the value of the "Status" item in the task information 24n for the target automatic F/W update task is not "Pending," the automatic update unit 25d ends the operations shown in Figs. 37 and 38.

When the automatic update unit 25d determines in S341 that the value of the "Status" item in the task information 24n for the target automatic F/W update task is "Pending", it determines whether the scheduled execution time set for the target automatic F/W update task has arrived (S342).

If the automatic update unit 25d determines in S342 that the scheduled execution time set for the target automatic F/W update task has not yet arrived, it executes the process of S341.

When the automatic update unit 25d determines in S342 that the scheduled execution time set for the target automatic F/W update task has arrived, it sets the value of the "Status" item in the task information 24n for the target automatic F/W update task to "Waiting for execution" (S343).

Next, the automatic update unit 25d determines whether or not there is a preceding F/W update task for the target image forming device of the target automatic F/W update task (hereinafter simply referred to as the "target image forming device" in the explanation of Figures 37 and 38) until it determines that there is no F/W update task (hereinafter referred to as the "preceding F/W update task") for which the value of the "Status" item in task information 24n is set to "waiting for execution" or "executing" before the target automatic F/W update task and has not yet been set to "success" or "failure" (S344).

When the automatic update unit 25d determines in S344 that there is no preceding F/W update task for the target image forming device, it determines whether or not a F/W update using the device management system 20 is permitted for the target image forming device based on the device information 24f (S345).

When the automatic update unit 25d determines in S345 that a F/W update using the device management system 20 is permitted for the target image forming device, it determines whether the release type of the firmware installed in the target image forming device is "official" based on the device information 24f (S346).

When the automatic update unit 25d determines in S346 that the release type of the firmware installed in the target image forming device is "official," it determines whether the F/W version of the firmware installed in the target image forming device is older than the F/W version set in the target automatic F/W update task based on the device information 24f (S347).

When the automatic update unit 25d determines in S347 that the F/W version of the firmware installed in the target image forming device is older than the F/W version set in the target automatic F/W update task, it requests the target image forming device to execute a F/W update using a F/W package identified by the package ID set in the target automatic F/W update task from among the F/W packages stored in the storage unit 24 (S348). Note that the image forming device cannot start executing a F/W update in certain cases, such as when it is in the middle of printing.

After processing S348, the automatic update unit 25d determines whether the target image forming device has notified it that it has been able to start executing the F/W update (S349). For example, if the image forming device is in the middle of printing, when the printing is completed, it starts executing the F/W update and notifies the device management system 20 that it has been able to start executing the F/W update.

When the automatic update unit 25d determines in S349 that the target image forming device has not notified it that it has been able to start the execution of the F/W update, it determines whether a specific situation has occurred in which the execution of the F/W update has not been started in the target image forming device (S350). Here, the specific situation may be, for example, a situation in which the target image forming device is in a state in which the image forming device is temporarily connected to the device management system 20 only when the image forming device transmits information about the image forming device, such as the number of printed sheets, to the device management system 20.

If the automatic update unit 25d determines in S350 that no specific situation has occurred in which execution of the F/W update is not initiated on the target image forming device, it executes the process of S349.

When the automatic update unit 25d determines in S349 that the target image forming device has notified it that it has been able to start executing the F/W update, it sets the value of the "Status" item in the task information 24n for the target automatic F/W update task to "In Progress" (S351).

After the processing of S351, the automatic update unit 25d determines whether the F/W update requested in S348 was successful (S352). Here, the automatic update unit 25d can determine in S352 that the F/W update requested in S348 was successful by receiving a notification from the target image forming device that the F/W update requested in S348 was successful.

When the automatic update unit 25d determines in S352 that the F/W update requested in S348 was not successful, the automatic update unit 25d determines whether the F/W update requested in S348 failed (S353). Here, the automatic update unit 25d can determine in S353 that the F/W update requested in S348 failed by being notified by the target image forming device that the F/W update requested in S348 failed.

When the automatic update unit 25d determines in S353 that the F/W update requested in S348 has not failed, it determines whether the target image forming device has not notified it for a specific period of time, such as 45 minutes, that the F/W update requested in S348 is currently being executed (S354). Here, if the target image forming device is currently executing the F/W update requested in S348 by the device management system 20, it notifies the device management system 20 that the F/W update is currently being executed, for example, every minute.

If the automatic update unit 25d determines in S354 that the target image forming device has not notified the user for a specific period of time that the F/W update requested in S348 is in progress, the automatic update unit 25d executes the process of S352.

When the automatic update unit 25d determines in S352 that the F/W update requested in S348 was successful, it sets the value of the "Status" item in the task information 24n for the target automatic F/W update task to "Success" (S355).

If the automatic update unit 25d determines in S345 that the F/W update using the device management system 20 is not permitted for the target image forming device, determines in S346 that the release type of the firmware installed in the target image forming device is not "official", determines in S347 that the F/W version of the firmware installed in the target image forming device is not older than the F/W version set in the target automatic F/W update task, determines in S350 that a specific situation has occurred in which the execution of the F/W update has not been started in the target image forming device, determines in S353 that the execution of the F/W update requested in S348 has failed, or determines in S354 that the target image forming device has not notified the user for a specific period of time that the execution of the F/W update requested in S348 is in progress, the automatic update unit 25d sets the value of the "Status" item in the task information 24n for the target automatic F/W update task to "failed" (S356).

When the automatic update unit 25d determines in S341 that the value of the "Status" item in the task information 24n for the target automatic F/W update task is not "Pending", or when the processing of S355 or S356 ends, the operation shown in FIG. 37 and FIG. 38 ends.

The above describes the operation of the device management system 20 when the automatic update unit 25d executes an automatic F/W update task for an intermediary-free image forming device.

The automatic update unit 25d executes a test F/W update task for a non-intermediary image forming device in the same manner as when executing an automatic F/W update task for a non-intermediary image forming device. Here, since a specific scheduled execution time is not set for the test F/W update task, the automatic update unit 25d immediately determines that the scheduled execution time set for the test F/W update task stored in the memory unit 24 has arrived.

The manual update unit 25c also executes a manual F/W update task for a non-intermediary image forming device in the same manner as when the automatic update unit 25d executes an automatic F/W update task for a non-intermediary image forming device. However, when executing a manual F/W update task, the manual update unit 25c does not execute the processes corresponding to S346 to S347, and immediately executes the process corresponding to S348 if it determines in the process corresponding to S345 that a F/W update using the device management system 20 is permitted for the target image forming device.

Next, we will explain the operation of the information processing system 10 when the intermediary device periodically requests a F/W update task from the device management system 20.

Figure 39 is a flowchart of the operation of the intermediary device when periodically requesting a F/W update task from the device management system 20.

As shown in FIG. 39, the firmware update unit of the intermediary device determines whether the periodic time has passed (S361) until it determines that the periodic time has passed. Here, the periodic time is, for example, every three hours.

When the F/W update unit determines in S361 that the periodic time has passed, it requests the device management system 20 to perform all F/W update tasks for all image forming devices indicated in the device information stored in the intermediary device itself, i.e., all image forming devices managed by the intermediary device itself (S362).

Figure 40 is a flowchart of part of the operation of the device management system 20 when a firmware update task is requested from an intermediary device. Figure 41 is a continuation of the flowchart shown in Figure 40.

When a F/W update task is requested from the intermediary device, the task management unit 25e of the device management system 20 executes the operations shown in Figures 40 and 41.

As shown in Figs. 40 and 41, the task management unit 25e judges whether or not there is an unexecuted F/W update task for an image forming device managed by the intermediary device that requested the F/W update task (hereinafter, simply referred to as the "requesting intermediary device" in the explanation of Figs. 40 and 41) among the F/W update tasks stored in the storage unit 24 (S381). Here, the task management unit 25e judges the image forming device managed by the requesting intermediary device based on the device information 24f, and judges the F/W update task for the image forming device based on the task information 24n. In addition, the task management unit 25e judges an F/W update task for which the value of the "Status" item in the task information 24n is "pending" as an unexecuted F/W update task.

When the task management unit 25e determines in S381 that there is an unexecuted F/W update task for an image forming device managed by the requesting intermediary device among the F/W update tasks stored in the memory unit 24, it determines whether or not there is an F/W update task for an image forming device for which F/W update using the device management system 20 is permitted among the unexecuted F/W update tasks for image forming devices managed by the requesting intermediary device (S382). Here, the task management unit 25e determines whether or not F/W update using the device management system 20 is permitted for the image forming device based on the device information 24f.

When the task management unit 25e determines in S382 that there is an F/W update task for an image forming device for which F/W updating using the device management system 20 is permitted among the unexecuted F/W update tasks for the image forming devices managed by the intermediary device that made the request, the task management unit 25e extracts only the F/W update tasks for the image forming devices for which F/W updating using the device management system 20 is permitted from the unexecuted F/W update tasks for the image forming devices managed by the intermediary device that made the request (S383).

After processing S383, the task management unit 25e determines whether or not a test F/W update task or an automatic F/W update task is present among the F/W update tasks extracted in S383 (S384).

When the task management unit 25e determines in S384 that the F/W update tasks extracted in S383 do not include a test F/W update task or an automatic F/W update task, it transmits, from among the F/W update tasks extracted in S383, a F/W update task other than the test F/W update task or the automatic F/W update task, i.e., a manual F/W update task, to the requesting intermediary device (S385), and ends the operation shown in Figures 40 and 41.

When the task management unit 25e determines in S384 that a test F/W update task or an automatic F/W update task is present among the F/W update tasks extracted in S383, it extracts the test F/W update task and the automatic F/W update task from the F/W update tasks extracted in S383 (S386).

Next, the task management unit 25e determines whether or not the test F/W update task and the automatic F/W update task extracted in S386 include a F/W update task for an image forming device in which the release type of the installed firmware is "official" (S387). Here, the task management unit 25e determines whether or not the release type of the firmware installed in the image forming device is "official" based on the device information 24f.

When the task management unit 25e determines in S387 that the test F/W update task and the automatic F/W update task extracted in S386 include a F/W update task for an image forming device in which the release type of the installed firmware is "official," the task management unit 25e extracts only the F/W update task for an image forming device in which the release type of the installed firmware is "official" from the test F/W update task and the automatic F/W update task extracted in S386 (S388).

Next, the task management unit 25e determines whether or not the F/W update tasks extracted in S388 include a F/W update task for an image forming device in which the F/W version of the installed firmware is older than the F/W version set in the target F/W update task (S389). Here, the task management unit 25e determines whether or not the F/W version of the firmware installed in the image forming device is older than the F/W version set in the target F/W update task based on the device information 24f.

When the task management unit 25e determines in S389 that the F/W update tasks extracted in S388 include a F/W update task for an image forming device in which the F/W version of the installed firmware is older than the F/W version set in the target F/W update task, it extracts only F/W update tasks for image forming devices in which the F/W version of the installed firmware is older than the F/W version set in the target F/W update task from the F/W update tasks extracted in S388 (S390).

Next, the task management unit 25e determines whether or not a manual F/W update task exists among the F/W update tasks extracted in S383 (S391).

When the task management unit 25e determines in S391 that a manual F/W update task exists among the F/W update tasks extracted in S383, it transmits the F/W update task extracted in S390 and the manual F/W update task extracted in S383 to the requesting intermediary device (S392), and ends the operation shown in Figures 40 and 41.

If the task management unit 25e determines in S391 that there is no manual F/W update task among the F/W update tasks extracted in S383, it transmits the F/W update task extracted in S390 to the requesting intermediary device (S393) and terminates the operation shown in Figures 40 and 41.

The task management unit 25e determines in S381 that, among the F/W update tasks stored in the memory unit 24, there is no unexecuted F/W update task for the image forming device managed by the intermediary device that originated the request, or determines in S382 that, among the unexecuted F/W update tasks for the image forming device managed by the intermediary device that originated the request, there is no F/W update task for the image forming device for which F/W update using the device management system 20 is permitted, or determines in S386 that the test F/W update task and the automatic F/W update task extracted are not installed. If it is determined in S387 that there is no F/W update task for an image forming device in which the release type of the installed firmware is "official," or if it is determined in S389 that there is no F/W update task for an image forming device in which the F/W version of the installed firmware is older than the F/W version set in the target F/W update task among the F/W update tasks extracted in S388, a notification that there is no F/W update task to be sent is sent to the requesting intermediary device (S394), and the operation shown in Figures 40 and 41 is terminated.

Note that even if the task management unit 25e sends the F/W update task stored in the memory unit 24 to the intermediary device, the task management unit 25e does not delete the F/W update task from the memory unit 24.

As shown in FIG. 39, after processing S362, the F/W update unit of the intermediary device determines whether or not it has received a notification from the device management system 20 that there is no F/W update task to send (S363).

If the F/W update unit determines in S363 that it has not received a notification from the device management system 20 that there is no F/W update task to send, it determines whether or not it has received a F/W update task from the device management system 20 (S364).

If the F/W update unit determines in S364 that the F/W update task has not been received from the device management system 20, it executes the process of S363.

When the F/W update unit determines in S364 that it has received a F/W update task from the device management system 20, it determines whether or not there is a F/W update task that is not stored in the memory unit of the intermediary device itself among the F/W update tasks received from the device management system 20 (S365). Here, the F/W update unit identifies the F/W update task by the task ID set in the F/W update task.

When the F/W update unit determines in S365 that there is a F/W update task that is not stored in the intermediary device's own memory among the F/W update tasks received from the device management system 20, the F/W update unit saves the F/W update task that is not stored in the intermediary device's own memory among the F/W update tasks received from the device management system 20 in the intermediary device's own memory (S366).

When the F/W update unit determines in S363 that it has received a notification from the device management system 20 that there is no F/W update task to be sent, or when it determines in S365 that there is no F/W update task stored in the memory unit of the intermediary device itself among the F/W update tasks received from the device management system 20, or when the process of S366 ends, it executes the process of S361.

Next, we will explain the operation of an intermediary device when performing pre-printing on an image forming device that it manages.

Figure 42 is a flowchart of the operation of an intermediary device when performing pre-printing on an image forming device that it manages.

The F/W update unit of the intermediary device executes the operation shown in FIG. 42 for each combination of an image forming device managed by the intermediary device itself and an automatic F/W update task stored in the memory unit of the intermediary device itself.

As shown in FIG. 42, the F/W update unit determines whether it is 12 hours before the scheduled execution time of the target automatic F/W update task (hereinafter, simply referred to as the "target automatic F/W update task" in the explanation of FIG. 42) that is the target of the operation shown in FIG. 42 (S401).

When the F/W update unit determines in S401 that it is 12 hours before the scheduled execution time of the target automatic F/W update task, it determines whether the value of the "Pre-print setting" item in the automatic F/W update group setting of the group to which the target image forming device (hereinafter simply referred to as the "target image forming device" in the explanation of FIG. 42) of the operation shown in FIG. 42 belongs is "ON" by inquiring of the device management system 20 (S402).

When the F/W update unit determines in S402 that the value of the "Pre-print setting" item in the automatic F/W update group setting for the group to which the target image forming device belongs is "ON", it requests the device management system 20 to execute all F/W update tasks for all image forming devices indicated in the device information stored in the intermediary device itself, i.e., all image forming devices managed by the intermediary device itself (S403). Therefore, the task management unit 25e of the device management system 20 executes the operations shown in Figs. 40 and 41.

As shown in FIG. 42, after processing S403, the F/W update unit of the intermediary device determines whether or not it has received a notification from the device management system 20 that there is no F/W update task to send (S404).

If the F/W update unit determines in S404 that it has not received a notification from the device management system 20 that there is no F/W update task to send, it determines whether or not it has received a F/W update task from the device management system 20 (S405).

If the F/W update unit determines in S405 that it has not received a F/W update task from the device management system 20, it executes the process of S404.

When the F/W update unit determines in S405 that it has received a F/W update task from the device management system 20, it determines whether or not there is a F/W update task that is not stored in the memory unit of the intermediary device itself among the F/W update tasks received from the device management system 20 (S406). Here, the F/W update unit identifies the F/W update task by the task ID set in the F/W update task.

When the F/W update unit determines in S406 that the F/W update tasks received from the device management system 20 include F/W update tasks that are not stored in the intermediary device's own memory, the F/W update unit saves the F/W update tasks received from the device management system 20 that are not stored in the intermediary device's own memory in the intermediary device's own memory (S407).

When the F/W update unit determines in S406 that the F/W update task not stored in the memory unit of the intermediary device itself is not present in the F/W update task received from the device management system 20, or when the processing of S407 ends, it determines whether the target automatic F/W update task is present in the F/W update task received from the device management system 20 (S408). Here, the F/W update unit identifies the F/W update task by the task ID set in the F/W update task.

When the F/W update unit determines in S408 that the target automatic F/W update task exists in the F/W update tasks received from the device management system 20, it generates print data for a notification that the execution of the F/W update in the automatic F/W update will start at the scheduled execution time of the target automatic F/W update task (S409). Here, the F/W update unit queries the device management system 20 about the language indicated in the "Language setting" item of the automatic F/W update group setting of the group to which the target image forming device belongs, and uses the language returned from the device management system 20 as the language of the notification in S409.

After processing S409, the F/W update unit sends the print data generated in S409 to the target image forming device (S410).

The F/W update unit will not resend the print data generated in S409 to the target image forming device even if the transmission in S410 fails or printing on the target image forming device based on the print data transmitted in S410 fails.

The F/W update unit ends the operation shown in FIG. 42 when it determines in S402 that the value of the "Pre-print setting" item in the automatic F/W update group settings for the group to which the target image forming device belongs is not "ON", determines in S404 that it has received a notification from the device management system 20 that there is no F/W update task to be sent, determines in S408 that the target automatic F/W update task does not exist in the F/W update tasks received from the device management system 20, or ends the processing of S410.

Next, we will explain the operation of the intermediary device when executing an automatic firmware update task on the image forming device that it manages.

Figure 43 is a flowchart of part of the operation of an intermediary device when executing an automatic firmware update task for an image forming device that the intermediary device manages. Figure 44 is a continuation of the flowchart shown in Figure 43.

The F/W update unit of the intermediary device executes the operations shown in Figures 43 and 44 for each automatic F/W update task stored in the memory unit of the intermediary device itself.

As shown in Figures 43 and 44, the F/W update unit of the intermediary device determines whether the scheduled execution time set for the target automatic F/W update task of the operation shown in Figures 43 and 44 (hereinafter simply referred to as the "target automatic F/W update task" in the explanation of Figures 43 and 44) has arrived (S421).

When the F/W update unit determines in S421 that the scheduled execution time set for the target automatic F/W update task has arrived, it requests the device management system 20 to execute all F/W update tasks for all image forming devices indicated in the device information stored in the intermediary device itself, i.e., all image forming devices managed by the intermediary device itself (S422). Therefore, the task management unit 25e of the device management system 20 executes the operations shown in Figs. 40 and 41.

As shown in Figures 43 and 44, after processing S422, the F/W update unit of the intermediary device determines whether or not it has received a notification from the device management system 20 that there is no F/W update task to send (S423).

If the F/W update unit determines in S423 that it has not received a notification from the device management system 20 that there is no F/W update task to send, it determines whether or not it has received a F/W update task from the device management system 20 (S424).

If the F/W update unit determines in S424 that the F/W update task has not been received from the device management system 20, it executes the process of S423.

When the F/W update unit determines in S424 that it has received a F/W update task from the device management system 20, it determines whether or not there is a F/W update task that is not stored in the memory unit of the intermediary device itself among the F/W update tasks received from the device management system 20 (S425). Here, the F/W update unit identifies the F/W update task by the task ID set in the F/W update task.

When the F/W update unit determines in S425 that there is a F/W update task that is not stored in the intermediary device's own memory among the F/W update tasks received from the device management system 20, the F/W update unit saves the F/W update task that is not stored in the intermediary device's own memory among the F/W update tasks received from the device management system 20 in the intermediary device's own memory (S426).

When the F/W update unit determines in S425 that the F/W update task not stored in the memory unit of the intermediary device itself is not present in the F/W update task received from the device management system 20, or when the processing of S426 ends, it determines whether the target automatic F/W update task is present in the F/W update task received from the device management system 20 (S427). Here, the F/W update unit identifies the F/W update task by the task ID set in the F/W update task.

When the F/W update unit determines in S427 that the target automatic F/W update task is present in the F/W update task received from the device management system 20, it determines whether or not the F/W package identified by the package ID set in the target automatic F/W update task (hereinafter referred to as the "target F/W package" in the explanations of Figures 43 and 44) is stored in the memory unit of the intermediary device itself (S428).

If the F/W update unit determines in S428 that the target F/W package is not stored in the storage unit of the intermediary device itself, it downloads the target F/W package from the device management system 20 using the package download link set in the target automatic F/W update task (S429). In other words, the F/W update unit acquires the target F/W package from the device management system 20 and stores the acquired F/W package in the storage unit of the intermediary device itself.

When the F/W update unit determines in S428 that the target F/W package is stored in the storage unit of the intermediary device itself, or when the processing of S429 ends, it requests the target image forming device of the target automatic F/W update task (hereinafter simply referred to as the "target image forming device" in the explanation of Figures 43 and 44) to execute a F/W update using the target F/W package stored in the storage unit of the intermediary device itself (S430). Note that the image forming device cannot start executing a F/W update in certain cases, such as when it is in the middle of printing.

After processing S430, the F/W update unit determines whether the target image forming device has notified it that it has been able to start executing the F/W update (S431). For example, if the image forming device is in the middle of printing, when the printing is completed, it starts executing the F/W update and notifies the intermediary device that it has been able to start executing the F/W update.

If the F/W update unit determines in S431 that the target image forming device has not notified it that it has been able to start the execution of the F/W update, it determines whether a specific situation has occurred in which the execution of the F/W update cannot be started on the target image forming device (S432).

If the F/W update unit determines in S432 that no specific situation has occurred that would prevent the execution of the F/W update from being started on the target image forming device, it executes the process of S431.

When the F/W update unit determines in S431 that the target image forming device has notified it that it has been able to start executing the F/W update, it transmits "Running" as the value of the "Status" item in the task information for the target automatic F/W update task to the device management system 20 (S433).

After processing S433, the F/W update unit determines whether the F/W update requested in S430 was successful (S434). Here, the F/W update unit can determine in S434 that the F/W update requested in S430 was successful by receiving a notification from the target image forming device that the F/W update requested in S430 was successful.

If the F/W update unit determines in S434 that the F/W update requested in S430 was not successful, it determines whether the F/W update requested in S430 failed (S435). Here, the F/W update unit can determine in S435 that the F/W update requested in S430 failed by being notified by the target image forming device that the F/W update requested in S430 failed.

If the F/W update unit determines in S435 that the F/W update requested in S430 has not failed, it determines whether one minute has passed since it sent "Running" as the value of the "Status" item in the task information for the target automatic F/W update task to the device management system 20 (S436).

If the F/W update unit determines in S436 that one minute has not yet elapsed since the value of the "Status" item in the task information for the target automatic F/W update task was previously sent to the device management system 20 as "Running", it executes the process of S434.

When the F/W update unit determines in S436 that one minute has elapsed since it last sent "Running" as the value of the "Status" item in the task information for the target automatic F/W update task to the device management system 20, it executes the process of S433.

When the F/W update unit determines in S434 that the F/W update requested in S430 was successful, it transmits "Success" as the value of the "Status" item in the task information for the target automatic F/W update task to the device management system 20 (S437).

If the F/W update unit determines in S432 that a specific situation has occurred in which the execution of the F/W update cannot be started on the target image forming device, or determines in S435 that the F/W update requested in S430 has failed, it transmits "Failed" as the value of the "Status" item in the task information for the target automatic F/W update task to the device management system 20 (S438).

When the F/W update unit determines in S423 that it has received a notification from the device management system 20 that there is no F/W update task to be sent, determines in S427 that the target automatic F/W update task does not exist in the F/W update tasks received from the device management system 20, or ends the processing of S437 or S438, the operation shown in FIG. 43 and FIG. 44 ends.

The above describes the operation of the intermediary device when the F/W update unit executes an automatic F/W update task for the intermediary image forming device.

The F/W update unit executes a test F/W update task for the intermediary image forming device in the same manner as when executing an automatic F/W update task for the intermediary image forming device. Here, since a specific scheduled execution time is not set for the test F/W update task, the F/W update unit immediately determines that the scheduled execution time set for the test F/W update task stored in the memory unit of the intermediary device itself has arrived.

The F/W update unit also executes a manual F/W update task for an intermediary image forming device in the same manner as it executes an automatic F/W update task for an intermediary image forming device.

Next, we will explain the operation of the device management system 20 when setting the value of the "Status" item of task information 24n of a F/W update task for an intermediary image forming device.

Figure 45 is a flowchart of the operation of the device management system 20 when setting the value of the "Status" item of task information 24n of a F/W update task for an intermediary image forming device.

The task management unit 25e of the device management system 20 executes the operation shown in FIG. 45 for each F/W update task for the intermediary image forming device.

As shown in FIG. 45, the task management unit 25e determines whether the scheduled execution time set for the target F/W update task of the operation shown in FIG. 45 (hereinafter, simply referred to as the "target F/W update task" in the explanation of FIG. 45) has arrived (S441).

When the F/W update unit determines in S441 that the scheduled execution time set for the target F/W update task has arrived, it determines whether the value of the "Status" item of the task information has not been transmitted from the intermediary device for a specific time from the scheduled execution time set for the target F/W update task (S442). Here, the specific time is, for example, 30 minutes.

When the F/W update unit determines in S442 that the value of the "Status" item of the task information has been sent from the intermediary device for a specific time from the scheduled execution time set for the target F/W update task, it determines whether "Running" has been sent from the intermediary device as the value of the "Status" item of the task information for the target F/W update task (S443).

When the task management unit 25e determines in S443 that the value of the "Status" item in the task information for the target F/W update task is "Running" sent from the intermediary device, it sets the value of the "Status" item in the task information 24n for the target F/W update task to "Running" (S444).

The task management unit 25e determines in S443 that the value of the "Status" item in the task information for the target F/W update task has not been sent from the intermediary device as "Running", or, upon completion of the processing of S444, determines whether the value of the "Status" item in the task information for the target F/W update task has been sent from the intermediary device as "Success" (S445).

When the task management unit 25e determines in S445 that the value of the "Status" item in the task information for the target F/W update task has not been sent from the intermediary device as "Success", it determines whether the value of the "Status" item in the task information for the target F/W update task has been sent from the intermediary device as "Failure" (S446).

When the task management unit 25e determines in S446 that the value of the "Status" item in the task information for the target F/W update task has not been sent from the intermediary device as "Failed", the task management unit 25e determines whether a specific time has elapsed since the value of the "Status" item in the task information for the target F/W update task was last sent from the intermediary device as "Running" (S447). Here, the specific time is a time that exceeds the 1 minute that is the judgment criterion for the processing of S436, such as 10 minutes.

When the task management unit 25e determines in S447 that a specific time has not elapsed since the value of the "Status" item in the task information for the target F/W update task was last sent from the intermediary device as "Running," the task management unit 25e executes the process of S442.

When the task management unit 25e determines in S445 that the value of the "Status" item in the task information for the target F/W update task has been sent from the intermediary device as "Success", it sets the value of the "Status" item in the task information 24n for the target F/W update task to "Success" (S448).

If the task management unit 25e determines in S442 that the value of the "Status" item in the task information has not been sent from the intermediary device for a specific time from the scheduled execution time set for the target F/W update task, determines in S446 that the value of the "Status" item in the task information for the target F/W update task has been sent from the intermediary device as "Failed", or determines in S447 that a specific time has passed since the value of the "Status" item in the task information for the target F/W update task was last sent from the intermediary device as "Running", then the task management unit 25e sets the value of the "Status" item in the task information 24n for the target F/W update task to "Failed" (S449).

When processing of S448 or S449 is completed, the task management unit 25e ends the operation shown in FIG. 45.

Next, we will explain the operation of the device management system 20 when showing the progress of a F/W update according to an automatic F/W update plan.

Figure 46 is a flowchart of the operation of the device management system 20 when showing the progress of a F/W update according to an automatic F/W update plan.

A user who is logged in to the device management system 20 can specify one specific automatic F/W update plan and send a request to check the progress of the F/W update according to this automatic F/W update plan (hereinafter referred to as a "progress check request") to the device management system 20 via a user terminal (hereinafter referred to as the "target user terminal" in the explanation of FIG. 46). When the automatic update unit 25d of the device management system 20 receives the progress check request, it executes the operation shown in FIG. 46.

As shown in FIG. 46, the automatic update unit 25d determines whether the user who sent the progress confirmation request (hereinafter referred to as the "requester" in the explanation of FIG. 46) has administrator or higher authority based on the user ID of the requester and the authorization information 24c in the same manner as in S125 (S461).

When the automatic update unit 25d determines in S461 that the requester does not have the authority of an administrator or higher, it displays on the target user terminal a message indicating that the requester does not have the authority to check the progress of the F/W update according to the automatic F/W update plan (S462), and ends the operation shown in FIG. 46.

When the automatic update unit 25d determines in S461 that the requester has administrator or higher authority, it transmits data of a screen showing the progress of the F/W update according to the automatic F/W update plan that is the subject of the progress confirmation request (hereinafter referred to as the "progress screen") to the target user terminal, thereby causing the target user terminal to display the progress screen (S463), and ends the operation shown in FIG. 46.

Figure 47 shows an example of a progress status screen 820 displayed on a user terminal during the operation shown in Figure 46.

As shown in FIG. 47, the progress status screen 820 includes a "Success" item indicating the number of image forming devices that have successfully completed the F/W update based on the automatic F/W update plan, a "Skip" item indicating the number of image forming devices that have skipped the F/W update based on the automatic F/W update plan, a "Failed" item indicating the number of image forming devices that have failed in the F/W update based on the automatic F/W update plan, a "Not Targeted" item indicating the number of image forming devices that are not targeted for the F/W update based on the automatic F/W update plan, a "Waiting for Execution" item indicating the number of image forming devices that are waiting for the execution of the F/W update based on the automatic F/W update plan, and a "Total" item indicating the total number of image forming devices that are targeted by the automatic F/W update plan.

Next, we will explain the operation of the device management system 20 when updating the progress screen 820.

Figure 48 is a flowchart of part of the operation of the device management system 20 when updating the progress status screen 820. Figure 49 is a continuation of the flowchart shown in Figure 48.

The automatic update unit 25d updates the progress shown on the progress screen 820 at least daily. The automatic update unit 25d executes the operations shown in Figures 48 and 49 when updating the progress screen 820.

As shown in Figures 48 and 49, the automatic update unit 25d sets the values of the "Success" item, "Skip" item, "Failure" item, "Not applicable" item, "Waiting for execution" item, and "Total" item to 0 (S481).

Next, the automatic update unit 25d identifies the target group for the automatic F/W update according to the target automatic F/W update plan based on the information shown in the "Target Group" item in the target automatic F/W update plan (hereinafter, simply referred to as the "target automatic F/W update plan" in the explanations of Figures 48 and 49) on the progress screen 820 (S482).

Next, the automatic update unit 25d determines whether at least one group was identified in S482 (S483).

When the automatic update unit 25d determines in S483 that at least one group has been identified in S482, it targets only one group among the groups identified in S482 that has not yet been targeted in the current operation shown in Figures 48 and 49 (S484).

Next, the automatic update unit 25d determines whether at least one image forming device belongs to the current target group (S485).

When the automatic update unit 25d determines in S485 that at least one image forming device belongs to the current target group, it targets only one image forming device among the image forming devices belonging to the current target group that has not yet been targeted in the current operation shown in Figures 48 and 49 (S486).

Next, the automatic update unit 25d determines whether there is an automatic F/W update task in the current cycle for the currently targeted image forming device (S487).

When the automatic update unit 25d determines in S487 that there is no automatic F/W update task in the current cycle for the current target image forming device, it determines whether the reason why the automatic F/W update task in the current cycle for the current target image forming device has not been generated is a reason corresponding to "not being targeted" (S488). Here, the reasons corresponding to "not being targeted" include, for example, a reason that the value of the "Automatic F/W Update Setting" item in the automatic F/W update group setting of the current target group is "OFF", a reason that the value of the "Automatic F/W Update Setting" item in the automatic F/W update group setting of the current target group is "Selected" and the value of the "Plan Allowed/Prohibited" item for the target automatic F/W update plan is "Prohibited", a reason that F/W updates using the device management system 20 are not permitted for the current target image forming device, and a reason that the release type of the firmware installed in the current target image forming device is not "official".

When the automatic update unit 25d determines in S488 that the reason why the automatic F/W update task has not been generated in the current cycle for the currently targeted image forming device is a reason corresponding to "not targeted," the automatic update unit 25d increments the value of the "not targeted" item by one (S489). In other words, the automatic update unit 25d determines that the current progress status of the F/W update according to the targeted automatic F/W update plan for the currently targeted image forming device is "not targeted."

When the automatic update unit 25d determines in S488 that the reason why the automatic F/W update task has not been generated in the current cycle for the currently targeted image forming device is not a reason that corresponds to "not targeted," the automatic update unit 25d determines whether the reason why the automatic F/W update task has not been generated in the current cycle for the currently targeted image forming device is a reason that corresponds to "skip" (S490). Here, a reason that corresponds to "skip" is, for example, that the F/W version of the firmware installed in the currently targeted image forming device is not older than the F/W version set in the currently targeted automatic F/W update task.

When the automatic update unit 25d determines in S490 that the reason why the automatic F/W update task has not been generated in the current cycle for the currently targeted image forming device is a reason corresponding to "skip", the automatic update unit 25d increments the value of the "skip" item by one (S491). In other words, the automatic update unit 25d determines that the current progress status of the F/W update according to the target automatic F/W update plan for the currently targeted image forming device is "skip".

When the automatic update unit 25d determines in S487 that there is an automatic F/W update task in the current cycle for the currently targeted image forming device, it determines whether the value of the "Status" item in task information 24n for the automatic F/W update task in the current cycle for the currently targeted image forming device is "Success" (S492).

When the automatic update unit 25d determines in S492 that the value of the "Status" item in the task information 24n for the automatic F/W update task in the current cycle for the currently targeted image forming device is "Success", it increments the value of the "Success" item by one (S493). In other words, the automatic update unit 25d determines that the current progress status of the F/W update according to the target automatic F/W update plan for the currently targeted image forming device is "Success".

When the automatic update unit 25d determines in S492 that the value of the "Status" item in task information 24n for the automatic F/W update task in the current cycle for the currently targeted image forming device is not "Success", it determines whether the value of the "Status" item in task information 24n for the automatic F/W update task in the current cycle for the currently targeted image forming device is "Cancelled" (S494).

When the automatic update unit 25d determines in S494 that the value of the "Status" item in task information 24n for the automatic F/W update task in the current cycle for the currently targeted image forming device is "Cancelled," it executes the process of S489.

When the automatic update unit 25d determines in S494 that the value of the "Status" item in task information 24n for the automatic F/W update task in the current cycle for the currently targeted image forming device is not "Cancelled," it determines whether the value of the "Status" item in task information 24n for the automatic F/W update task in the current cycle for the currently targeted image forming device is "Failed" (S495).

When the automatic update unit 25d determines in S495 that the value of the "Status" item in task information 24n for the automatic F/W update task in the current cycle for the currently targeted image forming device is "Failed", it determines whether the reason why the value of the "Status" item in task information 24n for the automatic F/W update task in the current cycle for the currently targeted image forming device is "Failed" is a reason that corresponds to "Not Target" (S496). Here, reasons for being "not applicable" include, for example, that the value of the "Automatic F/W Update Settings" item in the automatic F/W update group settings of the current target group is "OFF", that the value of the "Automatic F/W Update Settings" item in the automatic F/W update group settings of the current target group is "Selected" and the value of the "Plan Allowed/Prohibited" item for the target automatic F/W update plan is "Prohibited", that F/Update using the device management system 20 is not permitted for the current target image forming device, that the release type of the firmware installed in the current target image forming device is not "official", and that the target image forming device is in a state in which the image forming device is temporarily connected to the device management system 20 only when the image forming device transmits information about the image forming device, such as the number of printed sheets, to the device management system 20.

When the automatic update unit 25d determines in S496 that the reason why the value of the "Status" item in the task information 24n for the automatic F/W update task in the current cycle for the currently targeted image forming device is "Failed" is because the value is "Not Targeted," the automatic update unit 25d executes the process of S489.

When the automatic update unit 25d determines in S496 that the reason why the value of the "Status" item in the task information 24n is "Failed" for the automatic F/W update task in the current cycle for the currently targeted image forming device is not a reason corresponding to "Not Target", the automatic update unit 25d determines whether the reason why the value of the "Status" item in the task information 24n is "Failed" for the automatic F/W update task in the current cycle for the currently targeted image forming device is a reason corresponding to "Skip" (S497). Here, examples of reasons corresponding to "Skip" include the F/W version of the firmware installed in the currently targeted image forming device being not older than the F/W version set in the target automatic F/W update task.

When the automatic update unit 25d determines in S497 that the reason why the value of the "Status" item in the task information 24n for the automatic F/W update task in the current cycle for the currently targeted image forming device is "Failed" is a reason corresponding to "Skip", it executes the process of S491.

When the automatic update unit 25d determines in S497 that the reason why the value of the "Status" item in the task information 24n for the automatic F/W update task in the current cycle for the currently targeted image forming device is "Failed" is not a reason corresponding to "Skip", the automatic update unit 25d increments the value of the "Failed" item by one (S498). In other words, the automatic update unit 25d determines that the current progress status of the F/W update according to the target automatic F/W update plan for the currently targeted image forming device is "Failed".

When the automatic update unit 25d determines in S490 that the reason why the automatic F/W update task has not been generated in the current cycle for the currently targeted image forming device is not a reason corresponding to "skip", or determines in S495 that the value of the "Status" item in task information 24n for the automatic F/W update task in the current cycle for the currently targeted image forming device is not "failed", it determines whether or not the progress of the F/W update according to the target automatic F/W update plan was determined at the end of the previous cycle for the currently targeted image forming device (S499).

When the automatic update unit 25d determines in S499 that it has determined the progress status of the F/W update according to the target automatic F/W update plan at the end of the previous cycle for the currently targeted image forming device, it determines the progress status determined at the end of the previous cycle for the F/W update according to the target automatic F/W update plan for the currently targeted image forming device from among "success", "skip", "failure", "not targeted" and "waiting for execution" (S500).

When the automatic update unit 25d determines in S500 that the progress status determined at the end of the previous cycle for the F/W update according to the target automatic F/W update plan for the currently targeted image forming device is "successful," it executes the process of S493.

When the automatic update unit 25d determines in S500 that the progress status determined at the end of the previous cycle for the F/W update according to the target automatic F/W update plan for the currently target image forming device is "skip," it executes the process of S491.

When the automatic update unit 25d determines in S500 that the progress status determined at the end of the previous cycle for the F/W update according to the target automatic F/W update plan for the currently targeted image forming device was "failed," it executes the process of S498.

When the automatic update unit 25d determines in S500 that the progress status determined at the end of the previous cycle for the F/W update according to the target automatic F/W update plan for the currently target image forming device is "not targeted," it executes the process of S489.

When the automatic update unit 25d determines in S499 that the progress status of the F/W update according to the target automatic F/W update plan was not determined at the end of the previous cycle for the currently targeted image forming device, or determines in S500 that the progress status determined at the end of the previous cycle for the F/W update according to the target automatic F/W update plan for the currently targeted image forming device is "waiting for execution", the automatic update unit 25d increments the value of the "waiting for execution" item by one (S501). In other words, the automatic update unit 25d determines that the current progress status of the F/W update according to the target automatic F/W update plan for the currently targeted image forming device is "waiting for execution".

When the processing of S489, S491, S493, S498 or S501 is completed, the automatic update unit 25d determines whether all image forming devices belonging to the current target group have been targeted (S502).

If the automatic update unit 25d determines in S502 that at least one image forming device belonging to the current target group is not the target, it executes the process of S486.

When the automatic update unit 25d determines in S485 that no image forming devices belong to the current target group, or determines in S502 that all image forming devices belonging to the current target group have been targeted, it determines whether all groups identified in S482 have been targeted (S503).

If the automatic update unit 25d determines in S503 that at least one of the groups identified in S482 is not the target, it executes the process of S484.

When the automatic update unit 25d determines in S483 that no groups were identified in S482, or determines in S503 that all groups identified in S482 have been targeted, it calculates the value of the "Total" item by adding up the current value of the "Success" item, the current value of the "Skip" item, the current value of the "Failure" item, the current value of the "Not Targeted" item, and the current value of the "Waiting for Execution" item (S504).

Next, the automatic update unit 25d updates the progress screen 820 with the current value of the "Success" item, the current value of the "Skip" item, the current value of the "Failure" item, the current value of the "Not Applicable" item, the current value of the "Waiting for Execution" item, and the current value of the "Total" item (S505), and ends the operation shown in Figures 48 and 49.

Figure 50 shows an example of a change in progress status shown on the progress status screen 820.

In the example shown in FIG. 50, the progress is updated daily. In FIG. 50, the first three cycles of execution of the automatic F/W update task are shown. In the example shown in FIG. 50, the automatic F/W update mode is "update immediately," so all cycles are one week, i.e., seven days.

The first day of the first cycle in the example shown in FIG. 50 will be described. The number shown in the "Success" field of the progress screen 820 is "2" because the automatic F/W update tasks of image forming device A and image forming device E in the first cycle were successful (YES in S492) (S493). The number shown in the "Skip" field of the progress screen 820 is "0" because there is no corresponding image forming device managed by the device management system 20 (S481). The number shown in the "Failed" field of the progress screen 820 is "0" because there is no corresponding image forming device managed by the device management system 20 (S481). The number shown in the "Not Applicable" field of the progress screen 820 is "1" because F/W update using the device management system 20 is not permitted for image forming device F (YES in S488) (S489). The number shown in the "Waiting for Execution" field on progress status screen 820 is "4" (S501) because the automatic F/W update tasks for image forming apparatus B, image forming apparatus C, image forming apparatus G, and image forming apparatus H have not yet been executed (NO in S499). Therefore, the number shown in the "Total" field on progress status screen 820 is "7" (S504). Note that image forming apparatus D is not yet managed by device management system 20, so it is not reflected on progress status screen 820.

The second day of the first cycle in the example shown in FIG. 50 will be described. The number shown in the "Success" field of the progress screen 820 is "3" because the automatic F/W update tasks of image forming apparatus A, image forming apparatus B, and image forming apparatus E in the first cycle were successful (YES in S492) (S493). The number shown in the "Skip" field of the progress screen 820 is "0" because there is no corresponding image forming apparatus managed by the device management system 20 (S481). The number shown in the "Failed" field of the progress screen 820 is "0" because there is no corresponding image forming apparatus managed by the device management system 20 (S481). The number shown in the "Not applicable" field of the progress screen 820 is "1" because F/W update using the device management system 20 is not permitted for image forming apparatus F (YES in S488) (S489). The number shown in the "Waiting for Execution" field on progress status screen 820 is "3" (S501) because the automatic F/W update tasks for image forming apparatus C, image forming apparatus G, and image forming apparatus H have not yet been executed (NO in S499). Therefore, the number shown in the "Total" field on progress status screen 820 is "7" (S504). Note that image forming apparatus D is not yet managed by device management system 20, so it is not reflected on progress status screen 820.

The third day of the first cycle in the example shown in FIG. 50 will be described. The number shown in the "Success" item of the progress screen 820 is "3" (S493) because the automatic F/W update tasks of image forming device A, image forming device B, and image forming device E in the first cycle were successful (YES in S492). The number shown in the "Skip" item of the progress screen 820 is "0" (S481) because there is no corresponding image forming device managed by the device management system 20. The number shown in the "Failure" item of the progress screen 820 is "1" (S498) because the automatic F/W update task of image forming device C in the first cycle failed (NO in S497). The number shown in the "Not Applicable" field on the progress screen 820 is "2" (S489) because image forming apparatus F is not permitted to perform a F/W update using the device management system 20 (YES in S488) and the release type of the firmware installed in image forming apparatus H is not "official" (YES in S496). The number shown in the "Waiting for Execution" field on the progress screen 820 is "1" (S501) because the automatic F/W update task for image forming apparatus G has not yet been executed (NO in S499). Therefore, the number shown in the "Total" field on the progress screen 820 is "7" (S504). Note that image forming apparatus D is not yet managed by the device management system 20 and is not reflected on the progress screen 820.

The fourth day of the first cycle in the example shown in FIG. 50 will be described. On the fourth day of the first cycle, F/W update using the device management system 20 is permitted for image forming device F. However, since the first cycle is in progress, no new automatic F/W update task is generated for image forming device F. The number shown in the "Success" item of the progress screen 820 is "3" (S493) because the automatic F/W update tasks for image forming device A, image forming device B, and image forming device E in the first cycle were successful (YES in S492). The number shown in the "Skip" item of the progress screen 820 is "1" (S491) because the F/W version of the firmware installed in image forming device G was newer than the F/W version set in the target automatic F/W update task (YES in S497). The number shown in the "Failed" item on the progress screen 820 is "1" because the execution of the automatic F/W update task of the image forming device C in the first cycle has failed (NO in S497) (S498). The number shown in the "Not Targeted" item on the progress screen 820 is "1" because the release type of the firmware installed in the image forming device H was not "official" (YES in S496) (S489). The number shown in the "Waiting for Execution" item on the progress screen 820 is "1" because the automatic F/W update task of the image forming device F has not yet been executed (NO in S499) (S501). Therefore, the number shown in the "Total" item on the progress screen 820 is "7" (S504). Note that the image forming device D is not yet managed by the device management system 20, so it is not reflected on the progress screen 820.

The fifth day of the first cycle in the example shown in FIG. 50 will be described. On the fifth day of the first cycle, image forming device D is newly managed by device management system 20. However, since the first cycle is in progress, no new automatic F/W update task is generated for image forming device D. The number shown in the "Success" item of progress screen 820 is "3" (S493) because the automatic F/W update tasks for image forming device A, image forming device B, and image forming device E in the first cycle were successfully executed (YES in S492). The number shown in the "Skip" item of progress screen 820 is "1" (S491) because the F/W version of the firmware installed in image forming device G was newer than the F/W version set in the target automatic F/W update task (YES in S497). The number shown in the "Failed" item on the progress screen 820 is "1" (S498) because the execution of the automatic F/W update task for image forming device C in the first cycle failed (NO in S497). The number shown in the "Not Targeted" item on the progress screen 820 is "1" (S489) because the release type of the firmware installed in image forming device H was not "official" (YES in S496). The number shown in the "Waiting for Execution" item on the progress screen 820 is "2" (S501) because the automatic F/W update tasks for image forming device D and image forming device F have not yet been executed (NO in S499). Therefore, the number shown in the "Total" item on the progress screen 820 is "8" (S504).

In the example shown in FIG. 50, the progress screen 820 for days 6 and 7 of the first cycle is the same as the progress screen 820 for day 5 of the first cycle.

The first day of the second cycle in the example shown in FIG. 50 will be described. The number shown in the "Success" item of the progress screen 820 is "2" because the automatic F/W update tasks of image forming device B and image forming device E in the second cycle have not yet been executed, but the final progress status of image forming device B and image forming device E in the first cycle is "Success" ("Success" in S500) (S493). The number shown in the "Skip" item of the progress screen 820 is "2" (S491) because the F/W version of the firmware installed in image forming device A is the same as the F/W version set in the target automatic F/W update task (YES in S497) and the F/W version of the firmware installed in image forming device G is newer than the F/W version set in the target automatic F/W update task (YES in S497). The number shown in the "Failed" item on the progress screen 820 is "1" because the automatic F/W update task of the image forming apparatus C in the second cycle has not yet been executed, but the final progress status of the image forming apparatus C in the first cycle is "Failed" ("Failed" in S500) (S498). The number shown in the "Not Targeted" item on the progress screen 820 is "1" because the automatic F/W update task of the image forming apparatus H in the second cycle has not yet been executed, but the final progress status of the image forming apparatus H in the first cycle is "Not Targeted" ("Not Targeted" in S500) (S489). The number shown in the "Waiting for Execution" item on the progress screen 820 is "2" because the automatic F/W update tasks of the image forming apparatus D and the image forming apparatus F in the second cycle have not yet been executed, but the final progress status of the image forming apparatus D and the image forming apparatus F in the first cycle is "Waiting for Execution" ("Waiting for Execution" in S500) (S501). Therefore, the number shown in the "Total" field on the progress screen 820 is "8" (S504).

The second day of the second cycle in the example shown in FIG. 50 will be described. The number shown in the "Success" item of the progress screen 820 is "1" because the automatic F/W update task of image forming device E in the second cycle has not yet been executed but the final progress status of image forming device E in the first cycle is "Success" ("Success" in S500) (S493). The number shown in the "Skip" item of the progress screen 820 is "3" (S491) because the F/W versions of the firmware installed in image forming device A and image forming device B are the same as the F/W version set in the target automatic F/W update task (YES in S497) and the F/W version of the firmware installed in image forming device G is newer than the F/W version set in the target automatic F/W update task (YES in S497). The number shown in the "Failed" item on the progress screen 820 is "1" because the automatic F/W update task of the image forming device C in the second cycle has not yet been executed, but the final progress status of the image forming device C in the first cycle is "Failed" ("Failed" in S500) (S498). The number shown in the "Not Targeted" item on the progress screen 820 is "1" because the release type of the firmware installed in the image forming device H was not "Official" (YES in S496) (S489). The number shown in the "Waiting for Execution" item on the progress screen 820 is "2" because the automatic F/W update task of the image forming device D and the image forming device F in the second cycle has not yet been executed, but the final progress status of the image forming device D and the image forming device F in the first cycle is "Waiting for Execution" ("Waiting for Execution" in S500) (S501). Therefore, the number shown in the "Total" item on the progress screen 820 is "8" (S504).

The third day of the second cycle in the example shown in FIG. 50 will be described. The number shown in the "Success" item of the progress screen 820 is "3" because the automatic F/W update tasks of the image forming device C and the image forming device D in the second cycle have been successfully executed (YES in S492), and the automatic F/W update task of the image forming device E in the second cycle has not yet been executed, but the final progress status of the image forming device E in the first cycle is "Success" ("Success" in S500) (S493). The number shown in the "Skip" item of the progress screen 820 is "3" because the F/W version of the firmware installed in the image forming device A and the image forming device B is the same as the F/W version set in the target automatic F/W update task (YES in S497), and the F/W version of the firmware installed in the image forming device G is newer than the F/W version set in the target automatic F/W update task (YES in S497) (S491). The number shown in the "Failed" item on the progress screen 820 is "0" because there is no corresponding image forming device managed by the device management system 20 (S481). The number shown in the "Not Applicable" item on the progress screen 820 is "1" because the release type of the firmware installed in the image forming device H was not "official" (YES in S496) (S489). The number shown in the "Waiting for Execution" item on the progress screen 820 is "1" because the automatic F/W update task of the image forming device F in the second cycle has not yet been executed, but the final progress status of the image forming device F in the first cycle is "Waiting for Execution" ("Waiting for Execution" in S500) (S501). Therefore, the number shown in the "Total" item on the progress screen 820 is "8" (S504).

The fourth day of the second cycle in the example shown in FIG. 50 will be described. The number shown in the "Success" item of the progress screen 820 is "3" because the automatic F/W update tasks of the image forming apparatus C, image forming apparatus D, and image forming apparatus F in the second cycle were successful (YES in S492) (S493). The number shown in the "Skip" item of the progress screen 820 is "4" because the F/W versions of the firmware installed in the image forming apparatus A, image forming apparatus B, and image forming apparatus E are the same as the F/W version set in the target automatic F/W update task (YES in S497), and the F/W version of the firmware installed in the image forming apparatus G is newer than the F/W version set in the target automatic F/W update task (YES in S497) (S491). The number shown in the "Failure" item of the progress screen 820 is "0" because there is no corresponding image forming apparatus managed by the device management system 20 (S481). The number shown in the "Not Targeted" field on the progress status screen 820 is "1" (S481) because the release type of the firmware installed in image forming device H was not "official" (YES in S496). The number shown in the "Waiting for Execution" field on the progress status screen 820 is "0" (S481) because there is no corresponding image forming device managed by the device management system 20. Therefore, the number shown in the "Total" field on the progress status screen 820 is "8" (S504).

In the example shown in FIG. 50, the progress screen 820 for days 5 to 7 of the second cycle is the same as the progress screen 820 for day 4 of the second cycle.

The first day of the third cycle in the example shown in Figure 50 will be described. The number shown in the "Success" item on the progress screen 820 is "2" (S493) because although the automatic F/W update tasks for image forming device C and image forming device D in the third cycle have not yet been executed, the final progress status of image forming device C and image forming device D in the second cycle is "Success" ("Success" in S500). The number shown in the "Skip" item on the progress status screen 820 is "5" (S491) because the automatic F/W update tasks of image forming apparatus A, image forming apparatus B, and image forming apparatus E in the third cycle have not yet been executed, but the final progress statuses of image forming apparatus A, image forming apparatus B, and image forming apparatus E in the second cycle are "Skip" ("Skip" in S500), the F/W version of the firmware installed in image forming apparatus F is the same as the F/W version set in the target automatic F/W update task (YES in S497), and the F/W version of the firmware installed in image forming apparatus G is newer than the F/W version set in the target automatic F/W update task (YES in S497) (S491). The number shown in the "Failed" item on the progress status screen 820 is "0" (S481) because there is no corresponding image forming apparatus managed by the device management system 20. The number shown in the "Not Targeted" field on the progress status screen 820 is "1" because the automatic F/W update task for image forming device H in the third cycle has not yet been executed, but the final progress status of image forming device H in the second cycle is "Not Targeted" ("Not Targeted" in S500) (S489). The number shown in the "Waiting for Execution" field on the progress status screen 820 is "0" because there is no corresponding image forming device managed by the device management system 20 (S481). Therefore, the number shown in the "Total" field on the progress status screen 820 is "8" (S504).

The second day of the third cycle in the example shown in Figure 50 will be described. The number shown in the "Success" item on the progress screen 820 is "2" (S493) because although the automatic F/W update tasks for image forming device C and image forming device D in the third cycle have not yet been executed, the final progress status of image forming device C and image forming device D in the second cycle is "Success" ("Success" in S500). The number shown in the "Skip" item on the progress status screen 820 is "5" (S491) because the automatic F/W update task of image forming apparatus E in the third cycle has not yet been executed but the final progress status of image forming apparatus E in the second cycle is "Skip" (S500: "Skip"), the F/W versions of the firmware installed in image forming apparatus A, image forming apparatus B, and image forming apparatus F are the same as the F/W version set in the target automatic F/W update task (YES in S497), and the F/W version of the firmware installed in image forming apparatus G is newer than the F/W version set in the target automatic F/W update task (YES in S497). The number shown in the "Failed" item on the progress status screen 820 is "0" (S481) because there is no corresponding image forming apparatus managed by the device management system 20. The number shown in the "Not Targeted" field on the progress status screen 820 is "1" (S481) because the release type of the firmware installed in image forming device H was not "official" (YES in S496). The number shown in the "Waiting for Execution" field on the progress status screen 820 is "0" (S481) because there is no corresponding image forming device managed by the device management system 20. Therefore, the number shown in the "Total" field on the progress status screen 820 is "8" (S504).

The third day of the third cycle in the example shown in FIG. 50 will be described. The number shown in the "Success" item of the progress screen 820 is "0" because there is no corresponding image forming device managed by the device management system 20 (S481). The number shown in the "Skip" item of the progress screen 820 is "7" (S491) because the automatic F/W update task of image forming device E in the third cycle has not yet been executed, but the final progress status of image forming device E in the second cycle is "Skip" ("Skip" in S500), the F/W version of the firmware installed in image forming device A, image forming device B, image forming device C, image forming device D, and image forming device F is the same as the F/W version set in the target automatic F/W update task (YES in S497), and the F/W version of the firmware installed in image forming device G is newer than the F/W version set in the target automatic F/W update task (YES in S497). The number shown in the "Failed" item on the progress screen 820 is "0" because there is no corresponding image forming device managed by the device management system 20 (S481). The number shown in the "Not Targeted" item on the progress screen 820 is "1" because the release type of the firmware installed in image forming device H was not "official" (YES in S496) (S481). The number shown in the "Waiting for Execution" item on the progress screen 820 is "0" because there is no corresponding image forming device managed by the device management system 20 (S481). Therefore, the number shown in the "Total" item on the progress screen 820 is "8" (S504).

The fourth day of the third cycle in the example shown in FIG. 50 will be described. The number shown in the "Success" item of the progress screen 820 is "0" because there is no corresponding image forming device managed by the device management system 20 (S481). The number shown in the "Skip" item of the progress screen 820 is "7" because the F/W version of the firmware installed in the image forming device A, image forming device B, image forming device C, image forming device D, image forming device E, and image forming device F is the same as the F/W version set in the target automatic F/W update task (YES in S497), and the F/W version of the firmware installed in the image forming device G is newer than the F/W version set in the target automatic F/W update task (YES in S497) (S491). The number shown in the "Failure" item of the progress screen 820 is "0" because there is no corresponding image forming device managed by the device management system 20 (S481). The number shown in the "Not Targeted" field on the progress status screen 820 is "1" (S481) because the release type of the firmware installed in image forming device H was not "official" (YES in S496). The number shown in the "Waiting for Execution" field on the progress status screen 820 is "0" (S481) because there is no corresponding image forming device managed by the device management system 20. Therefore, the number shown in the "Total" field on the progress status screen 820 is "8" (S504).

In the example shown in FIG. 50, the progress screen 820 for days 5 to 7 of the third cycle is the same as the progress screen 820 for day 4 of the third cycle.

In the example shown in FIG. 50, in order to facilitate understanding of the changes in progress shown on the progress screen 820, the progress status of multiple image forming devices that have the same cycle update timing is shown. However, the progress status screen 820 can show the progress status of multiple image forming devices that have different cycle update timing.

Next, we will explain the operation of the device management system 20 when displaying a list of image forming devices that it manages.

A user who is logged in to the device management system 20 can send a request (hereinafter referred to as a "device list display request") to display a list of image forming devices (hereinafter referred to as a "device list") managed by the device management system 20 to the device management system 20 via a user terminal (hereinafter referred to as the "target user terminal"). When the device management unit 25f of the device management system 20 receives the device list display request, it causes the device list to be displayed on the target user terminal by sending data of the device list to the target user terminal. Here, the device management unit 25f includes the date and time when the latest F/W update was performed by the F/W update task in the information for each image forming device in the device list.

As described above, the device management system 20 generates an automatic F/W update task for each of all image forming devices that are the target of an automatic F/W update in one mode selected from multiple modes (S291 to S307), thereby improving the convenience of firmware updates.

The device management system 20 generates a F/W update task for each of all image forming devices that are targets of the F/W update in one mode selected from the "immediate update" mode and the "gradual update" mode in which the length of the first cycle in which the F/W update is executed once for all image forming devices that are targets of the F/W update is longer than that in the "immediate update" mode and the length of the second and subsequent cycles is the same as that in the "immediate update" mode (S291 to S307). Therefore, a user who wants the F/W update to be executed immediately for all image forming devices that are targets of the F/W update can select the "immediate update" mode, and a user who wants the F/W update to be executed gradually for all image forming devices that are targets of the F/W update to confirm that the F/W update will not cause problems for the image forming devices can select the "gradual update" mode, thereby improving the convenience of firmware updates.

The device management system 20 generates a F/W update task for each of all image forming devices that are targets of the F/W update in one mode selected from a "quick update" mode in which the ratio of the number of image forming devices on which the update is executed per unit time among all image forming devices that are targets of the F/W update does not change during all cycles in which the F/W update is executed for all image forming devices that are targets of the F/W update, and a "gradual update" mode in which the ratio of the number of image forming devices on which the F/W update is executed per unit time among all image forming devices that are targets of the F/W update increases during the first cycle and does not change during the second and subsequent cycles (S291 to S307). This allows a user who wants the F/W update to be executed immediately for all image forming devices that are targets of the F/W update to select the "quick update" mode, and allows a user who wants the F/W update to be executed gradually for all image forming devices that are targets of the F/W update to select the "gradual update" mode to confirm that the F/W update will not cause problems in the image forming devices, thereby improving the convenience of firmware updates.

In the device management system 20, the length of the cycle from the second update onwards is the same in the "immediate update" mode and the "gradual update" mode (S291 to S307). Therefore, after it is confirmed that the F/W update will not cause any problems in the image forming device, the F/W update can be performed immediately on all image forming devices that are the target of the F/W update, thereby improving the convenience of firmware updates.

In the device management system 20, the ratio of the number of image forming devices on which F/W updates are performed per unit time among all image forming devices that are subject to F/W updates does not change between the second and subsequent cycles in the "immediate update" mode and the "gradual update" mode (S291 to S307). Therefore, after it is confirmed that the F/W update will not cause any problems in the image forming devices, the F/W update can be performed promptly on all image forming devices that are subject to the F/W update, thereby improving the convenience of firmware updates.

The device management system 20 may generate the task so that the period is repeated, and may generate the task for each of the image forming devices even if the image forming devices include an image forming device in which the update was successful during the previous period.

Even if an image forming device that underwent a successful F/W update in the previous period is included among all image forming devices that are subject to the F/W update, the device management system 20 generates an automatic F/W update task for each of the image forming devices that are subject to the F/W update. Therefore, even if an image forming device that underwent a successful F/W update in the previous period was newly updated with, for example, a different version of firmware after the successful F/W update, the original version of firmware is updated again in the current period, and as a result, the variation in firmware among multiple image forming devices can be reduced.

In addition, by reducing the variation in firmware among multiple image forming devices, if a failure occurs in one of the multiple image forming devices, there is a high possibility that a similar failure will occur in the other image forming devices. Therefore, the time required to investigate the cause of a failure and to respond to the failure can be reduced compared to a configuration in which there is greater variation in firmware among multiple image forming devices.

The device management system 20 starts generating automatic F/W update tasks for image forming devices that become the new target of F/W update in the middle of a cycle in which a F/W update is performed on all image forming devices that are the target of F/W update from the next cycle, making it easier to manage automatic F/W update tasks compared to a configuration in which automatic F/W update tasks are started to be generated for image forming devices that become the new target of F/W update in the middle of a cycle at the time they become the new target of F/W update.

In this embodiment, the electronic device of the present invention is an image forming device, but it may be an electronic device other than an image forming device, such as a PC.

In this embodiment, the software of the present invention is firmware, but it may be software other than firmware, such as application software.

20. Equipment management system (computer)
24a Device management program 24l Automatic F/W update task (task)
30 Image forming device without intermediary (electronic equipment)
37a Firmware (software)
50 Image forming apparatus with intermediary (electronic equipment)

Claims (3)

providing a first mode and a second mode for generating a software update task, and generating the task for each of all electronic devices to which the update is to be applied in one mode selected from the first mode and the second mode, such that a period during which the update is performed once for all of the electronic devices to which the update is to be applied is repeated;
In the second mode, a length of the first period is longer than that in the first mode, and a length of the second and subsequent periods is the same as that in the first mode;
An equipment management system characterized in that the first mode and the second mode have different ratios of the number of electronic devices on which the update is performed per unit time among all of the electronic devices during the first period. the first mode being a mode in which the ratio does not change during the period;
2 . The device management system according to claim 1 , wherein the second mode is a mode in which the ratio increases during a first period and the ratio does not change during a second or subsequent period. providing a computer with a first mode and a second mode for generating a software update task, and causing the computer to generate the task for each of all of the electronic devices to which the update is to be applied in one mode selected from the first mode and the second mode, such that a period in which the update is performed once for all of the electronic devices to which the update is to be applied is repeated;
In the second mode, the length of the first period is longer than that in the first mode, and the lengths of the second and subsequent periods are the same as those in the first mode;
The first mode and the second mode are characterized in that the ratio of the number of electronic devices on which the update is executed per unit time among all of the electronic devices during the first period is different from each other.

Images