Method and device for communication compatibility adaptation of new and old power equipment under grid monitoring control

Abstract

This invention discloses a method and apparatus for communication compatibility adaptation of new and old power equipment under power grid supervision and control, relating to the field of power equipment communication technology. The method includes: pre-configuring a device protocol library, a data decryption algorithm library, a message verification rule library, and a power equipment message transmission parameter library; establishing a bidirectional communication link with both new and old power equipment; collecting and parsing the original communication data of the new equipment to determine its data type, functional requirements, collection frequency, and encryption status; retrieving the matching protocol script of the old equipment to clarify its communication protocol framework, point number definition rules, and message transmission specifications; generating new function point numbers and establishing a mapping relationship with the original data; decrypting the data and encapsulating the target message according to the old equipment specifications; performing CRC verification and format correction on the target message; and transmitting it back to the old equipment to complete communication compatibility. This invention achieves automated adaptation of new and old equipment, reduces manual intervention, lowers operation and maintenance costs, and improves the adaptability and efficiency.

Description

Technical Field

[0001] This invention relates to the field of power equipment communication technology, and in particular to a method and apparatus for communication compatibility adaptation between new and old power equipment under power grid supervision and control. Background Technology

[0002] In the renovation of old power station buildings and the application of incremental equipment grid connection in power engineering, new and old power equipment produced by different manufacturers at different times generally have inconsistent communication protocols, different data encryption algorithms, and significant differences in message verification rules and transmission parameters.

[0003] Currently, the industry's methods for communication compatibility between new and old power equipment mostly adopt customized single-device protocol forwarding and simple pass-through of fixed messages. Point-to-point temporary communication interoperability of niche models of equipment can only be achieved by manually configuring protocol conversion scripts, manually setting point correspondences, and debugging message encapsulation formats and verification rules one by one.

[0004] Existing traditional adaptation methods can only achieve partial communication integration through fragmented manual configuration. They lack the ability to systematically pre-configure device protocols, decryption algorithms, message verification, and transmission parameters. They also cannot automatically parse the communication data characteristics of new devices, adaptively match the protocol framework and point number definition specifications of old devices, or autonomously complete the entire process of function point number generation, data mapping, decryption and encapsulation, and automatic message verification and correction. This makes it difficult to meet the practical application needs of rapid communication integration between large-scale new and old devices in power field applications. Summary of the Invention

[0005] To address the technical problem of weak compatibility and universality in communication protocols, encrypted data, message verification, and point mapping for various types of new and old power equipment in existing technologies, this invention provides a method and apparatus for communication compatibility and adaptation of new and old power equipment under power grid supervision and control.

[0006] The technical solution adopted in this invention is:

[0007] The first aspect of this application provides a method for communication compatibility adaptation of new and old power equipment under power grid regulatory control, including the following steps:

[0008] Step 1: Pre-configure the device protocol library, data decryption algorithm library, message verification rule library, and power equipment message transmission parameter library.

[0009] Step 2: Establish a two-way communication link with both the old and new power equipment.

[0010] Step 3: Collect the raw communication data of the new power equipment, and parse the raw communication data to determine the data type, functional requirements, data collection frequency and encryption status.

[0011] Step 4: Based on the equipment information of the old power equipment, retrieve the matching protocol script from the equipment protocol library to determine the communication protocol framework, point number definition rules, and message transmission specifications of the old power equipment.

[0012] Step 5: Based on the data type, functional requirements, and data acquisition frequency, and in conjunction with the point number definition rules, generate new functional point numbers within the communication protocol framework of the old power equipment, and establish a mapping relationship between the new functional point numbers and the original communication data.

[0013] Step 6: Based on the encryption status of the original communication data, call the matching algorithm from the data decryption algorithm library to complete the decryption process. Based on the mapping relationship, encapsulate the decrypted original communication data and the new function point number into a target communication message according to the old power equipment message transmission standard.

[0014] Step 7: Retrieve verification rules from the message verification rule library, combine them with the power equipment message transmission parameter library, perform CRC verification on the target communication message, correct the format of the target communication message that fails the verification, and send the target communication message that passes the verification back to the old power equipment to complete the communication compatibility between the new and old power equipment.

[0015] The second aspect of this application provides a communication compatibility adaptation device for new and old power equipment under power grid regulatory control, which applies the above-mentioned communication compatibility adaptation method for new and old power equipment under power grid regulatory control, including:

[0016] A resource library pre-configuration module is used to pre-configure a device protocol library, a data decryption algorithm library, a message verification rule library, and a power equipment message transmission parameter library.

[0017] A two-way communication link establishment module, which is used to establish a two-way communication link with old power equipment and new power equipment;

[0018] The raw communication data acquisition and parsing module is used to acquire raw communication data from new power equipment and parse the raw communication data to determine the data type, functional requirements, data acquisition frequency and encryption status.

[0019] The old equipment protocol parsing module is used to retrieve matching protocol scripts from the equipment protocol library based on the equipment information of the old power equipment, and determine the communication protocol framework, point number definition rules and message transmission specifications of the old power equipment.

[0020] The new function point number generation and mapping module is used to generate new function point numbers within the communication protocol framework of the old power equipment according to the data type, functional requirements and data acquisition frequency, combined with the point number definition rules, and to establish a mapping relationship between the new function point numbers and the original communication data.

[0021] The data decryption and message encapsulation module is used to call a matching algorithm from the data decryption algorithm library to complete the decryption process according to the encryption status of the original communication data, and encapsulate the decrypted original communication data and the new function point number into a target communication message according to the old power equipment message transmission specification based on the mapping relationship.

[0022] The message verification and feedback module retrieves verification rules from the message verification rule base, combines them with the power equipment message transmission parameter base, performs CRC verification on the target communication message, corrects the format of target communication messages that fail verification, and feedback the verified target communication messages to the old power equipment to achieve communication compatibility between the new and old power equipment.

[0023] The beneficial effects of the present invention are at least one of the following:

[0024] By pre-configuring various resource libraries such as device protocol libraries and data decryption algorithm libraries, and combining processes such as automatically establishing bidirectional communication links, automatically parsing the original communication data of new devices, and automatically adapting to the protocol framework of old devices, manual intervention is reduced and maintenance costs are lowered.

[0025] Based on the pre-configuration and calling logic of the device protocol library and data decryption algorithm library, it can adapt to new and old power equipment with different protocols and encryption methods, improve the universality of communication compatibility and adaptation, and eliminate the need to customize adaptation scripts for a single model of equipment, thus improving the flexibility of adaptation.

[0026] By automatically generating new function point numbers, establishing data mapping relationships, completing data decryption and encapsulation, and performing message CRC verification and format correction, the system achieves integrated processing for communication compatibility between new and old power equipment, improves adaptation efficiency, and better meets the practical application needs of large-scale mixed network communication docking of new and old equipment in power fields. Attached Figure Description

[0027] Figure 1 This is a schematic flowchart of the method of the present invention;

[0028] Figure 2 This is a schematic diagram illustrating the interaction between the various devices in the apparatus of the present invention. Detailed Implementation

[0029] The embodiments of the present invention will now be described in detail with reference to the accompanying drawings.

[0030] Example 1

[0031] To address the technical problems of traditional adaptation methods relying on fragmented manual configuration and single-point customized forwarding, which cannot achieve automated, integrated, and batch compatibility adaptation of communication protocols, encrypted data, message verification, and location mapping for various types of new and old power equipment, and which suffer from weak adaptability and high manual maintenance costs, this embodiment provides a method for communication compatibility adaptation of new and old power equipment under power grid supervision and control. Figure 1 As shown, it includes the following steps:

[0032] Step 1: Pre-configure the device protocol library, data decryption algorithm library, message verification rule library, and power equipment message transmission parameter library.

[0033] It should be noted that the equipment protocol library is a collection of resources that gather communication protocol scripts and protocol frame format definitions for new and old power equipment from different manufacturers and models. It covers the standard and private communication protocols of various equipment commonly used in substations, such as measurement and control devices, protection devices, and smart meters, and is used to provide standardized script support for subsequent protocol matching of old equipment.

[0034] The data decryption algorithm library is a collection of resources storing general encryption and decryption algorithms used in the power industry and those proprietary to equipment manufacturers. It includes national cryptographic algorithms for power applications, AES general symmetric encryption algorithms, and manufacturer-defined proprietary decryption algorithms, which are used to decrypt and restore the original communication data encrypted by new equipment.

[0035] The message verification rule base is a collection of rules that include various message CRC verification algorithms, check bit definitions, and error judgment standards. It covers commonly used verification methods in the power industry such as CRC16 and CRC32, and is used to verify the integrity and legality of encapsulated target communication messages.

[0036] The power equipment message transmission parameter library is a unified collection of basic communication parameters such as message transmission baud rate, frame interval, maximum message length, and transmission timing constraints, adapted to the transmission parameter requirements of different models of new and old equipment.

[0037] In the implementation process, the communication protocols of mainstream new and old power equipment in the power industry were sorted out, including standard protocols and manufacturer-specific protocols. The complete scripts, frame structure definitions, and function code meanings of all types of protocols were uniformly entered into the archive to form an equipment protocol library, ensuring that the library's resources cover common equipment models in the field. Common decryption algorithms in the power industry and manufacturer-specific decryption algorithms were collected, categorized and encapsulated, and labeled with the equipment models and encryption types that the algorithms are compatible with. These were then entered into the data decryption algorithm library, and a corresponding index of algorithms and equipment encryption methods was established for easy and rapid subsequent retrieval.

[0038] The CRC check polynomials, check bit arrangement rules, and format error judgment conditions corresponding to various power communication messages are compiled, including judgment criteria such as excessive message frame length, misaligned fields, and abnormal check bits. After being organized, a message verification rule library is formed, which clarifies the verification methods corresponding to different types of messages.

