A method for topology analysis and cross-domain mapping of heterogeneous power distribution network engineering data

By performing unified preprocessing and cross-domain mapping on heterogeneous power distribution network engineering data, generating a topology connection diagram and performing lightweight processing, the problems of inconsistent data formats and information fragmentation are solved, and standardized data flow and association between different platforms are realized.

CN123115286APending Publication Date: 2026-11-17GUANGDONG POWER GRID CO LTD INFORMATION CENT
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611076578.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-07-20
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In existing technologies, when data from heterogeneous power distribution network projects flows between different platforms, there are problems such as inconsistent data formats, inconsistent field expressions, and fragmented information, making it difficult to effectively transfer and manage data across platforms.

Method used

By acquiring heterogeneous engineering source data, performing unified preprocessing to generate intermediate engineering datasets, identifying distribution network primitive objects, and mapping design-side equipment objects to operation and maintenance-side power grid asset IDs based on a cross-domain mapping rule base, generating topology connection diagrams and performing lightweight processing, and finally encapsulating them into engineering data handover packages, the data standardization and cross-domain mapping are realized.

Benefits of technology

It enables the parsing, association, and transfer of 2D CAD graphic data, 3D GIM model data, and engineering attribute data in the same data link, reducing repetitive manual data entry, ensuring data format uniformity and cross-platform continuity, and solving the problem of information fragmentation.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123115286A_ABST
    Figure CN123115286A_ABST
Patent Text Reader

Abstract

This invention relates to the field of engineering data processing technology and discloses a method for topology analysis and cross-domain mapping of heterogeneous engineering data in power distribution networks. The method includes the following steps: acquiring heterogeneous engineering source data; unified preprocessing; identifying and associating graphic primitives to form a set of design-side equipment objects; cross-domain mapping to generate mapping relationships; topology analysis and model conversion to generate an operation and maintenance-side topology model; lightweight processing, integrity verification, encapsulation of handover packages, and transmission. By adopting a technical solution of unified acquisition, unified preprocessing, and generation of intermediate engineering datasets from heterogeneous engineering source data, this method achieves the technical effect of standardizing two-dimensional CAD graphic data, three-dimensional GIM model data, and engineering attribute data under unified engineering coding, unified coordinate benchmarks, unified equipment classification, and unified attribute field formats. This solves the problems of inconsistent data formats, inconsistent field expressions, and information fragmentation during cross-platform transfer.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of engineering data processing technology, specifically to a method for topology analysis and cross-domain mapping of heterogeneous engineering data in power distribution networks. Background Technology

[0002] Digital management of distribution network infrastructure projects is a crucial aspect of power grid construction and operation management, typically involving multiple stages such as engineering design, construction, completion and handover, asset registration, and operation and maintenance management. During the distribution network engineering design process, the design end generates engineering deliverables such as 2D CAD graphic data, 3D GIM model data, and engineering attribute data. During project handover and operation and maintenance management, these deliverables need to be transferred between design software, infrastructure management platforms, equipment asset management platforms, and digital twin display platforms, and converted into data objects that the target platforms can recognize and manage.

[0003] In existing technologies, two-dimensional CAD graphic data, three-dimensional GIM model data, and engineering attribute data typically use different data formats, coordinate bases, equipment classifications, and attribute field expression methods. Furthermore, the lack of a unified data preprocessing and intermediate data organization mechanism during the engineering data transfer process leads to information fragmentation when heterogeneous power distribution network engineering data flows between different platforms. Summary of the Invention

[0004] To address the shortcomings of existing technologies, this invention provides a method for topology parsing and cross-domain mapping of heterogeneous engineering data in power distribution networks, which solves the problems of inconsistent data formats, inconsistent field expressions, and information fragmentation during cross-platform transfer.

[0005] To achieve the above objectives, the present invention provides the following technical solution: a method for topology analysis and cross-domain mapping of heterogeneous engineering data in power distribution networks, comprising the following steps: S1, Obtain heterogeneous engineering source data output from the power distribution network engineering design terminal. The heterogeneous engineering source data includes two-dimensional CAD graphic data, three-dimensional GIM model data, engineering attribute data, and design version identification data. S2, perform unified preprocessing on the heterogeneous engineering source data to generate an intermediate engineering dataset with unified engineering coding, unified coordinate reference, unified equipment classification and unified attribute field format; S3, Identify power distribution network graphic elements based on the intermediate engineering dataset, and associate the power distribution network graphic elements with the 3D GIM model data and engineering attribute data to form a set of design-side equipment objects; S4. Based on the preset cross-domain mapping rule base, the set of design-side equipment objects is mapped to the grid asset ID, CIM equipment object and asset ledger field on the operation and maintenance side, and a cross-domain mapping relationship is generated. S5. Based on the cross-domain mapping relationship and the conductors, connecting lines, terminal identifiers, node coordinates and equipment adjacency relationships in the two-dimensional CAD graphic data, generate the power distribution network engineering topology connection diagram and convert it into an operation and maintenance side topology model that meets the requirements of the CIM model. S6. Based on the cross-domain mapping relationship, the 3D GIM model data is processed to be lightweight. The lightweight 3D model data is bound to the CIM equipment object, asset ledger field and the power grid asset ID on the operation and maintenance side. After integrity verification, it is packaged into an engineering data handover package and sent to the target platform. The handover status information is generated and associated with the result returned by the target platform.

[0006] By adopting the above technical solutions, the continuous processing methods of unified acquisition of heterogeneous engineering source data, construction of intermediate engineering datasets, identification of design-side equipment objects, conversion of cross-domain mapping rule base, generation of topology connection diagrams, and encapsulation of engineering data handover packages enable 2D CAD graphic data, 3D GIM model data, and engineering attribute data to be parsed, associated, converted, and handed over in the same data link. At the same time, by associating and storing design version identifiers, design-side equipment objects, CIM equipment objects, and operation and maintenance-side power grid asset IDs, the effects of cross-format conversion of distribution network engineering data, automatic construction of topology relationships, automatic mapping of ledger fields, and recordable handover status are achieved, reducing the problems of manual repetitive data entry and data fragmentation.

[0007] Preferably, in S1, the two-dimensional CAD graphic data includes at least one of the following: primary wiring diagram of the power distribution network, plan layout diagram, tower arrangement diagram, or equipment installation diagram; The three-dimensional GIM model data includes three-dimensional component data of towers, conductors, insulators, transformers, switches, cable branch boxes or ring main units; The engineering attribute data includes at least one of the following: equipment name, equipment model, capacity parameters, voltage level, installation location, wire specifications, or construction status data.

