A power grid real-time data platform multi-collection channel data source optimization processing method and system

Abstract

This invention discloses a method for optimizing data sources from multiple acquisition channels in a real-time power grid data platform. Based on the real-time power grid data platform, the method includes the following steps: (1) performing multi-source modeling of power grid equipment, measurement points, and front-end acquisition channels, and maintaining priority criteria; (2) defining multi-source data priority rules in a general multi-source priority definition table; (3) performing multi-source data interaction with the SCADA system; (4) loading and storing multi-source data priority rules; (5) executing the equipment measurement point data priority acquisition algorithm; and (6) executing the equipment measurement point data optimization algorithm for subsequent business processing. This invention improves the maintenance efficiency of engineers.

Description

Technical Field

[0001] This invention relates to the field of real-time power grid data technology, specifically to a method and system for optimizing and processing multi-acquisition channel data sources in a real-time power grid data platform. Background Technology

[0002] The new characteristics of real-time data platform applications are "global, fast, and accurate," requiring the development of integrated power grid analysis and decision-making applications based on a comprehensive network model and data. Currently, the State Grid Corporation of China has designed and constructed unified real-time data platforms for both the "national dispatch, grid dispatch (sub-dispatch), provincial dispatch" and "provincial dispatch, regional dispatch, county dispatch" two-tier deployment models. The national sub-dispatch real-time data platform serves as the leading node, with real-time data sources from the national, sub-dispatch, and provincial dispatch systems. The provincial real-time data platform acts as a coordinating node, with real-time data sourced from the provincial, regional, and county dispatch systems. Taking the national sub-dispatch real-time data platform as an example, considering data reliability, multi-source data backup is required. Real-time data from the same device may be simultaneously collected and forwarded to the real-time data platform by several systems within the national, grid, and provincial dispatch systems.

[0003] If the SCADA system processes all the data forwarded from these different systems without selection, it will lead to inaccurate real-time power grid data and waste computing resources such as CPU. This manifests primarily in two ways: first, telemetry jumps occur because telemetry data collected from the same device by different data sources may differ, for example, due to different system acquisition parameter configurations or malfunctions in the acquisition device; second, remote signaling processing is abnormal, such as processing the opening and closing signals of the same switch multiple times, sending multiple remote signaling change alarms, and inconsistencies may also exist between remote signaling data collected by different systems. The final remote signaling value collected by the system depends on the order in which the data is received. Summary of the Invention

[0004] Purpose of the invention: The purpose of this invention is to provide a method and system for optimizing data sources from multiple acquisition channels in a real-time power grid data platform, so as to solve the problems of telemetry jumps and repeated processing of remote signaling events caused by the real-time power grid data platform receiving data sources from multiple channels.

[0005] Technical Solution: The present invention provides a method for optimizing data sources from multiple acquisition channels in a real-time power grid data platform. Based on the real-time power grid data platform, the method includes the following steps:

[0006] (1) Perform multi-source modeling of power grid equipment, measurement points and front-end acquisition channels, and maintain priority criteria;

[0007] (2) Define multi-source data priority rules in the general multi-source priority definition table;

[0008] (3) The front-end system performs multi-source data interaction with the SCADA system;

[0009] (4) Priority rules for loading and storing multi-source data;

[0010] (5) Execute the algorithm for prioritizing the acquisition of equipment measurement point data;

[0011] (6) Execute the equipment measurement point data optimization algorithm for subsequent business processing.

[0012] Further, in step (2), the specifics are as follows: The general multi-source priority definition table corresponds the data sources to the five levels of dispatch management agencies of the State Grid Corporation of China, namely, national dispatch data source, grid dispatch data source, provincial dispatch data source, regional dispatch data source, and county dispatch data source. On this basis, a dispatch management agency data source is added. The priority of the six data sources can be set to any number from 0 to 5. The smaller the number, the higher the priority. In addition, there are two special priorities. The data with abnormal real-time data quality code has a priority of 999, which represents the lowest priority. The real-time data of devices not defined in the general multi-source priority definition table has a priority of -1, which is the highest priority. As shown in Table 1.

[0013] Table 1 General Multi-Source Priority Definition Table

[0014] ;

