Power grid remote operation and maintenance processing method, device, computer equipment and storage medium

Abstract

The present application relates to a method, device, computer equipment, storage medium and computer program product for processing remote operation and maintenance of a power grid. The method includes: in response to a power grid remote operation and maintenance triggering event, performing a hash calculation based on a pre-stored high-risk device file to obtain a target feature code; the power grid remote operation and maintenance triggering event is used to instruct the target protection device to execute a remote operation and maintenance instruction to perform remote power grid operation and maintenance on the target protection device; obtaining the original feature code pre-stored for the pre-stored high-risk device file; when the target feature code is the same as the original feature code, performing a risk assessment on the target protection device based on the pre-stored high-risk device file to obtain an assessment result; when the assessment result indicates that the target protection device is at risk, blocking the remote operation and maintenance instruction for the target protection device and triggering an alarm prompt. The use of this method can improve the system security protection capability.

Description

Technical Field

[0001] The present application relates to the field of power grid network security technology, and in particular to a power grid remote operation and maintenance processing method, apparatus, computer equipment, storage medium and computer program product. Background Art

[0002] With the continuous improvement of the informationization and intelligence level of the power grid industry, higher requirements are being placed on the network security protection of the power monitoring system in the power grid. The power monitoring system includes a security system, which includes a security master station and security substations. Remote operation and maintenance of relay protection devices through the security master station can greatly improve the operation and maintenance efficiency of relay protection devices. Relay protection is a key task to ensure the safe and stable operation of the power system, so ensuring the safe operation of all aspects of relay protection is essential. Typically, the network security protection capabilities of the security system are improved through network boundary technologies (such as firewall technology and network gateway technology) to defend against network attacks outside the power grid and avoid threats to the power system.

[0003] However, network boundary technology can defend against network attacks on the main station of Baoxin from outside the power grid, but it cannot prevent network security incidents caused by internal personnel of the power grid modifying the risk level of relay protection equipment and performing remote operation and maintenance of high-risk equipment, which will affect the safe and stable operation of the power system. Summary of the Invention

[0004] Based on this, it is necessary to provide a power grid remote operation and maintenance processing method, device, computer equipment, computer-readable storage medium and computer program product that can improve the system security protection capability to address the above technical problems.

[0005] In a first aspect, the present application provides a method for remote operation and maintenance of a power grid. The method comprises:

[0006] In response to a power grid remote operation and maintenance triggering event, a target feature code is obtained by performing a hash calculation based on a pre-stored high-risk device file; the high-risk device file is generated based on a dynamic power grid risk file and a static baseline risk device file; the power grid remote operation and maintenance triggering event is used to instruct a target protection device to execute a remote operation and maintenance instruction to perform power grid remote operation and maintenance on the target protection device;

[0007] Obtaining a pre-stored original feature code for the pre-stored high-risk device file;

[0008] When the target feature code is identical to the original feature code, performing a risk assessment on the target protection device according to the pre-stored high-risk device file to obtain an assessment result;

[0009] When the evaluation result indicates that there is a risk to the target protection device, the remote operation and maintenance instruction for the target protection device is blocked and an alarm prompt is triggered.

[0010] In a second aspect, the present application also provides a power grid remote operation and maintenance processing device. The device includes:

[0011] a response module, configured to, in response to a power grid remote operation and maintenance triggering event, perform a hash calculation based on a pre-stored high-risk device file to obtain a target signature code; the high-risk device file is generated based on a dynamic power grid risk file and a static baseline risk device file; the power grid remote operation and maintenance triggering event is used to instruct a target protection device to execute a remote operation and maintenance instruction to perform power grid remote operation and maintenance on the target protection device;

[0012] an evaluation module configured to obtain an original feature code pre-stored for the pre-stored high-risk device file; and, if the target feature code is identical to the original feature code, perform a risk evaluation on the target protection device based on the pre-stored high-risk device file to obtain an evaluation result;

[0013] The blocking module is used to block the remote operation and maintenance instructions for the target protection device and trigger an alarm prompt when the evaluation result indicates that the target protection device is at risk.

[0014] In a third aspect, the present application further provides a computer device. The computer device includes a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are performed:

[0015] In response to a power grid remote operation and maintenance triggering event, a target feature code is obtained by performing a hash calculation based on a pre-stored high-risk device file; the high-risk device file is generated based on a dynamic power grid risk file and a static baseline risk device file; the power grid remote operation and maintenance triggering event is used to instruct a target protection device to execute a remote operation and maintenance instruction to perform power grid remote operation and maintenance on the target protection device;

[0016] Obtaining a pre-stored original feature code for the pre-stored high-risk device file;

[0017] When the target characteristic code is identical to the original characteristic code, performing a risk assessment on the target protection device according to the pre-stored high-risk device file to obtain an assessment result;

[0018] When the evaluation result indicates that there is a risk to the target protection device, the remote operation and maintenance instruction for the target protection device is blocked and an alarm prompt is triggered.

[0019] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the following steps:

