JP2006178892A - Software update device and method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a software update device and method that enable reduced update operations and a recovery from failed update operations without requiring a special management server or function. <P>SOLUTION: If software in an MFP machine is updated normally, each subnet of devices is searched for MFP machines of the same model as the MFP machine, software versions in the MFP machines are checked, and the software is delivered to software-deliverable MFP machines of the same model. If a defect is detected in the software, the software-delivered MFP machines are instructed to stop the software update. If the software in the MFP machine is updated abnormally, each subnet of devices is searched for MFP machines of the same model as the MFP machine, the software is acquired from the MFP machines, and the acquired software is updated again. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a software update apparatus and method, and more particularly, to a software update apparatus and method for updating software of an image processing apparatus main body connected via a network and peripheral devices connected thereto.

  In recent communication and information processing systems, etc., the program is often updated in a timely manner in order to change the system characteristics.

  For example, there is a POS system that can reduce the work by distributing the update file mainly on the host that manages the update and managing the result, so that the operator does not need to perform the update work on each device. (For example, refer to Patent Document 1).

In addition, for example, by having a redundant storage device in consideration of the case where a failure occurs in the updated version, in the unlikely event that a failure occurs due to an update, the program failure autonomous recovery that continues operation by switching to the backed up software There is a system (for example, refer to Patent Document 2).
Japanese Patent Application Laid-Open No. 5-183606 Japanese Patent Laid-Open No. 10-105407

  However, in the technique described in Patent Document 1, in a network environment where a printer, a multifunction printer, or the like is installed, a management server cannot always be installed, and it is not always possible to connect to an external management server. Therefore, it is not always possible to provide an update device tailored to the customer's environment.

  Further, the technique described in Patent Document 2 has a problem in that the storage device is duplicated, resulting in an increase in cost and a complicated mechanism for switching.

  Therefore, in view of the above problems, the present invention provides a software update apparatus and method that enables reduction of update work and recovery of update work failure without requiring a special management server or function. Objective.

  In order to achieve the above object, the invention of claim 1 is a software updating apparatus for controlling software updating of a device connected to a network, wherein software updating means for controlling software updating of the apparatus, and software for updating in the apparatus are provided. When updated normally, the same model searching means for searching for devices of the same model as the devices from the various devices on the network, and the update software is distributed to the devices of the same model searched by the same model searching means And software distribution means.

  The invention of claim 2 further comprises device table creation means for creating a device table related to a device of the same model searched by the same model search means in the invention of claim 1, wherein the same model search means comprises: Information on the device is acquired from the searched device of the same model, and the device table creation means records the information on the device of the same model acquired by the device of the same model in the device table.

  According to a third aspect of the present invention, in the second aspect of the present invention, the software distribution means compares the versions of the device and the same model device based on the device table, and determines the same version. The update software is distributed to a model device.

  The invention of claim 4 further comprises update result receiving means for receiving the update result of the update software from a device of the same model that delivered the update software by the software distribution means in the invention of claim 1. When the update result is unsuccessful, the software distribution unit redistributes the update software to a device of the same model that failed to be updated.

  According to a fifth aspect of the present invention, in the first aspect of the invention, the software distribution means updates the update software for a device of the same model that has distributed the update software until a predetermined time elapses. It is characterized by instructing to wait.

  Further, in the invention of claim 6, in the invention of claim 5, when a defect is found in the update software updated by the device before the predetermined time elapses, the software distribution means causes the update software to Update instruction means for instructing the apparatus of the same model that distributed the software to stop updating the update software.

  According to a seventh aspect of the present invention, in a software update apparatus that controls software update of a device connected to a network, a software update unit that controls software update of the device and an update history table relating to the software update history of the device are created. The update history table creating means, and when the update software is not normally updated in the device, the device of the same model as the device is searched from various devices on the network, and the device of the same model searched for Based on the same model search means for acquiring the information of the device, the device table creation means for creating a device table related to the information of the same model device searched by the same model search means, the update history table and the device table Check for devices of the same model that have the desired version of software, and ; And a software acquisition unit that the device of the same model that obtains the software, the software update means may be updated desired version of the software acquired by the software acquisition unit to the device.

  The invention of claim 8 is characterized in that, in the invention of claim 7, the same model having the desired version of software is instructed to prohibit software update.

  The invention according to claim 9 is the invention according to claim 7, wherein when the update of the desired version of the software has failed, the software acquisition means re-acquires the software from a device of the same model having the software. The software update means causes the device to re-update the desired version of software re-acquired by the software acquisition means.

  According to a tenth aspect of the present invention, there is provided a software update device for controlling software update of a device connected to a network, before updating software for update in the device, software update means for controlling software update of the device, Same model search means for searching for devices of the same model as all devices from various devices on the network, and software transmission means for transmitting pre-update software of the device to the same model devices searched by the same model search means And software acquisition means for acquiring the pre-update software from the same model apparatus that has transmitted the pre-update software by the software transmission means when the update software is not normally updated in the apparatus, The software update means is the software acquisition means. The resulting pre-update software and wherein the to be updated to the device.

  The invention of claim 11 further comprises a device table creating means for creating a device table relating to a device of the same model searched by the same model searching means in the invention of claim 10, wherein the same model searching means comprises: Information on the device is acquired from the searched device of the same model, and the device table creation means records the information on the device of the same model acquired by the device of the same model in the device table.

  Further, in the invention of claim 12 according to the invention of claim 10, when the update of the pre-update software fails, the software acquisition means re-reads the pre-update software from the same model device having the pre-update software. The software update means acquires the software before update reacquired by the software acquisition means, and causes the apparatus to update again.

  According to a thirteenth aspect of the present invention, in the software update method for controlling software update of a device connected to a network, the update software is updated in the device, and the update software is normally updated in the device. And searching for a device of the same model as the device from various devices on the network, and distributing the update software to the searched device of the same model.

  The invention of claim 14 is characterized in that, in the invention of claim 13, information of the device is acquired from the searched device of the same model, and the acquired information of the device of the same model is recorded in a device table. And

  According to a fifteenth aspect of the present invention, in the invention of the fourteenth aspect, the versions of the device and the device of the same model are compared based on the device table, and the update is made to the device of the same model determined as the same version. It is characterized by distributing software.

  Further, in the invention of claim 16, in the invention of claim 13, when the update result of the software is received from a device of the same model that delivered the update software, and the received update result is unsuccessful, the update is performed. The update software is redistributed to a failed device of the same model.

  According to a seventeenth aspect of the present invention, in the thirteenth aspect of the present invention, the same type of device that has distributed the update software is instructed to wait until a predetermined time elapses to update the update software. It is characterized by that.

  Further, the invention of claim 18 is the same model as that of the invention of claim 17, in which, when a defect is found in the update software updated by the device before the predetermined time has passed, the update software is distributed. The update software is instructed to stop updating the update software.

  The invention of claim 19 is a software update method for controlling software update of a device connected to a network, causing the device to update software for update, creating an update history table related to the software update history of the device, When the update software is not normally updated in the device, the device of the same model as the device is searched from various devices on the network, the information of the device is acquired from the searched device of the same model, and the device Create a device table related to the information of the acquired device of the same model, confirm the device of the same model having the desired version of software based on the update history table and the device table, from the confirmed device of the same model The desired version of software is acquired, and the acquired desired version of software It characterized in that for updating the device.

  The invention of claim 20 is characterized in that, in the invention of claim 19, instructing prohibition of software update to the same model having the desired version of software.

  Further, in the invention of claim 21, in the invention of claim 19, when the update of the desired version of the software fails, the software is reacquired from the same model device having the software, and the reacquired desired The version of the software is updated again by the apparatus.

  According to a twenty-second aspect of the present invention, there is provided a software updating method for controlling software updating of a device connected to a network, wherein the same model as all devices is selected from various devices on the network before the updating software is updated in the device. The device is searched for, and the pre-update software of the device is transmitted to the searched device of the same model, and the update software for all devices is updated by the device, and the update software is not updated normally in the device. In this case, the pre-update software is obtained from the same model device that transmitted the pre-update software, and the obtained pre-update software is updated by the device.

  The invention of claim 23 is characterized in that, in the invention of claim 22, information on the device is acquired from the searched device of the same model, and the acquired information on the device of the same model is recorded in a device table. And

  Further, in the invention of claim 24, in the invention of claim 22, when the update of the pre-update software fails, the pre-update software is re-acquired from the same model device having the pre-update software, and the re-acquisition The pre-update software is updated by the apparatus.

  According to the present invention, it is possible to reduce software update work without requiring a special management server device or function, and further, software update work can be performed by automatically detecting a device to be updated. In addition, it is possible to reduce the software, and even if the update fails, it is possible to reliably update the software of the device connected to the system by performing the re-execution.

  Further, according to the present invention, it is possible to recover the failure of the software update work without requiring a special management server device or function, and further, it is possible to reduce the software update work. Further, it is possible to reduce the downtime of the apparatus due to the failure of the software update work, and it is possible to minimize the influence on the business.

  Further, according to the present invention, there is an effect that it is possible to immediately stop without updating the software by performing software update after waiting for a certain period of time.

  DESCRIPTION OF EMBODIMENTS Hereinafter, embodiments of a software updating apparatus and method according to the present invention will be described in detail with reference to the accompanying drawings. As an embodiment of the present invention, a system composed of a plurality of multifunction printers (hereinafter referred to as MFPs) and a plurality of subnets connected to a plurality of printers will be described as an example.

  FIG. 1 is a block diagram showing an example of the overall configuration of a system to which the present invention is applied.

  As shown in FIG. 1, the system includes a plurality of subnets 1, and each subnet 1 processes an MFP 2 that can process a plurality of functions such as copying, printing, scanning, and faxing, and a printing function. The printer machine 3 that can be connected is connected. A software updating apparatus according to the present invention is connected to or built in the MFP 2 or the Printer 3 existing in this system.

  In the first embodiment, when the MFP machine 2 to which the software update apparatus according to the present invention is connected performs software update, the same software is applied to the MFP machine 2 of the same model in which the software update apparatus exists in the system. An embodiment for distributing and updating will be described.

  FIG. 2 is a block diagram illustrating an example of a functional configuration of the software update device 4 according to the first embodiment.

  As shown in FIG. 2, the MFP machine 2 is connected to or includes a software update apparatus 4 according to the present invention. The MFP machine 2 has communication with the software update apparatus 4, software update, and the MFP machine 2. Control of a control unit (not shown) for various services (copying, printing, scanning, faxing, etc.), MFP machine main control unit 6 for exchanging with peripheral devices 5 connected to the MFP machine 2, etc., on each subnet 1 And an I / F [Interface] 7 for transmitting / receiving various data to / from the MFP machine 2, the printer machine 3, and the like.

  Next, a functional configuration of the software update device 4 will be described.

  As shown in FIG. 2, the software update device 4 includes a software update unit 8, a same model search unit 9, a device table creation unit 10, a software distribution unit 11, and an update result reception unit 12.

  The software update unit 8 performs processing for causing the MFP device 2 to update the update software. Specifically, the update software is transferred to the MFP main control unit 6 and the MFP main control unit 6 performs an update of the update software.

  The same model search unit 9 searches for an MFP machine 2 of the same model as the MFP machine 2 from a device connected to each subnet 1 when the update software for the MFP machine 2 is normally updated. A process for confirming the software version of the MFP 2 of the same model is performed. Note that there are “automatic search within the same subnet”, “automatic search within a designated subnet”, and “search for a designated device” as search methods for the MFP 2 of the same model. This will be described later.

  The device table creation unit 10 performs processing for creating and storing a device table that records device information including the model information of the MFP 2 of the same model searched by the same model search unit 9 and the software version.

  The software distribution unit 11 determines whether or not the distribution is possible based on the comparison of the main body version or the like from the device information of the MFP model 2 of the same model recorded in the device table creation unit 10, and the MFP model 2 of the same model that can be distributed. Process to distribute software for update.

  The update result receiving unit 12 performs a process of receiving an update result transmitted from the MFP 2 of the same model to which the software distribution unit 11 has distributed the update software. The update result received by the update result receiving unit 12 is transferred to the device table creating unit 10, and the device table creating unit 10 records the update result in the device table.

  Next, a software distribution processing procedure performed by the software updating apparatus will be described with reference to the flowcharts shown in FIGS.

  The software update unit manually updates the software (hereinafter referred to as a connection device) connected to the software update device by the user (step S301), and the software update unit automatically reboots the connection device (step S302) to connect. If the booting of the device and the start of the service have failed (NO in step S303), the process proceeds to step S304. If the booting of the connected device and the start of the service have been successful (YES in step S303), the process proceeds to step S305.

  If the connection device boot and service start fail (NO in step S303), the software update failure is notified to the user (step S304), and the software distribution processing procedure ends.

  If the connection device boot and service start are successful (YES in step S303), the same model search unit performs the same model search process as a subroutine (step S305), and the device table creation unit creates and stores the device table. (Step S306), the software distribution unit starts a distribution loop (Step S307), and the software distribution unit searches for the connection device and the same model search unit by the software distribution unit (hereinafter referred to as the same type device). Are compared (step S308), and the software distribution unit determines that the main unit software can be distributed (YES in step S309), the process proceeds to step S310, and the software distribution unit does not distribute the main unit software. If it is determined that it is possible (NO in step S309), step S31 Proceed to.

  If the software distribution unit determines that the main body software can be distributed (YES in step S309), the software distribution unit distributes the main body software to the same model device (step S310), and the process proceeds to step S311.

  When the software distribution unit compares the peripheral device versions of the peripheral device of the connected device and the peripheral device of the same model device (step S311), and the software distribution unit determines that the peripheral device software can be distributed (step S312). In step S313, if the software distribution unit determines that the peripheral device software cannot be distributed (NO in step S312), the process proceeds to step S314.

  If the software distribution unit determines that the peripheral device software can be distributed (YES in step S312), the software distribution unit distributes the peripheral device software to the same model device (step S313), and the process proceeds to step S314.

  If the distribution loop of the software distribution unit is completed (YES in step S314), the process proceeds to the flowchart shown in FIG. 4. If the distribution loop of the software distribution unit is not completed (NO in step S314), step S308 is performed. Return to.

  When the distribution loop of the software distribution unit is completed (YES in step S314), the process proceeds to the flowchart shown in FIG. 4, the update result reception unit starts the update result reception loop (step S401), and the update result reception unit distributes the software. The update result is received from the device (hereinafter referred to as a distribution device) (step S402). If the received update result is successful (YES in step S403), the process proceeds to step S406, and the received update result is unsuccessful. (NO in step S403), the process proceeds to step S404.

  If the received update result is unsuccessful (NO in step S403), if re-execution is less than the specified number of times (YES in step S404), proceed to step S405, and if re-execution is more than the specified number of times (step (NO in S404), the process proceeds to step S406.

  If the re-execution is less than the specified number of times (YES in step S404), the software distribution unit redistributes the software to the distribution device (step S405), and the process proceeds to step S406.

  Then, the device table creation unit records the update result of the distribution device in the device table (step S406), and when the update result reception loop of the update result reception unit ends (YES in step S407), the process proceeds to step S408, If the update result receiving loop of the update result receiving unit has not ended (NO in step S407), the process returns to step S402.

  When the update result reception loop of the update result receiving unit is completed (YES in step S407), the update results of all the distribution devices are notified to the user (step S408), the connection device is shifted to the normal service mode (step S409), The software distribution processing procedure ends.

  Note that, as a re-execution method of update for a distribution apparatus that failed to be updated, there are “repeat the distribution until the update is successful” and “repeat the distribution as many times as specified by the user”.

  Next, the processing procedure of the same model search process performed by the same model search unit in step S305 of the flowchart shown in FIG. 3 will be described with reference to the flowchart shown in FIG.

  When a search method for a device of the same model as the device connected to the software update device (hereinafter referred to as a device of the same model) is selected (step S501), and the search method is “automatic search within the same subnet” (in step S502). If YES, the process proceeds to step S503, and if the search method is not “automatic search within the same subnet” (NO in step S502), the process proceeds to step S506.

  When the search method is “automatic search within the same subnet” (YES in step S502), the search packet is broadcasted in the same subnet (step S503), the return packet is received (step S504), and the address of the return packet The model is confirmed (step S504), and the process proceeds to step S514.

  If the search method is not “automatic search in the same subnet” (NO in step S502), if the search method is “automatic search in the designated subnet” (YES in step S506), the process proceeds to step S507. If the search method is not “automatic search in the designated subnet” (NO in step S506), the process proceeds to step S510.

  When the search method is “automatic search in the designated subnet” (YES in step S506), the search packet is transmitted by broadcast in the designated subnet (step S507), the reply packet is received (step S508), and the reply packet is transmitted. The model is confirmed from the address (step S509), and the process proceeds to step S514.

  If the search method is not “automatic search in the designated subnet” (NO in step S506), if the search method is “search for the designated device” (YES in step S510), the process proceeds to step S511. If the search method is not “search for specified device” (NO in step S510), the process returns to step S502.

  When the search method is “search for specified device” (YES in step S510), the search packet is transmitted to the address of the specified device (step S511), a reply packet is received (step S512), and the reply packet is transmitted. The model is confirmed from the address (step S513), and the process proceeds to step S514.

  Then, a version acquisition loop is started (step S514), a main body software version confirmation packet is transmitted to the same model device (step S515), and a main body software version information packet is received from the same model device (step S516). When the peripheral device software version confirmation packet is transmitted to the model device (step S517), the peripheral device software version information packet is received from the same model device (step S518), and the version acquisition loop is not completed (step S519). NO), the process returns to step S515, and if the version acquisition loop is ended (YES in step S519), the processing procedure of the same model search process is ended.

  Next, a software update processing procedure performed by a device to which software is distributed from the software update device will be described with reference to a flowchart shown in FIG.

  A software update request is received from the software updating apparatus (step S601), the job acceptance is terminated (step S602), and if there is no job being processed or waiting (YES in step S603), the process proceeds to step S605. If there is a job being processed or waiting (NO in step S603), the process advances to step S604.

  When there is a job being processed or waiting (NO in step S603), the job end event is waited (step S604), and the process returns to step S603.

  If there is no job being processed or waiting (YES in step S603), the main body software for update is received from the software update device (step S605), the version to be updated is confirmed (step S606), and the update is possible (step S606). If YES in step S607), the process proceeds to step S608. If update is not possible (NO in step S607), the process proceeds to step S609.

  If it can be updated (YES in step S607), the main body software is updated (step S608), and the process proceeds to step S609.

  Then, the peripheral device software for update is received from the software update device (step S609), the version to be updated is confirmed (step S610), and if it can be updated (YES in step S611), the process proceeds to step S612, and the update is performed. If not possible (NO in step S611), the process proceeds to step S613.

  If it can be updated (YES in step S611), the peripheral device software is updated (step S612), and the process proceeds to step S613.

  Then, automatic reboot is performed (step S613). If the boot and service start are successful (YES in step S614), the process proceeds to step S617. If the boot and service start fails (NO in step S614), step is performed. The process proceeds to S615.

  If the boot and service start fails (NO in step S614), the mode is changed to the forced update mode (step S615), the update result is transmitted to the software update device (step S616), and the process returns to step S605.

  When the boot and the service start are successful (YES in step S614), the update result is transmitted to the software update device (step S617), and the software update processing procedure is terminated.

  FIG. 7 is a diagram illustrating an example of the device table 13.

  As shown in FIG. 7, in the device table 13, the device number, network address, model, main body ID, main body version, peripheral device ID, peripheral device version, and other device information of each device, the update result of the main body software, and the peripheral Device software update results are recorded.

  Accordingly, it is possible to reduce the software update work without requiring a special management server device or function, and further, the software update work can be reduced by automatically detecting a device to be updated. Further, even if the update fails, it is possible to update the software of the device connected to the system reliably by performing the re-execution.

  In the second embodiment, when the MFP machine to which the software update apparatus according to the present invention is connected performs software update and a defect is detected in the software, the software update apparatus is recovered from the same type MFP machine existing in the system. An embodiment for acquiring software for use will be described.

  FIG. 8 is a block diagram illustrating an example of a functional configuration of the software update device 4 according to the second embodiment.

  As shown in FIG. 8, the MFP machine 2 is connected or built in the software update apparatus 4 according to the present invention. The MFP machine 2 has communication with the software update apparatus 4, software update, and the MFP machine 2. Control of a control unit (not shown) for various services (copying, printing, scanning, faxing, etc.), MFP machine main control unit 6 for exchanging with peripheral devices 5 connected to the MFP machine 2, etc., on each subnet 1 I / F [Interface] 7 for transmitting and receiving various data to and from other devices.

  Next, a functional configuration of the software update device 4 will be described.

  As shown in FIG. 8, the software update device 4 includes a software update unit 8, a model search unit 9, a device table creation unit 10, an update history table creation unit 14, and a software acquisition unit 15.

  The software update unit 8 performs processing for causing the MFP device 2 to update the update software. Specifically, the update software is transferred to the MFP main control unit 6 and the MFP main control unit 6 performs an update of the update software.

  The same model search unit 9 searches for an MFP machine 2 of the same model as the MFP machine 2 from the devices connected to each subnet 1 when a defect is detected in the update software updated by the MFP machine 2. Processing for confirming the software version of the MFP 2 of the same model that has been processed and searched is performed. Note that the search method for the MFP model 2 of the same model includes “automatic search within the same subnet”, “automatic search within a designated subnet”, and “search for a designated device”.

  The device table creation unit 10 performs processing for creating and storing a device table that records device information including the model information of the MFP 2 of the same model searched by the same model search unit 9 and the software version.

  The update history table creation unit 14 creates and stores an update history table that records the history of software updates of the MFP 2.

  The software acquisition unit 15 performs processing for requesting software transmission to the MFP device 2 of the same model, and processing for receiving software transmitted from the MFP device 2 of the same model that requested the software transmission.

  Next, a software recovery processing procedure performed by the software updating apparatus will be described with reference to flowcharts shown in FIGS.

  The software update unit manually updates the software (hereinafter referred to as a connection device) connected to the software update device by the user (step S901), and the software update unit automatically reboots the connection device (step S902) to establish a connection. If the device boot or service start fails (NO in step S903), the process proceeds to step S905. If the connection device boot and service start is successful (YES in step S903), the process proceeds to step S904.

  If the connection device boot and service start are successful (YES in step S903), the connection device is shifted to the normal service mode (step S904), and the software recovery processing procedure is terminated.

  If the connection device boot and service start are successful (YES in step S903), the same model search unit performs the same model search process as a subroutine (step S905), and the device table creation unit creates and stores the device table. (Step S906), the recovery version is collected from the update history table (Step S907), and it is confirmed whether the recovery version exists in the device table (Step S908). If the recovery version exists in the device table (YES in Step S909) ), The process proceeds to the flowchart shown in FIG. 10, and if the restoration version does not exist in the device table (NO in step S909), the process proceeds to step S910.

  If the recovery version does not exist in the device table (NO in step S909), the user is notified that the recovery version does not exist (step S910), and the software recovery processing procedure ends.

  When the restoration version exists in the device table (YES in step S909), the process proceeds to the flowchart shown in FIG. 10, and the software acquisition unit is a device of the same model as the connection device searched by the same model search unit (hereinafter referred to as the same model device). ) Request the transmission of the main body software (step S1001), the software acquisition unit receives the main body software from the same model device (step S1002), and the software update unit updates the main body software of the connection device (step S1003). The software acquisition unit requests the same model device to transmit peripheral device software (step S1004), the software acquisition unit receives the peripheral device software from the same model device (step S1005), and the software update unit determines the peripheral device of the connected device. Peripheral software update In step S1006), the update history table creation unit records the updated version in the update history table (step S1007), and the software update unit automatically reboots the connection device (step S1008), and the connection device boots and the service starts successfully. If yes (YES in step S1009), the process proceeds to step S1010. If booting of the connection device and service start have failed (NO in step S1009), the process proceeds to step S1012.

  When the connection device boots and the service starts successfully (YES in step S1009), the update history table creation unit records the update result in the update history table (step S1010), and shifts the connection device to the normal service mode (step S1010). S1011), the software recovery processing procedure is terminated.

  When the connection device boot and service start fail (NO in step S1009), the process proceeds to the forced update mode (step S1012), and the update history table creation unit records the update result in the update history table (step S1013). If the re-execution is less than the specified number of times (YES in step S1014), the process proceeds to step S1001, and if the re-execution is the specified number of times or more (NO in step S1014), the software recovery processing procedure is terminated.

  The restoration version determination method includes “same version as before update” and “version within a range designated by the user”.

  In addition, as a re-execution method of the update when the update fails, there are “repeat until the update is successful” and “repeat as many times as specified by the user”.

  The processing procedure of the same model search process performed by the same model searching unit in step S905 of the flowchart shown in FIG. 9 is the same as the processing procedure of the flowchart shown in FIG.

  Next, a software transmission processing procedure performed by a device requested to transmit software by the software update device will be described with reference to a flowchart shown in FIG.

  When a request for software transmission is received from the software update device (step S1101) and the request is for distribution of main body software (YES in step S1102), the process proceeds to step S1103, and when it is a request for distribution of peripheral device software (NO in step 1102), the process proceeds to step S1108.

  If it is a request for distribution of the main software (YES in step S1102), the requested version is confirmed (step S1103). If the versions match (YES in step S1104), the process proceeds to step S1105, and the versions match. If not (NO in step S1104), the process proceeds to step S1107.

  If the versions match (YES in step S1104), the main body software is packaged (step S1105), the main body software is transmitted to the software updating apparatus (step S1106), and the software transmission processing procedure is terminated.

  If the versions do not match (NO in step S1104), a transmission error is transmitted to the software update device (step S1107), and the software transmission processing procedure is terminated.

  If it is a request for distribution of peripheral device software (NO in step 1102), the requested version is confirmed (step S1108). If the versions match (YES in step S1109), the process proceeds to step S1110, and the version is If they do not match (NO in step S1109), the process advances to step S1107.

  If the versions match (YES in step S1109), the peripheral device software is requested from the peripheral device (step S1110), the peripheral device software is acquired from the peripheral device (step S1111), and the peripheral device software is transmitted to the software update device. (Step S1112), the software transmission processing procedure is terminated.

