Information processing device, 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 apparatus, method, and program.

Background Art

[0002] Conventionally, a device management system that performs maintenance of network devices such as image forming apparatuses installed in offices and the like via a network is known. By using the device management system, it becomes possible to detect via the network that a failure has occurred in a network device, that it is necessary to replenish consumables in the network device, etc., and to respond promptly.

[0003] As a conventional device management system, one including a device management server and a monitoring device is known. The device management server centrally manages each device. The monitoring device collects management information from a plurality of network devices and operates as a management client that transmits it to the device management server at the timing when a failure has occurred, at regular timings, etc.

[0004] However, in a conventional device management system, when the number of devices to be managed increases and it is set to send data at a specific time such as outside business hours, a plurality of monitoring devices start transmitting data simultaneously. For this reason, it is assumed that in a conventional device management system, the load on the network of the environment in which the network devices are installed, the load due to access to the server, etc. will increase.

[0005] Patent Document 1 discloses a server system that, when multiple devices are started simultaneously, adds a randomly calculated waiting time within a predetermined period from the set transmission timing. This reduces the network load in the environment where the devices are installed, as well as the load from accessing the server. Furthermore, since this server system is used in environments where the amount of data transmitted per device is not large, there was no need to consider the transmission interval, transmission time, etc., after data transmission has started. [Prior art documents] [Patent Documents]

[0006] [Patent Document 1] Japanese Patent Publication No. 2021-131774 [Overview of the project] [Problems that the invention aims to solve]

[0007] However, management clients that collect large amounts of management information from numerous devices and send it to a device management server may send a large amount of management information all at once in a short period of time at scheduled transmission times. In such cases, the network load in the environment where the management client is installed, as well as the load from accessing the server, can increase.

[0008] Therefore, management clients need to avoid sending data all at once in a short period of time, but rather send data over time to reduce the number of peak requests received by the management server. On the other hand, management clients need to avoid taking too long to send data, which could result in data transmission occurring outside of business hours or other specific time periods.

[0009] Furthermore, depending on the timing of data transmission, if management clients send large amounts of data to the management server all at once in a short period, it is possible that the load on accessing the management server and the network load on the environment in which the management clients are installed will increase even further.

[0010] Therefore, the present invention aims to distribute the load caused by management clients accessing the management server and the load on the network in the environment where the management clients are installed. [Means for solving the problem]

