Unified monitoring method and system for file interaction links of power grid dispatching automation system

Abstract

The invention discloses a unified monitoring method and system for file interaction links of a power grid dispatching automation system, and the method relates to information collection of file interaction links between systems and in the systems, verification of interaction files at a link source end and a link destination end, abnormal alarm and diagnosis analysis of the interaction links and visual display of the interaction links. The method aims at comprehensively monitoring the file interaction link state of the power grid dispatching automation system, expanding the operation and maintenance range of the automation system and guaranteeing efficient and stable operation of the power grid dispatching automation system.

Description

Technical Field

[0001] The present invention relates to an automatic monitoring method for electric power dispatching files, and in particular to a unified monitoring method and system for file interaction links of an electric power grid dispatching automation system. Background Art

[0002] In the power grid dispatching automation system, many businesses frequently interact with each other through files to achieve data transmission, command issuance, and information sharing. File interaction has become one of the main ways of business interaction within the system and between systems. With the continuous expansion of the scale of dispatching automation systems and the increasing degree of intelligence, the accuracy, timeliness, and stability of file interaction are also increasingly required. However, the existing file interaction link monitoring method has many shortcomings. On the one hand, there is a lack of unified monitoring and management of the interaction links within and between systems, and it is impossible to fully grasp the overall situation of file interaction, and it is easy to ignore the interaction link failure problem, which affects the business; on the other hand, when the link is abnormal, it is impossible to issue an early warning in time, and it is difficult to locate the problem, resulting in low troubleshooting efficiency, which seriously affects the efficient and stable operation of the power grid dispatching automation system. In addition, the existing manual inspection method cannot ensure that the interaction files at the source and destination ends of the link are completely consistent, which affects the accuracy and integrity of the data.

[0003] Therefore, there is an urgent need for an innovative unified monitoring method for file interaction links to achieve real-time perception of the status of file interaction links within and between systems and to quickly discover link anomalies. Summary of the invention

[0004] Purpose of the invention: In view of the above problems, the present invention proposes a unified monitoring method and system for file interaction links in a power grid dispatching automation system, which can collect the interactive file information of the source and destination ends of the link in real time, automatically perform consistency verification of the files at both ends, and issue early warnings for link anomalies, thereby realizing comprehensive, real-time and efficient monitoring of file interaction links.

[0005] Technical solution: The technical solution adopted by the present invention is a unified monitoring method for file interaction links of a power grid dispatching automation system, comprising the following steps:

[0006] Step 1: Collect the file information exchanged between the source and destination ends of the link in real time;

[0007] Step 2: Receive the interactive file information of each link in real time, verify the consistency of the interactive files at both ends of the link, record the verification result information, and issue an alarm for abnormal links.

[0008] The method also includes step three: displaying the file interaction links between the business modules in the power grid dispatching automation system in a visual manner.

[0009] The real-time collection of file information exchanged between the source and destination ends of the link includes: data collection based on the actual locations of the files at both ends of the interactive link; the scheduling automation system is physically divided into a production control area and a management information area, and the file information of the production control area is transmitted to the management information area through a cross-isolation device for unified analysis.

[0010] The real-time collection of file information interacting between the source and destination ends of the link also includes: extracting all files that the node needs to monitor based on the file template, periodically obtaining the file size, file update time, file access rights, file md5 value, file dynamic timestamp, file digital signature and the current time of this node; the production control area node data is transmitted to the gateway program via JSON-RPC, and the gateway program crosses the isolation device via TCP and is finally sent to the unified monitoring server.

[0011] Verifying the consistency of the exchange files at both ends of the link includes the following steps:

[0012] (1) After the file data is preprocessed, verification begins for each interactive link;

[0013] (2) Check whether the source file exists. If not, record the verification information that the source file has not been generated and go to step (1);

[0014] (3) Check the source file size. If the source file size is equal to 0, record the verification information that the source is an empty file and go to step (1).

[0015] (4) Check the source file time. If there is a data jump between the source file time and the source machine time, record the unreliable verification information of the source file and go to step (1);