[0020] In response to a power grid remote operation and maintenance triggering event, a target feature code is obtained by performing a hash calculation based on a pre-stored high-risk device file; the high-risk device file is generated based on a dynamic power grid risk file and a static baseline risk device file; the power grid remote operation and maintenance triggering event is used to instruct a target protection device to execute a remote operation and maintenance instruction to perform power grid remote operation and maintenance on the target protection device;

[0021] Obtaining a pre-stored original feature code for the pre-stored high-risk device file;

[0022] When the target feature code is identical to the original feature code, performing a risk assessment on the target protection device according to the pre-stored high-risk device file to obtain an assessment result;

[0023] When the evaluation result indicates that there is a risk to the target protection device, the remote operation and maintenance instruction for the target protection device is blocked and an alarm prompt is triggered.

[0024] In a fifth aspect, the present application further provides a computer program product. The computer program product includes a computer program that, when executed by a processor, implements the following steps:

[0025] In response to a power grid remote operation and maintenance triggering event, a target feature code is obtained by performing a hash calculation based on a pre-stored high-risk device file; the high-risk device file is generated based on a dynamic power grid risk file and a static baseline risk device file; the power grid remote operation and maintenance triggering event is used to instruct a target protection device to execute a remote operation and maintenance instruction to perform power grid remote operation and maintenance on the target protection device;

[0026] Obtaining a pre-stored original feature code for the pre-stored high-risk device file;

[0027] When the target feature code is identical to the original feature code, performing a risk assessment on the target protection device according to the pre-stored high-risk device file to obtain an assessment result;

[0028] When the evaluation result indicates that there is a risk to the target protection device, the remote operation and maintenance instruction for the target protection device is blocked and an alarm prompt is triggered.

[0029] The above-mentioned power grid remote operation and maintenance processing method, device, computer equipment, storage medium and computer program product can verify whether the high-risk device file has been tampered with by using the target feature code obtained by hash calculation and the pre-stored original feature code, thereby improving the security of the high-risk device file; moreover, the high-risk device file is generated through a dynamic power grid risk file and a static baseline risk device file. The risk assessment of the target protection device is performed based on the high-risk device file, and it can be identified whether the target protection device is at risk. When the target protection device is at risk, remote maintenance of the target protection device is prevented, which can avoid the internal power grid operation and maintenance personnel from performing remote operation and maintenance on the risky target protection device and posing a threat to the safe operation of the power grid, thereby improving the security protection capability of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] Figure 1 A diagram illustrating an application environment of a power grid remote operation and maintenance processing method in one embodiment;

[0031] Figure 2 1 is a flow chart of a method for remote operation and maintenance of a power grid according to an embodiment;

[0032] Figure 3 A flowchart of the steps of generating a high-risk device file in one embodiment is shown;

[0033] Figure 4 Schematic diagram of a flow chart of power grid remote operation and maintenance processing steps in one embodiment;

[0034] Figure 5 This is a structural block diagram of a power grid remote operation and maintenance processing device in one embodiment;

[0035] Figure 6 FIG. 1 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0036] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0037] The power grid remote operation and maintenance processing method provided in the embodiment of the present application can be applied to Figure 1In the application environment shown. Among them, the operation and maintenance terminal 102 can run the Baoxin master station client, the server 104 can run the Baoxin master station service end, the operation and maintenance terminal 102 communicates with the Baoxin master station service end running on the server 104 through the Baoxin master station client, and the target protection device 106 can communicate with the Baoxin master station service end running on the server 104. The data storage system can store the data that the server 104 needs to process. The data storage system can be integrated on the server 104, or it can be placed on the cloud or other servers. Among them, the operation and maintenance terminal 102 can be a desktop computer or a laptop computer. The server 104 can be implemented with an independent server or a server cluster composed of multiple servers. The target protection device 106 is a device for implementing relay protection in the power system. It can send an alarm signal when a fault occurs in the power system, or it can directly cut off the faulty protected transmission line or electrical component when a fault occurs in the power system to reduce the degree of damage to the power system by the faulty part. The target protection device 106 can be classified according to physical quantities or according to the protected objects, etc.; when classified according to physical quantities, the target protection device 106 can be a current protection device, a voltage protection device or a distance protection device, etc.; when classified according to the protected objects, the target protection device 106 can be a generator protection device, a transmission line protection device or a transformer protection device, etc.

[0038] Based on Figure 1 In the application environment shown, the Baoxin master station server running on the server 104 can respond to the power grid remote operation and maintenance trigger event triggered by the Baoxin master station client running on the operation and maintenance terminal 102, perform hash calculation based on the pre-stored high-risk device file, obtain the target feature code, and obtain the original feature code pre-stored for the high-risk device file. When the target feature code is the same as the original feature code, a risk assessment is performed on the target protection device 106 according to the high-risk device file to obtain an assessment result. When the assessment result indicates that the target protection device 106 is at risk, the remote operation and maintenance instructions for the target protection device 106 are blocked, and an alarm prompt is triggered.

[0039] In one embodiment, Figure 2 As shown, a method for remote operation and maintenance of a power grid is provided. In this embodiment, the method is applied to Figure 1 Taking the server 104 in FIG. 1 as an example, the method includes the following steps:

[0040] Step 202, in response to a power grid remote operation and maintenance triggering event, a hash calculation is performed based on a pre-stored high-risk device file to obtain a target feature code; the high-risk device file is generated based on a dynamic power grid risk file and a static baseline risk device file; the power grid remote operation and maintenance triggering event is used to instruct the target protection device to execute a remote operation and maintenance instruction to perform power grid remote operation and maintenance on the target protection device.

[0041] Among them, the power grid remote operation and maintenance trigger event is an event that triggers the remote operation and maintenance of the target protection device in the power grid. The power grid remote operation and maintenance trigger event can be an automatic trigger event, such as automatically triggering when a remote operation and maintenance instruction is sent to the target protection device at a preset time; it can also be a manual trigger operation, such as a mouse click or touch click operation on the remote operation and maintenance function key. The remote operation and maintenance instruction is a computer code executed by the target protection device to perform remote power grid operation and maintenance on the target protection device. Power grid remote operation and maintenance is the process of remote maintenance of the target protection device, such as remote modification of settings and remote upgrades, where the settings are the basis for the correct operation of the target protection device to achieve relay protection for the power system.

[0042] A high-risk device file records risk information for high-risk devices. This file can be a spreadsheet. A dynamic grid risk file is a dynamically changing data file related to risk information in the grid. A static baseline risk device file records baseline risk device information and remains unchanged over time.

[0043] Hash calculation is the process of converting information of long data length into information digest of short data length through a hash algorithm. Hash algorithms include MD5 (Message-Digest Algorithm 5) algorithm and SHA (Secure Hash Algorithm) algorithm. Performing hash calculation on a file using the MD5 algorithm can generate a 128-bit hash value, which is the original hash value; when the file is tampered with, the new hash value recalculated by the MD5 algorithm for the tampered file will be different from the original hash value, so the MD5 algorithm can be used to verify whether the file has been tampered with. The target signature is a signature obtained by performing hash calculation on a pre-stored high-risk device file; for example, the target signature can be a hash value obtained by performing hash calculation on a pre-stored high-risk device file using the MD5 algorithm.

[0044] In one embodiment, in response to a power grid remote operation and maintenance trigger event triggered by an operation and maintenance terminal, the server may retrieve a pre-stored high-risk device file and perform a hash calculation on the retrieved high-risk device file using a pre-configured hash algorithm to obtain a target signature code. The pre-configured hash algorithm is a pre-configured hash algorithm.

[0045] Step 204: Obtain the pre-stored original feature code for the pre-stored high-risk device file.

[0046] The original signature is a signature obtained by performing a hash calculation on the generated high-risk device file when the high-risk device file is generated. The original signature and the target signature are obtained by using the same hash calculation method on their respective corresponding high-risk device files.

[0047] In one embodiment, the pre-stored high-risk device file and the pre-stored original signature code may be stored in the same storage area, and the server may obtain the pre-stored original signature code while obtaining the pre-stored high-risk device file.

[0048] In one embodiment, the pre-stored high-risk device files and the pre-stored original signature codes may be stored in different storage areas. The server may query the storage location of the pre-stored original signature codes from a mapping table that records the identification information of the pre-stored high-risk device files and the storage locations of the pre-stored original signature codes, and obtain the pre-stored original signature codes based on the query storage location. The identification information may be a file name or file number, for example.

[0049] Step 206 : When the target signature code is the same as the original signature code, a risk assessment is performed on the target protection device according to the pre-stored high-risk device file to obtain an assessment result.

[0050] If the target signature code is identical to the original signature code, it indicates that the pre-stored high-risk device file has not been tampered with and is a trustworthy information source. The risk assessment result obtained by using this pre-stored high-risk device file to assess the target protection device is reliable. Risk assessment is the act of evaluating whether a target protection device is at risk. Risk means that remote operation and maintenance of the target protection device will pose a threat to the safe and stable operation of the power system. The assessment result is the result of a risk assessment of the target protection device.

[0051] In one embodiment, when the target feature code is the same as the original feature code, the server may query the target protection device from the pre-stored high-risk device file to perform a risk assessment on the target protection device; when the target protection device is queried in the pre-stored high-risk device file, an assessment result is obtained indicating that the target protection device has a risk; when the target protection device is not queried in the pre-stored high-risk device file, an assessment result is obtained indicating that the target protection device has no risk.

[0052] In one embodiment, when the target signature code is identical to the original signature code, the server may query the target protection device from a pre-stored high-risk device file. If the target protection device is found in the pre-stored high-risk device file and no preset risk relief information is found for the target protection device, an assessment result indicating that the target protection device is at risk is obtained. If the target protection device is found in the pre-stored high-risk device file and preset risk relief information is found for the target protection device, an assessment result indicating that the target protection device is not at risk is obtained. The preset risk relief information is preset information indicating that the high risk level of the device recorded in the high-risk device file has been relieved.

[0053] Step 208: When the evaluation result indicates that the target protection device has a risk, the remote operation and maintenance instructions for the target protection device are blocked and an alarm prompt is triggered.

