A method, system, equipment, and medium for monitoring the data flow of automated metering equipment systems.

By generating field-level flow chains and identifying concurrent branch conflicts, conflicting fields in the data flow of metering automation equipment systems are isolated, solving the problem of tracing concurrent conflicts in metering archive fields across multiple systems and ensuring the continuity of the data acquisition path and the accuracy of the data.

CN123115161APending Publication Date: 2026-11-17GUANGXI POWER GRID CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611308472.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-08-27
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

The source of concurrent conflicts in metering archive fields across multiple systems cannot be traced, and the isolation of the entire archive affects normal data collection.

Method used

By acquiring file change records from multiple systems, a field-level flow chain is generated, technical conflicts in concurrent branches are identified, conflicting fields are isolated and freeze commands are sent, trusted preceding events are traced back to generate compensation transactions, the continuity of the acquisition path is verified by simulating execution, and the freeze command is lifted to prevent the spread of errors.

Benefits of technology

It enables the tracing and isolation of file conflicts, avoids the influence of non-conflicting fields, ensures the normal reception of power data and the continuity of the acquisition path, and reduces the risk of erroneous parameter distribution.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123115161A_ABST
    Figure CN123115161A_ABST
Patent Text Reader

Abstract

This invention discloses a method, system, device, and medium for monitoring the flow of archival data in a metrology automation equipment system. It belongs to the field of archival flow monitoring technology and includes: acquiring archival change records from multiple systems for the same metrology automation equipment; converting these records into field change events; generating a flow summary and forming a field-level flow chain based on an interface mapping template; identifying technical association conflicts in concurrent branches based on logical clock values, preceding summary values, and archival semantic constraints; isolating conflicting fields and sending a first freeze command; generating a first compensation transaction by tracing back trusted preceding events; simulating execution to verify the continuity of the acquisition path; submitting the first compensation transaction when the prepared summary is consistent and releasing the freeze command after a consistent readback; otherwise, revoking the first compensation transaction and retaining the field isolation area.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of archival circulation monitoring technology, specifically to a method, system, equipment, and medium for monitoring the circulation of archival data using an automated metering equipment system. Background Technology

[0002] The archival data of metering automation equipment is distributed across multiple business systems, including the power energy acquisition master station, equipment asset system, marketing system, and geographic information system. Each system maintains fields such as equipment physical identifier, communication address, associated distribution transformer, metering point, and acquisition channel. The interface field names and value formats of each system are not entirely consistent. When archival data flows asynchronously through inter-system interfaces, field conversion needs to be performed according to the interface mapping relationship. The master station system generates parameters and issues instructions and acquisition tasks based on the communication address and acquisition channel in the archival data. When errors occur in the archival fields during the transfer process, the erroneous data is read by the master station system, leading to the issuance of erroneous parameters to the physical terminal, causing error detection or data collection anomalies. Current archival management methods mainly employ periodic full-volume comparisons.

[0003] Periodic full comparisons can detect inconsistencies in current file values ​​between systems, but they cannot determine during which interface conversion process the inconsistency occurred. Current methods also cannot distinguish between sequential updates of the same field and concurrent modifications performed by two systems simultaneously. When an entire device file is determined to be abnormal, current methods typically halt the synchronization of the entire file. Stopping the synchronization of the entire device file will block the normal flow of non-conflicting fields and also affect the normal reception of power data. Continuing to synchronize abnormal files may propagate incorrect communication addresses or transformer attribution to downstream systems.

[0004] Directly using archive values ​​from one system to overwrite those from other systems may result in the overwriting of recently completed, legitimate changes. When multiple systems modify the same field simultaneously, existing methods cannot determine the causal relationship between the modifications, relying solely on manual verification, which is time-consuming and prone to errors. Summary of the Invention

[0005] In view of the above-mentioned problems, the present invention provides a method, system, equipment and medium for monitoring the flow of archive data in metering automation equipment systems.

[0006] Therefore, the technical problem solved by this invention is: how to solve the problem that the source of concurrent conflicts in multi-system metering archive fields cannot be traced and that isolation of the entire archive affects normal data collection.

[0007] To solve the above-mentioned technical problems, the present invention provides the following technical solution: a method for monitoring the flow of archive data in a metering automation equipment system, comprising: Obtain file change records for the same automated metering equipment from multiple systems, convert them into field change events, generate a flow summary based on the interface mapping template, and form a field-level flow chain. Based on the logical clock value, the preceding summary value, and the archive semantic constraints, identify technical association conflicts in concurrent branches, isolate conflicting fields, and send the first freeze command; The first compensation transaction is generated by tracing back the trusted preceding events, simulating the execution of the verification collection path continuity, submitting the first compensation transaction when the prepared digest is consistent, and unfreezing the command after reading back the consistency; otherwise, the first compensation transaction is revoked and the field isolation area is retained.

[0008] As a preferred embodiment of the method for monitoring the flow of archive data in a metrology automation equipment system according to the present invention, the step of generating a flow summary and forming a field-level flow chain based on an interface mapping template includes: Obtain the interface mapping template, which includes source fields, target fields, value range conversion rules, null value handling rules, and template version. The template version is used to identify the update status of the interface mapping template. Based on the correspondence between the source field and the target field, the field identifier and field value in the field change event are converted into the target system field identifier and the converted field value; The device physical identifier and source system identifier in the control field change event remain unchanged after the conversion; Generate a first workflow summary based on the field change event summary before conversion, the template version, and the field values ​​after conversion; In response to template version changes, the generated flow summaries in the control field-level flow chain remain unchanged, and the field-level flow chain is expanded based on the first flow summary generated based on the current template version.

[0009] As a preferred embodiment of the method for monitoring the flow of archive data in a metrology automation equipment system according to the present invention, the step of identifying technical correlation conflicts in concurrent branches based on logical clock values, previous summary values, and archive semantic constraints includes: Get the field change events of the same device field in the field-level flow chain, and get the preceding summary value, source system identifier and logical clock value of each field change event; If two field change events have the same preceding digest value, different source system identifiers, and no sequential inclusion relationship between their logical clock values, then the two field change events are determined to be concurrent branches. If the changed values ​​in the concurrent branches are the same after being mapped via the interface, merge the concurrent branches; In response to the different modified values ​​in concurrent branches after interface mapping, the fields corresponding to the different modified values ​​are compared with the file semantic constraints respectively. The fields include the device physical identifier, communication address, the distribution transformer to which it belongs, the metering point and the acquisition channel. The technical association conflict was determined based on the comparison results.

