A method and system for communicating pairs of points across security partitions

Abstract

The application discloses a kind of communication point methods and systems across security partition, method includes: pre-constructing the reference library of the measuring point of the whole station uniform and the global unique identification of the measuring point throughout whole link, first by the same partition front-end acquisition device, complete source reference check, lock correct reference, again according to the safety isolation configuration of power station adaptive selection pure one-way check mode or two-way closed loop check mode, complete end-to-end consistency check, after check pass, open official communication permission again, finally lock reference rule and whole link archive.The application fully complies with the power safety protection specification, two-mode adaptive covers inventory and newly-built power station whole scene, targetedly solves the core pain point of hydropower station communication point, and can be widely applied to the communication point scene of various hydropower stations / pumped storage power stations.

Description

Technical Field

[0001] This invention belongs to the field of power plant automation communication technology, and in particular relates to a communication point method and system for end-to-end data consistency verification before formal communication in a cross-safety zone scenario. Background Technology

[0002] Having undergone a long process of automation, informatization, and digitalization, mature information systems have been established within each network security zone. These include computer monitoring systems and excitation systems in Security Zone I, and unit status monitoring systems and energy metering systems in Security Zone II. These systems involve numerous equipment manufacturers and diverse system types, with communication protocols encompassing various proprietary protocols such as IEC104, IEC 61850, Modbus, and TCP / IP. Therefore, the construction of a smart power plant's data center requires the deployment of front-end data acquisition devices in each security zone. These devices communicate with various systems to acquire data before relaying it to the data center in the management information zone via forward security isolation devices. This data access process involves multiple interactive stages, making point-to-point communication the most time-consuming and error-prone aspect of on-site implementation. Furthermore, while existing automation and information systems are mature products with mature communication protocols and stable, reliable communication APIs, customized adjustments are difficult or costly. Therefore, point-to-point communication cannot generally be achieved through a two-way closed-loop model of "client write value - server feedback" as in substations. Currently, mature point-to-point communication technologies in the industry are all designed for bidirectional communication scenarios in substations. The invention patent with authorization announcement number CN 108418699B adopts a bidirectional closed-loop scheme in which the client sends write value commands and the server returns simulated change reports. It relies entirely on bidirectional communication interaction and cannot be adapted to the compliance requirements of unidirectional isolation in substations to achieve widespread access. The invention patent with application publication number CN 121262243A achieves point-to-point communication by generating a self-describing point-to-point file on the server side, but it still relies on bidirectional interaction to complete parsing and verification. It has not been adapted for unidirectional transmission scenarios in substations, nor has it solved the problem of high manufacturer cooperation costs in heterogeneous scenarios with multiple manufacturers in substations.

[0003] Overall, the existing technology has the following shortcomings: 1) It relies on two-way communication interaction, which requires the cooperation of the equipment manufacturers to modify the system and even requires support for two-way write operations. It cannot adapt to the current situation of a large number of old systems in power plants and low cooperation from manufacturers, resulting in high implementation costs and long cycles. 2) The problem of frequent measurement point sequence errors, high and low byte order errors, and measurement point mapping misalignment in the entire data link of the power plant has not been addressed in a targeted manner, which can easily lead to serious failures such as full message parsing avalanche and data misattribution; 3) The lack of segmented closed-loop verification makes it impossible to accurately define the responsibility boundaries between equipment manufacturers and system integrators, which can easily lead to difficulties in troubleshooting and the shirking of responsibility. Summary of the Invention

[0004] This invention addresses the core constraints of power plant cross-security zone scenarios, solving key problems in existing technologies such as high implementation costs of bidirectional solutions, inability to adapt to existing power plant unidirectional isolation scenarios, and the inability of unidirectional solutions to achieve automated closed-loop operation and susceptibility to parsing errors. It provides a power plant cross-security zone communication point-to-point solution that is low-cost to upgrade, adaptable to both modes, provides end-to-end error prevention, is compliant and secure, and fully matches industry-standard point-to-point rules.

