Information processing apparatus, method, and program

Abstract

To provide an information processing apparatus, method and program for distributing a load due to access to a management server by a management client and a load on a network in an environment where the management client is installed.SOLUTION: A monitoring apparatus is an information processing apparatus that relays communication between a network device and a device management server that manages the network device, the monitoring apparatus including a collection unit that acquires management information about the network device, a data management unit that executes calculation processing for calculating the number of threads of the management information to be transmitted to the device management server by multi-thread based on the number of network devices that relay communication, and an adjustment unit that executes adjustment processing for adjusting a waiting time after the management information is transmitted to the device management server by multi-thread based on a type of the management information and a data amount of the management information. And a transmission part for transmitting the management information to the device management server by multi-thread on the basis of the calculated number of threads and the standby time adjusted by the adjustment means.SELECTED DRAWING: Figure 5

Description

[Technical Field]

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

[0002] Conventionally, there have been known device management systems that perform maintenance over a network on network devices such as image forming apparatuses installed in offices, etc. By using a device management system, it is possible to detect via the network that a failure has occurred in a network device, that the network device needs to be replenished with consumables, and so on, and to respond promptly.

[0003] A known conventional device management system includes a device management server and a monitoring device. The device management server manages each device in a unified manner. The monitoring device acts as a management client that collects management information from multiple network devices and sends it to the device management server when a failure occurs or at regular intervals.

[0004] However, with conventional device management systems, when the number of devices to be managed increases and data is set to be sent at specific times, such as outside of business hours, multiple monitoring devices will start sending data simultaneously. As a result, conventional device management systems are expected to increase the load on the network in the environment where the network devices are installed, as well as the load due to access to the server.

[0005] Patent Document 1 discloses a server system that adds a waiting time that is randomly calculated within a predetermined time from the set transmission timing when multiple devices are activated simultaneously. As a result, the server system reduces the load on the network in the environment where the devices are installed and the load caused by access to the server. Furthermore, since the server system is used in an environment where the amount of data transmitted per device is not large, there is no need to consider the transmission interval, transmission time, etc. after data transmission has started. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] Patent Publication No. 2021-131774 Summary of the Invention [Problem to be solved by the invention]

[0007] However, management clients that collect large amounts of management information from multiple devices and send it to a device management server may send large amounts of management information simultaneously in a short period of time at regular intervals, which increases the load on the network in which the management clients are installed and the load caused by accessing the server.

[0008] Therefore, the management client needs to transmit data over time rather than all at once in a short period of time, thereby reducing the number of requests received by the management server during peak times. On the other hand, the management client needs to avoid taking too long to transmit data, which could result in the data being transmitted during specific time periods such as outside of business hours.

[0009] Furthermore, depending on the timing of data transmission, management clients may send large amounts of data to the management server all at once in a short period of time, which may further increase the load caused by accessing the management server and the load on the network in the environment where the management clients are installed.

[0010] Therefore, an object of the present invention is to distribute the load caused by access to a management server by a management client and the load on a network in an environment where the management client is installed. [Means for solving the problem]

[0011] In order to solve the above-mentioned problems, an information processing apparatus according to the present invention includes: an acquisition means for acquiring management information, which is information about network devices; a calculation means for executing a calculation process for calculating the number of threads for the management information to be transmitted to the device management server in multithreads based on the number of network devices that relay communication; an adjustment means for executing an adjustment process for adjusting a wait time after transmitting the management information to the device management server in multithreads based on the type of the management information and the data amount of the management information; and a transmission means for transmitting the management information to the device management server in multithreads based on the number of threads calculated by the calculation means and the wait time adjusted by the adjustment means. The information processing apparatus according to the present invention relays communication between network devices and a device management server that manages the network devices. [Effects of the Invention]

[0012] According to the present invention, it is possible to provide an information processing device, method, and program that can distribute the load caused by access to a management server by a management client and the load on a network in an environment in which the management client is installed. [Brief explanation of the drawings]

