JP2019046231A - Device management system and device management method - Google Patents

Abstract

To eliminate the need for a troublesome connection setup when a device is changed, and to enable device data to be acquired even when an abnormality occurs in an edge server.SOLUTION: Provided is a device management system 1000 including a plurality of edge servers each monitoring a monitoring target having a device, and a management server that manages the plurality of edge servers. Each of the plurality of edge servers includes a connection management unit that, in the case where it is determined that a subordinate device of another edge server has been switched to own server on the basis of measurement information in the past received from the monitoring target through wireless communication and measurement information at present, updates a connection target table that manages a subordinate device of own server, and transmits the connection target table after the update to the management server. The management server includes a server management unit that, on the basis of the connection target table after the update received from an edge server and a connection target master table that manages subordinate devices of the plurality of edge servers, updates the connection target master table.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a device management system and a device management method.

  Remote monitoring services using IoT (Internet of Things) technology, such as installing devices (sensors) on various monitoring devices such as manufacturing equipment used in manufacturing, etc., and monitoring operating conditions and deterioration trends, have become widespread It is getting worse. In the conventional IoT system, it is common to directly communicate between a cloud storing data and a device, and there is a problem that communication delay occurs as the distance between the two physically increases.

  On the other hand, in recent years, edge computing technology that communicates with devices not on the cloud but on an intermediate server (edge server) such as a gateway distributed near the end user has attracted attention. Edge computing technology has advantages such as network costs can be reduced and response can be improved in real time because the edge server is located physically closer to the device or user than the cloud. As a technology related to such edge computing, for example, it is described in Patent Document 1.

Japanese Patent Application Laid-Open No. 2002-277032

  In the future, with the spread of edge computing technology, for example, for devices with low operating rates that are not normally used, monitor multiple devices by replacing one device or the like for cost reduction. It is expected that. There is a possibility that manual connection setup etc. may occur to the edge server that is the new connection destination at the time of replacement (assumption task 1). In addition, if an edge server abnormally stops, data from devices connected to the edge server may not be acquired during the period from the time when a field maintenance worker finds an abnormal stop until completion of the recovery work ( Expected task 2). As described above, with the spread of edge computing, there are assumed operational issues in device monitoring and edge server failure, and it is required to solve these issues.

  The present invention provides a device management system and device management method capable of acquiring device data even if an edge server becomes abnormal without requiring troublesome connection setup even when the device is replaced. With the goal.

  A device management system according to the present invention is a device management system including a plurality of edge servers for monitoring a monitoring target having a device and a management server for managing the plurality of edge servers, wherein the plurality of edge servers Each determines whether another device subordinate to the edge server has been switched to the own server or not based on past measurement information and current measurement information received from the monitoring target via wireless communication, and others Connection management for managing the devices under the own server, and transmitting the updated connection object table to the management server when it is determined that the device under the edge server is switched to the own server. And the management server receives the updated connection target table received from the edge server, and Based on the connection target master table to manage devices under few edge server, configured the connection target master table server management unit that updates, as a device management system comprising: a.

  The present invention is also understood as a device management method performed by the device management system.

  According to the present invention, even when a device is replaced, data of the device can be acquired even when an abnormality occurs in the edge server without requiring a troublesome connection setup.