[0016] (5) Check the source file access rights. If the source file access rights are unreasonable, record the verification information of the abnormal source file permissions and go to step (1);

[0017] (6) Temporarily record the source file md5 value;

[0018] (7) Generate a dynamic timestamp for the source file based on the current time and a random number to obtain the dynamic timestamp of the source file;

[0019] (8) Use the private key to digitally sign the source file content, source hash value, and source dynamic timestamp to generate signature information;

[0020] (9) Check whether the destination file exists. If not, record the verification information that the destination file has not been generated and go to step (1);

[0021] (10) Check the size of the destination file. If the size is equal to 0, record the verification information that the destination file is an empty file and go to step (1).

[0022] (11) Check the destination file time. If there is a data jump between the destination file time and the destination machine time, record the verification information that the destination file is unreliable and go to step (1);

[0023] (12) Check the target file update frequency. If it does not meet expectations, record verification information of the target file update anomaly and go to step (1);

[0024] (13) Temporarily record the md5 value of the destination file;

[0025] (14) Compare the md5 value of the source file with the md5 value of the destination file to see if they are the same. If they are not the same, record the information that the destination file is inconsistent with the source file and go to step (1);

[0026] (15) Generate a dynamic timestamp for the destination file to obtain the dynamic timestamp of the destination file;

[0027] (16) Compare the dynamic timestamp of the destination file with the dynamic timestamp of the source file. If the timestamp difference exceeds a preset threshold, record the verification information of the timestamp anomaly and go to step (1).

[0028] (17) Use the public key of the source end to verify the signature information. If the verification fails, record the verification information of the digital signature verification failure and go to step (1);

[0029] (18) Query the verification record information. If the record information is empty, the link status is recorded as normal. If the record information is not empty, the link status is recorded as faulty and a link abnormality alarm is issued.

[0030] (19) Go to step (1);

[0031] (20) Complete the consistency check of all interactive link files and end.

[0032] The present invention proposes a unified monitoring system for file interaction links of a power grid dispatching automation system, including an information collection module and a centralized monitoring module;

[0033] The information collection module is used to collect the interactive file information between the link source and the destination in real time;

[0034] The centralized monitoring module is used to: receive the interactive file information of each link in real time, verify the consistency of the interactive files at both ends of the link, record the verification result information, and issue an alarm for abnormal links.

[0035] The centralized monitoring module also includes a file interaction link visualization module, which is used to display the file interaction links between the business modules in the power grid dispatching automation system in a visualized manner.

[0036] The present invention proposes a computer device, comprising a memory, a processor and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the method for uniformly monitoring file interaction links of a power grid dispatching automation system is implemented.

[0037] The present invention provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the method for uniformly monitoring file interaction links of a power grid dispatching automation system is implemented.

[0038] The present invention provides a computer program product, including a computer program and / or instructions. When the computer program and / or instructions are executed by a processor, the method for uniformly monitoring file interaction links of a power grid dispatching automation system is implemented.

[0039] Beneficial effects: Compared with the prior art, the present invention has the following advantages: Through unified monitoring of the file interaction links within the dispatching automation system and between systems, the present invention can more comprehensively and in real time grasp the operating status of the file interaction links, promptly discover link interaction anomalies, and intuitively display the link status in a visual manner, which is convenient for users to monitor and manage in real time, greatly improves work efficiency and convenience, and effectively ensures the efficient and stable operation of the power grid dispatching automation system. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] Figure 1 It is a flow chart of the unified monitoring method of file interaction link of the power grid dispatching automation system according to the present invention;

[0041] Figure 2 The file verification process between the source end and the destination end of the file interaction link described in the present invention;

[0042] Figure 3 It is a visual display of the unified monitoring system of the file interaction link of the power grid dispatching automation system described in the present invention;

[0043] Figure 4 Provides a visual display of scheduling plan link anomalies. DETAILED DESCRIPTION

[0044] The technical solution of the present invention is further described below in conjunction with the accompanying drawings and embodiments.

