Data update method, data update program, information processing device, relay device, and data update system

Abstract

To appropriately update data.SOLUTION: When a part is added to or changed in a main body of an information processing device, the information processing device changes data set reception information to a content indicating the state of needing reception of the data set and transmits it. When a relay device receives the data set reception information from the information processing device, it transmits a data set corresponding to a predetermined version among data sets stored in a server, to the information processing device. The information processing device updates both main body data stored in the main body and part data stored in the part, by using the received data set; and then, changes the data set reception information to a content indicating the state of not needing to receive the data set, and deletes the data set.SELECTED DRAWING: Figure 5

Description

[Technical field]

[0001] The present invention relates to a data updating method, a data updating program, an information processing device, a relay device, and a data updating system. [Background technology]

[0002] In an information processing device having data such as firmware, update data for updating the data is downloaded from a server via a network, for example, and the update data is used to update the information processing device's own data (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2020-123775 A Summary of the Invention [Problem to be solved by the invention]

[0004] Incidentally, some information processing devices include a main body and replaceable parts, and each of the main body and parts has data such as firmware, etc. In such information processing devices, for example, a data set that combines update data for updating data on the main body and update data for updating data on the parts is automatically downloaded from a server, and the data set is used to update the main body data and the data on the parts.

[0005] However, in such information processing devices, even if the main body data and part data are updated using the latest version of the data set, if the part is subsequently replaced, the old version of the data may still be used for that part, making it difficult to properly update the data.

[0006] The present invention has been made in consideration of the above points, and aims to propose a data updating method, a data updating program, an information processing device, and a data updating system that are capable of updating data appropriately. [Means for solving the problem]

[0007] The data updating method of the present invention is a data updating method for an information processing device in which a removable part can be added or changed outside or inside a main body, and when the part is added or changed to the main body of the information processing device, the information processing device transmits dataset reception information used to receive a dataset with content indicating a state in which reception of the dataset is necessary, and when a relay device receives the dataset reception information transmitted from the information processing device due to the part being added or changed, the relay device transmits to the information processing device a dataset corresponding to a predetermined version used in data update of the main body and data update of the removable part from the dataset stored in a server, and the information processing device uses the received dataset to update the main body data stored in the main body and the part data stored in the part, and after the information processing device updates the main body data and the part data using the received dataset, the dataset reception information used to receive the dataset with content indicating a state in which reception of the dataset is not necessary.

[0008] Furthermore, a data updating method of the present invention is a data updating method for an information processing device capable of adding or changing removable parts outside or inside a main body, the information processing device stores update data version information indicating the version numbers of the data of the main body and the version numbers of the data of the parts contained in a data set used to update the data of the main body and the data of the parts, and operating data version information indicating the version numbers of the data operating in the main body and the version numbers of the data operating in the parts, the information processing device updates the operating data version information in response to the addition or change of the parts, the information processing device compares the stored update data version information with the operating data version information, and if the update data version information and the operating data version information differ, receives the data set provided from a server via a relay device, and the information processing device performs updating of the data of the main body and the data of the parts using the received data set.

[0009] Furthermore, the data updating program of the present invention is provided with the following functions for an information processing device capable of adding or changing a removable part outside or inside the main body, when the part is added or changed: a function of changing dataset receiving information used to receive the dataset to a relay device that relays between the information processing device and a server, the function of receiving a dataset corresponding to a predetermined version used in updating the data of the main body and updating the data of the removable part from a dataset stored in the server and transmitted from the relay device; a function of updating the data of the main body and the data of the part using the received dataset; and a function of changing the dataset receiving information used to receive the dataset to a state indicating a state in which reception of the dataset is not required after updating the data of the main body and the data of the part using the received dataset.

[0010] Furthermore, the data updating program of the present invention is configured to provide an information processing device capable of adding or changing removable parts outside or inside the main body, and a computer capable of communicating with a server that stores a dataset, with the following functions: receiving dataset reception information transmitted from the information processing device as a result of the part being added or changed, which the information processing device uses to receive the dataset; and, upon receiving the dataset reception information from the information processing device, transmitting to the information processing device a dataset corresponding to a predetermined version used in updating the data of the main body and updating the data of the removable parts from the dataset stored in the server.

[0011] Furthermore, the information processing device of the present invention is an information processing device in which a removable part can be added or changed outside or inside the main body, and is equipped with a transmitting unit that, when the part is added or changed, changes dataset reception information used to receive the dataset to a relay device that relays between the information processing device and a server, indicating a state in which reception of the dataset is necessary, and transmits the changed information to the relay device that relays between the information processing device and a server; a receiving unit that receives a dataset corresponding to a predetermined version used to update the data of the main body and the data of the removable part from the dataset stored in the server transmitted from the relay device; and an updating unit that uses the received dataset to update the main body data stored in the main body and the part data stored in the part, and then changes the dataset reception information used to receive the dataset to a state in which reception of the dataset is unnecessary.

[0012] Furthermore, the relay device of the present invention is a relay device that relays between an information processing device that can add or change removable parts outside or inside the main body and a server that stores a dataset, and is equipped with a receiving unit that receives dataset reception information that is transmitted from the information processing device as a result of the part being added or changed and that the information processing device uses to receive the dataset, and a transmitting unit that, upon receiving the dataset reception information from the information processing device, transmits a dataset corresponding to a predetermined version used in updating the data of the main body and updating the data of the removable parts from the dataset stored in the server to the information processing device.

[0013] Furthermore, the data updating system of the present invention includes an information processing device capable of adding or changing a removable part outside or inside the main body, a server that stores a dataset, and a relay device that relays between the information processing device and the server, and when the part is added or changed, the information processing device transmits dataset receiving information used to receive the dataset with content indicating a state in which reception of the dataset is necessary, and when the relay device receives the dataset receiving information transmitted from the information processing device due to the addition or change of the part, it transmits to the information processing device a dataset from the dataset stored in the server that corresponds to a predetermined version used in data update of the main body and data update of the removable part, and the information processing device uses the received dataset to update the main body data stored in the main body and the part data stored in the part, and then changes the dataset receiving information used to receive the dataset with content indicating a state in which reception of the dataset is not necessary.

[0014] In this way, when a part is added or changed to an information processing device, the information processing device receives a data set and updates the data for the main body and the part, thereby avoiding a situation in which the added or changed part is used with an old version of data. Effect of the Invention

[0015] According to the present invention, it is possible to realize a data updating method, a data updating program, an information processing device, a relay device, and a data updating system that are capable of updating data appropriately. [Brief description of the drawings]

[0016] [Figure 1] 1 is a block diagram showing a configuration of a data updating system according to a first embodiment. [Diagram 2] FIG. 11 is a diagram illustrating an example (1) of active FW version information according to the first embodiment. [Diagram 3] FIG. 11 is a diagram illustrating an example (2) of active FW version information according to the first embodiment. [Figure 4] FIG. 11 is a diagram illustrating an example of the latest FW version information according to the first embodiment. [Diagram 5] 4 is a flowchart showing an operation procedure of the data updating system according to the first embodiment. [Figure 6] FIG. 11 is a diagram illustrating an example of active FW version information to which change notification information has been added according to the second embodiment. [Figure 7] 10 is a flowchart showing an operation procedure when updating FW of a printer according to a second embodiment. [Figure 8] 13 is a flowchart showing an operation procedure when updating active FW version information on the printer side according to the second embodiment. [Figure 9] FIG. 13 is a diagram illustrating the extraction of the FWSuite version from active FW version information according to the third embodiment. [Figure 10] 13 is a flowchart showing an operation procedure when updating FW of a printer according to a third embodiment. [Figure 11] 13 is a flowchart showing an operation procedure when the version number of FWSuite is spoofed on the printer side according to the third embodiment. [Figure 12] FIG. 23 is a diagram illustrating the extraction of the smallest version number from active FW version information according to the fourth embodiment. [Figure 13]13 is a flowchart showing an operation procedure when updating FW of a printer according to a fourth embodiment. [Figure 14] 13 is a flowchart showing an operation procedure when checking the major version of each FW on the printer side according to the fourth embodiment. [Figure 15] FIG. 13 is a block diagram showing a configuration of a data updating system according to a fifth embodiment. [Figure 16] FIG. 13 is a diagram illustrating a configuration of an FWSuite according to a fifth embodiment. [Figure 17] 13 is a flowchart showing an operation procedure when updating FW of a printer according to a fifth embodiment. [Figure 18] 20 is a flowchart showing an operation procedure when updating FW of a printer according to the sixth embodiment. [Figure 19] 23 is a flowchart showing an operation procedure when updating FW of a printer according to the seventh embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0017] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, modes for carrying out the invention (hereinafter referred to as embodiments) will be described in detail with reference to the drawings.

[0018] 1. First embodiment [1-1. Data update system configuration] 1 shows the configuration of a data updating system 1 according to the first embodiment. This data updating system 1 is composed of a server 100, a PC (personal computer) 200, and a printer 300. The server 100 and the PC 200 are connected to a network Nt1 such as the Internet, and are capable of communicating with each other via the network Nt1. The PC 200 and the printer 300 are also connected to a network Nt2 such as a LAN (Local Area Network), and are capable of communicating with each other via the network Nt2.

[0019] In this data updating system 1, the latest version of firmware (hereinafter abbreviated as FW) for the printer 300 is provided from the server 100 via the PC 200 to the printer 300, and the printer 300 updates its own FW to the latest version.

[0020] The server 100 is a device that provides the latest version of the FW for the printer 300, and includes a control unit 101, a transmission / reception unit 102, and a storage unit 103. The transmission / reception unit 102 communicates with the PC 200 via the network Nt1. The storage unit 103 stores the latest version of the FW for the printer 300. The control unit 101 controls each unit to execute various processes.

[0021] The printer 300 includes a main body 300M and a part 300P (e.g., a fixing unit 300P1, an optional tray 300P2, etc.) that can be attached or detached to the outside or inside of the main body 300M, and the hardware included in each of the main body 300M and the part 300P is operated by an individual FW. In other words, the printer 300 is operated by a plurality of FWs. For this reason, the server 100 stores in the storage unit 103 a latest version of a data set (hereinafter, referred to as FWSuite) that combines the latest versions of a plurality of FWs for operating the printer 300 into one, and transmits the latest version of the FWSuite to the PC 200. The storage unit 103 of the server 100 may also store FWSuites other than the latest version, so that the server 100 can provide FWSuites other than the latest version (i.e., older versions) as necessary.

[0022] The PC 200 is a device that relays between the server 100 and the printer 300, and has a typical computer configuration including a CPU, ROM, RAM, storage, a network I / F, etc. The PC 200 has an application 201, which is a program that monitors the printer 300, installed in the storage.

[0023] The application 201 functions as a control unit 202, a transmission / reception unit 203, a storage unit 204, and a FW configuration information analysis unit 205. The transmission / reception unit 203 communicates with the server 100 via a network Nt1, and also communicates with the printer 300 via a network Nt2. The storage unit 204 stores information acquired through communication. The FW configuration information analysis unit 205 analyzes the latest version of the FWSuite acquired from the server 100, and extracts the version number (version) of the FWSuite and the version numbers (versions) of each of the multiple FWs included in the FWSuite. The versions extracted from the FWSuite in this way are stored in the storage unit 204 as latest FW version information. The control unit 202 controls each unit to execute various processes.

[0024] Furthermore, PC 200 periodically communicates with server 100, and when the FWSuite provided by server 100 has been updated, PC 200 updates the latest FW version information stored in memory unit 204 by obtaining the latest version of FWSuite from server 100 and analyzing it.

[0025] The printer 300 is composed of a main body 300M and parts 300P. The parts 300P are detachable from the main body 300M and can be added or changed, and operate in a FW separate from the main body 300M. FIG. 1 shows an example in which a fuser 300P1 and an optional tray 300P2 are mounted on the main body 300M as the parts 300P. The fuser 300P1 is a standard specification and is always mounted on the printer 300. On the other hand, the optional tray 300P2 is optional, and the user can choose whether or not to mount it on the printer 300.

[0026] The main body 300M has a control unit 301, a transmission / reception unit 302, a part change detection unit 303, an active FW version information storage unit 304, and a storage unit 305. The transmission / reception unit 302 communicates with the PC 200 via the network Nt2, and also communicates with the part 300P attached to the main body 300M. The part change detection unit 303 detects that the part 300P has been added to or changed in the main body 300M. Specifically, the part change detection unit 303 detects that the part 300P has been added to or changed in the main body 300M by communicating with the part 300P via the transmission / reception unit 302, or by using the detection result of a sensor that detects the attachment or detachment of the part 300P.

[0027] The active FW version information storage unit 304 stores active FW version information indicating the version numbers of each of the multiple FWs (FW operating the main body 300M and FW operating the component 300P) operating the printer 300. The storage unit 305 stores information acquired through communication, etc. The control unit 301 is composed of, for example, a CPU and a memory, and reads and executes programs stored in the storage unit 305 to control each unit and execute various processes.

[0028] Although omitted from Figure 1, this main body 300M is equipped with, for example, a unit CU that controls the overall operation, a unit PU that controls the printing operation, and an image drum IM that forms an image on a medium such as paper, each of which has its own individual FW stored in non-volatile memory (not shown) and is operated by that FW.

[0029] The fixing device 300P1 is a component that fixes an image formed on a medium by the image drum IM, and is operated by an individual FW stored in a non-volatile memory (not shown). The fixing device 300P1 has a control unit 311, a transmission / reception unit 312, and an operating FW version information storage unit 313. The transmission / reception unit 312 communicates with the main body 300M. The operating FW version information storage unit 313 stores operating FW version information that indicates the version of the FW that is operating the fixing device 300P1. The control unit 311 controls each unit to execute various processes.

