Metering specialty and power distribution specialty data sharing method for transformer area intelligent fusion terminal

Abstract

The invention discloses a metering major and power distribution major data sharing method for a transformer area intelligent fusion terminal, and belongs to the technical field of power system data processing. According to the method, a state grid 16 interface and a reference standard MQTT communication interface are uniformly selected, so that the problem of interface incompatibility is solved; the data sharing demand is realized from three aspects of real-time notification of power-off and power-on events, accurate transmission of frozen data and regular pushing of sub-equipment states; defining an equipment registration process and data operation limitation, and standardizing a data model and an equipment state mechanism; data quality is guaranteed through dual registration verification, a hierarchical data model gives consideration to time efficiency and lake chasing, and fine management of equipment states avoids data faults. According to the method, metering and power distribution professional data can be efficiently and accurately shared, the operation and maintenance efficiency and the fault response speed of the power system are improved, and data support is provided for fine management of the power system.

Description

Technical Field

[0001] This invention relates to the field of power system data processing technology, and in particular to a method for sharing data between metering and distribution professionals in a smart converged terminal for distribution transformer areas. Background Technology

[0002] In the current power system distribution area management, the data from the metering and distribution sectors are often relatively independent. Data such as data from metering, household meters, and smart switches cannot be synchronized to the distribution side business system in a timely and accurate manner. This makes it difficult for distribution business personnel to grasp the real-time operating status of equipment in the distribution area and to efficiently obtain historical frozen data of equipment. Consequently, it affects the efficiency of distribution fault diagnosis, the accuracy of power dispatching in the distribution area, and the effectiveness of data query in the business system.

[0003] The existing data sharing methods have the following problems: First, the interface standards are not unified, and some data interactions rely on custom interfaces, resulting in poor compatibility and difficulty in adapting to business systems under the State Grid system; Second, data sharing lacks a pre-verification mechanism, failing to confirm the legality of equipment and the standardization of data models, which can easily lead to invalid data being written into the power distribution data center, causing data pollution or storage chaos; Third, the status push of sub-devices is not timely. When the IoT platform sub-devices are offline, the business system cannot obtain the corresponding data, creating a data gap; Fourth, the sharing priority of fault events and frozen data is unclear, and critical data cannot be transmitted first, affecting the timeliness of business response.

[0004] Therefore, there is an urgent need for a standardized, streamlined, and highly reliable method for metering and power distribution data sharing using intelligent integrated terminals in distribution substations, in order to address the aforementioned shortcomings of existing technologies. Summary of the Invention

[0005] The purpose of this invention is to provide a data sharing method between metering and power distribution professionals for a smart converged terminal in a distribution area, so as to solve the problem that the data between metering and power distribution professionals cannot be effectively shared in the prior art, and to realize the real-time transmission, accurate storage and efficient utilization of data.

[0006] Step 1: Selecting the Data Sharing Interface

[0007] In this method, the data sharing interface adopts the State Grid 16 interface to ensure the compatibility and standardization of the interface and provide a stable transmission channel for data sharing.

[0008] Step 2: Implementing specific data sharing requirements

[0009] (a) Freezing data transmission

[0010] Frozen data from data acquisition equipment, customer meter equipment, and smart switchgear is transmitted to the distribution data center via a frozen data interface for centralized storage and management. The specific content of the frozen data is determined according to actual needs, including requirements such as data collection cycle, data field format, and data accuracy, ensuring the accuracy and completeness of the data transmitted to the distribution data center and meeting the needs of the distribution business APP for historical data query and analysis.

[0011] (II) Power Outage Notification

[0012] For power outages and power-on events occurring in equipment supplied by the distribution system, customer meter equipment, and smart switchgear, the event information is transmitted to the power distribution business app in real time via the SOE (Event Sequence Recording) interface and the fault change reporting interface. The SOE interface records the precise time and details of the event, while the fault change reporting interface promptly pushes updates on event status changes, ensuring the power distribution business app can obtain the equipment's power outage and power-on status immediately, supporting rapid response from maintenance personnel.

[0013] (III) Timed push notification of sub-device status

[0014] To avoid the IoT platform being unable to process sub-device data when sub-devices are offline, thus preventing the power distribution business app from querying corresponding data, this method requires periodically pushing sub-device status information northward. The push cycle can be set according to actual business needs, but it is generally recommended not to exceed 5 minutes. This ensures that the IoT platform can grasp the online status and operating parameters of sub-devices in real time. Even if a sub-device goes offline briefly, the IoT platform can still make preliminary judgments and handle the situation based on the latest pushed status data, ensuring the continuity of data queries in the business system.