[0045] Example 1

[0046] The method for unified monitoring of file interaction links in a power grid dispatching automation system of the present invention is shown in the flowchart as follows: Figure 1As shown, the following steps are included:

[0047] Step 1: Real-time collection of file information exchanged between the link source and destination.

[0048] The power grid dispatching automation system is physically divided into the production control area (hereinafter referred to as Area I) and the management information area (hereinafter referred to as Area III). Logically, it includes the dispatching system, control cloud, power market, network-province vertical, provincial-regional vertical, network-plant vertical and other subsystems. Data is collected according to the actual location of the files at both ends of the interactive link. The file information in Area I is transmitted to Area III through cross-isolation devices for unified analysis.

[0049] Deploy the file information collection program on the nodes where the link source and destination are located and configure the file template. The file template includes the directory where the file is located, the file prefix, the file suffix, the time rule paradigm in the middle of the file, the file generation cycle, the peer communication address, etc. The collection program extracts all the files that need to be monitored by this node based on the file template, and periodically obtains the file size, file update time, file md5 value and the current time of this node. The node data in zone I is transmitted to the gateway program via JSON-RPC. The gateway program crosses the isolation device via TCP and is finally sent to the unified monitoring server.

[0050] Deploy the collection program nusp-fileagent on the source and destination nodes of each link, configure the file template information, and add the file path, file prefix, file suffix, file time rule paradigm, file generation method (periodic generation), and file generation cycle in the template.

[0051] The nusp-fileagent program scans files in a specific directory every minute, starting with a file prefix and ending with a file suffix, with a regular time pattern in between, to obtain the file size, file access rights, update time and md5 value, file dynamic timestamp and digital signature information. The message digest algorithm md5 is a widely used cryptographic hash function that can generate a 128-bit hash value to ensure the integrity and consistency of information transmission.

[0052] Step 2: Receive the interactive file information of each link in real time, verify the consistency of the interactive files at both ends of the link, record the verification result information, and issue an alarm for abnormal links.

[0053] Modeling of intra-system and inter-system interactive links is performed on the unified monitoring server. Model information includes basic link information, source end service name, destination end service name, link interactive file paradigm, file generation method, etc. Data preprocessing is performed on all received file data and associated with the link model to form complete information of the interactive link. Consistency check is performed on the files at both ends of the link. The file size, update time, md5 value, dynamic timestamp and digital signature of the files at both ends of the file interactive link are checked, and detailed verification results are recorded.

[0054] In the unified monitoring module, firstly, each link to be monitored is modeled and the source and destination information of the link is recorded. Secondly, after receiving the message data, the receiving service program parses the data and associates it with the model to obtain the complete data information of the link. Figure 2 The process performs consistency check on the source file and the destination file data of the link, checks whether the file size, time and md5 value are correct, obtains the interactive link status and records the verification record. Finally, for abnormal interactive links file-link, query the verification record information, for example, if the source file is not generated, then push the file-link link abnormality (source file is not generated) alarm. Specifically, it includes the following steps:

[0055] a) Initialize interactive link data. After file data preprocessing, start verification for each interactive link;

[0056] b) Check whether the source file exists. If not, record the verification information "source file not generated" and go to step a);

[0057] c) Check the source file size. If the size is equal to 0, record the verification information "the source file is an empty file" and go to step a);

[0058] d) Check the source file time, compare the time with the source machine time, and if there is a data jump, record the "source file is unreliable" verification information; go to step a);

[0059] e) Check the source file access permissions. If the permissions are unreasonable, record the "source file permissions are abnormal" verification information; go to step a);

[0060] f) Temporarily record the md5 value of the source file, recorded as sourceMd5;

[0061] g) Temporarily generate a dynamic timestamp for the source file, recorded as sourceTimeStamp;

[0062] h) Use the private key to digitally sign the source file content, source hash value, and source dynamic timestamp to generate signature information;

[0063] i) Check whether the destination file exists. If not, record the verification information "destination file not generated" and go to step a);

