JP6194990B2 - Image forming apparatus, image forming system, and program - Google Patents

Description

  The present invention relates to an image forming apparatus such as an MFP (Multi-Functional Peripheral) and a related technology.

  There is a technique for transmitting update data of a terminal device. For example, in Patent Document 1, a plurality of terminal devices are logically connected in a hierarchical structure with an update data distribution device (for example, a server) as a vertex, and update data is sequentially transmitted from a higher-layer terminal device to a lower-layer terminal device. The technique to transmit is shown. According to this technique, it is possible to reduce the load concentration on the update data distribution device (server or the like).

JP 2007-334602 A

  By the way, it is preferable to perform an efficient distribution operation when distributing update data related to firmware and the like of a plurality of image forming apparatuses (MFPs and the like) related to a plurality of models.

  However, the technique disclosed in Patent Document 1 does not take into account a plurality of update data distribution operations related to a plurality of models.

  Accordingly, an object of the present invention is to provide a technique capable of efficiently updating programs such as firmware of a plurality of image forming apparatuses (MFPs, etc.) related to a plurality of models.

In order to solve the above problem, the invention of claim 1 is an image forming system having a plurality of types of image forming apparatuses logically connected in a hierarchical structure, and acquires each state of the plurality of types of image forming apparatuses. Determination means for determining whether to execute update data reception processing relating to firmware for each image forming apparatus based on the respective states acquired by the state acquisition means, and determination by the determination means Based on the results, a determination unit that determines a distribution order of a plurality of types of update data related to firmware of the plurality of types of image forming apparatuses, and a logical connection directly according to the distribution order determined by the determination unit. The same type of update data is simultaneously distributed from a higher-level image forming apparatus to a plurality of lower-level image forming apparatuses. An image forming apparatus that is determined by the determining means that the update data receiving process cannot be executed from all distribution target apparatus groups that are distribution targets of update data. Identifying a distributable device excluding a specific device group including an image forming device of a direct lower hierarchy logically connected with the device as a vertex, and based on the number of models included in the distributable device, The distribution order of a plurality of types of update data is determined.
The invention of claim 2 is an image forming system having a plurality of types of image forming apparatuses logically connected in a hierarchical structure, the status acquisition means for acquiring each status of the plurality of types of image forming apparatuses, Based on the states acquired by the state acquisition unit, for each image forming apparatus, the determination unit determines whether or not update data reception processing regarding firmware can be executed, and the plurality of the plurality of the image forming apparatuses based on the determination result by the determination unit Determining means for determining the distribution order of a plurality of types of update data relating to firmware of an image forming apparatus of a different model, and image formation of a higher hierarchy directly logically connected according to the distribution order determined by the determining means Distribution control means for sequentially distributing the same type of update data from the apparatus to a plurality of lower-layer image forming apparatuses. The determining means is logically connected to the image forming apparatus determined by the determining means that the update data receiving process cannot be executed from all distribution target apparatus groups to which update data is distributed, with the image forming apparatus as a vertex. Identifying a distributable device that excludes a specific device group including an image forming device of a direct lower hierarchy, and based on the number of models included in the distributable device, the plurality of types of update data The delivery order is determined.

According to a third aspect of the present invention, in the image forming system according to the first or second aspect of the present invention, the determining means is provided in an image forming apparatus of the highest hierarchy logically connected in a hierarchical structure. And

According to a fourth aspect of the present invention, in the image forming system according to any one of the first to third aspects, the image forming system updates the plural types of firmware related to firmware of the plural types of image forming apparatuses. And a server for distributing data.

According to a fifth aspect of the present invention, in the image forming system according to the first or second aspect of the invention, the image forming system distributes the plurality of types of update data relating to firmware of the plurality of types of image forming apparatuses. And the determination means is provided in the server.

According to a sixth aspect of the present invention, in the image forming system according to any one of the first to fifth aspects, the image forming apparatuses other than the lowest layer in the hierarchical structure receive the update data distributed by the distribution control means. After the reception, the update data is transmitted to the lower-level image forming apparatus that is directly logically connected, and after the update data is transmitted, the firmware update operation of the own apparatus is performed using the update data It is characterized by performing.

According to a seventh aspect of the present invention, there is provided an image forming system having a plurality of types of image forming apparatuses logically connected in a hierarchical structure ; a) acquiring each state of the plurality of types of image forming apparatuses; b ) Based on the respective states acquired in the step a), for each image forming apparatus, a step for determining whether or not update data reception processing relating to firmware can be executed; and c) a determination result obtained in the step b). And a step of determining a distribution order of a plurality of types of update data relating to firmware of the plurality of types of image forming apparatuses, and d) a logical connection directly according to the distribution order determined in the step c). The same type of update data is simultaneously distributed from a higher level image forming apparatus to a plurality of lower level image forming apparatuses. Tsu a program for executing the flop, the determination, the in step c), from all the distribution target device group which is update data distribution target, in the step b) and not execute the update data receive processing A distributable device that excludes a specific device group including the image forming device and the image forming device of a direct lower hierarchy that is logically connected with the image forming device as a vertex, and is included in the distributable device The distribution order of the plurality of types of update data is determined based on the number of update data.
According to an eighth aspect of the present invention, for an image forming system having a plurality of types of image forming apparatuses logically connected in a hierarchical structure , a) acquiring each state of the plurality of types of image forming apparatuses; b ) Based on the respective states acquired in the step a), for each image forming apparatus, a step for determining whether or not update data reception processing relating to firmware can be executed; and c) a determination result obtained in the step b). And a step of determining a distribution order of a plurality of types of update data relating to firmware of the plurality of types of image forming apparatuses, and d) a logical connection directly according to the distribution order determined in the step c). The same type of update data is sequentially distributed from the upper layer image forming apparatus to a plurality of lower layer image forming apparatuses. A program for executing a step, wherein the in step c), is determined from all the distribution target device group which is update data delivery target, the can not perform the update data reception processing and the in step b) A distributable device is specified by excluding a specific device group including the image forming device and the image forming device of the direct lower hierarchy logically connected with the image forming device as a vertex, and the types of models included in the distributable device The distribution order of the plurality of types of update data is determined based on the number of units.
According to a ninth aspect of the present invention, in the program according to the seventh or eighth aspect of the invention, the step c) is executed by an image forming apparatus in the highest hierarchy logically connected in a hierarchical structure. .
According to a tenth aspect of the present invention, in the program according to the seventh or eighth aspect, the image forming system distributes the plurality of types of update data relating to firmware of the plurality of types of image forming apparatuses. The step c) is executed by the server.
According to an eleventh aspect of the present invention, in the program according to any one of the seventh to tenth aspects, the step d) is executed by an image forming apparatus other than the lowest hierarchy in the hierarchical structure, and the step d) D-1) after receiving update data distributed from another apparatus, transmitting the update data to the lower-level image forming apparatus directly logically connected to the apparatus; d -2) After the update data is transmitted in the step d-1), a firmware update operation of the device itself is executed using the update data.

According to a twelfth aspect of the present invention, there is provided an image forming apparatus that is one of a plurality of types of image forming apparatuses logically connected in a hierarchical structure, and that acquires each state of the plurality of types of image forming apparatuses Based on the status acquired by the status acquisition means, the determination means for determining whether or not update data reception processing regarding firmware can be executed for each image forming apparatus, and the determination result by the determination means. A plurality of types of update data distribution order relating to firmware of the plurality of types of image forming apparatuses; and a logical connection directly to the apparatus according to the distribution order determined by the determination means. Distribution control means for simultaneously distributing the same type of update data to a plurality of lower-level image forming apparatuses, The stage is logically connected to the image forming apparatus that is determined by the determining means that the update data receiving process cannot be executed from all distribution target apparatus groups that are distribution targets of update data, with the image forming apparatus as a vertex. A distributable device that excludes a specific device group including lower-level image forming devices is identified, and the distribution order of the plurality of types of update data is determined based on the number of models included in the distributable device. It is characterized by determining.
  According to a thirteenth aspect of the present invention, there is provided an image forming apparatus of any one of a plurality of types of image forming apparatuses logically connected in a hierarchical structure, wherein each of the plurality of types of image forming apparatuses is acquired. Based on the status acquired by the status acquisition means, the determination means for determining whether or not update data reception processing regarding firmware can be executed for each image forming apparatus, and the determination result by the determination means. A plurality of types of update data distribution order relating to firmware of the plurality of types of image forming apparatuses; and a logical connection directly to the apparatus according to the distribution order determined by the determination means. Distribution control means for sequentially distributing the same type of update data to a plurality of lower-level image forming apparatuses. The means is a direct system logically connected to the image forming apparatus determined by the determining means that the update data receiving process cannot be executed from all distribution target apparatus groups that are distribution targets of update data, with the image forming apparatus as a vertex. A distributable device that excludes a specific device group including lower-level image forming devices is identified, and the distribution order of the plurality of types of update data is determined based on the number of models included in the distributable device. It is characterized by determining.
  According to a fourteenth aspect of the present invention, in the image forming apparatus according to the twelfth or thirteenth aspect of the present invention, the image forming apparatus is an image forming apparatus of the highest hierarchy logically connected in a hierarchical structure. .
  According to a fifteenth aspect of the present invention, in the image forming apparatus according to any one of the twelfth to fourteenth aspects, the image forming apparatus updates the plurality of types of firmware relating to firmware of the plurality of types of image forming apparatuses. It is characterized by being connected to a network that distributes data.
  According to a sixteenth aspect of the present invention, in the image forming apparatus according to any one of the twelfth to fifteenth aspects, the image forming apparatus is directly logically connected after update data is received from another apparatus. The update data is transmitted to the lower-level image forming apparatus, and after the update data is transmitted, the update operation of the firmware of the own apparatus is executed using the update data.