[0011] To solve the above-mentioned problems, the information processing apparatus according to the present invention comprises: acquisition means for acquiring management information which is information relating to a network device; calculation means for performing a calculation process to calculate the number of threads for sending the management information to the device management server in multithreaded mode based on the number of network devices that relay the communication; adjustment means for performing an adjustment process to adjust the waiting time after sending the management information to the device management server in multithreaded mode based on the type of management information and the amount of data of the management information; and transmission means for sending the management information to the device management server in multithreaded mode based on the number of threads calculated by the calculation means and the waiting time adjusted by the adjustment means. The information processing apparatus according to the present invention relays communication between a network device and a device management server that manages the network device. [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 management clients accessing the management server and the load on the network in the environment where the management clients are installed. [Brief explanation of the drawing]

[0013] [Figure 1] This diagram shows the overall device management system according to Example 1. [Figure 2] This is a block diagram showing an example of the hardware configuration of an image forming apparatus as a network device according to Example 1. [Figure 3] This block diagram shows an example of the internal configuration of the monitoring device and server according to Example 1. [Figure 4] This is a block diagram showing an example of the functional configuration of an image forming apparatus as a network device according to Example 1. [Figure 5] This block diagram shows an example of the functional configuration of the monitoring device according to Example 1. [Figure 6] This figure shows an example of the transmission schedule setting screen displayed by the screen control unit of the monitoring device according to Example 1. [Figure 7] This figure shows examples of device management information and transmitted data managed by the data management unit of the monitoring device according to Example 1. [Figure 8] This flowchart shows an example of a process for managing the number of threads transmitted by the transmission unit of the monitoring device according to Example 1. [Figure 9] This flowchart shows an example of processing related to threads transmitted by the transmission unit of the monitoring device according to Example 1. [Modes for carrying out the invention]

[0014] The embodiments for carrying out the present invention will be described below with reference to examples and drawings. However, the present invention is not limited to the following embodiments. In each figure, the same reference numeral is used for the same member or element. In addition, in the following embodiments, explanations of overlapping content will be omitted or simplified.

[0015] <Example 1> FIG. 1 is a diagram showing the overall device management system according to Embodiment 1. The device management system according to Embodiment 1 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 any device can be used as long as it can be connected to the network.

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

[0017] In Embodiment 1, a general OAuth mechanism is used, and each device (image forming apparatus 107, monitoring apparatus 106, etc.) is registered as a client associated with a specific tenant. Here, a tenant means a management unit assigned to each customer who has concluded a service use contract.

[0018] The authentication and authorization server 102 manages data in units of tenants. Further, the authentication and authorization server 102 issues tokens to clients such as the image forming apparatus 107 and the monitoring apparatus 10,6. Each device (image forming apparatus 107, monitoring apparatus 106, etc.) can access various servers by using the token.

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

[0020] The access destination management server 104 provides URLs of the device management server 101, the resource server 103, etc. that are access destinations of each device (image forming apparatus 107, monitoring apparatus 106, etc.) in response to requests from each device.

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

[0022] The information for each device configured via the web user interface described above can also be reflected in the device management server 101 and the resource server 103. Servers 101 through 105, the monitoring device 106, and the image forming apparatus 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 a network device and a device management server 101 that manages the network device. Multiple monitoring devices 106 exist on the network and operate in the standard time zone of each region. Alternatively, multiple monitoring devices 106 may be installed on a single LAN 109, each monitoring a different image forming apparatus 107.

[0024] Figure 2 is a block diagram showing an example of the hardware configuration of an image forming apparatus as a network device according to Example 1.

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

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

[0027] The overall control unit 211 controls various devices and interfaces connected to the image forming apparatus 107, as well as the operation of the entire device. The reader unit 212 functions as a scanner. The reader unit 212 reads the image of the 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 the image of the document and saves image data corresponding to the image to the device's storage device based on instructions from the user. The reader unit 212 can also transmit the above-mentioned image data to a host computer connected to the network 217 via the network interface 216.

[0028] The printer unit 213 functions as a printer. The printer unit 213 prints image data based on the document read by the reader unit 212, image data stored in the HDD 205 as a storage device within the device, etc. The printer unit 213 also receives print jobs from a host computer connected to the network 217 via the network interface 216 and prints the image data related to the print job. The network interface 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 notifies the overall control unit 211 of the display of information to the user by the overall control unit 211, user input, etc., via buttons, display devices, liquid crystal display screens with touch panel input, or a combination thereof. The switch unit 215 controls the ON / OFF state of the power supply of the overall control unit 211.

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

[0031] Figure 4 is a block diagram showing an example of the functional configuration of an image forming apparatus as a network device according to Embodiment 1. The monitoring unit 401 performs data collection and other tasks necessary for monitoring. The data management unit 402 manages the data collected by the monitoring device 106. The communication unit 403 transmits the data collected by the monitoring unit 401 in response to a request from the monitoring device 106.

[0032] Figure 5 is a block diagram showing an example of the functional configuration of the monitoring device according to Embodiment 1. In the explanation using Figure 5, we will focus on one of the multiple monitoring devices 106.

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

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

[0035] During the self-registration of the monitoring device 106, it obtains a token by registering itself with the authentication and authorization server 102, and uses this token to obtain URLs for various servers from the access destination management server 104. In addition, during the self-registration of the monitoring device 106, communication tests to various servers are performed.

[0036] The data management unit 503 is an example of a calculation means that performs a calculation process to determine the number of threads to send management information to the device management server 101 in a multithreaded manner, based on the number of network devices that relay the communication. For example, the data management unit 503 manages device information necessary for monitoring, such as management information collected from the image forming apparatus 107, and also manages the maximum number of threads to be simultaneously transmitted by the transmission unit 505 according to the number of registered managed devices. In addition, the data management unit 503 may perform the calculation process each time the above-mentioned registration process is completed.

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

[0038] The transmission unit 505 is an example of an adjustment means that performs an adjustment process to adjust the waiting time after sending management information to the device management server 101 in a multithreaded manner, based on the type of management information and the amount of data of the management information. The transmission unit 505 is also an example of a transmission means that sends management information to the device management server 101 in a multithreaded manner based on the number of threads calculated by the calculation means and the waiting time adjusted by the adjustment means. For example, the transmission unit 505 transmits data necessary 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 in the data management unit 503 via the input I / F unit 306.

[0040] Each functional block shown in Figure 4 and Figure 5 is implemented by having the CPU or other computer components included in each device execute computer programs stored in memory, which serves as a storage medium. However, at least a portion of each functional block shown in Figure 4 and Figure 5 may be implemented by hardware. Examples of such hardware include dedicated circuits such as ASICs (Application Specific Integrated Circuits) and processors such as Digital Signal Processors (DSPs).

[0041] Furthermore, each functional block shown in Figure 4 may be housed in a single enclosure, or it may be housed in multiple enclosures. Similarly, each functional block shown in Figure 5 may be housed in a single enclosure, or it may be housed in multiple enclosures.

[0042] Figure 6 shows an example of the transmission schedule setting screen displayed by the screen control unit of the monitoring device according to Embodiment 1. Based on the settings entered on the transmission schedule setting screen, the monitoring device 106 performs periodic transmissions using the transmission unit 505.

[0043] The "Transmission Time" section has a time input form for setting the time at which the transmission unit 505 begins periodic transmissions.

[0044] The default time in the "Send Time" section is set randomly within the nighttime hours, which are generally outside of business hours.

[0045] The monitoring device 106 may also include storage means for storing information related to the management information transmitted by the transmission means. The storage means stores a randomly determined waiting time for each type of management information and network device, added to the date and time for the next transmission of management information.

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

[0047] The "Transmission Interval" section has radio buttons for setting the interval at which the transmission unit 505 performs periodic transmissions. If "12H" is selected with the radio buttons, transmissions will be performed twice a day: once at the transmission start time set in the "Transmission Time" section, and again 12 hours after that start time. If "24H" is selected with the radio buttons, transmissions will be performed only once a day, 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 to the data management unit 503.

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

[0050] Columns 701 and 707 show the device ID, which is information that uniquely identifies the device within the monitoring device 106. Column 702 shows the serial number, which is information that uniquely identifies the device. Column 703 shows the IP address of the device. Note that while an IP address is given here as an example of information for accessing the device, a hostname, URL, etc., could also be used instead of an IP address.

[0051] Column 704 indicates the management status, showing whether or not the device is subject to management by the device management system. Column 705 indicates the registration status, showing whether or not the image forming apparatus subject to management by the device management system has been successfully registered. Column 706 shows the device management service device ID, which the device management server 101 uses to uniquely identify the image forming apparatus 107. Note that the information used by the device management server 101 to uniquely identify the image forming apparatus 107 is not limited to the device management service device ID.

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

[0053] Column 711 shows the transmission date and time of the transmitted data. When the transmission date and time of the transmitted 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 that the current time has passed the transmission date and time 711, and starts the transmission process 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 indicating the date and time when the transmission data was created in the task management unit 502.

[0054] Figure 8 is a flowchart showing an example of a process for managing the number of threads transmitted by the transmission unit of the monitoring device according to Embodiment 1. As described below, in the process shown in Figure 8, if there is data that needs to be transmitted, thread processing is started until the number of threads reaches the maximum. Furthermore, the process shown in Figure 8 may be executed periodically by the transmission unit 505, or when the monitoring task by the task management unit 502 is completed, or at any time based on the 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 transmission data that have passed the transmission time, and defines the smaller number of threads as the number of threads that can be started.

[0056] The maximum number of threads is set to a higher value as the total number of devices in column 704 (shown in Figure 7) that are "managed" and in column 705 that are "registered" increases. The timing at which the maximum number of threads is set may be when the registration task for the image forming apparatus 107, which is periodically executed by the task management unit 502, is completed, or at a timing periodically set by the transmission unit 505.

[0057] Here, the transmitting unit 505 sets a larger maximum number of threads for monitoring devices 106 that monitor a large number of devices, and a smaller maximum number of threads for monitoring devices 106 that monitor a small number of devices. This allows the transmitting unit 505 to avoid excessively long transmission times for monitoring devices 106 that monitor a large number of devices. In addition, this allows the transmitting unit 505 to reduce the load on the monitoring device 106 that accesses the resource server 103 and the load on the network in the environment where the monitoring device 106 is installed.

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

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

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

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

[0062] The information processing device may temporarily suspend its operation after transmitting the management information via the transmission means if the type of management information transmitted by the transmission means falls under a specific type. Figure 9 is a flowchart showing an example of processing related to threads transmitted by the transmission unit of the monitoring device according to Embodiment 1. As described below, the processing shown in Figure 9 transmits data that has passed its transmission time and temporarily suspends thread processing according to the type for each data type. Furthermore, the processing shown in Figure 9 is started when it is determined that thread processing can be started based on the processing shown in Figure 8.

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

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

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

[0066] In step S903, the transmission unit 505 sends to the resource server 103 the oldest data entry among the transmission data acquired in step S901, which is shown in column 712 of Figure 7.

[0067] In step S904, the transmitting unit 505 determines whether the transmission in step S903 was successful or not. If the transmitting unit 505 determines that the transmission in step S903 was successful (step S904: Yes), it 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), it proceeds to step S907.

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