[0010] As a preferred embodiment of the method for monitoring the flow of archive data in a metering automation equipment system according to the present invention, the step of determining technical correlation conflicts based on comparison results includes: Obtain the semantic constraints of the archives, which include the unique constraint of the physical identifier of the equipment, the unique constraint of the communication address within the same acquisition channel, the constraint that the distribution transformer to which the metering point belongs is consistent with the topology version of the geographic information system, and the constraint that the acquisition channel corresponds to the terminal communication interface. Map the fields corresponding to different modified values ​​in the concurrent branches to the device physical identifier, communication address, associated power distribution transformer, metering point, and data acquisition channel, respectively; In response to a violation of the unique constraint of the device's physical identifier or the unique constraint of the communication address within the same acquisition channel, a technical association conflict is identified. In response to a violation of the constraint that the distribution transformer to which the metering point belongs is consistent with the topology version of the geographic information system, a technical association conflict is identified. In response to a violation of the constraint between the acquisition channel and the terminal communication interface, a technical association conflict is identified.

[0011] As a preferred embodiment of the method for monitoring the flow of archive data in a metering automation equipment system according to the present invention, the step of isolating conflicting fields and sending a first freeze command includes: Write the concurrent branches, flow summary, parameter distribution type of the system involved and the impact of the conflict field, and collection task type into the field isolation area; Non-conflicting fields within the same device continue to flow; A first freeze command is generated, which carries the device physical identifier, conflict field identifier and validity period. The first freeze command is used to prevent the distribution of parameters generated by reading the conflict field and the collection task. Send a first freeze command to the metering automation master station. The first freeze command does not prevent the reception of electricity data and the updating of non-conflict file fields.

[0012] As a preferred embodiment of the method for monitoring the flow of archive data in a metering automation equipment system according to the present invention, the step of generating a first compensation transaction by tracing back a reliable preceding event includes: Retrieve events from the conflicting branch forward in the field-level flow chain, and check in turn whether the events satisfy the flow summary continuity, topology version validity, and archive semantic constraints; The most recent event that simultaneously satisfies the requirements of continuous flow digest, valid topological version, and archive semantic constraints is identified as a trusted preceding event; Using the changed value of the trusted preceding event as a baseline, determine the inverse field change of each system's current field value relative to the baseline value; The reverse field changes are arranged in the following order: first, restore the device physical identifier and communication address; then, restore the distribution transformer affiliation and metering point; and finally, restore the data acquisition channel. The first compensation transaction is generated based on the changes in the reversed fields after the arrangement.

[0013] As a preferred embodiment of the method for monitoring the flow of archive data in a metering automation equipment system according to the present invention, the steps of submitting a first compensation transaction when the prepared summary is consistent and unfreezing the command after reading back the consistency, otherwise canceling the first compensation transaction and retaining the field isolation area, include: Send a ready-to-submit instruction to each system, the ready-to-submit instruction carrying a first compensation transaction identifier and a field value to be submitted; Obtain the preparation summary returned by each system. The preparation summary includes the first compensation transaction identifier, the value of the field to be committed, the interface mapping template version, and the expected flow summary. In response to any system preparation timeout, any system interface mapping template version change, or any system expected flow summary inconsistency, all preparation states will be marked as invalid, and the control field isolation area will be retained. In response to the consistency of all prepared summaries, the first compensation transaction is submitted to each system, and a submission summary is generated; Obtain the flow summary read back from each system. If the flow summary read back matches the commit summary, send a freeze release command. If the flow summary read back does not match the commit summary, mark the first compensation transaction as invalid and retain the control field isolation zone.

[0014] This invention provides a monitoring system for the flow of archive data in automated metering equipment systems.

[0015] To solve the above technical problems, the present invention provides the following technical solution: a monitoring system for the flow of archive data of metering automation equipment system, comprising: a change event construction module, used to acquire archive change records of the same metering automation equipment from multiple systems, convert them into field change events containing equipment physical identifier, field identifier, value before change, value after change, source system identifier, topology version, logical clock value and preceding summary value, generate a flow summary according to the interface mapping template and form a field-level flow chain; The conflict identification and freezing module is used to identify technical association conflicts in concurrent branches based on logical clock values, previous summary values ​​and archive semantic constraints, isolate conflicting fields and send the first freeze command; The compensation backtracking and verification module is used to backtrack trusted preceding events to generate the first compensation transaction and simulate the execution of verification and collection path continuity. The commit and unfreeze module is used to commit the first compensation transaction when the prepared digest is consistent and unfreeze the command after the readback is consistent; otherwise, the first compensation transaction is revoked and the field isolation area is preserved.

[0016] The present invention provides a computer device, including a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the steps of the method for monitoring the flow of archive data in a metrology automation equipment system.

[0017] The present invention provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of the method for monitoring the flow of archive data in a metering automation equipment system.

[0018] The beneficial effects of this invention are as follows: This application records the source and conversion path of each field change through a field-level flow chain, enabling file conflicts to be traced back to the specific stage where the conflict occurred. This application distinguishes concurrent branches based on logical clock values ​​and preceding digest values, avoiding misjudging sequential updates as conflicts. This application only isolates conflicting fields, allowing non-conflicting fields to continue flowing, while the main station system can still receive power data. This application generates compensation transactions based on trusted preceding events, simulates execution in the isolation verification area to confirm the continuity of the acquisition path before submission, unfreezes when the prepared digest and readback digest are consistent, and cancels compensation and retains the field isolation area when any step is inconsistent, preventing erroneous files from spreading to downstream systems and reducing the risk of erroneous parameter distribution. Attached Figure Description

[0019] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0020] Figure 1 This is a flowchart of a method for monitoring the flow of archive data in a metering automation equipment system, provided as an embodiment of the present invention.

[0021] Figure 2 This invention provides a method for monitoring the flow of archive data in a metrology automation equipment system, which forms a field-level flow chain.

[0022] Figure 3 This is a schematic diagram illustrating technical conflicts in a method for monitoring the flow of archive data in a metrology automation equipment system, provided as an embodiment of the present invention. Detailed Implementation

[0023] To make the present invention more apparent and understandable, the specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present invention, not all of them. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the protection scope of the present invention.

[0024] Example 1, referring to Figure 1 This is one embodiment of the present invention, which provides a method for monitoring the flow of archive data in a metering automation equipment system, including: S100: Obtain file change records for the same metering automation equipment from multiple systems, convert them into field change events containing equipment physical identifier, field identifier, value before change, value after change, source system identifier, topology version, logical clock value, and preceding summary value, generate a flow summary based on the interface mapping template, and form a field-level flow chain; S200: Identify technical association conflicts in concurrent branches based on logical clock value, previous summary value and archive semantic constraints, isolate conflicting fields and send the first freeze command; S300: Backtrack trusted preceding events to generate the first compensation transaction, simulate execution to verify the continuity of the collection path, submit the first compensation transaction when the prepared digest is consistent, and unfreeze the command after reading back the consistency; otherwise, cancel the first compensation transaction and retain the field isolation area.