[0039] The communication transmission parameters of different models of new and old power equipment are statistically analyzed, including baud rate, message sending interval, maximum byte length per frame, and transmission timing requirements. These parameters are then uniformly entered into the power equipment message transmission parameter library, and the corresponding equipment models are labeled to ensure the accuracy of parameter retrieval.

[0040] For example, in the scenario of upgrading old and new equipment in a substation, the private communication protocol scripts of the old bay controllers and the standard protocol scripts of the new intelligent acquisition terminals are uniformly entered into the equipment protocol library; the power-specific national cryptographic SM4 decryption algorithm, the AES-128 general decryption algorithm, and a manufacturer's custom private decryption algorithm are entered into the data decryption algorithm library, and the equipment models adapted to each algorithm are marked; the CRC16 check rules and the rules for the check bit to be located at the end of the message frame are entered into the message check rule library; the 9600bps baud rate adapted to the old equipment, the 19200bps baud rate adapted to the new equipment, and the parameters such as the 50ms message frame interval and the maximum length of a single frame of 256 bytes uniform for various equipment are entered into the power equipment message transmission parameter library, thus completing the pre-configuration of the four types of resource libraries.

[0041] This step enables the centralized and organized storage of communication resources for various power equipment, providing a standardized resource call basis for subsequent protocol matching, data decryption, message verification, and transmission adaptation. It reduces the workload of on-site temporary configuration, avoids errors caused by manual configuration, and improves the efficiency and standardization of adaptation preparation work.

[0042] Step 2: Establish a two-way communication link with both the old and new power equipment.

[0043] Among them, the two-way communication link refers to the full-duplex data transmission channel established by the adapter with the new power equipment and the old power equipment respectively, which can realize uplink data acquisition and downlink command issuance. It can realize the real-time uploading of the original communication data of the new power equipment, as well as the back transmission of the target communication message after adaptation to the old power equipment, and at the same time support the transmission of downlink remote control commands from the old power equipment to the new power equipment.

[0044] In the specific implementation process, transmission parameters matching the models of the new and old power equipment are retrieved from the power equipment message transmission parameter database. These parameters include baud rate, frame interval, and communication port type. A physical link handshake is then performed with both the new and old power equipment to connect the adapter device to the equipment's communication port and confirm a normal physical connection. Next, a communication protocol handshake is performed. The adapter device sends a protocol handshake command, and both the new and old power equipment respond with a handshake response, confirming protocol compatibility and establishing a bidirectional communication link. This ensures that the link can achieve full-duplex data transmission without packet loss or bit errors during transmission.

[0045] For example, the adapter retrieves the 9600bps baud rate and RS485 port parameters corresponding to the old bay controller, and the 19200bps baud rate and Ethernet port parameters corresponding to the new intelligent acquisition terminal from the power equipment message transmission parameter database. Utilizing its independent baud rate configuration capability for multiple serial / Ethernet ports, it connects the RS485 port to the old bay controller and the Ethernet port to the new intelligent acquisition terminal without modifying the inherent communication parameters of the old and new devices. After the physical connection is completed, a bidirectional stable data transmission channel is established through protocol handshake commands.

[0046] Meanwhile, the adapter is equipped with a large-capacity data buffer to temporarily store and smooth the packets sent at a high speed of 19200bps by the new intelligent acquisition terminal. Based on the frame interval and packet transmission sequence pre-stored in the parameter library, it forwards packets at a uniform speed according to the old interval controller's transmission rate of 9600bps, realizing bidirectional barrier-free compatible communication across baud rates of 9600bps and 19200bps.

[0047] Step 3: Collect the raw communication data of the new power equipment, and parse the raw communication data to determine the data type, functional requirements, data collection frequency and encryption status.

[0048] The raw communication data consists of original message data output by the new power equipment without protocol conversion, format modification, or decryption. It directly reflects the business status of the new equipment and includes equipment operating parameters, fault information, and other content.

[0049] Data type refers to the service category corresponding to the original communication data, including telemetry data, remote signaling data, fault alarm data, setpoint parameter data, etc. Among them, telemetry data is continuously changing analog quantity data, and remote signaling data is discrete quantity data such as switch status.

[0050] Functional requirements refer to the business application scenarios corresponding to the original communication data, that is, the specific business functions that the data is used to achieve, such as equipment operation monitoring, fault alarm, parameter control, etc.

[0051] The data acquisition frequency is the time interval at which new power equipment actively sends raw communication data, that is, the number of times data is sent per unit time, reflecting the real-time nature of the data.

[0052] The encryption status is used to characterize whether the original communication data is transmitted in encrypted form and the type of encryption, including unencrypted, general encryption, and manufacturer-specific encryption, which are used to select the corresponding decryption algorithm later.

[0053] In the specific implementation process, the original data transmission status of the new power equipment is monitored in real time through the established two-way communication link, and every piece of original communication data actively transmitted by the new power equipment is collected synchronously to ensure the integrity and real-time nature of data collection.

[0054] In accordance with the power industry data classification standards, the message fields of the raw communication data are parsed to identify the corresponding data type and distinguish different categories of data such as telemetry, remote signaling, and fault alarms. By parsing the function identifiers in the message fields, the business function requirements corresponding to the raw communication data are identified, clarifying whether the data is used for equipment monitoring, fault alarms, or parameter control scenarios.

[0055] The data acquisition frequency of the new power equipment is determined by statistically analyzing the uploading time of multiple consecutive sets of raw communication data and calculating the time interval between two adjacent data sets.

[0056] Parse the header identifier field of the original communication data, and determine the encryption status of the original communication data according to the encoding rules of the identifier field, clarifying whether it is encrypted and the encryption type.

[0057] For example, the adapter collects the original messages sent by the new line protection device through a two-way communication link. After parsing the message fields, it determines that the data type is fault remote signaling data. The corresponding functional requirement is to monitor line faults in substations. The transmission time of 10 consecutive data messages is counted to obtain a data collection frequency of 1 second / message. The original communication data is determined to be transmitted using the manufacturer's proprietary encryption method through the message header identifier field, thus completing the collection and parsing of the original communication data.

[0058] Step 4: Based on the equipment information of the old power equipment, retrieve the matching protocol script from the equipment protocol library to determine the communication protocol framework, point number definition rules, and message transmission specifications of the old power equipment.

[0059] Among them, equipment information refers to the core identification information of old power equipment, including equipment model, manufacturer identification, hardware version, software version, etc., which is used to uniquely identify old power equipment and provide retrieval conditions for protocol script retrieval. Protocol script is the complete text of communication protocol that uniquely matches the old power equipment model and is stored in the equipment protocol library, containing all the rule definitions for communication of old equipment.

[0060] The communication protocol framework defines the overall architecture of the frame header structure, field arrangement order, function code definition, and reserved byte meaning of messages from legacy power equipment, serving as the foundation for legacy equipment to parse messages. The point number definition rules are the encoding rules for the background measurement point numbers of legacy power equipment, including the number of digits, encoding format, field allocation requirements, and numbering range, used to standardize the numbering method of measurement points in legacy equipment. The message transmission specification defines the message encapsulation format, field order, reserved byte definition, frame length limits, and other standards required by legacy power equipment, serving as the basis for new equipment data encapsulation into target communication messages.

[0061] Because older power equipment has a fixed proprietary communication protocol architecture and measurement point coding specifications, different models of older equipment have different protocol frameworks, point number definition rules, and message transmission specifications. Only by retrieving the protocol script that uniquely matches the older equipment can the communication rules of the older equipment be accurately obtained. Only then can these rules be followed to generate new function point numbers and encapsulate target communication messages, ensuring that the older equipment can correctly parse and recognize the adapted messages.

[0062] In the specific implementation process, equipment information such as the model number, manufacturer identification, and hardware version of the old power equipment is read. An equipment information query command is sent to the old power equipment via a two-way communication link, and complete equipment information is received from the old equipment to ensure accuracy. Using the obtained equipment information as search criteria, the equipment protocol library is traversed to search for protocol scripts that completely match the equipment information of the old power equipment. If a unique matching protocol script is found, it is directly retrieved; if multiple matching scripts appear, further filtering is performed based on hardware and software versions to determine the uniquely suitable protocol script. From the retrieved protocol script, the communication protocol framework of the old power equipment is extracted, clarifying the message frame header structure, field arrangement order, and function code meaning; point number definition rules are extracted, clarifying the point number length, encoding format, and numbering range; message transmission specifications are extracted, clarifying the message encapsulation format, field order, frame length limits, and the meaning of reserved bytes, providing a basis for subsequent steps.

[0063] For example, the adapter sends a device information query command to the old backend monitoring and control host, receives and obtains device information such as model XXX-2010, manufacturer identifier XX Power, and hardware version V1.0. Using this information as search criteria, it traverses the device protocol library, retrieves the uniquely matching protocol script, and decomposes the script to obtain the communication protocol framework of the old monitoring and control host, which has an 8-byte frame header, a 32-byte data segment, and a 2-byte frame tail. The point number definition rule is an 8-bit encoding, with the first 2 bits being the device number, the middle 3 bits being the measurement point type, and the last 3 bits being the measurement point sequence number. The message transmission specification is that the fields are arranged in the order of frame header, point number, data, and check bit, with a maximum of 42 bytes per frame, thus completing the determination of the old device's communication rules.

[0064] Step 5: Based on the data type, functional requirements, and data acquisition frequency, and in conjunction with the point number definition rules, generate new functional point numbers within the communication protocol framework of the old power equipment, and establish a mapping relationship between the new functional point numbers and the original communication data.

[0065] It should be noted that the new function point number is a compliant measurement point number newly compiled for the original business data of the new power equipment, following the definition rules of the old power equipment point number. It can be identified and parsed by the backend of the old power equipment and is the core carrier for the connection between the new equipment data and the old equipment measurement point system.