[0013] [Figure 1] 1 is a diagram illustrating an overall device management system according to a first embodiment. [Figure 2] 1 is a block diagram illustrating an example of a hardware configuration of an image forming apparatus as a network device according to a first embodiment. [Figure 3] 2 is a block diagram illustrating an example of the internal configuration of a monitoring device and a server according to the first embodiment. FIG. [Figure 4] 1 is a block diagram illustrating an example of a functional configuration of an image forming apparatus as a network device according to a first embodiment. [Figure 5] 1 is a block diagram illustrating an example of a functional configuration of a monitoring device according to a first embodiment. [Figure 6] FIG. 4 is a diagram illustrating an example of a transmission schedule setting screen displayed by a screen control unit of the monitoring device according to the first embodiment. [Figure 7] 4 is a diagram illustrating an example of management information and transmission data of devices managed by a data management unit of the monitoring device according to the first embodiment. FIG. [Figure 8] 10 is a flowchart illustrating an example of a process for managing the number of threads transmitted by a transmission unit of the monitoring device according to the first embodiment. [Figure 9] 10 is a flowchart illustrating an example of a process related to a thread transmitted by a transmission unit of the monitoring device according to the first embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0014] Hereinafter, embodiments of the present invention will be described using examples and drawings. However, the present invention is not limited to the following examples. In each drawing, the same members or elements are given the same reference numerals. In addition, in the following examples, descriptions of overlapping content will be omitted or simplified.

[0015] Example 1 1 is a diagram illustrating an overall device management system according to the first embodiment. The device management system according to the first embodiment is a system that manages an image forming apparatus 107 (hereinafter, sometimes referred to as a device) as a network device. Note that the network device is not limited to an image forming apparatus, and may be any device that can be connected to a network.

[0016] The device management server 101 manages information about the image forming device 107 and the monitoring device 106 that are the targets of various services. The authentication and authorization server 102 provides an authentication and authorization function for securely connecting the image forming device 107 and the monitoring device 106 to various servers.

[0017] In the first embodiment, a general OAuth mechanism is used, and each device (such as the image forming device 107 and the monitoring device 106) is registered as a client associated with a specific tenant. Here, a tenant refers to a management unit assigned to each customer who has signed a service usage contract.

[0018] The authentication and authorization server 102 manages data on a tenant-by-tenant basis. The authentication and authorization server 102 also issues tokens to clients such as the image forming device 107 and the monitoring device 106. Each device (such as the image forming device 107 and the monitoring device 106) can access various servers by using the tokens.

[0019] The resource server 103 manages information collected from the image forming apparatus 107. This information is mainly required to provide services to the image forming apparatus 107.

[0020] In response to a request from each device (such as the image forming device 107 or the monitoring device 106), the access destination management server 104 provides the URL of the device management server 101, resource server 103, or the like that each device accesses.

[0021] The service providing server 105 provides various services such as maintenance services and reporting services based on various information about the image forming device 107 managed by the resource server 103. The service providing server 105 provides a web user interface (WebUI) to the user, which enables the service providing server 105 to set information about each device (image forming device 107, monitoring device 106, etc.) that the user wishes to manage.

[0022] The information of each device set by the above-mentioned web user interface can also be reflected in the device management server 101 and the resource server 103. The servers 101 to 105, the monitoring device 106, and the image forming device 107 are connected to a network (WAN (Wide Area Network) 108 and LAN (Local Area Network) 109).

[0023] The monitoring device 106 is an example of an information processing device that relays communication between network devices and a device management server 101 that manages the network devices. Multiple monitoring devices 106 exist on the network, and each operates in the standard time zone of the area in which it is located. Furthermore, multiple monitoring devices 106 may be installed on a single LAN 109, and each may monitor a different image forming device 107.

[0024] FIG. 2 is a block diagram illustrating an example of a hardware configuration of an image forming apparatus as a network device according to the first embodiment.