[0025] It should be noted that the metering automation equipment file data involved in this application is distributed across multiple business systems, including at least the metering automation master station, equipment asset system, marketing system, and GIS system. Due to the different focuses of each system in maintaining the files, fields such as the communication address, associated distribution transformer, metering point, and acquisition channel of the same metering automation equipment may be modified by different systems. To accurately determine the source and causal relationship of each modification during asynchronous processing, step S100 first obtains the file change records for the same metering automation equipment from the file interfaces of each system. Each file change record is broken down into field change events, which include eight elements: equipment physical identifier, field identifier, value before change, value after change, source system identifier, topology version, logical clock value, and preceding summary value. The equipment physical identifier is used to uniquely identify a metering automation device; the field identifier is used to indicate the modified file field; the pre-change value is used to record the old value before the modification; the post-change value is used to record the new value after the modification; the source system identifier is used to mark the system that generated this change; the topology version is used to record the current transformer and line topology status of the GIS system; the logical clock value is used to indicate the order in which events occur within the same system; and the prequence summary value is used to connect the current event with the previous event.

[0026] Specifically, the logical clock value can be implemented using an integer clock. Each time a file change occurs, the corresponding system's logical clock value is incremented by 1, and this is done using the formula... Update the logical clock value of the current event; the preceding summary value is calculated based on the device physical identifier, field identifier, changed value, source system identifier, topology version, and template version of the previous field change event, using a summary function. It means that among them This represents a string that concatenates the elements in a pre-defined order. The calculated preceding summary value is written to the current field change event, thus enabling field change events for the same device field to form a traceable field-level flow chain based on the preceding summary value.

[0027] Furthermore, step S100 performs cross-system transformation of field change events based on the interface mapping template. The interface mapping template specifies the correspondence between source and target fields and the value domain transformation rules. After each transformation, a flow summary is generated, consisting of a summary of the field change event before transformation, the interface mapping template version, and the transformed field value. The flow summary records the complete state before and after a cross-system transformation, connecting adjacent events on the field-level flow chain in a verifiable manner. For example, after the "terminal address" field in the marketing system is transformed by the interface mapping template, it corresponds to the "communication address" field in the metering automation master station. The transformed field value is written into a new field change event, and the flow summary records the summary of the event before transformation, the template version used, and the transformed field value, thus enabling subsequent conflict backtracking to locate the specific transformation stage.

[0028] Step S200 identifies concurrent branches based on logical clock values, preceding summary values, and archival semantic constraints. When two field change events have the same preceding summary value but come from different source systems, and there is no sequential inclusion relationship between their logical clock values, it indicates that the two systems have modified based on the same historical state, and the modification belongs to a concurrent branch. If the changed values ​​in the concurrent branches are the same after interface mapping, it means that the modification results of the two systems are consistent and isolation is not required; if they are different, it is necessary to further determine whether the change violates archival semantic constraints. Archival semantic constraints include the unique constraint of the device physical identifier, the unique constraint of the communication address within the same acquisition channel, the constraint that the distribution transformer to which the metering point belongs is consistent with the GIS topology version, and the constraint that the acquisition channel corresponds to the terminal communication interface. When the field change in the concurrent branch violates any of the above constraints, it is determined that there is a technical association conflict; when there is a technical association conflict, only the conflicting field is placed in the field isolation area, and the non-conflicting fields in the same device can continue to circulate, while a first freeze command is sent to the metering automation master station. The first freeze command carries the device physical identifier, conflict field identifier, and validity period, which is used to prevent the master station from reading the conflict field value to generate parameter distribution or collection tasks, but does not prevent the reception of power data.

[0029] Step S300 is used to complete conflict resolution. It traces back along the field-level flow chain, checking each event sequentially to ensure it meets the requirements of digest continuity, valid topology version, and archive semantic constraints. The most recent event that simultaneously meets all three conditions is identified as a trusted preceding event. Using the changed value of the trusted preceding event as a benchmark, the reverse field changes of each system's current field value relative to the benchmark value are calculated. These reverse field changes are then arranged in the order of first restoring the device physical identifier and communication address, then the distribution transformer affiliation and metering point, and finally the acquisition channel, generating a first compensation transaction. The first compensation transaction is simulated and executed in the isolation verification area according to the interface mapping template to verify that the compensated device physical identifier, communication address, distribution transformer affiliation, metering point, and acquisition channel can form a continuous acquisition path. After successful verification, a prepare-to-submit instruction is sent to each system, and the prepare digests returned by each system are received. When the prepare digests are consistent, the first compensation transaction is submitted, and the freeze instruction is lifted after the flow digest of the fields read back by each system matches the submitted digest. If any system times out, the template version changes, the prepare digest is inconsistent, or the readback digest is inconsistent, the prepared compensation transaction is revoked, and the field isolation area is retained.

[0030] Simultaneously, the entire process forms a closed-loop data flow: field change events, after converging through the field-level flow chain, become the data foundation for concurrency identification and conflict determination; conflict determination results trigger field isolation and freeze commands; freeze commands block the propagation of erroneous values ​​to the main station parameters and the collection tasks; trusted preceding events provide a compensation benchmark; compensation transactions, after the collection path is confirmed to be continuous in the isolation verification area, enter a two-stage submission; the submission results are read back and verified by each system, and if the verification passes, the freeze is lifted; if the verification fails, the isolation area is retained and the transaction is rolled back. There are no logical breaks between the above links, and the output of any link becomes the input of the next link.

[0031] In this embodiment, the semantic constraints of the archives are based on the actual data acquisition path. Duplicate communication addresses can lead to uncertainty in the terminal response object; inconsistencies between the transformer's affiliation and the GIS version can alter the statistical boundaries of the distribution area; and mismatches between the acquisition channel and the terminal interface can cause recall failures. By incorporating these semantic constraints into conflict determination, it is possible to distinguish between two situations: "only field values ​​differ but have no technical consequences" and "changes in field values ​​will affect the acquisition path," thereby avoiding unnecessary isolation of non-substantive conflicts.

[0032] It is understood that the freeze command in the above steps is not limited to a fixed form. The freeze command can be accompanied by a validity period, for example, comparing the current timestamp with the expiration timestamp. The freeze takes effect before the expiration timestamp is exceeded, and the freeze is automatically lifted after the expiration timestamp is exceeded. The specific value of the validity period can be determined by the file maintenance policy, for example, it can be set to 24 hours, 48 ​​hours or 72 hours. If the conflict is still not resolved after the expiration, a new freeze command can be sent again.

[0033] Example 2 Reference Figure 2 As shown, in some embodiments, the step of generating a flow summary and forming a field-level flow chain based on the interface mapping template may further include the following steps: A1. Obtain the interface mapping template, which includes source fields, target fields, value domain conversion rules, null value handling rules, and template version. The template version is used to identify the update status of the interface mapping template. A2. Based on the correspondence between the source field and the target field, convert the field identifier and field value in the field change event into the target system field identifier and converted field value; A3. The device physical identifier and source system identifier in the control field change event remain unchanged after the conversion; A4. Generate the first workflow summary based on the field change event summary before conversion, the template version, and the field values ​​after conversion; A5. In response to template version changes, the generated flow summaries in the control field-level flow chain remain unchanged, and the field-level flow chain is extended based on the first flow summary generated based on the current template version.