[0015] Step 3: Device Registration and Data Operation Restrictions

[0016] (I) Equipment Registration Process

[0017] Before writing device data into the power distribution data center, device registration must be completed. The device data to be registered includes real-time user meter data, frozen user meter data, real-time data from cross-border procurement, and frozen cross-border procurement data. During registration, information such as device identification, data type, and transmission protocol must be accurately entered and verified to ensure that the device can be uniquely identified and managed within the power distribution data center.

[0018] (II) Restrictions on Freezing Data Write Operations

[0019] Freezing data write operations are prohibited without completing both model registration and device registration. Model registration refers to registering the structure and field definitions of the device data model to ensure that data follows a unified format standard during storage and transmission; device registration is the verification of the device's identity information. Only when both model registration and device registration are completed can the frozen data write interface be activated to avoid data storage errors caused by data model mismatch or unclear device identity.

[0020] (III) SOE Event Write Operation Restrictions

[0021] Similar to write operations for frozen data, SOE event write operations cannot be performed without model registration and device registration. SOE events are crucial fault and status recording data; their accuracy and completeness directly impact fault analysis results. Strict registration preconditions prevent invalid or erroneous SOE event data from entering the system, ensuring the reliability of event records.

[0022] Step 4: Data Model and Device Status Mechanism

[0023] (I) Fault Report Push Model

[0024] The fault report push adopts a real-time model, that is, when the equipment fails, the fault information is transmitted to the power distribution data center in real time through the fault push interface, without the need for data caching or delay processing, ensuring that the fault information can be received and processed as quickly as possible, and buying time for fault repair.

[0025] (II) SOE Event Storage Model

[0026] SOE event storage employs a freeze model, which freezes SOE event data at fixed time intervals. The stored data includes key information such as event occurrence time, event type, and device identifier. This freeze model enables ordered storage and efficient retrieval of SOE event data, facilitating subsequent fault analysis and tracing.

[0027] (III) Equipment Status Mechanism

[0028] After the devices to which the shared data belong are registered on the IoT platform, they must strictly adhere to the device status mechanism for operation and management. There are two reporting mechanisms: a timed online status reporting mechanism and an offline status reporting mechanism. The timed online status reporting mechanism requires that device data was collected in the most recent instance. In this case, before the next data collection, the device online status is reported every minute by default, and this cycle repeats. If no device data is collected in the most recent instance, reporting stops, and the IoT platform determines the device status based on the reporting time. The offline status reporting mechanism requires that no device data is currently collected. In this case, the timed online reporting mechanism fails, and the device offline status is reported once. By adhering to the device status mechanism, the IoT platform can accurately and in real time grasp the device's operating status, ensuring the reliability and effectiveness of data sharing.

[0029] The beneficial technical effects of this invention are as follows: First, by uniformly selecting the State Grid 16 interface and the MQTT communication interface of the reference standard, the problem of incompatibility between the data transmission interfaces of the metering profession and the power distribution profession is solved, providing a stable and standardized transmission channel for data sharing; Second, it realizes real-time notification of power outage and restoration events, accurate transmission of frozen data, and timed push of sub-equipment status, ensuring that the power distribution business APP and the power distribution data center can obtain the required data in a timely manner, thereby improving the operation and maintenance efficiency and fault response speed of the power system.

[0030] The equipment registration process and data operation restrictions were clarified, and the data model and equipment status mechanism were standardized to ensure the accuracy, integrity and reliability of shared data, providing data support for the refined management of the power system. Attached Figure Description

[0031] Figure 1 This is a schematic diagram of the frozen data transmission process. Figure 1 The process of transmitting frozen data from equipment to the power distribution data center includes three main stages: data acquisition, interface transmission, and central storage.

[0032] Figure 2 This is a schematic diagram of the power outage / power on event notification process. Figure 2 The transmission process from equipment to the power distribution data center during a power outage includes three main stages: data acquisition, interface transmission, and central storage.

[0033] Figure 3 This is a diagram illustrating the registration process. Figure 3 The registration process from the power distribution business APP to the configuration data center includes three main stages: model registration, equipment registration, and data collection and storage. Detailed Implementation

[0034] Example 1: Device Registration and Freeze Data Write Operation