[0054] Warnings are notifications of abnormal behavior, such as triggering remote maintenance on risky devices or tampering with files on high-risk devices.

[0055] In one embodiment, if the assessment results indicate a risk to the target protection device, the server can skip issuing remote operation and maintenance instructions to the target protection device and instead send an alert to the operation and maintenance terminal. The alert sent to the operation and maintenance terminal can be in the form of a to-do list or a pop-up message in the Baoxin main station client running on the operation and maintenance terminal.

[0056] In the above-mentioned power grid remote operation and maintenance processing method, the target feature code obtained by hash calculation and the pre-stored original feature code can be used to verify whether the high-risk device file has been tampered with, thereby improving the security of the high-risk device file; moreover, the high-risk device file is generated through the dynamic power grid risk file and the static baseline risk equipment file. The risk assessment of the target protection device is performed based on the high-risk device file, and it can be identified whether the target protection device has risks. When the target protection device has risks, remote maintenance of the target protection device is prevented, which can avoid the internal power grid operation and maintenance personnel from performing remote operation and maintenance on the risky target protection device and posing a threat to the safe operation of the power grid, thereby improving the security protection capability of the system.

[0057] In one embodiment, the above-mentioned power grid remote operation and maintenance processing method also includes a step of generating a high-risk device file and an original feature code, which step includes: respectively obtaining a dynamic power grid risk file and a static benchmark risk device file; the dynamic power grid risk file is a file that records risk event information during power grid operation, and the static benchmark risk device file is a file that records preset power grid benchmark risk devices; through pre-configured identification conditions, structured data is obtained from the dynamic power grid risk file and the static benchmark risk device file respectively, and a high-risk device file is generated and stored based on the structured data; hash calculation is performed on the generated high-risk device file to obtain the original feature code and store it.

[0058] The preconfigured recognition conditions are preconfigured conditions for identifying and extracting structured data. The recognition conditions can be configured through rule configuration in knowledge engineering. Specifically, a preconfigured field in a file can be preconfigured, and the recognition condition can be that when a preconfigured field in a file is identified, the data corresponding to the preconfigured field is structured data.

[0059] Structured data follows a specific format or length, making it easy to record in spreadsheets and understand by computers. For example, structured data might be dates, phone numbers, quantities, names, etc. In contrast to structured data, unstructured data can include irregular text, images, audio, video, or other data.

[0060] In this embodiment, a high-risk device file is generated by extracting structured data from a dynamic power grid risk file and a static baseline risk equipment file, so that when the high-risk device file is subsequently used to perform a risk assessment on a target protection device, it is convenient for the computer to identify the data in the high-risk device file, thereby improving the efficiency of the risk assessment; and after the high-risk device file is generated, the original feature code is obtained by hash calculation and stored, so that it is convenient to subsequently verify whether the stored high-risk device file has been tampered with by the original feature code, thereby improving the reliability of the high-risk device file.

[0061] In one embodiment, a static baseline risk device file is generated based on a risk granularity control file and a special information file. In this embodiment, the server can obtain the risk granularity control file and the special information file from the secondary equipment remote operation and maintenance control platform, obtain structured data from the risk granularity control file and the special information file respectively through pre-configured identification conditions, and generate a static baseline risk device file based on the obtained structured data. Among them, the secondary equipment remote operation and maintenance control platform is a platform for monitoring and managing secondary equipment that is undergoing remote operation and maintenance. Secondary equipment is auxiliary equipment that monitors, measures, controls, regulates, and protects primary equipment in the power system. Primary equipment is electrical equipment used to produce and use electrical energy in the power system, and the target protection device belongs to the secondary equipment.

[0062] In one embodiment, the dynamic grid risk file and the static baseline risk device file may be stored in Grid Security Zone 3, with the server located in Grid Security Zone 1. In this embodiment, the server may obtain the dynamic grid risk file and the static baseline risk device file from Grid Security Zone 3 via a reverse isolation device between Grid Security Zone 1 and Grid Security Zone 3.

[0063] In one embodiment, when there is an update to any file between the dynamic power grid risk file and the static baseline risk device file, the server can re-acquire the updated file, re-extract the structured data from the updated file, generate a new high-risk device file based on the re-extracted structured data and replace the stored high-risk device file, and re-hash the newly generated high-risk device file to obtain a new original feature code, and replace the stored original feature code with the new original feature code.

[0064] In one embodiment, the steps of respectively obtaining a dynamic grid risk file and a static baseline risk device file include: in response to a dynamic risk data update event, obtaining a dynamic grid risk file from a grid safety zone three through a reverse isolation device in a grid safety zone one; performing a credibility check on a pre-stored static baseline risk device file through a pre-stored baseline feature code in a grid safety zone one to obtain a verification result; the pre-stored static baseline risk device file is obtained and pre-stored from the grid safety zone three through a reverse isolation device; when the verification result indicates that the pre-stored static baseline risk device file is credible, the pre-stored static baseline risk device is used as the static baseline risk device file.

[0065] The dynamic risk data update event is an event in which a dynamic grid risk file is updated. The dynamic risk data update event can be triggered automatically when a dynamic grid risk file is updated, or manually by clicking a data update detection function key.

