Multi-source data fusion method and system based on feeder-level CIM file

Through the multi-source data fusion method based on feeder-level CIM files, the problem that traditional distribution network systems cannot effectively integrate multi-source data is solved, and the unified data fusion and visual display are realized, which improves the operating efficiency and safety of the distribution network .

CN119005730APending Publication Date: 2024-11-22CHINA ELECTRIC POWER RESEARCH INSTITUTE CO LTD +2
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410880461.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-02
Publication Date
2024-11-22

AI Technical Summary

Technical Problem

Traditional distribution network regulation systems cannot effectively integrate multi-source data, resulting in redundant data, complex operation and difficulty in adapting to digital transformation, and cannot meet the high-complexity and rapidly changing distribution network safe operation needs.

Method used

Using a multi-source data fusion method based on feeder-level CIM files, the network topology content and device information are imported into the device fusion model by generating a structured CIM model, and external system data is extracted based on the device information to realize the unified fusion of data of each system and Visual display.

Benefits of technology

It improves the work efficiency of data fusion, provides more accurate data support, helps the distribution network to operate safely, reliably and economically, and improves the quality of power supply services.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119005730A_ABST
    Figure CN119005730A_ABST
Patent Text Reader

Abstract

The invention belongs to the technical field of power distribution network data processing, and particularly relates to a feeder-level CIM file-based multi-source data fusion method and system, and the method comprises the steps: generating a structured CIM model based on a common information model CIM file of a power distribution network feeder, and filling the data in the CIM model into a pre-constructed equipment fusion model; the CIM file of the feeder line of the power distribution network comprises network topology content and equipment information; extracting external system data according to the equipment information, and backfilling the external system data into the equipment fusion model; the equipment fusion model is constructed by utilizing an equipment model table. According to the technical scheme provided by the invention, data of equipment of each system is fused, data support is provided for various simulations, the working efficiency of data fusion is also improved, and auxiliary decision support is provided for safe, reliable and economic operation of the power distribution network, so that the power supply potential of the active power distribution network is effectively mined, and the power supply service quality level is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention belongs to the technical field of distribution network data processing, and in particular relates to a multi-source data fusion method and system based on a feeder-level CIM file. Background Art

[0002] The rise of the power Internet of Things, distributed energy, energy storage, and electric vehicles has posed challenges to traditional distribution networks, and the digital transformation of distribution networks is imminent. The rapid development of emerging technologies such as the Internet, cloud computing, and big data has further promoted the arrival of the era of data-driven distribution network planning. At present, digital technology has been fully capable of obtaining various planning business process (transactional) data, but these data are often redundant, and more effective information must be obtained through mathematical modeling. The constructed models include descriptive models (such as load forecasting, network simulation) that understand the relationship between power companies and the external environment, as well as standard normative models (such as various optimization models). Traditional modeling is usually implemented using methods such as data analysis and probabilistic statistical analysis. These traditional methods have been revitalized by the massive data support provided by digital technology.

[0003] In the context of the big data era, users are paying more and more attention to the business information hidden behind the complex mass data. With the continuous development of distribution network information communication, and the large-scale access of new energy and various new distribution equipment to the distribution network, the complexity and safety risks of distribution network dispatching and control are constantly increasing. However, the traditional distribution network control is based on the current minute-level operation mode for safety verification and operates directly on the physical power grid. It is becoming increasingly difficult to adapt to the requirements of safe operation of highly complex and rapidly changing distribution networks. The distribution network interactive application system composed of big data, business process design, decision information, and human-computer interaction needs to develop in a more advanced and intelligent systematized direction.

[0004] The multi-source data fusion model of the distribution network faces two major challenges. First, the original technical platform is outdated and cannot adapt to business innovation in the era of digital technology. Second, many new technologies are difficult to match with the original system. The integration of new and old systems is a difficulty in platform innovation. Digital system integration requires the integration of digital informationization, networking and intelligence. There is no clear and strict boundary or mark between the three. They are all important components of digital development. The three have a progressive relationship, but they exist in parallel at the same time.

[0005] Common Information Model (CIM for short) is a public information model used for power system modeling and data exchange. In the process of power distribution network topology flow calculation, fault simulation, etc., the CIM model generated by the CIM file must first be imported to form the network topology. However, the data supporting the simulation includes equipment inventory data, equipment operation data, geographic location information data, etc. The source of these data is the original systems, including enterprise asset management system (EAM), SCADA system, geographic information system (GIS), etc. However, the data definitions of the original system equipment are not unified, resulting in the data of the original system cannot be directly applied to the new system for simulation. The existing data model does not integrate the data collected by each system into a unified equipment model, which is very troublesome to use and requires several manual data conversions before it can be used. Summary of the invention

[0006] In order to overcome the problems existing in the above-mentioned related technologies, the present application provides a multi-source data fusion method and system based on feeder-level CIM files.

[0007] According to a first aspect of an embodiment of the present application, a multi-source data fusion method based on a feeder-level CIM file is provided, comprising:

[0008] Generate a structured CIM model based on a common information model CIM file of a distribution network feeder, and fill the data in the CIM model into a pre-built device fusion model; the CIM file of the distribution network feeder includes: network topology content and device information;

[0009] Extracting external system data according to the device information, and backfilling the external system data into the device fusion model;

[0010] The device fusion model is constructed using a device model table.

[0011] Preferably, the device information includes: device ID and device type.

[0012] Preferably, the process of establishing the device fusion model includes:

[0013] Based on the preset equipment types, create equipment model tables for each type of equipment in the database;

[0014] The device fusion model is constructed using device model tables of all types of devices.

[0015] Preferably, the device fusion model includes at least one of the following models:

[0016] Plant model, power supply model, busbar model, switch model, cable model, transformer model, compensation equipment model, load model and new energy model.

[0017] Preferably, the generating of a structured CIM model based on the CIM file of the distribution network feeder includes:

[0018] Import the network topology content and device information in the CIM file of the distribution network feeder into the memory;