[0030] The optional tray 300P2 is a component that supplies media such as paper to the main body 300M, and is operated by an individual FW stored in a non-volatile memory (not shown). Like the fixing unit 300P1, this optional tray 300P2 also has a control unit 311, a transmission / reception unit 312, and an active FW version information storage unit 313. The transmission / reception unit 312 communicates with the main body 300M. The active FW version information storage unit 313 stores active FW version information that indicates the version of the FW that is operating the optional tray 300P2. The control unit 311 controls each unit to execute various processes.

[0031] In the printer 300, for example, the control unit 301 of the main body 300M cooperates with the control unit 311 of each component 300P to update each FW operating the printer 300 using the latest version of the FWSuite provided from the server 100 via the PC 200. At this time, the control units 301, 311 update the active FW version information stored in the active FW version information storage unit 304 of the main body 300M and the active FW version information stored in the active FW version information storage unit 313 of the component 300P as they update each FW.

[0032] In addition, in the printer 300, for example, when a part 300P is added or changed, the control unit 301 updates the operating FW version information stored in the operating FW version information storage unit 304 of the main body 300M based on the operating FW version information stored in the operating FW version information storage unit 313 of the added or changed part 300P. When a part 300P is added or changed in this way, it is possible that the version of the FW of the added or changed part 300P is older than the latest version. For this reason, as will be described in detail later, in the data update system 1, when a part 300P is added or changed, each FW of the printer 300 is updated to the latest version.

[0033] The above is the configuration of the data updating system 1. Here, an example of active FW version information stored in active FW version information storage unit 304 of main body 300M of printer 300 is shown in FIG.

[0034] This active FW version information includes the version of FWSuite and the version of the FW that operates each piece of hardware in the printer 300. For example, the active FW version information shown in Fig. 2 includes "FWSuite5.0", "CU:5.50", "PU:5.15", "IM:5.05", "FuserA:5.15", and "OpTrayA:5.05".

[0035] Among these, "FWSuite5.0" indicates that the version number of the FWSuite previously acquired by the printer 300 is "5.0." In addition, "CU:5.50" indicates that the version number of the FW running the unit CU is "5.50," "PU:5.15" indicates that the version number of the FW running the unit PU is "5.15," and "IM:5.05" indicates that the version number of the FW running the image drum IM is "5.05."

[0036] Furthermore, "Fixing A: 5.15" indicates that the version number of the firmware operating the currently installed fixing unit 300P1 is "5.15," and "OpTray A: 5.05" indicates that the version number of the firmware operating the currently installed optional tray 300P2 is "5.05."

[0037] Incidentally, in order to stably procure parts 300P, printer 300 is designed to be able to use parts 300P with the same functions procured from a plurality of manufacturers. Specifically, printer 300 is designed to be able to use, for example, a fixing unit 300P1 equipped with a microcomputer manufactured by company A and a fixing unit equipped with a microcomputer manufactured by company B.

[0038] Here, the fixing unit 300P1 equipped with a microcomputer manufactured by Company A and the fixing unit 300P1 equipped with a microcomputer manufactured by Company B may have the same functions but may operate with different FW. For this reason, as shown in Fig. 2, when the fixing unit 300P1 mounted on the printer 300 is equipped with a microcomputer manufactured by Company A (i.e., when it operates with FW for a microcomputer manufactured by Company A), the operating FW version information is configured to add "A" after "fixing", such as "fixing A: 5.15".

[0039] On the other hand, as shown in FIG. 3, when the fixing unit 300P1 installed in the printer 300 is equipped with a microcomputer manufactured by Company B (i.e., when it operates with FW for a microcomputer manufactured by Company B), the operating FW version information is configured to add "B" after "fixing", such as "fixing B: 4.44".

[0040] In this way, the active FW version information of the printer 300 is capable of distinguishing whether the FW operating the fixing unit 300P1 is FW for a microcomputer made by company A or FW for a microcomputer made by company B.

[0041] The same is true for the optional tray 300P2; for example, it is possible to use one equipped with a microcomputer made by company A and one equipped with a microcomputer made by company B. In addition, in the active FW version information, if the optional tray 300P2 attached to the printer 300 is equipped with a microcomputer made by company A, then "A" is added after "OpTray" as shown in Fig. 2, and if it is equipped with a microcomputer made by company B, then "B" is added after "OpTray" (not shown).

[0042] Furthermore, in the printer 300, the fixing unit 300P1 may be replaced from one equipped with a microcomputer manufactured by company A to one equipped with a microcomputer manufactured by company B (or vice versa). In this case, for example, as shown in Figures 2 and 3, "fixing A: 5.15" included in the active FW version information is rewritten to "fixing B: 4.44".

[0043] The same applies to the optional tray 300P2. For example, if the optional tray 300P2 is replaced with one equipped with a microcontroller made by company A and one equipped with a microcontroller made by company B, the "OpTrayA:5.05" contained in the information on the currently running firmware version will be rewritten to "OpTrayB:*.**".

[0044] Furthermore, the printer 300 is also configured to allow a part 300P to be added, in which case the version of the FW that is running the added part 300P is added to the active FW version information.

[0045] 4 shows an example of the latest FW version information stored in the memory unit 204 of the PC 200. This latest FW version information includes the latest version of the FWSuite provided by the server 100 and the latest version of the FW included in the FWSuite that operates each piece of hardware in the printer 300. For example, the latest FW version information shown in FIG. 4 includes "FWSuite5.0", "CU:5.50", "PU:5.15", "IM:5.05", "Fuser A:5.15", "Fuser B:5.55", "OpTray A:5.05", and "OpTray B:5.15".

[0046] Furthermore, the latest version of FWSuite provided by server 100 includes, as the latest version of FW for fixing unit 300P1, both FW for fixing unit 300P1 equipped with a microcomputer manufactured by company A and FW for fixing unit 300P1 equipped with a microcomputer manufactured by company B.

[0047] For this reason, the latest FW version information shown in Figure 4 includes the FW version number for the fixing unit 300P1 equipped with a microcomputer manufactured by Company A and the FW version number for the fixing unit 300P1 equipped with a microcomputer manufactured by Company B, such as "Fixing A: 5.15" and "Fixing B: 5.55".

[0048] Similarly, the latest version of FWSuite provided by server 100 includes, as the latest version of FW for optional tray 300P2, both FW for optional tray 300P2 equipped with a microcomputer manufactured by company A and FW for optional tray 300P2 equipped with a microcomputer manufactured by company B.

[0049] For this reason, the latest FW version information shown in Figure 4 includes the FW version number for optional tray 300P2 equipped with a microcontroller manufactured by company A and the FW version number for optional tray 300P2 equipped with a microcontroller manufactured by company B, such as "OpTrayA:5.05" and "OpTrayB:5.15".

[0050] As will be described in more detail later, PC 200 determines whether the FW operating each piece of hardware in printer 300 is the latest version by comparing its own latest FW version information (Figure 4) with the operating FW version information (Figure 2 or Figure 3) obtained from printer 300.

[0051] [1-2. Operation of the data update system] Next, the procedure of the operation of the data updating system 1 will be described with reference to the flowchart shown in FIG.

[0052] As a premise, as described above, the control unit 202 of the PC 200 communicates with the server 100 periodically (for example, once a month) and acquires the FWSuite when the FWSuite is updated on the server 100 side. The control unit 202 of the PC 200 also communicates (polls) with the printer 300 periodically (for example, once a day) and acquires active FW version information from the printer 300. Furthermore, as described above, the control unit 301 of the printer 300 updates the active FW version information stored in the active FW version information storage unit 304 when a part 300P is added or changed.

[0053] Then, in the first step SP11, the control unit 202 of the PC 200 analyzes the latest version of FWSuite acquired from the server 100 with the FW configuration information analysis unit 205, thereby extracting the latest version of FWSuite and the latest version of the FW that operates each piece of hardware in the printer 300. The control unit 202 then generates latest FW version information based on the version extracted from the FWSuite and stores it in the storage unit 204. The operation of this step SP11 is an operation that is performed when the PC 200 acquires the latest version of FWSuite from the server 100. Here, the PC 200 acquires the latest version of FWSuite from the server 100 when, for example, the application 201 is started for the first time, when the FWSuite is updated on the server 100 side, or when the PC 200 determines that the FW on the printer 300 side is not the latest version. In other cases, this step SP11 is skipped.

[0054] In the next step SP12, the control unit 202 of the PC 200 compares (checks) the active FW version information acquired from the printer 300 with the latest FW version information stored in the storage unit 204 in step SP11. Specifically, the control unit 202 compares the version of the FWSuite included in the active FW version information with the latest version of the FWSuite included in the latest FW version information. The control unit 202 also compares the version of each FW operating each piece of hardware included in the active FW version information with the latest version of each FW operating each piece of hardware included in the latest FW version information.

[0055] In the next step SP13, the control unit 202 of the PC 200 determines whether there is a difference between the version number of the FWSuite contained in the operating FW version information and the version number of each FW operating each piece of hardware, and the latest version number of the FWSuite contained in the latest FW version information and the latest version number of each FW operating each piece of hardware.

[0056] For example, if the version number of FWSuite included in the active FW version information and the version number of each FW operating each piece of hardware are the version numbers shown in Fig. 2, and the latest version number of FWSuite included in the latest FW version information and the latest version number of each FW operating each piece of hardware are the version numbers shown in Fig. 4, the control unit 202 of the PC 200 will determine that there is no difference because the version number of FWSuite included in the active FW version information and the version number of each FW operating each piece of hardware match the latest version number of FWSuite included in the latest FW version information and the latest version number of each FW operating each piece of hardware. This means that the FWs on the printer 300 side are all the latest versions.

[0057] In this case, the control unit 202 of the PC 200 obtains a negative result in step SP13, returns to step SP11, and continues regular communication with the server 100 and regular communication with the printer 300.

[0058] In contrast, if the version number of FWSuite included in the active FW version information and the version number of each FW operating each piece of hardware are the version numbers shown in Fig. 3, and the latest version number of FWSuite included in the latest FW version information and the latest version number of each FW operating each piece of hardware are the version numbers shown in Fig. 4, the control unit 202 of the PC 200 will determine that there is a difference because "fixing B: 4.44" included in the active FW version information is different from "fixing B: 5.55" included in the latest FW version information. This means that there is a FW that is not the latest version among the FWs on the printer 300 side.

[0059] In this case, the control unit 202 of the PC 200 obtains a positive result in step SP13 and proceeds to step SP14. In step SP14, the control unit 202 of the PC 200 communicates with the server 100 to obtain the latest version of FWSuite from the server 100. In the following step SP15, the control unit 202 of the PC 200 transmits the latest version of FWSuite obtained from the server 100 to the printer 300.

[0060] In the next step SP16, control unit 301 of printer 300 stores the latest version of FWSuite received from PC 200 in storage unit 305, and updates each FW operating printer 300 with the latest version of FWSuite. At this time, control unit 301 of printer 300 also updates the active FW version information stored in active FW version information storage unit 304 as each FW is updated. As a result, the version number of FWSuite and the version number of each FW included in the active FW version information stored in active FW version information storage unit 304 become the latest versions.

[0061] In the next step SP17, the control unit 301 of the printer 300 deletes the FWSuite used to update the FW from the storage unit 305, and ends the series of operations. Thereafter, the control unit 202 of the PC 200 returns to step SP11, and continues regular communication with the server 100 and regular communication with the printer 300. The procedure of the operation of the data updating system 1 is as described above.

[0062] [1-3. Summary and Effects] As described so far, in the first embodiment, the procedure for the operation (data updating method) of the data updating system 1 that updates the data (FW) of the printer 300 as an information processing device that can add or change a part 300P that is detachable to or attached to the outside or inside of the main body 300M is as follows: first, when a part 300P is added to or changed in the main body 300M of the printer 300, the control unit 301 of the printer 300 updates the operating FW version information, which is data set reception information used to receive the FWSuite as a data set and indicates the version number of each FW operating the printer 300, in accordance with the addition or change of the part 300P.

[0063] At this time, if the FW operating the added or changed part 300P (e.g., the fixing unit 300P1) is not the latest version, the updated active FW version information will indicate that the version of the FW of the part 300P is not the latest. In other words, the active FW version information at this time has been updated to indicate a state in which it is necessary to receive the latest version of the FWSuite. The control unit 301 of the printer 300 transmits the active FW version information updated in this manner to the PC 200 acting as a relay device via the transmitting / receiving unit 302 acting as a transmitting unit.

[0064] The control unit 202 of the PC 200 stores in a memory unit 204 latest FW version information indicating the latest version of each FW that operates the printer 300, which is included in the latest version of the FWSuite provided by the server 100, and when the control unit 202 receives the operating FW version information from the printer 300 by the transmitting / receiving unit 203 functioning as a receiving unit, it compares the version number of each FW included in the latest FW version information with the version number of each FW included in the operating FW version information received from the printer 300. At this time, since the FW version of the part 300P included in the operating FW version information is different from the FW version of the part 300P included in the latest FW version information and the printer 300 needs to receive the latest version of the FWSuite, the control unit 202 of the PC 200 obtains from the server 100 an FWSuite corresponding to a specified version used for updating the FW of the main body 300M of the printer 300 and the FW of the part 300P (i.e., the latest version of the FWSuite), and transmits the latest version of the FWSuite to the printer 300 by the transmission / reception unit 203 functioning as a transmission unit.

