Information processing device, method for controlling information processing device and program

Abstract

To perform schedule management for suppressing a failure of software distribution through a proxy server.SOLUTION: An information processing device 104 having a proxy server 402 for relaying communication between a network device and a software distribution system for providing the network device with a software distribution service acquires a distribution schedule of the network device being an object of the software distribution server to perform communication through the proxy server 402 from the software distribution system, detects a time zone applying a load of more than or equal to a prescribed level to the proxy server 402 by communication with a plurality of network devices performed thought the proxy server 402 on the basis of the distribution schedule, and performs notification to the software distribution system on the basis of a detection result.SELECTED DRAWING: Figure 6

Description

[Technical field]

[0001] The present invention relates to an information processing device that functions as a proxy server, and a control method and program for the information processing device. [Background technology]

[0002] There are known device management systems for acquiring and managing data such as operation information of network devices such as printers and multifunction devices. In order to continuously manage devices, the device management system can manage status, device settings, firmware, etc., and periodically acquire and distribute them. Patent Document 1 discloses a technology in which a GUI is displayed in an Internet distribution system for an operator to set the distribution date and time of firmware and applications, and updates are distributed to devices according to the settings specified in the GUI. In addition, mechanisms by which a distribution system or a device management system acquires data from devices and manages the devices include mechanisms that involve periodic polling and going through a proxy server. [Prior art documents] [Patent documents]

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

[0004] However, the distribution system of Patent Document 1 does not hold information on whether the device to which the software is to be distributed is managed via a proxy server. Therefore, although the proxy server has a limit on the number of devices that can communicate with it at the same time, it is difficult for the distribution system to set a distribution schedule that takes into account the load on the proxy server when distributing software. If software distribution is performed to more devices than the proxy server can communicate with at the same time, there is a risk that some of the software distribution will end up failing.

[0005] An object of the present invention is to perform schedule management to prevent failures in software distribution via a proxy server. [Means for solving the problem]

[0006] In order to solve the above problems, the information processing device of the present invention is an information processing device having a proxy server that relays communication between a network device and a software distribution system that provides a software distribution service to the network device, and has a distribution schedule management unit that obtains from the software distribution system a distribution schedule for a network device that is a target of the software distribution service and communicates via the proxy server, a load detection unit that detects a time period during which the proxy server is placed under a predetermined load or more due to communication with multiple network devices via the proxy server based on the distribution schedule, and a notification unit that notifies the software distribution system based on the results of the detection. Effect of the Invention

[0007] According to the present invention, schedule management can be performed to prevent failures in software distribution via a proxy server. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram showing the overall configuration of a system. [Diagram 2]FIG. 2 is a diagram illustrating a hardware configuration of an information processing device 104. [Diagram 3] FIG. 1 is a diagram illustrating a hardware configuration of a device 105. [Figure 4] FIG. 2 is a diagram illustrating a software configuration of the information processing device 104. [Diagram 5] FIG. 11 is a sequence diagram showing a distribution schedule confirmation process. [Figure 6] 13 is a flowchart showing a distribution schedule confirmation process in the first embodiment. [Figure 7] FIG. 13 illustrates an example of a warning screen. [Figure 8] 13 is a flowchart showing a distribution schedule confirmation process in the second embodiment. [Figure 9] 13 is a flowchart showing a distribution schedule confirmation process in the second embodiment. [Figure 10] 13 is a flowchart showing a distribution schedule confirmation process in the third embodiment. [Figure 11] 13 is a flowchart showing a schedule setting process. [Figure 12] 13 is a flowchart showing a schedule setting process. [Figure 13] FIG. 13 illustrates an example of a schedule setting screen. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] (First embodiment) 1 is a diagram showing the overall configuration of the system. The device management system 100 is a system for managing network devices via a network. The device management system 100 includes a management server 101 and a firmware distribution server 102. Note that, although this embodiment will be described taking as an example a case in which the management server 101 and the firmware distribution server 102 are separate devices, they may also be realized by the same server.

[0010] The device management system 100 manages the network devices 105 and 106 via a network. An information processing device 103 functioning as a proxy server is connected between the device management system 100 and the device 106. In addition to the information processing device 103 functioning as a proxy server, an information processing device 104 functioning as a proxy server is connected between the device management system 100 and the device 106.

[0011] The device management system 100 is connected to an information processing device 103 via a network 107. The network 107 is, for example, a wide area network (WAN). The information processing device 103 is connected to a device 106 via a network 108. The information processing device 103 is also connected to an information processing device 104 via the network 108, and the information processing device 104 is connected to a device 105 via a network 109. The network 108 and the network 109 are, for example, a local area network (LAN) within a company. The environment connected via the network 108 and the network 109 is, for example, an intra-company environment.

[0012] The information processing device 103 is a proxy server installed at the boundary between the network 107 and the network 108. That is, communication between the devices in the company intra environment and the network 107 is monitored and protected by the information processing device 103. Therefore, in the company intra environment, the threat of an attacker accessing the devices from the network 107 is significantly reduced.

[0013] The information processing device 104 is an information processing device having a proxy server function installed between the network 108 and the network 109. The information processing device 104 aggregates communications between devices on the network 109 and the device management system 100. While the information processing device 103 is a dedicated proxy server installed at the boundary between a company's internal network and the Internet, the proxy server function of the information processing device 104 is realized by software on a PC. Therefore, the number of communication requests that the proxy server of the information processing device 104 can simultaneously process is smaller and limited than that of the information processing device 103.

[0014] The management server 101 is an information processing device that provides a device management service that manages network devices via a network. The management server 101 communicates with the devices 105 and 106, acquires data and device states from the network devices, and distributes setting values. The service provided by the management server 101 may be realized by one or more information processing devices, a virtual machine (cloud service) using resources provided by a data center including the information processing devices, or a combination of these. The device management service provided by the management server 101 may also be implemented as a Web-based application, and may also be used via a Web browser on a client terminal.

[0015] The firmware distribution server 102 is an information processing device that realizes a software distribution system that provides a software distribution service that manages and distributes software such as firmware for network devices and extended applications. In this embodiment, an example will be described in which the firmware distribution server 102 provides a firmware distribution service, but the target of distribution is not limited to firmware, and may be any software or content that can be distributed to devices via a network. The service provided by the firmware distribution server 102 may be realized by one or more information processing devices, a virtual machine (cloud service) that uses resources provided by a data center that includes information processing devices, or a combination of these.