According to the first to sixteenth aspects, data transmission processing to a relatively large number of child devices can be completed at an early stage. Therefore, efficient update processing can be executed.

1 is a diagram illustrating an image forming system. 2 is a functional block diagram illustrating a schematic configuration of an MFP. FIG. 3 is a flowchart showing the operation of the MFP. It is a flowchart which shows a part of operation | movement of FIG. It is a conceptual diagram which shows the delivery operation | movement (basic operation | movement) of the 1st update data. It is a conceptual diagram which shows the delivery operation | movement (basic operation | movement) of the 2nd update data. It is a conceptual diagram which shows the delivery operation | movement (basic operation | movement) of the 3rd update data. It is a figure which shows the operation | movement at the time of high load apparatus presence. It is a figure which shows the number of arrangement | positioning possible. It is a conceptual diagram which shows the delivery operation | movement (improvement operation | movement) of update data. It is a conceptual diagram which shows the delivery operation | movement (improvement operation | movement) of update data. It is a conceptual diagram which shows the delivery operation | movement (improvement operation | movement) of update data. It is a conceptual diagram which shows the delivery operation | movement of the update data after completion | finish of a high load process. It is a conceptual diagram which shows the delivery operation | movement of the update data after completion | finish of a high load process. It is a conceptual diagram which shows the delivery operation | movement of the update data after completion | finish of a high load process. It is a conceptual diagram which shows another delivery operation | movement after completion | finish of a high load process. It is a conceptual diagram which shows another delivery operation | movement after completion | finish of a high load process. It is a conceptual diagram which shows another delivery operation | movement after completion | finish of a high load process. It is a conceptual diagram which shows the operation | movement which concerns on a modification. It is a flowchart which shows the operation | movement which concerns on a comparative example.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

<1. Outline of configuration>
FIG. 1 is a diagram illustrating an image forming system 1. As shown in FIG. 1, the image forming system 1 includes a plurality of image forming apparatuses 10. The image forming system 1 also includes a server computer (also simply referred to as a server) 50.

  The elements 10 and 50 in the system 1 are connected to be communicable with each other via the network NW. The network NW is configured by a LAN (Local Area Network), the Internet, and the like. More specifically, the plurality of image forming apparatuses 10 are connected to a certain LAN (for example, an in-house network), and the server 50 is connected to a network outside the LAN. The image forming apparatus 10 and the server (also referred to as an external server) 50 are connected via a so-called Internet. A gateway server (also referred to as a gateway) GW or the like is provided between the image forming apparatus 10 and the server 50. Note that the connection mode to the network NW may be wired connection or wireless connection.

  In the system 1, firmware update data (update data) of each image forming apparatus 10 is distributed from the server computer 50 to each image forming apparatus 10. Therefore, the system 1 is also referred to as an update data distribution system, and the server 50 is also referred to as an update data distribution device.

  In this system 1, as shown in FIG. 1, a large number of image forming apparatuses 10 are logically connected in a multilayer structure (multiple layers) in a hierarchical structure.

  Here, among a large number of image forming apparatuses that are logically connected in multiple layers in a hierarchical structure, the apparatus is one level lower (hierarchy immediately below) of a predetermined apparatus and is directly logically connected to the predetermined apparatus. A device that is connected is referred to as a “child device” (or a transmission destination device) related to the predetermined device. Of a plurality of image forming apparatuses that are logically connected in multiple layers in a hierarchical structure, the apparatus is one level higher (upper hierarchy) than a predetermined apparatus and is directly logically connected to the predetermined apparatus. The device is referred to as a “parent device” (or source device) for the predetermined device. Hereinafter, the image forming apparatus 10 in the i-th layer LVi is also referred to as an apparatus ARi.

  In the system 1, a plurality of types of image forming apparatuses 10 are mixed. Here, it is assumed that the system 1 includes three types of image forming apparatuses 10 (models Sa, Sb, and Sc image forming apparatuses 10). In FIG. 1 and the like, the three models Sa, Sb, and Sc are distinguished from each other by giving different hatching to the three models Sa, Sb, and Sc. Specifically, a device with diagonal hatching (for example, device AR1 (AR10) of the highest hierarchy LV1) is a device of model Sa. A device with vertical line hatching (for example, a device AR2 (AR21) on the left side in the second layer LV2) is a device of model Sb, and a device with sandy hatching (for example, the third layer LV3). The leftmost device AR3 (AR31) and the like in FIG.

  Each image forming apparatus 10 in the system 1 knows both the “parent device” and the “child device” of its own device. Specifically, each image forming apparatus 10 stores hierarchical structure information HM in each storage unit 5 (FIG. 2) (described later). The hierarchical structure information HM stores the identification number and network address of the “parent device” of the image forming apparatus 10 and the identification number and network address of the “child device” of the image forming apparatus 10. The hierarchical structure information HM is generated according to an operation by an administrator or the like and is stored in advance in the image forming apparatus 10 (storage unit 5).

  In addition, each image forming apparatus 10 stores a hierarchical structure in all hierarchical levels lower than the own apparatus in each hierarchical structure information HM.

  Further, each image forming apparatus 10 stores the device type (model) in all layers lower than the own device in the respective hierarchical structure information HM. For example, the device AR1 of the highest hierarchy LV1 includes all lower hierarchy devices (specifically, not only the child device AR2 but also lower hierarchy devices AR3, AR4, AR5) in the hierarchical structure information HM of the device AR1. Device type information is stored. Similarly, the device AR2 of the second hierarchy LV2 includes all lower layer devices (specifically, devices including not only the child device AR3 but also lower layer devices AR4 and AR5) in the hierarchical structure information HM of the device AR2. ) (Especially the direct lower-layer device) is stored in the hierarchical structure information HM. However, the present invention is not limited to this. For example, only the device AR1 of the highest hierarchy LV1 may store the model information of all lower hierarchy devices in the hierarchy structure information HM. In other words, the lower layer devices below the second layer LV2 may not store the model information of all lower layer devices in the respective layer structure information HM.

  In the present system 1, first, the firmware of each image forming apparatus 10 is transferred from the server 50 to the image forming apparatus 10 (apparatus AR1 (AR10)) of the first hierarchy (the highest hierarchy) LV1 via the gateway GW. Update data is sent.

  Thereafter, the firmware update data of each image forming apparatus 10 is transmitted from the image forming apparatus 10 in the relatively higher hierarchy to the image forming apparatus 10 in the relatively lower hierarchy using the multi-layer logical connection. Specifically, the update data is transmitted from the parent device to the child device, and the update data is further transmitted from the child device to the child device (also referred to as a grandchild device) of the child device.

  For example, the image forming apparatus 10 (apparatus AR1) of the first hierarchy LV1 sends update data to the image forming apparatus 10 (apparatus AR2 (specifically AR21, AR22 in detail)) of the second hierarchy LV2, which is the “child device”. Send. Further, the image forming apparatus 10 (apparatus AR2 (AR21, AR22)) of the second hierarchy LV2 transmits update data to the image forming apparatus 10 (apparatus AR3) of the third hierarchy LV3 that is the respective “child device”. . More specifically, the device AR21 of the second hierarchy LV2 transmits update data to the image forming apparatus 10 (devices AR3 (AR31, AR32)) of the third hierarchy LV3 that is the “child device”. Similarly, the device AR22 of the second tier LV2 transmits update data to the image forming device 10 (device AR3 (AR33, AR34)) of the third tier LV3 that is the “child device”. Thereafter, the same operation is performed with respect to the lower hierarchy device. In this way, update data is sequentially transferred over a plurality of layers (a plurality of generations).

  As described above, in the present system 1, in the LAN, the image forming apparatus 10 (more specifically, “parent apparatus”) in the relatively higher hierarchy to the image formation apparatus 10 (more specifically, “child apparatus” in the relatively lower hierarchy). The update data is sequentially transmitted to “)”. According to this, the data transfer from the server 50 is only required for the first time. Therefore, it is possible to alleviate the load concentration on the server 50 (update data distribution device) as compared with the case where each image forming apparatus 10 individually receives update data directly from the server 50.

  In addition, a plurality of types of update data Da, Db, Dc related to a plurality of models Sa, Sb, Sc are not transmitted at the same time but are transmitted sequentially (in other words, in stages). A specific transmission operation will be described in detail later.

