Program update system and information processing device

Abstract

To suppress a situation in which a user cannot execute a function for which the user was going to execute, because update of a control program has started.SOLUTION: A plurality of information processing devices include: at least one master unit and at least one slave unit. The master unit includes: a job data management storage unit that manages and stores obtained job data; an update data acquisition unit that obtains update data for updating a control program which controls operation of each information processing device; an update data storage unit that stores the obtained update data; and an update data distribution unit that distributes the update data which is read from the update data storage unit, to the slave unit. The slave unit includes a program update execution unit that stores the control program for controlling its own operation and updates the control program using the update data that has been received. At least any one of timing at which the master unit distributes the update data and timing at which the slave unit updates the control program is determined according to the job data.SELECTED DRAWING: Figure 7

Description

[Technical Field]

[0001] The present invention relates to a program update system, and more particularly to a program update system that distributes a control program for controlling the operation of an information processing device such as an image forming device to the information processing device and updates the control program of the information processing device with a new control program. [Background technology]

[0002] 2. Description of the Related Art Conventionally, image forming apparatuses have been used that have multiple functions such as a printing function, a document reading function, a read image data transmission function, an image data acquisition function, and a character recognition function. Also in practical use are printing systems in which an image forming device is operated to obtain a print job containing image data and the like stored in a server information processing device via a network and execute the print. Among the printing systems described above, there are also printing systems in which an image forming device plays the role of a server. That is, an image forming device (parent device) serving as a server receives and stores print jobs containing image data and the like, and in response to requests from other image forming devices (child devices) via the network, transmits the specified print jobs to the child devices, and the child devices execute printing of the print jobs. Such an image forming apparatus stores control programs for executing a large number of functions. This control program may be updated to a new program in order to add or change functions, fix defects, or the like.

[0003] In some cases, a maintenance technician visits the installation site of the image forming apparatus and updates the control program for each image forming apparatus. In addition, when maintaining a large number of image forming devices, a system is also used in which new control programs are stored on a designated server, and the new control programs are distributed from this server to each of the large number of image forming devices via a network, so that each image forming device automatically replaces its control program with the received new control program.

[0004] Furthermore, for example, Patent Document 1 describes an automatic update system in which a content server storing an update program, a file information providing server that provides file information of the update program, a mail server that receives e-mail containing the file information sent from the file information providing server, and an automatic update device that writes the downloaded update program to update the software are connected via a communication means such as the Internet, and when the automatic update device confirms that an e-mail exists in the mail server's mailbox, it receives the e-mail from the mail server, accesses the content server in accordance with the file information contained in the received e-mail, downloads the update program from the content server, and writes the downloaded update program into a ROM area to update the software. Patent document 1 also describes that after the automatic update device downloads an update program, if an update time is specified, the automatic update device will update the software using the downloaded update program when the specified update time arrives. [Prior art documents] [Patent documents]

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

[0006] However, in general, when an image forming apparatus or the like is undergoing a control program update, it is not possible to execute the image forming apparatus's original printing function or to perform input operations for that purpose. For example, when a user of an image forming device attempts to perform input operations to obtain a print job from a server and execute printing, if an update of the control program begins, the user may be unable to perform normal input operations and may have to wait a long time until the update of the control program is complete.

[0007] It is possible to avoid the above-mentioned problems by setting the start time of the control program update so that it begins during a time period when users do not use the device frequently. If the image forming device is always turned off during such time periods, a situation may arise in which the control program update is not performed as expected by the maintenance technician.

[0008] Therefore, this invention has been made in consideration of the above circumstances, and aims to ensure user convenience by preventing control program updates from being performed during periods when there is a high probability that a job will be executed by input operations, thereby reducing the possibility of a situation occurring in which, when a user attempts to use an information processing device such as an image forming device, an update to the control program of the information processing device has begun, preventing the user from performing normal input operations and forcing the user to wait until the update is complete. [Means for solving the problem]

[0009] The present invention relates to a program update system comprising a plurality of information processing devices connected via a network, the plurality of information processing devices comprising at least one parent device and at least one child device, the parent information processing device comprising: a job data acquisition unit that acquires job data including data to be processed in the child information processing device; a job data management storage unit that manages and stores the acquired job data; a job data transmission unit that transmits job data read from the job data management storage unit to the child device via the network in response to a request from the child device; an update data acquisition unit that acquires update data for updating a control program that controls operation of the information processing device; an update data storage unit that stores the acquired update data; and an update data distribution unit that distributes the update data read from the update data storage unit to the child device via the network, The information processing device is a device that includes a job data request unit that requests a parent device to send the job data via a network, a job data receiving unit that receives the job data sent from the parent device, a job execution unit that realizes the functions of the information processing device by processing the received job data, a program memory unit that stores a control program that controls its own operation, an update data receiving unit that receives the update data from the parent device via the network, and a program update execution unit that updates the control program stored in the program memory unit using the received update data, and provides a program update system characterized in that at least one of the timing at which the parent device distributes the update data and the timing at which the child device updates the control program is determined according to the job data stored in the job data management memory unit.

[0010] The parent device is also characterized by having a second job execution unit that realizes the functions of the information processing device in the same way as the child device by processing the job data read out from the job data management storage unit.

[0011] The parent machine further includes a scheduled delivery time determination unit that determines a scheduled delivery time for the update data based on the time the job data was acquired and stored in the job data management memory unit, and a memory unit that stores the scheduled delivery time, and the update data delivery unit delivers the update data at a timing based on the scheduled delivery time.

[0012] The parent device further includes a setting memory unit for storing a delay time setting, which is a setting for setting a period of time during which update data is not sent after receiving job data, and the scheduled delivery time determination unit determines the scheduled delivery time using the time when the job data stored in the job data management memory unit was last acquired and the previously stored delay time setting.

[0013] In addition, in the parent machine, if the job data acquisition unit acquires new job data after the scheduled delivery time has been stored in the memory unit, the scheduled delivery time determination unit changes the scheduled delivery time based on the time at which the new job data was acquired.

[0014] Furthermore, in the parent machine, when the job data acquisition unit acquires at least one or more job data, the job acquisition time, which is the time when each job data was acquired, is associated with the job data and stored in the job data management memory unit, and after the memory unit stores the scheduled delivery time, when the job data read from the job data management memory unit in response to a request from the child machine is transmitted to the child machine via a network by a job data transmission unit, the scheduled delivery time determination unit changes the scheduled delivery time using the job acquisition time of job data stored in the job data management memory unit other than the job data.

[0015] The child machine is further characterized in that it comprises an update data storage unit that stores the received update data, a scheduled update start time setting unit that sets a scheduled update start time, which is the time to start updating the control program, based on the time the update data was received, and a storage unit that stores the scheduled update start time, and that the parent machine changes the scheduled update start time in response to storing new job data in the job data management storage unit, and that the program update execution unit updates the control program at a timing based on the scheduled update start time.

[0016] The slave unit further includes a setting storage unit that stores an update start time setting, which is a setting related to the time at which to start updating the slave unit's control program, and the scheduled update start time setting unit uses the pre-stored update start time setting when setting the scheduled update start time.

[0017] The parent device further includes an update control information sending unit that sends update control information to the child device when the job data acquisition unit acquires a job and when job data is sent to the child device via the network, the update control information being information for determining the scheduled time at which the child device will execute the update process for the control program; when the job acquisition unit acquires a new job, the update control information sending unit sends the update control information to the child device, and the scheduled update start time setting unit of the child device updates the scheduled update start time based on the received update control information.

[0018] The parent device further includes an update acquisition request receiving unit that receives an update data acquisition request sent from a child device, and a delivery feasibility determination unit that, when the update data acquisition request is received from a child device, determines whether or not the update data can be delivered by the update data delivery unit based on the job data stored in the job data management memory unit, and the child device further includes an update data acquisition request unit that sends an update data acquisition request, which is a request to acquire update data, to the parent device.

[0019] The child device further includes a setting memory unit that stores an update request time setting, which is a setting regarding the time at which the update data acquisition request is sent to the parent device, and the update data acquisition request unit sends the update data acquisition request at a timing based on the update request time setting.

[0020] In the program update system of the present invention, the information processing device is an image forming device.

[0021] The present invention also provides an information processing device comprising: a job data acquisition unit that acquires job data including data to be processed in the information processing device; a job data management storage unit that manages and stores the acquired job data; a job data transmission unit that transmits job data read from the job data management storage unit to the second information processing device via a network in response to a request from the second information processing device; an update data acquisition unit that acquires update data for updating a control program that controls the operation of the information processing device; an update data storage unit that stores the acquired update data; and an update data distribution unit that distributes the update data read from the update data storage unit to the second information processing device via the network, and characterized in that the information processing device determines the timing or possibility of distributing the update data depending on the job data stored in the job data management storage unit.

[0022] The present invention also provides a program update method for an information processing device that updates a control program for executing a predetermined function using update data, wherein the information processing device comprises a parent device that receives the update data transmitted from a distribution device, and one or more child devices that use the update data distributed from the parent device to update a control program for executing a function of the information processing device, and the program update method for the information processing device includes a storage step in which a control unit provided in the parent device stores a scheduled delivery time that is a scheduled time for delivering the update data to the child devices, an update data acquisition step that acquires update data for updating the control program, a job acquisition step that acquires a job including data to be processed in the information processing device, a job acquisition time storage step that sets and stores the job acquisition time that is the time when the job is acquired, and a program update step in which a control unit provided in the parent device stores a scheduled delivery time that is a scheduled time for delivering the update data to the child devices, and an update data distribution step of distributing the acquired update data to the slave unit, and then a control unit provided in the slave unit executes an update data receiving step of receiving the update data distributed from the parent unit and a program update execution step of updating the control program using the received update data, wherein when one or more jobs are acquired in the job acquisition step, a job acquisition time is set and stored for each acquired job, and in the update data distribution step, the scheduled distribution time is set using the job acquisition time of the last acquired job among the set and stored job acquisition times, and the update data is distributed to the slave unit when the current time has passed the set scheduled distribution time. [Effects of the Invention]

[0023] According to this invention, when the job acquisition unit of the parent device of the information processing device acquires one or more jobs, it sets and stores a job acquisition time for each acquired job, and uses the job acquisition time of the last acquired job among the set and stored job acquisition times to set a scheduled delivery time, and delivers update data to the child device when the current time has passed the set scheduled delivery time. This makes it possible to avoid a situation where a function that the user is trying to execute cannot be executed because an update of the control program has started in the child device of the information processing device, and it is possible to ensure convenience for the user of the information processing device by preventing the timing of the user's job execution and the update of the control program from overlapping. [Brief explanation of the drawings]

[0024] [Figure 1] 1 is a schematic explanatory diagram of an embodiment of a program updating system of the present invention; [Figure 2] 1 is a block diagram showing the configuration of an embodiment of an image forming apparatus (parent machine) of the present invention. [Figure 3] 1 is a block diagram showing the configuration of an embodiment of an image forming apparatus (slave unit) according to the present invention; [Figure 4] 1 is a block diagram showing the configuration of an embodiment of a distribution device according to the present invention; [Figure 5] 3 is an explanatory diagram of an embodiment of information stored in a storage unit of the image forming apparatus (parent device) of the present invention; FIG. [Figure 6] 3 is an explanatory diagram of an embodiment of information stored in a storage unit of the image forming apparatus (slave unit) of the present invention; FIG. [Figure 7] 4 is a communication sequence of a first embodiment of a control program update process in the program update system of the present invention. [Figure 8] 10 is a communication sequence of a second embodiment of a control program update process in a program update system of the present invention. [Figure 9] 10 is a communication sequence of a second embodiment of a control program update process in a program update system of the present invention. [Figure 10]10 is a communication sequence of a control program update process according to a third embodiment of the present invention in a program update system. [Figure 11] 10 is a communication sequence of a control program update process according to a third embodiment of the present invention in a program update system. [Figure 12] 10 is a communication sequence of a control program update process according to a third embodiment of the present invention in a program update system. [Figure 13] 10 is a communication sequence of a fourth embodiment of a control program update process in a program update system of the present invention. [Figure 14] 10 is a communication sequence of a fourth embodiment of a control program update process in a program update system of the present invention. [Figure 15] 10 is a communication sequence of a fourth embodiment of a control program update process in a program update system of the present invention. [Figure 16] 10 is a communication sequence of a fourth embodiment of a control program update process in a program update system of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0025] Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. However, the present invention is not limited to the following embodiments. <Program update system configuration> FIG. 1 shows a schematic diagram of an embodiment of a program updating system according to the present invention. In FIG. 1, the program update system of the present invention is mainly composed of a distribution device 3 connected via a network 10 and image forming devices (1, 2) that process image data. The number of image forming devices may be one, but multiple image forming devices may also be connected to the network. The image forming apparatuses (1, 2) correspond to the information processing apparatuses of the present invention. Furthermore, the program update system may also include an information processing terminal 4 owned by the user, which the user uses to create or input print data and transmit the print data to the image forming device.