[0016] The device 105 and the device 106 are network devices. The device 105 and the device 106 are provided with a device management service by the device management system 100. In this embodiment, the network device is an image processing device. The device 105 and the device 106, which are image processing devices, are, for example, MFPs (Multifunction Peripherals) having a printing function and a scanning function. The device 105 and the device 106 receive print data received via a network by the printing function, and print on actual paper or the like by using a known printing technology such as electrophotography technology or inkjet technology. The device 105 and the device 106 read a paper document via a scanner and convert it into image data by the scanning function. Note that the network device may be any device capable of communication, and may be, for example, a single-function printer, scanner, 3D printer, notebook computer, smartphone, smart home appliance, or the like having only a printing function.

[0017] 2 is a diagram showing a hardware configuration of the information processing device 104. Note that the management server 101, the firmware distribution server 102, and the information processing device 103 have the same hardware configuration as the information processing device 104. The information processing device 104 has a control unit 200 and an operation unit 210. The control unit 200 includes a CPU 201, a ROM 202, a RAM 203, a HDD 204, a network I / F 205, and an operation unit I / F 206.

[0018] The CPU (Central Processing Unit) 201 controls the entire information processing device 104. The CPU 201 reads out a control program stored in the ROM 202 or the HDD 204 and executes various control processes. The control by the CPU 201 includes the execution of a program for implementing a flowchart described later. The ROM (Read Only Memory) 202 is a memory dedicated to reading data, and stores, for example, a basic control program of the information processing device 104. The RAM (Random Access Memory) 203 is a memory from which data can be read / written, and is used as a temporary storage area such as a work area of ​​the CPU 201. The HDD (Hard Disk Drive) 204 stores various data, programs, and applications. Note that, in this embodiment, an example in which the information processing device 104 includes the HDD 204 as a storage device will be described, but this is not limited thereto, and the information processing device 104 may include other storage devices such as an SSD or a Disk Drive for loading an external medium.

[0019] The network I / F 205 connects the information processing device 104 to a network. The information processing device 104 transmits and receives various information to and from external devices via the network I / F 205 and the network. The operation unit I / F connects the control unit 200 to the operation unit 210. The operation unit 210 has a display device and an input device. The display device is, for example, an LCD (Liquid Crystal Display). The input device is, for example, a keyboard or a pointing device. The display device and the input device may be realized by an integrated touch panel. By associating input coordinates and display coordinates on the touch panel, it is possible to configure a GUI as if the user could directly operate the screen displayed on the touch panel.

[0020] 3 is a diagram showing the hardware configuration of device 105. Device 106 has the same hardware configuration as device 105. Device 105, which is an image processing device, has a control unit 300, an operation unit 310, a printer 320, and a scanner 330. Control unit 300 has a CPU 301, ROM 302, RAM 303, HDD 304, an operation unit I / F 305, a printer I / F 306, a scanner I / F 307, and a network I / F 308.

[0021] The CPU 301 reads out a control program stored in the ROM 302 or the HDD 304 and executes various control processes of the device 105. The ROM 302 stores the programs executed by the CPU 301. The RAM 303 is used as a temporary storage area such as the main memory and work area of ​​the CPU 301. The HDD 304 is a storage device that stores image data, various programs, and various setting information. Note that the device 105 may include other storage devices such as an SSD (Solid State Drive) as a storage device.

[0022] The operation unit I / F 305 connects the operation unit 310 and the control unit 300. The operation unit 310 includes, for example, a display unit having a touch panel function, various hard keys, and the like. By associating input coordinates on the touch panel with display coordinates, it is possible to configure a GUI that makes it appear as if the user can directly operate a screen displayed on the touch panel. The operation unit 310 functions as a display unit that displays information to the user and a reception unit that receives instructions from the user.

[0023] The printer I / F 306 connects the printer 320 and the control unit 300. The printer 320 prints the document read by the reader or the image data stored in the HDD 304 on a recording medium (for example, on a sheet of paper). The printer 320 also prints the image data based on a print job. The image data printed by the printer 320 is transferred from the control unit 300 via the printer I / F. The scanner I / F 307 connects the scanner 330 and the control unit 300. The scanner 330 reads the document placed on the document platen and generates image data. The generated image data is input to the control unit 300 via the scanner I / F 307. Note that, in the present embodiment, an example has been described in which the device 105 has a printing function and a scanning function, but the device 105 may have at least one of the printing function and the scanning function.

[0024] The network I / F 308 is a communication interface that connects the device 105 to a network. For example, a network cable is connected to the network I / F 308 of the device 105, and the device 105 can communicate with an external device on the network. Note that, in this embodiment, it is assumed that the network I / F 308 is a communication interface that performs wired communication, but this is not limited to this. For example, the network I / F 308 may be a wireless communication interface.

[0025] 4 is a diagram for explaining the software configuration of the information processing device 104. The information processing device 104 has a monitoring mode management unit 401, a proxy server 402, a contract information management unit 403, a device management unit 405, a delivery schedule management unit 407, an event management unit 409, a load detection unit 411, a notification unit 412, and a display control unit 413. Furthermore, the information processing device 104 has, as databases, a setting information DB 404, a device information DB 406, a delivery information DB 408, and an event information DB 410. The software modules of the information processing device 104 are realized by the CPU 201 of the information processing device 104 executing a program stored in the memory (ROM 202 or HDD 204).

[0026] The monitoring mode management unit 401 manages the monitoring mode set in the information processing device 104. The monitoring modes include a proxy mode and a polling mode. In the polling mode, the information processing device 104 functioning as a monitoring device acquires data from a network device on the network 109 such as the device 105 by regular polling, transmits the acquired information to the device management system 100, and manages the device. In the proxy mode, the information processing device 104 functions as a proxy server that relays communication between a network device on the network 109 such as the device 105 and the device management system 100. The setting of the monitoring mode is set by the user when a relay application is installed in the information processing device 104, and is stored in a setting value management table of the setting information DB 404. The proxy server 402 collects communication from a network device on the network 109 such as the device 105, and relays communication between the network device and the device management system 100.

