JP6645233B2 - Device management system, device management device and program - Google Patents

Description

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

  2. Description of the Related Art Conventionally, there has been known a method of remotely updating firmware of an electronic device such as an image processing device, a multifunction device, and a printer device.

  Generally, firmware is released with a certain level of quality assurance, but if firmware updates are not applied until the track record of the firmware is accumulated, for example, defective firmware can be used or better functions can be used. The inconvenience that it cannot be used arises.

  With the conventional remote firmware update, when a problem occurs due to the firmware update, it is necessary to actually operate the device or change the firmware to be updated, which affects the normal work using the device There was a problem.

  The present invention has been made in view of the above, and provides a device management system, a device management device, and a program that can reduce the influence on normal business even when a problem due to firmware update occurs. With the goal.

  In order to solve the above-described problems and achieve the object, an apparatus management system according to the present invention includes an apparatus management apparatus, a plurality of apparatuses that communicate with the apparatus management apparatus, and a server apparatus that communicates with the apparatus management apparatus. Device management system comprising: the device management device, from each of the plurality of devices, for each time the device is used, identification information for identifying the device, and model information indicating the model of the device A usage information acquisition unit configured to acquire usage information at least associating usage function information indicating a function used among one or more functions of the device; and a firmware and an application target of the firmware from the server device. Firmware for acquiring additional information including target model information indicating a model of the device and target component information indicating a program component to which the firmware is applied. A acquisition unit, a function information identification unit that identifies function information indicating a function corresponding to the program component by using the target component information included in the additional information, and a function information identification unit that is included in the additional information from the usage information. A model information specifying unit that specifies the model information corresponding to the target model information to be obtained, the model information specified by referring to the use information, the used function information corresponding to the specified function information, and the time Using, for each piece of identification information of the device, a number of times information calculation unit that calculates number of times information indicating the number of times the function indicated by the use function information is used, and the number of times calculated for each piece of identification information of the device An importance information calculating unit that calculates importance information indicating the importance of the device using the information; and applying the firmware to each piece of identification information of the device based on the importance information. An update schedule information generation unit that generates update schedule information indicating a schedule; and an update request unit that includes, based on the update schedule information, an update request that includes the firmware and that requests a switch to the firmware. And wherein the device includes an update unit that executes switching to the firmware based on the update request, using the firmware included in the update request.

  Advantageous Effects of Invention According to the present invention, there is an advantageous effect that even if a problem due to firmware update occurs, the influence on normal business can be reduced.