[0015] Further, in step (3), the specific details are as follows: The front-end interacts with SCADA multi-source data. The interaction message carries data source information. First, multi-acquisition channel modeling is performed in the front-end channel table, and the data source of each acquisition channel is maintained. The data source is represented by an integer. The message structure for the front-end to send data to the SCADA system is defined using Protobuf. Specifically, the front-end interacts with SCADA multi-source data. The data source information in the message structure is represented by an integer representing the region code. The format is as follows:

[0016] National-level data source: 990000

[0017] Data sources at the network level: 990101 (North China), 990102 (East China), 990103 (Central China), 990104 (Northeast China), 990105 (Northwest China), 990106 (Southwest China)

[0018] Data source for provincial grade adjustment: 320000

[0019] Data source for local grade adjustment: 320100

[0020] Data source for county-level adjustment: 320115.

[0021] Further, step (4) is as follows: The SCADA system loads the records in the table into the plant / station data source priority hash table, the area data source priority hash table, and the voltage level data source priority ordered set, according to the plant / station, area, and voltage level, respectively. When the data in the general multi-source priority definition table changes, the program is triggered to reload the rules.

[0022] When the plant ID is not empty, the rule is stored in the plant data source priority hash table, where the key is the plant ID and the value is the PRIORITY_STRUCT structure.

[0023] When the region ID is not empty, the rule is stored in the plant data source priority hash table, where the key is the plant ID and the value is the PRIORITY_STRUCT structure.

[0024] When both the plant ID and the region ID are empty, the rule will be stored in the voltage level data source priority ordered set.

[0025] The PRIORITY_STRUCT structure is defined as follows:

[0026] struct PRIORITY_STRUCT

[0027] {

[0028] float low_voltage_lim; / / Lower limit of voltage level

[0029] float up_voltage_lim; / / Voltage level cap

[0030] int nation_dispatch_pri; / / Priority of national dispatch data source

[0031] int region_dispatch_pri; / / Priority of network dispatch data source

[0032] int prov_dispatch_pri; / / Priority of provincial dispatch data source

[0033] int city_dispatch_pri; / / Priority of the ground dispatch data source

[0034] int county_dispatch_pri; / / Priority of county data source

[0035] int dev_dispatch_pri; / / Priority of the data source belonging to the dispatching agency of the device

[0036] bool operator<(PRIORITY_STRUCT const&a,PRIORITY_STRUCT const&b)

[0037] {

[0038] if (a. low_voltage_lim == b. low_voltage_lim) return a. up_voltage_lim <b. up_voltage_lim;

[0039] else return a. low_voltage_lim <b. low_voltage_lim;

[0040] }

[0041] };

[0042] Storing a voltage level data source priority ordered set requires overloading the "less than" operator.

[0043] Furthermore, in step (5), the real-time data priority acquisition algorithm includes the following steps:

[0044] (51) Load the general multi-source priority definition table;

[0045] (52) Receive real-time data sent by the front-end acquisition channel. On the one hand, read the data source of the last data used by the device measurement point from the real-time telemetry table or telesignal table. On the other hand, parse the data source and data quality code of the data received this time from the message.

[0046] (53) If the data source of the current measurement point of the equipment is the same as the data source of the last received data, then the data is used directly, and the priority is the same as the priority of the data used last time;

[0047] (54) If the data source for the current measurement point is different from the data source for the last received data, then the following logic is executed:

[0048] (54a) If the quality code of the data at the device measurement point is abnormal, the priority of this data is defined as the lowest priority 999;

[0049] (54b) If the quality code of the data from the equipment measurement point is normal, read the equipment information of the received data from the real-time database, including the plant, region and voltage level of the equipment, and search the plant data source priority hash table, the region data source priority hash table and the voltage level priority ordered set respectively to obtain the priority of the data.

[0050] (54c) If no priority rule for the measurement point of the device is found in the above three sets, the priority of this data is set to the highest priority -1.

[0051] Furthermore, step (6) includes the following steps:

[0052] (61) If the data source of the equipment measurement point is the same as the data source used last time, use the current data and execute the power grid business logic, and write the data into the real-time database;

[0053] (62) If the data source for the current measurement point is different from the data source used last time, the following logic will be executed:

[0054] (62a) If the priority of the data received by the device measurement point this time is higher than the priority of the data used last time, the data is used and the power grid business logic is executed. The data is written to the real-time database, and the data source is written to the remote signaling table or the telemetry table. A data source switching alarm is sent.

[0055] (62b) If the priority of the data received by the device measurement point this time is lower than the priority of the data used last time, the data received this time shall be discarded.

[0056] The present invention discloses a multi-acquisition channel data source optimization and processing system for a real-time power grid data platform. The real-time power grid data platform includes:

[0057] Priority criterion module: used for multi-source modeling of power grid equipment, measurement points and front-end acquisition channels, and maintenance of priority criteria;

[0058] Priority rules module: Used to define multi-source data priority rules in the general multi-source priority definition table;

[0059] Multi-source data interaction module: used for front-end multi-source data interaction with the SCADA system;

[0060] Loading module: Used to load and store priority rules for multi-source data;

[0061] Priority acquisition algorithm module: used to execute the algorithm for acquiring the priority of equipment measurement point data;

[0062] Execution module: Used to execute the equipment measurement point data optimization algorithm and perform subsequent business processing.

[0063] Furthermore, in the priority rules module, the specifics are as follows: The general multi-source priority definition table maps data sources to the five levels of dispatch management agencies of the State Grid Corporation of China, namely, national dispatch data source, grid dispatch data source, provincial dispatch data source, regional dispatch data source, and county dispatch data source. An additional dispatch management agency data source is added on top of this. The priority of these six data sources can be set to any number from 0 to 5, with smaller numbers indicating higher priority. In addition, there are two special priorities: data with abnormal real-time data quality codes has a priority of 999, representing the lowest priority; and data from devices not defined in the general multi-source priority definition table has a real-time data priority of -1, which is the highest priority.

[0064] Furthermore, in the multi-source data interaction module, the specifics are as follows: the front-end interacts with SCADA multi-source data, and the interaction message carries data source information. First, multi-acquisition channel modeling is performed in the front-end channel table, and the data source of each acquisition channel is maintained. The data source is represented by an integer data, and the message structure for the front-end to send data to the SCADA system is defined through Protobuf.

[0065] Furthermore, the real-time data priority acquisition algorithm in the priority acquisition algorithm module is as follows:

[0066] First, load the general multi-source priority definition table;

[0067] Secondly, the system receives real-time data from the front-end acquisition channel. On one hand, it reads the data source of the last data used by the device's measurement point from the real-time database telemetry table or telesignal table. On the other hand, it parses the data source and data quality code of the data received this time from the message. If the data source of the current data of the device's measurement point is the same as the data source of the last data received, the data is directly used with the same priority as the data used last time. Finally, if the data source of the current data of the device's measurement point is different from the data source of the last data received, the following logic is executed: If the data quality code of the current data of the device's measurement point is abnormal, the priority of the current data is defined as the lowest priority 999. If the data quality code of the current data of the device's measurement point is normal, the device information of the received data is read from the real-time database, including the plant, region, and voltage level of the device. The system searches the plant data source priority hash table, the region data source priority hash table, and the voltage level priority ordered set to obtain the priority of the current data. If the priority rule of the device's measurement point is not found in the above three sets, the priority of the current data is set to the highest priority -1.

[0068] Furthermore, in the execution module, the specific steps are as follows: if the data source of the device measurement point this time is the same as the data source used last time, the current data is used and the power grid business logic is executed, and the data is written to the real-time database;

[0069] If the data source of the device measurement point this time is different from the data source used last time, the following logic is executed: If the priority of the data received by the device measurement point this time is higher than the priority of the data used last time, the data is used and the power grid business logic is executed, the data is written to the real-time database, the data source is written to the remote signaling table or the telemetry table, and a data source switching alarm is sent; If the priority of the data received by the device measurement point this time is lower than the priority of the data used last time, the data received this time is discarded.

[0070] Beneficial Effects: Compared with existing technologies, this invention has the following significant advantages: 1. It resolves the risk of data jumps: data from multiple acquisition channels may differ significantly, and simultaneous use can lead to data jumps. 2. It improves data accuracy: some acquisition channels contain erroneous data; by selecting the data with the optimal quality code, data accuracy can be improved, providing reliable real-time data for applications such as upper-level state estimation. 3. It enhances data processing performance: low-priority data is directly discarded, reducing data processing logic and thus improving data processing performance. 4. It offers flexible and convenient configuration: using the universal multi-source priority definition table designed in this invention, the priority of data from various management agencies can be flexibly modified at any time, improving the maintenance efficiency of engineers. Attached Figure Description