[0008] By adopting the above technical solution, since two-dimensional CAD graphic data, three-dimensional GIM model data, and engineering attribute data are acquired simultaneously as heterogeneous engineering source data, the graphic location, three-dimensional model, and equipment attributes in the power distribution network project can be uniformly included in the processing scope at the source stage. At the same time, since the data covers engineering elements such as primary wiring, plan layout, tower arrangement, equipment installation, equipment model, capacity parameters, and conductor specifications, a data foundation is obtained for multi-dimensional collection of engineering design results and subsequent equipment identification, model binding, and ledger filling.

[0009] Preferably, in step S2, the unified preprocessing includes: Perform layer cleaning, coordinate correction, and invalid element removal on 2D CAD graphic data; Perform component coding completion and coordinate normalization on the 3D GIM model data; Perform field name normalization, enumeration value normalization, and missing field completion on the project attribute data.

[0010] By adopting the above technical solutions, layer cleaning and invalid element removal of 2D CAD graphic data can reduce the interference of auxiliary lines, irrelevant annotations, and duplicate elements on equipment identification; component coding completion and coordinate normalization of 3D GIM model data can unify the spatial reference between 3D components and 2D graphic objects; and field name normalization, enumeration value standardization, and missing field completion of engineering attribute data can unify the expression methods of attribute fields from different sources. Therefore, the effects of unified multi-source data format, unified coordinates, and unified attribute fields are achieved, providing standardized input for subsequent power distribution network element object identification and cross-domain mapping.

[0011] Preferably, in S3, the set of design-side equipment objects includes at least design element ID, GIM component ID, equipment type, spatial coordinates, attribute fields, and design version information; Specifically, when the same equipment object meets at least two of the following matching conditions in the two-dimensional CAD graphic data, three-dimensional GIM model data, and engineering attribute data: equipment code, equipment name, spatial location, or equipment type, a corresponding association relationship is established.

[0012] By adopting the above technical solution, the design element ID, GIM component ID, equipment type, spatial coordinates, attribute fields, and design version information are written into the same design-side equipment object record, enabling two-dimensional elements, three-dimensional components, and engineering attributes to be associated around the same equipment object. At the same time, since at least two matching conditions among equipment code, equipment name, spatial location, and equipment type are used to establish the association relationship, the effect of multi-source confirmation and stable association results of design-side equipment objects is achieved, reducing the risk of erroneous association caused by missing single fields or inconsistent names.

[0013] Preferably, in step S4, the cross-domain mapping rule base includes a device type mapping table, an attribute field mapping table, an encoding mapping table, and a ledger template mapping table; The equipment type mapping table records the correspondence between the equipment types in the design phase and the equipment types in the CIM system; The attribute field mapping table records the correspondence between the attribute fields in the design end and the asset ledger fields; The encoding mapping table records the correspondence between design element IDs, GIM component IDs, and power grid asset IDs on the operation and maintenance side. The ledger template mapping table records the correspondence between project attribute data and the ledger fields of the target platform.

[0014] By adopting the above technical solution, since the cross-domain mapping rule base simultaneously sets up equipment type mapping tables, attribute field mapping tables, code mapping tables, and ledger template mapping tables, a rule-based correspondence is formed between the equipment type, engineering attribute fields, graphic element codes, GIM component codes, and target platform ledger fields on the design side. At the same time, since the mapping rules cover CIM equipment objects, asset ledger fields, and power grid asset IDs on the operation and maintenance side, a rule basis for converting design data into operation and maintenance data structures is obtained, which facilitates the transformation of design results into data objects that can be received by the target platform.

[0015] Preferably, in step S4, when generating cross-domain mapping relationships based on the cross-domain mapping rule base, the following steps are included: Based on the encoding mapping table, the design element ID and GIM component ID of the design-side equipment object are matched with the power grid asset ID of the operation and maintenance side; When multiple candidate operation and maintenance side device objects are matched by the design-side device object, the matching and verification are performed in sequence according to the device code, spatial coordinates, device name and device type. Based on the matching and verification results, the target operation and maintenance side device object is determined from the plurality of candidate operation and maintenance side device objects; Write the correspondence between the design-side device object and the target operation and maintenance-side device object into the cross-domain mapping relationship.

[0016] By adopting the above technical solution, the design element ID, GIM component ID, and operation and maintenance side power grid asset ID are first matched based on the coding mapping table. When multiple candidate operation and maintenance side equipment objects appear, they are further verified hierarchically according to equipment code, spatial coordinates, equipment name, and equipment type. Therefore, the effect of candidate object screening and target object determination is achieved. At the same time, since the final correspondence is written into the cross-domain mapping relationship, the same mapping result can be called for subsequent topology node conversion, 3D model binding, and engineering data transfer, reducing the problem of multiple inconsistent identifiers of the same equipment on different platforms.

[0017] Preferably, in step S5, generating the power distribution network engineering topology connection diagram includes: Using the design-side equipment objects as topology nodes, and the conductors, connecting lines, cable segments, or busbar segments in the 2D CAD graphic data as topology edges, the connection relationship between the topology edges and topology nodes is determined based on the terminal identifiers, node coordinates, line routing, and equipment adjacency relationships.

[0018] By adopting the above technical solution, the graphic connection relationships in the two-dimensional CAD drawing can be converted into computable topological relationships by abstracting the design-side equipment objects as topological nodes and the conductors, connecting lines, cable segments, or busbar segments as topological edges. At the same time, by combining terminal identifiers, node coordinates, line routing, and equipment adjacency relationships to determine the connection relationship between topological edges and topological nodes, the effect of automatically resolving the electrical connection relationship between distribution network equipment is achieved, providing a topological data foundation for the subsequent generation of an operation and maintenance-side topological model that meets the requirements of the CIM model.

[0019] Preferably, when the topology node is a pole or tower type device, it identifies the assembly relationship between the pole / tower body, crossarm, insulator string, conductor suspension point, and guy wire; The structural attachment relationship is determined based on the tower type, crossarm direction, hanging point coordinates, and conductor phase sequence. The structural attachment relationship is written into the power distribution network engineering topology connection diagram, and the corresponding asset affiliation field is formed when it is converted into the operation and maintenance side topology model.

[0020] By adopting the above technical solution, when the topology node is a pole-type device, the assembly relationship between the pole body, crossarm, insulator string, conductor suspension point and guy wire is further identified, so that the spatial installation relationship and structural subordination relationship between different components in the distribution network pole-type device are included in the topology analysis scope. At the same time, since the structural attachment relationship is determined according to the pole type, crossarm direction, suspension point coordinates and conductor phase sequence, the effect of simultaneously expressing the electrical connection relationship and structural attachment relationship of pole-type devices is achieved, avoiding the omission of the pole assembly hierarchy relationship when only the conductor connection is analyzed.

