JP2016161986A - System, upgrade method, and program; and information processing device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a system that performs software upgrade on a plurality of devices at an appropriate timing.SOLUTION: An information processing device (DFE) 121 adds information indicating that upgrade of installed second software is to be executed, to a notification S403 of the execution of upgrade of first software which is installed in an image processing device (MFP) 122; and transmits the notification S403 to which the information has been added, to a server 113; obtains second upgrade software 417 which is distributed from the server 113; and upgrades the second software by using the second upgrade software 417.SELECTED DRAWING: Figure 4

Description

  The present invention relates to a software version upgrade system, a version upgrade method and program, and an information processing apparatus.

  The software installed on information devices on the network may be upgraded. As one version upgrade method, a distribution server on the network holds a new version of software, and distributes a new version of software in response to a version upgrade request from an information device. Further, when a plurality of information devices are configured as one system, the plurality of information devices may be upgraded.

JP 2012-128571 A JP 2012-163994 A

  Patent Document 1 describes a method in which a biological information imaging apparatus includes a plurality of controllers and upgrades the plurality of controllers. In Patent Document 1, a plurality of controllers are shifted to the upgrade mode, the installed version of each controller is confirmed, each controller that needs to be upgraded is identified, and the controller is upgraded.

  However, when multiple controllers are designed by different companies, the transition method and version upgrade method for the distribution server, version upgrade mode, and version upgrade method are different. difficult.

  Patent Document 2 describes a method in which a management device once receives upgrade software for a plurality of information devices, and distributes the software to each information device in an optimum manner. In Patent Document 2, the management device plays the role of a proxy server for each information device, and mediates between each information device and the distribution server.

  However, when a plurality of information devices are configured as one system, no consideration is given to a method of performing version upgrade by matching the timing in each device.

  An object of the present invention is to solve such conventional problems. In view of the above points, an object of the present invention is to provide a system, a version upgrade method, a program, and an information processing apparatus that perform software upgrades at a suitable timing in a plurality of apparatuses.

  In order to solve the above problems, a system according to the present invention includes an image processing apparatus, an information processing apparatus, first software installed in the image processing apparatus, and the image processing apparatus installed in the information processing apparatus. And a server that manages second software related to the image processing apparatus, wherein the image processing apparatus notifies the server of execution of version upgrade of the first software via the information processing apparatus. Notification means; first acquisition means for acquiring first version upgrade software for upgrading the first software distributed from the server in response to the notification by the notification means; and the first The first software is obtained using the first version upgrade software obtained by the obtaining means. First upgrade means for version upgrade, and the server, in response to a notification from the notification means, a second version for upgrading the first upgrade software and the second software A first distribution unit that distributes version upgrade software, and the information processing apparatus adds to the notification by the notification unit that execution of version upgrade of the second software is performed. Acquired by the transmission means for transmitting the notified notification to the server, the second acquisition means for acquiring the second upgrade software distributed by the first distribution means, and the second acquisition means. A second version upgrade of the second software using the second version upgrade software. Comprising of a version-up means, and characterized in that.

  According to the present invention, software upgrades in a plurality of devices can be performed at an appropriate timing.

It is a figure which shows the structure of a system. It is a block diagram which shows the hardware constitutions of DFE. It is a functional block diagram of DFE. It is a figure which shows the flow of a process between the apparatuses which upgrade software. It is a flowchart which shows the procedure of the basic process in DFE. It is a flowchart which shows the procedure of the software upgrade process. It is a figure which shows the flow of a process between the apparatuses which upgrade software. It is a flowchart which shows the procedure of the software upgrade process.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. The following embodiments do not limit the present invention according to the claims, and all combinations of features described in the embodiments are not necessarily essential to the solution means of the present invention. . The same constituent elements are denoted by the same reference numerals, and the description thereof is omitted.