[0025] A CPU (Central Processing Unit) 201 executes a computer program that is stored in a ROM (Read Only Memory) 202 or an HDD (Hard Disk Drive) 205 and controls all devices connected to a system bus 206. A RAM 203 functions as a work area for the CPU 201. An HDC 204 is a hard disk controller that controls the HDD 205. A reader I / F 207 is connected to a reader unit 212 and controls the device. A printer I / F 208 is connected to a printer unit 213 and controls the device.

[0026] The operation unit I / F 209 is connected to the operation unit 214 and controls the display on the operation unit 214, input by the user using the operation unit 214, etc. The operation unit 214 is composed of buttons for operation, a display unit, etc. The switch I / F 210 is connected to the switch unit 215 and controls operations using the switch unit 215. The switch unit 215 is composed of switches for operation, etc. The network I / F 216 transmits and receives data to and from external devices such as a host computer via a network 217.

[0027] The overall control unit 211 controls various devices and interfaces connected to the image forming apparatus 107, and also controls the operation of the entire device. The reader unit 212 functions as a scanner. The reader unit 212 reads an image of an original document and outputs image data corresponding to the image to the printer unit 213 based on instructions from the user. Alternatively, the reader unit 212 reads an image of an original document and stores image data corresponding to the image in a storage device of the device based on instructions from the user. The reader unit 212 can also transmit the image data to a host computer connected to a network 217 via a network I / F 216.

[0028] The printer unit 213 functions as a printer. The printer unit 213 prints image data based on an original read by the reader unit 212, image data stored in the HDD 205 serving as a storage device within the device body, and the like. The printer unit 213 also receives a print job from a host computer connected to a network 217 via a network I / F 216, and prints the image data related to the print job. The network I / F 216 is connected via the network 217, and is used by the overall control unit 211 to communicate with other information devices on the network 217.

[0029] The operation unit 214 uses buttons, a display device, a liquid crystal display screen with touch panel input, or a combination of these to display information to the user by the overall control unit 211, and notify the overall control unit 211 of inputs by the user, etc. The switch unit 215 controls the ON / OFF state of the power supply to the overall control unit 211.

[0030] 3 is a block diagram showing an example of the internal configuration of the monitoring device and server according to the first embodiment. The communication I / F unit 301 is a network interface for communicating with external systems and devices. The storage device 302 stores an operating system (OS), computer programs, management data, data collected from external systems and devices, etc. The CPU 303 as a computer loads the computer program from the storage device 302 into memory 304 and executes it. The output I / F unit 305 is connected to an output device such as a display and outputs the results of executing the computer program, etc. The input I / F unit 306 is connected to a keyboard, pointing device, etc. and accepts user input.

[0031] 4 is a block diagram showing an example of the functional configuration of an image forming apparatus as a network device according to the first embodiment. A monitoring unit 401 executes data collection necessary for monitoring. A data management unit 402 manages data collected by the monitoring device 106. A communication unit 403 transmits the data collected by the monitoring unit 401 in response to a request from the monitoring device 106.

[0032] 5 is a block diagram illustrating an example of a functional configuration of a monitoring device according to Example 1. In the description using FIG.

[0033] The collection unit 501 is an example of an acquisition unit that acquires management information, which is information related to network devices. The collection unit 501 communicates with the image forming apparatus 107 and collects data required for monitoring.

[0034] The task management unit 502 executes a task of obtaining from the device management server 101 a list of devices (hereinafter referred to as a managed device list) that are pre-registered as devices to be managed by the monitoring device 106, a monitoring task of collecting data from the devices by the collection unit 501, etc. The task management unit 502 also manages various tasks such as the registration of the monitoring device 106 and the image forming device 107. Therefore, the task management unit 502 is an example of a registration means that executes a registration process of registering a network device as a target for management by the device management server 101.

[0035] When the monitoring device 106 self-registers, it acquires a token by registering itself with the authentication and authorization server 102, and then uses the token to acquire the URLs of various servers from the access destination management server 104. Furthermore, when the monitoring device 106 self-registers, a communication test is performed on the various servers.