[0069] In step S906, the transmission unit 505 temporarily suspends thread processing according to the type of data type 709 of the data that has been transmitted. Furthermore, the transmission unit 505 increases the duration of the temporary suspension of thread processing as the data size of the data type increases. This reduces the load on the resource server 103, the load on the network where the monitoring device 106 is installed, and the load on the CPU 303 installed in the monitoring device 106.

[0070] Counter information, including the number of prints and copies, is relatively large in size, so thread processing is paused for 6 seconds. Counter information, including consumable parts, is the next largest in size, so thread processing is paused for 4 seconds. Counter information, including environmental information such as temperature and humidity, and network information, is relatively small in size, so thread processing is paused for 2 seconds.

[0071] This creates a gap before the next transmission in step S903 within this thread. Also, if the transmission within a thread is the last transmission, one thread is occupied while that thread is stopped, creating a gap between the end of that thread and the start of the next thread, and the transmission interval is adjusted according to the data type.

[0072] In step S907, the transmission unit 505 updates the transmission date and time shown in column 711 in Figure 7 for the data that failed to transmit, and deletes it from the data currently being transmitted managed by the transmission 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 it may be the current time with a few minutes added for transmission retries. 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, and the current time with a few minutes added for transmission retries.

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

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

[0075] By executing the process shown in Figure 9, the monitoring device 106, which manages a large number of devices, will no longer experience excessive transmission time. Furthermore, by executing the process shown in Figure 9, the load caused by the monitoring device 106 accessing the resource server 103 and the load on the network where the monitoring device 106 is installed can be distributed.

