A low-voltage power grid multi-service subject data sharing integrity processing method and system

Abstract

The application discloses a low-voltage power grid multi-service subject data sharing integrity processing method, comprising the following steps: acquiring power consumption data of different service subjects, interacting the power consumption data with corresponding service systems, setting a data processing period, and processing the power consumption data in the data processing period; synchronizing the processed power consumption data to a power gateway by using an increment to obtain data update information, recording different power consumption data in a label library and marking the label information; and synchronizing the data update information and the label information to the remaining service systems by using a synchronization signal according to the power gateway, and setting a time axis signal to search for power consumption data, so that the data processing efficiency and the data accuracy are improved, and the economic benefit is remarkable.

Description

Technical Field

[0001] This invention relates to the field of low-voltage power distribution network technology, specifically a method and system for processing the integrity of data sharing among multiple business entities in a low-voltage power grid. Background Technology

[0002] The operations of a power grid company are typically completed through the coordinated efforts of one or more departments. At the operational level, multiple business systems exist: low-voltage distribution network areas primarily involve two major areas: electricity marketing and distribution. Marketing and distribution each have specialized departments managing and maintaining different equipment within the area, undertaking different management dimensions. For example, marketing metering focuses on metering-related equipment such as the main meter and user meters; marketing marketing focuses on charging piles, photovoltaics, demand-side management, and load forecasting within the area; and distribution focuses on distribution network management, including distribution network automation, power outage management, and fault repair. With the further refinement of the power grid company's management requirements, a single terminal is required for each distribution area. When everyone has a need for the same type of data, how to achieve data sharing, and how to ensure data consistency during sharing, especially regarding data supplementation and cleaning processes for incomplete or corrupted data, which system should implement these processes, and how to ensure data consistency while reducing computational effort, are urgent problems that power companies need to solve.

[0003] In existing multi-business entity data sharing, data integrity processing is primarily handled by the data-using system, adopting a "whoever uses it is responsible" approach. One drawback of this approach is that after applying different data point replenishment and deduplication cleaning procedures to the same data, discrepancies can arise between systems, leading to confusion for users based on the data analysis results. Since the field acquisition devices are all on a single communication network (HPLC+RF), there's a tendency for simultaneous replenishment of the same / batch of missing data, each performing its own replenishment, which unnecessarily burdens the local communication network. Each professional department has extensive experience and mature solutions for the quality of data from its primary acquisition devices and for replenishment strategies, and also needs to use data from other systems. Currently, each department cleans and processes its own acquired data, relying solely on its own understanding. Because the data with the same defects are consistent, simultaneous replenishment attempts consume HPLC communication bandwidth between the gateway and the devices, and multiple unnecessary duplicate replenishment attempts also increase the performance resources of the gateway and the devices themselves. Furthermore, unprofessional data cleaning and replenishment can result in unreasonable replenished data, causing unnecessary trouble for subsequent data processing. Summary of the Invention

[0004] In view of the above-mentioned problems, the present invention is proposed.

[0005] Therefore, the technical problem solved by the present invention is: the present invention is to solve the problem of data processing and data sharing between electricity consumption data obtained by different business entities corresponding to different business systems in low-voltage power grids.

[0006] To solve the above-mentioned technical problems, the present invention provides the following technical solution:

[0007] In a first aspect, the present invention provides a method for processing the integrity of data sharing among multiple service entities in a low-voltage power grid, comprising:

[0008] Obtain electricity consumption data from different business entities, interact the electricity consumption data with the corresponding business systems, set a data processing cycle, and process the electricity consumption data within the data processing cycle.

[0009] The processed electricity consumption data results are incrementally synchronized to the power gateway to obtain data update information. Different electricity consumption data are recorded in the tag library and tagged.

[0010] The power gateway transmits the data update information and tag information to other business systems using synchronization signals, and sets up time axis signals to search for electricity consumption data.