[0026] In the following embodiment, a process for updating a control program installed in an image forming apparatus corresponding to an information processing apparatus will be described. However, the control program update process of the present invention is applicable not only to image forming apparatuses but also to update processes for control programs installed in information processing devices other than image forming apparatuses (for example, personal computers, mobile terminals, etc.). Information including data processed in an information processing device is called a job, and in the following examples, jobs including data processed in an image forming device that are primarily intended for printing are called print jobs.

[0027] The distribution device 3, the image forming devices (1, 2), and the information processing terminal 4 are capable of communicating with each other via a network 10. The number of image forming devices and information processing terminals connected to the distribution device 3 via the network 10 may not be one, but may be multiple.

[0028] The network 10 may be any existing communication network, such as a wide area communication network like the Internet or a LAN, and the communication format may be either wired communication or wireless communication.

[0029] An image forming device (MFP: Multifunction Peripheral) is a device that processes image data, and performs input, formation, output, storage, transfer, etc. of image data. An image forming apparatus is also called a multifunction peripheral, or simply an MFP. In addition, in this invention, an image forming device corresponding to an information processing device is comprised of a parent device 1 that receives update data transmitted from a distribution device 3, and one or more child devices 2 that use the update data transmitted from the parent device to update the control program that executes the functions of the image forming device itself. Hereinafter, the base unit 1 will also be referred to as the MFPP, and the handset 2 will also be referred to as the MFPC.

[0030] The distribution device 3 is a device that mainly stores a control program used in the image forming apparatus MFP and distributes the control program to the image forming apparatus. Furthermore, when a defect in the control program is corrected or a new function is added, the control program is updated. Data including an update program for updating the control program used in the image forming apparatus MFP is called update data. When a control program already stored in the image forming device MFP needs to be updated, update data for updating the control program is stored in the distribution device 3 and transmitted from the distribution device 3 to the image forming device MFP that is the parent device. In the following embodiment, the update data is transmitted from the distribution device 3 to the image forming device MFP, which is the parent device. However, the update data may be stored in an external storage medium such as a USB memory, and the external storage medium may be directly attached to the parent device to obtain the update data from the external storage medium.

[0031] The distribution device 3 is also called a distribution server, or simply an SV. The update data may be sent directly from the distribution device 3 to each image forming device, but in this invention, the update data is sent only to the parent device 1 among the multiple image forming devices.

[0032] The control program is a program for executing functions provided in the image forming apparatus, and is software that is installed in each image forming apparatus, and is also called control software. In addition, update data is data for adding new functions to the image forming device or changing or improving functions by updating the control program, and the control program is updated through specified processing by the control program.

[0033] As described above, the information processing terminal 4 is a device owned by a user who intends to use the image forming apparatus, and corresponds to a personal computer or a mobile terminal. The information processing terminal 4 is also called a user terminal, or simply a TE.

[0034] <Configuration of image forming device> The image forming device MFP is an electronic device that has functions for processing image data, such as a copying function, a printing function, a document scanning function, a document editing function, a document saving function, a document transmission (fax) function, and a communication function. As described above, the image forming apparatus MFP is made up of a parent device MFPP that receives a control program directly from a distribution server SV, and a child device MFPC that receives the control program from the parent device MFPP. The MFPP master and MFPC slave devices perform different processes related to the update function of the control program, so the configuration block diagrams for the MFPP master and MFPC slave devices will be explained separately. The MFPP parent device is a device that has the function of receiving update data and print jobs and distributing the update data and print jobs to the MFPC child devices, but it does not have to be an image forming device that has a printing function or the like, and may be an information processing device that does not have a printing function or the like. In the following embodiments, the image forming apparatus MFP of the present invention will be described as having a printing function in particular, but may have other functions.

[0035] (Configuration of image forming device (parent machine)) FIG. 2 shows a block diagram of the configuration of an embodiment of the image forming apparatus (parent machine) of the present invention. In FIG. 2, the image forming apparatus (parent machine) MFPP of the present invention mainly includes a control unit 11, an operation unit 12, a display unit 13, an image processing unit 14, a communication unit 15, an update data acquisition unit 16, a print job acquisition unit 17, a job acquisition time setting unit 21, an update data distribution unit 22, an update change time setting unit 23, an update change time transmission unit 24, a print job transmission unit 25, a control program update unit 26, an update acquisition request receiving unit 27, a program distribution determination unit 28, an acquisition request response unit 29, a function execution unit 30, and a memory unit 40.

[0036] Here, the image processing unit 14 is mainly composed of an image input unit, an image conversion unit, and an image output unit, as will be described later. Moreover, an update acquisition request receiving unit 27, a program distribution determining unit 28, and an acquisition request responding unit 29 are functional blocks that operate when there is a request from the MFPC slave side to acquire update data.

[0037] The control unit 11 is a part that controls the operation of each component such as the display unit 13 and the image processing unit 14, and is mainly composed of a CPU, a ROM, a RAM, an I / O controller, a timer, and the like. The CPU organically operates various hardware components based on a control program stored in advance in a nonvolatile memory such as a ROM, thereby executing the image forming function and update data distribution function of the present invention.

[0038] Among the above components, the job acquisition time setting unit 21, the update change time setting unit 23, the program distribution determination unit 28, etc. are functional blocks in which the CPU executes the respective processes based on a predetermined program.

[0039] The operation unit 12 is an input device that allows the user of the MFPP master device to perform predetermined input operations. For example, it is a part for inputting information such as characters and selecting functions, and may use a touch panel, keys for specific purposes, or the like. Keys operated by the user include an operation start key, a function selection key, a setting key, and the like. For example, the user can start reading a document by operating the touch panel or by pressing a key to start the reading operation, or can start transmitting information such as image data to a specified destination by pressing a transmission start key to start transmitting information.

[0040] Display unit 13 is a part that displays information, and displays information necessary for executing each function, the results of executing the function, etc. to inform the user. For example, if an LCD, an organic EL display, or the like is used and a touch panel is used as operation unit 12, display unit 13 and the touch panel are arranged so as to overlap each other. The display unit 13 displays, for example, the settings of the setting items used for printing, etc. of the parent MFPP device, the information necessary to execute document reading functions, etc., and the operation screen of the selected function using characters, symbols, figures, images, icons, animations, videos, etc.

[0041] Furthermore, in this invention, for example, when update data is received, the fact that the update data has been received may be displayed on the display unit 13, and when updating (updating) the control program using the update data, the fact that the control program is being updated may be displayed on the display unit 13.

[0042] The image processing unit 14 is a unit that executes the image forming function, which is the main function of the MFPP master unit, and is mainly made up of an image input unit, an image conversion unit, and an image output unit. Primarily, the image input unit is the part that inputs image data in a specified format, the image conversion unit is the part that converts the input image data into data of appropriate image quality and format depending on the intended use, such as printing or screen display, and the image output unit is the part that outputs the data obtained as a result of the conversion onto printing paper, etc., or transmits it to other devices via a network.

[0043] The image input unit is a part that inputs image data of a document containing images, text, figures, etc., such as print data intended for printing. For example, it is a part that optically reads a document placed on a document tray, etc., and acquires image data to be printed that is included in print job information 43 received by the print job acquisition unit 17 described below from another device. A scanner (reading device) is used as an image input unit that optically reads an original document on which information is written. The parent machine MFPP includes a document table (document table) on which the document is placed and a document cover that holds the document in place in order to read the document. The MFPP may also include an automatic document feeder (ADF) that allows multiple sheets of original documents to be placed on it and automatically transports and reads the multiple original documents one by one. When receiving data from another device via a network, the print data included in the received data may be the image data itself to be printed, or it may be data in a specified format for generating an image, such as a page description language.

[0044] There are various methods for inputting image information. For example, a document containing an image or the like is read by a scanner, and image data of the document (hereinafter referred to as input image data) is stored in storage unit 40.

[0045] Furthermore, for example, an interface for connecting an external storage medium such as a USB memory corresponds to the image input unit. An electronic data file such as image information to be input may be stored in an external storage medium such as a USB memory, and the USB memory or the like may be connected to an input interface such as a USB terminal, and the desired electronic data file stored in the USB memory or the like may be read out by performing a predetermined input operation on the operation unit 12, and stored in the storage unit 40 as input image data.

[0046] The image conversion unit performs various image processing on input image data in RGB format that has been scanned and stored in the storage unit 40, for example, and converts the data into image data in CMYK format that is suitable for printing. It also converts the data into printable image data by analyzing and rendering the page description language. Alternatively, it converts the resolution when outputting an image for display on a screen. The image data obtained through conversion by the image conversion unit (hereinafter referred to as output image data) may be stored again in the storage unit 40, or may be output directly from the image output unit.

[0047] The image output unit is a part that outputs output image data, and for example, forms an image by electrophotography and fixes the image on a printing sheet. However, the output of image data is not limited to printing, but also includes sending image data to other communication devices by fax over a telephone line, or by e-mail or FTP over a network such as the Internet. Writing and storing output image data in an external storage medium such as a USB memory also corresponds to image output.

[0048] The communication unit 15 is a part that performs data communication with other communication devices via the network 10. As shown in FIG. 1, the MFPP master device is connected via a network 10 to a distribution server (SV) 3 and an information processing terminal (TE) 4 owned by a user. The image forming apparatus (MFP) 1 is also connected to other image forming apparatuses MFP via a network 10.

[0049] The MFPP master device receives, via the communication unit 15, for example, update data transmitted from the distribution server (SV) 3, and information such as print jobs transmitted from the information processing terminal (TE) 4. Alternatively, it may transmit an inquiry request for updated data to the distribution server SV or the like via the network 10.

[0050] The update data acquisition unit 16 is a part that acquires update data transmitted from the distribution server SV. As a general rule, the parent MFPP inquires of the distribution server SV whether there is any update data, and if there is, sends an update software inquiry request requesting the distribution of the update data.If new update data is stored in the distribution server SV, the distribution server SV sends the new update data to the parent MFPP in response to the inquiry request. However, when new update data is stored in the distribution server SV, the distribution server SV may automatically transmit the new update data to the master device MFPP.

[0051] The update software inquiry request may be sent to the distribution server SV, for example, periodically (every day at a set time), or may be sent to the distribution server SV when an administrator of the parent MFPP performs a specified input operation at the parent MFPP. The acquired update data is stored in storage unit 40 for distribution (transfer) to the MFPC slave devices.

[0052] Print job acquisition unit 17 is a part that acquires a print job including data to be processed in image forming apparatus MFP. Generally, a functional block that acquires a job including data to be processed in an information processing device is called a job acquisition unit, and the job acquisition unit includes a print job acquisition unit 17. The job acquisition unit also includes, for example, a reading job acquisition unit, an image recognition job acquisition unit, a transmission job acquisition unit, and the like.

[0053] A print job may be generated, for example, by a user directly inputting data into the MFPP parent device, or by scanning a document. In addition, a print job generated by an information processing terminal TE owned by a user may be received via the network 10 using the communication unit 15. The acquired print job is stored in the storage unit 40 as print job information 43. Furthermore, in the MFPP parent device, for example, when a print start operation specifying that print job is performed, the image data included in the print job is printed.

[0054] The job acquisition time setting unit 21 is a unit that sets and stores the time when the print job is acquired by the print job acquisition unit 17. In general, the time when the job is acquired is called the job acquisition time. The time when the print job is acquired is stored in the storage unit 40 as a job acquisition time (tj) 44.

[0055] The update data distribution unit 22 distributes the acquired update data to the MFPC slave after a predetermined scheduled distribution time has passed. The predetermined scheduled distribution time is a time (th) 47 stored in the storage unit 40 (described later), and is set by the update data distribution unit 22. For example, if the timing for distributing update data to the MFPC slave is set in advance to distribute the update data to the MFPC slave immediately after acquiring the update data from the distribution server SV, the time when the update data is acquired is set as the scheduled distribution time th.

[0056] However, the scheduled delivery time th may be set based on whether or not there is a print job stored in the parent device MFPP. For example, when the print job acquisition unit 17 acquires one or more print jobs, the job acquisition time setting unit 21 sets and stores the job acquisition time tj for each acquired job, and the update data distribution unit 22 sets the scheduled distribution time th using the job acquisition time tj of the last acquired print job among the set and stored job acquisition times tj, and distributes the update data to the slave device when the current time has passed the set scheduled distribution time th.