[0034] First, the purpose of the interface mapping template is to map fields with inconsistent names and encoding rules between different systems. The interface mapping template includes five components: source field, target field, value conversion rule, null value handling rule, and template version. The source field describes the field name in the system to which the change event currently belongs; the target field describes the field name in the system to which it belongs after conversion; the value conversion rule converts the value of the source field into a value acceptable to the target field; the null value handling rule specifies how to fill null values ​​in the source field; and the template version indicates the update status of the interface mapping template. For example, the device number in the asset system is 16 digits long, while the device number in the marketing system is 12 digits long with a letter at the end. The value conversion rule between the two systems truncates the first 12 digits of the 16-digit number and maps them to the corresponding letter encoding.

[0035] In this application, when performing field conversion, the correspondence between source and target fields in the interface mapping template is first read. Then, the field identifier in the field change event is replaced with the target system field identifier. Simultaneously, the values ​​before and after the change are converted according to the value range conversion rules. The value range conversion rules can be implemented using an enumerated matching table, which records the correspondence between source and target values. When the source value is not in the enumerated matching table, a linear proportional conversion can be used, for example, if the source value range is... The target value range is The converted value is given by the formula. Calculated.

[0036] Furthermore, after the value domain conversion is completed, the converted field change event still retains the original device physical identifier and source system identifier. The device physical identifier is used to identify the same device in different systems, and the source system identifier is used to trace the source of this change. These two identifiers do not change with the conversion of field names and field values, ensuring that the device identity and the source of the change are always identifiable during cross-system transmission.

[0037] For example, in a master station field conversion process, the source field is the "terminal communication card number" of the marketing system, the target field is the "communication address" of the master station system, the device physical identifier is the asset number, and the source system identifier is "marketing system". After the conversion is completed, the field identifier becomes "communication address", and the values ​​before and after the change are converted from mixed English uppercase and lowercase to numeric lowercase according to the format rules of the operator's SIM card number, while the asset number and the "marketing system" identifier remain unchanged.

[0038] In addition, step A4 generates a first flow summary. This first flow summary consists of three parts: a summary of the field change event before conversion, a template version, and the field value after conversion. The summary of the field change event before conversion can be calculated using a summary function by taking the field identifier, the changed value, the source system identifier, and the preceding summary value of the event before conversion; the template version is directly taken from the version number of the interface mapping template; and the field value after conversion is the target field value after conversion. This first flow summary is appended to the current field change event, enabling a verifiable intermediate state between adjacent events in the field-level flow chain.

[0039] Specifically, when the interface mapping template version changes, the historical flow summary before the template update remains unchanged. For example, after the template version is upgraded from version 1 to version 2, the historical flow summary generated by the version 1 template is still retained in the corresponding position of the field-level flow chain; the system will not recalculate historical events using the version 2 template, nor will it modify the already formed field-level flow chain. Subsequent field change events generate a new first flow summary based on the version 2 template and connect it to the end of the original flow chain with the preceding summary value. This approach ensures that the historical flow chain is template version-dependent, and the data used when tracing back trusted preceding events is consistent with the mapping rules at the time the event occurred.

[0040] Optionally, the template version number can be formatted as "major version number.minor version number.revision number", such as "2.1.0". The major version number increments when value domain conversion rules undergo compatibility changes; the minor version number increments when only mapping fields are added without altering existing mapping relationships; and the revision number increments when documentation or comments are revised. The template version number can be stored in the metadata area of ​​the interface mapping template and deployed and published along with the template.

[0041] Example 3 Reference Figure 3 As shown, in some embodiments, the step of identifying technical association conflicts in concurrent branches based on logical clock values, prior summary values, and archive semantic constraints may further include the following steps: B1. Obtain field change events for the same device field in the field-level transfer chain, and obtain the preceding summary value, source system identifier, and logical clock value for each field change event; B2. In response to two field change events having the same preceding digest value, different source system identifiers, and no sequential inclusion relationship between the logical clock values, the two field change events are determined to be concurrent branches. B3. If the changed values ​​in the concurrent branches are the same after being mapped via the interface, merge the concurrent branches. B4. In response to different modified values ​​in concurrent branches after interface mapping, the fields corresponding to the different modified values ​​are compared with the file semantic constraints respectively. The fields include the device physical identifier, communication address, the distribution transformer to which it belongs, the metering point and the acquisition channel. B5. Determine the technical association conflicts based on the comparison results.

[0042] It is understandable that "concurrency" in file changes does not mean that two modifications occur at the same physical moment, but rather that two modifications are generated independently based on the same historical state. To accurately identify this causal-level concurrency, step B1 extracts all field change events for the same device field from the field-level flow chain. Each event carries a preceding summary value, a source system identifier, and a logical clock value. The preceding summary value indicates which historical event the event was based on; the source system identifier indicates the location where the modification occurred; and the logical clock value indicates the order of events within the same system.

[0043] Specifically, step B2 compares the two field change events pairwise. If the preceding digest value of event A is the same as the preceding digest value of event B, and the source system identifier of event A is different from that of event B, and there is no sequential relationship between the logical clock values ​​of event A and event B, then the two events are identified as concurrent branches. The comparison rule for logical clock values ​​is as follows: if the logical clock value range of event A is... The logical clock value range for event B is: ,when At that time, event A precedes event B; when When event B occurs before event A, and both conditions are not met, it is determined that there is no sequential inclusion relationship between the two events, which is a concurrent branch.

[0044] Furthermore, step B3 compares the modified values ​​of the concurrent branches after interface mapping. The modified values ​​of events A and B are converted according to their respective source system to target system interface mapping templates to obtain values ​​under the target system. If the two converted values ​​are the same, it indicates that although the modifications in the two systems occurred independently, the results are consistent. In this case, the two concurrent branches are merged into one branch, and further conflict determination is not performed. This merging operation avoids invalid isolation caused by concurrent identical values.

[0045] For example, the marketing system changes the communication address to "13800001111", and the asset system also changes the communication address of the same terminal to "13800001111". The two events are generated concurrently based on the same preceding event, but the target field values ​​after conversion are completely identical. In this case, after merging the branches, it can be considered that there is no value conflict.

[0046] On the other hand, when the modified values ​​of concurrent branches differ after interface mapping, step B4 compares the fields corresponding to the different modified values ​​with the semantic constraints of the archive. These fields include the device physical identifier, communication address, associated distribution transformer, metering point, and acquisition channel. The comparison process is performed for each field one by one: for the communication address, it checks whether conflicting values ​​will result in duplicate addresses within the same acquisition channel; for the device physical identifier, it checks whether conflicting values ​​will prevent the device identity from being uniquely determined; for the associated distribution transformer, it checks whether the conflicting values ​​are inconsistent with the GIS topology version; for the acquisition channel, it checks whether the conflicting values ​​do not match the terminal communication interface.