[0066] Grid Safety Zone 1 and Grid Safety Zone 3 belong to the safety protection zones of the grid secondary system. The power secondary system is used to monitor and control various automation systems in the production and operation process of the power system. The safety protection zones of the power secondary system can be divided into the production control zone (including Grid Safety Zone 1 and Grid Safety Zone 2) and the management information zone (including Grid Safety Zone 3 and Grid Safety Zone 4). The safety levels of Grid Safety Zone 1 to Grid Safety Zone 4 decrease in sequence. The production control zone and the management information zone can only communicate through the isolation device. The isolation device is a device used to perform network and physical isolation between the production control zone and the management information zone; among them, the computer system in the production control zone needs to access the data in the management information zone through the reverse isolation device, and the computer system in the management information zone needs to access the data in the production control zone through the forward isolation device.

[0067] The baseline signature code is obtained by hashing the static baseline risk device file obtained by Grid Security Zone 1 from Grid Security Zone 3. Credibility verification verifies whether the pre-stored static baseline risk device file has been tampered with, thereby verifying its authenticity.

[0068] In this embodiment, when the dynamic power grid risk file is updated, the updated dynamic power grid risk file can be obtained, and the high-risk device file can be updated in time to improve the reliability of the high-risk device file; while the static benchmark risk device file remains unchanged for a period of time after being pre-stored, and there is a risk of being tampered with. The credibility of the pre-stored static benchmark risk device file is verified by using the pre-stored benchmark feature code, which can ensure the reliability of the pre-stored static benchmark risk device file, and thus ensure the reliability of the high-risk device file.

[0069] In one embodiment, in response to a dynamic risk data update event, a server in Grid Security Zone 1 can retrieve a dynamic grid risk file from a grid risk management platform in Grid Security Zone 3 via a reverse isolation device. The grid risk management platform monitors, controls, and manages risk events in the grid. These events include power outages and restoring normal operation of abnormal or defective equipment.

[0070] In one embodiment, after obtaining the dynamic grid risk file, the server may store the dynamic grid risk file, perform hash calculation on the obtained dynamic grid risk file to obtain a dynamic risk characteristic code and store it, so that the stored dynamic grid risk file can be re-hashed to obtain a new dynamic risk characteristic code in the future, and the stored dynamic risk characteristic code and the new dynamic risk characteristic code can be used to verify whether the dynamic grid risk file has been tampered with.

[0071] In one embodiment, the server can obtain a static baseline risk device file pre-stored in the power grid security zone 1, perform a hash calculation on the static baseline risk device file, obtain a new baseline feature code, compare the new baseline feature code with the pre-stored baseline feature code to perform a credibility verification on the pre-stored static baseline risk device file. When the new baseline feature code is the same as the pre-stored baseline feature code, a credibility verification result of the pre-stored static baseline risk device file is obtained.

[0072] In one embodiment, the structured data in the dynamic power grid risk file includes at least risk identification, risk device identification and risk level; the static benchmark risk equipment file is generated based on the risk fine-grained control file that records device fault information and the T-type information file that records device maintenance information; the structured data in the risk fine-grained control file includes at least fault device identification and accident level; the structured data in the T-type information file includes at least T-type level, T-type plant identification and T-type device identification.

[0073] The risk identifier is the identifier of a risk event in the power grid. The risk device identifier is the identifier of the device targeted by the risk event corresponding to the risk identifier. The risk device identifier can be the device name or device number, etc. The risk level is the level of the risk event corresponding to the risk identifier.

[0074] The risk granularity management and control files and the Tevi information files can be stored in the secondary equipment remote operation and maintenance management platform and can be reviewed and maintained by power grid management personnel. The fault device identification is the identification of the secondary equipment that has failed, which can be the device name or device number, etc. The accident level is the level of impact on the power system when the secondary equipment corresponding to the fault device identification fails. The Tevi information file is a file recorded by the power grid management personnel when executing the device maintenance plan for the secondary equipment. The Tevi level is the level of importance of the device maintenance plan. The Tevi plant station identification is the identification of the power plant or substation targeted by the device maintenance plan, such as the power plant name, substation name, power plant number, substation number, etc. The Tevi device identification is the identification of the device targeted by the device maintenance plan, such as the device name or device number, etc.

[0075] In this embodiment, by clarifying the structured data in the dynamic power grid risk file, the risk fine-grained control file, and the special information file, it is convenient to configure the identification conditions for identifying the structured data, and then facilitate the subsequent identification of the structured data in the high-risk device file, thereby improving the efficiency of risk assessment of the target protection device through the high-risk device file.

[0076] In one embodiment, in step 206, a risk assessment is performed on the target protection device based on a pre-stored high-risk device file, and the step of obtaining the assessment result includes: obtaining a protection device identifier of the target protection device; querying the protection device identifier from the pre-stored high-risk device file to perform a risk assessment on the target protection device; when the protection device identifier is queried from the pre-stored high-risk device file, obtaining an assessment result indicating that a risk exists in the target protection device; when the protection device identifier is not queried from the pre-stored high-risk device file, obtaining an assessment result indicating that no risk exists in the target protection device.

