Computer program, management device, and management method

Abstract

To provide technique capable of appropriately controlling a processing load in a plurality of sub-management devices.SOLUTION: Each of a plurality of sub-management devices 20, 30, and 40 is constructed so as to manage one or more devices allocated as a management object. A management device 10 is constructed so as to manage the plurality of sub-management devices. A management method executed in the management device includes a step (S670 and S680) of changing allocation of the management object against two or more sub-management devices containing a high load device contained in the same group so as to make at least one part of two or more devices managed by the high load device to be managed by another sub-management device belonged to the group that is similar to the high load device from the plurality of sub-management devices. The high load device is each sub-management device managing two or more devices and is each sub-management device of which a processing load in regard to the management of two or more devices exceeds a reference.SELECTED DRAWING: Figure 6

Description

[Technical field]

[0001] The present disclosure relates to a management device, and related computer programs and methods. [Background technology]

[0002] Conventionally, a communication system is known that includes a plurality of relay devices that manage one or more devices, and a management device that manages the plurality of relay devices (see, for example, Patent Document 1). The management device and the plurality of relay devices are arranged so as to be able to communicate with each other via a global network. The plurality of relay devices are connected to different local area networks, and are arranged so as to be able to communicate with devices in the local area networks. [Prior art documents] [Patent documents]

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

[0004] In the above-described system, as the number of devices to be managed increases, the processing load on the intermediary device related to device management increases. When the processing load on the intermediary device increases, a delay in processing related to device management may occur in the intermediary device. The processing delay may lead to a deterioration in response to an instruction to execute the processing.

[0005] Therefore, according to one aspect of the present disclosure, it is desirable to provide a technology that can appropriately control the processing load of multiple sub-management devices in an environment where a management device manages multiple sub-management devices, each of which manages one or more devices. [Means for solving the problem]

[0006] According to one aspect of the present disclosure, there is provided a computer program executed by a computer of a management device configured to manage a plurality of secondary management devices through communication with the plurality of secondary management devices, the computer program including instructions for causing the computer of the management device to execute a management process.

[0007] Each of the multiple sub-management devices is configured to communicate with one or more devices assigned as management targets and to manage the one or more devices. The management process includes grouping at least some of the sub-management devices based on information received from the sub-management devices so that two or more sub-management devices that are in an environment capable of communicating with a common device are assigned to the same group.

[0008] The management process further includes changing the allocation of managed objects to two or more sub-management devices including the high-load device included in the same group so that at least a part of the two or more devices managed by the high-load device is managed by another sub-management device among the multiple sub-management devices that belongs to the same group as the high-load device. The high-load device is a sub-management device among the multiple sub-management devices that manages two or more devices as managed objects and whose processing load related to the management of the two or more devices exceeds a standard.

[0009] The change includes changing the allocation of managed objects to two or more sub-management devices so that a sub-management device whose processing load exceeds a standard does not newly occur due to the change in the allocation of managed objects. According to this computer program, the processing load in the multiple sub-management devices can be appropriately controlled.

[0010] According to another aspect of the present disclosure, a management device configured to manage a plurality of sub-management devices through communication with the plurality of sub-management devices may be provided. The management device may include a processor and a storage device. The storage device may store instructions for causing the processor to execute a management process. Each of the plurality of sub-management devices may be configured to communicate with one or more devices assigned as a management target to manage the one or more devices. As described above, the management process may include grouping at least a portion of the plurality of sub-management devices and changing the allocation of the management targets to two or more sub-management devices. According to this management device, the processing load in the plurality of sub-management devices can be appropriately controlled.

[0011] According to another aspect of the present disclosure, there may be provided a management method. The management method may be executed in a management device configured to manage a plurality of sub-management devices through communication with the plurality of sub-management devices. Each of the plurality of sub-management devices may be configured to communicate with one or more devices assigned as a management target to manage the one or more devices.

[0012] The management method may include grouping at least some of the sub-management devices and changing the allocation of management targets to two or more sub-management devices, similar to the management process described above. This management method makes it possible to appropriately control the processing load on the sub-management devices. [Brief description of the drawings]

[0013] [Figure 1] FIG. 1 is a block diagram showing a configuration of a device management system. [Diagram 2] 11 is a flowchart showing a device information acquisition process executed by a client. [Diagram 3] FIG. 3A is a flowchart showing a client information acquisition process executed by a client, and FIG. 3B is a flowchart showing a client information transmission process executed by a client. [Figure 4] 11 is a flowchart showing an information providing process executed by a client. [Diagram 5] 11 is a flowchart showing a table update process executed by the management device. [Figure 6] 11 is a flowchart showing a load management process executed by a management device. [Figure 7] 13 is a flowchart showing a target switching process executed by a client. [Figure 8] 1 is a flowchart (part 1) illustrating details of some steps in a load management process. [Figure 9] 13 is a second flowchart illustrating details of some steps in the load management process. [Figure 10] 11 is a flowchart showing a management screen related process executed by the management device. [Figure 11] 13 is a flowchart illustrating details of some steps in a load management process according to a second embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] Exemplary embodiments of the present disclosure will now be described with reference to the drawings. [First embodiment] The device management system 1 of this embodiment shown in Fig. 1 includes a management device 10 and one or more managed systems. Each managed system includes one or more sub-management devices and one or more devices. Hereinafter, the sub-management devices are referred to as clients. The one or more clients are managed by the management device 10. Each of the clients is configured to manage a device that is assigned as a management target among the one or more devices.

[0015] The illustrated device management system 1 includes a first managed system 110 and a second managed system 140. The first managed system 110 includes a plurality of clients 20 and 30. The first managed system 110 further includes devices 51, 52, 53, 54, 55, and 56 managed by the clients 20 and 30.

[0016] The clients 20 and 30 of the first managed system 110 are connected to the same local area network NT1, which may be a wired network and / or a wireless network.

[0017] The clients 20 and 30 are connected to each other so as to be able to communicate with each other through the same local area network NT1. A relay device 115 is connected to the local area network NT1. The clients 20 and 30 can communicate with the management device 10 connected to a wide area network NT0 through the relay device 115. The wide area network NT0 is, but is not limited to, the Internet, for example.

[0018] The relay device 115 is connected to the wide area network NT0 and the local area network NT1, and relays communications between the wide area network NT0 and the local area network NT1. The relay device 115 may include a firewall for restricting access from the wide area network NT0 to the local area network NT1.

[0019] Of the devices 51 , 52 , 53 , 54 , 55 , and 56 , the devices 51 , 52 , 53 , 55 , and 56 excluding the device 54 that is directly connected to the client 20 are connected to a local area network NT 1 of the first managed system 110 .