[0027] The contract information management unit 403 manages contract information related to the service provided by the device management system 100, which the user of the relay application has subscribed to. The contract information management unit 403 requests the management server 101 for contract information, and stores and manages the contract information received as a response from the management server 101 in the setting information DB 404. The request for contract information sent by the contract information management unit 403 includes, as user information, for example, an agent ID registered in the device management system 100 and a tenant ID in which the information processing device 104 is installed. The management server 101 identifies contract information based on the user information (for example, the agent ID and the tenant ID) included in the request for contract information, and sends the contract information to the information processing device 104 that made the request. The contract information includes, for example, the contract conclusion date, the service start date, the service end date, and the contract details. The contract details include information related to the contracted service. For example, if a firmware distribution service is subscribed to, the firmware distribution service is included in the contract details.

[0028] The setting information DB 404 is a database that stores the setting values ​​of the relay application. The setting information DB 404 stores the setting values ​​of the relay application in, for example, a setting value management table. Table 1 is an example of the setting value management table. [Table 1] The setting value management table includes a contract and a mode as setting items (Key). The contract indicates contract information of the service for which the relay application is used, and the setting value (Value) stores the contract information acquired from the management server 101. In the example shown in Table 1, the contract information stores the contract conclusion date, service start date, service end date, and contract details, and it can be seen that a contract has been made for a plurality of services including a firmware distribution service. The contract indicates the monitoring mode set in the relay application, and the setting value (Value) stores either Proxy, which indicates the proxy mode, or Polling, which indicates the polling mode. In the example shown in Table 1, it can be seen that the proxy mode is set.

[0029] The device management unit 405 manages device information of network devices on the network 109. That is, the device management unit 405 manages device information of network devices that communicate with the device management system 100 via the information processing device 104. The device information managed by the device management unit 405 includes, for example, information for identifying a device, a monitoring method (monitoring mode) of the device, and information indicating whether or not the device has been registered in a device management service provided by the device management system 100. For example, when a device is registered in the management server 101 as a target for providing a service, the device information is also registered in the information processing device 104 and stored in the device information DB 406.

[0030] The device information DB 406 is a database that stores device information. The device information DB 406 manages device information, for example, with a device management table. Table 2 is an example of the device management table. [Table 2] The device management table includes, as device information, for example, a device ID, a serial number, a type, and a registration state. The device ID and the serial number are information for identifying a device. The device ID is, for example, an ID given by the management server 101 when the device is registered. The serial number is, for example, an ID given to each device when the device is shipped. The type indicates a monitoring method (monitoring mode) of the device, and stores either Proxy indicating a proxy mode or Polling indicating a polling mode. The type is set based on the management mode set in the information processing device 104 and the capability information of the device when the device information is registered in the information processing device 104. The registration state is information indicating whether or not the device has been registered as a managed device of the device management service provided by the device management system 100. The registration state stores a value indicating either registered or unregistered. The device management table may further include information such as the model name of the device, the IP address set in the device, and a management status indicating whether or not the device is currently a target of the device management service.

[0031] The delivery schedule management unit 407 manages the delivery schedule for firmware delivery to the network devices. The delivery schedule management unit 407 acquires the delivery schedule for firmware delivery to the network devices set by the firmware delivery server 102, and stores it in the delivery information DB 408. The delivery schedule management unit 407 also functions as an adjustment unit that adjusts the delivery schedule set by the firmware delivery server 102 in consideration of the load on the proxy server 402. The delivery information DB 408 stores the schedule for firmware delivery to the network devices.

[0032] The event management unit 409 manages the schedule of event transmission of the network device. Event transmission is, for example, communication performed as information collection by the device management system 100, and the status of the network device, the state of consumables such as the number of printed sheets, and the like are periodically transmitted from the network device to the management server 101. The event information DB 410 stores the schedule of event transmission. Note that the objects managed by the event management unit 409 are not limited to event transmission, and the event management unit 409 may also manage the schedule of communication by services other than the firmware distribution service.

[0033] The load detection unit 411 detects a time period when the proxy server 402 is subjected to a load equal to or greater than a predetermined load due to communication performed via the proxy server 402. Since the function of the proxy server 402 is realized by software in the information processing device 104, which is a PC, the number of communication requests that the proxy server 402 can process simultaneously is limited. The load detection unit 411 detects, as the load detection of the communication load of the proxy server 402, whether or not the communication between the device and the server scheduled via the proxy server 402 exceeds the number of communication requests that the proxy server 402 can process simultaneously. In this embodiment, the load detection unit 411 performs load detection on the firmware distribution schedule. Also, in this embodiment, the number of devices to which firmware is distributed via the proxy server 402 is set as the number of communication requests processed by the proxy server 402.

[0034] The notification unit 412 controls notifications from the information processing device 104 to external devices such as the management server 101 and the firmware distribution server 102. The notifications include, for example, a warning notification that the communication load via the proxy server 402 described below exceeds a threshold, a notification of a change in schedule settings for firmware distribution, etc. The display control unit 413 controls the display on the display device of the operation unit 210.

[0035] Although the firmware distribution schedule for the network devices is set by the firmware distribution server 102, the firmware distribution server 102 does not hold information on which devices are managed via the proxy server 402. Therefore, there is a risk that the firmware distribution schedule set by the firmware distribution server 102 will exceed the number of communication requests that the proxy server 402 can process simultaneously. Therefore, the information processing device 104 having the proxy server 402 checks whether the firmware distribution communication executed according to the schedule set by the firmware distribution server 102 does not exceed the number of communication requests that the proxy server 402 can process. If the scheduled firmware distribution exceeds the number of communication requests that the proxy server 402 can process, the information processing device 104 issues a warning to the firmware distribution server 102. The firmware distribution server 102 that receives the warning displays a warning screen and requests the user who sets the schedule to change the schedule, etc., thereby making it possible to set a schedule that takes into account the load on the proxy server 402.

[0036] Therefore, in this embodiment, the information processing device 104 executes a delivery schedule check process for detecting the load on the proxy server 402 due to firmware delivery, based on a schedule of firmware delivery via the proxy server 402. Here, the flow of the delivery schedule check process will be described with reference to FIG. 5. FIG. 5 is a sequence diagram showing the delivery schedule check process. In FIG. 5, each process executed by the management server 101 of the device management system 100 is realized by the CPU 201 of the management server 101 executing a program stored in the memory (ROM 202 or HDD 204). Each process executed by the firmware delivery server 102 of the device management system 100 is realized by the CPU 201 of the firmware delivery server 102 executing a program stored in the memory (ROM 202 or HDD 204). Each process executed by the information processing device 104 is realized by the CPU 201 of the information processing device 104 executing a program stored in the memory (ROM 202 or HDD 204).

