Marketing and distribution through distribution network one-picture generation method, device and equipment and storage medium

Abstract

The invention relates to the technical field of power distribution network mapping, discloses a marketing and distribution connection distribution network one-graph generation method, device and equipment and a storage medium, and is used for realizing automatic mapping of the marketing and distribution connection distribution network one-graph by integrating power distribution network model data and user side equipment data. The marketing and distribution through distribution network graph generation method comprises the following steps: obtaining distribution network model data and user side equipment data; converting the user side equipment data into user model data according to a preset standard format; splicing the user model data and the power distribution network model data according to each preset graphic type to obtain a model data packet corresponding to each graphic type; and generating a marketing and distribution through distribution network graph according to a preset layout rule and each model data packet.

Description

Technical Field

[0001] The present application relates to the technical field of distribution network mapping, and in particular to a method, device, equipment and storage medium for generating a single map of a distribution network. Background Art

[0002] With the expansion and development of the power system, the large-scale access of high-proportion distributed energy and diversified loads has prompted the distribution network to gradually transform from passive to active, from unidirectional flow to multi-directional flow, and from AC system to a complex system with flexible AC and DC interconnection, which has put higher requirements on the operation and management of the distribution network.

[0003] Distribution network graphics are the basis of distribution network operation and management. Distribution network equipment is huge, the wiring method is complex, and the distribution network changes frequently. The distribution network graphics operation and maintenance workload is heavy. Traditionally, distribution network graphics rely on manual drawing, which is not only inefficient, time-consuming and labor-intensive, but also often cannot be modified in time with the transformation of distribution lines. The distribution network graphics are inconsistent with the actual status, which brings operational risks to distribution network scheduling.

[0004] The automatic mapping technology for distribution networks focuses on the automatic generation of higher voltage level graphics such as distribution network single-line diagrams and ring network diagrams. There are fewer automatic mapping solutions for medium and low voltage substations. In addition, distribution models and new energy equipment are usually managed through different systems. The models between systems are isolated, the graphics standards are not unified, and the information is scattered, messy and incomplete, which makes the transparent management of medium and low voltage substations very difficult. Various new energy equipment such as photovoltaic storage and charging cannot be accurately perceived in the distribution network, and cannot meet the automatic mapping requirements on the medium and low voltage side. Summary of the Invention

[0005] The present application provides a method, device, equipment and storage medium for generating a map of the distribution network, which is used in the case where the models of the various systems in the medium and low voltage substations are isolated, the graphic standards are not unified, and the new energy equipment cannot be accurately perceived.

[0006] A first aspect of the present application provides a method for generating a diagram of a distribution network through operation and distribution, comprising: obtaining distribution network model data and user-side device data;

[0007] Convert user-side device data into user model data according to a preset standard format;

[0008] According to the preset graphic types, the user model data and the distribution network model data are spliced to obtain the model data package corresponding to each graphic type;

[0009] Generate a diagram of the distribution network according to the preset layout rules and each model data package.

[0010] A second aspect of the present application provides a device for generating a map of a distribution network for operation and distribution, comprising: an acquisition module for acquiring distribution network model data and user-side device data;

[0011] A conversion module, used to convert user-side device data into user model data according to a preset standard format;

[0012] A splicing module is used to splice user model data and distribution network model data according to preset graphic types to obtain model data packets corresponding to each graphic type;

[0013] The generation module is used to generate a diagram of the distribution network according to the preset layout rules and various model data packages.

[0014] The third aspect of the present application provides a device for generating a one-picture diagram of a distribution network for operation and distribution, comprising: a memory and at least one processor, wherein the memory stores instructions; at least one processor calls the instructions in the memory to enable the device for generating a one-picture diagram of a distribution network for operation and distribution to execute the above-mentioned method for generating a one-picture diagram of a distribution network for operation and distribution.

[0015] The fourth aspect of the present application provides a computer-readable storage medium, which stores instructions. When the computer-readable storage medium is run on a computer, it enables the computer to execute the above-mentioned method for generating a map of the distribution network.

[0016] In the technical solution provided by this application, data integration between user-side equipment and distribution network equipment is achieved, which solves the problem that traditional mapping solutions cannot accurately perceive various new energy devices, and provides a rich source of equipment data for the generation of subsequent topology maps; the user-side equipment data is converted into user model data through a preset standard format, which realizes the standardized processing of user-side equipment and provides a basis for subsequent model splicing. According to each graphic type, the corresponding model file is selected for splicing to obtain the model data package corresponding to each graphic type, and based on the corresponding layout rules, a distribution network map containing user-side and grid-side information can be obtained, and multi-level panoramic information is displayed on the map, realizing the transformation from "manual drawing modeling" to "automatic generation of drawing models", greatly improving the drawing efficiency, solving the problem of easy errors in manual drawing, improving the accuracy of drawing, realizing source-end governance, and ensuring model consistency. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 This is a schematic diagram of an embodiment of a method for generating a diagram of a distribution network in this application;

[0018] Figure 2 This is a schematic diagram of another embodiment of the method for generating a diagram of a distribution network in this application;

[0019] Figure 3This is a schematic diagram of an embodiment of a device for generating a diagram of a distribution network in this application;

[0020] Figure 4 This is a schematic diagram of another embodiment of the device for generating a diagram of a distribution network in this application;

[0021] Figure 5 This is a schematic diagram of an embodiment of a device for generating a diagram of a distribution network in this application. DETAILED DESCRIPTION

[0022] The present application provides a method, apparatus, equipment and storage medium for generating a map of a distribution network for operation and distribution, which is used to automatically generate a map of a distribution network for operation and distribution by integrating distribution network model data and user-side equipment data.

[0023] The terms "first," "second," "third," "fourth," and the like (if any) in the specification and claims of this application and in the accompanying drawings are used to distinguish similar objects and are not necessarily used to describe a particular order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate so that the embodiments described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "including" or "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product, or apparatus comprising a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0024] It is understandable that the execution subject of this application can be a device for generating a single diagram of a distribution network, a terminal, a system or a server, and the specific implementation is not limited here. This embodiment is described by taking a server as the execution subject as an example.

