Data-driven IT architecture graph generation method and device
By building a unified data model and a declarative rule language, real-time synchronization and efficient incremental updates of IT architecture diagrams were achieved, solving the problems of data and view disconnect and consistency, and improving the update efficiency and accuracy of IT architecture diagrams.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- CHINA IND SECURITIES CO LTD
- Filing Date
- 2025-12-03
- Publication Date
- 2026-05-01
AI Technical Summary
Existing IT architecture diagram generation methods suffer from data and view disconnect, lack of efficient incremental update mechanisms, and lack of bidirectional consistency guarantees, resulting in outdated diagrams, layout jumps, and cumbersome consistency checks.
It adopts a data-driven approach, constructs a unified data model, uses a declarative rule language to define mapping relationships, achieves stable IDs for nodes and edges, performs incremental topology updates, and has automated consistency verification and correction capabilities, supporting bidirectional real-time synchronization of data and graphs.
It enables real-time synchronization of data and graphics, improves update efficiency and accuracy, reduces layout jitter, enhances the automation level of consistency verification, and reduces compliance audit costs.
Smart Images
Figure CN121957656A_ABST
Abstract
Description
Data-driven IT architecture diagram generation method and apparatus Technical Field
[0001] This invention relates to the field of computer software, and in particular to a data-driven method and apparatus for automatically generating IT architecture diagrams. Background Technology
[0002] In modern enterprise IT operations and architecture management, accurate and intuitive architecture topology diagrams are core tools for system monitoring, capacity planning, change management, and fault analysis. However, the generation and maintenance of such architecture diagrams have long relied heavily on manual drawing (such as using tools like Visio) or semi-automatic CMDB visualization plugins. These traditional methods have revealed many insurmountable limitations in the increasingly dynamic and complex IT environment.
[0003] First, there is a severe disconnect between data and view. Manually drawn diagrams are essentially "static works of art," their content being separate from dynamic data sources such as the actual Configuration Management Database (CMDB) and cloud resource inventory. Any changes to the data center, such as server expansion, application instance migration, or network configuration adjustments, cannot be reflected in the architecture diagram in real time, causing the diagrams to quickly become outdated and lose their reference value, creating a governance blind spot of "diagram-data" inconsistency.
[0004] Secondly, there is a lack of efficient incremental update mechanisms. Some existing automated graphical tools typically regenerate the entire topology map by full reconstruction when data changes. This not only causes significant performance overhead when dealing with large-scale architectures, but more critically, it leads to drastic changes in layout, i.e., the "map jump" phenomenon. This severely damages the visual memory and spatial cognition of operations and maintenance personnel, requiring them to relocate and understand the architecture after each update, resulting in a very poor user experience.
[0005] Furthermore, there is a lack of bidirectional consistency guarantees. While a few solutions can achieve unidirectional generation from data to graphs, when users edit the graphs to correct reality, these modifications cannot be automatically and reliably written back to the underlying data source. This unidirectional process makes it impossible to eliminate discrepancies between data and graphics in a closed loop, and consistency verification relies on manual processes, which are cumbersome and prone to errors.
[0006] Therefore, there is an urgent need in this field for an automatic IT architecture diagram generation method that can achieve real-time bidirectional synchronization of data and graphics, support high-performance incremental updates and stable layouts, and have automated consistency verification and correction capabilities. Summary of the Invention
[0007] Based on the above-mentioned problems in this technical field, the present invention proposes the following technical solution:
[0008] A data-driven method for generating IT architecture diagrams includes the following steps:
[0009] Construct a unified data model to standardize IT configuration and architecture data from several heterogeneous data sources into a set of configuration items and relationships based on the unified data model;
[0010] A declarative rule language is used to define the mapping relationship between configuration item types and relation definitions, visual coding rules, and layout constraints;
[0011] In response to the event stream of the data processing engine, based on the stable IDs assigned to nodes and edges, the local subgraph affected by the change is located, and the local subgraph is incrementally updated.
[0012] The affected local subgraphs are subjected to stability constraints that maintain geometric continuity and are then rearranged to update the overall architecture graph.
[0013] Furthermore, in the data-driven IT architecture diagram generation method, the "incremental topology update of the local subgraph" specifically includes:
[0014] Receive event streams from the data processing engine and extract configuration items and relationship change information;
[0015] Compare the current topology with the event data to generate node difference sets and edge difference sets;
[0016] Based on the stable ID, the affected local subgraph is located, and topology merging and deduplication operations are performed on the difference set.
[0017] Furthermore, in the data-driven IT architecture diagram generation method, after the step of "performing topology merging and deduplication operations on the difference set", the method further includes: triggering a re-layout of the affected local subgraphs; and merging the updated subgraphs with the original topology diagram.
[0018] Furthermore, in the data-driven IT architecture diagram generation method, after the step of "incremental topology update of the local subgraph", the method further includes the following steps: classifying the bidirectional differences between the current architecture diagram and the target state defined by the unified data model to obtain inconsistency types including missing, conflicting, or redundant types; performing a credibility assessment on the inconsistency types based on the declarative rule language; triggering a preset correction operation based on the result of the credibility assessment, including data write-back or approval flow recording; and recording the correction operation and its result in the audit log.
[0019] Furthermore, in the data-driven IT architecture diagram generation method, the step of "standardizing IT configuration and architecture data from several heterogeneous data sources into a set of configuration items and relationships based on the unified data model" specifically includes:
[0020] It can access heterogeneous data sources, including CMDB, Excel, and Visio.
[0021] The heterogeneous data source data is parsed, cleaned, field aligned, entity extracted, and relation inferred.
[0022] The processed data is transformed into a set of configuration items and relationships based on a unified data model.
[0023] Corresponding to the method, the inventors also propose a data-driven IT architecture diagram generation device, comprising:
[0024] The data standardization module is used to build a unified data model and standardize IT configuration and architecture data from several heterogeneous data sources into a set of configuration items and relationships based on the unified data model.
[0025] The relation template binding module is used to define the mapping relationship between configuration item types and relation definitions, visual coding rules and layout constraints using a declarative rule language;
[0026] The incremental update module is used to respond to the event stream of the data processing engine, locate the local subgraph affected by the change based on the stable IDs assigned to nodes and edges, and perform incremental topology updates on the local subgraph.
[0027] The local layout constraint module is used to apply stability constraints that maintain geometric continuity to the affected local subgraphs and to rearrange them to update the overall architecture graph.
[0028] Furthermore, in the data-driven IT architecture diagram generation device, the incremental update module "performs incremental topology updates on the local subgraph" specifically includes:
[0029] Receive event streams from the data processing engine and extract configuration items and relationship change information;
[0030] Compare the current topology with the event data to generate node difference sets and edge difference sets;
[0031] Based on the stable ID, the affected local subgraph is located, and topology merging and deduplication operations are performed on the difference set.
[0032] Furthermore, in the data-driven IT architecture diagram generation device, after the incremental update module performs "topology merging and deduplication operation on the difference set", it also performs: triggering the rearrangement of the affected local subgraphs; and merging the updated subgraphs with the original topology diagram.
[0033] Furthermore, the data-driven IT architecture diagram generation device also includes a two-way verification and correction module, used for:
[0034] The bidirectional differences between the current architecture diagram and the target state defined by the unified data model are classified to obtain inconsistency types including missing, conflicting, or redundant.
[0035] The credibility of the inconsistency type is evaluated based on the declarative rule language.
[0036] The results of the credibility assessment trigger preset corrective actions, including data write-back or approval flow records;
[0037] The corrective actions and results are recorded in the audit log.
[0038] Furthermore, in the data-driven IT architecture diagram generation device, the data standardization module "standardizes IT configuration and architecture data from several heterogeneous data sources into a set of configuration items and relationships based on the unified data model," specifically includes:
[0039] It can access heterogeneous data sources, including CMDB, Excel, and Visio.
[0040] The heterogeneous data source data is parsed, cleaned, field aligned, entity extracted, and relation inferred.
[0041] The processed data is transformed into a set of configuration items and relationships based on a unified data model.
[0042] Compared with existing technologies, the method proposed in this invention can achieve real-time bidirectional synchronization of data and graphics, support high-performance incremental updates and stable layouts, and possess automated consistency verification and correction capabilities. Achievable technical indicators include: Rendering and update efficiency: During large-scale topology updates, rendering latency is reduced by ≥50%, and overall image jitter is reduced by ≥70%; Accuracy: The consistency defect detection rate is improved by ≥30%, and the false alarm rate is reduced by ≥20%; Traceability: Change location time is shortened by ≥40%, and compliance audit costs are reduced by ≥30%. Attached Figure Description
[0043] Figure 1 is a flowchart of the data-driven IT architecture diagram generation method of the present invention;
[0044] Figure 2 is a structural diagram of the data-driven IT architecture diagram generation device of the present invention.
[0045] Explanation of reference numerals in the attached figures:
[0046] 1-Data Standardization Module;
[0047] 2-Relationship Template Binding Module;
[0048] 3-Incremental update module;
[0049] 4-Local layout constraint module;
[0050] 5- Bidirectional verification and correction module. Detailed Implementation
[0051] To explain in detail the technical content, structural features, objectives, and effects of the technical solution, the following description is provided in conjunction with specific embodiments and accompanying drawings.
[0052] Please refer to Figure 1, which is a flowchart of a data-driven IT architecture diagram generation method according to the present invention. The method includes the following steps:
[0053] S1. Data Standardization: Constructing a unified data model to standardize IT configuration and architecture data from several heterogeneous data sources into a set of configuration items and relationships based on the unified data model; specifically including:
[0054] S11. Access heterogeneous data sources including CMDB, Excel, and Visio;
[0055] S12. Perform parsing, cleaning, field alignment, entity extraction and relation inference processing on the heterogeneous data source data;
[0056] S13. Convert the processed data into a set of configuration items and relationships based on a unified data model.
[0057] S2. Relationship Template Binding: A declarative rule language is used to define the mapping relationship between configuration item types and relationship definitions, visual coding rules, and layout constraints.
[0058] S3. Event-Driven Incremental Update: Responding to the event stream of the data processing engine, based on the stable IDs assigned to nodes and edges, the local subgraph affected by the change is located, and incremental topology updates are performed on the local subgraph. Specifically, this includes:
[0059] S31. Receive the event stream from the data processing engine and extract configuration items and relationship change information;
[0060] S32. Compare the current topology graph with the event data to generate node difference sets and edge difference sets;
[0061] S33. Based on the stable ID, locate the affected local subgraph and perform topology merging and deduplication operations on the difference set;
[0062] S4. Local Layout and Stability Constraints: Apply stability constraints that maintain geometric continuity to the affected local subgraphs located in S33 and rearrange them; then merge the updated subgraphs with the original topology graph to update the overall architecture graph.
[0063] The process ends if no verification is required; otherwise, proceed to step S5.
[0064] S5. Two-way verification and correction: After the overall architecture diagram is updated, the two-way differences between the current architecture diagram and the target state defined by the unified data model are classified to obtain inconsistency types including missing, conflicting, or redundant; the credibility of the inconsistency types is evaluated based on the declarative rule language; the result of the credibility evaluation triggers a preset correction operation, including data write-back or approval flow recording; the correction operation and the result are recorded in the audit log, and the process ends here.
[0065] In a specific case, step S1 might involve: a pluggable data integration engine accessing heterogeneous data sources from CMDB, Excel spreadsheets, and Visio drawings. CMDB data is extracted directly via an API interface; the Excel files undergo table structure parsing; and the Visio files are processed for graphic element recognition and metadata extraction. Next, data cleaning (removing duplicate records and filling in missing fields) and field alignment (unifying different naming fields such as "IP address" and "ip_address" to "host_ip") are performed. Entity information is extracted from unstructured descriptions using a pre-trained entity recognition model, and relationships between configuration items are inferred based on connection relationships and dependency analysis. Finally, all processed data is converted into a set of configuration items and relationships based on a unified data model, where each configuration item is assigned a standard type identifier such as "server," "router," or "database."
[0066] In a specific case, step S3 might involve the data processing engine detecting an application server scaling event (adding a new server instance Srv-Node-5) in the CMDB and immediately generating an event stream containing details of that configuration item. Upon receiving the event, the system extracts Srv-Node-5 and its connection to the load balancer LB-1 as change information. By comparing the current topology snapshot, it generates a node difference set ΔV={Add: Srv-Node-5} and an edge difference set ΔE={Add: (LB-1 →Srv-Node-5)}. Based on the stable UUIDs assigned to all nodes, it locates the affected load balancing cluster subgraph (containing LB-1 and all its connected server nodes). The newly added node and edges are then merged with this subgraph, and hash verification is used to avoid duplicate additions.
[0067] In a specific case, step S4 might involve the following: After the incremental topology update is complete, the layout engine only initiates a re-layout for the affected load balancing cluster subgraph. When using the force-directed algorithm for local computation, anchor constraints are applied to the existing nodes Srv-Node-1 to Srv-Node-4 to limit their movement range; a gravity constraint is set on the newly added node Srv-Node-5 to make it move closer to the geometric center of the cluster. These stability constraints effectively maintain the overall shape of the subgraph, causing only smooth position adjustments when inserting new nodes, avoiding drastic changes to the entire topology. After the layout is complete, the updated subgraph is merged with the original topology to generate a new architecture diagram version.
[0068] Step S5, as an optional enhancement process, might in a specific case be as follows: After the architecture diagram is updated, the consistency checker detects a configuration conflict between a firewall rule connection in the diagram and the access control list in the CMDB (the inconsistency type is marked as "conflict"). Based on the security policy rules defined by the declarative rule language, the system assesses the risk confidence of this conflict as 0.9 (high risk). A semi-automatic correction process is triggered based on the assessment result: a change request form is generated, requiring approval from the security administrator. After administrator confirmation, the system writes the corrected configuration back to the CMDB and records the entire correction operation (including the difference content, assessment results, approver, and write-back data) completely in the audit log, forming a closed-loop management system.
[0069] Please refer to Figure 2, which is a structural diagram of a data-driven IT architecture diagram generation device according to an embodiment of the present invention. The data-driven IT architecture diagram generation device includes:
[0070] Data standardization module 1 is used to construct a unified data model and standardize IT configuration and architecture data from several heterogeneous data sources into a set of configuration items and relationships based on the unified data model. Specifically, it includes: accessing heterogeneous data sources including CMDB, Excel, and Visio; performing parsing, cleaning, field alignment, entity extraction, and relationship inference processing on the heterogeneous data source data; and converting the processed data into a set of configuration items and relationships based on the unified data model.
[0071] Relationship template binding module 2 is used to define the mapping relationship between configuration item types and relationship definitions, visual coding rules and layout constraints using a declarative rule language;
[0072] Incremental update module 3 is used to respond to the event stream of the data processing engine, locate the affected local subgraph based on the stable IDs assigned to nodes and edges, and perform incremental topology updates on the local subgraph. Specifically, the incremental update module 3's "incremental topology updates on the local subgraph" includes: receiving the event stream from the data processing engine and extracting configuration items and relationship change information; comparing the current topology graph with the event data to generate node difference sets and edge difference sets; locating the affected local subgraph based on the stable IDs, and performing topology merging and deduplication operations on the difference sets.
[0073] After the incremental update module 3 performs the "topology merging and deduplication operation on the difference set", it also performs the following: triggering the rearrangement of the affected local subgraphs; and merging the updated subgraphs with the original topology graph.
[0074] The local layout constraint module 4 is used to apply stability constraints that maintain geometric continuity to the affected local subgraphs and to rearrange them to update the overall architecture graph.
[0075] Furthermore, in some embodiments, the data-driven IT architecture diagram generation device further includes a two-way verification and correction module 5, used to: classify the two-way differences between the current architecture diagram and the target state defined by the unified data model to obtain inconsistency types including missing, conflicting, or redundant types; perform a credibility assessment on the inconsistency types based on the declarative rule language; trigger a preset correction operation based on the result of the credibility assessment, including data write-back or approval flow recording; and record the correction operation and the result to the audit log.
[0076] Compared with existing technologies, the method proposed in this invention can achieve real-time bidirectional synchronization of data and graphics, support high-performance incremental updates and stable layouts, and possess automated consistency verification and correction capabilities. Achievable technical indicators include: Rendering and update efficiency: During large-scale topology updates, rendering latency is reduced by ≥50%, and overall image jitter is reduced by ≥70%; Accuracy: The consistency defect detection rate is improved by ≥30%, and the false alarm rate is reduced by ≥20%; Traceability: Change location time is shortened by ≥40%, and compliance audit costs are reduced by ≥30%.
[0077] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or terminal device that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or terminal device. Unless otherwise specified, an element defined by the phrase "comprising..." or "including..." does not exclude the presence of additional elements in the process, method, article, or terminal device that includes said element. Additionally, in this document, "greater than," "less than," "exceeding," etc., are understood to exclude the stated number; "above," "below," "within," etc., are understood to include the stated number.
[0078] Those skilled in the art will understand that the above embodiments can be provided as methods, apparatus, or computer program products. These embodiments may take the form of entirely hardware embodiments, entirely software embodiments, or embodiments combining software and hardware aspects. All or part of the steps in the methods involved in the above embodiments can be implemented by a program instructing related hardware, and the program can be stored in a computer-readable storage medium for executing all or part of the steps described in the methods of the above embodiments. The computer device includes, but is not limited to: personal computers, servers, general-purpose computers, special-purpose computers, network devices, embedded devices, programmable devices, smart mobile terminals, smart home devices, wearable smart devices, in-vehicle smart devices, etc.; the storage medium includes, but is not limited to: RAM, ROM, magnetic disks, magnetic tapes, optical disks, flash memory, USB flash drives, portable hard drives, memory cards, memory sticks, network server storage, network cloud storage, etc.
[0079] The above embodiments are described with reference to flowchart illustrations and / or block diagrams of the methods, apparatus (systems), and computer program products according to the embodiments. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a computer device to produce a machine, such that the instructions, which execute through the processor of the computer device, create means for implementing the functions specified in one or more flowchart illustrations and / or one or more block diagrams.
[0080] These computer program instructions may also be stored in a computer device readable storage medium that can direct a computer device to function in a particular manner, such that the instructions stored in the computer device readable storage medium produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more block diagrams.
[0081] These computer program instructions may also be loaded onto a computer device to cause a series of operational steps to be performed on the computer device to produce a computer-implemented process, such that the instructions, which execute on the computer device, provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.
[0082] Although the above embodiments have been described, those skilled in the art, once they understand the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the above descriptions are merely embodiments of the present invention and do not limit the scope of patent protection of the present invention. Any equivalent structural or procedural transformations made using the content of the present invention's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the scope of patent protection of the present invention.
Claims
1. A data-driven method for generating IT architecture diagrams, characterized in that, The steps include: constructing a unified data model to standardize IT configuration and architecture data from several heterogeneous data sources into a set of configuration items and relationships based on the unified data model; A declarative rule language is used to define the mapping relationship between configuration item types and relation definitions, visual encoding rules and layout constraints; in response to the event stream of the data processing engine, based on the stable IDs assigned to nodes and edges, the local subgraph affected by the change is located and the local subgraph is incrementally updated; stability constraints that maintain geometric continuity are imposed on the affected local subgraph and the layout is rearranged to update the overall architecture graph.
2. The data-driven IT architecture diagram generation method as described in claim 1, characterized in that, The "incremental topology update of the local subgraph" specifically includes: receiving an event stream from the data processing engine and extracting configuration items and relationship change information; comparing the current topology graph with the event data to generate a node difference set and an edge difference set; locating the affected local subgraph based on the stable ID and performing topology merging and deduplication operations on the difference set.
3. The data-driven IT architecture diagram generation method as described in claim 2, characterized in that, The steps following "perform topology merging and deduplication on the difference set" also include: triggering a re-layout of the affected local subgraphs; and merging the updated subgraphs with the original topology graph.
4. The data-driven IT architecture diagram generation method as described in claim 1, characterized in that, After the step "incremental topology update of the local subgraph", the method further includes the following steps: classifying the bidirectional differences between the current architecture graph and the target state defined by the unified data model to obtain inconsistency types including missing, conflicting, or redundant; and evaluating the credibility of the inconsistency types based on the declarative rule language. The results of the credibility assessment trigger preset corrective actions, including data write-back or approval flow records; The corrective actions and results are recorded in the audit log.
5. The data-driven IT architecture diagram generation method as described in claim 1, characterized in that, The step "standardizing IT configuration and architecture data from several heterogeneous data sources into a set of configuration items and relationships based on the unified data model" specifically includes: accessing heterogeneous data sources including CMDB, Excel, and Visio; performing parsing, cleaning, field alignment, entity extraction, and relationship inference processing on the heterogeneous data source data; and converting the processed data into a set of configuration items and relationships based on the unified data model.
6. A data-driven IT architecture diagram generation device, characterized in that, include: The data standardization module is used to build a unified data model and standardize IT configuration and architecture data from several heterogeneous data sources into a set of configuration items and relationships based on the unified data model. The relation template binding module is used to define the mapping relationship between configuration item types and relation definitions, visual coding rules and layout constraints using a declarative rule language; The incremental update module is used to respond to the event stream of the data processing engine, locate the local subgraph affected by the change based on the stable IDs assigned to nodes and edges, and perform incremental topology updates on the local subgraph; the local layout constraint module is used to apply stability constraints that maintain geometric continuity to the affected local subgraph and rearrange it to update the overall architecture graph.
7. The data-driven IT architecture diagram generation apparatus as described in claim 6, characterized in that, The incremental update module "performs incremental topology updates on the local subgraph" specifically includes: receiving an event stream from the data processing engine and extracting configuration items and relationship change information; comparing the current topology graph with the event data and generating node difference sets and edge difference sets; locating the affected local subgraph based on the stable ID and performing topology merging and deduplication operations on the difference sets.
8. The data-driven IT architecture diagram generation apparatus as described in claim 7, characterized in that, After the incremental update module performs "topology merging and deduplication operations on the difference set", it also performs the following: triggering a rearrangement of the affected local subgraphs; and merging the updated subgraphs with the original topology graph.
9. The data-driven IT architecture diagram generation apparatus as described in claim 6, characterized in that, It also includes a two-way verification and correction module, used to: classify the two-way differences between the current architecture diagram and the target state defined by the unified data model to obtain inconsistency types including missing, conflicting, or redundant; and evaluate the credibility of the inconsistency types based on the declarative rule language. The results of the credibility assessment trigger preset corrective actions, including data write-back or approval flow records; The corrective actions and results are recorded in the audit log.
10. The data-driven IT architecture diagram generation apparatus as described in claim 6, characterized in that, The data standardization module, which "standardizes IT configuration and architecture data from several heterogeneous data sources into a set of configuration items and relationships based on the unified data model," specifically includes: accessing heterogeneous data sources including CMDB, Excel, and Visio; performing parsing, cleaning, field alignment, entity extraction, and relationship inference processing on the heterogeneous data source data; and converting the processed data into a set of configuration items and relationships based on the unified data model.