[0057] It is difficult to set a fixed time period after acquisition, but since a user stores a print job in the MFPP parent device with the intention of printing the print job, it is highly likely that the user will perform an operation to start printing the print job within a relatively short period of time, such as five or ten minutes, after the print job has been stored in the MFPP parent device. Therefore, if the update process of the control program using the update data is started within a specified time after acquisition, the timing of the execution of the print job and the timing of the update process of the control program may overlap, and the execution of the print job may have to wait until the update process is completed.

[0058] To avoid, as much as possible, a situation in which the execution of a print job that the user is attempting to execute has to wait, it is preferable to distribute the update data to the MFPC slave devices at a timing determined based on the print job information stored in the MFPP master device, rather than distributing the update data to the MFPC slave devices immediately after acquiring the update data. For example, as will be described later, if the print job is stored in the parent device MFPP, the scheduled delivery time th is set using the time when the print job was acquired (job acquisition time tj). In this case, after the update data is acquired, the update data is distributed to the MFPC slave when the current time passes the scheduled distribution time th that has been set. Hereinafter, the current time will also be represented by the symbol TN.

[0059] Furthermore, as will be described later, if the print job acquisition unit 17 acquires a new print job before the scheduled delivery time th is set, the job acquisition time setting unit 21 may set and store a second job acquisition time tj at which the new print job is acquired, and the update data distribution unit 22 may use the set and stored second job acquisition time tj to change the scheduled delivery time th.

[0060] Furthermore, as described above, the timing of distributing update data is primarily managed by the MFPP master, but instead of automatically distributing update data at the timing set by the MFPP master, the MFPP master may distribute update data to the MFPC slave when it receives an update data acquisition request from the MFPC slave. In this case, as will be described later, the update data distribution unit 22 uses the set and stored job acquisition time tj to set a scheduled distribution time th, which is the scheduled time for distributing update data to the MFPC slave, and distributes the acquired update data to the MFPC slave when the current time has passed the set scheduled distribution time th after receiving an update data acquisition request from the MFPC slave.

[0061] As described above, there are at least three types of timing for distributing update data: one in which the update data is distributed to the MFPC slave immediately after being acquired; one in which the scheduled distribution time (th) is set using the time when the print job is acquired (job acquisition time tj) when the print job is stored in the MFPP master; and one in which the update data is distributed to the MFPC slave when an update data acquisition request is received from the MFPC slave. It is preferable that the MFPP master and MFPC slave set and store in advance which distribution timing to adopt.

[0062] The update change time setting unit 23 is a part that, when a print job is acquired, changes the scheduled time for executing the update process of the control program using update data, and sets the update change time, which is the scheduled time after the change. The changed scheduled time is stored in the storage unit 40 as an updated change time 46 (t2). As will be described later, the update change time t2 is set from the above-mentioned job acquisition time tj and a predetermined delay setting time t0 (t2=tj+t0). For example, if the job acquisition time tj is 11:00 on September 24, 2021, and the delay setting time t0 is preset to 20 minutes, the update change time t2 is set to 11:20 on September 24, 2021. The update change time t2 is set to avoid the situation where, when a print job is acquired, the print processing is normally executed by the print job, but the update processing of the control program is executed just before or during the execution of the print job, causing the execution of the print job to have to wait. The delay setting time t0 is set in advance in consideration of the execution time of the printing process of a typical print job.

[0063] The update change time transmitting unit 24 is a part that transmits the set update change time t2 to each MFPC slave device, as described above. When the MFPC device receives the update change time t2, it updates the scheduled update start time T (described later) to the update change time t2 if a predetermined condition is satisfied.

[0064] The print job transmitting unit 25 is a part that, when a print job request is received from an MFPC slave, transmits the requested print job data to the MFPC slave. The MFPC slave device that receives the print job data analyzes the various data included in the print job and executes the print process.

[0065] The control program update unit 26 is a unit that uses update data to update the control program of the MFPP master device. Alternatively, the control program may be replaced with an updated program.

[0066] The update acquisition request receiving unit 27 is a part that receives an update data acquisition request transmitted from the MFPC slave. The update data acquisition request is transmitted from the MFPC slave device to the MFPP master device, for example, when the current time TN passes the scheduled update start time T in the MFPC slave device. When the MFPP master device receives the update data acquisition request and the update data is stored in its own storage unit 40, the MFPP master device determines whether or not to distribute the update data to the MFPC slave device.

[0067] The program distribution determining unit 28 is a part that determines whether or not update data should be distributed to the MFPC slave device. As described above, when an update data acquisition request is received from the MFPC slave device, a determination is made as to whether or not the update data should be distributed. For example, if there is no update data in storage unit 40 of the MFPP master device, or if the control program of the MFPC slave device has already been updated to the latest control program, it is determined that there is nothing to distribute.

[0068] On the other hand, if there is update data in the storage unit 40 of the MFPP parent device, and the current time TN has passed the scheduled distribution time th, the user does not have a print job that is likely to be processed using the child device within a certain time, and therefore it is determined that the update data should be distributed to the MFPC child device. However, if the current time TN has not passed the scheduled distribution time th, the printer is holding a print job that was recently submitted by the user, and it is highly likely that the user will use the slave device in the future, so it is determined that the update data should not yet be distributed to the slave device MFPC. As will be described later, the result of the determination made by program distribution determination unit 28 is sent as acquisition response information to the MFPC device that has transmitted the update data acquisition request.

[0069] Acquisition request response unit 29 is a part that generates a response to an update data acquisition request transmitted from a slave MFPC device and transmits the response to the slave MFPC device. A response to an update data acquisition request is called acquisition response information. The acquired response information may include, for example, the following three pieces of response information in accordance with the results of the above determination. Response 1: No update data response (no update data to apply) Response 2: Retry response (Update data is available, but it is not yet time to distribute it) Response 3: Update available (update data is available and it is time to update)

[0070] For example, as described above, if there is no update data in storage unit 40 of the MFPP master device, there is nothing to distribute, so the MFPP master device generates acquisition response information meaning a "no update data response" and transmits it to the MFPP slave device. On the other hand, if there is update data in storage unit 40 of the MFPP master device and the current time TN has passed the scheduled distribution time th, acquisition response information indicating an "update possible response" is generated and transmitted to the MFPC slave device. In this case, the update data stored in storage unit 40 is transmitted to the MFPC slave device.

[0071] Furthermore, if there is update data in the storage unit 40 of the MFPP master device, but the current time TN has not passed the scheduled distribution time th, the MFPP master device generates acquisition response information meaning a "retry response" and transmits it to the MFPC slave device. In this case, even if the update data is stored, it has not yet been transmitted to the MFPC slave device.

[0072] Function execution unit 30 is a part that executes predetermined functions that can be executed by image forming apparatus MFP. In the case where the image forming apparatus MFP is a multifunction peripheral having the above-mentioned various functions, for example, when the user performs an input operation to select a desired function, the selected function is executed. Like the MFPC handset, the MFPP parent device also has an image forming function, so when the user selects the copy function, for example, a copy operation is performed on the document placed on the document platen.

[0073] The memory unit 40 is a part that stores information and programs necessary to execute each function of the image processing device (parent device) MFPP of this invention, and uses semiconductor memory elements such as ROM, RAM, and flash memory, storage devices such as HDD and SSD, and other storage media. Information that is preset as a fixed value and never changes is stored in memory such as ROM, information that is preset as a fixed value but may change is stored in non-volatile memory such as flash memory or HDD, and information that is stored temporarily is stored in volatile memory such as RAM, flash memory, HDD, etc.

[0074] The storage unit 40 stores, for example, child device management information 41, update data 42, print job information 43, job acquisition time 44, delay setting time 45, update change time 46, scheduled delivery time 47, acquisition response information 48, and the like. The storage unit 40 also stores a control program for executing the functions of the master MFPP. FIG. 5 is an explanatory diagram of an example of information stored in the storage unit 40 of the image forming apparatus (parent device).

[0075] The slave unit management information 41 is information for identifying the image forming device (slave unit), and includes, for example, the slave unit MFPC's device name, model name, serial number, IP address, installation location, optional function information, and control program version information. For example, a print job or update data is sent to the MFPC slave device using the IP address.

[0076] As described above, the update data 42 is a program for updating the control program of the image forming apparatus, and is mainly acquired from the distribution server SV. However, update data 42 may also be directly input into the master MFPP by an administrator of the master MFPP. The update data 42 includes both data for updating the control program of the MFPP master device and data for updating the control program of the slave device. If the update data 42 is a program common to all MFPC slave devices, the update data is distributed to all MFPC slave devices. Alternatively, if the update data 42 is a program relating to a specific function, the update data may be distributed only to MFPC slave devices that have that specific function. However, in the following embodiment, the update data 42 is a program common to all MFPC slave devices, and will be described as being distributed to all MFPC slave devices.

[0077] The print job information 43 is information used when executing the print function, and includes information about the user who registered the print job, information specifying the paper feed and output trays, other control information, and image data to be printed. In this invention, print job information 43 is received from the information processing terminal TE and temporarily stored in the parent device MFPP, and when the parent device MFPP requests the print job information 43, the parent device MFPP transmits the requested print job information 43 to the child device MFPC. Furthermore, when a print function for printing image data in print job information 43 is selected in the MFPP parent device, the print process is executed in the MFPP parent device.

[0078] The job acquisition time 44 is the time (tj) when the print job is acquired, and is set and stored by the job acquisition time setting unit 21 described above. For example, as shown in FIG. 5, date information (2021.09.25, 11:00) meaning 11:00 on September 25, 2021 is stored as the job acquisition time tj. The job acquisition time (tj) 44 is used when setting the update change time 46 and the scheduled delivery time 47.

[0079] The delay setting time 45 is the time (t0) that takes into account the time from when a job is registered in the parent device to when the child device is operated and printing begins, or the time until printing is completed, and is information that is set in advance to prevent the control program from being updated between when the parent device acquires the print job and when the user operates the child device and executes the print job. As the delay setting time (t0) 45, for example, 20 minutes is set as shown in FIG. Here, the user who manages the parent machine sets a fixed time, but the parent machine may also automatically determine the delay setting time (t0) 45 after tracing the history of past print jobs and performing a statistical analysis of the time from registration to execution. The delay setting time (t0) 45 is used when setting the update change time 46 and the scheduled distribution time 47.

[0080] The update change time 46 corresponds to the scheduled time (t2) at which the update process of the control program using the update data is executed, and is set by the update change time setting unit 23 and transmitted to the slave MFPC by the update change time transmitting unit 24. The scheduled time for executing the update process is set to a predetermined time as an initial value in each MFPC handset. If no print job has been acquired, the initial value time is used as it is as the scheduled time for executing the update process.

[0081] However, when a print job is acquired, it is preferable to avoid the printing process of the print job being postponed due to the update process of the control program, so the scheduled time for executing this update process is changed. The update change time (t2) 46 is the time that is set when a print job is acquired, and by transmitting the update change time (t2) 46 to each MFPC slave device, the update process executed by the MFPC slave device is postponed to the update change time (t2) 46.

[0082] The update change time (t2) 46 is set corresponding to the time when the print job is acquired. For example, the time obtained by adding the delay setting time t0 to the job acquisition time tj is set as the update change time (t2) 46 (t2=tj+t0). As shown in Figure 5, if the job acquisition time tj is 11:00 on September 25, 2021, and the delay setting time t0 is 20 minutes, then t2 = tj + t0, so the update change time t2 is 11:20 on September 25, 2021.

[0083] Scheduled distribution time 47 is the scheduled time (th) at which update data is distributed to MFPC slave devices, and in principle, update data distribution unit 22 distributes update data to MFPC slave devices after scheduled time th has passed. The scheduled delivery time (th) 47 is set to a predetermined time as an initial value, and if no print job is acquired, the initial time is used.

[0084] However, as described above, when the MFPP parent device acquires a print job, it is highly likely that the print job will be executed by the MFPP parent device within a predetermined time, or that a print processing request for the print job will be made by the MFPC child device, so the scheduled delivery time (th) 47 is changed to correspond to the acquisition time of the print job. For example, the scheduled delivery time th may be a time later than the job acquisition time tj of the last acquired print job, and the scheduled delivery time th may be set to the job acquisition time tj of the last acquired print job plus a delay setting time t0 pre-stored in the memory unit 40.