[0066] The mapping relationship is a one-to-one association and binding logic between the new function point number and the original communication data of the new power equipment. That is, each set of original communication data corresponds to a unique new function point number, and each new function point number uniquely corresponds to a set of original communication data, which is used to realize the accurate association between the data of the new equipment and the measurement points of the old equipment.

[0067] Because the original measurement point numbers of the new power equipment do not conform to the point number definition rules of the old power equipment, they cannot be identified and archived by the old equipment's backend, resulting in the inability of the new equipment's data to be integrated into the old equipment's business management system. Based on the characteristics of the new equipment's original data and the old equipment's point number definition rules, new functional point numbers are compiled and a mapping relationship is established. This enables a smooth mapping and conversion of the new equipment's data to the old equipment's measurement point system, allowing the old equipment to identify the new equipment's data through the new functional point numbers.

[0068] In the specific implementation process, based on the type, functional requirements, and data acquisition frequency of the new equipment's original communication data obtained from step 3, the business attributes corresponding to each set of original data are clarified, and the coding requirements for the new functional point number are determined. Following the old power equipment point number definition rules determined in step 4, a unique new functional point number is assigned to each set of original communication data within the point number gap specified in the old equipment communication protocol framework. This ensures that the point number encoding format, number of bits, and range conform to the old equipment rules and do not duplicate the original measurement point numbers of the old equipment. Each set of new power equipment original communication data is bound one-to-one with the corresponding assigned new functional point number, solidifying a fixed mapping relationship. This mapping relationship is recorded and stored for quick retrieval during subsequent message encapsulation.

[0069] For example, step 3 parses a set of new equipment's original communication data, which is the telemetry data of bus voltage #1. The functional requirement is bus voltage monitoring, and the data acquisition frequency is 1 second / data. Step 4 determines the old equipment point number definition rule as an 8-bit code. The first two bits are the equipment number, such as 01 for bus #1; the middle three bits are the measurement point type, such as 001 for telemetry; and the last three bits are the measurement point sequence number, such as the 001st telemetry measurement point. Combining this information, a new functional point number, 01001001, is created in the empty interval of the old equipment point number. This new functional point number is then bound one-to-one with the original telemetry data of bus voltage #1 to establish a mapping relationship, ensuring that the old equipment can identify the corresponding voltage data through this new functional point number.

[0070] This step enables the matching and association of data points from the new equipment without altering the original measurement point system of the old equipment, achieving seamless integration between the old and new measurement point systems and allowing the old equipment to accurately identify the data from the new equipment.

[0071] Step 6: Based on the encryption status of the original communication data, call the matching algorithm from the data decryption algorithm library to complete the decryption process. Based on the mapping relationship, encapsulate the decrypted original communication data and the new function point number into a target communication message according to the old power equipment message transmission standard.

[0072] It should be noted that decryption is the process of restoring the encrypted original communication data to plaintext business data using a corresponding decryption algorithm, ensuring that the data can be parsed normally by old power equipment. Different encryption states correspond to different decryption algorithms.

[0073] Plaintext data is the unencrypted original business data obtained after decryption processing. It retains the core business information of the original data of the new power equipment and is the core content of the message encapsulation. The target communication message is a standardized adaptation message generated by integrating the decrypted plaintext data and the corresponding new function point number, in accordance with the old power equipment message transmission specifications. It can be directly parsed and recognized by the old power equipment.

[0074] In the specific implementation process, based on the encryption status of the original communication data determined in step 3, the data decryption algorithm library is retrieved, and the decryption algorithm that matches the encryption status and device model is called. If the original data is not encrypted, there is no need to call the decryption algorithm, and the original data can be used directly; if it is general encryption or manufacturer proprietary encryption, the corresponding algorithm is called.

[0075] The encrypted original communication data is decrypted using the invoked decryption algorithm, restoring it to plaintext business data. This ensures that the plaintext data completely preserves the original data's business information without data loss or distortion. Based on the mapping relationship established in step 5, the new function point number corresponding to each set of plaintext data is found, and the plaintext data is combined with the corresponding new function point number.

[0076] According to the old power equipment message transmission specifications determined in step 4, the target communication message is encapsulated in the order of frame header, new function point number, plaintext data, and check bit to ensure that the message frame length, field arrangement, reserved bytes, etc. meet the requirements of the old equipment.

[0077] For example, step 3 determines that the original communication data of a certain group of new equipment uses the manufacturer's proprietary encryption method. Step 6 calls the corresponding proprietary decryption algorithm from the data decryption algorithm library to decrypt the original data and restore it to plaintext data with a voltage of 10.5kV for bus #1. Based on the mapping relationship, the new function point number corresponding to this plaintext data is found to be 01001001. According to the old equipment message transmission specifications, the frame header, the new function point number 01001001, the plaintext data 10.5kV, and the check bit are combined in sequence to encapsulate and generate the target communication message, ensuring that the message format meets the parsing requirements of the old equipment.

[0078] This step completes the decryption and restoration of encrypted data and standardized message encapsulation, enabling the new device's data to be fully compatible with the message parsing logic of the old device, ensuring that the old device can accurately parse the new device's data, and achieving effective data interoperability between the new and old devices.

[0079] Step 7: Retrieve verification rules from the message verification rule library, combine them with the power equipment message transmission parameter library, perform CRC verification on the target communication message, correct the format of the target communication message that fails the verification, and send the target communication message that passes the verification back to the old power equipment to complete the communication compatibility between the new and old power equipment.

[0080] It should be noted that CRC check is a process of verifying the integrity and field validity of a target communication message according to the power industry standard Cyclic Redundancy Check algorithm. It determines whether the message contains format errors by comparing the calculated check value with a preset check value. Format correction involves adjustments to target communication messages that fail the CRC check, including adjusting the field arrangement order, removing redundant bytes, correcting check bits, and adjusting frame length, to ensure the message format conforms to the requirements of older equipment. A target communication message that passes the CRC check is a standardized message that has been confirmed to have no format errors and can be correctly parsed by older power equipment.

[0081] In the specific implementation process, CRC check algorithms and judgment rules matching the old power equipment model and message type are retrieved from the message verification rule base, and the check polynomial, check bit position, and error judgment criteria are clearly defined. Combined with parameters such as frame length and frame interval from the power equipment message transmission parameter database, CRC check is performed on each target communication message, the actual check value of the message is calculated, and compared with the preset check value to determine whether the message passes the check.

[0082] For target communication messages that fail verification, analyze the type of format error. If the error is due to misaligned fields, adjust the field arrangement order. If the frame length exceeds the limit, trim redundant bytes. If the error is due to an abnormal check bit, recalculate and correct the check bit. After format correction, perform CRC verification again until the verification passes.

[0083] All verified target communication messages are transmitted back to the old power equipment through the established bidirectional communication link. The old equipment receives and parses the target communication messages, enabling the transmission of data from the new equipment to the old equipment and completing the communication compatibility between the new and old power equipment.

[0084] For example, CRC16 check rules adapted to the old equipment are retrieved from the message verification rule library and combined with the 42-byte single-frame maximum length parameter in the power equipment message transmission parameter library to perform CRC verification on the encapsulated target communication message. If a target message frame length of 45 bytes is found, exceeding the maximum frame length, the verification fails. The message format is corrected by trimming 3 redundant bytes, adjusting the frame length to 42 bytes, and the CRC verification is re-executed, which succeeds. All successfully verified target communication messages are sent back to the old backend monitoring and control host. The host successfully parses the message content, enabling real-time monitoring of the new equipment's voltage data and achieving communication compatibility between the old and new equipment. This solution is not limited to adapting to the single CRC16 check rule; the check rule library has an extensible and general architecture, fully covering CRC8, CRC32, and various manufacturers' proprietary custom CRC check modes.

[0085] This step can screen and correct format defects in target communication messages, improve the reliability of message transmission, avoid parsing failures of old devices due to incorrect message formats, ensure stable communication compatibility between new and old power equipment, and guarantee the integrity and effectiveness of the adaptation process.

[0086] Example 2

[0087] Considering that in the actual application of Implementation Example 1, when generating new function point numbers in step 5, the point numbers are mechanically compiled according to the point number definition rules of the old power equipment. The generated new function point numbers only meet the format compliance requirements and do not have the business identity and topology belonging attributes that can be identified by the backend of the old power equipment.

[0088] In actual substation applications, the old power equipment backend distinguishes the business attributes of different equipment and different measurement points through business semantic tags. If the new function point number has no relevant attributes, the old power equipment backend cannot distinguish the equipment location and measurement point business type corresponding to the new equipment data. This can easily lead to problems such as mixed compilation of business data ledgers and inability to trace data ownership, which cannot meet the actual needs of refined operation and maintenance of substations.

[0089] To address the aforementioned issues, the process of generating new function point numbers within the communication protocol framework of existing power equipment, in conjunction with the point number definition rules, includes the following:

[0090] Extract native business semantic tags from the old power equipment backend database. The native business semantic tags include equipment topology ID and measurement point type identifier. Perform semantic matching between the native business semantic tags and the original communication data of the new power equipment to determine the target semantic template with the highest matching degree. Generate a new function point number based on the target semantic template so that the new function point number carries the business attributes that can be identified by the old power equipment backend.

[0091] Among them, the native business semantic tag is a tag information pre-stored in the old power equipment backend database, used to identify the business attributes and topology affiliation of the old equipment measurement points. It includes the equipment topology ID and measurement point type identifier, and is the core basis for the old equipment backend to identify the identity of the measurement points.

[0092] The device topology ID is a core component of the native business semantic tag, used to identify the device location and topology node corresponding to the measurement point, such as the unique identifier of a line or busbar in a substation, ensuring the traceability of the topology attribution of the measurement point. The measurement point type identifier is a component of the native business semantic tag, used to identify the business type of the measurement point, such as telemetry, remote signaling, fault alarm, etc., corresponding to the data type in step 3.