[0065] The control unit 301 functioning as an update unit of the printer 300 executes an update of the FW (e.g., the FW of each of the unit CU, the unit PU, and the image drum IM) as the main body data stored in the main body 300M and the FW (e.g., the FW of each of the fuser 300P1 and the optional tray 300P2) as the part data stored in the part 300P, using the latest version of the FWSuite received from the PC 200 by the transmission / reception unit 302 functioning as a reception unit. When the FW update is completed, the control unit 301 functioning as an update unit of the printer 300 updates the active FW version information in accordance with the FW update, and deletes the FWSuite used for the FW update. At this time, the updated active FW version information indicates that the versions of all FWs are the latest versions. In other words, the active FW version information at this time is updated to a state indicating that the reception of the latest version of the FWSuite is unnecessary.

[0066] In this way, in the data updating system 1 of the first embodiment, when a part 300P is added or changed on the printer 300 side, the printer 300 receives the latest FWSuite from the server 100 via the PC 200, and updates the FW of the main body 300M and the FW of the part 300P using the latest FWSuite. This makes it easier to avoid a situation where the added or changed part 300P continues to use an old version of FW, compared to, for example, the conventional case in which a user manually updates the data of the part.

[0067] Thus, in the data updating system 1 of the first embodiment, the FW of the printer 300 can be updated appropriately.

[0068] Furthermore, in the data update system 1 of the first embodiment, the application 201 installed in the PC 200 that relays between the server 100 and the printer 300 has a function to periodically obtain operating FW version information from the printer 300 on the PC 200 side, and compares the operating FW version information with the latest FW version information to determine whether or not the FW of the printer 300 needs to be updated.

[0069] In this way, the data update system 1 of the first embodiment can utilize an existing system in which, for example, a PC that acts as an intermediary between the server and the printer communicates with the server periodically (for example, once a month) and, when the FWSuite is updated, obtains the latest version of FWSuite from the server and sends it to the printer, thereby making it possible to significantly reduce the costs required to build a system compared to building a system from scratch.

[0070] 2. Second embodiment Next, a second embodiment will be described. In this second embodiment, a part of the operation of the data update system 1 is different from that of the first embodiment. In the first embodiment, as shown in Fig. 2 or 3, the printer 300 transmits to the PC 200 the active FW version information updated in association with the addition or modification of the part 300P to the printer 300, and the PC 200 compares the active FW version information with the latest FW version information to determine whether or not the printer 300 needs to update the FW.

[0071] In contrast, in the second embodiment, when the printer 300 updates the active FW version information in conjunction with adding or changing the part 300P, if the updated active FW version information contains a portion that has been changed from the active FW version information before the update, change notification information (e.g., "*") is added to that portion. The active FW version information is then sent to the PC 200, and if the active FW version information contains the change notification information, the printer 300 determines that a FW update is required.

[0072] Specifically, when updating the active FW version information, the control unit 301 of the printer 300 first copies the active FW version information before the update stored in the active FW version information storage unit 304 to its own memory, etc. Here, it is assumed that the copied active FW version information before the update has the content shown in Fig. 2, for example. Thereafter, the control unit 301 updates the active FW version information stored in the active FW version information storage unit 304 in conjunction with the addition or modification of the part 300P. Here, it is assumed that the updated active FW version information has the content shown in Fig. 3, for example.

[0073] When the control unit 301 of the printer 300 identifies that there is a part in the updated active FW version information that has been changed from the active FW version information before the update by comparing the active FW version information before the update with the active FW version information after the update, it adds "*" as change notification information to the end of the changed part (for example, "fixing B: 4.44") as shown in Fig. 6. Note that even if the version number has not changed but the type of microcomputer mounted on the part 300P has changed, for example, "fixing A: 5.15" before the update and "fixing B: 5.15" after the update, or if the type of microcomputer has not changed but the version number has changed, for example, "fixing A: 5.15" before the update and "fixing A: 4.50" after the update, "*" is added as change notification information to the end of the changed part.

[0074] In this way, when the operating FW version information contains change notification information, this means that the addition or modification of part 300P has changed the version of the FW operating part 300P or the type of microcontroller on which the FW operates, and therefore a FW update is required on the printer 300 side.

[0075] When the operating FW version information acquired from the printer 300 includes change notification information, the control unit 202 of the PC 200 immediately acquires the latest version of FWSuite from the server 100 and transmits it to the printer 300. As a result, the FW is updated on the printer 300 side using the latest version of FWSuite.

[0076] [2-1. Operation of the data update system] Here, the procedure of the operation of the data updating system 1 according to the second embodiment will be described with reference to the flowcharts shown in FIGS.

[0077] First, the procedure of the operation when updating the active firmware version information on the printer 300 side will be described with reference to the flowchart shown in FIG.

[0078] In a first step SP31, a user adds or changes a part 300P to the main body 300M of the printer 300. In the following step SP32, the control unit 301 of the printer 300 detects, by the part change detection unit 303, that the part 300P has been added or changed.

[0079] In the next step SP33, the control unit 301 of the printer 300 copies the pre-update active FW version information stored in the active FW version information storage unit 304 to its own memory or the like, and then updates the active FW version information stored in the active FW version information storage unit 304 in accordance with the addition or change of the part 300P. Next, the control unit 301 compares the pre-update active FW version information with the updated active FW version information to determine whether or not there is a part in the updated active FW version information that has been changed from the pre-update active FW version information (i.e., a difference from the pre-update active FW version information).

[0080] Here, if the updated active FW version information does not contain any changes from the active FW version information before the update, this means, for example, that the part 300P has simply been removed. In this case, the control unit 301 of the printer 300 obtains a negative result in step SP33, proceeds to step SP35, and transmits the active FW version information stored in the active FW version information storage unit 304 (i.e., the active FW version information that does not include the change notification information) to the PC 200 during communication with the PC 200.

[0081] On the other hand, if the updated active FW version information contains any changes from the active FW version information before the update, this means that, for example, the addition or modification of the part 300P has changed the version of the FW operating the part 300P or the type of microcomputer in which the FW operates. In this case, the control unit 301 of the printer 300 obtains a positive result in step SP33 and proceeds to step SP34.

[0082] In step SP34, the control unit 301 of the printer 300 adds change notification information ("*") to the changed portion of the active FW version information stored in the active FW version information storage unit 304. After that, in the following step SP35, the control unit 301 of the printer 300 transmits the active FW version information stored in the active FW version information storage unit 304 (i.e., the active FW version information including the change notification information) to the PC 200 during communication with the PC 200, and ends the series of operations. The above is the procedure of the operation when updating the active FW version information on the printer 300 side. Note that, here, even if the active FW version information has not been changed before and after the update, the printer 300 is configured to transmit the active FW version information to the PC 200, but this is not limiting, and if the active FW version information has not been changed before and after the update, the active FW version information may not be transmitted to the PC 200.

[0083] Next, the procedure of the operation when updating the firmware of the printer 300 will be described with reference to the flowchart shown in FIG.

[0084] As a premise, the control unit 202 of the PC 200 communicates (polls) with the printer 300 periodically (for example, once a day) and acquires active FW version information from the printer 300. Furthermore, as described above, the control unit 301 of the printer 300 updates the active FW version information stored in the active FW version information storage unit 304 when the part 300P is added or changed.

[0085] Then, in the first step SP21, the control unit 202 of the PC 200 checks whether the active firmware version information acquired from the printer 300 includes change notification information.

[0086] In the next step SP22, the control unit 202 of the PC 200 determines whether or not the active FW version information contains change notification information based on the check result in step SP21. If the active FW version information does not contain change notification information, this means that the FW version and the type of microcomputer in which the FW operates have not changed on the printer 300 side, and there is no need to update the FW. In this case, the control unit 202 of the PC 200 obtains a negative result in step SP22, returns to step SP21, and continues regular communication with the printer 300.

[0087] On the other hand, if the active FW version information includes change notification information, this means that the FW version or the type of microcomputer in which the FW runs has changed on the printer 300 side, and so the FW needs to be updated on the printer 300 side. In this case, the control unit 202 of the PC 200 obtains a positive result in step SP22 and proceeds to step SP23.

[0088] In step SP23, the control unit 202 of the PC 200 communicates with the server 100 to obtain the latest version of FWSuite from the server 100. In the following step SP24, the control unit 202 of the PC 200 transmits the latest version of FWSuite obtained from the server 100 to the printer 300.

[0089] In the next step SP25, control unit 301 of printer 300 stores the latest version of FWSuite received from PC 200 in storage unit 305, and updates each FW operating printer 300 using the latest version of FWSuite. At this time, control unit 301 of printer 300 also updates the active FW version information stored in active FW version information storage unit 304 as each FW is updated. As a result, the version number of FWSuite and the version number of each FW included in the active FW version information stored in active FW version information storage unit 304 become the latest versions. Note that when updating the active FW version information at this time, no change or addition information is added.

[0090] In the next step SP26, the control unit 301 of the printer 300 deletes the FWSuite used to update the FW from the storage unit 305, and ends the series of operations. Thereafter, the control unit 202 of the PC 200 returns to step SP21 and continues regular communication with the printer 300. The procedure of operations when updating the FW of the printer 300 is as described above.

[0091] [2-2. Summary and Effects] As described so far, in the second embodiment, the procedure for the operation (data updating method) of the data updating system 1 for updating the FW of the printer 300 as an information processing device that can add or change a part 300P that is detachable to or attached to the outside or inside of the main body 300M is as follows: first, when a part 300P is added to or changed in the main body 300M of the printer 300, the control unit 301 of the printer 300 updates the operating FW version information, which is data set reception information used to receive the FWSuite and indicates the version number of each FW operating the printer 300, in accordance with the addition or change of the part 300P.

[0092] At this time, if the updated active FW version information contains any changes from the active FW version information before the update (i.e., any changes to the FW version or the type of microcomputer in which the FW runs), the control unit 301 of printer 300 adds change notification information as data to the updated active FW version information. In other words, the active FW version information to which the change notification information has been added has been updated to content indicating a state in which it is necessary to receive the latest version of the FWSuite. The control unit 301 of printer 300 transmits the active FW version information updated in this way to PC 200.

[0093] When the control unit 202 of the PC 200 receives the active FW version information from the printer 300, the control unit 202 determines whether or not the active FW version information includes change notification information. If the active FW version information includes change notification information, the control unit 202 of the PC 200 acquires the latest version of FWSuite from the server 100 and transmits the latest version of FWSuite to the printer 300, since it is necessary for the printer 300 to receive the latest version of FWSuite.

[0094] The control unit 301 of the printer 300 uses the latest version of the FWSuite received from the PC 200 to execute the update of the FW of the main body 300M (for example, the respective FW of the unit CU, the unit PU, and the image drum IM) and the FW of the part 300P (for example, the respective FW of the fixing unit 300P1 and the optional tray 300P2). When the FW update is completed, the control unit 301 of the printer 300 updates the active FW version information in conjunction with the FW update (no change notification information is added), and deletes the FWSuite used for the FW update. At this time, the updated active FW version information is in a state indicating that the versions of all FWs are the latest versions and does not include change notification information (i.e., the change notification information has been deleted). Therefore, at this time, the active FW version information has been updated to a state indicating that it is not necessary to receive the latest version of the FWSuite.

[0095] In this way, in the data updating system 1 of the second embodiment, as in the first embodiment, when a part 300P is added or changed on the printer 300 side, the printer 300 receives the latest FWSuite from the server 100 via the PC 200, and updates the FW of the main body 300M and the FW of the part 300P using the latest FWSuite. This makes it easier to avoid a situation where the added or changed part 300P continues to be used with an old version of FW, compared to, for example, the conventional case in which a user manually updates the data of the part.

[0096] In addition, in the data update system 1 of the second embodiment, when the printer 300 updates the operating FW version information in response to the addition or change of a part 300P, if the updated operating FW version information contains changes from the operating FW version information before the update, change notification information is added to the updated operating FW version information and then sent to the PC 200.

[0097] The PC 200 determines whether or not the FW of the printer 300 needs to be updated based on whether or not the active FW version information acquired from the printer 300 includes change notification information.

[0098] In this way, in the PC 200 of the second embodiment, the process of comparing the latest version number of each FW contained in the latest FWSuite provided by the server 100 with the version number of each FW contained in the operating FW version information obtained from the printer 300 as in the first embodiment is not necessary, and it is possible to determine whether or not the FW of the printer 300 needs to be updated by the simple process of checking whether or not the operating FW version information obtained from the printer 300 contains change notification information.

[0099] In this way, in the data update system 1 of the second embodiment, the processing load on the PC 200 side can be reduced compared to the first embodiment. For example, when multiple printers 300 are connected to one PC 200, the processing load can be distributed to each printer 300, thereby shortening the time required for updating the FW.

[0100] 3. Third Embodiment Next, a third embodiment will be described. In the third embodiment, a part of the operation of the data update system 1 is different from the first and second embodiments. In the second embodiment, as shown in Fig. 6, when the active FW version information is updated in association with the addition or change of a part 300P to the printer 300, if there is a part in the active FW version information after the update that has been changed from the active FW version information before the update, change notification information is added to the active FW version information and transmitted from the printer 300 to the PC 200.

[0101] In contrast, in the third embodiment, when the active FW version information is updated in conjunction with the addition or modification of a part 300P in the printer 300, if the updated active FW version information contains a portion that has been changed from the active FW version information before the update, the control unit 301 of the printer 300 extracts the FWSuite version from the active FW version information and changes the FWSuite version to a value smaller than the original version (for example, a value obtained by subtracting 0.1), as shown in Fig. 9. The changed FWSuite version is then transmitted to the PC 200 as the FWSuite version used to update the FW on the printer 300 side.

[0102] In this way, in the third embodiment, if the updated active FW version information contains any changes from the active FW version information before the update, it is necessary to update the FW on the printer 300 side, so the printer 300 changes (disguises) the FWSuite version to a smaller (older) version than the actual version and notifies the PC 200. As shown in Fig. 9, for example, if the actual version of FWSuite is 5.0, the FWSuite version is disguised as 4.9 and sent to the PC 200.