[0020] The devices 51, 52, 53, 55, and 56 are arranged so as to be able to communicate with the clients 20 and 30 through the local area network NT1. The device 54 is directly connected to the client 20, specifically, connected via a universal serial bus (USB). That is, the device 54 is wired connected to the client 20 through a communication cable so as to be able to serially communicate with the client 20. As another example, the device 54 may be directly connected to the client 20 so as to communicate wirelessly with the client 20.

[0021] The devices 51, 52, 53, 55, and 56 can be managed by the clients 20 and 30 through communication via the local area network NT1. The device 54 is managed by the client 20 through direct communication with the client 20 without going through a network.

[0022] The second managed system 140 includes a single client 40. The second managed system 140 further includes devices 57 and 58 managed by the client 40. The client 40 of the second managed system 140 is connected to a local area network NT2. The local area network NT2 is a wired network and / or a wireless network.

[0023] A relay device 145 is connected to the local area network NT2. The client 40 is disposed so as to be able to communicate with the management device 10 connected to the wide area network NT0 via the relay device 145.

[0024] The relay device 145 is connected to the wide area network NT0 and the local area network NT2, and relays communications between the wide area network NT0 and the local area network NT2. The relay device 145 may include a firewall for restricting access from the wide area network NT0 to the local area network NT2.

[0025] The devices 51 to 58 managed by the clients 20, 30, and 40 may be, but are not limited to, peripheral devices used by information devices such as personal computers. Examples of peripheral devices include printers. A printer has a function of printing an image on a recording medium (e.g., recording paper).

[0026] The devices 51 to 58 have a communication function in addition to their main functions. The communication may be wired or wireless. The devices 51 to 58 may have a communication interface of the same standard as at least one of the clients 20, 30, and 40 for communication.

[0027] Examples of the communication interface include a wired LAN communication interface conforming to the IEEE 802.3 standard, a wireless LAN communication interface conforming to the IEEE 802.11 standard, a short-range wireless communication interface conforming to the IEEE 802.15.1 standard, and a USB interface.

[0028] The device management system 1 is used, for example, by one company to remotely manage multiple devices 51-58 installed at multiple locations through the management device 10. In this case, each of the managed systems 110, 140 may be installed, for example, in one of multiple floors, offices, or branches.

[0029] The management device 10 is configured to acquire device information of each of the multiple devices 51-58 via the wide area network NT0 and the clients 20, 30, 40, and display the acquired device information to an administrator who operates the management device 10. If the devices 51-58 are printers, the device information may include information on remaining ink / toner and print setting information.

[0030] 1 as one information processing device performs processing related to management of clients 20, 30, and 40. However, the functions of the management device 10 may be realized through a cloud server connected to a wide area network NT0.

[0031] The functions of the management device 10 may be provided to a company administrator as a web service through a cloud server. In this case, the cloud server may function as the management device 10. A personal computer of the administrator that can use the cloud server may function as a user interface.

[0032] 1 includes a processor 11, a memory 12, a storage 13, a user interface 15, and a communication interface 17. The processor 11 performs functions related to management by executing processes according to a computer program stored in the storage 13. The computer program includes instructions for causing the processor 11 to perform processes described below. The processor 11 is the computer of the management device 10.

[0033] The memory 12 includes a RAM, and is used as a working area when the processor 11 executes processing. The memory 12 stores computer programs loaded from the storage 13 by the processor 11.

[0034] The storage 13 stores various data used in processing according to the computer programs executed by the processor 11. The storage 13 may include, for example, a hard disk drive (HDD) and / or a solid state drive (SSD). The memory 12 and the storage 13 are examples of storage devices.

[0035] The user interface 15 may include an input device for receiving operations from the administrator, and an output device for displaying various information to the administrator. Examples of the input device include a keyboard and a pointing device. Examples of the output device include a liquid crystal display. The communication interface 17 is configured to be able to communicate with the clients 20, 30, and 40 through the wide area network NT0.

[0036] Similarly to the management device 10, the client 20 also includes a processor 21, a memory 22, a storage 23, a user interface 25, and a communication interface 27. The communication interface 27 is a communication interface capable of communicating with devices 51, 52, 53, 55, and 56 within the local area network NT1. Examples of the communication interface 27 include a wired LAN communication interface conforming to the IEEE802.3 standard and a wireless LAN communication interface conforming to the IEEE802.11 standard.

[0037] The client 20 further includes a device communication interface 29 as a communication interface capable of directly communicating with the device 54. An example of the device communication interface 29 includes a USB interface.

[0038] In the first managed system 110, a client 30 connected to the local area network NT1 together with the client 20 is also configured in the same manner as the client 20, except that the object of management is different.

[0039] The client 40 of the second managed system 140 is also configured similarly to the client 20, except that it is connected to a local area network NT2 independent of the local area network NT1 of the first managed system 110, and the objects to be managed are different.

[0040] Although not shown, the client 30 of the first managed system 110 may be provided with a communication interface capable of communicating with the devices 51, 52, 53, 55, and 56 within the local area network NT1.

[0041] Although not shown, the client 40 of the second managed system 140 may have a communication interface capable of communicating with devices 57 and 58 in the local area network NT2. The processes executed by the client 20 described below may also be executed by the other clients 30 and 40.

[0042] The client 20 stores in the storage 23 management object description data that describes the devices to be managed. The management object description data has device identification information for each of the one or more managed devices that are to be managed by the client 20. The identification information for each device includes a device-specific identification code that is required for the client 20 to communicate with the device. Examples of this identification code include a MAC address and an IP address. Similarly to the client 20, the clients 30 and 40 also store management object description data that describes the devices to be managed by the clients 30 and 40 in storage (not shown).

[0043] The processor 21 of the client 20 is configured to communicate with and manage each device to be managed based on the management object description data stored in the storage 23. The devices to be managed in the client 20 include a device 54 directly connected to the client 20. The devices to be managed in the client 20 may further include one or more of devices 51, 52, 53, 55, 56 connected to the local area network NT1.

[0044] In order to manage the devices to be managed, the processor 21 periodically executes the device information acquisition process shown in Fig. 2. When the device information acquisition process starts, the processor 21 identifies the devices to be managed based on the management device description data stored in the storage 23 of the client 20 (S110). The processor 21 further communicates with each of the devices to be managed and acquires device information of the device from each device (S110).

