Cooperative control method for substation equipment

Abstract

The invention discloses a substation equipment cooperative control method. The method comprises the following steps: acquiring operation data of power equipment in a substation in real time; identifying a target equipment group under the current working condition based on a pre-constructed equipment coordination relationship library; generating a cooperative control strategy and issuing the cooperative control strategy to the edge intelligent gateway; the gateway analyzes the strategy into an executable instruction set of heterogeneous equipment and performs dual security verification; synchronously issuing an instruction to multiple devices through the parallel control channel; and if the execution fails, triggering a self-adaptive retry mechanism, and after the retry fails, starting standby equipment switching and storing fault information into the block chain. According to the invention, intelligent, safe and efficient cooperative linkage control among multiple devices of the transformer substation is realized, and the response speed of the devices of the transformer substation is remarkably improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of power system automation, in particular to a substation equipment cooperative control method. BACKGROUND

[0002] With the deepening of the construction of smart grid, the number of equipment in the substation has increased rapidly, and there are various types of equipment, including transformers, circuit breakers, relay protection devices and various environmental monitoring sensors. There are complex electrical and logical association relationships between these devices. The traditional single-point independent control mode has been difficult to meet the needs of modern substation for efficient, reliable and intelligent operation.

[0003] In the prior art, the control of substation equipment mainly depends on the centralized decision and instruction issuing of the background monitoring system. This method has the following defects: High response delay: the control instruction is transmitted through the server, the link is long, the time delay is large, and it is difficult to meet the real-time requirement of the cooperative control scene; Poor coordination: each device usually receives instructions independently, lacks efficient and accurate multi-device synchronous linkage mechanism, and is prone to deterioration of system transient process due to asynchronous instructions; Insufficient reliability: the instruction issuing process lacks sufficient security verification mechanism, and in the face of instruction execution failure, there is usually no effective localized self-healing and redundancy strategy; Data reliability is questionable: critical information such as fault logs is stored in the central database, which has the risk of being tampered with, and is not conducive to accurate analysis and responsibility definition afterwards. SUMMARY

[0004] To solve the above problems, the present application provides a substation equipment cooperative control method, which comprises: S1, real-time acquisition of the running state data of each power equipment in the substation, including transformers, circuit breakers, relay protection devices and environmental monitoring sensors; S2, based on the pre-constructed device cooperative relationship library, the target device group with cooperative control association relationship is identified according to the current operating condition; S3, according to the real-time running state data of the target device group and the cooperative rule library, the cooperative control strategy for the target device group is generated, and the control strategy is sent to the edge intelligent gateway of the substation through the security communication protocol; S4, the edge intelligent gateway parses the cooperative control strategy into an executable instruction set matched with the interface protocol of each device in the target device group through the protocol conversion engine, and performs a double security verification operation on the executable instruction set; S5, synchronously issue executable instruction set to each device in the target device group through the parallel control channel of the edge intelligent gateway, drive multiple devices to perform operations according to the cooperation rules, and feed back the execution state to the edge intelligent gateway in real time; S6, when the edge intelligent gateway detects that any device fails to execute, trigger an adaptive retry mechanism, and if the retry still fails, start a backup device switching strategy, and write fault information into a fault log stored in the blockchain.

[0005] Further, in the step S2, the construction method of the device cooperation relationship library comprises: S2.1, generating a topological matrix between devices according to the electrical connection relationship of the devices in the substation SCD configuration file; S2.2, obtaining historical operation data of the substation, the historical operation data comprising device operation records, fault records and recovery records; S2.3, based on the historical operation data and the topological matrix between devices, performing clustering analysis through a K-means clustering algorithm to identify a cooperative association mode between devices, the cooperative association mode comprising at least one of an electrical connection relationship, a functional dependency relationship and a fault linkage relationship; S2.4, converting the identified cooperative association mode into an executable logic rule set and storing it in the device cooperation relationship library in a structured data format.