It is a figure showing an example of composition of a device management system. It is a block diagram which shows the functional structure of an edge server. It is a figure which shows the example of a connection object table. It is a block diagram showing functional composition of a cloud server. It is a figure which shows the example of a server management table. It is a sequence diagram which shows the process sequence of the process (device confirmation process) performed by this system.

  Hereinafter, embodiments of a device management system and a device management method will be described in detail with reference to the attached drawings.

  FIG. 1 is a view showing a configuration example of a device management system 1000. As shown in FIG. 1, the device management system 1000 monitors the monitoring targets 100A, 100B, and 100C to be monitored by the device management system 1000 by IoT, and an edge server 200A that monitors these monitoring targets 100A to 100C under the monitoring targets 100A, 100B, and 100C. 200B and 200C, and the cloud server 300 which manages these edge servers 200A-200C are comprised. Although FIG. 1 shows an example in which three monitoring targets 100, three edge servers 200, and one cloud server 300 are provided, these numbers are arbitrary according to the size and environment of the system. It can be determined. The configuration of the monitoring target 100, the edge server 200, and the cloud server 300 and data to be held will be described later. In the following description, when the monitoring targets are collectively referred to, the monitoring target 100 is simply used. When the edge servers are collectively referred to, the edge servers 200 are simply referred to. There is something to do.

  The monitoring targets 100 and the edge servers 200 are connected by networks N1, N2, and N3 that are wirelessly communicated according to a predetermined standard for realizing the IoT. The edge servers 200 and the edge servers 200 and the cloud server 300 are connected by networks N4, N5, and N6, which are common public networks such as the Internet. First, the monitoring target 100 will be described.

  The monitoring target 100 is an IoT target, and is a monitoring device monitored by the device management system 1000. As shown in FIG. 1, the monitoring target 100 includes a monitoring device 101 monitored by the present system, and a device 102 having a sensor for detecting information obtained from the monitoring device 101. Here, the monitoring device 101 is a monitoring device that broadly indicates various targets to be monitored, and, for example, industrial products such as personal computers (PCs), doors, and refrigerators, parts of these materials and materials, animals such as pets, Plants such as potted plants, crops such as rice, environment such as temperature and humidity, atmospheric pressure, illuminance, noise, etc. are included. As an example of the monitoring target 100, when the monitoring device 101 is an object having an opening / closing mechanism such as a door or a window, the device 102 can wirelessly communicate with the opening / closing sensor or an apparatus capable of wireless communication. It is. Therefore, the device 102 includes a sensor that detects a measurement value such as a state or position of the monitoring device 101 as the above information from the monitoring device 101 and a environmental value, and a wireless communication unit for transmitting the measurement value to the edge server 200. Have.

  By attaching such a device 102 to the monitoring device 101, various information can be obtained from the monitoring device 101. In this example, although the case where the device 102 is attached to the monitoring apparatus 101 is described, these may be integrally configured.

The edge server 200 is configured of a general server apparatus as hardware, and is a server that monitors the monitoring target 100 and manages information obtained from the monitoring target 100.
FIG. 2 is a block diagram showing a functional configuration of the edge server 200. As shown in FIG. As shown in FIG. 2, the edge server 200 functionally includes a storage unit 201, a connection management unit 202, an operation monitoring unit 203, a wireless communication unit 204, and a communication unit 205. ing.

  The storage unit 201 includes, as hardware, a general storage device such as an HDD (Hard Disk Drive), and stores the connection target table 2011.

  FIG. 3 is a diagram illustrating an example of the connection target table 2011. The connection target table 2011 is a table for managing the connection state of the monitoring target 100 subordinate to each edge server 200. As illustrated in FIG. 3, the connection target table 2011 includes a monitoring target ID for identifying the monitoring target 100, monitoring device information indicating the monitoring device 101 that configures the monitoring target, and a device 102 that configures the monitoring target. The device information indicating the address of the device 102, the measurement threshold value indicating the threshold of the measurement value of the sensor of the device 102, and the data including the measurement value of the sensor and the measurement date and time are stored in association with each other.

  In FIG. 3, for example, the monitoring target 100 whose monitoring target ID is identified as "T_A0001" is a device having a "door" which is the monitoring device 101 and an "open / close sensor" which is a sensor attached to the "door". And indicates that the address (for example, the MAC address) of the device 102 is "a1". Also, the threshold of the measured value measured by the "open / close sensor" is "a2" (for example, 1 centimeter indicating the upper limit of the measured value), the actual measured value is "a3" (for example, 0.5 millimeter), It indicates that the measurement date and time is “a4” (for example, May 01, 2017, 00:00:00). In this example, in order to reduce the amount of communication between the device 102 and the edge server 200, the measurement threshold is provided so as not to communicate the measured value that can be regarded as an error range. If the number is considered to be small, it may not necessarily be provided.

  When the wireless communication unit 204 of the edge server 200 receives measurement information including the monitoring target ID, the measurement value, and the measurement date and time from the monitoring target 100 under the edge server 200, the connection management unit 202 uses the monitoring target ID as a key. As the connection target table 2011, and update these measurement information as needed. Although the case where measurement information is overwritten and updated is explained below, you may accumulate these measurement information by history for every monitoring object ID.

  The connection management unit 202 determines whether the monitoring target 100 is under the control of the own server according to the radio wave intensity with the device 102 of the monitoring target 100, and is the monitoring target 100 under the control of the own server. When it is determined, the measurement information of the monitoring target stored in the connection target table 2011 is updated. Specific processing executed by the connection management unit 202 will be described later using a sequence.

  The operation monitoring unit 203 monitors resources of its own server (for example, CPU (Central Processing Unit), memory, disk capacity, network interface) to determine whether or not an abnormality has occurred, and an abnormality occurs in the resource. If it is determined, the cloud server 300 transmits status information including the server ID that is the identification information of the own server, the identification information of the resource in which the abnormality has occurred, and the information indicating the operating state (abnormal or normal) of the resource. Do. Specific processing executed by the operation monitoring unit 203 will be described later using a sequence.

  The wireless communication unit 204 wirelessly communicates various information including the measurement information and the like with the device 102 of the monitoring target 100.

  The communication unit 205 wirelessly communicates various information including the status information and the like with the other edge server 200.

  The cloud server 300 is configured by a general server device as hardware, and manages the edge server 200 and monitors the operating state of each edge server 200.