[0045] The processor 21 stores the acquired device information in the storage 23 of the client 20 (S120). The device information describes the details of the corresponding device. The device information when the device is a printer is as described above. The device information may include identification information and status information of the corresponding device. The device information may include information regarding the communication form, particularly the communication standard, between the corresponding device and the client that manages the corresponding device.

[0046] The processor 21 further periodically executes a client information acquisition process shown in Fig. 3A to search for another client connected to the same local area network NT1 as the client 20 and acquire information about the client. The processor 21 further repeatedly executes a client information transmission process shown in Fig. 3B to transmit information about the client 20 to another client.

[0047] In the client information transmission process, the processor 21 waits until it receives, via the communication interface 27, a search signal transmitted from another client 30 within the same local area network NT1 (S210).

[0048] When the processor 21 receives the search signal (Yes in S210), the processor 21 transmits client information related to the client 20 as a response signal to the search signal to the other client 30 that transmitted the search signal (S220).

[0049] In the client information acquisition process, the processor 21 sends a search signal to the local area network NT1 in which the client 20 participates, via the communication interface 27 (S310).

[0050] As described above, the search signal is a signal for searching for other clients 30. The client 30 that receives the search signal operates to return its own client information.

[0051] The processor 21 receives client information from other clients 30 located within the same local area network NT1 as a response signal to the search signal (S320). The client information includes identification information of the client 30 corresponding to the sender. The identification information of the client 30 may include, for example, the MAC address and IP address of the client 30.

[0052] The client information may further include information regarding the communication environment of the client 30 corresponding to the sender. The information regarding the communication environment may include information regarding the communication form or communication standard available between the client 30 and other clients and between the client 30 and devices to be managed.

[0053] The information on the communication environment may include information on a service set identifier (SSID) when the client 30 is connected to a wireless network. The information on the communication mode may include information indicating whether the communication mode is wired or wireless.

[0054] When the processor 21 receives the client information, it stores the received client information in the storage 23 of the client 20 (S330). If the processor 21 does not receive a response signal, it determines that there are no other clients in the same local area network NT1, and ends the client information acquisition process.

[0055] The processor 21 is configured to provide the management device 10 with the client information of other clients capable of communicating with the client 20 thus stored in the storage 23 (hereinafter referred to as other client information) and the device information of the devices to be managed stored in the storage 23 in the device information acquisition process via the wide area network NT0. The other clients are clients in the same network as the client 20 that has transmitted the search signal and is found by the search. The other client information corresponds to environment information that indicates the communication environment between the client 20 and the other clients.

[0056] In order to provide the other client information and device information, the processor 21 repeatedly executes the information providing process shown in Fig. 4. When the information providing process starts, the processor 21 waits until the transmission conditions for the other client information and device information are satisfied (S410).

[0057] When the transmission conditions are satisfied (Yes in S410), the processor 21 transmits the collected information of the client 20, including other client information about other clients that can communicate with the client 20 and device information about devices managed by the client 20, to the management device 10 via the communication interface 27 (S420).

[0058] The processor 21 operates, for example, to periodically transmit the collected information to the management device 10. The processor 21 can transmit the client information of the client 20 as collected information to the management device 10 together with the other client information. The clients 30 and 40 also operate in the same manner as the client 20, and transmit their own collected information to the management device 10.

[0059] The processor 11 of the management device 10 receives collected information transmitted from each of the multiple clients 20, 30, and 40 and updates the management table stored in the storage 13 by repeatedly executing the table update process shown in FIG.

[0060] When the table update process is started, the processor 11 waits until the above-mentioned collected information is received from any of the clients 20, 30, and 40 (S510). When the collected information is received (Yes in S510), the processor 11 updates the device management table and the client management table based on the received collected information (S520).

[0061] The device management table is a table that stores the latest device information for each of the devices 51-58 that are set as managed devices in the device management system 1. The client management table is a table that stores the latest management information for each of the multiple clients 20, 30, 40 managed by the management device 10. Examples of the management information include information on other clients with which the corresponding client can communicate, and a list of managed devices assigned to the corresponding client.

[0062] Furthermore, the processor 11 determines a combination of clients 20, 30 that can communicate with each other based on the other client information received from each of the clients 20, 30, 40 and the client management table (S530).

[0063] Based on the result of this determination, the processor 11 groups a group of clients 20, 30 that can communicate with each other as clients 20, 30 that exist in the same network (S540). That is, the processor 11 groups the multiple clients 20, 30, 40 so that the clients 20, 30 that can communicate with each other are assigned to the same group (S540).

[0064] According to this embodiment, multiple clients 20, 30 belonging to the same group are in an environment in which they can communicate with devices 51, 52, 53, 55, and 56 connected to the same network as a common device, and this makes it possible for the clients to switch between devices to be managed.

[0065] In S540, the processor 11 can update the group management table stored in the storage 13 in accordance with the grouping. The group management table can be a table that describes, for each client, identification information of the group to which the corresponding client belongs. In this way, the processor 11 can update the device management table, client management table, and group management table stored in the storage 13.

[0066] In addition, the processor 11 is configured to execute the load management process shown in FIG. 6 periodically or whenever a change occurs in the allocation of devices, thereby determining the processing load L of each client 20, 30, 40 related to the management of devices, and to change the devices to be allocated to each client 20, 30, 40 as the objects to be managed.

[0067] When the load management process is started, the processor 11 determines, for each of all the clients 20, 30, 40 managed by the management device 10, the processing load L relating to the management of the device in the corresponding client (S610).

[0068] According to this embodiment, the processing load L of each client 20, 30, 40 is determined based on the number M of devices managed by the corresponding client. According to this embodiment, the processing load L is calculated as the number M of devices managed by the corresponding client (L=M).

[0069] For example, when the client 20 manages a total of two devices including the devices 51 and 54, the load of the client 20 is calculated as L=2. For example, when the client 30 manages a total of four devices including the devices 52, 53, 55, and 56, the load of the client 30 is calculated as L=4.

[0070] In the next S620, the processor 11 judges whether or not there is a high-load device among the clients 20, 30, 40 managed by the management device 10. In this embodiment, a high-load device is a client whose processing load L exceeds a reference value THL. For example, when the reference value THL is a value of 3, the client 30 whose processing load L=4 corresponds to the high-load device.

[0071] If the processor 11 determines that a high-load device exists (Yes in S620), it executes the process from S630 onwards, and if it determines that no high-load device exists (No in S620), it ends the load management process.

[0072] In S630, the processor 11 selects one of the groups in which high-load devices exist as the group to be processed. When there are multiple groups in which high-load devices exist, the processor 11 selects one of the multiple groups in which high-load devices exist as the group to be processed. The group here corresponds to the group of clients defined based on the grouping executed in S540. Multiple clients in a group can communicate with each other.