[0019] Create a device object according to the device type in the device information of the CIM file;

[0020] The network topology content of the CIM file is read in sequence in a traversal manner, and the structured fields in the network topology content of the CIM file are added to the device objects corresponding thereto to generate a structured CIM model.

[0021] Preferably, filling the data in the CIM model into a pre-built device fusion model includes:

[0022] Based on a preset device fusion model mapping table, mapping each device in the CIM model with a device in the device fusion model;

[0023] The network topology content and structured fields in the device information corresponding to each device in the CIM model are filled into the devices in the device fusion model corresponding to each device in the CIM model.

[0024] Preferably, extracting external system data according to the device information includes:

[0025] According to the device information of each device in the device fusion model, calling the external system mapping file corresponding to the device information of each device in the device fusion model;

[0026] The external system data extraction subroutine is called to extract structured query language SQL text information according to the data in the external system mapping file, access the external system database, and extract the external system data corresponding to the device information of each device in the device fusion model.

[0027] Preferably, the calling of a subroutine for extracting external system data includes:

[0028] Loading the device ID of each device in the device fusion model, the device type of each device in the device fusion model, data extraction related information, external system database information and data set template; the data extraction related information at least includes: data extraction SQL text information;

[0029] Based on the device ID of each device in the device fusion model, the device type of each device in the device fusion model and the external system database information, determine whether the data of the external system database can be extracted; if so, use the data extraction SQL text information to extract the data to obtain a data extraction result set; if not, end the call of the subroutine for extracting external system data;

[0030] Determine whether the data extraction result set is empty. If the data extraction result set is not empty, transfer the data extraction result set to the external system data subroutine and fill it into the device fusion model; otherwise, terminate the call of the external system data extraction subroutine.

[0031] Preferably, judging whether data from the external system database can be extracted based on the device ID of each device in the device fusion model, the device type of each device in the device fusion model and the external system database information includes:

[0032] According to the device ID and device type of each device in the device fusion model, determine whether the external system database authorizes the device fusion model to access the external system database. If the external system database authorizes the device fusion model to access the external system database, determine whether the external system database information is complete; otherwise, terminate the call of the subroutine for extracting external system data.

[0033] Determine whether the external system database information is complete. If the external system database information is complete, data from the external system database can be extracted, and the data extraction SQL text information is called to access the external system database. After successfully connecting to the external system database, data extraction is performed, and the extracted data is stored in the data set template to obtain a data extraction result set; otherwise, the call to the subroutine for extracting external system data is terminated.

[0034] Preferably, when the external system database is an enterprise asset management system database, the external system database information includes: enterprise asset management system database information;

[0035] The data set template includes: an equipment inventory data set template.

[0036] Preferably, when the external system database is a geographic information system database, the external system database information includes: geographic information system database information;

[0037] The data set template includes: equipment GIS data set template.

[0038] Preferably, when the external system database is a SCADA system database, the external system database information includes: SCADA system database information;

[0039] The data extraction related information also includes: the start time of extracting the running data and the end time of extracting the running data;

[0040] The data set template includes: a device operation data set template.

[0041] Preferably, when the external system database is a SCADA system database, the calling and extracting external system data subroutine further comprises:

[0042] The start time of extracting the running data and the end time of extracting the running data are loaded.

[0043] Preferably, when the external system database is a SCADA system database, before determining whether the external system database information is complete, the process further includes:

[0044] Determine whether the start time of extracting running data and the end time of extracting running data meet the date query specification. If the start time of extracting running data and the end time of extracting running data meet the date query specification, determine whether the external system database information is complete; otherwise, terminate the call of the subroutine for extracting external system data.

[0045] Preferably, the method further comprises:

[0046] Based on the network topology content in the CIM file, the data in the device fusion model is visualized.

[0047] Preferably, the visual display of the data in the device fusion model based on the network topology content in the CIM file includes:

[0048] The network topology content in the CIM file is bound to the device fusion model, so that when the primitive attributes in the network topology are opened, the attribute information in the device fusion model corresponding to the primitive attributes is visually displayed.

[0049] According to a second aspect of an embodiment of the present application, a multi-source data fusion system based on a feeder-level CIM file is provided, including:

[0050] A first filling unit is used to generate a structured CIM model based on a common information model CIM file of a distribution network feeder, and fill the data in the CIM model into a pre-built device fusion model; the CIM file of the distribution network feeder includes: network topology content and device information;

[0051] A second filling unit, configured to extract external system data according to the device information, and backfill the external system data into the device fusion model;

[0052] The device fusion model is constructed using a device model table.

[0053] Preferably, the device information includes: device ID and device type.

[0054] Preferably, it further comprises: an establishing unit, used to establish the device fusion model; the establishing unit comprises:

[0055] A first creation module is used to create a device model table of each type of device in the database based on the preset device type;

[0056] A construction module is used to construct the device fusion model by using device model tables of all types of devices.

[0057] Preferably, the device fusion model includes at least one of the following models:

[0058] Plant model, power supply model, busbar model, switch model, cable model, transformer model, compensation equipment model, load model and new energy model.

[0059] Preferably, the first filling unit comprises:

[0060] Import module, used to import network topology content and device information in the CIM file of the distribution network feeder into the memory;

[0061] A second creation module, used to create a device object according to the device type in the device information of the CIM file;

[0062] The generation module is used to read the network topology content of the CIM file in turn in a traversal manner, add the structured fields in the network topology content of the CIM file to the corresponding device objects, and generate a structured CIM model.

[0063] Preferably, the first filling unit further includes:

[0064] A mapping module, used for mapping each device in the CIM model with a device in the device fusion model based on a preset device fusion model mapping table;

[0065] The filling module is used to fill the network topology content and structured fields in the device information corresponding to each device in the CIM model into the devices in the device fusion model corresponding to each device in the CIM model.

[0066] Preferably, the second filling unit comprises:

[0067] A calling module, used for calling an external system mapping file corresponding to the device information of each device in the device fusion model according to the device information of each device in the device fusion model;