[0071] Figure 1 This is the overall framework for multi-source data acquisition and optimization of the present invention;

[0072] Figure 2 This invention relates to a multi-source data priority acquisition algorithm;

[0073] Figure 3 This is the data optimization algorithm of the present invention. Detailed Implementation

[0074] The technical solution of the present invention will be further described below with reference to the accompanying drawings.

[0075] like Figure 1 As shown in the figure, this invention provides a method and system for optimizing multi-channel data sources for a real-time power grid data platform, the specific steps of which are as follows:

[0076] Step 1: Perform multi-source modeling of power grid equipment, measuring points, and front-end acquisition channels, and maintain priority criteria.

[0077] Step 1.1: Modeling power grid equipment. Power grid equipment includes generators, circuit breakers, switches, disconnectors, busbars, transformers, transformer windings, loads, etc. This invention requires the establishment and maintenance of priority criterion fields including "affiliated substation", "voltage level", and "affiliated dispatching agency". Taking circuit breakers as an example, the modeling is as follows:

[0078] Table 2. Description of Power Grid Equipment Modeling

[0079] ;

[0080] Circuit breaker A is a 220kV switch and is under the jurisdiction of the provincial dispatch center (320000). Circuit breaker B is a 110kV switch and is under the jurisdiction of the local dispatch center (320100).

[0081] Step 1.2: Measurement Point Modeling. Measurement points refer to the remote signaling and telemetry of network-disconnected equipment. For example, the remote signaling of a circuit breaker includes "remote signaling values," "auxiliary node remote signaling values," and "A / B / C three-phase remote signaling values," etc. These telemetry values ​​are all triggered in the remote signaling table. Telemetry values ​​include "current values," "voltage values," "active power values," and "reactive power values," etc. These telemetry values ​​are triggered from the equipment table to the remote signaling / telemetry table through database triggers. Taking the telemetry table as an example, an example is as follows:

[0082] Table 3. Telemetry Table Modeling Instructions

[0083] ;

[0084] The first record in the table above is "Circuit Breaker A Current", and the current data source is 320000, which is Jiangsu Provincial Dispatch Center. The second record is "Bus A Line Voltage", and the current data source is 320100, which is Nanjing Regional Dispatch Center.

[0085] Step 1.3: Modeling the front-end data acquisition channels. Each plant can trigger multiple data acquisition channels. These channels can be forwarding channels of various levels of scheduling systems, or channels that directly collect data within this system. After collecting data, these channels can all send data to SCADA. Examples are as follows:

[0086] Table 4. Modeling Description of the Pre-acquisition Channel

[0087] ;

[0088] In the table above, both records were triggered by plant S, with one data source being 320000 (provincial dispatch) and the other being 320100 (regional dispatch).

[0089] Step 2: Define multi-source data priority rules in the general multi-source priority definition table.

[0090] Table 5. Data Source Priority Definitions

[0091]

[0092] In the three rules in the table above, the data source priority of the respective dispatching agency is 0, meaning that the data sent by the dispatching agency has a higher priority than data sent by other systems. The dispatching agency is also one of the five levels of dispatching agencies; for example, the East China Real-time Data Platform is a network-level system, and the Jiangsu Real-time Data Platform is a provincial-level system.

[0093] If the data does not originate from the equipment's governing body, its priority will be determined according to the configuration in the table.

[0094] For example, in the first rule Id1, for the specified substation "Substation A", all equipment from 0kV to 1000kV has the highest priority for data from the local dispatch center, followed by the provincial dispatch center, county dispatch center, grid dispatch center, and national dispatch center.

[0095] The second rule, Id2, applies to the designated region "Jiangsu". For all equipment from 0kV to 1000kV, data from the provincial dispatch center has the highest priority, followed by data from the local dispatch center, county dispatch center, grid dispatch center, and national dispatch center.