[0037] In S501, the information processing device 104 requests the management server 101 of the device management system 100 for contract information of the client. The request includes information for identifying the client. The contract information includes information of the service to which the client has subscribed, and it is possible to determine whether or not the client has subscribed to a firmware distribution service based on the contract information. In S502, the management server 101 of the device management system 100, which has received the request for contract information, transmits the client's contract information to the information processing device 104.

[0038] In S503, the information processing device 104 stores the contract information acquired in S502 in the contract information DB. In S504, the information processing device 104 checks the monitoring mode of its own device. The monitoring mode set in the information processing device 104 is either the polling mode or the proxy mode. If the monitoring mode is set to the polling mode, this process ends. On the other hand, if the monitoring mode is set to the proxy mode, the process of S505 is performed. Therefore, if the monitoring mode of the information processing device 104 is the proxy mode and the contract information includes a software distribution service, the processes from S505 onwards are performed.

[0039] The processes from S505 onwards are executed periodically. In S505, the information processing device 104 identifies the device that is the target of firmware distribution. In S506, the information processing device 104 requests the firmware distribution server 102 of the device management system 100 for a distribution schedule for the device identified in S504. In S507, the firmware distribution server 102 of the device management system 100 that has received the request for the distribution schedule transmits the distribution schedule to the information processing device 104.

[0040] In S508, the information processing device 104 detects a time period during which the proxy server 402 is under a load equal to or greater than a predetermined load, based on the distribution information acquired in S507. Here, the time period during which the proxy server 402 is under a load equal to or greater than a predetermined load refers to the time of day for which distribution is scheduled for devices that exceed the number of devices that the proxy server 402 can simultaneously process. If there is a time period during which the proxy server 402 is under a load, that is, if firmware distribution that exceeds the processing capacity of the proxy server 402 has been set, the information processing device 104 performs the process of S509.

[0041] In S509, the information processing device 104 transmits a warning notification to the firmware distribution server 102 of the device management system 100 based on the result of the detection in S508. The warning notification includes data that can identify the time period detected in S508. In S510, the firmware distribution server 102 of the device management system 100 that has received the warning notification from the information processing device 104 displays a warning screen based on the warning notification. The firmware distribution server 102 provides the warning screen to the user via, for example, a Web browser. The user (administrator) issues an instruction for adjusting the distribution schedule for the notified time period on a screen (UI) provided by the firmware distribution server 102. In adjusting the distribution schedule, for example, for some devices among those whose distribution schedule is set for a time period that places a load, the distribution schedule is changed to another schedule that does not place a load. Here, the schedule that does not place a load is a schedule that does not exceed the number of devices that the proxy server 402 can process simultaneously. The firmware distribution server 102 can receive an instruction from the administrator for adjusting the distribution schedule for the notified time period and set the schedule for firmware distribution based on the instruction.

[0042] Details of the process executed by the information processing device 104 in the distribution schedule confirmation process will be described with reference to Fig. 6. Fig. 6 is a flowchart showing the distribution schedule confirmation process in the first embodiment. Each process executed by the information processing device 104 in Fig. 6 is realized by the CPU 201 of the information processing device 104 executing a program stored in the memory (ROM 202 or HDD 204). This process is executed periodically, for example, once a week. In addition to the periodic process, it may also be executed when instructed by the user.

[0043] In S601, the monitoring mode management unit 401 determines whether or not the monitoring mode of the information processing device 104 is the proxy mode. Specifically, the monitoring mode management unit 401 determines whether or not the monitoring mode of the information processing device 104 is the proxy mode based on the setting value of the mode in the setting value management table (Table 1) stored in the setting information DB 404. If the monitoring mode is the proxy mode, the information processing device 104 performs the process of S602. On the other hand, if the monitoring mode is the polling mode, that is, if the monitoring mode is not the proxy mode, this process ends.

[0044] In S602, the contract information management unit 403 determines whether the client has contracted for the firmware distribution service, i.e., whether the client is a target for the firmware distribution service. Specifically, the contract information management unit 403 determines whether the client has contracted for the firmware distribution service based on the setting value of the contract (Contract) in the setting value management table (Table 1) stored in the setting information DB 404. If the setting value of the contract (Contract) includes the firmware distribution service, i.e., if the client has contracted for the firmware distribution service, the information processing device 104 performs the process of S603. On the other hand, if the setting value of the contract (Contract) does not include the firmware distribution service, i.e., if the client has not contracted for the firmware distribution service, this process ends.

[0045] In S603, the device management unit 405 identifies network devices that are targets of the firmware distribution service executed via the proxy server 402 of the information processing device 104. Specifically, the device management unit 405 identifies devices that are registered in the device management table as having a type of proxy and a registration state of registered, as devices that are targets of the firmware distribution service executed via the proxy server 402. In the example shown in Table 2, devices with device IDs Device01 and Device02 are identified as devices that are targets of the firmware distribution service executed via the proxy server 402.

[0046] In S604, the delivery schedule management unit 407 requests the firmware delivery schedule (firmware delivery information) of the network device identified in S603 from the firmware delivery server 102. The request includes information that uniquely identifies the network device identified in S603, such as a serial number. The firmware delivery server 102, which has received the request for the firmware delivery schedule from the information processing device 104, identifies and returns a firmware delivery schedule to respond to, based on the information that uniquely identifies the network device included in the request. In S605, the delivery schedule management unit 407 acquires the firmware delivery schedule (firmware delivery information) of the network device identified in S603 from the firmware delivery server 102. The firmware delivery schedule (firmware delivery information) includes, for example, information that identifies the device (for example, a serial number) and the day of the week and time when firmware delivery is scheduled. Table 3 is an example of firmware delivery information. [Table 3] In the example shown in Table 3, for example, a device with serial number Serial0001 is scheduled for firmware distribution at 2:00 on Monday.