[0005] To achieve the above objectives, the present invention adopts the following technical solution: A cross-security partition communication point-to-point method for verifying the consistency of measurement point data between the system to be connected and the data center in a power system includes the following core steps: S1. Construct a unified and unique measurement point benchmark library for the entire station and the entire link. Assign a globally unique identifier to each measurement point to be connected that runs through the entire data link and remains unchanged throughout the entire process. The measurement point benchmark library contains the specification definition, data format and mapping rules of each measurement point. S2. Perform source benchmark verification of local closed loop within the security partition: Through the front-end acquisition device of the security partition where the system to be accessed is located, receive the point test data packets sent by the system to be accessed according to the agreed protocol, and complete the protocol compliance verification and parsing consistency verification of the original data packets based on the test point benchmark library. After the verification is passed, generate structured benchmark data with a globally unique identifier and lock the cache to prevent unauthorized modification. S3. Adaptively match end-to-end verification mode according to the actual security isolation deployment of the power station: If the power station only deploys forward security isolation devices, select the pure one-way verification mode; if the power station deploys both forward and reverse security isolation devices, select the two-way closed-loop verification mode. S4. Perform end-to-end consistency verification for the corresponding mode. Only after the verification passes can formal communication permissions be granted; otherwise, the service channel will not be opened.

[0006] Furthermore, the globally unique identifier remains unchanged throughout the entire process of data packet packaging, parsing, forwarding, and repackaging, serving as the unique identity credential for the test point and the unique identity credential for the entire test point chain, thus fundamentally solving the problem of misaligned test point mapping.

[0007] Furthermore, the source benchmark verification described in S2 supports two compatible modes, which can be flexibly selected according to the manufacturer's cooperation level: The first mode is the manufacturer-free cooperation mode: the front-end acquisition device pre-builds the test point benchmark library based on the agreed specification document provided by the manufacturer, without requiring the access system to carry out business logic modification; after receiving the point test data packet of the access system, it caches the binary image of the original data packet with the full-site synchronization time stamp; based on the test point benchmark library, it verifies the compliance of the original data packet's frame format, message length, total number of test points, and check code; it parses the data packet according to the preset fixed offset and globally unique identifier in the test point benchmark library, and completes the parsing consistency verification of the test point order, high and low byte order, and name mapping relationship. The second method is the enhanced closed-loop mode: The front-end acquisition device sends a point-to-point enable command to the system to be connected that supports bidirectional write values ​​within the same partition, closes the formal business communication channel, and only opens the point-to-point test channel; it sends write value commands with globally unique identifiers to test points one by one or in batches, triggering the system to be connected to generate point-to-point test data packets for the corresponding test points and send them in a package; after receiving the data packets, the front-end acquisition device parses and verifies that the globally unique identifier, name, value and timing of the test points are completely matched with the sent write value commands, thus completing the source benchmark verification.

[0008] Furthermore, the core definition of the pure one-way verification mode is: there is no reverse message interaction from the management information area to the production control area throughout the entire process. Full closed-loop verification can be completed at the receiving end solely through the pre-encapsulated self-verification information. Specifically, the pre-acquisition device repackages the locked structured benchmark data according to a custom protocol, encapsulates the full self-verification information for the corresponding batch, and then transmits it unidirectionally to the power plant-level data center in the management information area via a forward security isolation device. The power plant-level data center, based on the measured point benchmark library and the received self-verification information, completes data packet integrity verification, parsing consistency verification, and end-to-end full data comparison, achieving one-way closed-loop point-to-point verification without reverse interaction. The data packet repackaged by the pre-acquisition device has a fixed format of [point-to-point verification header][measurement point index area][business data area]. The self-verification information encapsulated in the header includes: a unique batch number, a transmission timestamp based on the full-station synchronization clock, the measurement point index area, and the full message integrity verification value. The measurement point index area contains the globally unique identifier, name, offset, data length, and single measurement point verification value for all measurement points in this transmission. In one-way verification mode, the power plant-level data center will feed back the verification failure result to the operation and maintenance personnel or system to block the transmission of erroneous data.

[0009] Furthermore, the specific implementation of the bidirectional closed-loop verification mode is as follows: the front-end acquisition device repackages the locked structured reference data according to a custom protocol, encapsulates the unique verification identifier of the corresponding batch and the full self-verification information, and then transmits it unidirectionally to the power plant-level data center of the management information area through the forward security isolation device; after the power plant-level data center completes local parsing and verification, it generates a plain text receipt message containing only the unique verification identifier of the batch and the statistical value of the measurement point verification results, and transmits it unidirectionally back to the front-end acquisition device of the corresponding security partition through the reverse security isolation device; after receiving the receipt message, the front-end acquisition device verifies the consistency between the verification identifier and the batch, compares the statistical value of the verification results with the locally locked structured reference data, and completes the end-to-end bidirectional closed-loop verification.