[First Embodiment]
FIG. 1 is a diagram showing the configuration of the system 100. An image processing apparatus 122, a client PC 111, a distribution server 112, and a DFE 121 are connected to the first network 101 so that they can communicate with each other. Further, another distribution server 113 is connected to the first network 101 via the Internet 103. The DFE 121 is connected to the image processing apparatus 122 via the second network 102 through a network port different from the network port connected to the first network 101. The image processing device 122 is, for example, an MFP. MFP is an abbreviation for MultiFunction Peripheral and is an apparatus in which a plurality of functions such as copying and printers are integrated. Hereinafter, the image processing apparatus 122 will be described as the MFP 122. DFE is an abbreviation for Digital Front End, and is an information processing apparatus for providing function expansion and function assistance to functions such as printing that are connected to the MFP and the MFP has.

  In the system 100, for example, the client PC 111 transmits a job (print job or the like) that can be executed by the MFP 122 to the MFP 122. If the client PC 111 is a print job, printing is performed on a recording medium such as print paper. Can do. In that case, for example, a print application or the like is installed in the client PC 111. Further, firmware or software (hereinafter, collectively referred to as software) corresponding to the version of the print application is installed in the MFP 122 or DFE 121. In that case, when the print application of the client PC 111 is upgraded, the software of the MFP 122 and the DFE 121 needs to be upgraded and matched. Further, when a device related to the function of the MFP 122 such as the DFE 121 is connected to the MFP 122, when the software of the MFP 122 is upgraded, the software of the DFE 121 needs to be upgraded and matched. The distribution servers 112 and 113 manage version information of software installed in each device and upgrade software for upgrading the software. The version upgrade software includes all software formats for updating the version of the installed software. For example, version upgrade software is patch file format correction software.

  When the software of the DFE 121 or the MFP 122 is upgraded, there are a case where the version is upgraded by the distribution server 112 existing on the first network 101 and a case where the version is upgraded by the distribution server 113 via the Internet 103. The software upgrade process of the DFE 121 and the MFP 122 described below can be applied to any of the above cases. In the present embodiment, the software upgrade process of the DFE 121 and the MFP 122 having functions related to printing has been described, but the software upgrade process of the DFE 121 and the MFP 122 having other functions can also be applied.

  With reference to FIG. 4, the flow of processing for upgrading the software of the DFE 121 and the MFP 122 will be described. First, the user instructs execution of software version upgrade on the operation screen of the MFP 122. The MFP 122 transmits a version upgrade request to the predetermined distribution server 112 or the distribution server 113 (S401). In the following description, it is assumed that a version upgrade request is transmitted to the distribution server 113.

  In FIG. 4, communication between the MFP 122 and the distribution server 113 is as follows. The DFE 121 receives a software upgrade request from the MFP 122 to the distribution server 113 via the second network 102, and transfers the software upgrade request from the first network 101 to the distribution server 113. Also, the DFE 121 receives upgrade software from the distribution server 113 to the MFP 122 via the first network 101 and transfers the software from the second network 102 to the MFP 122.

  The version upgrade request target is described in the software version upgrade request command transmitted to the distribution server 113. The upgrade request target is, for example, the MFP 122 that is its own device. In the present embodiment, the DFE 121 adds the DFE 121 as its own device as a version upgrade request target to the version upgrade request transmitted from the MFP 122.

  The distribution server 113 transmits to the MFP 122 an information file 411 in which information such as the name and version of the upgrade software to be upgraded is described (S402). At this time, the DFE 121 copies the transmitted information file 411 and holds it as an information file 412, and transmits the information file 411 to the MFP 122. The MFP 122 receives the received information file 411. In the present embodiment, the received information file 411 is referred to as an information file 413. The information file 411 describes information about both the MFP 122 and the DFE 121.

  Based on the information described in the information file 413, the MFP 122 requests the distribution server 113 to transmit the upgrade software to be upgraded (S403). The distribution server 113 transmits the upgrade software 414 to the MFP 122 (S404). The MFP 122 receives the upgrade software 414. In the present embodiment, the received upgrade software 414 is referred to as upgrade software 415.

  The MFP 122 determines whether the version upgrade software 415 is correct. Whether or not it is correct is, for example, whether or not the received software is authenticated by the system 100. The MFP 122 repeats the processes of S403 and S404 for the version upgrade request target. During the repetition, a request for upgrade software of the DFE 121 (S405) and transmission of upgrade software (S406) are performed. When it is determined that the DFE 121 has received its own upgrade software, the DFE 121 copies the transmitted upgrade software 416 and stores it as the upgrade software 417. At the same time, the DFE 121 transfers the upgrade software 416 to the MFP 122. The MFP 122 receives the upgrade software 416. In the present embodiment, the received upgrade software 416 is referred to as upgrade software 418.

  If the MFP 122 determines based on the information file 413 that all the upgrade software to be received is available, the MFP 122 upgrades its own software (S408). If the DFE 121 determines based on the information file 412 that all version upgrade software to be received is available, the DFE 121 upgrades its own software (S407).

  For upgrading the software in the MFP 122 and the DFE 121, a general method such as restart may be used. Note that the MFP 122 does not use the received upgrade software 418 for the DFE 121 in the upgrade process.

  FIG. 2 is a block diagram showing a hardware configuration of the DFE 121. As shown in FIG. The DFE 121 includes a CPU 211, a ROM 212, a RAM 213, a display / operation device interface (I / F) unit 214, a storage device I / F unit 215, a printer device I / F unit 216, a first network I / F unit 217, and a second network. I / F unit 218 is included. Such hardware is realized by, for example, an LSI called a chip set. In addition, a plurality of functional blocks may be realized by one chip set. The above functional blocks are connected to each other via an internal bus 220 so that they can communicate with each other.

  The storage device 219 is an external storage device such as a hard disk drive (HDD) or a flash memory, and is connected to the storage device I / F unit 215. The first network 101 and the second network 102 are, for example, Ethernet (registered trademark), and are connected to the first network I / F unit 217 and the second network I / F unit 218, respectively. The second network 102 is also connected to the MFP 122. Further, the MFP 122 is connected to the printer apparatus I / F unit 216 of the DFE 121 with a dedicated cable or a general-purpose cable. This connection is generally called Video, and is used, for example, to transmit print data subjected to image processing in the DFE 121 to the MFP 122. The display / operation device 231 includes, for example, a display for display, a keyboard for input operation, and a pointing device, and is connected to the display / operation device I / F unit 214 via a display cable, a USB cable, or the like.

  In the DFE 121, the CPU 211 executes part or all of the program on the RAM 213 based on the program stored in the ROM 212 or the storage device 219. In addition, the first network I / F unit 217 and the second network I / F unit 218 communicate with the client PC 111, the distribution server 112, and the distribution server 113 by executing the above programs. The display / operation device I / F unit 214 displays, for example, the processing status of the software operating on the DFE 121 to the user or accepts an instruction operation from the user by executing the above program. The storage device I / F unit 215 stores files and data by executing the above-described program. Further, the printer apparatus I / F unit 216 transmits print data to the MFP 122 by executing the above program. In the present embodiment, the MFP 122 performs printing on a recording medium by, for example, an inkjet recording method or an electrophotographic method.

  The first network 101 and the second network 102 may be a wired network or a wireless network. Further, the first network I / F unit 217 and the second network I / F unit 218 have configurations according to the media of the first network 101 and the second network 102.

  FIG. 3 is a functional block diagram of the DFE 121. The functional block diagram of FIG. 3 is realized by the CPU 211 executing a part or all of the program on the RAM 213 based on the program stored in the ROM 212 or the storage device 219.

  The first network I / F processing unit 306 and the second network I / F processing unit 307 operate in cooperation with the first network I / F unit 217 and the second network I / F unit 218 which are hardware. Then, it functions as a so-called network protocol stack for processing the hardware driver software and the TCP / IP layer. The first network I / F processing unit 306 processes the TCP / IP header on the data received as the network packet addressed to itself by the first network I / F unit 217 and processed with the MAC header, and processes the payload (data body ) Is stored in the data storage unit 308.

  The second network I / F processing unit 307 processes the TCP / IP header on the data received as the network packet addressed to itself by the second network I / F unit 218 and processed with the MAC header, and performs the payload (data body ) Is stored in the data storage unit 308. The data storage unit 308 is realized in the storage device 219, for example. In addition, the first network I / F processing unit 306 and the second network I / F processing unit 307 transmit the data body stored in the data storage unit 308 to the first network 101 and the second network 102. The first network 101 and the second network 102 are assumed to be Ethernet, but other communication systems such as Token Ring and optical fiber may be used.

  The first service specific processing unit 301 executes the upgrade process in the present embodiment. The second service specific processing unit 302, the third service specific processing unit 303, and the fourth service specific processing unit 304 are processing units corresponding to processes other than the upgrade process. The service basic processing unit 305 is a processing unit corresponding to processing common to a plurality of services of the first service specific processing unit 301 to the fourth service specific processing unit 304. An example of the operation of the second service specific processing unit 302 to the second network I / F processing unit 307 will be described with reference to FIG.

  FIG. 5 shows a basic processing procedure common to packet processing such as transmission of a software upgrade request (S401) and reply of upgrade software (S402) in the sequence diagram of FIG. It is a flowchart. The flowcharts of FIGS. 5 and 6 are realized by the CPU 211 executing a part or all of the program on the RAM 213 based on the program stored in the ROM 212 or the storage device 219, for example.

  When the DFE 121 starts processing (S500), the first network I / F processing unit 306 or the second network I / F processing unit 307 receives a network packet from the network (S501). Then, the service basic processing unit 305 stores the payload in the received network packet in the data storage unit 308 (S502). After storing the payload in the data storage unit 308, the service basic processing unit 305 verifies the payload data (S503). In this verification, for example, it is verified whether or not a character string, a data name, a data format, and the like predetermined for each unique service exist. As a result of the verification, if a predetermined character string, data name, data format, or the like exists, the service basic processing unit 305 notifies the corresponding service specific processing unit among the service specific processing units 301 to 304 (S504). . Upon receiving the notification, the service specific processing unit performs the service specific processing on the payload (S505). The process performed at that time is, for example, a process of copying the corresponding data in the payload or editing a part of the character string in the payload. When the processing on the payload is completed, the service basic processing unit 305 passes the processed payload to the first network I / F processing unit 306 or the second network I / F processing unit 307 (S506). The first network I / F processing unit 306 or the second network I / F processing unit 308 transmits the transferred payload to the network (S507), and ends the process of FIG. 5 (S508). The processes of S506 and S507 are so-called network packet transmission processes, and may be realized by existing network technology.

  FIG. 6 is a flowchart showing a procedure of software upgrade processing in the present embodiment. In FIG. 6, the processing of the service basic processing unit 305 in S501 to S504 and S506 to S507 in FIG. 5 is the same. Therefore, in FIG. 6, the description of the processing of the service basic processing unit 305 is omitted, and the processing of the service specific processing unit in S505 will be described.

  When the DFE 121 starts processing (S600), the service basic processing unit 305 verifies the payload and determines whether there is a software version upgrade request (S601). For example, the service basic processing unit 305 determines whether a character string of a software upgrade request command from the MFP 122 to the distribution server 113 exists in the payload. As a result of the determination (S602), when it is determined that it exists, the process proceeds to S603, and when it is determined that it does not exist, the process of S601 is repeated.

  In step S <b> 603, the first service specific processing unit 301 refers to the parameter of the software upgrade request command in the payload and determines whether the DFE 121 is included in the upgrade request target. For example, when the upgrade request command and the upgrade request target parameter have the following structure, it is determined that the upgrade request is made using the character string <request versionup>. Further, the object is determined by the parameter “Target =”. In the following example, it can be seen that the main controller and the finisher controller are targets, and the DFE 121 is not included as a target. As a result of the determination in S603 (S604), if it is determined that the DFE 121 is included, the process proceeds to S606, and if it is determined that the DFE 121 is not included, the process proceeds to S605.