If the versions do not match (NO in step S1109), a transmission error is transmitted to the software update device (step S1107), and the software transmission processing procedure is terminated. Accordingly, the software is not required without requiring a special management server device or function. It becomes possible to recover the failure of the update work, further reduce the software update work, and further reduce the downtime of the device due to the failure of the software update work. In addition, it is possible to minimize the impact on business.

  In the third embodiment, when an MFP machine to which the software updating apparatus according to the present invention is connected performs software updating, the software is backed up to the same type of MFP machine existing in the system, and a defect is detected in the software. In this case, an embodiment for acquiring backed up software will be described.

  FIG. 12 is a block diagram illustrating an example of a functional configuration of the software update device 4 according to the third embodiment.

  As shown in FIG. 12, the MFP machine 2 is connected to or includes a software update apparatus 4 according to the present invention. The MFP machine 2 has communication with the software update apparatus 4, software update, and the MFP machine 2. Control of a control unit (not shown) for various services (copying, printing, scanning, faxing, etc.), MFP machine main control unit 6 for exchanging with peripheral devices 5 connected to the MFP machine 2, etc., on each subnet 1 I / F [Interface] 7 for transmitting and receiving various data to and from other devices.

  Next, a functional configuration of the software update device 4 will be described.

  As shown in FIG. 12, the software update device 4 includes a software update unit 8, a homogeneous model search unit 9, a device table creation unit 10, a software transmission unit 16, an update history table creation unit 14, and a software acquisition unit 15. .

  The software update unit 8 performs processing for causing the MFP device 2 to update the update software. Specifically, the update software is transferred to the MFP main control unit 6 and the MFP main control unit 6 performs an update of the update software.

  The same model search unit 9 searches for an MFP machine 2 of the same model as the MFP machine 2 from the devices connected to each subnet 1 and searches for the MFP machine 2 before causing the MFP machine 2 to update the update software. Processing for confirming the software version of the MFP 2 of the same model is performed. Note that the search method for the MFP model 2 of the same model includes “automatic search within the same subnet”, “automatic search within a designated subnet”, and “search for a designated device”.

  The device table creation unit 10 performs processing for creating and storing a device table that records device information including the model information of the MFP 2 of the same model searched by the same model search unit 9 and the software version.

  The software transmission unit 16 performs processing for transmitting the update software to the MFP 2 of the same model recorded in the device table creation unit 10.

  The update history table creation unit 14 creates and stores an update history table that records the history of software updates of the MFP 2.

  The software acquisition unit 15 performs a process of requesting software transmission to the MFP machine 2 that backed up the software, and a process of receiving software transmitted from the MFP machine 2 that requested the software transmission.

  Next, software backup and software recovery processing procedures performed by the software updating apparatus will be described with reference to the flowcharts shown in FIGS.

  The same model search unit performs the same model search process as a subroutine (step S1301), the device table creation unit creates and stores the device table (step S1302), and connects to the software update device (hereinafter referred to as the connection device). The same model device of the same version as that of the current main body software is searched (step S1303), and if the same model device of the same version exists (YES in step S1304), the process proceeds to step S1305, and If there is no version of the same model device (NO in step S1304), the process advances to step S1306.

  If the same model device of the same version exists (YES in step S1304), the same model device is instructed to prohibit updating of the main body software (step S1305), and the process proceeds to step S1307.

  If the same model device of the same version does not exist (NO in step S1304), the software transmission unit transmits the main body software to the same model device for backup (step S1306), and the process proceeds to step S1307.

  Then, the same model device of the same version as the current peripheral device software is searched (step S1307), and if the same model device of the same version exists (YES in step S1308), the process proceeds to step S1309, and the same device If there is no version of the same model device (NO in step S1308), the process advances to step S1310.

  If the same model device of the same version exists (YES in step S1308), the same model device is instructed to prohibit updating of the main body software (step S1309), and the process proceeds to step S1311.

  If the same model device of the same version does not exist (NO in step S1308), the software transmission unit transmits the main body software to the same model device for backup (step S1310), and proceeds to step S1311.

  Then, the software update unit updates the main body software of the connection device (step S1311), the software update unit updates the peripheral device software of the connection device (step S1312), and the update history table creation unit updates the update history table. The software update unit automatically reboots the connection device (step S1314). If the connection device boots and the service starts successfully (YES in step S1315), the process proceeds to step S1316. If the connection device boot and the service start fail (NO in step S1315), the process proceeds to the flowchart shown in FIG.

  If the connection device boots and the service starts successfully (YES in step S1315), the update history table creation unit records the update result in the update history table (step S1316), and backs up the software (hereinafter referred to as a backup device). (In step S1317), the connected device is shifted to the normal service mode (step S1318), and the software backup processing procedure is terminated.

  When the connection device boot and the service start fail (NO in step S1315), the process proceeds to the flowchart shown in FIG. 14 and shifts to the recovery update mode (step S1401), and the update history table creation unit updates the update history table. (Step S1402), the software acquisition unit requests the backup device to transmit the main body software (step S1403), the software acquisition unit receives the main body software from the backup device (step S1404), and the software update unit receives the connection device. (Step S1405), the software acquisition unit requests the backup device to transmit peripheral device software (step S1406), and the software acquisition unit receives the peripheral device software from the backup device ( (Step S1407), the software update unit updates the peripheral device software of the peripheral device of the connected device (step S1408), the update history table creation unit records the updated version in the update history table (step S1409), and the software update unit Automatically reboots the connection device (step S1410), and when the connection device boot and service start are successful (YES in step S1411), the process proceeds to step S1412, and when the connection device boot and service start fail (NO in step S1411), the process proceeds to step S1415.

  When the connection device boots and the service starts successfully (YES in step S1411), the update history table creation unit records the update result in the rear wheel history table (step S1412), and cancels the prohibition of update or discards the backup in the backup device. (Step S1413), the connection apparatus is shifted to the normal service mode (step S1414), and the software recovery processing procedure is terminated.

  When the boot of the connection device and the start of the service have failed (NO in step S1411), the process shifts to the forced update mode (step S1415), the update history table records the update result in the update history table (step S1416), and the backup device Is instructed to cancel the prohibition of update or discard the backup (step S1417), the software of the connected device is updated manually (step S1418), and the software recovery processing procedure is terminated.

  When the backup destination cannot be searched, there are “notify the user to that effect” and “continue the update operation without performing backup”.

  Note that the processing procedure of the same model searching process performed by the same model searching unit in step S1301 of the flowchart shown in FIG. 13 is the same as the processing procedure of the flowchart shown in FIG.

  Further, the software transmission processing procedure performed when the device designated as the software backup destination is requested to transmit software from the software updating device is the same as the processing procedure of the flowchart shown in FIG. Therefore, explanation is omitted.

  Accordingly, it is possible to recover the failure of the software update work without requiring a special management server device or function, and further, the software update work can be reduced. It becomes possible to reduce the downtime of the apparatus due to the failure of the work, and to minimize the influence on the work.

  In the fourth embodiment, after the MFP machine to which the software update apparatus according to the present invention is connected performs software update, the software update apparatus distributes the same software to the same type of MFP machine existing in the system, An embodiment will be described in which a software update is instructed to the MFP of the same model when a malfunction is detected in the software.

  FIG. 15 is a block diagram illustrating an example of a functional configuration of the software update device 4 according to the fourth embodiment.

  As shown in FIG. 15, the MFP machine 2 is connected or built in the software update apparatus 4 according to the present invention. The MFP machine 2 has communication with the software update apparatus 4, software update, and the MFP machine 2. Control of a control unit (not shown) of various services (copying, printing, scanning, faxing, etc.), MFP machine main control unit 6 for exchanging with peripheral devices 5 connected to the MFP machine 2, etc., each subnet 1 It has an I / F [Interface] 7 for transmitting / receiving various data to / from other devices above.

  Next, a functional configuration of the software update device 4 will be described.

  As shown in FIG. 15, the software update device 4 includes a software update unit 8, a homogeneous model search unit 9, a device table creation unit 10, a software distribution unit 11, an update result reception unit 12, a service execution table creation unit 17, an update instruction. The unit 18 and the timer 19 are included.

  The software update unit 8 performs processing for causing the MFP device 2 to update the update software. Specifically, the update software is transferred to the MFP main control unit 6 and the MFP main control unit 6 performs an update of the update software.

  The same model search unit 9 searches for an MFP machine 2 of the same model as the MFP machine 2 from a device connected to each subnet 1 when the update software for the MFP machine 2 is normally updated. A process for confirming the software version of the MFP 2 of the same model is performed. Note that the search method for the MFP model 2 of the same model includes “automatic search within the same subnet”, “automatic search within a designated subnet”, and “search for a designated device”.

  The device table creation unit 10 performs processing for creating and storing a device table that records device information including the model information of the MFP 2 of the same model searched by the same model search unit 9 and the software version.

  The software distribution unit 11 determines whether or not the distribution is possible based on the comparison of the main body version or the like from the device information of the MFP model 2 of the same model recorded in the device table creation unit 10, and the MFP model 2 of the same model that can be distributed. Process to distribute software for update.

  The update result receiving unit 12 performs a process of receiving an update result transmitted from the MFP 2 of the same model to which the software distribution unit 11 has distributed the update software. The update result received by the update result receiving unit 12 is transferred to the device table creating unit 10, and the device table creating unit 10 records the update result in the device table.

  The service execution table creation unit 17 records whether or not various services (copy, print, scan, fax, etc.) of the MFP machine 2 have been normally executed after the MFP machine 2 has updated software. Create and save the table.

  The update instruction unit 18 performs a process of transmitting an instruction to update the software for update or an instruction to cancel the update of the update software to the MFP 2 of the same model to which the software distribution unit 11 has distributed the update software.

  The timer 19 distributes the update software to the MFP device 2 of the same model by the software distribution unit 11, and then transmits an instruction to update the update software to the MFP device 2 to which the update software is distributed by the update instruction unit 18. The process of counting the update pending time until it is done.

  Next, a software distribution processing procedure performed by the software updating apparatus will be described with reference to flowcharts shown in FIGS.

  The software update unit manually updates the software (hereinafter referred to as a connection device) connected to the software update device by the user (step S1601), the software update unit automatically reboots the connection device (step S1602), and the connection is made. If the device boot or service start fails (NO in step S1603), the process proceeds to step S1604. If the connection device boot and service start succeeds (YES in step S1603), the process proceeds to step S1605.

  If the connection device boot and service start fail (NO in step S1603), the software update failure is notified to the user (step S1604), and the software distribution processing procedure ends.

  If the connection device boots and the service starts successfully (YES in step S1603), the same model search unit performs the same model search process as a subroutine (step S1605), and the device table creation unit creates and stores the device table. (Step S1606), the software distribution unit starts a distribution loop (Step S1607), and the software distribution unit searches for the connection device and the same model search unit by the software distribution unit (hereinafter referred to as the same model device). (Step S1608), and if the software distribution unit determines that the main body software can be distributed (YES in step S1609), the process proceeds to step S1610, and the software distribution unit does not distribute the main body software. When it is determined that it is possible (NO in step S1609) The process proceeds to step S1611.

  If the software distribution unit determines that the main body software can be distributed (YES in step S1609), the software distribution unit distributes the main body software to the same model device (step S1610), and the process proceeds to step S1611.

  When the software distribution unit compares the peripheral device versions of the peripheral device of the connected device and the peripheral device of the same model device (step S1611), and the software distribution unit determines that the peripheral device software can be distributed (step S1612). In step S1613, if the software distribution unit determines that the peripheral device software cannot be distributed (NO in step S1612), the process proceeds to step S1614.

  If the software distribution unit determines that the peripheral device software can be distributed (YES in step S1612), the software distribution unit distributes the peripheral device software to the same model device (step S1613), and the process proceeds to step S1614.

  If the distribution loop of the software distribution unit has ended (YES in step S1614), the process proceeds to the flowchart shown in FIG. 17, and if the distribution loop of the software distribution unit has not ended (NO in step S1614), step S1608 Return to.

  When the distribution loop of the software distribution unit is completed (YES in step S1614), the process proceeds to the flowchart shown in FIG. 17 and the service of the connection device is executed (step S1701), and no error occurs in the service (in step S1702). NO), the process proceeds to step S1703, and if an error has occurred in the service (YES in step S1702), the process proceeds to step S1704.

  If no error has occurred in the service (NO in step S1702), the service execution table creation unit records the normal operation in the service execution table (step S1703), and the process proceeds to step S1708.

  If an error has occurred in the service (YES in step S1702), the cause of the error is isolated (step S1704), if the cause is not software (NO in step S1705), the process proceeds to step S1706, and if the cause is software ( YES in step S1705), the process proceeds to step S1708.

  If the cause is not software (NO in step S1705), the update instruction unit instructs all devices that distributed the software (hereinafter referred to as distribution devices) to stop updating (step S1706), and notifies the user of the occurrence of an error. (Step S1707), and the software distribution processing procedure ends.

  If there is no unexecuted service (NO in step S1708), the process proceeds to step S1709. If there is an unexecuted service (YES in step S1708), the process proceeds to step S1710.

  If there is no unexecuted service (NO in step S1708), the update instruction unit instructs all distribution apparatuses to perform the update (step S1709), and the process proceeds to step S1711.

  If there is an unexecuted service (YES in step S1708), if the update time has not elapsed (NO in step S1710), the process returns to step S1701, and if the update time has elapsed (YES in step S1710), step The process proceeds to S1711.

  Then, the update result receiving unit starts an update result receiving loop (step S1711), the update result receiving unit receives the update result from the distribution device (step S1712), and the device table creation unit stores the update result of the distribution device in the device table. Is recorded (step S1713), and the update result receiving loop of the update result receiving unit is finished (YES in step S1714), the process proceeds to step S1715, and the update result receiving loop of the update result receiving unit is not finished (NO in step S1714), the process returns to step S1712.

  When the update result reception loop of the update result receiving unit is completed (YES in step S1714), the update results of all the distribution devices are notified to the user (step S1715), the connected device is shifted to the normal service (step S1716), and the software is updated. The delivery processing procedure is terminated.

  Note that, as a re-execution method of update for a distribution apparatus that failed to be updated, there are “repeat the distribution until the update is successful” and “repeat the distribution as many times as specified by the user”.

  Note that the processing procedure of the same model searching process performed by the same model searching unit in step S1605 of the flowchart shown in FIG. 16 is the same as the processing procedure of the flowchart shown in FIG.

  Next, a software update processing procedure performed by a device to which software is distributed from the software update device will be described with reference to flowcharts shown in FIGS.

  A software update request is received from the software update device (step S1801), update main body software is received from the software update device (step S1802), update peripheral device software is received from the software update device (step S1803), and a timer is received. In step S1804, if the update hold time has elapsed (YES in step S1805), the process proceeds to step S1807. If the update hold time has not passed (NO in step S1806), step The process proceeds to S1806.

  If the update hold time has not elapsed (NO in step S1806), or if no update instruction has been received from the software update device or the user (YES in step S1806), the process proceeds to step S1807, and the software update device or When an instruction to perform update is received from the user (NO in step S1806), the process proceeds to step S1809.

  If an update center instruction is received from the software update apparatus (YES in step S1807), the process proceeds to step S1808. If an update center instruction is not received from the software update apparatus (NO in step S1807), The process returns to step S1805.

  Then, the acceptance of the job is stopped (step S1809), and if there is a job being processed or waiting (NO in step S1810), the process proceeds to step S1811, and if there is no job being processed or waiting (step S1810). YES), the process proceeds to the flowchart shown in FIG.

  If there is a job being processed or waiting (NO in step S1710), the job end event is waited (step S1811), and the process returns to step S1810.

  If there is no job being processed or waiting (YES in step S1810), the process proceeds to the flowchart shown in FIG. 19 to check the version of the main body software for update (step S1901), and if it can be updated (YES in step S1902), The process proceeds to step S1903, and if it cannot be updated (NO in step S1902), the process proceeds to step S1904.

  If it can be updated (YES in step S1902), the main body software is updated (step S1903), and the process proceeds to step S1904.

  Then, the update result is transmitted to the software update device (step S1904), the version of the update peripheral device software is confirmed (step S1905), and if it can be updated (YES in step S1906), the process proceeds to step S1907, and the update is performed. If not possible (NO in step S1906), the process advances to step S1908.

  If it can be updated (YES in step S1906), the peripheral device software is updated (step S1907), and the process proceeds to step S1908.

  If the automatic reboot is performed (step S1908) and the boot and service start are successful (YES in step S1909), the process proceeds to step S1910. If the boot and service start fails (NO in step S1909), step is performed. The process proceeds to S1911.

  If the boot and service start are successful (YES in step S1909), the update result is transmitted to the software update device (step S1910), and the software update processing procedure is terminated.

  If the boot or service start has failed (NO in step S1909), the mode is shifted to the forced update mode (step S1911), the update result is transmitted to the software update device (step S1912), and the software update processing procedure is terminated.

  FIG. 20 is a diagram illustrating an example of the service execution table 20.

  As shown in FIG. 20, the service execution table 20 records the execution date and time of each service.

  Therefore, by updating the software after waiting for a certain period of time, it is possible to immediately stop without spreading the problem.