[0085] When a plurality of print jobs are acquired consecutively at different times, the time at which each print job is acquired (job acquisition time tj) is stored in the storage unit 40 for each print job. In this case, the job acquisition time tj of the last acquired print job among the acquired print jobs is read out, and the time obtained by adding the above-mentioned delay setting time t0 to this job acquisition time tj is set as the scheduled delivery time (th) 47 (th=tj+t0). After the current time TN passes the scheduled distribution time (th) 47, the update data is distributed to the MFPC slave devices.

[0086] As shown in Figure 5, if the job acquisition time tj of the last acquired print job is 11:00 on September 25, 2021, and the delay setting time t0 is 20 minutes, then the scheduled delivery time (th) 47 is 11:20 on September 25, 2021, since th = tj + t0.

[0087] As described above, the acquisition response information 48 is a response to the update data acquisition request sent from the MFPC slave device. For example, as shown in FIG. 5, “01” in the acquisition response information 48 corresponds to response 1, which indicates no updated data; “02” in the acquisition response information 48 corresponds to response 2, which indicates a retry response; and “03” in the acquisition response information 48 corresponds to response 3, which indicates an update possible response. Acquired response information 48 including any one of the three pieces of response information (responses 1, 2, and 3) described above (01, 02, or 03) is transmitted to the MFPC slave.

[0088] (Configuration of image forming device (slave unit)) FIG. 3 shows a block diagram of the configuration of an embodiment of the image forming apparatus (slave unit) of the present invention. In FIG. 3, the image forming apparatus (child machine) MFPC of the present invention mainly includes a control unit 51, an operation unit 52, a display unit 53, an image processing unit 54, a communication unit 55, an update data receiving unit 56, a function execution unit 57, an update acquisition time recording unit 58, an update start scheduled time setting unit 59, a print request accepting unit 60, a print job acquisition request unit 61, a print job acquisition unit 62, an update change time receiving unit 63, an update postponement setting unit 64, a program update executing unit 65, an update data acquisition request unit 66, an acquisition response receiving unit 67, an update start change unit 68, and a memory unit 70.

[0089] Here, the operation unit 52, display unit 53, image processing unit 54, and communication unit 55 are functional blocks that perform the same processing as in the parent unit, and the image processing unit 54 is mainly composed of an image input unit, an image conversion unit, and an image output unit. The details of these functional blocks are the same as in the parent unit, so they will be omitted here. An update data acquisition request unit 66, an acquisition response receiving unit 67, and an update start changing unit 68 are functional blocks that operate when the MFPC device makes an update data acquisition request to the MFPP device.

[0090] The control unit 51 is a part that controls the operation of each component such as the operation unit 52 and the image processing unit 54, and is mainly composed of a CPU, a ROM, a RAM, an I / O controller, a timer, and the like. The CPU organically operates various hardware components based on a control program stored in advance in a nonvolatile memory such as a ROM, thereby executing the image forming function of the present invention.

[0091] Furthermore, among the above components, the update acquisition time recording unit 58, the scheduled update start time setting unit 59, the print request receiving unit 60, the update postponement setting unit 64, the update start change unit 68, etc. are functional blocks in which the CPU executes each process based on a predetermined program.

[0092] The update data receiving unit 56 is a part that receives update data distributed from the MFPP master device. In principle, when the MFPC slave device receives update data, it uses the update data to update the control program. Alternatively, if a scheduled update start time has been set, when the current time TN passes the scheduled update start time, the received update data is used to update the control program.

[0093] The function execution unit 57, like the parent device MFPP described above, is a part that executes predetermined functions that can be executed by the image forming device MFP, and for example, when a user performs an input operation to select a desired function, the selected function (for example, a printing function) is executed.

[0094] The update acquisition time recording unit 58 is a unit that records the update acquisition time tk when update data distributed from the MFPP master device is received. The update acquisition time tk is, for example, the time when the update data is received. The update acquisition time tk is used to set update start calculation information t1, which will be described later, and further, the update start scheduled time T is set from the update start calculation information t1.

[0095] The scheduled update start time setting unit 59 is a part that sets the scheduled update start time T using the recorded update acquisition time tk. The scheduled update start time T is the time at which the MFPC device starts updating the control program that executes the functions of the MFPC device using the received update data. The scheduled update start time setting unit 59 sets the scheduled update start time T to, for example, a date that is later than the recorded update acquisition time tk and is equal to the hour and minute information portion set in the update execution setting time S described below.

[0096] As described above, when update data is received and the update acquisition time tk is set, first, the update start calculation information t1 is set. The update start calculation information t1 is time information for setting the scheduled update start time T, and is set from the update execution set time S and the update acquisition time tk that are set and stored in advance for each MFPC device.

[0097] The update execution set time S is the initial value of the time information for starting updating of the control program using the update data, and only hour and minute information is set without setting the year, month, and day. For example, the time information of 3:00 is initially set as the update execution set time S and stored in a nonvolatile memory such as an HDD. The update execution set time S may be set and stored in advance as the same time information in all MFPC slave devices, or may be changed to different time information for each MFPC slave device in accordance with the installation conditions of each MFPC slave device, such as the location where the MFPC is installed or the operating time zone.

[0098] As the update start calculation information t1, taking into consideration this update execution set time S, a date that is later than the update acquisition time tk and whose hour / minute information portion is equal to the update execution set time S is set. The year / month / day portion of the update start calculation information t1 may be any time that is later than the year / month / day of the update acquisition time tk, but may also be, for example, the year / month / day that next comes first when the update execution set time S occurs, or the day after the year / month / day of the update acquisition time tk.

[0099] For example, if the update acquisition time tk, which is the time when the update data was received, is 16:00 on September 24, 2021, and the update execution setting time S is 3:00, the next date after the update acquisition time tk on which the update execution setting time S first occurs is September 25, 2021, the day after the update acquisition time tk, so the date 3:00 on September 25, 2021 is set as the update start calculation information t1.

[0100] Furthermore, if the update acquisition time tk is 1:00 on September 25, 2021, and the update execution setting time S is 3:00, the next date on which the update execution setting time S first occurs is September 25, 2021, which is the day of the update acquisition time tk, so the update start calculation information t1 is set to 3:00 on September 25, 2021.

[0101] Next, this set update start calculation information t1 is used as the initial value of the scheduled update start time T. For example, when update data is received for the first time, the update start calculation information t1 is set as is for the update start scheduled time T (T=t1). Furthermore, each time new update data is received, a different date is set in the update start calculation information t1, and therefore the scheduled update start time T is also changed to a date equal to t1.

[0102] However, as will be described later, when update change time t2 is received from the parent MFPP device, the scheduled update start time T is changed to correspond to that update change time t2. In this case, the scheduled update start time T is postponed. For example, if the update start calculation information t1 set for the scheduled update start time T is 3:00 on September 25, 2021, the update change time t2 received from the parent device MFPP is 3:10 on September 25, 2021, and since t2 is a date later than t1, the scheduled update start time T is changed (postponed) to the update change time t2 (T=t2). The scheduled update start time T is changed in this way when a new print job is stored in the parent MFPP device, in order to prevent the printing process of the print job and the update process of the control program from overlapping at the same time as much as possible, and to prevent the printing process from being postponed due to the update process of the control program.

[0103] The print request receiving unit 60 is a part that receives a print job execution request from a user using the operation unit and display unit. For example, in response to a user performing a predetermined input operation on the operation unit, the slave MFPC acquires information about print jobs registered by the user and stored in the master unit via the network, displays a list on the operation unit, and further accepts an execution request for the print job selected by the user's input operation.

[0104] The print job acquisition request unit 61 is a unit that, when receiving a print request from a user, transmits an acquisition request (print job data request) for the print job requested to be printed to the MFPP parent device. The print job data request includes information about the requested print job (for example, the job identification number).

[0105] The print job acquisition unit 62 is a part that acquires a print job sent from the MFPP parent device. The acquired print job includes data for generating an image to be printed.

[0106] The update change time receiving unit 63 is a part that receives the update change time t2 transmitted from the master MFPP. As described above, when the MFPP parent device acquires a print job, the scheduled time at which the MFPP parent device will execute the update process for the control program using the update data is changed, and the updated scheduled time t2 is received.

[0107] The update postponement setting unit 64 is a part that changes the scheduled update start time T using the received update change time t2. For example, when update start calculation information t1 is set to scheduled update start time T (T=t1), and update change time t2 is received from the parent MFPP device, if the update change time t2 is later than scheduled update start time T (t2>T), the scheduled update start time T is changed to update change time t2 (T=t2). That is, the scheduled update start time T is postponed.

[0108] The program update execution unit 65 is a part that updates the control program of the MFPC device stored in the storage unit 70 with the received update data. In the MFPC slave device, when the current time TN passes the scheduled update start time T, the program update execution unit 65 updates the control program with the update data.

[0109] The update data acquisition request unit 66 is a part that transmits a request to acquire update data (update data acquisition request) to the MFPP master device. This update data acquisition request is information transmitted when the MFPC slave device automatically acquires update data at its own timing, and is used when the timing of acquiring update data is managed by the MFPC slave device side. For example, when the current time TN passes a predetermined scheduled update start time T stored in the MFPC slave device, the MFPC slave device transmits an update data acquisition request to the MFPP master device.

[0110] Alternatively, for example, when an administrator or the like performs a predetermined input operation in the MFPC slave device corresponding to the update data acquisition request, the update data acquisition request may be transmitted to the MFPP master device. If the timing of delivery of update data is managed on the parent MFPP side, the update data acquisition request does not need to be used.

[0111] The acquisition response receiving unit 67 is a part that receives acquisition response information transmitted from the MFPP master device in response to an update data acquisition request. As described above, the acquisition response information has three response contents, and after the acquisition response information is received, a process corresponding to each response content is executed. For example, when acquisition response information including an update possible response is received, update data is received from the master MFPP, and the update process of the control program is executed using the update data.

[0112] The update start change unit 68 is a part that resets the scheduled update start time T and resets the time (timing) at which an update data acquisition request is sent. For example, after the update acquisition request receiving unit 27 of the master MFPP receives an update data acquisition request from the slave MFPC, if the current time TN has not passed the set scheduled distribution time th, the acquisition request response unit 29 transmits, as a response to the update data acquisition request, acquisition response information including a retry response indicating that it is not yet time for distribution to the slave MFPC. Thereafter, when the acquisition response receiving unit 67 of the slave MFPC receives acquisition response information including a retry response, the update start changing unit 68 resets the scheduled update start time T to the time obtained by adding predetermined restart interval information tR, which will be described later, to the current time TN.

[0113] As described above, in the MFPP master device that has received the update data acquisition request, the program distribution determination unit 28 determines whether or not the update data should be distributed to the MFPC slave device. If it is determined that new update data is stored in the MFPP master device but that it is not yet time for distribution, acquisition response information including a retry response is transmitted to the MFPC slave device.

[0114] The MFPC device that has received the acquisition response information including the retry response has not yet transmitted the update data, and therefore must again transmit an update data acquisition request to the MFPP device to acquire the update data. Furthermore, the current time TN may already be past the scheduled update start time T, so the scheduled update start time T needs to be reset (postponed). Therefore, when acquisition response information including a retry response is received, the scheduled update start time T is reset (postponed), and further, the time (timing) for transmitting the update data acquisition request to the parent MFPP device is reset.

[0115] For example, as will be described later, the scheduled update start time T and the time to retransmit the update data acquisition request are set using restart interval information tR that is set and stored in advance in storage unit 70 of the MFPC device. As the restart interval information tR, a time such as 5 minutes or 10 minutes is set in advance. In this case, the scheduled update start time T is set to the current time TN plus the restart interval information tR (T=TN+tR). Furthermore, the time to retransmit the update data acquisition request may be set to, for example, the time when the acquisition response information including the retry response is received plus the restart interval information tR.

[0116] The memory unit 70 is a part that stores information and programs necessary to execute each function of the image processing device (child device) MFPC of the present invention, and uses semiconductor memory elements such as ROM, RAM, and flash memory, storage devices such as HDD and SSD, and other storage media. The memory unit 70 stores, for example, parent machine information 71, update data 72, print job information 73, update execution setting time 74, update acquisition time 75, update start calculation information 76, update change time 77, scheduled update start time 78, restart interval information 79, and acquisition response information 80. The storage unit 70 also stores a control program for executing the functions of its own MFPC device. FIG. 6 is an explanatory diagram of an example of information stored in the storage unit 70 of the image forming apparatus (slave).

[0117] The parent machine information 71 is information for identifying the image forming apparatus (parent machine), and includes, for example, the device name, model name, serial number, IP address, and installation location of the parent machine MFPP. For example, a print job data request or an update data acquisition request is sent to the MFPP parent device using the IP address.

[0118] Update data 72 is a program distributed from the master MFPP, and corresponds to update data 42 stored in the master MFPP described above.

