Monitoring control server, monitoring control system, monitoring control method, and monitoring control program

The supervisory control server optimizes data storage by managing resources for existing and future devices, releasing space when needed and restoring data strategically, addressing storage reduction and reboot needs in supervisory control systems.

JP2024158337AInactive Publication Date: 2024-11-08MITSUBISHI ELECTRIC CORP
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2023073464
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-04-27
Publication Date
2024-11-08
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

The existing supervisory control systems face a challenge where updating data requires additional storage space, leading to a reduction in available data storage during system operation.

Method used

The supervisory control server manages data by storing information on existing and future devices, monitors storage area resources, and releases storage space for future data when resources are insufficient, restoring it when resources become available, prioritizing data that does not require rebooting.

Benefits of technology

This approach effectively suppresses the decrease in data storage capacity during system operation, reduces the need for reboots, and minimizes disruptions by managing resource utilization efficiently.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024158337000001_ABST
    Figure 2024158337000001_ABST
Patent Text Reader

Abstract

To obtain a monitoring control server capable of suppressing a decrease in the data amount of storable data during system operation.SOLUTION: A server 1A comprises: a storage unit 50A for storing existing apparatus data 40X which is data on an existing apparatus including the apparatus itself that has been already connected, and future apparatus data 41X which is data on a future apparatus to be connected to the existing apparatus in the future; a monitoring unit 21A for monitoring resources of a storage area of the storage unit 50A; and an event processing unit 22A for releasing a future data storage area which is an area in the storage areas where the future apparatus data 41X has been stored, if the monitoring unit 21A determines that there is a shortage of resources. If the monitoring unit 21A determines that the shortage of resources has been resolved after the future data storage area is released, the storage unit 50A restores the future apparatus data 41X by storing the future apparatus data 41X transmitted from an external apparatus.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present disclosure relates to a monitoring and control server, a monitoring and control system, a monitoring and control method, and a monitoring and control program that monitor the status of resources. [Background technology]

[0002] One type of distributed system is a supervisory control system that operates while monitoring the status of resources. When the configuration of this supervisory control system is changed, it is necessary to update the data of the component devices that make up the supervisory control system.

[0003] In the system described in Patent Document 1, storage areas for data of component devices are pre-disposed in the component devices that make up the system, and when data of a component device is updated, the updated data is broadcast to the storage areas. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Publication No. 6-318956 Summary of the Invention [Problem to be solved by the invention]

[0005] However, with the technology of Patent Document 1 mentioned above, the storage area for storing update data puts pressure on the data storage area, limiting the data storage area available during system operation and reducing the amount of data that can be stored during system operation.

[0006] The present disclosure has been made in consideration of the above, and aims to provide a monitoring control server that can prevent a reduction in the amount of data that can be stored during system operation. [Means for solving the problem]

[0007] In order to solve the above-mentioned problems and achieve the object, the monitoring control server of the present disclosure includes a storage unit that stores existing device data, which is data of existing devices already connected including the server itself, and future device data, which is data of future devices that are to be connected to the existing devices in the future. The monitoring control server of the present disclosure also includes a monitoring unit that monitors the resources of the storage area of ​​the storage unit, and an event processing unit that releases a future data storage area, which is an area of ​​the storage area that has stored the future device data, when the monitoring unit determines that there is a resource shortage. After the future data storage area is released, when the monitoring unit determines that the resource shortage has been resolved, the storage unit restores the future device data by storing the future device data transmitted from the external device. Effect of the Invention

[0008] The monitoring and control server according to the present disclosure has an effect of preventing a reduction in the amount of data that can be stored during system operation. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram showing a configuration of a monitoring and control system according to an embodiment. [Diagram 2] FIG. 1 is a diagram for explaining a process executed in a monitoring and control system according to an embodiment when resources are exhausted in the monitoring and control system; [Diagram 3] 1 is a flowchart showing a procedure of a process executed by a server in which resources are depleted when resources are depleted in a monitoring and control system according to an embodiment; [Figure 4] 1 is a flowchart showing a procedure for processing a process executed by a server whose resources are not depleted when resources are depleted in a monitoring and control system according to an embodiment; [Diagram 5] FIG. 1 is a diagram for explaining a process executed in a monitoring and control system when a resource is restored in the monitoring and control system according to an embodiment; [Figure 6]1 is a flowchart showing a procedure of a process executed by a server whose resource has been restored when the resource is restored in the monitoring and control system according to the embodiment; [Figure 7] 1 is a flowchart showing a procedure of a process executed by a server whose resources are not exhausted when resources are restored in the monitoring and control system according to the embodiment; [Figure 8] FIG. 1 is a diagram for explaining a process executed in a monitoring and control system when a server is added to the monitoring and control system according to an embodiment; [Figure 9] 1 is a flowchart showing a procedure of a process executed by a server when the server is added to the monitoring and control system according to the embodiment; [Figure 10] 1 is a flowchart showing a procedure of a process executed by a representative existing device of a server when a server is added to a monitoring and control system according to an embodiment; [Figure 11] 1 is a flowchart showing a procedure of a process executed by a non-representative existing device of a server when a server is added to a monitoring and control system according to an embodiment; [Figure 12] FIG. 1 is a diagram illustrating a configuration example of a processing circuit included in a server according to an embodiment when the processing circuit is realized by a processor and a memory; [Figure 13] FIG. 1 is a diagram illustrating an example of a processing circuit in a case where the processing circuit of the server according to the embodiment is realized by dedicated hardware; DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS A monitoring and control server, a monitoring and control system, a monitoring and control method, and a monitoring and control program according to embodiments of the present disclosure will be described below in detail with reference to the accompanying drawings.

