A power cloud chain data fusion method and system
By collecting and cleaning raw data from the power supply cloud chain, establishing a unified data object library and synchronizing its status, the synchronization problem caused by the dispersion of power supply business data was solved. This achieved a closed-loop data processing system that is queryable, statistically accurate, traceable, and interconnected, thereby reducing operational risks.
Patent Information
- Application Number
- CN202611610291.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-10-19
- Publication Date
- 2026-11-17
AI Technical Summary
Existing power business data is scattered across the management backend, mobile terminals, field execution terminals, smart metering equipment, and external systems. The inconsistent object identification makes it difficult to synchronize billing status, equipment status, contract status, and cost status. It also makes it difficult to detect cross-project settlement anomalies, and it is difficult to locate data missing and status conflicts in a timely manner. There are also breakpoints in the flow of maintenance work orders, inconsistent financial statistics, and untimely operational risk warnings.
The system collects raw power supply cloud chain data from the management backend, mobile operation and maintenance terminal, field execution terminal, customer service terminal, smart metering equipment and external business systems, establishes a unified data object library, cleans, matches, deduplicates and synchronizes the status based on object identifiers, generates fused status data, and triggers linkage actions through anomaly detection to output fused results.
It has achieved unified processing of power supply business data, forming a closed loop of industrial big data processing that is queryable, statistical, traceable, and interconnected. It can promptly detect and handle issues such as overdue payments, unsettled accounts, unapproved transactions, status conflicts, and missing data, thereby reducing operational risks.
Smart Images