[0073] In the next step S640, the processor 11 determines whether or not there are multiple clients in the processing target group. This determination corresponds to determining whether or not there are clients other than the high-load device in the processing target group.

[0074] If it is determined that there are not multiple clients in the processing target group (No in S640), it is assumed that there is no client that can take over management of the device managed by the high-load device, and an overload is notified to the administrator (S650).

[0075] For example, the processor 11 can notify the administrator of the overload of a client by sending an e-mail addressed to the e-mail address of the administrator that is registered in advance. Alternatively, the processor 11 can notify the administrator of the overload through an output device of the management apparatus 10. The notification is made in a form that allows the administrator to understand which clients are high-load devices.

[0076] After the notification in S650, the processor 11 determines whether or not all groups in which high-load devices exist have been selected as groups to be processed (S690). If it is determined that all have been selected (Yes in S690), the load management process ends.

[0077] If it is determined that not all groups have been selected (No in S690), the processor 11 selects one of the groups containing high-load devices that has not yet been selected as a group to be processed as a new group to be processed (S630), and executes the processing from S640 onwards.

[0078] When the processor 11 determines in S640 that there are multiple clients in the processing group (Yes in S640), it executes the processing from S660 onwards. In S660, the processor 11 transmits an inquiry message to each client in the processing group via the communication interface 17. The processor 11 transmits the high-load device list together with the inquiry message to each client in the processing group.

[0079] The inquiry message is a message for inquiring of a destination client about devices that the client can manage. The inquiry message may be sent to all clients in the processing target group, or to clients excluding high-load devices.

[0080] The high-load device list is a list of devices managed by a high-load device in a processing target group. The high-load device list can be data describing the identification information of each device managed by the high-load device. However, the high-load device list does not include devices directly connected to the high-load device (e.g., device 54 in FIG. 1). This is because devices directly connected to one client cannot be managed by other clients.

[0081] Each client 20, 30, 40 in the equipment management system 1 is configured to repeatedly execute the target switching process shown in Figure 7, and in response to an inquiry message, transmit a list of devices that the client 20, 30, 40 can manage, among the devices managed by the high-load device, to the management device 10 as a list of manageable devices.

[0082] When the processor 21 of the client 20 starts the target switching process shown in FIG. 7, the processor 21 waits until it receives an inquiry message from the management device 10 via the wide area network NT0 (S810).

[0083] When the inquiry message is received, the processor 21 checks whether each device listed in the high-load device list received together with the inquiry message can be managed by communicating with the device (S820). Specifically, the processor 21 checks whether each device can be managed by attempting to obtain device information from each device listed in the high-load device list via the local area network NT1.

[0084] For example, when the high-load device is client 30 and client 30 manages devices 52, 53, 55, and 56, processor 21 of client 20 operates to communicate with each of devices 52, 53, 55, and 56 and obtain device information of the device from each of devices 52, 53, 55, and 56.

[0085] Based on the investigation result in S820, the processor 21 generates a list of devices that can be managed by the client 20 itself from among the devices listed in the high-load device list as a manageable device list (S830). The manageable device list may be data that lists identification information of the manageable devices. The processor 21 further transmits the manageable device list to the management device 10 via the communication interface 27 and the wide area network NT0.

[0086] The management device 10 reallocates the devices 51 to 56 managed within the processing target group to a plurality of clients based on the manageable device list received from each client.

[0087] The processor 21 receives the management target list transmitted from the management device 10 after this reallocation (S840), and updates the management target description data that the client 20 manages in the storage 23 based on the received management target list (S850). The management target list is a list of devices to be managed that the management device 10 specifies for the destination client. The management target list describes the identification information of each device to be managed.

[0088] The processor 21 updates the management object description data based on this management object list so as to update the information of the devices to be managed (S850). By updating the data, the processor 21 switches the devices to be managed by the own client 20 in accordance with an instruction from the management device 10. Thereafter, the processor 11 ends the target switching process.

[0089] As described above, the processor 11 of the management device 10 transmits an inquiry message and a high-load device list to each client in the processing target group in S660 (see FIG. 6). The processor 11 then receives the manageable device list transmitted from each of the clients that received the inquiry message (S665).

[0090] Thereafter, the processor 11 updates the managed devices to be assigned to each client in the processing group based on the received manageable device list (S670). The update is performed so that a client whose processing load L exceeds the reference value THL does not newly occur in the processing group by changing the allocation of managed devices. The process in S670 will be described later in detail. In S670, the client management table can be updated.

[0091] The processor 11 further generates a management target list for each client in the processing group according to the updated allocation of the devices to be managed to each client. That is, the processor 11 generates a management target list for each client in the processing group, in which identification information of the devices to be managed by the corresponding client is described.

[0092] In the next step S680, the processor 11 transmits each of the generated management target lists to the corresponding client via the communication interface 17 and the wide area network NT0. As a result, the devices managed by each client are switched.

[0093] That is, the processor 11 changes the allocation of managed objects to two or more clients 20, 30 including a high-load device included in the same group so that at least a portion of the two or more devices managed by the high-load device is managed by another client among the multiple clients 20, 30, 40 that belongs to the same group as the high-load device.

[0094] At this time, the processor 11 changes the allocation of managed objects to the two or more clients 20, 30 so that the change in the allocation of managed objects does not result in the occurrence of a new client whose processing load L exceeds the reference value THL. In this way, the processor 11 manages each client so as to manage the allocation of managed objects through communication with each client.

[0095] Next, details of the processes executed by the processor 11 in S670 and S680 will be described with reference to Figures 8 and 9. In S670 and S680, the processor 11 can execute the processes of S671 to S680 and S710 to S760 shown in Figures 8 and 9.

[0096] In S671, the processor 11 determines the total number of devices managed by multiple clients in the processing group as the number of devices in the processing group, X. For example, when the processing group is a group of clients 20 and 30 managing devices 51 to 56, the processor 11 determines that the number of devices is 6 (X=6).

[0097] In the next S673, the processor 11 divides the number of devices X by the number of clients N, which is the total number of clients in the processing group, to calculate the number of devices Y allocated to one client (Y=X / N). When two clients 20 and 30 exist in the processing group, the number of clients N=2. The reason for calculating the number of devices Y allocated in this manner is to reduce the variation between clients in the number of devices M managed by each client, in other words, the processing load L.