[0077] The high-risk device file records information about various high-risk devices. The protection device identifier is the identification information of the target protection device. The protection device identifier can be the name or number of the target protection device.

[0078] In this embodiment, by querying the protection device identifier from the high-risk device file, it is possible to quickly determine whether the target protection device exists in the high-risk device file, and then obtain an assessment result of whether the target protection device is at risk, thereby creating conditions for subsequently preventing the execution of remote operation and maintenance instructions on the target protection device at risk.

[0079] In one embodiment, the above-mentioned power grid remote operation and maintenance processing method further includes the following steps: when the evaluation result indicates that there is no risk to the target protection device, remote operation and maintenance instructions are executed through the target protection device to perform remote power grid operation and maintenance on the target protection device.

[0080] In this embodiment, when the evaluation result indicates that there is no risk to the target protection device, it means that remote maintenance of the target protection device will not have an adverse impact on the safe operation of the power system. Then, by executing remote operation and maintenance instructions through the target protection device, remote operation and maintenance of the power grid of the target protection device can be realized without the need for on-site maintenance, thereby improving the maintenance efficiency of the target protection device.

[0081] In one embodiment, when the evaluation result indicates that the target protection device does not pose a risk, the server may issue a remote operation and maintenance instruction to the target protection device, and the target protection device may start executing the remote operation and maintenance instruction to perform remote operation and maintenance of the power grid on the target protection device.

[0082] In a specific embodiment, the above-mentioned power grid remote operation and maintenance process specifically includes the following steps:

[0083] like Figure 3 As shown in the flow chart of the high-risk device file generation steps, the server located in the grid safety zone 1 can obtain the dynamic grid risk file from the grid risk management platform located in the grid safety zone 3 through the reverse isolation device, and obtain the static benchmark risk device file from the secondary equipment remote operation and maintenance control platform located in the grid safety zone 3, so that the dynamic grid risk file and the static benchmark risk device file are transmitted to the grid safety zone 1 through the reverse isolation device; through pre-configured identification conditions, structured data is obtained from the dynamic grid risk file and the static benchmark risk device file respectively, and a high-risk device file is generated and stored based on the structured data; the generated high-risk device file is hashed using the MD5 algorithm to obtain the original feature code and store it.

[0084] The static baseline risk equipment file is generated by obtaining structured data from the risk fine-grained control file and the Tevi information file, respectively, and based on this structured data. The dynamic power grid risk file may include structured data such as risk identification, risk device identification, and risk level, as well as unstructured data such as risk analysis and risk resolution conditions. The risk fine-grained control file may include structured data such as faulty device identification, accident level, and risk grade, as well as unstructured data such as risk description, risk assessment, risk analysis, and risk control measures. The Tevi information file may include structured data such as Tevi level, Tevi plant identification, and Tevi device identification, as well as Tevi work content, Tevi requirements, and inspection methods.

[0085] like Figure 4As shown in the flowchart of the power grid remote operation and maintenance processing steps, the server can respond to the power grid remote operation and maintenance trigger event triggered by the operation and maintenance terminal through the Baoxin master station client (which can be used to instruct the server to issue remote operation and maintenance instructions), and perform hash calculation on the pre-stored high-risk device file through the MD5 algorithm to obtain the target feature code and obtain the pre-stored original feature code for the pre-stored high-risk device file; when the target feature code is different from the original feature code, the server can skip the step of issuing the remote operation and maintenance instruction to the target protection device, and send an alarm prompt to the operation and maintenance terminal to prompt that the pre-stored high-risk device file has been tampered with.

[0086] When the target feature code is the same as the original feature code, the server can obtain the protection device identification of the target protection device; query the protection device identification from the pre-stored high-risk device file to perform a risk assessment on the target protection device; when the protection device identification is queried from the pre-stored high-risk device file, an assessment result characterizing the risk of the target protection device is obtained; the server can skip the step of issuing remote operation and maintenance instructions to the target protection device and send an alarm prompt to the operation and maintenance terminal. The alarm prompt information can carry the risk information of the target protection device stored in the high-risk device file.

[0087] When the protection device identification is not found from the pre-stored high-risk device file, the server can obtain an assessment result indicating that there is no risk in the target protection device, issue a remote operation and maintenance instruction to the target protection device, and execute the remote operation and maintenance instruction through the target protection device to perform remote operation and maintenance of the power grid on the target protection device.

[0088] It should be understood that, although the various steps in the flowcharts involved in the various embodiments described above are displayed in sequence according to the instructions of the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be executed in other orders. Moreover, at least a portion of the steps in the flowcharts involved in the various embodiments described above can include multiple steps or multiple stages, and these steps or stages are not necessarily executed and completed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a portion of steps or stages in other steps.

[0089] Based on the same inventive concept, embodiments of the present application further provide a power grid remote operation and maintenance processing device for implementing the aforementioned power grid remote operation and maintenance processing method. The implementation solution provided by this device is similar to the implementation solution described in the aforementioned method. Therefore, the specific limitations of one or more power grid remote operation and maintenance processing device embodiments provided below can be found in the above-mentioned limitations of the power grid remote operation and maintenance processing method, and will not be repeated here.