[0103] The control unit 202 of the PC 200 compares the version number of the FWSuite sent from the printer 300 with the latest version number of the FWSuite included in the latest FW version information. If the version number of the FWSuite sent from the printer 300 is smaller than the latest version number of the FWSuite, the control unit 202 of the PC 200 obtains the latest version of the FWSuite from the server 100 and sends it to the printer 300. This causes the FW to be updated on the printer 300 side using the latest version of the FWSuite.

[0104] At this time, the version number of the FWSuite sent from the printer 300 is disguised as a version number smaller than the actual version number, and is always smaller than the version number of the latest version of the FWSuite, so that the FW is updated on the printer 300 side using the latest version of the FWSuite provided by the server 100.

[0105] [3-1. Operation of the data update system] Here, the procedure of the operation of the data updating system 1 according to the third embodiment will be described with reference to the flow charts shown in FIGS.

[0106] First, the procedure of operations performed when the version number of the FWSuite is spoofed on the printer 300 side will be described with reference to the flow chart shown in FIG.

[0107] In a first step SP51, the user adds or changes a part 300P to the main body 300M of the printer 300. In the following step SP52, the control unit 301 of the printer 300 detects, by the part change detection unit 303, that the part 300P has been added or changed.

[0108] In the next step SP53, the control unit 301 of the printer 300 copies the pre-update active FW version information stored in the active FW version information storage unit 304 to its own memory or the like, and then updates the active FW version information stored in the active FW version information storage unit 304 in accordance with the addition or change of the part 300P. Next, the control unit 301 compares the pre-update active FW version information with the updated active FW version information to determine whether or not the updated active FW version information contains any part that has been changed from the pre-update active FW version information (i.e., any difference from the pre-update active FW version information).

[0109] If the updated active FW version information does not contain any changes from the active FW version information before the update, this means, for example, that the part 300P has simply been removed. In this case, the control unit 301 of the printer 300 obtains a negative result in step SP53, proceeds to step SP55, and transmits to the PC 200 the version of the FWSuite extracted from the active FW version information stored in the active FW version information storage unit 304 during communication with the PC 200.

[0110] On the other hand, if the updated active FW version information contains any changes from the active FW version information before the update, this means that, for example, the addition or modification of the part 300P has changed the version of the FW operating the part 300P or the type of microcomputer in which the FW operates. In this case, the control unit 301 of the printer 300 obtains a positive result in step SP53 and proceeds to step SP54.

[0111] In step SP54, the control unit 301 of the printer 300 extracts the version number of the FWSuite from the active FW version information stored in the active FW version information storage unit 304, and sets the version number obtained by subtracting a predetermined number from the extracted version number (-0.1 version number) as the version number of the FWSuite. After that, in the following step SP55, the control unit 301 of the printer 300 transmits the version number of the FWSuite (i.e., a version number disguised to a value smaller than the actual version number) to the PC 200 during communication with the PC 200, and ends a series of operations. The above is the procedure of the operation when the version number of the FWSuite is disguised on the printer 300 side. Here, if the active FW version information has not been changed before and after the update, the printer 300 transmits the version number of the FWSuite to the PC 200 without disguising it, but this is not limited to the above, and if the active FW version information has not been changed before and after the update, the FWSuite version number itself may not be transmitted to the PC 200.

[0112] Next, the procedure of the operation when updating the firmware of the printer 300 will be described with reference to the flowchart shown in FIG.

[0113] As a premise, the control unit 202 of the PC 200 communicates with the server 100 periodically (for example, once a month), and when the FWSuite is updated on the server 100 side, acquires the FWSuite and updates the latest FW version information stored in the storage unit 204. The control unit 202 of the PC 200 also communicates (polls) with the printer 300 periodically (for example, once a day) and acquires the FWSuite version from the printer 300. Furthermore, as described above, the control unit 301 of the printer 300 updates the active FW version information stored in the active FW version information storage unit 304 when a part 300P is added or changed.

[0114] Then, in the first step SP41, the control unit 202 of the PC 200 compares (checks) the version number of the FWSuite obtained from the printer 300 with the version number of the latest version of the FWSuite contained in the latest FW version information stored in the memory unit 204.

[0115] In the next step SP42, the control unit 202 of the PC 200 determines whether or not there is a difference between the version number of the FWSuite acquired from the printer 300 and the version number of the latest version of FWSuite included in the latest FW version information. If there is no difference between the version number of the FWSuite acquired from the printer 300 and the version number of the latest version of FWSuite included in the latest FW version information, this means that the printer 300 has already acquired the latest version of FWSuite and there is no need to update the FW. In this case, the control unit 202 of the PC 200 obtains a negative result in step SP42, returns to step SP41, and continues regular communication with the printer 300.

[0116] On the other hand, if there is a difference between the version number of the FWSuite acquired from the printer 300 and the latest version number of the FWSuite included in the latest FW version information, this means that the FWSuite acquired on the printer 300 side is not the latest version, and the FW needs to be updated using the latest version of the FWSuite. In this case, the control unit 202 of the PC 200 obtains a positive result in step SP42 and proceeds to step SP43.

[0117] In step SP43, the control unit 202 of the PC 200 communicates with the server 100 to obtain the latest version of FWSuite from the server 100. In the following step SP44, the control unit 202 of the PC 200 transmits the latest version of FWSuite obtained from the server 100 to the printer 300.

[0118] In the next step SP45, control unit 301 of printer 300 stores the latest version of FWSuite received from PC 200 in storage unit 305, and uses the latest version of FWSuite to update each FW operating printer 300. At this time, control unit 301 of printer 300 also updates the active FW version information stored in active FW version information storage unit 304 as each FW is updated. As a result, the version number of FWSuite and the version number of each FW included in the active FW version information stored in active FW version information storage unit 304 become the latest versions.

[0119] In the next step SP46, the control unit 301 of the printer 300 deletes the FWSuite used to update the FW from the storage unit 305, and ends the series of operations. Thereafter, the control unit 202 of the PC 200 returns to step SP41, and continues regular communication with the printer 300. The procedure of operations when updating the FW of the printer 300 is as described above.

[0120] [3-2. Summary and Effects] As described so far, in the third embodiment, the procedure for the operation (data update method) of the data update system 1 for updating the FW of the printer 300 as an information processing device that can add or change a part 300P that is detachable to or attached to the outside or inside of the main body 300M is as follows: first, when a part 300P is added to or changed in the main body 300M of the printer 300, the control unit 301 of the printer 300 updates the operating FW version information, which is data set reception information used to receive the FWSuite and indicates the version number of each FW operating the printer 300, in accordance with the addition or change of the part 300P.

[0121] At this time, if the updated active FW version information contains any changes from the active FW version information before the update (i.e., any changes to the FW version or the type of microcomputer in which the FW runs), the control unit 301 of the printer 300 changes the version of the FWSuite extracted from the updated active FW version information to a smaller (older) version than the changed version. In other words, the changed version of the FWSuite will be smaller than the version of the latest version of FWSuite, and so the information has been changed to indicate a state in which it is necessary to receive the latest version of FWSuite. The control unit 301 of the printer 300 transmits the changed version of the FWSuite to the PC 200.

[0122] When the control unit 202 of the PC 200 receives the version number of the FWSuite from the printer 300, it determines whether or not there is a difference between that version number and the latest version number of the FWSuite extracted from the latest FW version information. If there is a difference between the version number of the FWSuite received from the printer 300 and the version number of the latest version of the FWSuite, the control unit 202 of the PC 200 acquires the latest version of the FWSuite from the server 100 and transmits the latest version of the FWSuite to the printer 300, since it is necessary for the printer 300 to receive the latest version of the FWSuite.

[0123] The control unit 301 of the printer 300 uses the latest version of the FWSuite received from the PC 200 to update the FW of the main body 300M (e.g., the respective FW of the unit CU, unit PU, and image drum IM) and the FW of the part 300P (e.g., the respective FW of the fuser 300P1 and optional tray 300P2). When the FW update is completed, the control unit 301 of the printer 300 updates the active FW version information in conjunction with the FW update, and deletes the FWSuite used for the FW update. At this time, the updated active FW version information has the FWSuite version number and each FW version number the same as the latest version of the FWSuite and each FW version number. In other words, the FWSuite version number included in the active FW version information at this time has been updated to content indicating a state in which it is not necessary to receive the latest version of the FWSuite.

[0124] In this way, in the data updating system 1 of the third embodiment, as in the first embodiment, when a part 300P is added or changed on the printer 300 side, the printer 300 receives the latest FWSuite from the server 100 via the PC 200, and updates the FW of the main body 300M and the FW of the part 300P using the latest FWSuite. This makes it easier to avoid a situation where the added or changed part 300P continues to be used with an old version of FW, compared to, for example, the conventional case in which a user manually updates the data of the part.

[0125] Furthermore, in the data update system 1 of the third embodiment, when the printer 300 updates the active FW version information in response to the addition or modification of a part 300P, if the updated active FW version information contains changes from the active FW version information before the update, the version number of the FWSuite extracted from the updated active FW version information is changed (disguised) to a version number smaller than the original version number, and then transmitted to the PC 200.

[0126] The PC 200 determines whether or not the FW of the printer 300 needs to be updated based on whether or not there is a difference between the version number of the FWSuite acquired from the printer 300 and the version number of the latest version of the FWSuite.

[0127] In this way, in the PC 200 of the third embodiment, it is possible to determine whether or not the FW of the printer 300 needs to be updated by a simple process of comparing the version number of the FWSuite acquired from the printer 300 with the version number of the latest version of the FWSuite. In this way, in the data updating system 1 of the third embodiment, like the second embodiment, it is possible to reduce the processing load on the PC 200 side.

[0128] [4. Fourth embodiment] Next, a fourth embodiment will be described. In the fourth embodiment, part of the operation of the data updating system 1 is different from the first to third embodiments.

[0129] In the data update system 1 of this fourth embodiment, the premise is that the version number of the FWSuite and the integer part of the version number of each FW indicate the major version, and the major version of the FWSuite is updated when the FWSuite is released, so that the version number of the FWSuite and the major version of the version number of each FW contained in the FWSuite match.

[0130] Specifically, for example, when FWSuite 2.00 (major version "2") is released, the version numbers of all FWs included in that FWSuite will be "2.xx."Also, for example, when FWSuite 3.00 (major version "3") is released, the version numbers of all FWs included in that FWSuite will be "3.xx."

[0131] Furthermore, in the data update system 1 of the fourth embodiment, if the major version of each FW operating the printer 300 matches the major version of the FWSuite used to update each FW, there is no need to update the FW on the printer 300 side, but on the other hand, if there is a FW operating the printer 300 whose major version does not match the major version of the FWSuite used to update each FW (i.e., the major version is older than the major version of the FWSuite), the printer 300 determines that a FW update is necessary.

[0132] Furthermore, in this fourth embodiment, when the operating FW version information is updated in conjunction with adding or changing a part 300P to the printer 300, as shown in FIG. 12, if the version numbers of each FW included in the operating FW version information include a version number whose major version number differs from the version number of the FWSuite (for example, a version number other than "5.xx"), the control unit 301 of the printer 300 transmits the smallest version number of each FW (for example, "4.44") to the PC 200.

[0133] In this manner, in the fourth embodiment, if the version numbers of each FW contained in the active FW version information after the update include a version number with a different major version from the version number of the FWSuite, the printer 300 is configured to notify the PC 200 of the smallest version number, since a FW update is required on the printer 300 side.

[0134] The control unit 202 of the PC 200 compares the version number sent from the printer 300 with the latest version number of FWSuite included in the latest FW version information. If the version number sent from the printer 300 differs from the latest version number of FWSuite, the control unit 202 of the PC 200 obtains the latest version of FWSuite from the server 100 and sends it to the printer 300. This causes the FW to be updated on the printer 300 side using the latest version of FWSuite.

[0135] At this time, since the version number sent from printer 300 is smaller than the version number of the latest version of FWSuite (the major version is older), the FW will be updated on the printer 300 side using the latest version of FWSuite provided by server 100.

[0136] [4-1. Operation of the data update system] Here, the procedure of the operation of the data updating system 1 according to the fourth embodiment will be described with reference to the flow charts shown in FIGS.

[0137] First, the procedure of the operation when checking the major version of each FW on the printer 300 side will be described with reference to the flowchart shown in FIG.

[0138] In a first step SP71, the user adds or changes a part 300P to the main body 300M of the printer 300. In the following step SP72, the control unit 301 of the printer 300 detects, via the part change detection unit 303, that the part 300P has been added or changed.

[0139] In the next step SP73, the control unit 301 of the printer 300 copies the pre-update active FW version information stored in the active FW version information storage unit 304 to its own memory or the like, and then updates the active FW version information stored in the active FW version information storage unit 304 in accordance with the addition or change of the part 300P. Next, the control unit 301 compares the pre-update active FW version information with the updated active FW version information to determine whether or not there is a part in the updated active FW version information that has been changed from the pre-update active FW version information (i.e., a difference from the pre-update active FW version information).

[0140] If the updated active FW version information does not contain any changes from the active FW version information before the update, this means, for example, that the part 300P has simply been removed. In this case, the control unit 301 of the printer 300 obtains a negative result in step SP73 and ends the series of operations.

[0141] On the other hand, if the updated active FW version information contains any changes from the active FW version information before the update, this means that, for example, the addition or modification of the part 300P has changed the version of the FW operating the part 300P or the type of microcomputer in which the FW operates. In this case, the control unit 301 of the printer 300 obtains a positive result in step SP73 and proceeds to step SP74.

[0142] In step SP74, the control unit 301 of the printer 300 extracts the FWSuite version number and the version number of each FW from the operating FW version number information stored in the operating FW version number information storage unit 304, and determines whether or not there is a version number among the versions of each FW whose major version is different from the version number of the FWSuite.