[0096] Rule 3 (Id3) addresses situations where no specific substation or region is designated. For all equipment from 0kV to 1000kV, data from the grid dispatch center has the highest priority, followed by data from the national dispatch center, provincial dispatch center, regional dispatch center, and county dispatch center.

[0097] Note that the voltage levels in the table above can also be adjusted. For example, priority rules can be set separately for equipment in voltage ranges such as 35kV, 110kV, 220kV, and 500kV.

[0098] Step 3: The front-end system interacts with the SCADA system using multi-source data. Data exchange between the front-end system and the SCADA system employs the Protobuf protocol. Each data packet header needs to carry data source information. Taking change telemetry as an example, the data interaction structure is illustrated below:

[0099] message ChangeYcPkg

[0100] {

[0101] required FesPkgHead package_head = 1;

[0102] repeated ChangeYc yc_seq = 2;

[0103] };

[0104] A single telemetry packet consists of a packet header (FesPkgHead) and multiple ChangeYc telemetry point information. The packet header information is as follows:

[0105] message FesPkgHead

[0106] {

[0107] required int32 package_type = 1; / / Package type

[0108] required int32 data_num = 2; / / Count

[0109] required int64 second = 3; / / Change time, in seconds

[0110] required int32 msecond = 4; / / Change time, milliseconds

[0111] optional int32 para = 5; / / Reserved

[0112] optional UData.TSgKeyID fac_id = 6; / / Factory site ID

[0113] optional int32 data_source = 7; / / Data source

[0114] };

[0115] The data_source in the FesPkgHead structure of the message header above comes from the data source in Table 4, which describes the modeling of the front-end acquisition channel.

[0116] The telemetry information for a single change is as follows:

[0117] message ChangeYc

[0118] {

[0119] required UData.TSgKeyID fac_id = 1; / / Factory site ID

[0120] required UData.TSgKeyID keyid = 2; / / keyword

[0121] required float value = 3; / / Telemetry value

[0122] required int32 status = 4; / / Telemetry status

[0123] optional int64 second = 5; / / Change time, in seconds

[0124] optional int32 msecond = 6; / / Change time, milliseconds

[0125] };

[0126] Step 4: Load and store multi-source data priority rules. The SCADA system loads the records in this table into the plant / station data source priority hash table, the area data source priority hash table, and the voltage level data source priority ordered set, respectively, according to the plant / station, area, and voltage level.

[0127] When the plant ID is not empty, the rule is stored in the plant data source priority hash table, where the key is the plant ID and the value is the PRIORITY_STRUCT structure.

[0128] When the region ID is not empty, the rule is stored in the plant data source priority hash table, where the key is the plant ID and the value is the PRIORITY_STRUCT structure.

[0129] When both the plant ID and the region ID are empty, the rule will be stored in the voltage level data source priority ordered set.

[0130] The PRIORITY_STRUCT structure is defined as follows:

[0131] struct PRIORITY_STRUCT

[0132] {

[0133] float low_voltage_lim; / / Lower limit of voltage level

[0134] float up_voltage_lim; / / Voltage level cap

[0135] int nation_dispatch_pri; / / Priority of national dispatch data source

[0136] int region_dispatch_pri; / / Priority of network dispatch data source

[0137] int prov_dispatch_pri; / / Priority of provincial dispatch data source

[0138] int city_dispatch_pri; / / Priority of the ground dispatch data source

[0139] int county_dispatch_pri; / / Priority of county data source

[0140] int dev_dispatch_pri; / / Priority of the data source belonging to the dispatching agency of the device

[0141] bool operator<(PRIORITY_STRUCT const&a,PRIORITY_STRUCT const&b)

[0142] {

[0143] if (a. low_voltage_lim == b. low_voltage_lim) return a. up_voltage_lim <b. up_voltage_lim;

[0144] else return a. low_voltage_lim <b. low_voltage_lim;

[0145] }

[0146] };

[0147] Storing a voltage level data source priority ordered set requires overloading the "less than" operator.

[0148] Step 5: Execute the device measurement point data priority acquisition algorithm. The priority acquisition algorithm design is attached. Figure 2 As shown, after receiving multi-source data, the SCADA system parses the data source information, queries the plant, dispatching agency, and region to which the data belongs, and calculates the priority of the data according to the priority definition in the hash table. The specific steps are as follows:

[0149] (5.1) Load the general multi-source priority definition table;

[0150] (5.2) Receive real-time data sent from the front-end acquisition channel. On the one hand, read the data source of the last data used by the device measurement point from the real-time telemetry table or teleindication table. On the other hand, parse the data source and data quality code of the data received this time from the message.

[0151] (5.3) If the data source of the current measurement point of the equipment is the same as the data source of the last received data, the data shall be used directly, and the priority shall be the same as the priority of the data used last time;

[0152] (5.4) If the data source for the current measurement point is different from the data source for the last received data, the following logic will be executed:

[0153] (5.4.1) If the quality code of the data at the device measurement point is abnormal, the priority of this data shall be defined as the lowest priority 999;

[0154] (5.4.2) If the quality code of the data from the equipment measurement point is normal, read the equipment information of the received data from the real-time database, including the plant, region and voltage level of the equipment, and search the plant data source priority hash table, the region data source priority hash table and the voltage level priority ordered set respectively to obtain the priority of the data.

[0155] (5.4.3) If no priority rule for the measurement point of the device is found in the above three sets, the priority of this data is set to the highest priority -1.

[0156] Step 6: Execute the equipment measurement point data optimization algorithm for subsequent business processing. The design of the data optimization algorithm is shown in the attached figure. Figure 3 As shown, the specific steps are as follows:

[0157] (6.1) If the data source of the equipment measurement point is the same as the data source used last time, use the current data and execute the power grid business logic, and write the data into the real-time database;

[0158] (6.2) If the data source for the device measurement point is different this time from the data source used last time, the following logic will be executed:

[0159] (6.2.1) If the priority of the data received by the device measurement point this time is higher than the priority of the data used last time, the data is used and the power grid business logic is executed. The data is written to the real-time database, and the data source is written to the remote signaling table or the telemetry table. A data source switching alarm is sent.

[0160] (6.2.2) If the priority of the data received by the device measurement point this time is lower than the priority of the data used last time, the data received this time shall be discarded.

[0161] This invention also provides a multi-acquisition channel data source optimization and processing system for a real-time power grid data platform. The real-time power grid data platform includes:

[0162] Priority criterion module: used for multi-source modeling of power grid equipment, measurement points and front-end acquisition channels, and maintenance of priority criteria;

[0163] Priority Rules Module: Used to define multi-source data priority rules in the General Multi-Source Priority Definition Table; specifically as follows: The General Multi-Source Priority Definition Table maps data sources to the five levels of dispatch management agencies of the State Grid Corporation of China, namely, National Dispatch Data Source, Grid Dispatch Data Source, Provincial Dispatch Data Source, Regional Dispatch Data Source, and County Dispatch Data Source. An additional dispatch management agency data source is added on top of this. The priority of these six data sources can be set to any number from 0 to 5, with smaller numbers indicating higher priority. In addition, there are two special priorities: data with abnormal real-time data quality codes has a priority of 999, representing the lowest priority; and data from devices not defined in the General Multi-Source Priority Definition Table has a real-time data priority of -1, the highest priority.

[0164] Multi-source data interaction module: used for multi-source data interaction between the front-end and the SCADA system; specifically as follows: the front-end interacts with the SCADA system through multiple sources of data. The interaction messages carry data source information. First, multi-acquisition channels need to be modeled in the front-end channel table, and the data source of each acquisition channel needs to be maintained. The data source is represented by an integer. The message structure for the front-end to send data to the SCADA system is defined by Protobuf.

[0165] Loading module: Used to load and store priority rules for multi-source data;

[0166] Priority acquisition algorithm module: used to execute the algorithm for acquiring the priority of equipment measurement point data; real-time data priority acquisition algorithm, as follows:

[0167] First, load the general multi-source priority definition table;