[0093] Semantic matching involves comparing and associating the service characteristics of the original communication data of new power equipment with the native service semantic tags of old equipment to find the tag that best matches the service attributes of the original data. The target semantic template is the native service semantic tag with the highest matching degree with the service attributes of the original communication data of the new power equipment, determined through semantic matching. It serves as the template for generating new function point numbers, ensuring that the new function point numbers carry the corresponding service attributes.

[0094] The native business semantic tags in the background of old power equipment are the core basis for old equipment to identify the business attributes and topology of measurement points. If the new function point number does not carry the attributes corresponding to the tag, the old equipment cannot accurately identify the source and business type of the new equipment data.

[0095] By extracting the native business semantic tags from the old device and semantically matching them with the original data of the new device, a target semantic template is determined. Based on this template, a new function point number is generated, which enables the new function point number to naturally carry the business attributes and topology belonging that can be identified by the old device. This solves the problem of the new point number having no business identity identifier and chaotic data belonging, and improves the accuracy of the adaptation between the old and new devices.

[0096] For example, the database of the old back-end measurement and control host is accessed through a two-way communication link to extract the set of native business semantic tags, where the device topology ID of a certain tag is 1# bus and the measurement point type is identified as telemetry-voltage.

[0097] Step 3 parses the original communication data obtained from the new equipment, which is the telemetry data of the voltage of bus #1. The functional requirement is bus voltage monitoring. The business characteristics of this original data are semantically matched with all tags in the tag set. It is found that the above tag has the highest matching degree with the original data, and this tag is determined as the target semantic template. Following the 8-point numbering definition rules of the old equipment, a new functional point number of 01001001 is compiled based on the target semantic template. The first two digits 01 correspond to the topology ID of bus #1, the middle three digits 001 correspond to the telemetry type identifier, and the last three digits 001 are the measurement point sequence number. This new functional point number carries the business attributes of bus #1 and voltage telemetry, and can be accurately identified by the old equipment backend.

[0098] This embodiment enables the generated new function point number to carry the business attributes and topology affiliation that can be identified by the old power equipment backend, solving the problem of the new function point number having no business identity identifier and chaotic data affiliation in Embodiment 1. It ensures that the old equipment backend can accurately distinguish the source and business type of the new equipment data, avoid the mixing of business data ledgers, and facilitate data traceability and refined operation and maintenance.

[0099] Example 3

[0100] Considering that in practical applications, Example 2 relies solely on single-layer semantic matching based on device topology ID and measurement point type identifier to determine the target semantic template, in actual substation applications, there are often multiple subdivided measurement points of the same type and model under the same topology node. For example, under the same bus or device topology ID, there are multiple subdivided measurement points of the same type, such as voltage, current, and power. In this case, multiple sets of original communication data from new power equipment will match the same target semantic template, making it impossible to accurately distinguish subdivided measurement points. The uniqueness of semantic matching is insufficient, resulting in the generated new function point number not accurately corresponding to the subdivided measurement point, and data confusion will still occur.

[0101] To address the aforementioned issues, this embodiment provides a possible implementation method. Specifically, the step of semantically matching the native business semantic tags with the original communication data of the new power equipment to determine the target semantic template with the highest matching degree includes:

[0102] Extract the business sub-dimensional features attached to the original communication data of new power equipment; perform multi-dimensional weighted semantic coupling matching of the business sub-dimensional features with equipment topology ID and measurement point type identifier; perform matching weight correction and uniqueness identification for conflict scenarios in which multiple sets of original communication data match the same semantic label; after multi-dimensional coupling matching and conflict identification, determine the target semantic template with the highest matching degree.

[0103] It should be noted that the business sub-dimension features are specific features attached to the original communication data of new power equipment and used to distinguish the same type of subdivided measurement points. They include at least the data dimension attributes, sampling rate level and measurement point business sub-classification, and are the core basis for achieving accurate differentiation of subdivided measurement points.

[0104] Data dimension attributes refer to the unit of measurement characteristics of the raw communication data, such as voltage in kV, current in A, and power in kW, used to distinguish subdivided measurement points for different physical quantities. Sampling rate levels are the frequency classifications of the raw communication data acquisition, such as second-level or minute-level, used to distinguish subdivided measurement points with different real-time requirements. Measurement point service subcategories are further subdivided service categories under the same measurement point type, such as voltage, current, and power subcategories under telemetry, used to further distinguish measurement points of the same type.

[0105] Multi-dimensional weighted semantic coupling matching combines business sub-dimensional features with device topology IDs and measurement point type identifiers, assigning different weights to different dimensions. The matching degree is then calculated through weighted averages to achieve accurate semantic matching. Matching weights are importance coefficients for each matching dimension, used to quantify the influence of different dimensions in semantic matching. These weights are set according to objective standards to ensure the reasonableness of the matching results.

[0106] Matching weight correction adjusts the weights of each dimension to ensure the uniqueness of the matching results in conflict scenarios where multiple sets of data match the same semantic tag. Uniqueness identification is the process of further filtering tags with similar matching degrees to determine the unique target semantic template.

[0107] Because single-dimensional semantic matching cannot distinguish subdivided measurement points under the same topology and type, the matching results are not unique. By introducing business sub-dimensional features and constructing a multi-dimensional matching system, and assigning reasonable matching weights to different dimensions, the differences of subdivided measurement points can be accurately characterized. By calculating the matching degree with weights, the accurate identification of subdivided measurement points under the same template can be achieved. For matching conflict scenarios, the uniqueness of the target semantic template is ensured through weight correction and uniqueness identification, solving the problem of insufficient uniqueness of semantic matching in Implementation Example 2, and further improving the accuracy of dot generation.

[0108] For example, the service sub-dimension features of two sets of original communication data from the new equipment are extracted. The first set of data is the telemetry data of the voltage of bus #1, with the unit being kV, the sampling rate level being seconds, and the service sub-category being voltage. The second set of data is the telemetry data of the current of bus #1, with the unit being A, the sampling rate level being seconds, and the service sub-category being current. The native service semantic tags of the old equipment are extracted, one of which has the device topology ID of bus #1 and the measurement point type identifier as telemetry.

[0109] Based on the weighted allocation (device topology ID 0.4, measurement point type 0.3, dimension 0.2, sampling rate 0.1), the weighted matching degree between the first set of data and this label is calculated as 1×0.4+1×0.3+1×0.2+1×0.1=1.0, and the weighted matching degree between the second set of data and this label is 1×0.4+1×0.3+0×0.2+1×0.1=0.8. The target semantic template for the first set of data is determined to be this label. At the same time, another label is matched for the second set of data, with the measurement point type identifier being telemetry and the service subclass adaptation current, thus achieving accurate differentiation between the two sets of subdivided measurement points and avoiding matching conflicts.

[0110] This implementation method solves the problem of insufficient semantic matching uniqueness in Embodiment 2, and achieves accurate identification of subdivided measurement points under the same topology and type. It ensures that each set of original data corresponds to a unique target semantic template, and the generated new function point number can accurately correspond to the subdivided measurement point, further avoiding data confusion and improving the fineness of the adaptation between new and old equipment.

[0111] Considering that most of the field-adapted devices are low-power embedded edge hardware with limited CPU computing power, they are unable to meet the low latency and high stability requirements of hard real-time services such as relay protection and fault recording.

[0112] To address this technical issue, the native business semantic tags are semantically matched with the original communication data of the new power equipment to determine the target semantic template with the highest matching degree, which includes the following:

[0113] The device topology ID, measurement point type identifier, data quantity attribute, sampling rate level, and measurement point service subclass are divided into two categories. Device topology ID and measurement point type identifier are the essential feature dimensions for matching, while data quantity attribute, sampling rate level, and measurement point service subclass are the feature dimensions for enhancing matching. The basic weight of each dimension is calculated using the information entropy method, with the following formula:

[0114]

[0115] In the formula: For the first The basic weights of each feature dimension; For the first Information entropy of each feature dimension; This represents the total number of feature dimensions involved in the matching.

[0116] Real-time acquisition of adapter CPU load rate Construct CPU load response factor The calculation formula is:

[0117]

[0118] In the formula: CPU load factor; This is the weight decay coefficient; This is the CPU load warning threshold.

[0119] Based on the base weights and CPU load factor, the dynamic weights of each feature dimension are calculated using the following formula:

[0120]

[0121] In the formula: For the first Dynamic weights for each feature dimension; loading factors for matching required feature dimensions. It is always 1.

[0122] Preset pruning threshold When matching enhances the dynamic weights of the feature dimension If the dimension is not specified, it will be removed and will not be included in subsequent matching calculations.

[0123] The new equipment business sub-dimensional features and the old equipment semantic tags are respectively constructed into standardized feature vectors. , The matching degree is calculated using an improved weighted coupling similarity formula:

[0124]

[0125] In the formula: The degree of coupling and matching between the new device data and the semantic tags of the old device; For new equipment data 3D eigenvalues; Semantic tags for older devices 3D eigenvalues; The number of feature dimensions involved in the calculation.

[0126] Only for scenarios where multiple sets of original communication data conflict with the same semantic label due to matching necessary dimensions, matching weight correction and uniqueness identification are performed; conflicts caused by matching enhancement dimensions are directly ignored, reducing computation time.

[0127] The correspondence between the matched test points and the target semantic template is stored in the hash cache. The continuous original communication data of the same test point directly calls the cached results, without having to repeat the entire process of feature extraction, weighted calculation and conflict identification.

[0128] When starting up or changing the device topology, if semantic matching of all measurement points is required, the full set of measurement points is split into several sub-batches and the matching calculation is performed sequentially according to fixed time slices to avoid communication link blockage caused by instantaneous computing power peaks.

[0129] This implementation solves the technical problems of CPU computing power overload, data processing latency jitter, and communication link blockage misjudgment in existing embedded adapters under high concurrency scenarios, and further improves the stability and real-time performance of communication compatibility between new and old devices.