<Request versionup>
Target = Main_controller
Target = Finisher_controller
</ Request versionup>
In S605, the first service specific processing unit 301 adds DFE to the upgrade request target (S605). This addition is performed by adding a “Target = DFE_controller” line to the corresponding portion of the payload command and changing the payload as follows.

<Request versionup>
Target = Main_controller
Target = Finisher_controller
Target = DFE_controller
</ Request versionup>
In S606, as described with reference to FIG. 5, the first network I / F processing unit 306 or the second network I / F processing unit 307 transmits the network packet in which the payload is processed to the network. The processing so far corresponds to S401 in FIG. Then, the process of S606 is performed as a process for the next received payload.

  In step S606, the first service specific processing unit 301 verifies the payload and determines whether there is version upgrade information. In the present embodiment, when the distribution server 113 receives the upgrade request command and transmits the upgrade software designated as the upgrade request target, first, the distribution server 113 transmits a list of upgrade software to be transmitted. This list is, for example, a list of target software to be upgraded in the system 100 when the software in the MFP 122 is upgraded. For example, the distribution server 113 transmits a file called info.lst as shown below using the list of version upgrade software as version upgrade information. This process corresponds to S402 in FIG. In step S606, the first service specific processing unit 301 determines whether a file named info.lst exists in the payload. As a result of the determination (S607), when it is determined that it exists, the process proceeds to S608, and when it is determined that it does not exist, the process of S606 is repeated.