[0025] Both the distribution network model data and the user-side device data can be used to describe the device attributes of each device and the topological connection relationship between the devices. Since the two are usually managed by different systems, the data formats and corresponding field description forms stored in the two may be different. For example, each device in the distribution network model data is usually stored in a standard format file, while the user-side device data may be stored in the form of an equipment ledger table based on its collected data source. Furthermore, the user-side device data is based on different data sources, and its storage format and field description form may also be different. The distribution network model data may also differ depending on whether its system is standardized. Therefore, there are many obstacles to generating a distribution network diagram using distribution network model data and user-side device data. To solve the above problems, the specific process of this application is described below. Please refer to Figure 1In this application, an embodiment of a method for generating a diagram of a distribution network includes:

[0026] 101. Obtain distribution network model data and user-side device data.

[0027] In this embodiment, the distribution network model data is used to indicate the model corresponding to the traditional distribution network equipment, which can represent the data of various devices between the distribution network and the user access point, such as switches, transformers, etc. The distribution network model data includes but is not limited to feeder models, substation models (or transformer models), etc., which are usually stored in the model library in accordance with the Common Information Model (CIM) standard of IEC61970. Among them, a feeder or a substation corresponds to a feeder model file, and the corresponding model file can be directly exported for drawing.

[0028] The feeder model is used to indicate the model describing the equipment and their connection relationships on the 10kV power line; the substation model is used to indicate the model describing the connection relationships between the 380V substation transformer and the user access point and the equipment.

[0029] In this embodiment, the user-side device data is used to indicate the data of various devices between the user access point and the user, such as marketing data associated with various new energy elements such as user-side low-voltage circuit breakers, wind power, photovoltaics, user-side energy storage, electric vehicles, charging piles, virtual power plants, etc.

[0030] It is understandable that new energy elements are usually managed differently from traditional distribution network equipment (such as the above-mentioned feeder model and substation model), that is, there is no data integration between marketing data and distribution network data. Therefore, conventional traditional distribution network equipment mapping solutions cannot cover user-side equipment, that is, based on the traditional distribution network model data, the diagram-to-model conversion is performed, and the resulting distribution network diagram will not display various new energy elements. However, new elements are developing in leaps and bounds, catalyzing continuous changes in the distribution network. A marketing-connected distribution diagram covering user-side equipment and distribution network equipment has broad prospects. However, due to the isolated models between systems, inconsistent graphic standards, and scattered, messy and incomplete information, the mapping efficiency of the marketing-connected distribution diagram is low, and there are many technical obstacles. This embodiment collects data from user-side devices to subsequently establish data links with power grid resource business middle platforms, enterprise-level measurement centers, etc., integrates and aggregates multi-dimensional data, applies IoT perception and image model splicing, and automatically generates maps. The distribution network map of "supply area - 10kV feeder - substation - access point - meter box - user" is fully connected, and can be accessed layer by layer, and flexibly displayed layer by layer, showing multi-level panoramic information on the map. The feeder and substation maps cover all elements of photovoltaic storage and charging, providing a data foundation.

[0031] Optionally, data verification can be performed when importing distribution network model data and user-side equipment data to ensure the reliability of the data basis for generating a single diagram of the distribution network, so as to improve subsequent processing efficiency.

[0032] In this embodiment, the device attributes are used to describe various configuration information of the device, including but not limited to the device name, device ID, device type, device type number, and user information. The topological connection relationship includes at least access point information.

[0033] Exemplarily, it is verified whether each model file of the distribution network model data conforms to the standard format, and / or whether the device attributes of each model file are correct and complete, and / or whether the topological connection relationship of each model file meets the connectivity requirements.

[0034] 102. Convert the user-side device data into user model data according to a preset standard format.

[0035] In this embodiment, the standard format is used to indicate a file format that complies with the CIM standard. For example, a fixed standard format such as Extensible Markup Language (XML) may be used to store or manage its version.

[0036] In this embodiment, the user model data is converted into a model file in a standard unified format based on the user-side device data. The user device model that conforms to the standard format includes device attributes and topological connection relationships, which are used to describe the model consisting of the user access point to the user-side low-voltage circuit breaker, distributed wind power, distributed photovoltaic, user-side energy storage, charging piles, regular users and their connection relationships.

[0037] The above-mentioned topological connection relationship is used to indicate the connection relationship of each user equipment. The topological connection relationship includes but is not limited to: access point identifier psrId and access point type psrType, wherein the access point identifier psrId is used to indicate the unique identifier of the access point; access point type psrType: transformer or user access point, etc.

[0038] The above-mentioned device attributes are used to indicate various attributes of each device. The device attributes include but are not limited to the user identification number userId used to indicate the unique identification of the user; the user type userType is used to define the user category, such as distributed wind power, distributed photovoltaic, user-side energy storage, charging pile, regular user, etc.; the user name userName is used to indicate the user name on the ledger; the user level grade is used to indicate the device hierarchy relationship, and the number of device levels can be set according to actual conditions. For example, the root node is the substation transformer, and the child node is the smart circuit breaker associated with the transformer. The light, storage, charging, load and other equipment controlled by the smart circuit breaker are the children of the smart circuit breaker, that is, for the substation distribution fusion terminal, it is a first-level device, the smart circuit breaker is a second-level device, and the light, storage, charging, load, etc. are third-level devices. It should be noted that the above-mentioned device hierarchy is only an example. When it is an ordinary circuit breaker (that is, when the intelligent transformation is not performed, the circuit breaker is not collected), the above-mentioned light, storage, charging, and load are second-level devices.

[0039] 103. According to the preset graphic types, the user model data and the distribution network model data are spliced to obtain model data packets corresponding to the graphic types.

[0040] Specifically, based on the selected graphic type, all model files of the corresponding area are called from the model library and combined to obtain the model data package corresponding to each graphic type required for the drawing. The model data package corresponding to each graphic type in this embodiment covers all model files required for the graphic type.

