Systems and methods

Abstract

The aim is to make it possible to check the results of firmware updates remotely. [Solution] A system having an image processing device and a distribution management server that manages the distribution of firmware operating on the image processing device, and having a distribution means that distributes firmware to be distributed as instructed in distribution instruction information from the image processing device to the image processing device, and the distribution management server has an acquisition means that acquires information about firmware installed in the image processing device, and an update means that updates the distribution status, which is the distribution result of the firmware to be distributed as instructed in the distribution instruction information, based on whether the information about the installed firmware corresponds to the information about the firmware to be distributed as instructed in the distribution instruction information, without receiving the update result of the firmware to be distributed as instructed in the distribution instruction information from the image processing device.

Description

[Technical Field]

[0001] The present invention relates to a system and a method, and more particularly to a system including an image processing device and a distribution management server, and a control method thereof. [Background technology]

[0002] In the past, when firmware for image forming devices such as printers and multifunction peripherals needed to be updated due to a version upgrade, malfunction, etc., a service technician would visit the customer's site and manually perform the update, which resulted in high costs for firmware updates.

[0003] Recently, a technique has been devised for updating firmware by storing the firmware in a rewritable storage device such as a flash memory and transmitting the firmware via the Internet.

[0004] Patent Document 1 proposes a system for remotely issuing instructions to update firmware for image forming devices. A distribution management server that controls distribution instructs multiple image forming devices on firmware download and installation times. Upon receiving the instructions, the image forming devices download the firmware from the distribution management server at the specified time and use the downloaded firmware to perform the update. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Application Laid-Open No. 2012-059180 Summary of the Invention [Problem to be solved by the invention]

[0006] Manufacturers of image forming devices and service providers that provide device management services want to remotely check the firmware update status. However, after the firmware is distributed, the image forming device to which the firmware is applied may not send the distribution result, or some kind of communication problem may occur when sending the distribution result. In such cases, it is difficult to remotely check the firmware update status.

[0007] An object of the present invention is to enable the results of firmware update to be confirmed remotely. [Means for solving the problem]

[0008] A system according to one embodiment of the present invention is a system having an image processing device and a distribution management server that manages the distribution of firmware operating on the image processing device, and has a distribution means that distributes firmware to be distributed as instructed in distribution instruction information from the image processing device to the image processing device, and the distribution management server has an acquisition means that acquires information about firmware installed in the image processing device, and an update means that updates the distribution status, which is the distribution result of the firmware to be distributed as instructed in the distribution instruction information, based on whether the information about the installed firmware corresponds to the information about the firmware to be distributed as instructed in the distribution instruction information, without receiving the update result of the firmware to be distributed as instructed in the distribution instruction information from the image processing device. [Effects of the Invention]

[0009] According to the present invention, it is possible to check the results of firmware update remotely. [Brief explanation of the drawings]

[0010] [Figure 1] 1 is a block diagram showing a system configuration according to a first embodiment of the present invention. [Figure 2]1 is a diagram showing the hardware configuration of a distribution management server 101, a content server 102, and a client PC 104. FIG. [Figure 3] FIG. 2 is a hardware configuration diagram of an image forming apparatus 103. [Figure 4] FIG. 2 is a block diagram of a distribution management server 101. [Figure 5] FIG. 1 is a block diagram of a content server 102. [Figure 6] FIG. 1 is a block diagram of an image forming apparatus 103. [Figure 7] FIG. 10 is a sequence diagram of firmware registration. [Figure 8] FIG. 10 is a sequence diagram when a delivery instruction is registered from a client PC 104. [Figure 9] FIG. 10 is a sequence diagram when a distribution instruction is registered from the image forming apparatus 103. [Figure 10] FIG. 2 is a distribution sequence diagram from downloading to installation of firmware according to the first embodiment of the present invention. [Figure 11] 10 is a flowchart of processing by a result determination unit 409 according to the first embodiment of the present invention. [Figure 12] FIG. 10 is a distribution sequence diagram from downloading to installation of firmware according to the second embodiment of the present invention. [Figure 13] 10 is a flowchart of processing by a result determination unit 409 according to the second embodiment of the present invention. [Figure 14] 11 is a flowchart of processing by a result determination unit 409 according to the third embodiment of the present invention. [Figure 15] FIG. 11 is a sequence diagram of a status confirmation unit 405 according to the third embodiment of the present invention. [Figure 16] FIG. 11 is a sequence diagram of a report generating unit 406 according to the third embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, embodiments of the present invention will be described with reference to the drawings. However, the present invention is not limited to the following embodiments. Furthermore, the following embodiments do not limit the scope of the present invention as defined by the claims, and not all of the combinations of features described in the present embodiments are necessarily essential to the solution of the present invention. In each drawing, the same members or elements are designated by the same reference numerals, and duplicate descriptions are omitted or simplified.

[0012] <Embodiment 1> 1 is a block diagram showing a system configuration according to a first embodiment of the present invention. The system 10 according to the first embodiment is configured by interconnecting a delivery management server 101, a content server 102, an image forming device 103, and a client PC 104 via a network 100. The image forming device 103 is an example of an image processing device. The system 10 may include multiple delivery management servers 101, content servers 102, image forming devices 103, and client PCs 104.

[0013] The delivery management server 101 can manage delivery information set by a serviceman or a customer. The delivery management server 101 also allows the delivery information to be checked from the UI, making it possible to check the delivery results for the image forming apparatus 103. UI is an abbreviation for User Interface. Furthermore, the delivery management server 101 allows the user to manually register and manage firmware. The delivery management server 101 manages the delivery of firmware that runs on the image forming apparatus 103.

[0014] The content server 102 holds firmware corresponding to firmware managed by the distribution management server 101. The content server 102 responds with firmware in response to a request from the image forming device 103, allowing the image forming device 103 to download the firmware. In this embodiment, the distribution management server 101 and the content server 102 are separate, but a single server may have both functions.