[0035] Step 1, Model Registration: In the model management module of the power distribution data center, enter the following four types of models: DC_Meter (fields: meter_id - string, real_time_energy - floating-point), DC_Meter_frozen (fields: meter_id - string, frozen_energy - floating-point, frozen_time - timestamp), DC_ADC (fields: adc_id - string, real_time_current - floating-point), and DC_ADC_frozen (fields: adc_id - string, frozen_current - floating-point, frozen_time - timestamp) to complete the registration;

[0036] Step 2, Equipment Registration: For the meter numbered "HB001" within the distribution area, enter the equipment ID "HB001", type "meter", installation location "Building 1, XX Community", bind the DC_Meter and DC_Meter_frozen models, and complete the registration after the power distribution data center verifies and passes the verification.

[0037] Step 3, Frozen Data Writing: When the "HB001" meter generates daily frozen data (frozen_energy: 120.5kWh, frozen_time: 202X-XX-XX 23:59:59), the smart converged terminal of the distribution area transmits the data through the frozen data writing interface (State Grid 16 interface). The distribution data center verifies that "HB001" has been registered and that the data format matches the DC_Meter_frozen model, and writes the data into the corresponding data table.

[0038] Example 2: Power Outage / Power On Event Sharing

[0039] When a power outage occurs at the smart switch numbered "ZK003", the smart fusion terminal of the distribution area records the event timestamp "202X-XX-XX 10:05:23" and the device ID "ZK003" through the SOE interface, and records the fault type "power outage" through the fault change reporting interface. Both types of data are pushed to the power distribution business APP at the same time. The APP pop-up window prompts "Smart switch ZK003 experienced a power outage at 10:05:23. Please check it in time".

[0040] Example 3: Sub-device status push

[0041] The sub-device status push cycle is set to 5 minutes. The smart converged terminal in the distribution area collects the status of all sub-devices every 5 minutes. Among them, the status of the "ADC005" sub-device is "online", the signal strength is "-75dBm" and the most recent interaction time is "202X-XX-XX10:00:00". This status is pushed to the northbound IoT platform. If the northbound IoT platform does not receive the "ADC005" status at 10:20, the terminal triggers a re-push and sends an "ADC005 communication abnormality" prompt to the power distribution business APP.

[0042] All equivalent structural or procedural transformations made using the description and drawings of this invention are similarly included within the scope of patent protection of this invention.

Claims

1. A method for data sharing between metering and power distribution specialties in a smart converged terminal for a distribution transformer area, characterized in that, This includes selecting a data sharing interface, implementing specific data sharing requirements, device registration and data operation restrictions, and data models and device status mechanisms. The specific steps are as follows: Step 1: Data sharing interface selection, specifically, the metering and distribution data sharing interface adopts the State Grid Corporation's 16 standardized interfaces; Step 2: Implement specific data sharing requirements. Specifically, for power outage and power-on events occurring in the distribution equipment, customer meter equipment, and smart switchgear, event information is notified to the power distribution business APP in real time through the SOE interface and the fault change reporting interface. The SOE interface records the precise time and details of the event, while the fault change reporting interface pushes the event status changes. Frozen data from the distribution equipment, customer meter equipment, and smart switchgear is transmitted to the power distribution data center through the frozen data interface. Sub-equipment status information is pushed northward periodically, with a push cycle not exceeding 5 minutes. Step 3: Equipment registration and data operation restrictions. Specifically, before writing equipment data into the power distribution data center, the equipment registration operation must be completed. The equipment data to be registered includes real-time data of user meters, frozen data of user meters, real-time data of cross-border procurement, and frozen data of cross-border procurement. During the registration process, the equipment identification, data type, and transmission protocol information must be accurately entered and verified. Freezing data write operations are prohibited if model registration and device registration are not completed. Model registration is the process of registering the structure and field definitions of the device data model. SOE event write operations cannot be performed without model registration and device registration. Step 4: Data Model and Device Status Mechanism. Specifically, the fault report push adopts a real-time model. When a device fails, the fault information is transmitted to the target system in real time through the fault push interface. The SOE event storage adopts a freeze model, freezing and storing SOE event data at fixed time intervals. The stored data includes the event occurrence time, event type, and device identifier. After the device to which the shared data belongs completes registration on the IoT platform, it follows the device status mechanism for operation and management. The device status mechanism clearly defines the online, offline, fault, and maintenance status of the device, the judgment criteria, and the status switching process.

2. The method according to claim 1, characterized in that, The push cycle for sub-device status information in step 2 can be adjusted according to actual business needs, and the adjusted cycle shall not exceed 5 minutes.

3. The method according to claim 1, characterized in that, The fixed time intervals for freezing and storing SOE event data in step 4 include 15 minutes and 30 minutes.

Images