[0076] <Example 2> In Example 1, when the transmission date and time set on the transmission schedule setting screen arrives, each thread is started simultaneously up to the maximum number of threads.

[0077] In such cases, the simultaneous start of transmissions can lead to a load on the network in the environment where the monitoring devices 106 are installed. Furthermore, if there are multiple monitoring devices 106 whose transmission times overlap, the number of transmitted data immediately after the start of transmission will be large, leading to a load on the resource server 103 due to access issues.

[0078] In Example 2, even in the case described above, the configuration is designed to reduce the load on the network in the environment where the monitoring device 106 is installed and the load caused by accessing the resource server 103.

[0079] The following describes Example 2 of the present invention. Note that the description of the same configuration as in Example 1 will be omitted in the description of Example 2.

[0080] In Example 2, when the transmission date and time shown in column 711 of Figure 7 is saved in the data management unit 503, the next transmission date and time set on the transmission schedule setting screen is not saved. In Example 2, when the transmission date and time shown in column 711 of Figure 7 is saved in the data management unit 503, a random waiting time is added to the next transmission date and time set on the transmission schedule setting screen, for each device ID shown in column 707 of Figure 7 and each data type shown in column 709 of Figure 7, before it is saved.

[0081] The process described above prevents all threads from starting simultaneously immediately after periodic transmission begins, thereby distributing 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] Furthermore, the present invention includes the following inventions, which appropriately combine the above-mentioned features.