<2. Configuration of Image Forming Apparatus 10>
In this embodiment, an MFP (Multi-Functional Peripheral) is exemplified as the image forming apparatus 10.

  FIG. 2 is a functional block diagram illustrating a schematic configuration of the MFP 10. Here, the functional blocks of the MFP 10 (see FIG. 1) in the highest hierarchy (first hierarchy) LV1 will be mainly described. The MFPs 10 in the second and lower layers have the same configuration.

  The MFP 10 is a device (also referred to as a multi-function device) having a scan function, a copy function, a facsimile function, a box storage function, and the like. Specifically, as shown in the functional block diagram of FIG. 2, the MFP 10 includes an image reading unit 2, a print output unit 3, a communication unit 4, a storage unit 5, an input / output unit 6, a controller 9, and the like. Various functions are realized by operating these components in a complex manner.

  The image reading unit 2 optically reads (that is, scans) a document placed at a predetermined position of the MFP 10 and generates image data of the document (also referred to as a scanned image). It is. The image reading unit 2 is also referred to as a scanning unit.

  The print output unit 3 is an output unit that prints out an image on various media such as paper based on data related to a print target.

  The communication unit 4 is a processing unit capable of performing facsimile communication via a public line or the like. Further, the communication unit 4 can perform network communication via the network NW. In this network communication, for example, various protocols such as TCP / IP (Transmission Control Protocol / Internet Protocol) are used. By using the network communication, the MFP 10 can exchange various data with a desired destination.

  The storage unit 5 includes a storage device such as a hard disk drive (HDD). The storage unit 5 stores various data. For example, the storage unit 5 stores various setting information (including hierarchical structure information HM), image data relating to various jobs, and the like. In addition, update data UD (Da, Db, Dc) and the like related to the firmware (program) PG1 of the MFP 10 are also stored in the storage unit 5 (temporarily).

  The input / output unit 6 includes an operation input unit 6a that receives input to the MFP 10 and a display unit 6b that displays and outputs various types of information. The MFP 10 includes an operation panel unit 6c (not shown) having a touch panel (also referred to as a touch screen) configured by embedding a piezoelectric sensor or the like in a liquid crystal display panel. The operation panel unit 6c functions as a part of the operation input unit 6a and also functions as a part of the display unit 6b.

  The controller 9 is a control device that is built in the MFP 10 and controls the MFP 10 in an integrated manner. The controller 9 is configured as a computer system including a CPU and various semiconductor memories (RAM and ROM). The controller 9 implements various processing units by executing a predetermined software program (firmware or simply called a program) PG1 stored in a ROM (for example, EEPROM) in the CPU. Note that the program PG1 may be recorded on a portable recording medium such as a USB memory and installed in the MFP 10 via the recording medium. Alternatively, the program PG1 may be downloaded via the network NW or the like and installed in the MFP 10.

  As shown in FIG. 2, the controller 9 implements various processing units including a state acquisition unit 11, a state notification unit 12, a determination unit 13, a determination unit 14, and a distribution control unit 15 by executing a program PG1. To do.

  The state notification unit 12 is a processing unit that notifies the parent device 10 of the own device 10 of the load state (processing status) of the own device 10, and the state acquisition unit 11 indicates the load state of the child device 10 of the own device. It is a processing unit acquired from the child device 10. The state acquisition unit 11 of the parent device 10 and the state notification unit 12 of the child device 10 cooperate to acquire the load state of the child device 10 by the parent device 10. Further, by repeating such an operation in a relay manner over a plurality of generations, the relatively higher layer device 10 acquires the load states of the plurality of devices 10 in all the lower layers than the device. For example, the device AR1 (specifically, the state acquisition unit 11) of the highest hierarchy LV1 loads each load of not only the child device AR2 (AR21, AR22) but also a plurality of lower hierarchy devices (AR3, AR4, AR5). Also get the status.

  The determination unit 13 is a processing unit that determines whether or not the update data reception process (download process) can be executed in each of the plurality of lower layer devices based on the load state of the plurality of lower layer devices.

  The determination unit 14 determines the firmware FWa of the plurality of models Sa, Sb, and Sc based on the determination result of whether or not the update data reception process can be executed in each of the plurality of lower layer apparatuses related to the plurality of models Sa, Sb, and Sc. , FWb, FWc, a plurality of types of update data Da, Db, Dc are distributed. For example, the determination unit 14 of the device AR1 of the highest hierarchy LV1 selects a specific device group GP1 (distribution) from all distribution target device groups (device groups including all distribution target devices including a plurality of lower layers LV2 to LV5). A device group that includes devices that cannot perform operations (explained later) is excluded, and a distributable device is specified from the entire distribution target device group. And the said determination part 14 calculates | requires the number of deliverables (number of the deliverable apparatuses) for every some model. Furthermore, the determination unit 14 distributes a plurality of types of update data Da, Db, and Dc so that update data for each model is distributed in the order of models with the largest number of deliverables (number of deliverables for each model). The order (reception order (download order) and / or transmission order) is determined.

  The distribution control unit 15 is a processing unit that controls the distribution operation of update data. The distribution control unit 15 controls the update data distribution operation according to the distribution order determined by the determination unit 14.

  The distribution control unit 15 controls the operation of transmitting update data to the child device and the like, and also controls the operation of receiving update data from the parent device.

  Specifically, the distribution control unit 15 of the first layer device AR1 (parent device) further receives update data from the parent device (0th layer device (server 50)). Then, the distribution control unit 15 of the parent device (first layer device) AR1 further receives update data acquired from the parent device (0th layer device (server 50)) as a child device (second layer device) AR2. Deliver to.

  The distribution control unit 15 of the second layer device (new parent device) AR2 receives the update data from the parent device (first layer device) AR1. Then, the distribution control unit 15 of the new parent device (second layer device) AR2 uses the update data acquired from the parent device (first layer device) AR1 as the child device (third layer) of the device AR2. Device) is distributed to AR3.

  Further, the same operation is executed in each lower level apparatus.

  In this embodiment, the order of distribution of a plurality of types of update data Da, Db, Dc related to firmware of a plurality of models Sa, Sb, Sc is determined by the determination unit 14 of the device AR1 in the highest hierarchy. Further, not only the device AR1 (specifically, the distribution control unit 15) of the highest hierarchy LV1, but also the devices AR2, AR3, AR4, AR5 (specifically, the respective distribution control units 15) of the second and lower layers are the highest. A plurality of types of update data Da, Db, and Dc are distributed according to the distribution order determined by the determination unit 14 of the higher-layer apparatus AR1.

<3. Operation>
<3-1. Overview>
Next, the operation of the system 1 will be described in more detail with reference to FIGS. FIG. 3 is a flowchart showing an operation in the device AR1, and FIG. 4 is a flowchart showing a part of the operation.

  As described above, the plurality of image forming apparatuses 10 are logically connected in multiple layers (see FIG. 1). Then, after the update data is transmitted from the server 50 to the image forming apparatus 10 (AR1) of the highest hierarchy (first hierarchy) LV1, a terminal of a relatively lower hierarchy is transmitted from a terminal apparatus of a relatively higher hierarchy. Updater is sent to the device sequentially.

  Here, three types of update data Da, Db, and Dc have already been transmitted from the server 50 to the image forming apparatus 10 (apparatus AR1) of the first hierarchy (top hierarchy) LV1 via the gateway GW. It shall be. Then, the device AR1 of the first layer LV1 controls the operation of distributing update data to the plurality of lower layer devices AR2 to AR5 of the lower layers LV2 to LV5. In other words, the device AR1 of the first hierarchy LV1 controls the delivery operation regarding all delivery target devices (all delivery target device groups) including the plurality of lower layer devices AR2 to AR5. More specifically, the device AR1 of the first hierarchy LV1 determines the distribution order of the three types of update data Da, Db, Dc, and updates the update data to the child device AR2 (AR21, AR22) according to the distribution order. Da, Db, and Dc are transmitted. The devices AR2 to AR4 below the second hierarchy LV2 further transfer the update data Da, Db, Dc to their child devices according to the order transmitted from the device AR1. As a result, the update data transmitted in accordance with the distribution order is received by the devices AR1 to AR5 in all layers.

  A plurality of types of update data Da, Db, and Dc related to a plurality of models are not transmitted at the same time, but are transmitted sequentially (in other words, stepwise). Specifically, the first type of update data (update data for the first model) is transmitted from the highest-level device to the lowest-level device. Next, the second type of update data (update data for the second model) is transmitted from the highest-level device to the lowest-level device. Then, the third type of update data (update data for the third model) is transmitted from the highest level device to the lowest level device. In this way, the three types of update data are transmitted in the system 1 sequentially at independent timings. When a certain type of update data is transmitted from a certain parent device to the plurality of child devices, the certain type of update data is simultaneously transmitted from a certain parent device to a plurality of child devices. It may be transmitted, or may be transmitted sequentially (sequentially) from the parent device to a plurality of child devices.

  Also, here, the distribution order of the update data Da, Db, Dc related to the firmware FWa, FWb, FWc of the plurality of models Sa, Sb, Sc is the device AR1 of the highest hierarchy LV1 (specifically, the determination unit thereof) 14). However, the present invention is not limited to this, and the distribution order may be determined by the server 50.