[0015] The image forming apparatus 103 is, for example, an MFP. MFP is an abbreviation for Multifunction Peripheral. The image forming apparatus 103 can download and install firmware by communicating with the distribution management server 101 and the content server 102.

[0016] The client PC 104 is a PC operated by a user. PC is an abbreviation for personal computer. The user can operate the client PC 104 to register firmware and distribute firmware to the image forming apparatus 103.

[0017] 2 shows a hardware configuration diagram of the distribution management server 101, content server 102, and client PC 104. 201 is a temporary memory area RAM. RAM is an abbreviation for Random Access Memory. 202 is storage where installed programs and data are recorded.

[0018] 203 is a network interface that connects to the network 100 and communicates with other computers and network devices. The communication method may be either wired or wireless. It may also have a mobile network interface.

[0019] Reference numeral 205 denotes an input / output interface, which may input and output information and signals using a display, keyboard, mouse, touch panel, buttons, etc. Computers that do not have this hardware can also be connected and operated from other computers using remote desktop, remote shell, etc.

[0020] Reference numeral 206 denotes a secondary storage device such as a HDD or flash memory. Reference numeral 200 denotes a CPU, which executes programs read from a RAM 201, a storage 202, a secondary storage device 206, etc. CPU is an abbreviation for Central Processing Unit. Each component is connected via a system bus 204. In this embodiment, unless otherwise specified, the system bus 204 propagates control commands from the CPU 200 to each piece of hardware connected to the system bus 204.

[0021] FIG. 3 shows a hardware configuration diagram of the image forming apparatus 103. Reference numeral 301 denotes a RAM for temporary memory area. Reference numeral 302 denotes storage in which installed programs and data are recorded. Reference numeral 303 denotes a network interface, which connects to a network and communicates with other computers and network devices. The communication method may be either wired or wireless. The image forming apparatus 103 may also have a mobile network interface.

[0022] Reference numeral 305 denotes an input / output interface, which inputs and outputs information and signals using a touch panel, buttons, etc. Devices that do not have this hardware can also be connected and operated from another computer using a remote interface, etc.

[0023] Reference numeral 306 denotes a secondary storage device such as a hard disk drive (HDD) or flash memory. Reference numeral 300 denotes a CPU, which executes programs read from a RAM 301, a storage 302, or the secondary storage device 306.

[0024] A printer 308 executes jobs such as printing. A device controller 307 receives control commands from the CPU 300 and controls the printer 308. Each unit is connected via a system bus 304. In this embodiment, unless otherwise specified, the system bus 304 propagates control commands from the CPU 300 to each piece of hardware connected to the system bus 304.

[0025] Fig. 4 is a block diagram showing an example of the software configuration of the delivery management server 101. Each configuration shown in Fig. 4 is realized by reading the programs of the delivery management server 101 from the RAM 201, storage 202, secondary storage device 206, etc., and executing them by the CPU 200. Access from the delivery management server 101 to external devices such as the content server 102 is performed via the network interface 203.

[0026] The distribution management server 101 can accept registration of firmware files from the client PC 104 operated by a user such as a firmware registration clerk via a UI provided by the operation screen providing unit 402 through the firmware management unit 404. The accepted firmware file is transmitted to the content server 102 by the external communication unit 401. The firmware management unit 404 also creates and stores firmware management information corresponding to the firmware file.

[0027] The delivery management server 101 can accept delivery instructions from a client PC 104 operated by a user such as a delivery instruction manager via a UI provided by an operation screen providing unit 402. A request processing unit 403 accepts the delivery instructions, creates delivery instruction information, and stores it in an instruction management unit 408. The delivery management server 101 can also process communications from the image forming apparatus 103 using the request processing unit 403 to proceed with delivery.

[0028] The distribution management server 101 can determine the result of distribution using a result determination unit 409, and can check the latest distribution instruction information for each image forming device 103 using a status confirmation unit 405. In addition, a report generation unit 406 can generate a report using the distribution instruction information stored in an instruction management unit 408 and the distribution history information stored in a history management unit 407.

[0029] The history management unit 407 holds distribution history information created by the request processing unit 403. The instruction management unit 408 holds distribution instruction information created by the request processing unit 403. The instruction management unit 408 also holds version information of each component of firmware already installed in the image forming apparatus 103, which is sent by a notification unit 608 of the image forming apparatus 103.

[0030] Fig. 5 is a block diagram showing an example of the software configuration of the content server 102. Each configuration shown in Fig. 5 is realized by reading programs of the content server 102 from the RAM 201, storage 202, secondary storage device 206, etc., and executing them by the CPU 200. Access from the content server 102 to external devices such as the distribution management server 101 and image forming device 103 is performed via the network interface 203.

[0031] The content server 102 receives the firmware file transmitted by the distribution management server 101 via the external communication unit 501. The firmware file management unit 502 holds the firmware file received by the external communication unit 501 and issues a URL for accessing the file. URL is an abbreviation for Uniform Resource Locator. This allows the image forming device 103 to access the URL issued by the firmware file management unit 502 and download the firmware file. The URL for accessing the firmware file held by the firmware file management unit 502 is also called a link to the firmware file.

[0032] Fig. 6 is a block diagram showing an example of the software configuration of the image forming apparatus 103. Each configuration shown in Fig. 6 is realized by reading a program of the image forming apparatus 103 from the RAM 301, storage 302, secondary storage device 306, etc., and executing it by the CPU 300. Access from the image forming apparatus 103 to external devices such as the distribution management server 101 is performed via the network interface 303.

[0033] A client request processing unit 602 performs processing related to distribution with the distribution management server 101 via an external communication unit 601. The client request processing unit 602 acquires distribution instruction information held on the image forming apparatus 103 side from a client instruction management unit 604 as needed and uses it.