[0006] Further, in the step S4, the double-layer security verification operation comprises: First-layer security verification: extracting a digital signature field of the executable instruction set, decrypting and matching verifying it by using a device public key certificate pre-stored locally by the edge intelligent gateway, and determining that the executable instruction set is an illegal instruction and intercepting it if the verification fails; Second-layer security verification: verifying the integrity and compliance of an instruction format, a data packet length, a device identification bit, a check bit and a function code field of the executable instruction set one by one according to a substation device communication protocol specification, and generating an error log and discarding the executable instruction set if the verification fails.

[0007] Further, in the step S5, the parallel control channel adopts a bidirectional multiplexing communication channel, manages executable instruction sets of multiple devices through a thread pool, allocates an independent sending queue for each device, and asynchronously receives an execution state code fed back by the device.

[0008] Further, in the step S6, the adaptive retry mechanism comprises: S6.1, the edge intelligent gateway obtains an execution state code fed back by the device, extracts a device type, an instruction type and an error code corresponding to a failed instruction when the state code represents a failure in execution; S6.2, based on the device type, instruction type and error code, query the preset retry strategy library, match the corresponding maximum retry number and retry interval time, the retry strategy library includes the mapping rule between the device type, instruction type and error code and retry parameter; S6.3, according to the retry interval time, retry sending the failed instruction, and monitor the device response state and record the retry number; S6.4, when receiving the success status code of the device feedback within the maximum retry number, end the retry and mark the instruction execution success, when the maximum retry number is reached and still unsuccessful, terminate the retry and trigger the standby device switching strategy.

[0009] Further, in the step S6, the fault log stored by the block chain adopts a distributed ledger, the edge intelligent gateway encapsulates the fault information into a fault log data packet according to a preset format, generates a digital fingerprint by performing a hash operation on the fault log data packet, and combines the fault log data packet, the digital fingerprint and a timestamp to generate a log block to be stored, and adds the log block to the distributed ledger through a consensus mechanism.

[0010] The beneficial effects of the application are: The application can automatically identify the device group having the correlation relationship by constructing the device coordination relationship library and the rule library, and generate the coordinated control strategy, realize the leap from the "single point control" to the "system level coordinated control", and improve the overall response speed and operation efficiency of the substation; the double security check mechanism is adopted, which not only guarantees the legality and integrity of the instruction source, but also prevents the device misoperation or refusal caused by format error, and improves the safety of the device control process; the parallel control channel and thread pool technology of the edge intelligent gateway are used to realize the synchronous instruction issuing and asynchronous state monitoring of multiple devices, effectively reduce the time delay of the multi-device coordinated operation, and ensure the synchronism of the coordinated operation; the built-in adaptive retry mechanism effectively deals with the temporary communication interference or device busy state, and when the retry is invalid, the standby device is automatically enabled, and the fault information is recorded in an unalterable manner by combining the block chain technology, realizing the rapid isolation, recovery and traceable analysis of the fault. BRIEF DESCRIPTION OF DRAWINGS

[0011] Figure 1 is a general flowchart of a substation device coordinated control method provided by the application. DETAILED DESCRIPTION

[0012] The technical method of the present application will be described clearly and completely below in conjunction with the drawings. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor fall within the scope of protection of the present application.

[0013] Embodiment one A substation equipment collaborative control method, the method comprises: S1, collecting the running state data of each power equipment in the substation in real time, the power equipment including transformers, circuit breakers, relay protection devices and environmental monitoring sensors; S2, based on the pre-constructed equipment collaborative relationship library, identifying the target equipment group with collaborative control correlation according to the current operating condition; S3, generating a collaborative control strategy for the target equipment group according to the real-time running state data of the target equipment group and the collaborative rule library, and sending the control strategy to the edge intelligent gateway of the substation through a secure communication protocol; S4, the edge intelligent gateway parses the collaborative control strategy into an executable instruction set matched with the interface protocol of each device in the target equipment group through a protocol conversion engine, and performs a double security check operation on the executable instruction set; S5, through the parallel control channel of the edge intelligent gateway, the executable instruction set is synchronously issued to each device in the target equipment group, driving multiple devices to perform operations according to the collaborative rules, and feeding back the execution state to the edge intelligent gateway in real time; S6, when the edge intelligent gateway detects that any device fails to execute, an adaptive retry mechanism is triggered, and if the retry still fails, a backup device switching strategy is started, and the fault information is written into the fault log stored in the blockchain.