[0068] The extraction module is used to call the subroutine for extracting external system data to extract structured query language SQL text information according to the data in the external system mapping file, access the external system database, and extract the external system data corresponding to the device information of each device in the device fusion model.

[0069] Preferably, the extraction module comprises:

[0070] A loading submodule is used to load the device ID of each device in the device fusion model, the device type of each device in the device fusion model, data extraction related information, external system database information and data set template; the data extraction related information at least includes: data extraction SQL text information;

[0071] The first judgment submodule is used to judge whether the data of the external system database can be extracted based on the device ID of each device in the device fusion model, the device type of each device in the device fusion model and the external system database information. If yes, the data is extracted by using the data extraction SQL text information to obtain a data extraction result set; if not, the call of the subroutine for extracting external system data is terminated;

[0072] The second judgment submodule is used to judge whether the data extraction result set is empty. If the data extraction result set is not empty, the data extraction result set is transmitted to the external system data subroutine and filled into the device fusion model; otherwise, the call of the external system data extraction subroutine is terminated.

[0073] Preferably, the first judgment submodule is specifically used to:

[0074] According to the device ID and device type of each device in the device fusion model, determine whether the external system database authorizes the device fusion model to access the external system database. If the external system database authorizes the device fusion model to access the external system database, determine whether the external system database information is complete; otherwise, terminate the call of the subroutine for extracting external system data.

[0075] Determine whether the external system database information is complete. If the external system database information is complete, data from the external system database can be extracted, and the data extraction SQL text information is called to access the external system database. After successfully connecting to the external system database, data extraction is performed, and the extracted data is stored in the data set template to obtain a data extraction result set; otherwise, the call to the subroutine for extracting external system data is terminated.

[0076] Preferably, it also includes:

[0077] A visualization unit is used to visualize the data in the device fusion model based on the network topology content in the CIM file.

[0078] Preferably, the visualization unit is specifically used for:

[0079] The network topology content in the CIM file is bound to the device fusion model, so that when the primitive attributes in the network topology are opened, the attribute information in the device fusion model corresponding to the primitive attributes is visually displayed.

[0080] According to a third aspect of an embodiment of the present application, there is provided an electronic device, comprising: at least one processor and a memory; the memory and the processor are connected via a bus;

[0081] The memory is used to store one or more programs;

[0082] When the one or more programs are executed by the at least one processor, the multi-source data fusion method based on the feeder-level CIM file is implemented.

[0083] According to a fourth aspect of an embodiment of the present application, a readable storage medium is provided, on which an execution program is stored. When the execution program is executed, the multi-source data fusion method based on the feeder-level CIM file is implemented.

[0084] The technical solution provided by the present invention has the following beneficial effects:

[0085] The present invention provides a multi-source data fusion method and system based on feeder-level CIM files. A structured CIM model is generated based on the CIM files of distribution network feeders, and the data in the CIM model is filled into a pre-built device fusion model. The CIM files of distribution network feeders include: network topology content and device information. By extracting external system data according to the device information and backfilling the external system data into the device fusion model, not only the data of devices of various systems are integrated to provide data support for various simulations, but also the working efficiency of data fusion is improved, and auxiliary decision support is provided for the safe, reliable and economical operation of the distribution network, thereby effectively tapping the power supply potential of the active distribution network and improving the power supply service quality level. BRIEF DESCRIPTION OF THE DRAWINGS

[0086] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0087] Figure 1 is a flow chart of a multi-source data fusion method based on a feeder-level CIM file provided by an embodiment of the present invention;

[0088] Figure 2 It is a structural block diagram of a multi-source data fusion system based on a feeder-level CIM file provided by an embodiment of the present invention;

[0089] Figure 3 It is a main structural block diagram of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0090] In order to make the purpose, technical solution and advantages of the present invention clearer, the technical solution of the present invention will be clearly and completely described below in conjunction with the accompanying drawings. Obviously, the following embodiments are part of the embodiments of the present invention, rather than all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0091] Embodiment 1

[0092] The present invention provides a multi-source data fusion method based on feeder-level CIM files, such as Figure 1 As shown, the following steps are included:

[0093] Step 11: Generate a structured CIM model based on the common information model CIM file of the distribution network feeder, and fill the data in the CIM model into the pre-built device fusion model; the CIM file of the distribution network feeder includes: network topology content and device information;

[0094] Step 12: Extract external system data based on device information and fill the external system data back into the device fusion model;

[0095] The device fusion model is built using the device model table.

[0096] Furthermore, the device information includes: device ID and device type.

[0097] Furthermore, the process of establishing the device fusion model includes:

[0098] Based on the preset equipment types, create equipment model tables for each type of equipment in the database;

[0099] Build a device fusion model using device model tables for all types of devices.

[0100] The present invention does not limit the "database for creating device model tables of various types of devices", which can be selected by those skilled in the art according to engineering needs. In some embodiments, an Oracle database or a MySQL database can be used, but is not limited to it.

[0101] For example, in the Oracle database, different device model tables are created through the Create Table command according to different device types.

[0102] Furthermore, the device fusion model includes at least one of the following models:

[0103] Plant model, power supply model, busbar model, switch model, cable model, transformer model, compensation equipment model, load model and new energy model.

[0104] In some embodiments, the table structures of the plant model, power supply model, busbar model, switch model, cable model, transformer model, compensation device model, load model and new energy model are shown in Table 1 to Table 9. New energy equipment may include but is not limited to: generators, wind power, photovoltaics, gas turbines, fuel cells and batteries.

[0105] Table 1 Equipment model table of power supply model

[0106]

[0107]

[0108] Table 2 Equipment model table of busbar model

[0109]

[0110]

[0111] Table 3 Equipment model table of cable model

[0112]

[0113]

[0114] Table 4 Equipment model table of switch model

[0115]

[0116]

[0117] Table 5 Equipment model table of transformer model

[0118]

[0119]

[0120]

[0121] Table 6 Equipment model table of load model

[0122]

[0123]