[0010] Furthermore, if the verification fails, the point-to-point process is immediately terminated, and a list of abnormal measurement points and fault location results are output. During the point-to-point verification, the front-end acquisition device closes the formal business communication channel of the system to be connected and only opens the point-to-point test channel, strictly implementing the security control requirement of "verification before activation". After the end-to-end consistency verification passes in full, the formal communication permission of the system to be connected is activated, the measurement point benchmark library, parsing rules and repackaging rules corresponding to this point-to-point are locked, an unalterable communication point-to-point report is generated and archived throughout the entire link.

[0011] Correspondingly, the present invention also provides a cross-security zone communication point-to-point system, including a central side unit deployed in a power plant-level data center of a management information zone, and front-end side units deployed in front-end acquisition devices of each production control security zone. The central side unit and the front-end side units achieve compliant connection through a power-specific security isolation device. The central side unit includes a benchmark library management module, a mode adaptive verification center module, and a verification result processing module. The benchmark library management module is unidirectionally synchronously connected to the mode adaptive verification center module, the verification result processing module, and the front-end side unit, respectively, and the mode adaptive verification center module is bidirectionally connected to the verification result processing module. The front-end side unit includes a communication channel control module, a same-zone source verification module, and a mode adaptive verification front-end module. The communication channel control module is bidirectionally connected to the same-zone source verification module and the system to be accessed, respectively, and the same-zone source verification module is bidirectionally connected to the mode adaptive verification front-end module. The mode adaptive verification front-end module is unidirectionally connected to the mode adaptive verification center module through a forward security isolation device. The system also includes a processor and a memory. The memory stores a computer program, and the processor executes the computer program to implement the steps of the above-described cross-security zone communication point-to-point method.

[0012] Furthermore, the central-side unit also includes a receipt processing center module and an archive storage module. The mode-adaptive verification center module is bidirectionally connected to the receipt processing center module, and the verification result processing module is unidirectionally written to the archive storage module. The front-end unit also includes a receipt processing front-end module. The mode-adaptive verification front-end module is bidirectionally connected to the receipt processing front-end module, and the receipt processing center module is unidirectionally connected to the receipt processing front-end module through a reverse security isolation device to support bidirectional closed-loop verification mode.

[0013] Compared with the prior art, the present invention has the following advantages and beneficial effects: This invention proposes a dual-mode adaptive architecture for unidirectional and bidirectional verification, adapting to the current situation where existing power plants only have forward isolation devices and lack system upgrades, while also meeting the high-precision closed-loop verification requirements of newly built power plants with complete forward and reverse isolation devices. Both modes share a core benchmark system and can be smoothly switched. The unidirectional verification mode only requires the manufacturer to provide formal specification documents and accurate communication interface APIs to complete the entire point-to-point verification process, without deploying reverse security isolation devices or modifying existing mature business systems, and can be directly implemented in most existing power plants. Through technologies such as globally unique identifier binding throughout the process, fixed offset parsing, and pre-emptive self-verification of the index area, it fundamentally avoids and accurately locates core industry problems such as incorrect measurement point order, high / low byte order errors, and misaligned measurement point names, avoiding full-message parsing failures. By first completing source benchmark verification within the same partition and then completing end-to-end verification across partitions, this invention can accurately locate the faulty link and responsible party, completely resolving the issue of responsibility shirking between equipment manufacturers and system integrators, and significantly reducing fault diagnosis costs. Attached Figure Description

[0014] Figure 1 This is an overall flowchart of the cross-security partition communication point-to-point method in an embodiment of the present invention; Figure 2 This is a flowchart of the data interaction process in the one-way verification mode in an embodiment of the present invention; Figure 3 This is a flowchart illustrating the data interaction process of the bidirectional closed-loop verification mode in an embodiment of the present invention. Figure 4 This is a diagram of the cross-security partition communication point-to-point system architecture in an embodiment of the present invention. Detailed Implementation

[0015] To enable those skilled in the art to better understand the technical solutions of the present invention, preferred embodiments of the present invention are described below in conjunction with specific examples. However, it should be understood that the accompanying drawings are for illustrative purposes only and should not be construed as limiting the present invention. For better illustration of this embodiment, some components in the drawings may be omitted, enlarged, or reduced, and do not represent the actual dimensions of the product. It is understandable that some well-known structures and their descriptions may be omitted in the drawings for those skilled in the art. The positional relationships described in the drawings are for illustrative purposes only and should not be construed as limiting the present invention.

[0016] The present invention will be further described in detail below with reference to specific embodiments. It should be understood that the specific embodiments described herein are only for explaining the present invention and are not intended to limit the present invention.