<3-2. Comparative Example>
Here, before describing the operation according to the present embodiment, the operation according to the comparative example will be described. FIG. 20 is a flowchart showing the operation according to the comparative example.

  In steps S91 and S92 of FIG. 20, the distribution order of update data Da, Db, and Dc related to a plurality of models Sa, Sb, and Sc is determined.

  In this comparative example, the device AR1 of the highest hierarchy LV1 determines the distribution order of the plurality of types of update data Da, Db, Dc according to the number of devices of the lower hierarchy LV2 to LV5 of the device AR1 for each model. To do.

  Specifically, as shown in FIG. 20, first, in step S91, the device AR1 obtains the number of distribution target devices (distribution target devices that have not yet received the update data for the device itself) by model. To do. For example, when the update data has not been distributed to any device below the second layer, the device AR1 determines the number of models for all the devices in the lower layers LV2 to LV5 from the own device. Get based on. Specifically, in the system configuration as shown in FIG. 1, the number of devices of the first model Sa is 12, the number of devices of the second model Sb is 10, and the number of devices of the third model Sc. Is acquired that the number is eight.

  In the next step S92, the device AR1 has a plurality of models relating to firmware of a plurality of models Sa, Sb, Sc based on the number of distribution target devices for each model (here, the number of all lower layer devices for each model). The distribution order of the types of update data Da, Db, Dc is determined. Specifically, among the plurality of models Sa, Sb, and Sc, a higher priority is assigned in order from the model with the largest number, and a priority among the plurality of models Sa, Sb, and Sc is given. Based on the priorities among the plurality of models Sa, Sb, and Sc, the distribution order of the plurality of types of update data Da, Db, and Dc corresponding to each model is determined. Specifically, a relatively high distribution order is assigned to update data for a relatively high priority model.

  More specifically, update data corresponding to the model having the largest number among the three models Sa, Sb, and Sc is determined as the first rank distribution data. In the system configuration of FIG. 1, the number of model Sa is twelve, and the number of model Sa is the largest among the three models Sa, Sb, and Sc. Therefore, the update data Da corresponding to the model Sa is determined as the first rank delivery data. Next, the distribution data of each rank after the next rank (second rank) is also determined. Specifically, the number of model Sb is 10, and the number of model Sb is the second largest among the three models Sa, Sb, and Sc. Therefore, the update data Db corresponding to the next-order model Sb whose number is the second largest after the model Sa is determined as the second-order distribution data. Similarly, update data Dc corresponding to the next-ranked model Sc having the second largest number after the model Sb is determined as third-ranked distribution data.

  A plurality of types of update data Da, Db, and Dc corresponding to each model are distributed according to the distribution order between the models. This distribution operation starts in step S93 and continues until completion is confirmed in step S94.

  Specifically, first, as shown in FIG. 5, the distribution operation of the update data Da related to the model Sa is performed. Specifically, from the device AR1 (AR10) of the first layer (top layer) LV1, through the device AR2 of the second layer LV2, the device AR3 of the third layer LV3, and the device AR4 of the fourth layer LV4, the fifth It is sequentially delivered to the device AR5 of the hierarchy (lowest hierarchy) LV5. More specifically, the update data Da is sequentially transferred over a plurality of generations with branch distribution processing from a parent device in a relatively higher hierarchy to a plurality of child devices in a relatively lower hierarchy. When the device other than the model Sa (specifically, devices of the models Sb and Sc) receives the update data Da from the parent device, the device executes a transmission process of transmitting the received update data Da to the child device. On the other hand, when the device of model Sa receives the update data Da from its parent device, it executes the following operation. Specifically, the device of model Sa (for example, device AR22) executes a transmission process (transfer process) for transmitting update data Da received by the device to its child devices (for example, devices AR33 and AR34). At the same time, after the transfer process is completed, the update operation of the firmware of the own apparatus is executed using the update data Da. In this way, the distribution process of the update data Da to the 12 devices of the model Sa and the firmware update operation in the 12 devices are executed. Note that the transfer process to the child device is not performed by the lowest-layer device (hereinafter the same).

  Next, as shown in FIG. 6, the distribution operation of the update data Db related to the model Sb is performed. Similarly to the update data Da, the update data Db also changes from the device AR1 (AR10) of the first layer (top layer) LV1, the device AR2 of the second layer LV2, the device AR3 of the third layer LV3, and the fourth layer. It is sequentially delivered to the device AR5 of the fifth layer (lowest layer) LV5 via the device AR4 of LV4. When a device other than model Sb (specifically, devices of models Sa and Sc) receives update data Db from its parent device, it transmits the received update data Db to its child device (transfer processing). Execute. On the other hand, the device of model Sb executes the following operation when receiving update data Db from its parent device. Specifically, the device of model Sb (for example, device AR21) executes a transmission process for transmitting update data Db received by the device to its child devices (for example, devices AR31 and AR32) and transmits the transmission data After the processing is completed, the firmware update operation of the own device (for example, device AR21) is executed using the update data Db. In this way, the distribution process of the update data Db to the ten devices of the model Sb and the firmware update operation in the ten devices are executed.

  Thereafter, as shown in FIG. 7, an operation of distributing update data Dc related to the model Sc is performed. Specifically, the update data Dc is also the same as the update data Da, from the device AR1 (AR10) of the first layer (top layer) LV1, to the device AR2 of the second layer LV2, and the device AR3 of the third layer LV3. , And the device AR4 of the fourth hierarchy LV4, and sequentially delivered to the device AR5 of the fifth hierarchy (lowest hierarchy) LV5. When the device other than the model Sc (specifically, the devices of the models Sa and Sb) receives the update data Dc from the parent device, the device performs transfer processing for transmitting the update data Dc received by the device to the child device. Run. On the other hand, the device of the model Sc executes the following operation. Specifically, the device of model Sc (for example, device AR31) executes a transfer process for transmitting update data Dc received by the device to its child devices (for example, devices AR41 and AR42) and performs the transfer. After the processing is completed, the firmware update operation of the own device (for example, device AR31) is executed using the update data Dc. In this way, the distribution process of the update data Dc to the eight devices of the model Sc and the firmware update operation in the eight devices are executed.

  According to the operation as described above, by distributing the first update data Da among the three update data, distribution processing to a relatively large number (12 in FIG. 5) of devices 10 at the time when the distribution of the update data Da is completed. It is possible to complete. Therefore, it is possible to complete update data distribution processing for a relatively large number of devices at an early stage. On the other hand, when starting from the processing of the update data Dc in FIG. 7, only the distribution processing for a relatively small number (eight in FIG. 7) of devices 10 is completed when the distribution of the update data Dc is completed. Can not.