[0034] The firmware download unit 603 downloads firmware by communicating with the distribution management server 101 and the content server 102 via the external communication unit 601. The downloaded firmware is stored in a downloaded firmware management unit 605.

[0035] A firmware installation unit 606 installs the firmware held in the downloaded firmware management unit 605. An installed firmware information management unit 607 holds the version of each component of the firmware for which installation has been completed.

[0036] The notification unit 608 notifies the distribution management server 101 of current version notification information including version information of each component of firmware installed in the image forming apparatus 103 held in the installed firmware information management unit 607 .

[0037] FIG. 7 is a diagram showing the flow up to firmware registration. In FIG. 7, firmware is abbreviated as "FW." This also applies to the following figures. The flow of FIG. 7 is implemented by the client PC 104 operated by the user, starting with a firmware registration operation by the operation screen providing unit 402 provided by the distribution management server 101.

[0038] In step S701, the delivery management server 101 accepts firmware registration by a user operating the client PC 104. The firmware file registered here may be a single file, or files for each individual component may be compressed in a zip file format or the like and registered. Here, the delivery management server 101 determines whether the format of the registered firmware is a predetermined format, and may treat the registration as a failure if the format is not intended. The delivery management server 101 may also check whether the registered firmware contains a virus, and may treat the registration as a failure if a virus is detected.

[0039] In the next step S702, the distribution management server 101 transmits the received firmware file to the content server 102 via the external communication unit 401 of the distribution management server 101. At this time, the content server 102 stores the transmitted firmware file in the firmware file management unit 502 and issues a URL that allows the firmware file to be accessed from outside.

[0040] In the next step S703, the distribution management server 101 creates firmware management information corresponding to the firmware file in the firmware management unit 404 and stores it in the firmware management unit 404 of the distribution management server 101.

[0041] The firmware management information includes the following information: Firmware ID Firmware version Firmware component information The following describes each piece of information contained in this firmware management information.

[0042] The firmware ID is an ID that uniquely identifies the registered firmware. The firmware ID may be used to identify the target firmware in the distribution instruction information described below. The firmware version is the version of the firmware.

[0043] Firmware component information is information that indicates the type and version of each component of the firmware. Firmware may consist of multiple components, and the firmware version is considered to be determined by the combination of the individual versions of those components. Of course, if firmware is composed of a single component, it is sufficient to only indicate the version of that single component. Firmware component information may be handled in a dictionary format, for example, as shown below. { “firmwareComponentMap”: { “componentA”: “1.0”, “componentB”: “1.0”, “componentC”: “1.0” } } In this case, it indicates that the firmware is configured by component A of version 1.0, component B of version 1.0, and component C of version 1.0. After the processing of step S703 is performed, the registered firmware can be distributed to the image forming apparatus 103.

[0044] Fig. 8 shows a flow from when a user remotely issues a distribution instruction to when the image forming apparatus 103 is notified of the distribution instruction. The flow in Fig. 8 is assumed to be executed after the firmware to be distributed is registered in the distribution management server 101 by the flow in Fig. 7. The flow in Fig. 8 is executed starting from the registration operation of the client PC 104 operated by the user to register distribution instruction information provided by the distribution management server 101 via the operation screen providing unit 402.

[0045] In step S801, the delivery management server 101 accepts a delivery instruction, i.e., a registration operation of delivery instruction information, from the user-operated client PC 104. In step S802, the delivery management server 101 creates delivery instruction information using the request processing unit 403 and stores it in the instruction management unit 408.

[0046] The distribution instruction information includes the following information: Distribution ID Delivery Status -Firmware ID to be distributed - Delivery target device ID How to create delivery instructions How to install - Forced installation Download time Installation time Creation time of delivery instruction information -Last update time of distribution instruction information Error Codes -Firmware information currently installed on the image forming device Each piece of information contained in this distribution instruction information will be explained below.

[0047] The delivery ID is an ID that uniquely identifies delivery instruction information. The delivery ID is used to identify the corresponding delivery instruction information when communication occurs between the image forming device 103 and the delivery management server 101. The delivery status is information that indicates the current stage of the delivery. The delivery status changes state when communication occurs between the image forming device 103 and the delivery management server 101.

[0048] The distribution target firmware ID is an ID that identifies firmware to be installed in the image forming apparatus 103. The distribution target firmware ID corresponds to the firmware ID in the firmware management information, and can be specified by the user.

[0049] The distribution target device ID is an ID that identifies a device on which the firmware identified by the distribution target firmware ID is to be installed.

[0050] The distribution instruction information creation method describes how to create the distribution instruction information. The installation method describes how to install the firmware identified by the distribution target firmware ID. The forced installation availability describes whether the firmware identified by the distribution target firmware ID can be forcedly installed. The download execution time describes the time when the firmware identified by the distribution target firmware ID was downloaded. The installation execution time describes the time when the firmware identified by the distribution target firmware ID was installed. The distribution instruction information creation time describes the time when this distribution instruction information was created. The distribution instruction information last update time describes the time when this distribution instruction information was last updated. The error code describes the error code of the distribution instruction by this distribution instruction information. The firmware information currently installed in the image forming device is information about the firmware currently installed in the device identified by the distribution target device ID.

[0051] Following step S802, in step S803, the image forming apparatus 103 makes a request to acquire distribution instruction information to the distribution management server 101. The request to acquire distribution instruction information by the image forming apparatus 103 may be configured, for example, so that the image forming apparatus 103 periodically makes a request to acquire distribution instruction information to the distribution management server 101, thereby enabling the image forming apparatus 103 to acquire registered distribution instruction information.

[0052] When the delivery management server 101 receives a request to acquire delivery instruction information from the image forming apparatus 103, the request processing unit 403 identifies delivery instruction information whose delivery target device ID matches that of the image forming apparatus 103. The delivery management server 101 acquires the identified delivery instruction information from the instruction management unit 408 and transmits it to the image forming apparatus 103. Here, the delivery instruction information transmitted by the delivery management server 101 may use the delivery instruction information held on the delivery management server 101 side as is, or may delete information unnecessary for delivery, such as the creation time of the delivery instruction information.