[0064] j) Check the size of the destination file. If the size is equal to 0, record the verification information "the destination file is an empty file" and go to step a);

[0065] k) Check the destination file time, compare the time with the destination machine time, and record the verification information "destination file is unreliable" if there is a data jump; go to step a);

[0066] l) Check the target file update frequency, if it does not meet expectations, record the "target file update abnormality" verification information; go to step a);

[0067] m) Temporarily record the md5 value of the destination file, recorded as targetMd5;

[0068] n) Compare targetMd5 and sourceMd5 to see if they are the same. If they are not the same, record the message "the target end and the source end files are inconsistent" and go to step a);

[0069] o) Generate a dynamic timestamp for the destination file, denoted as targetTimestamp;

[0070] p) Compare targetTimestamp with sourceTimestamp. If the timestamp difference is too large (exceeds the preset threshold), record the "timestamp anomaly" verification information; go to step a);

[0071] q) Use the public key of the source to verify the signature information. If the verification fails, record the verification information of "digital signature verification failed"; go to step a);

[0072] r) If the recorded information is empty, the link status is recorded as normal; if it is not empty, the link status is recorded as faulty and a link abnormality alarm is issued;

[0073] s) Go to step a);

[0074] t) Complete the consistency check of all interactive link files and end.

[0075] As a preferred solution, the method further comprises:

[0076] Step 3: Visualize the link status. Visualize the file interaction links between business modules in the power grid dispatching automation system.

[0077] Build the file interaction link topology within and between systems, and display the link status in a topological visualization way. The interactive connection line uses red and green colors to indicate whether the link is abnormal. For abnormal links, the link details are displayed in the form of cards, including the source node, source file directory, destination node, destination file directory, and abnormal reason.

[0078] Example 2

[0079] In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the above-mentioned unified monitoring method for file interaction links of a power grid dispatching automation system when executing the computer program.

[0080] Example 3

[0081] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the above-mentioned unified monitoring method for file interaction links of a power grid dispatching automation system is implemented.

[0082] Example 4

[0083] In one embodiment, a computer program product is provided, including a computer program / instruction, which, when executed by a processor, implements the method for uniformly monitoring file interaction links in a power grid dispatching automation system.

[0084] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0085] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0086] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0087] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0088] Example 5

[0089] The file interaction link unified monitoring system of the power grid dispatching automation system of the present invention comprises an information collection module and a centralized monitoring module;

[0090] Information collection module, used to collect the interactive file information between the link source and destination in real time;

[0091] The centralized monitoring module is used to: receive the interactive file information of each link in real time, verify the consistency of the interactive files at both ends of the link, record the verification result information, and issue an alarm for abnormal links.

[0092] The centralized monitoring module also includes a file interaction link visualization module, which is used to display the file interaction links between the business modules in the power grid dispatching automation system in a visualized manner.

[0093] like Figure 3 As shown in the figure, all links in the system are intuitively displayed through topology, cards and other visual methods, so that the operating status of the internal / external interactive links in the system can be intuitively grasped. For abnormal links, the topology connection line turns red, flashes, and pops up a detail card, such as Figure 4 shown.

Claims

1. A unified monitoring method for file interaction links in a power grid dispatching automation system, characterized in that: The following steps are involved: Step 1: Collect the file information exchanged between the source and destination ends of the link in real time; Step 2: Receive the interactive file information of each link in real time, verify the consistency of the interactive files at both ends of the link, record the verification result information, and issue an alarm for abnormal links.

2. The method for unified monitoring of file interaction links in a power grid dispatching automation system according to claim 1, characterized in that: The method also includes step three: displaying the file interaction links between the business modules in the power grid dispatching automation system in a visual manner.

3. The method for unified monitoring of file interaction links in a power grid dispatching automation system according to claim 1, characterized in that: The real-time collection of file information exchanged between the source and destination ends of the link includes: data collection based on the actual locations of the files at both ends of the interactive link; the scheduling automation system is physically divided into a production control area and a management information area, and the file information of the production control area is transmitted to the management information area through a cross-isolation device for unified analysis.