[0098] In the next step S675, the processor 11 determines whether or not it is possible to allocate the number of devices Y. That is, the processor 11 determines whether or not it is possible to allocate Y or less devices to be managed to each client in the group to be processed, including the high-load device, based on the manageable list received from each client in the group to be processed and the devices currently managed by each client.

[0099] This determination can be achieved by searching for possible device allocation patterns for the processing group such that all devices managed by the processing group can be assigned to a client, under the constraint that each client in the processing group is assigned Y devices or less from among the devices currently managed by the processing group and the devices listed in the manageable list.

[0100] The search for an allocation pattern may be performed for the high-load device such that a new device is not assigned as a management target, but a device to be removed from the management target is selected from the currently managed devices. In other words, an allocation pattern that allows the currently managed devices of the high-load device to be changed to other devices as the management targets may be searched for.

[0101] If it is determined in S675 that the implementation is possible (Yes in S675), the processor 11 executes the process of S677. If it is determined that the implementation is not possible (No in S675), the processor 11 executes the process of S710.

[0102] In S677, the processor 11 generates a management target list that lists Y devices, which is less than the current number M, as devices to be managed for the high-load devices, based on the searched allocation pattern.

[0103] Specifically, the processor 11 can generate a managed device list in which some devices are excluded from the currently managed devices in the high-load device according to the searched allocation pattern, and the remaining devices are listed as new managed devices.

[0104] In the next step S679, the processor 11 generates a management target list that lists new management target devices for each client other than the high-load device in the processing target group. The management target list may list the current management target devices of the corresponding client and new management target devices that were managed by the high-load device. The number of management target devices to be listed is Y or less.

[0105] In the next step S680, the processor 11 transmits the management target list for each client in the processing target group including the high-load device, which is generated in steps S677 and S679, to the corresponding client.

[0106] On the other hand, if the processor 11 makes a negative decision in S675, it executes the process of S710. In S710, the processor 11 determines whether or not there is a client in the processing target group whose processing load L is sufficiently small with respect to the reference value THL.

[0107] The process of S710 is performed to determine whether the processing load L of the other client exceeds the reference value THL if at least one of the devices managed by the high-load device is changed to a managed object of another client. If there is another client whose processing load L does not exceed the reference value THL even after this change, the processor 11 makes a positive determination in S710, and otherwise makes a negative determination.

[0108] Specifically, when a client whose processing load L is smaller than the reference value THL by 1 or more is present in the processing target group, the processor 11 can determine that a client whose processing load L is sufficiently small is present.

[0109] However, in S710, if a client does not have any device that it can manage among the devices managed by the high-load device, the client is excluded from the determination of a client with a sufficiently small processing load L. Hereinafter, a client with a sufficiently small processing load L is referred to as a low-load device.

[0110] If the determination in S710 is affirmative, the processor 11 selects, in the next S720, from among the devices currently managed by the high-load device, a device to be newly assigned as a management target to the low-load device. If there are multiple low-load devices, a device to be newly assigned as a management target for each of the multiple low-load devices can be selected from among the high-load devices. At this time, the processor 11 can adjust the number of devices to be assigned as management targets to each client so that the processing load L of each client in the processing target group is as uniform as possible.

[0111] In S720, a management target list for each low load device is generated in accordance with the above selection. That is, for each client corresponding to a low load device, a management target list is generated that lists devices to be managed by the corresponding client.

[0112] In the next step S730, the processor 11 excludes the devices to be newly assigned as management targets to the low-load device from the management targets of the high-load device. Here, the processor 11 generates a management target list that lists the devices to be managed by the high-load device (i.e., the devices that have not been excluded).

[0113] In the next S740, the processor 11 transmits the management target list generated in S720 and S730 to the corresponding client. In S740, the management target list in which the management target devices have not changed from the current state may be transmitted formally to each client in the processing target group other than the high load device and the low load device. After that, the processor 11 ends the load management process.

[0114] In addition, if the processor 11 makes a negative determination in S710, it stops changing the managed devices in the next S750. That is, it stops changing the current allocation of devices to be managed by each client including the high-load device in the processing target group. In S750, the processor 11 can formally transmit to each client a list of managed devices in which there is no change from the current managed devices.

[0115] In the next step S760, the processor 11 executes a process of notifying the administrator of the overload, similar to the process in step S650, and then ends the load management process.

[0116] In addition, the processor 11 is configured to execute a management screen-related process shown in FIG. 10 and change the allocation of devices in accordance with an operation by an administrator based on the management screen.

[0117] When the processor 11 starts the management screen related processing, it displays the management screen to the administrator through the output device of the user interface 15. That is, the processor 11 causes the output device to display the management screen (S910). The management screen can function as a graphical user interface. The management screen can be a screen capable of accepting operations related to the allocation of managed objects to each client. The management screen can further be a screen capable of displaying a list of devices managed by each client and device information for each device.

[0118] Thereafter, the processor 11 accepts an operation on the management screen from the administrator through the user interface 15 (S920). When an operation is performed, the processor 11 determines whether the corresponding operation is an end operation (S930). If it is determined that the operation is an end operation (Yes in S930), the processor 11 closes the management screen and ends the management screen-related process.

[0119] On the other hand, if the processor 11 determines that the operation is not a termination operation (No in S930) but a change operation related to the allocation of the device (Yes in S940), the processor 11 executes the process of S950. In the change operation, the operator designates the device and the client that will newly manage the device to the management device 10.

[0120] When this change operation is performed, in the process of S950, the processor 11 communicates with the designated client (hereinafter, designated client) via the communication interface 17 to investigate whether the device designated by the change operation (hereinafter, designated device) can be managed by the client designated by the change operation. Specifically, the processor 11 instructs the designated client to obtain device information from the designated device.

[0121] The designated client that has received the instruction can then follow the instruction to attempt communication to acquire device information from the designated device in the local area network to which the client is connected. The designated client can also notify the management device 10 of the success or failure of acquiring the device information.

[0122] The processor 11 determines whether the designated client has succeeded in acquiring the device information from the designated device according to the notification of success or failure (S960). If the processor 11 determines that the acquisition was successful (Yes in S960), it changes the management target of the current management client, which is the client currently managing the designated device, so as to exclude the designated device from the management target of the current management client (S970). The processor 11 further changes the management target of the designated client so as to add the designated device to the management target of the designated client (S970).

[0123] The processor 11 updates the client management table and transmits the list of managed clients to the currently managed client and the designated client, thereby completing the procedure for changing the managed client.

[0124] Thereafter, the processor 11 updates the management screen (S975) and waits until the next operation is performed in S920. In addition, when an operation other than the end operation or the change operation is performed (No in S940), the processor 11 executes processing according to the performed operation (S990).