[0143] Here, if there is no version number of each FW whose major version differs from that of the FWSuite, this means that the major version of each FW matches the major version of the FWSuite, and therefore no FW update is required on the printer 300 side. In this case, the control unit 301 of the printer 300 obtains a negative result in step SP74 and ends the series of operations.

[0144] On the other hand, if the version numbers of each FW include a version number whose major version differs from that of the FWSuite, this means that the major version of each FW does not match the major version of the FWSuite, and a FW update is required on the printer 300 side. In this case, the control unit 301 of the printer 300 obtains a positive result in step SP74 and proceeds to step SP75.

[0145] In step SP75, the control unit 301 of the printer 300 extracts the smallest version number of each FW from the active FW version information. Note that this version number is, for example, the version number of the FW that is operating the part 300P that has been added or changed to the printer 300. In the following step SP76, when communicating with the PC 200, the control unit 301 of the printer 300 transmits to the PC 200 the smallest version number of each FW extracted from the active FW version information, and the series of operations ends. The above is the procedure of operations when checking the major version of each FW on the printer 300 side.

[0146] Next, the procedure of the operation when updating the firmware of the printer 300 will be described with reference to the flowchart shown in FIG.

[0147] As a premise, the control unit 202 of the PC 200 communicates with the server 100 periodically (for example, once a month), and when the FWSuite is updated on the server 100 side, acquires the FWSuite and updates the latest FW version information stored in the storage unit 204. The control unit 202 of the PC 200 also communicates (polls) with the printer 300 periodically (for example, once a day) and acquires the version number from the printer 300. Furthermore, as described above, the control unit 301 of the printer 300 updates the active FW version information stored in the active FW version information storage unit 304 when a part 300P is added or changed.

[0148] Then, in the first step SP61, the control unit 202 of the PC 200 compares (checks) the version number obtained from the printer 300 with the version number of the latest version of the FWSuite contained in the latest FW version information stored in the memory unit 204.

[0149] In the next step SP62, the control unit 202 of the PC 200 determines whether or not there is a difference between the version number acquired from the printer 300 and the version number of the latest version of FWSuite included in the latest FW version information. If there is no difference between the version number of FWSuite acquired from the printer 300 and the version number of the latest version of FWSuite included in the latest FW version information, this means that there is no need to update the FW on the printer 300 side. In this case, the control unit 202 of the PC 200 obtains a negative result in step SP62, returns to step SP61, and continues regular communication with the printer 300.

[0150] On the other hand, if there is a difference between the version number obtained from printer 300 and the version number of the latest version of FWSuite included in the latest FW version information, this means that the FW needs to be updated because the FW on the printer 300 side contains a FW whose major version is different from the major version of the latest version of FWSuite. In this case, the control unit 202 of the PC 200 obtains a positive result in step SP62 and proceeds to step SP63.

[0151] In step SP63, the control unit 202 of the PC 200 communicates with the server 100 to obtain the latest version of FWSuite from the server 100. In the following step SP64, the control unit 202 of the PC 200 transmits the latest version of FWSuite obtained from the server 100 to the printer 300.

[0152] In the next step SP65, control unit 301 of printer 300 stores the latest version of FWSuite received from PC 200 in storage unit 305, and updates each FW operating printer 300 with the latest version of FWSuite. At this time, control unit 301 of printer 300 also updates the active FW version information stored in active FW version information storage unit 304 as each FW is updated. As a result, the version number of FWSuite and the version number of each FW included in the active FW version information stored in active FW version information storage unit 304 become the latest versions.

[0153] In the next step SP66, the control unit 301 of the printer 300 deletes the FWSuite used to update the FW from the storage unit 305, and ends the series of operations. Thereafter, the control unit 202 of the PC 200 returns to step SP61, and continues regular communication with the printer 300. The procedure of operations when updating the FW of the printer 300 is as described above.

[0154] [4-2. Summary and Effects] As described so far, in the fourth embodiment, the procedure for the operation (data update method) of the data update system 1 for updating the FW of the printer 300 as an information processing device to which a removable part 300P can be added or changed is as follows: first, when a part 300P is added to or changed in the printer 300, the control unit 301 of the printer 300 updates the operating FW version information, which is data set reception information used to receive the FWSuite and indicates the version number of each FW operating the printer 300, in accordance with the addition or change of the part 300P.

[0155] At this time, if the updated active FW version information contains a change from the active FW version information before the update (i.e., a change in the version of the FW or the type of the microcomputer in which the FW runs) and the version of each FW contained in the active FW version information contains a version with a different major version from the FWSuite contained in the active FW version information, the control unit 301 of the printer 300 extracts the smallest (oldest) version of each FW contained in the active FW version information. Since the version extracted at this time is smaller than the version of the latest version of FWSuite, the active FW version information has been updated to a state in which it is necessary to receive the latest version of FWSuite. The control unit 301 of the printer 300 transmits the version extracted from the active FW version information updated in this way to the PC 200.

[0156] When the control unit 202 of the PC 200 receives the version number from the printer 300, it determines whether or not there is a difference between the version number and the latest version of FWSuite extracted from the latest FW version information. If there is a difference between the version number received from the printer 300 and the version number of the latest version of FWSuite, the control unit 202 of the PC 200 acquires the latest version of FWSuite from the server 100 and transmits the latest version of FWSuite to the printer 300, since it is necessary for the printer 300 to receive the latest version of FWSuite.

[0157] The control unit 301 of the printer 300 uses the latest version of the FWSuite received from the PC 200 to update the FW of the main body 300M (for example, the respective FW of the unit CU, unit PU, and image drum IM) and the FW of the part 300P (for example, the respective FW of the fuser 300P1 and optional tray 300P2). When the FW update is completed, the control unit 301 of the printer 300 updates the active FW version information in conjunction with the FW update, and deletes the FWSuite used for the FW update. At this time, the updated active FW version information is in a state where the major versions of the FWSuite and each FW match. In other words, the active FW version information at this time has been updated to a state where it is no longer necessary to receive the latest version of the FWSuite.

[0158] In this manner, in the data update system 1 of the fourth embodiment, as in the first embodiment, when a part 300P is added or changed on the printer 300 side, the printer 300 receives the latest FWSuite from the server 100 via the PC 200, and uses the latest FWSuite to update the FW of the main body 300M and the FW of the part 300P, thereby avoiding a situation in which the added or changed part 300P continues to be used with an old version of FW.

[0159] Furthermore, in the data update system 1 of the fourth embodiment, when the printer 300 updates the active FW version information in response to the addition or modification of a part 300P, if the version numbers of each FW included in the updated active FW version information include a version number that has a different major version from the FWSuite included in the active FW version information, the smallest version number among the versions of each FW is extracted from the active FW version information and transmitted to the PC 200.

[0160] The PC 200 determines whether or not the FW of the printer 300 needs to be updated based on whether or not there is a difference between the version number acquired from the printer 300 and the latest version number of the FWSuite.

[0161] In this way, in the PC 200 of the fourth embodiment, it is possible to determine whether or not the FW of the printer 300 needs to be updated by a simple process of comparing the version number acquired from the printer 300 with the version number of the latest version of the FWSuite. In this way, in the data updating system 1 of the fourth embodiment, like the second and third embodiments, it is possible to reduce the processing load on the PC 200 side.

[0162] [5. Fifth Embodiment] Next, a fifth embodiment will be described. In the fifth embodiment, update FW version information indicating the version number of each FW included in the latest version of FWSuite used for updating the FW is stored in the printer 300, and the printer 300 compares the version number of each FW included in the update FW version information with the version number of each FW included in the active FW version information.

[0163] In the fifth embodiment, the configurations of the PC 200 and the printer 300 are different from those of the first to fourth embodiments. Therefore, in order to distinguish the PC 200 and the printer 300 of the fifth embodiment from the PC 200 and the printer 300 of the first to fourth embodiments, they are referred to as the PC 200x and the printer 300x, respectively. Similarly, the data update system 1 of the fifth embodiment is referred to as the data update system 1x.

[0164] [5-1. Data update system configuration] FIG. 15 shows the configuration of a data updating system 1x according to the fifth embodiment. This data updating system 1x differs from the data updating system 1 in the configurations of a PC 200x and a printer 300x. The PC 200x has a configuration in which a connection unit 206 for connecting to a USB memory 500, which is an example of an external storage medium, is added to the PC 200 of the first embodiment. The printer 300x has a configuration in which an update FW version information storage unit 306 for storing update FW version information, a display unit 307, and a connection unit 308 for connecting to the USB memory 500 are added to the printer 300 of the first embodiment. The connection unit 206 of the PC 200x and the connection unit 308 of the printer 300x will be described in the sixth embodiment.

[0165] As in the first to fourth embodiments, the latest version of FWSuite is stored in the storage unit 103 of the server 100. An example of the latest version of FWSuite 400 stored in the storage unit 103 of the server 100 is shown in FIG.

[0166] As in the first to fourth embodiments, the FWSuite 400 includes the latest versions of multiple FWs (e.g., "CU FW:01.06") for operating the printer 300x. Furthermore, in the fifth embodiment, the FWSuite 400 includes FW version information 401 indicating the version number of the FWSuite 400 and the version numbers of each of the multiple FWs included in the FWSuite 400. The FW version information 401 is, for example, a text file generated when the FWSuite 400 is built, and is stored in the FWSuite 400.

[0167] In the printer 300x, each FW operating the printer 300x is updated using the latest version of the FWSuite 400 provided from the server 100 via the PC 200x. At this time, the control unit 301 of the printer 300x updates the active FW version information stored in the active FW version information storage unit 304 of the main body 300M in conjunction with updating each FW.

[0168] Furthermore, at this time (that is, when the FW is updated), the printer 300x acquires the FW version information 401 from the latest version of the FWSuite 400 and stores this in the update FW version information storage unit 306 as update FW version information.

[0169] Then, for example, when the printer 300x is turned on, it compares (checks) the updated FW version information stored in the updated FW version information memory unit 306 with the operating FW version information stored in the operating FW version information memory unit 304.

[0170] Normally, in the printer 300x, the update FW version information stored in the update FW version information storage unit 306 matches the operating FW version information stored in the operating FW version information storage unit 304. On the other hand, in the printer 300x, the FW of the added or changed part 300P may not be the latest. In this case, a difference occurs between the update FW version information stored in the update FW version information storage unit 306 and the operating FW version information stored in the operating FW version information storage unit 304.

[0171] In this way, if a difference occurs between the updated FW version information and the operating FW version information, the printer 300x obtains the latest version of FWSuite 400 from the server 100 via the PC 200x, and uses the latest version of FWSuite 400 to update each FW operating the printer 300x to the latest version.

[0172] [5-2. Operation of the data update system] Next, the procedure of the operation of the data updating system 1x will be described with reference to the flowchart shown in Fig. 17. Here, as the operation of the data updating system 1x, the procedure of the operation when updating the FW of the printer 300x will be described.

[0173] As a premise, as described above, the control unit 301 of the printer 300x is configured to update the operating FW version information stored in the operating FW version information storage unit 304 when a part 300P is added or changed.

[0174] Then, in the first step SP101, the control unit 301 of the printer 300x obtains FW version information 401 from the latest version of FWSuite 400 obtained from the server 100 via the PC 200x, and stores and holds this as updated FW version information in the updated FW version information storage unit 306. Here, the time when the printer 300x obtains the latest version of FWSuite 400 from the server 100 is when the FW is updated. Note that in the case of the printer 300x whose FW has never been updated (i.e., in the case of the printer 300x at the time of shipment), no updated FW version information is stored in the updated FW version information storage unit 306.

[0175] Thereafter, the printer 300x is powered off, and in step SP102, the printer 300x is powered on. In the following step SP103, the control unit 301 of the printer 300x performs a comparison (version check) between the update FW version information stored in the update FW version information storage unit 306 and the operating FW version information stored in the operating FW version information storage unit 304, and determines whether there is a difference between them. Specifically, in the version check, the control unit 301 compares the FWSuite version number and the FW version number included in the operating FW version information with the FWSuite version number and the FW version number included in the update FW version information.

[0176] If the version check determines that there is no difference between the updated FW version information and the active FW version information, this means that FW update is not necessary. In this case, the control unit 301 of the printer 300x stores version check information indicating the result of this version check (no difference) in, for example, the storage unit 305, obtains a negative result in step SP103, and ends the series of operations.

[0177] On the other hand, if the version check determines that there is a difference between the update FW version information and the active FW version information, this means that the FW needs to be updated. In this case, the control unit 301 of the printer 300x stores version check information indicating the result of this version check (there is a difference) in, for example, the storage unit 305, obtains a positive result in step SP103, and proceeds to step SP104.

[0178] In step SP104, the control unit 301 of the printer 300x displays a message, etc., on the display unit 307, urging the user to update the FW. Here, the user who has seen the message, etc., starts the application 201 of the PC 200x. When the application 201 is started, the control unit 202 of the PC 200x communicates with the printer 300x.

[0179] In the next step SP105, the control unit 202 of the PC 200x acquires version check information from the printer 300x. If the version check information indicates that there is a difference between the update FW version information and the active FW version information as a result of the version check, the control unit 202 of the PC 200x acquires the latest version of the FWSuite 400 from the server 100 by communicating with the server 100, and transmits the FWSuite 400 to the printer 300x.