[0047] In another scenario, step B5 determines technical association conflicts based on the comparison results. If the changes to fields involved in the concurrent branch violate any of the aforementioned file semantic constraints, a technical association conflict is determined to exist; if the field changes involved in the concurrent branch do not affect the device acquisition path and device identification, no technical association conflict is determined to exist. For example, if the concurrent branch modifies the device name field, although the device name values ​​are different in the two systems, the device name does not affect the main station parameter distribution and acquisition task addressing, therefore it does not constitute a technical association conflict and does not trigger field isolation.

[0048] Furthermore, all comparison operations in the concurrent branch determination process can be completed by ordinary numerical comparison and string equality judgment. The comparison of the preceding digest value uses string bit-by-bit comparison, the comparison of the logical clock value uses integer range judgment, and the comparison of the source system identifier uses enumerated value equality judgment; the above operations do not involve complex algorithms, and the data flow process can be implemented by database query and memory array traversal.

[0049] Example 4 In some embodiments, determining the technical association conflict based on the comparison results may further include the following steps: C1. Obtain the semantic constraints of the archive, which include the unique constraint of the physical identifier of the device, the unique constraint of the communication address within the same acquisition channel, the constraint that the distribution transformer to which the metering point belongs is consistent with the topology version of the geographic information system, and the constraint that the acquisition channel corresponds to the terminal communication interface. C2. Map the fields corresponding to different modified values ​​in the concurrent branches to the device physical identifier, communication address, distribution transformer, metering point and data acquisition channel, respectively. C3. In response to a violation of the unique constraint of the device's physical identifier or the unique constraint of the communication address within the same acquisition channel, a technical association conflict is determined. C4. In response to the violation of the constraint that the distribution transformer to which the metering point belongs is consistent with the topology version of the geographic information system, a technical association conflict is identified. C5. In response to the violation of the corresponding constraints between the acquisition channel and the terminal communication interface, a technical association conflict is determined.

[0050] It should be noted that the semantic constraints of the archives in this application are used to measure whether changes in the archive fields affect the actual operating path of the metering automation equipment. The actual operating path includes the master station sending parameters to the terminal through the communication address, reading terminal data through the acquisition channel, calculating line loss according to the distribution transformer affiliation, and calculating electricity charges according to the metering point relationship. Step C1 obtains four types of semantic constraints of the archives, among which the unique constraint of the equipment physical identifier is used to ensure that the same equipment has a unique asset number in the multiple systems; the unique constraint of the communication address within the same acquisition channel is used to ensure that multiple terminals do not correspond to the same address when the master station addresses through a specific channel; the constraint that the distribution transformer to which the metering point belongs is consistent with the GIS topology version is used to ensure that the transformer area affiliation of the metering point is consistent with the current topology version of the GIS system; and the constraint that the acquisition channel and the terminal communication interface correspond to each other is used to ensure that the acquisition channel parameters used by the master station match the terminal physical interface.

[0051] In this embodiment, step C2 maps the fields corresponding to different modified values ​​in the concurrent branches to the device physical identifier, communication address, associated distribution transformer, metering point, and data acquisition channel. Field mapping can be completed based on the interface mapping templates of each system. For example, the "User Metering Point Number" field in the marketing system is mapped to the metering point field in the device file, and the "Distribution Transformer Number" field in the asset system is mapped to the associated distribution transformer field. After mapping, each field obtains a standardized field name for comparison with the semantic constraints of the file.

[0052] Meanwhile, step C3 verifies the uniqueness constraints of the device physical identifier and the communication address within the same acquisition channel. The verification process for the uniqueness constraint of the device physical identifier is as follows: the device physical identifier value to be written is entered into the device file table for querying. If another file record using the same device physical identifier already exists in the query results, and the device primary key of that file record is different from the current device's primary key, then the constraint is determined to be violated. The verification process for the uniqueness constraint of the communication address within the same acquisition channel is as follows: the communication address to be written is compared one by one with the communication addresses of all terminals under the current acquisition channel. If a terminal different from the current device uses the same communication address, then the constraint is determined to be violated. This comparison can be implemented through a database unique index or a memory hash table.

[0053] For example, if the marketing system provides a communication address of "13800002222" in a concurrent branch, and another terminal in the asset system under the same acquisition channel is already using this address, then the communication address is no longer unique within the same acquisition channel, and is determined to be a technical association conflict.

[0054] Furthermore, step C4 verifies the consistency between the distribution transformer to which the metering point belongs and the GIS topology version. It obtains the current topology version number of the GIS system. And obtain the distribution transformer attribution value of the metering point record involved in the concurrent branch. ;when and If the transformer number corresponding to the metering point recorded in the database is inconsistent, it is determined that the constraint has been violated. This verification process can call the transformer number field returned by the GIS topology service interface to perform string equality judgment, or it can establish a mapping table between metering points and transformer numbers and perform a lookup in the mapping table.

[0055] In addition, step C5 verifies the correspondence between the acquisition channel and the terminal communication interface. It retrieves the communication interface type recorded in the terminal device file, such as RS485 interface, broadband carrier interface, or wireless public network interface; it retrieves the channel type corresponding to the acquisition channel field in the concurrent branch; and it matches the communication interface type with the acquisition channel type. If the terminal communication interface and acquisition channel type do not match—for example, the terminal only supports a wireless public network interface but the concurrent branch sets the acquisition channel to a broadband carrier channel—then it is determined that the correspondence between the acquisition channel and the terminal communication interface has been violated, and a technical conflict has been identified.

[0056] For example, the verification results of the four types of file semantic constraints are combined to form the basis for determining technical association conflicts. When any constraint is violated, the conflicting field is placed in the field isolation area; the unviolated fields continue to flow; if all constraints are satisfied, the concurrent branches, although having different values, do not affect the acquisition path, and only a normal verification prompt needs to be generated, without the need to freeze parameter distribution.

[0057] Example 5 In some embodiments, isolating the conflicting fields and sending the first freeze command may further include the following steps: D1. Write the concurrent branches, flow summary, parameter distribution type of the system involved and the impact, and collection task type of the conflict field into the field isolation area; D2. Control the continued flow of non-conflicting fields within the same device; D3. Generate a first freeze command. The first freeze command carries the device physical identifier, conflict field identifier and validity period. The first freeze command is used to prevent the distribution and collection of parameters generated by reading the conflict field. D4. Send a first freeze command to the metering automation master station. The first freeze command does not prevent the reception of electricity data and the updating of non-conflict file fields.

[0058] Optionally, the field isolation area is used to store all information about the conflict site, providing a data source for subsequent compensation transactions. Step D1 writes each concurrent branch of the conflict field into the field isolation area. Each concurrent branch records the source system identifier, the value before the change, the value after the change, and the logical clock value; the flow summary of each concurrent branch is also written into the field isolation area to identify the position of each branch on the field-level flow chain; the involved systems are used to record which systems participated in the concurrent branches; the affected parameter distribution type is used to record the parameter distribution actions that the conflict field may drive, such as communication parameter distribution, terminal parameter distribution, and rate parameter distribution; the affected acquisition task type is used to record the acquisition actions that the conflict field may drive, such as power data acquisition, event data acquisition, and curve data acquisition.