<3-3. Operation 1 according to Embodiment>
By the way, in any of the plurality of image forming apparatuses 10 in the system 1, high load processing such as FAX reception processing (processing of high load above a predetermined level) may be performed. An apparatus that performs such a high load process is also referred to as a “high load apparatus”.

  In such a high-load device, there are very few hardware resources available for the update data transmission / reception operation, and it may be difficult to execute the update data transmission / reception operation. Alternatively, even though the update data transmission / reception operation itself can be performed, it may be preferable that the update data transmission / reception operation is not performed at that time from the viewpoint of processing stability in the high-load device. .

  In consideration of such circumstances, in this embodiment, whether or not update data transmission / reception processing (particularly reception processing) can be performed in each of the plurality of lower layer devices is determined based on the load state of the plurality of lower layer devices. . Specifically, it is determined that the high-load device is a device that cannot execute update data reception processing due to its load state (high load state), and update data reception processing (update data download processing in the high-load device) ) Is prohibited. In other words, when high load processing is being executed in a certain device in the system, update data transmission processing to the device (high load device) is not performed. Along with this, update data transmission processing from the device to the lower layer device is also not performed.

  For example, in FIG. 8, when the device AR22 in the second layer is performing a high load process, the device AR22 and the devices AR3 (AR33, AR34), AR4 (AR45 to AR48) in the lower layer than the device AR22. , AR5 (AR519 to AR526) are temporarily excluded from the distribution destination of the update data. Then, among all the lower layer devices 10, devices other than the excluded devices (remaining devices) are determined as “distributable devices”. Specifically, the devices AR2 (AR21), AR3 (AR31, AR32), AR4 (AR41 to AR44), and AR5 (AR511 to AR518) are determined as “distributable devices”.

  However, in such a situation, the number of each model is calculated for all devices in the same manner as in FIGS. 5 to 7, and based on the distribution order determined according to the model order in which the number is large, When update data for a model is distributed, the following problems occur. Specifically, when such distribution processing is performed, as shown in FIG. 8, among the “distributable devices” (all 15 devices), the number of devices of the distribution target model Sa of the first rank is relatively small. (3 units). In this case, the delivery operation for preferentially delivering the update data Da related to the model Sa is not always efficient.

  Therefore, in this embodiment, a technique capable of more efficiently distributing a plurality of types of update data Da, Db, and Dc will be described. Specifically, the distribution order of a plurality of types of update data Da, Db, and Dc is determined in consideration of whether update data reception processing (download processing) can be performed in the lower-layer device. Hereinafter, such a technique will be described in detail with reference to FIG.

  First, as shown in step S11 of FIG. 3, the device AR1 of the highest hierarchy LV1 acquires the load status (processing status) of a plurality of lower hierarchy devices. Here, it is assumed that only the device AR22 among all the lower layer devices has been acquired.

  In the next step S12 (see also FIG. 4), the distribution order of the update data Da, Db, Dc related to the plurality of models Sa, Sb, Sc is determined.

  Also in this embodiment, as in the comparative example, the device AR1 of the highest hierarchy LV1 basically determines the distribution order of the plurality of types of update data Da, Db, Dc, and basically the lower hierarchy LV2 of the device AR1. This is determined according to the number of LV5 devices for each model. However, the following operations are different from the comparative example described above in consideration of whether or not update data reception processing (download processing) can be performed in the lower layer device.

  Specifically, (1) as shown in FIG. 4, first, in step S31, the device AR1 determines the number of distribution target devices (distribution target devices that have not yet received update data for the device itself) (number of distribution target numbers). (Also called). Here, the update data has not been distributed to any device below the second layer. Therefore, the device AR1 acquires the number of units for each model related to all devices in the lower hierarchy (LV2 to LV5) than the own device based on the hierarchical structure information HM. In other words, the device AR1 obtains the number of each model regarding all of a plurality of distribution target devices (a plurality of lower layer devices). In FIG. 8, as in FIG. 5, it is acquired that there are 12 model Sa devices, 10 model Sb devices, and 8 model Sc devices (the leftmost in FIG. 9). Column). In other words, the number of each model related to the device group GP0 (a plurality of non-distributed devices) to which update data is not distributed is obtained. The device group GP0 is composed of 30 devices excluding the device AR1 (AR10) among all 31 devices.

  (2) In the next step S32, it is determined whether or not there is a device (high load device) having a load state higher than a predetermined level (for example, the CPU resource usage rate (load factor) is 80%). If it is determined that there is no high load device, the process proceeds from step S32 (without proceeding to step S33) to step S34. On the other hand, if it is determined that there is a high load device, the process proceeds from step S32 to step S33. Here, it is assumed that apparatus AR22 is receiving a FAX (receiving a facsimile) and it is determined that the load factor of apparatus AR22 exceeds a reference value (for example, 80%). That is, it is determined that the high load device AR22 exists. Then, the process proceeds from step S32 to step S33. Thus, when there is a high load device AR22 having a load state higher than a predetermined level, it is determined that the high load device AR22 is a device that cannot execute the update data reception process due to the high load state. The process proceeds to step S33. Here, it is determined whether the device is a high load device based on the usage rate (load factor) of the CPU resource, but the present invention is not limited to this. For example, whether or not each device is a high load device may be determined based on the usage rate (load factor) of the memory resource of each device.

  In step S33, the device AR1 obtains the total number of the high load device AR22 and the devices directly below the high load device AR22 for each of a plurality of models Sa, Sb, and Sc. Specifically, the number of each model in the device group (group) GP1 within the range surrounded by the broken line in FIG. 8 is obtained. Here, the device group GP1 is composed of a high load device AR22 and devices in a direct lower layer of the high load device AR22 (AR33, AR34, AR45 to AR48, AR519 to AR526). The device group GP1 is also expressed as a direct device group (direct subordinate device group) having the high load device AR22 as a vertex. The number of devices for each model in the device group GP1 is calculated as nine devices of model Sa, five devices of model Sb, and one device of model Sc (center column in FIG. 9). reference).

  Note that since the update data addressed to the devices in the device group GP1 cannot be distributed, the device related to the device group GP1 is also referred to as a “distributable device”. The device group GP1 is also a device group composed of devices that cannot perform the update data distribution operation (particularly, the update data reception operation), and is therefore also expressed as a non-distributable device group. On the other hand, among the distribution target devices, devices other than the non-distributable devices are also referred to as “distributable devices”. Further, the number of non-distributable devices is also referred to as a non-distributable number, and the number of distributable devices is also referred to as a distributable number.

  Further, when there are a plurality of high-load devices, the direct subordinate device group relating to each of the plurality of high-load devices may be determined as a non-delivery device.

  (3) In step S34, the device AR1 obtains the number of models for each of the plurality of distributable devices. Specifically, for each model, the number obtained by subtracting the number obtained in (2) (the number that cannot be delivered) from the number obtained in (1) (the number to be delivered) is the number of deliverables (the number of deliverable devices). As per model. Specifically, the number of distributable devices of model Sa is 3 (= 12-9), the number of distributable devices of model Sb is 5 (= 10-5), and the distribution of model Sc It is acquired that the number of possible devices is 7 (= 8-1) (see the rightmost column in FIG. 9).

  In this way, the direct device group GP1 having the high load device AR22 as the apex is excluded, the “distributable device” is specified from the plurality of lower layer devices AR2 to AR5 of the device AR1, and the number of distributable devices is a plurality of models. Every one is required.

  (4) In step S35, the device AR1 (decision unit 14) sets the distribution order of the update data for the model in the order of the model having the largest number of deliverables (the number of deliverables for each model) of a plurality of types. It is determined as the “distribution order” regarding the update data Da, Db, Dc. Specifically, the number of distributable models Sc is 7, which is the largest of the distributable devices of the three models. In this case, the distribution order of the update data Dc related to the model Sc having the largest number of deliverables is determined as the first order. The model Sb has a distributable number (five), and is the model ranked next to the model Sc. The distribution order of the update data Db related to the model Sb is determined as the second order. In addition, the distribution order of the update data Da regarding the next-order model Sa having the number of distributable units (three) next to the model Sb is determined as the third order.

  In this way, a plurality of types of update data related to firmware of a plurality of models based on the determination result of whether or not the update data reception process (download process) can be performed in each of a plurality of lower layer apparatuses related to a plurality of models. The delivery order is determined. Specifically, when the “high load device” is present in all the lower layer devices, the determination unit 14 of the device AR1 includes the high load device and the high load device among all the lower layer devices. A distributable device is specified from all the lower layer devices, excluding the devices of the direct lower layer. Then, the determination unit 14 obtains the number of deliverables (number of deliverable devices) for each of a plurality of models, and distributes update data for the model in order from the model with the largest number of deliverables (number of deliverables for each model). The order to be performed is determined as a “distribution order” for a plurality of types of update data Da, Db, and Dc.

  Then, a plurality of types of update data Da, Db, Dc are transmitted to a plurality of lower layer devices in accordance with the distribution order (Dc, Db, Da) determined in this way. Specifically, in step S13, the distribution operation is started.

  FIG. 10 is a diagram illustrating a state in which the first rank update data Dc is first distributed. The update data Dc related to the model Sc includes the device AR1 (AR10) of the first layer (top layer) LV1, the device AR2 of the second layer LV2, the device AR3 of the third layer LV3, and the device AR4 of the fourth layer LV4. Then, it is sequentially delivered to the device AR5 of the fifth hierarchy (lowest hierarchy) LV5. More specifically, the update data Dc is sequentially transferred over a plurality of generations with branch distribution processing from a parent device in a relatively higher hierarchy to a plurality of child devices in a relatively lower hierarchy. However, the update data Dc is not distributed to the high load device AR22 and its direct lower layer device.

  Devices other than the model Sc (specifically, devices of the models Sa and Sb) execute transmission processing for transmitting the update data Dc received by the device to the child devices. On the other hand, the device of the model Sc (parent device) (for example, the device AR31) executes transmission processing (transfer processing) for transmitting the update data Dc received by the device to its child devices (for example, the devices AR41 and AR42). Then, after the transfer process is completed, the update operation of the firmware of the own device (for example, the device AR31) is executed using the update data Dc.

  By distributing the first update data Dc as described above, as shown in FIG. 10, the update data Dc for the own model Sc is sent to seven devices (AR31, AR41, AR42, AR511, AR512, AR515, AR516). Is delivered. Therefore, when the first update data Dc among the three update data is distributed, the distribution process for a relatively large number (seven in FIG. 10) of devices 10 can be completed as compared with FIG. . That is, it is possible to complete update data distribution processing for a relatively large number of devices at an early stage. As shown in FIG. 8, when the distribution process is started from another update data Da, a relatively small number (three in FIG. 8) of devices (AR513, AR514, when the distribution of the update data Da is completed). Only the distribution process for AR517) can be completed.

  FIG. 11 is a diagram illustrating a state in which the second-ranked update data Db is distributed. The update data Db related to the model Sb is also transmitted from the device AR1 (AR10) of the first layer (top layer) LV1, the device AR2 of the second layer LV2, the device AR3 of the third layer LV3, and the device AR4 of the fourth layer LV4. Then, it is sequentially delivered to the device AR5 of the fifth hierarchy (lowest hierarchy) LV5. More specifically, the update data Db is sequentially transferred over a plurality of generations with branch distribution processing from a parent device in a relatively higher hierarchy to a plurality of child devices in a relatively lower hierarchy. However, the update data Db is not distributed to the high load device AR22 and its direct lower layer device.

  Devices other than the model Sb (specifically, devices of the models Sa and Sc) execute a transmission process (transfer process) for transmitting the update data Db received by the apparatus to the child apparatus. On the other hand, the device of model Sb (for example, device AR32) executes transmission processing (transfer processing) for transmitting update data Da received by the device to its child devices (for example, devices AR43 and AR44), and performs the transfer. After the processing is completed, the firmware update operation of the own apparatus is executed using the update data Db. However, the lowest-layer device does not execute the transfer process to the child device (the same applies hereinafter).

  In this way, the second rank update data Db is distributed, and the update data Db for the own model Sb is distributed to five devices (AR21, AR32, AR43, AR44, AR518).

  FIG. 12 is a diagram illustrating a state in which the third rank update data Da is distributed. The update data Da related to the model Sa also includes the device AR1 (AR10) of the first layer (top layer) LV1, the device AR2 of the second layer LV2, the device AR3 of the third layer LV3, and the device AR4 of the fourth layer LV4. Then, it is sequentially delivered to the device AR5 of the fifth hierarchy (lowest hierarchy) LV5.

  More specifically, the update data Da is sequentially transferred over a plurality of generations with branch distribution processing from a parent device in a relatively higher hierarchy to a plurality of child devices in a relatively lower hierarchy. However, the update data Da is not distributed to the high load device AR22 and its direct lower layer devices.

  In principle, each type of device executes transmission processing (transfer processing) for transmitting update data received by the device to its child devices. Further, after receiving the update data Da from the parent device (for example, the device AR42), the device of model Sa (for example, the device AR513) uses the update data Da to update the firmware of its own device. Run. Since the device AR513 is the lowest-level device and does not have the child device, the transfer process from the device AR513 to the child device is not executed.

  In this way, the third rank update data Da is distributed, and the update data Da for the model Sa is distributed to the three devices (AR513, AR514, AR517).

  Thereafter, standby processing is executed until the high load state of the device AR22 returns to the non-high load state (see steps S14, S15, and S19 in FIG. 3). In other words, the standby process is continued until the load state of the device AR22 returns to a state lower than the predetermined level and update data reception processing in the high load device becomes possible.

  When it is determined in step S15 that the device AR22 has returned from the high load state to the non-high load state, the process proceeds to step S16. In step S16, the same operation as in step S11 is executed. Thereafter, the process proceeds to step S17. In step S17, the distribution order of a plurality of types of update data is determined for the device group GP1 that has not yet received the update data when the device AR22 returns to the non-high load state. A plurality of types of update data Da, Db, and Dc are distributed to the device group GP1 according to the distribution order. In step S17, the same operation as in step S12 is performed.

  Specifically, (1) First, in step S31 (FIG. 4), the device AR1 has not yet received update data for its own device among all device groups to which update data has not been distributed (all distribution target device groups). No distribution target device group) (here, device group GP1), the number of each model is obtained. Specifically, it is acquired that there are nine devices of type Sa, five devices of type Sb, and one device of type Sc (see FIG. 13).

  (2) Next, it is determined in step S32 that the load state of the device AR22 has returned to the non-high load state and no other high load device exists, and the process proceeds to step S34.

  (3) In step S34, the device AR1 acquires the number of distributable devices of each model. Specifically, the number of distributable devices of model Sa is 9 (= 9-0), the number of distributable devices of model Sb is 5 (= 5-0), and the distribution of model Sc The number of possible devices is calculated as 1 (= 1-0).

  (4) In step S35, the device AR1 (decision unit 14) sets the order in which update data for the model is distributed in order from the model having the largest number of deliverables (number of deliverables for each model) to a plurality of types. Are determined as the “distribution order” for the update data Da, Db, and Dc. Specifically, the number of distributable models Sa is nine, which is the largest of the three distributable devices of the three models. Therefore, the distribution order of the update data Dc related to the model Sa having the largest number of deliverables is determined as the first order. In addition, the distribution order of the update data Db related to the next-order model Sb having the number of distributable units (five) next to the model Sa is determined to be the second order. In addition, the distribution order of the update data Dc related to the next-order model Sc having the number of distributable units (one) next to the model Sb is determined as the third order.

  Then, a plurality of types of update data are transmitted to each device in the device group GP1 in accordance with such a distribution order. Specifically, in step S18, the distribution operation is started. If update data being distributed exists, the update data distribution operation is continued as it is thereafter. Then, the operation of distributing update data other than the update data being distributed is subsequently executed. Here, as described above, the distribution operation of update data Da, Db, Dc for all models to devices other than device group GP1 has been completed, and distribution of update data Da, Db, Dc for all models to device group GP1 has been completed. The mode by which operation | movement is started is illustrated.

  FIG. 13 is a diagram illustrating a state in which the first rank update data Da is distributed. The update data Da related to the model Sa is transmitted from the device AR1 (AR10) of the first layer (top layer) LV1, the device AR2 (AR22) of the second layer LV2, the device AR3 (AR33, AR34) of the third layer LV3, and It is sequentially delivered to the device AR5 (AR521, AR522, AR525, AR526) of the fifth layer (lowest layer) LV5 via the device AR4 (AR46, AR48) of the fourth layer LV4. More specifically, the update data Da is sequentially transferred over a plurality of generations with branch distribution processing from a parent device in a relatively higher hierarchy to a plurality of child devices in a relatively lower hierarchy. Devices other than the model Sa (specifically, devices of the models Sb and Sc) execute update data Da transfer processing to the child devices. On the other hand, when the distribution of the update data Da to the device (parent device) (for example, the device AR22) of the model Sa ends (for example, the devices AR33 and AR34), the device Sa (for example, the device AR22) uses the update data Da. The firmware update operation of the device AR22) is also executed.

  By distributing the update data Da, the update data Da for the own model Sa is distributed to nine devices (AR22, AR33, AR34, AR46, AR48, AR521, AR522, AR525, AR526). Therefore, after the high load device AR22 returns to the normal state, the distribution of the first update data Da among the three update data results in the completion of the distribution of the first update data, and the remaining 15 distribution target devices. The distribution process for a relatively large number (nine in FIG. 13) of the apparatuses 10 can be completed. That is, it is possible to complete update data distribution processing for a relatively large number of devices at an early stage.

  FIG. 14 is a diagram illustrating a state in which the second-ranked update data Db is distributed. The update data Db related to the model Sb is similarly performed. Specifically, the update data Db is sequentially transferred over a plurality of generations with branch distribution processing from a parent device in a relatively higher hierarchy to a plurality of child devices in a relatively lower hierarchy.

  In this way, the second rank update data Db is distributed, and the update data Db for the own model Sb is distributed to five devices (AR45, AR47, AR520, AR523, AR524).

  FIG. 15 is a diagram showing a state in which the third rank update data Dc is distributed. The update data Dc related to the model Sc is similarly performed. Specifically, the update data Dc is sequentially transferred over a plurality of generations with branch distribution processing from a parent device in a relatively higher hierarchy to a plurality of child devices in a relatively lower hierarchy.

  In this way, the third rank update data Dc is distributed, and the update data Dc for the own model Sc is distributed to one device (AR 519).

  As described above, when the distribution operation for all the lower-level devices is completed (step S14), the operation of FIG. 3 is completed.