[0130] Example 4

[0131] Considering the above-mentioned practical application, when encapsulating the target communication message in step 6, only the decrypted original communication data is combined and encapsulated with the new function point number. The encapsulated target communication message only carries numerical data and point information, which cannot be adapted to the native alarm association rules built into the old power equipment backend. In the actual application scenario of substations, the old power equipment backend identifies faults and anomalies through the implicit status bit mask of the message status byte field and triggers the corresponding alarm logic. If the target communication message does not carry this implicit status bit mask, the fault and anomaly data generated by the new power equipment cannot trigger the corresponding alarm logic in the old power equipment backend, resulting in the problem of missed fault alarm detection and alarm linkage failure, which cannot meet the actual needs of substation fault monitoring.

[0132] To address the aforementioned technical problems, this embodiment provides another possible implementation method. The encapsulation of the decrypted original communication data and the new function point number into a target communication message according to the old power equipment message transmission standard includes the following:

[0133] Parse the native alarm association rules in the background of the old power equipment to obtain the implicit status bitmask corresponding to the specific fault type; based on the decryption result of the original communication data, call the matching implicit status bitmask, embed the implicit status bitmask into the status byte segment of the target communication message, and generate a target communication message compatible with the alarm logic of the old power equipment.

[0134] It should be noted that the native alarm association rules are built into the backend of the old power equipment and are used to determine the fault type and trigger alarms. They define the correspondence between specific fault types and implicit status bitmasks and are the core basis for triggering alarms on old equipment.

[0135] The implicit status bitmask is a binary code defined in the native alarm association rules to represent a specific fault type. It is stored in the status byte field of the target communication message and is used by legacy equipment to identify fault anomalies. The status byte field is a fixed field in the target communication message, used to store fault status-related information. It is the carrier of the implicit status bitmask, and its position and length are determined by the legacy power equipment message transmission specifications. The target communication message compatible with the legacy power equipment alarm logic is a target communication message that embeds the implicit status bitmask and can be identified by the legacy equipment backend to identify the fault type and trigger the corresponding alarm.

[0136] Because the alarm logic of old power equipment relies on implicit status bitmasks for triggering, the old equipment can only identify the faults and anomalies of the new equipment and trigger the corresponding alarms if the target communication message carries an implicit status bitmask that matches the fault type. By parsing the native alarm association rules of the old equipment, obtaining the correspondence between fault types and implicit status bitmasks, and embedding the matching mask into the message status byte segment, the target communication message can be adapted to the alarm logic of the old equipment. This solves the problems of missed fault alarms and alarm linkage failures, ensuring the effectiveness of substation fault monitoring.

[0137] For example, the native alarm association rules in the old power equipment's backend are parsed to establish a fault type-mask correspondence table. The implicit status bitmask corresponding to a bus overvoltage fault is 00000001, and the implicit status bitmask corresponding to a line overload fault is 00000010. The decrypted raw communication data in step 6 is the data for the #1 bus overvoltage fault. The corresponding table is searched to obtain the matching implicit status bitmask 00000001. According to the old equipment's message transmission specifications, bytes 9-10 of the target communication message are determined to be the status byte segment. The mask 00000001 is embedded in this field. Simultaneously, the plaintext overvoltage fault data is combined with the new function point number 01001001 to encapsulate and generate the target communication message. After receiving this message, the old equipment parses the mask of the status byte segment, identifies the bus overvoltage fault, and triggers the corresponding alarm logic.

[0138] This implementation enables the target communication messages to adapt to the native alarm association rules of the old power equipment backend. The old equipment can identify the faults and anomalies of the new equipment through the implicit status bit mask of the message status byte field, trigger the corresponding alarm logic, solve the problems of missed fault alarms and alarm linkage failure, and improve the timeliness and effectiveness of substation fault monitoring.

[0139] Example 5

[0140] Considering the above, in practical applications, only a single implicit status bitmask corresponding to a single fault can be matched and embedded into the status byte segment of the target communication message. However, in actual substation application scenarios, complex linkage fault conditions often occur, involving line faults, equipment overloads, and overlapping protection actions. That is, a single original communication data simultaneously carries the primary fault and related auxiliary faults. In this case, a single implicit status bitmask can only represent the primary fault; the related auxiliary faults cannot be reflected through status bits. This results in older equipment backends only being able to report the primary fault status, while related auxiliary faults are missed, leading to incomplete alarm information. This fails to provide a comprehensive basis for fault diagnosis and affects the efficiency of substation fault handling.

[0141] To address the aforementioned technical problems, this embodiment provides another possible implementation method, wherein the step of invoking the matching implicit state bitmask based on the decryption result of the original communication data specifically includes:

[0142] The decrypted original communication data is decomposed into fault dimensions to identify single fault conditions and compound linkage fault conditions; all implicit status bit mask resources in the background of old power equipment are traversed for different fault conditions; suitable mask combinations are filtered and collected according to the fault association level; after condition identification and level filtering, the matching implicit status bit mask is obtained.

[0143] Among them, fault dimension decomposition is the process of analyzing the decrypted original communication data, separating all fault types contained in the data, and distinguishing between single fault conditions and compound linkage fault conditions. It is the basis for identifying multiple faults.

[0144] A single fault condition is one where the original communication data carries only one type of fault, such as a bus overvoltage fault. A compound linkage fault condition is one where the original communication data carries two or more related fault types simultaneously, such as a line overload fault superimposed with a protection activation fault.

[0145] The mask combination is a set of multiple implicit state bit masks, selected for complex linkage fault conditions, that correspond one-to-one with each sub-fault. It is used to completely represent all fault types of complex faults. The fault association hierarchy is the primary and secondary relationship of each sub-fault in the complex linkage fault. For example, if the primary fault is line overload, the secondary associated fault is protection action. This hierarchy is used to determine the embedding order of the mask combination.

[0146] Because a single implicit status bitmask cannot fully represent all fault types under complex linkage fault conditions, the alarm information is incomplete. By decomposing the original communication data according to fault dimensions, identifying all sub-fault types, and batch matching multiple sets of corresponding implicit status bitmasks to form mask combinations, a complete representation of all fault information in complex faults can be achieved. Mask combinations are filtered and aggregated according to fault association levels to ensure the rationality of mask embedding.

[0147] For example, fault judgment thresholds are set as follows: voltage exceeding the rated value by 10% is considered an overvoltage fault, current exceeding the rated value by 20% is considered an overload fault, and a protection action signal of 1 is considered a protection action fault. The decrypted original communication data is decomposed into fault dimensions. It is found that the data shows voltage exceeding the rated value by 12%, current exceeding the rated value by 25%, and a protection action signal of 1, indicating a composite linked fault condition. The primary fault is identified as line overload, and the secondary related faults are bus overvoltage and protection action. The old equipment mask resources are traversed, and the mask corresponding to line overload (00000010), bus overvoltage (00000001), and protection action (00000100) are matched in batches. According to the fault association level, such as primary fault first and secondary fault second, these are grouped into mask combinations 00000010, 00000001, and 00000100, and this mask combination is used to embed the message.

[0148] This implementation method can adapt to complex linkage fault conditions, fully identify all sub-fault types, call multiple sets of matching implicit status bit masks, and ensure that the target communication message can fully carry all fault information of the complex fault, providing a comprehensive basis for substation fault investigation and improving fault handling efficiency.

[0149] Considering that the above-mentioned composite linkage fault mask combination scheme is only suitable for ideal scenarios where the number of faults is limited, all are known faults of old equipment, the faults have a strong correlation and do not exceed the limit of the old equipment's mask bit width, in actual complex fault scenarios in substations, there are technical problems such as the limited fixed mask bit width of old equipment leading to mask combination explosion, unknown faults detected by new equipment having no matching mask, and forced combination of non-correlated faults causing parsing errors in old equipment. To solve this technical problem, in another possible implementation, the step of calling the matching implicit status bit mask based on the decryption result of the original communication data includes the following:

[0150] The decrypted raw communication data is broken down by fault dimension to identify single faults and compound linked faults, extract all valid fault types, and construct a fault set. ,in This represents the current number of valid faults. The main fault, to This is a derivative associated fault.

[0151] Based on historical fault statistics of the power system, a fault correlation matrix is ​​constructed to quantify the causal correlation strength between faults and eliminate unrelated interference faults. The calculation formula is as follows:

[0152]

[0153] In the formula: For a fault and degree of association; 、 is the probability of the independent occurrence of the fault; is the probability of the joint occurrence of the faults.

[0154] Preset degree-of-association threshold , When it is determined as a non-associated fault, directly eliminate the low-priority interference items, and only retain the strongly associated faults to participate in the mask combination.

[0155] Use fault tree analysis to sort out the fault physical conduction logic, and automatically distinguish the main fault and the derivative faults according to the top event judgment rules of the fault tree, the fault severity level, the occurrence time sequence, and the influence scope: Determine the top event in the fault tree, that is, the root cause fault, as the main fault; Determine the associated faults that directly cause the main fault to occur as the first-level derivative faults; Determine the associated faults that cause the first-level derivative faults to occur as the second-level derivative faults; At the same time, combine the fault grading rules of the electric power industry standard, the critical fault has a higher priority than the serious fault, and the serious fault is higher than the abnormal fault; Among the faults of the same level, the fault that is triggered first and has a larger influence scope is determined as the main fault;

[0156] Determine the priority sequence in the order of the main fault, the first-level derivative fault, and the second-level derivative fault. The main fault has the highest priority, and the priority of the derivative faults decreases in turn to form an ordered fault sequence.

[0157] Normalize the standard masks of all faults to single-bit placeholders ( ), allocate independent bit fields according to the priority, the main fault occupies the lowest bit, and the derivative faults are allocated to the higher bits in turn to avoid bit field overlap. The displacement rule is:

[0158]

[0159] Where: is the index number of the ordered fault sequence, with a value of , corresponds to the main fault, corresponds to the first-level derivative fault, corresponds to the second-level derivative fault; is the total number of effective faults after screening; is the fault independent bit position allocated in the mask.<>

[0160] Increment the index number and offset to the higher bit in turn. The main fault occupies the lowest bit, and each level of derivative faults is allocated to the higher bits in turn, which mechanismically prevents the overlap of different fault bit fields.

[0161] Priority-weighted mask compression uses bitwise OR operations to merge multiple fault masks, combined with bit field allocation to achieve lossless compression, adapting to older equipment with fixed mask bit widths. (8 bits / 16 bits), the calculation formula is:

[0162]

[0163] In the formula: This is the final embedded implicit state bitmask; This is a bitwise OR operation (the only known bitwise AND operator). This is a logical left shift; This is the normalized value of a single fault bit; Ensure that the mask bit width does not exceed the limit.

[0164] The uniqueness of the compressed mask is verified in real time. When the mask corresponds to multiple fault combinations, the highest bit of the mask is forcibly set as a fuzzy alarm flag. After receiving the signal, the old equipment will automatically report the complex fuzzy fault and prompt manual verification to avoid automatic misjudgment.

[0165] When a new device detects an unknown fault that is not defined in the protocol library of an old device, it maps it to a preset universal composite fault fallback mask. This way, the fault information is neither discarded nor forcibly mapped, which would lead to false alarms. The universal composite fault fallback mask refers to a standard universal fault identifier mask that is predefined by the equipment manufacturer, reserved for a long time, and compatible with all models in the communication protocol and background alarm logic of old power equipment.

[0166] In summary, this implementation method, after fault screening, sorting, bit-domain isolation and compression, conflict verification and fallback processing, obtains a compliant implicit status bitmask, which solves the technical problems of mask combination explosion, fault confusion, loss of main fault characteristics and inability to adapt to unknown faults, and meets the requirements of high reliability and low false alarm of power system fault alarm.

[0167] Example 6

[0168] In the above embodiments, when establishing the mapping relationship between the new function point number and the original communication data in step 5, the historical data archiving partitioning rules of the old power equipment background database were not considered, and the newly generated new function point number was not adapted to the partitioning encoding logic of the old database.

[0169] In practical substation applications, the backend database of old power equipment typically stores historical data in partitions based on rules such as equipment topology, data type, and time. Point number prefixes and database partitions have a fixed mapping logic. If a new function's point number lacks a corresponding point number prefix, the established mapping relationship cannot match the old database partitioning logic. This results in new equipment business data failing to be assigned to the corresponding storage partition, leading to historical data storage errors and the inability to retrieve continuous operating curves in the backend. Consequently, it affects the substation's historical data traceability and equipment operation analysis.

[0170] To address the aforementioned technical problems, this embodiment provides another implementation method, wherein establishing the mapping relationship between the new function point number and the original communication data includes the following:

[0171] The historical data archiving partitioning rules of the old power equipment backend are analyzed to determine the mapping logic between the point number prefix and the database partition; according to the mapping logic, a specific point number prefix is ​​assigned to the new function point number; based on the new function point number assigned a specific point number prefix, a mapping relationship between the new function point number and the original communication data is established.

[0172] It should be noted that the historical data archiving partitioning rules are the rules used by the old power equipment backend database to divide historical data storage partitions. These rules include the partitioning basis, partition coding logic, the correspondence between the dot prefix and the partition, etc., and are used to standardize the storage and management of historical data.

[0173] The dot prefix is ​​the starting part of the new function dot number, composed of a specific code, and has a fixed mapping logic with the old database partitions. It is the core basis for the old database to identify data storage partitions. The mapping logic is a one-to-one correspondence between the dot prefix and each storage partition of the old power equipment backend database, clearly defining the data storage partition corresponding to different dot prefixes, and is used to guide the prefix allocation of new function dot numbers.

[0174] Because the old power equipment's backend database identifies the storage partition corresponding to the data through point number prefixes, if the new function's point number does not have a matching point number prefix, the database cannot determine the data's storage partition, leading to data storage errors. By parsing the historical data archiving partition rules of the old database, determining the mapping logic between point number prefixes and partitions, and assigning corresponding point number prefixes to the new function's point number, the established mapping relationship can be adapted to the old database's storage logic, ensuring that the new equipment's data can be assigned to the corresponding partition.

[0175] For example, parsing the historical data archiving partitioning rules of the old power equipment backend database reveals that the database is partitioned according to equipment topology. Bus #1 corresponds to partition code 01, and Bus #2 corresponds to partition code 02. The point number prefix is ​​consistent with the partition code; that is, prefix 01 corresponds to the Bus #1 partition, and prefix 02 corresponds to the Bus #2 partition. A prefix-partition mapping table is established. Step 3 parses a set of new equipment original communication data, which is Bus #1 voltage telemetry data. The corresponding storage partition is the Bus #1 partition. The matching point number prefix 01 is found in the mapping table, and a new functional point number 01001001 is assigned to the corresponding new functional point number. Based on this new functional point number, a mapping relationship is established with the Bus #1 voltage original data. The old database automatically assigns this data to the Bus #1 storage partition using the point number prefix 01.

[0176] This embodiment adapts the established mapping relationship to the historical data archiving and partitioning rules of the old power equipment backend database. New equipment data can be identified by the old database through the prefix of the new function point number and automatically classified into the corresponding storage partition. This solves the problems of disordered historical data storage and inability to retrieve continuous operating curves, ensuring the continuity and traceability of historical data, and facilitating substation equipment operation analysis and historical data tracing.

[0177] Example 7

[0178] Considering that in practical applications, it is only possible to parse the regular archive partitions that are fixed in the background of old power equipment, determine the mapping logic between the point number prefix and the partition, and assign a fixed point number prefix to the new function point number.

[0179] However, in actual substation applications, temporary operating conditions such as maintenance work and load expansion upgrades exist. In these cases, a new temporary dynamic expansion archive partition is added to the backend of the old power equipment to store business data under these temporary operating conditions. The fixed point number prefix in Implementation Example 6 cannot be adapted to the newly added temporary dynamic partition code, causing the new equipment business data under temporary operating conditions to be unable to be properly classified into the temporary partition and can only be written to the default partition. This results in a disconnect between the historical data of the regular partition and the temporary partition, and a discontinuous archiving curve, affecting the management of historical data under temporary operating conditions.

[0180] To address the aforementioned technical problems, this embodiment provides another implementation method. The step of parsing the historical data archiving partitioning rules of the old power equipment backend and determining the mapping logic between the point number prefix and the database partition specifically includes:

[0181] The system periodically polls and traverses the backend of old power equipment, synchronously collecting all rule parameters of fixed regular archive partitions and temporary dynamic expansion archive partitions; it normalizes and merges the static partition rules and dynamic temporary partition rules; iterates and updates the association between partitions and point number prefixes in real time; after full partition collection and rule fusion, it determines the mapping logic between point number prefixes and database partitions.

[0182] Among them, the timed polling is the process by which the adapter periodically accesses the background database of the old power equipment at preset time intervals to collect partition information, which is used to capture partition changes in real time and ensure the timeliness of partition information.

[0183] Fixed, regular archiving partitions are partitions permanently set up in the backend of old power equipment for storing business data under normal operating conditions. Their partitioning rules and coding logic remain unchanged over a long period, such as fixed partitions divided according to equipment topology and data type. Temporary, dynamically expanded archiving partitions are partitions newly added in the backend of old power equipment under temporary operating conditions (such as maintenance or load expansion) for storing temporary business data. Their existence time is consistent with the temporary operating condition, and they can be canceled or retained after the operating condition ends.

[0184] Normalization and fusion refers to the process of unifying and standardizing the rule parameters of fixed regular archive partitions and temporary dynamic expansion archive partitions, eliminating the rule differences between the two types of partitions, and forming a unified partition rule system. Dynamic mapping logic is the real-time updated correspondence between dot prefixes and all archive partitions, such as fixed regular partitions and temporary dynamic partitions, adapting to changes in partition additions and deletions, and ensuring the accuracy of prefix allocation.

[0185] Because the addition of temporary dynamic expansion archive partitions is random, fixed mapping logic cannot adapt to partition changes, leading to temporary data archiving failures. By periodically polling, we can capture partition changes in the backend of older devices in real time and collect all partition information; through normalization and fusion, we can unify the rules for fixed and temporary partitions, avoiding rule conflicts; and by iteratively updating the mapping logic in real time, we ensure that the dot prefix accurately corresponds to all partitions.

[0186] For example, a timed polling threshold is set to 5 minutes per polling session, and the adapter accesses the old power equipment backend database every 5 minutes. When the substation carries out maintenance work on busbar #1, a temporary dynamic expansion archive partition is added to the old backend database. The partition code is 01-T, where T represents temporary, and the corresponding point number prefix is ​​01T. This partition is used to store temporary business data of busbar #1 during the maintenance period. The adapter captures this temporary partition through timed polling, collects its rule parameters, and normalizes and merges them with the rules of fixed regular partitions, such as those with code 01 and prefix 01, to unify the encoding format. The prefix-partition mapping table is updated in real time, and the association relationship between the 01T prefix and the 01-T temporary partition is added.

[0187] When a new device generates temporary data during the maintenance of bus #1, the prefix 01T is assigned to its new function point number according to the dynamic mapping logic, generating a new function point number 01T001001. After the mapping relationship is established, the data is automatically assigned to the 01-T temporary partition to avoid confusion with regular data.

[0188] This embodiment can adapt to the fixed regular partitions and temporary dynamic expansion partitions of the old power equipment backend, capture partition changes in real time, update the mapping logic, solve the problem that the sixth embodiment cannot adapt to temporary partitions and the data archiving is disordered, ensure that the new equipment business data under temporary working conditions can be normally classified into the corresponding temporary partition, ensure the continuity of historical data between regular partitions and temporary partitions, and facilitate the management and traceability of historical data under temporary working conditions.