[0059] In this embodiment, step D2 controls the continued flow of non-conflicting fields within the same device. Non-conflicting fields refer to fields that have not experienced concurrent branching or, although concurrent branching has occurred, have not caused technical conflicts. These non-conflicting fields continue to be converted and synchronized between systems according to the original interface mapping template, without stopping their flow due to conflicts with other fields. For example, when a communication address field conflicts, non-conflicting fields such as device name, maintenance department, and installation date can still be updated normally; the power data receiving channel remains operational and does not enter a stopped state.

[0060] Further, step D3 generates a first freeze command. This first freeze command carries a device physical identifier, a conflict field identifier, and a validity period. The device physical identifier specifies the object to be frozen, the conflict field identifier specifies the fields that are prohibited from being read, and the validity period specifies the time range within which the freeze takes effect. The specific content of the first freeze command can be represented as a structured data record, including five fields: device physical identifier, field identifier, effective timestamp, expiration timestamp, and command status. The command status is initially "effective," and changes to "expired" when the current timestamp is greater than the expiration timestamp.

[0061] For example, the current timestamp with expiration timestamp The comparison formula is: when At that time, the freeze command is in a valid state; when When the freeze command expires, the freeze command automatically becomes expired. The validity period can be set to 24 hours, 48 ​​hours, or 72 hours from the time of sending; the specific value can be set according to the average time to repair file conflicts. For example, in an operation and maintenance environment with strong fault handling capabilities, the validity period can be set to 24 hours; when cross-departmental coordination is required, the validity period can be set to 72 hours.

[0062] On the other hand, step D4 sends a first freeze command to the metering automation master station. This freeze command only prevents the master station from reading conflicting field values ​​to generate parameter distribution or data acquisition tasks; it does not prevent the master station from receiving the device's power data, nor does it prevent the master station from reading non-conflicting fields for normal file field updates. For example, when the communication address field is frozen, the master station's existing task generation service cannot use this field value to generate new communication parameter distribution tasks; however, the master station can still receive power data such as voltage, current, and power reported by the terminal according to the metering point number, and can still receive changes to non-conflicting fields such as device name and asset number.

[0063] Specifically, the process of sending the first freeze command can reuse the existing command delivery channel, encoding the command into a JSON or XML message and sending it to the main site task generation service via a message queue. Upon receiving the freeze command, the main site task generation service queries the list of conflicting fields in the field isolation zone when generating parameters and collecting tasks. If the required field is not in the list of conflicting fields, the task is generated normally; if the required field is in the list of conflicting fields, the task is skipped and the reason for the interception is recorded.

[0064] Furthermore, if the conflicting field remains unresolved after the freeze command expires, a new freeze command carrying the same device physical identifier and conflicting field identifier can be resent, and the expiration timestamp updated. If the conflicting field has been compensated and unfrozen, the corresponding field's freeze record is removed from the field isolation area. The state transition of the freeze record is guaranteed to be atomic through database transactions.

[0065] Example 6 In some embodiments, the process of generating the first compensation transaction by tracing back the trusted preceding events may further include the following steps: E1. Obtain events in the field-level flow chain from the conflict branch forward, and check in turn whether the events satisfy the flow summary continuity, topology version validity, and archive semantic constraints. E2. The most recent event that simultaneously satisfies the requirements of continuous flow digest, valid topological version, and archive semantic constraints is identified as a trusted preceding event. E3. Using the changed value of the trusted preceding event as a baseline, determine the reverse field change of the current field value of each system relative to the baseline value; E4. Arrange the reverse field changes in the following order: first restore the device physical identifier and communication address, then restore the distribution transformer affiliation and metering point, and finally restore the acquisition channel. E5. Generate the first compensation transaction based on the changes in the reversed fields after the arrangement.

[0066] It should be noted that trusted preceding events serve as the data baseline for compensation transactions, and their selection quality determines the reliability of the repair results. The E1 step starts from the conflict branch and traverses all events forward along the field-level flow chain. For each traversed event, three conditions are checked sequentially: first, the flow digests are continuous, meaning the preceding digest value of the current event is consistent with the flow digest of the previous event, which can be verified using the digest matching formula. Make a judgment, among which The first requirement is that the event's topology version is valid, meaning the event's topology version matches the currently available topology version number in the GIS system. The second requirement is that the event's record satisfies the semantic constraints, meaning that the values ​​of each field in the event record do not violate the four types of constraints: unique physical identifier of the equipment, unique communication address, consistent transformer affiliation, and correspondence between the data acquisition channel and the terminal interface.

[0067] In practical applications, the E2 step selects the event that is closest in time to the current conflicting event from the set of events that meets three conditions as the trusted preceding event. "Closest" can be determined based on the sequence number of the event on the field-level flow chain, with the candidate event having the smallest sequence number difference being the closest trusted preceding event; or it can be determined based on the difference between the event's logical clock value and the current clock value, with the candidate event having the smallest absolute difference being the trusted preceding event.

[0068] Furthermore, step E3 uses the modified value of the trusted preceding event as a baseline value to calculate the inverse field change of each system's current field value relative to the baseline value. The calculation process for the inverse field change is as follows: Let the modified value of the trusted preceding event be... The current value of a certain field in a system is Then the change in the reverse field of the system is .when When the current value is equal to the baseline value, no modification is needed; when... When this occurs, it indicates that the current value of the system deviates from the baseline value, and a field update needs to be performed to change the current field value from the baseline value. Adjust back For string fields, reverse field changes are recorded using a target value replacement method, which records both the name of the field to be updated and the target value to be written.

[0069] For example, if the trusted preceding event baseline value of the communication address field is "13800001111", and the current value of the marketing system is "13800002222", then the reverse field change record will be: field name "communication address", target value "13800001111"; if the current value of the asset system is "13800001111", then the reverse field change record will be: no change required.

[0070] Specifically, step E4 sorts the reverse field changes according to their dependencies. Device physical identifiers and communication addresses belong to the addressing fields, distribution transformer affiliation and metering point belong to the topology fields, and acquisition channels belong to the execution fields. The order of sorting is as follows: first, reverse field changes for device physical identifiers and communication addresses are sorted; then, reverse field changes for distribution transformer affiliation and metering points are sorted; and finally, reverse field changes for acquisition channels are sorted. The sorting logic is as follows: during addressing, the master station first determines the target terminal based on the device physical identifier and communication address, then determines the data collection object based on the distribution transformer affiliation and metering point, and finally determines the communication link based on the acquisition channel; if the preceding fields are not restored, the restoration of the following fields has no practical significance.