[0041] In this embodiment, different graphic types have slightly different focuses in their display, and the one-picture diagram of the marketing and distribution through-network includes various preset graphic types. Users can select the corresponding graphic type for display on the one-picture diagram of the marketing and distribution through-network according to actual needs, and quickly access topology diagrams at different levels by switching between different graphic types.

[0042] The graph types of this embodiment include, but are not limited to, regional system diagrams, regional communication diagrams, feeder single-line topology diagrams, substation topology diagrams, and energy user diagrams. Regional system diagrams and regional communication diagrams can be used to define the control range of all substations and feeders for management purposes, or they can be used to define the range of two or more fixed substations and their feeders.

[0043] The equipment in the above-mentioned regional system diagram includes substations, switchgear, ring main units, busbars, circuit breakers, medium-voltage distribution lines (overhead lines or cables), etc.; the equipment in the above-mentioned regional communication diagram includes substations, switchgear, ring main units, busbars, circuit breakers, medium-voltage distribution lines (overhead lines or cables); the difference between the regional communication diagram and the regional system diagram in this embodiment is that it does not include all incoming and outgoing lines of the substation, only retains the lines with communication relationships between stations, and does not include single radial branches or branch lines.

[0044] The equipment in the above-mentioned single-line feeder topology diagram includes substations, switchgear, ring main units, busbars, circuit breakers, medium-voltage distribution lines (cables), distribution rooms, box-type substations, distribution transformers, and the aggregation of their internal resources. The single-line feeder topology diagram of this embodiment can realize the aggregation of energy resources with the traditional single-line diagram. The photovoltaic power generation of the substation area in the feeder diagram is obtained by aggregating all photovoltaic users under the substation area.

[0045] The equipment in the above-mentioned substation topology diagram includes the 10kV lines, the upper 10kV switches of the substation, distribution transformers, low-voltage circuit breakers, low-voltage distribution lines, distributed power sources, energy storage, charging piles, conventional loads, etc., among which conventional loads need to be aggregated according to the low-voltage bus. The substation drag ticket in this embodiment does not expand to display the load of each household.

[0046] The equipment in the above energy user diagram includes distribution transformers, low-voltage circuit breakers, low-voltage distribution lines, distributed power sources, energy storage, charging piles, etc.

[0047] Exemplarily, if the graphic type is a regional system diagram, the model files of the corresponding regional substation and all related feeders are called from the model library for combination.

[0048] Optionally, when generating model data packages of each graphic type, in order to improve the quality and reliability of the subsequent generation of a distribution network diagram, the model data packages of each graphic type can be verified again to ensure the accuracy and completeness of the file format, device properties, and topological connection relationships in the model data packages.

[0049] 104. Generate a diagram of the distribution network according to the preset layout rules and the model data packages corresponding to each graphic type.

[0050] In this embodiment, a map of the marketing and distribution network is used to indicate the distribution network diagram that connects the marketing data and the distribution network data. That is, the distribution network equipment and user-side equipment in the target area can be displayed on the map, and various electrical parameters (such as current, voltage), flow direction, equipment and line on-off status and other information can be further presented to facilitate users to achieve full and transparent management of the medium and low voltage sides.

[0051] In this embodiment, one graphic type corresponds to one layout rule, so as to facilitate intuitive and comprehensive display of information of various graphic types. This embodiment solves the problem that traditional graphics are single in type and cannot adapt to the needs of new energy equipment aggregation display (such as regional energy distribution and substation load aggregation).

[0052] For example, the regional system diagram should adopt a horizontal and vertical orthogonal layout; the substation should be expanded to display the medium-voltage distribution network busbar and all outgoing circuit breakers. When the outgoing line is a connecting line, the equipment on each side of the connection is generated; when the outgoing line is a single radial line, only the outgoing circuit breakers within the station are generated; and the layout between station buildings is arranged according to the principles of proximity and non-intersection; the station diagram should be displayed in the ring network cabinet and switchgear, and the horizontal layout of the busbar within the station is that the ring-in and ring-out circuit breakers are placed on one side of the busbar, and the feeder circuit breakers with connections are placed on the other side of the busbar.

[0053] It is understandable that this embodiment combines model data packages corresponding to various graphic types to meet different user needs, achieving flexible display of hierarchical and graded penetration. Users can click different locations to switch between different graphic types. For example:

[0054] By clicking on the feeder on the regional system diagram or regional communication diagram, you can jump to the corresponding feeder single-line topology diagram. By clicking on the thumbnail displayed ring main unit or switchgear on the regional system diagram or regional communication diagram, you can jump to the display of the corresponding complete station diagram. By clicking on the transformer or substation block diagram on the feeder single-line topology diagram, you can jump to the corresponding substation diagram. By clicking on the ring main unit or switchgear on the feeder single-line topology diagram, you can jump to the display of the corresponding complete station diagram. By clicking on the energy aggregation element on the feeder single-line topology diagram, you can jump to a certain energy user graphic of the corresponding substation, and you can switch to display other user diagrams of the corresponding type in the substation. By clicking on the energy user element on the substation diagram, you can jump to the corresponding energy user diagram.

[0055] The switching and adjustment of various graphic types on the above-mentioned distribution network diagram is only a possible example and is not limited to any specific example.

[0056] In this embodiment, distribution network model data and user-side device data are obtained to generate a topology map, which realizes the connection between the user-side device and the original distribution network device, solves the problem that traditional mapping solutions cannot accurately perceive various new energy devices, and provides a rich source of device data for the subsequent generation of topology maps; the user-side device data is converted into user model data through a preset standard format, which realizes the standardized processing of user-side devices, provides a basis for subsequent model splicing, and selects the corresponding model for splicing through the selected graphic type, so as to obtain a complete topology map containing user-side and grid-side information, and can display multi-level panoramic information on one map; after completing the model splicing of the graphic type, automatic mapping is performed according to the preset layout rules, which realizes the transformation from "manual drawing modeling" to "automatic generation of drawing models", greatly improves the mapping efficiency, solves the problem of easy errors in manual drawing, improves the accuracy of mapping, realizes source-end governance, and ensures model consistency.