[0124] Table 7 Equipment model table of compensation equipment model

[0125]

[0126]

[0127] Table 8 Equipment model table of plant model

[0128]

[0129] Table 9 Equipment model table of plant model

[0130]

[0131]

[0132]

[0133] Digital system fusion technology can be applied to the efficient use of digital substation data, making information collection more direct and fault elimination more intelligent in the process of handling distribution network defects and faults. The present invention integrates data of SCADA system, enterprise asset management system (EAM), geographic information system (GIS), etc. according to the specifications in the power grid common information model (CIM), establishes a device fusion model for multi-source data fusion based on CIM, automatically integrates the data of equipment in each system, and achieves data support for various simulations of the new system, thereby improving the work efficiency of data fusion and better displaying model data.

[0134] Furthermore, in step 11, a structured CIM model is generated based on the CIM file of the distribution network feeder, including:

[0135] Step 111: Import the network topology content and device information in the CIM file of the distribution network feeder into the memory;

[0136] Step 112: Create a device object according to the device type in the device information of the CIM file;

[0137] Step 113: read the network topology content of the CIM file in turn in a traversal manner, add the structured fields in the network topology content of the CIM file to the corresponding device objects, and generate a structured CIM model.

[0138] For example, in actual applications, you can choose to import the CIM file function, import the feeder's CIM file (the feeder's CIM file includes: network topology content and device information) into the memory, and generate a structured CIM model. The specific operation is: click the Import CIM File button, open the file selection box, select the feeder-level CIM file to be imported, click the OK button, import the network topology content and device information in the feeder-level CIM file into the memory, create a device object according to the device type, read the CIM file content in turn through the traversal method, add the structured fields in the CIM file to the corresponding type of device object, and generate a structured CIM model.

[0139] The feeder-level CIM file refers to the network topology of the distribution network feeder, which is a diagram of all the devices connected in the feeder. Extract a certain device from the feeder-level CIM file and import the basic information into the device fusion model. If the CIM file is not structured, it will be disorganized and cannot be extracted. Therefore, the CIM file has certain rules, and the desired device information can be extracted according to the rules.

[0140] Furthermore, in step 11, the data in the CIM model is filled into the pre-built device fusion model, including:

[0141] Step 114: Mapping each device in the CIM model with a device in the device fusion model based on a preset device fusion model mapping table;

[0142] Step 115: Fill the network topology content and structured fields in the device information corresponding to each device in the CIM model into the device in the device fusion model corresponding to each device in the CIM model.

[0143] For example, in the process of traversing and reading the CIM model, the data of the corresponding device type is a two-winding transformer, and the data is stored in the fields defined in the device fusion model according to the structured fields in the CIM model.

[0144] It can be understood that the device fusion model mapping table contains cim device model code and device fusion model code. Through cim device model code, the corresponding device fusion model code is found, so that the corresponding attributes in the cim device model are assigned to the attributes of the device fusion model of the specified code. Each device in the CIM model is mapped to the device in the device fusion model mapping table of the corresponding device fusion model, that is, the defined device type and device fusion model mapping table are loaded. For example, the device integration model sets 9 types. Loading the defined device types means loading these 9 device type fusion models. Then, through the CODE (such as C001) of the device (such as transformer) in the CIM file, find the device CODE=C001 in the device fusion model mapping table, which proves that the device exists in the device fusion mapping table. Then, through the CODE (such as R0035) of the device in the fusion model in the device fusion model mapping table, the device in the CIM model and the device in the fusion model are mapped together. In this way, some basic information such as device connection relationship and device name can be extracted from the CIM model and imported into the fusion model of the device.

[0145] Furthermore, in step 12, the external system data is extracted according to the device information, including:

[0146] Step 121: according to the device information of each device in the device fusion model, calling the external system mapping file corresponding to the device information of each device in the device fusion model;

[0147] Step 122: call the external system data extraction subroutine to extract structured query language SQL text information according to the data in the external system mapping file, access the external system database, and extract the external system data corresponding to the device information of each device in the device fusion model.

[0148] SQL stands for Structured Query Language, which can be used to access and process databases, including data insertion, query, update, and deletion.

[0149] It should be noted that the external system mapping file is a supporting file for importing external system data into the device fusion model. The external system mapping file is pre-defined, including: which external system data is connected, which model is connected, and which data is obtained. Among them, the specific content of the external system mapping file includes: the IP, port number, user name, password, device type, device ID, SQL, etc. of the external system database. The external system database is an existing database, including: PMS system database, GIS system database, and SCADA system database.

[0150] The present invention aims at the equipment fusion model based on the feeder-level CIM file, and completes the attribute setting of the integrated graph and model, including (plant model, power supply model, busbar model, switch model, cable model, transformer model, compensation equipment model, load model and new energy model, etc.). Through the equipment ID mapping table, the relevant data of different systems can be extracted and filled into the equipment fusion model, which can more conveniently meet the data requirements of the simulation of the entire network topology.

[0151] Further, step 122 includes:

[0152] Step 1221: Load the device ID of each device in the device fusion model, the device type of each device in the device fusion model, data extraction related information, external system database information and data set template; the data extraction related information at least includes: data extraction SQL text information;

[0153] Step 1222: Based on the device ID of each device in the device fusion model, the device type of each device in the device fusion model and the external system database information, determine whether the data in the external system database can be extracted. If so, extract the data using the data extraction SQL text information to obtain a data extraction result set; if not, terminate the call of the subroutine for extracting external system data.

[0154] Step 1223: Determine whether the data extraction result set is empty. If the data extraction result set is not empty, transfer the data extraction result set to the external system data subroutine and fill it into the device fusion model; otherwise, terminate the call of the external system data extraction subroutine.

[0155] Further, step 1222 includes:

[0156] Step 1222a: According to the device ID and device type of each device in the device fusion model, determine whether the external system database authorizes the device fusion model to access the external system database. If the external system database authorizes the device fusion model to access the external system database, execute step 1222b; otherwise, terminate the call of the subroutine for extracting external system data.

