Information processing device and program

Abstract

To speed up the update of software installed in an information processing apparatus compared to when not referring to a use history of functions included in the software.SOLUTION: An update management server 4 has: a use actual result management part 41 which totals, for each of functions that software mounted on a multifunction machine 1 has, the number of using users after last version upgrade to generate use function information; an update detail information acquisition part 42 which acquires update detail information associated with the model of the multifunction machine 1 having been updated from a management center 3; an update function specification part 43 which specifies only a function being used by the multifunction machine 1 among functions having been updated as an object of update; and an execution control part 44 which instructs the multifunction machine 1 to upgrade the version of the software only for the function, specified as the object of update, as the object of update.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to an information processing device and a program. [Background technology]

[0002] In recent years, software installed in devices has become increasingly multifunctional, and various additional service functions have been added. However, even if software becomes more multifunctional, device users often use the same functions provided by the software repeatedly. Furthermore, there may be functions provided by the software that are never used by any user.

[0003] Incidentally, software is generally updated as needed to fix bugs, improve functions, etc., depending on the contract, etc. This software update is generally called a "version upgrade." [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2014-085759 Summary of the Invention [Problem to be solved by the invention]

[0005] However, in the past, updates were performed uniformly on a software-by-software basis without considering the user's use of the functions included in the software. In other words, even functions that users do not use are updated, so the time required to update functions that users do not use is wasted.

[0006] The present invention aims to improve the time efficiency of software updates compared to when the usage history of functions included in software installed in an information processing device is not referenced. [Means for solving the problem]

[0007] The information processing device according to the present invention includes a processor, and the processor is configured to generate usage history information including usage status of functions within a predetermined period in a device equipped with software having a plurality of functions. Usage record information including the functions used within a specified period and the number of users who used the functions and when the software needs to be updated, the information on the usage history is referenced to determine which of the functions included in the software are being used in the device. identification Control to update death , The function used in the device is a function used by a predetermined number of users within a predetermined period of time. It is characterized by:

[0008] The processor is also characterized in that it acquires update information for the software from the software management center and notifies the administrator of the device of the need to update the software based on the content of the acquired software update information.

[0009] The processor controls updating of functions used in the device in response to instructions from the administrator.

[0010] The processor may also instruct the device to update the functions used in the device at the update date and time instructed by the administrator.

[0013] The processor is also characterized in that it presents the usage history information corresponding to the functions being used in the device to an administrator of the device, and selects, from among the functions being used in the device, a function selected by the administrator who has referred to the usage history information as the function to be updated.

[0014] The software is characterized in that it is firmware.

[0015] The program according to the present invention is a program for storing, in a computer, usage history information including the usage status of functions within a predetermined period in a device equipped with software having multiple functions. Usage record information including the functions used within a specified period and the number of users who used the functionsa function of storing the information in a storage means when the software needs to be updated, and a function of storing the information in a storage means when the software needs to be updated, among the functions included in the software, by referring to the usage history information; Used by a specified number of users within a specified period Function identification This realizes the function of controlling the update. [Effects of the Invention]

[0016] According to the invention of claim 1, the time efficiency of software updates can be improved compared to when the usage history of functions included in the software installed in the information processing device is not referenced. It is also possible to select the functions being used by the user of the device. It is also possible to identify the functions being used in the device according to the user's usage status.

[0017] According to the invention as set forth in claim 2, it is possible to notify the administrator of the need for software update.

[0018] According to the invention as set forth in claim 3, the functions used in the device can be updated under the initiative of the administrator.

[0019] According to the invention as set forth in claim 4, the functions used in the device can be updated at the timing desired by the administrator.

[0022] Claim 5 According to the invention described in the item (1), the administrator can select the function to be updated.

[0023] Claim 6 According to the invention described above, firmware downtime can be reduced.

[0024] Claim 7 According to the invention described in the item (1), it is possible to improve the time efficiency of software updates compared to when the usage history of functions included in software installed in an information processing device is not referenced. Furthermore, it is possible to select functions that are being used by the user of the device, and to identify functions that are being used in the device according to the user's usage status. [Brief explanation of the drawings]

[0025] [Figure 1]1 is a block diagram showing a computer system according to an embodiment of the present invention; [Figure 2] 3 is a diagram illustrating an example of a data configuration of a model master stored in a model master storage unit in the present embodiment. FIG. [Figure 3] 3 is a diagram showing an example of a data configuration of contract information stored in a contract information storage unit according to the present embodiment. FIG. [Figure 4] 3 is a diagram showing an example of a data configuration of administrator information stored in an administrator information storage unit in the present embodiment. FIG. [Figure 5] 10 is a flowchart showing a usage record management process according to the present embodiment. [Figure 6] 3 is a diagram showing an example of the data configuration of a usage history log stored in a usage history log storage unit in the present embodiment. FIG. [Figure 7] 3 is a diagram showing an example of a data configuration of use function information stored in a use function information storage unit in the present embodiment. FIG. [Figure 8] 10 is a flowchart showing a setup process for version upgrade according to the present embodiment. [Figure 9] FIG. 2 is a diagram showing an example of a data configuration of update content information in the present embodiment. [Figure 10] 10A and 10B are diagrams for explaining a method for determining whether an upgrade is necessary in the present embodiment. [Figure 11] FIG. 10 is a diagram showing an example of a notification screen according to the present embodiment. [Figure 12] FIG. 10 is a diagram illustrating an example of a firmware update setting list screen according to the present embodiment. [Figure 13] FIG. 10 is a diagram illustrating an example of a firmware update setting details screen according to the present embodiment. [Figure 14] 3 is a diagram showing an example of a data configuration of reservation information stored in a reservation information storage unit in the present embodiment. FIG. [Figure 15] 10 is a flowchart showing an execution control process for version upgrade according to the present embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0026] Hereinafter, preferred embodiments of the present invention will be described with reference to the drawings.