[0011] As a preferred embodiment of the low-voltage power grid multi-business entity data sharing integrity processing method described in this invention, the method includes: acquiring electricity consumption data from different business entities, and interacting the electricity consumption data with the corresponding business systems, including...

[0012] Application programming interface (API) interaction methods;

[0013] Based on the electricity consumption data, an application programming interface (API) is matched and integrated into the business system, enabling the business system to call the API to upload electricity consumption data.

[0014] In a preferred embodiment of the low-voltage power grid multi-service entity data sharing integrity processing method described in this invention, a data processing cycle is set, and the electricity consumption data is processed within the data processing cycle.

[0015] Data processing is performed on different types of electricity consumption data at different times within the data processing cycle, including data integrity processing and data cleaning.

[0016] The electricity consumption data is cleaned within a set data processing cycle. The cleaned electricity consumption dataset is then processed for data integrity. For missing data, a defect compensation method is selected, and interpolation methods are used to estimate the value of the missing electricity consumption data.

[0017] As a preferred embodiment of the low-voltage power grid multi-service entity data sharing integrity processing method described in this invention, the processed data results are incrementally synchronized to the power gateway to obtain data update information, including:

[0018] Electricity consumption data is synchronized using an application programming interface that follows the REST architecture specification in incremental synchronization.

[0019] After processing the electricity consumption data, the electricity consumption data that needs to be synchronized is packaged into JSON format and sent to the application programming interface of the power gateway in the REST architecture specification via an HTTP POST request.

[0020] A data synchronization anomaly handling mechanism is constructed, which adopts a data rollback approach. When an anomaly occurs during the power consumption data synchronization process, the synchronized power consumption data is rolled back and the synchronization operation is performed again.

[0021] As a preferred embodiment of the low-voltage power grid multi-service entity data sharing integrity processing method described in this invention, the method includes: recording and tagging different electricity consumption data in a tag library, including...

[0022] The business system replenishes and cleans the daily frozen electricity consumption data at the first moment of each day, and after the processing is completed, it adds the first tag information to the daily frozen electricity consumption data;

[0023] At the second hour of each day, the electricity consumption data or minute-level data within the set time period of the previous day is supplemented and dirty data is cleaned and deduplicated. After processing, the electricity consumption data or minute-level data within the set time period is tagged with a second label.

[0024] At the third hour of each day, the loop impedance data from the previous day is supplemented and dirty data is cleaned and deduplicated. After processing, the loop impedance data is labeled with the third tag information.

[0025] As a preferred embodiment of the low-voltage power grid multi-service entity data sharing integrity processing method of the present invention, wherein: based on the power gateway, the data update information and tag information are transmitted to other service systems using a synchronization signal, including,

[0026] The first, second, and third tag information and the update information are respectively labeled with corresponding synchronization tags. Different command values ​​are set according to different tag information. When the corresponding command value is entered, the corresponding tag information and data update information will be synchronized to the other business systems. The other business systems include the prediction and planning system and the customer service system.

[0027] As a preferred embodiment of the low-voltage power grid multi-service entity data sharing integrity processing method described in this invention, the method includes: setting a time axis signal to search for electricity consumption data, including...

[0028] A time axis signal is added to the second tag information, and a time command is set. After the electricity consumption data or minute-level data is tagged with the second tag information, the second tag information within the corresponding time period can be found by inputting the time axis command value.

[0029] Secondly, this invention provides a system for processing the integrity of data sharing among multiple service entities in a low-voltage power grid, comprising:

[0030] The data processing module is used to acquire electricity consumption data of different business entities, interact the electricity consumption data with the corresponding business system, set a data processing cycle, and process the electricity consumption data within the data processing cycle.

[0031] The recording and tagging module is used to incrementally synchronize the processed electricity consumption data results to the power gateway to obtain data update information, and to record and tag different electricity consumption data in the tag library.