It is a block diagram which shows an example of the whole structure of the system to which this invention is applied. 1 is a block diagram illustrating an example of a functional configuration of a software update device according to a first embodiment. It is a flowchart which shows the process sequence of the software delivery which a software update apparatus performs. It is a flowchart which shows the process sequence of the software delivery which a software update apparatus performs. It is a flowchart which shows the process sequence of the same model search process which a same model search part performs by step S305 of the flowchart shown in FIG. It is a flowchart which shows the process sequence of the software update which the apparatus to which software was distributed from the software update apparatus performs. It is a figure which shows an example of an apparatus table. It is a block diagram which shows an example of a functional structure of the software update apparatus in Example 2. FIG. It is a flowchart which shows the process sequence of the software recovery which a software update apparatus performs. It is a flowchart which shows the process sequence of the software recovery which a software update apparatus performs. It is a flowchart which shows the process sequence of the software transmission which the apparatus requested | required of software transmission from the software update apparatus performs. FIG. 10 is a block diagram illustrating an example of a functional configuration of a software update device according to a third embodiment. It is a flowchart which shows the process sequence of the software backup and software recovery which a software update apparatus performs. It is a flowchart which shows the process sequence of the software backup and software recovery which a software update apparatus performs. FIG. 10 is a block diagram illustrating an example of a functional configuration of a software update device according to a fourth embodiment. It is a flowchart which shows the process sequence of the software delivery which a software update apparatus performs. It is a flowchart which shows the process sequence of the software delivery which a software update apparatus performs. It is a flowchart which shows the process sequence of the software update which the apparatus to which software was distributed from the software update apparatus performs. It is a flowchart which shows the process sequence of the software update which the apparatus to which software was distributed from the software update apparatus performs. It is a figure which shows an example of a service execution table.