[0047] In S606 to S608, the load detection unit 411 detects a time period (schedule) in which the scheduled firmware distribution places a load equal to or greater than a predetermined load on the proxy server 402. In S606, the load detection unit 411 tallies up the schedule of firmware distribution executed via the proxy server 402. Specifically, the load detection unit 411 tallies up the number of devices for which firmware distribution is scheduled for each schedule, based on the firmware distribution schedule (firmware distribution information) acquired in S605. Here, in this embodiment, for each schedule, it means for each time of day of the week. Also, devices that are targets of firmware distribution for which no distribution schedule is set are tallied up as having no schedule set. Table 4 shows an example of the tallied results for each schedule. [Table 4]

[0048] In S607, the load detection unit 411 compares the number of devices counted in S606 with the number of devices set as a threshold for each schedule, and checks whether the number of devices counted in S606 exceeds the threshold. The number of devices set as the threshold is a number of devices set based on the number of devices that can communicate simultaneously with the proxy server 402, and may be a number set as a default value by the device management system 100 or a number specified by a user. In this embodiment, the number of devices set as the threshold is 200. In the example shown in Table 4, the number of devices with a delivery schedule set for 2:00 on Monday is 400, which exceeds the threshold. On the other hand, the number of devices with a delivery schedule set for 3:00 on Tuesday is 150, which does not exceed the threshold.

[0049] In S608, the load detection unit 411 detects a schedule (time period) that exceeds the load of the proxy server 402. Specifically, the load detection unit 411 judges whether a schedule in which firmware distribution for a number of devices exceeding the threshold value is set has been confirmed in S607. If a schedule in which firmware distribution for a number of devices exceeding the threshold value is confirmed, that is, if there is a schedule for firmware distribution that exceeds the performance of the proxy server 402, the process of S609 is performed. On the other hand, if a schedule in which firmware distribution for a number of devices exceeding the threshold value is not confirmed, that is, if there is only a schedule for firmware distribution that can be processed by the proxy server 402, this process ends. In the example shown in Table 4, 2:00 on Monday is detected as a time period in which the proxy server 402 is under load.

[0050] In S609, the load detection unit 411 notifies the firmware distribution server 102 of a warning via the notification unit 412 based on the result of the detection in S608. The notified warning includes, for example, a message that firmware distribution may fail under the current firmware distribution schedule, and data on a time period during which the proxy server 402 will be subjected to a load equal to or greater than a predetermined value. A schedule in which firmware distribution may fail is a schedule in which the number of devices counted in S606 exceeds a threshold value. The warning notification may also include the number of devices set as a threshold value.

[0051] The process by the information processing device 104 is completed with a warning notification in S609. The firmware distribution server 102 that has received the warning notification from the information processing device 104 displays a warning screen in response to the warning notification. FIG. 7 is a diagram showing an example of the warning screen. The warning screen 700 includes, for example, a message indicating that firmware distribution may fail under the current schedule, the number of devices that can communicate simultaneously with the proxy server 402 set as a threshold, and a schedule for which firmware distribution may fail. The warning screen is displayed on an information processing device such as a PC of a user who uses the firmware distribution service provided by the firmware distribution server 102 via a Web browser. A user who sets a schedule for firmware distribution to a network device can re-set the schedule for firmware distribution taking into account the load of the proxy server 402 by checking the warning screen 700. This makes it possible to suppress the risk of firmware distribution failing due to the performance of the information processing device 104 functioning as the proxy server 402. In the present embodiment, an example has been described in which a warning is notified only when the number of devices targeted for firmware distribution, which is counted for each schedule, exceeds a threshold, but the present invention is not limited to this. For example, even if the number of devices to which firmware distribution is to be performed does not exceed the threshold value in any schedule, a notification may be given that there is no problem with the firmware distribution schedule.

[0052] As described above, according to this embodiment, in an information processing apparatus having a proxy server 402, it is possible to detect a time period during which scheduled firmware distribution places a load on the proxy server 402. Then, when the number of devices communicating simultaneously is greater than a specified value and there is a possibility that firmware distribution will fail due to the load on the proxy server 402, a warning is sent to the firmware distribution server 102, and it is possible to prompt the user to reconsider the schedule. This makes it possible to perform schedule management to prevent firmware distribution via a proxy server from failing.

[0053] Second embodiment In the first embodiment, only the load due to firmware distribution was counted to detect the load on the proxy server 402, but communication via the proxy server 402 also involves communications other than firmware distribution. There may be multiple services that are not dependent on each other that execute communications other than firmware distribution, and it is difficult for the firmware distribution server 102 to grasp these communications. For this reason, in this embodiment, the schedule for firmware distribution via the proxy server 402 can be confirmed taking into consideration the load on the proxy server 402 due to other services in addition to the firmware distribution service. Below, only the differences from the first embodiment will be described, and the same configurations and processes as those in the first embodiment will be denoted with the same reference numerals and their description will be omitted.

[0054] Details of the process executed by the information processing device 104 in the distribution schedule confirmation process will be described with reference to Figs. 8 and 9. Figs. 8 and 9 are flowcharts showing the distribution schedule confirmation process in the second embodiment. Each process executed by the information processing device 104 in Figs. 8 and 9 is realized by the CPU 201 of the information processing device 104 executing a program stored in the memory (ROM 202 or HDD 204). This process is executed periodically, for example, once a week. In addition to the periodic process, it may also be executed when instructed by the user.

[0055] After tallying up the schedule of firmware distribution executed via the proxy server 402 in S606, the information processing device 104 performs processing in S801. In S801, the event management unit 409 requests the device management system 100 for a schedule of communication by other services of the firmware distribution service for the device identified in S603. That is, the event management unit 409 requests a schedule of communication other than the firmware distribution schedule executed via the proxy server 402. In this embodiment, an event transmission schedule by a remote monitoring service of a device is described as an example of a schedule by other services of the firmware distribution service, but this is not limited thereto. In addition, there may be a plurality of other services of the firmware distribution service. For example, the event management unit 409 requests an event transmission schedule from the management server 101 that provides a remote monitoring service of a device. The request includes information (for example, a serial number) that identifies the device identified in S603. The device management system 100 that receives a request from the information processing device 104 having the proxy server 402 transmits a schedule of communication by other services of the firmware distribution service to the information processing device 104 based on the information that identifies the device. For example, the management server 101 of the device management system 100 transmits an event transmission schedule of a target device to the information processing device 104 .