[0011] Embodiment FIG. 1 is a diagram showing a configuration of a monitoring control system according to an embodiment. The monitoring control system 5 is a distributed system equipped with a plurality of servers. FIG. 1 shows a case where the monitoring control system 5 is equipped with servers 1A and 1B. A server other than the servers 1A and 1B (a server 1C described below) can be added to the monitoring control system 5. In the first embodiment, a case will be described where the monitoring control system 5 operates using the servers 1A and 1B, and then the server 1C is added and the monitoring control system 5 operates using the servers 1A to 1C.

[0012] In the monitoring and control system 5, the servers 1A and 1B store data of the server 1C that is scheduled to be connected (installed) to the servers 1A and 1B in the future (future device data 41X, described later) in an invalid state, and when the server 1C is connected, the future device data 41X is enabled.

[0013] When the server 1C is not connected and the remaining resource capacity of one of the servers 1A, 1B falls below a first threshold, the server releases the storage area for the future device data 41X, and when the remaining resource capacity reaches or exceeds a second threshold, the server obtains and stores a copy of the future device data 41X from the other server, thereby restoring the future device data 41X.

[0014] The servers 1A to 1C are monitoring control servers that operate while monitoring the states of resources. Since the servers 1A to 1C have the same configuration, the configuration of the server 1A will be described here.

[0015] The server 1A includes a configuration management unit 10A that manages the configuration of the server 1A, and a storage unit 50A that stores various data. The storage unit 50A stores resource information 30A, existing device data 40X, and future device data 41X.

[0016] The resource information 30A is information on the resources of the server 1A. The resource information 30A includes information on the memory capacity and hardware capacity required to operate the software, hardware, firmware, etc. used by the server 1A. The resource information 30A includes information on the resource capacity in use and information on the unused resource capacity.

[0017] The existing device data 40X is data of a server (existing device) connected to the monitoring and control system 5 and operating within the monitoring and control system 5. In other words, the existing device data 40X is data of existing devices that have already been installed (connected), including the device itself. The existing device data 40X here is data of the servers 1A, 1B operating within the monitoring and control system 5. The servers 1A, 1B use the existing device data 40X to perform data transmission and reception between the servers 1A, 1B, etc.

[0018] The future device data 41X is data of a server (future device) that will be subsequently connected to the monitoring control system 5 and operate within the monitoring control system 5. The future device data 41X here is data of the server 1C that will operate within the monitoring control system 5. The future device data 41X is disabled until the server 1C is connected to the monitoring control system 5, and is enabled when the server 1C is connected to the monitoring control system 5.

[0019] The types of data included in the future device data 41X are, for example, system definition data that defines the configuration of the monitoring and control system 5 when the server 1C is added, station definition data that defines the configuration of a station (server 1C) included in the monitoring and control system 5, and item definition data that defines items related to the server 1C. The system definition data is data that defines the devices that make up the monitoring and control system 5. The station definition data is data that defines the configuration of a station that performs monitoring and control, and the item definition data is data that defines specific monitoring items (such as values ​​obtained from sensors installed on-site). While it is difficult to continue operating the monitoring and control system 5 without the system definition data, it is possible to continue operating the monitoring and control system 5 even if the station definition data and item definition data are absent, as the monitoring and control will simply stop functioning.

[0020] When the monitoring control system 5 is connected to the server 1C, the server 1C becomes an existing device instead of a future device. That is, when the monitoring control system 5 is connected to the server 1C, the future device data 41X becomes the existing device data of the servers 1A to 1C and is included in the existing device data 40X.

[0021] After the monitoring control system 5 is connected to the server 1C, the servers 1A and 1B operate using the existing device data 40X including the data of the servers 1A to 1C. For example, the server 1A uses the latest existing device data 40X to transmit and receive data between the servers 1B and 1C. The server 1C also has data similar to the latest existing device data 40X, and after the server 1C is connected to the monitoring control system 5, it uses the latest existing device data 40X to transmit and receive data between the servers 1A and 1B.

[0022] The configuration management section 10A includes a resource management section 11A, a warning management section 12A, a status management section 13A, a communication management section 14A, and a data management section 15A. The resource management section 11A manages resource information 30A indicating the resources of the server 1A.

[0023] The resource management unit 11A includes a monitoring unit 21A and an event processing unit 22A. The monitoring unit 21A monitors the resource information 30A stored in the storage unit 50A. When the remaining capacity of the resource indicated by the resource information 30A becomes equal to or less than a first threshold, the monitoring unit 21A sends a deletion request notification to the event processing unit 22A to request the deletion of the future device data 41X since the resource is exhausted. In addition, when the remaining capacity of the resource indicated by the resource information 30A becomes equal to or more than a second threshold (≧first threshold) after the future device data 41X is deleted, the monitoring unit 21A determines that the shortage of the resource has been resolved, and sends a restoration request notification to the event processing unit 22A to request the restoration of the resource.

[0024] When the event processing unit 22A receives the deletion request notification, it deletes the future device data 41X from the storage unit 50A and releases the data storage area in which the future device data 41X was stored. That is, when the event processing unit 22A receives the deletion request notification, it releases the data storage area (future data storage area) in which the future device data 41X was stored in the storage area of ​​the storage unit 50A. As a result, the data storage area in which the future device data 41X was stored becomes available as a resource when the server 1A operates. After this, the server 1A becomes able to store any data in the data storage area in which the future device data 41X was stored.

[0025] The event processing unit 22A may delete only a part of the future device data 41X. In this case, a part (the area from which the data has been deleted) of the data storage area (storage area) in which the future device data 41X was stored becomes available as a resource when the server 1A operates.