[0021] Preferably, in step S6, the lightweight processing of the 3D GIM model data includes: Remove construction auxiliary components, temporary markings, and details that are not necessary for operation and maintenance; Retain the equipment's external outline, installation coordinates, interface locations, wire hanging point locations, nameplate parameters, and operation and maintenance display parameters; The retained lightweight 3D model data is bound to CIM equipment objects, asset ledger fields, and power grid asset IDs on the operation and maintenance side.

[0022] By adopting the above technical solutions, redundant model data in the handover data package can be reduced by deleting construction auxiliary components, temporary markings, and non-operational details. Key geometric and attribute information required during the operation and maintenance phase can be preserved by retaining the equipment outline, installation coordinates, interface locations, conductor attachment points, nameplate parameters, and operation and maintenance display parameters. At the same time, by establishing a binding relationship between the lightweight 3D model data and CIM equipment objects, asset ledger fields, and operation and maintenance-side power grid asset IDs, the effect of consistent association between 3D model data and operation and maintenance-side equipment asset data can be achieved.

[0023] Preferably, in step S6, the integrity verification includes device object mapping integrity verification, asset ledger field integrity verification, topology connection integrity verification, and 3D model binding integrity verification. When verification fails, abnormal location information is generated based on the design element ID, GIM component ID, CIM equipment object, and operation and maintenance side power grid asset ID. When the verification passes, the CIM device object, asset ledger field, operation and maintenance side topology model, lightweight 3D model data and design version identification data are packaged into an engineering data handover package; After the engineering data handover package is sent to the target platform, handover status information is generated based on the results returned by the target platform, and the handover status information is written into an index table corresponding to the design version identifier data, design-side equipment objects, CIM equipment objects, and operation and maintenance-side power grid asset IDs.

[0024] By adopting the above technical solution, since the integrity verification of equipment object mapping, asset ledger fields, topology connections, and 3D model binding is performed before data handover, anomalies such as missing mappings, missing fields, topology breakpoints, or unbound models can be detected before the engineering data handover package is generated. Since anomaly location information is generated based on design element ID, GIM component ID, CIM equipment object, and maintenance-side power grid asset ID when verification fails, a basis for locating and correcting abnormal data is obtained. Since the CIM equipment object, asset ledger fields, maintenance-side topology model, lightweight 3D model data, and design version identifier data are encapsulated into an engineering data handover package after verification passes, and written to an index table after the target platform returns the results, the effect of recording the handover process status and archiving the correspondence between design-side data and maintenance-side data is achieved.

[0025] This invention provides a method for topology analysis and cross-domain mapping of heterogeneous engineering data in power distribution networks. It has the following beneficial effects: 1. This invention achieves the technical effect of standardizing two-dimensional CAD graphic data, three-dimensional GIM model data, and engineering attribute data under unified engineering coding, unified coordinate benchmark, unified equipment classification, and unified attribute field format by adopting a technical solution of unified acquisition, unified preprocessing, and generation of engineering intermediate datasets from heterogeneous engineering source data. Compared with the existing technical solutions that rely on manual export of files, manual arrangement of tables, and separate entry into different platforms, this invention solves the problems of inconsistent data formats, inconsistent field expressions, and information fragmentation during cross-platform transfer.

[0026] 2. This invention adopts a technical solution based on a cross-domain mapping rule base to map equipment type, attribute field, code, and ledger template of design-side equipment objects. This achieves the technical effect of establishing a correspondence between design element ID, GIM component ID, CIM equipment object, asset ledger field, and operation and maintenance side power grid asset ID. Compared with the existing technical solutions that only perform file transfer or one-way interface conversion, this invention solves the problems of lacking a rule-based mapping relationship between design-side objects and operation and maintenance-side asset objects, and the difficulty in maintaining the continuous correspondence of equipment identity and attribute fields.

[0027] 3. This invention adopts a technical solution based on cross-domain mapping relationships for topology parsing, topology model conversion on the operation and maintenance side, lightweight binding of 3D GIM models, integrity verification, engineering data handover package encapsulation, and handover status association storage. This achieves the technical effect of unifying the distribution network engineering topology relationships, 3D models, asset ledger fields, and handover status into the handover process. Compared with the existing technology, which lacks automatic topology relationship construction, tower assembly relationship retention, handover status feedback, and anomaly location mechanisms in the handover process, this invention solves the problems of difficulty in verifying handover results, difficulty in locating failure reasons, and difficulty in tracking the object relationship between the design and operation and maintenance ends. Attached Figure Description

[0028] Figure 1 This is a schematic diagram of the method steps of the present invention; Figure 2 This is a schematic diagram of heterogeneous data acquisition and preprocessing according to the present invention; Figure 3 This is a schematic diagram illustrating the device object identification and association of the present invention; Figure 4 This is a schematic diagram of cross-domain mapping according to the present invention; Figure 5 This is a schematic diagram illustrating the topology model generation and data transfer of the present invention. Detailed Implementation

[0029] The technical solution of the present invention will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0030] Please see the appendix Figure 1 This invention provides a method for topology analysis and cross-domain mapping of heterogeneous engineering data in power distribution networks, comprising the following steps: Please see the appendix Figure 2S1, Obtain heterogeneous engineering source data output from the power distribution network engineering design terminal. The heterogeneous engineering source data includes two-dimensional CAD graphic data, three-dimensional GIM model data, engineering attribute data, and design version identification data. Furthermore, the two-dimensional CAD graphic data includes at least one of the following: primary wiring diagram of the power distribution network, plan layout diagram, tower arrangement diagram, or equipment installation diagram; The 3D GIM model data includes 3D component data of towers, conductors, insulators, transformers, switches, cable branch boxes, or ring main units; Project attribute data includes at least one of the following: equipment name, equipment model, capacity parameters, voltage level, installation location, conductor specifications, or construction status data; Specifically, in S1, two-dimensional CAD graphic data parsing interface, three-dimensional GIM model data parsing interface, and engineering attribute data parsing interface are set up respectively. The project number and design version identifier are used as common retrieval conditions for multi-source data to extract heterogeneous engineering source data belonging to the same project and the same design version from the power distribution network engineering design end.

[0031] For two-dimensional CAD graphic data, the following are parsed to obtain the layer name, block reference name, element handle, element type, element coordinates, line segment endpoints, polyline vertices, text annotations, and spatial adjacency relationships between elements; among them, element types include points, lines, polylines, arcs, block references, and text objects.

[0032] For 3D GIM model data, the following are obtained by parsing: model component tree, GIM component ID, component name, component type, component spatial coordinates, component spatial orientation, component attributes, and hierarchical relationships between components.

[0033] For engineering attribute data, the system parses the equipment code, equipment name, equipment model, capacity parameters, voltage level, installation location, wire specifications, manufacturer, construction status, and completion acceptance status, and retains the original field name, original field value, and data source for each attribute field.