[0180] In the next step SP106, the control unit 301 of the printer 300x stores the latest version of the FWSuite 400 received from the PC 200x in the storage unit 305, and updates each FW operating the printer 300x with the latest version of the FWSuite 400. At this time, the control unit 301 of the printer 300x updates the active FW version information stored in the active FW version information storage unit 304 as each FW is updated, and updates the update FW version information stored in the update FW version information storage unit 306 with the FW version information 401 included in the FWSuite 400. Furthermore, since the update FW version information and the active FW version information match as each FW is updated, the control unit 301 of the printer 300x updates the version check information stored in the storage unit 305 to content indicating "no difference." Then, the control unit 301 of the printer 300x deletes the FWSuite used to update the FW from the storage unit 305, and ends the series of operations. The procedure of the operation of the data updating system 1x is as described above.

[0181] In this embodiment, the version check information is updated to indicate "no difference" when the FW is updated, but this is not limited to the above. For example, the version check information may not be updated when the FW is updated, and may be updated the next time the version check is performed.

[0182] [5-3. Summary and Effects] As described so far, in the fifth embodiment, the procedure for the operation (data update method) of the data update system 1x that updates the data (FW) of the printer 300x as an information processing device to which a detachable part 300P can be added or changed outside or inside the main body 300M is as follows: first, when the control unit 301 of the printer 300x updates each FW that operates the printer 300 using the FWSuite 400 as the latest version of the data set provided by the server 100, the control unit 301 obtains FW version information 401 from the FWSuite 400 and stores this in the update FW version information memory unit 306 as update FW version information, which is an example of update data version information.

[0183] In addition, the control unit 301 of the printer 300x stores in an operating FW version information storage unit 304 operating FW version information, which is an example of operating data version information indicating the version of the FW operating in the main body 300M and the version of the FW operating in the part 300P, and when a part 300P is added or changed to the main body 300M of the printer 300x, the operating FW version information stored in the operating FW version information storage unit 304 is updated in accordance with the addition or change of the part 300P.

[0184] Then, the control unit 301 of the printer 300x performs a version check to compare the version of each FW contained in the updated FW version information stored in the updated FW version information memory unit 306 with the version of each FW contained in the operating FW version information stored in the operating FW version information memory unit 304, and stores the result of the version check in the memory unit 305 as version check information, which is an example of data set reception information used to receive the FWSuite 400.

[0185] At this time, if the FW operating the added or changed part 300P (e.g., the fixing unit 300P1) is not the latest version, the version check information indicates that a difference has occurred between the updated FW version information and the active FW version information. In other words, the version check information at this time indicates a state in which it is necessary to receive the latest version of FWSuite 400. The control unit 301 of the printer 300x transmits this version check information to the PC 200x, which serves as a relay device, via the transmitting / receiving unit 302, which serves as a transmitting unit.

[0186] The control unit 202 of the PC 200x receives version check information from the printer 300x by the transmission / reception unit 203 functioning as a receiver. If the version check information indicates that a difference has occurred between the updated FW version information and the active FW version information, the control unit 202 of the PC 200 determines that the printer 300x needs to receive the latest version of the FWSuite 400, and acquires from the server 100 the FWSuite 400 (i.e., the latest version of the FWSuite) that corresponds to a predetermined version used for updating the FW of the main body 300M of the printer 300x and updating the FW of the part 300P, and transmits the latest version of the FWSuite 400 to the printer 300x by the transmission / reception unit 203 functioning as a transmitter.

[0187] The control unit 301, which functions as an update unit for the printer 300x, uses the latest version of the FWSuite 400 received from the PC 200x by the transmitting / receiving unit 302, which functions as a receiving unit, to update the FW as main body data stored in the main body 300M (e.g., the FW of each of the units CU, PU, ​​and image drum IM) and the FW as part data stored in the part 300P (e.g., the FW of each of the fixing unit 300P1 and optional tray 300P2).

[0188] When the FW update is complete, the control unit 301 of the printer 300x updates the active FW version information in conjunction with the FW update, and updates the update FW version information with the FW version information 401 included in the FWSuite 400 used to update the FW. The control unit 301 of the printer 300x also updates the version check information to information indicating that there is no difference between the update FW version information and the active FW version information, that is, to information indicating a state in which it is not necessary to receive the latest version of FWSuite 400. The control unit 301 of the printer 300x then deletes the FWSuite 400 used to update the FW.

[0189] In this manner, in the data update system 1x of the fifth embodiment, as in the first embodiment, when a part 300P is added or changed on the printer 300x side, the printer 300x receives the latest FWSuite from the server 100 via the PC 200x, and updates the FW of the main body 300M and the FW of the part 300P using the latest FWSuite, thereby easily avoiding a situation in which the added or changed part 300P continues to use an old version of FW.

[0190] In the data update system 1x of the fifth embodiment, the printer 300x stores the FW version information 401 included in the FWSuite 400 used in the previous FW update as update FW version information. The control unit 301 of the printer 300x compares this update FW version information with the FW version information in operation, and if there is a difference between them, the latest version of the FWSuite 400 is obtained from the server 100 via the PC 200x to update the FW.

[0191] In this way, in the data update system 1x of the fifth embodiment, there is no need to store and manage the latest FW version information in the storage unit 204 of the PC 200x, and even if the PC 200x is changed to another PC 200x (for example, a PC 200x that has never communicated with the printer 300x), the FW update required on the printer 300x side can be reliably executed without being overlooked. In other words, in the data update system 1x of the fifth embodiment, the FW can be appropriately updated on the printer 300x side without depending on the PC 200x.

[0192] 6. Sixth Embodiment Next, a sixth embodiment will be described. In the sixth embodiment, the latest FW version information is stored in the PC 200x, and the updated FW version information is stored in the printer 300x, so that the version check can be performed in either the PC 200x or the printer 300x.

[0193] [6-1. Data update system configuration] The sixth embodiment has a data update system 1x similar to that of the fifth embodiment shown in Fig. 15. Meanwhile, while in the fifth embodiment the update FW version information is stored in the printer 300x, in the sixth embodiment, as described above, the latest FW version information is stored in the PC 200x and the update FW version information is stored in the printer 300x.

[0194] As in the fifth embodiment, the latest version of FWSuite 400 (see FIG. 16) is stored in storage unit 103 of server 100. As in the fifth embodiment, FWSuite 400 includes the latest versions of multiple FWs for operating printer 300x and FW version information 401 indicating the respective versions of the multiple FWs included in FWSuite 400.

[0195] The control unit 202 of the PC 200x periodically communicates with the server 100, and when the FWSuite 400 provided by the server 100 has been updated, the control unit 202 obtains the latest version of the FWSuite 400 from the server 100, and updates the latest FW version information stored in the memory unit 204 with the FW version information 401 contained in the FWSuite 400.

[0196] In addition, when PC 200x is able to communicate with printer 300x (i.e., when printer 300x is connected to network Nt2), it sends the latest version of FWSuite 400 provided by server 100 to printer 300x, and when PC 200x is unable to communicate with printer 300x, it stores the latest version of FWSuite 400 provided by server 100 in USB memory 500 connected to connection unit 206.

[0197] The printer 300x is adapted to update each FW operating the printer 300x using the latest version of FWSuite 400 provided from the server 100 via the PC 200x. Here, when the printer 300x is able to communicate with the PC 200x, the printer 300x acquires the latest version of FWSuite 400 provided from the server 100 by receiving it from the PC 200x. On the other hand, when the printer 300x is unable to communicate with the PC 200x, the printer 300x is adapted to connect a USB memory 500 storing the latest version of FWSuite 400 provided from the server 100 to the connection unit 308, and acquires the latest version of FWSuite 400 from the USB memory 500.

[0198] In addition, when the printer 300x updates the FW using the latest version of the FWSuite 400, the printer 300x updates the update FW version information stored in the update FW version information memory unit 306 using the FW version information 401 included in the FWSuite 400.

[0199] [6-2. Operation of the data update system] Next, the procedure of the operation of the data updating system 1x will be described with reference to the flowchart shown in Fig. 18. Here, as the operation of the data updating system 1x, the procedure of the operation when updating the FW of the printer 300x will be described.

[0200] As a premise, as described above, the control unit 202 of the PC 200x communicates with the server 100 periodically (for example, once a month), and when the FWSuite 400 is updated on the server 100 side, the control unit 202 acquires the FWSuite 400 and updates the latest FW version information stored in the storage unit 204 with the FW version information 401 included in the FWSuite 400. The control unit 202 of the PC 200x also communicates (polls) with the printer 300x periodically (for example, once a day) and acquires active FW version information from the printer 300.

[0201] Furthermore, as described above, the control unit 301 of the printer 300x is configured to update the active FW version information stored in the active FW version information storage unit 304 when the part 300P is added or changed.

[0202] Then, in the first step SP201, the control unit 301 of the printer 300x obtains FW version information 401 from the latest version of FWSuite 400 obtained from the server 100 via the PC 200x, and stores this as updated FW version information in the updated FW version information storage unit 306. Here, the time when the printer 300x obtains the latest version of FWSuite 400 from the server 100 is when the FW is updated.

[0203] After that, in step SP202, the control unit 202 of the PC 200x communicates with the printer 300x (that is, polls) in order to obtain information on the version number of the firmware currently in operation from the printer 300x.

[0204] In the next step SP203, the control unit 202 of the PC 200x judges whether or not there is a response from the printer 300x. If there is a response from the printer 300x, this means that the PC 200x and the printer 300x are in a state where they can communicate with each other via the network Nt2, and the operating FW version information has been obtained from the printer 300x.

[0205] In this case, the control unit 202 of the PC 200x proceeds from step SP203 to step SP204. In step SP204, the control unit 202 of the PC 200x transmits a call to the printer 300x to validate the latest FW version information stored in the memory unit 204 of the PC 200x (i.e., a call to execute a version check on the PC 200x side). In the data update system 1x, while the latest FW version information stored in the memory unit 204 of the PC 200x is valid, the version check is executed on the PC 200x side.

[0206] In the next step SP205, the control unit 202 of the PC 200x compares (checks) the latest FW version information stored in the memory unit 204 with the active FW version information acquired from the printer 300x, and determines whether there is a difference between them.

[0207] If the version check determines that there is no difference between the latest FW version information and the active FW version information, this means that FW update is not necessary. In this case, the control unit 202 of the PC 200x obtains a negative result in step SP205, returns to step SP202, and continues regular communication (polling) with the printer 300x.

[0208] On the other hand, if the version check determines that there is a difference between the latest FW version information and the operating FW version information, this means that the FW needs to be updated. In this case, the control unit 202 of the PC 200x obtains a positive result in step SP205 and proceeds to step SP206. In step SP206, the control unit 202 of the PC 200x acquires the latest version of FWSuite 400 from the server 100 by communicating with the server 100. In the following step SP207, the control unit 202 of the PC 200x transmits the latest version of FWSuite 400 acquired from the server 100 to the printer 300x. At this time, the control unit 202 of the PC 200x also transmits a call to the printer 300x to invalidate the latest FW version information stored in the memory unit 204.

[0209] The control unit 301 of the printer 300x stores the latest version of FWSuite 400 received from the PC 200x in the storage unit 305, and updates each FW operating the printer 300x with the latest version of FWSuite 400. At this time, the control unit 301 of the printer 300x updates the active FW version information stored in the active FW version information storage unit 304 in conjunction with the updating of each FW, and updates the update FW version information stored in the update FW version information storage unit 306 with the FW version information 401 included in the FWSuite 400. The control unit 301 of the printer 300x then deletes the FWSuite 400 used to update the FW from the storage unit 305, and ends the series of operations.

[0210] On the other hand, if the PC 200x attempts to communicate with the printer 300x in step SP202 but receives no response, this means that the PC 200x and the printer 300x are unable to communicate with each other and it is not possible to obtain active FW version information from the printer 300x. In this case, the version check is performed on the printer 300x side, not on the PC 200x side.

[0211] That is, in step SP208 to which the process proceeds when a negative result is obtained in the above-mentioned step SP203, the control unit 301 of the printer 300x, since no call to perform a version check was received from the PC 200x when the power was turned on, compares (checks) the updated FW version information stored in the updated FW version information storage unit 306 with the operating FW version information stored in the operating FW version information storage unit 304, and determines whether there is a difference between them.

[0212] If the version check determines that there is no difference between the update FW version information and the active FW version information, this means that FW update is not necessary. In this case, the control unit 301 of the printer 300x obtains a negative result in step SP208 and ends the series of operations.

[0213] On the other hand, if the version check determines that there is a difference between the update FW version information and the active FW version information, this means that the FW needs to be updated. In this case, the control unit 301 of the printer 300x obtains a positive result in step SP208 and proceeds to step SP209.

[0214] In step SP209, the control unit 301 of the printer 300x displays on the display unit 307 a message urging the user to update the FW using the USB memory 500. Upon seeing this message, the user performs an operation on the PC 200x to store the latest version of FWSuite 400 in the USB memory 500 connected to the connection unit 206. In step SP210, the control unit 202 of the PC 200x communicates with the server 100 in response to this operation, thereby acquiring the latest version of FWSuite 400 from the server 100, and stores the FWSuite 400 in the USB memory 500.

[0215] The user removes the USB memory 500 from the PC 200x, connects it to the connection unit 308 of the printer 300x, and performs an operation to update the FW on the printer 300x. In response to this operation, the control unit 301 of the printer 300x reads the latest version of the FWSuite 400 from the USB memory 500 in step SP210, and updates each FW operating the printer 300x with the latest version of the FWSuite 400. At this time, the control unit 301 of the printer 300x updates the active FW version information stored in the active FW version information storage unit 304 with the update of each FW, and updates the update FW version information stored in the update FW version information storage unit 306 with the FW version information 401 included in the FWSuite 400, and ends the series of operations. The procedure of the operation of the data update system 1x is as described above.