[0014] Specifically, through the intelligent sensors and data acquisition units deployed on the substation site, the transformer oil temperature, circuit breaker opening and closing state, protection device action signal and environmental temperature and humidity data are collected in real time, the data acquisition frequency is 100ms / time, and the real-time nature of the running state is ensured through high-frequency acquisition, providing a data basis for collaborative control.

[0015] As a preferred mode of the present embodiment: in the step S2, the construction method of the equipment collaborative relationship library comprises: S2.1, generating a topological matrix between devices according to the electrical connection relationship of devices in the substation SCD configuration file; S2.2, obtaining the historical running data of the substation, the historical running data including device operation records, fault records and recovery records; S2.3. Based on the historical operating data and the topology matrix between devices, cluster analysis is performed using the K-means clustering algorithm to identify collaborative association patterns between devices. The collaborative association patterns include at least one of electrical connection relationships, functional dependency relationships, and fault linkage relationships. S2.4. Convert the identified collaborative association patterns into an executable set of logical rules and store them in the device collaborative relationship library in a structured data format.

[0016] Specifically, the SCD configuration file of the substation is parsed to extract the electrical connection relationships of all IED devices (such as the interlocking relationship between circuit breakers and disconnectors, and the association relationship between protection devices and measurement units), and a topology matrix is ​​constructed using the device ID as the row and column index. (n is the total number of devices), matrix elements Indicates device With equipment Connection relationships: :equipment With equipment It has an electrical connection or a strong logical relationship.

[0017] :equipment With equipment There is no direct connection between them.

[0018] The substation's SCD configuration file describes the substation's standardized configuration information. By parsing its logical nodes (LN) and input / output relationships, device associations can be accurately extracted, ensuring that the construction of the collaborative relationship library is based on an accurate electrical topology.

[0019] Historical data from the past year was extracted from the substation's historical database, including: equipment operation records (equipment operation events); fault records (protection device action events); and recovery records (equipment status restoration operations after a fault). This historical data reflects the inter-equipment linkage patterns in actual operation and helps to uncover implicit collaborative relationships between devices.

[0020] Based on historical data and the topology matrix between devices, feature vectors of device operation events are constructed. For example, for a certain fault event, a feature vector is generated. dimensional vector ,in Indicates device It is operated on or triggered in this event, otherwise it is 0.

[0021] Set the number of clusters ( The value is set according to the number of station equipment types), the K-means algorithm is used to cluster the operation event feature vectors, the characteristics of events in each cluster are analyzed, the collaborative mode is identified, and the clustering results are converted into IF-THEN form logical rules, which are stored in the collaborative relationship database in JSON format. The collaborative mode includes: Electrical connection mode: devices in the same electrical interval often appear in the same cluster (for example: IF circuit breaker CB01 opens THEN interlock disconnecting switch DS01 opens).

[0022] Functional dependency mode: different electrical connections but functionally related devices (for example: IF transformer T1 oil temperature > 85°C THEN start fan FAN01 AND reduce load L1).

[0023] Fault linkage mode: frequently co-occurring device combinations in fault records (for example: IF protection device P01 acts THEN trip circuit breaker CB01 AND start backup power BKU01).

[0024] The K-means clustering algorithm extracts the hidden relationships between devices that are difficult for humans to identify from frequently co-occurring device combinations in historical data, and the clustering results can be dynamically updated with new data, improving the coverage and adaptability of the collaborative relationship database. The use of regular storage allows the collaborative relationship to be directly called by the control program.

[0025] As a preferred mode of the present embodiment: in step S4, the double-layer security verification operation includes: First layer security verification: extract the digital signature field of the executable instruction set, use the edge intelligent gateway local pre-stored device public key certificate for decryption and matching verification. If the verification fails, it is determined that the executable instruction set is illegal and is intercepted; The second layer security verification checks the integrity and compliance of the instruction format, data packet length, device identification bit, check bit and function code field of the executable instruction set according to the substation equipment communication protocol specification. If the verification fails, an error log is generated and the executable instruction set is discarded.