[0027] Fig. 1 is a block diagram showing a computer system according to this embodiment. Fig. 1 shows a multifunction device 1, an administrator terminal 2, a management center 3, and an update management server 4. The update management server 4 is connected to the multifunction device 1, the administrator terminal 2, and the management center 3 via a network (not shown), enabling bidirectional communication. For example, the multifunction device 1, the administrator terminal 2, and the update management server 4 are installed in the same facility, such as a business establishment, and are connected to a LAN (Local Area Network). The management center 3 and the update management server 4 are connected via the Internet.

[0028] The multifunction peripheral 1 is an example of a device that incorporates the software of the present invention. The multifunction peripheral 1 is used, for example, by employees of a business establishment. The multifunction peripheral 1 is a form of image forming device, and is a device that incorporates various functions such as printing, copying, and scanning, and has a built-in computer. Therefore, the multifunction peripheral 1 is equipped with storage means such as a CPU, ROM, RAM, and hard disk drive, a user interface such as an operation panel, a network interface, and the like. The multifunction peripheral 1 is also equipped with a scanner and a printer to realize various functions such as printing. Furthermore, the multifunction peripheral 1 may be configured by connecting additional devices to realize additional functions such as a finisher function, a puncher function, and an Internet fax function.

[0029] For the sake of convenience, the present embodiment will be described assuming that only one piece of software is installed in each multifunction device 1. If the multifunction device 1 is equipped with multiple pieces of software, the process described below can be executed for each piece of software. Each piece of software has one or more functions. The user selects and executes one of the functions possessed by the software. In this way, in the present embodiment, the software is executed on a function-by-function basis, so that when the software is executed, only one function selected by the user is actually executed. Of course, it is conceivable that multiple functions may operate in conjunction with each other, but in the present embodiment, it is assumed that only the function selected by the user is used.

[0030] In this embodiment, the terms "use" of a function and "execution" of a function are used synonymously. Also, in this embodiment, the upgrade is performed on a function-by-function basis, and software is updated by upgrading the functions. In this embodiment, the terms "upgrade" and "update" of software or functions are used synonymously.

[0031] The multifunction device 1 in this embodiment has a function execution unit 11, a function use notification unit 12, and a version upgrade processing unit 13. Note that components not used in the description of this embodiment are omitted from the figure. The function execution unit 11 executes a function specified by a user. When the function execution unit 11 executes a function and the function use notification unit 12 detects that the function has been used by the user, the function execution unit 11 notifies the update management server 4 that the function has been used in the multifunction device 1. In this embodiment, the function provided to the user is realized by an application that is the target of a version upgrade. The version upgrade processing unit 13 updates the software by performing a version upgrade of the function, and notifies the update management server 4 that the version upgrade has been performed. Each of the components 11 to 13 is realized by cooperative operation between a computer installed in the multifunction device 1 and a program running on a CPU installed in the computer.

[0032] The administrator terminal 2 is an information processing device used by an administrator of the software running on the multifunction device 1. The administrator terminal 2 can be realized by a general-purpose hardware configuration that has existed for some time, such as a personal computer (PC). That is, the administrator terminal 2 includes a CPU, ROM, RAM, storage means such as a hard disk drive, user interfaces such as a mouse, keyboard, and display, a network interface, etc.

[0033] While the multifunction device 1, administrator terminal 2, and update management server 4 are basically installed within the same business facility, the management center 3 is located outside the business facility and is a facility that provides information about software updates to business facilities in various locations. In particular, the management center 3 in this embodiment centrally manages information about software updates provided to business facilities using a server or the like. In this embodiment, the "management center 3" refers not only to the facility but also to the "server installed in the management center 3."