[0157] Step 1222b: Determine whether the external system database information is complete. If the external system database information is complete, the data of the external system database can be extracted, and the data extraction SQL text information is called to access the external system database. After successfully connecting to the external system database, data extraction is performed, and the extracted data is stored in the data set template to obtain the data extraction result set; otherwise, the call of the subroutine for extracting external system data is terminated.

[0158] Further, when the external system database is an enterprise asset management system database, the external system database information includes: enterprise asset management system database information;

[0159] Data set templates include: Equipment inventory data set template.

[0160] Further, when the external system database is a geographic information system database, the external system database information includes: geographic information system database information;

[0161] Dataset templates include: Equipment GIS dataset template.

[0162] Further, when the external system database is a SCADA system database, the external system database information includes: SCADA system database information;

[0163] The data extraction related information also includes: the start time of the extraction operation data and the end time of the extraction operation data;

[0164] The data set templates include: equipment operation data set template.

[0165] Further, when the external system database is a SCADA system database, step 1221 further includes:

[0166] Load the start time and end time of the extraction operation data.

[0167] In some embodiments, the formats of the start time and the end time of extracting the running data may be, but are not limited to, set to YYYY-MM-DD HH24:MI:SS, for example, 2024-01-01 14:00:00.

[0168] Further, when the external system database is a SCADA system database, before executing step 1222 in step 1221, the following steps are also included:

[0169] Determine whether the start time and end time of the extracted running data meet the date query specifications. If the start time and end time of the extracted running data meet the date query specifications, execute step 2; otherwise, end the call of the subroutine for extracting external system data.

[0170] For example, assuming that the external system database is an enterprise asset management system (EAM) database, a SCADA system database, and a geographic information system (GIS) database, the specific steps for calling a subroutine to extract external system data are as follows.

[0171] (1) The external system database is an enterprise asset management system (EAM) database. The specific steps of calling the subroutine to extract external system data include:

[0172] Step a: Load the device ID of the device fusion model, the device type of the device fusion model, the data extraction SQL text information, the enterprise asset management system database information and the equipment ledger data set template;

[0173] Step b: According to the device ID and device type of the device fusion model, determine whether the enterprise asset management system database authorizes the device fusion model to access the enterprise asset management system database. If the enterprise asset management system database authorizes the device fusion model to access the enterprise asset management system database, execute step c; otherwise, terminate the call of the subroutine for extracting external system data.

[0174] Step c: Determine whether the enterprise asset management system database information is complete. If the enterprise asset management system database information is complete, call the data extraction SQL text information to access the enterprise asset management system database. After successfully connecting to the enterprise asset management system database, extract data and store the extracted data in the equipment inventory data set template to obtain the data extraction result set and execute step d; otherwise, end the call of the subroutine for extracting external system data.

[0175] Step d: Determine whether the data extraction result set is empty. If the data extraction result set is not empty, the data extraction result set is transferred out of the external system data subroutine and filled into the device fusion model; otherwise, the call of the external system data extraction subroutine is terminated.

[0176] (2) The external system database is the SCADA system database. The specific steps of calling the subroutine to extract external system data include:

[0177] Step e: Load the device ID of the device fusion model, the device type of the device fusion model, the start time of extracting operation data, the end time of extracting operation data, the data extraction SQL text information, the SCADA system database information and the device operation data set template;

[0178] Step f: According to the device ID and device type of the device fusion model, determine whether the SCADA system database authorizes the device fusion model to access the SCADA system database. If the SCADA system database authorizes the device fusion model to access the SCADA system database, execute step g; otherwise, terminate the call of the subroutine for extracting external system data.

[0179] Step g: Determine whether the start time and the end time of the operation data extraction meet the date query specification. If the start time and the end time of the operation data extraction meet the date query specification, execute step h; otherwise, terminate the call of the subroutine for extracting external system data.

[0180] Step h: Determine whether the SCADA system database information is complete. If the SCADA system database information is complete, call the data extraction SQL text information to access the SCADA system database. After successfully connecting to the SCADA system database, extract data and store the extracted data in the equipment operation data set template to obtain the data extraction result set and execute step i; otherwise, end the call of the subroutine for extracting external system data.

[0181] Step i: Determine whether the data extraction result set is empty. If the data extraction result set is not empty, the data extraction result set is transferred out of the external system data subroutine and filled into the device fusion model; otherwise, the call of the external system data extraction subroutine is terminated.

[0182] (3) The external system database is a geographic information system (GIS) database. The specific steps of calling the subroutine to extract external system data include:

[0183] Step j: Load the device ID of the device fusion model, the device type of the device fusion model, the data extraction SQL text information, the geographic information system database information and the device GIS data set template;

[0184] Step k: according to the device ID and device type of the device fusion model, determine whether the GIS database authorizes the device fusion model to access the GIS database. If the GIS database authorizes the device fusion model to access the GIS database, execute step m; otherwise, terminate the call of the subroutine for extracting external system data.

[0185] Step m: Determine whether the GIS database information is complete. If the GIS database information is complete, call the data extraction SQL text information to access the GIS database. After successfully connecting to the GIS database, extract data and store the extracted data in the device GIS data set template to obtain the data extraction result set and execute step n; otherwise, end the call of the subroutine for extracting external system data.

[0186] Step n: Determine whether the data extraction result set is empty. If the data extraction result set is not empty, the data extraction result set is transferred out of the external system data subroutine and filled into the device fusion model; otherwise, the call of the external system data extraction subroutine is terminated.

[0187] Furthermore, the method further includes:

[0188] Step 13: Based on the network topology content in the CIM file, visualize the data in the device fusion model.

[0189] Further, step 13 includes:

[0190] Bind the network topology content in the CIM file to the device fusion model so that when the primitive attributes in the network topology are opened, the attribute information in the device fusion model corresponding to the primitive attributes can be visually displayed.

[0191] The present invention visualizes the data in the device fusion model based on the network topology content in the CIM file, so as to better display the model data.