[0032] The data synchronization module is used to transmit the data update information and tag information to other business systems using synchronization signals based on the power gateway, and to set time axis signals to search for electricity consumption data.

[0033] Thirdly, the present invention provides a computing device, comprising:

[0034] Memory and processor;

[0035] 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, the steps of the low-voltage power grid multi-service entity data sharing integrity processing method are implemented.

[0036] Fourthly, the present invention provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the steps of the low-voltage power grid multi-service entity data sharing integrity processing method.

[0037] The beneficial effects of this invention are as follows: The low-voltage power grid multi-business entity data sharing integrity processing method of this invention does not require each data-demanding system to ensure data integrity and data cleaning on its own. Professional tasks are handled by professional systems. Data is processed by the data responsibility entity, tagged after confirmation, and notified to other systems using the data. This ensures the consistency of data within the large system, improves the efficiency and accuracy of data processing, and results in significant economic benefits. Attached Figure Description

[0038] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the embodiments will be briefly introduced below. Obviously, the 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. Wherein:

[0039] Figure 1 This invention provides an overall flowchart of a method for handling the integrity of data sharing among multiple service entities in a low-voltage power grid.

[0040] Figure 2 This invention provides a schematic diagram of a low-voltage distribution network multi-service entity networking method for data sharing and integrity processing of multiple service entities in a low-voltage power grid. Detailed Implementation

[0041] To make the above-mentioned objects, features, and advantages of the present invention more apparent and understandable, 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, and 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.

[0042] Many specific details are set forth in the following description in order to provide a full understanding of the invention. However, the invention may also be practiced in other ways different from those described herein, and those skilled in the art can make similar extensions without departing from the spirit of the invention. Therefore, the invention is not limited to the specific embodiments disclosed below.

[0043] Secondly, the term "one embodiment" or "embodiment" as used herein refers to a specific feature, structure, or characteristic that may be included in at least one implementation of the present invention. The phrase "in one embodiment" appearing in different places in this specification does not necessarily refer to the same embodiment, nor is it a single or selective embodiment that is mutually exclusive with other embodiments.

[0044] This invention is described in detail with reference to the schematic diagrams. When detailing the embodiments of this invention, for ease of explanation, the cross-sectional views illustrating the device structure may be partially enlarged, not adhering to the usual scale. Furthermore, the schematic diagrams are merely examples and should not be construed as limiting the scope of protection of this invention. In actual fabrication, the three-dimensional spatial dimensions of length, width, and depth should be included.

[0045] Furthermore, in the description of this invention, it should be noted that the terms "upper," "lower," "inner," and "outer," etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. These terms are used solely for the convenience of describing the invention and for simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on the invention. In addition, the terms "first," "second," or "third" are used for descriptive purposes only and should not be construed as indicating or implying relative importance.

[0046] Unless otherwise explicitly specified and limited, the terms "installation," "connection," and "joining" in this invention should be interpreted broadly. For example, they can refer to fixed connections, detachable connections, or integral connections; similarly, they can refer to mechanical connections, electrical connections, or direct connections, or indirect connections through an intermediate medium, or internal connections between two components. Those skilled in the art can understand the specific meaning of the above terms in this invention based on the specific circumstances.

[0047] Example 1

[0048] Reference Figure 1 As an embodiment of the present invention, a method for handling data sharing integrity among multiple service entities in a low-voltage power grid is provided, comprising:

[0049] S1: Obtain electricity consumption data from different business entities, interact the electricity consumption data with the corresponding business systems, set a data processing cycle, and process the electricity consumption data within the data processing cycle;

[0050] Furthermore, application programming interface (API) interaction methods;

[0051] Match the application programming interface (API) to the electricity consumption data and integrate the API into the business system, so that the business system can call the API to upload electricity consumption data.

[0052] It should be noted that the business system includes an electricity information collection system, a load management system, and a distribution automation system. The multiple business entities include the main meter for the transformer area, residential meters, photovoltaic devices, charging piles, and branch monitoring units (LTUs).