[0168] Secondly, the system receives real-time data from the front-end acquisition channel. On one hand, it reads the data source of the last data used by the device's measurement point from the real-time database telemetry table or telesignal table. On the other hand, it parses the data source and data quality code of the data received this time from the message. If the data source of the current data of the device's measurement point is the same as the data source of the last data received, the data is directly used with the same priority as the data used last time. Finally, if the data source of the current data of the device's measurement point is different from the data source of the last data received, the following logic is executed: If the data quality code of the current data of the device's measurement point is abnormal, the priority of the current data is defined as the lowest priority 999. If the data quality code of the current data of the device's measurement point is normal, the device information of the received data is read from the real-time database, including the plant, region, and voltage level of the device. The system searches the plant data source priority hash table, the region data source priority hash table, and the voltage level priority ordered set to obtain the priority of the current data. If the priority rule of the device's measurement point is not found in the above three sets, the priority of the current data is set to the highest priority -1.

[0169] Execution module: Used to execute the equipment measurement point data optimization algorithm and perform subsequent business processing. Specifically: If the data source for the equipment measurement point this time is the same as the data source used last time, the current data is used and the power grid business logic is executed, and the data is written to the real-time database;

[0170] If the data source of the device measurement point this time is different from the data source used last time, the following logic is executed: If the priority of the data received by the device measurement point this time is higher than the priority of the data used last time, the data is used and the power grid business logic is executed, the data is written to the real-time database, the data source is written to the remote signaling table or the telemetry table, and a data source switching alarm is sent; If the priority of the data received by the device measurement point this time is lower than the priority of the data used last time, the data received this time is discarded.

Claims

1. A method for optimizing data sources from multiple acquisition channels in a real-time power grid data platform, characterized in that, The steps involved in using a real-time power grid data platform are as follows: (1) Perform multi-source modeling of power grid equipment, measurement points and front-end acquisition channels, and maintain priority criteria; (2) Define multi-source data priority rules in the general multi-source priority definition table; (3) The front-end system performs multi-source data interaction with the SCADA system; (4) Priority rules for loading and storing multi-source data; (5) Execute the equipment measurement point data priority acquisition algorithm; the real-time data priority acquisition algorithm includes the following steps: (51) Load the general multi-source priority definition table; (52) Receive real-time data sent by the front-end acquisition channel. On the one hand, read the data source of the last data used by the device measurement point from the real-time telemetry table or telesignal table. On the other hand, parse the data source and data quality code of the data received this time from the message. (53) If the data source of the current measurement point of the equipment is the same as the data source of the last received data, then the data is used directly, and the priority is the same as the priority of the data used last time; (54) If the data source for the current measurement point is different from the data source for the last received data, then the following logic is executed: (54a) If the quality code of the data at the device measurement point is abnormal, the priority of this data is defined as the lowest priority 999; (54b) If the quality code of the data from the equipment measurement point is normal, read the equipment information of the received data from the real-time database, including the plant, region and voltage level of the equipment, and search the plant data source priority hash table, the region data source priority hash table and the voltage level priority ordered set respectively to obtain the priority of the data. (54c) If no priority rule for the measurement point of the device is found in the above three sets, the priority of this data is set to the highest priority -1; (6) Execute the equipment measurement point data optimization algorithm and perform subsequent business processing.

2. The method for optimizing data sources from multiple acquisition channels in a real-time power grid data platform according to claim 1, characterized in that, In step (2), the specific details are as follows: The general multi-source priority definition table corresponds the data sources to the five-level dispatch management agencies of the State Grid Corporation of China. The five-level dispatch management agencies of the State Grid Corporation of China are the national dispatch data source, the grid dispatch data source, the provincial dispatch data source, the regional dispatch data source, and the county dispatch data source. On this basis, an additional dispatch management agency data source is added. The priority of the six data sources can be set to any number from 0 to 5. The smaller the number, the higher the priority. In addition, there are two special priorities. The data with abnormal real-time data quality code has a priority of 999, which represents the lowest priority. Devices not defined in the general multi-source priority definition table have a real-time data priority of -1, which is the highest priority.

3. The method for optimizing data sources from multiple acquisition channels in a real-time power grid data platform according to claim 1, characterized in that, In step (3), the specific details are as follows: the front-end interacts with SCADA multi-source data, and the interaction message carries the data source information. First, multi-acquisition channel modeling is performed in the front-end channel table, and the data source of each acquisition channel is maintained. The data source is represented by an integer data. The message structure for the front-end to send data to the SCADA system is defined by Protobuf.