[0026] For the servers 1A and 1B to continue the operation of the monitoring and control system 5 without rebooting, the system definition data included in the resource information 30A is essential. That is, the servers 1A and 1B must be rebooted when restoring the system definition data and using it for the first time. On the other hand, the servers 1A and 1B do not need to be rebooted when using station definition data and item definition data for the first time.

[0027] To reduce the number of reboots, the servers 1A and 1B preferentially delete station definition data and item definition data that do not require rebooting. When the resource shortage is resolved and the station definition data and item definition data are restored, the servers 1A and 1B can use the station definition data and item definition data without rebooting. This allows the servers 1A and 1B to continue operating without rebooting.

[0028] In this way, when the future device data 41X includes system definition data, station definition data, and item definition data, the event processing unit 22A deletes the station definition data and the item definition data first. That is, the event processing unit 22A preferentially releases the data storage area in which the data (first data) that does not require rebooting after the future device data 41X is restored from the future device data 41X is stored, over the data storage area in which the data (second data) that requires rebooting after the future device data 41X is restored from the future device data 41X is stored. This allows the server 1A to restore the station definition data and the item definition data without rebooting.

[0029] The event processing unit 22A selects data to be deleted according to the remaining capacity of resources. For example, if there is a shortage of resources even after deleting the item definition data, the event processing unit 22A deletes the station definition data. Also, for example, if there is a shortage of resources even after deleting the item definition data and the station definition data, the event processing unit 22A deletes the system definition data.

[0030] Furthermore, when the event processing unit 22A deletes the future device data 41X, it sends a deletion completion notification indicating that the future device data 41X has been deleted to the warning management unit 12A, the state management unit 13A, and the communication management unit 14A.

[0031] Furthermore, when the event processing unit 22A receives the revival request notification, it sends this revival request notification to the warning management unit 12A, the state management unit 13A, and the communication management unit 14A. Note that the event processing unit 22A may send a revival completion notification indicating that the revival has been completed to the warning management unit 12A and the state management unit 13A after a copy of the future device data 41X is sent from the server 1B and stored in the storage unit 50A.

[0032] When the warning management unit 12A receives a deletion completion notification from the event processing unit 22A, it warns the user that a resource shortage (resource exhaustion) has occurred and that the future device data 41X has been deleted. The warning management unit 12A warns the user, for example, by displaying a warning on a display device. Furthermore, when the warning management unit 12A receives a restoration request notification or a restoration completion notification from the event processing unit 22A, it notifies the user that the resource shortage has been resolved.

[0033] The state management unit 13A manages the state of the storage unit 50A etc. When the future device data 41X is stored in the storage unit 50A, the state management unit 13A stores that the storage unit 50A is in a state where the future device data 41X is stored.

[0034] Furthermore, when the state management unit 13A receives a deletion completion notification from the event processing unit 22A, it stores that the future device data 41X in the storage unit 50A is in a deleted state. Furthermore, when the state management unit 13A receives a restoration request notification or a restoration completion notification from the event processing unit 22A, it stores that the storage unit 50A is in a state storing the future device data 41X.

[0035] The communication management unit 14A manages communications with another server (here, server 1B). When server 1C is connected to the monitoring control system 5, the communication management unit 14A manages communications with servers 1B and 1C.

[0036] When the communications management unit 14A receives a deletion completion notification from the event processing unit 22A, it transmits the deletion completion notification to the server 1B. Furthermore, when the communications management unit 14A receives a restoration request notification from the event processing unit 22A, it transmits the restoration request notification to the server 1B. Furthermore, when the communications management unit 14A receives a restoration completion notification from the event processing unit 22A, it may transmit the restoration completion notification to the server 1B.

[0037] In addition, when the communications management unit 14A receives a notification from the newly connected server 1C indicating that server 1C has been added to the monitoring and control system 5 (a device addition notification designating server 1C), the communications management unit 14A sends the device addition notification designating server 1C to server 1B and the data management unit 15A.

[0038] When the data management unit 15A receives the device addition notification that the server 1C is specified, the data management unit 15A validates the future device data 41X in the storage unit 50A. As a result, the future device data 41X in the storage unit 50A is included in the existing device data 40X.

[0039] Server 1B has the same components as server 1A. That is, server 1B has a configuration management unit 10B similar to configuration management unit 10A, and a storage unit 50B similar to storage unit 50A. Storage unit 50B stores resource information 30B, existing device data 40X, and future device data 41X. While resource information 30A is information on resources of server 1A, resource information 30B is information on resources of server 1B.

[0040] The configuration management unit 10B has the same components as the configuration management unit 10A. That is, the configuration management unit 10B has a resource management unit 11B similar to the resource management unit 11A, a warning management unit 12B similar to the warning management unit 12A, a status management unit 13B similar to the status management unit 13A, a communication management unit 14B similar to the communication management unit 14A, and a data management unit 15B similar to the data management unit 15A. The resource management unit 11B manages resource information 30B indicating the resources of the server 1B.

[0041] The resource manager 11B includes the same components as the resource manager 11A. That is, the resource manager 11B includes a monitor 21B similar to the monitor 21A, and an event processor 22B similar to the event processor 22A.

[0042] In the monitoring and control system 5, the servers 1A and 1B are existing devices, and the server 1C is a future device that will be connected to the existing devices in the future. In the following explanation, the server 1A is a representative device (representative existing device) among the existing devices, and the server 1B is another device (non-representative device) among the existing devices.

[0043] In the monitoring and control system 5, when server 1C, which is a future device, is added to the monitoring and control system 5, server 1C transmits a device addition notification to server 1A, which is a representative existing device. Upon receiving the device addition notification, server 1A, which is the representative existing device, transmits a device addition notification to a server (server 1B in FIG. 1) which is a non-representative device (non-representative existing device) among the existing devices.