[0053] In step S804, the image forming apparatus 103 that has received the distribution instruction information creates client distribution instruction information using the request processing unit 403 and stores it in the client instruction management unit 408. The client distribution instruction information is distribution instruction information stored in the image forming apparatus 103, and the image forming apparatus 103 stores the client distribution instruction information in order to perform subsequent distribution processing. The image forming apparatus 103 may use the distribution instruction information stored in the instruction management unit 408 of the distribution management server 101 as the client distribution instruction information, or may delete unnecessary information such as the creation time of the distribution instruction information.

[0054] 9 shows a sequence when a distribution instruction is issued from the image forming apparatus 103. It is assumed that the processing in FIG. 9 is performed after the firmware to be distributed is registered in the distribution management server 101 according to the flow in FIG.

[0055] In step S901, the image forming apparatus 103 requests the distribution management server 101 to register distribution instruction information. In the following step S902, the distribution management server 101 creates distribution instruction information using the request processing unit 403 and returns the result of the request to register the distribution instruction information to the image forming apparatus 103.

[0056] The processing of step S901 may be triggered when a user such as a serviceman sets a distribution instruction via the input / output I / F 306 of the image forming apparatus 103. Alternatively, if client distribution instruction information indicating that periodic updates will be performed is set in the client instruction management unit 604 of the image forming apparatus 103, the processing may be triggered when the update time set in the client distribution instruction information arrives.

[0057] In step S903, if the result of the registration request for the distribution instruction information returned in step S902 is a value indicating successful registration, the image forming apparatus 103 creates client distribution instruction information using the request processing unit 403. The image forming apparatus 103 stores the created client distribution instruction information in the client instruction management unit 604.

[0058] 10 is a diagram showing a distribution flow from downloading to installation of firmware for the image forming apparatus 103. The flow in FIG. 10 is executed when the download start time included in the client distribution instruction information held in the client instruction management unit 604 arrives.

[0059] In step S1001, the image forming apparatus 103 makes a request to acquire firmware information to be downloaded to the distribution management server 101 via the client request processing unit 602. At this time, the image forming apparatus 103 sends the distribution instruction information stored in the client instruction management unit 604 to the distribution management server 101, including an ID that uniquely identifies the distribution instruction information.

[0060] The delivery management server 101 acquires the corresponding delivery instruction information from the instruction management unit 408 via the request processing unit 403. The delivery management server 101 identifies firmware to be downloaded to the image forming apparatus 103 from the firmware management unit 404 based on the firmware ID to be delivered in the corresponding delivery instruction information. The delivery management server 101 acquires a link to the identified firmware file to be downloaded.

[0061] The delivery management server 101 may download only firmware that is different from the firmware to be delivered, based on list information about the components and versions of firmware already installed in the image forming device 103. This makes it possible to reduce the number of firmware files to be downloaded. In the process of FIG. 11 , which will be described later, the delivery management server 101 registers a list of the components and versions of firmware already installed in the image forming device 103 in the delivery instruction information. The delivery management server 101 then returns a link to the firmware file to be downloaded to the image forming device 103.

[0062] In step S1002, the image forming apparatus 103 downloads the firmware by accessing the link to the returned firmware file. After downloading the firmware, the image forming apparatus 103 may notify the distribution management server 101 of the completion of the download by sending a download completion notification to the distribution management server 101. Upon receiving the download completion notification, the distribution management server 101 may update the distribution status of the distribution instruction information to a value such as "downloaded" indicating that the download has completed, via the request processing unit 403. This firmware download is an example of a distribution means for distributing the firmware to be distributed, as specified in the distribution instruction information, to the image forming apparatus 103.

[0063] After downloading the firmware, the image forming apparatus 103 performs firmware installation processing when the installation time arrives according to the client distribution instruction information stored in the client instruction management unit 604. In step S1003, the client request processing unit 602 communicates with the distribution management server 101 via the external communication unit 601 to notify the start of firmware installation.

[0064] In step S1004, the delivery management server 101, via the request processing unit 403, updates the delivery status of the corresponding delivery instruction information to an item such as "applying", which indicates that installation is in progress.

[0065] Thereafter, in step S1005 , the image forming apparatus 103 causes the firmware installation unit 606 to install the firmware file acquired by the firmware download unit 603 .

[0066] FIG. 11 illustrates the processing flow of the result determination unit 409. The flow in FIG. 11 is performed asynchronously with the firmware distribution in FIG. 10. The image forming apparatus 103 transmits current version notification information to the distribution management server 101 via the notification unit 608. Upon receiving the current version notification information, the distribution management server 101 executes the result determination unit 409 via the request processing unit 403, and the flow in FIG. 11 begins. The notification unit 608 repeatedly transmits the current version notification information at predetermined intervals to remotely manage the status of the image forming apparatus 103. The notification unit 608 may also transmit information about errors occurring in the image forming apparatus 103, the remaining amount of consumables, and the like. The notification unit 608 may transmit the current version notification information when the image forming apparatus 103 is powered on, or periodically, such as every six hours. The reception of the current version notification information by the distribution management server 101 is an example of a means for acquiring information about firmware installed in the image forming apparatus 103.

[0067] The current version notification information includes the following information: Device ID -Information about currently installed firmware components The following describes each piece of information contained in this current version notification information.

[0068] The device ID is an ID that identifies the device that notifies the firmware version in the current version notification information. The component information of the currently installed firmware is a description of the component information of the firmware currently installed in the device identified by the device ID.

[0069] An example of the current version notification information notified by the notification unit 608 is described below. { “deviceId”: “1”, “installedFirmwareComponentMap”: { “componentA”: “2.0”, “componentB”: “1.0”, “componentC”: “1.0”, “componentD”: “1.0” } }