[0057] See also Figure 2Another embodiment of the method for generating a diagram of a distribution network in the present application includes:

[0058] 201. Obtain distribution network model data and user-side device data.

[0059] In this embodiment, the distribution network model data is managed by a unified model library and can be directly exported from the model library, while the user-side device data can be obtained through marketing system export, manual entry and automatic reporting.

[0060] Optionally, an offline original ledger table, or a marketing user information table, is exported from the marketing system, and user-side device data is determined based on the offline original ledger table.

[0061] It is understandable that since marketing and scheduling operations belong to two separate departments, their data are usually managed separately. This embodiment exchanges information by exporting offline files from the marketing system. If the data of the two departments can be connected, this solution can be used to obtain complete and accurate user information for distribution network construction.

[0062] In this embodiment, the offline original ledger table includes but is not limited to the following data based on the content of the data center management data: area unique identifier, area name, user unique identifier, user type, user name, installed capacity, etc.

[0063] Optionally, a manually input ledger fund collection table is received, and user-side device data is determined based on the ledger fund collection table.

[0064] It is understandable that by collecting funds through manual ledgers, we can collect ledgers of various users under the substation area. As long as the construction is reported, the model can be maintained independently and in a timely manner. For the dispatching department, large or extensive new energy users will affect the dispatching. From the perspective of independent maintenance, this method is convenient and does not require connecting to external departments or processes.

[0065] In this embodiment, the standard format for collecting funds may include but is not limited to: a unique identification of the station area, a name of the station area, a unique identification of the user, a user type, a user name, an installed capacity, and the like.

[0066] Optionally, user-side device data can be collected through a distribution convergence terminal. The distribution convergence terminal reports relevant information about each managed new energy device. User-side device data can be obtained by formatting the data in the target field.

[0067] The above-mentioned distribution fusion terminal is a secondary terminal installed on the low-voltage side of the distribution transformer in the substation. It can realize the function of the edge management terminal through the smart control unit (Smart Control Unit, SCU) to collect the operation and ledger information of independent new energy equipment, and use communication technology to realize information aggregation of distributed new energy, energy storage and electric vehicles. On the basis of this, the construction information of energy users can be sent comprehensively based on the topological connection relationship between the substation and the energy. After the distribution fusion terminal is installed on the equipment side, it can automatically identify user information. The distribution master station can receive user change or connection data in a timely manner, and automatically trigger model updates and ledger updates.

[0068] In a feasible implementation, when the user-side device data comes from at least two data sources, that is, from two or three sources including the distribution fusion terminal, the ledger collection table, and the offline original ledger table, there is a technical problem that data conflicts are prone to occur in the fusion of multi-source heterogeneous data. This embodiment provides a solution for a dynamic priority data fusion engine to solve the problem that the field format, device naming rules, and timestamp inconsistencies of data from different sources lead to device duplication or attribute contradictions when the model is spliced.

[0069] Optionally, the original data of each data source is converted into a preset standard format through a field mapping table to obtain a standard format file corresponding to each data source; the standard format file corresponding to each data source is processed according to a preset conflict resolution algorithm to obtain user model data.

[0070] In this embodiment, the field alias mapping relationship of different data sources is defined through a field mapping table, so that the data of different data sources are mapped to standard and identical field names, which is convenient for subsequent conflict identification and resolution. It can also further generate standardized files to facilitate the subsequent generation of a map of the distribution network.

[0071] For example, the standard field "user number" corresponds to the "user userId" in the offline original ledger table and the "terminal ID" monitored in real time by the distribution fusion terminal; the standard field "user name" corresponds to the "user name" in the offline original ledger table and the "userName" monitored in real time.

[0072] For example, standard conversion rules can also be formulated. For example, for user numbers, the unified conversion rule is to add a regional prefix (such as ZJ-01-); for user names, the unified conversion rule is to truncate the last 6 digits of the string.

[0073] In this embodiment, the conflict resolution algorithm is used to indicate an algorithm for resolving data conflicts between multi-source data. It can combine various types of data standardization output, comparison and selection conditions to select the user-side equipment with the highest confidence, that is, the most reliable, to generate a map of the distribution network. There is no specific restriction.

[0074] Exemplarily, each standard format file is aggregated according to the device's unique identification code (i.e., device ID) to obtain each device set; the confidence corresponding to each device in each device set is determined based on the weight corresponding to each data source and a preset time decay function; and user model data is generated based on the standard format file corresponding to the device with the maximum confidence value in each device set.

[0075] It can be understood that the standard format file corresponds to the device one-to-one, that is, each standard format file corresponds to a device. The same device in different data sources can be quickly summarized by aggregating through the device's unique identification code, and the confidence is calculated for each device set. Each device in each device set comes from a different data source. The standard format file corresponding to the device with the highest credibility can be selected as the final user model data, which improves the processing efficiency of the conflict resolution algorithm.

[0076] This embodiment does not impose specific restrictions on the number of devices in each device set and the data source from which each device originates. Each device set may include only one device, that is, the device ID is only stored in a certain data source. Each device set may include only two or three devices, that is, the device ID is stored in two or three data sources.

[0077] It is understandable that a confidence threshold can be further set to determine whether there is an anomaly. When the confidence level determines an anomaly, the governance data is manually modified based on the actual data. For high-reliability scenarios (such as user level, access point psrId, etc.), a confidence level of ≥85% is required, while for low-risk scenarios (such as user name), an acceptable confidence level of ≥60% is acceptable.

[0078] Optionally, the confidence level corresponding to each device in each device set is determined based on the weight corresponding to each data source and a preset time decay function, including: determining the time decay value of each data source based on the data timestamps of each standard format file in each device set in different data sources; determining the confidence level corresponding to each device based on the weight corresponding to each data source and the corresponding time decay value.

[0079] In this embodiment, the time decay function is used to quantify the degree of reliability decay of data over time. It can be calculated using an exponential decay model or other time decay models, without limitation. For example, the expression of the exponential decay model can be:

[0080] decay(t)=e-λΔt