[0026] Specifically, the edge intelligent gateway receives a JSON format cooperative control strategy data packet, parses the protocol into an executable instruction set matched with the device interface protocol, extracts the digital signature field in the instruction set header and the instruction set content, reads the pre-set device public key certificate from the local security storage area, decrypts the digital signature using the public key to obtain the original hash value, performs SHA-256 hash calculation on the instruction content part, compares the decrypted hash value with the calculated hash value, if the match is successful, the next layer of verification is entered, if the match fails, a security event is recorded and the instruction is intercepted. The digital signature adopts the asymmetric encryption principle to ensure that the instruction source is credible and has not been tampered with, and only the authorized system holding the private key can generate a valid signature, effectively preventing unauthorized instruction injection.

[0027] When the first layer of security verification passes, various device communication protocol specifications are loaded, and a protocol rule library is established, including the format requirements of each protocol, which are checked one by one: Check instruction format: verify whether the instruction structure conforms to the pre-set structure specification.

[0028] Check packet length: check whether the total length of the instruction is within the allowed range.

[0029] Check device identification bit: verify whether the device ID conforms to the naming specification and exists in the device registration table.

[0030] Check check bit: calculate the CRC32 checksum and compare it with the check bit at the end of the instruction set.

[0031] Check function code field: check whether the operation command is within the range of supported function codes of the device.

[0032] When the verification fails, detailed error logs are generated, recording information such as failure reason, timestamp, source IP address, etc., and the abnormal instruction is discarded. Based on the syntax and semantic check of the protocol specification, it is ensured that the instruction conforms to the device communication requirements, and when the double verification passes, it is issued to the corresponding device interface to drive the device to work, improving the security and reliability of the system.

[0033] As a preferred mode of the present embodiment: in step S5, the parallel control channel adopts a bidirectional multiplexing communication channel, manages the executable instruction set of multiple devices through a thread pool, allocates an independent sending queue for each device, and asynchronously receives the execution status code feedback by the device.

[0034] Specifically, a bidirectional multiplexing communication channel is established based on the TCP / IP protocol stack, multiple logical channels are virtually created through a single physical network port, and an independent communication port is allocated for each type of device, and a fixed-size thread pool is created including 8 worker threads and 1 monitor thread, wherein: Threads 1-4 (high priority): used for instruction sending.

[0035] Thread 5-7 (medium priority): for state reception.

[0036] Thread 8 (real-time priority): for exception handling.

[0037] A separate ring sending queue is created for each device to avoid mutual blocking of instructions between devices, and priority scheduling is used to ensure that critical instructions are processed first. Device state codes are received asynchronously, and execution timestamps are recorded and device state databases are updated to achieve fast collaborative response of multiple devices, improving the efficiency and reliability of substation device collaborative control.

[0038] Embodiment Two As a preferred mode of this embodiment: in step S6, the adaptive retry mechanism includes: S6.1, the edge intelligent gateway acquires the execution state code fed back by the device, and when the state code represents execution failure, extracts the device type, instruction type and error code corresponding to the failed instruction; S6.2, based on the device type, instruction type and error code, query the pre-set retry strategy library to match the corresponding maximum retry number and retry interval time, and the retry strategy library includes the mapping rule between the device type, instruction type and error code and the retry parameter; S6.3, according to the retry interval time, retry sending the failed instruction, and monitor the device response state and record the retry number; S6.4, when receiving the successful state code fed back by the device within the maximum retry number, end the retry and mark the instruction execution success; when the maximum retry number is reached and still unsuccessful, terminate the retry and trigger the standby device switching strategy.