<3-4. Operation 2 according to Embodiment>
In the above, when the high load device AR22 exists, the high load device AR22 is transmitted after all three types of update data Da, Db, Dc are transmitted to the devices other than the device group GP1 among all devices. A situation in which the high load state is resolved is illustrated.

  In the case where the high load device AR22 exists, the high load device AR22 is high after one (or two) of the three types of update data Da, Db, Dc is transmitted to the devices other than the device group GP1 among all devices. When the high load state of the load device AR22 is resolved, the following distribution operation may be performed.

  In the following, when there is a high load device AR22, one of the three types of update data Da, Db, Dc (specifically, one type) for all devices except the device group GP1. The case where the high load state of the high load device AR22 is resolved during the transmission of the update data Dc only) is illustrated.

  Specifically, when the high load device AR22 exists, it is determined that a plurality of update data Dc, Db, Da should be distributed in this order, as described above. Then, during the distribution operation of the first update data Dc (FIG. 10), it is assumed that the load state of the high load device AR22 returns to the normal state (non-high load state). In the following description, the distribution operation after completion of the distribution operation of the update data Dc is determined in a state where the distribution operation of the update data Dc is not completed.

  At the time of returning to the non-high load state, the device AR1 re-determines the distribution order for the device group GP2 (step S17). Here, the device group GP2 is the device of the seven models Sc (AR31, AR41, AR42, AR511, to which the update data Dc for its own model has already been distributed among the device group GP0 composed of 30 devices. It is composed of 23 devices excluding AR512, AR515, AR516). That is, the device group GP2 is a device group including devices that have not yet received update data for the device itself (for the device model). At the time of returning to the non-high load state, the update data Dc that is being distributed is distributed to the devices of the seven models Sc (AR31, AR41, AR42, AR511, AR512, AR515, AR516). It is almost fixed. Therefore, the device AR1 assumes that the update data Dc for its model has already been distributed to the seven devices, and the other 23 devices after the distribution of the update data Dc to the seven devices is completed. Re-determine the distribution order of update data for