[0034] The management center 3 has an update content information providing unit 31 and an update file providing unit 32. In response to an inquiry from the update management server 4, if update content information corresponding to the inquired model exists, the update content information providing unit 31 provides the update content information by transmitting the update content information. "Update content information" is prepared for each model, and is generated when software corresponding to that model is updated. The "update content information" includes the updated content. More strictly speaking, software updates are performed on a function-by-function basis, so when at least one function of the model is updated, update content information is generated. The generated update content information includes update content information related to updated functions, and does not generally include information related to functions that have not been updated, since they have not been updated.

[0035] The update file providing unit 32 provides an update file in response to a transmission request from the update management server 4. An "update file" is a program that is executed to upgrade a function.

[0036] The update management server 4 is a server computer provided to manage software upgrades for one or more multifunction peripherals 1 installed within a business establishment. The update management server 4 in this embodiment can be realized with the hardware configuration of a conventional general-purpose server computer. That is, the update management server 4 includes a CPU, ROM, RAM, storage means such as a hard disk drive, and a network interface. It may also include a user interface as needed.

[0037] 1, the update management server 4 in this embodiment includes a usage record management unit 41, an update content information acquisition unit 42, an update function identification unit 43, an execution control unit 44, a model master storage unit 51, a contract information storage unit 52, an administrator information storage unit 53, a usage history log accumulation unit 54, a used function information storage unit 55, and a reservation information storage unit 56. Note that components not used in the description of this embodiment are omitted from the figure.

[0038] The usage history management unit 41 generates a usage history log relating to the usage history of the function from the function usage notification information sent from the multifunction device 1 and stores it in the usage history log storage unit 54. At the same time, by aggregating the usage history logs within a predetermined period, the usage history management unit 41 generates usage function information including the usage status of the function within the predetermined period and sets and registers it in the usage function information storage unit 55.

[0039] The update content information acquisition unit 42 designates a model and inquires of the management center 3 about the presence or absence of update content information corresponding to that model. In addition, the update content information acquisition unit 42 acquires the update content information sent from the management center 3 in response to the inquiry.

[0040] The update function identification unit 43 refers to the update content information sent from the management center 3 and identifies functions that are actually used in the multifunction device 1, among the functions included in the software installed in the multifunction device 1, as functions to be upgraded. The update function identification unit 43 has an administrator cooperation processing unit 431 and a reservation processing unit 432. The administrator cooperation processing unit 431 interacts with an administrator who uses the administrator terminal 2, allowing the administrator to specify functions to actually be upgraded, among the functions included in the software installed in the multifunction device 1 managed by the administrator. The reservation processing unit 432 generates reservation information and registers it in the reservation information storage unit 56 by executing reservation processing for the version upgrade process.

[0041] The execution control unit 44 obtains the update files required for the upgrade from the management center 3 in accordance with the reservation information registered in the reservation information storage unit 56, and instructs the execution of the upgrade by transmitting the files to the multifunction device 1. Furthermore, when the execution control unit 44 receives a notification from the multifunction device 1 that the upgrade has been completed, it reports this to the administrator terminal 2.

[0042] Fig. 2 is a diagram showing an example of the data configuration of the model master stored in the model master storage unit 51 in this embodiment. The model master is set by associating installed functions with model identification information (hereinafter referred to as "model ID") as information for specifying the model of the multifunction device 1. The model name or the like may be used as information for specifying the model. A list of functions installed in the model is set as the installed functions. As shown in Fig. 2, the installed functions differ depending on the model.

[0043] FIG. 3 is a diagram showing an example of the data configuration of contract information stored in the contract information storage unit 52 in this embodiment. In this embodiment, the multifunction peripheral 1 is installed in a business establishment upon the conclusion of a contract, and the contract information is information related to that contract. The contract information is set by associating a device ID, a model ID, and an administrator ID with a contract number that identifies the contract. The device ID is set with device identification information that identifies the multifunction peripheral 1 installed in the business establishment under the contract. For example, the serial number or name of the multifunction peripheral 1 may be used as the device ID. As described above, the model ID is set with information that identifies the model of the device. The administrator ID is set with identification information of the administrator (hereinafter referred to as "administrator ID") that identifies the administrator of the multifunction peripheral 1 installed in the business establishment under the contract.

[0044] FIG. 4 is a diagram showing an example of the data configuration of administrator information stored in administrator information storage unit 53 in this embodiment. The administrator information includes information about the administrator of multifunction device 1. In this embodiment, the administrator information is set by associating an administrator ID, which serves as identification information for identifying the administrator, with an administrator name, a contract number, and contact information. The administrator name is set as the name of the administrator. The contract number is set as the contract number under which the administrator has become the administrator of multifunction device 1. The contact information is set as information about how to contact the administrator. In this embodiment, it is assumed that the administrator will be notified by email, so an email address is set as the contact information.

[0045] The other storage units 54 to 56 store information generated in the process of the processing, and will be explained together with the explanation of the processing.