[0039] Specifically, the edge intelligent gateway monitors the state code fed back by the device in real time, and when a non-successful state code is detected, a fault analysis process is started: The meaning of the state code is analyzed, the device type, instruction type and specific error code are extracted, the essential characteristics of the failed instruction are identified, and the basis for subsequent intelligent retry decision is provided. The built-in retry strategy library adopts a hierarchical index structure, and is matched according to the error code. Each fault combination corresponds to specific retry parameters, including maximum retry number, retry interval time, interval growth factor, etc. According to the matched retry parameters, the system starts a controllable retry process, and each retry is accompanied by a complete instruction checksum and security authentication process to ensure the legality of the retry instruction.

[0040] During the retry process, the system monitors the device response state in real time, records the timestamp, response time and result state of each retry, and when a successful status code is received from the device, the instruction execution is successful, and the retry is terminated; when the maximum number of retries is reached and it is still unsuccessful, it is determined as a persistent fault, the system starts the standby device switching strategy, and the system generates detailed fault information including device identifier, instruction content, error code, retry history, timestamp and other data, and writes into the fault log stored in the blockchain.

[0041] The application adopts automatic fault processing, reduces the need for manual intervention, greatly shortens the fault processing time, and sets detailed retry logs and fault records to provide rich data support for system health state analysis, and a reasonable termination and upgrade mechanism ensures that the system can still maintain key functions in the case of persistent faults.

[0042] As a preferred mode of the embodiment: in step S6, the fault log stored in the blockchain adopts a distributed ledger, and the edge intelligent gateway encapsulates the fault information into a fault log data packet according to a preset format, generates a digital fingerprint by performing a hash operation on the fault log data packet, and combines the fault log data packet, the digital fingerprint and the timestamp to generate a log block to be stored, and adds the log block to the distributed ledger through a consensus mechanism.

[0043] Specifically, after the edge intelligent gateway detects that the device execution fails, the generated fault information is obtained, including device identifier, instruction content, error code, retry history, timestamp and other data, and is encapsulated into a fault log data packet according to a preset standardized format, each data packet contains a metadata header and a payload part, the header records version number, encryption algorithm, gateway identifier and other information, and the payload stores specific fault details, a SHA-256 hash algorithm is used to calculate the fault log data packet, a 256-bit digital fingerprint is generated, the generated digital fingerprint is bound to the original data packet, the security of the data is enhanced, the fault log data packet, the digital fingerprint and the precise timestamp are combined to construct a log block, the blocks are connected in a chain structure through a hash pointer, the hash value of the previous block is contained in the header of the next block, forming an unbreakable link relationship, and through a consensus mechanism, a consensus network is formed by 5 edge intelligent gateway nodes, when a new log block is generated, the initiator node broadcasts the block proposal to other nodes, each node independently verifies the validity of the block, including digital fingerprint matching, timestamp rationality and format specification. After more than two-thirds of the nodes are verified, the block is officially added to the chain.

[0044] The application stores the fault log through the blockchain, so that the system can establish trust in an untrusted environment, and provide mathematical reliability proof for fault recording.

[0045] Those skilled in the art will appreciate that embodiments of the present application can be readily used as software, hardware, or a combination of software and hardware. In a software embodiment, various elements are implemented in hardware, software, or a combination of both hardware and software. In a software embodiment, the software implementation can be

[0046] The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks. Figure 1 one or more flowcharts and / or blocks Figure 1 means for functionally implementing the steps listed in the flowchart block or blocks.

[0047] These computer program instructions can also be stored in a computer- readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instructions which implement the function specified in the flowchart block or blocks. Figure 1 one or more flowcharts and / or blocks Figure 1 means for functionally implementing the steps listed in the flowchart block or blocks.

[0048] The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks. Figure 1 one or more flowcharts and / or blocks Figure 1 means for functionally implementing the steps listed in the flowchart block or blocks.

[0049] While preferred embodiments of the application have been described, modifications and variations can be effected without departing from the scope of the application. It is intended that the appended claims be interpreted as including all such alterations and modifications.

[0050] Obviously, numerous modifications and variations of the present application are possible in light of the above teachings. It is therefore to be understood that within the scope of the appended claims and their equivalents, the application can be practiced otherwise than as specifically described.

Claims