[0125] According to the device management system 1 of the first embodiment described above, in an environment in which multiple devices 51-56 are managed by multiple clients 20, 30, the management device 10 distinguishes between the clients 20, 30 and the devices 51-56 located within the same network, and changes the allocation of the managed devices 51-56 to each of the clients 20, 30 so as to reduce the processing load L required for managing the devices 51-56.

[0126] In particular, when a client with a processing load L exceeding a reference value THL is found as a high-load device, some of the devices managed by the high-load device are changed to be managed by other clients in the same network, thereby reducing the processing load L in the high-load device. Furthermore, when making this change, the devices to be managed are determined for each client so that no new high-load devices are created as a result of the change.

[0127] Therefore, according to this embodiment, it is possible to appropriately control the processing load L in each of the clients 20, 30 in a system in which a plurality of devices 51-56 are managed by a plurality of clients 20, 30. In particular, in this embodiment, since the processing load L is determined based on the number M of devices to be managed, it is possible to appropriately control the processing load L by a simple calculation.

[0128] [Second embodiment] Next, a device management system 1 according to a second embodiment will be described. However, the device management system 1 according to the second embodiment corresponds to a modified example of the device management system 1 according to the first embodiment, and has many components in common with the first embodiment.

[0129] The device management system 1 of the second embodiment differs from the first embodiment in the method of calculating the processing load L. The device management system 1 of the second embodiment further differs from the first embodiment in that the processor 11 of the management device 10 executes the process shown in Fig. 11 in place of the processes shown in Fig. 8 and Fig. 9 in S680 and S690 of the load management process. In other respects, the device management system 1 of the second embodiment is similar to the first embodiment.

[0130] Therefore, in the following, the processes executed in S680 and S690 will be selectively described as differences between the device management system 1 of the second embodiment and the first embodiment. Descriptions of the configurations of the device management system 1 of the second embodiment that are common to the first embodiment will be omitted as appropriate.

[0131] This embodiment is an embodiment assuming that the processing load L related to device management differs depending on the communication form between the device and the client that manages the device. In this embodiment, the processing load L of each client is determined based on the number of devices for each communication form managed by the client and the communication form between the client and the device.

[0132] Specifically, the processing load L of each client is calculated based on the number of devices M[i] for each communication type managed by the client and the load coefficient W[i] for each communication type according to the following formula: L = ΣW[i] M[i]. i is the index of the communication type. Σ means the sum of W[i] M[i] for communication type i. In other words, the processing load L is calculated as the weighted sum of the number of devices M[i] for each communication type when the number of devices M[i] is weighted by the corresponding load coefficient W[i].

[0133] Here, the communication form is distinguished, for example, by wired communication form and wireless communication form. For example, the processing load L is calculated based on the number M[1] of devices that the client manages by wired communication and the number M[2] of devices that the client manages by wireless communication, as follows: L = W[1] · M[1] + W[2] · M[2].

[0134] Alternatively, the communication formats are differentiated by communication standards. For example, the processing load L is calculated based on the number M[1] of devices managed by the client through communication according to the first communication standard, the number M[2] of devices managed through communication according to the second communication standard, the number M[3] of devices managed through communication according to the third communication standard, and the number M[4] of devices managed through communication according to the fourth communication standard, as follows: L = W[1] · M[1] + W[2] · M[2] + W[3] · M[3] + W[4] · M[4].

[0135] The first communication standard is, for example, a wired communication standard conforming to IEEE802.3. The second communication standard is, for example, a wireless communication standard conforming to IEEE802.11. The third communication standard is, for example, a wireless communication standard conforming to IEEE802.15.1. The fourth communication standard is, for example, a USB standard.

[0136] The load coefficient W[i] can be set smaller as the communication speed of the corresponding communication format / standard is faster, and larger as the communication speed is slower. The processing time required for communication by the client varies depending on the communication speed. According to this embodiment, the processing load L is calculated taking into account the difference in communication speed.

[0137] According to this embodiment, the processor 11 calculates the processing load L for each client according to the above-mentioned formula in S610 of the load management process shown in Fig. 6. The reference value THL used to identify a high-load device in S620 is set to a value that takes into account the scale of the processing load L calculated according to the above-mentioned formula.

[0138] In S680 and S690, the processor 11 can execute the processes of S1010 to S1060 shown in Fig. 11. In S1010, the processor 11 selects one client other than the high-load device among the clients in the processing target group.

[0139] In the next step S1020, the processor 11 determines which high-load devices the selected client can manage based on the manageable device lists sent from each client received in S665. The "high-load device devices" here means "devices currently managed by the high-load device."

[0140] In the next step S1030, the processor 11 searches for an allocation pattern of devices for the selected client, in which the processing load L is equal to or less than the reference value THL. Searching for an allocation pattern corresponds to searching for a combination of devices to be managed for the selected client, in which the processing load L is equal to or less than the reference value THL. The processing load L is calculated according to the above-mentioned formula, using the load coefficient W[i] corresponding to the communication format / standard between the selected client and the devices.

[0141] Specifically, searching for an allocation pattern corresponds to searching for a combination of managed devices to be assigned to the selected client by a method of adding devices selected from the high-load device devices as managed devices to a group of managed devices currently assigned to the selected client.

[0142] The processor 11 executes the processes of S1010 to S1030 while switching the selected client until the above-mentioned allocation pattern is searched for for all clients except the high-load device in the processing target group. When the allocation pattern search for all clients is completed (Yes in S1040), the processor 11 executes the process of S1050.

[0143] In S1050, based on the allocation pattern searched for for each client other than the high-load device in the processing group, the processor 11 determines devices to be excluded from the management target of the high-load device and clients to which these devices will be newly assigned, so as to minimize the variation in processing load L among clients.

[0144] Based on this determination, the processor 11 determines a new allocation of devices to be managed to each client in the processing target group including the high-load device. The variation here refers to the variation in the processing load L among the clients in the processing target group including the high-load device.

[0145] In S1050, the processor 11 can, for example, determine an allocation pattern for each client found by the search that is consistent between clients, and select from the determined allocation patterns an allocation pattern that minimizes the variation between clients in the processing load L. This allows the processor 11 to newly allocate devices to each client while preventing the processing load L from exceeding the reference value THL.

[0146] In order to determine the allocation that minimizes the variation, the processor 11 can determine the new allocation while calculating the processing load L of the high-load device when the allocation is changed. Thereafter, the processor 11 generates and transmits to each client in the processing group a management target list according to the determined new allocation (S1060).