[0036] The data management unit 503 is an example of a calculation means that executes a calculation process to calculate the number of threads for management information to be transmitted to the device management server 101 in multiple threads based on the number of network devices that relay communication. For example, the data management unit 503 manages device information required for monitoring, such as management information collected from the image forming apparatus 107, and also manages the maximum number of threads that can be transmitted simultaneously by the transmission unit 505 based on the number of registered devices to be managed. The data management unit 503 may also execute the calculation process each time the above-described registration process is completed.

[0037] The authentication unit 504 communicates with the authentication and authorization server 102, and performs registration processing of the monitoring device 106 and the image forming device 107, token acquisition, management, and the like.

[0038] The transmission unit 505 is an example of an adjustment unit that executes an adjustment process to adjust the wait time after transmitting management information to the device management server 101 in multiple threads, based on the type of management information and the data amount of the management information. The transmission unit 505 is also an example of a transmission unit that transmits management information to the device management server 101 in multiple threads, based on the number of threads calculated by the calculation unit and the wait time adjusted by the adjustment unit. For example, the transmission unit 505 transmits data required for monitoring, such as management information collected from the image forming apparatus 107, to the resource server 103.

[0039] The screen control unit 506 displays an image on the output device via the output I / F unit 305 , and stores input information from the input device via the input I / F unit 306 in the data management unit 503 .

[0040] Each functional block shown in Figure 4 and each functional block shown in Figure 5 is realized by causing a CPU or the like serving as a computer included in each device to execute a computer program stored in a memory serving as a storage medium. However, at least a portion of each functional block shown in Figure 4 and each functional block shown in Figure 5 may be realized by hardware. Examples of such hardware include dedicated circuits such as an ASIC (Application Specific Integrated Circuit) and processors such as a digital signal processor (DSP).

[0041] 4 may be built in a single housing or may be divided into multiple housings. Similarly, the functional blocks shown in FIG. 5 may be built in a single housing or may be divided into multiple housings.

[0042] 6 is a diagram illustrating an example of a transmission schedule setting screen displayed by the screen control unit of the monitoring device according to Example 1. The monitoring device 106 executes periodic transmission by the transmission unit 505 based on the settings input on the transmission schedule setting screen.

[0043] The "Transmission Time" section has a time input form for setting the time when the transmission unit 505 starts periodic transmission.

[0044] The default time in the "Send Time" section is set randomly during the night, which is typically off-hours.

[0045] The monitoring device 106 may include a storage means for storing information relating to the management information transmitted by the transmission means. The storage means adds a waiting time, which is randomly determined for each type of management information and each network device, to the date and time when the management information will next be transmitted, and stores the result.

[0046] The time input form in the "Send Time" section allows you to set the send time in 30-minute increments. The actual sending start time is an internally randomly added time between 0 and 29 minutes from the time displayed on the screen. For example, if the default time is 18:30, the actual sending start time will be any time between 18:30 and 18:59.

[0047] The "Transmission Interval" section has radio buttons for setting the interval at which the transmitter 505 performs periodic transmission. If the "12H" radio button is selected, transmission is performed twice a day, at the transmission start time set in the "Transmission Time" section and at a time obtained by adding 12 hours to that transmission start time. If the "24H" radio button is selected, transmission is performed once a day only at the transmission start time set in the "Transmission Time" section.

[0048] Next, by pressing the “Apply” button, the transmission schedule settings can be confirmed and saved in the data management unit 503 .

[0049] 7 is a diagram illustrating an example of management information and transmission data of devices managed by the data management unit of the monitoring device according to Example 1. The transmission data is data to which information related to data transmission collected from devices by the collection unit 501 is added during monitoring tasks periodically executed by the task management unit 502, and is stored in the data management unit 503. FIG. 7 shows columns 701 to 712.

[0050] Columns 701 and 707 show device IDs, which are information that uniquely identify devices within the monitoring device 106. Column 702 shows serial numbers, which are information that uniquely identify devices. Column 703 shows IP addresses of devices. Note that while IP addresses are given here as an example of information for accessing devices, host names, URLs, etc. may also be used instead of IP addresses.