[0192] It should be noted that the device fusion model in the network topology is displayed on the page, and the graphics elements in the network topology have been bound to the device fusion model. By opening the graphics element properties in the network topology, all attribute information in the device fusion model (including equipment inventory information, equipment GIS information, equipment operation data information, etc.) can be displayed.

[0193] Aiming at the different data requirements of current enterprise asset management systems (EAM), SCADA systems, geographic information systems (GIS), etc., and the inability of single system equipment data information to support various simulation data requirements of new systems, the present invention provides a multi-source data fusion method and system based on feeder-level CIM files. By extracting data from multi-source databases such as enterprise asset management systems (EAM), SCADA systems, geographic information systems (GIS), etc., a new type of equipment fusion model is implemented in the new system, and then various network topologies are simulated and calculated, various practical problems occurring in power distribution are analyzed and verified, and auxiliary decision-making support is provided for safe, reliable and economical operation of the distribution network, thereby effectively tapping the power supply potential of the active distribution network and improving the quality level of power supply services.

[0194] Embodiment 2

[0195] The present invention provides a multi-source data fusion system based on feeder-level CIM files, such as Figure 2 As shown, including:

[0196] The first filling unit is used to generate a structured CIM model based on a common information model CIM file of a distribution network feeder, and fill the data in the CIM model into a pre-built device fusion model; the CIM file of the distribution network feeder includes: network topology content and device information;

[0197] The second filling unit is used to extract external system data according to the device information and fill the external system data back into the device fusion model;

[0198] The device fusion model is built using the device model table.

[0199] Furthermore, the device information includes: device ID and device type.

[0200] Furthermore, it also includes: an establishment unit for establishing a device fusion model; the establishment unit includes:

[0201] A first creation module is used to create a device model table of each type of device in the database based on the preset device type;

[0202] A building module for building a device fusion model using device model tables for all types of devices.

[0203] Furthermore, the device fusion model includes at least one of the following models:

[0204] Plant model, power supply model, busbar model, switch model, cable model, transformer model, compensation equipment model, load model and new energy model.

[0205] Furthermore, the first filling unit includes:

[0206] Import module, used to import network topology content and device information in the CIM file of the distribution network feeder into the memory;

[0207] The second creation module is used to create a device object according to the device type in the device information of the CIM file;

[0208] The generation module is used to read the network topology content of the CIM file in turn in a traversal manner, add the structured fields in the network topology content of the CIM file to the corresponding device objects, and generate a structured CIM model.

[0209] Furthermore, the first filling unit further includes:

[0210] A mapping module, used for mapping each device in the CIM model with a device in the device fusion model based on a preset device fusion model mapping table;

[0211] The filling module is used to fill the network topology content and structured fields in the device information corresponding to each device in the CIM model into the devices in the device fusion model corresponding to each device in the CIM model.

[0212] Furthermore, the second filling unit comprises:

[0213] A calling module, used for calling an external system mapping file corresponding to the device information of each device in the device fusion model according to the device information of each device in the device fusion model;

[0214] The extraction module is used to call the subroutine for extracting external system data to extract structured query language SQL text information according to the data in the external system mapping file, access the external system database, and extract the external system data corresponding to the device information of each device in the device fusion model.

[0215] Furthermore, the extraction module includes:

[0216] The loading submodule is used to load the device ID of each device in the device fusion model, the device type of each device in the device fusion model, data extraction related information, external system database information and data set template; the data extraction related information at least includes: data extraction SQL text information;

[0217] The first judgment submodule is used to judge whether the data of the external system database can be extracted based on the device ID of each device in the device fusion model, the device type of each device in the device fusion model and the external system database information. If yes, the data is extracted using the data extraction SQL text information to obtain a data extraction result set; if not, the call of the subroutine for extracting external system data is terminated;

[0218] The second judgment submodule is used to judge whether the data extraction result set is empty. If the data extraction result set is not empty, the data extraction result set is transmitted to the external system data subroutine and filled into the device fusion model; otherwise, the call of the external system data extraction subroutine is terminated.

[0219] Furthermore, the first judgment submodule is specifically used for:

[0220] According to the device ID and device type of each device in the device fusion model, determine whether the external system database authorizes the device fusion model to access the external system database. If the external system database authorizes the device fusion model to access the external system database, determine whether the external system database information is complete; otherwise, end the call of the subroutine for extracting external system data.

[0221] Determine whether the external system database information is complete. If the external system database information is complete, you can extract the data from the external system database, call the data extraction SQL text information to access the external system database, extract data after successfully connecting to the external system database, and store the extracted data in the data set template to obtain the data extraction result set; otherwise, end the call of the subroutine for extracting external system data.

[0222] Further, when the external system database is an enterprise asset management system database, the external system database information includes: enterprise asset management system database information;

[0223] Data set templates include: Equipment inventory data set template.

[0224] Further, when the external system database is a geographic information system database, the external system database information includes: geographic information system database information;

[0225] Dataset templates include: Equipment GIS dataset template.

[0226] Further, when the external system database is a SCADA system database, the external system database information includes: SCADA system database information;

[0227] The data extraction related information also includes: the start time of the extraction operation data and the end time of the extraction operation data;

[0228] The data set templates include: equipment operation data set template.

[0229] Furthermore, when the external system database is a SCADA system database, the loading submodule is also used for:

[0230] Load the start time and end time of the extraction operation data.

[0231] Further, when the external system database is a SCADA system database, before determining whether the external system database information is complete, it also includes:

[0232] Determine whether the start time and the end time of extracting running data meet the date query specifications. If the start time and the end time of extracting running data meet the date query specifications, determine whether the external system database information is complete; otherwise, terminate the call of the subroutine for extracting external system data.

[0233] Furthermore, the device further comprises:

[0234] The visualization unit is used to visualize the data in the device fusion model based on the network topology content in the CIM file.

[0235] Furthermore, the visualization unit is specifically used for:

[0236] Bind the network topology content in the CIM file to the device fusion model so that when the primitive attributes in the network topology are opened, the attribute information in the device fusion model corresponding to the primitive attributes can be visually displayed.