[0189] Example 8

[0190] Considering that in practical applications, only the one-way transmission and adaptation of monitoring data from the new equipment to the old power equipment has been achieved, the scenario of the old power equipment issuing remote control commands to the new power equipment has not been considered.

[0191] In practical substation applications, older power equipment systems require remote control commands to operate new power equipment, such as switching on / off and adjusting parameters. However, if the new function point number is not registered in the access control logic table of the older power equipment system, remote control commands issued by the older equipment targeting the new function point number will be directly blocked by the older system's security checks and five-prevention interlocking mechanisms. This results in the inability to remotely control the new equipment, even though data can be monitored, thus failing to meet the actual needs of remote substation operation and maintenance.

[0192] To address the aforementioned technical problems, this embodiment provides another implementation method, which further includes, after establishing a bidirectional communication link with the old and new power equipment:

[0193] Obtain the permission interlocking logic table from the background of the old power equipment. The permission interlocking logic table contains a security check code and remote control execution sequence rules. Based on the permission interlocking logic table, generate a remote control permission feature code corresponding to the new function point number. When encapsulating the target communication message in step 6, write the remote control permission feature code into the verification field of the message so that the old power equipment performs security verification based on the remote control permission feature code.

[0194] It should be noted that the permission locking logic table is a rule table built into the background of the old power equipment, used to implement remote control permission security verification. It contains information such as security verification code, remote control execution sequence rules, and range of remotely controllable measurement points. It is the core basis for the old equipment to determine whether the remote control command is legal.

[0195] The security check code is an encoding defined in the access control logic table to verify the legitimacy of remote control commands, ensuring that the remote control commands come from a legitimate source and avoiding misoperation or unauthorized manipulation.

[0196] The remote control execution sequence rules are the order and operational specifications for executing remote control commands as defined in the permission locking logic table. These rules are used to standardize remote control operation procedures and ensure equipment operation safety. The remote control permission feature code is a unique code generated based on the permission locking logic table. It is generated for new function point numbers and is used to pass security verification by older equipment. It corresponds one-to-one with each new function point number and is the core credential for new equipment to receive remote control commands from older equipment.

[0197] The verification field of the message is a fixed field in the target communication message, used to store security verification information. Its position and length are determined by the old power equipment message transmission specifications. The remote control authorization feature code is written into this field and used by the old equipment to verify the remote control authorization of the new equipment.

[0198] Because remote control commands for older power equipment require security verification through an access control logic table before execution, if a new function point number is not registered, the corresponding remote control command will be deemed illegal and blocked. By obtaining the access control logic table of the older equipment, generating a corresponding remote control access permission feature code for the new function point number, and writing it into the message verification field, the new function point number can complete access control registration. The older equipment then verifies the remote control access of the new equipment using the feature code in the verification field, allowing the remote control commands to be issued and executed.

[0199] For example, the permission interlocking logic table of the old power equipment is retrieved through a two-way communication link. The security check code rule is a 6-digit numerical code, the remote control execution sequence rule is verification-confirmation-execution, and the remotely controllable measurement point range includes all remote signaling measurement points. Step 5 generates a new function point number 01001001, corresponding to the 1# bus voltage telemetry measurement point, which can be remotely adjusted. Based on the security check code rule, a remote control permission feature code 123456 is generated for this new function point number. In step 6, when encapsulating the target communication message, according to the old equipment message transmission specification, bytes 43-48 of the message are determined to be the verification field, and the feature code 123456 is written into this field. When the old equipment issues a remote control adjustment command for point number 01001001, the feature code 123456 in the message verification field is parsed and compared with the verification rule in the permission interlocking logic table. After the verification is passed, the remote control command is allowed to be issued to the new equipment, completing the remote adjustment operation.

[0200] This embodiment completes the remote control permission registration for the new function point number, enabling the old power equipment to verify the remote control permission of the new equipment through the remote control permission feature code in the target communication message verification field, allowing the issuance and execution of remote control commands. This solves the problem in the above embodiment that only the data of the new equipment can be monitored but not remotely controlled, and opens up a two-way interactive link between the new and old equipment, meeting the actual needs of remote operation and maintenance of substations and improving operation and maintenance efficiency.

[0201] Example 9

[0202] Considering that in practical applications, only the encapsulation and transmission of business data messages are completed, without matching the inherent online heartbeat detection mechanism of the old power equipment backend.

[0203] In practical substation applications, the backend of older power equipment determines the online status of the equipment by receiving heartbeat messages. If no heartbeat message is received for an extended period, the equipment is considered offline, and the bidirectional communication link is actively disconnected. In the above embodiment, no suitable heartbeat message is sent to the older equipment. The older backend cannot recognize the online status of the new equipment and may mistakenly determine that the new equipment is offline based on its own heartbeat judgment rules, actively disconnecting the bidirectional communication link. This results in unstable communication connections and frequent disconnections, affecting the stability of communication compatibility between the old and new equipment and preventing continuous data transmission.

[0204] To address the aforementioned technical problems, this embodiment provides another implementation method, which further includes the following step in the process of transmitting the verified target communication message back to the old power equipment:

[0205] Extract the native heartbeat semantics identified by the old power equipment backend, the native heartbeat semantics including specific function codes and frame header verification rules; generate exclusive heartbeat messages based on the native heartbeat semantics; insert the exclusive heartbeat messages into the target communication message stream at preset time intervals to maintain the old power equipment backend's online status determination of the new power equipment.

[0206] It should be noted that the native heartbeat semantics are heartbeat message features predefined in the background of old power equipment to identify the online status of the equipment. They include specific function codes and frame header verification rules and are the core basis for old equipment to determine that the equipment is online. The native heartbeat semantics of different models of old equipment are different.

[0207] The function code, a component of the native heartbeat semantics, is an identification field for heartbeat messages. It is used by older devices to distinguish heartbeat messages from service data messages, ensuring the accuracy of heartbeat detection. The frame header verification rules are the verification standards for heartbeat message frame headers defined in the native heartbeat semantics. They are used by older devices to verify the legitimacy of heartbeat messages and avoid misjudgments.

[0208] The dedicated heartbeat message is a heartbeat message generated based on the native heartbeat semantics of the old device and can be recognized by the backend of the old device. Its function code and frame header verification rules are completely consistent with the native heartbeat semantics of the old device, and it is used to report the online status of the new device to the old device.

[0209] The preset time interval is the interval for sending dedicated heartbeat messages, which matches the heartbeat detection interval in the background of the old device. This is used to ensure that the old device can continuously receive heartbeat messages and determine that the new device is online.

[0210] Because the online status determination of older power equipment relies on native heartbeat semantics, the equipment can only be considered online if the received heartbeat message matches this semantics. If an appropriate heartbeat message is not sent, the older equipment will mistakenly determine that the new equipment is offline and disconnect the communication link. By extracting the native heartbeat semantics of the older equipment, generating a dedicated heartbeat message, and inserting it into the target communication message stream at preset intervals, the online status of the new equipment can be continuously fed back to the older equipment. This adapts to the heartbeat detection mechanism of the older equipment, solves the problem of frequent communication link disconnections, and ensures the stability of communication between the new and older equipment.

[0211] For example, the native heartbeat semantics of the old power equipment's backend are extracted through a bidirectional communication link, identifying its specific function code as 0x01, frame header verification rule as CRC8 checksum, and frame structure as a 4-byte frame header + 1-byte function code + 1-byte checksum. Based on this native heartbeat semantics, a dedicated heartbeat message is generated with a frame header of 00010203, a function code of 0x01, and a checksum of 0x0A, ensuring a complete match with the native heartbeat semantics. The old equipment's backend heartbeat detection interval is 10 seconds, and the preset time interval is set to 8 seconds. During the transmission of the target communication message, a dedicated heartbeat message is sent to the old equipment every 8 seconds, synchronously transmitted with the business data message. The old equipment's backend receives the dedicated heartbeat message every 8 seconds, parses the function code and frame header verification rule, confirms that the new equipment is online, and will not actively disconnect the communication link, ensuring a stable communication connection.

[0212] This embodiment adapts to the native heartbeat detection mechanism of the old power equipment backend. By periodically sending dedicated heartbeat messages, it continuously feeds back the online status of the new equipment to the old equipment, solving the problems of frequent communication link disconnection and old equipment misjudging the new equipment as offline in the above embodiment. It ensures the stability of the two-way communication link between the old and new equipment, ensures continuous and stable data transmission, and improves the reliability of communication compatibility between the old and new equipment.

[0213] Example 10

[0214] The communication compatibility adaptation device for new and old power equipment under power grid supervision and control applies the above-mentioned communication compatibility adaptation method for new and old power equipment under power grid supervision and control, including: a resource library pre-configuration module, a two-way communication link establishment module, a raw communication data acquisition and parsing module, an old equipment protocol parsing module, a new function point number generation and mapping module, a data decryption and message encapsulation module, and a message verification and feedback module.

[0215] like Figure 2 As shown, the resource library pre-configuration module stores the device protocol library, data decryption algorithm library, message verification rule library, and power equipment message transmission parameter library. It provides call interfaces to the bidirectional communication link establishment module, old equipment protocol parsing module, data decryption and message encapsulation module, and message verification and feedback module, and provides transmission parameters such as protocol scripts, decryption algorithms, verification rules, baud rate / frame interval in real time.

[0216] like Figure 2 As shown, the pre-configuration module of the bidirectional communication link establishment module calls the baud rate, communication port, frame interval and other parameters of the power equipment message transmission parameter library to complete the handshake establishment of the bidirectional communication link with the new and old power equipment. After the link is established, it connects to the original communication data acquisition and parsing module to provide a channel for acquiring the original communication data of the new power equipment, and connects to the message verification and return module to provide a channel for sending back the verified target communication message to the old power equipment.

