JP2012248018A - Management device, management system, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a management device, a management system, and a program capable of improving convenience related to updating of software which is stored in a storage unit provided in an electronic apparatus and is for controlling the electronic apparatus.SOLUTION: When firmware (FW) as one example of software which is stored in a storage unit provided in an electronic apparatus and is for controlling the electronic apparatus is updated to a newer version than a version of the FW which is stored in the storage unit, a management device is configured, in the case that a user policy is given to the new version, to control so that processing for presenting the user policy to a user to obtain approval of the user for updating is executed, and when the approval is obtained from the user after the processing is executed, the management device is configured to control so that the FW which is stored in the storage unit of the electronic apparatus is updated to a FW with the new version (manual update). Also, when the user policy is not given to the new version, the management device is configured to control so that the FW stored in the storage unit is updated to the FW with the new version without executing the processing (automatic update).

Description

  The present invention relates to a management device, a management system, and a program.

  In Patent Document 1, an image forming apparatus, an information server that stores control information such as firmware of the image forming apparatus, and a management server that stores a storage location of control information are connected via a network so that an operator can A system is disclosed in which an image forming apparatus acquires a control information storage destination from a management server, and acquires and updates control information from the storage destination by instructing firmware update from a UI apparatus of the forming apparatus. .

JP 2010-225117 A

  It is an object of the present invention to obtain a management device, a management system, and a program that can be stored in a storage unit provided in an electronic device and can improve convenience related to software update for controlling the electronic device. To do.

  The management device of the invention of claim 1 updates the software for controlling the electronic device stored in the storage unit provided in the electronic device to a newer version than the version of the software. When the terms of use are given, control is performed so that processing for presenting the terms of use to the user and obtaining approval for updating from the user is executed, and from the user after execution of the processing When consent is obtained, the first control means for controlling the software stored in the storage unit to be updated to the new version of software, and the software stored in the storage unit When updating to a newer version than the software version, terms of use are given to the new version. When no includes a second control means for controlling so that said software stored in the storage unit is updated the the new version of the software without executing the process.

  According to a second aspect of the present invention, in the management apparatus according to the first aspect, in the processing, the first control unit further includes functions of the software version and the new version stored in the storage unit. Control is performed so that function difference information indicating the difference is presented to the user together with the usage rule.

  According to a third aspect of the present invention, in the management device according to the first or second aspect, the second control means further includes a case where the software stored in the storage unit is updated to the new version of software. In addition, together with the completion of the update, control is performed so that function difference information indicating a difference in function between the version before the update and the version after the update is presented to the user.

  The management system of the invention of claim 4 is an electronic device provided with a storage unit, wherein the storage unit stores software for controlling the electronic device, and the storage unit stores the software. When updating the software to a newer version than the version of the software, if the new version has a usage agreement, the user is presented with the usage agreement to obtain an approval for the update from the user. The software stored in the storage unit is updated to the new version of the software when consent is obtained from the user after the execution of the process. The first control means for controlling the software and the software stored in the storage unit from the version of the software In the case of updating to a new version, when the terms of use are not given to the new version, the software stored in the storage unit is updated to the new version of software without executing the processing. And a management device having a second control means for controlling.

  According to the invention of claim 5, when the software for controlling the electronic device stored in the storage unit provided in the electronic device is updated to a newer version than the version of the software, the computer is updated to the new version. When the terms of use are given, control is performed so that processing for presenting the terms of use to the user and obtaining approval for updating from the user is executed, and from the user after execution of the processing When consent is obtained, the first control means for controlling the software stored in the storage unit to be updated to the new version of software, and the software stored in the storage unit When updating to a newer version than the software version, the new version has terms of use. When not given, a program for causing the software stored in the storage unit to function as second control means for controlling the software to be updated to the new version without executing the processing. .

  According to the first aspect of the present invention, as compared with the case where the present configuration is not provided, the convenience of updating the software stored in the storage unit provided in the electronic device for controlling the electronic device. Can be improved.

  According to the second aspect of the present invention, it is possible to provide the user with a determination material for determining whether or not to accept the update.

  According to the third aspect of the present invention, even when the software is updated without the user's consent, the user can recognize the difference between the completion of the software update and the function before and after the update.

  According to the invention described in claim 4, as compared with the case where the present configuration is not provided, the convenience of updating the software stored in the storage unit provided in the electronic device for controlling the electronic device. Can be improved.

  According to the invention described in claim 5, as compared with the case where the present configuration is not provided, the convenience of updating the software stored in the storage unit provided in the electronic device for controlling the electronic device. Can be improved.