[0017] This embodiment applies to a pumped storage power station. The power station is strictly divided into a production control zone (including Safety Zone I and Safety Zone II) and a management information zone (Safety Zone III) according to power safety protection requirements. Safety Zone I houses the pump-turbine speed control system, excitation system, relay protection system, and computer monitoring system. Safety Zone II houses the unit status monitoring system, high-voltage equipment online monitoring system, hydrological forecasting system, and electricity metering system. These systems are all mature industry systems with long-term usage and stable, reliable communication interface APIs; therefore, only communication functionality is supported, and customized development is not permitted. This embodiment deploys one front-end data acquisition device in each safety zone and a power plant-level data center in the management information zone. The entire station is equipped with a unified clock synchronization device, ensuring time synchronization of all systems, equipment, and servers in all zones with a synchronization accuracy of no less than 1ms.

[0018] This embodiment strictly follows industry-standard communication point-to-point rules, performing point-to-point verification only before the initial formal communication activation of the system to be connected and before the initial formal communication activation after a communication configuration change. Verification failure prevents the activation of the formal communication link. It also covers two typical power plant configuration scenarios: Scenario A: Existing power plants, with only forward security isolation devices deployed between the production control area and the management information area, but no reverse isolation devices, and existing business systems do not support the transformation; Scenario B: A new power plant is being built, with both forward and reverse safety isolation devices deployed. The new system supports minimal adaptation and modification.

[0019] like Figure 1 As shown, the overall process of the cross-security partition communication peer-to-peer method in this embodiment includes: S1. Construction of a unified measurement point benchmark database and a globally unique identifier for the entire station. In the data center of the management information region, a unified measurement point benchmark library is built for the entire site. Each measurement point to be connected is assigned a globally unique identifier that runs through the entire data link. The benchmark library is synchronized to the front-end acquisition devices of all security partitions, serving as the sole benchmark for point-to-point verification throughout the entire process. The two scenarios share the same benchmark system.

[0020] 1) Globally Unique Identifier Encoding Rules: A 16-bit fixed-length hexadecimal encoding is used, with the following encoding rules: The first two digits: security zone code, 01 represents security zone I, 02 represents security zone II, and 03 represents security zone III; The 3rd and 4th digits: Manufacturer code, a unique code assigned to each equipment manufacturer; 5th-6th digits: System code, a unique code is assigned to each business system; 7th-8th digits: Device code, which assigns a unique code to each device in the system; Digits 9-16: Measurement point serial number, assigning a unique serial number to each measurement point within the equipment.

[0021] This identifier remains unchanged throughout the entire process of data packet packaging, parsing, and repackaging, serving as the unique identity credential for the measurement point and fundamentally resolving the problem of misaligned measurement point mapping.

[0022] 2) Core fields of the measurement point benchmark library: Each measurement point corresponds to one benchmark entry, and the core fields include:

[0023] 3) Pre-processing control rules: During the point-to-point verification period, the pre-processing acquisition device only opens the point-to-point test channel and closes the formal business communication channel of the system to be connected, strictly implementing the requirement of "verification first, then activation".

[0024] S2, Source baseline verification within the security zone This step is completed within the security partition of the system to be connected, without crossing any security partitions. The core objective is to confirm that the "point-to-point test data packet sent by the system to be connected" is 100% consistent with the "data parsed by the front-end acquisition device," thereby pinpointing the correct benchmark from the source and accurately assigning manufacturer responsibility. The verification logic of this step is shared for both scenarios. This embodiment provides two compatible modes, which can be flexibly selected based on the manufacturer's cooperation level.