[0034] Based on the project number, design version identifier, source data type, and source data file fingerprint, a source data index is generated for each type of heterogeneous project source data. The source data index is represented as follows: ,in, Indicates the first Source data index of heterogeneous project source data; This represents a hash operation; Indicates the project number; Indicates the design version identifier; Indicates the first Data types of heterogeneous project source data; Indicates the first Source data file fingerprint of heterogeneous project source data.

[0035] Data types This includes 2D CAD graphic data types, 3D GIM model data types, and project attribute data types. Source data file fingerprint. Generates a checksum based on the filename, file size, modification time, and content verification code of the source data file.

[0036] In this scheme, the content verification code of the source data file is preferably generated using the SHA-256 algorithm; the project number and design version identifier are preferably read from the design results management system. When the source data does not carry the design version identifier, the corresponding design version identifier is generated based on the file modification time, the batch of results approval, and the project number.

[0037] Two-dimensional CAD drawing data, three-dimensional GIM model data, and project attribute data with the same project number and design version identifier are written into the same source data cache, and the source data index, source file path, data type, parsing status, and parsing time are recorded. The heterogeneous project source data in the source data cache serves as the input data for unified preprocessing in S2.

[0038] S2 performs unified preprocessing on heterogeneous engineering source data to generate an intermediate engineering dataset with unified engineering coding, unified coordinate reference, unified equipment classification, and unified attribute field format. Furthermore, in S2, the unified preprocessing includes: Perform layer cleaning, coordinate correction, and invalid element removal on 2D CAD graphic data; Perform component coding completion and coordinate normalization on the 3D GIM model data; Perform field name normalization, enumeration value normalization, and missing field completion on project attribute data; Specifically, in S2, the two-dimensional CAD graphic data, three-dimensional GIM model data, and engineering attribute data written to the source data cache area by S1 are taken and processed according to the data type, including graphic cleaning, model sorting, coordinate transformation, and attribute field standardization.

[0039] For two-dimensional CAD graphic data, the equipment layer, line layer, terminal layer, text annotation layer and auxiliary layer are identified according to the preset layer configuration table. Blank elements, duplicate elements, invalid auxiliary lines and construction description layers that are not related to the power distribution network equipment are deleted. Elements with the same element handle or overlapping geometric position and the same attributes are merged into a standard element object.

[0040] For 3D GIM model data, expand the model component tree and extract the component nodes corresponding to towers, crossarms, insulator strings, conductors, transformers, switches, cable branch boxes, and ring main units; for components lacking GIM component IDs, generate supplementary component codes based on the project number, parent component ID, component type, and component sequence number.

[0041] For engineering attribute data, field names from different sources are normalized according to a standard field dictionary. In one embodiment, equipment specifications and model parameters are uniformly mapped to equipment models, and rated capacity and capacity parameters are uniformly mapped to equipment capacity; the enumerated values ​​corresponding to voltage level, construction status, and equipment type are uniformly encoded, and null value identifiers and missing reason identifiers are added to missing fields.

[0042] Coordinate unification processing is performed on 2D CAD graphic data and 3D GIM model data. Based on at least three non-collinear engineering control points, the scale factor, rotation matrix, and translation vector are calculated, and the parameters are determined by the following formula: ;in, Indicates the number of engineering control points involved in coordinate registration; Indicates the first The coordinate vectors of each engineering control point in the source coordinate system; Indicates the first The coordinate vectors of each engineering control point in the target engineering coordinate system; Indicates the scale coefficient to be determined; This represents the rotation matrix to be determined; This represents the translation vector to be determined. , and Let X represent the scale factor, rotation matrix, and translation vector, respectively, that minimize the sum of squared residuals of the control point coordinates. This represents the parameter that minimizes the objective function; This represents the Euclidean norm.

[0043] Using the scale factor, rotation matrix, and translation vector, the first... The coordinates of each source data object are converted to unified engineering coordinates, represented as follows: ;in, Indicates the first The original coordinate vector of each source data object in the source coordinate system; Indicates the first The coordinate vector of a source data object in a unified engineering coordinate system.

[0044] When 2D CAD graphic data uses 2D coordinates, the 2D coordinates will be used as the coordinates. Expanded to three-dimensional coordinates Then, coordinates are unified with the 3D GIM model data; when the equipment elevation is recorded in the CAD drawing, the equipment elevation is used as the third-dimensional coordinate value.

[0045] In this scheme, the number of engineering control points involved in coordinate registration The maximum residual of the control point after coordinate correction is preferably not less than 3; the maximum residual of the control point after coordinate correction is preferably not greater than 0.5m; when the maximum residual of the control point is greater than 0.5m, the corresponding source data is marked as coordinate abnormal data, and the abnormal control point number and residual value are recorded.

[0046] After completing graphic cleaning, component code completion, coordinate unification, and attribute field standardization, source data indexes, unified engineering codes, unified coordinates, standard equipment types, standard attribute fields, and design version identifiers are added to each data object, generating an intermediate engineering dataset. This intermediate dataset serves as input data for S3 to identify power distribution network element objects and establish multi-source relationships.

[0047] Please see the appendix Figure 3 S3, Identify power distribution network graphic elements based on intermediate engineering datasets, and associate power distribution network graphic elements with 3D GIM model data and engineering attribute data to form a set of design-side equipment objects; Furthermore, in S3, the set of equipment objects on the design side includes at least the design element ID, GIM component ID, equipment type, spatial coordinates, attribute fields, and design version information; Among them, when the same equipment object meets at least two of the matching conditions of equipment code, equipment name, spatial location or equipment type in two-dimensional CAD graphic data, three-dimensional GIM model data and engineering attribute data, a corresponding association relationship is established. Specifically, in S3, the intermediate dataset of the project generated by S2 is used to identify power distribution network primitive objects based on the layer name, block reference name, primitive geometry, text annotation and spatial adjacency relationship in the two-dimensional CAD graphic data.

[0048] When a CAD element is a block reference object, the device type is identified based on the block reference name and block attributes. When a CAD element is a line segment or polyline object, it is identified as a conductor, connector, cable segment, or busbar segment based on its layer, line type, start and end point coordinates, and adjacent elements. When a CAD element is a text object, the text content is matched with a preset device keyword library, and the matching result is used as the device name, device code, or model parameter of adjacent device elements.

[0049] For each CAD primitive object identified, GIM components and engineering attribute objects that meet the candidate conditions in terms of spatial location, equipment type, or equipment code are selected from the intermediate engineering dataset to form a set of candidate associated objects.

[0050] Calculate the first The first CAD primitive object and the first Spatial distance between candidate related objects: ; in, Indicates the first The first CAD primitive object and the first Spatial distance between candidate related objects; Indicates the first Unified engineering coordinates for each CAD element object; Indicates the first Unified engineering coordinates for each candidate associated object.