[0081] Where λ is the attenuation coefficient, which is used to control the attenuation speed; Δt is the difference between the current time and the data timestamp.

[0082] The larger the value of the above λ, the faster the weight of historical data decays; the smaller the λ value, the slower the weight of historical data decays. For example, for data with high real-time requirements such as user level, λ can be set to 0.2 (1 / hour), and for data with low real-time requirements such as user name, λ can be set to 0.05 (1 / day).

[0083] For ease of understanding, let's use an example. Suppose a user's data timestamp is 2023-09-2010:00:00, and the current time is 2023-09-2012:00:00. The setting λ is 0.1 / hour, and △t is 2 hours. Based on the above decay = e-0.1*2 = 0.8187, the reliability of the current timeliness of the data is approximately 81.87%.

[0084] In this embodiment, the confidence level is used to indicate the reliability of the device in the data source. By selecting the device with the highest confidence level as the device in the user-side device data, the reliability of subsequent mapping can be improved. The weight corresponding to each data source is the weight assigned by the user based on the reliability of different data sources. The reliability of the device reported by the SCU real-time monitoring is higher, and the data of the manually input ledger collection table has a certain probability of error due to manual participation, and there is a certain delay in the maintenance of the offline original ledger table. Therefore, the weights can be set from large to small as follows: SCU real-time monitoring data, ledger collection table, offline original ledger table, for example, set to 0.5, 0.3, and 0.2 respectively.

[0085] For example, the confidence calculation formula can be expressed as:

[0086]

[0087] Among them, ω priority,i Used to indicate the priority weight of the i-th data source; decay i Used to indicate the time attenuation value of the i-th data source.

[0088] To facilitate understanding, an example is provided. Taking user-level fields as an example, assume three data sources:

[0089] SCU real-time monitoring: priority =0.5, decay=0.9;

[0090] Manual ledger collection table: ω priority =0.3, decay=0.6;

[0091] Offline original ledger: ω priority =0.2, decay=1;

[0092] After calculating the confidence level using the confidence formula, the confidence level for this user-level field is 83%. Each time data is updated, a final value with a confidence level tag is generated. Only the final value with the highest confidence level is retained for mapping or record management. A confidence threshold can be set, and when confidence levels indicate anomalies, the governance data can be manually modified based on the actual data.

[0093] It is understood that this embodiment groups multi-source data using unique device identifiers. If only one device exists within a group, that device is directly output as the target device, improving the efficiency of the conflict resolution algorithm. By dynamically integrating priority weights and time decay factors, and identifying conflicts among multiple data sources using confidence levels, the multivariate model is incrementally processed and resolved.

[0094] Optionally, before converting the original data of each data source into a preset standard format through a field mapping table to obtain the standard format file corresponding to each data source, it also includes: data cleaning of the input offline original ledger table, ledger collection table and SCU reporting data.

[0095] 202. Convert the user-side device data into user model data according to a preset standard format.

[0096] Specifically, the user-side device data is parsed to obtain the device attributes and topological connection relationships of each device, wherein the device attributes at least include the user information and the topological connection relationship at least includes the access point information; the device attributes and topological connection relationship of each device are converted into user model data based on a preset standard format.

[0097] Optionally, the above-mentioned conversion of the device attributes and topological connection relationships of each device into user model data based on a preset standard format includes: converting the device attributes and topological connection relationships of each device into target files corresponding to each device according to a preset standard format; and storing the target files corresponding to each device into the device database to obtain user model data.

[0098] For example, the data reported by SCU is usually in json format, which is converted into XML standard format through parsing, and the root node is mapped to the distribution fusion terminal; the child node is mapped to the intelligent circuit breaker, and the end node is mapped to the distributed power supply or energy storage device.

[0099] 203. Read target model files corresponding to respective graphic types from user model data and distribution network model data.

[0100] In this embodiment, each target model file includes at least a reference file that meets the standard format. The target area may contain model files that meet the standard format, or model files that do not meet the standard format.

[0101] In this embodiment, when the graphic type is a regional system diagram or a regional communication diagram, the substation model file corresponding to the target substation in the distribution network model data and all feeder model files are determined as target model files; when the graphic type is a feeder single-line topology diagram, the feeder model file and substation model file corresponding to the target substation in the distribution network model data, and all user model files corresponding to the target substation in the user model data are determined as target model files; when the graphic type is a substation topology diagram, the substation model file corresponding to the target substation in the distribution network model data and all user model files corresponding to the target substation in the user model data are determined as target model files; when the graphic type is an energy user diagram, all user model files corresponding to the target substation in the user model data are determined as target model files.

[0102] Optionally, each model file is verified to improve the accuracy of the drawing. It is understandable that various errors may occur in the model conversion of the user-side equipment. For example, the ledger collection table entered through manual ledger collection has the risk of data entry errors due to the presence of manual participation. This embodiment can pass verification in model conversion, model splicing, and the generation of a single map based on the distribution network of the distribution network, thereby solving the problem of independent management of feeder, substation, and user models, and the problem of node isolation and attribute conflicts during splicing.

[0103] The above-mentioned verification of each model file includes: verifying each model file to verify whether each model file conforms to the standard format and obtains a format verification result; and / or, verifying whether the device attributes of each model file meet the integrity requirements and obtains an integrity verification result; and / or, verifying whether the topological connection relationship of each model file meets the connectivity requirements and obtains a connectivity verification result.

[0104] In this embodiment, the error classification of the model verification item includes but is not limited to model format error, parsing model error and topology error.

[0105] Exemplarily, each model file is checked to verify whether it conforms to the standard format, and the format verification results include: checking whether there are errors in the model format, or the CIM object cannot be parsed; among them, the error in the model format is a loading file error, which may be a CIM / XML format error; the inability to parse the CIM object is because the CIM object has not been modeled in the software. In this case, the model needs to be improved in the software according to the application requirements.