[0025] Mode 1: Manufacturer-Free Cooperation Mode This embodiment takes the Safety Zone II unit status monitoring system as an example. This system is an existing operating system, and the manufacturer only provides proprietary protocol specifications, a list of measurement points, and data packet format instructions. It does not cooperate with any system modifications and is used for point verification before the system's first formal communication activation. The specific execution steps are as follows: 1) The front-end acquisition device pre-builds a benchmark library of measurement points for the unit condition monitoring system based on the specification documents provided by the manufacturer, and assigns a globally unique identifier to each measurement point (such as 0203010100000001, representing Safety Zone II, Manufacturer 03, Unit Condition Monitoring System 01, Equipment 01, Measurement Point 00000001). 2) The front-end acquisition device shuts down the system's formal business communication channel and only opens the point-to-point test channel; 3) The manufacturer's maintenance personnel can trigger a full refresh of the device's measurement data on-site without modifying the device program. Once connected to the system, the full measurement data will be packaged into a point-to-point test data package according to the agreed protocol and sent to the front-end acquisition device. 4) After receiving the point-to-point test data packet, the front-end acquisition device caches a binary image of the original data packet with a full-site synchronization time stamp. The caching period meets the requirements of power industry compliance audit and fault tracing, and is used for subsequent fault tracing and responsibility determination. 5) Compliance verification of regulations: a. Verify whether the frame header and frame footer conform to the specification definition. If they do not conform, directly determine that the manufacturer's packaging is non-compliant and terminate the point-to-point process. b. Verify that the actual length of the verification message is consistent with the length agreed upon in the benchmark library, excluding data packet truncation or excessive length; c. Verify that the total number of measurement points in the verification message is consistent with the standard library agreement, eliminating missing or extra points; d. Calculate the checksum according to the agreed rules, compare it with the checksum in the data packet, and confirm that the data packet has no transmission errors.

[0026] 6) Parsing Consistency Check a. Preventing high / low byte order errors: First, verify the fixed benchmark check word agreed upon by the benchmark library (e.g., the 3rd-4th bytes of the data packet are fixed as 0xAA55), and parse it according to the agreed endianness format. If 0x55AA is parsed, it is directly determined that there is a high / low byte order error, an alarm is immediately issued, and the point-to-point process is terminated. b. Prevention of measurement point sequence errors: Blindly parses the data packet without following the order within the data packet, strictly parses according to the fixed offset of each measurement point in the benchmark library, and at the same time checks the correspondence between the globally unique identifier of the measurement point and the offset. If the order is abnormal, an alarm will be immediately triggered, and there will be no parsing misalignment. c. Preventing Misalignment of Measurement Point Mapping: After parsing, a mandatory check is performed to verify whether the globally unique identifier and name of each measurement point completely match the benchmark library. Only those that match are considered valid data, thus preventing misattribution.

[0027] 7) After all verifications pass, generate structured baseline data with a globally unique identifier, lock and cache it locally on the front-end server, and use it as the sole baseline for subsequent cross-regional transmission. It is prohibited to modify it arbitrarily.

[0028] Mode 2: Enhanced Closed-Loop Mode This embodiment takes a safety zone I relay protection system as an example. This system is a newly built system that supports bidirectional write operations according to the IEC 61850 protocol. The manufacturer has a high degree of cooperation, and this system is used for point-to-point verification before the system's first formal communication activation. The specific execution steps are as follows: 1) The front-end acquisition device shuts down the formal business communication channel of the system and only opens the point-to-point test channel; 2) Within the same safety zone, the front-end acquisition device sends a point-to-point enable command to the relay protection system, writes it into the preset "communication point-to-point enable" data object in the IEC61850 model, and enables the device point-to-point test function. 3) The front-end acquisition device issues write commands for measurement points with globally unique identifiers, including measurement point ID, target value, and time stamp, point by point or in batches, according to the measurement point benchmark library; 4) After receiving the write command, the relay protection system generates a point-to-point test data packet for the corresponding measurement point, packages it according to the IEC61850 protocol, and sends it to the front-end acquisition device. 5) After receiving the data packet, the front-end acquisition device parses out the globally unique identifier, name, value, and timing of the measurement point, and compares it with the written value command issued one by one. If they match completely, the measurement point is deemed to have passed the verification. 6) After the full measurement point verification is completed, generate structured benchmark data with a globally unique identifier, lock the cache on the front-end server, issue a point-to-point prohibition command, and disable the device's point-to-point testing function.

[0029] S3, Dual-mode adaptive end-to-end verification Based on the power station's security isolation configuration, this step adaptively selects the verification mode. Both modes share the structured benchmark data locked in step S2, eliminating the need to reconstruct the core logic and keeping the formal business communication channel closed throughout the process.