[0044] In addition, in the monitoring control system 5, the server 1B may be a representative existing device. In this case, the server 1A becomes a non-representative existing device. After the server 1C is added to the monitoring control system 5, the server 1C becomes an existing device. In this state, if there is another future device, the servers 1A to 1C store the future device data 41X of the other future device.

[0045] Next, the operation of the servers 1A and 1B when resources are depleted in the server 1A of the monitoring and control system 5 will be described. FIG. 2 is a diagram for explaining the processing executed in the monitoring and control system according to the embodiment when resources are depleted. FIG. 3 is a flowchart showing the processing procedure executed by the server whose resources are depleted when resources are depleted in the monitoring and control system according to the embodiment. Note that in FIG. 2, the data management units 15A and 15B are not shown.

[0046] Here, a case will be described in which the server whose resources are depleted is server 1A and the server whose resources are not depleted is server 1B. In server 1A, monitor 21A monitors the resources of its own device (server 1A) based on resource information 30A (steps S10, st1). Based on resource information 30A, monitor 21A determines whether or not a resource shortage occurs in server 1A (step S20).

[0047] If no resource shortage occurs in the server 1A (step S20, No), the monitoring unit 21A continues the process of monitoring the resources of its own device based on the resource information 30A (step S10, st1).

[0048] When a resource shortage occurs in the server 1A (step S20, Yes), the monitoring unit 21A notifies the event processing unit 22A that the resource is depleted (step S30, st2). That is, when the remaining capacity of the resource indicated by the resource information 30A becomes equal to or less than the first threshold, the monitoring unit 21A sends a deletion request notification to the event processing unit 22A.

[0049] When the event processing unit 22A receives the deletion request notification, it deletes the future device data 41X from the storage unit 50A (step S40, st3). This releases the data storage area in which the future device data 41X was stored.

[0050] Moreover, when the event processing unit 22A deletes the future device data 41X, it notifies the warning management unit 12A that the future device data 41X has been deleted (step S50, st4). That is, when the event processing unit 22A deletes the future device data 41X, it sends a deletion completion notification indicating that the future device data 41X has been deleted to the warning management unit 12A. When the warning management unit 12A receives the deletion completion notification from the event processing unit 22A, it notifies the user of resource shortage (step S60).

[0051] Furthermore, when the event processing unit 22A deletes the future device data 41X, it notifies the state management unit 13A that the future device data 41X has been deleted (step S70, st5). That is, when the event processing unit 22A deletes the future device data 41X, it sends a deletion completion notification indicating that the future device data 41X has been deleted to the state management unit 13A. When the state management unit 13A receives the deletion completion notification from the event processing unit 22A, it stores that the future device data 41X in the storage unit 50A has been deleted.

[0052] In addition, when the event processing unit 22A deletes the future device data 41X, it notifies the communication management unit 14A that the future device data 41X has been deleted (step S80, st6). That is, when the event processing unit 22A deletes the future device data 41X, it sends a deletion completion notification indicating that the future device data 41X has been deleted to the communication management unit 14A.

[0053] When the communication management unit 14A receives the deletion completion notification from the event processing unit 22A, it notifies other devices (devices whose resources are not exhausted) that a resource shortage has occurred and the resources have been released (step S90). That is, when the communication management unit 14A receives the deletion completion notification from the event processing unit 22A, it transmits a deletion completion notification indicating that the future device data 41X has been deleted from the storage unit 50A to the server 1B (st7).

[0054] Any of the processes of steps S50, S70, and S80 may be executed first. Furthermore, the process of step S60 may be executed at any timing after the process of step S50. Furthermore, the process of step S90 may be executed at any timing after the process of step S80.

[0055] In addition, when the state management unit 13A stores that the future device data 41X has been deleted in the server 1B, the event processing unit 22A does not delete the future device data 41X. That is, in the monitoring control system 5, the state in which any server stores the future device data 41X is maintained, and the future device data 41X is prevented from being deleted from all servers.

[0056] In addition, when resources are exhausted, the event processing unit 22A may save the future device data 41X to a recording medium such as a CD (Compact Disc), a DVD (Digital Versatile Disc), a USB (Universal Serial Bus) memory, etc. In other words, when resources are exhausted, the event processing unit 22A may read the future device data 41X from the storage unit 50A and store it in a recording medium, and delete the future device data 41X from the storage unit 50A.

[0057] FIG. 4 is a flowchart of a process performed by a server whose resources are not depleted when resources are depleted in the monitoring control system according to the embodiment.

[0058] The communication management unit 14B of the server 1B receives a deletion completion notification from another device (the server 1A whose resources have been exhausted) (step S110). The communication management unit 14B notifies the state management unit 13B of the deletion completion notification (step S120, st8). As a result, the state management unit 13B stores that the future device data 41X of the server 1A has been deleted.

[0059] Next, the operation of the servers 1A and 1B when resources are restored (resource shortage is resolved) in the server 1A of the monitoring and control system 5 will be described. FIG. 5 is a diagram for explaining the processing executed in the monitoring and control system when resources are restored in the monitoring and control system according to the embodiment. FIG. 6 is a flowchart showing the processing procedure of the processing executed by the server whose resources have been restored when resources are restored in the monitoring and control system according to the embodiment. Note that data management units 15A and 15B are not shown in FIG. 5.

[0060] Here, a case will be described in which the server whose resource has been restored is server 1A, and the server whose resource has not been exhausted or restored is server 1B. In server 1A, monitoring unit 21A monitors the resource of its own device (server 1A) based on resource information 30A (steps S210, st11). Based on resource information 30A, monitoring unit 21A judges whether the resource has been restored in server 1A (step S220). When more data than future device data 41X can be stored in the resource, monitoring unit 21A judges that the resource has been restored.