[0051] Calculate spatial location matching value based on spatial distance: ;in, Indicates the first The first CAD primitive object and the first Spatial location matching values ​​between candidate associated objects; Represents an exponential function with the natural constant as its base; This indicates the scale parameter for spatial location matching.

[0052] The device name matching value is represented as: ; in, Indicates the device name matching value; Indicates the first The standardized device name of a CAD element object; Indicates the first The standardized device names of the candidate associated objects; Indicates name With name Edit distance between; and Representing names respectively and name The length of the characters; This indicates the operation of finding the maximum value.

[0053] Match device code value Set to: 1 if the standardized device codes are the same, otherwise 0; match device type values. Set to 1 when the standard device type is the same or belongs to the preset compatible device type, otherwise set to 0.

[0054] No. The first CAD primitive object and the first The association matching score between candidate associated objects is represented as follows: ; in, Indicates the associated matching score; , , and These represent the matching weights corresponding to device code, device name, spatial location, and device type, respectively, and satisfy the following conditions: ; The range of values ​​for device code matching, device name matching, spatial location matching, and device type matching is [missing information]. .

[0055] In this plan, The preferred value is 0.4. The preferred value is 0.2. The preferred value is 0.3. The preferred value is 0.1, which is the spatial location matching scale parameter. The preferred depth is 0.5m.

[0056] When the correlation matching score When at least two of the following conditions are met: the device code is not less than 0.65, the device name matching value is not less than 0.8, the spatial distance is not greater than 0.5m, and the device type matches, an association relationship is established between the CAD primitive object and the GIM component or project attribute object.

[0057] When a CAD element object corresponds to multiple candidate associated objects that meet the conditions, the candidate associated object with the highest associated matching score is selected; when the difference between the highest and second highest associated matching scores is less than a preset difference, the corresponding CAD element object is marked as an object to be reviewed.

[0058] In this scheme, the preset difference between the highest correlation matching score and the second highest correlation matching score is preferably 0.05.

[0059] Based on the established relationships, the design element ID, GIM component ID, equipment code, equipment type, unified engineering coordinates, standard attribute fields, source data index, and design version identifier are written into the same equipment object record, forming a design-side equipment object set. This design-side equipment object set serves as the input data for S4 to generate cross-domain mapping relationships.

[0060] Please see the appendix Figure 4 S4, based on the preset cross-domain mapping rule base, maps the set of equipment objects on the design side to the power grid asset ID, CIM equipment object and asset ledger fields on the operation and maintenance side, and generates cross-domain mapping relationships; Furthermore, in S4, the cross-domain mapping rule base includes a device type mapping table, an attribute field mapping table, an encoding mapping table, and a ledger template mapping table; The equipment type mapping table records the correspondence between the equipment types in the design phase and the equipment types in the CIM. The attribute field mapping table records the correspondence between attribute fields in the design phase and asset ledger fields; The coding mapping table records the correspondence between design element IDs, GIM component IDs, and power grid asset IDs on the operation and maintenance side; The ledger template mapping table records the correspondence between project attribute data and the ledger fields of the target platform; In S4, when generating cross-domain mapping relationships based on the cross-domain mapping rule base, the following is included: Based on the coding mapping table, the design element ID and GIM component ID of the equipment object on the design side are matched with the power grid asset ID on the operation and maintenance side; When multiple candidate operation and maintenance equipment objects are obtained by matching the design-side equipment object, the matching and verification are performed in sequence according to the equipment code, spatial coordinates, equipment name and equipment type. Based on the matching and verification results, the target operation and maintenance side device object is determined from multiple candidate operation and maintenance side device objects; Write the correspondence between the design-side device objects and the target operation and maintenance-side device objects into the cross-domain mapping relationship; Specifically, in S4, the set of design-side device objects formed in S3 is inherited, and the cross-domain mapping rule library corresponding to the target platform is called according to the target platform type.

[0061] The equipment type mapping table records the correspondence between standard equipment types, CIM equipment types, and target platform equipment classification codes at the design end; the attribute field mapping table records the correspondence between standard attribute fields, CIM attribute fields, and asset ledger fields at the design end; the code mapping table records the correspondence between design element IDs, GIM component IDs, and power grid asset IDs at the operation and maintenance side; and the ledger template mapping table records the field names, field types, required attributes, data units, and data sources in the target platform ledger template.

[0062] For the first in the design-side device object set For each design-side equipment object, based on the project number, equipment type, equipment code, and spatial location, candidate operation and maintenance-side equipment objects are selected from the existing operation and maintenance-side equipment objects on the target platform to form a candidate operation and maintenance-side equipment object set. .

[0063] Calculate the first Each design-side device object and candidate set The Middle Comprehensive matching score among candidate operation and maintenance side equipment objects: ; in, Indicates the first The design-side equipment object and the first A comprehensive matching score among candidate operation and maintenance side equipment objects; Indicates the device coding consistency score; Indicates the consistency score of GIM component coding; Indicates the consistency score of spatial coordinates; Indicates the consistency score of the equipment name; Indicates the consistency score of equipment type; , , , and Let each represent the weight of the corresponding score, and satisfy the following conditions: ; The value ranges for equipment code consistency score, GIM component code consistency score, spatial coordinate consistency score, equipment name consistency score, and equipment type consistency score are all [missing information]. .

[0064] Specifically, when the equipment code of the design-side equipment object and the asset code of the candidate operation and maintenance-side equipment object satisfy the correspondence in the coding mapping table, the equipment code consistency score is 1; when the GIM component ID of the design-side equipment object is consistent with the model component code recorded by the candidate operation and maintenance-side equipment object, the GIM component code consistency score is 1; the spatial coordinate consistency score is determined according to the spatial location matching value calculation method in S3; and the equipment name consistency score is determined according to the equipment name matching value calculation method in S3.

[0065] The candidate operation and maintenance side device object with the highest comprehensive matching score is determined from the set of candidate operation and maintenance side device objects, denoted as: ; in, This indicates the sequence number of the candidate operation and maintenance side device object with the highest comprehensive matching score; Indicates the first A set of candidate operation and maintenance side equipment objects corresponding to each design-side equipment object; This indicates the candidate number that corresponds to the maximum value of the comprehensive matching score.

[0066] In this plan, The preferred value is 0.35. The preferred value is 0.25. The preferred value is 0.20. The preferred value is 0.10. The preferred value is 0.10.

[0067] When the highest overall matching score When it is not less than 0.7, the first One candidate operation and maintenance side device object is determined as the target operation and maintenance side device object; when multiple candidate operation and maintenance side device objects have the same comprehensive matching score, or the difference between the highest comprehensive matching score and the second highest comprehensive matching score is less than 0.05, the matching verification is carried out in sequence according to the consistency of device code, spatial coordinates, device name and device type.