1. A method for coordinated control of substation equipment, characterized in that, The method includes: S1. Real-time acquisition of operating status data of various power equipment in the substation, including transformers, circuit breakers, relay protection devices and environmental monitoring sensors; S2. Based on a pre-built equipment collaboration relationship library, identify target equipment groups with collaborative control relationships according to the current operating conditions; S3. Based on the real-time operating status data and collaborative rule base of the target equipment group, generate a collaborative control strategy for the target equipment group, and send the control strategy to the edge smart gateway of the substation through a secure communication protocol. S4. The edge intelligent gateway uses a protocol conversion engine to parse the collaborative control strategy into an executable instruction set that matches the interface protocol of each device in the target device group, and performs a dual security verification operation on the executable instruction set. S5. Through the parallel control channel of the edge smart gateway, the executable instruction set is synchronously sent to each device in the target device group, driving multiple devices to perform operations according to the collaborative rules, and the execution status is fed back to the edge smart gateway in real time. S6. When the edge smart gateway detects that any device has failed to execute, it triggers an adaptive retry mechanism. If the retry still fails, it starts a backup device switching strategy and writes the fault information to the fault log stored on the blockchain.

2. The substation equipment collaborative control method according to claim 1, characterized in that: In step S2, the method for constructing the device collaboration relationship library includes: S2.1 Generate the topology matrix between devices based on the electrical connection relationships of the devices in the substation SCD configuration file; S2.2 Obtain historical operating data of the substation, including equipment operation records, fault records, and recovery records; S2.

3. Based on the historical operating data and the topology matrix between devices, cluster analysis is performed using the K-means clustering algorithm to identify collaborative association patterns between devices. The collaborative association patterns include at least one of electrical connection relationships, functional dependency relationships, and fault linkage relationships. S2.

4. Convert the identified collaborative association patterns into an executable set of logical rules and store them in the device collaborative relationship library in a structured data format.

3. The substation equipment collaborative control method according to claim 1, characterized in that: In step S4, the two-layer security verification operation includes: First layer of security verification: Extract the digital signature field of the executable instruction set, and use the device public key certificate pre-stored locally on the edge smart gateway for decryption and matching verification. If the verification fails, the executable instruction set is determined to be an illegal instruction and is blocked. The second layer of security verification is based on the substation equipment communication protocol specifications. It verifies the integrity and compliance of the instruction format, data packet length, device identifier, check bit, and function code field of the executable instruction set item by item. If the verification fails, an error log is generated and the executable instruction set is discarded.

4. The substation equipment collaborative control method according to claim 1, characterized in that: In step S5, the parallel control channel adopts a bidirectional multiplexed communication channel, manages the executable instruction sets of multiple devices through a thread pool, allocates an independent sending queue for each device, and asynchronously receives the execution status codes fed back by the devices.

5. The substation equipment collaborative control method according to claim 1, characterized in that: In step S6, the adaptive retry mechanism includes: S6.1 The edge intelligent gateway obtains the execution status code fed back by the device. When the status code indicates that the execution has failed, it extracts the device type, instruction type and error code corresponding to the failed instruction. S6.

2. Based on the device type, instruction type and error code, query the preset retry strategy library and match the corresponding maximum number of retries and retry interval time. The retry strategy library includes the mapping rules between the device type, instruction type and error code and retry parameters. S6.

3. Based on the retry interval, resend the failed command, and simultaneously monitor the device response status and record the number of retries. S6.4 If a success status code is received from the device within the maximum number of retries, the retries will end and the instruction will be marked as successfully executed; if the maximum number of retries is reached and the retries are still unsuccessful, the retries will be terminated and the standby device switching strategy will be triggered.

6. The substation equipment collaborative control method according to claim 1, characterized in that: In step S6, the fault logs stored in the blockchain adopt a distributed ledger. The edge smart gateway encapsulates the fault information into a fault log data packet according to a preset format, performs a hash operation on the fault log data packet to generate a digital fingerprint, and combines the fault log data packet, digital fingerprint, and timestamp to generate a log block to be stored. The log block is added to the distributed ledger through a consensus mechanism.

Images