[0119] The print job information 73 is information including data for generating an image to be printed, and corresponds to the print job information 43 stored in the above-mentioned MFPP parent device.

[0120] Update execution set time 74 is an initial value (S) of time information at which updating of the control program of the MFPC slave device is started using update data. As the update execution set time (S) 74, for example, as shown in FIG. 6, hour and minute information (03:00) meaning 3:00 is stored.

[0121] As described above, the update acquisition time 75 is the time (tk) when the update data is received. As the update acquisition time (tk) 75, for example, as shown in FIG. 6, date information (2021.09.24, 16:00) meaning 16:00 on September 24, 2021 is stored.

[0122] The update start calculation information 76 is time information (t1) for setting the scheduled update start time T. As the update start calculation information (t1) 76, for example, as shown in FIG. 6, date information (2021.09.25,03:00) meaning 3:00 on September 25, 2021 is stored.

[0123] As described above, update change time 77 is the same as update change time 46, which is the scheduled time when the update process of the control program using the update data is executed, and is information (t2) sent from the MFPP master device. As the update change time (t2) 77, for example, as shown in FIG. 6, date information (2021.09.25, 11:00) meaning 11:00 on September 25, 2021 is stored.

[0124] As described above, scheduled update start time 78 is the time (T) at which updating of the control program of the MFPC slave device will start using the received update data. As the scheduled update start time (T) 78, for example, as shown in FIG. 6, date information (2021.09.25,03:00) meaning 3:00 on September 25, 2021 is stored.

[0125] As described above, the restart interval information 79 is the scheduled update start time T and time information (tR) for resetting the retransmission time of the update data acquisition request. As the restart interval information (tR) 79, for example, time information such as 30 minutes is stored as shown in FIG.

[0126] As described above, the acquisition response information 80 is information sent from the master MFPP to the slave MFPC in response to the update data acquisition request sent from the slave MFPC, and is, for example, the same information as the acquisition response information 48 shown in FIG. 5.

[0127] <Configuration of distribution device (distribution server)> FIG. 4 shows a block diagram of the configuration of an embodiment of a distribution server according to the present invention. 4, the distribution server (SV) 3 of the present invention mainly comprises a control unit 101, an operation unit 102, a display unit 103, a communication unit 104, an update data transmission unit 105, and a storage unit 110.

[0128] The control unit 101 is a part that controls the operation of each component such as the operation unit 102 and the display unit 103, and is mainly composed of a CPU, a ROM, a RAM, an I / O controller, a timer, and the like. The CPU organically operates various hardware components based on a control program stored in advance in a non-volatile memory such as a ROM, and executes functions such as transmitting update data in the distribution server SV.

[0129] The operation unit 102 is an input device for the administrator of the distribution server SV to perform predetermined input operations. For example, it is a part for inputting information such as characters and selecting functions, and uses a keyboard, mouse, etc.

[0130] The display unit 103 is a part that displays information, and displays information necessary for executing each function, the results of the execution of the function, etc., to inform the administrator. For example, an LCD, an organic EL display, etc. may be used. On the display unit 103, for example, information required for generating and transmitting update data is displayed using characters, symbols, figures, images, icons, animations, moving images, and the like.

[0131] The communication unit 104 is a part that performs data communication with the image forming apparatus MFP via the network 10. For example, when an update software inquiry request is received from the parent MFPP of the image forming apparatus, and update data for the image forming apparatus MFP exists, the update data is transmitted to the parent MFPP.

[0132] The update data transmission unit 105 is a part that transmits update data for updating the control program that is stored in the distribution server SV and causes the image forming apparatus to execute its functions to the master device MFPP. In the following embodiment, transmission of update data also includes transmission of the new control program itself to the MFPP master device. As described above, for example, when an update software inquiry request transmitted from the MFPP master device is received, the latest update data stored in storage unit 110 is transmitted to the MFPP master device. Alternatively, even if no update software inquiry request is received, when new update data is stored in the distribution server SV, the update data may be transmitted to the master device MFPP.

[0133] The memory unit 110 is a part that stores the information and programs necessary to execute each function of the distribution server SV of this invention, and may use semiconductor memory elements such as ROM, RAM, flash memory, storage devices such as HDD, SSD, or other storage media. The storage unit 110 stores, for example, parent machine information 111, update data 112, and the like.

[0134] The parent device information 111 is information about the parent device MFPP to which update data for the image forming device is to be transmitted, and at least the IP address of the parent device MFPP and the like are stored.

[0135] The update data 112 is various data for updating the control program of the image forming apparatus, or may be the control program itself of a new image forming apparatus. Furthermore, the update data 112 may be a program common to all image forming apparatuses (MFPP master devices and MFPC slave devices), or may be a program that differs for each model or function of the image forming apparatus.

[0136] <Control program update process: Example 1> Here, an embodiment will be described in which the timing of distributing update data is managed in the MFPP master device. In this embodiment, when the print job acquisition unit 17 acquires a print job, the update data distribution unit 22 uses the job acquisition time tj, which is the time when the print job is acquired, to set the scheduled distribution time th, which is the scheduled time when the update data is to be distributed to another information processing device (MFPC slave), and distributes the update data to another information processing device (MFPC slave) when the current time has passed the set scheduled distribution time th.

[0137] When the MFPP parent device acquires update data from distribution server SV, if the MFPP parent device does not store any print jobs whose print processing has not been completed, it is considered unlikely that the timing of executing a print job and the timing of updating the control program will overlap, so there are no particular restrictions on the timing of distribution, and the update data may be distributed to each MFPC child device immediately after acquisition, or may be distributed after waiting for a predetermined time to arrive.

[0138] However, if the MFPP parent device stores a print job whose printing process has not yet been completed, it is preferable to impose a limit on the timing of distribution in order to prevent the print process from being postponed due to the control program update process, and distribute the update data to each MFPC child device after a predetermined time has elapsed since the print job was acquired, as will be described later. This reduces the possibility of an overlap between the timing of executing a print job and the timing of updating the control program even if the MFPC slave executes control program update processing immediately after receiving update data without checking the existence of a print job or update data stored in the MFPP master.

[0139] FIG. 7 shows a communication sequence of the first embodiment of the control program update process in the program update system. In the following communication sequence, the update data is also referred to as update software. Also shown is a communication sequence performed between the distribution server SV, the master device MFPP, the slave device MFPC, and the user terminal TE. In this first embodiment, it is assumed that the user does not perform an input operation to execute printing of a print job in the MFPC slave device.

[0140] It is assumed that at least the delay setting time t0 is stored in advance in the master MFPP. Furthermore, all devices, including the parent MFPP, are assumed to have a clock function and to be able to acquire the current time TN. The user terminal TE is assumed to be able to connect to the parent MFPP, and to have information about the parent MFPP, such as the IP address of the parent MFPP, and user authentication information (ID, password PW, etc.) for connecting to the parent MFPP stored in advance.

[0141] In step T1 of the user terminal TE in FIG. 7, it is assumed that the user creates document data, generates a print job to print the document, and performs an operation to send the print job to the parent device MFPP. The print job includes image data to be printed. This operation causes a print job to be sent from the user terminal TE to the parent device MFPP. Alternatively, the print job may be automatically sent to the MFPP parent device simply by the user performing an operation to input the print job he or she has created. For the purpose of explaining the update process, the input job is assumed to be a print job, but since some image forming devices have functions other than printing functions, the input job may also be a job other than a print job.

[0142] In step M1, the MFPP parent device acquires a print job and stores it in the storage unit 40 as print job information 43. In step M2, the time when the print job is acquired is stored as a job acquisition time tj. The job acquisition time tj is stored in association with the print job. The print job information 43 may store the image data to be printed contained in the print job, as well as the identification information of the user terminal TE that sent the print job, the name of the creator of the print job, a number for identifying the job, and the like. For the sake of explanation, the job acquisition time tj and the print job information 43 are described as separate information, but the job acquisition time tj may also be included in the print job information 43.

[0143] In step M3, an update software inquiry request is sent to the distribution server SV. In step S1, the distribution server SV receives an update software inquiry request. In step S2, it is confirmed whether new update data that has not yet been transmitted is stored in the storage unit 110. In step S3, if there is new update data that has not yet been transmitted, the update data is transmitted to the master MFPP. However, if no new update data exists, a "no update software response" indicating that no update data exists may be sent to the parent MFPP, although this is not shown.

[0144] In step M4, the master MFPP receives and stores the update data. In step M5, the job acquisition time tj of the last acquired print job is read. In FIG. 7, since only one print job is acquired, the job acquisition time tj of the print job acquired in step M1 is read out. However, if the MFPP parent device has already stored a plurality of print jobs, it reads out the most recent job acquisition time tj of the respective job acquisition times tj of the plurality of print jobs.

[0145] In step M6, the scheduled delivery time th is set from the read job acquisition time tj. For example, the time obtained by adding a pre-stored delay setting time t0 to the read job acquisition time tj is set as the scheduled delivery time th (th=tj+t0).

[0146] In step M7, the current time TN is compared with the scheduled distribution time th. When the current time TN matches the scheduled distribution time th or has passed the scheduled distribution time th (TN ≥ th), the process proceeds to step M8. However, when the current time TN has not passed the scheduled distribution time th (TN < th), that is, when the current time TN has not yet reached the scheduled distribution time th, the process remains at step M7, and the comparison between the current time TN and the scheduled distribution time th is repeated periodically.

[0147] In step M8, when the current time TN reaches the scheduled distribution time th, the update data is distributed to the slave unit MFPC. Here, using the slave unit management information 41 stored in advance in the storage unit 40, in principle, the update data is transmitted to all the managed slave units MFPC.

[0148] In step C1 of the slave unit MFPC, the update data is received and stored. In step C2, using the received update data, the update process (update) of the control program of the slave unit MFPC is executed. The update process may be automatically started immediately after receiving the update data, but it is preferable to perform the update process after confirming that the slave unit MFPC is not being operated by the user and that no arbitrary function is being executed.

[0149] As described above, when the master unit MFPP stores a print job, even if the update data is received, considering the job acquisition time tj, the time (scheduled distribution time th) for distributing the update data to the slave unit MFPC is postponed after a predetermined time (delay setting time t0) has passed since the job acquisition time tj. Thus, in the slave unit MFPC, it is possible to reduce the occurrence of a situation where the timing for executing the print job and the timing for updating the control program overlap.

[0150] <Update Process of Control Program: Embodiment 2> Here too, as in Embodiment 1, an embodiment in the case of managing the timing for distributing the update data in the master unit MFPP will be described. However, in this second embodiment, a case will be described in which, when update data has not yet been delivered to the MFPC slave, a user performs a print execution input operation for a print job in the MFPC slave, and the scheduled delivery time th is changed. Similar to the first embodiment, update data is distributed to each MFPC slave after a predetermined time has elapsed since the print job was acquired, and the MFPC slave immediately executes the update process of the control program after receiving the update data.

[0151] 8 and 9 show communication sequences of the second embodiment of the control program update process in the program update system. In the communication sequence of the second embodiment, steps that perform the same processing as steps in the communication sequence of FIG. 7 are assigned the same step numbers.

[0152] In FIG. 8, step T1 of the user terminal TE, steps S1 to S3 of the distribution server SV, and steps M1 to M6 of the master device MFPP are the same processes as those in the communication sequence of FIG. That is, after the user sends print job A input to the user terminal TE, print job A is stored in the parent device MFPP, and the parent device MFPP sends an update software inquiry request to the distribution server SV, the parent device MFPP receives the update data sent from the distribution server SV, and taking into consideration the time at which it acquired print job A (job acquisition time tja), it adds a pre-stored delay setting time t0 to the job acquisition time tja and sets the result as the scheduled distribution time th (th=tja+t0).

[0153] After step M6 of the parent device MFPP, in step M11, the user performs an operation to input print job B on the user terminal TE. In this case, the MFPP parent device stores the input print job B in its own storage unit 70. Also, the time when print job B is input is stored as job acquisition time tjb. Here, the job acquisition time tjb of print job B is later than the job acquisition time tja of print job A. However, similarly to step T1, the user may input a print job B different from print job A at the user terminal TE.

[0154] In step M12, similar to step M6, the job acquisition time tjb of print job B is used to change the scheduled delivery time th. That is, the time obtained by adding the previously stored delay setting time t0 to the job acquisition time tjb is set as the scheduled delivery time th (th=tjb+t0). As a result, new print job B is stored, and the scheduled delivery time th is postponed.