FIG. 4 is a block diagram showing a functional configuration of the cloud server 300. As shown in FIG. As shown in FIG. 4, the cloud server 300 functionally includes a storage unit 301, a server management unit 302, and a communication unit 303.
The storage unit 301 is formed of a general storage device such as an HDD as hardware, and stores a connection target master table 3011 and a server management table 3012.

  The connection target master table 3011 is a master table in which all the tables of the connection target table 2011 stored in each edge server 200 are combined for each edge server. The specific configuration of the connection target master table 3011 is the same as that shown in FIG.

  FIG. 5 is a diagram showing an example of the server management table 3012. The server management table 3012 is a table for managing each edge server 200. As shown in FIG. 5, the server management table 3012 includes a server ID for identifying the edge server 200, own status information indicating the operating state of the edge server itself, and other edges connected to the edge server. Other status information indicating the operating status of the server, switch information indicating that the monitoring target 100 under control of another edge server has switched to the control of its own server, and a switch threshold value indicating the condition for switching the monitoring target 100 Are stored in association with each other.

  In FIG. 5, for example, the edge server 200 (for example, the edge server 200A) identified by the server ID "S_A0001" has an operation state of itself "s1" (for example, CPU operating rate: 40%, cache memory utilization rate: 20%, disk free capacity: X1 GB, communication speed: Y1 bps, and the operating status of the edge server (for example, edge server 200 B) connected to the relevant edge server is “s2” (for example, CPU operating rate: 70%, Cache memory usage rate: 80%, disk free capacity: X2 GB, communication speed: Y2 bps, and the switch information is “s3” (for example, the device 102 B attached to the monitoring target 100 B under the edge server 200 B is an edge server The device 102A attached to the monitoring target 100A under 200A And the switch threshold is "s4" (for example, when the measured value included in the measurement information of the device 102B is a monitoring device that indicates the operation rate), the operation rate is determined as 80%. The device 102 that outputs measurement information that satisfies the switch threshold is the above-described replacement target.

  Note that although the use status of the edge server resource is indicated in the above self status information and the other status information, in addition to the information regarding these resources, whether the start of the edge server 200 is normal or abnormal Or, information indicating whether the resource is operating normally may be included.

  Further, as another example of the switch information and the switch threshold, when the field intensity between the device 102B and the edge server 200A exceeds the field intensity indicated by the switch threshold, the device 102B under the edge server 200B is an edge. Information (for example, information stored in the connection target table shown in FIG. 3) indicating that the device 102A of the monitoring target 100A subordinate to the server 200A has been replaced may be stored.

  As described above, since it is automatically determined whether the radio wave intensity has exceeded the predetermined threshold value as switch information and the replacement of the device is performed, the monitoring target can be managed without bothering the system administrator and the like.

  The server management unit 302 merges the connection target table 2011 received from the edge server 200 for each server, and updates the connection target master table 3011. Specific processing executed by the server management unit 302 will be described later using a sequence.

  The communication unit 303 communicates with the edge server 200 various types of information including the information stored in the connection target table 2011 and the like.

  In addition, each process performed by the edge server 200 and the cloud server 300 is actually realized by executing a program in which an arithmetic device such as a CPU is installed in these servers. The program is provided by being incorporated in a ROM or the like in advance, or is a file in an installable format or an executable format and a computer readable recording medium such as a CD-ROM, a CD-R, and a DVD (Digital Versatile Disk). It may be recorded and provided or distributed. Furthermore, the program may be stored on a computer connected to a network such as the Internet, and may be provided or distributed by being downloaded via the network. Subsequently, processing performed in the present system will be described.

  FIG. 6 is a sequence diagram showing a processing procedure of processing (device confirmation processing) performed in the present system. FIG. 6 describes the processing when the device 102B subordinate to the edge server 200B is replaced as the device 102A subordinate to the edge server 200A, and when the status information of the edge server 200C includes an abnormality.

  As shown in FIG. 6, the connection management unit 202 of the edge server 200A receives measurement information from the subordinate device (S601). The measurement information is repeatedly performed at a predetermined timing, and thereafter, the device 102B subordinate to the edge server 200B is replaced with the monitoring target 100A subordinate to the edge server 100A, and the device 102 becomes a monitoring device switched (S).

  The connection management unit 202A of the edge server 200A determines whether a new device has been switched under the control of the edge server 200A (S602). In the determination, for example, the connection management unit 202A detects a device whose radio wave intensity is equal to or more than the switch threshold, and the number of devices whose radio wave intensity is equal to or more than the switch threshold before the determination and the number after the determination By comparison, if there is a difference between the two (if there is an increase) (S602: Yes), it is determined that the device has been switched and the configuration of the device 102A subordinate to the own server has changed, and the process proceeds to S603. On the other hand, when it is determined that the above configuration has not been changed (S602; No), the process returns to S601.

  The connection management unit 202A refers to the connection target table 2011A, and updates the measurement information corresponding to the same monitoring target ID as the monitoring target ID included in the measurement information received from the switched device 102B to the received measurement information. (S603).

  For example, in a case where the radio wave intensity of the previous time (past) between the connection management unit 202A and the device 102A attached to the monitoring target ID “T_A0001” does not satisfy a predetermined threshold, the connection managing unit 202A does not meet the device 102A. If the current (current) radio wave intensity becomes equal to or higher than the switch threshold, it is determined that the device 102A has been switched to another device (in this example, the device 102B) due to aging, and the monitoring stored in the connection target table 2011A The measurement information of the device 102A corresponding to the monitoring target of the target ID “T_A0001” is updated to the measurement information of the device 102B.

  The connection management unit 202A transmits the connection target table 2011A after the measurement information is updated to the cloud server 300 (S604). The server management unit 302 of the cloud server 300 associates the updated connection target table 2011A received from the edge server 200A with the connection target master table 3011 stored in the storage unit 301, and generates a connection target master table The connection target table 2011A included in the table 3011 is rewritten to the connection target table 2011A after the update (S605). By executing the processing of S601 to S605, the connection target table managed by the edge server and the connection target master table managed by the cloud server 300 are automatically updated even if a device is added due to replacement. Devices in operation can be properly monitored and managed without bothering an administrator.

  On the other hand, in the edge server 200B, the connection management unit 202B receives the measurement information from the subordinate device as in the case of the edge server 200A (S606). As described above, since the device 102B subordinate to the edge server 200B is replaced with the monitoring target 100A subordinate to the edge server 100A and the device 102 is switched (S), the connection management unit 202B of the edge server 200B becomes subordinate to the edge server 200B. It is determined whether the device has been switched (S), and the corresponding record is deleted from the connection target table 2011B (S607, S608).

  For example, when the difference between the previous radio wave intensity and the current radio wave intensity between the device 102B attached to the monitoring target ID “T_B0001” and the current radio wave intensity has a value greater than or equal to a certain value, the connection management unit 202B determines the device 102B. Is determined to be switched as a device under another edge server (in this example, the device 102A under the edge server 200A), and a device corresponding to the monitoring target of the monitoring target ID “T_B0001” stored in the connection target table 2011B. Delete the record containing the measurement information of 102B.

  The connection management unit 202B determines that the difference between the previous radio wave intensity and the current radio wave intensity with the device 102B is a predetermined value or more, and the device compares the number before the determination with the number after the determination. If there is a difference between the two (if there is a decrease) (S607; Yes), it is determined that the device has been switched and the configuration of the device 102B subordinate to the own server has changed, and the process proceeds to S608. On the other hand, when it is determined that the above configuration has not been changed (S607; No), the process returns to S606.

  The connection management unit 202B transmits the connection target table 2011B after the record is deleted to the cloud server 300 (S609). The server management unit 302 of the cloud server 300 associates the connection target table 2011B after the record received from the edge server 200B is deleted with the connection target master table 3011 stored in the storage unit 301 and connects them. The connection target table 2011B included in the target master table 3011 is updated to the connection target table 2011B after the record is deleted (S610). Since the connection target table managed by the edge server and the connection target master table managed by the cloud server 300 are automatically updated even when the device is deleted due to the execution of the processing of S606 to S610, Devices in operation can be properly monitored and managed without bothering an administrator.

  Subsequently, processing in the case where the status information of the edge server 200C includes an abnormality will be described. In the following, the operation monitoring units 203A to 203C of the edge servers 200A to 200C monitor the operation state of the own server and update the status information as needed, and also receive the status information of the edge servers connected to each other It is assumed that the operation state of the edge server is monitored, and the other status information which is the status information and the own status information which is the status information of the own server are appropriately transmitted to the cloud server 300.

  The operation monitoring unit 203C of the edge server 200C determines whether the resource of the own server is operating normally, that is, whether or not an abnormality of the own server is detected (S611). For example, the operation monitoring unit 203C determines whether shutdown of its own server has been detected, and whether the usage rate of the cache memory exceeds 80% which is a threshold.

  If the operation monitoring unit 203C determines that an abnormality of its own server has been detected (S611; Yes), the server ID "S_C0001", identification information of the resource in which the abnormality has occurred (for example, identification information of cache memory "M0001"), Status information including information indicating the operating status (abnormality) of the resource (for example, alarm information indicating that the usage rate of the cache memory exceeds the threshold 80%) is transmitted to the cloud server 300 and the other edge server 200B. (S612).

  The server management unit 302 of the cloud server 300 writes the status information received from the edge server 200C in the connection target master table 3011 and updates the connection target master table 3011 (S613). For example, the server management unit 302 rewrites its own status information corresponding to the server ID of the server stored in the connection target master table 3011 into “ERROR” indicating that it is abnormal.

  After that, the server management unit 302 transmits a server switch instruction to switch all the monitoring targets 100C subordinate to the edge server 200C reported as abnormal to subordinate to the edge server 200B to the edge server 200B as a switch destination (S614). The server switch instruction includes the connection target table 2011C of the edge server 200C for which an abnormality has been reported. The connection target table 2011C may extract the server ID from the connection target master table 3011 as a key.

  When the operation monitoring unit 203B of the edge server 200B receives the server switch instruction from the management server 300, the operation monitoring unit 203B causes the connection management unit 202B to perform acquisition processing for confirming measurement information of a device switched under the edge server 200B. An instruction to execute is output (S615), and the connection management unit 202B detects a device whose radio wave intensity is equal to or higher than the switch threshold as in the case of S602, and whether a new device is switched under the edge server 200B. It is determined whether or not (S616). In the determination, for example, the connection management unit 202B detects a device whose radio wave intensity is the switch threshold or more, and the number of devices whose radio wave intensity is the switch threshold or more before the determination and the number after the determination By comparison, if there is a difference between the two (if there is an increase) (S 616; Yes), it is determined that the device is switched and the configuration of the device 102 B subordinate to the own server has changed, and the process proceeds to S 617. On the other hand, when it is determined that the above configuration has not been changed (S616; No), the process returns to S615.

  The connection management unit 202B refers to the connection target table 2011B, and updates the measurement information corresponding to the same monitoring target ID as the monitoring target ID included in the measurement information received from the switched device 102C to the received measurement information. (S617).

  For example, for a device whose radio field strength with the device 102C attached to the monitoring target ID “T_C0001” is greater than or equal to the switch threshold, the connection management unit 202B causes the device to be under the edge server 200C or under the edge server 200B. And the connection target table 2011C is added and updated in the connection target table 2011B.

  The connection management unit 202B transmits the updated connection target table 2011B to the cloud server 300 (S618). The server management unit 302 of the cloud server 300 associates the updated connection target table 2011B received from the edge server 200B with the connection target master table 3011 stored in the storage unit 301, and generates a connection target master table The connection target table 2011B included in the table 3011 is rewritten to the connection target table 2011B after the update (S619).

  After executing the process of S612, the server management unit 202C of the edge server 200C in which the abnormality is detected reports that the maintenance worker terminal T registered in advance has an abnormality (S620). After that, the maintenance staff who has received the notification rushes to the site, confirms the abnormality, and executes necessary measures such as server restart and disk restoration.

  As described above, by executing the processing of S611 to S619, the edge server is automatically changed even when the device is changed and the connection destination edge server is changed due to the occurrence of an abnormality in the edge server. Since the connection target table managed by and the connection target master table managed by the cloud server 300 are updated, it is possible to correctly monitor and manage the devices at the time of operation without bothering the administrator. Further, when an abnormality occurs, the maintenance worker terminal T registered in advance is notified that an abnormality has occurred, so that it is possible to take necessary measures for the abnormality promptly.

  When an abnormality occurs in the edge server 200C, a device whose radio wave intensity is equal to or higher than the switch threshold is targeted for server switch instruction as in S602, but a device whose radio wave intensity is determined to be less than the threshold is an edge server It may be determined that it should not be a device under 200 B, and a report may be output indicating that the device is an error device.

  Further, in the above-described example, the acquisition processing for confirming measurement information of the device switched under the edge server 200B is executed according to the server switch instruction. However, in S612, the edge server 200C transmits the connection target table 2011C to the edge server 200B together with the status information, and the connection management unit 202B of the edge server 200B includes the device 102C stored in the received connection target table 2011C. The above acquisition process may be executed. In this case, there is no need to go through the cloud server 300, so it is possible to switch edge servers that manage devices more quickly.

  As described above, in this system, an edge server to be an optimum connection destination is automatically determined as a device connection switch management function. For example, based on the field intensity, the edge server of the connection destination is determined according to the field intensity of the device. When device A is moved (changed from monitoring target B to monitoring target A), the connection destination is changed from edge server 200B to edge server 200A with edge server 200A receiving radio wave of device A as a new connection destination (switch) And connect automatically. The device information to be connected may be stored in the edge server by transmitting the connection target master table 3011 of the device in the cloud server 300 to each edge server. In this case, device information can also be shared between edge servers, which enables high-speed and accurate switch connection.

  Also, in the present system, as the operation monitoring function of edge servers, the edge servers communicate with each other to monitor the operation state. For example, when an abnormality occurs in the edge server 200C and stops, from the edge server 200B monitoring the edge server 200C, the abnormality of the edge server 200C to the cloud server 300, not only to the other edge servers 200B but also to the site maintenance staff Real-time maintenance in the field is realized by notifying. Also, if the edge server 200B can receive the radio wave of the device C that has been connected to the edge server 200C, the edge server 200B reconnects and takes over the measurement processing and the like (performs the above-described switch connection). The matching of the measurement data of the device B in the edge servers 200B and 200C is performed on the cloud server 300 side. Therefore, it is possible to prevent the data measurement failure and the data dropout which occur when the device changes the connection destination (switch) of the edge server, and to reduce the risk of the monitoring failure.

  In addition, when the voltage value of the device is included in the measurement information, the load of the wireless communication between the edge server and the device is suppressed by determining whether the voltage value of the device is equal to or more than a certain threshold. It is also good. For example, when the connection management unit 202 of the edge server 200 determines that the voltage value of the device is not equal to or higher than a certain threshold value, it determines that the use frequency of the device is low or the possibility of being not used is high. The instruction to the device may be transmitted so as to reduce the frequency of transmitting the measurement information received from the device. In this case, it is possible to reduce the load of wireless communication from the device which is not likely to be used usually to the edge server.

  Further, in the present embodiment, when an abnormality occurs in the edge server 200C, the device 102C under the edge server 200C is automatically switched to the edge server 200B closest to the edge server 200C. However, if there is a large number of devices 102B subordinate to the edge server 200B, or if the measurement information of the devices is frequently acquired, or if the processing load of the edge server 200B or the load of wireless communication is high, the edge server 200B is abnormal. It is also conceivable that Therefore, instead of automatically switching the device to the edge server closest to the edge server where the abnormality has occurred as described above, the device is switched in consideration of the processing load of the edge server to be switched and the load of wireless communication. You may

  For example, consider a case where there are 10 devices 102A subordinate to the edge server 200A, 20 devices 102B subordinate to the edge server 200B, and 10 devices 102C subordinate to the edge server 200C, and an abnormality occurs in the edge server 20C. In this case, when the edge server 200B closest to the edge server 200C automatically switches the devices 102C subordinate to the edge server 200C, the total number of devices subordinate to the edge server 200B is 30, and the above processing is compared to the edge server 200A. It is considered that the load and the load of wireless communication will increase.

  Therefore, the server management unit 302 of the cloud server 300 determines that there is an abnormality in the edge server 200C by referring to the status information received from each edge server among the edge servers managed in the entire system, and the abnormality is Check the number of devices under the edge server 200B closest to the edge server 200C that occurred and the number of devices under the edge server 200A next to it, and the processing load and wireless communication load do not concentrate on any of the edge servers In this way, determine the edge server of the switch destination and distribute the switch destination.

  As a method of the dispersion, for example, since edge servers capable of stable wireless communication can be different due to difference (strong or weak) of radio wave strength, an edge with a stronger radio wave strength among devices under the edge server 200C A device under control of the server 200A and a device having a weak radio wave intensity is a device under control of the edge server 200B close in distance.

  Further, the edge server to be the switch destination may be determined according to the frequency of the measurement information transmitted from the device side, not the processing load of the edge server side or the load of wireless communication as described above. For example, among the devices 102C under the edge server 200C, the server management unit 302 of the cloud server 300 transmits the measurement information to the edge server for devices whose transmission frequency of measurement information is equal to or more than a certain number per unit time. Since there is a possibility of increasing the load, by defining an edge server with few managed devices as the edge server of the switch destination, the load of wireless communication on the edge server side with the increase of the transmission frequency of the device side It can be leveled per server.

1000 device management system 100 monitoring target 101 monitoring device 102 device 200 edge server 201 storage unit 2011 connection target table 202 connection management unit 203 operation monitoring unit 204 wireless communication unit 205 communication unit 300 cloud server 301 storage unit 3011 connection target master table 3012 server Management table 302 Server management unit 303 Communication unit N1-N3 Network (wireless communication)
N4-N6 network.

Claims (10)

A device management system comprising: a plurality of edge servers for monitoring a monitoring target having a device; and a management server for managing the plurality of edge servers,
Each of the plurality of edge servers is
Based on past measurement information and current measurement information received from the monitoring target via wireless communication, it is determined whether another device under the edge server has been switched to its own server, and the other edge When it is determined that the device under the server is switched to the own server, the connection target table for managing the device under the own server is updated, and the connection management unit for transmitting the updated connection target table to the management server is provided. ,
The management server is
A server management unit that updates the connection target master table based on the updated connection target table received from the edge server and a connection target master table that manages devices under the plurality of edge servers;
A device management system comprising: Each of the plurality of edge servers is
Other status information indicating the operating status of the other edge server received from the other edge server while monitoring the operating status of the own server and notifying the other edge server of its own status information indicating the operating status Operation monitoring unit to determine whether there is an abnormality in the
The connection management unit, when it is determined that the other status information is abnormal, the connection target table under the other edge server received with the other status information, and the connection target table under the own server Update the connection target table under the own server based on
The device management system according to claim 1, characterized in that: The operation monitoring unit of the edge server transmits the own status information or the other status information to the management server.
The server management unit of the management server determines, based on the own status information or the other status information received from the edge server, whether or not an abnormality is derived in the edge server, and causes the edge server to fail. If it is determined that is occurring, an edge server to be a switch destination is determined based on the processing load of the plurality of edge servers or the wireless communication load on the edge server side,
The device management system according to claim 2, characterized in that: The server management unit of the management server determines the edge server to be a switch destination according to the frequency of the measurement information transmitted from the device.
The device management system according to claim 2, characterized in that: The connection management unit of the edge server determines whether or not the voltage value of the device is equal to or higher than a certain threshold, and if it is determined that the voltage value of the device is not equal to or higher than a certain threshold, transmission of the measurement information Send instructions to the device to reduce the frequency
The device management system according to claim 1, characterized in that: Each of a plurality of edge servers monitoring a monitoring target having a device
Based on past measurement information and current measurement information received from the monitoring target via wireless communication, it is determined whether another device under the edge server has been switched to the own server or not.
If it is determined that another device under the edge server is switched to the own server, the connection target table for managing the device under the own server is updated,
Sending the updated connection target table to the management server;
A management server that manages the plurality of edge servers is
The connection target master table is updated based on the updated connection target table received from the edge server and a connection target master table that manages devices under the plurality of edge servers.
A device management method comprising: Each of the plurality of edge servers is
Other status information indicating the operating status of the other edge server received from the other edge server while monitoring the operating status of the own server and notifying the other edge server of its own status information indicating the operating status To determine if there is an abnormality in
If it is determined that the other status information is abnormal, the self connection target table based on the other connection target table under the other edge server and the connection target table under the self server received together with the other status information Update the connection target table under the server,
The device management method according to claim 6, characterized in that: The edge server transmits the own status information or the other status information to the management server.
The management server determines, based on the own status information or the other status information received from the edge server, whether or not an abnormality is derived in the edge server,
When it is determined that an abnormality has occurred in the edge server, an edge server to be switched is determined based on the processing load of the plurality of edge servers or the wireless communication load on the edge server side.
The device management method according to claim 7, characterized in that: The management server determines the edge server to be a switch destination according to the frequency of the measurement information transmitted from the device.
The device management method according to claim 7, characterized in that: When the edge server determines whether or not the voltage value of the device is equal to or greater than a certain threshold, and determines that the voltage value of the device is not greater than a certain threshold, the frequency of transmitting the measurement information is reduced. Send instructions to the device
The device management method according to claim 6, characterized in that:

Images