Specifically, (1) First, in step S31, the device AR1 is a device group to which update data has not yet been distributed (distribution target device that has not yet received its own update data among all distribution target device groups. Group) (here, device group GP2), the number of each model is obtained. Specifically, it is acquired that there are 12 devices of model Sa, 10 devices of model Sb, and 1 device of model Sc. (2) Next, the load state of device AR22 is non-high load It is determined in step S32 that the state has returned to the state and no other high load device exists, and the process proceeds to step S34.

  (3) In step S34, the device AR1 acquires the number of distributable devices of each model. Specifically, the number of distributable devices of model Sa is 12 (= 12-0), the number of distributable devices of model Sb is 10 (= 5-0), and the distribution of model Sc The number of possible devices is calculated as 1 (= 1-0).

  (4) In step S35, the device AR1 (decision unit 14) sets the order in which update data for the model is distributed in order from the model having the largest number of deliverables (number of deliverables for each model) to a plurality of types. Are determined as the “distribution order” for the update data Da, Db, and Dc. Specifically, the distribution order of the update data Da related to the model Sa having the largest distributable number (12 units) among the distributable numbers of the three models is determined as the first rank. In addition, the distribution order of the update data Db related to the next-order model Sb having the number of deliverables (10) next to the model Sa is determined as the second order. In addition, the distribution order of the update data Dc related to the next-order model Sc having the number of distributable units (one) next to the model Sb is determined as the third order.

  Then, a plurality of types of update data are transmitted to each device in the device group GP2 in accordance with such a distribution order (step S18). However, here, as described above, the high load device AR22 returns to the non-high load state during the distribution of the update data Dc to the devices other than the device group GP1, and the distribution operation of the update data Dc being distributed at the time of the return is performed. Will continue. Then, after the distribution operation of the update data Dc to devices other than the device group GP1 is completed, new distribution operations of the three types of update data Da, Db, and Dc to the device group GP2 are started. The new distribution operation is executed according to the distribution order newly determined in step S35.

  FIG. 16 is a diagram illustrating a state in which the first rank update data Da is distributed. The update data Da relating to the model Sa is sequentially transferred over a plurality of generations while branch distribution processing is performed from a parent device in a relatively higher hierarchy to a plurality of child devices in a relatively lower hierarchy. .

  In this way, the first rank update data Da is distributed, and to 12 devices (AR22, AR33, AR34, AR46, AR48, AR513, AR514, AR517, AR521, AR522, AR525, AR526) Update data Da for its own model Sa is distributed.

  According to this, after the high load device AR22 returns to the normal state, a relatively large number of the 23 distribution target devices (12 in FIG. 16) are distributed by distributing the first update data Da among the three update data. ) For the device 10 can be completed. That is, it is possible to complete update data distribution processing for a relatively large number of devices at an early stage.

  FIG. 17 is a diagram illustrating a state in which the second rank update data Db is distributed. The distribution operation of the update data Db related to the model Sb is performed in the same manner. Specifically, the update data Db is sequentially transferred over a plurality of generations with branch distribution processing from a parent device in a relatively higher hierarchy to a plurality of child devices in a relatively lower hierarchy.

  In this way, the second-ranked update data Db is distributed, and for 10 devices (AR21, AR32, AR43, AR44, AR45, AR47, AR518, AR520, AR523, AR524) for the own model Sb. Update data Db is distributed.

  FIG. 18 is a diagram illustrating a state in which the third rank update data Dc is distributed. The distribution operation of the update data Dc related to the model Sc is similarly performed. Specifically, the update data Dc is sequentially transferred over a plurality of generations with branch distribution processing from a parent device in a relatively higher hierarchy to a plurality of child devices in a relatively lower hierarchy.

  In this manner, the third rank update data Dc is distributed, and the update data Dc for the own model Sc is distributed to the remaining one device (AR519).