4. The method for optimizing data sources from multiple acquisition channels in a real-time power grid data platform according to claim 1, characterized in that, Step (6) includes the following steps: (61) If the data source of the equipment measurement point is the same as the data source used last time, use the current data and execute the power grid business logic, and write the data into the real-time database; (62) If the data source for the current measurement point is different from the data source used last time, the following logic will be executed: (62a) If the priority of the data received by the device measurement point this time is higher than the priority of the data used last time, the data is used and the power grid business logic is executed. The data is written to the real-time database, and the data source is written to the remote signaling table or the telemetry table. A data source switching alarm is sent. (62b) If the priority of the data received by the device measurement point this time is lower than the priority of the data used last time, the data received this time shall be discarded.

5. A multi-channel data source optimization and processing system for a real-time power grid data platform, characterized in that, The power grid real-time data platform includes: Priority criterion module: used for multi-source modeling of power grid equipment, measurement points and front-end acquisition channels, and maintenance of priority criteria; Priority rules module: Used to define multi-source data priority rules in the general multi-source priority definition table; Multi-source data interaction module: used for front-end multi-source data interaction with the SCADA system; Loading module: Used to load and store priority rules for multi-source data; Priority acquisition algorithm module: used to execute the algorithm for acquiring the priority of equipment measurement point data; real-time data priority acquisition algorithm, including: Load the general multi-source priority definition table; receive real-time data from the front-end acquisition channel. On one hand, read the data source of the last data used by the device measurement point from the real-time database telemetry table or teleindication table. On the other hand, parse the data source and data quality code of the data received this time from the message. If the data source of the data of the device measurement point this time is the same as the data source of the last data received, the data is directly used, and the priority is the same as the priority of the last data used. If the data source of the data of the device measurement point this time is different from the data source of the last data received, the following logic is executed: If the data quality code of the device measurement point this time is abnormal, the priority of the data this time is defined as the lowest priority 999. If the data quality code of the device measurement point this time is normal, read the device information of the received data from the real-time database, including the plant, region, and voltage level of the device. Search the plant data source priority hash table, the region data source priority hash table, and the voltage level priority ordered set to obtain the priority of the data this time. If the priority rule of the device measurement point is not found in the above three sets, the priority of the data this time is set to the highest priority -1. Execution module: Used to execute the equipment measurement point data optimization algorithm and perform subsequent business processing.

6. The power grid real-time data platform multi-acquisition channel data source optimization and processing system according to claim 5, characterized in that, In the priority rules module, the specifics are as follows: The general multi-source priority definition table maps data sources to the five levels of dispatch management agencies of the State Grid Corporation of China. The five levels of dispatch management agencies of the State Grid Corporation of China are national dispatch data source, grid dispatch data source, provincial dispatch data source, regional dispatch data source, and county dispatch data source. On this basis, a dispatch management agency data source is added. The priority of these six data sources can be set to any number from 0 to 5, with the smaller the number, the higher the priority. In addition, there are two special priorities, among which the data with abnormal real-time data quality codes has a priority of 999, representing the lowest priority. Devices not defined in the general multi-source priority definition table have a real-time data priority of -1, which is the highest priority.

7. The power grid real-time data platform multi-acquisition channel data source optimization and processing system according to claim 5, characterized in that, In the multi-source data interaction module, the specifics are as follows: the front-end interacts with SCADA multi-source data, and the interaction message carries data source information. First, multi-acquisition channel modeling is performed in the front-end channel table, and the data source of each acquisition channel is maintained. The data source is represented by an integer data. The message structure for the front-end to send data to the SCADA system is defined through Protobuf.

8. The power grid real-time data platform multi-acquisition channel data source optimization and processing system according to claim 5, characterized in that, In the execution module, the specific steps are as follows: If the data source for the current measurement point is the same as the data source used last time, the current data is used and the power grid business logic is executed, and the data is written to the real-time database. If the data source of the device measurement point this time is different from the data source used last time, the following logic is executed: If the priority of the data received by the device measurement point this time is higher than the priority of the data used last time, the data is used and the power grid business logic is executed, the data is written to the real-time database, the data source is written to the remote signaling table or the telemetry table, and a data source switching alarm is sent; If the priority of the data received by the device measurement point this time is lower than the priority of the data used last time, the data received this time is discarded.

Images