It is the figure which showed schematic structure of the management system of embodiment. It is a figure which shows the structure of a management apparatus. It is a figure which shows the structure of an electronic device. It is a figure which shows the structure of a terminal device. (A) is a figure which shows an example of a version management table, (B) is a figure which shows an example of the usage rule management table of firmware FW-A. It is a figure which shows an example of the flowchart of an update instruction | indication production | generation process. It is a figure which shows an example of the flowchart of a manual update process. It is a figure which shows the other example of the flowchart of a manual update process. It is a figure which shows an example of the flowchart of an automatic update process. (A) is a flowchart showing a usage agreement inquiry reception process, (B) is a flowchart showing a usage agreement inquiry reception process, and (C) is a flowchart showing a usage agreement / function difference information inquiry reception process. It is a figure which shows an example of the flowchart of an update process in case an electronic device judges whether update is possible and an update method.

  Hereinafter, an embodiment of the present invention will be described with reference to the drawings.

  FIG. 1 is a diagram showing a schematic configuration of a management system 10 according to the present embodiment.

  As shown in FIG. 1, the management device 12, the electronic device 14, and the terminal device 16 are connected via a communication means 18 such as a network and can communicate with each other. The network as an example of the communication means mentioned here may be, for example, the Internet or an intranet.

  The management device 12 performs management related to updating of software (in this case, firmware) for controlling the electronic device 14 stored in a storage unit provided in the electronic device 14. The electronic device 14 is a device that executes firmware stored in the storage unit and provides a predetermined service to the user. The electronic device 14 may be a multifunction device that provides services such as printing, copying, facsimile transmission / reception, and scanning, but is not limited to the multifunction device. Although FIG. 1 illustrates a case where a plurality of electronic devices 14 are connected to the communication unit 18, the number of electronic devices 14 connected to the communication unit 18 may be one. The terminal device 16 is a terminal device operated by a user 20 who uses the electronic device 14.

  Next, the configuration of the management device 12, the electronic device 14, and the terminal device 16 will be described with reference to FIG. 2, FIG. 3, and FIG.

  FIG. 2 is a diagram illustrating the configuration of the management device 12.

  The management device 12 is provided with a CPU 30, a memory 32, an input / output IF 34, a network communication control unit 40, and a storage unit 42, which are connected to each other via a bus 44.

  The CPU 30 executes various programs stored in the program storage area 42a of the storage unit 42. The memory 32 is used as a work memory when the CPU 30 executes a program, for example.

  A display device 36 and an operation device 38 are connected to the input / output IF 34. The display device 36 displays various images under the control of the CPU 30. The operating device 38 is operated by the user 20 and is configured by, for example, a keyboard and buttons.

  The network communication control unit 40 is a control unit for transmitting and receiving information via the communication means 18.

  The storage unit 42 is a nonvolatile rewritable storage unit including a hard disk drive (HDD), a flash memory, or the like. The storage unit 42 is provided with the aforementioned program storage area 42a. In the program storage area 42a, a WEB service program for providing a WEB service including an update management program for managing firmware updates of the electronic device 14 and services such as uploading and downloading data to the storage unit 42 via a network. Etc. are stored.

  Furthermore, the storage unit 42 is provided with a firmware storage area 42b. Firmware of the electronic device 14 is stored in the firmware storage area 42b. When the firmware is corrected by a manufacturer of the electronic device 14 or a new function is added, a new version is released. Each time the firmware is upgraded, a new version of firmware is additionally stored in the firmware storage area 42b without being overwritten. Therefore, the firmware is stored for each version in the firmware storage area 42b of the management apparatus 12. When a plurality of types of firmware are stored and used in the electronic device 14, the plurality of types of firmware are stored for each version. When the electronic device 14 updates the firmware, the firmware stored therein is downloaded to the electronic device 14 via the communication unit 18 and used.

  Note that the firmware may be provided with a usage rule regarding the use of the firmware by the firmware provider. The usage agreement may or may not be granted depending on the firmware version.

  For example, if the newly released version has no function addition or correction to the previous version of firmware, or if it is intended for small-scale defect correction, etc. There are cases where the user agreement is not required, the user agreement is provided when the firmware is provided for a fee, and the user agreement is not provided when the firmware is provided free of charge.

  Such a usage rule file is also stored in the firmware storage area 42b in association with the version information of the firmware when the version of firmware to which the usage rule is assigned is stored in the storage unit 42 of the management apparatus 12. Furthermore, for versions other than the first version of the firmware, function difference information indicating a difference in function from the previous released version is also stored in association with each version information. It can be said that the function difference information is information indicating the content of firmware update.

  Furthermore, the storage unit 42 stores a version management table and a usage rule management table.

  In the version management table, the type and version information of firmware stored and operating in each electronic device 14 are stored in association with each electronic device 14. FIG. 5A shows an example of the version management table. In the example shown in FIG. 5A, the identification information (“FW−” in FIG. 5) is associated with the identification number for identifying each electronic device 14 and identifies each firmware currently stored in the electronic device 14. Version information is stored for each of “A” and “FW-B”).

  In the usage rule management table, information indicating the storage destination of the usage rule and information indicating the storage destination of the function difference information are stored in association with each version of the firmware. The usage rule management table is provided for each firmware. FIG. 5B is a diagram illustrating an example of the usage rule management table of the firmware FW-A. The smaller the number, the older the version.

  The information on the storage destination of the usage rule is information indicating a storage area in which the usage rule is stored. By accessing this storage destination, the usage rule can be acquired and referred to. In the example shown in FIG. 5 (B), for version 1.0 and version 1.1, no usage agreement is given (does not exist), so information indicating the storage location of the usage agreement is not stored, but version 1.2 is used. A rule is attached (exists), and information indicating the storage destination of the use rule is stored in association with version 1.2. The information indicating the storage destination may be, for example, a URL (Uniform Resource Locator) indicating the location where the usage agreement exists.