[0056] In S802, the event management unit 409 acquires a communication schedule other than the firmware distribution schedule of the network device identified in S603 from the device management system 100. The information of the communication schedule other than the firmware distribution schedule includes information for identifying the device (e.g., a serial number) and the day of the week and time when communication is scheduled.

[0057] In S803, the load detection unit 411 counts up the schedules of communications other than firmware distribution executed via the proxy server 402. Specifically, the load detection unit 411 counts up the number of devices for which communications other than firmware distribution are scheduled for each schedule (for each time of day of the week) based on the communication schedule other than the firmware distribution schedule acquired in S802. In this embodiment, the load detection unit 411 counts up the number of devices for which event transmission by a device remote monitoring service is scheduled for each schedule (for each time of day of the week).

[0058] In S804, the load detection unit 411 counts the number of devices for scheduled communications executed via the proxy server 402 for each schedule (for each time of day of the week). Specifically, the load detection unit 411 counts the number of devices for each schedule (for each time of day of the week) by combining the schedule of firmware distribution counted in S606 with the schedule of other communications for firmware distribution counted in S803.

[0059] In S805, the load detection unit 411 compares the number of devices counted in S804 with the number of devices set as a threshold for each schedule, and checks whether the number of devices counted in S804 exceeds the threshold. The number of devices set as the threshold is set based on the number of devices that can communicate simultaneously with the proxy server 402. In this embodiment, the number of devices set as the threshold is 200.

[0060] In S806, the load detection unit 411 detects a schedule that exceeds the load of the proxy server 402. Specifically, the load detection unit 411 determines whether a schedule in which communication for a number of devices exceeding the threshold has been confirmed in S805. If a schedule in which communication for a number of devices exceeding the threshold has been confirmed, that is, if there is a schedule for communication that exceeds the performance of the proxy server 402, the process of S807 is performed. On the other hand, if a schedule in which communication for a number of devices exceeding the threshold has not been confirmed, that is, if there is only a schedule for communication that can be processed by the proxy server 402, this process ends.

[0061] In S807, the load detection unit 411 notifies the firmware distribution server 102 of a warning via the notification unit 412. The notified warning includes, for example, a message that firmware distribution may fail under the current schedule and a schedule in which firmware distribution may fail. A schedule in which firmware distribution may fail is a schedule in which the number of devices counted in S804 exceeds a threshold. The warning notification may also include the number of devices set as a threshold.

[0062] In this embodiment, only the number of devices including firmware distribution and other communications is compared with the threshold value. In addition, the number of devices in firmware distribution may be compared with the threshold value. This can be realized, for example, by performing the processes of S607 and S608 in the first embodiment between S606 and S801. Furthermore, when there are communications by multiple services other than firmware distribution, the number of devices for each schedule may be tallied for each service and compared with the threshold value. This allows the information processing device 104 to issue a more detailed warning notice about communications that cause a load on the proxy server 402. For example, a warning screen based on the warning notice can display more specifically the services that schedule communications and the number of devices for the schedules that exceed the threshold value, and the user can understand this through the warning screen and use it to reset the schedule.

[0063] As described above, according to this embodiment, it is possible to detect a time period during which the proxy server 402 is under load, taking into consideration cases in which other firmware distribution services schedule communications via the proxy server 402. This makes it possible to perform schedule management to prevent failures in software distribution via the proxy server.

[0064] Third embodiment In the first and second embodiments, when the load on the proxy server exceeds a specified value, a warning is sent to the firmware distribution server, and the firmware distribution server provides the user with a warning screen in response to the notification, urging the user to set a schedule. In this embodiment, in order to reduce the burden on the user of resetting the schedule, an appropriate schedule is automatically reset so that the load on the proxy server does not exceed a specified value. Therefore, in this embodiment, when the load on the proxy server exceeds a specified value, an information processing device having the proxy server resets an appropriate schedule so that the load on the proxy server does not exceed a specified value, and notifies the firmware distribution server of the setting.

[0065] Details of the processing executed by the information processing device 104 in the distribution schedule confirmation processing of this embodiment will be described with reference to Fig. 10. Fig. 10 is a flowchart showing the distribution schedule confirmation processing in the third embodiment. Each process executed by the information processing device 104 in Fig. 10 is realized by the CPU 201 of the information processing device 104 executing a program stored in the memory (ROM 202 or HDD 204). This processing is executed periodically, for example, once a week. In addition to the periodic processing, it may also be executed when instructed by the user.

[0066] The processes of S601 to S608 are the same as those in the first embodiment. In S1001, the distribution schedule management unit 407 performs a schedule setting process. That is, instead of the warning notification process (S609) in the first embodiment, the schedule setting process is performed in this embodiment. Similarly, instead of the warning notification process (S807) in the second embodiment, a schedule setting process (S1001) may be performed. In the schedule setting process, the information processing device 104 adjusts the distribution schedule taking into account the load of the proxy server 402, and notifies the firmware distribution server 102 of the adjusted schedule.

[0067] Details of the schedule setting process will be described with reference to Fig. 11 and Fig. 12. Fig. 11 and Fig. 12 are flowcharts showing the schedule setting process. Each process executed by the information processing device 104 in Fig. 11 and Fig. 12 is realized by the CPU 201 of the information processing device 104 executing a program stored in the memory (ROM 202 or HDD 204).

[0068] In S1101, the delivery schedule management unit 407 displays a schedule setting screen. Specifically, the delivery schedule management unit 407 displays the schedule setting screen on the display device of the operation unit 210 of the information processing device 104 via the display control unit 413. The schedule setting screen is a screen for the user to set a schedule for firmware delivery. An example of the schedule setting screen is shown in FIG.

[0069] FIG. 13 is a diagram showing an example of a schedule setting screen. The schedule setting screen 1300 includes a confirmation time 1301 for setting a time when firmware distribution is possible, an application time 1302 for setting a time when the confirmation time 1301 is applied, and a setting button 1303 for reflecting the set contents. In the confirmation time 1301, the user sets a schedule (day of the week and time period) when firmware distribution is possible. In the confirmation time 1301, multiple days of the week and time periods can be set. If the number of devices that can communicate simultaneously with the proxy server 402 is exceeded, the information processing device 104 sets a new schedule for firmware distribution for the excess devices, but at the time of setting, the schedule set in the confirmation time 1301 is set preferentially. In the application time 1302, the time when the confirmation time 1301 is applied is set. For example, in the application time 1302, the time after which the setting is to be applied, such as after two hours, may be set, or a date and time may be specified. In addition, 0 hours may be specified when applying immediately. When the setting of the confirmation time 1301 and the application time 1302 is completed, the user presses the setting button 1303. When detecting that the setting button 1303 is pressed, the information processing apparatus 104 performs the process of S1102.