[0083] (Composition 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: acquisition means for acquiring management information which is information relating to the network device; calculation means for performing a calculation process to calculate the number of threads for sending the management information to the device management server in multithreaded mode based on the number of network devices relaying the communication; adjustment means for performing an adjustment process to adjust the waiting time after sending the management information to the device management server in multithreaded mode based on the type of management information and the amount of data of the management information; and transmission means for sending the management information to the device management server in multithreaded mode based on the number of threads calculated by the calculation means and the waiting time adjusted by the adjustment means.

[0084] (Configuration 2) The information processing apparatus according to configuration 1, further comprising registration means for performing a registration process to register the network device as an object of management by the device management server, and the calculation means performing the calculation process each time the registration process is completed.

[0085] (Composition 3) If the type of management information transmitted by the transmission means falls under a specific type, the information processing device temporarily stops operating after transmitting the management information by the transmission means. A state processing apparatus according to configuration 1 or configuration 2, characterized in that it is a state processing apparatus.

[0086] (Composition 4) 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 the type of management information and a randomly determined waiting time for each network device to the date and time for the next transmission of the management information, and stores this information, characterized in that the status processing device is as described in any one of configurations 1 to 3.

[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, characterized by: acquiring management information which is information relating to the network device; executing a calculation process to calculate the number of threads to send the management information to the device management server in multithreaded mode based on the number of network devices that relay the communication; executing an adjustment process to adjust the waiting time after sending the management information to the device management server in multithreaded mode based on the type of management information and the amount of data of the management information; and sending the management information to the device management server in multithreaded mode 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, wherein the information processing device includes: an acquisition means for acquiring management information which is information relating to the network device; a calculation means for performing a calculation process to calculate the number of threads for sending the management information to the device management server in multithreaded mode based on the number of network devices relaying the communication; an adjustment means for performing an adjustment process to adjust the waiting time after sending the management information to the device management server in multithreaded mode based on the type of management information and the amount of data of the management information; and a transmission means for sending the management information to the device management server in multithreaded mode based on the number of threads calculated by the calculation means and the waiting time adjusted by the adjustment means.

[0089] Preferred embodiments of the present invention have been described above. However, the present invention is not limited to the embodiments described above. That is, the present invention includes embodiments that have been modified in accordance with 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 Department 505 Transmitter 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 aforementioned information processing device is An acquisition means for acquiring management information which is information related to the aforementioned network device, A computing means that performs a calculation process to calculate the number of threads for sending the management information to the device management server in a multithreaded manner, based on the number of network devices that relay the communication. An adjustment means that performs an adjustment process to adjust the waiting time after sending the management information to the device management server in a multithreaded manner, based on the type of management information and the amount of data of the management information, A transmission means that transmits the management information to the device management server in a multithreaded manner based on the number of threads calculated by the calculation means and the waiting time adjusted by the adjustment means, An information processing device characterized by comprising:

2. The information processing device further comprises registration means for performing a registration process to register the network device as an object of management by the device management server, The calculation means executes the calculation process each time the registration process is completed. The information processing apparatus according to feature 1.

3. If the type of management information transmitted by the transmission means falls under a specific type, the information processing device temporarily stops operating after transmitting the management information by the transmission means. The information processing apparatus according to claim 1 or 2.

4. The information processing device further comprises storage means for storing information relating to the management information transmitted by the transmission means, The storage means adds the type of management information and a randomly determined waiting time for each network device to the date and time when the management information will be transmitted next, and stores this information. The information processing apparatus 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, The management information, which is information about the aforementioned network device, is obtained. The number of threads to send the management information to the device management server in a multithreaded manner is calculated based on the number of network devices that relay the communication. After sending the management information to the device management server using multithreading, an adjustment process is performed to adjust the waiting time based on the type of management information and the amount of data of the management information. The management information is sent to the device management server in a multithreaded manner based on the number of threads calculated by the calculation process and the waiting time adjusted by the adjustment process. A method characterized by the following:

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 aforementioned information processing device, An acquisition means for acquiring management information which is information related to the aforementioned network device, A computing means that performs a calculation process to calculate the number of threads for sending the management information to the device management server in a multithreaded manner, based on the number of network devices that relay the communication. The waiting time after sending the management information to the device management server using multithreading is, An adjustment means that performs an adjustment process to adjust based on the type of management information and the amount of data of the management information, A transmission means that transmits the management information to the device management server in a multithreaded manner based on the number of threads calculated by the calculation means and the waiting time adjusted by the adjustment means, A program characterized by its ability to achieve this.

Images