[0070] In step S1101, the result determination unit 409 acquires, from the distribution instruction information held in the instruction management unit 408, distribution instruction information whose distribution target device value corresponds to the device ID included in the received current version notification information. In step S1102, the result determination unit 409 determines whether or not there is distribution instruction information whose distribution status is "applied" from the acquired distribution instruction information. If the result determination unit 409 determines that there is distribution instruction information whose distribution status is "applied", the process of step S1103 is executed. If the result determination unit 409 determines that there is no distribution instruction information whose distribution status is "applied", the process of step S1106 is executed.

[0071] In step S1103, if there is distribution instruction information with a distribution status of "applying," the result determination unit 409 acquires firmware management information corresponding to the distribution target firmware ID of the corresponding distribution instruction information. Further in step S1103, the result determination unit 409 compares the firmware component information in the firmware management information with the component information of the currently installed firmware in the received current version notification information, and determines whether they correspond. If the result determination unit 409 determines that the firmware component information corresponds, the process of step S1104 is executed. If the result determination unit 409 determines that the firmware component information does not correspond, the process of step S1105 is executed.

[0072] In step S1103, correspondence between pieces of firmware component information may mean that the types and versions of the components included in each piece of component information completely match.

[0073] Note that in step S1103, the correspondence between pieces of firmware component information may also be the case in the following cases. For example, some firmware components included in the firmware component information downloaded from the distribution management server 101 may be unnecessary and not installed depending on the type or state of the image forming apparatus 103. Such cases may also be considered to be correspondence between pieces of firmware component information. That is, this is the case when the firmware component information in the firmware management information corresponding to the firmware to be distributed includes the component information of the currently installed firmware in the received current version notification information. This case will be further explained below. For example, assume that the component information of the currently installed firmware in the current version notification information is as follows: { “installedFirmwareComponentMap”: { “componentA”: “2.0”, “componentB”: “1.0” } } Also, it is assumed that the firmware component information in the firmware management information corresponding to the distribution target firmware ID to be compared is as follows: { “firmwareComponentMap”: { “componentA”: “2.0”, “componentB”: “1.0”, “componentC”: “1.0” } } In this case, the firmware component information may correspond to each other.

[0074] In step S1103, the correspondence between the pieces of firmware component information may also be the case in the following cases. For example, consider a case where component information other than the component information included in the firmware to be distributed this time has already been installed in the image forming apparatus 103 and is stored in the installed firmware information management unit 607. The component information of the currently installed firmware in the received current version notification information may include component information of firmware in firmware management information corresponding to the firmware to be distributed this time. In this case, the correspondence between the pieces of firmware component information may also be considered. For example, assume that the component information of the currently installed firmware in the current version notification information is as follows: { “installedFirmwareComponentMap”: { “componentA”: “2.0”, “componentB”: “1.0”, “componentC”: “1.0” } } Also, it is assumed that the firmware component information in the firmware management information corresponding to the distribution target firmware ID to be compared is as follows: { “firmwareComponentMap”: { “componentA”: “2.0”, “componentB”: “1.0” } } In this case, the firmware component information may correspond to each other.

[0075] In step S1103, the correspondence between the firmware component information may be a combination of the above conditions.

[0076] In step S1104, the result determination unit 409 updates the distribution status of the corresponding distribution instruction information to "Complete," indicating that distribution is complete. In step S1105, the result determination unit 409 updates the distribution status of the corresponding distribution instruction information to "Failed," indicating that distribution failed. In step S1105, the result determination unit 409 may also update the value of the error code included in the distribution instruction information to a value indicating that the result determination unit 409 has determined that the distribution status is "Failed." Then, in step S1106, the distribution management server 101 stores the component information of the currently installed firmware transmitted by the notification unit 608 in the instruction management unit 408. Steps S1103, S1104, and S1105 are an example of an update unit that updates the distribution status, which is the distribution result of the firmware to be distributed. Here, the update unit updates the distribution status based on whether the information on the firmware already installed in the image forming apparatus 103 corresponds to the information on the firmware to be distributed specified in the distribution instruction information. Here, the update unit updates the distribution status without receiving from the image forming apparatus 103 the results of updating the firmware to be distributed as instructed by the distribution instruction information.

[0077] As described above, according to this embodiment, the distribution result can be determined even when the image forming apparatus to which the firmware is applied does not transmit the distribution result or when the image forming apparatus does not notify the result due to some kind of trouble.

[0078] <Embodiment 2> Next, a second embodiment of the present invention will be described. In the second embodiment, only the differences from the first embodiment will be described. In the first embodiment, the image forming apparatus 103 did not have a function for notifying the result of firmware installation when firmware is installed. In the second embodiment, the image forming apparatus 103 has a function for notifying the result of firmware installation when firmware is installed.

[0079] 12 is a sequence diagram showing the process when the client request processing unit 602 of the image forming apparatus 103 notifies the distribution management server 101 of the installation result at the end of firmware installation. The processes from step S1201 to step S1205 are the same as the processes from step S1001 to step S1005 according to the first embodiment, and therefore a description thereof will be omitted.

[0080] After the firmware is installed (step S1205), in step S1206, the image forming apparatus 103 notifies the distribution management server 101 of the completion of the installation via the client request processing unit 602. The processing of step S1206 is an example of a notification unit that notifies the distribution management server 101 of the installation result of the firmware distributed by the distribution unit.

[0081] The installation completion notification information sent when notifying the completion of installation includes the following information: Distribution ID Installation result information Error Codes The following describes each piece of information contained in this installation completion notification information.

[0082] The distribution ID is an ID that uniquely identifies the distribution instruction information. The installation result information is a description of the installation result of the firmware instructed by the distribution instruction information identified by the distribution ID. The error code is a description of the error code of the distribution instruction by the distribution instruction information identified by the distribution ID.