[0071] Furthermore, step E5 generates a first compensation transaction based on the rearranged reverse field changes. This first compensation transaction includes a transaction identifier, a device physical identifier, a field update list, and a recovery order description. The field update list includes the field name, target value, involved system, and pre-calculated expected flow summary for each reverse field change. This first compensation transaction is stored as a separate data record for subsequent reading during isolated verification area simulation.

[0072] For example, the list of field updates for the first compensation transaction can be represented as an ordered set. ,in and For address field recovery actions, and For topology field recovery actions, to This is the action to restore the acquisition channel. During the simulation execution in the verification area, the restoration actions for each field are applied sequentially in the order described. After each action is applied, the connectivity status of the acquisition path of the device is recalculated until all fields have been applied.

[0073] Example 7 In some embodiments, the step of submitting the first compensation transaction when the digest is ready to be consistent and unfreezing the command after the readback is consistent, otherwise revoking the first compensation transaction and retaining the field isolation area, may further include the following steps: F1. Send a ready-to-submit instruction to each system, the ready-to-submit instruction carrying the first compensation transaction identifier and the value of the field to be submitted; F2. Obtain the preparation summary returned by each system. The preparation summary includes the first compensation transaction identifier, the value of the field to be committed, the interface mapping template version, and the expected flow summary. F3. In response to any system preparation timeout, any system interface mapping template version change, or any system expected flow summary inconsistency, mark all preparation statuses as invalid and retain the control field isolation area. F4. In response to the consistency of all prepared summaries, the first compensation transaction is submitted to each system, and a submission summary is generated. F5. Obtain the flow summary of each system readback. If the flow summary readback matches the commit summary, send a freeze release command. If the flow summary readback does not match the commit summary, mark the first compensation transaction as invalid and retain the control field isolation zone.

[0074] Understandably, when multiple systems submit compensation transactions, a two-phase process of preparation and commit is used to avoid new data splits caused by each system writing independently. Step F1 sends a prepare-to-commit instruction to each system involved in the conflict. This prepare-to-commit instruction carries the first compensation transaction identifier and the value of the field to be committed. Each system receiving the prepare-to-commit instruction temporarily stores the value of the field to be committed in its local transaction buffer, without directly writing it to the official archive table. Simultaneously, it locks the interface mapping template version within that system to ensure that the same template version is used in both the preparation and commit phases.

[0075] Specifically, step F2 retrieves the preparation summary returned by each system. The preparation summary includes the first compensation transaction identifier, the field value to be committed, the interface mapping template version, and the expected workflow summary. The expected workflow summary is calculated by substituting the field value to be committed into the interface mapping template of that system, calculating the transformed field value, and then concatenating it with the first compensation transaction identifier and the template version to generate the summary. A formula can be used. It means that among them This serves as the identifier for the first compensation transaction. For the field value to be submitted, This refers to the interface mapping template version. The expected workflow summary returned by each system should be consistent, indicating that the expected calculation of the submission status is consistent across systems.

[0076] Furthermore, step F3 handles preparation anomalies. If any system fails to return a preparation summary within the preset response time, it is considered a preparation timeout; if the interface mapping template version returned by any system differs from the version issued with the preparation command, it is considered a template version change; if the expected flow summary returned by any system is inconsistent with the summaries of the other systems, it is considered a summary inconsistency. In any of these cases, all preparation states are marked as invalid, no commit command is sent to any system, and the field isolation zone is preserved, keeping conflicting fields in an isolated protection state. The preset response time can be set to 5 seconds, 10 seconds, or 30 seconds, depending on the interface response performance.

[0077] Step F4 only executes the commit when all prepared summaries are consistent. The first compensation transaction is written to the official archive table of each system, and each system updates the corresponding fields according to the values ​​to be committed. At the same time, a commit summary is generated, which includes the compensation transaction identifier, the commit timestamp, and the final field values ​​written by each system. The commit summary is sent to a common verification location for comparison when each system reads it back.

[0078] In addition, step F5 is used for eventual consistency verification. After the commit is completed, each system reads back the flow summary of the committed fields from its local archive table and compares the read flow summary with the commit summary. When the read flow summary and the commit summary are completely consistent, it means that the compensation transaction has taken effect in each system and no subsequent overwriting has occurred. At this time, a freeze release command is sent to remove the read restriction on the conflicting fields. When the read flow summary of any system is inconsistent with the commit summary, it means that the system has not written the compensation data correctly. At this time, the first compensation transaction is marked as invalid, the field isolation area is reserved, and a retry task record is generated so that compensation can be re-initiated based on trusted preceding events.

[0079] For example, after a system completes a commit, a database write error causes the value of the field to be committed to not be persisted, resulting in a discrepancy between the flow digest and the commit digest during readback. In this case, the compensation transaction is marked as invalid, and the field isolation zone retains the data from the original conflicting branch. Subsequently, the trusted preceding event backtracking process can be re-executed to generate a new compensation transaction until the readback digests of all systems are consistent. Throughout this process, trusted preceding events are not replaced with partial success results, ensuring the correctness of the repair process.

[0080] Example 8 is an embodiment of the present invention, which provides a monitoring system for the flow of archive data in a metering automation equipment system, comprising: The change event construction module is used to obtain the file change records of the same metering automation equipment from multiple systems, convert them into field change events containing equipment physical identifier, field identifier, value before change, value after change, source system identifier, topology version, logical clock value and preceding summary value, generate a flow summary based on the interface mapping template and form a field-level flow chain; The conflict identification and freezing module is used to identify technical association conflicts in concurrent branches based on logical clock values, previous summary values ​​and archive semantic constraints, isolate conflicting fields and send the first freeze command; The compensation backtracking and verification module is used to backtrack trusted preceding events to generate the first compensation transaction and simulate the execution of verification and collection path continuity. The commit and unfreeze module is used to commit the first compensation transaction when the prepared digest is consistent and unfreeze the command after the readback is consistent; otherwise, the first compensation transaction is revoked and the field isolation area is preserved.

[0081] This embodiment also provides a computer device applicable to a method for monitoring the flow of archival data in a metrology automation equipment system, comprising: a memory and a processor; the memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions to implement the method for monitoring the flow of archival data in a metrology automation equipment system as proposed in the above embodiment.

[0082] This embodiment also provides a storage medium on which a computer program is stored. When the program is executed by a processor, it implements a method for monitoring the flow of archive data in a metering automation equipment system as proposed in the above embodiment.

[0083] The storage medium proposed in this embodiment belongs to the same inventive concept as the method for monitoring the flow of archive data in a metering automation equipment system proposed in the above embodiments. Technical details not described in detail in this embodiment can be found in the above embodiments, and this embodiment has the same beneficial effects as the above embodiments.

[0084] Based on the above description of the implementation methods, those skilled in the art can clearly understand that the present invention can be implemented using software and necessary general-purpose hardware, and of course, it can also be implemented using hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as a computer floppy disk, read-only memory (ROM), random access memory (RAM), flash memory, hard disk, or optical disk, etc., including several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods of the various embodiments of the present invention.