[0051] Column 704 indicates a management status indicating whether the device is a target of management by the device management system. Column 705 indicates a registration status indicating whether the image forming device that is a target of management by the device management system has been successfully registered. Column 706 indicates a device management service device ID that the device management server 101 uses to uniquely identify the image forming device 107. Note that the information that the device management server 101 uses to uniquely identify the image forming device 107 is not limited to the device management service device ID.

[0052] Column 708 indicates a transmission data ID for uniquely identifying transmission data within the monitoring device 106. Column 709 indicates a data type indicating the data type of transmission data. In a monitoring task executed by the task management unit 502, when data is acquired from a device and saved in the data management unit 503, the type of acquired data is saved. Column 710 indicates content indicating the content of data to be sent to the resource server 103. Data collected from a device by the task management unit 502 through the collection unit 501 is converted into a JSON format for sending to the resource server 103 and saved as content 710.

[0053] Column 711 indicates the transmission date and time, which indicates the date and time when the transmission data was sent. When the transmission date and time of the transmission data is saved in the data management unit 503, the next transmission date and time set on the transmission schedule setting screen is calculated. The transmission unit 505 periodically checks whether the current time has passed the transmission date and time 711, and starts transmission processing if the transmission execution date and time has passed. Here, if the data type 709 is something that should be sent to the resource server immediately, such as device status or error information, the task management unit 502 saves the transmission date and time 711 as the current time in the monitoring task. The creation date and time 712 is information that indicates the date and time when the transmission data was created in the task management unit 502.

[0054] 8 is a flowchart illustrating an example of a process for managing the number of threads transmitted by the transmission unit of the monitoring device according to the first embodiment. As will be described below, in the process illustrated in FIG. 8, when there is data that needs to be transmitted, thread processing is started until the number of threads reaches a maximum. In addition, the process illustrated in FIG. 8 may be periodically executed by the transmission unit 505, may be executed when a monitoring task by the task management unit 502 is completed, or may be executed at any timing based on a user's operation of the screen control unit 506.

[0055] In step S801, the transmitting unit 505 calculates the number of threads that can be started. Specifically, in step S801, the transmitting unit 505 compares the difference between the maximum number of threads and the current number of threads with the number of pieces of transmission data whose transmission time has passed, and defines the smaller number of threads as the number of threads that can be started.

[0056] 7, the greater the total number of devices that are set to "management target" in column 704 and "registered" in column 705, the greater the maximum number of threads is set. The maximum number of threads may be set when a registration task for the image forming apparatus 107, which is periodically executed by the task management unit 502, is completed, or may be set periodically by the transmission unit 505.

[0057] Here, the transmitting unit 505 sets a larger maximum number of threads for the monitoring device 106 that monitors a larger number of devices, and sets a smaller maximum number of threads for the monitoring device 106 that monitors a smaller number of devices. This allows the transmitting unit 505 to prevent the transmission time from becoming too long for the monitoring device 106 that monitors a large number of devices. This also allows the transmitting unit 505 to reduce the load caused by the monitoring device 106 accessing the resource server 103 and the load on the network in the environment in which the monitoring device 106 is installed.

[0058] For example, if the number of devices monitored by the monitoring device 106 is 600 or more, the transmission unit 505 sets the maximum number of threads to "10." Also, for example, if the number of devices monitored by the monitoring device 106 is 300 to 599, the transmission unit 505 sets the maximum number of threads to "6." Also, for example, if the number of devices monitored by the monitoring device 106 is 299 or less, the transmission unit 505 sets the maximum number of threads to "3."

[0059] In step S802, the transmission unit 505 determines whether the number of threads that can be started calculated in step S801 is "0." If the transmission unit 505 determines that the number of threads that can be started calculated in step S801 is "0" (step S802: Yes), the processing proceeds to step S804. On the other hand, if the transmission unit 505 determines that the number of threads that can be started calculated in step S801 is not "0" (step S802: No), the processing proceeds to step S803.