[0030] Example 1: Pure one-way verification mode (suitable for scenario A) like Figure 2 As shown, the one-way verification mode in this embodiment is adapted to existing power plants and newly built power plants that only deploy forward security isolation devices and have no system modification conditions. There are no reverse messages throughout the process, which strictly complies with power safety protection specifications. The specific execution steps are as follows: 1) Pre-packaging and self-verification information encapsulation The front-end acquisition device repackages the structured reference data locked in step S2 according to a custom protocol. The fixed message format is: [Point Verification Header] [Measurement Point Index Area] [Service Data Area] a. Point-to-point verification header (fixed 32 bytes): includes a unique batch number (4 bytes), transmission timestamp (8 bytes, based on the station's synchronous clock), total message length (4 bytes), total number of measurement points (4 bytes), full message SHA256 hash value (8 bytes), endianness identifier (1 byte), base check word (2 bytes), and reserved bytes (1 byte). b. Measurement point index area: Each measurement point corresponds to a 16-byte index entry, which includes a globally unique identifier (8 bytes), data offset (4 bytes), data length (2 bytes), and single measurement point CRC32 check value (2 bytes). c. Business Data Area: Measurement point values ​​arranged in the order of the index area, with each measurement point bound to a corresponding globally unique identifier.

[0031] This embodiment supports both TCP transmission and file transfer modes: a. TCP transmission mode: The repackaged message is transmitted unidirectionally to the management information regional data center via a forward security isolation device using TCP. b. File transfer mode: The repackaged business data and peer self-verification information are used to generate a business data file and a peer snapshot verification file bound to the same batch number, which are then transferred unidirectionally via the file transfer function of the forward security isolation device.

[0032] 2) One-way closed-loop verification of power plant-level data center After the data center receives the data packet / file, it does not need to send any messages to the front end. The closed-loop verification is completed according to the following steps: a. Basic compliance verification: Read the baseline checksum of the packet header / snapshot file to confirm that the high and low byte order is correct, and verify that the message length and total number of test points are consistent with the agreement, eliminating truncation and incorrect packets; b. Transmission integrity verification: Calculate the SHA256 hash value of the entire message / file and compare it with the encapsulated check value to confirm that there is no tampering or packet loss during the transmission process; c. Measurement point mapping and sequence verification: Parse the measurement point index area, verify that the global unique identifier and offset of each measurement point are completely consistent with the measurement point benchmark library, and confirm that there is no disorder of order or misalignment of mapping. d. Data correctness verification: Parse the business data according to the offset and length of the index area, calculate the CRC32 check value of each measurement point, compare it with the check value in the index area, confirm that the parsing is correct, and generate a quadruple of "globally unique identifier-measurement point name-measurement value-time stamp"; e. End-to-end consistency comparison: The parsed quadruple is compared with the baseline data of the front-end package. If they are completely consistent, the test point is deemed to have passed the verification. If all test points pass, the end-to-end verification is deemed to have passed.

[0033] In one-way verification mode, the data center will report the verification failure result to the operation and maintenance personnel or system to block the transmission of erroneous data.

[0034] Example 2: Two-way closed-loop verification mode (suitable for scenario B) like Figure 3 As shown, the bidirectional closed-loop verification mode in this embodiment is adapted to newly built power plants that simultaneously deploy forward and reverse security isolation devices. The reverse channel only transmits plain text verification receipts without any control commands, fully complying with safety specifications and achieving end-to-end high-precision closed-loop verification. The specific execution steps are as follows: 1) Pre-packaging and verification mark encapsulation The front-end acquisition device repackages the structured reference data locked in step S2 according to a custom protocol. In addition to encapsulating the full self-verification information in the pure one-way mode, it assigns a unique 32-bit verification identifier to this batch and generates a summary verification value of the reference data for this batch (number of full measurement points, number of normal measurement points, and hash value of full data). The repackaged message is transmitted unidirectionally to the management information area data center via the forward security isolation device.

[0035] 2) Local data center resolution and receipt generation After receiving the message, the data center completes the same 5-step local verification process as in the pure one-way mode, generating the verification result statistics for this batch; subsequently, it generates a plain text receipt message containing only the following content, without any other data: a. A unique verification identifier for this batch; b. The total number of measurement points received in this batch and the number of measurement points that passed verification; c. The hash value of the full parsed data for this batch.

[0036] The receipt message is transmitted unidirectionally back to the front-end acquisition device of the corresponding security zone via the reverse security isolation device. There are no production control commands throughout the process, which strictly complies with the usage specifications of the reverse security isolation device.

[0037] 3) Front-end bidirectional closed-loop confirmation After receiving the acknowledgment message, the front-end acquisition device performs the following verification to complete the closed loop: a. Verify that the unique verification identifier in the receipt message is completely consistent with the identifier of this batch to confirm that the receipt matches the batch and avoid incorrect packets; b. The total number of measurement points and the number of verification passes in the comparison receipt are completely consistent with the locally locked structured benchmark data; c. Compare the hash value of the full data in the receipt with the hash value of the local baseline data; If all three checks pass, the end-to-end bidirectional closed-loop check is deemed successful.