<File_name = info.lst>
<Versionup>
Target = Main_controller; Name = main.pkg.Ver = 5.01, Checksum = 1234,
Target = Finisher_controller; Name = finisher.pkg. Ver = 5.02, Checksum = 4567,
Target = DFE_controller; Name = dfe.dwl.Ver = 012, Checksum = 7890,
</ Versionup>
In the present embodiment, the first service specific processing unit 301 copies the received info.lst to a storage area such as the RAM 213 before performing the processing of S608, and thereafter continues the processing for the copied data. . In addition, the first service specific processing unit 301 transmits the received info.lst to the MFP 122, and the MFP 122 uses the info.lst transmitted from the first service specific processing unit 301 to perform software upgrade processing. Do.

  Next, the first service specific processing unit 301 analyzes info.lst and acquires information such as a software name (S608). In the above example of info.lst, the first service specific processing unit 301 analyzes the contents of info.lst data. The name of the upgrade software for DFE 121 is “dfe.dwl”, the version is “012”, and the checksum is “7890”.

  Thereafter, the processing of S403 to S406 in FIG. 4 is performed, and in particular, the processing after S609 is performed in the DFE 121.

  In step S609, the first service specific processing unit 301 verifies the payload, and determines whether there is version upgrade software. This process is performed in S404 or S406 of FIG. Also, in this determination process, for example, when the upgrade software is transmitted from the distribution server 113, the payload is saved in the data storage unit 308. Therefore, the data storage unit 308 is searched for data whose name is dfe.dwl. Is done. As a result of the determination (S610), if it is determined that there is version upgrade software, the process proceeds to S611. If it is determined that there is no version upgrade software, the process proceeds to S621.

  In step S611, the first service specific processing unit 301 acquires version upgrade software. Then, the first service specific processing unit 301 verifies whether or not the acquired version upgrade software is correct (S612). This verification is done by, for example, analyzing dfe.dwl using the version obtained by analyzing info.lst and the value of checksum, the analysis is missing, its version is 012, and the checksum calculation result of dfe.dwl If is 7890, verify that it is correct. As a result of the verification, if it is determined to be correct, the process proceeds to S613, and if it is determined to be incorrect, an error display (not shown) is performed. When an error is displayed, the software waits for an instruction input from the user regarding whether or not the software upgrade process can be interrupted. When the interrupt instruction input is accepted, the process ends or the process is repeated from S601.

  Next, the first service specific processing unit 301 executes a software upgrade process (S613). In executing the software version upgrade process, a general version upgrade method may be used. Usually, if the software upgrade process is performed, the system may need to be restarted. Since the DFE 121 transfers the upgrade software from the distribution server 113 to the MFP 122, the transfer is interrupted if the DFE 121 is restarted, and the software upgrade process in the MFP 122 fails. Therefore, the execution of the software upgrade process in the DFE 121 needs to wait until the transmission of the upgrade software to the MFP 122 is completed.

  Therefore, the first service specific processing unit 301 pays attention to an end command transmitted when the transmission of the upgrade software from the distribution server 113 to the MFP 122 ends. This end command may be predetermined within the system 100, for example. The first service specific processing unit 301 verifies the payload and determines whether or not the transmission of the upgrade software has ended based on whether or not the end command is detected (S614). Alternatively, the first service specific processing unit 301 acquires not only the DFE 121 but also information on all the file names to be transmitted when analyzing the info.lst in S608, and when verifying the payload in S609, these files are stored. You may make it determine whether all exist.

  If the first service specific processing unit 301 determines that the transmission of the upgrade software has been completed, the first service specific processing unit 301 performs a screen display process that allows the user to select whether or not to reboot (S615). As described with reference to FIG. 1, since the execution instruction for the software upgrade process is performed on the operation screen of the MFP 122, an indication whether the DFE 121 may be rebooted is displayed on the operation screen of the MFP 122. . This display processing is executed by, for example, remote display processing via the second network 102 between the MFP 122 and the DFE 121. The user can monitor the upgrade process status of the MFP 122 on the operation screen of the MFP 122. When it is determined that the reception of the upgrade software has been completed and the DFE 121 may be restarted, the user inputs an instruction to approve the restart of the DFE 121 on the operation screen.

  When the MFP 122 notifies the DFE 121 of the approval request, the first service specific processing unit 301 executes a reboot (S616). In rebooting the DFE 121, for example, an OS reboot command or a restart command prepared as a system command of the DFE 121 may be executed. When the DFE 121 is restarted, the process of FIG. 6 is terminated (S630).

  Next, the case where it is determined in S610 that there is no upgrade software will be described. For example, when the first service specific processing unit 301 analyzes info.lst and all of the upgrade software has been transmitted, the upgrade software for the DFE 121 is not found. If not found. Alternatively, the upgrade software for the DFE 121 is not found even though an end command indicating that transmission of the upgrade software has ended is detected. In this case, the first service specific processing unit 301 displays an error message indicating that version upgrade software is not found and a screen that can be canceled on the operation screen of the MFP 122, and waits for an instruction input from the user (S621). If the user inputs an instruction to cancel, the first service specific processing unit 301 stops the software upgrade process (S622) and ends the process of FIG. 6 (S630).

  As described above, in this embodiment, first, the MFP 122 transmits a software upgrade request to the distribution server 113. If the DFE 121 located between the communication path between the MFP 122 and the distribution server 113 does not describe itself in the upgrade request target, the DFE 121 adds the DFE 121 and transfers the software upgrade request to the distribution server 113. Upon receiving the software upgrade request, the distribution server 113 transmits a list of upgrade software (upgrade information) for each device. The DFE 121 copies the upgrade information to itself and transfers it to the MFP 122. As a result, the MFP 122 and the DFE 121 can grasp software upgrade information for each apparatus.

  The MFP 122 sequentially sends a request for upgrade software according to the upgrade information of each device, and the distribution server 113 sends the upgrade software in response to the request. The DFE 121 acquires upgrade software corresponding to itself if there is software corresponding to the upgrade software transmitted from the distribution server 113.

  With the configuration as described above, even when a plurality of devices are configured as a system and the software upgrade method for each device is different, the execution of the software upgrade in each device is synchronized at an appropriate timing. It can be carried out.