[0237] It can be understood that the system embodiment provided above corresponds to the method embodiment described above, and the corresponding specific contents can be referenced to each other and will not be repeated here.

[0238] It can be understood that the same or similar parts of the above embodiments can be referenced to each other, and the contents not described in detail in some embodiments can refer to the same or similar contents in other embodiments.

[0239] Embodiment 3

[0240] like Figure 3 As shown, the present invention also provides an electronic device, which may be a computer device, a single-chip device, an intelligent mobile device, etc. The electronic device in this embodiment may include a processor, a memory, a transceiver component, etc. The memory, the processor, and the transceiver component are connected via a bus; the memory may be used to store an execution program, and an exemplary execution program may include instructions; the processor is used to execute the instructions stored in the memory. The memory may also be used to store data, which may be called and / or modified when the instructions are executed.

[0241] The processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. It is the computing core and control core of the terminal, which is suitable for implementing one or more instructions, specifically suitable for loading and executing one or more instructions in a storage medium to implement a corresponding method flow or a corresponding function, so as to implement the steps of a multi-source data fusion method based on a feeder-level CIM file in the above-mentioned embodiment.

[0242] Embodiment 4

[0243] Based on the same inventive concept, the present invention also provides a readable storage medium, specifically an electronic device readable storage medium (Memory), which is a memory device in an electronic device for storing programs and data. It can be understood that the storage medium here can include both built-in storage media in the electronic device and, of course, extended storage media supported by the electronic device. The storage medium provides a storage space, which stores the operating system of the terminal. In addition, one or more instructions suitable for being loaded and executed by the processor are also stored in the storage space, and these instructions can be one or more execution programs (including program codes). It should be noted that the storage medium here can be a high-speed RAM memory or a non-volatile memory, such as at least one disk memory. The processor loads and executes one or more instructions stored in the storage medium, which can implement the steps of a multi-source data fusion method based on a feeder-level CIM file in the above embodiment.

[0244] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0245] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0246] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0247] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0248] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention rather than to limit it. Although the present invention has been described in detail with reference to the above embodiments, ordinary technicians in the relevant field should understand that the specific implementation methods of the present invention can still be modified or replaced by equivalents. Any modification or equivalent replacement that does not depart from the spirit and scope of the present invention should be covered within the scope of protection of the claims of the present invention.

Claims

1. A multi-source data fusion method based on feeder-level CIM files, It is characterized in that include: Generate a structured CIM model based on a common information model (CIM) file of a distribution network feeder, and fill the data in the CIM model into a pre-built device fusion model; The CIM file of the distribution network feeder includes: network topology content and equipment information; Extracting external system data according to the device information, and backfilling the external system data into the device fusion model; The device fusion model is constructed using a device model table.

2. The method according to claim 1, It is characterized in that The device information includes: device ID and device type.

3. The method according to claim 1, It is characterized in that The process of establishing the device fusion model includes: Based on the preset equipment types, create equipment model tables for each type of equipment in the database; The device fusion model is constructed using device model tables of all types of devices.

4. The method according to claim 1, It is characterized in that The device fusion model includes at least one of the following models: Plant model, power supply model, busbar model, switch model, cable model, transformer model, compensation equipment model, load model and new energy model.

5. The method according to claim 1, It is characterized in that The generating of a structured CIM model based on the CIM file of the distribution network feeder includes: Import the network topology content and device information in the CIM file of the distribution network feeder into the memory; Create a device object according to the device type in the device information of the CIM file; The network topology content of the CIM file is read in sequence in a traversal manner, and the structured fields in the network topology content of the CIM file are added to the device objects corresponding thereto to generate a structured CIM model.

6. The method according to claim 1, It is characterized in that Filling the data in the CIM model into the pre-built device fusion model includes: Based on a preset device fusion model mapping table, mapping each device in the CIM model with a device in the device fusion model; The network topology content and structured fields in the device information corresponding to each device in the CIM model are filled into the devices in the device fusion model corresponding to each device in the CIM model.

7. The method according to claim 1, It is characterized in that The extracting external system data according to the device information includes: According to the device information of each device in the device fusion model, calling the external system mapping file corresponding to the device information of each device in the device fusion model; The external system data extraction subroutine is called to extract structured query language SQL text information according to the data in the external system mapping file, access the external system database, and extract the external system data corresponding to the device information of each device in the device fusion model.

8. The method according to claim 7, It is characterized in that The calling of the subroutine for extracting external system data includes: Loading the device ID of each device in the device fusion model, the device type of each device in the device fusion model, data extraction related information, external system database information and data set template; the data extraction related information at least includes: data extraction SQL text information; Based on the device ID of each device in the device fusion model, the device type of each device in the device fusion model and the external system database information, determine whether the data of the external system database can be extracted; if so, use the data extraction SQL text information to extract the data to obtain a data extraction result set; if not, end the call of the subroutine for extracting external system data; Determine whether the data extraction result set is empty. If the data extraction result set is not empty, transfer the data extraction result set to the external system data subroutine and fill it into the device fusion model; otherwise, terminate the call of the external system data extraction subroutine.

9. The method according to claim 8, It is characterized in that The determining whether data from the external system database can be extracted based on the device ID of each device in the device fusion model, the device type of each device in the device fusion model, and the external system database information includes: According to the device ID and device type of each device in the device fusion model, determine whether the external system database authorizes the device fusion model to access the external system database. If the external system database authorizes the device fusion model to access the external system database, determine whether the external system database information is complete; otherwise, terminate the call of the subroutine for extracting external system data. Determine whether the external system database information is complete. If the external system database information is complete, data from the external system database can be extracted, and the data extraction SQL text information is called to access the external system database. After successfully connecting to the external system database, data extraction is performed, and the extracted data is stored in the data set template to obtain a data extraction result set; otherwise, the call to the subroutine for extracting external system data is terminated.