[0216] [6-3. Summary and Effects] As described so far, in the sixth embodiment, the procedure for the operation (data update method) of the data update system 1x that updates the data (FW) of the printer 300x is as follows: first, when the control unit 301 of the printer 300x updates each FW that operates the printer 300 using the latest version of the FWSuite 400 provided by the server 100, the control unit 301 obtains FW version information 401 from the FWSuite 400 and stores this in the update FW version information memory unit 306 as update FW version information.

[0217] In addition, the control unit 301 of the printer 300x stores in an operating FW version information storage unit 304 operating FW version information, which is an example of operating data version information indicating the version of the FW operating in the main body 300M and the version of the FW operating in the part 300P, and when a part 300P is added or changed to the main body 300M of the printer 300x, the operating FW version information stored in the operating FW version information storage unit 304 is updated in accordance with the addition or change of the part 300P.

[0218] When the PC 200x and the printer 300x are able to communicate with each other, the data update system 1x performs a version check between the latest FW version information and the operating FW version information on the PC 200x side, in the same manner as in the first embodiment, and based on the results of the version check, the control unit 301 functioning as an update unit of the printer 300x executes a FW update using the latest version of FWSuite 400 received from the PC 200x by the transmission / reception unit 302 functioning as a receiving unit.

[0219] On the other hand, when the PC 200x and the printer 300x are in a situation where they cannot communicate with each other (that is, when the printer 300x is in an environment where it cannot be connected to a network), the data update system 1x performs a version check on the printer 300x side between the update FW version information and the operating FW version information, and based on the result of the version check, the user stores the latest version of FWSuite 400 provided by the server 100 in a USB memory 500 connected to the connection unit 206 of the PC 200x, and then connects this USB memory 500 to the connection unit 308 of the printer 300x. Then, the control unit 301 of the printer 300x executes a FW update using the latest version of FWSuite 400 stored in the USB memory 500.

[0220] In this way, in the data updating system 1x of the sixth embodiment, it is possible to switch between performing the version number check on the PC 200x side or on the printer 300x side depending on the connection status between the PC 200x and the printer 300x. If the PC 200x and the printer 300x are unable to communicate with each other and the printer 300x performs the version number check, the USB memory 500 storing the latest version of the FWSuite 400 provided by the server 100 is connected to the printer 300x, and the FW of the printer 300x is updated by the FWSuite 400 stored in the USB memory 500.

[0221] In this way, in the data update system 1x of the sixth embodiment, even in a connection state in which the PC 200x and the printer 300x cannot communicate with each other, the printer 300x can check the version number and update the FW, so that the opportunities to update the FW can be increased compared to the first to fifth embodiments. As a result, in the data update system 1x of the sixth embodiment, it is possible to avoid as much as possible a situation in which the printer 300x is used with an old FW.

[0222] [7. Seventh embodiment] Next, a seventh embodiment will be described. The seventh embodiment is an embodiment that allows the FW of the printer 300x to be updated even if the printer 300x is installed in an environment where it cannot be connected to a network.

[0223] [7-1. Data update system configuration] The seventh embodiment has a data update system 1x similar to that of the fifth embodiment shown in FIG. 15, and, similar to the fifth embodiment, stores update FW version information in an update FW version information storage unit 306 of a printer 300x.

[0224] On the other hand, in the seventh embodiment, the printer 300x is not connected to the network Nt2, and the PC 200x and the printer 300x can be directly connected by a cable, short-distance wireless communication, etc. It is assumed that the directly connected PC 200x and the printer 300x can communicate with each other via the transmitting / receiving unit 203 and the transmitting / receiving unit 302.

[0225] As in the fifth embodiment, the latest version of the FWSuite 400 is stored in the storage unit 103 of the server 100. As in the fifth embodiment, the FWSuite 400 includes the latest versions of multiple FWs for operating the printer 300x and FW version information 401 indicating the respective versions of the multiple FWs included in the FWSuite 400.

[0226] Furthermore, control unit 202 of PC 200x communicates with server 100, and when FWSuite 400 provided by server 100 has been updated, obtains the latest version of FWSuite 400 from server 100 and stores FWSuite 400 in storage unit 204. In other words, PC 200x stores FWSuite 400 itself in storage unit 204, and handles FW version information 401 included in FWSuite 400 stored in storage unit 204 as the latest FW version information.

[0227] When the printer 300x is directly connected to the PC 200x, the printer 300x obtains the latest version of the FWSuite 400 provided by the server 100 from the PC 200x, and uses the FWSuite 400 to update each FW that operates the printer 300x.

[0228] [7-2. Operation of the data update system] Next, the procedure of the operation of the data updating system 1x will be described with reference to the flowchart shown in Fig. 19. Here, as the operation of the data updating system 1x, the procedure of the operation when updating the FW of the printer 300x will be described.

[0229] As a premise, the printer 300x is installed in an environment in which it cannot be connected to the networks Nt1 and Nt2. In addition, the control unit 301 of the printer 300x is configured to update the active FW version information stored in the active FW version information storage unit 304 when the part 300P is added or changed.

[0230] Then, in the first step SP301, the control unit 301 of the printer 300x obtains FW version information 401 from the latest version of FWSuite 400 obtained from the directly connected PC 200x, and stores this as updated FW version information in the updated FW version information storage unit 306. Here, the time when the printer 300x obtains the latest version of FWSuite 400 from the PC 200x is when the FW is updated. Here, as an example, it is assumed that after the FW is updated, the user releases the direct connection between the PC 200x and the printer 300x.

[0231] Thereafter, in step SP302, the user again directly connects the PC 200x to the printer 300x to check whether the FW of the printer 300x needs to be updated. Note that since the printer 300x is installed in an environment in which it cannot be connected to the networks Nt1 and Nt2, the PC 200x directly connected to the printer 300x cannot communicate with the server 100. Also, it is assumed that the PC 200x has stored in the storage unit 204 the latest version of the FWSuite 400 obtained from the server 100 when it was in an environment in which it could communicate with the server 100 in the past.

[0232] In the next step SP303, the control unit 202 of the PC 200x acquires the operating FW version information from the printer 300x, compares the operating FW version information with the FW version information 401 (i.e., the latest FW version information) contained in the FWSuite 400 stored in the memory unit 204 (version check), and determines whether there is a difference between them.

[0233] If the version check determines that there is no difference between the latest FW version information and the operating FW version information, this means that FW update is not necessary. In this case, the control unit 202 of the PC 200x obtains a negative result in step SP303 and proceeds to step SP305.

[0234] On the other hand, if the version check determines that there is a difference between the latest FW version information and the active FW version information, this means that the FW needs to be updated. In this case, the control unit 202 of the PC 200x obtains a positive result in step SP303 and proceeds to step SP304. In step SP304, the control unit 202 of the PC 200x transmits the FWSuite 400 stored in the memory unit 204 to the printer 300x.

[0235] The control unit 301 of the printer 300x stores the FWSuite 400 received from the PC 200x in the storage unit 305, and updates each FW operating the printer 300x using the FWSuite 400. At this time, the control unit 301 of the printer 300x updates the active FW version information stored in the active FW version information storage unit 304 in conjunction with the updating of each FW, and updates the update FW version information stored in the update FW version information storage unit 306 using the FW version information 401 included in the FWSuite 400. The control unit 301 of the printer 300x then deletes from the storage unit 305 the FWSuite 400 used to update the FW.

[0236] In step SP305, the control unit 202 of the PC 200x obtains updated FW version information from the printer 300x and stores it in the memory unit 204, regardless of whether the FW was updated in step SP304 (i.e., regardless of whether a positive result was obtained in step SP303).

[0237] In steps SP302 to SP305 described above, since PC 200x is in an environment where it cannot connect to network Nt1 and cannot communicate with server 100, the FWSuite 400 sent from PC 200x to printer 300x is not necessarily the latest version provided by server 100. For this reason, in step SP306, the user moves PC 200x to an environment where it can connect to network Nt1. This enables communication between PC 200x and server 100. In the following step SP307, control unit 202 of PC 200x communicates with server 100 to obtain the latest version of FWSuite 400 from server 100, and stores the FWSuite 400 in memory unit 204.

[0238] In the next step SP308, the control unit 202 of the PC 200x compares (checks) the FW version information 401 (i.e., the latest FW version information) contained in the latest version of the FWSuite 400 obtained from the server 100 with the updated FW version information obtained from the printer 300x, and determines whether there is a difference between them.

[0239] If the version check determines that there is no difference between the latest FW version information and the running FW version information, this means that FW update is not necessary. In this case, the control unit 202 of the PC 200x obtains a negative result in step SP308 and ends the series of operations.

[0240] On the other hand, if the version check determines that there is a difference between the latest FW version information and the updated FW version information, this means that a FW update is necessary. In this case, the control unit 202 of the PC 200x obtains a positive result in step SP308 and proceeds to step SP309. In step SP309, the user again directly connects the PC 200x to the printer 300x.

[0241] In the next step SP310, the control unit 202 of the PC 200x transmits the latest version of the FWSuite 400 stored in the storage unit 204 to the printer 300x. The control unit 301 of the printer 300x stores the FWSuite 400 received from the PC 200x in the storage unit 305, and updates each FW operating the printer 300x with the FWSuite 400. At this time, the control unit 301 of the printer 300x updates the active FW version information stored in the active FW version information storage unit 304 with the update of each FW, and updates the update FW version information stored in the update FW version information storage unit 306 with the FW version information 401 included in the FWSuite 400. Then, the control unit 301 of the printer 300x deletes the FWSuite 400 used for updating the FW from the storage unit 305, and ends the series of operations. The procedure of the operation of the data update system 1x is as described above.

[0242] In this embodiment, in the above-mentioned SP307 and SP308, the control unit 202 of the PC 200x acquires the latest version of the FWSuite 400 from the server 100, and compares (checks) the FW version information 401 included in the FWSuite 400 (i.e., the latest FW version information) with the updated FW version information acquired from the printer 300x. Without being limited to this, the control unit 101 of the server 100 may acquire the updated FW version information from the PC 200x, and compares (checks) the updated FW version information with the FW version information 401 included in the latest version of the FWSuite 400 (i.e., the latest FW version information), and returns the result of the version check to the PC 200. In this case, the control unit 202 of the PC 200x may acquire the latest version of the FWSuite 400 from the server 100 based on the result of the version check acquired from the server 100.

[0243] [7-3. Summary and Effects] As described so far, in the seventh embodiment, the procedure for the operation (data update method) of the data update system 1x that updates the data (FW) of the printer 300x is as follows: first, when the control unit 301 of the printer 300x updates each FW operating the printer 300x using the latest version of the FWSuite 400 provided by the server 100, the control unit 301 obtains FW version information 401 from the FWSuite 400 and stores this in the update FW version information memory unit 306 as update FW version information.

[0244] Furthermore, the control unit 301 of the printer 300x stores in an operating FW version information memory unit 304 operating FW version information indicating the version number of the FW operating in the main body 300M and the version number of the FW operating in the part 300P, and when the part 300P is added or changed to the main body 300M of the printer 300x, the operating FW version information stored in the operating FW version information memory unit 304 is updated in accordance with the addition or change of the part 300P.

[0245] When the printer 300x is installed in an environment where it cannot be connected to a network (networks Nt1 and Nt2), the data update system 1x directly connects the PC 200x to the printer 300x via a cable or short-distance wireless communication. When the PC 200x is directly connected to the printer 300x, the PC 200x performs a version check between the latest FW version information, which is an example of the latest data version information, and the active FW version information. Based on the result of the version check, the control unit 301 functioning as an update unit of the printer 300x executes a FW update using the FWSuite 400 received from the PC 200x by the transmitting / receiving unit 302 functioning as a receiving unit. When the PC 200x is directly connected to the printer 300x, the PC 200x obtains the updated FW version information regardless of the FW update.

[0246] Thereafter, when PC200x is connected to network Nt1, control unit 202 of PC200x obtains the latest version of FWSuite 400 from server 100, performs a version check between the latest FW version information contained in FWSuite 400 and the updated FW version information obtained from printer 300x, and obtains the latest version of FWSuite 400 from server 100 based on the result of the version check.

[0247] Thereafter, the PC 200x is directly connected to the printer 300x again. Here, the control unit 301 functioning as an update unit of the printer 300x executes the FW update again using the latest version of the FWSuite 400 received from the PC 200x by the transmitting / receiving unit 302 functioning as a receiving unit.

[0248] In this way, in the data updating system 1x of the seventh embodiment, even if the printer 300x is installed in an environment where it cannot be connected to a network, the PC 200x can be directly connected to the printer 300x and the FW of the printer 300x can be updated using the FWSuite 400 stored in the PC 200x. Also, when the PC 200x is moved to an environment where it can be connected to a network, the FWSuite 400 stored in the PC 200x is updated with the latest version of the FWSuite 400 obtained from the server 100. In this way, in the data updating system 1x of the seventh embodiment, compared to the first to fifth embodiments, it is possible to increase the opportunities for updating the FW and to avoid, as much as possible, a situation where the printer 300x is used with an old FW.

[0249] 8. Other embodiments [8-1. Another embodiment 1] In the second embodiment described above, when the printer 300 changes the active FW version information when adding or changing a part 300P, the printer 300 adds "*" to the changed portion of the active FW version information as change notification information, and then transmits the active FW version information to the PC 200.

[0250] Without being limited to this, for example, character information other than "*" may be added as change notification information to a change location of the active FW version information, or information indicating whether the active FW version information has been changed may be written in a specific line of the active FW version information. In short, it is sufficient that the PC 200 side is able to identify whether the received active FW version information has been changed due to the addition or change of the component 300P. Also, for example, it may be possible to determine whether the active FW version information has been changed by obtaining a hash value of the active FW version information.

[0251] Furthermore, without being limited to this, instead of the currently operating FW version information, the printer 300 may send to the PC 200 information indicating that the currently operating FW version information has been changed due to the addition or modification of the component 300P (i.e., that the version of the FW operating the component 300P or the type of microcontroller in which the FW operates has changed).