Figure CN123115245A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of industrial big data technology, and in particular to a power supply cloud chain data fusion method and system. Background Technology
[0002] The field of industrial big data technology involves the collection, storage, comparison, processing, and display of data generated by industrial equipment, business systems, metering terminals, mobile terminals, and external platforms. In scenarios such as power equipment operation and maintenance, energy consumption settlement, contract approval, cost accounting, status monitoring, and mobile querying, it is necessary to synchronize equipment-side status with business-side processes. Traditional power business data processing involves the management backend, terminal input system, metering equipment interface, and external business system recording business data separately, followed by manual verification or single-system reports for querying, statistics, reconciliation, and anomaly alerts.
[0003] Existing power business data is scattered across the management backend, mobile terminals, field execution terminals, smart metering equipment, and external systems. Object identification is inconsistent, and it is difficult to synchronize bill status, equipment status, contract status, approval status, and expense status. Cross-project settlement, anomaly detection, equipment linkage, and mobile queries rely on manual verification. When data is missing, status conflicts occur, or external feedback is delayed, it is difficult to locate the source in a timely manner. This can easily lead to untimely operational risk warnings, inconsistent financial statistics, and breakpoints in the flow of maintenance work orders, making it difficult to form a traceable data loop. Summary of the Invention
[0004] To address the aforementioned technical problems, this invention provides a power cloud chain data fusion method, comprising the following steps: Collect raw power cloud chain data generated by the management backend, mobile operation and maintenance terminal, field execution terminal, customer service terminal, smart metering equipment and external business systems; Establish a unified data object library based on equipment, projects, organizations, users, contracts, expenses, approvals, work orders, and time cycles, and generate object identifiers for objects within the library; Based on object identifiers, the raw data of the power cloud chain is cleaned, matched, deduplicated, merged, and synchronized to generate fused status data. Based on the bill status, device status, contract status, approval status, expense status, and external feedback status, perform anomaly detection on the fusion status data and generate anomaly detection results; Based on the anomaly detection results, preset linkage actions are triggered, and the fusion results are output to the display terminal and the mobile operation and maintenance terminal.
[0005] Furthermore, the raw data from the power supply cloud chain includes management backend data, edge-side business data, metering equipment data, and external system data. Management backend data is generated by the management backend and includes project site information, equipment asset information, power supply contract information, and business approval records. Edge-side business data is generated by mobile maintenance terminals, field execution terminals, and customer service terminals, including work order flow records, customer interaction records, and mobile query records. Metering equipment data is generated by smart metering devices and includes energy consumption metering values, billing status, and equipment on / off status. External system data is transmitted back from external business systems and includes financial settlement data, invoice data, regulatory feedback data, and enterprise resource management data.
[0006] Furthermore, the unified data object repository includes equipment asset objects, service contract objects, energy consumption bill objects, smart metering objects, operation and maintenance approval objects, financial settlement objects, customer profile objects, and industrial operation statistics objects. Equipment asset objects and smart metering objects are associated through equipment codes, service contract objects and energy consumption bill objects are associated through user codes and contract periods, and operation and maintenance approval objects are associated with work order numbers. The results of these associations constitute an object relationship table, which is used as the read object for cross-source matching.
[0007] Furthermore, when generating object identifiers for objects in the unified data object database, the project code, organization code, user code, equipment code, cost cycle, and work order number are extracted as identifier fields. Original records lacking identifier fields are written to the record to be verified, using the data source and receipt time as the retrieval keys. After the identifier fields are completed, the record to be verified is updated, and the updated record is written back to the unified data object database. Records whose identifier fields cannot be completed are kept in isolated storage and are not used as status synchronization inputs.
[0008] Furthermore, when cleaning, matching, deduplicating, merging, and synchronizing the original power supply cloud chain data, the original power supply cloud chain data first undergoes field integrity verification and data source verification. Records that pass the verification and have the same object identifier and time period are compared by field comparison. Records with identical field values are merged into object fusion records, while records with inconsistent field values are written into conflict records. Records to be synchronized are determined from the conflict records according to the receipt time and business confirmation status, and the fusion status data is updated with these records. Object fusion records, conflict records, and updated fusion status data are stored separately for use in anomaly detection and display output.
[0009] Further, the anomaly detection includes comparing the status fields in the fused status data with preset status rules, where the preset status rules are configured by the management backend and include anomaly conditions of arrears, unsettled accounts, pending approval, inconsistency between device status and bill status, unsynchronized external return, and missing data. When a status field hits any anomaly condition in the preset status rules, an anomaly detection result carrying the anomaly type, anomaly object identifier, triggering status field, data source and generation time is generated; When the status field does not hit any anomaly condition in the preset status rules, the corresponding fused status data is marked as a synchronization completed status.
[0010] Further, when triggering a preset linkage action according to the anomaly detection result, the anomaly type and anomaly object identifier in the anomaly detection result are read. When the anomaly type is arrears or unsettled accounts, a fee processing task is generated and pushed to the mobile operation and maintenance terminal; When the anomaly type is pending approval, an approval reminder task is generated and written into the management backend; When the anomaly type is inconsistency between device status and bill status, a device control instruction is generated and sent to the smart metering device; When the anomaly type is unsynchronized external return or missing data, a data correction task is generated, and the processing track of the anomaly object identifier is retained.
[0011] Further, when fusing financial settlement data, the energy consumption fee bill object, service contract object and financial settlement object are associated according to the project code, user code, contract period and fee period. Actual receipt records are generated based on the cash basis rule, and receivable records are generated based on the accrual basis rule, and the actual receipt records and receivable records are written into the financial statistical data. The financial statistical data is synchronously verified with the bill data and enterprise resource management data, and layered financial statements divided by project, organization, customer and fee period are output.
[0012] Further, when outputting the fusion result to the display terminal and the mobile operation and maintenance terminal, the fusion result includes project site information, device node coordinates, customer profile data, energy consumption fee statistical data, operation and maintenance statistical data, and anomaly processing track. The display terminal presents the fusion result by project, organization, device and fee period. The mobile operation and maintenance terminal reads the fusion result according to the permission scope of the logged-in account, and writes the work order feedback generated for the anomaly processing track back to the management backend, and the management backend updates the processing status of the fused status data according to the work order feedback.
[0013] This invention also provides a power cloud chain data fusion system, which is used to implement the above-mentioned power cloud chain data fusion method. The system includes a data acquisition module, an object modeling module, a fusion processing module, an anomaly detection module, and a linkage output module. The data acquisition module is used to collect raw power cloud chain data generated by the management backend, mobile maintenance terminal, field execution terminal, customer service terminal, smart metering equipment, and external business systems. The object modeling module is used to establish a unified data object library and generate object identifiers according to equipment, projects, organizations, users, contracts, expenses, approvals, work orders and time periods; The fusion processing module is used to clean, match, deduplicatize, merge, and synchronize the status of the raw power cloud chain data based on object identifiers, and generate fused status data. The anomaly detection module is used to perform anomaly detection on the fusion status data based on bill status, equipment status, contract status, approval status, expense status, and external feedback status, and generate anomaly detection results. The linkage output module is used to trigger preset linkage actions based on the anomaly detection results and output the fusion results to the display terminal and the mobile operation and maintenance terminal.
[0014] Compared with the prior art, the advantages and positive effects of the present invention are as follows: In this invention, unified data collection from the management backend, mobile operation and maintenance terminal, field execution terminal, customer service terminal, intelligent metering equipment, and external business systems, combined with object identification, unified data object library, and continuous generation of fused status data, enables scattered data to be cleaned, matched, merged, and synchronized in the same object dimension. Through joint detection of bill status, equipment status, contract status, approval status, expense status, and external feedback status, overdue payments, unsettled payments, unapproved payments, status conflicts, data missing, and feedback delays are transformed into executable linkage actions, thereby forming a queryable, statistically accurate, traceable, and linkage-enabled industrial big data processing closed loop. Attached Figure Description
[0015] Figure 1 This is a schematic diagram of the power cloud chain data flow topology; Figure 2 A diagram illustrating the object relationships in a unified data object repository; Figure 3 A schematic diagram of raw data cleaning, matching, and status synchronization for the power cloud chain; Figure 4 This is a schematic diagram illustrating the state transition between anomaly detection and linkage output. Figure 5 This is a schematic diagram of the interaction between modules in the power cloud chain data fusion system. Detailed Implementation
[0016] The following description, in conjunction with the accompanying drawings and embodiments, further illustrates a power supply cloud chain data fusion method and system. In the following embodiments, the power supply cloud chain refers to a data processing link formed around power equipment assets, power supply contracts or service contracts, energy consumption bills, smart metering equipment, operation and maintenance approvals, financial settlements, customer profiles, industrial operation statistics, and project site management. The management backend is used to generate and maintain project site information, equipment asset information, power supply contract information, business approval records, fee rules, and status rules; the mobile operation and maintenance terminal is used to receive fee processing tasks, approval reminder tasks, data correction tasks, and anomaly handling trajectories; the field execution terminal is used to generate work order flow records and field processing feedback; the customer service terminal is used to generate customer interaction records and mobile query records; smart metering equipment is used to generate energy consumption metering values, billing status, and equipment on / off status; and external business systems are used to transmit back financial settlement data, invoice data, regulatory feedback data, and enterprise resource management data. All the above objects are used with a unified name during implementation, and the same name corresponds to the same data object or processing object, without changing meaning due to different display or calling terminals.
[0017] In this invention, the raw power supply cloud chain data refers to unintegrated data generated or transmitted from the management backend, mobile maintenance terminal, field execution terminal, customer service terminal, smart metering equipment, and external business systems. The unified data object library refers to a data storage structure established using equipment, project, organization, user, contract, expense, approval, work order, and time period as basic dimensions. Object identifiers are combinations of identifiers used to identify the same business object or equipment object across multiple data sources. These include at least one of project code, organization code, user code, equipment code, expense period, and work order number, and select a combination of fields that uniquely locates the object based on its business affiliation. Integrated status data refers to the set of statuses formed after the raw power supply cloud chain data has been cleaned, matched, deduplicated, merged, and synchronized. It carries the statuses of bills, equipment, contracts, approvals, expenses, and external transmissions. Anomaly detection results refer to the result objects formed after anomaly detection of the integrated status data, which at least carry the anomaly type, anomaly object identifier, trigger status field, data source, and generation time. The fusion result refers to the data object output to the display terminal and the mobile operation and maintenance terminal, which includes project site information, equipment node coordinates, customer profile data, energy consumption cost statistics, operation and maintenance statistics, and anomaly handling trajectory.
[0018] Example 1 Please see Figure 1-4This embodiment provides a power supply cloud chain data fusion method. In this embodiment, the method uses management backend, mobile operation and maintenance terminal, field execution terminal, customer service terminal, smart metering equipment and external business system as data sources, a unified data object library as the data carrier object, object identifier as the cross-source matching basis, fusion status data as the anomaly detection object, and anomaly detection result as the trigger object for linkage action, thereby forming a continuous processing chain from data acquisition, object modeling, fusion processing, anomaly detection and linkage output.
[0019] S1 collects raw data from the power supply cloud chain.
[0020] In S1, the data acquisition process is handled by the data receiving service, which divides the receiving channels according to the data source. Management backend data is written by the management backend during project creation, equipment registration, contract signing, cost generation, and approval processes. The data receiving service reads project site information, equipment asset information, power supply contract information, and business approval records from this type of data. End-side business data is written by mobile maintenance terminals, field execution terminals, and customer service terminals during work order reception, field processing, customer interaction, and mobile querying. The data receiving service reads work order flow records, customer interaction records, and mobile query records from this type of data. Metering equipment data is reported by smart metering devices at the end of the metering cycle, when billing status changes, or when equipment on / off status changes. The data receiving service reads energy consumption metering values, billing status, and equipment on / off status from this type of data. External system data is transmitted back from external business systems via controlled interfaces. The data receiving service reads financial settlement data, invoice data, regulatory feedback data, and enterprise resource management data from this type of data.
[0021] The data receiving service establishes a receiving record for the received raw power cloud chain data. The receiving record includes the data source, receiving time, data type, and original record index. The data source indicates whether the record originates from the management backend, mobile maintenance terminal, field execution terminal, customer service terminal, smart metering equipment, or external business system; the receiving time is used for time sequence determination in subsequent conflict handling; the data type distinguishes between management backend data, terminal-side business data, metering equipment data, and external system data; the original record index is used to trace back to the corresponding original record in case of conflicting records, missing data, or asynchronous external feedback. After collection, the data receiving service transfers the raw power cloud chain data and receiving record to the object modeling process as input for establishing a unified data object library.
[0022] S2, establish a unified data object library and generate object identifiers.
[0023] In S2, the object modeling process parses the raw power supply cloud chain data output from S1 according to fields such as equipment, project, organization, user, contract, expense, approval, work order, and time period. Field parsing does not change the original meaning of the fields; rather, it groups fields from different data sources that point to the same object into a unified dimension. For example, equipment codes in equipment asset information, equipment codes in metering equipment data, and feedback codes used to identify equipment in external system data are all grouped into the equipment dimension; user codes in power supply contract information, user codes in customer interaction records, and user codes in invoice data are all grouped into the user dimension; and expense periods in energy consumption bill objects, settlement periods in financial settlement objects, and invoicing periods in invoice data are all grouped into time period-related dimensions.
[0024] The unified data object repository includes equipment asset objects, service contract objects, energy consumption bill objects, smart metering objects, operation and maintenance approval objects, financial settlement objects, customer profile objects, and industrial operation statistics objects. Equipment asset objects carry information about power equipment assets and their project ownership; service contract objects carry information about power supply contracts or service contracts and their user ownership; energy consumption bill objects carry information about energy consumption costs, billing cycles, and billing status; smart metering objects carry information about the energy consumption values and on / off status of smart metering devices; operation and maintenance approval objects carry information about approval status and work order numbers; financial settlement objects carry information about actual receipts, accounts receivable, and settlement status; customer profile objects carry information about customer or enterprise ownership, project ownership, and interaction records; and industrial operation statistics objects carry operation statistics, operation and maintenance statistics, and mobile query data.
[0025] The object modeling process generates object identifiers based on the identifiable fields of different objects. For equipment asset objects and smart metering objects, project codes, organization codes, and equipment codes are prioritized for generating object identifiers; for service contract objects and energy consumption bill objects, project codes, user codes, contract periods, and payment periods are used to generate object identifiers; for operation and maintenance approval objects, project codes, organization codes, and work order numbers are used to generate object identifiers; and for financial settlement objects, project codes, user codes, payment periods, and the business number corresponding to the settlement status are used to generate object identifiers. After the object identifiers are generated, they are written into a unified data object database and enter the subsequent cleaning and matching process along with the corresponding objects.
[0026] When the raw data of the power supply cloud chain lacks the identifier field required to generate an object identifier, the object modeling process writes this raw record into a verification record. The verification record includes the data source, reception time, existing fields, missing fields, and the original record index. The data source and reception time serve as the retrieval key for the verification record, used to locate the corresponding record when fields are subsequently filled in. After the identifier field is filled in, the verification record is updated and written back to the unified data object database; records where the identifier field cannot be filled in are isolated and stored. These isolated records are not used as status synchronization input, but their original record index is retained for subsequent data correction tasks. Therefore, subsequent matching, synchronization, and anomaly detection all use data with a clear object identifier as the processing object, avoiding the participation of unidentified objects in status judgment.
[0027] S3 performs cleaning, matching, deduplication, merging, and state synchronization based on object identifiers to generate fused state data.
[0028] In S3, the fusion processing first reads the object identifier, data source, reception time, field set, and status field from the unified data object library. It then performs field integrity checks and data source checks on the raw power cloud chain data. Field integrity checks determine the existence of the object identifier and the necessary status fields corresponding to that data type. Data source checks determine whether the record originates from an already connected management backend, mobile maintenance terminal, field execution terminal, customer service terminal, smart metering device, or external business system. Records that pass the checks proceed to cross-source matching; records that fail the checks are written to pending verification records or isolated storage areas.
[0029] Cross-source matching uses object identifier as the first matching condition and time period as the second matching condition. If two or more records have the same object identifier and the same time period, the fusion process will group these records into the same object group. If the object identifiers are the same but the time periods are different, object groups will be generated separately according to the time periods. If the time periods are the same but the object identifiers are different, they will not be grouped into the same object group. After the object groups are formed, the fusion process will compare the status fields within the object groups. Records with the same field values will be merged into an object fusion record, which includes the object identifier, time period, set of merged fields, source list, and merge time. Records with inconsistent field values will be written into a conflict record, which includes the object identifier, conflicting fields, source list corresponding to the conflicting fields, values of each source field, reception time, and business confirmation status.
[0030] The deduplication process handles duplicate records within an object group that share the same source, object identifier, time period, and field values. The fusion process retains the record with the later reception time as the currently valid record and writes the original record index of the overwritten record into the historical index list of the object fusion records. This historical index list does not participate in anomaly detection but is used to trace the data update process of the same object within the same period. For conflicting records with inconsistent field values, the fusion process determines the record to be synchronized based on the reception time and business confirmation status. When the business confirmation status returned by the management backend or external business system indicates that a record has been confirmed, the confirmed record is used as the record to be synchronized; if no confirmed record exists, the record with the later reception time is used. After the record to be synchronized is determined, the fusion process updates the fusion status data with the record to be synchronized and stores the conflicting record along with the update reason.
[0031] The status synchronization process compares the object fusion record, the record to be synchronized, and the original fusion status data. If the object identifier does not exist in the fusion status data, new fusion status data is generated; if the object identifier already exists, the corresponding billing status, device status, contract status, approval status, expense status, and external feedback status are updated according to the time period. The updated fusion status data is written to the fusion status data table and read by the anomaly detection process. Through the above processing, the fusion status data can reflect the current status of the same object within the same time period, and retains object fusion records and conflict records as auxiliary data for subsequent display and traceability.
[0032] S4, perform anomaly detection based on the fused state data, and generate anomaly detection results.
[0033] In S4, the anomaly detection process reads the status fields from the fusion status data and compares them with preset status rules. These preset status rules are configured by the management backend and include anomalies such as overdue payments, unsettled accounts, unapproved accounts, discrepancies between device status and bill status, unsynchronized external data transmission, and missing data. The overdue payment anomaly condition identifies objects with incomplete payments or overdue payment markers in their expense status; the unsettled accounts anomaly condition identifies financial settlement objects where the expense cycle has been formed but the settlement status is incomplete; the unapproved accounts anomaly condition identifies maintenance approval objects where the approval status is not passed or incomplete; the discrepancy between device status and bill status anomaly condition identifies objects where the device on / off status in smart metering objects is inconsistent with the bill status in energy consumption expense billing objects; the unsynchronized external data transmission anomaly condition identifies objects where the external data transmission status is not updated or the transmission cycle is inconsistent with the local expense cycle; and the missing data anomaly condition identifies objects in the fusion status data where necessary status fields are empty or where pending verification records are missing.
[0034] The anomaly detection process generates a status detection record for each piece of fusion status data. The status detection record includes the object identifier, the status fields involved in the detection, the preset status rules that were hit, the detection time, and the detection conclusion. When any status field matches an anomaly condition, the anomaly detection process generates an anomaly detection result. The anomaly detection result includes the anomaly type, the anomaly object identifier, the triggering status field, the data source, and the generation time. The anomaly type is determined from overdue payment, unsettled, unapproved, inconsistent device status and billing status, unsynchronized external feedback, and missing data. The anomaly object identifier uses the object identifier corresponding to the fusion status data that caused the anomaly. The triggering status field uses the field name and value that matched the preset status rule. The data source uses the source list of the record containing the triggering status field. The generation time uses the time of the anomaly detection process's output result. When no status field matches an anomaly condition, the anomaly detection process marks the corresponding fusion status data as synchronized and writes the status detection record to the detection history.
[0035] When multiple anomaly conditions are simultaneously detected by the same object identifier, the anomaly detection process generates separate anomaly detection results according to the anomaly type. Each anomaly detection result contains the same anomaly object identifier and its corresponding trigger status field. Multiple anomaly detection results do not overwrite each other; instead, they each trigger their corresponding preset actions during the linked output process. This way, when the same device or project has issues related to costs, approvals, data transmission, or missing data, each anomaly type can be tracked independently, and subsequent processing actions can be mapped to the specific source of the anomaly.
[0036] S5 triggers preset linkage actions based on the anomaly detection results and outputs the fusion results.
[0037] In S5, the linkage output process reads the anomaly detection results generated in S4 and determines the preset linkage action based on the anomaly type and anomaly object identifier. The preset linkage action is not a single action name, but rather a combination of the output object, output content, and receiver corresponding to the anomaly type. When the anomaly type is overdue payment or unsettled payment, the linkage output process generates a fee processing task, which includes the anomaly object identifier, fee period, trigger status field, data source, and processing deadline, and pushes the fee processing task to the mobile maintenance terminal. When the anomaly type is unapproved, the linkage output process generates an approval reminder task, which includes the anomaly object identifier, approval status, work order number, and trigger status field, and writes it to the management backend. When the anomaly type is inconsistent device status and bill status, the linkage output process generates a device control command, which includes the anomaly object identifier, device code, current device status, bill status, and command generation time, and sends it to the smart metering device. After receiving the device control command, the smart metering device returns a command reception status, which is written into the anomaly processing track. When the exception type is external return synchronization failure or data missing, the linkage output process generates a data correction task. The data correction task includes the exception object identifier, missing fields, external return status, data source and original record index, and retains the processing trajectory of the exception object identifier.
[0038] The fusion results are generated by the linked output process from fusion status data, object fusion records, conflict records, anomaly detection results, and anomaly handling trajectories. The fusion results include project site information, device node coordinates, customer profile data, energy consumption cost statistics, operation and maintenance statistics, and anomaly handling trajectories. The display terminal shows the fusion results according to project, organization, device, and cost cycle, allowing the status of the same object to be queried across different dimensions. The mobile operation and maintenance terminal reads the fusion results according to the permissions of the logged-in account and writes the work order feedback generated for the anomaly handling trajectory back to the management backend. After receiving the work order feedback, the management backend updates the processing status of the fusion status data according to the processing status, processing time, and processing personnel in the work order feedback, and then passes the updated processing status to the anomaly detection process as input for the next status detection.
[0039] During the operation of this embodiment, the data processing link can be tracked through receiving records, object identifiers, object fusion records, conflict records, fusion status data, anomaly detection results, and anomaly handling trajectories. If the display terminal shows a conflict between the cost status and the device status of a certain device, the anomaly handling trajectory can be traced back to the corresponding anomaly detection result. The anomaly detection result can then locate the triggering status field and data source, and further locate the original power cloud chain data entering the processing link through the original record index. If the mobile maintenance terminal completes the cost processing task or data correction task, the management backend receives the work order feedback and updates the fusion status data, enabling the subsequent anomaly detection process to read the updated processing status. Thus, a continuous closed loop is formed between the data source, processing process, intermediate status, output result, and feedback status.
[0040] Example 2 Please see Figure 5 This embodiment provides a power cloud chain data fusion system. The difference between this embodiment and Embodiment 1 is that the method steps in Embodiment 1 are implemented in a modular collaborative manner. The data acquisition module, object modeling module, fusion processing module, anomaly detection module, and linkage output module respectively undertake the corresponding data input, processing actions, output results, and downstream receivers. The modules are connected through object identifiers, fusion status data, and anomaly detection results.
[0041] The data acquisition module takes as input data from the management backend, mobile maintenance terminal, field execution terminal, customer service terminal, smart metering equipment, and external business systems. The module calls the data receiving service, writes the data source, receiving time, data type, and original record index to the received data, and outputs the power cloud chain raw data and receiving records. The power cloud chain raw data is passed to the object modeling module, and the receiving records are saved as traceability entry points. The data acquisition module does not change the meaning of the fields; its role is to integrate data from different sources into a unified processing chain based on identifiable data source and receiving time.
[0042] The object modeling module takes as input the raw power cloud chain data and received records output by the data acquisition module. It reads fields corresponding to equipment, projects, organizations, users, contracts, expenses, approvals, work orders, and time periods to create equipment asset objects, service contract objects, energy consumption bill objects, smart metering objects, operation and maintenance approval objects, financial settlement objects, customer profile objects, and industrial operation statistics objects. The module generates object identifiers and writes them to a unified data object database. For raw records lacking identifier fields, the module generates a record to be verified; after completing the identifier fields, the record is written back to the unified data object database; records that cannot be completed are stored in isolation. The output of the object modeling module includes the unified data object database, object identifiers, and records to be verified.
[0043] The fusion processing module takes as input the unified data object library and object identifiers output by the object modeling module. The fusion processing module invokes field integrity verification, data source verification, cross-source matching, deduplication and merging, and status synchronization. Field integrity verification identifies the existence of object identifiers and necessary status fields; data source verification identifies whether records originate from an already connected source; cross-source matching groups records with the same object identifier and time period into the same object group; deduplication and merging merges duplicate records with identical field values into a single fusion record; and status synchronization updates the fusion status data with fusion records or records to be synchronized. The fusion processing module outputs object fusion records, conflict records, and fusion status data. The fusion status data is passed to the anomaly detection module, while the object fusion records and conflict records are retained for display and tracing purposes.
[0044] The anomaly detection module takes as input the fusion status data output by the fusion processing module and the preset status rules configured in the management backend. The module reads the bill status, device status, contract status, approval status, expense status, and external feedback status from the fusion status data and compares these status fields with the preset status rules. After comparison, the module outputs a status detection record. If an anomaly condition is met, the module outputs the anomaly detection result; if no anomaly condition is met, the module marks the corresponding fusion status data as synchronized and complete. The anomaly detection result is transmitted to the linkage output module, and the status detection record is written to the detection history.
[0045] The input to the linkage output module is the anomaly detection result output by the anomaly detection module and the fusion status data output by the fusion processing module. The linkage output module generates preset linkage actions based on the anomaly type and anomaly object identifier in the anomaly detection result. The cost processing task is output to the mobile maintenance terminal, the approval reminder task is written to the management backend, the equipment control command is sent to the smart metering device, and the data correction task is written to both the management backend and the mobile maintenance terminal. The linkage output module also forms a fusion result from the fusion status data, object fusion records, conflict records, anomaly detection results, and anomaly processing trajectories, and outputs the fusion result to the display terminal and the mobile maintenance terminal. The display terminal shows the fusion result by project, organization, equipment, and cost cycle; the mobile maintenance terminal reads the fusion result according to the login account's permission scope and writes the work order feedback back to the management backend. After receiving the work order feedback, the management backend updates the processing status of the fusion status data, which serves as the input for the next detection by the anomaly detection module.
[0046] In this embodiment, the system modules and the method steps of Embodiment 1 have corresponding input-output relationships. The data acquisition module corresponds to S1, the object modeling module corresponds to S2, the fusion processing module corresponds to S3, the anomaly detection module corresponds to S4, and the linkage output module corresponds to S5. These modules are not merely listed side-by-side by function name, but rather form a continuous data transmission relationship through raw power supply cloud chain data, object identifiers, a unified data object library, object fusion records, conflict records, fusion status data, anomaly detection results, and fusion results. When the data output by the data acquisition module has not been processed by the object modeling module to generate an object identifier, it does not enter the state synchronization of the fusion processing module; when the fusion processing module has not generated fusion status data, the anomaly detection module does not perform anomaly detection; when the anomaly detection module has not generated an anomaly detection result, the linkage output module does not trigger the preset linkage action. This input-output constraint ensures that the system operation process is consistent with the method implementation process.
[0047] The specific processes, field states, processing order, judgment conditions, parameter sources, module collaboration, and carrier inheritance relationships described in the above embodiments are only used to explain the possible implementations of the present invention and should not limit the present invention to the specific embodiments listed. Without departing from the technical solutions described in the present invention and the technical solutions described in the application documents, any equivalent substitutions, equivalent modifications, equivalent combinations, order adjustments, corresponding module replacements, equivalent changes in field names, equivalent inheritance of the executing entity, or equivalent changes in the carrier form that can be conceived by those skilled in the art should fall within the scope of protection of this patent; however, they should not be extended to unclaimed topics, nor should the substantive correspondence of the technical objects be changed through changes in the drawing names.
Claims
1. A power cloud chain data fusion method, characterized in that, include: Collect raw power cloud chain data generated by the management backend, mobile operation and maintenance terminal, field execution terminal, customer service terminal, smart metering equipment and external business systems; Establish a unified data object library based on equipment, projects, organizations, users, contracts, expenses, approvals, work orders, and time cycles, and generate object identifiers for objects within the library; Based on object identifiers, the original data of the power cloud chain is cleaned, matched, deduplicated, merged, and synchronized in state to generate fused state data; Anomaly detection is performed on the fused status data based on bill status, device status, contract status, approval status, expense status, and external feedback status, and anomaly detection results are generated. Based on the anomaly detection results, a preset linkage action is triggered, and the fused results are output to the display terminal and the mobile operation and maintenance terminal.
2. The power cloud chain data fusion method according to claim 1, characterized in that, The raw data of the power cloud chain includes management backend data, terminal business data, metering equipment data, and external system data; The management backend data is generated by the management backend and includes at least project site information, equipment asset information, power supply contract information, and business approval records; The terminal-side business data is generated by the mobile operation and maintenance terminal, the on-site execution terminal, and the customer service terminal, and includes at least work order flow records, customer interaction records, and mobile query records. The metering equipment data is generated by the smart metering equipment and includes at least energy consumption metering values, billing status, and equipment on / off status. The external system data is transmitted back from external business systems and includes at least financial settlement data, invoice data, regulatory feedback data, and enterprise resource management data.
3. The power cloud chain data fusion method according to claim 2, characterized in that, The unified data object library includes equipment asset objects, service contract objects, energy consumption bill objects, smart metering objects, operation and maintenance approval objects, financial settlement objects, customer profile objects, and industrial operation statistics objects. The equipment asset object is associated with the smart metering object through the equipment code; the service contract object is associated with the energy consumption bill object through the user code and the contract period; and the operation and maintenance approval object is associated with the work order number. The associated results form an object relationship table, which is then used as the reading object for cross-source matching.
4. The power cloud chain data fusion method according to claim 1, characterized in that, When generating object identifiers for objects in a unified data object library, the project code, organization code, user code, equipment code, cost cycle, and work order number are extracted as identifier fields. Write the original record that is missing the identification field into the record to be verified, and use the data source and the receiving time as the retrieval key of the record to be verified; After completing the identification field, update the record to be verified and write the updated record back to the unified data object database; Records for which the identification field cannot be completed are kept in isolated storage and are not used as status synchronization inputs.
5. The power cloud chain data fusion method according to claim 1, characterized in that, When cleaning, matching, deduplication, merging and synchronizing the original data of the power cloud chain, the original data of the power cloud chain is first subjected to field integrity verification and data source verification. For records that pass the verification and have the same object identifier and time period, perform field comparison. Records with the same field values are merged into object fusion records, and records with different field values are written into conflict records. The record to be synchronized is determined from the conflict record according to the reception time and service confirmation status, and the fusion status data is updated with the record to be synchronized. The object fusion record, the conflict record, and the updated fusion status data are stored separately for use in anomaly detection and display output.
6. The power cloud chain data fusion method according to claim 1, characterized in that, Anomaly detection includes comparing the status field in the fused status data with preset status rules. The preset status rules are configured by the management backend and include anomaly conditions such as overdue payment, unsettled payment, unapproved payment, inconsistency between device status and bill status, unsynchronized external feedback, and missing data. When the status field matches any of the abnormal conditions in the preset status rules, an abnormal detection result is generated, carrying the abnormal type, abnormal object identifier, triggering status field, data source, and generation time. When the status field does not match the abnormal conditions in the preset status rules, the corresponding fusion status data will be marked as synchronization completed.
7. The power cloud chain data fusion method according to claim 6, characterized in that, When a preset linkage action is triggered based on the anomaly detection result, the anomaly type and anomaly object identifier in the anomaly detection result are read. When the anomaly type is overdue payment or unsettled payment, a fee processing task is generated and pushed to the mobile operation and maintenance terminal; When the exception type is "unapproved", an approval reminder task is generated and written to the management backend; When the anomaly type is that the device status is inconsistent with the bill status, a device control command is generated and sent to the smart metering device. When the anomaly type is external return synchronization failure or data missing, a data correction task is generated and the processing trajectory of the anomaly object identifier is retained.
8. The power cloud chain data fusion method according to claim 2, characterized in that, When integrating financial settlement data, energy consumption bill objects, service contract objects, and financial settlement objects are associated according to project code, user code, contract period, and fee period; The actual receipt record is generated based on the cash basis rule, and the accounts receivable record is generated based on the accrual basis rule. The actual receipt record and the accounts receivable record are then written into the financial statistics. The financial statistics data are synchronized and verified with invoice data and enterprise resource management data to output hierarchical financial statements divided by project, organization, customer and expense cycle.
9. The power cloud chain data fusion method according to claim 1, characterized in that, When outputting the fusion results to the display terminal and the mobile operation and maintenance terminal, the fusion results include project site information, device node coordinates, customer profile data, energy consumption cost statistics, operation and maintenance statistics, and anomaly handling trajectory; The presentation panel displays the fusion results according to project, organization, equipment, and cost cycle. The mobile operation and maintenance terminal reads the fusion results according to the permissions of the logged-in account and writes the work order feedback generated for the anomaly handling trajectory back to the management backend; The management backend updates the processing status of the fusion status data based on the work order feedback.
10. A power cloud chain data fusion system, the power cloud chain data fusion system corresponding to the power cloud chain data fusion method of claim 1, characterized in that, include: The data acquisition module is used to collect raw power cloud chain data generated by the management backend, mobile operation and maintenance terminal, field execution terminal, customer service terminal, smart metering equipment and external business systems; The object modeling module is used to establish a unified data object library and generate object identifiers according to equipment, projects, organizations, users, contracts, expenses, approvals, work orders and time periods. The fusion processing module is used to clean, match, deduplicate, merge, and synchronize the original data of the power cloud chain based on the object identifier, and generate fused status data. The anomaly detection module is used to perform anomaly detection on the fused status data based on bill status, device status, contract status, approval status, expense status, and external feedback status, and generate anomaly detection results. The linkage output module is used to trigger preset linkage actions based on the anomaly detection results and output the fusion results to the display terminal and the mobile operation and maintenance terminal.