[0061] If the resource has not been restored in the server 1A (step S220, No), the monitoring unit 21A continues the process of monitoring the resource of its own device based on the resource information 30A (step S210, st11).

[0062] If the resource is restored in the server 1A (step S220, Yes), the monitoring unit 21A notifies the event processing unit 22A that the resource has been restored (step S230, st12). That is, when the remaining capacity of the resource indicated by the resource information 30A becomes equal to or greater than the second threshold, the monitoring unit 21A sends a restoration request notification to the event processing unit 22A to request restoration of the future device data 41X.

[0063] When the event processing unit 22A receives the revival request notification, it notifies the warning management unit 12A that the future device data 41X is in a state where it can be revived (step S240, st13). Note that the event processing unit 22A may send a revival completion notification indicating that the revival of the future device data 41X has been completed to the warning management unit 12A after the memory unit 50A stores the future device data 41X.

[0064] When the warning management unit 12A receives a restoration request notification or a restoration completion notification from the event processing unit 22A, it notifies the user of resource restoration (step S250). That is, when the event processing unit 22A receives a restoration request notification, it sends a notification to the warning management unit 12A indicating that the server 1A has enough resources to restore the device data 41X in the future, or indicating that restoration has been completed.

[0065] Furthermore, when the event processing unit 22A receives the revival request notification, it notifies the state management unit 13A that the future device data 41X is in a state in which it can be revived (step S260, st14). That is, when the event processing unit 22A receives the revival request notification, it sends the revival request notification to the state management unit 13A. Note that the event processing unit 22A may send a revival completion notification indicating that the revival of the future device data 41X has been completed to the state management unit 13A after the memory unit 50A stores the future device data 41X.

[0066] When the state management unit 13A receives a revival request notification or a revival completion notification from the event processing unit 22A, it stores the fact that the future device data 41X is stored in the storage unit 50A.

[0067] Furthermore, upon receiving the revival request notification, the event processing unit 22A notifies the communication management unit 14A that the future device data 41X is in a state in which it can be revived (step S270, st15). That is, upon receiving the revival request notification, the event processing unit 22A sends the revival request notification to the communication management unit 14A.

[0068] When the communication management unit 14A receives the restoration request notification, it notifies other devices (devices whose resources have not been exhausted) that the future device data 41X is in a state in which it can be restored (step S280, st16).

[0069] Any of the processes of steps S240, S260, and S270 may be executed first. Furthermore, the process of step S250 may be executed at any timing after the process of step S240. Furthermore, the process of step S280 may be executed at any timing after the process of step S270.

[0070] If the future device data 41X has been saved to a recording medium when resources are exhausted, the event processing unit 22A acquires the future device data 41X from the recording medium and stores it in the storage unit 50A.

[0071] FIG. 7 is a flowchart of a process performed by a server whose resources are not depleted when resources are restored in the monitoring and control system according to the embodiment.

[0072] The communication management unit 14B of the server 1B receives a revival request notification from the resource depletion occurrence device (the server 1A that has been revived after the resource depletion) (step S310). The communication management unit 14B notifies the state management unit 13B of the revival request notification for reviving the future device data 41X (step S320, st17).

[0073] The state management unit 13B notifies the event processing unit 22B of a restoration request notification for restoring the future device data 41X to the server 1A (step S330, st18). The event processing unit 22B reads out the copy data of the future device data 41X from the storage unit 50B (st19).

[0074] The event processing unit 22B writes copy data of the future device data 41X to the storage unit 50A of the server 1A. That is, the event processing unit 22B copies the future device data 41X in its own device (server 1B) to the server 1A, which is the device where resource depletion has occurred (steps S340, st20).

[0075] After that, the state management unit 13B stores that the future device data 41X of the server 1A has been restored. That is, the state management unit 13B stores that the server 1A is in a state in which the future device data 41X has been stored. Note that the state management unit 13B may store that the server 1A is in a state in which the future device data 41X has been stored at any timing after receiving the restoration request notification.

[0076] The event processing unit 22B of the server 1B may provide copy data of the future device data 41X to the event processing unit 22A of the server 1A. In this case, the event processing unit 22A of the server 1A stores the future device data 41X in the storage unit 50A.

[0077] After storing the future device data 41X in the storage unit 50A, the server 1A can reboot at any timing. The server 1A executes rebooting at a timing according to the system to which the monitoring control system 5 is applied. The date and time of rebooting in this case may be set by the user or may be set in advance in the server 1A. The server 1A may also acquire various information from the system to which the monitoring control system 5 is applied and determine the date and time of rebooting based on the acquired information. For example, when the monitoring control system 5 is applied to a train operation system, the server 1A may determine the date and time of rebooting based on operation information (operation information) in the operation system. In this case, the server 1A sets the date and time of rebooting to a date and time that does not affect train operation, maintenance work, or business. Since the server 1A can reboot at any timing, the number of times that the operation of the monitoring control system 5 is affected can be reduced. In addition, when the future device data 41X is station definition data and item definition data, rebooting is not necessary.

[0078] Next, the operation of the servers 1A to 1C when a new server (future device) server 1C is added to the monitoring and control system 5 will be described. Fig. 8 is a diagram for explaining the processing executed in the monitoring and control system when a server is added to the monitoring and control system according to the embodiment. Fig. 9 is a flowchart showing the processing procedure of the processing executed by the added server when a server is added to the monitoring and control system according to the embodiment.

[0079] Here, a case will be described in which the server to be added to the monitoring control system 5 is the server 1C, the representative existing device of the server is the server 1A, and the non-representative existing device of the server is the server 1B.