[0217] like Figure 2 As shown, the original communication data acquisition and parsing module establishes the channel built by the bidirectional communication link module, and collects the original communication data sent by the new power equipment in real time. After completing the parsing of data type, functional requirements, data acquisition frequency and encryption status, the parsed four-dimensional feature parameters are output to the new function point number generation and mapping module as the input basis for point number generation.

[0218] like Figure 2 As shown, after the old equipment protocol parsing module obtains the old power equipment information, it retrieves the matching protocol script from the equipment protocol library of the resource library pre-configuration module, and parses it to obtain three types of rule parameters: old power equipment communication protocol framework, point number definition rules, and message transmission specifications. The point number definition rules and communication protocol framework are output to the new function point number generation and mapping module, and the message transmission specifications are output to the data decryption and message encapsulation module as the format basis for message encapsulation.

[0219] like Figure 2 As shown, the new function point number generation and mapping module receives the data type, functional requirements, and data acquisition frequency characteristics output by the original communication data acquisition and parsing module, and receives the communication protocol framework and point number definition rules output by the old device protocol parsing module. It then completes the generation of new function point numbers, establishes a mapping relationship between the new function point numbers and the original communication data, and synchronously outputs the new function point numbers and mapping relationship table to the data decryption and message encapsulation module.

[0220] like Figure 2 As shown, the data decryption and message encapsulation module calls the matching decryption algorithm from the data decryption algorithm library from the resource library pre-configuration module, receives the message transmission specification output by the old device protocol parsing module, receives the new function point number and mapping relationship output by the new function point number generation and mapping module, completes the original data decryption and message format encapsulation, and generates the target communication message.

[0221] like Figure 2 As shown, the message verification and feedback module calls the parameters from the message verification rule library and the power equipment message transmission parameter library from the resource library pre-configuration module, receives the target communication message output by the data decryption and message encapsulation module, and after completing CRC verification and format correction, sends the qualified message back to the old power equipment through the communication channel of the bidirectional communication link establishment module.

[0222] The embodiments described above are merely illustrative of specific implementations of the present invention, and while the descriptions are detailed, they should not be construed as limiting the scope of the present invention. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of the present invention, and these modifications and improvements all fall within the scope of protection of the present invention.

Claims

1. A method for communication compatibility adaptation of new and old power equipment under the control of power grid supervision, characterized in that, Includes the following steps: Step 1: Pre-configure the device protocol library, data decryption algorithm library, message verification rule library, and power equipment message transmission parameter library; Step 2: Establish a two-way communication link with both the old and new power equipment; Step 3: Collect raw communication data from the new power equipment, and parse the raw communication data to determine the data type, functional requirements, data collection frequency, and encryption status; Step 4: Based on the equipment information of the old power equipment, retrieve the matching protocol script from the equipment protocol library to determine the communication protocol framework, point number definition rules and message transmission specifications of the old power equipment. Step 5: Based on the data type, functional requirements, and data acquisition frequency, and in conjunction with the point number definition rules, generate new functional point numbers within the communication protocol framework of the old power equipment, and establish a mapping relationship between the new functional point numbers and the original communication data. Step 6: Based on the encryption status of the original communication data, call the matching algorithm from the data decryption algorithm library to complete the decryption process. Based on the mapping relationship, encapsulate the decrypted original communication data and the new function point number into a target communication message according to the old power equipment message transmission standard. Step 7: Retrieve verification rules from the message verification rule library, combine them with the power equipment message transmission parameter library, perform CRC verification on the target communication message, correct the format of the target communication message that fails the verification, and send the target communication message that passes the verification back to the old power equipment to complete the communication compatibility between the new and old power equipment.

2. The communication compatibility adaptation method for new and old power equipment under power grid supervision and control according to claim 1, characterized in that, The process of generating new function point numbers within the communication protocol framework of old power equipment, in conjunction with the point number definition rules, includes the following: Extract native business semantic tags from the old power equipment backend database. The native business semantic tags include equipment topology ID and measurement point type identifier. The native business semantic tags are semantically matched with the original communication data of the new power equipment to determine the target semantic template with the highest matching degree. A new function point number is generated based on the target semantic template, so that the new function point number carries the business attributes that can be identified by the old power equipment backend.

3. The communication compatibility adaptation method for new and old power equipment under power grid supervision and control according to claim 2, characterized in that, The step of semantically matching the native business semantic tags with the original communication data of the new power equipment to determine the target semantic template with the highest matching degree specifically includes: Extract the business sub-dimensional features attached to the raw communication data of new power equipment; Perform multi-dimensional weighted semantic coupling matching between business sub-dimensional features and device topology ID and measurement point type identifier; For conflict scenarios where multiple sets of original communication data match the same semantic tag, the matching weight is corrected and the uniqueness is identified. After multi-dimensional coupling matching and conflict identification, the target semantic template with the highest matching degree is determined.

4. The communication compatibility adaptation method for new and old power equipment under power grid supervision and control according to claim 1, characterized in that, The decrypted original communication data and the new function point number are encapsulated into a target communication message according to the old power equipment message transmission standard. Includes the following: Parse the native alarm association rules in the background of old power equipment to obtain the implicit status bitmask corresponding to specific fault types; Based on the decryption result of the original communication data, the matching implicit status bit mask is invoked, and the implicit status bit mask is embedded into the status byte segment of the target communication message to generate a target communication message compatible with the alarm logic of old power equipment.

5. The communication compatibility adaptation method for new and old power equipment under power grid supervision and control according to claim 4, characterized in that, The step of calling the matching implicit state bitmask based on the decryption result of the original communication data specifically includes: The decrypted raw communication data is broken down by fault dimensions to identify single fault conditions and complex linkage fault conditions. For different fault conditions, iterate through all implicit status bitmask resources in the background of the old power equipment; Filter and aggregate suitable mask combinations according to fault association level; After working condition identification and hierarchical filtering, the matching implicit state bitmask is obtained.

6. The communication compatibility adaptation method for new and old power equipment under power grid supervision and control according to claim 1, characterized in that, The establishment of the mapping relationship between the new function point number and the original communication data includes the following: Analyze the historical data archiving partitioning rules of the old power equipment backend to determine the mapping logic between the point number prefix and the database partition; According to the mapping logic, a specific dot prefix is ​​assigned to the new function dot number; Based on the new function point number assigned a specific point number prefix, a mapping relationship between the new function point number and the original communication data is established.

7. The communication compatibility adaptation method for new and old power equipment under power grid supervision and control according to claim 6, characterized in that, The process of parsing the historical data archiving partitioning rules of the old power equipment backend and determining the mapping logic between the dot prefix and the database partition specifically includes: Periodically poll and traverse the backend of old power equipment to synchronously collect all rule parameters of fixed regular archiving partitions and temporary dynamic expansion archiving partitions; The static partitioning rules and dynamic temporary partitioning rules are normalized, integrated, and streamlined. The association between partitions and period prefixes is updated in real time. After full partition data collection and rule fusion, the mapping logic between the dot prefix and the database partition is determined.

8. The communication compatibility adaptation method for new and old power equipment under power grid supervision and control according to claim 1, characterized in that, After establishing a two-way communication link with both old and new power equipment, the following is also included: Obtain the permission interlocking logic table from the background of the old power equipment, wherein the permission interlocking logic table includes a security check code and remote control execution sequence rules; Based on the aforementioned permission locking logic table, a remote control permission feature code corresponding to the new function point number is generated. When encapsulating the target communication message in step 6, the remote control authorization feature code is written into the verification field of the message so that the old power equipment can perform security verification based on the remote control authorization feature code.

9. The communication compatibility adaptation method for new and old power equipment under power grid supervision and control according to claim 1, characterized in that, The process of sending the verified target communication message back to the old power equipment also includes: Extract the native heartbeat semantics from the background identification of old power equipment. The native heartbeat semantics include specific function codes and frame header verification rules. Generate a unique heartbeat message based on the native heartbeat semantics; The dedicated heartbeat message is inserted into the target communication message stream at preset time intervals to maintain the old power equipment backend's online status determination of the new power equipment.

10. A communication compatibility adapter for new and old power equipment under power grid supervision and control, characterized in that, The communication compatibility adaptation method for new and old power equipment under power grid supervision and control as described in any one of claims 1-9 includes: A resource library pre-configuration module is used to pre-configure a device protocol library, a data decryption algorithm library, a message verification rule library, and a power equipment message transmission parameter library. A two-way communication link establishment module, which is used to establish a two-way communication link with old power equipment and new power equipment; The raw communication data acquisition and parsing module is used to acquire raw communication data from new power equipment and parse the raw communication data to determine the data type, functional requirements, data acquisition frequency and encryption status. The old equipment protocol parsing module is used to retrieve matching protocol scripts from the equipment protocol library based on the equipment information of the old power equipment, and determine the communication protocol framework, point number definition rules and message transmission specifications of the old power equipment. The new function point number generation and mapping module is used to generate new function point numbers within the communication protocol framework of the old power equipment according to the data type, functional requirements and data acquisition frequency, combined with the point number definition rules, and to establish a mapping relationship between the new function point numbers and the original communication data. The data decryption and message encapsulation module is used to call a matching algorithm from the data decryption algorithm library to complete the decryption process according to the encryption status of the original communication data, and encapsulate the decrypted original communication data and the new function point number into a target communication message according to the old power equipment message transmission specification based on the mapping relationship. The message verification and feedback module is used to retrieve verification rules from the message verification rule library, combine them with the power equipment message transmission parameter library, perform CRC verification on the target communication message, correct the format of the target communication message that fails the verification, and feedback the target communication message that passes the verification to the old power equipment to complete the communication compatibility between the new and old power equipment.

Images