[0046] Each of the components 41 to 44 in the update management server 4 is realized by cooperative operation between the computer that forms the update management server 4 and a program running on a CPU installed in the computer. Each of the storage means 51 to 56 is realized by an HDD installed in the update management server 4. Alternatively, RAM or external storage means may be used via a network.

[0047] Furthermore, the programs used in the present embodiment can be provided not only by communication means, but also by being stored in a computer-readable recording medium such as a CD-ROM or USB memory. The programs provided from the communication means or recording medium are installed in a computer, and various processes are realized by the computer's CPU sequentially executing the programs.

[0048] When an administrator wishes to upgrade the software installed in the multifunction device 1, the administrator operates the multifunction device 1 to download an update file from the management center 3 and perform the upgrade. Conventionally, upgrades were performed collectively on a software-by-software basis, so even if the software contained functions that the user of the multifunction device 1 did not use, those functions were also upgraded. However, there is no point in upgrading functions that are not used, and in fact, the time required to upgrade functions that the user does not use is a waste of time.

[0049] Therefore, in this embodiment, an update management server 4 is provided between the multifunction device 1 and the management center 3, and when upgrading the software of the multifunction device 1, the update management server 4 refers to the usage status of the functions in the multifunction device 1 and selects functions to be upgraded from among the functions included in the software. In other words, functions that are not used by the user are excluded from the upgrade, thereby improving time efficiency.

[0050] Next, the operation of this embodiment will be described. First, the usage record management process that the update management server 4 performs to grasp the usage status of the functions in the multifunction device 1 will be described with reference to the flowchart shown in FIG.

[0051] In the multifunction device 1, the function execution unit 11 executes a function selected by a user in response to a user operation. When the function usage notification unit 12 detects that the user has used a function, it notifies the update management server 4 that the function has been used by transmitting function usage notification information.

[0052] When the usage history management unit 41 in the update management server 4 receives the function usage notification information sent from the multifunction device 1 (step 111), it generates a usage history log and registers it in the usage history log accumulation unit 54 (step 112). In addition, the usage history management unit 41 updates the used function information so that the usage status of the function that can be identified by the received function usage notification information is reflected in the used function information (step 113).

[0053] FIG. 6 is a diagram showing an example of the data configuration of a usage history log stored in the usage history log storage unit 54 in this embodiment. The usage history log is information indicating the usage record of functions in each multifunction device 1, and is configured by associating date and time, device ID, model ID, function ID, and user ID. The date and time is set to the start date and time when the function was used. The device ID is set to the device ID of the multifunction device 1 on which the function was used. The model ID is set to the model ID that identifies the model of the multifunction device 1. The function ID is set to the function ID that identifies the function used. And the user ID is set to identification information of the user who used the function (hereinafter referred to as "user ID"). It is sufficient that the usage history log storage unit 54 stores at least usage history logs corresponding to the use of functions within a "predetermined period" described below.

[0054] 7 is a diagram showing an example of the data configuration of used function information stored in the used function information storage unit 55 in this embodiment. The used function information is information indicating the usage status of a function, and is set by referring to the usage history log, so it is also information on the actual usage record of the function.

[0055] The used function information is set by associating a device ID and a model ID with a usage status. The device ID is set to the device ID of the multifunction device 1 on which the function was used. The model ID is set to a model ID that identifies the model of the multifunction device 1. The usage status is set to the usage status of each function used in the multifunction device 1. Specifically, for each function installed in the multifunction device 1, the most recent date and number of users are set as the usage status. The most recent date and time on which the function was used are set as the most recent date and time on which the function was used. The number of users is an example of an indicator of the usage status of the function. The number of users is the number of users who used the function, obtained by aggregating usage history logs generated according to the use of the function within a predetermined period for each multifunction device 1 and function, and can therefore also be considered as performance information regarding function usage. Examples of indicators of usage status include usage frequency and usage time. In this embodiment, the "number of users" who used the function is used as an indicator of usage frequency. The total number of users who used the function within a predetermined period is set to the number of users. The "number of users" here can also be considered as the "number of times" it was used.

[0056] The functions to be set in the usage status may be set by referring to the function master and looking up the functions installed in the multifunction device in advance, or if a function included in the function usage notification information received from the multifunction device 1 is not set in the usage function information, the function included in the received function usage notification information may be set and registered to be added to the usage function information.

[0057] Furthermore, the period for which the number of users is tallied, i.e., the above-mentioned "predetermined period," can be set as appropriate. In this embodiment, the "number of users" counter is initialized when an upgrade is implemented. In other words, the number of users included in the usage status is set to a value indicating the number of users since the most recent upgrade. Note that, although the number of users is set to the number of users since the most recent upgrade here, it may also be set to a fixed period, for example, at the end of a weekend or the end of the month, so as to indicate the number of users over a week or month.