[0252] [8-2. Other embodiment 2] In the first to seventh embodiments described above, after updating the FW on the printer 300 (300x) side, the FWSuite used for the update is deleted, but this is not limited thereto, and the FWSuite used for the update may be stored in the printer 300 (300x).

[0253] Furthermore, in the first to fourth embodiments described above, the FW configuration information analysis unit 205 of the PC 200 analyzes the latest version of the FWSuite acquired from the server 100 to obtain the latest FW version information, and stores this in the storage unit 204. However, as in the fifth to seventh embodiments, the server 100 may provide the PC 200 with the FWSuite 400 including the FW version information 401, and the control unit 202 of the PC 200 may acquire the FW version information 401 from the FWSuite 400 and store this in the storage unit 204 as the latest FW version information.

[0254] Furthermore, in the sixth embodiment described above, when the printer 300x is not connected to the network Nt2 and is unable to communicate with the PC 200x, the printer 300x acquires the latest version of FWSuite 400 provided by the server 100 via the USB memory 500. This is not limiting, and for example, the PC 200x that has acquired the latest version of FWSuite 400 from the server 100 may be directly connected to the printer 300x via a cable or short-distance wireless communication, so that the printer 300x acquires the latest version of FWSuite 400 provided by the server 100.

[0255] Furthermore, in the fifth and sixth embodiments described above, a comparison (version check) between the updated FW version information and the operating FW version information is performed when the printer 300x is powered on. However, this is not limited to the above, and the version check may be performed, for example, when the part change detection unit 303 detects that the part 300P has been added to or changed in the main body 300M.

[0256] [8-3. Other embodiment 3] In the above-described first to seventh embodiments, the present invention is applied to the data update system 1 (1x) that updates FW as data held by the printer 300 (300x), but the present invention is not limited to this and can be applied to a data update system that updates various data held by an information processing device such as the printer 300 (300x). For example, the present invention can be applied to a data update system that updates a data table that stores various setting values ​​held by an information processing device.

[0257] [8-4. Other embodiment 4] Furthermore, in the first to seventh embodiments described above, the PC 200 (200x) acts as an intermediary between the server 100 and the printer 300 (300x), but this is not limited thereto. For example, the printer 300 (300x) may be provided with the functions of the PC 200 (200x) so that the printer 300 (300x) communicates directly with the server 100.

[0258] [8-5. Other embodiment 5] Furthermore, in the above-mentioned first to seventh embodiments, the present invention is applied to the printer 300 (300x) as an information processing device to which detachable parts can be added or changed, but the present invention is not limited to this and can be applied to various information processing devices to which detachable parts can be added or changed. For example, the present invention can be applied to information processing devices such as multifunction peripherals and personal computers.

[0259] Furthermore, in the first to seventh embodiments described above, the present invention is applied to the PC 200 (200x) as a relay device and computer that relays between the server 100 and the printer 300 (300x), but the present invention is not limited to this. For example, the present invention can be applied to various relay devices that can relay between the server 100 and the printer 300 (300x), such as using a shared server or a cloud server with the functions of the PC 200 (200x).

[0260] [8-6. Other embodiment 6] Furthermore, the present invention is not limited to the above-described embodiments, and the scope of application of the present invention extends to embodiments in which some or all of the above-described embodiments are combined in any manner, or in which some of the embodiments are extracted. [Industrial Applicability]

[0261] The present invention can be widely used in, for example, a data update system for updating the firmware of a printer. [Explanation of symbols]

[0262] 1, 1x...data update system, 100...server, 101...control unit, 102...transmitting / receiving unit, 103...memory unit, 200, 200x...PC, 201...application, 202...control unit, 203...transmitting / receiving unit, 204...memory unit, 205...FW configuration information analysis unit, 206...connection unit, 300, 300x...printer, 300M...main unit, 300P...parts, 300P1...fuser, 300P2...optional tray, 301, 311...control unit, 302, 312...transmitting / receiving unit, 303...part change detection unit, 304, 313...operating FW version information memory unit, 305...memory unit, 306...updated FW version information memory unit, 307...display unit, 308...connection unit, 400...FWSuite, 401...version information, Nt1, Nt2...network.

Claims

1. A data update method for an information processing device capable of adding or changing a removable part inside or outside a main body, comprising: When the part is added or changed to a main body of the information processing device, data set reception information used by the information processing device to receive a data set is transmitted with content indicating a state in which reception of the data set is required; when the relay device receives the data set reception information transmitted from the information processing device due to the addition or change of the part, the relay device transmits to the information processing device a data set corresponding to a predetermined version used in updating the data of the main body and updating the data of the removable part from the data sets stored in a server; the information processing device executes updating of the main body data stored in the main body and the part data stored in the part using the received data set; After the information processing device updates the data of the main body and the data of the parts using the received data set, the data set reception information used to receive the data set is changed to a content indicating a state in which reception of the data set is not required.

23. A data updating method comprising:

2. The information processing device updates the data of the main body and the data of the parts using the received data set, and then deletes the data set.

2. The data updating method according to claim 1.

3. The information processing device includes a storage unit that stores the data set reception information, When the part is added or changed to the main body of the information processing device, the information processing device adds data to the data set reception information, thereby changing the data set reception information to a content indicating a state in which reception of the data set is required, and stores the content in the storage unit; The information processing device updates the data of the main body and the data of the parts using the received data set, and then deletes the data from the data set reception information stored in the storage unit, thereby changing the data set reception information to a content indicating a state in which reception of the data set is not required.

3. The data updating method according to claim 1 or 2.

4. When the part is added or changed to the main body of the information processing device, the information processing device changes the data set reception information to an older version number than the version number of the data set used when updating the data of the main body and the data of the part in the information processing device, thereby transmitting the data set reception information with content indicating a state in which reception of the data set is necessary; After the information processing device updates the data of the main body and the data of the parts using the received data set, the data set reception information is set to a version number equal to the version number of the received data set, thereby changing the data set reception information to a content indicating a state in which reception of the data set is not required.

3. The data updating method according to claim 1 or 2.

5. When the part is added or changed to the main body of the information processing device, the information processing device sets the data set reception information to the oldest version number among the version numbers of the data of the main body of the information processing device and the version numbers of the data of the part, the major version number being different from the version number of the data set used when updating the data of the main body and the data of the part in the information processing device, thereby transmitting the data set reception information with content indicating a state in which reception of the data set is necessary; After the information processing device updates the data of the main body and the data of the parts by using the received data set, the data set reception information is set to a major version number that is the same as the version number of the received data set, thereby changing the data set reception information to a content that indicates a state in which reception of the data set is not required.

3. The data updating method according to claim 1 or 2.

6. When the part is added or changed to the main body of the information processing device, the information processing device disguises the data set receiving information to a version number older than the version number of the data set used when updating the data of the main body and the data of the part in the information processing device, and transmits the data set receiving information with content indicating a state in which reception of the data set is necessary; After the information processing device updates the data of the main body and the data of the parts using the received data set, the data set reception information is set to a version number equal to the version number of the received data set, thereby changing the data set reception information to a content indicating a state in which reception of the data set is not required.

5. The data updating method according to claim 4.

7. When the part is added or changed to the main body of the information processing device, the information processing device changes the data set reception information to a version number of the data of the added or changed part, thereby changing the data set reception information to a content indicating a state in which reception of the data set is necessary, and transmits the data set reception information; After the information processing device updates the data of the main body and the data of the part using the received data set, the data set reception information is set to a version number of the data of the part after the update, thereby changing the data set reception information to a content indicating a state in which reception of the data set is not required.

3. The data updating method according to claim 1 or 2.

8. the relay device stores a version number of data that is included in the data set stored in the server and that operates on the main body of the information processing device and a version number of data that is included in the data set stored in the server and that operates on the component; the information processing device stores a version number of data running on the main body and a version number of data running on the component; When the part is added or changed, the information processing device changes the data set reception information to a version number of data operating in the added or changed part, thereby changing the data set reception information to a content indicating a state in which reception of the data set is necessary, and transmits the data set reception information to the relay device; The relay device compares the version number of the data operated by the stored part with the version number of the data operated by the part included in the data set reception information received from the information processing device, The relay device transmits the data set stored in the server to the information processing device when the version number of the data operated by the stored part differs from the version number of the data operated by the part included in the data set reception information received from the information processing device.

3. The data updating method according to claim 1 or 2.

9. the information processing device stores update data version information indicating the version numbers of the data of the main body and the data of the parts included in the data set used to update the data of the main body and the data of the parts, and operating data version information indicating the version numbers of the data operating in the main body and the version numbers of the data operating in the parts; the information processing device updates the operational data version information in response to the addition or change of the part; the information processing device compares the stored update data version information with the operating data version information, and if the update data version information and the operating data version information differ, transmits the data set reception information to the relay device with content indicating a state in which reception of the data set is required; When the relay device receives the data set reception information from the information processing device, the relay device transmits the data set stored in the server to the information processing device.

3. The data updating method according to claim 1 or 2.

10. A data update method for an information processing device capable of adding or changing a removable part inside or outside a main body, comprising: the information processing device stores update data version information indicating the version numbers of the data of the main body and the data of the parts included in a data set used to update the data of the main body and the data of the parts, and operating data version information indicating the version numbers of the data operating in the main body and the version numbers of the data operating in the parts; the information processing device updates the operational data version information in response to the addition or change of the part; the information processing device compares the stored update data version information with the operating data version information, and if the update data version information and the operating data version information differ from each other, receives the data set provided from the server via a relay device; The information processing device updates the data of the main body and the data of the parts using the received data set.

23. A data updating method comprising:

11. When the information processing device is in an environment where a network connection is not possible, an external storage medium storing the data set provided by the server is connected to the information processing device; The information processing device updates the data of the main body and the data of the parts by using the data set stored in the external storage medium.

11. The data updating method according to claim 10.

12. When the information processing device is in an environment where it cannot be connected to a network, the information processing device is directly connected to the relay device; the relay device stores the data set provided by the server, and transmits the data set to the directly connected information processing device; The information processing device updates the data of the main body and the data of the parts using the data set received from the relay device to which the information processing device is directly connected.

11. The data updating method according to claim 10.

13. the information processing device transmits the update data version information to the relay device to which the information processing device is directly connected; the relay device receives the update data version number information from the information processing device to which the relay device is directly connected, and then receives the latest version of the data set from the server when the relay device moves to an environment in which the relay device can be connected to the server via a network; the relay device compares latest data version information indicating the version numbers of the data of the main body and the data of the parts included in the received data set with the update data version information received from the information processing device, and if the latest data version information and the update data version information differ from each other, transmits the data set received from the server to the information processing device directly connected thereto; The information processing device re-updates the data of the main body and the data of the parts using the latest version of the data set received from the relay device to which the information processing device is directly connected.

13. The data updating method according to claim 12.

14. An information processing device capable of adding or changing removable parts on the outside or inside of the main body, a function of, when the part is added or changed, changing data set reception information used for receiving a data set to a content indicating a state in which reception of the data set is required, and transmitting the data set reception information to a relay device that relays between the information processing device and a server; a function of receiving a data set corresponding to a predetermined version used for updating data of the main body and updating data of the removable part from a data set stored in the server, the data set being transmitted from the relay device; performing an update of the body data and the part data using the received data set; a function of updating the data of the main body and the data of the parts using the received data set, and then changing the data set reception information used to receive the data set to a content indicating a state in which reception of the data set is not required; Data update program to have.

15. An information processing device capable of adding or changing removable parts on the outside or inside of the main body, and a computer capable of communicating with a server that stores a data set, a function of receiving data set reception information used by the information processing device to receive the data set, the data set reception information being transmitted from the information processing device due to the addition or change of the part; a function of transmitting, when receiving the data set reception information from the information processing device, a data set corresponding to a predetermined version used in updating the data of the main body and updating the data of the removable part from the data sets stored in the server to the information processing device; Data update program to have.

16. An information processing device in which removable parts can be added or changed to the outside or inside of the main body, a transmission unit that, when the part is added or changed, transmits data set reception information used for receiving a data set to a relay device that relays between the information processing device and a server, the data set reception information indicating a state in which reception of the data set is required; a receiving unit that receives a data set corresponding to a predetermined version used for updating the data of the main body and the data of the removable part from the data set stored in the server, the data set being transmitted from the relay device; an update unit that uses the received data set to update the main body data stored in the main body and the part data stored in the part, and then changes the data set reception information used to receive the data set to content indicating a state in which reception of the data set is not required; An information processing device comprising:

17. A relay device that relays between an information processing device to which a removable part can be added or changed inside or outside a main body and a server that stores a data set, a receiving unit that receives data set reception information used by the information processing device to receive the data set, the data set reception information being transmitted from the information processing device due to the addition or change of the part; a transmitting unit that, when receiving the data set reception information from the information processing device, transmits to the information processing device a data set corresponding to a predetermined version used in updating the data of the main body and updating the data of the removable part from the data sets stored in the server; A relay device comprising:

18. An information processing device capable of adding or changing a removable part to the outside or inside of a main body, a server that stores a data set, and a relay device that relays between the information processing device and the server, The information processing device includes: When the part is added or changed, data set reception information used for receiving the data set is transmitted with content indicating a state in which reception of the data set is required; The relay device is When receiving the data set reception information transmitted from the information processing device due to the addition or change of the part, transmitting to the information processing device, from the data set stored in the server, a data set corresponding to a predetermined version used in data update of the main body and data update of the removable part; The information processing device includes: Using the received data set, the data of the main body stored in the main body and the data of the part stored in the part are updated, and then the data set reception information used to receive the data set is changed to a content indicating a state in which reception of the data set is not required. A data updating system comprising:

Images