[0155] Next, after step M12 in FIG. 8, in step C11 of the MFPC2 slave device shown in FIG. 9, the user performs an input operation (print execution input operation) to start the print execution of print job B in order to print the image data included in print job B that was input to the MFPP master device. In step C12, the MFPC 2 slave device transmits a data request (print job data request) for print job B to the MFPP, since the requested print job B is not stored in the MFPC 2 slave device. The print job data request includes information about the requested print job B.

[0156] In step M21, the MFPP parent device receives a print job data request. In step M22, the information about print job B included in the print job data request is checked, and print job B is read from the storage unit . In step M23, the read print job B is sent to the MFPC 2 slave device that sent the print job data request. The sent print job B also includes image data to be printed.

[0157] In step C13, the MFPC2 slave device receives print job B including image data. In step C14, the print process for print job B is executed. That is, the image output section of the image processing section 54 prints the image data included in print job B onto a predetermined printing paper.

[0158] In step M24 of the MFPP parent device, after sending print job B, print job B stored in storage unit 70 is deleted. Alternatively, although not shown, print job B may be deleted after receiving information indicating that printing of print job B has been completed from MFPC 2 slave device. In step M25, the most recently acquired job is selected from the print jobs stored in the storage unit 70 of the MFPP parent device. At step M11 in Figure 8 described above, the last job acquired was print job B, but print job B was deleted in step M24, so print job A, which is the last job acquired from the print jobs stored in memory unit 70, is selected here.

[0159] In step M26, the job acquisition time tja of the selected print job A is read out. In step M27, similarly to step M12, the scheduled delivery time th is changed using the read job acquisition time tja. That is, the time obtained by adding the previously stored delay setting time t0 to the job acquisition time tja is set as the scheduled delivery time th (th=tja+t0). As a result, the scheduled delivery time th is updated to a time that takes into consideration the job acquisition time tja of the last acquired job among the print jobs remaining in the storage unit 70.

[0160] In step M28, the current time TN is compared with the scheduled distribution time th, as in step M7. If the current time TN matches the scheduled distribution time th or has passed the scheduled distribution time th (TN≧th), the process proceeds to step M8. However, if the current time TN has not passed the scheduled distribution time th (TN < th), that is, if the current time TN has not yet reached the scheduled distribution time th, it remains at step M28 and periodically repeats the comparison between the current time TN and the scheduled distribution time th.

[0161] In step M8, when the current time TN reaches the scheduled distribution time th, the updated data is distributed to all the slave devices (MFPC1 and MFPC2 in FIG. 9) being managed.

[0162] In step C1 of the two slave devices (MFPC1 and MFPC2) in FIG. 9, the updated data is received and stored respectively. Furthermore, in step C2 of the two slave devices (MFPC1 and MFPC2), using the received updated data, an update process (update) of the control program of the slave device MFPC is executed. The update process may be automatically started immediately after receiving the updated data, but it is preferable to perform the update process after confirming that the slave device MFPC is not being operated by the user and that no arbitrary function is being executed.

[0163] As described above, when the slave device MFPC requests a print job from the master device MFPP and the print job is executed in the slave device MFPC, if the content of the print job stored in the master device MFPP changes, among the print jobs remaining in the storage unit 70 of the master device MFPP, the scheduled distribution time th is changed at a time considering the job acquisition time tj of the last acquired job. Thus, similar to the above-described Example 1, in the slave device MFPC, it is possible to reduce the occurrence of a situation where the timing for executing the print job and the timing for updating the control program overlap.

[0164] <Update Process of Control Program: Example 3> Here, an embodiment will be described in which, when update data is stored in the MFPP master device, the update data is immediately distributed to each MFPC slave device, and the timing of updating the control program using the update data is determined in the MFPC slave device based on information acquired from the master device. When a new print job is stored in the MFPP parent device after update data is distributed from the MFPP parent device to the MFPC child device, the MFPP parent device transmits the update change time t2 to the MFPC child device, and the MFPC child device changes the scheduled update start time T using the received update change time t2.

[0165] For example, when print job acquisition unit 17 of the MFPP parent device acquires a new print job, job acquisition time setting unit 21 sets and stores a second job acquisition time tj at which the new job was acquired, update change time setting unit 23 sets update change time t2 using the second job acquisition time tj, update change time sending unit 24 sends the set update change time t2 to the MFPC child device, and scheduled update start time setting unit 59 of the MFPC child device updates the scheduled update start time T to the received update change time t2.

[0166] This allows the MFPP master device to distribute update data to the MFPC slave devices at any timing. Furthermore, in the MFPC slave device, when a new print job is stored in the MFPP master device, the timing for updating the control program is changed, and even if a print execution input operation for executing a print job is performed, it is possible to reduce the occurrence of a situation in which the timing for executing a 1:1 print job by user operation and the timing for updating the control program overlap.

[0167] 10, 11 and 12 show communication sequences of the control program update process in the program update system according to the third embodiment. Although two slave MFPCs are shown in the figure, there may be three or more slave MFPCs. In the communication sequence of the third embodiment, steps that perform the same processing as steps in the communication sequence of FIG. 7 are assigned the same step numbers. It is assumed that at least the delay setting time t0 is stored in advance in the master MFPP. It is also assumed that the two MFPC slave devices have update execution set time S stored in advance. The set update execution time S may be the same for all MFPC slave devices, or may be different for each MFPC slave device.

[0168] In FIG. 10, steps S1 to S3 of the distribution server SV, steps M3, M4, and M8 of the master device MFPP, and step C1 of the slave device MFPC are the same processes as those in the communication sequence of FIG. That is, in step M3 of FIG. 10, after the parent device MFPP sends an update software inquiry request to the distribution server SV, when the parent device MFPP receives the update data sent from the distribution server SV, it immediately sends the update data to each child device (MFPC1, MFPC2). When the slave units (MFPC1, MFPC2) receive the update data, they store the update data in the storage unit 40, but do not yet perform the update process.

[0169] In step C21, after storing the update data, the two MFPC slave devices store in storage section 40 the update acquisition time tk, which is the time at which the update data was received. In step C22, update start calculation information t1 is set. Here, the update start calculation information t1 is set using the update execution set time S and the update acquisition time tk stored in advance in the MFPC device, as described above.

[0170] In step C23, update start calculation information t1 is stored as the scheduled update start time T (T=t1). Here, the scheduled update start time T is the same as the update start calculation information t1. After that, if there is no event such as storing a print job in the MFPP parent device or executing printing processing of a print job in the MFPC child device, when the current time TN passes the scheduled update start time T, the update processing of the control program of the MFPC child device is executed using the update data.

[0171] In FIG. 10, after step C23, in step T11 of the user terminal TE, similar to step T1 in FIG. 7, the user inputs the created print job A and performs an operation to send print job A to the parent device MFPP in order to print the print job. It is assumed that print job A includes image data to be printed. This operation causes print job A to be sent from the user terminal TE to the parent device MFPP.

[0172] In step M31, the MFPP parent device acquires print job A and stores it in the storage unit 40 as print job information 43. In step M32, the time when print job A is acquired is stored as job acquisition time tja. Job acquisition time tja is stored in association with print job A.

[0173] In step M33, the update change time t2a is calculated. As described above, the update change time t2a is calculated by adding the delay setting time t0 to the job acquisition time tja (t2a=tja+t0). In step M34, the calculated update change time t2a is transmitted to each MFPC slave device. In step C24, the MFPC slave device receives the update change time t2a.

[0174] In step C25, the received update change time t2a is compared with the update start calculation information t1 set in the MFPC slave device. If the update change time t2a is later than the update start calculation information t1 (t2a>t1), the update change time t2a is stored as the scheduled update start time T (T=t2a). That is, the scheduled update start time T is changed from the update start calculation information t1 to the update change time t2a, which is a later time. On the other hand, if the update change time t2a is the same as the update start calculation information t1 or is earlier than the update start calculation information t1 (t2a≦t1), the scheduled update start time T remains as the update start calculation information t1 (T=t1). After step C25 in FIG. 10, the process proceeds to the communication sequence in FIG.

[0175] In FIG. 11, in step T12 of the user terminal TE, as in step T11, the user inputs print job B, which is different from print job A, and performs an operation to send print job B to the parent device MFPP in order to print that print job. This operation causes print job B to be sent from the user terminal TE to the parent device MFPP.

[0176] In step M35 of the MFPP parent device, print job B is acquired and stored in the storage unit 40 as print job information 43. In step M36, the time when print job B is acquired is stored as job acquisition time tjb. The job acquisition time tjb is stored in association with print job B. The job acquisition time tjb is set to be later than the above-mentioned job acquisition time tja (tjb>tja).

[0177] In step M37, the update change time t2b is calculated. As described above, the update change time t2b is calculated by adding the delay setting time t0 to the job acquisition time tjb (t2b=tjb+t0). In step M38, the calculated update change time t2b is transmitted to each MFPC slave device. In step C26, the MFPC slave device receives the update change time t2b.

[0178] In step C27, similarly to step C25, the received update change time t2b is compared with the update start calculation information t1 set in the MFPC slave device. If the update change time t2b is later than the update start calculation information t1 (t2b>t1), the update change time t2b is stored as the scheduled update start time T (T=t2b). That is, the scheduled update start time T is changed to the update change time t2a, which is later than the update change time t2a. On the other hand, if the update change time t2b is the same as the update start calculation information t1 or is earlier than the update start calculation information t1 (t2b≦t1), the scheduled update start time T remains the update start calculation information t1. However, if the update change time t2a has already been stored as the scheduled update start time T, the scheduled update start time T remains the update change time t2a (T=t2a).

[0179] Next, in step C31 of the MFPC2 slave device, similar to step C11 in FIG. 9, the user performs an input operation (print execution input operation) to start the printing execution of print job B in order to print the image data contained in print job B that was input to the MFPP master device. In step C32 of the MFPC2 slave device, as in step C12, the requested print job B is not stored in the MFPC2 slave device, so a data request for print job B (print job data request) is sent to the MFPC2 master device.

[0180] Thereafter, the parent device MFPP performs the same processing as steps M21 to M24. That is, in step M41, the MFPP parent device receives a print job data request. In step M42, the information about print job B included in the print job data request is checked, and print job B is read from the storage unit 70. In step M43, the read print job B is sent to the MFPC 2 slave device that sent the print job data request. The sent print job B also includes image data to be printed. In step M44 of the master device MFPP, after transmitting the print job B, the print job B stored in the storage unit 70 is deleted.

[0181] In step C33 of the slave device MFPC2, similar to step C13, a print job B including image data is received. In step C34, similar to step C14, the printing process of the print job B is executed.

[0182] In the master device MFPP, after step M44 of the master device MFPP, it proceeds to step M45 in FIG. 12. In step M45, among the print jobs stored in the storage unit 70 of the master device MFPP, the last acquired job is selected. At the time of step M35 in FIG. 11 described above, the last acquired job was the print job B, but since the print job B was deleted in step M44, among the print jobs stored in the storage unit 70, the print job A, which is the last acquired job, is selected.

[0183] In step M46, the job acquisition time tja of the selected print job A is read out. In step M47, the update change time t2a is calculated again from the job acquisition time tja. The update change time t2a is calculated by adding the delay setting time t0 to the job acquisition time tja (t2a = tja + t0).

[0184] In step M48, the current time TN is compared with the update change time t2a. If the current time TN has not passed the update change time t2a (TN < t2a), it proceeds to step M49. However, if the current time TN is the same as the update change time t2a or has passed the update change time t2a (TN ≧ t2a), the process of step M49 is not performed. In step M49, similar to step M34, the calculated update change time t2a is transmitted to each slave device MFPC. In step C41 of each slave unit MFPC, the update change time t2a is received.

[0185] In step C42, the received update change time t2a is compared with the update start calculation information t1 set in the slave unit MFPC. When the update change time t2a is a time later than the update start calculation information t1 (t2a > t1), the update start scheduled time T is changed to the update change time t2a (T = t2a). On the other hand, when the update change time t2a is the same as or earlier than the update start calculation information t1 (t2a ≤ t1), the update start scheduled time T is not changed.

[0186] In step C43, the current time TN is compared with the update start scheduled time T. When the current time TN is the same as the update start scheduled time T or has passed the update start scheduled time T (TN ≥ T), proceed to step C2. When the current time TN has not passed the update start scheduled time T (TN < T), step C43 is periodically repeated and waits for the current time TN to reach the update start scheduled time T.

[0187] In step C2 of each slave unit (MFPC1, MFPC2), using the update data that has already been received, the update process (update) of the control program of the slave unit MFPC is executed. The update process may automatically start immediately after receiving the update data, but it is preferable to perform the update process after confirming that no arbitrary function of the slave unit MFPC is being executed.