[0068] Based on the equipment type mapping table, the equipment type of the design-side equipment object is converted into the corresponding CIM equipment type; based on the attribute field mapping table and the ledger template mapping table, the equipment model, capacity parameters, voltage level, installation location, wire specifications, manufacturer, and construction status are written into the corresponding asset ledger fields.

[0069] The design element ID, GIM component ID, design-side equipment type, CIM equipment type, asset ledger fields, target platform receiving fields, operation and maintenance-side power grid asset ID, design version identifier, and comprehensive matching score are written into the cross-domain mapping relationship table to form a cross-domain mapping relationship. The cross-domain mapping relationship serves as the basis for topology node transformation in S5 and 3D model binding and data encapsulation in S6.

[0070] Please see the appendix Figure 5 S5, based on cross-domain mapping relationships and conductors, connecting lines, terminal identifiers, node coordinates and equipment adjacency relationships in two-dimensional CAD graphic data, generates a power distribution network engineering topology connection diagram and converts it into an operation and maintenance side topology model that meets the requirements of CIM model; Furthermore, in S5, generating the distribution network engineering topology connection diagram includes: The topology nodes are the equipment objects on the design side, and the topology edges are the wires, connecting lines, cable segments or busbar segments in the two-dimensional CAD graphic data. The connection relationship between the topology edges and topology nodes is determined according to the terminal identification, node coordinates, line routing and equipment adjacency relationship. When the topology node is a pole or tower type device, identify the assembly relationship between the pole / tower body, crossarm, insulator string, conductor suspension point, and guy wire; The structural attachment relationship is determined based on the tower type, crossarm direction, hanging point coordinates, and conductor phase sequence. The structural attachment relationships are written into the topology connection diagram of the power distribution network project, and the corresponding asset affiliation relationship fields are formed when the topology model is converted into the operation and maintenance side. Specifically, in S5, the set of design-side equipment objects formed in S3 and the cross-domain mapping relationship generated in S4 are used as topology nodes, and the conductors, connecting lines, cable segments or busbar segments in the two-dimensional CAD graphic data are used as topology edges to generate the initial distribution network engineering topology connection diagram.

[0071] For each topology edge, extract the topology edge identifier, start coordinates, end coordinates, route, route type, terminal identifier, phase sequence identifier, and adjacent equipment objects. Based on the cross-domain mapping relationship, associate the design-side equipment objects at both ends of the topology edge with CIM equipment objects and operation-maintenance-side power grid asset IDs.

[0072] When the endpoint of a topology edge is directly within the terminal range of a device element, a connection is established between that endpoint and the corresponding terminal. When the endpoint of a topology edge is not directly within the terminal range of a device element, candidate terminals are selected based on device type, layer affiliation, line type, and spatial distance to form a candidate terminal set. .

[0073] The minimum distance between the endpoint of the topological edge and the candidate terminal is expressed as: ; in, This represents the minimum distance between the endpoint of the topology edge and the candidate terminal; Indicates the endpoints of the topological edge. The corresponding set of candidate terminals; Represents any candidate terminal in the candidate terminal set; The coordinate vector representing the endpoints of the topological edge; Indicates candidate terminal The coordinate vector.

[0074] The candidate terminal with the smallest distance from the topological edge endpoint is represented as: ;in, This represents the candidate terminal with the smallest distance from the topological edge endpoint.

[0075] Further calculations are performed to determine the directional consistency between the topology edge direction and the candidate terminal connection direction: ; in, Represents the endpoints of the topology edge With candidate terminals Consistency in direction between them; This represents the direction vector of a topological edge at its endpoint. Indicates the connection direction vector of the candidate terminal; superscript Indicates vector transpose; This indicates taking the absolute value.

[0076] When the minimum distance Not greater than the endpoint adsorption threshold, and with consistent orientation. When the value is not less than the directional consistency threshold, connect the topology edge endpoints to the candidate terminals. Otherwise, mark the endpoint of the topological edge as a topological breakpoint.

[0077] In this scheme, the endpoint snapping threshold is preferably 0.3m, and the directional consistency threshold is preferably 0.8m. For CAD drawings with a small scale or low coordinate accuracy, the endpoint snapping threshold can be adjusted according to the drawing scale and coordinate error.

[0078] When the topology node is a pole or tower type device, based on the device code and spatial range of the pole or tower body element, search for crossarms, insulator strings, conductor hanging points, and guy wire elements that are located within the spatial range or have a block nesting relationship with the pole or tower body to form a set of pole or tower assembly objects.

[0079] The installation relationship between the crossarm and the tower body is determined based on the positional relationship between the center coordinates of the crossarm and the central axis of the tower; the installation relationship between the insulator string and the crossarm is determined based on the distance between the end point of the insulator string and the crossarm connection point; the connection relationship between the conductor and the insulator string is determined based on the coordinates of the conductor end point, phase sequence mark, and free end of the insulator string; and the attachment relationship between the guy wire and the tower body is determined based on the positional relationship between the end point of the guy wire and the tower body and the ground anchor point.

[0080] The relationships between the tower body, crossarm, insulator string, conductor suspension point, conductor, and guy wire are written into the distribution network engineering topology connection diagram. Among them, conductors, connecting wires, cable segments, and busbar segments form electrical connection relationships; the tower body, crossarm, insulator string, conductor suspension point, and guy wire form structural attachment relationships.

[0081] Based on the cross-domain mapping relationship generated by S4, the design-side equipment objects are replaced with the corresponding CIM equipment objects. The topology edges are converted into associations between terminal objects, connection node objects, and conductive equipment objects. The structural attachment relationships are converted into asset dependency relationship fields between CIM equipment objects or asset objects, generating the operation and maintenance-side topology model. The operation and maintenance-side topology model serves as the input data for S6 to perform 3D model binding and integrity verification.