[0053] Common interaction methods include file transfer, database connection, and web services. However, these methods require additional configuration and settings, and necessitate data transfer and conversion between different systems, leading to additional communication overhead and tight coupling between the systems, which limits system flexibility. This invention seeks a simplified and highly flexible interaction method, therefore, it preferentially adopts the Application Programming Interface (API) interaction method. This not only provides a simplified and standardized way to achieve interaction between systems, but also allows systems to interact in a more granular manner, sharing only necessary data and functions without the need for the transfer of entire files or databases. API interaction is typically real-time, enabling instant data transfer and response.

[0054] Compared to traditional interaction methods, API interaction can reduce unnecessary data conversion and transmission steps, improving interaction efficiency and response speed.

[0055] Furthermore, data processing is performed on different types of electricity consumption data at different times during the data processing cycle, including data integrity processing and data cleaning.

[0056] The electricity consumption data is cleaned within a set data processing cycle. The cleaned electricity consumption dataset is then processed for data integrity. For missing data, a defect compensation method is selected, and interpolation methods are used to estimate the value of the missing electricity consumption data.

[0057] It should be noted that the data processing cycle T is one day. Data cleaning includes deduplication of dirty data. By deduplication of dirty data, duplicate data can be removed, data quality can be improved, and the uniqueness of records in the dataset can be guaranteed, avoiding data inconsistency problems. The electricity dataset used for analysis is accurate and reliable, thereby improving the accuracy and credibility of data analysis.

[0058] It should also be noted that common methods for data integrity processing include filling missing values, deleting missing values, and merging data. However, common methods may lead to data distortion and are limited by the data source. Therefore, it is preferable to adopt a method that compensates for the shortcomings of the data source. This method can not only maintain the integrity of the electricity consumption dataset and prevent the loss of samples or data, but also maintain the distribution characteristics of the electricity consumption data and avoid data bias and distortion.

[0059] S2: The processed electricity consumption data results are incrementally synchronized to the power gateway to obtain data update information. Different electricity consumption data are recorded in the tag library and tagged with information.

[0060] Furthermore, an application programming interface that follows the REST architecture specification is used for incremental synchronization of electricity consumption data.

[0061] After processing the electricity consumption data, the electricity consumption data that needs to be synchronized is packaged into JSON format and sent to the application programming interface of the power gateway in the REST architecture specification via an HTTP POST request.

[0062] A data synchronization anomaly handling mechanism is constructed, which adopts a data rollback approach. When an anomaly occurs during the power consumption data synchronization process, the synchronized power consumption data is rolled back and the synchronization operation is performed again.

[0063] It should be noted that when determining the API interfaces that need to be called for different electricity consumption data of different business systems, when sending HTTP requests, ensure that the URL address of the request is accurate, use JSON format as the request header, and add the specific electricity consumption data as the request body to the request. Once the API returns a response, the correct electricity consumption data is successfully synchronized, and the abnormal data enters the synchronization exception handling mechanism for resynchronization.

[0064] Regarding the issue of electricity consumption data synchronization, this invention preferentially uses an application programming interface (API) that follows the REST architecture specification for incremental synchronization. For the management and monitoring of low-voltage power grids, the REST architecture API can improve the efficiency and accuracy of data synchronization, while also helping to protect data security.

[0065] Furthermore, the business system replenishes and cleans the daily frozen electricity consumption data at the first moment of each day, and after processing, it adds the first tag information to the daily frozen electricity consumption data;

[0066] At the second hour of each day, the electricity consumption data or minute-level data within the set time period of the previous day is supplemented and dirty data is cleaned and deduplicated. After processing, the electricity consumption data or minute-level data within the set time period is tagged with a second label.

[0067] At the third hour of each day, the loop impedance data from the previous day is supplemented and dirty data is cleaned and deduplicated. After processing, the loop impedance data is labeled with the third tag information.