[0090] In one embodiment, Figure 5 As shown, a power grid remote operation and maintenance processing device 500 is provided, including: a response module 510, an evaluation module 520 and a blocking module 530, wherein:

[0091] Response module 510 is used to respond to a power grid remote operation and maintenance trigger event, perform hash calculation based on a pre-stored high-risk device file, and obtain a target feature code; the high-risk device file is generated based on a dynamic power grid risk file and a static baseline risk device file; the power grid remote operation and maintenance trigger event is used to instruct the target protection device to execute a remote operation and maintenance instruction to perform power grid remote operation and maintenance on the target protection device.

[0092] The evaluation module 520 is used to obtain the original feature code pre-stored for the pre-stored high-risk device file; when the target feature code is the same as the original feature code, the target protection device is risk evaluated based on the pre-stored high-risk device file to obtain an evaluation result.

[0093] The blocking module 530 is used to block remote operation and maintenance instructions for the target protection device and trigger an alarm prompt when the evaluation result indicates that the target protection device has a risk.

[0094] In one embodiment, the above-mentioned power grid remote operation and maintenance processing device 500 also includes a pre-storage module, which is used to respectively obtain dynamic power grid risk files and static benchmark risk equipment files; dynamic power grid risk files are files that record risk event information during power grid operation, and static benchmark risk equipment files are files that record preset power grid benchmark risk equipment; through pre-configured identification conditions, structured data is obtained from the dynamic power grid risk files and static benchmark risk equipment files respectively, and a high-risk device file is generated and stored based on the structured data; a hash calculation is performed on the generated high-risk device file to obtain the original feature code and store it.

[0095] In one embodiment, the pre-storage module is also used to respond to a dynamic risk data update event, obtain a dynamic grid risk file from the grid safety zone three through a reverse isolation device in the grid safety zone one; perform a credibility check on the pre-stored static baseline risk device file in the grid safety zone one through a pre-stored baseline feature code to obtain a verification result; the pre-stored static baseline risk device file is obtained and pre-stored from the grid safety zone three through the reverse isolation device; when the verification result indicates that the pre-stored static baseline risk device file is credible, the pre-stored static baseline risk device is used as the static baseline risk device file.

[0096] In one embodiment, the structured data in the dynamic power grid risk file includes at least risk identification, risk device identification and risk level; the static benchmark risk equipment file is generated based on the risk fine-grained control file that records device fault information and the T-type information file that records device maintenance information; the structured data in the risk fine-grained control file includes at least fault device identification and accident level; the structured data in the T-type information file includes at least T-type level, T-type plant identification and T-type device identification.

[0097] In one embodiment, the assessment module 520 is also used to obtain a protection device identification of the target protection device; query the protection device identification from a pre-stored high-risk device file to perform a risk assessment on the target protection device; when the protection device identification is queried from the pre-stored high-risk device file, an assessment result is obtained indicating that there is a risk in the target protection device; when the protection device identification is not queried from the pre-stored high-risk device file, an assessment result is obtained indicating that there is no risk in the target protection device.

[0098] In one embodiment, the above-mentioned power grid remote operation and maintenance processing device 500 also includes an execution module, which is used to execute remote operation and maintenance instructions through the target protection device when the evaluation result indicates that there is no risk to the target protection device, so as to perform remote power grid operation and maintenance on the target protection device.

[0099] Each module in the aforementioned power grid remote operation and maintenance processing device can be implemented in whole or in part through software, hardware, or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in hardware form, or can be stored in a computer device memory in software form, so that the processor can call and execute the corresponding operations of each module.

[0100] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 6As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, abbreviated as I / O) and a communication interface. The processor, memory and input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The database of the computer device is used to store data that needs to be stored when executing the power grid remote operation and maintenance processing method. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a power grid remote operation and maintenance processing method is implemented.

[0101] Those skilled in the art will understand that Figure 6 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0102] In one embodiment, a computer device is further provided, including a memory and a processor. The memory stores a computer program, and the processor implements the steps in the above method embodiments when executing the computer program.

[0103] 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 steps in the above-mentioned method embodiments are implemented.

[0104] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0105] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiment methods can be implemented by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, database or other media used in the embodiments provided in this application may include at least one of non-volatile and volatile memory. Non-volatile memory may include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory may include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in the various embodiments provided herein may include at least one of a relational database and a non-relational database. Non-relational databases may include, but are not limited to, distributed databases based on blockchains. The processor involved in the various embodiments provided herein may be, but are not limited to, a general-purpose processor, a central processing unit, a graphics processing unit, a digital signal processor, a programmable logic unit, a data processing logic unit based on quantum computing, and the like.

[0106] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0107] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present application. It should be noted that a person of ordinary skill in the art may make various modifications and improvements without departing from the spirit of the present application, and these modifications and improvements fall within the scope of protection of the present application. Therefore, the scope of protection of the present application shall be determined by the appended claims.