[Second Embodiment]
In the first embodiment, the distribution server 113 distributes version upgrade software for both the DFE 121 and the MFP 122. In the present embodiment, a distribution server 113 that distributes version upgrade software for the MFP 122 and a distribution server 112 that distributes version upgrade software for the DFE 121 are used. In FIG. 1, the distribution server 113 for the MFP 122 is configured on the Internet 103, and the distribution server 112 for the DFE 121 is configured on the first network 101. However, these servers may have other configurations as long as they can communicate with the DFE 121 and the MFP 122. In this embodiment, the distribution server 113 distributes the upgrade software to the MFP 122, and the distribution server 112 distributes the upgrade software to the DFE 121. The description of the hardware block diagram of FIG. 2, the processing function block diagram of FIG. 3, and the flowchart of FIG. 5 is the same in this embodiment.

  With reference to FIG. 7, the flow of processing for upgrading the software of the DFE 121 and the MFP 122 will be described. First, the user instructs execution of software version upgrade on the operation screen of the MFP 122. The MFP 122 transmits a version upgrade request to the predetermined distribution server 113 (S701).

  In FIG. 7, communication between the MFP 122 and the distribution server 113 is as follows. The DFE 121 receives a version upgrade request from the MFP 122 to the distribution server 113 via the second network 102 and transfers the request from the first network 101 to the distribution server 113. Further, the DFE 121 receives version upgrade software from the distribution server 113 to the MFP 122 via the first network 101 and transfers the software from the second network 102 to the MFP 122.

  The upgrade request from the MFP 122 describes the upgrade request target. The upgrade request target is, for example, the MFP 122 and the DFE 121 that is operationally related to the MFP 122. The distribution server 113 transmits to the MFP 122 an information file 711 in which information such as the name and version of the requested version upgrade request target software is described (S702). At this time, the DFE 121 copies the transmitted information file 711 and holds it as an information file 712, and transmits the information file 711 to the MFP 122. The MFP 122 receives the received information file 711. In the present embodiment, the received information file 711 is referred to as an information file 713.

  Based on the information described in the information file 413, the MFP 122 requests the distribution server 113 to transmit the upgrade software to be upgraded (S703). The distribution server 113 transmits the upgrade software 714 to the MFP 122 (S704). The MFP 122 receives the upgrade software 714. In the present embodiment, the received upgrade software 714 is referred to as upgrade software 715.

  The MFP 122 determines whether the version upgrade software 715 is correct. Whether or not it is correct is, for example, whether or not the received software is authenticated by the system 100. The MFP 122 repeats the processes of S703 and S704 for the version upgrade request target. During the repetition, a request for software for upgrading the DFE 121 is made (S703 '). However, in this embodiment, the distribution server 113 does not have version upgrade software for the DFE 121. Accordingly, the distribution server 113 transmits an error indicating that the requested upgrade software does not exist (S704 ').

  The DFE 121 analyzes the information file 712 and detects that its own version upgrade software request (S703 ') has been made. Furthermore, the DFE 121 detects an error indicating that the DFE 121 version upgrade software does not exist in the distribution server 113 based on the reply from the distribution server 113 (S704 '). When detecting the error, the DFE 121 requests the distribution server 112 to transmit the upgrade software (S705). The distribution server 112 transmits the upgrade software 716 to the DFE 121 (S706). The DFE 121 receives the upgrade software 716 and stores it in the DFE 121 as the upgrade software 717.

  Here, in addition to the method by which the DFE 121 detects the above-described error, a method by which the DFE 121 determines to make a request for version upgrade software (S705) to the distribution server 112 will be described.

  When the MFP 122 analyzes the information file 713, there may be a case where an object that is not requested to the distribution server 113 among the upgrade request objects can be detected. For example, this is a case where information (name or the like) for identifying the requested delivery server is described in the information file 713. Alternatively, based on the option configuration information of the MFP 122 held in advance by the MFP 122, the MFP 122 knows which distribution server holds the upgrade software corresponding to each option as a distribution target. In these cases, the MFP 122 does not have to make a request that causes an error in S703 '. In that case, the DFE 121 may detect that the request in S703 'is not transmitted from the MFP 122 by, for example, a timeout from the last request in S703.

  Alternatively, if the MFP 122 recognizes that the distribution server 112 is requested for the software for upgrading the DFE 121 when the information file 713 is analyzed, the MFP 122 may notify the DFE 121 accordingly. Upon receiving the notification, the DFE 121 requests the DFE 121 distribution server 112 for the upgrade software in S705.

  Alternatively, if the DFE 121 recognizes that the distribution server 112 is requested for the upgrade software of the DFE 121 when the information file 712 is analyzed, the DFE 121 may make a request for the upgrade software in S705 to the distribution server 112.

  As described above, the DFE 121 requests upgrade software from the distribution server 112 for the DFE 121 by various methods.

  The DFE 121 determines whether or not the version upgrade software 717 is correct. Whether or not it is correct is, for example, whether or not the received software is authenticated by the system 100. The DFE 121 repeats the processes of S705 and S706 for the version upgrade request target.

  If the MFP 122 determines based on the information file 713 that all the upgrade software to be received has been prepared, the MFP 122 executes an upgrade process of its own software (S708). If the DFE 121 determines based on the information file 712 that all the upgrade software to be received has been prepared, the DFE 121 executes an upgrade process for its own software (S707).

  FIG. 8 is a flowchart illustrating a procedure of software upgrade processing according to the present embodiment. In FIG. 8, the processing of the service basic processing unit 305 in S501 to S504 and S506 to S507 in FIG. 5 is the same. Therefore, in FIG. 8, the description of the processing of the service basic processing unit 305 is omitted, and the processing of the service specific processing unit in S505 will be described. 8 is realized by the CPU 211 executing a part or all of the program on the RAM 213 based on a program stored in the ROM 212 or the storage device 219, for example.

  When the DFE 121 starts processing (S800), the service basic processing unit 305 verifies the payload and determines whether there is a software version upgrade request (S801). For example, the service basic processing unit 305 determines whether a character string of a software upgrade request command from the MFP 122 to the distribution server 113 exists in the payload. As a result of the determination (S802), when it is determined that it exists, the process proceeds to S803, and when it is determined that it does not exist, the process of S801 is repeated.

  In S803, the first service specific processing unit 301 verifies the payload, and if it detects info.lst transmitted from the distribution server 113, it copies it to a storage area such as the RAM 213. Continue processing. In addition, the first service specific processing unit 301 transmits the received info.lst to the MFP 122, and the MFP 122 uses the info.lst transmitted from the first service specific processing unit 301 to perform software upgrade processing. Do.

  In step S <b> 804, the first service specific processing unit 301 determines whether there is a request for upgrade software for the DFE 121. For example, if the upgrade request target parameter of the upgrade request command received from the MFP 122 in S701 has the following structure, it is determined that the upgrade request is made with the character string <request versionup>. Then, the object is determined by the parameter “Target =”. In the following example, it can be seen that the main controller, the finisher controller, and the DFE are targets.