[0038] S4. Verification Result Processing and Closed-Loop Operation 1) Verification Pass Handling: After 100% of the end-to-end verification of all measurement points passes, perform the following operations: a. The front-end acquisition device opens the formal business communication channel of the system to be connected and closes the point-to-point test channel; b. Lock the benchmark library, pre-analysis rules, repackaging rules, and data center parsing rules corresponding to this point, write them to a read-only configuration file, and without a formal change approval process, no one may modify them; c. Generate an unalterable communication point-to-point acceptance report, including: point-to-point execution timing, verification scope, selected verification mode, full list of measurement points, verification results, anomaly rectification records, full-link time stamp information, and confirmation of the responsible party. After being signed and confirmed by relevant parties, it serves as an essential compliance certificate for the commissioning of the communication link. d. End-to-end credential archiving: The manufacturer's original point-to-point test data packet binary image, pre-locked structured benchmark data, repackaged data packets, point-to-point snapshot files, receipt messages (two-way mode), and point-to-point acceptance reports are all stored in an immutable archive storage, with a retention period that meets the power industry's compliance audit and fault tracing requirements.

[0039] 2) Handling of Verification Failures: If any step fails verification, immediately terminate the peer-to-peer process and perform the following actions: a. Keep the formal business communication channels of the system to be connected closed and do not open them; b. Output a list of abnormal measurement points and accurate fault location results, clearly identifying the fault link and the responsible party; c. After the responsible party completes the rectification, the full-process point-to-point verification will be retried until the verification is passed before formal communication can be resumed.

[0040] Example 3: A cross-security partition communication point-to-point system like Figure 4As shown, the system includes a central unit deployed in the power plant-level data center of the management information zone, and front-end units deployed in the front-end acquisition devices of each production control safety zone. The central unit and the front-end units are connected in compliance with regulations through a power-specific safety isolation device. The central unit includes a benchmark library management module, a mode adaptive verification center module, and a verification result processing module. The benchmark library management module is unidirectionally synchronously connected to the mode adaptive verification center module, the verification result processing module, and the front-end units, respectively. The mode adaptive verification center module is bidirectionally connected to the verification result processing module. The front-end units include a communication channel control module, a same-zone source verification module, and a mode adaptive verification front-end module. The communication channel control module is bidirectionally connected to the same-zone source verification module and the system to be accessed, respectively. The same-zone source verification module is bidirectionally connected to the mode adaptive verification front-end module. The mode adaptive verification front-end module is unidirectionally connected to the mode adaptive verification center module through a forward safety isolation device. The system also includes a processor and a memory. The memory stores a computer program, and the processor executes the computer program to implement the steps of the above-mentioned cross-safety zone communication point-to-point method.

[0041] The central unit also includes a receipt processing center module and an archive storage module. The mode adaptive verification center module is bidirectionally connected to the receipt processing center module, and the verification result processing module is unidirectionally written to the archive storage module. The front-end unit also includes a receipt processing front-end module. The mode adaptive verification front-end module is bidirectionally connected to the receipt processing front-end module, and the receipt processing center module is unidirectionally connected to the receipt processing front-end module through a reverse security isolation device to support bidirectional closed-loop verification mode.

[0042] Finally, it should be noted that the above-described embodiments are merely specific implementations of the present invention, used to illustrate the technical solutions of the present invention, and not to limit it. The scope of protection of the present invention is not limited thereto. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can still modify or easily conceive of changes to the technical solutions described in the foregoing embodiments within the technical scope disclosed in the present invention, or make equivalent substitutions for some of the technical features; and these modifications, changes, or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be covered within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A method for point-to-point communication across security partitions, characterized in that, Includes the following steps: S1. Construct a unified and unique measurement point benchmark library for the entire station and the entire link. Assign a globally unique identifier to each measurement point to be connected that runs through the entire data link and remains unchanged throughout the entire process. The measurement point benchmark library contains the specification definition of each measurement point. S2. Perform source benchmark verification of local closed loop within the security partition: Through the front-end acquisition device of the security partition where the system to be accessed is located, receive the point test data packets sent by the system to be accessed according to the agreed protocol, and complete the protocol compliance verification and parsing consistency verification of the original data packets based on the test point benchmark library. After the verification is passed, generate structured benchmark data with a globally unique identifier and lock the cache to prevent unauthorized modification. S3. Adaptively match the end-to-end verification mode across security zones based on the actual security isolation deployment of the power station: If the power station only deploys forward security isolation devices, select the pure one-way verification mode; if the power station deploys both forward and reverse security isolation devices, select the two-way closed-loop verification mode. S4. Perform end-to-end consistency verification for the corresponding mode. Only after the verification passes can formal communication permissions be granted; otherwise, the service channel will not be opened.