[0188] As described above, when update data is stored in the MFPP parent device, the update data is immediately transmitted to each MFPC child device. However, each time a print job is stored in the MFPP parent device, the update change time t2 calculated using the job acquisition time tj of that print job is transmitted to each MFPC child device, and the scheduled update start time T is postponed to a time that takes into account the job acquisition time tj. As a result, similar to the above-described embodiment, it is possible to reduce the occurrence of a situation in which the timing of executing a print job and the timing of updating the control program overlap in the MFPC child devices.

[0189] Furthermore, even when the MFPC slave requests a print job from the MFPP master and the print job is printed in the MFPC slave, if a change occurs in the content of the print job stored in the MFPP master, the scheduled update start time T is changed to a time that takes into account the job acquisition time tj of the most recently acquired job among the print jobs remaining in storage unit 70 of the MFPP master, and similarly, it is possible to reduce the occurrence of a situation in which the timing of updating the control program in the MFPC slave is delayed more than necessary.

[0190] <Control program update process: Example 4> Here, an embodiment will be described in which the MFPC slave device manages the timing of requests to the MFPP master device to acquire update data, and the MFPP master device, upon receiving the request to acquire update data, determines whether or not to distribute the update data depending on the reception status of the print job. For example, when new update data is stored in the MFPP master device, the MFPP master device does not automatically distribute the update data to each MFPC slave device, but when an update data acquisition request is received from an MFPC slave device, the MFPP master device transmits the stored update data to the MFPC slave device that has transmitted the acquisition request.

[0191] However, if a print job is stored in the MFPP parent device, the scheduled delivery time is set taking into consideration the time when the print job was stored (job acquisition time), and if the current time has passed the scheduled delivery time, the update data is sent to the MFPC child device, but if the current time has not passed the scheduled delivery time, the update data is not sent to the MFPC child device. That is, if a predetermined time has not yet elapsed since the time when the print job was stored (job acquisition time), there is a high possibility that the user will operate the MFPC slave to execute the print job, so even if an update data acquisition request is received from the MFPC slave, update data is not transmitted to the MFPC slave. Furthermore, if update data is not to be transmitted to the MFPC slave device, the transmission timing of the update data acquisition request transmitted from the MFPC slave device to the MFPP master device is reset.

[0192] As a result, the MFPP parent device manages the timing at which update data can be distributed, so the MFPC child device does not need to check the existence of print jobs stored in the MFPP parent device, and can request distribution of update data at any timing. Furthermore, when a new print job is stored in the MFPP parent device, the timing of delivery of update data is reset in the MFPP parent device taking into consideration the time when the print job was acquired, thereby reducing the occurrence of a situation in which the timing when the user attempts to perform a print execution input operation on the MFPC child device overlaps with the timing when the control program is updated.

[0193] 13 to 16 show a communication sequence of the control program update process in the program update system according to the fourth embodiment. Although two slave MFPCs are shown in the figure, there may be three or more slave MFPCs. In the communication sequence of the fourth embodiment, steps that perform the same processing as steps in the communication sequence of FIG. 7 are assigned the same step numbers. It is assumed that at least the delay setting time t0 is stored in advance in the master MFPP. Furthermore, in the first embodiment of FIG. 2 and FIG. 7, the scheduled delivery time is written as "th", but in this embodiment, the scheduled delivery time is written as "th2". For example, the scheduled delivery time set for print job A is written as "th2a."

[0194] It is also assumed that the two MFPC slave devices have stored in advance the update execution set time S, the initial values ​​of the scheduled update start time T, and restart interval information tR. The set update execution time S, the initial values ​​of the scheduled update start time T, and the restart interval information tR may be the same for all MFPC slave devices, or may be different for each MFPC slave device. Here, the initial value of the scheduled update start time T may be the current time TN at the time of startup of the MFPC device, or may be calculated from the update execution set time S and the current time TN. For example, if the set update execution time S is 03:00 and the current time TN at startup is 16:00 on September 24, 2021, the initial value of the scheduled update start time T is set to 3:00 on September 25, 2021.

[0195] The communication sequence in FIG. 13 shows an example of update processing when the current time TN at which the MFPP parent device receives an update data acquisition request from the MFPC child device has passed the scheduled delivery time th2 that is set taking into account the time at which the print job is stored (job acquisition time tj). On the other hand, the communication sequences in FIGS. 14, 15, and 16 show update processing in embodiments including a case where the current time TN at which the MFPP parent device receives an update data acquisition request from the MFPC child device has not yet passed the scheduled delivery time th2 that is set taking into account the time at which the print job was stored (job acquisition time tj).

[0196] (Explanation of the communication sequence in Figure 13) In FIG. 13, steps S1 to S3 of the distribution server SV and steps M3 and M4 of the parent device MFPP are the same processes as those in the communication sequence of FIG. That is, in step M3 of FIG. 13, the parent device MFPP sends an update software inquiry request to the distribution server SV, and then in step S3 the distribution server SV sends the update data, and in step M4 the parent device MFPP receives and stores the update data sent from the distribution server SV. At the time when the update data is received, the update data is not yet transmitted to the slave units (MFPC1, MFPC2).

[0197] In step T21 of the user terminal TE in FIG. 13, as in step T1 in FIG. 7, the user inputs the created print job A and performs an operation to send print job A to the parent device MFPP in order to print the print job. It is assumed that print job A includes image data to be printed. This operation causes print job A to be sent from the user terminal TE to the parent device MFPP.

[0198] In step M51, the MFPP parent device acquires print job A and stores it in the storage unit 40 as print job information 43. In step M52, the time when print job A is acquired is stored as job acquisition time tja. Job acquisition time tja is stored in association with print job A. In step M53, the scheduled distribution time th2a is calculated. The scheduled delivery time th2a is set by adding the delay setting time t0 to the job acquisition time tja (th2a=tja+t0).

[0199] In step C51, if the current time TN has passed the preset scheduled update start time T (TN≧T), the MFPC1 slave device transmits an update data acquisition request to the MFPP master device. In step M54, the MFPP master device receives the update data acquisition request.

[0200] The parent device MFPP compares the current time TN with the scheduled distribution time th2a. If the current time TN has passed the scheduled distribution time th2a (TN≧th2a), the process proceeds to step M55. If the current time TN coincides with the scheduled distribution time th2a, the process also proceeds to step M55. Hereinafter, when the scheduled distribution time th2 has passed, this also includes the case where the current time TN coincides with the scheduled distribution time th2. If the current time TN has passed the scheduled delivery time th2a, the delay setting time t0 has already passed since the time print job A was acquired (job acquisition time tja), so it is determined that the update data can be delivered.

[0201] On the other hand, if the current time TN has not passed the scheduled distribution time th2a, in order to avoid overlapping between the timing of updating the control program and the timing of executing the print job, the update data is not distributed, and acquisition response information (retry response) is sent to the MFPC1 slave device as shown in the communication sequence of Fig. 14, which will be described later. This case will be described in the communication sequence of Fig. 14, which will be described later.

[0202] In step M55, the MFPPC master device generates acquisition response information (update possible response) as a response to the update data acquisition request, and transmits it to the MFPC1 slave device. In step C52, the MFPC1 slave device receives the acquisition response information (update possible response). The update data itself may be included in the acquisition response information (update possible response) sent from the MFPPC master device to the MFPC1 slave device. If the update data is included in the acquisition response information (update possible response), the following step M8 can be omitted.

[0203] Thereafter, as in FIG. 7, step M8 of the master device MFPP and steps C1 and C2 of the slave device MFPC1 are executed. In step M8, the update data is distributed to the MFPC 1 slave device that has sent the update data acquisition request.

[0204] In step C1, MFPC1 receives and stores the update data. In step C2, the received update data is used to perform update processing of the control program of MFPC1. The update process may be started automatically immediately after receiving the update data, but it is preferable to start the update process after confirming that no functions of the MFPC slave device are being executed.

[0205] Unlike in FIG. 13, if the MFPP parent device receives an update data acquisition request when no new update data is stored in the MFPP parent device, there is no new update data, so in step M55 the MFPPC parent device generates acquisition response information (no update data) as a response to the update data acquisition request and transmits it to the MFPC1 child device. In this case, the MFPC1 slave device that has received the message "no update data" may set the scheduled update start time T to, for example, the update execution set time S of the next day, and then, when the postponed scheduled update start time T arrives, may resend the update data acquisition request.

[0206] As described above, in this embodiment, regardless of whether the MFPP parent device has stored a print job, when a predetermined time (scheduled update start time T) has passed in the MFPC child device, the MFPC child device sends an update data acquisition request to the MFPP parent device. Furthermore, if the MFPP parent device has stored a print job and receives an update data acquisition request from the MFPC child device, and the current time TN has passed the scheduled distribution time th2a, the MFPP parent device distributes the update data to the MFPC child device, since it is unlikely that the processing of the print job will be kept waiting even if the update data is distributed to the MFPC child device.

[0207] (Explanation of communication sequences in Figures 14 to 16) In FIG. 14, the processes from step S1 to S3 of the distribution server SV, steps M3 and M4 of the master machine MFPP, step T21 of the user terminal TE, and steps M51 to M53 of the master machine MFPP are the same as the communication sequence in FIG. 13. That is, in FIG. 14, after the master machine MFPP sends an update software inquiry request to the distribution server SV, the distribution server SV sends update data, and the master machine MFPP receives and stores the update data sent from the distribution server SV. Thereafter, in step T21 of the user terminal TE, when the user inputs the created print job A and performs an operation to send the print job A to the master machine MFPP in order to print the print job, the print job A is sent from the user terminal TE to the master machine MFPP. In the master machine MFPP, the print job A is acquired, and the time when the print job A is acquired is stored as the job acquisition time tja, and the scheduled distribution time th2a is set (th2a = tja + t0).

[0208] In step C61 of the slave machine MFPC1 in FIG. 14, similar to step C51 in FIG. 13, when the current time TN has passed the preset scheduled update start time T (TN≧T), an update data acquisition request is sent to the master machine MFPP. In step M54 of the master machine MFPP, an update data acquisition request is received.

[0209] In the master machine MFPP, the current time TN and the scheduled distribution time th2a are compared. When the current time TN has not passed the scheduled distribution time th2a (TN<th2a), it proceeds to step M56.

[0210] In step M56 of the master machine MFPP, as a response to the update data acquisition request, acquisition response information (retry response) is generated and sent to the slave machine MFPC1. In step C62 of the slave machine MFPC1, the acquisition response information (retry response) is received. If a retry response is received, the update data has not yet been transmitted from the parent device MFPP, so the scheduled update start time T is postponed and the time to resend the update data acquisition request is reset. Here, the time when the scheduled update start time T is postponed is set as the time when the update data acquisition request is resent. In step C63, the scheduled update start time T is reset (postponed). For example, the time obtained by adding the restart interval information tR to the current time TN when the retry response is received is set as the scheduled update start time T (T=TN+tR). After this, the communication sequence shown in FIG. 15 is carried out.

[0211] In step T22 of the user terminal TE in FIG. 15, as in step T21 in FIGS. 13 and 14, the user inputs the created print job B and performs an operation to send print job B to the parent device MFPP in order to print the print job. It is assumed that print job B includes image data to be printed that is different from that of print job A input in step T21. This operation causes print job B to be sent from the user terminal TE to the parent device MFPP.

[0212] Steps M61, M62, and M63 of the parent device MFPP are the same processes as steps M51, M52, and M53 shown in FIG. In step M61, the MFPP parent device acquires print job B and stores it in the storage unit 40 as print job information 43. In step M62, the time when print job B is acquired is stored as job acquisition time tjb. Job acquisition time tjb is stored in association with print job B. In step M63, the scheduled distribution time th2b is set. The scheduled delivery time th2b is set by adding the delay setting time t0 to the job acquisition time tjb (th2b=tjb+t0).

[0213] In step C71 of the slave device MFPC1, when the current time TN has passed the preset scheduled update start time T (TN ≥ T), a request for obtaining update data is transmitted to the master device MFPP. In step M64 of the master device MFPP, a request for obtaining update data is received.

[0214] In the master device MFPP, the current time TN is compared with the scheduled distribution time th2b. If the current time TN has not passed the scheduled distribution time th2b (TN < th2b), the process proceeds to step M65.

[0215] In step M65 of the master device MFPP, in the same manner as step M56 described above, acquisition response information (retry response) is generated as a response to the request for obtaining update data and transmitted to the slave device MFPC1. In step C72 of the slave device MFPC1, acquisition response information (retry response) is received. When the retry response is received, since the update data has not yet been transmitted from the master device MFPP, the scheduled update start time T is postponed and the time for retransmitting the request for obtaining update data is reset. In step C73, in the same manner as step C63 described above, the scheduled update start time T is reset (postponed). For example, the time obtained by adding the restart interval information tR to the current time TN at which the retry response is received is set as the scheduled update start time T (T = TN + tR). Thereafter, the process proceeds to the communication sequence in FIG. 16.