Explanation of symbols

1 Subnet 2 MFP machine 3 Printer machine 4 Software update device 5 Peripheral device 6 MFP machine main controller 7 I / F
DESCRIPTION OF SYMBOLS 8 Software update part 9 Same model search part 10 Device table creation part 11 Software distribution part 12 Update result reception part 13 Device table 14 Update history table creation part 15 Software acquisition part 16 Software transmission part 17 Service execution table creation part 18 Update instruction part 19 Timer 20 Service execution table

Claims (24)

In a software update device that controls software updates of devices connected to a network,
Software update means for controlling software updates of the device;
When the update software is normally updated in the device, the same model search means for searching for a device of the same model as the device from various devices on the network;
A software update apparatus comprising: software distribution means for distributing the update software to an apparatus of the same model searched by the same model search means. A device table creating means for creating a device table related to a device of the same model searched by the same model searching means;
The same model searching means is
Obtain the information of the device from the searched device of the same model,
The device table creation means
The software update apparatus according to claim 1, wherein information on a device of the same model acquired by the same model search unit is recorded in the device table. The software distribution means includes
3. The software according to claim 2, wherein versions of the device and the device of the same model are compared based on the device table, and the update software is distributed to devices of the same model determined to be the same version. Update device. An update result receiving means for receiving an update result of the update software from a device of the same model that has distributed the update software by the software distribution means;
The software distribution means includes
The software update apparatus according to claim 1, wherein when the update result is unsuccessful, the update software is redistributed to an apparatus of the same model that failed to be updated. The software distribution means includes
The software updating apparatus according to claim 1, wherein the same type of apparatus that has distributed the update software is instructed to wait until a predetermined time elapses to update the update software. If a defect is found in the update software updated by the device before the predetermined time has elapsed, the software distribution means updates the update software to the same type of device that has distributed the update software. 6. The software updating apparatus according to claim 5, further comprising update instruction means for instructing to stop the operation. In a software update device that controls software updates of devices connected to a network,
Software update means for controlling software updates of the device;
Update history table creating means for creating an update history table related to the software update history of the device;
When the update software is not normally updated in the device, the same type of device as that of the device is searched from various devices on the network, and the information of the device is acquired from the searched same type of device. Model searching means,
A device table creating means for creating a device table related to information on devices of the same model searched by the same model searching means;
Based on the update history table and the device table, and confirms a device of the same model having a desired version of software, and comprises software acquisition means for acquiring the software from the confirmed device of the same model,
The software update means includes
A software update apparatus that causes the apparatus to update a desired version of software acquired by the software acquisition means. The software update apparatus according to claim 7, wherein the same model having the desired version of software is instructed to prohibit software update. The software acquisition means includes
If the update of the desired version of the software fails, re-acquire the software from a device of the same model having the software,
The software update means includes
The software update apparatus according to claim 7, wherein the apparatus updates the desired version of software reacquired by the software acquisition unit. In a software update device that controls software updates of devices connected to a network,
Software update means for controlling software updates of the device;
Before updating the update software in the device, the same model search means for searching for devices of the same model as all devices from various devices on the network,
Software transmission means for transmitting the pre-update software of the device to the same model device searched by the same model search means;
A software acquisition means for acquiring the pre-update software from the same model apparatus that has transmitted the pre-update software by the software transmission means when the update software is not normally updated in the apparatus;
The software update means includes
A software update apparatus that causes the apparatus to update pre-update software acquired by the software acquisition means. A device table creating means for creating a device table related to a device of the same model searched by the same model searching means;
The same model searching means is
Obtain the information of the device from the searched device of the same model,
The device table creation means
The software update apparatus according to claim 10, wherein information on a device of the same model acquired by the same model search unit is recorded in the device table. The software acquisition means includes
If the update of the pre-update software fails, re-acquire the pre-update software from the same model device having the pre-update software,
The software update means includes
The software update apparatus according to claim 10, wherein the apparatus re-updates the pre-update software reacquired by the software acquisition unit. In a software update method for controlling software update of a device connected to a network,
Update the software for updating in the device,
When the update software is normally updated in the device, search for devices of the same model as the device from various devices on the network,
Distributing the update software to the searched device of the same model. Obtain the information of the device from the searched device of the same model,
The software update method according to claim 13, wherein the acquired information of the same type of device is recorded in a device table. 15. The software according to claim 14, wherein versions of the device and the device of the same model are compared based on the device table, and the update software is distributed to devices of the same model determined to be the same version. Update method. Receiving the update result of the software from the same model device that distributed the update software,
The software update method according to claim 13, wherein, when the received update result is unsuccessful, the update software is redistributed to the same model apparatus that failed to be updated. 14. The software update method according to claim 13, wherein the same model device that has distributed the update software is instructed to wait for a predetermined time to elapse to update the update software. When a defect is found in the update software updated by the device before the predetermined time has elapsed, an instruction to stop updating the update software is given to the same model device that has distributed the update software. The software update method according to claim 17, wherein: In a software update method for controlling software update of a device connected to a network,
Update the software for updating in the device,
Create an update history table for the software update history of the device,
When the update software is not normally updated in the device, search for devices of the same model as the device from various devices on the network,
Obtain the information of the device from the searched device of the same model,
Create a device table related to the acquired device information of the same model,
Based on the update history table and the device table, confirm a device of the same model having a desired version of software,
Obtain the desired version of the software from the confirmed device of the same model,
A software update method characterized by causing the device to update the acquired desired version of software. 20. The software update method according to claim 19, wherein the same model having the desired version of software is instructed to prohibit software update. If the update of the desired version of the software fails, re-acquire the software from a device of the same model having the software,
The software update method according to claim 19, wherein the device re-updates the re-acquired desired version of software. In a software update method for controlling software update of a device connected to a network,
Before updating the update software in the device, search for devices of the same model as all devices from various devices on the network,
Send the pre-update software of the device to the searched device of the same model,
Update the device update software to the device,
When the software for update is not normally updated in the device, the pre-update software is acquired from the same model device that transmitted the pre-update software,
A software update method characterized by causing the apparatus to update the acquired pre-update software. Obtain the information of the device from the searched device of the same model,
23. The software updating method according to claim 22, wherein the acquired information on the same type of device is recorded in a device table. If the update of the pre-update software fails, re-acquire the pre-update software from the same model device having the pre-update software,
23. The software updating method according to claim 22, wherein the device re-updates the re-acquired pre-update software.

Images