Further, the storage location information of the functional difference information is information indicating a storage area in which the functional difference information is stored, and the functional difference information can be acquired and referred to by accessing the storage destination. Since the function difference information is information indicating a difference from the previous version, there is no function difference information for the oldest version, that is, the first version.
The information indicating the storage destination may be, for example, a URL (Uniform Resource Locator) indicating the location where the function difference information exists.

  FIG. 3 is a diagram illustrating a configuration of the electronic device 14.

  The electronic device 14 is provided with a CPU 50, a memory 52, an operation panel 54, a network communication control unit 56, a service execution unit 58, and a storage unit 60, which are connected to each other via a bus 62.

  The CPU 50 executes various programs (including an update processing program described later) stored in the storage unit 60. The memory 52 is used as a work memory when the CPU 50 executes a program, for example.

  The operation panel 54 is provided with a display unit 54a made up of an LCD or the like, and an operation receiving unit 54b made up of a numeric keypad, a touch panel, etc. and accepting an operation by a user.

  The network communication control unit 56 is a control unit for transmitting and receiving information via the communication unit 18.

  The service execution unit 58 executes a service provided to the user 20. For example, if the electronic device 14 is a multifunction peripheral, the service execution unit 58 executes services such as printing and scanning.

  The storage unit 60 is a non-volatile rewritable storage unit composed of an HDD (Hard Disk Drive), a flash memory, or the like. Firmware for controlling the electronic device 14 is stored in the storage unit 60. Furthermore, the storage unit 60 stores an update processing program and a WEB service program. The update processing program is a program for performing update processing of firmware stored in the storage unit 60, and includes programs for performing manual update processing and automatic update processing described later. The WEB service program is a program for providing a service related to the WEB (World Wide Web) (for example, a service that makes a WEB page open on the network and can be viewed from other devices). The storage unit 60 also stores information indicating the mail address of the user 20.

  FIG. 4 is a diagram illustrating a configuration of the terminal device 16. The terminal device 16 is provided with a CPU 70, a memory 72, an input / output IF 74, a network communication control unit 80, and a storage unit 82, which are connected to each other via a bus 84.

  The CPU 70 executes various programs stored in the storage unit 82. The memory 72 is used as a work memory when the CPU 70 executes a program, for example.

  A display device 76 and an operation device 78 are connected to the input / output IF 74. The display device 76 displays various images under the control of the CPU 70. The operating device 78 is operated by the user 20, and is configured by, for example, a keyboard and buttons.

  The network communication control unit 80 is a control unit for transmitting and receiving information via the communication unit 18.

  The storage unit 82 is a non-volatile storage unit including a hard disk drive (HDD), a flash memory, or the like. The storage unit 82 stores various programs such as an application program for sending and receiving e-mail and a browser application program for browsing a web page published on the network.

  Next, the operation of the management system according to the present embodiment will be described.

  The management device 12 receives the version information of the firmware stored in the storage unit 60 of the electronic device 14 from the electronic device 14 being managed, so that the firmware version information currently stored in each electronic device 14 Is registered in the version control table. For example, the electronic device 14 may transmit firmware version information stored in the electronic device 14 itself to the management apparatus 12 when the polling function is executed. Alternatively, the management device 12 may communicate with the electronic device 14 at a preset timing to obtain the version information from the electronic device 14.

  In addition, when a new version of firmware is released and the new version firmware, its usage rules, and function difference information are stored in the storage unit 42 of the management device 12, the usage rule management table corresponding to the firmware is used. In addition, the usage rule management table is updated by additionally registering the usage rule storage destination information and the functional difference information storage destination information in association with the new version. In the case of a version to which no terms of use are given, a flag indicating “no terms of use” is registered in the item of storage of the terms of use in the terms of use management table. The update of the usage rule management table may be automatically performed by the management apparatus 12 itself as a trigger when new firmware is stored in the storage unit 42, but may be manually performed by a firmware provider or the like. Good.

  When the user 20 of the electronic device 14 presses the inquiry button displayed on the display unit 54a of the operation panel 54, when a predetermined timing arrives (for example, when the power button is pressed and the power is turned on, etc.) ) Or the update processing program of the electronic device 14 is activated each time a predetermined time elapses, and the electronic device 14 sends an inquiry about whether or not the firmware of the electronic device 14 can be updated to the management apparatus 12.

  When the management device 12 receives an update availability inquiry from the electronic device 14, the update management program is activated and the update instruction generation process shown in FIG. 6 is started. In the following description, for the sake of simplicity of explanation, it is assumed that the firmware stored in the electronic device 14 is one type of FW-A.

  In step 100, the version management table and the usage rule management table are referred to.

  In step 102, it is determined whether or not the firmware can be updated for the electronic device 14 that is the transmission source of the update availability inquiry. Specifically, the firmware version information (current version information) stored in the version management table in association with the identification number of the electronic device 14 that transmitted the update availability inquiry and the usage rule management table are stored. Compare the latest version information. If the current version information is older than the latest version information, it is determined that the update is possible, and if the latest version information and the current version information are equal, it is determined that the update is impossible.

  For example, as shown in FIG. 5A, when the electronic device 14 that transmitted the update availability inquiry is the electronic device 14 with the identification number “AAA”, the FW− stored in the electronic device 14 with the identification number “AAA”. Although the current version information of A is 1.1, as shown in FIG. 5B, when the latest version information is 1.2, it is determined that the update is possible. In addition, when the electronic device 14 that has transmitted the update availability inquiry is the electronic device 14 with the identification number “BBB”, the current version information of the FW-A stored in the electronic device 14 with the identification number “BBB” is 1.2. Since the latest version information is 1.2, it is determined that it cannot be updated.

  If it is determined in step 102 that the update is impossible, an update impossible notification is transmitted to the electronic device 14 that is the transmission source of the update availability inquiry in step 112.

  If it is determined in step 102 that updating is possible, the process proceeds to step 104. In step 104, it is determined whether or not a usage rule is given to a version (hereinafter referred to as an update version) that is newer than the version indicated by the current version information for the updatable firmware. For example, as shown in FIGS. 5A and 5B, when the firmware “FW-A” of the electronic device 14 having the identification number “AAA” is updated to version 1.2, the usage rule management table includes Since the information on the storage destination of the usage agreement is stored in association with version 1.2, it is determined in step 104 that the usage agreement exists (manual update processing is performed). Further, if the storage information of the usage rule is not stored in association with version 1.2 in the usage rule management table, it is determined that there is no usage rule (automatic update processing is performed). That is, here, the update method is determined according to the presence or absence of the usage agreement.

  If it is determined in step 104 that there is a usage rule, the process proceeds to step 106 and a manual update instruction is generated. The manual update instruction is an update instruction for updating the firmware when the user 20 is presented with a usage rule and the user 20 obtains a firmware update consent.

  On the other hand, if it is determined in step 104 that there is no usage agreement, the process proceeds to step 108 and an automatic update instruction is generated. The automatic update instruction is an update instruction that automatically updates the firmware without requiring the user 20 to present the terms of use and accepting the user 20.

  Note that in both the manual update instruction and the automatic update instruction, updateable firmware identification information, version information indicating an updated version of the firmware (in the above example, information indicating “1.2”), and the management device 12 Information indicating the storage location of the updated version file (in the above example, information indicating the storage location of the version 1.2 firmware FW-A, for example, a URL). Update information is included.

  In step 110, an update instruction is transmitted. That is, when a manual update instruction is generated in step 106, the manual update instruction is transmitted to the electronic device 14, and when an automatic update instruction is generated in step 108, the automatic update instruction is transmitted to the electronic device 14. To do.

  When receiving the manual update instruction from the management apparatus 12, the electronic device 14 starts the manual update process shown in FIG.

  In step 200, based on the update information included in the manual update instruction, a usage rule query for acquiring information on the storage destination of the usage rule assigned to the update version of the updatable firmware is generated and sent to the management apparatus 12. Send.

  When receiving the usage agreement inquiry, the management device 12 executes the usage agreement inquiry reception process shown in FIG. In step 400, the information on the storage destination of the usage rule associated with the version information of the update version of the updatable firmware is read from the usage rule management table. In step 402, the information on the storage destination of the read usage rule is electronically stored. Transmit to device 14.

  In step 202, it is determined whether or not information on the storage destination of the usage agreement has been received from the management apparatus 12, and the waiting state is continued until it is determined that it has been received. If it is determined in step 202 that the storage destination information has been received, the process proceeds to step 204.

  In step 204, the usage agreement is acquired from the storage location indicated by the storage location information of the usage agreement.

  In step 206, the acquired usage agreement is displayed on the display unit 54a of the operation panel 54 together with the identification information of the firmware that can be updated and the version information indicating the updated version of the firmware. The display unit 54a also displays a consent button for accepting the update and a non-approval button for not accepting the update. The user 20 determines whether or not to update the firmware in consideration of the displayed terms of use, and inputs the determination result by touching the approval button or the non-approval button displayed on the operation panel 54.

  In step 208, it is determined whether or not the user 20 has accepted the update, and here, whether or not the accept button has been pressed. If the determination in step 208 is affirmative, the process proceeds to step 210 to update the firmware. Specifically, an updated version file is acquired (downloaded) from the storage location indicated by the update information included in the manual update instruction, and the old version firmware stored in the storage unit 60 of the electronic device 14 itself is updated. Replace with the obtained update version firmware and update.

  If a negative determination is made in step 208, the process ends without performing the firmware update process in step 210.

  In the above description, the example in which the usage rule is presented to the user 20 when the electronic device 14 receives the manual update instruction has been described. However, the functional difference information may be presented together with the usage rule. A flowchart of the manual update process in this case is shown in FIG.

  In step 220, based on the update information included in the manual update instruction, the usage rule for acquiring the storage destination information of the usage rule and the storage destination of the functional difference information given to the update version of the updatable firmware A function difference information query is generated and transmitted to the management device 12.

  Upon receiving the usage agreement / function difference information inquiry, the management device 12 executes the usage agreement / function difference information inquiry reception process shown in FIG. In step 600, information on the storage destination of the usage rule associated with the version information of the update version of the updatable firmware is read from the usage rule management table, and in step 602, the version information of the update version of the updatable firmware is supported. The information on the storage destination of the attached function difference information is read from the usage rule management table, and the information on the storage destination of the read usage rule and the storage destination of the function difference information is transmitted to the electronic device 14 in step 604. To do.

  In step 222, it is determined whether information on the storage destination of the terms of use and information on the storage destination of the function difference information are received from the management apparatus 12, and the waiting state is continued until it is determined that the information has been received. If it is determined in step 222 that the information has been received, the process proceeds to step 224.

  In step 224, the usage agreement is acquired from the storage location indicated by the storage location information of the usage agreement. In step 226, the function difference information is acquired from the storage destination indicated by the storage destination information of the function difference information.

  In step 228, the obtained usage agreement and function difference information are displayed on the display unit 54a of the operation panel 54 together with the identification information of the updatable firmware and the version information indicating the updated version of the firmware. The display unit 54a also displays a consent button for accepting the update and a non-approval button for not accepting the update.

  In step 230, it is determined whether or not the user 20 has accepted the update, and here, whether or not the accept button has been pressed. If the determination in step 230 is affirmative, the process proceeds to step 232, and the firmware is updated in the same manner as in step 210.

  On the other hand, if a negative determination is made in step 230, the process ends without performing the firmware update process in step 232.

  In addition, when receiving an automatic update instruction from the management apparatus 12, the electronic device 14 starts the automatic update process illustrated in FIG.

  In step 300, the firmware is updated as in step 210 above.

  In step 302, a function difference information query for acquiring the storage destination information of the function difference information stored for the updated version of the updated firmware is generated and transmitted to the management apparatus 12.

  When receiving the function difference information inquiry, the management device 12 executes a usage agreement inquiry reception process shown in FIG. In step 500, information on the storage destination of the functional difference information associated with the version information of the updated version of the updated firmware is read from the usage rule management table. In step 502, information on the storage destination of the read function difference information. Is transmitted to the electronic device 14.

  In step 304, it is determined whether or not information on the storage destination of the function difference information has been received from the management apparatus 12, and the waiting state is continued until it is determined that the function difference information has been received. If it is determined in step 304 that the storage destination information has been received, the process proceeds to step 306.

  In step 306, the function difference information is acquired from the storage destination indicated by the storage destination information of the function difference information.

  In step 308, the acquired function difference information is displayed on the display unit 54a of the operation panel 54 together with the update completion.

  In this example, the user 20 is notified of the completion of the update through the processing in step 302 and subsequent steps, but step 302 and subsequent steps may be omitted.

  In addition, after the update is completed, the function difference information is not displayed on the display unit 54a of the operation panel 54 together with the update completion, but the function difference information storage destination together with the update completion is displayed at the mail address of the user 20. A mail including the above information may be generated and transmitted. When the user 20 receives the mail by the terminal device 16, the user 20 can not only grasp the completion of the update, but can acquire and browse the functional difference information from the storage destination information included in the mail. In addition, the function difference information itself may be included in the mail instead of the function difference information storage destination information.

  In the above description, a detailed description of the processing example in the case where there are a plurality of update versions and the control in the case where there are a plurality of updatable firmware is omitted, but the control in these cases will be described in detail below.