[0216] In the communication sequence in FIG. 16, the processing from steps C31 to C34 of the slave device MFPC2 is the same as the processing shown in FIG. 9, and the processing from steps M41 to M47 of the master device MFPP is the same as the processing shown in FIGS. 11 and 12.

[0217] That is, in step C31 of the MFPC2 slave device in FIG. 16, similar to step C11 in FIG. 9, the user performs an input operation (print execution input operation) to start the printing execution of print job B in order to print the image data contained in print job B that was input to the MFPP master device. In step C32, the MFPC2 slave device transmits a data request for print job B (print job data request) to the MFPC2 master device, since the requested print job B is not stored in the MFPC2 slave device.

[0218] In step M41, the MFPP parent device receives a print job data request. In step M42, the information about print job B included in the print job data request is checked, and print job B is read from the storage unit 70. In step M43, the read print job B is sent to the MFPC 2 slave device that sent the print job data request. The sent print job B also includes image data to be printed. In step M44 of the MFPP parent device, after sending print job B, print job B stored in the storage unit 70 is deleted.

[0219] In step C33, the MFPC2 slave device receives print job B including image data. In step C34, the print process for print job B is executed.

[0220] In step M45 of the MFPP parent device, the most recently acquired job is selected from the print jobs stored in the storage unit 70 of the MFPP parent device. At step M61 in Figure 15 described above, the last job acquired was print job B, but print job B was deleted in step M44, so print job A, which was the last job acquired, is selected from the print jobs stored in memory unit 70.

[0221] In step M46, the job acquisition time tja of the selected print job A is read out. In step M47, the scheduled delivery time th2a is calculated again from the job acquisition time tja. The scheduled delivery time th2a is set by adding the delay setting time t0 to the job acquisition time tja (th2a=tja+t0).

[0222] Thereafter, the same processes as steps C51, C52, C1, and C2 of the MFPC1 handset and steps M54, M55, and M8 of the MFPP handset shown in FIG. 13 are performed.

[0223] In step C51, if the current time TN has passed the preset scheduled update start time T (TN≧T), the MFPC1 slave device transmits an update data acquisition request to the MFPP master device. In step M54, the MFPP master device receives the update data acquisition request.

[0224] The parent device MFPP compares the current time TN with the scheduled distribution time th2a. If the current time TN has passed the scheduled distribution time th2a (TN≧th2a), the process proceeds to step M55. If the current time TN passes the scheduled delivery time th2a, the delay setting time t0 has already passed since the time print job A was acquired (job acquisition time tja), so it is determined that it is now OK to distribute the update data.

[0225] In step M55, the MFPP master device generates acquisition response information (update possible response) as a response to the update data acquisition request, and transmits it to the MFPC1 slave device. In step C52, the MFPC1 slave device receives the acquisition response information (update possible response). The update data itself may be included in the acquisition response information (update possible response) sent from the MFPPC master device to the MFPC1 slave device.

[0226] Thereafter, in step M8, the master MFPPC distributes the update data to the slave MFPC1 that has sent the update data acquisition request.

[0227] In step C1, MFPC1 receives and stores the update data. In step C2, the received update data is used to perform update processing of the control program of MFPC1. The update process may be started automatically immediately after receiving the update data, but it is preferable to start the update process after confirming that no functions of the MFPC slave device are being executed.

[0228] As described above, in the embodiments of FIGS. 14 to 16, regardless of whether the MFPP parent device has stored a print job, when a predetermined time (scheduled update start time T) has passed in the MFPC child device, the MFPC child device sends an update data acquisition request to the MFPP parent device. Furthermore, when the MFPP parent device has a print job stored therein when it receives an update data acquisition request from the MFPC child device, and the current time TN has not yet passed the scheduled distribution time th2, it is determined that there is a high possibility that the print job will be processed, and the update data is not distributed immediately, thereby reducing the occurrence of a situation in which the timing for executing a print job and the timing for updating the control program overlap in the MFPC child device. [Explanation of symbols]

[0229] 1. Image forming device (parent machine), 2. Image forming device (child machine), 3. Distribution device (distribution server), 4. Information processing terminal (user terminal), 10 networks, 11 control section, 12 Operation section, 13 Display section, 14 Image processing unit, 15 Communications Department, 16 Update data acquisition unit, 17 print job acquisition unit, 21 Job acquisition time setting unit, 22 Update data distribution department, 23 update change time setting unit, 24 Update change time sending unit, 25 Print job sending unit, 26 Control program update unit, 27 Update acquisition request receiving unit, 28 Program distribution determination unit, 29 Acquisition request response part, 30 Function execution unit, 40 storage section, 41 Handset management information, 42 update data, 43 Print job information, 44 Job acquisition time, 45 delay setting time, 46 Update change time, 47 Scheduled Delivery Time, 48 Obtain response information, 51 control section, 52 Operation section, 53 Display section, 54 Image processing unit, 55 Communications Department, 56 update data receiving unit, 57 Function execution unit, 58 Update acquisition time recording unit, 59 Update start scheduled time setting unit, 60 Printing request reception unit, 61 print job acquisition request unit, 62 print job acquisition unit, 63 update change time receiving unit, 64 Update postponement setting section, 65 Program update execution unit, 66 update data acquisition request unit, 67 Acquisition response receiving unit, 68 Update Start Change Section, 70 storage section, 71 Parent unit information, 72 update data, 73 Print job information, 74 Update execution setting time, 75 Update acquisition time, 76 Update start calculation information, 77 Update change time, 78 Scheduled start time of update, 79 Resume interval information, 80 Get response information, 101 control section, 102 Operation section, 103 Display section, 104 Communications Department, 105 update data transmission unit, 110 storage section, 111 parent unit information, 112 Update Data

Claims

1. A program update system comprising a plurality of information processing devices connected via a network, the plurality of information processing devices each including at least one parent device and at least one child device; The information processing device that is the parent device a job data acquisition unit that acquires job data including data to be processed in the child information processing device; a job data management storage unit that manages and stores the acquired job data; a job data transmission unit that transmits job data read from the job data management storage unit to the slave device via a network in response to a request from the slave device; an update data acquisition unit that acquires update data for updating a control program that controls the operation of the information processing device; an update data storage unit that stores the acquired update data; an update data distribution unit that distributes the update data read from the update data storage unit to the slave device via the network; a function execution unit that processes the job data read from the job data management storage unit to realize functions of the information processing device in the same way as the slave device; Equipped with The information processing device that is the slave device a job data request unit that requests the parent machine to transmit the job data via a network; a job data receiving unit that receives the job data transmitted from the parent machine; a function execution unit that processes the received job data to realize functions of the information processing device; a program storage unit that stores a control program for controlling its own operation; an update data receiving unit that receives the update data from the parent device via a network; a program update execution unit that updates the control program stored in the program storage unit using the received update data; Equipped with A program update system characterized in that at least one of the timing at which the parent device distributes update data and the timing at which the child device updates the control program is determined according to the job data stored in the job data management memory unit.

2. The parent device: a scheduled delivery time determination unit that determines a scheduled delivery time of the update data based on the time when the job data is acquired and stored in the job data management storage unit; a storage unit that stores the scheduled distribution time; Furthermore, 2. The program update system according to claim 1, wherein the update data distribution unit distributes the update data at a timing based on the scheduled distribution time.

3. The parent device: A setting storage unit for storing a delay time setting that is a setting for providing a period during which update data is not transmitted after job data is received. Furthermore, 3. The program update system according to claim 2, wherein the scheduled delivery time determination unit determines the scheduled delivery time using the time when the job data stored in the job data management storage unit was last acquired and the delay time setting stored in advance.

4. In the base unit, A program update system as described in claim 2 or 3, characterized in that if the job data acquisition unit acquires new job data after the scheduled delivery time has been stored in the memory unit, the scheduled delivery time determination unit changes the scheduled delivery time based on the time at which the new job data was acquired.

5. In the base unit, When the job data acquisition unit acquires at least one or more pieces of job data, a job acquisition time, which is a time when each piece of job data was acquired, is stored in the job data management storage unit in association with the job data; After the storage unit stores the scheduled delivery time, if the job data read from the job data management storage unit in response to a request from the slave device is transmitted to the slave device via the network by a job data transmission unit, A program update system as described in any one of claims 2 to 4, characterized in that the scheduled delivery time determination unit changes the scheduled delivery time using the job acquisition time of job data other than the job data stored in the job data management storage unit.

6. The slave unit, an update data storage unit that stores the received update data; an update start scheduled time setting unit that sets an update start scheduled time, which is a time to start updating the control program, based on the time when the update data is received; a storage unit that stores the scheduled update start time; Equipped with The parent machine changes the scheduled update start time in response to new job data being stored in the job data management storage unit; and 2. The program update system according to claim 1, wherein the program update execution unit updates the control program at a timing based on the scheduled update start time.

7. The slave unit, a setting storage unit for storing an update start time setting, which is a setting relating to the time when an update of the control program of the slave unit is to be started; Furthermore, 7. The program update system according to claim 6, wherein the scheduled update start time setting unit uses the update start time setting stored in advance when setting the scheduled update start time.

8. The parent device: an update control information transmitting unit that transmits, to the slave unit, update control information that is information for determining a scheduled time for the slave unit to execute an update process of a control program when the job data acquiring unit acquires a job and when the job data is transmitted to the slave unit via a network; Furthermore, When the job data acquisition unit acquires a new job, the update control information transmission unit transmits the update control information to the slave device; 8. The program update system according to claim 6, wherein the scheduled update start time setting unit of the slave device updates the scheduled update start time based on received update control information.

9. The parent device: an update acquisition request receiving unit that receives an update data acquisition request transmitted from a slave device; a distribution possibility determination unit that, when receiving the update data acquisition request from the slave device, determines whether or not the update data distribution unit is able to distribute the update data in accordance with the job data stored in the job data management storage unit; Furthermore, The slave unit, an update data acquisition request unit that transmits an update data acquisition request, which is a request for acquiring update data, to the parent device; 2. The program update system according to claim 1, further comprising:

10. The slave unit, a setting storage unit for storing an update request time setting, which is a setting relating to the time when the update data acquisition request is to be sent to the parent device; Furthermore, 10. The program update system according to claim 9, wherein the update data acquisition request unit transmits the update data acquisition request at a timing based on the update request time setting.

11. 11. The program update system according to claim 1, wherein the information processing device is an image forming device.

12. An information processing device, a job data acquisition unit that acquires job data including data to be processed in the information processing device; a job data management storage unit that manages and stores the acquired job data; a job data transmitting unit that transmits job data read from the job data management storage unit in response to a request from a second information processing apparatus via a network to the second information processing apparatus; an update data acquisition unit that acquires update data for updating a control program that controls the operation of the information processing device; a function execution unit that processes the job data read from the job data management storage unit to realize functions of the information processing device; an update data storage unit that stores the acquired update data; an update data distribution unit that distributes the update data read from the update data storage unit to the second information processing device via a network; Equipped with an information processing apparatus that determines the timing or possibility of delivering the update data in accordance with the job data stored in the job data management storage unit;

13. 1. A program update method for an information processing device that updates a control program for executing a predetermined function using update data, comprising: the information processing device comprises a parent device that receives the update data transmitted from a distribution device, and one or more child devices that use the update data distributed from the parent device to update a control program that causes the information processing device to execute its own function, The program update method for the information processing device includes: A control unit provided in the parent device a storage step of storing a scheduled distribution time, which is a scheduled time at which the update data is distributed to the slave device; an update data acquisition step of acquiring update data for updating the control program; a job acquisition step of acquiring a job including data to be processed by the information processing device; a job acquisition time storage step for setting and storing a job acquisition time, which is the time when the job is acquired; and an update data distribution step of distributing the acquired update data to the child device after the scheduled distribution time has passed. A control unit provided in the slave unit, an update data receiving step of receiving update data distributed from the parent device; and a program update execution step of updating the control program using the received update data, When one or more jobs are acquired in the job acquisition step, In the job acquisition time storage step, a job acquisition time is set and stored for each acquired job; In the update data distribution step, setting the scheduled delivery time using the job acquisition time of the most recently acquired job among the set and stored job acquisition times; A program update method for an information processing device, comprising the steps of: distributing the update data to the slave device when the current time has passed the scheduled distribution time that has been set.

Images