JP2018045725A - Information processing apparatus, control method of the same, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To make it possible to reduce downtime generated in updating software.SOLUTION: An image forming apparatus 100 performs background processing to download update firmware in an update firmware storage area 321 (a step S102), and when download has been completed, immediately performs the background processing to expand the update firmware in a firmware expansion area 330 (a step S105). When the image forming apparatus is indicated to update software mounted thereon, the image forming apparatus stores the update firmware expanded in the firmware expansion area 330 in a firmware copy area 311 (a step S112), and performs the background processing to replace the software mounted thereon with link information for executing the update firmware stored in the firmware copy area 311 (a step S114).SELECTED DRAWING: Figure 7

Description

  The present invention relates to an information processing apparatus, a control method thereof, and a program.

  In an information processing apparatus capable of updating software, a periodic update function that automatically updates the information processing apparatus to automatically update the software of the information processing apparatus is generally known.

  Some of these periodic update functions allow the user to specify the time to download new software.

  Furthermore, a function for manually updating software and a function for specifying a time for updating software are also known. In addition, a technique for downloading a program to a computer and performing installation without clicking with no input from a user is also disclosed (for example, see Patent Document 1).

JP 2008-282251 A

  However, Patent Document 1 does not describe a downtime that is a time that cannot be used by the user, and cannot be said to provide an optimal software update method. Also, there is no detailed description of how to process the downloaded software and it is not clear.

  Furthermore, regarding the periodic update function, the procedure is to update after downloading, and the update processing time is generally set to a time that the user cannot use.

  An object of the present invention is to provide an information processing apparatus capable of reducing downtime caused by updating software, a control method therefor, and a program.

  To achieve the above object, the information processing apparatus according to claim 1 downloads update software for updating software installed in the information processing apparatus, and updates the installed software with the downloaded update software. An information processing apparatus comprising: a download unit that downloads the update software to a predetermined first storage area by background processing; and a second predetermined unit immediately after the download unit finishes downloading the update software. Expansion means for expanding the update software in a storage area by background processing; and when the update of the installed software is instructed, the expansion is performed in a predetermined third storage area for executing the software The second storage area by means Storage means for storing the updated software that has been deployed, and link information for executing the updated software stored in the third storage area by the storage means in place of the installed software by background processing It has the replacement means to replace.

  According to the present invention, the update software is downloaded to the first storage area by the background process, and when the download is completed, the update software is immediately deployed to the second storage area by the background process, so that the software is updated. Downtime can be shortened.