10. The method according to claim 8, It is characterized in that When the external system database is an enterprise asset management system database, the external system database information includes: enterprise asset management system database information; The data set template includes: an equipment inventory data set template.

11. The method according to claim 8, It is characterized in that When the external system database is a geographic information system database, the external system database information includes: geographic information system database information; The data set template includes: a device GIS data set template.

12. The method according to claim 9, It is characterized in that When the external system database is a SCADA system database, the external system database information includes: SCADA system database information; The data extraction related information also includes: the start time of extracting the running data and the end time of extracting the running data; The data set template includes: a device operation data set template.

13. The method according to claim 12, It is characterized in that When the external system database is a SCADA system database, the calling of the subroutine for extracting external system data further includes: The start time of extracting the running data and the end time of extracting the running data are loaded.

14. The method according to claim 12, It is characterized in that When the external system database is a SCADA system database, before determining whether the external system database information is complete, the method further includes: Determine whether the start time of extracting running data and the end time of extracting running data meet the date query specification. If the start time of extracting running data and the end time of extracting running data meet the date query specification, determine whether the external system database information is complete; otherwise, terminate the call of the subroutine for extracting external system data.

15. The method according to claim 1, It is characterized in that Also includes: Based on the network topology content in the CIM file, the data in the device fusion model is visualized.

16. The method according to claim 15, It is characterized in that The visual display of the data in the device fusion model based on the network topology content in the CIM file includes: The network topology content in the CIM file is bound to the device fusion model, so that when the primitive attributes in the network topology are opened, the attribute information in the device fusion model corresponding to the primitive attributes is visually displayed.

17. A multi-source data fusion system based on feeder-level CIM files, It is characterized in that include: A first filling unit is used to generate a structured CIM model based on a common information model CIM file of a distribution network feeder, and fill the data in the CIM model into a pre-built device fusion model; The CIM file of the distribution network feeder includes: network topology content and equipment information; A second filling unit, configured to extract external system data according to the device information, and backfill the external system data into the device fusion model; The device fusion model is constructed using a device model table.

18. The system according to claim 17, It is characterized in that The device information includes: device ID and device type.

19. The system according to claim 17, It is characterized in that It also includes: an establishing unit, used to establish the device fusion model; the establishing unit includes: A first creation module is used to create a device model table of each type of device in the database based on the preset device type; A construction module is used to construct the device fusion model by using device model tables of all types of devices.

20. The system according to claim 17, It is characterized in that The device fusion model includes at least one of the following models: Plant model, power supply model, busbar model, switch model, cable model, transformer model, compensation equipment model, load model and new energy model.

21. The system according to claim 18, It is characterized in that The first filling unit comprises: Import module, used to import network topology content and device information in the CIM file of the distribution network feeder into the memory; A second creation module, used to create a device object according to the device type in the device information of the CIM file; The generation module is used to read the network topology content of the CIM file in turn in a traversal manner, add the structured fields in the network topology content of the CIM file to the corresponding device objects, and generate a structured CIM model.

22. The system according to claim 18, It is characterized in that The first filling unit further includes: A mapping module, used for mapping each device in the CIM model with a device in the device fusion model based on a preset device fusion model mapping table; The filling module is used to fill the network topology content and structured fields in the device information corresponding to each device in the CIM model into the devices in the device fusion model corresponding to each device in the CIM model.

23. The system according to claim 18, It is characterized in that The second filling unit comprises: A calling module, used for calling an external system mapping file corresponding to the device information of each device in the device fusion model according to the device information of each device in the device fusion model; The extraction module is used to call the subroutine for extracting external system data to extract structured query language SQL text information according to the data in the external system mapping file, access the external system database, and extract the external system data corresponding to the device information of each device in the device fusion model.

24. The system according to claim 23, It is characterized in that The extraction module comprises: A loading submodule is used to load the device ID of each device in the device fusion model, the device type of each device in the device fusion model, data extraction related information, external system database information and data set template; the data extraction related information at least includes: data extraction SQL text information; The first judgment submodule is used to judge whether the data of the external system database can be extracted based on the device ID of each device in the device fusion model, the device type of each device in the device fusion model and the external system database information. If yes, the data is extracted by using the data extraction SQL text information to obtain a data extraction result set; if not, the call of the subroutine for extracting external system data is terminated; The second judgment submodule is used to judge whether the data extraction result set is empty. If the data extraction result set is not empty, the data extraction result set is transmitted to the external system data subroutine and filled into the device fusion model; otherwise, the call of the external system data extraction subroutine is terminated.

25. The system according to claim 24, It is characterized in that The first judgment submodule is specifically used to: According to the device ID and device type of each device in the device fusion model, determine whether the external system database authorizes the device fusion model to access the external system database. If the external system database authorizes the device fusion model to access the external system database, determine whether the external system database information is complete; otherwise, terminate the call of the subroutine for extracting external system data. Determine whether the external system database information is complete. If the external system database information is complete, data from the external system database can be extracted, and the data extraction SQL text information is called to access the external system database. After successfully connecting to the external system database, data extraction is performed, and the extracted data is stored in the data set template to obtain a data extraction result set; otherwise, the call to the subroutine for extracting external system data is terminated.

26. The system according to claim 17, It is characterized in that Also includes: A visualization unit is used to visualize the data in the device fusion model based on the network topology content in the CIM file.

27. The system according to claim 26, It is characterized in that The visualization unit is specifically used for: The network topology content in the CIM file is bound to the device fusion model, so that when the primitive attributes in the network topology are opened, the attribute information in the device fusion model corresponding to the primitive attributes is visually displayed.

28. An electronic device, It is characterized in that include: at least one processor and memory; The memory and the processor are connected via a bus; The memory is used to store one or more programs; When the one or more programs are executed by the at least one processor, the multi-source data fusion method based on the feeder-level CIM file as described in any one of claims 1 to 16 is implemented.

29. A readable storage medium, It is characterized in that An execution program is stored thereon, and when the execution program is executed, the multi-source data fusion method based on the feeder-level CIM file as described in any one of claims 1 to 16 is implemented.