[0068] It should be noted that the business system refers to the electricity information collection system. The first moment, the second moment, and the third moment are carried out in sequence. In this invention, the first moment is 0:10, the second moment is 0:52, and the third moment is 1:35. The time is set to 15 minutes based on technical experience.

[0069] It should also be noted that by using a tag library to record the tag information, a database is created, and the database fields are determined. The three types of data—daily frozen electricity consumption data, electricity consumption data within a set time period, and circuit impedance data—are associated with the first, second, and third tags. After tagging, objects with specific tags can be quickly found through searching, and statistics and analysis can be performed.

[0070] S3: Based on the power gateway, update data and tag information to other business systems using synchronization signals, and set time axis signals to search for electricity consumption data;

[0071] Furthermore, corresponding synchronization tags are added to the first, second, and third tag information and the update information. Different command values ​​are set according to different tag information. When the corresponding command value is entered, the corresponding tag information and data update information will be synchronized to the other business systems, including the forecasting and planning system and the customer service system.

[0072] It should be noted that the command values ​​for setting the first, second, and third tag information and update information are as follows: If the first tag information needs to be synchronized, the command value for the first tag is entered in the console to trigger the first tag synchronization command. The synchronization is then performed to other business systems via REST API, ensuring that the other business systems can obtain the latest first, second, and third tag information and update information. In other words, the command value can act as a trigger. When the corresponding command value is entered, the system will perform the corresponding synchronization operation, sending the tag information and data update information to the forecasting and planning system and the customer service system. This ensures that all business systems can obtain the latest information in a timely manner and maintain data consistency and accuracy.

[0073] Furthermore, a time axis signal is added to the second tag information, and a time command is set. After the electricity consumption data or minute-level data is tagged with the second tag information, the second tag information within the corresponding time period can be found by inputting the time axis command value.

[0074] It should be noted that by adding an input timeline command value to the second label, when the command value is entered, the business system will prompt the user to enter the start and end times. The user can query the second label information within a specific time range by specifying the start and end times. Based on the start and end times entered by the user, the system searches for the corresponding second label information within the database or data storage, and uses the REST API to synchronize the queried second label information to other business systems. This ensures that the second label information in other systems is consistent with the data within the specified time range, which facilitates timeline queries and ensures the accuracy and consistency of the data.

[0075] The above is an illustrative scheme of a low-voltage power grid multi-service entity data sharing integrity processing method according to this embodiment. It should be noted that the technical solution of the low-voltage power grid multi-service entity data sharing integrity processing device belongs to the same concept as the technical solution of the aforementioned low-voltage power grid multi-service entity data sharing integrity processing method. Details not described in detail in the technical solution of the low-voltage power grid multi-service entity data sharing integrity processing device in this embodiment can be found in the description of the technical solution of the aforementioned low-voltage power grid multi-service entity data sharing integrity processing method.

[0076] The apparatus for low-voltage power grid multi-service entity data sharing integrity processing in this embodiment includes:

[0077] The data processing module is used to acquire electricity consumption data from different business entities, interact the electricity consumption data with the corresponding business systems, set a data processing cycle, and process the electricity consumption data within the data processing cycle.

[0078] The recording and tagging module is used to incrementally synchronize the processed electricity consumption data results to the power gateway to obtain data update information, and to record and tag different electricity consumption data in the tag library.

[0079] The data synchronization module is used to transmit the data update information and tag information to other business systems using synchronization signals based on the power gateway, and to set time axis signals to search for electricity consumption data.

[0080] This embodiment also provides a computing device suitable for handling data sharing integrity in low-voltage power grids involving multiple service entities, including:

[0081] The system includes a memory and a processor. The memory stores computer-executable instructions, and the processor executes these instructions to implement the data sharing and integrity processing method for multiple business entities in a low-voltage power grid, as proposed in the above embodiments.