[0058] In addition, in this embodiment, only one index value, "the number of users" since the most recent upgrade, is included, but the "number of users" for multiple periods, such as the number of users for each consecutive week, may be included in the used function information as a predetermined period, so that the transition in the number of users can be understood. Also, the used function information may include multiple indexes that use different time periods as aggregation units, such as the number of users since the most recent upgrade and the number of users in the most recent week.

[0059] As will be described in detail later, the function usage information is one piece of information provided to the administrator. The administrator may use the provided function usage information as a judgment indicator to select functions to be upgraded. Therefore, as described above, the function usage information may include a variety of information indicating usage status.

[0060] As described above, in this embodiment, log recording and updating of used function information are repeatedly performed every time function usage notification information is received from the multifunction device 1. Each multifunction device 1 may transmit function usage notification information every time a function is used, or may periodically transmit function usage notification information related to the use of functions on that day collectively to the update management server 4 at a predetermined timing, for example, at the end of the day.

[0061] The upgrade setup process that the update management server 4 performs after receiving function usage notification information from all the multifunction devices 1 will be described below with reference to the flowchart shown in FIG.

[0062] As described above, once it is confirmed that one day's worth of function usage notification information has been received from all multifunction devices 1, the update content information acquisition unit 42 in the update management server 4 inquires of the management center 3 about whether or not there have been any updates for all models registered in the model master (step 121). At this time, it is preferable to send the date and time of the most recent inquiry for each model, and inquire about whether or not there have been any updates since that date and time.

[0063] The update content information providing unit 31 in the management center 3 checks whether or not there is an update for each of the inquired models. If there is an update, the update content information corresponding to the updated model is provided to the update content information acquiring unit 42.

[0064] The update content information acquisition unit 42 in the update management server 4 acquires the update content information sent in response to the inquiry (step 122).

[0065] FIG. 9 is a diagram showing an example of update content information in this embodiment. In this embodiment, since an inquiry is made to models registered in the model master, the update content information is shown in a table format corresponding to the model master shown in FIG. 2. In FIG. 9, blank spaces indicate that there is no update content information for the corresponding function. According to the update content information shown in FIG. 9, since there is update content information for the finisher function, scan function, and auto feed function, it can be seen that these functions have been updated since the previous inquiry. Furthermore, update content information is not generated for a model with a model ID of "m003" that does not include any of the finisher function, scan function, and auto feed function, and therefore is not sent from the management center 3. By being presented with the update content information, an administrator or the like can know what updates have been made to the updated functions.

[0066] Next, the update function identification unit 43 determines which functions have been used within a predetermined period and whether or not the functions have been used for each multifunction device 1 (step 123). The update function identification unit 43 determines whether or not a function has been used by referring to the used function information, but here, the example of the number of users in the used function information shown in Fig. 7 will be described assuming that it indicates the number of users since the most recent version upgrade.

[0067] It is extremely easy to determine whether a function is present or absent by checking whether the "number of people" is 0 or not. For example, in Fig. 7, the number of people for function 3 of the multifunction device 1 with the device ID "mfp05" (hereinafter referred to as "multifunction device mfp05", and the same applies to other multifunction devices 1) is "0", so it can be determined that this function 3 is "not in use". The other functions are 1 or more, so it can be determined that they are "in use".

[0068] However, if a long time has passed since the most recent version upgrade, even if the number of users is not zero, it may be acceptable to consider the function as not being used if it is extremely low. In such cases, a predetermined threshold value for determining whether or not the function is being used may be set in advance, and each "number of users" included in the used function information may be compared with the threshold value. If the number is equal to or greater than the threshold value, it is determined that the function is being used, and if the number is less than the threshold value, it is determined that the function is not being used. The threshold value may be set for each function or for each multifunction device 1.

[0069] In addition, if multiple indicators indicating usage status are set, such as the number of users since the most recent version upgrade and the number of users in the most recent week, conditions such as a judgment formula that combines these can be set to determine whether or not a function is being used.

[0070] In this way, the update function identification unit 43 determines whether or not each function installed in each multifunction device 1 is in use. Then, the update function identification unit 43 determines whether or not an upgrade is necessary for each multifunction device 1 as follows.

[0071] Fig. 10 is a diagram for explaining a method for determining whether an upgrade is necessary. Fig. 10 focuses on one function of a certain multifunction device 1. In the table shown in Fig. 10, "function usage" is the result of determination by the update function identification unit 43, as described above. "Function update content information" indicates whether or not it has been obtained from the management center 3.

[0072] Here, if a function is being used (i.e., "function use" is "yes" in FIG. 10) and there is update content information corresponding to that function (i.e., "function update content information" is "yes" in FIG. 10), then that function is being used by the user and should naturally be upgraded. Therefore, that function is subject to an upgrade (i.e., "upgrade" is "needed" in FIG. 10).