<Request versionup>
Target = Main_controller
Target = Finisher_controller
Target = DFE_controller
</ Request versionup>
When the first service specific processing unit 301 analyzes the payload of the received network packet and detects that the upgrade software request for the DFE 121 is transmitted from the MFP 122 to the distribution server 113, the following processing is performed. I do. After the detection, the first service specific processing unit 301 determines whether the DFE 121 upgrade software has been distributed from the distribution server 113 or whether an error indicating that there is no DFE 121 upgrade software has been transmitted to the distribution server 113. judge. At that time, as described in the sequence diagram of FIG. 7, another detection method may be used.

  As a result of the determination (S805), when it is determined that an error indicating that the DFE 121 version upgrade software does not exist is transmitted to the distribution server 113, the process proceeds to S806. On the other hand, if it is determined that the version upgrade software for the DFE 121 has been distributed from the distribution server 113, the processing in FIG. 8 is terminated, and the processing described in the first embodiment is performed.

  If it is determined that an error indicating that there is no version upgrade software for the DFE 121 has been transmitted to the distribution server 113, the first service specific processing unit 301 thereafter causes the distribution server 112 to distribute the version upgrade software. Process.

  The first service specific processing unit 301 tries to connect to the distribution server 112 for the DFE 121. As a result of the connection attempt (S807), if it is determined that the connection is impossible, the process proceeds to S821. In step S <b> 821, the first service specific processing unit 301 displays an error indicating that the connection to the distribution server 112 cannot be made on the display / operation device 231, and waits for an instruction input from the user. When the first service specific processing unit 301 receives a connection stop instruction input from the user via the display / operation device 231, the first service specific processing unit 301 stops the connection to the distribution server 112 and also stops the software upgrade process (S822). ), The process of FIG. 8 is terminated (S830).

  If it is determined in S807 that connection is possible, the process proceeds to S808.

  In step S <b> 808, the first service specific processing unit 301 inquires of the distribution server 112 whether there is version upgrade software for the DFE 121. As a result of the inquiry (S809), if it is determined that it does not exist, the process proceeds to S823. In S823, the first service specific processing unit 301 displays an error indicating that the DFE 121 version upgrade software does not exist on the distribution server 112 on the display / operation device 231, and waits for an instruction input from the user. When the first service specific processing unit 301 receives a connection stop instruction input from the user via the display / operation device 231, the first service specific processing unit 301 stops the software upgrade process (S824) and ends the process of FIG. 8 (S830). ).

  As a result of the inquiry (S809), if it is determined that it exists, the process proceeds to S810. The first service specific processing unit 301 requests the distribution server 112 to transmit upgrade software for the DFE 121 (S810). The first service specific processing unit 301 verifies whether or not the upgrade software received from the distribution server 112 is correct (S811). This verification is performed using information such as the software name, version, and checksum described in the information file 712. For example, as in the first embodiment, dfe.dwl is analyzed using the version and checksum values obtained by analyzing info.lst, and the version is 012. The checksum of dfe.dwl If the calculation result of is 7890, it is verified as correct.

  Next, the first service specific processing unit 301 executes a software upgrade process (S812). In executing the software version upgrade process, a general version upgrade method may be used. Usually, if a software upgrade process is performed, it is often necessary to restart the system. However, since the DFE 121 transfers the upgrade software from the distribution server 113 to the MFP 122, the transfer is interrupted if the DFE 121 is restarted, and the upgrade of the MFP 122 fails. Therefore, the execution of the upgrade needs to wait until the transmission of the upgrade software to the MFP 122 is completed. Therefore, the first service specific processing unit 301 pays attention to an end command transmitted when the transmission of the upgrade software from the distribution server 113 to the MFP 122 ends. This end command may be predetermined within the system 100, for example. The first service specific processing unit 301 verifies the payload, and determines whether or not transmission of the upgrade software to the MFP 122 is completed based on the detection result of the transmission of the end command (S813). Alternatively, the first service specific processing unit 301 acquires information on all file names of the upgrade software for the MFP 122 when acquiring and analyzing info.lst in S803, and whether all of these files exist in S804. May be determined.

  If the first service specific processing unit 301 determines that the transmission of the upgrade software has been completed, the first service specific processing unit 301 performs a screen display process that allows the user to select whether or not to reboot (S814). As described with reference to FIG. 1, an instruction to upgrade the software is given on the operation screen of the MFP 122, so that an indication whether the DFE 121 may be rebooted is displayed on the operation screen of the MFP 122. This display processing is executed by, for example, remote display processing via the second network 102 between the MFP 122 and the DFE 121. The user can monitor the upgrade status of the MFP 122 on the operation screen of the MFP 122. When it is determined that the reception of the upgrade software has been completed and the DFE 121 may be restarted, the user inputs an instruction to approve the restart of the DFE 121 on the operation screen.

  When the MFP 122 notifies the DFE 121 of the approval request, the first service specific processing unit 301 executes a reboot (S815). In rebooting the DFE 121, for example, an OS reboot command or a restart command prepared as a system command of the DFE 121 may be executed. When the DFE 121 is restarted, the process of FIG. 8 is terminated (S830).

  As described above, in the present embodiment, first, the MFP 122 transmits a software upgrade request for the DFE 121 and the MFP 122 to the distribution server 113. Upon receiving the software upgrade request, the distribution server 113 transmits a list of upgrade software (upgrade information) for each device. The DFE 121 copies the upgrade information to itself and transfers it to the MFP 122. As a result, the MFP 122 and the DFE 121 can grasp software upgrade information for each apparatus.

  The MFP 122 sequentially sends a request for upgrade software according to the upgrade information of each device, and the distribution server 113 sends the upgrade software in response to the request. When the DFE 121 receives an error indicating that the DFE 121 upgrade software does not exist in the distribution server 112, the DFE 121 tries to connect to the distribution server 112. When the distribution server 112 can connect to the distribution server 112 and recognizes that the DFE 121 upgrade software exists in the distribution server 112, the distribution server 112 requests the DFE 121 upgrade software.

  With the configuration as described above, even when a plurality of devices are configured as a system and the software upgrade method for each device is different, the execution of the software upgrade in each device is synchronized at an appropriate timing. It can be carried out.

  In the second embodiment, the MFP 122 sends a software upgrade request to both the DFE 121 and the MFP 122 as upgrade request targets. However, as in the first embodiment, the DFE 121 may add itself to the version upgrade request target. Further, when the MFP 122 transmits only the version upgrade request target itself and the distribution server 113 receives the software upgrade request, both the MFP 122 and the DFE 121 may be included in the upgrade information.

  In the second embodiment, the DFE 121 attempts to connect to the distribution server 112 when receiving an error notification from the distribution server 113. However, the DFE 121 predetermines the connection trial order when there are a plurality of distribution servers. Anyway. Alternatively, it may be described in the error notification transmitted by the distribution server 113 that version upgrade software for the DFE 121 exists.