[0106] Exemplarily, it is verified whether the device attributes of each model file meet the integrity requirements, and the integrity verification results obtained include: whether the endpoint-associated device cannot be retrieved, whether the B device associated with device A cannot be retrieved, and whether the number of endpoints of the transformer is correct, etc.; for example, a search has been performed based on the endpoint ID, which is a type of device attribute. If the device corresponding to the endpoint cannot be retrieved in the endpoint, the integrity verification fails; for another example, the aggregation relationship between objects is judged. If the B device associated with device A cannot be retrieved, that is, device A Id = XX cannot retrieve B associated with XX, then there is an error in the aggregation relationship of the device and the integrity verification fails; the power grid transformer generally has two or three windings. If it is not a two-group or three-winding transformer, the integrity verification fails.

[0107] Exemplarily, verify whether the topological connection relationship of each model file meets the connectivity requirements, and obtain connectivity verification results including: whether the device node corresponding to the endpoint is empty; whether the endpoint has no corresponding node; whether the device I / J side node is empty; whether the device I / J side node is isolated; the node is empty; the node is isolated, etc.

[0108] If the endpoint node ID is empty, the connectivity check fails and the endpoint cannot be associated with the actual physical device, resulting in a missing power supply relationship, which may cause electricity metering disputes or reduce power supply reliability. Specifically, a regular expression check is added at the data access layer;

[0109] Among them, if the endpoint cannot retrieve the corresponding node, the connectivity check fails; if the user-side device is not correctly mounted in the power grid topology, the actual manifestation is that the user's electricity meter has no voltage signal, which may easily lead to user complaints; object persistence detection can be used to traverse all adjacent nodes of all endpoints: establish an endpoint-node reverse index table, and implement fuzzy matching through Elasticsearch, such as the Unicode standardization of the fault-tolerant device names "Transformer A" and "Transformer A".

[0110] If a device node is empty, meaning no associated nodes have been retrieved for the device, the node is assigned a value through the device's breakpoint retrieval. Specifically, if a power grid device loses its control point in the topology, the dispatch system cannot issue operational instructions (such as remotely disconnecting a circuit breaker), posing a security risk. This can be addressed by checking the integrity of the ORM mapping and database foreign key constraints. During the topology loading phase, a virtual placeholder node is injected to record missing device logs.

[0111] Among them, if there is a node that is not connected to the power grid, that is, an isolated node, then the device node is not connected to the power grid, and the connectivity check fails; specifically, the device is not connected to the distribution network trunk line, forming an electrical island, which may cause the distributed power supply to be out of control or the load to lose power. By locating the nearest connectable node between the isolated subgraph and the backbone network (such as based on the Dijkstra algorithm), candidate connection paths can be dynamically generated, and the optimal access point can be automatically recommended in combination with the line capacity margin to reduce manual intervention.

[0112] 204. Modify the device node names and connection point names of each non-benchmark file using any benchmark file to obtain a model data package corresponding to each graphic type.

[0113] Specifically, the device node names in the benchmark file are assigned to the corresponding nodes in the non-benchmark file; the connection points of the corresponding device terminals in the non-benchmark file are renamed according to the connection point names in the benchmark file; the device models in the non-benchmark file that are repeated in the benchmark file are deleted to obtain the model data packages corresponding to each graphic type.

[0114] For example, any CIM file is selected as the benchmark file, and the substation model file is the non-benchmark file; the nodes of the equipment in the benchmark file are used as the device nodes in the non-benchmark file; the device node names in the benchmark file are used to assign the node names of the non-benchmark file; the names of the connection points of the device terminals in the non-benchmark file are revised, and through model standardization in CIM, the equipment automatically associates the terminals to obtain new node names; the newly added attributes of the non-benchmark file are assigned (merged attributes); and the device model in the non-benchmark file is deleted.

[0115] In one feasible implementation, lower-level associated devices are selected for splicing based on access point ID and access point type, and a topology adjacency matrix is constructed in real time. A depth-first search (DFS) is used to detect potential loops. If a loop is detected, an alarm is triggered and the system backtracks to the nearest compliant node for re-splicing. This embodiment uses two unique indexes to splice each graph type, and uses a graph-theory-driven loop prediction algorithm to address the problem of automatic splicing potentially generating loops that violate the radial structure of the distribution network, such as closed loops formed by incorrectly connected circuit breakers, thereby improving the accuracy of the model data packets corresponding to each graph type.

[0116] It is understandable that new energy equipment such as photovoltaic users usually need to be connected to bidirectional power nodes. In order to solve the problem that traditional algorithms easily mistakenly mount them to ordinary user buses, resulting in splicing errors, this embodiment uses semantic analysis to identify dynamic matching rules for device types in the ledger. Specifically, if the device to be spliced is a new energy device, the access point type of its parent node is forced to be a bidirectional power interface.

[0117] 205. Generate a diagram of the distribution network according to the preset layout rules and the model data packages corresponding to each graphic type.

[0118] Step 205 can be performed with reference to step 104 and will not be described again here.

[0119] In this embodiment, data integration between user-side devices and distribution network devices is achieved, which solves the problem that traditional mapping solutions cannot accurately perceive various new energy devices, and provides a rich source of device data for the generation of subsequent topology maps; the user-side device data is converted into user model data through a preset standard format, which realizes the standardized processing of user-side devices and provides a basis for subsequent model splicing. According to each graphic type, the corresponding model file is selected for splicing to obtain the model data package corresponding to each graphic type, and based on the corresponding layout rules, a distribution network map containing user-side and grid-side information can be obtained, and multi-level panoramic information is displayed on the map, realizing the transformation from "manual drawing modeling" to "automatic generation of drawing models", greatly improving the drawing efficiency, solving the problem of easy errors in manual drawing, improving the accuracy of drawing, realizing source-end governance, and ensuring model consistency.

[0120] The above describes the method for generating a diagram of the distribution network in this application. The following describes the device for generating a diagram of the distribution network in this application. Figure 3 In this application, an embodiment of a device for generating a diagram of a distribution network includes:

[0121] Acquisition module 301, used to acquire distribution network model data and user-side device data;

[0122] The conversion module 302 is used to convert the user-side device data into user model data according to a preset standard format;

[0123] A splicing module 303 is used to splice user model data and distribution network model data according to preset graphic types to obtain model data packets corresponding to each graphic type;