1 is a diagram illustrating a schematic configuration of an image forming apparatus as an information processing apparatus according to an embodiment of the present invention. FIG. 2 is a diagram for explaining a state in which a firmware mounted on an image forming apparatus is updated in the flash memory and the HDD in FIG. 1. It is a figure which shows each screen displayed on the operation part in FIG. It is a figure which shows the structural example of the part of the farm required when updating. It is a figure which shows each information managed in order to replace the link information in FIG. It is a timing chart which shows the flow of an update process. It is a flowchart which shows the procedure of the update control process performed by CPU in FIG. It is a timing chart which shows the procedure of each process during expansion | deployment. It is a figure which shows the management information which manages an expansion | deployment state. FIG. 10A is a flowchart showing a procedure of the in-deployment process A in the update control process of FIG. 7, and FIG. 10B is a flowchart showing a procedure of the in-deployment process B in the update control process of FIG. is there. It is a flowchart which shows the procedure of the process C during expansion | deployment in the update control process of FIG.

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

  FIG. 1 is a diagram showing a schematic configuration of an image forming apparatus 100 as an information processing apparatus according to an embodiment of the present invention.

  In FIG. 1, the image forming apparatus 100 includes a control unit 200, an operation unit 220, a printer engine 221, a scanner engine 222, and a power supply 240, and is connected to a PC 260 and an external server 250 via a LAN 110.

  The control unit 200 controls the entire image forming apparatus 100. The operation unit 220 displays various types of information to the user and receives user operation inputs. The printer engine 221 prints an image of the image data output from the control unit 200 on a recording medium such as paper according to a printer engine farm 231 stored in a non-volatile storage device (not shown).

  The scanner engine 222 reads a document and outputs image data indicating a document image to the control unit 200 according to a scanner engine farm 232 stored in a non-volatile storage device (not shown).

  The control unit 200 includes a CPU 210, a chip set 211, a RAM 212, an SRAM 213, a NIC 214, an operation unit interface 215, a printer interface 216, a scanner interface 217, an HDD 218, and a flash memory 219.

  The CPU 210 controls the entire image forming apparatus 100 by controlling the control unit 200. A flowchart to be described later shows processing in which the CPU 210 executes a program loaded from the HDD 218 or the flash memory 219 to the RAM 212.

  The RAM 212 is used as a work area for the CPU 210 and stores various data and various programs. The SRAM 213 stores setting values, image adjustment values, and the like necessary for the image forming apparatus 100, and the stored contents are retained even when the image forming apparatus 100 is turned off by a backup power source.

  The chip set 211 is a plurality of integrated circuits including an RTC (Real Time Clock) 270 which is a chip dedicated to timing. Even if the power is not supplied from the power supply 240 to the RTC 270, the power is supplied from a built-in battery (not shown), and therefore the RTC 270 can operate even when the image forming apparatus 100 is in the sleep state.

  Thereby, in a state where power is supplied to the chipset 211, recovery from the sleep state can be realized. On the other hand, in the shutdown state in which no power is supplied to the chipset 211, the RTC 270 cannot operate.

  The NIC 214 is an interface for connecting to the LAN 110 and communicating with the PC 260 and the external server 250. In the present embodiment, the NIC 214 can download software from the external server 250 that is an external device.

  In the following description, software is expressed as firmware or firmware. Furthermore, update software for updating a firmware installed in the image forming apparatus 100 (hereinafter referred to as “update”) may be expressed as an update firmware.

  The operation unit interface 215 is an interface between the operation unit 220 and the control unit 200. The printer interface 216 is an interface between the printer engine 221 and the control unit 200. The scanner interface 217 is an interface between the scanner engine 222 and the control unit 200.

  The HDD 218 stores various programs and various data. The flash memory 219 stores various data such as setting values used in the image forming apparatus 100 and various programs. The HDD 218 and the flash memory 219 store various files used for updating the firmware.

  FIG. 2 is a diagram for explaining a state in which the firmware installed in the image forming apparatus 100 is updated in the flash memory 219 and the HDD 218 in FIG.

  In FIG. 2, firmware 310 is an installed firmware. The flash memory 219 stores an update program 320.

  When the update firmware can be downloaded from the external server 250, the update program 320 is an update firmware storage which is a first storage area provided in the flash memory 219 from the external server 250 via the NIC 214 in accordance with a firmware download instruction from the CPU 210. The update firmware is temporarily stored in the area 321.

  Next, the update program 320 expands the update firmware stored in the update firmware storage area 321 in the firmware expansion area 330 which is the second storage area provided in the HDD 218 in accordance with the firmware expansion instruction from the CPU 210. This expansion is a process of decoding the encoded update firmware. As this encoding, there is encoding by compression or encryption. In the case of compression, decompression is decompression.

  Next, in accordance with an update instruction from the CPU 210, the update program 320 provides the update firmware expanded in the firmware expansion area 330 in the flash memory 219 and stores it in the firmware copy area 311 that is a third storage area for executing the firmware. To do.

  Finally, the update firmware stored in the firmware copy area 311 is normally activated by replacing the link information for executing the update firmware stored in the firmware copy area 311 instead of the installed firmware in accordance with an instruction from the CPU 210. Sometimes, the update of the firmware 310 is completed. This replacement of link information will be described later.

  FIG. 3 is a diagram showing each screen displayed on the operation unit 220 in FIG.

  3A shows a menu screen 407, and FIG. 3B shows a setting screen 408.

  In the menu screen 407 of FIG. 3A, the firmware update key 401 is a key for displaying the setting screen 408 of FIG. The regular update management column 402 is a column that indicates whether the regular update is valid.

  In the setting screen 408 of FIG. 3B, when the user sets the periodic update, the On key 403 is selected.

  The download time 404 is a field for setting the time for downloading the update firmware. The update time 405 is a field for setting the time for updating the firmware with the downloaded update firmware. The contents set on the setting screen 408 are stored in the flash memory 219.

  In the setting screen 408 of FIG. 3B, for example, the setting contents when downloading at 19:00 every Friday and updating the firmware at 20:00 every Friday are shown.

  FIG. 3C is a diagram showing a download screen 410 displayed during the download of the update firmware.

  When the time set in the download time 404 on the setting screen 408 arrives, the download is started. At that time, the download screen 410 is displayed.

  FIG. 3D is a diagram showing an update screen 409 displayed when the downloaded update firmware is expanded in the firmware expansion area 330.

  When the update screen 409 is displayed, since the download has already been completed, a firmware update button 406 and a firmware deletion button 411 are displayed as shown in FIG.

  FIG. 4 is a diagram illustrating a configuration example of parts of a firmware necessary for updating.

  FIG. 4A illustrates an example of system parts.

  In FIG. 4A, the system part is composed of a binary file (system.bin), a library (libsystem.so), and a configuration file (system.conf).

  FIG. 4B is a diagram showing the storage locations and attributes of the components of the system part.

  In FIG. 4B, the binary file (system.bin) is stored under the / bin directory, and the attribute is an executable file. The library (libsystem.so) is stored under the / lib directory, and the attribute is a read-only file. Furthermore, the configuration file (system.conf) is stored under the / etc directory, and the attribute is a read-only file. Also, the version of the system parts is shown to be 3.1.1.

  FIG. 4C is a diagram showing storage locations and attributes of the components of the new system parts.

  FIG. 4C shows that the version of the new system part is 4.0.0. It should be noted that the storage locations and attributes of the old and new parts are not only different in version but also different in part configuration. Examples of different configurations include different binary files and multiple configuration files. In this way, the update farm is composed of parts.

  FIG. 5 is a diagram showing each piece of information managed to replace the link information in FIG.

  In FIG. 5, first, oldpkgs 501 indicating an old part and newpkgs 502 indicating a new part are shown. oldpkgs 501 and newpkgs 502 indicate that the system part is replaced from version 3.1.1 to version 4.0.0.

  Also, oldpkgs 501 and newpkgs 502 indicate that the systemui and copy-app parts are replaced with new versions. In addition, a new part may become a part downgraded.

  In the next oldbinarys 503 and newbinarys 504, the system part has the same name in the old and new parts, so the old part has the same name system.bin, and the new part is identified by adding the suffix ".new". It is shown that.

  And oldlibs 505 and newlibs 506 indicate that parts of libsystem.so and libsystemui.so are replaced with new versions.

  Also, oldconfs 507 and newconfs 508 indicate that new and old are discriminated by adding the above-mentioned “.new”.

  FIG. 6 is a timing chart showing the flow of the update process.

  FIG. 6A is a timing chart showing the procedure of the update process in the prior art.

  In FIG. 6A, when the download time comes in the normal operation state in which copying and printing can be executed, downloading is performed. After the download is completed, the normal startup operation state is restored. Thereafter, when an update is instructed due to the arrival of the update time, the system is restarted and the update is activated.

  In the conventional update activation state shown in FIG. 6 (A), expansion in which encoded parts are decoded is performed, and then the firmware is updated and then restarted again. As described above, in the conventional technique, since the downloaded parts are expanded after the update is instructed, a long downtime for the update process occurs.

  In the following description, a series of processing for decompressing or decrypting the compressed or encrypted parts performed in the above-described prior art and then updating the firmware is expressed as normal update processing.

  FIG. 6B is a timing chart showing the procedure of the update control process according to the present embodiment.

  In FIG. 6B, when the download time comes in the normal operation state, the download is performed. After the download is completed, the parts stored in the update firmware storage area 321 are expanded in the firmware expansion area 330 and returned to the normal activation operation state again. As shown in the figure, download and expansion are performed as background processing.

  Thereafter, when the update time arrives or the firmware update button 406 on the update screen 409 is selected by the user, the CPU 210 instructs the update. The system is restarted by this update instruction and transitions to an update start state. Then, the parts developed in the firmware development area 330 are stored in the firmware copy area 311.

  After that, the system is restarted, transits to the normal startup state, and the update process is completed when the link information is replaced. Thus, in this embodiment, link information is replaced by background processing.

  Thus, in the present embodiment, since the downloaded parts are immediately deployed, the downtime for the update process can be shortened as compared with the prior art.

  In the update control process of FIG. 6B, an update is instructed after the completion of development, but an update may be instructed during the development. In this case, a processing during development described later is performed. First, a flowchart illustrating a processing procedure in a case where an update instruction is given after the development is completed will be described.

  FIG. 7 is a flowchart showing a procedure of update control processing executed by the CPU 210 in FIG.

  In FIG. 7, when the download time arrives (YES in step S101), the update program 320 downloads the parts and stores them in the update firmware storage area 321 (step S102). Further, at this time, the download screen 410 is displayed on the operation unit 220 (step S103). Step S102 corresponds to download means.

  Next, when the download is completed, the update program 320 immediately develops the parts stored in the update firmware storage area 321 in the firmware development area 330 (step S104). This step S104 corresponds to a developing means.

  When the update program 320 is instructed to update from the CPU 210 (YES in step S105), the update program 320 determines whether or not the part is being developed in the farm development area (step S106).

  As a result of the determination in step S106, if it is determined that the part is being developed in the farm development area (YES in step S106), a process during development described later is performed (step S116), and this process ends.

  On the other hand, as a result of the determination in step S106, if it is determined that the part is not being developed in the farm development area (NO in step S106), the part is restarted and transitioned to the update activation state (step S111).

  Then, the update program 320 stores the parts developed in the firmware development area 330 in the firmware copy area 311 (step S112), restarts, and transitions to a normal operation state (step S113). Step S112 corresponds to storage means.

  Next, the above-described link information is replaced (step S114), and this process is terminated. This step S114 corresponds to replacement means.

  Hereinafter, in the above-described update control process, three types of in-deployment processes, which are processes when an update is instructed by the CPU 210 while being deployed, will be described.

  FIG. 8 is a timing chart showing the procedure of each developing process.

  FIG. 8A is a timing chart showing the procedure of the processing A during development.

  In FIG. 8A, when the download time comes in the normal operation state, the download is performed. After the download is completed, the parts stored in the update firmware storage area 321 are expanded in the firmware expansion area 330. During the expansion, the update time comes or the firmware update button 406 on the update screen 409 is displayed. It is assumed that the update is instructed by the CPU 210 by being selected by the user.

  When an update is instructed, the deployment is terminated halfway, the deployed parts are discarded, the system is restarted, and a transition is made to the update activation state. Thereafter, normal update processing is performed.

  Note that when the update time comes or the firmware update button 406 on the update screen 409 is selected by the user in the expanded state, the operation unit 220 displays a warning screen indicating that the expansion is stopped. The remaining time required for expansion may be displayed on the operation unit 220.

  FIG. 8B is a timing chart showing the procedure of processing B during development.

  In FIG. 8B, the download time arrives in the normal operation state, and updating is instructed to the firmware development area 330 during the development is the same as the development process A. Continue to expand all parts.

  When all the parts are deployed, the result is the same as when the update is instructed after the deployment is completed. Therefore, in the in-deployment process B, as in the case where the update is instructed after the end of the deployment, the process is restarted to enter the update activation state, and the parts deployed in the firmware deployment area 330 are stored in the firmware copy area 311. To do.

  Thereafter, after the transition to the normal activation state, the system is restarted. After the transition to the normal activation, the link information is replaced, and the update process ends.

  FIG. 8C is a timing chart showing the procedure of the developing process C.

  In FIG. 8C, the download time arrives in the normal operation state, and starting the expansion in the farm expansion area 330 is the same as the expansion process A, but in the expansion process C, the expansion state Manage. The management of the expanded state will be described.

  FIG. 9 is a diagram showing management information 700 for managing the development state.

  In FIG. 9, the management information 700 is composed of Updatepkgs 701, Executing 702, and Waiting 703.

  Updatepkgs 701 indicates the deployed parts. Executing 702 indicates a part being developed. Waiting 703 indicates a part waiting for deployment. Based on this management information, it is possible to determine which part is a deployed part, a part that is being deployed, and a part that is waiting to be deployed. This management information is stored in the RAM 212.

  Returning to FIG. 8C, when update is instructed by the CPU 210 during the expansion, the expansion ends in the middle. However, the parts that are Executing 702 in the management information continue to be expanded, and the parts waiting for expansion are expanded. Reboot without doing and transition to the update start state.

  The parts developed in the firmware development area 330 are stored in the firmware copy area 311. On the other hand, normal update processing is performed on the parts waiting to be deployed.

  Thereafter, when the system is restarted and transitions to the normal state, the update process is completed by replacing the link information only for the parts stored in the firmware copy area 311.

  In the developing process C, since the developed parts are used, the downtime is shortened compared to the developing process A in which the developed parts are discarded.

  Hereinafter, the procedure of each developing process will be described with reference to flowcharts.

  FIG. 10A is a flowchart showing the procedure of the developing process A in the update control process of FIG.

  In FIG. 10A, when it is determined in step S106 in the update control process of FIG. 7 that the part is being deployed in the farm deployment area (YES in step S106), the deployment is terminated, and the deployed part is Discard (step S201).

  Next, the system is restarted to transit to the update startup state (step S202), and normal update processing is performed (step S203). And it restarts again and it changes to a normal starting state (step S204), and complete | finishes this process.

  As described above, in this embodiment, when an update is instructed during the deployment of the update farm, the deployment of the update farm is terminated, the deployed update farm is discarded, and the update farm is placed in the farm deployment area 330. Update the installed farm without deploying it.

  FIG. 10B is a flowchart showing the procedure of the in-deployment process B in the update control process of FIG.

  In FIG. 10B, when it is determined in step S106 in the update control process of FIG. 7 that the part is being deployed in the farm deployment area (YES in step S106), a warning screen indicating that the deployment is continued is displayed. The information is displayed on the operation unit 220 (step S301).

  Next, when all parts have been developed (YES in step S302), steps S111 to S115 in the update control process of FIG. 7 are performed (step S303), and this process ends.

  As described above, in this embodiment, when an update is instructed during the deployment of the update firmware, the deployment is continued, and after the deployment of the update firmware is completed, the firmware copy region 311 is deployed in the firmware deployment region 330. The updated update firmware is stored.

  FIG. 11 is a flowchart showing the procedure of the developing process C in the update control process of FIG.

  As described above, in the in-deployment process C, the process is inserted into the update control process of FIG.

  FIG. 11A is a flowchart showing a procedure of processing inserted in the update control processing of FIG.

  In step S104 of FIG. 7, the parts are developed in the farm development area 330, but the development state is managed together with that (step S400), and the process proceeds to step S105.

  FIG. 11B is a flowchart showing a procedure of the developing process B in the update control process of FIG.

  In FIG. 11B, when it is determined in step S106 in the update control process of FIG. 7 that the part is being deployed in the farm deployment area (YES in step S106), the deployment is terminated (step S401). As described above, the development is terminated in the middle, but the parts that are Executing 702 in the management information continue to be developed.

  Then, it restarts and changes to an update starting state (step S402). Then, the parts developed in the firmware development area 330 are stored in the firmware copy area 311 (step S402).

  Next, a normal update process is performed on the undeveloped parts (step S403). And it restarts again, it changes to a normal starting state (step S304), replacement | exchange of link information is performed (step S405), and this process is complete | finished.

  As described above, in the present embodiment, when an update is instructed during deployment of an update firmware, the deployment of the update firmware is terminated, and the update firmware deployed before the deployment is terminated is stored in the firmware copy area 311. To remember.

  Then, the link information for executing the update firmware stored in the firmware copy area 311 is replaced, and the update firmware that has not been expanded in the firmware expansion area 330 is updated without being expanded in the firmware expansion area 330. To do.

  As described above, according to the present embodiment, the update firmware is downloaded to the update firmware storage area 321 by background processing (step S102), and immediately after the download is completed, the update firmware is downloaded to the farm development area 330 in the background. The processing is expanded (step S105).

  When an update of the installed software is instructed, the firmware copy area 311 stores the update firmware developed in the firmware development area 330 (step S112), and instead of the installed software, the firmware copy area Since the link information for executing the update firmware stored in 311 is replaced by background processing (step S114), it is possible to reduce downtime caused by updating the software.