[Other Examples]
The present invention supplies a program that realizes one or more functions of the above-described embodiments to a system or apparatus via a network or a storage medium, and one or more processors in a computer of the system or apparatus read and execute the program This process can be realized. It can also be realized by a circuit (for example, ASIC) that realizes one or more functions.

  112, 113 Distribution server: 121 DFE: 122 MFP: 211 CPU: 212 ROM: 213 RAM: 219 Storage device

Claims (15)

An image processing device;
An information processing device;
A system that includes first software installed in the image processing apparatus and a server that manages second software installed in the information processing apparatus and related to the image processing apparatus;
The image processing apparatus includes:
Notification means for notifying the server of execution of the upgrade of the first software via the information processing apparatus;
First acquisition means for acquiring first upgrade software for upgrading the first software distributed from the server in response to the notification by the notification means;
First upgrade means for upgrading the first software using the first upgrade software acquired by the first acquisition means, and
The server
First distribution means for distributing the first version-up software and second version-up software for upgrading the second software in response to the notification by the notification means;
The information processing apparatus includes:
To the notification by the notification means, adding that the execution of version upgrade of the second software is performed, and a transmission means for transmitting the added notification to the server,
Second acquisition means for acquiring the second version upgrade software distributed by the first distribution means;
Second upgrade means for upgrading the second software using the second upgrade software acquired by the second acquisition means,
A system characterized by that. An image processing device;
An information processing device;
A system that includes first software installed in the image processing apparatus and a server that manages second software installed in the information processing apparatus and related to the image processing apparatus;
The image processing apparatus includes:
Notification means for notifying the server of execution of the upgrade of the first software;
First acquisition means for acquiring first upgrade software for upgrading the first software distributed from the server in response to the notification by the notification means;
First upgrade means for upgrading the first software using the first upgrade software acquired by the first acquisition means, and
The server
First distribution means for distributing the first version-up software and second version-up software for upgrading the second software in response to the notification by the notification means;
The information processing apparatus includes:
Second acquisition means for acquiring the second version upgrade software distributed by the first distribution means;
Second upgrade means for upgrading the second software using the second upgrade software acquired by the second acquisition means,
A system characterized by that. The first distribution means transmits the first upgrade software and the second upgrade software to the information processing apparatus,
The information processing apparatus includes:
3. The system according to claim 1, further comprising a first transfer unit configured to transfer the first upgrade software to the image processing apparatus. The information processing apparatus includes:
Determination means for determining whether the upgrade software received from the server is the first upgrade software or the second upgrade software; and
The second acquisition unit acquires the second version upgrade software when the determination unit determines that the received version upgrade software is the second version upgrade software,
When the determination unit determines that the received upgrade software is the first upgrade software, the first transfer unit sends the first upgrade software to the image processing apparatus. Forward,
The system according to claim 3. The server
In response to the notification by the notification means, before distributing the first version-up software and the second version-up software, the software to be upgraded in relation to the version upgrade of the first software A second distribution means for distributing the list;
The determination means determines whether the upgrade software received from the server is the first upgrade software based on the list distributed from the server or the second upgrade software. Determine if there is,
The system according to claim 4. The second distribution means transmits the list to the information processing apparatus;
The information processing apparatus includes:
6. The system according to claim 5, further comprising second transfer means for acquiring the list transmitted by the second distribution means and transferring the list to the image processing apparatus. The server
A second notification means for notifying the image processing apparatus via the information processing apparatus that there is no version upgrade software to be distributed in response to the notification by the notification means;
The information processing apparatus includes:
Third acquisition means for acquiring a notification by the second notification means;
Requesting means for requesting the second upgrade software from the second server when the notification acquired by the third acquisition means indicates that the second upgrade software is not present in the server; The system according to claim 6, further comprising: Image processing apparatus, and
The information processing apparatus capable of communicating via a network with a server that manages the first software installed in the image processing apparatus and the second software installed in the information processing apparatus and related to the image processing apparatus Because
Obtaining means for obtaining notification of execution of version upgrade of the first software transmitted from the image processing apparatus to the server;
To the notification acquired by the acquisition unit, a transmission unit that adds execution of upgrade of the second software and transmits the added notification to the server;
Second acquisition means for acquiring second version upgrade software for upgrading the second software distributed from the server;
Version upgrade means for upgrading the second software using the second version upgrade software acquired by the second acquisition means;
An information processing apparatus comprising: Determination means for determining whether the upgrade software received from the server is the first upgrade software for upgrading the first software or the second upgrade software Further comprising
The second acquisition unit acquires the second version upgrade software when the determination unit determines that the received version upgrade software is the second version upgrade software. The information processing apparatus according to claim 8.   A transfer unit configured to transfer the first upgrade software to the image processing apparatus when the determination unit determines that the received upgrade software is the first upgrade software; The information processing apparatus according to claim 9. Receiving means for receiving from the server a list of software to be upgraded in connection with upgrading of the first software;
The determination means determines whether the upgrade software received from the server is the first upgrade software or the second upgrade software based on the list received by the reception means. The information processing apparatus according to claim 9, wherein the information processing apparatus determines whether there is any. An image processing device;
An information processing device;
Version upgrade method executed in a system including first software installed in the image processing apparatus and a server that manages second software installed in the information processing apparatus and related to the image processing apparatus Because
The image processing apparatus is
A notification step of notifying the server of the execution of the upgrade of the first software via the information processing apparatus;
A first acquisition step of acquiring a first version upgrade software for upgrading the first software distributed from the server in response to the notification in the notification step;
A first version upgrade step of upgrading the first software using the first version upgrade software acquired in the first acquisition step, and
The server is
In response to the notification in the notification step, the first distribution step of distributing the first version-up software and the second version-up software for upgrading the second software,
The information processing apparatus is
To the notification in the notification step, adding that the second software version upgrade is executed, and transmitting the added notification to the server,
A second acquisition step of acquiring the second version upgrade software distributed in the first distribution step;
A second version upgrade step of upgrading the second software using the second version upgrade software acquired in the second acquisition step,
A version upgrade method characterized by that. An image processing device;
An information processing device;
Version upgrade method executed in a system including first software installed in the image processing apparatus and a server that manages second software installed in the information processing apparatus and related to the image processing apparatus Because
The image processing apparatus is
A notification step of notifying the server of execution of the upgrade of the first software;
A first acquisition step of acquiring a first version upgrade software for upgrading the first software distributed from the server in response to the notification in the notification step;
A first version upgrade step of upgrading the first software using the first version upgrade software acquired in the first acquisition step, and
The server is
In response to the notification in the notification step, the first distribution step of distributing the first version-up software and the second version-up software for upgrading the second software,
The information processing apparatus is
A second acquisition step of acquiring the second version upgrade software distributed in the first distribution step;
A second version upgrade step of upgrading the second software using the second version upgrade software acquired in the second acquisition step,
A version upgrade method characterized by that. Image processing apparatus, and
The information processing apparatus capable of communicating via a network with a server that manages the first software installed in the image processing apparatus and the second software installed in the information processing apparatus and related to the image processing apparatus A version upgrade method executed in
An acquisition step of acquiring a notification of execution of the upgrade of the first software transmitted from the image processing apparatus to the server;
To the notification acquired in the acquisition step, adding that the second software version upgrade is performed, and transmitting the added notification to the server,
A second acquisition step of acquiring second version upgrade software for upgrading the second software distributed from the server;
A version upgrade step of upgrading the second software using the second version upgrade software acquired in the second acquisition step;
A version-up method characterized by comprising:   The program for making a computer perform each process of the version upgrade method of Claim 14.

Images