[0073] Furthermore, if a function is being used but there is no update content information corresponding to that function (i.e., in FIG. 10, "update content information for function" is "none"), then naturally an upgrade is not possible because no update file is prepared for that function. Therefore, that function is not subject to an upgrade (i.e., in FIG. 10, "upgrade" is "not required").

[0074] Also, if a function is not being used (i.e., "function use" is "no" in FIG. 10), and there is no update content information corresponding to that function, then naturally there is no need to upgrade that function. Therefore, that function is not subject to upgrade.

[0075] This corresponds to the determination of whether an upgrade is necessary, which is a feature of this embodiment, but even if update content information corresponding to a function exists, if that function is not being used, there is no point in upgrading that function. Therefore, that function is not subject to an upgrade.

[0076] 10 for each function of each multifunction device 1. Next, the update function identification unit 43 executes the following process for each multifunction device 1 based on the determination of whether an upgrade is required as shown in FIG.

[0077] First, attention is focused on one unprocessed multifunction device 1. If a software upgrade is not required for this multifunction device 1 (N in step 124), processing moves on to the next unprocessed multifunction device 1. If a software upgrade is required for this multifunction device 1 (Y in step 124), in other words, if at least one function included in the software installed in the multifunction device 1 needs to be upgraded, the administrator of the multifunction device 1 is notified of the need for a software upgrade by sending an email (step 125). The administrator of the multifunction device 1 and the email address can be identified by referencing the contract information and administrator information.

[0078] 11 is a diagram showing an example of a notification screen that is sent to the administrator in this embodiment and displayed on the administrator terminal 2. The administrator opens the notification message sent by email, for example, and the notification message shown in FIG. 11 is displayed on the screen.

[0079] By referring to this notification, the administrator will know that a software (firmware in the example shown in FIG. 11) upgrade is necessary, and to set up the upgrade, the administrator selects hyperlink 61 on the screen. An example of a firmware update setting list screen displayed on the screen of the administrator terminal 2 in response to this selection is shown in FIG. 12.

[0080] The administrator cooperation processing unit 431 displays the firmware update setting list screen on the screen of the administrator terminal 2 in response to selection of the hyperlink 61. For example, a file for screen display may be acquired and displayed by a browser installed in the administrator terminal 2.

[0081] The management target display area 62 on the firmware update setting list screen displays, as additional information, the model and multifunction device 1 that the administrator manages. The update information display area 63 displays the following information: The model to be updated, the functions to be updated in that model, and the multifunction device 1 corresponding to that model are displayed. The functions to be updated are displayed in association with the update content for that function obtained from the update content information acquired from the management center 3. For each multifunction device 1 corresponding to that model, the result of whether or not the function has been used, as determined in step 123, is displayed as a "usage history." Here, "no usage history" corresponds to "no function usage" in FIG. 10. Therefore, a multifunction device 1 with a "no usage history" is not a target for a version upgrade. On the other hand, a "usage history" of "yes" corresponds to "yes function usage" in FIG. 10. Therefore, according to the display example in FIG. 12, the multifunction devices mfp01 and mfp10 are candidates for a version upgrade. Even if the "usage history" is "yes," if there is no update content information corresponding to the function, the function will not be subject to a version upgrade.

[0082] In this embodiment, the device ID 64 of the multifunction device 1 is underlined to indicate that the administrator can select it. When the administrator selects one of the device IDs 64, the administrator cooperation processing unit 431 displays an upgrade setting screen for the multifunction device 1 that can be upgraded. Here, FIG. 13 shows an example of the firmware update setting details screen that is displayed when the device ID 64 corresponding to the multifunction device mfp01 is selected in FIG. 11. Note that the "upgrade setting screen" mentioned above refers to the "firmware update setting details screen."

[0083] As explained with reference to Fig. 10, the version upgrade setting screen is displayed only for a multifunction device 1 that has a function in use and for which update content information exists. If a device ID 64 corresponding to another multifunction device 1 is selected, information about that multifunction device 1 is presented to the administrator, rather than information for setting the version upgrade. For example, the function usage information shown in Fig. 7 is presented to the administrator. Alternatively, even if there was no usage during the period for which the function usage information was generated, there may have been usage before that, so the usage history log may be referenced to present the usage status before that.

[0084] In response to the administrator's selection of the device ID 64, the administrator collaboration processing unit 431 displays a firmware update setting details screen for version upgrade settings for the multifunction peripheral 1 with the selected device ID (in this example, the multifunction peripheral mfp01) on the screen of the administrator terminal 2. FIG. 13 shows an information display area 65 that displays information about the target multifunction peripheral 1, the model of the multifunction peripheral 1, and firmware, and a setting area 66 for version upgrade settings. The setting area 66 includes a selection area for functions to be upgraded and an area for setting a reservation for the version upgrade. According to the display example shown in FIG. 13, the finisher function of the multifunction peripheral mfp01 is not being used and is therefore not subject to version upgrade. On the other hand, functions that are being used and therefore are candidates for version upgrade are displayed with associated check boxes 67. The administrator checks the check boxes 67 corresponding to the functions to be upgraded. Information set in the used function information, specifically the number of users of the function, is displayed in association with each function, so the administrator can use the function usage information as a criterion for determining whether to check the check boxes 67.