[0124] The generation module 304 is used to generate a diagram of the distribution network according to the preset layout rules and each model data package.

[0125] In this embodiment, distribution network model data and user-side device data are obtained to generate a topology map, which realizes the connection between the user-side device and the original distribution network device, solves the problem that traditional mapping solutions cannot accurately perceive various new energy devices, and provides a rich source of device data for the subsequent generation of topology maps; the user-side device data is converted into user model data through a preset standard format, which realizes the standardized processing of user-side devices, provides a basis for subsequent model splicing, and selects the corresponding model for splicing through the selected graphic type, so as to obtain a complete topology map containing user-side and grid-side information, and can display multi-level panoramic information on one map; after completing the model splicing of the graphic type, automatic mapping is performed according to the preset layout rules, which realizes the transformation from "manual drawing modeling" to "automatic generation of drawing models", greatly improves the mapping efficiency, solves the problem of easy errors in manual drawing, improves the accuracy of mapping, realizes source-end governance, and ensures model consistency.

[0126] See also Figure 4 Another embodiment of the device for generating a diagram of a distribution network in the present application includes:

[0127] Acquisition module 301, used to acquire distribution network model data and user-side device data;

[0128] The conversion module 302 is used to convert the user-side device data into user model data according to a preset standard format;

[0129] A splicing module 303 is used to splice user model data and distribution network model data according to preset graphic types to obtain model data packets corresponding to each graphic type;

[0130] The generation module 304 is used to generate a diagram of the distribution network according to the preset layout rules and each model data package.

[0131] Optionally, the conversion module 302 includes:

[0132] The conversion unit 3021 is used to convert the original data of each data source into a preset standard format through the field mapping table to obtain a standard format file corresponding to each data source;

[0133] The conflict resolution unit 3022 is configured to process the standard format files corresponding to each data source according to a preset conflict resolution algorithm to obtain user model data.

[0134] Optionally, the conflict resolution unit 3022 includes:

[0135] Aggregation subunit 30221, for aggregating each standard format file according to the device unique identification code to obtain a set of devices, where the standard format files correspond to the devices one-to-one;

[0136] A confidence calculation subunit 30222 is configured to determine the confidence corresponding to each device in each device set based on the weight corresponding to each data source and a preset time decay function, wherein each device in each device set is derived from a different data source;

[0137] The generating subunit 30223 is used to generate user model data according to the standard format file corresponding to the device corresponding to the maximum confidence value in each device set.

[0138] Optionally, the confidence calculation subunit 30222 is specifically configured to determine the time decay value of each data source based on the data timestamps of each standard format file in each device set in different data sources;

[0139] The confidence level of each device is determined based on the weight and time decay value of each data source.

[0140] Optionally, the acquisition module 301 is specifically configured to: export an offline original ledger table from the marketing system, and determine user-side device data based on the offline original ledger table; and / or,

[0141] receiving a manually input ledger fund collection table and determining user-side device data based on the ledger fund collection table; and / or,

[0142] Collect user-side device data through the power distribution fusion terminal.

[0143] Optionally, the splicing module 303 includes:

[0144] The reading unit 3031 is configured to read target model files corresponding to each graphic type from the user model data and the distribution network model data, wherein each target model file at least includes a reference file that meets a standard format;

[0145] The correction unit 3032 is used to correct the device node names and connection point names of each non-reference file using any reference file to obtain a model data package corresponding to each graphic type.

[0146] Optionally, the reading unit 3031 is specifically configured to: when the graphic type is a regional system diagram or a regional communication diagram, determine the substation model file corresponding to the target substation in the distribution network model data and all feeder model files as the target model files;

[0147] When the graphic type is a feeder single-line topology diagram, the feeder model file and the substation model file corresponding to the target substation in the distribution network model data, and all user model files corresponding to the target substation in the user model data are determined as target model files;

[0148] When the graphic type is a substation diagram, the substation model file corresponding to the target substation in the distribution network model data and all user model files corresponding to the target substation in the user model data are determined as target model files;

[0149] When the graph type is an energy user graph, all user model files corresponding to the target substation in the user model data are determined as target model files.

[0150] Optionally, the device for generating a map of the distribution network further includes a verification module 305, which includes:

[0151] The first verification unit 3051 is used to verify whether each model file conforms to the standard format and obtain a format verification result;

[0152] The second verification unit 3052 is used to verify whether the device attributes of each model file meet the integrity requirements and obtain an integrity verification result.

[0153] The third verification unit 3053 is used to verify whether the topological connection relationship of each model file meets the connectivity requirement and obtain a connectivity verification result.

[0154] In this embodiment, distribution network model data and user-side device data are obtained to generate a topology map, which realizes the connection between the user-side device and the original distribution network device, solves the problem that traditional mapping solutions cannot accurately perceive various new energy devices, and provides a rich source of device data for the subsequent generation of topology maps; the user-side device data is converted into user model data through a preset standard format, which realizes the standardized processing of user-side devices, provides a basis for subsequent model splicing, and selects the corresponding model for splicing through the selected graphic type, so as to obtain a complete topology map containing user-side and grid-side information, and can display multi-level panoramic information on one map; after completing the model splicing of the graphic type, automatic mapping is performed according to the preset layout rules, which realizes the transformation from "manual drawing modeling" to "automatic generation of drawing models", greatly improves the mapping efficiency, solves the problem of easy errors in manual drawing, improves the accuracy of mapping, realizes source-end governance, and ensures model consistency.

[0155] above Figure 3 and Figure 4 The device for generating a map of the distribution network in this application is described in detail from the perspective of modular functional entities. The device for generating a map of the distribution network in this application is described in detail from the perspective of hardware processing.

[0156] See also Figure 5As shown, the device for generating a diagram of the distribution network includes a processor 500 and a memory 501. The memory 501 stores machine executable instructions that can be executed by the processor 500. The processor 500 executes the machine executable instructions to implement the self-test method of the above-mentioned inverter circuit.