[0083] In step S1207, the delivery management server 101, via the request processing unit 403, updates the delivery status of the delivery instruction information corresponding to the delivery ID in the received installation completion notification information, according to the value of the installation result information. For example, if the installation result information is a value indicating normal completion, the request processing unit 403 updates the delivery status of the delivery instruction information to "completed." For example, if the installation result information is a value indicating abnormal completion, the request processing unit 403 updates the delivery status of the delivery instruction information to "failed," and updates the error code of the delivery instruction information with the received error code. The processing of step S1207 is an example of an update unit that updates the delivery status based on the installation result notified by the notifying unit.

[0084] Fig. 13 is a diagram showing the processing flow in the result determination unit 409 of the distribution management server 101 according to the second embodiment. The flow in Fig. 13, like the flow in Fig. 11 according to the first embodiment, is performed asynchronously with the firmware distribution in Fig. 12. The processing in steps S1301 to S1303 and S1306 is the same as the processing in steps S1101 to S1103 and S1106 according to the first embodiment, and therefore a description thereof will be omitted.

[0085] In step S1304, the result determination unit 409 updates the distribution status of the corresponding distribution instruction information to a value such as "Completed (Deemed)." This makes it possible to distinguish the distribution status from when the installation result is determined on the device side (step S1206). Of course, if there is no need to distinguish this, the flow in FIG. 11 can be applied as is. In the example in FIG. 13, the distribution status of the distribution instruction information is updated to a different value. In this case, the result determination unit 409 updates the distribution status in a way that makes it possible to distinguish this from an update of the distribution status based on whether or not the information on the installed firmware corresponds to the information on the firmware to be distributed as specified in the distribution instruction information.

[0086] For example, by including a server-side determination flag in the delivery instruction information, it is possible to distinguish between the same delivery status of "completed" depending on whether or not the flag is included. In this case, the delivery instruction information has a flag indicating whether or not the update of the delivery status is based on the installation result notified by the notifying means.

[0087] In step S1305, the result determination unit 409 updates the delivery status of the corresponding delivery instruction information to "failed (deemed)", which indicates that delivery has failed. Here, the value of the error code included in the delivery instruction information may be updated to a value indicating that the result determination unit 409 has determined that the delivery status is "failed (deemed)".

[0088] 13 is executed before step S1207, the delivery status may be updated to "completed" by prioritizing the result of the installation completion notification information from the image forming apparatus 103. Setting the delivery status to "completed" or "failed" is an example of a provisional update of the delivery status. Updating the delivery status in accordance with the result of the installation completion notification information from the image forming apparatus 103 when the delivery status is "completed" is an example of a final update. In this case, the delivery status is overwritten with the final update.

[0089] As described above, according to this embodiment, the image forming apparatus 103 can distinguish between devices that notify the installation result and devices that do not notify the installation result even when they are mixed.

[0090] <Embodiment 3> Next, a third embodiment of the present invention will be described. In the third embodiment, only the parts that are different from the first embodiment will be described. The third embodiment is an example in which the image forming apparatus 103 has a function of registering a distribution history, and has a function that allows a user to check the distribution status and past distribution history using a status checking unit 405 and a report generating unit 406 of the distribution management server 101. In the third embodiment, the distribution management server 101 creates distribution history information when processing is executed by the request processing unit 403, and stores the information in a history management unit 407.

[0091] The distribution history information includes the following information: Distribution history ID History registration date Event name Device ID of the image forming device 103 Corresponding distribution ID Region Identification information of the parent company to which the image forming device 103 belongs Processing results - The firmware ID registered on the device at the time of history registration -Firmware ID to be distributed Each piece of information contained in this distribution history information will be explained below.

[0092] The delivery history ID is an ID that uniquely identifies the delivery history information. The history registration date is a description of the registration date of the delivery history identified by the delivery history ID. The event name is a description of the event name of the delivery history identified by the delivery history ID. The device ID of the image forming device 103 is the device ID of the image forming device 103 that is the target device of the delivery history identified by the delivery history ID. The corresponding delivery ID is the delivery ID of the target delivery of the delivery history identified by the delivery history ID. The region is a description of the region of the delivery history identified by the delivery history ID. The identification information of the parent company to which the image forming device 103 belongs is the identification information of the parent company to which the image forming device 103 that is the target device of the delivery history identified by the delivery history ID belongs. The processing result is the processing result of the target delivery of the delivery history identified by the delivery history ID. The firmware ID registered in the device at the time of history registration is the firmware ID of the firmware that was registered in the device at the time of history registration for the target device of the delivery history identified by the delivery history ID. The firmware ID of the firmware to be distributed is the firmware ID of the firmware to be distributed in the distribution of the distribution history specified by the distribution history ID.

[0093] Here, the event name will be further explained. The event name is information for identifying the timing at which distribution history information is written. The timing at which this distribution history information is written may include, for example, the following timings. The timing at which distribution instruction information is created in response to an instruction from the client PC 104 via the operation screen providing unit 402 The timing at which the distribution instruction information is created in response to a request from the image forming apparatus 103 The timing when the image forming apparatus 103 attempts to acquire firmware information to be downloaded When the image forming apparatus 103 finishes downloading The timing when the image forming device 103 starts installing firmware Timing when the image forming apparatus 103 notifies the completion of firmware installation The timing at which the result determination unit 409 of the distribution management server 101 makes a determination

[0094] Fig. 14 is a diagram showing the processing flow in the result determination unit 409 of the distribution management server 101 according to the third embodiment. The flow in Fig. 14, like the flow in Fig. 11 according to the first embodiment, is performed asynchronously with the firmware distribution in Fig. 10. The processing in steps S1401 to S1406 is the same as the processing in steps S1101 to S1106 in the first embodiment, and therefore a description thereof will be omitted.