[0085] The administrator then selects whether or not to perform the upgrade by selecting a radio box. If the upgrade is to be performed, the administrator then specifies the date and time for the upgrade to be performed on the multifunction device 1. The administrator then reserves the execution of the upgrade by selecting the reservation button 68. By having the administrator perform the above-described instruction operations, the administrator cooperation processing unit 431 sets the software upgrade for each multifunction device 1 (step 126).

[0086] Furthermore, if you want to make a similar reservation for upgrading another multifunction device 1, or if you want to check information about a device that is not subject to upgrading, select the back button 69 to display the firmware update setting list screen shown in Figure 12 again, and select another device ID 64.

[0087] 11 to 13, in response to instructions from the administrator via the screens, the administrator interaction processing unit 431 controls software updates for each multifunction device 1. As described above, even if a function is in use and update content information is available, the administrator interaction processing unit 431 selects only functions selected by the administrator by checking the checkboxes 67 as update targets.

[0088] Here, since the process is repeatedly executed for each multifunction device 1 (step 124), instructions are accepted for one multifunction device 1, as shown in Figures 11 and 13. However, in Figure 12, in consideration of the convenience of the administrator or the efficiency of processing, all of the multifunction devices 1 managed by one administrator are displayed together in the update information display area 63. Therefore, in subsequent processing, the multifunction device 1 displayed in the update information display area 63 is treated as a processed multifunction device 1.

[0089] When the administrator issues a reservation instruction by selecting the reservation button 68, the reservation processing unit 432 generates reservation information according to the settings made on the firmware update setting details screen and registers it in the reservation information storage unit 56 (step 127).

[0090] The above-described process is performed for each multifunction device 1, and when the process is completed for all multifunction devices 1 (Y in step 128), the update management server 4 ends the version upgrade setup process.

[0091] FIG. 14 is a diagram showing an example of the data configuration of reservation information stored in the reservation information storage unit 56 in this embodiment. The reservation information is generated in response to a reservation set by an administrator. The reservation information is set by associating an update date and time, a device ID, and a function. The update date and time is set to the date and time set by the administrator when software is updated by starting the execution of an upgrade. The device ID is set to the device ID of the multifunction device 1 to be upgraded. The function is set to the function to be upgraded when the administrator checks the check box 67 on the firmware update setting details screen.

[0092] The execution control process of the upgrade performed by the execution control unit 44 of the update management server 4 will be described below with reference to the flowchart shown in FIG.

[0093] The execution control unit 44 operates continuously and executes the process described below at a predetermined execution timing, for example, every hour. The execution control unit 44 waits until the predetermined execution timing arrives (N in step 131). When the execution timing arrives (Y in step 131), the execution control unit 44 reads one piece of unprocessed reservation information registered in the reservation information storage unit 56 and obtains the update date and time of the reservation information (step 132). Next, the execution control unit 44 compares the obtained update date and time with the current time. If the current time has not yet reached the update date and time (N in step 133), the execution control unit 44 next extracts one piece of unprocessed reservation information (Y in step 134, step 132). However, if there is no unprocessed reservation information (N in step 134), the execution control unit 44 enters a standby state until the next execution timing arrives (step 131).

[0094] If the current time has reached the update date and time (Y in step 133), the execution control unit 44 transmits to the management center 3 a request to transmit an update file corresponding to the function included in the reservation information.

[0095] In response to the transmission request, the update file providing unit 32 in the management center 3 transmits the update file for the corresponding function to the update management server 4 that sent the request.

[0096] In this way, when the execution control unit 44 acquires the update file corresponding to the function to be upgraded (step 135), it sends the acquired update file to the multifunction device 1 having the device ID set in the reservation information, thereby instructing the execution of an upgrade of the function, i.e., an upgrade of the software having the function (step 136). Thereafter, the execution control unit 44 waits for a notification of completion of the upgrade from the multifunction device 1 (N in step 137).

[0097] The upgrade processing unit 13 in the multifunction device 1 executes the update file in accordance with instructions from the update management server 4, thereby upgrading the corresponding functions. If multiple functions are to be upgraded, the multiple functions included in one piece of software are upgraded consecutively. When the software upgrade is complete, the upgrade processing unit 13 notifies the update management server 4 that the upgrade is complete.

[0098] When the execution control unit 44 receives a notification from the multifunction device 1 that the version upgrade has been completed (Y in step 137), it notifies the administrator by email (step 138). After that, the execution control unit 44 enters a standby state until the next execution timing (step 131). Note that the processed reservation information is no longer needed, so it is preferable to delete it at an appropriate time.