[0080] Server 1C has the same components as servers 1A and 1B. That is, server 1C has a configuration management unit 10C similar to configuration management unit 10A, and a storage unit 50C similar to storage unit 50A. Storage unit 50C stores resource information (not shown), existing device data 40X, and host device data 41Y. Server 1A stores resource information 30A of server 1A, while server 1C stores resource information of server 1C. Host device data 41Y is the same data as future device data 41X.

[0081] The configuration management unit 10C has the same components as the configuration management unit 10A. That is, the configuration management unit 10C has a resource management unit (not shown) similar to the resource management unit 11A, a warning management unit (not shown) similar to the warning management unit 12A, a status management unit 13C similar to the status management unit 13A, a communication management unit 14C similar to the communication management unit 14A, and a data management unit (not shown) similar to the data management unit 15A. In Fig. 8, only some of the components of the servers 1A to 1C are shown.

[0082] When the server 1C is connected to the monitoring and control system 5 in a state in which the servers 1A and 1B are connected to the monitoring and control system 5 as existing devices, the status management unit 13C of the server 1C notifies the communication management unit 14C that the startup preparation of the server 1C is complete. That is, the status management unit 13C notifies the communication management unit 14C that the system startup preparation is complete (steps S410, st21).

[0083] The communication management unit 14C of the server 1C notifies the communication management unit 14A of the server 1A, which is the representative existing device, that the startup preparation of the server 1C is completed (step S420). That is, the communication management unit 14C transmits a startup preparation completion notification of the server 1C to the communication management unit 14A (st22).

[0084] After that, the server 1C waits for a notification (activation completion notification) indicating that the activation of the future device data 41X has been completed from the server 1A, which is the representative existing device (step S430). The server 1C judges whether or not the activation completion notification has been received (step S440). If the activation completion notification has not been received (step S440, No), the server 1C waits for the activation completion notification (step S430).

[0085] When the activation completion notification is received (step S440, Yes), the communication management unit 14C of the server 1C receives the activation completion notification and notifies the status management unit 13C that the activation of the future device data 41X is completed (step S450, st32). As a result, the status management unit 13C starts up the system of the server 1C (step S460).

[0086] FIG. 10 is a flowchart of a process performed by a representative existing device of a server when the server is added to the monitoring and control system according to the embodiment.

[0087] In the server 1A, which is the representative existing device, the communication management unit 14A receives a device addition notification from the server 1C (step S510). That is, the communication management unit 14A receives a device addition notification, which is a notification indicating that the server 1C has been added to the monitoring control system 5, from the communication management unit 14C of the server 1C.

[0088] The communication management unit 14A notifies the communication management unit 14B of the server 1B, which is a non-representative existing device, that the server 1C has been added to the monitoring control system 5 (step S520, st23). In addition, the communication management unit 14A notifies the data management unit 15A that the server 1C has been added to the monitoring control system 5 (step S530, st24).

[0089] The data management unit 15A validates the future device data 41X in the storage unit 50A (step S540, st25). The data management unit 15A notifies the communication management unit 14A of the completion of validation of the future device data 41X (information indicating that validation has been completed) (step S550, st26).

[0090] Note that the process of step S520 and the process of step S530 may be executed first, and the process of step S540 may be executed at any timing after the process of step S530. Furthermore, the process of step S550 may be executed at any timing after the process of step S540.

[0091] After notifying the non-representative existing device that the server 1C has been added to the monitoring control system 5, the communication management unit 14A waits for a notification of completion of activation from the non-representative existing device (step S560). That is, the communication management unit 14A waits for a notification indicating that activation of the future device data 41X has been completed from the communication management unit 14B of the server 1B, which is another existing device.

[0092] The server 1A judges whether or not the activation completion notification has been received (step S570). If the activation completion notification has not been received (step S570, No), the server 1A waits for the activation completion notification (step S560).

[0093] If a notification of completion of activation is received (step S570, Yes), the communication management unit 14A of the server 1A notifies the communication management unit 14C of the server 1C, which is the added device, that activation of the future device data 41X has been completed in all existing devices (step S580, st31).

[0094] The communication management unit 14A does not notify the communication management unit 14C of the completion of the validation of the future device data 41X until the communication management unit 14A receives the completion of the validation of the future device data 41X from the data management unit 15A.

[0095] That is, when the communication management unit 14A receives notification of completion of the validation of the future device data 41X from both the data management unit 15A and the communication management unit 14B, it notifies the communication management unit 14C that the validation of the future device data 41X has been completed for all existing devices.

[0096] FIG. 11 is a flowchart of a process procedure executed by a non-representative existing device of a server when the server is added to the monitoring and control system according to the embodiment.

[0097] In the server 1B, which is the non-representative existing device, the communication management unit 14B receives the device addition notification from the communication management unit 14A of the server 1A, which is the representative existing device (step S610). The device addition notification that the communication management unit 14B receives from the communication management unit 14A is a notification indicating that the server 1C has been added to the monitoring control system 5.

[0098] The communication management unit 14B notifies the data management unit 15B that the server 1C has been added to the monitoring control system 5 (steps S620, st27).

[0099] The data management unit 15B validates the future device data 41X in the storage unit 50B (step S630, st28). The data management unit 15B notifies the communication management unit 14B of the completion of validation of the future device data 41X (step S640, st29).

[0100] The communications management unit 14B notifies the communications management unit 14A of the server 1A, which is the representative existing device, of the completion of the activation (steps S650, st30). As a result, the server 1A notifies the server 1C of the completion of the activation, and the server 1C starts up the system.