[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 the method for handling data sharing integrity of multiple business entities in a low-voltage power grid as proposed in the above embodiments.

[0083] The storage medium proposed in this embodiment and the method for achieving data sharing integrity processing of multiple business entities in low-voltage power grids proposed in the above embodiments belong to the same inventive concept. 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] Example 2

[0086] This embodiment differs from the first embodiment in that it provides a verification test of a method for handling the integrity of data sharing among multiple business entities in a low-voltage power grid, thereby verifying and explaining the technical effects adopted in this method.

[0087] This experiment assumes that there are multiple business entities in a city's low-voltage power grid, including,

[0088] Power company: Possesses a power supply business system, responsible for providing power services and managing electricity consumption data.

[0089] Energy management company: A company that provides energy management solutions and possesses an energy management business system.

[0090] A smart home service provider is a company that offers smart home products and services and owns a smart home control system.

[0091] Each business entity obtains electricity consumption data from other entities through a RESTful API and interacts with its own business system.

[0092] The data cycle is set to once a day. The power company processes the acquired electricity consumption data within the processing cycle, calculating each user's user volume, peak-valley-average electricity consumption, user's electricity consumption patterns, and abnormal electricity consumption behaviors.

[0093] The power company will incrementally synchronize the processed electricity consumption data results to the power gateway, and add fields for first, second and third tag information to the electricity consumption data structure to identify specific attributes of the data.

[0094] Define the following command values ​​for data update and synchronization:

[0095] Command value A: Synchronize the latest electricity consumption data from the power company with energy management companies and smart home service providers.

[0096] Command value B: Synchronizes the latest electricity usage data from the energy management company to the power company and smart home service provider.

[0097] Command value C: Synchronizes the latest electricity usage data from smart home service providers to power companies and energy management companies.

[0098] Suppose that the power company obtains new electricity consumption data and determines the corresponding tag information, the power company will send the new electricity consumption data and command value A to the energy management company and the smart home service provider.

[0099] As shown in the table below:

[0100] Table 1 Latest Electricity Consumption Data from Power Companies

[0101]

[0102] As shown in Table 1, the energy management company receives command value A and electricity consumption data, updates the electricity consumption data to its energy management business system and smart home service provider, and performs corresponding data processing and analysis.

[0103] Table 2: Data from smart home service providers:

[0104]

[0105] Table 3: Data from Energy Management Companies

[0106]

[0107] After data synchronization, as shown in Tables 2 and 3, the data in the tables of smart home service providers and energy management companies has been updated and is consistent with the latest electricity consumption data of the power company.

[0108] Add a time axis field to the electricity consumption data structure to record the data generation time, and set the command value D to trigger the time axis query function.

[0109] When the command value D is entered, the system enters timeline query mode, waiting for the user to input the start and end times. After the user provides the start and end times, the system queries the second tag information based on the time range and synchronizes the results to the databases of other business entities.

[0110] Each business entity can share and synchronize electricity consumption data, set tag information and command values, and query timelines according to the defined RESTful API, ensuring data integrity and consistency. Through data integrity verification testing, the technical effectiveness of the adopted method in data sharing and synchronization can be verified, ensuring that each business entity can share data efficiently and maintain data accuracy and consistency.

[0111] It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and not 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, and all such modifications or substitutions should be covered within the scope of the claims of the present invention.

Claims