[0060] In step S803, the transmission unit 505 starts threads equal to the number of threads that can be started calculated in step S801.

[0061] In step S804, the transmission unit 505 sets a timer to start the process of FIG. 8 at the next transmission date and time set on the transmission schedule setting screen.

[0062] The information processing device may temporarily stop operation after transmitting the management information by the transmitting means if the type of management information transmitted by the transmitting means corresponds to a specific type. Fig. 9 is a flowchart showing an example of processing related to a thread transmitted by the transmitting unit of the monitoring device according to the first embodiment. As will be described below, the processing shown in Fig. 9 transmits data whose transmission time has passed and temporarily suspends thread processing according to the type of each data type. In addition, the processing shown in Fig. 9 is started when it is determined that thread processing can be started by the processing shown in Fig. 8.

[0063] In step S901, the transmitting unit 505 obtains data whose transmission time has passed from the data management unit 503. Specifically, in step S901, the transmitting unit 505 obtains the device ID and data type of the transmission data with the oldest creation date and time 712, and obtains all transmission data having the same device ID and data type in order of oldest creation date and time 712.

[0064] The data acquired here is managed as data currently being transmitted by the transmission unit 505. When transmission data is acquired in step S901 of another thread, the transmission data managed as data currently being transmitted is excluded.

[0065] In step S902, the transmitting unit 505 determines whether the number of pieces of transmission data acquired in step S901 is "0." If the transmitting unit 505 determines that the number of pieces of transmission data acquired in step S901 is "0" (step S902: Yes), the processing proceeds to step S908. On the other hand, if the transmitting unit 505 determines that the number of pieces of transmission data acquired in step S901 is not "0" (step S902: No), the processing proceeds to step S903.

[0066] In step S903, the transmission unit 505 transmits to the resource server 103 one of the transmission data acquired in step S901, the one with the oldest creation date and time shown in column 712 of FIG.

[0067] In step S904, the transmitting unit 505 determines whether the transmission in step S903 was successful. If the transmitting unit 505 determines that the transmission in step S903 was successful (step S904: Yes), the process proceeds to step S905. On the other hand, if the transmitting unit 505 determines that the transmission in step S903 was not successful (step S904: No), the process proceeds to step S907.

[0068] In step S905, the transmitting unit 505 deletes the data that has been completely transmitted from the data management unit 503. Also in step S905, the transmitting unit 505 deletes the data that has been completely transmitted from the data that is currently being transmitted.

[0069] In step S906, the transmission unit 505 suspends the processing of the thread in accordance with the type of data type 709 of the data that has been transmitted. Here, the transmission unit 505 suspends the processing of the thread for a longer period of time as the data size of the data type increases. In this way, the transmission unit 505 reduces the load caused by access to the resource server 103, the load on the network on which the monitoring device 106 is installed, the load on the CPU 303 installed in the monitoring device 106, and the like.

[0070] Counter information including the number of times printed, the number of times copied, etc., is relatively large in volume, so thread processing is stopped for 6 seconds. Counter information including consumable parts is the second largest in volume after counter information including the number of times printed, the number of times copied, etc., so thread processing is stopped for 4 seconds. Counter information including environmental information such as temperature and humidity, and network information, is relatively small in volume, so thread processing is stopped for 2 seconds.

[0071] This creates an interval until the next transmission in this thread in step S903. Also, if the transmission in the thread is the last transmission, one thread is occupied while the thread is stopped, so an interval occurs between the end of the thread and the start of the next thread, and the transmission interval is adjusted according to the data type.

[0072] In step S907, the transmitting unit 505 updates the transmission date and time shown in column 711 shown in FIG. 7 for the data that failed to be transmitted, and deletes it from the data currently being transmitted that is managed by the transmitting unit 505. The transmission date and time updated here may be the next transmission date and time set on the transmission schedule setting screen, or may be the current time plus a few minutes for a transmission retry. Alternatively, the transmission date and time updated here may be the next transmission date and time set on the transmission schedule setting screen according to the type of data type 709, or the current time plus a few minutes for a transmission retry.