[0147] According to the second embodiment described above, when differences in communication formats or communication standards have a significant impact on the processing load L related to the management of devices at each client, it is possible to calculate the processing load L with higher accuracy and change the allocation of devices according to the processing load L.

[0148] [Other embodiments] The present disclosure is not limited to the above-described embodiment, and can adopt various aspects. 1 is merely an example. The device management system 1 may include three or more managed systems. Each of the managed systems may include three or more clients that can communicate with each other.

[0149] The method of allocating devices is not limited to the above embodiment. If it is not possible to change the devices to be managed so that the processing load L does not exceed the reference value THL, it is possible to consider not changing the allocation of devices. In addition, a method of reallocating devices can be considered so as to reduce the variation in the processing load L within the processing target group as much as possible.

[0150] In the above embodiment, the processing load L in the high-load device is adjusted by a method of setting the devices of the high-load device as the management target of the other clients. However, the devices managed by the high-load device may be changed so that some devices managed by the high-load device are removed from the management target of the high-load device, while some devices managed by other clients are added to the management target of the high-load device. Similarly, for clients other than the high-load device, the managed devices may be changed so that some devices are removed from the management target of the high-load device, while some devices managed by other clients are added to the management target.

[0151] By adding or removing managed devices to each client, not limited to high-load devices and low-load devices, it is possible to reallocate devices to each client so that the processing load L of each client does not exceed the reference value THL.

[0152] In addition, the management device 10 may determine clients that can communicate with each other based on information about the communication environment included in the received client information (S530) and group the clients (S540). For example, multiple clients participating in the same wireless network can be determined as clients that can communicate with each other based on the SSID and grouped. With this type of determination, it is not necessary to transmit and receive a search signal and its response signal between the clients to determine whether or not they can communicate with each other.

[0153] Alternatively, the client information may include information on the relay devices 115 and 145. The management device 10 may determine that a plurality of clients 20 and 30 that can communicate with the management device 10 via the same relay device 115 are clients that participate in the same local area network NT1 and can communicate with each other.

[0154] Alternatively, the client information may include identification information that allows the client's address on the network to be identified, and the management device 10 may determine and group the clients 20, 30 that can communicate with each other based on this identification information.

[0155] The function of one component in the above embodiments may be distributed among multiple components. The functions of multiple components may be integrated into one component. Part of the configuration of the above embodiments may be omitted. At least part of the configuration of the above embodiments may be added to or substituted for the configuration of another of the above embodiments. All aspects included in the technical idea identified from the wording of the claims are embodiments of the present disclosure.

[0156] [Technical idea disclosed in this specification] It can be understood that the present specification discloses the following technical ideas. [Item 1] A computer program executed by a computer of a management device configured to manage a plurality of sub-management devices through communication with the plurality of sub-management devices, An instruction for causing a computer of the management device to execute a management process, each of the plurality of sub-management devices is configured to communicate with one or more devices assigned as management targets and to manage the one or more devices; The management process includes: grouping at least a portion of the sub-management devices based on information received from the sub-management devices such that two or more sub-management devices that are in an environment capable of communicating with a common device are assigned to the same group; changing the allocation of the managed objects to the two or more sub-management devices including a high-load device included in the same group as the high-load device, so that at least a part of the two or more devices managed by a high-load device, which is a sub-management device among the multiple sub-management devices and which is a sub-management device whose processing load related to the management of the two or more devices exceeds a standard, is managed by another sub-management device among the multiple sub-management devices which belongs to the same group as the high-load device; Including, The changing includes changing the allocation of the managed objects to the two or more secondary management devices so that a secondary management device whose processing load exceeds the standard does not newly occur as a result of changing the allocation of the managed objects. Computer program. [Item 2] 2. The computer program according to item 1, wherein the processing load is determined based on the number of devices managed by the corresponding sub-management device. [Item 3] 3. The computer program according to item 2, wherein the processing load is determined based on the number of devices as well as the form of communication between the corresponding sub-management device and the devices managed by the corresponding sub-management device. [Item 4] The computer program according to any one of items 1 to 3, wherein the modifying includes changing an allocation of the managed objects to the two or more sub-management devices so as to reduce variation in the processing load among the two or more sub-management devices included in the same group. [Item 5] The computer program according to any one of items 1 to 4, wherein grouping the multiple sub-management devices includes grouping the multiple sub-management devices so that the two or more sub-management devices connected to the same network and in an environment capable of communicating with devices connected to the same network are assigned to the same group. [Item 6] A computer program described in any one of items 1 to 4, wherein grouping the multiple sub-management devices includes determining which of the two or more sub-management devices is in an environment in which it can communicate with the common equipment based on identification information of the corresponding sub-management device or information regarding the communication environment of the corresponding sub-management device received from each of the multiple sub-management devices. [Item 7] each of the plurality of sub-management devices is connected to a network and configured to search for other sub-management devices in the same network and transmit information about the other sub-management devices discovered by the search as environment information to the management device; The computer program of any one of items 1 to 4, wherein grouping the multiple sub-management devices includes grouping the multiple sub-management devices so that the two or more sub-management devices connected to the same network and in an environment capable of communicating with devices connected to the same network are assigned to the same group based on the environmental information received from each of the multiple sub-management devices. [Item 8] each of the plurality of sub-management devices is connected to a network and is capable of managing, as a first device, one or more devices connected to the same network; At least one of the sub-management devices among the plurality of sub-management devices is further capable of managing one or more devices directly connected thereto by wire or wirelessly as second devices; The computer program according to any one of items 1 to 7, wherein the changing includes changing an allocation of the managed objects to the two or more sub-management devices by changing an allocation of the first device to the two or more sub-management devices, among the first device and the second device. [Item 9] A management device configured to manage a plurality of sub-management devices through communication with the plurality of sub-management devices, A processor; a storage device that stores instructions for causing the processor to execute a management process; Equipped with each of the plurality of sub-management devices is configured to communicate with one or more devices assigned as management targets and to manage the one or more devices; The management process includes: grouping at least a portion of the sub-management devices based on information received from the sub-management devices such that two or more sub-management devices that are in an environment capable of communicating with a common device are assigned to the same group; changing the allocation of the managed objects to the two or more sub-management devices including a high-load device included in the same group as the high-load device, so that at least a part of the two or more devices managed by a high-load device, which is a sub-management device among the multiple sub-management devices and which is a sub-management device whose processing load related to the management of the two or more devices exceeds a standard, is managed by another sub-management device among the multiple sub-management devices which belongs to the same group as the high-load device; Including, The changing includes changing the allocation of the managed objects to the two or more secondary management devices so that a secondary management device whose processing load exceeds the standard does not newly occur as a result of changing the allocation of the managed objects. Management device. [Item 10] 1. A management method executed in a management device configured to manage a plurality of sub-management devices through communication with the plurality of sub-management devices, comprising: each of the plurality of sub-management devices is configured to communicate with one or more devices assigned as management targets and to manage the one or more devices; The management method includes: grouping at least a portion of the sub-management devices based on information received from the sub-management devices such that two or more sub-management devices that are in an environment capable of communicating with a common device are assigned to the same group; changing the allocation of the managed objects to the two or more sub-management devices including a high-load device included in the same group as the high-load device, so that at least a part of the two or more devices managed by a high-load device, which is a sub-management device among the multiple sub-management devices and which is a sub-management device whose processing load related to the management of the two or more devices exceeds a standard, is managed by another sub-management device among the multiple sub-management devices which belongs to the same group as the high-load device; Including, The changing includes changing the allocation of the managed objects to the two or more secondary management devices so that a secondary management device whose processing load exceeds the standard does not newly occur as a result of changing the allocation of the managed objects. Management method. [Explanation of symbols]