FIG. 1 is a diagram illustrating an example of the overall configuration of the device management system. FIG. 2 is a diagram illustrating an example of a hardware configuration of the device management apparatus. FIG. 3 is a diagram illustrating an example of a hardware configuration of a device (MFP). FIG. 4 is a block diagram illustrating an example of a functional configuration of the device management device, the device, the server device, and the client PC. FIG. 5 is a diagram illustrating an example of the usage information table. FIG. 6 is a diagram illustrating an example of supplementary information. FIG. 7 is a diagram illustrating an example of a method for specifying function information. FIG. 8 is a diagram illustrating an example of the task status information. FIG. 9 is a diagram illustrating an example in which devices of an update target model are rearranged in order of importance and normalized in importance. FIG. 10 is a diagram illustrating an example of the update schedule information. FIG. 11 is a diagram illustrating an example of the update schedule information. FIG. 12 is a diagram illustrating an example of the format of the update schedule information. FIG. 13 is a flowchart illustrating an example of a process in which the device management apparatus generates update schedule information and performs firmware update. FIG. 14 is a flowchart illustrating an example of a process of generating update schedule information.

  Hereinafter, an embodiment of a device management system, a device management device, and a program according to the present invention will be described in detail with reference to the accompanying drawings. The present invention is not limited by the following embodiments. In addition, the embodiments can be appropriately combined within a range that does not contradict the contents.

  The device management system according to the present embodiment includes a device management device, a plurality of devices that communicate with the device management device, and a server device that communicates with the device management device. The device management apparatus is configured to provide, from each of the plurality of devices, identification information for identifying the device, model information indicating the model of the device, and a function used among one or more functions of the device at each time the device is used. The usage information that associates at least the usage function information shown is acquired. The device management apparatus acquires, from the server device, additional information including firmware, target model information indicating a model of a device to which the firmware is applied, and target component information indicating a program component to which the firmware is applied. The device management device uses the target part information included in the additional information to specify function information indicating a function corresponding to the program component, and, from the usage information, extracts the model information corresponding to the target model information included in the additional information. Identify. The device management device refers to the usage information, and uses the specified model information, the usage function information corresponding to the specified function information, and the time to determine the function indicated by the usage function information for each device identification information. Count information indicating the number of times of use is calculated, and for each piece of device identification information, importance information indicating the importance of the device is calculated using the calculated count information. The device management device generates update schedule information indicating a schedule to which the firmware is to be applied for each device identification information based on the importance information, includes the firmware based on the update schedule information, and includes An update request for switching is transmitted to the device. Based on the update request, the device uses the firmware included in the update request to execute switching to the firmware. Thereby, even if a problem occurs due to the firmware update, it is possible to reduce the influence on the normal business.

  Hereinafter, an example will be described in which the device management apparatus according to the present embodiment is realized as a part of a device management system that remotely controls a device by communicating with a device (image processing device), a server device, and a client information processing device. . The device management system to which the device management device of the present embodiment can be applied is not limited to such a system. In the following, a case where the device according to the present invention is applied to a multifunction peripheral (MFP) is described as an example, but the present invention is not limited to this. Note that the MFP is an apparatus having at least two of a printing function, a copying function, a scanning function, and a facsimile function. The devices are not limited to MFPs, but may be printers, LPs (Laser Printers), inkjet printers, fax machines, digital copiers, scanners, projectors, digital cameras, and other industrial cameras.

  First, an overall configuration example and an outline of the device management system 1 will be described with reference to FIG. As shown in FIG. 1, the device management system 1 includes a device management device 10, a plurality of devices 20 a, 20 b, 20 c that communicate with the device management device 10 via a network 50, and a device management device 10 and a network 60. And a client information processing device (PC: Personal Computer) 40 that communicates with the device management device 10 and the devices 20a to 20c via the network 50. The network 60 is, for example, an external network such as a high-security dedicated line, a VPN (Virtual Private Network), or the Internet. The network 50 is, for example, an in-house computer network such as an in-house LAN used in a corporate office or the like.

  Hereinafter, when it is not necessary to distinguish a plurality of devices 20a to 20c, they are referred to as devices 20. When there is no need to distinguish between the network 50 and the network 60, the network is described as a network.

  The device management apparatus 10 is installed, for example, in an office or the like on the side of a device user (user), and implements management software (application program) for the device management device 10 to control and manage the device 20. The device management apparatus 10 communicates with the device 20 to collect usage information of the device 20, apply firmware, and the like. The device management device 10 communicates with the server device 30 and a client information processing device (hereinafter, referred to as a client PC) 40 to acquire firmware and create a firmware application schedule. That is, the device management apparatus 10 generates update schedule information indicating a firmware update schedule.

  The device management device 10 manages each device 20 via, for example, a client PC 40 having a function of an intermediary device. The device management apparatus 10 performs, for example, updating of firmware, counting of counters (charging process), ordering of consumables, dispatch of CE (dispatch of a customer engineer), and the like from data notified from the device 20 via the client PC 40. It is also a device to do.

  The device 20 is a network device, an electronic device, for example, an MFP. In the present embodiment, the device 20 will be described using an MFP as an example. The plurality of devices 20a to 20c communicate with the client PC 40 and the device management apparatus 10 via the network 50 for each of the devices 20a to 20c. The device 20 can connect to the network 60 via the device management device 10 and perform communication. The device 20 receives, for example, information on a process managed and instructed by the workflow management device (client PC 40), executes the process, and transmits the result to the workflow management device (client PC 40).

  The server device 30 communicates with the device management device 10 and the client PC 40 via the network 60. The server device 30 holds original data for executing various data processing. The server device 30 is a server that holds data for executing data processing to be transmitted to the device management device 10, the device 20, and the client PC 40, for example. The data held by the server device 30 holds, for example, information such as firmware of the device 20, update firmware, device setting information, and large-scale setting information. That is, data for executing data processing is held. The server device 30 transmits update firmware and the like to the device management device 10 in response to a request from the device management device 10.

  The client PC 40 communicates with the device management device 10 and the device 20 via the network 50. The client PC 40 transmits the firmware and the update firmware to the device management apparatus 10, for example, when receiving an input from the user regarding uploading of the firmware. When a problem occurs in the device 20, input from the device 20 or a user is received and transmitted to the device management apparatus 10.

  FIG. 1 illustrates a case where the number of devices 20 connected to the device management apparatus 10 is three, but the number is not limited to this, and the number of devices 20 is arbitrary. Further, the case where the number of client PCs 40 connected to the network 50 is one is illustrated, but the number is not limited to this, and the number of client PCs 40 is arbitrary. Further, the case where the number of the server devices 30 is one is illustrated, but the number is not limited thereto, and the number of the server devices 30 is arbitrary.

  Further, the device management system 1 transmits a “request”, which is a request for processing to a method of an application to be mutually implemented, to the client PC 40 and each device 20 by RPC (Remote Procedure Call) in order to perform management. It has a function of transmitting and receiving a “response” which is a result of the processing. That is, the client PC 40 or the device 20 connected thereto can generate a request to the device management apparatus 10, pass the generated request to the device management apparatus 10, and acquire a "response" to the "request". On the other hand, the device management apparatus 10 can generate a request to the client PC 40 and the device 20, pass the generated request to the client PC 40 and the device 20, and acquire a “response” to the “request”. ing. This request includes causing the client PC 40 to transmit various requests to the device 20 and obtaining a response from the device 20 via the client PC 40.

  In addition, in order to realize RPC, PPP (Point-to-Point Protocol), TCP / IP (Transmission Control Protocol / Internet Protocol), SOAP (Simple Object Access Protocol), HTTP (Hyper-TPE, Hyper-TPT) Known protocols (communication standards) such as Transfer Protocol (COM), Component Object Model (COM), and Common Object Request Broker Architecture (CORBA), technologies, and specifications can be used.

  Next, a hardware configuration of the device management apparatus 10 will be described with reference to FIG. FIG. 2 is a diagram illustrating an example of a hardware configuration of the device management apparatus.

  As shown in FIG. 2, the device management apparatus 10 includes a CPU (Central Processing Unit) 101, a RAM (Random Access Memory) 102, a ROM (Read Only Memory) 103, a HDD (Hard Disk Drive) 104, a device I / F 105, It has a network I / F 108, which is connected to each other by a bus 109. The display unit 106 and the operation unit 107 are connected to the device I / F 105.

  The CPU 101 is an arithmetic unit, and controls the overall operation of the device management apparatus 10. The RAM 102 is a volatile storage medium that can read and write information at high speed, and is used as a work area when the CPU 101 processes information. The ROM 103 is a read-only nonvolatile storage medium and stores programs such as firmware. The HDD 104 is a nonvolatile storage medium on which information can be read and written, and stores an OS (Operating System), various control programs, application programs, and the like. The HDD 104 stores files, data, and the like necessary to realize various functions of the device management apparatus 10. The HDD 104 stores various management information parameters (device information) used for managing the device 20 to be managed and a management program.

  The device I / F 105 is an interface for connecting each of the display unit 106 and the operation unit 107 to the bus 109. The display unit 106 is a visual user interface for displaying various information, and is configured by, for example, an LCD (Liquid Crystal Display). The operation unit 107 is a user interface, such as a keyboard and a mouse, for a user to input various information to the device management apparatus 10. The network I / F 108 is an interface for connecting the device management apparatus 10 to the networks 50 and 60.

  In such a hardware configuration, a software control unit is configured by the CPU 101 performing calculations in accordance with a program stored in the ROM 103 or a program loaded into the RAM 102 from a storage medium such as the HDD 104 or an optical disk (not shown). A functional block that realizes the functions of the device management apparatus 10, the server apparatus 30, and the client PC 40 according to the present embodiment is configured by a combination of the software control unit and the hardware configured as described above. Since the hardware configurations of the server device 30 and the client PC 40 are the same as those of the device management device 10 described above, a detailed description thereof will be omitted below.

  The program for the device management apparatus 10 may be recorded in a computer-readable recording medium such as a recording medium and distributed in a file in an installable format or an executable format.

  Next, a hardware configuration of the device (MFP) 20 will be described with reference to FIG. FIG. 3 is a diagram illustrating an example of a hardware configuration of a device (MFP). As shown in FIG. 3, the MFP 20 includes a CPU 201, a ROM 202, a RAM 203, an external storage device 204, an engine unit 205, an operation display unit 206, and a communication I / F 207. These units are communicably connected by a system bus 208.

  The CPU 201 reads out a program stored in the ROM 202 or the like onto the RAM 203, executes the program, and controls the operation of the MFP 20 as a whole. ROM 202 is a nonvolatile storage device that stores a program for MFP 20. The RAM 203 is a volatile storage device used as a work area for calculation of the CPU 201.

  The external storage device 204 is a device that stores various data such as image data and print data. The external storage device 204 is, for example, an HDD or an SSD (Solid State Drive).

  The engine unit 205 is a hardware device that implements a scanner function, a printer function, and the like. Here, the scanner function is a function of reading document data and generating a scanner image. The printer function is a function of executing image processing on a scanner image or image data transmitted from the outside, and printing a plotter image in a format that can be output on a print sheet.

  The operation display unit 206 is, for example, a touch panel or the like, and is a device that receives an input to the MFP 20 and displays a state of the MFP 20 and the like. Note that the operation display unit 206 may be configured separately from the operation unit and the display unit. As described above, a mobile terminal such as a smartphone may be used as the operation display unit instead of the operation display unit 206.

  The communication I / F 207 is an interface for connecting to the network 50 and communicating data.

  Next, the functions of the device management apparatus 10, the device 20, the server device 30, and the client PC 40 according to the present embodiment will be described with reference to FIG. FIG. 4 is a block diagram illustrating an example of a functional configuration of the device management device, the device, the server device, and the client PC.

  First, a functional configuration of the device management apparatus 10 will be described. As illustrated in FIG. 4, the device management apparatus 10 includes a communication unit 111, a usage information acquisition unit 112, a firmware acquisition unit 113, and a function information identification unit 114, which are functions implemented when the CPU 101 executes a program. , Model information specifying unit 115, frequency information calculating unit 116, task status information generating unit 117, importance information calculating unit 118, update schedule information generating unit 119, update requesting unit 120, and update executing unit 121. And a storage unit 122. A part of each of the units may be software (program) generated by the CPU 101 reading and executing software (program) from the ROM 103 or the HDD 104 so that the units are loaded on the RAM 102 and the units are generated on the RAM 102. . Further, a part or all of the above-described units may be replaced with a hardware circuit such as a processor that performs arithmetic processing.

  The communication unit 111 communicates with the device 20 and the client PC 40 via the network 50. The communication unit 111 transmits and receives various data to and from the plurality of devices 20 a to 20 c and the client PC 40 via the network 50. The communication unit 111 communicates with the server device 30 via the network 60. The communication unit 111 transmits and receives various data to and from the server device 30 via the network 60. Specifically, for example, the communication unit 111 indicates, from the device 20, identification information for identifying the device 20, model information indicating the model of the device 20, and a function used from one or more functions of the device 20. The use function information, the use time in which the function is used, and the use information in which the user who uses the function is associated at least are received, and the model information specifying unit 115, the number-of-times information calculating unit 116, and the business status information generating unit 117 are received. Is transferred to the importance information calculation unit 118, the update schedule information generation unit 119, the storage unit 122, and the corresponding units. Further, for example, the communication unit 111 indicates, from the server device 30, an update firmware for updating the firmware of the device 20, and a model of the device 20 to which the update firmware is applied, which accompanies the update firmware. Receiving the target model information, the target component information indicating the program component to which the update firmware is applied, and the supplementary information including the update information indicating the update type of the update firmware, and receiving the function information specifying unit 114 and the model information specifying unit 115, the update schedule information generation unit 119, the storage unit 122, and the corresponding units. In addition, for example, the communication unit 111 transmits to the device 20 an update request including the update firmware and requesting switching (update) to the update firmware.

  The usage information acquisition unit 112 receives, from each of the plurality of devices 20, identification information of the device 20, model information indicating a model of the device 20, and usage function information indicating a function used from one or more functions of the device 20. And usage information that associates at least the time at which the function was used and the user who used the function. The use information acquisition unit 112 stores the acquired use information in the storage unit 122 (use information database) in the form of a table, for example, in the order of the execution ID in which the process was executed. FIG. 5 is a diagram illustrating an example of the usage information table. As shown in FIG. 5, the usage information table includes an execution ID, a device ID, a model, an installation location indicating a location where the device 20 is installed, a usage function used from among the functions of the device 20, and This is information that associates a user who has used a function with a use time at which the function has been used. In the example of FIG. 5, for example, the device ID “1” of the execution ID “1” is the model “MP 1601”, the installation location “2F A point”, the use function “Print”, the user “A”, and the use time “2015”. -09-29 10:23:54 ". The use function “Print” indicates “print function”, “Scan” indicates “scanner function”, “Fax” indicates “facsimile function”, and “Copy” indicates “copy function”. Among the above usage information, the execution IDs are assigned IDs in the order in which the processes are executed. Information about the device ID, model, and installation location is collected when the device 20 is registered in the device management apparatus 10. The table design of the database is arbitrary, for example, by normalization.

  Returning to FIG. 4, the description will be continued. The firmware acquisition unit 113 receives, from the server device 30, an update firmware for updating the firmware of the device 20, and target model information attached to the update firmware and indicating a model of the device 20 to which the update firmware is applied. And additional information including target component information (target module information) indicating a program component (hereinafter also referred to as a module) to which the update firmware is applied, and update information indicating an update type of the update firmware. . That is, the firmware acquisition unit 113 transmits an update firmware acquisition request for updating the firmware to the server device 30 and downloads the update firmware (new version firmware) and the accompanying information from the server device 30 in response to the request. I do. The firmware acquisition unit 113 causes the storage unit 122 to store the acquired update firmware and additional information attached to the update firmware. FIG. 6 is a diagram illustrating an example of supplementary information. As shown in FIG. 6, the supplementary information includes target model information (target model) indicating the model of the device 20 to which the update firmware is applied, and target information indicating program components (modules) to which the update firmware is applied. It includes component information (target module) and update information (update type) indicating the update type of the update firmware. As the update type, Critical indicates “important”, Maintenance indicates “maintenance (maintenance)”, and New indicates “new”.

  Returning to FIG. 4, the description will be continued. The function information specifying unit 114 specifies function information indicating a function corresponding to a program component (module) to which the firmware is applied, using the target module information of the update firmware. That is, a function that is affected when the firmware is updated is specified. FIG. 7 is a diagram illustrating an example of a method for specifying function information. The device management apparatus 10 stores a module hierarchy map shown in FIG. 7 for each model of the device 20 in advance. The module hierarchy map is a hierarchy map in which upper modules (program components) related to lower modules (program components) are indicated by arrows. In other words, the module hierarchy map shows the upper modules (program components) associated with the lower modules (program components) in a hierarchical structure in order, and identifies the function information associated with the uppermost module (program components). It is a possible hierarchy map figure. Note that the module hierarchy map may be mounted in a module in advance, or may be obtained from an external device.

  The function information specifying unit 114 inputs a lower module from the information of the target module shown in FIG. 6 included in the supplementary information of the update firmware by using a module hierarchy map stored in advance for each model of the device 20. I do. In other words, the lower module of the module hierarchy map corresponding to the target module of the incidental information is started. Then, by tracing the arrows of the module hierarchy map from the lower order to the upper order, it is possible to specify the function (relevant) corresponding to the target module (program component). Specifically, when the target module information of the supplementary information shown in FIG. 6 is, for example, “module 1A”, “lower module 1A” in FIG. 7 is started. Following the arrow from "module 1A", "module 2A"... "Module nA" and "function B" are reached. In this case, the function specified by using the target module of the update firmware is “function B”. That is, when the firmware is updated to the update firmware, it is possible to specify that the affected function is “function B”. In this way, the function related to the firmware update is specified using the module (program component) to which the firmware is applied and the module hierarchy map. That is, the function information indicating the function corresponding to the program component (module) is specified using the target component information (target module information) included in the supplementary information. Note that the module to be started is not necessarily limited to the lowest module. For example, an intermediate “module 2A” can be started or an upper “module nA” can be started.

  Returning to FIG. 4, the description will be continued. The model information specifying unit 115 specifies the model information corresponding to the target model information included in the supplementary information of the firmware from the acquired usage information. That is, when the target model shown in FIG. 6 is, for example, “MP 1601”, the model “MP 1601” is specified from the usage information shown in FIG. If the model can be specified, the device ID associated with the model, the installation location, the use function, the user, and the use time using the function of the device 20 can also be specified. Note that the function of the model information specifying unit 115 may be provided in the importance information calculating unit 118 described later.

  The number-of-times information calculating unit 116 refers to the obtained usage information, and uses the device 20 and the model information specified by the model information specifying unit 115, the used function information corresponding to the function information specified by the function information specifying unit 114, and the device 20. Using the time, for each piece of identification information of the device 20, frequency information indicating the number of times the function indicated by the used function information is used is calculated. That is, if the model information specified by the model information specifying unit 115 is, for example, “MP 1601” and the used function information is, for example, “Print”, the execution ID “1” is referred to by referring to the use information shown in FIG. Is calculated as “1” for the device ID “1”.

  If the model information is, for example, “MP 1601” and the use function information is, for example, “Scan”, the frequency information of the device ID “1” of the execution ID “3” is “1”, and the device ID of the execution ID “4”. The number information of “3” is calculated as “1”. The function of the number-of-times information calculation unit 116 may be provided in the importance information calculation unit 118 described later.

  The business situation information generation unit 117 refers to the usage information using the target model information to which the update firmware is to be applied and the function information specified by the function information specifying unit 114, and determines the device 20 corresponding to the target model. For each piece of identification information, the user who uses the device 20 is associated with the count information indicating the number of times the function of the device 20 has been used calculated by the count information calculation unit 116, and the number of devices 20 having the function. Generate business status information. That is, the task status information generation unit 117 generates task status information (task status table) from the usage information acquired from the device 20 under the management of the device management apparatus 10. FIG. 8 is a diagram illustrating an example of the task status information. As shown in FIG. 8, the business status information includes the device ID of the target model, the user who has used the function of the device 20, the number of times the function of the device 20 has been used, and the number of devices 20 having the same function. Is associated information. In other words, the job status information includes, for example, how many times the “function B” of the device 20 specified by the function information specifying unit 114 has been used in the job, and how many devices 20 having the “function B” used. It can also be regarded as a business situation table in which the information is associated. In the example of FIG. 8, the information is information in which the device ID of the target model, the number of times the user has used the function of the device 20, and the number of devices 20 having the same function are associated with each other.

  In the present embodiment, the number of times the function is used can be arbitrarily set, for example, an average value per day, an average value per week, an average value per month or a predetermined period. In the present embodiment, the number of devices 20 having the same function is counted only when a certain user uses only one device 20. The target for counting the number of devices 20 having the same function may be limited to the devices 20 installed on the same floor, for example, or may be set to the devices 20 installed in the entire office, The counting method is arbitrary. The number of the devices 20 having the same function is used as one of the weight values when calculating the importance described later.

  Further, in the present embodiment, rules for generating a business status table (business status information) are set as follows. A task status table is generated in which at least the device ID of the target model, the user, the number of times the function specified by the function information specifying unit 114 is used, and the number of devices 20 having the same function are associated. If there is no user for the device ID of the target model, the user is set to “−” and the number of times the function is used is set to “0”. When a certain user uses only one device 20, the number of devices having the same function is counted. In this case, the counting method is performed when the character strings in the “installation location” column of the usage information match. If there is no information in the “installation location” column, “0” is set.

  In the example of FIG. 8, for example, the user “C” uses the function B with the device ID “1” “10 times”, and the number of the devices 20 having the function B is “− (in this example,“ not count ”). )), The user “B” uses the function B of the device ID “1” “12 times”, and the number of the devices 20 having the function B is “− (in this example,“ does not count ”)”. Is shown. That is, the user “C, B” uses the function B of the device ID “1” a total of “22 times”, and the user “C, B” uses the device ID “4” other than the device ID “1”. , 10 ", the number of devices 20 having the function B is"-(in this example, "not count"). "

  Also, for example, the user “B” uses the function B with the device ID “4” “4 times”, and the number of the devices 20 having the function B indicates “− (in this example, indicates“ do not count ”)”. The user “C” uses the function B of the device ID “4” three times, and the number of the devices 20 having the function B indicates “− (in this example, indicates“ do not count ”)”. Since the user “D” uses the function B of the device ID “4” “11 times” and the user “D” uses only the device ID “4”, the number of the devices 20 having the function B is "2" is shown. That is, the user B and C use the function B of the device ID “4” a total of “7 times”, and the number of the devices 20 having the function B is “−” (in this example, “does not count”). The user B uses the function B with the device ID “4” in total “11 times”, and the number of the devices 20 having the function B is “2”.

  Further, for example, the user “C” uses the function B of the device ID “10” “12 times”, and the user “C” also uses other device IDs “1, 4” other than the device ID “10”. Therefore, the number of the devices 20 having the function B indicates “-(in this example,“ not counting ”)”.

  Further, for example, the user “F” uses the function B with the device ID “11” “5 times”, and the number of the devices 20 having the function B is “0 (in this example,“ indicates no information ”)”. Is shown.

  Further, for example, since there is no user using the function B with the device ID “12”, the user “−”, the number of times the function B is used “0”, and the number of the devices 20 having the function B are “3”. It indicates that there is.

  Returning to FIG. 4, the description will be continued. The importance information calculation unit 118 calculates importance information indicating the importance of the device 20 using the frequency information calculated by the frequency information calculation unit 116 for each piece of identification information of the device 20. When the importance information calculating unit 118 has the functions of the model information specifying unit 115 and the number-of-times information calculating unit 116 described above, the importance information calculating unit 118 uses the usage information corresponding to the target model information included in the supplementary information. Identifying the model information of the device 20 by referring to the usage information, and using the identified function information and the calculated count information for each piece of identification information of the device 20 linked to the identified model information, Calculate degree information. In other words, the importance information calculation unit 118 uses the work status information (work status table) generated by the work status information generation unit 117 to indicate, for each piece of identification information of the device 20, the importance of the device 20 used for the business. Calculate importance information. Specifically, the importance of the importance information can be calculated using the following equation (1).

  Importance = total number of uses + impossibility of substitution (1)

  In the above equation (1), the total number of times of use represents the sum of the times of all users who have used the function of the device. The non-substitution degree is set to “−” when the number of devices having the same function is “−” or 1 or more.

  When the number of devices having the same function is other than “−” or one or more, the importance of the importance information can be calculated using the following equation (2).

  Importance = Total number of times of use + (Total number of times of use × Non-substitute ratio)

  In the above equation (2), (total number of times of use × impossible substitutable ratio) indicates the non-substitutable degree, and indicates a weighting value that places importance on non-substitute devices. The non-substitution ratio is a value of 0 or more and 1 or less, and 0.5 is set as a default.

  The update schedule information generation unit 119 generates update schedule information indicating a schedule (update schedule) to which the firmware is to be applied for each device 20 based on the importance information described above. That is, based on the business importance of the device 20 calculated by the importance information calculation unit 118, update schedule information (update schedule) for applying the update firmware (updating the firmware) is generated.

  First, the update schedule information generation unit 119 sorts the devices 20 in the order of importance using the importance information calculated by the importance information calculation unit 118. Alternatively, the importance is normalized, and rearrangement is performed in the normalized importance order. FIG. 9 is a diagram illustrating an example in which devices of an update target model are rearranged in order of importance and normalized in importance. In the example of FIG. 9, the importance “22” of the device ID “1” and the normalized importance “0.37” are shown, the importance “18” of the device ID “4”, and the normalized importance “0”. .30 ", the importance" 12 "of the device ID" 10 ", the normalized importance" 0.20 ", the importance" 7.5 "of the device ID" 11 ", and the normalized importance "0.13", indicating the importance "0" of the device ID "12" and the normalized importance "0.00".

  Next, using the normalized importance, the update schedule information generation unit 119 sets the current time as a start time, sets an update execution time (for example, 24h) up to an end time obtained by adding the update times, and updates the update execution time. Is divided by the normalized importance to generate update schedule information. FIG. 10 is a diagram illustrating an example of the update schedule information. In the example of FIG. 10, the device ID “1” updates the firmware at 8.87 h from the current time, and then updates the device ID “4” at 7.26 h in descending order of importance. After that, the device ID “10” updates the firmware at 4.84h, then updates the device ID “11” at 3.03h, and then updates the firmware of the device ID “12”. It is schedule information (update schedule).

  The update schedule information generating unit 119 generates the update schedule information by using the update information (update type) indicating the update type of the firmware for updating the incidental information illustrated in FIG. FIG. 11 is a diagram illustrating an example of the update schedule information. In the example of the update schedule on the upper side of FIG. 11, if the update type is critical, it is determined that the risk is high if the current firmware is continuously used, and the devices 20 with the highest importance shown in FIG. Generate update schedule information for performing a firmware update. That is, when the update type (update type) included in the update information is important, the update schedule information generating unit 119 generates the update schedule information arranged in the descending order of the importance information. Further, in the example of the update schedule on the lower side of FIG. 11, if the update type is other than critical, that is, if the maintenance type is maintenance (Maintenance) or new (New), it is possible to avoid the problem due to the firmware update. For this purpose, update schedule information for executing firmware update in the order of the devices 20 having the lower importance shown in FIG. 9 is generated. That is, when the update type (update type) included in the update information is other than important, the update schedule information generating unit 119 generates the update schedule information arranged in ascending order of importance information. When the update schedule information is generated, if the update prohibition time zone is set, the update schedule information is shifted and generated so that the firmware update is not performed in that time zone. For example, the update schedule information generating unit 119 uses the function specified by the function information specifying unit 114 and the time at which the function of the usage information is used to set the time period during which the function is most used as the update prohibited time period. By setting, even if a problem occurs due to the firmware update, it is possible to reduce the influence on normal business. That is, the update schedule information generation unit 119 generates the update schedule information that does not switch to the update firmware during the time zone when the function of the device 20 is used most, using the function information and the usage information.

  FIG. 12 is a diagram illustrating an example of the format of the update schedule information. As shown in FIG. 12, the format of the update schedule information (update schedule) is information in which timestamp (date and time) is associated with target (identification information of the device 20). The identification information of the device 20 may be any information that identifies (specifies) the device 20, such as an IP address, a domain name, or a host name.

  As described above, the update schedule information generation unit 119 performs the firmware update based on the device 20 of the target model of the firmware update, the importance of the device 20 used for the job, and the update type of the supplementary information of the firmware. Generate update schedule information (update schedule).

  The update request unit 120 transmits an update request including the update firmware and requesting a switch (update) to the update firmware to the device 20 based on the update schedule information generated by the update schedule information generation unit 119. . In addition, when the update request unit 120 receives a notification indicating that the device 20 that has performed the switch to the update firmware has a problem, the update request unit 120 stops transmitting the update request that requests the subsequent switch to the update firmware (update). When the update execution unit 121 executes the firmware update of the device 20 using the update firmware, the update request unit 120 may not be provided.

  The update execution unit 121 executes the firmware update of the device 20 using the update firmware acquired by the firmware acquisition unit 113, based on the update schedule information generated by the update schedule information generation unit 119. In addition, when the update execution unit 121 receives a notification indicating that the device 20 that has performed the switch (update) to the update firmware has a defect, the update execution unit 121 stops performing the subsequent switch (update) to the update firmware. The update request unit 120 transmits an update request for updating the firmware to the device 20, and the device 20 switches to the update firmware based on the update request by using the update firmware included in the update request. When performing (update), the update execution unit 121 may not be provided.

  The storage unit 122 stores various data. For example, the storage unit 122 stores the usage information in a predetermined area in a table format in the order of, for example, the execution IDs of the processes that have been executed. Further, for example, the storage unit 122 stores the update firmware and additional information accompanying the update firmware in a predetermined area. Further, for example, the storage unit 122 stores the above-described module hierarchy map in a predetermined area. Further, for example, the storage unit 122 acquires and manages various types of information necessary for managing the device 20. Further, for example, the storage unit 122 manages a plurality of devices 20, and stores, for example, information related to a user's model, device number, installation location, installation date, usage period, and the like for each device 20.

  Next, a functional configuration of the device 20 will be described. As illustrated in FIG. 4, the device 20 includes a communication unit 211, an update unit 212, a process execution unit 213, and a storage unit 214, which are functions realized by the CPU 201 executing a program. A part of the respective units is software (program) generated by the CPU 201 reading the software (program) from the ROM 202 or the external storage device 204 and loading the respective units on the RAM 203, and the respective units being generated on the RAM 203. You may. Further, a part or all of the above-described units may be replaced with a hardware circuit such as a processor that performs arithmetic processing.

  The communication unit 211 communicates with the device management apparatus 10 and the client PC 40 via the network 50. The communication unit 211 transmits and receives various data to and from the device management apparatus 10 and the client PC 40 via the network 50. For example, the communication unit 211 includes identification information for identifying the device 20 from the device management apparatus 10, model information indicating the model of the device 20, and usage function information indicating a function used from one or more functions of the device 20. Receiving a use information acquisition request that requests acquisition of use information that associates at least the time at which the function was used with the user who used the function, and stores the use information held by the device 20 in the device management apparatus. Send to 10. Further, for example, the communication unit 211 receives an update request for updating the firmware from the device management apparatus 10 and passes the update request to the update unit 212 and the storage unit 214. Further, for example, the communication unit 211 transmits device information including state information indicating the state of the device 20 to the device management apparatus 10. That is, a request to acquire device information is received from the device management apparatus 10, and the device information held by the device 20 is transmitted as a response. Alternatively, the device 20 transmits the device information held by the device 20 to the device management apparatus 10 at predetermined intervals set in advance.

  The update unit 212 switches to the update firmware using the update firmware included in the update request, based on the update request that includes the update firmware and requests the switch (update) to the update firmware (update). Update).

  The processing execution unit 213 performs data processing using the data for executing the data processing received from the client PC 40.

  The storage unit 214 stores various data. For example, the storage unit 214 stores the firmware in a predetermined area. Further, for example, the storage unit 214 uses the identification information of the device 20, model information indicating the model of the device 20, use function information indicating a function used from one or more functions of the device 20, and uses the function. Usage information including at least a time and a user who has used the function is stored in a predetermined area. Further, for example, the storage unit 214 stores device information including status information indicating the status of the device 20 in a predetermined area. The status information indicating the status of the device 20 includes, for example, counter information, device status information, device setting information, and the like. Further, for example, the storage unit 214 includes, as device information, individual information such as a model and a machine number, optional mounting information such as a sorter and a finisher, various counter information such as a total copy number, a monochrome copy number, and a color copy number, the number of failures, and the like. Device status information (history information) such as a repaired part and the number of times, device setting information such as serviceman (SP) settings set when the device 20 is installed and user settings arbitrarily set by a user are stored in a predetermined area.

  Next, a functional configuration of the server device 30 will be described. As illustrated in FIG. 4, the server device 30 includes a communication unit 311 that is a function realized by the CPU 101 executing a program, and a firmware storage unit 312. A part of each of the units may be software (program) generated by the CPU 101 reading and executing software (program) from the ROM 103 or the HDD 104 so that the units are loaded on the RAM 102 and the units are generated on the RAM 102. . Further, a part or all of the above-described units may be replaced with a hardware circuit such as a processor that performs arithmetic processing.

  The communication unit 311 communicates with the device management device 10 via the network 60. The communication unit 311 transmits and receives various data to and from the device management apparatus 10 via the network 60. For example, the communication unit 311 receives the update firmware, the target model information indicating the model of the device 20 to which the update firmware is applied, and the target model information attached to the update firmware and the update firmware. Receiving a request to acquire target component information indicating a program component (module) and incidental information including update information indicating an update type of the update firmware, updating firmware read from the firmware storage unit 312, and The additional information is transmitted to the device management apparatus 10. That is, the communication unit 311 receives a request for acquiring the update firmware and the supplementary information from the device management device 10 and transmits the update firmware and the supplementary information read from the firmware storage unit 312 to the device management device 10. I do.

  The firmware storage unit 312 stores, in a predetermined area, firmware and additional information of the device 20, update firmware for updating the firmware, additional information, and the like.

  Next, a functional configuration of the client PC 40 will be described. As shown in FIG. 4, the client PC 40 includes a communication unit 411, a reception unit 412, an acquisition unit 413, and a storage unit 414, which are functions realized by the CPU 101 executing a program. A part of each of the units may be software (program) generated by the CPU 101 reading and executing software (program) from the ROM 103 or the HDD 104 so that the units are loaded on the RAM 102 and the units are generated on the RAM 102. . Further, a part or all of the above-described units may be replaced with a hardware circuit such as a processor that performs arithmetic processing.

  The communication unit 411 communicates with the device management device 10 and the device 20 via the network 50. The communication unit 411 transmits and receives various data to and from the device management apparatus 10 and the device 20 via the network 50. For example, the communication unit 411 transmits data for executing data processing to the device 20. The communication unit 411 communicates with the server device 30 via the network 60. The communication unit 411 transmits and receives various data via the network 60.

  The receiving unit 412 receives, for example, various operation instructions from the user and transfers the received instructions to corresponding units. Further, for example, the receiving unit 412 receives an input of a firmware update from a user, and transmits the update firmware to the device management apparatus 10 via the communication unit 411. Further, for example, the receiving unit 412 receives the occurrence of a failure from the device 20 and transmits to the device management apparatus 10 via the communication unit 411 that the device 20 that has performed the firmware update has a problem.

  The acquisition unit 413 stores, for example, the update firmware, target model information indicating the model of the device 20 to which the update firmware is applied, and program components (modules) to which the update firmware is applied. A request for acquiring additional information including target component information indicating the type of update and the update information indicating the update type of the update firmware is transmitted to the server device 30, the update firmware and the additional information are acquired from the server device 30, and the storage unit 414 is stored.

  The storage unit 414 stores various data. For example, the storage unit 414 stores the update firmware and additional information accompanying the update firmware in a predetermined area.

  Next, a processing operation of the device management apparatus 10 will be described. FIG. 13 is a flowchart illustrating an example of a process in which the device management apparatus generates update schedule information and performs firmware update. The device management apparatus 10 receives, from the plurality of devices 20, identification information of the device 20, model information indicating the model of the device 20, and use function information indicating a function used from one or more functions of the device 20 (used function information). Use information indicating a function of the device 20), a time at which the function was used, and a user who has used the function at least are acquired (step S1). Next, the device management apparatus 10 determines whether or not the server apparatus 30 has update firmware (step S2). In other words, the device management apparatus 10 sends the update firmware and the target model information indicating the model of the device 20 to which the update firmware is to be applied to the server apparatus 30 and the update firmware. A request for acquiring additional information including target component information (target module information) indicating a program component (module) to be applied and update information indicating an update type of the update firmware is transmitted. When the additional information is received, it is determined that there is an update firmware. When there is no response or a response indicating that there is no update firmware is received, it is determined that there is no update firmware.

  If there is an update firmware (step S2: Yes), the process proceeds to step S4 to continue the process. If there is no update firmware (step S2: No), the device management apparatus 10 determines whether or not update firmware has been received (step S3). That is, the device management apparatus 10 determines whether the update firmware has been received from the client PC 40. This is because, in the present embodiment, the device management apparatus 10 may acquire the update firmware from the server device 30 or may receive and acquire the update firmware from the client PC 40.

  If the update firmware has not been received (step S3: No), the process returns to step S2 and continues. If the update firmware has been received (step S3: Yes), the process proceeds to step S4.

  In step S4, the device management apparatus 10 acquires the update firmware and the accompanying information from the server device 30 as described above. Alternatively, it receives and acquires the update firmware and the accompanying information from the client PC 40 (step S4). Next, the device management apparatus 10 generates the update schedule information (update schedule) as described above using the usage information acquired in step S1 and the accompanying information acquired in step S4 (step S5). Next, the device management apparatus 10 executes a firmware update on the target device 20 based on the update schedule information (update schedule) shown in FIGS. 11 and 12 (step S6). As the firmware update process, as described above, the update request unit 120 transmits an update request for requesting switching (update) to the update firmware to the device 20, and the device 20 executes the firmware update. In some cases, the firmware of the device 20 is updated using the update firmware. However, the firmware can be set in advance, and the setting is arbitrary.

  Next, the device management apparatus 10 determines whether the device 20 that has performed the firmware update (switching to the update firmware) has a problem (step S7). That is, the device management apparatus 10 can determine whether or not the device 20 has a problem by acquiring status information indicating the status of the device 20 every time the firmware of one device 20 is updated. It is also possible to determine that a failure has occurred by receiving from the client PC 40 that the device 20 that has performed the firmware update has a failure.

  If there is a defect (step S7: Yes), the device management apparatus 10 stops the firmware update process according to the update schedule information (update schedule) (step S8) and ends the process. That is, when it is determined that the device 20 has a problem, the subsequent update processing for the device 20 is stopped. If there is no failure (step S7: No), the device management apparatus 10 determines whether or not all devices 20 in the update schedule information (update schedule) have been updated (step S9). If all devices 20 have not been updated (step S9: No), the process returns to step S6, and the firmware is updated for the next device 20. If all the devices 20 have been updated (step S9: Yes), the process ends. As described above, the device management apparatus 10 generates the update schedule information that has little effect on the business, updates the firmware of the device 20, and stops the update process if the updated device 20 has a problem. Even if a problem occurs due to the firmware update, the advantageous effect that the influence on the normal business can be reduced can be achieved.

  Next, details of the processing in step S5 will be described. FIG. 14 is a flowchart illustrating an example of a process of generating update schedule information. In the device management apparatus 10, the function information specifying unit 114 specifies the function information indicating the function to which the firmware is applied according to the module hierarchy map using the target module information of the update firmware (step S21). That is, the function information indicating the function corresponding to the program component (module) is specified using the target component information (target module information) included in the supplementary information. That is, the function information specifying unit 114 specifies the function information by using the program component (module) to which the firmware is applied and the module hierarchy map. Next, the device management apparatus 10 refers to the usage information using the target model information of the update firmware and the specified function information in the task status information generation unit 117, and identifies the identification information of the device 20 of the target model. Then, task status information (task status table) is generated in which the user who uses the device 20 is associated with the number of times the function of the device 20 is used and the number of devices 20 having the function (step S22). . Next, in the device management apparatus 10, the importance information indicating the importance of the device 20 used for the business is used for each piece of identification information of the device 20 by using the business status information (business status table) in the importance information calculation unit 118. Information is calculated (step S23). Next, the device management apparatus 10 uses the update schedule information generation unit 119 to update the update firmware (update the firmware) update schedule information (update schedule) based on the business importance information of the device 20. It is generated (step S24). As described above, the device management apparatus 10 generates update schedule information (update schedule).

  Although the embodiment according to the present invention has been described above, the present invention is not limited to the above-described embodiment as it is, and can be embodied by modifying constituent elements without departing from the gist thereof at the stage of implementation. Various inventions can be formed by appropriately combining a plurality of components disclosed in the above-described embodiments. For example, some components may be deleted from all the components described in the embodiments. Further, components of different embodiments may be appropriately combined.

  For example, the above-described usage information acquisition unit 112, firmware acquisition unit 113, function information identification unit 114, model information identification unit 115, number-of-times information calculation unit 116, business status information generation unit 117, importance information calculation unit 118, update schedule information The generation unit 119, the update request unit 120, the update execution unit 121, and the storage unit 122 may be configured to be separately mounted on the device management device 10, the device 20, the server device 30, and the client PC 40. In addition, for example, the above-described usage information acquisition unit 112, firmware acquisition unit 113, function information identification unit 114, model information identification unit 115, number-of-times information calculation unit 116, work status information generation unit 117, importance information calculation unit 118, and update schedule The information generation unit 119, the update request unit 120, the update execution unit 121, and the storage unit 122 are provided in each of the device management device 10, the device 20, the server device 30, the client PC 40, and one or more external devices (for example, a server device). A configuration in which the components are mounted separately may be used.

  The program executed by the device management system 1 of each embodiment described above is a file in an installable format or an executable format in the form of a CD-ROM, a flexible disk (FD), a CD-R, a DVD (Digital Versatile Disk). ), A USB (Universal Serial Bus) or other computer-readable recording medium, or may be provided, or may be provided or distributed via a network such as the Internet. In addition, various programs may be configured to be provided by being incorporated in a ROM or the like in advance.

  Note that the device management system configuration in which the device management apparatus 10, the device 20, the server device 30, and the client PC 40 of the present embodiment are connected is an example, and there are various configuration examples of the device management system depending on the application and purpose. Needless to say.