[0073] In step S908, the transmission unit 505 calculates the number of threads currently being executed and determines whether there are any other threads being executed. If there are other threads being executed (step S908: Yes), the transmission unit 505 proceeds to step S908. On the other hand, if there are no other threads being executed (step S908: No), the transmission unit 505 ends the process.

[0074] In step S909, the transmission unit 505 sets a timer so as to immediately start the management process shown in FIG.

[0075] 9, excessive transmission time is prevented from being required in the monitoring device 106 that manages a large number of devices. Also, by executing the processing shown in Fig. 9, it is possible to distribute the load caused by access to the resource server 103 by the monitoring device 106 and the load on the network on which the monitoring device 106 is installed.

[0076] <Example 2> In the first embodiment, when the transmission date and time set on the transmission schedule setting screen arrives, the maximum number of threads are started simultaneously.

[0077] In such a case, the simultaneous start of transmission will place a load on the network in the environment where the monitoring devices 106 are installed. In addition, if there are multiple monitoring devices 106 with overlapping transmission dates and times, the amount of data to be transmitted immediately after transmission starts will increase, leading to a load due to access to the resource server 103.

[0078] In the second embodiment, even in the above-mentioned case, the load on the network in the environment where the monitoring device 106 is installed and the load due to access to the resource server 103 are reduced.

[0079] Hereinafter, a second embodiment of the present invention will be described. In the description of the second embodiment, the description of the same configuration as the first embodiment will be omitted.

[0080] In the second embodiment, when the transmission dates and times shown in column 711 of Fig. 7 are saved in the data management unit 503, the next transmission dates and times set on the transmission schedule setting screen are not saved. In the second embodiment, when the transmission dates and times shown in column 711 of Fig. 7 are saved in the data management unit 503, a random waiting time is added to the next transmission dates and times set on the transmission schedule setting screen for each device ID shown in column 707 of Fig. 7 and each data type shown in column 709 of Fig. 7 before saving.

[0081] The above-described processing prevents all threads from starting simultaneously immediately after the start of periodic transmission, and it is possible to distribute the load caused by the monitoring device 106 accessing the resource server 103 and the load on the network in the environment where the monitoring device 106 is installed.

[0082] The present invention includes the following inventions that appropriately combine the above-mentioned features.

[0083] (Configuration 1) an information processing device that relays communication between a network device and a device management server that manages the network device, the information processing device comprising: an acquisition means that acquires management information, which is information about the network device; a calculation means that executes a calculation process that calculates the number of threads for the management information to be sent to the device management server in multithreads based on the number of network devices that relay communication; an adjustment means that executes an adjustment process that adjusts a wait time after sending the management information to the device management server in multithreads based on the type of the management information and the data amount of the management information; and a transmission means that transmits the management information to the device management server in multithreads based on the number of threads calculated by the calculation means and the wait time adjusted by the adjustment means.

[0084] (Configuration 2) The information processing device according to configuration 1 further comprises a registration means for executing a registration process for registering the network device as a target for management by the device management server, and the calculation means executes the calculation process each time the registration process is completed.

[0085] (Configuration 3) when the type of the management information transmitted by the transmitting means corresponds to a specific type, the information processing device temporarily stops operation after transmitting the management information by the transmitting means; 3. The state processing device according to configuration 1 or 2.

[0086] (Configuration 4) 4. A status processing device according to any one of configurations 1 to 3, wherein the information processing device further comprises a storage means for storing information relating to the management information transmitted by the transmission means, and the storage means adds a wait time randomly determined for each type of management information and each network device to the date and time of the next transmission of the management information and stores the result.