[0099] In this embodiment, the software installed in the multifunction device 1 is upgraded as described above, but as mentioned above, only the functions that are used are upgraded, and functions that are not used are not upgraded even if there is an update file to be updated. This reduces the time required for software upgrade.

[0100] However, there is software for which an update file is prepared for the entire software. That is, this is the case when update files for all functions to be updated are packaged together. Following the example above, instead of an update file being prepared for each function, such as the finisher function, the scan function, and the auto-feed function, an update file containing update files for the following functions, the finisher function, the scan function, and the auto-feed function, may be prepared for each model. In this case, the multifunction device 1 receives a single packaged update file from the update management server 4. That is, the multifunction device 1 also receives an update file corresponding to a function not to be upgraded (the "finisher function" in the example above), but the upgrade processing unit 13 only needs to upgrade the functions selected by the update management server 4 from the multiple functions included in the update file.

[0101] In the above description, the functions selected by the administrator are upgraded at a designated scheduled date and time under the administrator's management. However, once the upgrade function identification unit 43 identifies the functions to be upgraded, it may instruct the execution control unit 44 to upgrade the functions at a predetermined timing, for example, when the functions are identified or at a predetermined time, for example, after work hours, without inquiring of the administrator. This makes it possible to automate the upgrade process.

[0102] In addition, in this embodiment, a multifunction peripheral 1 used by multiple users is described as an example of a device equipped with software to be updated. Unused functions are identified from among multiple functions possessed by the software. However, this embodiment can also be applied to devices such as a smartphone (hereinafter referred to as "smartphone") or tablet terminal used by a single user. For example, multiple applications are downloaded and installed on a smartphone, but some of the downloaded applications may never be used. In this way, by selecting applications that are no longer used in the same manner as described above, it is possible to exclude those applications from being subject to version upgrades.

[0103] In the above embodiments, the term "processor" refers to a processor in a broad sense, and includes general-purpose processors (e.g., CPU: Central Processing Unit, etc.) and dedicated processors (e.g., GPU: Graphics Processing Unit, ASIC: Application Specific Integrated Circuit, FPGA: Field Programmable Gate Array, programmable logic device, etc.).

[0104] Furthermore, the operations of the processors in the above embodiments may not only be performed by a single processor, but may also be performed by multiple processors located at physically separate locations working together. Furthermore, the order of the operations of the processors is not limited to the order described in the above embodiments, and may be changed as appropriate. [Explanation of symbols]

[0105] 1 Multifunction device, 2 Administrator terminal, 3 Management center, 4 Update management server, 11 Function execution unit, 12 Function usage notification unit, 13 Version upgrade processing unit, 31 Update content information providing unit, 32 Update file providing unit, 41 Usage history management unit, 42 Update content information acquisition unit, 43 Update function identification unit, 44 Execution control unit, 51 Model master storage unit, 52 Contract information storage unit, 53 Administrator information storage unit, 54 Usage history log accumulation unit, 55 Used function information storage unit, 56 Reservation information storage unit, 431 Administrator collaboration processing unit, 432 Reservation processing unit.

Claims

1. a processor; The processor: In a device equipped with software having a plurality of functions, usage history information including the usage status of the functions within a predetermined period, the usage history information including the functions used within the predetermined period and the number of users who used the functions, is stored in a storage means; When the software needs to be updated, referring to the usage history information, a function that is being used in the device among functions included in the software is identified and controlled to be updated; The function used in the device is a function used by a predetermined number of users within a predetermined period of time.

1. An information processing device comprising:

2. The processor: acquiring update information for the software from a management center for the software; notifying an administrator of the device of the necessity of updating the software according to the content of the acquired software update information; 2. The information processing apparatus according to claim 1, wherein:

3. 3. The information processing apparatus according to claim 2, wherein the processor controls updating of functions used in the device in response to an instruction from the administrator.

4. 4. The information processing apparatus according to claim 3, wherein the processor instructs the device to update the functions used in the device at an update date and time instructed by the administrator.

5. The processor: presenting the usage history information corresponding to the functions used in the device to an administrator of the device; selecting, from among the functions used in the device, a function selected by the administrator with reference to the usage history information, as a target for update; 2. The information processing apparatus according to claim 1, wherein:

6. 2. The information processing apparatus according to claim 1, wherein the software is firmware.

7. On the computer, A function for storing usage history information including the usage status of functions within a predetermined period in a storage means, the usage history information including the functions used within the predetermined period and the number of users who used the functions, in a device equipped with software having multiple functions; a function of, when an update of the software is necessary, referring to the usage history information, identifying functions included in the software that have been used by a predetermined number of users within a predetermined period, and controlling the updating of the functions; A program to achieve this.

Images