[0085] It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention.

Claims

1. A method for monitoring the flow of archive data in a metering automation equipment system, characterized in that, include: Acquire file change records for the same automated metering equipment from multiple systems, convert field change events, generate a flow summary based on the interface mapping template, and form a field-level flow chain; Based on the logical clock value, the preceding summary value, and the archive semantic constraints, identify technical association conflicts in concurrent branches, isolate conflicting fields, and send the first freeze command; The first compensation transaction is generated by tracing back the trusted preceding events, simulating the execution of the verification collection path continuity, submitting the first compensation transaction when the prepared digest is consistent, and unfreezing the command after reading back the consistency; otherwise, the first compensation transaction is revoked and the field isolation area is retained.

2. The method according to claim 1, characterized in that, The steps for generating a flow summary and forming a field-level flow chain based on the interface mapping template include: Obtain the interface mapping template, which includes source fields, target fields, value range conversion rules, null value handling rules, and template version. The template version is used to identify the update status of the interface mapping template. Based on the correspondence between the source field and the target field, the field identifier and field value in the field change event are converted into the target system field identifier and the converted field value; The device physical identifier and source system identifier in the control field change event remain unchanged after the conversion; Generate a first workflow summary based on the field change event summary before conversion, the template version, and the field values ​​after conversion; In response to template version changes, the generated flow summaries in the control field-level flow chain remain unchanged, and the field-level flow chain is expanded based on the first flow summary generated based on the current template version.

3. The method according to claim 2, characterized in that, The steps for identifying technical association conflicts in concurrent branches based on logical clock values, prior summary values, and archive semantic constraints include: Get the field change events of the same device field in the field-level flow chain, and get the preceding summary value, source system identifier and logical clock value of each field change event; If two field change events have the same preceding digest value, different source system identifiers, and no sequential inclusion relationship between their logical clock values, then the two field change events are determined to be concurrent branches. If the changed values ​​in the concurrent branches are the same after being mapped via the interface, merge the concurrent branches; In response to the different modified values ​​in concurrent branches after interface mapping, the fields corresponding to the different modified values ​​are compared with the file semantic constraints respectively. The fields include the device physical identifier, communication address, the distribution transformer to which it belongs, the metering point and the acquisition channel. The technical association conflict was determined based on the comparison results.

4. The method according to claim 3, characterized in that, The steps for determining technical association conflicts based on the comparison results include: Obtain the semantic constraints of the archives, which include the unique constraint of the physical identifier of the equipment, the unique constraint of the communication address within the same acquisition channel, the constraint that the distribution transformer to which the metering point belongs is consistent with the topology version of the geographic information system, and the constraint that the acquisition channel corresponds to the terminal communication interface. Map the fields corresponding to different modified values ​​in the concurrent branches to the device physical identifier, communication address, associated power distribution transformer, metering point, and data acquisition channel, respectively; In response to a violation of the unique constraint of the device's physical identifier or the unique constraint of the communication address within the same acquisition channel, a technical association conflict is identified. In response to a violation of the constraint that the distribution transformer to which the metering point belongs is consistent with the topology version of the geographic information system, a technical association conflict is identified. In response to a violation of the constraint between the acquisition channel and the terminal communication interface, a technical association conflict is identified.

5. The method according to claim 4, characterized in that, The steps of isolating the conflicting fields and sending the first freeze command include: Write the concurrent branches, flow summary, parameter distribution type of the system involved and the impact of the conflict field, and collection task type into the field isolation area; Non-conflicting fields within the same device continue to flow; A first freeze command is generated, which carries the device physical identifier, conflict field identifier and validity period. The first freeze command is used to prevent the distribution of parameters generated by reading the conflict field and the collection task. Send a first freeze command to the metering automation master station. The first freeze command does not prevent the reception of electricity data and the updating of non-conflict file fields.

6. The method according to claim 5, characterized in that, The steps for generating the first compensation transaction by tracing back trusted preceding events include: Retrieve events from the conflicting branch forward in the field-level flow chain, and check in turn whether the events satisfy the flow summary continuity, topology version validity, and archive semantic constraints; The most recent event that simultaneously satisfies the requirements of continuous flow digest, valid topological version, and archive semantic constraints is identified as a trusted preceding event; Using the changed value of the trusted preceding event as a baseline, determine the inverse field change of each system's current field value relative to the baseline value; The reverse field changes are arranged in the following order: first, restore the device physical identifier and communication address; then, restore the distribution transformer affiliation and metering point; and finally, restore the data acquisition channel. The first compensation transaction is generated based on the changes in the reversed fields after the arrangement.

7. The method according to claim 6, characterized in that, The steps for committing the first compensation transaction when the digest is consistent and unfreezing the freeze command after a consistent readback, otherwise reversing the first compensation transaction and preserving the field isolation zone, include: Send a ready-to-submit instruction to each system, the ready-to-submit instruction carrying a first compensation transaction identifier and a field value to be submitted; Obtain the preparation summary returned by each system. The preparation summary includes the first compensation transaction identifier, the value of the field to be committed, the interface mapping template version, and the expected flow summary. In response to any system preparation timeout, any system interface mapping template version change, or any system expected flow summary inconsistency, all preparation states will be marked as invalid, and the control field isolation area will be retained. In response to the consistency of all prepared summaries, the first compensation transaction is submitted to each system, and a submission summary is generated; Obtain the flow summary read back from each system. If the flow summary read back matches the commit summary, send a freeze release command. If the flow summary read back does not match the commit summary, mark the first compensation transaction as invalid and retain the control field isolation zone.

8. A monitoring system for the flow of archive data in a metering automation equipment system, characterized in that, include: The change event construction module is used to obtain the file change records of the same metering automation equipment from multiple systems, convert them into field change events containing equipment physical identifier, field identifier, value before change, value after change, source system identifier, topology version, logical clock value and preceding summary value, generate a flow summary based on the interface mapping template and form a field-level flow chain; The conflict identification and freezing module is used to identify technical association conflicts in concurrent branches based on logical clock values, previous summary values ​​and archive semantic constraints, isolate conflicting fields and send the first freeze command; The compensation backtracking and verification module is used to backtrack trusted preceding events to generate the first compensation transaction and simulate the execution of verification and collection path continuity. The commit and unfreeze module is used to commit the first compensation transaction when the prepared digest is consistent and unfreeze the command after the readback is consistent; otherwise, the first compensation transaction is revoked and the field isolation area is preserved.

9. An electronic device, comprising: Memory and processor; The memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions. When the computer-executable instructions are executed by the processor, they implement the steps of the data flow monitoring method for the metering automation equipment system archives as described in any one of claims 1 to 7.

10. A computer-readable storage medium storing computer-executable instructions that, when executed by a processor, implement the steps of the method for monitoring the flow of archive data in a metering automation equipment system as described in any one of claims 1 to 7.