4. The method for unified monitoring of file interaction links in a power grid dispatching automation system according to claim 2, characterized in that: The real-time collection of file information interacting between the source and destination ends of the link also includes: extracting all files that the node needs to monitor based on the file template, periodically obtaining the file size, file update time, file access rights, file md5 value, file dynamic timestamp, file digital signature and the current time of this node; the production control area node data is transmitted to the gateway program via JSON-RPC, and the gateway program crosses the isolation device via TCP and is finally sent to the unified monitoring server.

5. The method for unified monitoring of file interaction links in a power grid dispatching automation system according to claim 1, characterized in that: Verifying the consistency of the exchange files at both ends of the link includes the following steps: (1) After the file data is preprocessed, verification begins for each interactive link; (2) Check whether the source file exists. If not, record the verification information that the source file has not been generated and go to step (1); (3) Check the source file size. If the source file size is equal to 0, record the verification information that the source is an empty file and go to step (1). (4) Check the source file time. If there is a data jump between the source file time and the source machine time, record the unreliable verification information of the source file and go to step (1); (5) Check the source file access rights. If the source file access rights are unreasonable, record the verification information of the abnormal source file permissions and go to step (1); (6) Temporarily record the md5 value of the source file; (7) Generate a dynamic timestamp for the source file based on the current time and a random number to obtain the dynamic timestamp of the source file; (8) Use the private key to digitally sign the source file content, source hash value, and source dynamic timestamp to generate signature information; (9) Check whether the destination file exists. If not, record the verification information that the destination file has not been generated and go to step (1); (10) Check the size of the destination file. If the size is equal to 0, record the verification information that the destination file is an empty file and go to step (1). (11) Check the destination file time. If there is a data jump between the destination file time and the destination machine time, record the verification information that the destination file is unreliable and go to step (1); (12) Check the target file update frequency. If it does not meet expectations, record verification information of the target file update anomaly and go to step (1); (13) Temporarily record the md5 value of the destination file; (14) Compare the md5 value of the source file with the md5 value of the destination file to see if they are the same. If they are not the same, record the information that the destination file is inconsistent with the source file and go to step (1); (15) Generate a dynamic timestamp for the destination file to obtain the dynamic timestamp of the destination file; (16) Compare the dynamic timestamp of the destination file with the dynamic timestamp of the source file. If the timestamp difference exceeds a preset threshold, record the verification information of the timestamp anomaly and go to step (1). (17) Use the public key of the source end to verify the signature information. If the verification fails, record the verification information of the digital signature verification failure and go to step (1); (18) Query the verification record information. If the record information is empty, the link status is recorded as normal. If the record information is not empty, the link status is recorded as faulty and a link abnormality alarm is issued. (19) Go to step (1); (20) Complete the consistency check of all interactive link files and end.

6. A unified monitoring system for file interaction links in a power grid dispatching automation system, characterized in that: Including information collection module and centralized monitoring module; The information collection module is used to collect the interactive file information between the link source and the destination in real time; The centralized monitoring module is used to receive the interactive file information of each link in real time, verify the consistency of the interactive files at both ends of the link, record the verification result information, and issue an alarm for abnormal links.

7. The unified monitoring system for file interaction links of a power grid dispatching automation system according to claim 6 is characterized by: The centralized monitoring module also includes a file interaction link visualization module, which is used to display the file interaction links between the business modules in the power grid dispatching automation system in a visualized manner.

8. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the method for uniformly monitoring file interaction links of a power grid dispatching automation system according to any one of claims 1 to 5 is implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method for uniformly monitoring file interaction links of a power grid dispatching automation system according to any one of claims 1 to 5 is implemented.

10. A computer program product comprising a computer program and / or instructions, characterized in that: When the computer program and / or instruction is executed by a processor, the method for uniformly monitoring file interaction links of a power grid dispatching automation system according to any one of claims 1 to 5 is implemented.

Images