(Specific example 1)
Here, it is assumed that there is a usage rule for each version of the firmware FW-A stored in the management device 12 as follows.

<FW-A>
1.0 (no terms of use)
1.1 (no terms of use)
1.2 (with terms of use)
2.0 (Terms of use available)-Latest version

  Then, the following processing is performed according to the firmware version information (current version information) stored in the storage unit 60 of the electronic device 14 that has made an inquiry about whether or not the update is possible.

(1) Current version information: 1.1 In this case, the updated versions are 1.2 and 2.0, and there are terms of use for both versions. Accordingly, a manual update instruction is generated, and a usage rule for each version is presented to the user 20 via the operation panel 54 (providing functional difference information together with the usage rule as shown in FIG. 8). Also good).

  Here, when the user 20 accepts the update of both sides, the update is performed in order up to version 2.0, and the version 1.2 is accepted, but when 2.0 is not accepted, the version is updated to version 1.2. In addition, when the firmware has a specification that needs to be updated in order from the old version without skipping the version, if the version 1.2 is not accepted, the firmware is controlled not to be updated. Also, if neither version 1.2 nor 2.0 is agreed, the firmware is controlled not to be updated.

  In some cases, the firmware does not need to be updated in order from the old version, and the specification can be skipped and updated to the new version. In this case, the version 1.2 is not accepted, and if the version 2.0 is accepted, the firmware may be controlled not to be updated, or the version 1.2 may be skipped and controlled to be updated to the version 2.0. Also good.

  In addition, when obtaining the consent of the user 20, it is possible to display the consent button and the non-consent button individually for each version so that the user 20 selects them, but all versions are updated at once. It is also possible to display a batch approval button to be updated and a batch non-approval button not to be batch approved, and press either one of them. When the collective acceptance button is pressed, all the versions of the files are acquired and used for updating as if all the updates of the updated version were accepted. When the batch non-acknowledge button is pressed, the firmware is not updated as the update of all versions is not accepted.