[0087] (Method 1) A method for controlling an information processing device that relays communication between a network device and a device management server that manages the network device, the method comprising: acquiring management information that is information about the network device; performing a calculation process to calculate the number of threads for the management information to be sent to the device management server in multi-threads based on the number of network devices that relay communication; performing an adjustment process to adjust a waiting time after sending the management information to the device management server in multi-threads based on the type of the management information and the data amount of the management information; and transmitting the management information to the device management server in multi-threads based on the number of threads calculated by the calculation means and the waiting time adjusted by the adjustment means.

[0088] (Program 1) A program for an information processing device that relays communication between a network device and a device management server that manages the network device, the program causing the information processing device to realize the following: an acquisition means for acquiring management information, which is information about the network device; a calculation means for executing a calculation process that calculates the number of threads for the management information to be sent to the device management server in multi-threads based on the number of network devices that relay communication; an adjustment means for executing an adjustment process that adjusts the wait time after sending the management information to the device management server in multi-threads based on the type of the management information and the data amount of the management information; and a transmission means for sending the management information to the device management server in multi-threads based on the number of threads calculated by the calculation means and the wait time adjusted by the adjustment means.

[0089] The preferred embodiments of the present invention have been described above. However, the present invention is not limited to the above-described embodiments. In other words, the present invention includes embodiments in which various modifications have been made based on the spirit of the present invention, and these embodiments are not excluded from the scope of the present invention. [Explanation of symbols]

[0090] 501 Collection Department 502 Task Management Department 503 Data Management Department 504 Authentication Section 505 Transmission Unit 506 Screen control unit

Claims

1. An information processing device that relays communication between a network device and a device management server that manages the network device, The information processing device includes: an acquisition means for acquiring management information that is information about the network device; a calculation unit that executes a calculation process to calculate the number of threads of the management information to be transmitted to the device management server in multithreads based on the number of the network devices that relay communication; an adjusting unit that executes an adjustment process to adjust a waiting time after transmitting the management information to the device management server in a multi-threaded manner based on the type of the management information and the data amount of the management information; a transmission means for transmitting the management information to the device management server in multithreads based on the number of threads calculated by the calculation means and the waiting time adjusted by the adjustment means; An information processing device comprising:

2. the information processing device further comprises a registration unit that executes a registration process to register the network device as a target for management by the device management server; the calculation means executes the calculation process each time the registration process is completed; 2. The information processing apparatus according to claim 1, wherein:

3. when the type of the management information transmitted by the transmitting means corresponds to a specific type, the information processing device temporarily stops operation after transmitting the management information by the transmitting means; 3. The state processing device according to claim 1 or 2.

4. the information processing device further comprises a storage means for storing information relating to the management information transmitted by the transmission means; the storage means adds a waiting time randomly determined for each type of management information and each network device to a date and time when the management information will next be transmitted, and stores the result.

3. The state processing device according to claim 1 or 2.

5. A method for controlling an information processing device that relays communication between a network device and a device management server that manages the network device, comprising: acquiring management information relating to the network device; executes a calculation process to calculate the number of threads of the management information to be transmitted to the device management server in multithreads based on the number of the network devices that relay communication; executing an adjustment process for adjusting a waiting time after transmitting the management information to the device management server in a multi-thread manner based on the type of the management information and the data amount of the management information; transmitting the management information to the device management server in multithreads based on the number of threads calculated by the calculation means and the waiting time adjusted by the adjustment means; A method characterized by:

6. A program for an information processing device that relays communication between a network device and a device management server that manages the network device, The information processing device includes: an acquisition means for acquiring management information that is information about the network device; a calculation unit that executes a calculation process to calculate the number of threads of the management information to be transmitted to the device management server in multithreads based on the number of the network devices that relay communication; an adjusting unit that executes an adjustment process to adjust a waiting time after transmitting the management information to the device management server in a multi-threaded manner based on the type of the management information and the data amount of the management information; a transmission means for transmitting the management information to the device management server in multithreads based on the number of threads calculated by the calculation means and the waiting time adjusted by the adjustment means; A program characterized by realizing the above.

Images