1 Device Management System 10 Device Management Device 20 Device 30 Server Device 40 Client PC
50 network 60 network 101 CPU
102 RAM
103 ROM
104 HDD
105 Device I / F
106 display unit 107 operation unit 108 network I / F
109 Bus 111 Communication unit 112 Usage information acquisition unit 113 Firmware acquisition unit 114 Function information identification unit 115 Model information identification unit 116 Frequency information calculation unit 117 Business status information generation unit 118 Importance information calculation unit 119 Update schedule information generation unit 120 Update request Unit 121 update execution unit 122 storage unit 201 CPU
202 ROM
203 RAM
204 External storage device 205 Engine unit 206 Operation display unit 207 Communication I / F
208 System bus 211 Communication unit 212 Update unit 213 Process execution unit 214 Storage unit 311 Communication unit 312 Firmware storage unit 411 Communication unit 412 Acceptance unit 413 Acquisition unit 414 Storage unit

JP 2015-138297 A

Claims (12)

Device management system, a device management system including a plurality of devices that communicate with the device management device, and a server device that communicates with the device management device,
The device management device,
From each of the plurality of devices, for each time the device is used, identification information for identifying the device, model information indicating the model of the device, and a function used from one or more functions of the device. A use information acquisition unit for acquiring use information at least associating the use function information with
A firmware acquisition unit that acquires, from the server device, firmware and additional information including target model information indicating a model of the device to which the firmware is applied and target component information indicating a program component to which the firmware is applied; ,
Using the target component information included in the accompanying information, a function information specifying unit that specifies function information indicating a function corresponding to the program component,
A model information specifying unit that specifies the model information corresponding to the target model information included in the supplementary information from the usage information;
With reference to the use information, using the specified model information, the used function information corresponding to the specified function information, and the time, each of the device identification information is indicated by the used function information. A frequency information calculation unit that calculates frequency information indicating the number of times the function has been used,
For each of the identification information of the device, an importance information calculation unit that calculates importance information indicating the importance of the device using the calculated number of times information,
An update schedule information generation unit that generates update schedule information indicating a schedule to which the firmware is to be applied, based on the importance information, for each piece of the device identification information;
An update request unit that includes the firmware, based on the update schedule information, and transmits an update request for requesting a switch to the firmware to the device,
The device comprises:
Based on the update request, using the firmware included in the update request, comprising an update unit that performs switching to the firmware,
Equipment management system. The usage information further includes a user who has used the device,
The device management device,
Using the specified model information and the specified function information, the use information is referred to, and for each device identification information associated with the model information, the user and the number of times information are specified. A task status information generation unit that generates task status information at least associating the number of the devices having the function of the function information,
The importance information calculation unit refers to the business situation information, and for each piece of identification information of the device, the total number of times all the users have used the function of the device, and the number of devices having the function. And calculating the importance information using
The device management system according to claim 1. The incidental information further includes update information indicating an update type of the firmware,
When the update type included in the update information is important,
The update schedule information generating unit generates the update schedule information arranged in descending order of importance of the importance information,
The device management system according to claim 1. The incidental information further includes update information indicating an update type of the firmware,
When the update type included in the update information is other than important,
The update schedule information generating unit generates the update schedule information arranged in ascending order of the importance information,
The device management system according to claim 1. The function information specifying unit sequentially indicates, in a hierarchical structure, the upper program components associated with the lower program components in a hierarchical structure, and a hierarchical map capable of specifying the function information associated with the uppermost program component in advance. Holding, using the program component and the hierarchical map to which the firmware is applied, specifying the function information,
The device management system according to claim 1. The update schedule information generating unit generates the update schedule information that does not switch to the firmware during a time period when the function of the device is used most, using the specified function information and the usage information. ,
The device management system according to claim 1. The update request unit, when receiving a notification that there is a defect in the device that has performed the switch to the firmware, stops transmitting the update request,
The device management system according to claim 1. The device management system further includes an information processing device that communicates with the device management device and the device,
The firmware acquisition unit includes:
From the information processing device, acquiring the firmware and the accompanying information,
The device management system according to claim 1. A device management device that communicates with a device and a server device,
From each of the plurality of devices, for each time the device is used, identification information for identifying the device, model information indicating the model of the device, and a function used from one or more functions of the device. A use information acquisition unit for acquiring use information at least associating the use function information with
A firmware acquisition unit that acquires, from the server device, firmware and additional information including target model information indicating a model of the device to which the firmware is applied and target component information indicating a program component to which the firmware is applied; ,
Using the target component information included in the accompanying information, a function information specifying unit that specifies function information indicating a function corresponding to the program component,
A model information specifying unit that specifies the model information corresponding to the target model information included in the supplementary information from the usage information;
With reference to the use information, using the specified model information, the used function information corresponding to the specified function information, and the time, each of the device identification information is indicated by the used function information. A frequency information calculation unit that calculates frequency information indicating the number of times the function has been used,
For each identification information of the device, an importance information calculation unit that calculates importance information indicating the importance of the device using the calculated number of times information,
An update schedule information generation unit that generates update schedule information indicating a schedule to which the firmware is to be applied, based on the importance information, for each piece of identification information of the device;
An update execution unit that executes switching to the firmware for the device based on the update schedule information,
Equipment management device. A device management device that communicates with a device and an information processing device,
From each of the plurality of devices, for each time the device is used, identification information for identifying the device, model information indicating the model of the device, and a function used from one or more functions of the device. A use information acquisition unit for acquiring use information at least associating the use function information with
A firmware acquisition unit that acquires, from the information processing apparatus, firmware and target model information indicating a model of the device to which the firmware is to be applied and target component information indicating program components to which the firmware is to be applied; When,
Using the target component information included in the accompanying information, a function information specifying unit that specifies function information indicating a function corresponding to the program component,
A model information specifying unit that specifies the model information corresponding to the target model information included in the supplementary information from the usage information;
With reference to the use information, the specified function information, the used function information corresponding to the specified function information, and the time are used to indicate the used function information for each device identification information. A frequency information calculation unit that calculates frequency information indicating the number of times the function has been used,
For each of the identification information of the device, an importance information calculation unit that calculates importance information indicating the importance of the device using the calculated number of times information,
An update schedule information generation unit that generates update schedule information indicating a schedule to which the firmware is to be applied, based on the importance information, for each piece of identification information of the device;
An update execution unit that executes switching to the firmware for the device based on the update schedule information,
Equipment management device. In the device management device that communicates with the device and the server device,
From each of the plurality of devices, for each time the device is used, identification information for identifying the device, model information indicating the model of the device, and a function used from one or more functions of the device. Use information acquisition step of acquiring use information at least associating the use function information with
A firmware obtaining step of obtaining, from the server device, firmware and additional information including target model information indicating a model of the device to which the firmware is applied and target component information indicating a program component to which the firmware is applied; ,
A function information specifying step of specifying function information indicating a function corresponding to the program component, using the target component information included in the supplementary information;
A model information specifying step of specifying the model information corresponding to the target model information included in the supplementary information from the use information;
With reference to the use information, using the specified model information, the used function information corresponding to the specified function information, and the time, each of the device identification information is indicated by the used function information. A count information calculating step of calculating count information indicating the number of times the function has been used;
For each piece of identification information of the device, importance information calculation step of calculating importance information indicating the importance of the device using the calculated number of times information,
An update schedule information generation step of generating update schedule information indicating a schedule to which the firmware is to be applied, based on the importance information, for each piece of identification information of the device;
An update execution step of executing switching to the firmware for the device based on the update schedule information;
A program for executing In the device management device that communicates with the device and the information processing device,
From each of the plurality of devices, for each time the device is used, identification information for identifying the device, model information indicating the model of the device, and a function used from one or more functions of the device. Use information acquisition step of acquiring use information at least associating the use function information with
A firmware acquisition step of acquiring, from the information processing apparatus, firmware and target information including target model information indicating a model of the device to which the firmware is applied and target component information indicating a program component to which the firmware is applied; When,
A function information specifying step of specifying function information indicating a function corresponding to the program component, using the target component information included in the supplementary information;
A model information specifying step of specifying the model information corresponding to the target model information included in the supplementary information from the use information;
With reference to the use information, using the specified model information, the used function information corresponding to the specified function information, and the time, each of the device identification information is indicated by the used function information. A count information calculating step of calculating count information indicating the number of times the function has been used;
For each piece of identification information of the device, importance information calculation step of calculating importance information indicating the importance of the device using the calculated number of times information,
An update schedule information generation step of generating update schedule information indicating a schedule to which the firmware is to be applied, based on the importance information, for each piece of identification information of the device;
An update execution step of executing switching to the firmware for the device based on the update schedule information;
A program for executing

Images