<4. Modified example>
Although the embodiments of the present invention have been described above, the present invention is not limited to the contents described above.

  For example, in the above-described embodiment, an apparatus “fax receiving” is detected as a high-load apparatus. However, the present invention is not limited to this, and preview processing (“real-time preview” using the operation panel unit 6 c of the image forming apparatus 10 is not limited thereto. ") A running device may be detected as a high load device. Alternatively, a device that is executing the OCR process may be detected as a high-load device. In addition, a device that is executing two or more of the plurality of types of processing may be detected as a high-load device.

  Then, it is determined that the update data transmission process for the high load device is prohibited (the update data reception process cannot be executed in the high load device), and based on the number of deliverables acquired according to the determination result, The distribution order of a plurality of types of update data Da, Db, Dc may be determined.

  Further, in the above-described embodiment, the device other than the lowest layer exemplifies a mode in which all types of received update data Da, Db, and Dc are transferred to the child device. However, the present invention is not limited to this. For example, a certain device (a specific device) is a device group including the child device (transfer destination device) and its direct lower layer device (hereinafter referred to as a direct lower layer device group related to the transfer destination device). It is also possible to transfer only update data for models existing in the

  For example, only two models Sa and Sc exist in the direct lower layer device group related to the child device (transfer destination device) AR31 of the device AR21. In this case, the device AR21 may transfer only the update data Da and Dc for the two models Sa and Sc to the child device (transfer destination device) AR31. In other words, the update data Dc for one other model Sb may not be transferred to the lower layer device AR31. According to this, useless transfer processing can be reduced.

  In the above-described embodiment, each image forming apparatus 10 exemplifies a mode in which the device types (models) of devices in all layers lower than the self-device are known. However, the present invention is not limited to this. For example, only the device AR1 at the highest layer knows the device type (model) of the devices at all lower layers than the own device, and the other devices may not know the model of the lower layer device. Good.

  In the above-described embodiment, distribution is performed in a state where the device AR1 of the highest hierarchy LV1 is not included in the entire distribution target device group (specifically, in a state where the total distribution target device group is configured only by the device group GP0). Although the target number and the number of deliverables are calculated, the present invention is not limited to this. For example, in a state where the device AR1 of the highest hierarchy LV1 is included in the all distribution target device group (specifically, in a state where the device AR1 is added to the device group GP0 to configure the entire distribution target device group), The number of deliverable units may be calculated. In particular, when update data is not yet distributed from the external server 50 to the device AR1, the number of distribution targets is calculated including the device AR1 of the highest hierarchy LV1, and the device AR1 of the highest hierarchy LV1 is included. It is preferable that the number of deliverables is calculated.

  More specifically, as shown in FIG. 10, when a high load device (AR22) determined not to be able to execute update data reception processing is present in a plurality of lower layer devices, distribution is performed as follows. The target device may be specified. Specifically, a total of 31 devices including the device AR1 itself as well as the lower-layer devices AR2 to AR5 of the device AR1 may be specified as the distribution target devices (distribution target device group). Then, from these distribution target devices (all distribution target device groups), a device group GP1 (a device group including a total of 15 high load devices AR22 and direct lower layer devices of the high load devices AR22) is excluded. Thus, it is only necessary to specify a distributable device.

  In this case, the situation of FIG. 10 differs from that of FIG. 9 in that it is determined that the number of models Sa to be arranged is 13 and the number of models Sa that can be arranged is 4. The other numbers are the same as in FIG.

  Then, the determination unit 14 of the device AR1 determines the distribution order based on the number of distributable devices (distributable number) so that the update data for each model is distributed in the order of the models with the largest number of distributable devices. decide.

  Furthermore, the distribution control unit 15 of the device AR1 controls not only the update data distribution operation to the plurality of lower layer devices AR2 to AR5 (from the server 50) but also the update data distribution operation to the device AR1 itself. In FIG. 19, the update data Dc is distributed from the server 50 to the device AR1, and the update data Dc is distributed from the device AR1 to the lower layer devices AR2 to AR5 using the hierarchical structure. It is shown. The same applies to the other update data Db and Da. For example, the update data Db may be distributed from the server 50 to the device AR1, and the update data Db may be distributed from the device AR1 to the lower layer devices AR2 to AR5 using a hierarchical structure.

  Further, after the load state of the high load device AR22 returns to a predetermined level or less and the update data reception process in the high load device AR22 can be executed, the distribution target device group is also specified by adding the device AR1. What should I do? Further, the devices that can be distributed so as to include the high load device AR22 and the devices in the direct lower hierarchy of the high load device AR22 among the devices that have not yet received the update data for the own device in the distribution target device group. Need only be identified. And the delivery order after a return should just be determined based on the number etc. of the said delivery possible apparatus.

  In the above embodiment, the mode in which the device AR1 of the first layer LV1 determines the distribution order of the update data to the plurality of lower layer devices below the second layer LV2 is exemplified, but the present invention is not limited to this. For example, the distribution order of update data may be determined by the device AR2 of the second hierarchy LV2 to a plurality of lower hierarchy devices below the third hierarchy LV3 (direct hierarchy devices of the device AR2).

  In the above-described embodiment, a mode in which a plurality of image forming apparatuses 10 are logically connected in a five-layer hierarchical structure is illustrated, but the present invention is not limited to this. For example, a plurality of image forming apparatuses 10 may be logically connected with a hierarchical structure of four layers or less, or may be logically connected with a hierarchical structure of six layers or more.

  Moreover, in the said embodiment, although the mode by which two child apparatuses are logically connected with respect to one parent apparatus is illustrated, it is not limited to this. For example, three or more child devices may be logically connected to one parent device. Also, it is not necessary that a plurality of child devices are logically connected to all parent devices. For example, only a single child device is logically connected to some parent devices. Also good. However, in order to improve the transfer efficiency of update data, it is preferable to perform a branch transfer process of update data by logically connecting a plurality of “child devices” to a relatively large number of parent devices. In other words, it is preferable that the hierarchical structure is defined so that the number of relatively lower layer devices is larger than the number of relatively higher layer devices.

  In the above embodiment, the MFP is exemplified as the image forming apparatus 10, but the present invention is not limited to this, and the above-described idea is applied to various image forming apparatuses (printing apparatus, copying apparatus, scanner apparatus, etc.). It may be applied.

1 image forming system 10 MFP (image forming apparatus)
50 Server computer ARi Device in layer i Da, Db, Dc Update data GP0 Device group composed of all lower layer devices of device AR1 GP1 Direct device group having high load device AR22 as a vertex GW Gateway HM Hierarchical structure information Sa , Sb, Sc models

Claims (16)

An image forming system having a plurality of types of image forming apparatuses logically connected in a hierarchical structure,
Status acquisition means for acquiring the statuses of the plurality of types of image forming apparatuses;
Based on the respective states acquired by the state acquisition unit, for each image forming apparatus, a determination unit that determines whether update data reception processing relating to firmware can be executed,
A determination unit that determines a distribution order of a plurality of types of update data related to firmware of the plurality of types of image forming apparatuses based on a determination result by the determination unit;
Distribution control means for simultaneously distributing update data of the same type from a directly upper logically connected image forming apparatus to a plurality of lower hierarchical image forming apparatuses in accordance with the distribution order determined by the determining means When,
With
The determination means is logically connected to the image forming apparatus determined by the determining means that the update data receiving process cannot be executed from all distribution target apparatus groups that are distribution targets of update data, with the image forming apparatus as a vertex. A plurality of types of update data is distributed based on the number of models included in the distributable device. An image forming system characterized by determining an order. An image forming system having a plurality of types of image forming apparatuses logically connected in a hierarchical structure,
Status acquisition means for acquiring the statuses of the plurality of types of image forming apparatuses;
Based on the respective states acquired by the state acquisition unit, for each image forming apparatus, a determination unit that determines whether update data reception processing relating to firmware can be executed,
A determination unit that determines a distribution order of a plurality of types of update data related to firmware of the plurality of types of image forming apparatuses based on a determination result by the determination unit;
Distribution that sequentially distributes the same type of update data from a directly upper logically connected image forming apparatus to a plurality of lower hierarchical image forming apparatuses in accordance with the distribution order determined by the determining means Control means;
With
The determination means is logically connected to the image forming apparatus determined by the determining means that the update data receiving process cannot be executed from all distribution target apparatus groups that are distribution targets of update data, with the image forming apparatus as a vertex. A plurality of types of update data is distributed based on the number of models included in the distributable device. An image forming system characterized by determining an order. The image forming system according to claim 1 or 2,
The image forming system according to claim 1, wherein the determining means is provided in an image forming apparatus of the highest hierarchy logically connected in a hierarchical structure. The image forming system according to any one of claims 1 to 3,
The image forming system includes:
A server that distributes the plurality of types of update data relating to firmware of the plurality of types of image forming apparatuses;
An image forming system comprising: The image forming system according to claim 1 or 2,
The image forming system includes:
A server that distributes the plurality of types of update data relating to firmware of the plurality of types of image forming apparatuses;
With
The image forming system, wherein the determination unit is provided in the server. The image forming system according to any one of claims 1 to 5,
Image forming apparatuses other than the lowest hierarchy in the hierarchical structure
After receiving the update data distributed by the distribution control means, send the update data to the lower-level image forming apparatus that is directly logically connected,
An image forming system, wherein after the update data is transmitted, a firmware update operation of the own apparatus is executed using the update data. For an image forming system having a plurality of types of image forming apparatuses logically connected in a hierarchical structure ,
a) acquiring each state of the plurality of types of image forming apparatuses;
b) determining whether or not to execute update data reception processing relating to firmware for each image forming apparatus based on the respective states acquired in step a);
c) determining a distribution order of a plurality of types of update data related to firmware of the plurality of types of image forming apparatuses based on the determination result in the step b);
d) According to the distribution order determined in the above step c), the same type of update data is simultaneously distributed from the upper level image forming apparatus directly logically connected to a plurality of lower level image forming apparatuses. Steps,
A program for executing
In step c), the image forming apparatus determined in step b) that the update data receiving process cannot be executed from all distribution target apparatus groups to which update data is distributed and the image forming apparatus as a vertex are logically processed. A plurality of types of updates are identified based on the number of models included in the distributable device, wherein a distributable device is specified excluding a specific device group including a connected direct lower layer image forming device. A program characterized in that a data distribution order is determined. For an image forming system having a plurality of types of image forming apparatuses logically connected in a hierarchical structure ,
a) acquiring each state of the plurality of types of image forming apparatuses;
b) determining whether or not to execute update data reception processing relating to firmware for each image forming apparatus based on the respective states acquired in step a);
c) determining a distribution order of a plurality of types of update data related to firmware of the plurality of types of image forming apparatuses based on the determination result in the step b);
d) In accordance with the distribution order determined in the step c), the same type of update data is sequentially transmitted from the upper-level image forming apparatus directly logically connected to the plurality of lower-level image forming apparatuses. Delivering, and
A program for executing
In step c), the image forming apparatus determined in step b) that the update data receiving process cannot be executed from all distribution target apparatus groups to which update data is distributed and the image forming apparatus as a vertex are logically processed. A plurality of types of updates are identified based on the number of models included in the distributable device, wherein a distributable device is specified excluding a specific device group including a connected direct lower layer image forming device. A program characterized in that a data distribution order is determined. In the program according to claim 7 or 8,
The step c) is executed by an image forming apparatus of the highest hierarchy logically connected in a hierarchical structure. In the program according to claim 7 or 8,
The image forming system includes:
A server that distributes the plurality of types of update data relating to firmware of the plurality of types of image forming apparatuses;
With
The step c) is executed by the server. The program according to any one of claims 7 to 10,
Step d) is executed by an image forming apparatus other than the lowest hierarchy in the hierarchical structure,
Said step d)
d-1) after receiving update data distributed from another apparatus, transmitting the update data to an image forming apparatus in a lower hierarchy directly logically connected to the apparatus;
d-2) After the update data is transmitted in the step d-1), performing an update operation of the firmware of the own device using the update data;
The program characterized by having. An image forming apparatus of any one of a plurality of types of image forming apparatuses logically connected in a hierarchical structure,
Status acquisition means for acquiring the statuses of the plurality of types of image forming apparatuses;
Based on the respective states acquired by the state acquisition unit, for each image forming apparatus, a determination unit that determines whether update data reception processing relating to firmware can be executed,
A determination unit that determines a distribution order of a plurality of types of update data related to firmware of the plurality of types of image forming apparatuses based on a determination result by the determination unit;
Distribution control means for simultaneously distributing update data of the same type to a plurality of lower-level image forming apparatuses that are directly logically connected to the apparatus according to the distribution order determined by the determination means;
With
The determination means is logically connected to the image forming apparatus determined by the determining means that the update data receiving process cannot be executed from all distribution target apparatus groups that are distribution targets of update data, with the image forming apparatus as a vertex. A plurality of types of update data is distributed based on the number of models included in the distributable device. An image forming apparatus that determines an order. An image forming apparatus of any one of a plurality of types of image forming apparatuses logically connected in a hierarchical structure,
Status acquisition means for acquiring the statuses of the plurality of types of image forming apparatuses;
Based on the respective states acquired by the state acquisition unit, for each image forming apparatus, a determination unit that determines whether update data reception processing relating to firmware can be executed,
A determination unit that determines a distribution order of a plurality of types of update data related to firmware of the plurality of types of image forming apparatuses based on a determination result by the determination unit;
Distribution control means for sequentially distributing the same type of update data to a plurality of lower-level image forming apparatuses that are directly logically connected to the apparatus according to the distribution order determined by the determination means;
With
The determination means is logically connected to the image forming apparatus determined by the determining means that the update data receiving process cannot be executed from all distribution target apparatus groups that are distribution targets of update data, with the image forming apparatus as a vertex. A plurality of types of update data is distributed based on the number of models included in the distributable device. An image forming apparatus that determines an order. The image forming apparatus according to claim 12 or 13,
The image forming apparatus is an image forming apparatus of the highest hierarchy logically connected in a hierarchical structure. 15. The image forming apparatus according to claim 12, wherein:
The image forming apparatus is connected to a server that distributes the plurality of types of update data related to firmware of the plurality of types of image forming apparatuses via a network. The image forming apparatus according to any one of claims 12 to 15,
The image forming apparatus includes:
After the update data is received from the other device, the update data is transmitted to the lower-level image forming device that is directly logically connected,
An image forming apparatus, wherein after the update data is transmitted, an update operation of firmware of the apparatus is executed using the update data.