(2) Current version information: 1.0 In this case, the updated versions are 1.1, 1.2, and 2.0. There are no usage rules for version 1.1, but there are usage rules for versions 1.2 and 2.0. Therefore, an automatic update instruction is generated for version 1.1 in which no usage agreement exists, and a manual update instruction is generated for versions 1.2 and 2.0. As described above, the version for which the automatic update instruction has been generated does not require the consent of the user 20, so that the automatic update is performed without obtaining the consent of the user 20 without presenting the terms of use. Processing is executed. Then, after the firmware is updated to version 1.1, the electronic device 14 presents the usage rules for each of versions 1.2 and 2.0 to the user 20 through the operation panel 54 in accordance with the manual update instruction (FIG. The function difference information may be presented together with the terms of use as shown in FIG. The subsequent processing is the same as in the case of (1) above, and therefore the description thereof is omitted.

  As described above, as another example of control in the case where a version having a usage agreement and a non-existing version coexist in a plurality of update versions, there may be at least one version having a usage agreement in the update version. For example, it is necessary to obtain the consent of the user 20 for all updatable versions, and obtain and present the use agreement for the version for which the use agreement exists, and obtain the consent of the user 20 for each update version. Good.

  At that time, as described above, a batch approval button or a batch non-approval button for updating all versions at once may be displayed and either one of them may be pressed, or an individual approval is obtained. As shown, an approval button and a non-acceptance button may be displayed and pressed for each version.

(Specific example 2)
It is assumed that the usage rules for each version of the firmware FW-A stored in the management device 12 are as follows.

<FW-A>
1.0 (no terms of use)
1.1 (no terms of use)
2.0 (with terms of use)
2.1 (no terms of use)-latest version

  When the version information (current version information) of the firmware FW-A stored in the storage unit 60 of the electronic device 14 that has made an inquiry about whether or not update is possible is 1.1, the update version is 2.0 and 2.1. There are conventions, but there is no usage agreement for version 2.1. First, a manual update instruction is generated for version 2.0 where the usage agreement exists. The automatic update instruction is generated after the consent of the user 20 is obtained by the manual update instruction and the FW-A is updated to version 2.0. Thereafter, the same processing as described above may be performed according to each update instruction. As another processing example, if the firmware FW-A has a specification that can be updated by skipping the version, the manual update instruction of version 2.0 is not generated and the automatic update of version 2.1 is performed. An indication may be generated and processed.

(Specific example 3)
Next, when there are a plurality of types of firmware, the control when each of the plurality of types of firmware can be updated will be described. When there are a plurality of types of firmware, it is only necessary to determine and process each firmware individually.

  Here, it is assumed that whether or not there is a usage rule for each version of the two firmwares FW-A and FW-B stored in the management device 12 is as follows.

<FW-A>
1.0 (no terms of use)
1.1 (no terms of use)
1.2 (with terms of use)
2.0 (Terms of use available)-Latest version

<FW-B>
1.0 (no terms of use)
1.1 (no terms of use)
2.0 (with terms of use)
2.1 (no terms of use)-latest version

  Then, the following processing is performed according to the firmware version information (current version information) stored in the storage unit 60 of the electronic device 14 that has made an inquiry about whether or not the update is possible.

(1) Current version information: When FW-A = 1.2 and FW-B = 2.0 In this case, the update version of FW-A is 2.0 and the update version of FW-B is 2.1. There is a usage rule for FW-A version 2.0, but there is no usage rule for version 2.1 of FW-B. Therefore, an automatic update instruction is generated for version 2.1 of FW-B that does not have a usage rule, and a manual update instruction is generated for version 2.0 of FW-A. As described above, the FW-B for which the automatic update instruction has been generated does not require the consent of the user 20, and is updated without obtaining the consent of the user 20 without presenting the terms of use. Automatic update processing is executed. On the other hand, for the FW-A version 2.0, the electronic device 14 obtains the usage rule for the FW-A version 2.0 according to the manual update instruction and presents it to the user 20 via the operation panel 54 (FIG. 8). Functional difference information may be presented along with the terms of use as shown). After the presentation, if it is approved, it will be updated. If it is not approved, it will not be updated.