[0082] S6 performs lightweight processing of 3D GIM model data based on cross-domain mapping relationship, binds lightweight 3D model data with CIM equipment objects, asset ledger fields and power grid asset IDs on the operation and maintenance side, encapsulates it into an engineering data handover package after integrity verification and sends it to the target platform, generates handover status information based on the results returned by the target platform and stores it in association. Furthermore, in S6, lightweight processing of 3D GIM model data includes: Remove construction auxiliary components, temporary markings, and details that are not necessary for operation and maintenance; Retain the equipment's external outline, installation coordinates, interface locations, wire hanging point locations, nameplate parameters, and operation and maintenance display parameters; The retained lightweight 3D model data is bound to the CIM equipment objects, asset ledger fields, and power grid asset IDs on the operation and maintenance side. In S6, integrity verification includes device object mapping integrity verification, asset ledger field integrity verification, topology connection integrity verification, and 3D model binding integrity verification. When verification fails, abnormal location information is generated based on the design element ID, GIM component ID, CIM equipment object, and operation and maintenance side power grid asset ID. When the verification passes, the CIM device object, asset ledger field, operation and maintenance side topology model, lightweight 3D model data and design version identification data are packaged into an engineering data handover package; After the engineering data handover package is sent to the target platform, handover status information is generated based on the results returned by the target platform, and the handover status information is written into the index table corresponding to the design version identifier data, design-side equipment objects, CIM equipment objects, and operation and maintenance-side power grid asset IDs. Specifically, in S6, the cross-domain mapping relationship generated in S4 and the operation and maintenance side topology model generated in S5 are inherited. Based on the correspondence between design element ID, GIM component ID, CIM equipment object and operation and maintenance side power grid asset ID, the components in the 3D GIM model data are filtered and lightweighted.

[0083] Regarding the first For each GIM component, determine whether it has a power grid asset ID binding relationship on the operation and maintenance side, whether it participates in the operation and maintenance side topology model, whether it contains asset ledger fields, and whether it contains operation and maintenance display parameters, and calculate the GIM component retention score: ; in, Indicates the first Retention score for each GIM component; Indicates the first Does each GIM component have a binding relationship with the power grid asset ID on the operation and maintenance side? Indicates the first Whether each GIM component participates in the operation and maintenance side topology model; Indicates the first Does each GIM component contain an asset ledger field? Indicates the first Does each GIM component include operation and maintenance display parameters? , , and Let each represent the weight of the corresponding judgment item, and satisfy the following: ; When the corresponding conditions are met , , or The value of is 1; when the corresponding condition is not met, its value is 0.

[0084] In this plan, The preferred value is 0.35. The preferred value is 0.30. The preferred value is 0.20. The preferred value is 0.15; the preferred component retention score threshold is 0.6.

[0085] When GIM components are retained If the score is not less than 0.6, retain the equipment outline, installation coordinates, spatial orientation, interface location, wire attachment point location, nameplate parameters, and operation and maintenance display parameters of the GIM component, and delete construction auxiliary components, temporary positioning marks, design verification parameters, duplicate texture data, and non-operation and maintenance necessary details; if the retention score is less than 0.6, remove the GIM component from the 3D model to be handed over or only retain its component identifier and parent component relationship.

[0086] The lightweight GIM components are bound to the corresponding CIM device objects, asset ledger fields, operation and maintenance side topology nodes, and operation and maintenance side power grid asset IDs, and the GIM component ID, CIM device object ID, asset ID, model file location, and model version are recorded.

[0087] After completing the lightweight 3D model data binding, calculate the device object mapping integrity rate, asset ledger field integrity rate, topology connection integrity rate, and 3D model binding integrity rate respectively.

[0088] Device object mapping completeness is expressed as: ; in, Indicates the device object mapping completeness rate; This indicates the number of design-side device objects with established valid cross-domain mapping relationships; This indicates the total number of design-side equipment objects involved in the handover.

[0089] The asset ledger field completeness rate is expressed as: ; in, Indicates the completeness rate of asset ledger fields; This indicates the number of required ledger fields that have been filled in and whose data type, data unit, and value format all conform to the target platform's specifications. This indicates the total number of required fields in the target platform's ledger template.

[0090] Topology connectivity completeness is expressed as: ; in, Indicates the topology connectivity completeness; This indicates the number of valid terminal connection relationships or asset dependency relationships that have been generated in the topology. This represents the total number of expected topological relationships determined based on the distribution network engineering topology connection diagram generated by S5.

[0091] The completeness of 3D model binding is expressed as: ; in, Indicates the completeness of the 3D model binding; This indicates the number of lightweight GIM components that have been bound to CIM device objects and operation and maintenance-side power grid asset IDs. This indicates the total number of device objects that need to be bound to a 3D model according to the target platform's receiving specifications.

[0092] Calculate the comprehensive verification score based on the completeness rate of each item: ; in, This indicates the comprehensive verification score; , , and These represent the weights corresponding to the device object mapping completeness rate, asset ledger field completeness rate, topology connection completeness rate, and 3D model binding completeness rate, respectively, and satisfy the following conditions: ; In this plan, , , and The optimal value is 0.25; comprehensive verification score Preferably, the value should be no less than 0.95, and preferably, any one of the following: device object mapping completeness rate, asset ledger field completeness rate, topology connection completeness rate, and 3D model binding completeness rate should be no less than 0.90.

[0093] When the comprehensive verification score or the completeness rate of any single item fails to meet the corresponding threshold, anomaly location information is generated based on the data type of the verification failure. This information includes the anomaly type, design element ID, GIM component ID, CIM equipment object ID, operation and maintenance side power grid asset ID, anomaly field, anomaly coordinates, and data source. The corresponding data is then marked as data to be corrected.

[0094] When the comprehensive verification score and the completeness rate of each item meet the corresponding threshold, the CIM equipment objects, asset ledger fields, operation and maintenance side topology model, lightweight 3D model data, cross-domain mapping relationship, design version identifier and exception handling record are encapsulated into an engineering data handover package.

[0095] The engineering data handover package includes a package header, equipment object data area, asset ledger data area, topology model data area, lightweight 3D model data area, mapping log data area, verification files, and receipt interface information. The package header records the project number, design version identifier, handover package number, generation time, and target platform type.

[0096] Calculate the hash value of each data area separately, and generate the overall verification value of the engineering data handover package: ; in, This represents the overall verification value of the engineering data handover package; This represents the hash value of the packet header; The hash value representing the device object's data area; This represents the hash value of the asset ledger data area; The hash value represents the topology model data area; The hash value representing the lightweight 3D model data area; This represents the hash value of the mapped log data area.

[0097] In response to the one-click handover command, the project data handover package and overall verification value are sent to the target platform. After receiving the project data handover package, the target platform performs verification on the overall verification value, field format, equipment code, topology relationship and model file, and returns the handover task number, reception status, verification status, storage status, exception code and processing time.

[0098] Based on the results returned by the target platform, handover status information is generated. The handover status information includes at least one of the following: pending, sending, being verified by the target platform, being added to the database by the target platform, handover successful, or handover failed.

[0099] Write the project number, design version identifier, handover package number, handover task number, design element ID, GIM component ID, CIM equipment object ID, operation and maintenance side power grid asset ID, handover status, exception code, and processing time into the handover index table, and establish an association between the handover task number returned by the target platform and the corresponding project data handover package.

[0100] Although embodiments of the invention have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the appended claims and their equivalents.

Claims