Claims

1. A method for remote operation and maintenance of a power grid, characterized in that: The method comprises: In response to a power grid remote operation and maintenance triggering event, a target feature code is obtained by performing a hash calculation based on a pre-stored high-risk device file; the high-risk device file is generated based on a dynamic power grid risk file and a static baseline risk device file; the power grid remote operation and maintenance triggering event is used to instruct a target protection device to execute a remote operation and maintenance instruction to perform power grid remote operation and maintenance on the target protection device; Obtaining a pre-stored original feature code for the pre-stored high-risk device file; When the target feature code is identical to the original feature code, performing a risk assessment on the target protection device according to the pre-stored high-risk device file to obtain an assessment result; When the assessment result indicates that the target protection device is at risk, blocking the remote operation and maintenance instruction for the target protection device and triggering an alarm prompt; Among them, the dynamic power grid risk file is a file that records risk event information during power grid operation; the static benchmark risk equipment file is a file that records preset power grid benchmark risk equipment; the structured data in the dynamic power grid risk file includes at least risk identification, risk device identification and risk level; the static benchmark risk equipment file is generated based on the risk fine-grained control file that records device fault information and the T-type information file that records device maintenance information; the structured data in the risk fine-grained control file includes at least fault device identification and accident level; the structured data in the T-type information file includes at least T-type level, T-type plant identification and T-type device identification.

2. The method according to claim 1, characterized in that The method further comprises: Obtain dynamic grid risk files and static baseline risk equipment files respectively; Obtaining structured data from the dynamic grid risk file and the static baseline risk device file respectively through preconfigured identification conditions, generating and storing a high-risk device file based on the structured data; Perform hash calculation on the generated high-risk device file to obtain and store the original feature code.

3. The method according to claim 2, characterized in that The obtaining of the dynamic grid risk file and the static baseline risk device file respectively includes: In response to a dynamic risk data update event, obtaining a dynamic grid risk file from grid security zone 3 via a reverse isolation device in grid security zone 1; In the first grid security zone, a pre-stored static baseline risk device file is subjected to a credibility check using a pre-stored baseline characteristic code to obtain a check result; the pre-stored static baseline risk device file is obtained and pre-stored from the third grid security zone via the reverse isolation device; When the verification result indicates that the pre-stored static baseline risk device file is credible, the pre-stored static baseline risk device file is used as the static baseline risk device file.

4. The method according to claim 1, wherein The step of performing risk assessment on the target protection device according to the pre-stored high-risk device file to obtain an assessment result includes: Obtaining a protection device identifier of the target protection device; querying the protection device identifier from the pre-stored high-risk device file to perform a risk assessment on the target protection device; When the protection device identifier is found from the pre-stored high-risk device file, an assessment result indicating that the target protection device has a risk is obtained; When the protection device identifier is not found from the pre-stored high-risk device file, an assessment result indicating that the target protection device does not have any risk is obtained.

5. The method according to claim 1, characterized in that The method further comprises: When the evaluation result indicates that there is no risk to the target protection device, the remote operation and maintenance instruction is executed through the target protection device to perform remote power grid operation and maintenance on the target protection device.

6. A power grid remote operation and maintenance processing device, characterized in that: The device comprises: A response module is used to respond to a power grid remote operation and maintenance triggering event, perform hash calculation based on a pre-stored high-risk device file, and obtain a target feature code; the high-risk device file is generated based on a dynamic power grid risk file and a static benchmark risk device file; the power grid remote operation and maintenance triggering event is used to instruct a target protection device to execute a remote operation and maintenance instruction to perform power grid remote operation and maintenance on the target protection device; wherein, the dynamic power grid risk file is a file that records risk event information during power grid operation; the static benchmark risk device file is a file that records preset power grid benchmark risk devices; the structured data in the dynamic power grid risk file includes at least a risk identifier, a risk device identifier, and a risk level; the static benchmark risk device file is generated based on a risk fine-grained control file that records device fault information and a T-type information file that records device maintenance information; the structured data in the risk fine-grained control file includes at least a fault device identifier and an accident level; the structured data in the T-type information file includes at least a T-type level, a T-type plant identifier, and a T-type device identifier; an evaluation module configured to obtain an original feature code pre-stored for the pre-stored high-risk device file; and, if the target feature code is identical to the original feature code, perform a risk evaluation on the target protection device based on the pre-stored high-risk device file to obtain an evaluation result; A blocking module is used to block the remote operation and maintenance instructions for the target protection device and trigger an alarm prompt when the evaluation result indicates that the target protection device has a risk.

7. The device according to claim 6, characterized in that The device further includes a pre-storage module, the pre-storage module being configured to respectively obtain a dynamic grid risk file and a static baseline risk device file; obtain structured data from the dynamic grid risk file and the static baseline risk device file respectively based on pre-configured identification conditions, and generate and store a high-risk device file based on the structured data; Perform hash calculation on the generated high-risk device file to obtain and store the original feature code.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 5 are 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 steps of the method according to any one of claims 1 to 5 are implemented.

10. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 5 are implemented.

Images