[0157] Further, Figure 5 The device for generating a map of the distribution network shown also includes a bus 502 and a communication interface 503 , and the processor 500 , the communication interface 503 and the memory 501 are connected via the bus 502 .

[0158] Among them, the memory 501 may include a high-speed random access memory (RAM), and may also include a non-volatile memory (non-volatile memory), for example, at least one disk storage. The communication connection between the system network element and at least one other network element is realized through at least one communication interface 503 (which can be wired or wireless), and the Internet, wide area network, local area network, metropolitan area network, etc. can be used. The bus 502 can be an ISA bus, a PCI bus, or an EISA bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 5 Only one bidirectional arrow is used in the diagram, but this does not mean that there is only one bus or one type of bus.

[0159] The processor 500 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by hardware integrated logic circuits or software instructions in the processor 500. The processor 500 may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it may also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present disclosure. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in conjunction with the embodiments of the present disclosure may be directly implemented and executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium mature in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory 501 , and the processor 500 reads the information in the memory 501 and completes the method steps of the aforementioned embodiment in combination with its hardware.

[0160] The present application also provides a computer-readable storage medium, which may be a non-volatile computer-readable storage medium or a volatile computer-readable storage medium. The computer-readable storage medium stores instructions, which, when executed on a computer, cause the computer to execute the steps of a method for generating a map of a distribution network.

[0161] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0162] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0163] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the above embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the above embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for generating a diagram of a distribution network, characterized in that: The method for generating a map of the distribution network includes: Obtaining distribution network model data and user-side device data, wherein the distribution network model data is used to indicate data of each device between the distribution network and the user access point, and the user-side device data is used to indicate data of each device between the user access point and the user; Converting the user-side device data into user model data according to a preset standard format; splicing the user model data and the distribution network model data according to preset graphic types to obtain model data packets corresponding to the graphic types; A diagram of the distribution network is generated according to the preset layout rules and the model data packages.

2. The method for generating a single diagram of a distribution network according to claim 1, characterized in that: Obtain user-side device data, including: Exporting an offline original ledger table from the marketing system, and determining user-side device data based on the offline original ledger table; and / or, receiving a manually input ledger fund collection table, and determining user-side device data based on the ledger fund collection table; and / or, Collect user-side device data through the power distribution fusion terminal.

3. The method for generating a single diagram of a distribution network according to claim 1, characterized in that: When the user-side device data is derived from at least two data sources, converting the user-side device data into user model data according to a preset standard format includes: Convert the original data of each data source into a preset standard format through the field mapping table to obtain the standard format file corresponding to each data source; The standard format files corresponding to each of the data sources are processed according to a preset conflict resolution algorithm to obtain user model data.

4. The method for generating a single diagram of a distribution network according to claim 3, characterized in that: The processing of the standard format files corresponding to the data sources according to the preset conflict resolution algorithm to obtain the user model data includes: Aggregating the standard format files according to the unique identification code of the device to obtain a set of devices, wherein the standard format files correspond to the devices one by one; Determining the confidence level of each device in each device set based on a weight corresponding to each data source and a preset time decay function, wherein each device in each device set comes from a different data source; Generate user model data based on the standard format file corresponding to the device with the maximum confidence value in each device set.

5. The method for generating a single diagram of a distribution network according to claim 4, characterized in that: The determining of the confidence level corresponding to each device in each device set according to the weight corresponding to each data source and a preset time decay function includes: Determine the time decay value of each data source according to the data timestamps of each standard format file in each device set at different data sources; The confidence level of each device is determined based on the weight and time decay value of each data source.

6. The method for generating a single diagram of a distribution network according to claim 1, characterized in that: The step of splicing the user model data and the distribution network model data according to the preset graphic types to obtain the model data packets corresponding to the graphic types includes: Reading target model files corresponding to each graphic type from the user model data and the distribution network model data, wherein each target model file at least includes a reference file that meets the standard format; The device node names and connection point names of each non-benchmark file are modified through any benchmark file to obtain the model data package corresponding to each graphic type.

7. The method for generating a single diagram of a distribution network according to claim 6, characterized in that: The step of reading target model files corresponding to respective graphic types from the user model data and the distribution network model data includes: When the graphic type is a regional system diagram or a regional communication diagram, the substation model file corresponding to the target substation in the distribution network model data and all feeder model files are determined as target model files; When the graphic type is a feeder single-line topology diagram, the feeder model file and the substation model file corresponding to the target substation in the distribution network model data, and all user model files corresponding to the target substation in the user model data are determined as target model files; When the graphic type is a substation diagram, the substation model file corresponding to the target substation in the distribution network model data and all user model files corresponding to the target substation in the user model data are determined as target model files; When the graph type is an energy user graph, all user model files corresponding to the target substation in the user model data are determined as target model files.

8. The method for generating a single diagram of a distribution network according to claim 1, characterized in that: Also includes: Verify whether each model file conforms to the standard format and obtain a format verification result; and / or, Verify whether the device attributes of each model file meet the integrity requirements and obtain the integrity verification result; and / or, Verify whether the topological connection relationship of each model file meets the connectivity requirements and obtain the connectivity verification result.

9. A device for generating a map of a distribution network, characterized in that: The device for generating a map of the distribution network comprises: Acquisition module, used to obtain distribution network model data and user-side equipment data; A conversion module, configured to convert the user-side device data into user model data according to a preset standard format; a splicing module, configured to splice the user model data and the distribution network model data according to preset graphic types to obtain model data packets corresponding to the graphic types; The generation module is used to generate a diagram of the distribution network according to the preset layout rules and the model data packages.

10. A device for generating a single diagram of a distribution network, characterized in that: The device for generating a map of the distribution network comprises: a memory and at least one processor, wherein the memory stores instructions; The at least one processor calls the instructions in the memory to enable the device for generating a map of the distribution network to execute the method for generating a map of the distribution network to be operated as described in any one of claims 1 to 8.

11. A computer-readable storage medium having instructions stored thereon, characterized in that: When the instruction is read and executed, the method for generating a map of the distribution network as described in any one of claims 1 to 8 is executed.

Images