[0157] 1...device management system, 10...management device, 11...processor, 12...memory, 13...storage, 15...user interface, 17...communication interface, 20, 30, 40...client, 21...processor, 22...memory, 23...storage, 25...user interface, 27...communication interface, 29...device communication interface, 51, 52, 53, 54, 55, 56, 57, 58...device, 110, 140...managed system, 115, 145...relay device, NT0...wide area network, NT1, NT2...local area network.

Claims

1. A computer program executed by a computer of a management device configured to manage a plurality of sub-management devices through communication with the plurality of sub-management devices, An instruction for causing a computer of the management device to execute a management process, each of the plurality of sub-management devices is configured to communicate with one or more devices assigned as management targets and to manage the one or more devices; The management process includes: grouping at least a portion of the sub-management devices based on information received from the sub-management devices such that two or more sub-management devices that are in an environment capable of communicating with a common device are assigned to the same group; changing allocation of the managed objects to the two or more sub-management devices including a high-load device included in the same group as the high-load device, so that at least a part of the two or more devices managed by a high-load device that is a sub-management device of the plurality of sub-management devices and that is a sub-management device whose processing load related to the management of the two or more devices exceeds a standard is managed by another sub-management device of the plurality of sub-management devices that belongs to the same group as the high-load device; Including, The change includes changing the allocation of the managed objects to the two or more secondary management devices so that a secondary management device whose processing load exceeds the standard does not newly occur as a result of changing the allocation of the managed objects. Computer program.

2. 2. The computer program product according to claim 1, wherein the processing load is determined based on the number of devices managed by the corresponding sub-management device.

3. 3. The computer program product according to claim 2, wherein the processing load is determined based on the number of devices as well as a communication form between the corresponding sub-management device and a device managed by the corresponding sub-management device.

4. A computer program according to any one of claims 1 to 3, wherein the modifying includes modifying the allocation of the managed objects to the two or more sub-management devices so as to reduce the variation in the processing load among the two or more sub-management devices included in the same group.

5. The computer program product of claim 1, wherein grouping the multiple sub-management devices includes grouping the multiple sub-management devices so that the two or more sub-management devices that are connected to the same network and are in an environment capable of communicating with devices connected to the same network are assigned to the same group.

6. The computer program of claim 1, wherein grouping the multiple sub-management devices includes determining which of the two or more sub-management devices is in an environment capable of communicating with the common equipment based on identification information of the corresponding sub-management device or information regarding the communication environment of the corresponding sub-management device received from each of the multiple sub-management devices.

7. each of the plurality of sub-management devices is connected to a network and configured to search for other sub-management devices in the same network and transmit information about the other sub-management devices discovered by the search as environment information to the management device; The computer program product of claim 1, wherein grouping the plurality of sub-management devices includes grouping the plurality of sub-management devices so that the two or more sub-management devices connected to the same network and in an environment capable of communicating with devices connected to the same network are assigned to the same group based on the environmental information received from each of the plurality of sub-management devices.

8. each of the plurality of sub-management devices is connected to a network and is capable of managing, as a first device, one or more devices connected to the same network; At least one of the sub-management devices among the plurality of sub-management devices is further capable of managing one or more devices directly connected thereto by wire or wirelessly as second devices, 2. The computer program product of claim 1, wherein the change includes changing an allocation of the managed objects to the two or more sub-management devices by changing an allocation of the first device to the two or more sub-management devices, among the first device and the second device.

9. A management device configured to manage a plurality of sub-management devices through communication with the plurality of sub-management devices, A processor; a storage device that stores instructions for causing the processor to execute a management process; Equipped with each of the plurality of sub-management devices is configured to communicate with one or more devices assigned as management targets and to manage the one or more devices; The management process includes: grouping at least a portion of the sub-management devices based on information received from the sub-management devices such that two or more sub-management devices that are in an environment capable of communicating with a common device are assigned to the same group; changing allocation of the managed objects to the two or more sub-management devices including a high-load device included in the same group as the high-load device, so that at least a part of the two or more devices managed by a high-load device that is a sub-management device of the plurality of sub-management devices and that is a sub-management device whose processing load related to the management of the two or more devices exceeds a standard is managed by another sub-management device of the plurality of sub-management devices that belongs to the same group as the high-load device; Including, The change includes changing the allocation of the managed objects to the two or more secondary management devices so that a secondary management device whose processing load exceeds the standard does not newly occur as a result of changing the allocation of the managed objects. Management device.

10. 1. A management method executed in a management device configured to manage a plurality of sub-management devices through communication with the plurality of sub-management devices, comprising: each of the plurality of sub-management devices is configured to communicate with one or more devices assigned as management targets and to manage the one or more devices; The management method includes: grouping at least a portion of the sub-management devices based on information received from the sub-management devices such that two or more sub-management devices that are in an environment capable of communicating with a common device are assigned to the same group; changing allocation of the managed objects to the two or more sub-management devices including a high-load device included in the same group as the high-load device, so that at least a part of the two or more devices managed by a high-load device that is a sub-management device of the plurality of sub-management devices and that is a sub-management device whose processing load related to the management of the two or more devices exceeds a standard is managed by another sub-management device of the plurality of sub-management devices that belongs to the same group as the high-load device; Including, The change includes changing the allocation of the managed objects to the two or more secondary management devices so that a secondary management device whose processing load exceeds the standard does not newly occur as a result of changing the allocation of the managed objects. Management method.

Images