(Other embodiments)
The present invention is also realized by executing the following processing. That is, software (program) that realizes the functions of the above-described embodiments is supplied to a system or apparatus via a network or various storage media, and a computer (or CPU, MPU, etc.) of the system or apparatus reads the program code. It is a process to be executed. In this case, the program and the storage medium storing the program constitute the present invention.

100 Image forming apparatus 200 Control unit 210 CPU
212 RAM
218 HDD
219 Flash memory 220 Operation unit 310 Firmware 311 Firmware copy area 320 Update program 321 Update firmware storage area 330 Firmware development area

In order to achieve the above object, an information processing apparatus according to claim 1 is an information processing apparatus having firmware and controlled by the firmware, and acquiring update firmware for updating the firmware via a network Obtaining means, deploying means for deploying the update firmware obtained by the obtaining means to a predetermined storage area different from the area where the firmware is stored, and during deployment of the update firmware by the decompressing means, Execution means for executing processing including processing different from processing for deploying update firmware, and processing for controlling the information processing apparatus using the update firmware deployed by the deployment means instead of the firmware And a control means .

Claims (8)

An information processing apparatus that downloads update software for updating software installed in an information processing apparatus and updates the installed software with the downloaded update software,
Download means for downloading the update software to a predetermined first storage area by background processing;
An unfolding means for unfolding the update software in a predetermined second storage area immediately after the download of the update software is completed by the download means;
When updating of the installed software is instructed, the update software expanded in the second storage area by the expansion means is stored in a predetermined third storage area for executing the software Storage means;
In place of the installed software, the storage means includes replacement means for replacing the link information for executing the updated software stored in the third storage area by background processing. apparatus.   If the update is instructed during the deployment of the update software by the deployment unit, the deployment unit terminates the deployment of the update software, discards the update software deployed by the deployment unit, and updates the update software. The information processing apparatus according to claim 1, wherein the installed software is updated without deploying software in the second storage area.   When the update is instructed during the deployment of the update software by the deployment unit, the deployment unit continues the deployment, and the storage unit performs the first after the deployment of the update software by the deployment unit is completed. The information processing apparatus according to claim 1, wherein the updated software expanded in the second storage area is stored in three storage areas.   4. The information processing apparatus according to claim 3, wherein a warning screen indicating that the expansion by the expansion means is continued is displayed.   When the update is instructed during the deployment of the update software by the deployment unit, the deployment unit terminates the deployment of the update software, and the storage unit is deployed before the deployment unit finishes the deployment. The updated software is stored in the third storage area, and the replacement means replaces link information for executing the updated software stored in the third storage area, and the expansion means stores the updated software in the second storage area. The information processing apparatus according to claim 1, wherein the installed software is updated without expanding the update software that has not been expanded in the second storage area.   6. The information processing apparatus according to claim 1, wherein the expansion by the expansion unit is a process of decoding the encoded update software. A method for controlling an information processing apparatus that downloads update software for updating software installed in an information processing apparatus and updates the installed software by the downloaded update software,
A download step of downloading the update software to a predetermined first storage area by background processing;
When the download of the update software is completed by the download step, a development step of immediately deploying the update software in a predetermined second storage area by background processing;
When update of the installed software is instructed, the updated software expanded in the second storage area by the expansion step is stored in a predetermined third storage area for executing the software A memory step;
In place of the installed software, the storage method includes a replacement step of replacing link information for executing the updated software stored in the third storage area by background processing. . A program for downloading update software for updating software installed in an information processing apparatus and causing a computer to execute a control method of the information processing apparatus for updating the installed software by the downloaded update software. ,
The control method is:
A download step of downloading the update software to a predetermined first storage area by background processing;
When the download of the update software is completed by the download step, a development step of immediately deploying the update software in a predetermined second storage area by background processing;
When update of the installed software is instructed, the updated software expanded in the second storage area by the expansion step is stored in a predetermined third storage area for executing the software A memory step;
In place of the installed software, there is provided a replacement step of replacing link information for executing the updated software stored in the third storage area by the storage step by background processing.

Images