[0070] In S1102, the delivery schedule management unit 407 saves the setting contents of the schedule setting screen 1300. The delivery schedule management unit 407 saves, for example, the confirmation time 1301 and the application time 1302 specified on the schedule setting screen 1300 as a delivery schedule in the delivery information DB 408. Note that the processes of S1101 and S1102 may be performed in advance.

[0071] In S1103, the delivery schedule management unit 407 determines the number of devices for which firmware delivery can be set for each schedule. The number of devices for which firmware delivery can be set is determined based on the performance of the proxy server 402 and the number of devices that communicate via the proxy server 402. Since the number of devices that can simultaneously communicate with the proxy server 402 is determined by the performance of the proxy server 402, the number of devices for which firmware delivery can be set is determined so that the total number of devices that perform firmware delivery and communications other than firmware delivery does not exceed this number. Therefore, if firmware delivery does not overlap with a communication schedule for other services such as event transmission, the number of devices for which firmware delivery can be set is the number of devices for which firmware delivery can be set (a specified value) that can simultaneously communicate with the proxy server 402. If firmware delivery overlaps with a communication schedule for other services such as event transmission, the number of devices obtained by subtracting the number of devices that communicate with other services from the specified value is the number of devices for which firmware delivery can be set.

[0072] In S1104, the distribution schedule management unit 407 selects one schedule to be the target of the schedule change process. The processes of S1105 to S1110 are executed for the schedule selected in S1104, and by performing this for all schedules, it is possible to adjust the firmware distribution schedule to take into account the performance of the proxy server 402.

[0073] In S1105, the delivery schedule management unit 407 determines whether the number of devices (number of set devices) that communicate via the proxy server 402 set in the schedule selected in S1004 exceeds the number of settable devices determined in S1103. If the number of set devices exceeds the number of settable devices, the process of S1106 is performed. On the other hand, if the number of set devices does not exceed the number of settable devices, the process of S1111 is performed.

[0074] In S1106, the delivery schedule management unit 407 checks whether a schedule of another executable firmware delivery is set for a set device (excess device) that exceeds the number of settable devices. The other executable schedule is a schedule that is different from the schedule selected in S1104 among the schedules set for the excess device, and the number of set devices in the schedule does not exceed the number of settable devices. If a schedule of another executable firmware delivery is set, the process of S1107 is performed. On the other hand, if a schedule of another executable firmware delivery is not set, the process of S1108 is performed. In S1107, the delivery schedule management unit 407 changes the setting of the schedule of firmware delivery for the excess device. Specifically, the delivery schedule management unit 407 performs schedule adjustment to set a schedule of another executable firmware delivery as a schedule of firmware delivery for the excess device, and delete the schedule selected in S1004. The delivery schedule management unit 407 stores the adjusted schedule of firmware delivery in the delivery information DB 408.

[0075] If no other executable firmware distribution schedule is set for the excess device, the schedule setting is changed based on the schedule set in the confirmation time 1301 of the schedule setting screen 1300. In S1108, the distribution schedule management unit 407 checks whether the schedule of the excess device can be changed to another time on the same day of the week. The schedule that can be set in S1108 is a schedule that can be set for a different time on the same day of the week as the schedule currently set for the excess device, among the schedules set in the confirmation time 1301 of the schedule setting screen 1300. The settable schedule is a schedule in which the number of devices set for the schedule does not exceed the number of devices that can be set. The distribution schedule management unit 407 checks whether the schedule of the excess device can be changed to another time on the same day of the week, based on the distribution schedule stored in the distribution information DB 408. If the schedule of the excess device can be changed to another time on the same day of the week, the process of S1109 is performed. On the other hand, if the schedule of the excess device cannot be changed to another time on the same day of the week, the process of S1110 is performed. In S1109, the delivery schedule management unit 407 changes the setting of the firmware delivery schedule for the excess device. Specifically, the delivery schedule management unit 407 adjusts and sets the firmware delivery schedule for the excess device to a different time on the same day within the schedule set in the confirmation time 1301. The delivery schedule management unit 407 saves the adjusted firmware delivery schedule in the delivery information DB 408.

[0076] In S1110, the delivery schedule management unit 407 changes the setting of the firmware delivery schedule for the excess device. The delivery schedule management unit 407 adjusts and sets, as the delivery schedule for the excess device, a schedule for firmware delivery within the schedule set in the confirmation time 1301 in which the number of set devices does not exceed the number of settable devices. The delivery schedule management unit 407 stores the adjusted firmware delivery schedule in the delivery information DB 408.

[0077] In S1111, the delivery schedule management unit 407 determines whether all schedules have been checked. If all schedules have been selected in S1104, the delivery schedule management unit 407 performs processing in S1112, assuming that all schedules have been checked. On the other hand, if selection of all schedules has not been completed in S1104, it is assumed that all schedules have not been checked, and the process returns to S1104. In S1104, a new unselected schedule is selected.

[0078] In S1112, the delivery schedule management unit 407 notifies the firmware delivery server 102 of the changed firmware delivery schedule via the notification unit 412. The delivery schedule management unit 407 notifies the firmware delivery server 102 of the changed firmware delivery schedule for the devices whose settings have been changed, i.e., the excess devices. The firmware delivery server 102, which has received a notification of the setting change from the information processing device 104, updates the firmware delivery schedule for the target device based on the contents of the notification and stores the updated schedule. Through the above processing, it becomes possible for the information processing device 104 having the proxy server 402 to change the delivery schedule for the devices that use the proxy server 402 to an appropriate one and have the firmware delivery server 102 apply the schedule change.

[0079] In the first to third embodiments, the information processing device 104 is a PC or the like, but the information processing device 104 may be a network device (e.g., an image processing device) that is managed by the device management system 100. In this case, a proxy server is built into the image processing device that is a network device, and the image processing device on the network 109 that includes the image processing device communicates with the device management system 100 via the proxy server.