1. A method for topology analysis and cross-domain mapping of heterogeneous engineering data in power distribution networks, characterized in that, Includes the following steps: S1, Obtain heterogeneous engineering source data output from the power distribution network engineering design terminal. The heterogeneous engineering source data includes two-dimensional CAD graphic data, three-dimensional GIM model data, engineering attribute data, and design version identification data. S2, perform unified preprocessing on the heterogeneous engineering source data to generate an intermediate engineering dataset with unified engineering coding, unified coordinate reference, unified equipment classification and unified attribute field format; S3, Identify power distribution network graphic elements based on the intermediate engineering dataset, and associate the power distribution network graphic elements with the 3D GIM model data and engineering attribute data to form a set of design-side equipment objects; S4. Based on the preset cross-domain mapping rule base, the set of design-side equipment objects is mapped to the grid asset ID, CIM equipment object and asset ledger field on the operation and maintenance side, and a cross-domain mapping relationship is generated. S5. Based on the cross-domain mapping relationship and the conductors, connecting lines, terminal identifiers, node coordinates and equipment adjacency relationships in the two-dimensional CAD graphic data, generate the power distribution network engineering topology connection diagram and convert it into an operation and maintenance side topology model that meets the requirements of the CIM model. S6. Based on the cross-domain mapping relationship, the 3D GIM model data is processed to be lightweight. The lightweight 3D model data is bound to the CIM equipment object, asset ledger field and the power grid asset ID on the operation and maintenance side. After integrity verification, it is packaged into an engineering data handover package and sent to the target platform. The handover status information is generated and associated with the result returned by the target platform.

2. The method for topology analysis and cross-domain mapping of heterogeneous engineering data in a power distribution network according to claim 1, characterized in that, In S1, the two-dimensional CAD graphic data includes at least one of the following: primary wiring diagram of the power distribution network, plan layout diagram, tower arrangement diagram, or equipment installation diagram. The three-dimensional GIM model data includes three-dimensional component data of towers, conductors, insulators, transformers, switches, cable branch boxes or ring main units; The engineering attribute data includes at least one of the following: equipment name, equipment model, capacity parameters, voltage level, installation location, wire specifications, or construction status data.

3. The method for topology analysis and cross-domain mapping of heterogeneous engineering data in a power distribution network according to claim 1, characterized in that, In S2, the unified preprocessing includes: Perform layer cleaning, coordinate correction, and invalid element removal on 2D CAD graphic data; Perform component coding completion and coordinate normalization on the 3D GIM model data; Perform field name normalization, enumeration value normalization, and missing field completion on the project attribute data.

4. The method for topology analysis and cross-domain mapping of heterogeneous engineering data in a power distribution network according to claim 1, characterized in that, In S3, the set of equipment objects on the design side includes at least design element ID, GIM component ID, equipment type, spatial coordinates, attribute fields, and design version information; Specifically, when the same equipment object meets at least two of the following matching conditions in the two-dimensional CAD graphic data, three-dimensional GIM model data, and engineering attribute data: equipment code, equipment name, spatial location, or equipment type, a corresponding association relationship is established.

5. The method for topology analysis and cross-domain mapping of heterogeneous engineering data in a power distribution network according to claim 1, characterized in that, In S4, the cross-domain mapping rule base includes a device type mapping table, an attribute field mapping table, an encoding mapping table, and a ledger template mapping table; The equipment type mapping table records the correspondence between the equipment types in the design phase and the equipment types in the CIM system; The attribute field mapping table records the correspondence between the attribute fields in the design end and the asset ledger fields; The encoding mapping table records the correspondence between design element IDs, GIM component IDs, and power grid asset IDs on the operation and maintenance side. The ledger template mapping table records the correspondence between project attribute data and the ledger fields of the target platform.

6. The method for topology analysis and cross-domain mapping of heterogeneous engineering data in a power distribution network according to claim 5, characterized in that, In step S4, when generating cross-domain mapping relationships based on the cross-domain mapping rule base, the following steps are included: Based on the encoding mapping table, the design element ID and GIM component ID of the design-side equipment object are matched with the power grid asset ID of the operation and maintenance side; When multiple candidate operation and maintenance side device objects are matched by the design-side device object, the matching and verification are performed in sequence according to the device code, spatial coordinates, device name and device type. Based on the matching and verification results, the target operation and maintenance side device object is determined from the plurality of candidate operation and maintenance side device objects; Write the correspondence between the design-side device object and the target operation and maintenance-side device object into the cross-domain mapping relationship.

7. The method for topology analysis and cross-domain mapping of heterogeneous engineering data in a power distribution network according to claim 1, characterized in that, In step S5, generating the distribution network engineering topology connection diagram includes: Using the equipment objects on the design side as topology nodes, and the wires, connecting lines, cable segments or busbar segments in the two-dimensional CAD graphic data as topology edges, the connection relationship between the topology edges and topology nodes is determined based on the terminal identification, node coordinates, line routing and equipment adjacency relationship.

8. The method for topology analysis and cross-domain mapping of heterogeneous engineering data in a power distribution network according to claim 7, characterized in that, When the topology node is a pole or tower type device, the assembly relationship between the pole / tower body, crossarm, insulator string, conductor suspension point, and guy wire is identified. The structural attachment relationship is determined based on the tower type, crossarm direction, hanging point coordinates, and conductor phase sequence. The structural attachment relationship is written into the power distribution network engineering topology connection diagram, and the corresponding asset affiliation field is formed when it is converted into the operation and maintenance side topology model.

9. The method for topology analysis and cross-domain mapping of heterogeneous engineering data in a power distribution network according to claim 1, characterized in that, In step S6, the lightweight processing of the 3D GIM model data includes: Remove construction auxiliary components, temporary markings, and details that are not necessary for operation and maintenance; Retain the equipment's external outline, installation coordinates, interface locations, wire hanging point locations, nameplate parameters, and operation and maintenance display parameters; The retained lightweight 3D model data is bound to CIM equipment objects, asset ledger fields, and power grid asset IDs on the operation and maintenance side.

10. The method for topology analysis and cross-domain mapping of heterogeneous engineering data in a power distribution network according to claim 1, characterized in that, In S6, the integrity verification includes device object mapping integrity verification, asset ledger field integrity verification, topology connection integrity verification, and 3D model binding integrity verification. When verification fails, abnormal location information is generated based on the design element ID, GIM component ID, CIM equipment object, and operation and maintenance side power grid asset ID. When the verification passes, the CIM device object, asset ledger field, operation and maintenance side topology model, lightweight 3D model data and design version identification data are packaged into an engineering data handover package; After the engineering data handover package is sent to the target platform, handover status information is generated based on the results returned by the target platform, and the handover status information is written into an index table corresponding to the design version identifier data, design-side equipment objects, CIM equipment objects, and operation and maintenance-side power grid asset IDs.