[0101] It is possible to add a fourth or subsequent server to the monitoring and control system 5. In the case where N servers (N is a natural number) are to be added to the monitoring and control system 5 to which the servers 1A and 1B are connected, the servers 1A and 1B store the future device data 41X for N servers and the existing device data 40X for two servers. In the monitoring and control system 5 to which the servers 1A to 1C are connected, the servers 1A to 1C store the future device data 41X for (N-1) servers and the existing device data 40X for three servers.

[0102] Here, the hardware configuration of the servers 1A to 1C will be described. Since the servers 1A to 1C have the same hardware configuration, the hardware configuration of the server 1A will be described here. The server 1A is realized by a processing circuit. The processing circuit may be a processor and memory that executes a program stored in a memory, or may be dedicated hardware.

[0103] FIG. 12 is a diagram showing a configuration example of a processing circuit when the processing circuit included in the server according to the embodiment is realized by a processor and a memory. The processing circuit 90 shown in FIG. 12 includes a processor 91 and a memory 92. When the processing circuit 90 is configured with the processor 91 and the memory 92, each function of the processing circuit 90 is realized by software, firmware, or a combination of software and firmware. The software or firmware is described as a monitoring control program of data and stored in the memory 92. In the processing circuit 90, each function is realized by the processor 91 reading and executing the monitoring control program stored in the memory 92. That is, the processing circuit 90 includes a memory 92 for storing a monitoring control program that results in the processing of the server 1A being executed. This monitoring control program can also be said to be a program for causing the server 1A to execute each function realized by the processing circuit 90. This monitoring control program may be provided by a storage medium in which the monitoring control program is stored, or may be provided by other means such as a communication medium.

[0104] The above-mentioned monitoring and control program has a modular configuration including a configuration management section 10A, and these are loaded onto the main storage device and generated on the main storage device.

[0105] Here, the processor 91 is, for example, a CPU (Central Processing Unit), a processing device, an arithmetic device, a microprocessor, a microcomputer, or a DSP (Digital Signal Processor), etc. Also, the memory 92 is, for example, a non-volatile or volatile semiconductor memory such as a RAM (Random Access Memory), a ROM (Read Only Memory), a flash memory, an EPROM (Erasable Programmable ROM), or an EEPROM (Electrically EPROM), a magnetic disk, a flexible disk, an optical disk, a compact disk, a mini disk, or a DVD.

[0106] Fig. 13 is a diagram showing an example of a processing circuit provided in a server according to an embodiment, which is realized by dedicated hardware. The processing circuit 93 shown in Fig. 13 corresponds to, for example, a single circuit, a composite circuit, a programmed processor, a parallel programmed processor, an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or a combination of these. The processing circuit 93 may be partially realized by dedicated hardware and partially realized by software or firmware. In this way, the processing circuit 93 can realize each of the above-mentioned functions by dedicated hardware, software, firmware, or a combination of these.

[0107] In this way, when the server 1A of the embodiment judges that there is a resource shortage, it releases the area in the storage area of ​​the storage unit 50A in which the future device data 41X was stored. Then, when the server 1A judges that the resource shortage has been resolved, it restores the future device data 41X by storing the future device data 41X transmitted from the server 1B, which is an external device, in the storage unit 50A. This allows the server 1A to prevent the amount of data that can be saved during system operation from decreasing.

[0108] In addition, the server 1A preferentially deletes data that does not require rebooting from among the future device data 41X, so that the number of reboots can be reduced. In addition, after the server 1A saves the future device data 41X in the storage unit 50A, the server 1A can reboot at any timing, so that the number of times that the operation of the monitoring and control system 5 is affected can be reduced.

[0109] The configurations shown in the above embodiments are merely examples, and may be combined with other known technologies. Parts of the configurations may be omitted or modified without departing from the spirit of the invention.

[0110] Various aspects of the present disclosure are summarized below as appendices.

[0111] (Appendix 1) a storage unit that stores existing device data, which is data on existing devices already connected including the device itself, and future device data, which is data on future devices to be connected to the existing devices in the future; a monitoring unit that monitors resources of a storage area of ​​the storage unit; an event processing unit that releases a future data storage area, which is an area of ​​the storage area in which the future device data has been stored, when the monitoring unit determines that the resource is insufficient; Equipped with When the monitoring unit determines that the resource shortage has been resolved after the future data storage area is released, the storage unit restores the future device data by storing the future device data transmitted from an external device. A monitoring and control server comprising: (Appendix 2) When the monitoring unit determines that the resources are insufficient, the event processing unit preferentially releases a future data storage area in which a first data item among the future device data that does not require rebooting after the future device data is restored is stored, over a future data storage area in which a second data item among the future device data that requires rebooting after the future device data is restored is stored. 2. The monitoring and control server according to claim 1 . (Appendix 3) when the monitoring unit determines that the remaining capacity of the resource is equal to or less than a first threshold, the event processing unit releases the future data storage area; When the monitoring unit determines that the remaining capacity of the resource is equal to or greater than a second threshold, the future device data is restored; The second threshold is equal to or greater than the first threshold. 3. The monitoring and control server according to claim 1 or 2. (Appendix 4) the event processing unit transmits the future device data to another device, when a notification indicating that the resource shortage has been resolved is received from another device other than the device itself among the existing devices. 4. The monitoring and control server according to claim 1, (Appendix 5) and a data management unit that, when receiving a notification from the future device indicating that the future device is connected to the existing device, enables the future device stored in the storage unit, and stores the enabled future device in the storage unit as the existing device data. 5. The monitoring and control server according to claim 1, (Appendix 6) a first monitoring control server and a second monitoring control server which are existing devices already connected including the device itself; a third monitoring and control server which is a future device to be connected to the existing device in the future; having The first monitoring control server includes: A storage unit that stores existing device data that is data of the existing device and future device data that is data of the future device; a monitoring unit that monitors resources of a storage area of ​​the storage unit; an event processing unit that releases a future data storage area, which is an area of ​​the storage area in which the future device data has been stored, when the monitoring unit determines that the resource is insufficient; Equipped with When the monitoring unit determines that the resource shortage has been resolved after the future data storage area is released, the storage unit restores the future device data by storing the future device data transmitted from the second monitoring control server. A monitoring and control system comprising: (Appendix 7) a monitoring step in which the monitoring and control server monitors resources of a storage area of ​​a storage unit that stores existing device data, which is data of existing devices already connected including the monitoring and control server itself, and future device data, which is data of future devices to be connected to the existing devices in the future; an event processing step of releasing a future data storage area, which is an area in the storage area where the future device data has been stored, when the monitoring control server determines that the resource is insufficient; Including, when the monitoring control server determines that the resource shortage has been resolved after releasing the future data storage area, the future device data transmitted from the external device is stored in the storage unit, thereby restoring the future device data. A monitoring and control method comprising: (Appendix 8) a monitoring step of monitoring resources of a storage area of ​​a storage unit that stores existing device data, which is data of existing devices already connected including the device itself, and future device data, which is data of future devices to be connected to the existing devices in the future; an event processing step of releasing a future data storage area, which is an area of ​​the storage area in which the future device data has been stored, when it is determined that the resource is insufficient; on the computer, when it is determined that the resource shortage has been resolved after the future data storage area is released, the future device data transmitted from the external device is stored in the storage unit to restore the future device data; A monitoring and control program comprising: [Explanation of symbols]