[0095] After the status is updated by the processes in steps S1404 and S1405, the result determination unit 409 creates distribution history information and stores it in the history management unit 407 in step S1407. The history management unit 407 holds, for example, the following distribution history information: { “historyId”: “1234”, “registeredDate”: “2024 / 04 / 19 09:00:00”, “eventName”: “updateEndByServer”, “deviceId”: “AAA00001”, “deliveryId”: “1”, “region”: “JP”, “TenantId”: “A”, “resultCode”: “00000001”, “installedFirmwareId”: “0”, “targetfirmwareId”: “1” }

[0096] The event name of the distribution history information created in the processing of step S1407 may be differentiated assuming a case where a firmware installation completion notification is sent from the image forming apparatus 103 and distribution history information is created in response to the notification, as in embodiment 2. For example, the event name of the distribution history information created in the processing of step S1404 is set to "eventName": "updateEndByServer" in the above example. On the other hand, the event name of the distribution history information created when a firmware installation completion notification is sent is set to "eventName": "updateEndByDevice", for example.

[0097] The event name of the distribution history information may also be as follows: When a firmware installation completion notification is not sent from the image forming apparatus 103 as in the first embodiment, the event name of the distribution history information may be set to "eventName": "updateEnd". When a firmware installation completion notification is sent from the image forming apparatus 103 as in the second embodiment, but there is no need to distinguish the event name of the distribution history information created at that time, the event name may be set to "eventName": "updateEnd".

[0098] Furthermore, by notifying an external server that monitors the distribution management server 101 of the distribution history information, a report can be created using the report creation function of the external server.

[0099] Fig. 15 is a diagram showing a sequence when a user checks the latest distribution instruction information using the status checking unit 405 according to embodiment 3. The sequence in Fig. 15 is started when the user sends a distribution status acquisition request to the distribution management server 101 via the client PC 104 from the UI provided by the operation screen providing unit 402 of the distribution management server 101.

[0100] In step S1501, the distribution management server 101 receives a distribution status acquisition request from the client PC 104. Upon receiving the distribution status acquisition request, the status confirmation unit 405 of the distribution management server 101 performs subsequent processing based on the distribution status acquisition detailed information included in the received distribution status acquisition request.

[0101] The detailed distribution status acquisition information may include the following information: ·Output format Device ID of the image forming device 103 to be output The information contained in this detailed distribution status acquisition information will be described below.

[0102] The output format may include information indicating that the information is to be displayed on a UI, or may include information indicating that the information is to be output in a report format such as a CSV file. CSV is an abbreviation for Comma Separated Values. Also, while Figure 15 describes an example in which the display on the UI and the report format are switched depending on the value of the output format of the distribution status acquisition detailed information, the output format may be switched without specifying the output format by preparing separate UIs for each.

[0103] In step S1502, the status confirmation unit 405 acquires the latest distribution instruction information corresponding to the device ID of the image forming apparatus 103 to be output, which is included in the received distribution status acquisition detailed information, from the instruction management unit 408. Here, the search for the latest distribution instruction information may target the distribution instruction information with the most recent creation time included in the distribution instruction information, or, if the distribution IDs are sequential numbers that gradually increase, may target the distribution instruction information with the largest distribution ID value.

[0104] Then, in step S1503, the status confirmation unit 405 creates distribution status information based on the distribution instruction information acquired in step S1502 and the distribution status acquisition detail information received in step S1501. If information indicating that the output format of the distribution status acquisition detail information is to be displayed on the UI is received, the distribution status information can be created in a file format that can be confirmed on the UI. Also, if information indicating that the output format of the distribution status acquisition detail information is to be output in report format is received, the distribution status information can be created as a CSV file or the like, and a link or the like that allows the created file to be downloaded can be generated.

[0105] The distribution status information is created by acquiring, for example, the following information from the distribution instruction information: Delivery Status -Firmware ID to be distributed - Delivery target device ID Creator of delivery instruction information How to install Download time Installation time Error Codes

[0106] Here, as in embodiment 2, if the distribution status of the distribution instruction information contains a mixture of statuses indicating the completion of distribution, such as "Completed" and "Deemed Completed," the value may be updated to unify these and display "Completed."

[0107] Then, in step S1504, the status confirmation unit 405 returns a distribution status acquisition response to the client PC 104. If information indicating that the distribution status acquisition detailed information should be displayed on the UI as the output format is specified, a file format that can be confirmed on the UI is returned as the distribution status acquisition response, and the distribution status can be confirmed on the UI from the client PC 104. Also, if information indicating that the distribution status acquisition detailed information should be output in a report format such as a CSV file is specified as the output format, a link for downloading the CSV file is returned as the distribution status acquisition response. The user can download the CSV file by accessing the link and check the distribution status on the client PC 104.

[0108] Fig. 16 shows a sequence when a delivery history report is generated by the report generation unit 406 according to embodiment 3. The sequence in Fig. 16 starts when the user transmits a delivery history report creation request to the delivery management server 101 via the client PC 104 from the UI provided by the operation screen providing unit 402 of the delivery management server 101.

[0109] In step S1601, the delivery management server 101 receives a delivery history report creation request from the client PC 104. Upon receiving the delivery history report creation request, the report generation unit 406 of the delivery management server 101 performs subsequent processing based on the delivery history report creation request information included in the received delivery history report creation request.

[0110] The delivery history report creation request information may include the following information. Report Type Device ID of the image forming device 103 to be output - Firmware ID of the distribution history information to be output - Creation period of the distribution history information to be output

[0111] In addition, the report type may be specified so that the following reports can be output, for example. -Report that outputs delivery history information A report that lists the number of image forming devices 103 for which firmware distribution updates have been completed A report that lists the number of image forming devices 103 for which firmware distribution updates have been completed, by installation method and distribution instruction information creation method. A report that lists the device IDs of the image forming devices 103 whose firmware has been updated