(2) Current version information: When FW-A = 1.0 and FW-B = 1.1 In this case, the updatable versions of FW-A are 1.1, 1.2, and 2.0, and there are no terms of use for version 1.1 There are terms of use for versions 1.2 and 2.0. Therefore, the processing may be performed in the same manner as the above-described specific example (2).
On the other hand, the updatable versions of FW-B are 2.0 and 2.1, and there are usage rules for version 2.0, but there are no usage rules for version 2.1. Therefore, the processing may be performed in the same manner as in the second specific example.

  According to the above embodiment, for example, the user of the electronic device 14 and the provider who provides the firmware of the electronic device 14 exchange the terms of use when the electronic device 14 is installed or whenever the firmware needs to be updated. Compared with the case of performing the above, the burden on the provider of the firmware of the electronic device 14 and the user is reduced, and convenience is improved. Furthermore, in the above-described embodiment, automatic update processing is executed for a version that does not have a usage rule, and high convenience is obtained, and manual update processing is executed for a version that has a usage rule. Since the user can easily grasp the terms of use, convenience is improved.

[Modification]

  In the above-described embodiment, the management device 12 receives the version information of the firmware stored in the electronic device 14 from the electronic device 14 managed by the management device 12, so that each electronic device 14 receives the firmware version information. Although an example in which the currently stored firmware version information is acquired and registered in the version management table has been described, the present invention is not limited to this. For example, when the electronic device 14 has downloaded the firmware from the management device 12, the management device 12 determines that the firmware of the electronic device 14 has been updated to the downloaded version, and the management device 12 updates the version management table. You may make it do. The management device 12 may be configured not to use a version management table. For example, when an update availability inquiry is transmitted from the electronic device 14 to the management apparatus 12, the firmware version information currently stored in the storage unit 60 of the electronic device 14 may be included in the inquiry and transmitted.

  In the above embodiment, the function difference information is stored for each firmware version, and the storage destination information is registered in the usage rule management table. When the functional difference information is not presented when obtaining consent, and when the functional difference information is not presented to the user 20 when the update is completed, the storage of the functional difference information and registration in the table are not essential.

  In the above embodiment, the case where the management apparatus 12 starts the update instruction generation process triggered by the reception of the update availability inquiry from the electronic device 14 is described as an example. However, the present invention is not limited to this. For example, the update instruction generation process may be started by using a new version of firmware stored in the management apparatus 12 as a trigger. Further, the update instruction generation process may be started not by an inquiry about whether or not update is possible, but by using a polling notification that is performed every day as a trigger.

  Furthermore, in the above-described embodiment, an example has been described in which when an update availability inquiry is received, an automatic or manual update instruction (or an update impossible notification) is generated and transmitted. However, the present invention is not limited to this. For example, the management device 12 creates an automatic or manual update instruction triggered by the fact that a new version of firmware has been stored in the management device 12 and stores it in the storage unit 42 without transmitting it. Thereafter, when an update availability inquiry is received from the electronic device 14 or when a daily polling communication is performed, the stored automatic or manual update instruction (or update impossible notification) is transmitted to the electronic device 14. It may be.

  In the above-described embodiment, the example in which each of the firmware, the usage rule, and the function difference information is stored in the storage unit 42 of the management device 12 has been described. However, the present invention is not limited to this, and is stored in another device. You may make it leave.

  In the above-described embodiment, the management apparatus 12 has been described with respect to an example in which when the electronic device 14 inquires about the usage rule, the management device 12 transmits information on the storage destination of the usage rule to the electronic device 14. It is not limited to. For example, the usage rule file itself may be transmitted to the electronic device 14. The same applies to the inquiry about the function difference information.

  In the above embodiment, the firmware storage destination information is included in both the automatic update instruction and the manual update instruction. However, the present invention is not limited to this. For example, for the manual update instruction, the storage destination information When the user 20 obtains the update approval, the management device 12 receives the notification so that the management device 12 is notified that the electronic device 14 has accepted the update. In this case, the electronic device 14 may be notified of information on the storage destination of the update version file of the firmware that can be updated.

  In the above embodiment, when the electronic device 14 receives a manual update instruction, as shown in FIG. 7, an example is shown in which the terms of use are displayed on the display unit 54 a of the operation panel 54 and presented to the user 20. Although described, it is not limited to this. For example, information on the storage destination of the usage rule may be acquired from the management device 12, and a mail including the information on the storage destination of the usage rule may be generated and transmitted to the mail address of the user 20. Alternatively, when the electronic device 14 receives the manual update instruction, the storage unit of the electronic device 14 acquires the usage rule information from the management device 12 and acquires (downloads) the usage rule from the storage destination. A mail including information (for example, URL) indicating the storage destination storing the usage rule may be generated and transmitted to the mail address of the user 20.

  When the user 20 receives the mail by the terminal device 16, the user 20 can access the URL included in the mail via the Web browser and refer to the usage rule. The user 20 views this, generates a mail indicating whether or not to accept the update, and transmits it to the electronic device 14. The electronic device 14 may update the firmware when consent is obtained by the mail.

  Further, when the electronic device 14 receives the manual update instruction, the electronic device 14 acquires the storage information of the usage rule and the storage of the function difference information from the management device 12, and the email address of the user 20 is obtained. You may make it produce | generate and transmit the mail containing these acquired information. Alternatively, when the electronic device 14 receives the manual update instruction, the storage device 12 acquires the usage rule storage destination information and the functional difference information storage destination information from the management device 12, and acquires (downloads) the usage rule and the functional difference information. Then, it may be stored in the storage unit 60 of the electronic device 14, and a mail including information (for example, URL) indicating the stored storage destination may be generated and transmitted to the mail address of the user 20. .

  When the user 20 receives the mail by the terminal device 16, the user 20 can access the URL included in the mail via the Web browser and refer to the usage rule and the function difference information. The user 20 views this, generates a mail indicating whether or not to accept the update, and transmits it to the electronic device 14. The electronic device 14 may update the firmware when consent is obtained by the mail.

  In the above embodiment, an example has been described in which firmware is updated when the electronic device 14 receives an automatic update instruction. However, the present invention is not limited to this. For example, when an automatic update instruction is received, if a service is being executed by the service execution unit 58 of the electronic device 14, or if it is not being executed but a service reserved for execution exists in the electronic device 14, The firmware may be updated after the execution of the service is completed. Furthermore, after receiving the automatic update instruction, the firmware may be updated when the service is not executed for a predetermined time or when the operation panel 54 is not operated for a predetermined time. .

  Further, after receiving the automatic update instruction, the electronic device 14 updates the firmware when an operation button for turning off the power of the electronic device 14 is pressed, and turns on the power of the electronic device 14 after the update is completed. It may be turned off.

  Further, after receiving the automatic update instruction, the electronic device 14 may update the firmware when the next electronic device 14 is activated (when the power is turned on).

  In addition, after receiving the automatic update instruction, the electronic device 14 may update the firmware at the timing of shifting to a power saving mode in which power to some components of the electronic device 14 is stopped.

  In addition, when the electronic device 14 does not perform the update immediately after receiving the automatic update instruction, it may be configured to be able to set in advance at which timing the update is performed. In this case, the update is performed at a timing set by the user 20 for the electronic device 14 after the electronic device 14 receives the automatic update instruction.

  Furthermore, in the above-described embodiment, an example has been described in which the management device 12 determines whether update is possible and an update method. However, the present invention is not limited to this. For example, the function of the management device 12 may be provided in the electronic device 14 so that the electronic device 14 itself can perform update control by determining whether or not the update is possible and the update method as the management device. Specifically, for example, the management apparatus 12 may hold only the usage rule management table without holding the version management table, and the electronic device 14 may execute the update process shown in FIG.

  In FIG. 11, instead of transmitting an update availability inquiry, the electronic device 14 requests the management apparatus 12 for information on the usage rule management table stored in the management apparatus 12 in step 700. When the electronic device 14 acquires the information of the table, in step 702, the electronic device 14 refers to the acquired information of the table, and stores the information stored in the usage rule management table from the management device 12 and the electronic device 14. The currently stored firmware version information (current version information) is compared. In step 704, it is determined whether firmware can be updated.

  In step 704, if the current version information is older than the latest version information stored in the acquired table, the electronic device 14 determines that it can be updated, and the current version information is stored in the acquired table. If it is equal to the latest version information, it is determined that the update is impossible.

  If it is determined in step 704 that updating is not possible, the updating process is terminated.

  If it is determined in step 704 that the update can be performed, it is determined in step 706 whether or not the update version has a usage rule for the updateable firmware. If an affirmative determination is made in step 706, it is determined in step 708 that a manual update process is to be executed, and a manual update process is executed in step 710. The manual update process is as described with reference to FIGS. 7 and 8. However, since the electronic device 14 has already received the information on the use rule management table from the management device 12, the use rule inquiry and use are performed here. It is not necessary to inquire about the contract / function difference information.

  If a negative determination is made in step 706, it is determined in step 712 that automatic updating is performed, and automatic updating processing is executed in step 714. The automatic update process is as described with reference to FIG. 9, but since the electronic device 14 has already received the information on the usage rule management table from the management apparatus 12, the function difference information inquiry is unnecessary here.

  Note that whether or not update is possible is determined on the management device 12 side, and based on the determination result, the update method may be determined on the electronic device 14 side.

  As described above, even if the determination is performed on the electronic device 14 side, the same effect as that determined on the management device 12 side can be obtained.