[0112] 1A to 1C servers, 5 monitoring and control system, 10A to 10C configuration management section, 11A, 11B resource management section, 12A, 12B warning management section, 13A to 13C status management section, 14A to 14C communication management section, 15A, 15B data management section, 21A, 21B monitoring section, 22A, 22B event processing section, 30A, 30B resource information, 40X existing device data, 41X future device data, 41Y own device data, 50A to 50C memory section, 90, 93 processing circuit, 91 processor, 92 memory.

Claims

1. a storage unit that stores existing device data, which is data on existing devices already connected including the device itself, and future device data, which is data on future devices to be connected to the existing devices in the future; a monitoring unit that monitors resources of a storage area of ​​the storage unit; an event processing unit that releases a future data storage area, which is an area of ​​the storage area in which the future device data has been stored, when the monitoring unit determines that the resource is insufficient; Equipped with When the monitoring unit determines that the resource shortage has been resolved after the future data storage area is released, the storage unit restores the future device data by storing the future device data transmitted from an external device. A monitoring and control server comprising:

2. When the monitoring unit determines that the resources are insufficient, the event processing unit preferentially releases a future data storage area in which a first data item among the future device data that does not require rebooting after the future device data is restored is stored over a future data storage area in which a second data item among the future device data that requires rebooting after the future device data is restored is stored.

2. The monitor and control server according to claim 1.

3. when the monitoring unit determines that the remaining capacity of the resource is equal to or less than a first threshold, the event processing unit releases the future data storage area; When the monitoring unit determines that the remaining capacity of the resource is equal to or greater than a second threshold, the future device data is restored; The second threshold is equal to or greater than the first threshold.

2. The monitor and control server according to claim 1.

4. the event processing unit transmits the future device data to another device, when a notification indicating that the resource shortage has been resolved is received from another device other than the device itself among the existing devices.

2. The monitor and control server according to claim 1.

5. and a data management unit that, when receiving a notification from the future device indicating that the future device is connected to the existing device, enables the future device stored in the storage unit, and stores the enabled future device in the storage unit as the existing device data.

5. The monitor and control server according to claim 1, wherein the monitor and control server is a server that is connected to the network.

6. a first monitoring control server and a second monitoring control server which are existing devices already connected including the device itself; a third monitoring and control server which is a future device to be connected to the existing device in the future; having The first monitoring control server A storage unit that stores existing device data that is data of the existing device and future device data that is data of the future device; a monitoring unit that monitors resources of a storage area of ​​the storage unit; an event processing unit that releases a future data storage area, which is an area of ​​the storage area in which the future device data has been stored, when the monitoring unit determines that the resource is insufficient; Equipped with When the monitoring unit determines that the resource shortage has been resolved after the future data storage area is released, the storage unit restores the future device data by storing the future device data transmitted from the second monitoring control server. A monitoring and control system comprising:

7. a monitoring step in which the monitoring and control server monitors resources of a storage area of ​​a storage unit that stores existing device data, which is data of existing devices already connected including the monitoring and control server itself, and future device data, which is data of future devices to be connected to the existing devices in the future; an event processing step of releasing a future data storage area, which is an area in the storage area where the future device data has been stored, when the monitoring control server determines that the resource is insufficient; Including, when the monitoring control server determines that the resource shortage has been resolved after releasing the future data storage area, the future device data transmitted from the external device is stored in the storage unit, thereby restoring the future device data. A monitoring and control method comprising:

8. a monitoring step of monitoring resources of a storage area of ​​a storage unit that stores existing device data, which is data of existing devices already connected including the device itself, and future device data, which is data of future devices to be connected to the existing devices in the future; an event processing step of releasing a future data storage area, which is an area of ​​the storage area in which the future device data has been stored, when it is determined that the resource is insufficient; on the computer, when it is determined that the resource shortage has been resolved after the future data storage area is released, the future device data transmitted from the external device is stored in the storage unit to restore the future device data; A monitoring and control program comprising:

Citation Information

Patent Citations

  • Data update method for packet switching network

    JP1994318956A