2. The cross-security partition communication point-to-point method according to claim 1, characterized in that, The globally unique identifier mentioned in S2 adopts a fixed-length encoding, and the encoding rule is: security partition encoding - manufacturer encoding - system encoding - device encoding - test point serial number. The globally unique identifier remains unchanged throughout the entire process of data packet packaging, parsing, forwarding, and repackaging, serving as the unique identity credential of the test point.

3. The cross-security partition communication point-to-point method according to claim 1, characterized in that, The source benchmark verification within the security zone described in S2 adopts a manufacturer-free mode, specifically including: The front-end data acquisition device pre-builds a benchmark library of measurement points based on the manufacturer's agreed-upon specifications and documentation, requiring no modification to the system to be connected, no adaptation to the manufacturer's business logic, and no on-site manual intervention. After receiving the point-to-point test data packet from the system to be connected, a binary image of the original data packet with a unified synchronization time stamp cached across the entire site is used for fault tracing and responsibility determination. The frame format, message length, total number of measurement points, and verification code of the original data packets are verified based on the measurement point benchmark library to ensure compliance with the protocol. The data packets are parsed according to the fixed offset and globally unique identifier preset in the measurement point reference library to complete the parsing consistency verification of measurement point order, high and low byte order, and name mapping relationship.

4. The cross-security partition communication point-to-point method according to claim 1, characterized in that, The source benchmark verification within the security partition described in S2 adopts an enhanced closed-loop mode, specifically including: The front-end acquisition device sends a point-to-point enable command to the system to be accessed within the same partition that supports bidirectional write values, closes the formal business communication channel, and only opens the point-to-point test channel. Send write command for each test point with a globally unique identifier either point by point or in batches, triggering the system to be connected to generate the corresponding test data packet for the test point and send it in a package; After receiving the data packet, the front-end acquisition device parses and verifies that the global unique identifier, name, value and timing of the measurement point are completely consistent with the written value command issued, thus completing the source benchmark verification.

5. The cross-security partition communication point-to-point method according to claim 1, characterized in that, The specific implementation of the pure one-way verification mode described in S3 is as follows: The front-end acquisition device repackages the locked structured benchmark data according to a custom protocol, encapsulates the full self-verification information of the corresponding batch, and then transmits it unidirectionally to the power plant-level data center of the management information area through the forward security isolation device. Based on the aforementioned measurement point reference library and the received self-verification information, the power plant-level data center independently completes data packet integrity verification, parsing consistency verification, and end-to-end full data comparison, achieving fully automatic one-way closed-loop point matching without reverse interaction or control commands.

6. The cross-security partition communication point-to-point method according to claim 5, characterized in that, The self-verification information encapsulated in the header of the data packet repackaged by the front-end acquisition device includes: a unique batch number, a transmission timestamp based on the full-station synchronization clock, a measurement point index area, and a full message integrity verification value; the measurement point index area contains the globally unique identifier, name, offset, data length, and single measurement point verification value of all measurement points in this transmission, supporting rapid single measurement point location and accurate anomaly identification.

7. The cross-security partition communication point-to-point method according to claim 1, characterized in that, The specific implementation of the bidirectional closed-loop verification mode described in S3 is as follows: The front-end acquisition device repackages the locked structured benchmark data according to a custom protocol, encapsulates the unique verification identifier of the corresponding batch and the full self-verification information, and then transmits it unidirectionally to the power plant-level data center of the management information area through the forward security isolation device. After the power plant-level data center completes local parsing and verification, it generates a plain text receipt message containing only the batch unique verification identifier and the statistical values ​​of the measurement point verification results. This message is then transmitted unidirectionally back to the front-end acquisition device of the corresponding security partition via the reverse security isolation device. After receiving the acknowledgment message, the front-end acquisition device verifies the consistency of the verification identifier, batch matching, and the consistency of the verification result statistics with the local benchmark data, thus completing the end-to-end bidirectional closed-loop verification.

8. A cross-security zone communication point-to-point system, characterized in that, The system further includes a processor and a memory, the memory storing a computer program, and the processor executing the computer program to implement all the steps of the cross-security partition communication peer method according to any one of claims 1-7.

Images