DESCRIPTION OF SYMBOLS 10 Management system 12 Management apparatus 14 Electronic device 16 Terminal apparatus 18 Communication means 30 CPU
32 Memory 36 Display device 38 Operating device 40 Network communication control unit 42 Storage unit 50 CPU
52 Memory 54 Operation Panel 56 Network Communication Control Unit 58 Service Execution Unit 60 Storage Unit

Claims (5)

In a case where software for controlling the electronic device stored in a storage unit provided in the electronic device is updated to a version newer than the version of the software, when a usage rule is given to the new version, Control is performed so that a process for presenting a user agreement to the user and obtaining an update consent from the user is executed, and when the approval is obtained from the user after the process is executed, the storage is performed. First control means for controlling the software stored in the unit to be updated to the new version of software;
When the software stored in the storage unit is updated to a version newer than the version of the software, if no terms of use are given to the new version, the software is stored in the storage unit without executing the process. Second control means for controlling the software being updated to the new version of software;
Management device with. In the processing, the first control means further presents to the user functional difference information indicating a functional difference between the software version stored in the storage unit and the new version together with the usage rule. The management device according to claim 1. When the software stored in the storage unit is updated to the new version of the software, the second control unit further updates the functions of the version before the update and the version after the update together with the completion of the update. The management apparatus according to claim 1, wherein control is performed such that function difference information indicating a difference is presented to the user. An electronic device provided with a storage unit, wherein the storage unit stores software for controlling the electronic device, and
In the case where the software stored in the storage unit is updated to a newer version than the version of the software, when a usage rule is given to the new version, the user is presented with the usage rule and the user The software stored in the storage unit is updated to the new version when the user obtains the consent after the execution of the process. In the case of updating the software stored in the storage unit to a version newer than the version of the software, a usage rule is given to the new version. If not, the data is stored in the storage unit without executing the process. Second control means for controlling so as to have the software is updated the the new version of the software, a management apparatus having a,
Management system. Computer
In a case where software for controlling the electronic device stored in a storage unit provided in the electronic device is updated to a version newer than the version of the software, when a usage rule is given to the new version, Control is performed so that a process for presenting a user agreement to the user and obtaining an update consent from the user is executed, and when the approval is obtained from the user after the process is executed, the storage is performed. A first control means for controlling the software stored in the storage unit to be updated to the new version of software, and the software stored in the storage unit to be updated to a version newer than the version of the software And when the new version has no terms of service attached, Second control means for controlling the software stored in the storage unit to be updated to the new version of software without executing
Program to function as.

Images