[0080] In the first to third embodiments, the information processing device 104 having the proxy server 402 detects the load and changes the schedule, but the firmware distribution server 102 may detect the load and change the schedule. The firmware distribution server 102 does not manage the network environment of the client, and does not have information on which network device is communicating via the proxy server 402. Therefore, the firmware distribution server 102 needs to obtain information on the network device (target device) that performs firmware distribution via the proxy server 402 from the information processing device 104. In response to a request to specify a device from the firmware distribution server 102, the information processing device 104 performs the processes of S601 to S603, specifies information on the target device, and transmits the specified information to the firmware distribution server 102. The firmware distribution server 102 that has obtained the information on the target device performs the same processes as S605 to S608 to detect the load on the proxy server 402, and displays the warning screen 700 based on the result of the load detection. In this way, it is possible to obtain necessary information from the information processing device 104 having the proxy server 402 and detect the load and change the schedule on the firmware distribution server 102 side.

[0081] As described above, according to the present embodiment, it is possible to adjust the firmware distribution schedule taking into account the performance of the proxy server, thereby enabling schedule management to be performed to prevent failures in software distribution via a proxy server.

[0082] The disclosure of this embodiment includes the following configuration of an information processing device. (Configuration 1) An information processing apparatus having a proxy server that relays communication between a network device and a software distribution system that provides a software distribution service to the network device, a distribution schedule management unit that acquires, from the software distribution system, a distribution schedule for a network device that is a target of the software distribution service and that communicates via the proxy server; a load detection unit that detects a time period during which a load equal to or greater than a predetermined load is applied to the proxy server due to communications with the plurality of network devices via the proxy server based on the delivery schedule; a notification unit that notifies the software distribution system based on a result of the detection. (Configuration 2) 2. The information processing apparatus according to configuration 1, wherein the load on the proxy server is determined based on the number of devices that communicate via the proxy server. (Configuration 3) The information processing device according to configuration 1 or 2, characterized in that when the monitoring mode in which the information processing device monitors the network device is a proxy mode, and when contract information including the contract contents of a client's service is obtained from a device management system that manages the network device, and the contract contents include a software distribution service, the information processing device periodically identifies a network device that obtains a distribution schedule from the software distribution system, obtains the distribution schedule of the network device from the software distribution system, and detects a time period when the proxy server is under a predetermined load or more based on the distribution schedule. (Configuration 4) The information processing device described in any one of configurations 1 to 3, characterized in that the notification includes data that can identify the detected time period, and the software distribution system that receives the notification provides a warning screen to inform the user of the time period during which the proxy server will be subjected to a load greater than a specified level. (Configuration 5) 5. The information processing device according to configuration 4, wherein the software distribution system is capable of receiving an instruction from an administrator for adjusting a distribution schedule for the notified time period. (Configuration 6) The information processing device of any one of configurations 1 to 5, wherein the load detection unit detects a time period during which the proxy server is under a predetermined load or more based on the distribution schedule and a schedule of communication between other services of the software distribution service and the network device via the proxy server. (Configuration 7) an adjusting unit that adjusts a delivery schedule for a time period when a time period during which the proxy server is under a load equal to or greater than a predetermined load is detected; The information processing device according to any one of configurations 1 to 3, characterized in that the notification is a notification of an adjusted new distribution schedule, and the software distribution system that receives the notification updates the software distribution schedule based on the notification.

[0083] (Other embodiments) The present invention can also be realized by a process in which a program for implementing one or more of the functions of the above-described embodiments is supplied to a system or device via a network or a storage medium, and one or more processors in a computer of the system or device read and execute the program. The present invention can also be realized by a circuit (e.g., ASIC) that implements one or more of the functions.

[0084] Although the preferred embodiments of the present invention have been described above, the present invention is not limited to these embodiments, and various modifications and changes are possible within the scope of the gist of the present invention.

Claims

1. An information processing apparatus having a proxy server that relays communication between a network device and a software distribution system that provides a software distribution service to the network device, a distribution schedule management unit that acquires, from the software distribution system, a distribution schedule for a network device that is a target of the software distribution service and that communicates via the proxy server; a load detection unit that detects a time period during which a load equal to or greater than a predetermined load is applied to the proxy server due to communications with the plurality of network devices via the proxy server based on the delivery schedule; a notification unit that notifies the software distribution system based on a result of the detection.

2. 2 . The information processing apparatus according to claim 1 , wherein the load on the proxy server is determined based on the number of devices that communicate via the proxy server.

3. The information processing device according to claim 1, characterized in that when the monitoring mode in which the information processing device monitors the network device is a proxy mode, and when contract information including the contract contents of a client's service is obtained from a device management system that manages the network device, and the contract contents include a software distribution service, the information processing device periodically identifies a network device that obtains a distribution schedule from the software distribution system, obtains the distribution schedule of the network device from the software distribution system, and detects a time period when the proxy server is under a predetermined load or more based on the distribution schedule.

4. The information processing device described in claim 1, characterized in that the notification includes data that can identify the detected time period, and the software distribution system that receives the notification provides a warning screen to the user to indicate the time period during which the proxy server will be subjected to a load greater than a specified level.

5. 5. The information processing apparatus according to claim 4, wherein said software distribution system is capable of accepting an instruction from an administrator for adjusting a distribution schedule for the notified time period.

6. The information processing device according to claim 1, characterized in that the load detection unit detects a time period during which the proxy server is under a predetermined load or more based on the distribution schedule and a schedule of communication between other services of the software distribution service and the network device via the proxy server.

7. an adjusting unit that adjusts a delivery schedule for a time period when a time period during which the proxy server is under a load equal to or greater than a predetermined load is detected; 2. The information processing apparatus according to claim 1, wherein the notification is a notification of an adjusted new distribution schedule, and the software distribution system that has received the notification updates the software distribution schedule based on the notification.

8. 1. A method for controlling an information processing apparatus having a proxy server that relays communication between a network device and a software distribution system that provides a software distribution service to the network device, comprising: acquiring, from the software distribution system, a distribution schedule for a network device that is a target of the software distribution service and that communicates via the proxy server; detecting a time period during which a load equal to or greater than a predetermined load is placed on the proxy server due to communications with the plurality of network devices via the proxy server based on the delivery schedule; and notifying the software distribution system based on a result of the detection.

9. A program for causing a computer of an information processing device to execute each step according to claim 8.

Images