[0112] In step S1602, the report generation unit 406 searches for the target delivery history information based on the received delivery history report creation request. Then, in step S1603, the report generation unit 406 generates a delivery history report using the searched delivery history information. Finally, in step S1604, the report generation unit 406 returns the created delivery history report to the client PC 104. Here, the delivery management server 101 may return the created delivery history report directly to the client PC 104, or may issue a download URL and return the URL so that the delivery history report can be downloaded.

[0113] As described above, according to this embodiment, the user can check information related to distribution from the image forming apparatus 103.

[0114] In each of the first to third embodiments, the number of servers and image forming apparatuses does not necessarily have to be the same as that of the overall configuration shown in FIG.

[0115] (Other embodiments) The present invention can also be realized by supplying a program that realizes one or more functions of the above-described embodiments to a system or device via a network or a storage medium, and having one or more processors in the computer of the system or device read and execute the program. It can also be realized by a circuit (e.g., ASIC) that realizes one or more functions.

[0116] Although the preferred embodiments of the present invention have been described above, the present invention is not limited to these embodiments and various modifications and changes are possible within the scope of the gist of the present invention.

[0117] The disclosure of this embodiment includes the following configurations and methods. (Configuration 1) A system including an image processing device and a distribution management server that manages distribution of firmware that operates on the image processing device, a distribution unit that distributes firmware to be distributed, the firmware being specified by distribution instruction information from the image processing device, to the image processing device; The delivery management server has an acquisition means for acquiring information on firmware already installed in the image processing device, and an update means for updating a delivery status, which is a delivery result of the firmware to be delivered specified in the delivery instruction information, based on whether or not the information on the installed firmware corresponds to the information on the firmware to be delivered specified in the delivery instruction information, without receiving an update result of the firmware to be delivered specified in the delivery instruction information from the image processing device. A system characterized by: (Configuration 2) the image processing device includes a notification unit that notifies the distribution management server of an installation result of the firmware distributed by the distribution unit; the update means updates the delivery status based on the installation result notified by the notification means; the delivery instruction information includes a flag indicating whether the update of the delivery status is an update based on the installation result notified by the notifying means; 2. The system of claim 1. (Configuration 3) the image processing device has a notification unit that notifies the distribution management server of an installation result of the firmware distributed by the distribution unit; the update means updates the distribution status based on the installation result notified by the notification means, in a manner that can be distinguished from updating the distribution status based on whether or not the information on the installed firmware corresponds to the information on the firmware to be distributed instructed by the distribution instruction information. 3. The system according to configuration 1 or 2, (Configuration 4) the image processing device has a notification unit that notifies the distribution management server of an installation result of the firmware distributed by the distribution unit; the update means updates the distribution status based on whether or not the information on the installed firmware corresponds to the information on the firmware to be distributed as instructed by the distribution instruction information, as a provisional update, and overwrites the distribution status with a final update based on the installation result notified by the notification means. 4. The system of any one of configurations 1 to 3. (Method 1) A control method for a system having an image processing device and a distribution management server that manages distribution of firmware that operates on the image processing device, comprising: a distribution step of distributing firmware to the image processing device, the firmware being distributed as instructed by distribution instruction information from the image processing device; The delivery management server has an acquisition step of acquiring information on firmware already installed in the image processing device, and an update step of updating a delivery status, which is a delivery result of the firmware to be delivered specified by the delivery instruction information, based on whether or not the information on the installed firmware corresponds to the information on the firmware to be delivered specified by the delivery instruction information, without receiving an update result of the firmware to be delivered specified by the delivery instruction information from the image processing device. A method characterized by: [Explanation of symbols]

[0118] 100 Network 101 Distribution Management Server 102 Content Server 103 Image forming device 104 client PCs

Claims

1. A system including an image processing device and a distribution management server that manages distribution of firmware that operates on the image processing device, a distribution unit that distributes firmware to be distributed, the firmware being specified by distribution instruction information from the image processing device, to the image processing device; The delivery management server has an acquisition means for acquiring information on firmware already installed in the image processing device, and an update means for updating a delivery status, which is a delivery result of the firmware to be delivered specified in the delivery instruction information, based on whether or not the information on the installed firmware corresponds to the information on the firmware to be delivered specified in the delivery instruction information, without receiving an update result of the firmware to be delivered specified in the delivery instruction information from the image processing device. A system characterized by:

2. the image processing device has a notification unit that notifies the distribution management server of an installation result of the firmware distributed by the distribution unit; the update means updates the delivery status based on the installation result notified by the notification means; the delivery instruction information includes a flag indicating whether the update of the delivery status is an update based on the installation result notified by the notifying means; 2. The system of claim 1.

3. the image processing device has a notification unit that notifies the distribution management server of an installation result of the firmware distributed by the distribution unit; the update means updates the distribution status based on the installation result notified by the notification means, in a manner that can be distinguished from updating the distribution status based on whether or not the information on the installed firmware corresponds to the information on the firmware to be distributed instructed by the distribution instruction information.

2. The system of claim 1.

4. the image processing device has a notification unit that notifies the distribution management server of an installation result of the firmware distributed by the distribution unit; the update means updates the distribution status based on whether or not the information on the installed firmware corresponds to the information on the firmware to be distributed as instructed by the distribution instruction information, as a provisional update, and overwrites the distribution status with a final update based on the installation result notified by the notification means.

2. The system of claim 1.

5. A control method for a system having an image processing device and a distribution management server that manages distribution of firmware that operates on the image processing device, comprising: a distribution step of distributing firmware to the image processing device, the firmware being distributed as instructed by distribution instruction information from the image processing device; The delivery management server has an acquisition step of acquiring information on firmware already installed in the image processing device, and an update step of updating a delivery status, which is a delivery result of the firmware to be delivered specified by the delivery instruction information, based on whether or not the information on the installed firmware corresponds to the information on the firmware to be delivered specified by the delivery instruction information, without receiving an update result of the firmware to be delivered specified by the delivery instruction information from the image processing device. A method characterized by:

Images