1. A method for low voltage grid multi-service actor data sharing integrity processing, characterized in that, include: Obtain electricity consumption data from different business entities, interact the electricity consumption data with the corresponding business systems, set a data processing cycle, and process the electricity consumption data within the data processing cycle. The processed electricity consumption data results are incrementally synchronized to the power gateway to obtain data update information. Different electricity consumption data are recorded in the tag library and tagged. Based on the power gateway, the data update information and tag information are transmitted to other business systems using synchronization signals, and a time axis signal is set to search for electricity consumption data; A data processing cycle is set, and the electricity consumption data is processed within the data processing cycle, wherein... Data processing is performed on different types of electricity consumption data at different times within the data processing cycle, including data integrity processing and data cleaning. The electricity consumption data is cleaned within a set data processing cycle. The cleaned electricity consumption dataset is then processed for data integrity. For missing data, a defective compensation method is selected, and interpolation methods are used to estimate the value of the missing electricity consumption data. Different electricity consumption data are recorded in a tag library and tagged with information including, The business system replenishes and cleans the daily frozen electricity consumption data at the first moment of each day, and after the processing is completed, it adds the first tag information to the daily frozen electricity consumption data; At the second hour of each day, the electricity consumption data or minute-level data within the set time period of the previous day is supplemented and dirty data is cleaned and deduplicated. After processing, the electricity consumption data or minute-level data within the set time period is tagged with a second label. At the third hour of each day, the loop impedance data from the previous day is supplemented and dirty data is cleaned and deduplicated. After processing, the loop impedance data is labeled with the third tag information. According to the power gateway, the data update information and tag information are transmitted to other business systems using synchronization signals, including, The first, second, and third tag information and the update information are respectively labeled with corresponding synchronization tags. Different command values ​​are set according to different tag information. When the corresponding command value is entered, the corresponding tag information and data update information will be synchronized to the other business systems. The other business systems include the prediction and planning system and the customer service system.

2. The low-voltage power grid multi-service entity data sharing integrity processing method as described in claim 1, characterized in that, Obtain electricity consumption data from different business entities, and then interact with the corresponding business systems using this electricity consumption data. include, Application programming interface (API) interaction methods; Based on the electricity consumption data, an application programming interface (API) is matched and integrated into the business system, enabling the business system to call the API to upload electricity consumption data.

3. The low-voltage power grid multi-service entity data sharing integrity processing method as described in claim 2, characterized in that, The processed data results are incrementally synchronized to the power gateway to obtain updated data information, including: Electricity consumption data is synchronized using an application programming interface that follows the REST architecture specification in incremental synchronization. After processing the electricity consumption data, the electricity consumption data that needs to be synchronized is packaged into JSON format and sent to the application programming interface of the power gateway in the REST architecture specification via an HTTP POST request. A data synchronization anomaly handling mechanism is constructed, which adopts a data rollback approach. When an anomaly occurs during the power consumption data synchronization process, the synchronized power consumption data is rolled back and the synchronization operation is performed again.

4. The low-voltage power grid multi-service entity data sharing integrity processing method as described in claim 3, characterized in that, Set up a time axis signal to search for power consumption data, including: A time axis signal is added to the second tag information, and a time command is set. After the electricity consumption data or minute-level data is tagged with the second tag information, the second tag information within the corresponding time period can be found by inputting the time axis command value.

5. A system for processing the integrity of data sharing among multiple service entities in a low-voltage power grid, comprising applying the data sharing integrity processing method for multiple service entities in a low-voltage power grid as described in any one of claims 1-4, characterized in that, include: The data processing module is used to acquire electricity consumption data of different business entities, interact the electricity consumption data with the corresponding business system, set a data processing cycle, and process the electricity consumption data within the data processing cycle. The tagging module is used to incrementally synchronize the processed electricity consumption data results to the power gateway to obtain data update information, and to record and tag different electricity consumption data in the tag library. The data synchronization module is used to transmit the data update information and tag information to other business systems using synchronization signals based on the power gateway, and to set time axis signals to search for electricity consumption data.

6. An electronic device, characterized in that, The device includes: processor; Memory used to store processor-executable instructions; The processor is configured to invoke instructions stored in the memory to execute the method described in any one of claims 1 to 4.

7. A computer-readable storage medium having computer program instructions stored thereon, characterized in that, When the computer program instructions are executed by the processor, they implement the method described in any one of claims 1 to 4.

Images