Branch network topology intelligent construction method, device, equipment and storage medium

By acquiring network topology layout information and device hierarchy mapping tables, combining data center-level and zone-level layouts, and performing hierarchy reallocation when layout anomalies occur, the problem of discrepancies between the topology diagram and the actual network architecture in existing technologies is solved, achieving efficient and accurate topology layout generation.

CN123123181APending Publication Date: 2026-11-17CHINA MERCHANTS BANK
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611458270.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-09-18
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

Existing technologies struggle to automatically generate a complete and accurate topology layout that matches the actual network architecture of branch offices, resulting in discrepancies between the topology diagram and the actual network architecture, insufficient layout completeness, and low operational efficiency.

Method used

By acquiring network topology layout information, device hierarchy mapping table, and data center physical space attributes, data center-level and zone-level layouts are performed. When layout anomalies are detected, hierarchical reallocation is performed based on the device hierarchy mapping table to generate a topology layout that conforms to the actual network architecture of the branch office.

Benefits of technology

It enables the automatic generation of a complete and accurate topology layout that conforms to the actual network architecture of branch offices, improving the efficiency of topology construction and reducing manual maintenance costs.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123123181A_ABST
    Figure CN123123181A_ABST
Patent Text Reader

Abstract

This application discloses a method, apparatus, device, and storage medium for intelligent construction of branch network topology, relating to the field of network topology management technology. The method includes: acquiring network topology layout information, device hierarchy mapping table, and physical space attributes of the computer room for the target organization; the layout information characterizes the arrangement relationship of computer room nodes and the arrangement relationship of partitions within the computer room; aggregating devices according to physical space attributes to generate computer room nodes and edge relationships; performing computer room-level layout based on the node and edge relationships and the layout information; determining network partitions within each computer room based on the computer room-level layout results; hierarchically laying out devices within each network partition to obtain a partition-level topology layout result containing multiple network partitions; and when an abnormal layout is detected in the partition-level layout result, hierarchically reallocating the abnormal device nodes based on the device hierarchy mapping table to obtain the target topology layout. This application can automatically generate a complete and accurate topology layout that conforms to the actual architecture.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of network topology management technology, and in particular to a method, apparatus, device and storage medium for intelligent construction of branch network topology. Background Technology

[0002] As branch office networks continue to expand, branch office network topology management requires generating topology maps that reflect the actual network architecture hierarchy. This allows operations and maintenance personnel to intuitively determine the location and hierarchical relationship of devices, quickly locate faults, and improve operational efficiency.

[0003] Currently, branch network topology construction typically employs either the head office backbone network topology algorithm, manual drag-and-drop, manual customization, or a general graph layout algorithm. The head office backbone network topology algorithm, based on a preset device hierarchy, is difficult to adapt to branch network environments with different topology levels. Manual drag-and-drop requires maintenance personnel to complete the layout node by node, which is time-consuming and increases maintenance costs as the number of devices grows. Manual customization requires designing layout algorithms for different branches, resulting in high manpower costs and poor reusability. While general graph layout algorithms can automatically lay out the network, they cannot recognize business semantics such as partitioning and layering, and the generated topology map lacks the hierarchical structure of the actual network architecture. Furthermore, incomplete collection of branch device connection relationships leads to many devices being treated as isolated nodes in the topology, further contributing to insufficient layout integrity.

[0004] Therefore, how to automatically generate a complete and accurate topology layout that conforms to the actual network architecture of branch offices is a problem that urgently needs to be solved.

[0005] The above content is only used to help understand the technical solution of this application and does not represent an admission that the above content is prior art. Summary of the Invention

[0006] The main objective of this application is to provide a method, apparatus, device, and storage medium for intelligent construction of branch network topology, aiming to solve the technical problems corresponding to the background technology.

[0007] To achieve the above objectives, this application proposes a method for intelligent construction of branch network topology, the method comprising: Obtain the network topology layout information, device hierarchy mapping table, and physical space attributes of the computer room of the target organization. The network topology layout information represents the arrangement relationship between computer room nodes and the partition arrangement relationship within the computer room. Based on the physical space attributes of the data center, the devices are aggregated to generate data center nodes and edge relationships, and based on the data center nodes and edge relationships, a data center-level topology layout is performed according to the network topology layout information; Based on the data center-level topology layout results, network partitions within each data center are determined according to the network topology layout information, and devices within each network partition are arranged in a hierarchical manner to obtain a partition-level topology layout result containing multiple network partitions. If an anomaly is detected in the partition-level topology layout result, the device nodes corresponding to the anomaly are hierarchically reassigned based on the device hierarchy mapping table to obtain the target network topology layout.

[0008] In one embodiment, the step of hierarchically reassigning device nodes corresponding to layout anomalies based on the device hierarchy mapping table to obtain the target network topology layout includes: Determine the layout anomaly type, which includes at least one of the following: no entry device in the network partition, isolated device with missing device connection relationship in the network partition, and all devices in the network partition are located at the same level. Based on the layout anomaly type, the device nodes corresponding to the layout anomaly are hierarchically reassigned according to the device hierarchy mapping table to obtain the target network topology layout.

[0009] In one embodiment, the step of hierarchically reallocating the device nodes corresponding to the layout anomaly based on the device hierarchy mapping table includes: When the layout anomaly type is that there is no entry device in the network partition, all device nodes in the network partition are reallocated to the corresponding level based on the device level mapping table; When the layout anomaly type is an isolated device with missing device connection relationships within a network partition, the isolated device is added to the corresponding level of the current layout based on the device hierarchy mapping table; When the layout anomaly type is that all devices in the network partition are at the same level, all device nodes in the network partition are reallocated to the corresponding level based on the device level mapping table.

[0010] In one embodiment, before obtaining the network topology layout information, device hierarchy mapping table, and physical space attributes of the computer room of the target organization, the method further includes: Obtain the network device architecture diagram and network topology diagram of the target organization; The network device architecture diagram is used to identify data center nodes, and the areas containing data center identifiers are identified as data center nodes; The network device architecture diagram is partitioned and the regions containing partition identifiers are identified as partition nodes. Based on the arrangement relationships between the data center nodes, the partition nodes, the data center nodes, and the partition arrangement relationships within the data center, network topology layout information is generated. The network topology is parsed to extract device types, device role information, and vertical layout characteristics within partitions, and a device hierarchy mapping table is generated.

[0011] In one embodiment, the method further includes: A confidence level assessment is performed on the results of the data center node identification and the results of the partition node identification; The confidence level of the network topology graph parsing results is evaluated. If the confidence level of the data center node identification, the partition node identification, or the network topology map resolution is lower than a set threshold, the data center node identification, the partition node identification, or the network topology map resolution shall be re-executed.

[0012] In one embodiment, the step of aggregating devices to generate data center nodes and edge relationships based on the physical space attributes of the data center, and performing data center-level topology layout based on the network topology layout information according to the data center nodes and edge relationships, includes: Obtain the equipment list of the target organization; The equipment in the equipment list is aggregated according to the physical space attributes of the computer room to generate a set of computer room nodes and the edge relationships between the computer room nodes; Based on the arrangement relationship between data center nodes represented in the network topology layout information, a data center-level topology layout is performed on the data center nodes and edge relationships.

[0013] In one embodiment, the step of determining network partitions within each data center based on the data center-level topology layout results, and hierarchically arranging the devices within each network partition to obtain a partition-level topology layout result containing multiple network partitions, includes: Based on the data center-level topology layout results, the network partitions within each data center are determined according to the partition arrangement relationship within the data center represented in the network topology layout information. For each network partition, obtain the device connection relationship, and analyze the ingress and egress devices within the network partition based on the device connection relationship; The hierarchical relationship between devices within the network partition is determined based on the ingress device and the egress device. Based on the hierarchical relationship, the devices within each network partition are arranged in a hierarchical manner to obtain a partition-level topology layout result containing multiple network partitions.

[0014] Furthermore, to achieve the above objectives, this application also proposes a branch office network topology intelligent construction device, which includes: The information acquisition module is used to acquire the network topology layout information, device hierarchy mapping table and physical space attributes of the target organization. The network topology layout information represents the arrangement relationship between nodes in the computer room and the partition arrangement relationship within the computer room. The data center-level layout module is used to aggregate devices to generate data center nodes and edge relationships based on the physical space attributes of the data center, and to perform data center-level topology layout based on the data center nodes and edge relationships and the network topology layout information. The partition-level layout module is used to determine the network partitions in each data center based on the data center-level topology layout results and the network topology layout information, and to perform hierarchical layout of the devices in each network partition to obtain a partition-level topology layout result containing multiple network partitions. The abnormal reassignment module is used to perform hierarchical reassignment of the device nodes corresponding to the abnormal layout based on the device hierarchical mapping table when an abnormal layout is detected in the partition-level topology layout result, so as to obtain the target network topology layout.

[0015] In addition, to achieve the above objectives, this application also proposes a branch network topology intelligent construction device, the device comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the branch network topology intelligent construction method as described above.

[0016] In addition, to achieve the above objectives, this application also proposes a storage medium, which is a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, it implements the steps of the branch network topology intelligent construction method described above.

[0017] In addition, to achieve the above objectives, this application also provides a computer program product, which includes a computer program that, when executed by a processor, implements the steps of the branch network topology intelligent construction method described above.

[0018] This application provides a method for intelligently constructing a branch network topology. First, it acquires the target organization's network topology layout information, device hierarchy mapping table, and the physical space attributes of the computer room. Based on the computer room's physical space attributes, it aggregates devices to generate computer room nodes and edge relationships. Then, based on these computer room nodes and edge relationships, it performs a computer room-level topology layout according to the network topology layout information to automatically generate a topology layout conforming to the computer room-level architecture hierarchy. Next, based on the computer room-level topology layout result, it determines network partitions within each computer room according to the network topology layout information and performs hierarchical layout of devices within each network partition, obtaining a partition-level topology layout result containing multiple network partitions, to automatically generate a topology layout conforming to the partition-level architecture hierarchy. If a layout anomaly is detected in the partition-level topology layout result, it performs hierarchical reallocation of the device nodes corresponding to the layout anomaly based on the device hierarchy mapping table to obtain the target network topology layout, thereby correcting the device hierarchy when layout anomalies occur and ensuring the integrity and hierarchical accuracy of the topology layout.

[0019] In summary, this application overcomes the technical shortcomings of existing technologies by combining data center-level topology layout, partition-level topology layout, and hierarchical reallocation based on device-level mapping tables during anomalies. These shortcomings include the inability of existing technologies to ensure that the topology diagram conforms to the actual network architecture hierarchy and that the integrity of the layout is difficult to guarantee. Since the data center-level topology layout, partition-level topology layout, and hierarchical reallocation during anomalies are all executed automatically by the system, eliminating the need for manual node-by-node dragging or customized development for different branch offices, this not only improves topology construction efficiency but also reduces manual maintenance costs, achieving a complete and accurate topology layout that conforms to the actual network architecture hierarchy of the branch office. Attached Figure Description

[0020] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0021] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0022] Figure 1 This is a flowchart illustrating an embodiment of the intelligent construction method for branch network topology in this application. Figure 2 This is a flowchart illustrating Embodiment 2 of the intelligent construction method for branch network topology in this application. Figure 3 This is a schematic diagram illustrating the overall process of the intelligent construction method for branch network topology in this application; Figure 4This is a schematic diagram of the module structure of the intelligent branch network topology construction device according to an embodiment of this application; Figure 5 This is a schematic diagram of the device structure of the hardware operating environment involved in the intelligent construction method of branch network topology in this application embodiment.

[0023] The purpose, features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0024] It should be understood that the specific embodiments described herein are merely illustrative of the technical solutions of this application and are not intended to limit this application.

[0025] To better understand the technical solution of this application, a detailed description will be provided below in conjunction with the accompanying drawings and specific implementation methods.

[0026] The main solution of this application embodiment is as follows: Obtain the network topology layout information, device hierarchy mapping table, and physical space attributes of the target organization. The network topology layout information represents the arrangement relationship between nodes in the data center and the partition arrangement relationship within the data center. Based on the physical space attributes of the data center, aggregate the devices to generate data center nodes and edge relationships. Based on the data center nodes and edge relationships, perform a data center-level topology layout according to the network topology layout information. Based on the data center-level topology layout result, determine the network partitions within each data center according to the network topology layout information, and perform hierarchical layout of the devices within each network partition to obtain a partition-level topology layout result containing multiple network partitions. If a layout anomaly is detected in the partition-level topology layout result, perform hierarchical reallocation of the device nodes corresponding to the layout anomaly based on the device hierarchy mapping table to obtain the target network topology layout.

[0027] Currently, branch network topology construction typically employs methods such as the head office backbone network topology algorithm, manual drag-and-drop, manual customization, or general graph layout algorithms. The head office backbone network topology algorithm, based on a preset device hierarchy, is difficult to adapt to branch network environments with different topology levels. Manual drag-and-drop requires maintenance personnel to complete the layout node by node, which is time-consuming and increases maintenance costs as the number of devices grows. Manual customization requires designing layout algorithms for different branches, resulting in high manpower costs and poor reusability. While general graph layout algorithms can automatically lay out the network, they cannot recognize business semantics such as partitioning and layering, and the generated topology lacks the hierarchical structure of the actual network architecture. Furthermore, incomplete collection of branch device connection relationships leads to many devices being treated as isolated nodes, further complicating the layout integrity. Therefore, how to automatically generate a complete and accurate topology layout that conforms to the actual network architecture hierarchy of branch offices is a problem that urgently needs to be solved.

[0028] In summary, this application overcomes the technical shortcomings of existing technologies that cannot make the topology map conform to the actual network architecture hierarchy and whose layout integrity is difficult to guarantee by combining data center-level topology layout, partition-level topology layout, and hierarchical reallocation based on device-level mapping table in case of anomalies. It achieves a complete and accurate topology layout that conforms to the actual network architecture hierarchy of branch offices, improves topology construction efficiency, and reduces manual maintenance costs.

[0029] It should be noted that the executing entity in this embodiment can be a branch network topology intelligent construction system, or a computing service device with data processing, network communication, and program execution functions, such as a tablet computer, personal computer, or mobile phone. This embodiment does not specifically limit this. The following description uses a branch network topology intelligent construction system as the executing entity to illustrate this embodiment and the subsequent embodiments. All actions involving the acquisition of signals, information, or data in this application are performed in accordance with the relevant local data protection regulations and with authorization from the owner of the corresponding device.

[0030] Based on this, embodiments of this application provide a method for intelligent construction of branch network topology, referring to... Figure 1 , Figure 1 This is a flowchart illustrating the first embodiment of the intelligent construction method for branch network topology in this application.

[0031] In this embodiment, the intelligent construction method for branch network topology includes steps S10 to S40: It should be noted that this embodiment is applied to the intelligent construction of branch network topology. Currently, in the process of constructing branch network topology, manual drag-and-drop or general layout algorithms are usually used, which can easily lead to problems such as the topology map not matching the actual network architecture and insufficient layout completeness. That is, when the device connection relationship is not fully collected, a large number of devices are regarded as isolated nodes, making it difficult for the generated topology map to reflect the actual network hierarchy, and making it difficult for maintenance personnel to quickly locate faults. Therefore, this embodiment obtains network topology layout information, device hierarchy mapping table and physical space attributes of the data center, and performs two-level layout at the data center level and the zone level. When layout anomalies are detected, the abnormal device nodes are reassigned hierarchically based on the device hierarchy mapping table. This avoids the problem of layout quality degradation caused by incomplete collection of device connection relationships, thereby realizing the automatic generation of a complete and accurate topology layout that conforms to the actual network architecture hierarchy of the branch.

[0032] Step S10: Obtain the network topology layout information, device hierarchy mapping table, and physical space attributes of the computer room of the target organization. The network topology layout information represents the arrangement relationship between computer room nodes and the partition arrangement relationship within the computer room. It should be noted that the target organization can refer to a branch office that requires network topology construction, such as a bank branch or corporate branch. Network topology layout information refers to the information used to guide the arrangement of nodes in the topology diagram, which can include the arrangement relationships between data center nodes and the arrangement relationships between partitions within a data center. The arrangement relationships between data center nodes can refer to the relative positions of multiple data center nodes in the topology diagram, for example, data center A is located to the left of data center B. The arrangement relationships between partitions within a data center can refer to the relative positions of various network partitions within a data center, for example, the production area is located above the office area. The device hierarchy mapping table can refer to the correspondence between device types and hierarchies, for example, firewalls correspond to the first level, routers to the second level, switches to the third level, etc. The physical space attributes of the data center can refer to the data center information to which the device belongs in the physical space, such as the data center number and location of the data center.

[0033] Additionally, it should be noted that network topology layout information and device hierarchy mapping tables can be obtained by parsing network device architecture diagrams and network topology diagrams, or they can be obtained from a knowledge base. This embodiment does not limit this.

[0034] Understandably, since obtaining network topology layout information, device hierarchy mapping tables, and the physical space attributes of the data center provides a basis for subsequent automatic data center-level and zone-level layout, step S10 avoids the inefficiencies and high costs associated with manual drag-and-drop or customized development in related technologies, thereby improving the automation and efficiency of topology construction. Unlike the head office backbone network topology algorithm, which cannot adapt to the branch office network environment, this step obtains layout information and hierarchy mapping tables specifically tailored to the characteristics of branch office networks, laying the foundation for generating a topology diagram that conforms to the actual network architecture hierarchy of the branch office.

[0035] Step S20: Based on the physical space attributes of the computer room, aggregate the devices to generate computer room nodes and edge relationships, and based on the computer room nodes and edge relationships, perform computer room-level topology layout according to the network topology layout information; It should be noted that the physical space attributes of a data center can refer to the data center information to which a device belongs in the physical space, such as the data center number or location of the data center to which the device belongs. Aggregating devices to form data center nodes means grouping devices within the same data center together to form a data center node. Edge relationships refer to the connection relationships between data center nodes; for example, an edge is generated if there is a physical link between two data centers. Data center-level topology layout refers to determining the position of each data center node in the topology graph based on the arrangement relationships between data center nodes represented in the network topology layout information.

[0036] Additionally, it should be noted that device aggregation can be based on the device list managed by the target organization, which can be obtained from the network management system or configuration management database.

[0037] Understandably, since step S20 aggregates devices based on the physical space attributes of the data center to generate data center nodes and edge relationships, and then performs data center-level topology layout accordingly, it avoids the problem that general graph layout algorithms in related technologies cannot recognize business semantics such as partitioning and layering, thereby improving the accuracy and automatic generation capability of data center-level topology layout. Unlike manual drag-and-drop or manual customization development, this step automatically aggregates data center nodes based on physical space attributes, making the generated data center-level topology structure more closely match the actual network architecture of the branch office, thus realizing the automatic generation of data center-level topology layout.

[0038] In one feasible implementation, step S20 may include steps A21 to A23: Step A21: Obtain the equipment list of the target organization; It should be noted that the equipment list can refer to a list of all network devices managed by the target organization, which may include information such as device name, device type, and the data center to which the device belongs.

[0039] Additionally, it should be noted that the equipment list can be obtained from the network management system, configuration management database, or asset management system.

[0040] Step A22: Aggregate the devices in the equipment list according to the physical space attributes of the computer room to generate a set of computer room nodes and the edge relationships between the computer room nodes; It should be noted that aggregation based on the physical spatial attributes of the data center can refer to grouping devices belonging to the same data center in the equipment list into the same group, with each group corresponding to a data center node. The set of data center nodes can refer to the collection of all data center nodes. Edge relationships can refer to the connections between data center nodes, which can be generated based on the connections between devices. For example, when there is a connection between devices in two data centers, an edge is generated between the nodes of these two data centers.

[0041] Additionally, it should be noted that edge relationships can also be generated based on pre-stored data center connection information or historical topology data.

[0042] Step A23: Based on the arrangement relationship between the data center nodes represented in the network topology layout information, perform data center-level topology layout for the data center nodes and edge relationships; It should be noted that the arrangement relationship between data center nodes represented in the network topology layout information can refer to the relative position of each data center node in the topology graph, for example, data center A is located to the left of data center B. Data center-level topology layout of data center nodes and edge relationships refers to determining the specific position of each data center node in the topology graph based on this arrangement relationship, while preserving the edge relationships.

[0043] Additionally, it should be noted that if the network topology layout information does not include the arrangement of a certain data center, a default layout strategy can be used, such as arranging them according to the number of data center nodes or their names.

[0044] Understandably, by first obtaining the equipment list and then aggregating it according to physical space attributes, this implementation method avoids the problems of manual drag-and-drop or the inability of general layout algorithms to automatically identify the data center affiliation in related technologies, thereby improving the accuracy and automatic generation capability of the data center-level topology layout. Unlike the head office backbone network topology algorithm, which cannot adapt to the branch office network environment, this implementation method automatically aggregates data center nodes based on physical space attributes, making the data center-level topology layout more closely match the actual network architecture of the branch office.

[0045] Step S30: Based on the data center-level topology layout result, determine the network partitions in each data center according to the network topology layout information, and perform hierarchical layout of the devices in each network partition to obtain a partition-level topology layout result containing multiple network partitions. It should be noted that the data center-level topology layout result can refer to the topology layout including data center nodes and their edge relationships obtained after step S20. Network partitions can refer to logical areas within a data center divided according to business or security requirements, such as production areas, office areas, and DMZ (Demilitarized Zone). Determining network partitions within each data center based on network topology layout information means using the partition arrangement relationships represented in the network topology layout information to determine which network partitions are included in each data center and their relative positions. Hierarchical deployment of devices within each network partition means assigning devices to different levels according to their type or role, such as deploying firewalls at higher levels and switches at lower levels.

[0046] Additionally, it should be noted that when laying out devices in a hierarchical manner within a network partition, the entry and exit devices can be analyzed based on their connection relationships to determine the hierarchical relationship between the devices.

[0047] It is understandable that, since the network partitions in each data center are determined based on the data center-level topology layout results, and the devices in each network partition are arranged in a hierarchical manner according to the network topology layout information, step S30 can realize the automatic generation of partition-level topology layout, so that the topology map contains multiple network partitions and has business semantics, thereby improving the completeness and readability of the topology map.

[0048] In one feasible implementation, step S30 may include steps A31 to A34: Step A31: Based on the data center-level topology layout results, determine the network partitions in each data center according to the partition arrangement relationship represented in the network topology layout information. It should be noted that the layout of network zones within a data center refers to the relative positions of the various network zones within that data center. For example, the production zone might be located above the office zone, and the DMZ zone might be located to the right of the production zone. Based on this relationship, it is possible to determine which network zones each data center contains and their relative positions.

[0049] Additionally, it should be noted that the layout of partitions within the data center can be obtained from the network topology information, which can be obtained by identifying the network device architecture diagram.

[0050] Step A32: For each network partition, obtain the device connection relationship, and analyze the ingress and egress devices within the network partition based on the device connection relationship; It should be noted that device connectivity can be obtained through the LLDP (Link Layer Discovery Protocol) or inferred from network data such as routing tables and ARP (Address Resolution Protocol) tables.

[0051] Additionally, it should be noted that when device connection relationships are missing, hierarchical reallocation can be performed based on the device hierarchy mapping table in subsequent step S40.

[0052] Step A33: Determine the hierarchical relationship between devices within the network partition based on the ingress device and the egress device; It should be noted that when there are multiple inlet or outlet devices, the horizontal arrangement order of the devices within the same level can be determined according to the device type or connection relationship.

[0053] Step A34: Based on the hierarchical relationship, the devices in each network partition are laid out in a hierarchical manner to obtain a partition-level topology layout result containing multiple network partitions; It should be noted that the partition-level topology layout result can contain multiple network partitions, and the devices in each network partition are arranged according to the hierarchical relationship.

[0054] Understandably, this implementation method, by determining network partitions based on the internal layout of the computer room and analyzing entry and exit devices based on device connectivity to determine hierarchical relationships, ensures that the hierarchical layout of devices within a partition aligns with their connectivity, thereby improving the accuracy of the device hierarchy within the partition. Unlike methods that can only generate topology diagrams without a hierarchical structure, this implementation method uses a multi-level layout within the computer room, allowing the generated topology diagram to reflect the actual network partition structure and device hierarchy of the branch office.

[0055] Step S40: If an abnormality is detected in the partition-level topology layout result, the device nodes corresponding to the abnormality are hierarchically reassigned based on the device hierarchy mapping table to obtain the target network topology layout. It should be noted that layout anomalies can refer to situations where the device node hierarchy in the partition-level topology layout result is unreasonable or cannot be determined. Reassigning the device nodes corresponding to layout anomalies involves re-determining the appropriate hierarchy for these device nodes based on the device hierarchy mapping table and adjusting them to the corresponding hierarchy.

[0056] Additionally, it should be noted that the detection of layout anomalies can be performed after the partition-level topology layout is completed, such as checking for node conflicts, overlaps, and whether all devices are arranged on the same layer.

[0057] Understandably, step S40 addresses the issue of incomplete device connection data collection leading to layout anomalies by performing hierarchical reallocation of abnormal device nodes based on the device hierarchy mapping table when layout anomalies are detected. This improves the completeness and hierarchical accuracy of the topology layout. Unlike resolving missing connection data through data completion, this step does not rely on completing connection data but directly performs hierarchical reallocation based on the device hierarchy mapping table. This ensures the completeness and accuracy of the topology layout even with incomplete connection data collection. The resulting target network topology layout can be used for visualization, allowing maintenance personnel to intuitively view the hierarchical arrangement of devices in each data center and network partition, facilitating rapid location of faulty devices.

[0058] In one feasible implementation, step S40 may include steps A41-A42: Step A41: Determine the layout anomaly type, which includes at least one of the following: no entry device in the network partition, isolated devices with missing device connection relationships in the network partition, and devices in the network partition being located at the same level. It should be noted that layout anomaly types can refer to the results of classifying layout anomalies. "No ingress device in network partition" means that no upstream device was found in the partition. "Isolated device with missing connection relationship in network partition" means that there are devices in the partition whose connection relationship cannot be determined because LLDP is not enabled. "All devices in network partition are at the same level" means that all devices in the partition are arranged at the same level.

[0059] Additionally, it should be noted that determining the type of layout anomaly can be achieved by analyzing the connection relationships and hierarchical distribution of devices within the partition.

[0060] Step A42: Based on the layout anomaly type, perform hierarchical reallocation of the device nodes corresponding to the layout anomaly according to the device hierarchy mapping table to obtain the target network topology layout. It should be noted that the type of layout anomaly can determine the device nodes that need to be reassigned. The device hierarchy mapping table can contain the priority mapping relationship between device types and hierarchy, such as firewalls corresponding to the first level, routers to the second level, and switches to the third level, etc.

[0061] It is understandable that by determining the corresponding device nodes and performing hierarchical reallocation for different types of layout anomalies, steps A41 to A42 can solve the problem of incomplete correction caused by using the same correction method uniformly, thereby improving the accuracy of layout anomaly handling and layout integrity.

[0062] In one feasible implementation, the hierarchical reallocation of the device nodes corresponding to the layout anomaly based on the device hierarchy mapping table may include steps A421~A423: Step A421: When the layout anomaly type is that there is no entry device in the network partition, all device nodes in the network partition are reallocated to the corresponding level based on the device level mapping table. It should be noted that reallocation can refer to placing all device nodes in the partition to the correct level according to the correspondence between device type and level indicated by the device level mapping table.

[0063] Additionally, it should be noted that when all device nodes within the partition are reassigned, both the reassignment mechanism and the conflict resolution mechanism can be enabled simultaneously to ensure layout convergence.

[0064] Step A422: When the layout anomaly type is an isolated device with missing device connection relationship in the network partition, the isolated device is added to the corresponding level of the current layout based on the device hierarchy mapping table. It should be noted that "adding" can refer to inserting isolated devices into the corresponding hierarchical positions while maintaining the current layout.

[0065] Step A423: When the layout anomaly type is that all devices in the network partition are at the same level, all device nodes in the network partition are reallocated to the corresponding level based on the device level mapping table. It should be noted that reallocation can refer to placing all device nodes in the partition to the correct level according to the correspondence between device type and level indicated by the device level mapping table.

[0066] Additionally, it should be noted that after performing any of the reassignment steps A421 to A423, the generated result can be reviewed once to check whether the reassignment has introduced new node conflicts or overlaps. If the review fails, the partition will be added to the manual processing list. If the review passes, the reassigned layout result will be used as the target network topology layout.

[0067] This embodiment provides a method for intelligently constructing a branch network topology. First, it acquires the target organization's network topology layout information, device hierarchy mapping table, and the physical space attributes of the computer room. Based on the computer room's physical space attributes, it aggregates devices to generate computer room nodes and edge relationships. Then, based on these relationships, it performs a computer room-level topology layout according to the network topology layout information to automatically generate a topology layout that conforms to the computer room-level architecture hierarchy. Next, based on the computer room-level topology layout result, it determines network partitions within each computer room according to the network topology layout information and performs hierarchical layout of devices within each network partition, obtaining a partition-level topology layout result containing multiple network partitions, to automatically generate a topology layout that conforms to the partition-level architecture hierarchy. If a layout anomaly is detected in the partition-level topology layout result, it performs hierarchical reallocation of the device nodes corresponding to the layout anomaly based on the device hierarchy mapping table to obtain the target network topology layout. This corrects the device hierarchy when layout anomalies occur, ensuring the integrity and hierarchical accuracy of the topology layout.

[0068] In summary, this embodiment overcomes the technical shortcomings of existing technologies that fail to ensure the topology map conforms to the actual network architecture hierarchy and that layout integrity is difficult to guarantee. This is achieved by combining data center-level topology layout, partition-level topology layout, and hierarchical reallocation based on device-level mapping tables during anomalies. Since the data center-level topology layout, partition-level topology layout, and hierarchical reallocation during anomalies are all executed automatically by the system, eliminating the need for manual node-by-node dragging or customized development for different branch offices, it not only improves topology construction efficiency but also reduces manual maintenance costs, achieving a complete and accurate topology layout that conforms to the actual network architecture hierarchy of the branch office.

[0069] Based on the first embodiment of this application, in the second embodiment of this application, the content that is the same as or similar to that in the first embodiment described above can be referred to the above description, and will not be repeated hereafter. Based on this, please refer to... Figure 2 Before step S10, the intelligent construction method for branch network topology further includes steps S01 to S05: It should be noted that this embodiment is applied to the intelligent construction of branch network topology. Currently, in the process of constructing branch network topology, it is usually necessary to manually analyze the network device architecture diagram and the existing topology diagram to extract layout rules. The manual sorting is labor-intensive and inefficient. Therefore, this embodiment automatically identifies and parses the network device architecture diagram and the network topology diagram to generate network topology layout information and device hierarchy mapping table, respectively, so as to reduce the workload of manual sorting and provide a rule basis for the subsequent automatic generation of topology layout.

[0070] Step S01: Obtain the network device architecture diagram and network topology diagram of the target organization; It should be noted that a network equipment architecture diagram can refer to a drawing depicting the physical connections of network equipment in a branch office and the partitioned structure of the data center. It may include data center identifiers, partition identifiers, and the connection relationships between devices. A network topology diagram can refer to a screenshot of an existing topology diagram, which may include device types, device role information, and the vertical layout characteristics of devices within a partition.

[0071] Additionally, it should be noted that network device architecture diagrams and network topology diagrams can be obtained from document management systems, operation and maintenance knowledge bases, or historical topology data.

[0072] Step S02: Identify data center nodes in the network device architecture diagram and identify areas containing data center identifiers as data center nodes; It should be noted that "data center identifier" can refer to the text or graphics used to identify data centers in the network architecture diagram, such as "Data Center A" or "Data Center B". Data center node identification in the network device architecture diagram can be performed using image recognition or text recognition methods to identify the areas containing the data center identifier and designate those areas as data center nodes.

[0073] Step S03: Identify partition nodes in the network device architecture diagram and identify the regions containing partition identifiers as partition nodes; It should be noted that partition identifiers can refer to text or graphics used to identify partitions in the architecture diagram, such as "production area," "office area," or "DMZ area." Partition node identification in network device architecture diagrams can be performed using image recognition or text recognition methods to identify areas containing partition identifiers and designate those areas as partition nodes.

[0074] Step S04: Generate network topology layout information based on the arrangement relationship between the data center nodes, the partition nodes, the data center nodes, and the partition arrangement relationship within the data center; It should be noted that the arrangement of nodes within a data center can refer to the relative positions of multiple data center nodes in the architecture diagram, such as data center A being located to the left of data center B. The arrangement of partitions within a data center can refer to the relative positions of various network partitions within a data center, such as the production area being located above the office area. Both the arrangement of nodes and the arrangement of partitions within a data center can be determined by identifying the connections or relative positions of nodes in the architecture diagram.

[0075] Additionally, it should be noted that network topology layout information can be stored in the form of structured data, such as node coordinates or relative positional relationships.

[0076] Step S05: parse the network topology diagram, extract device type, device role information and vertical layout characteristics within the partition, and generate a device hierarchy mapping table; It should be noted that device type can refer to firewalls, switches, routers, etc. Device role information can refer to the role that the device plays in the network, such as core switch, aggregation switch, access switch, etc. The hierarchical layout characteristics within a partition can refer to the hierarchical arrangement of devices within a partition, such as firewalls being located at the upper layer and switches at the lower layer.

[0077] In one feasible implementation, after partition node identification and network topology graph parsing, the steps may include: evaluating the confidence level of the results of data center node identification and partition node identification; evaluating the confidence level of the results of network topology graph parsing; and re-executing the data center node identification, partition node identification, or network topology graph parsing if the confidence level of the data center node identification, partition node identification, or network topology graph parsing is lower than a set threshold.

[0078] It should be noted that confidence assessment refers to scoring the reliability of the identification or parsing results. A threshold can be set according to actual needs, such as 0.6. Re-execution can refer to performing the identification or parsing again to obtain more reliable results.

[0079] Additionally, it should be noted that after re-executing the identification or parsing, the confidence level can be reassessed until it is not lower than the set threshold. Preferably, identification or parsing results with a confidence level lower than the set threshold can also be marked as requiring manual confirmation, and corrected by the administrator after manual review. Manual review can be used as a supplement to automatic re-executing of identification or parsing when reliable results still cannot be obtained by automatic re-executing.

[0080] This embodiment provides a method for intelligently constructing a branch network topology. Before obtaining network topology layout information, device hierarchy mapping table, and physical space attributes of the computer room, this embodiment first obtains the network device architecture diagram and network topology diagram of the target organization. The computer room node and partition node are identified in the network device architecture diagram. Based on the identified computer room nodes, partition nodes, the arrangement relationship between computer room nodes, and the partition arrangement relationship within the computer room, network topology layout information is generated. At the same time, the network topology diagram is parsed to extract device type, device role information, and vertical layout characteristics within the partitions, and a device hierarchy mapping table is generated.

[0081] In summary, this embodiment overcomes the technical shortcomings of manual analysis of architecture and topology diagrams by extracting layout information and hierarchical mapping tables from two different types of images: network device architecture diagrams and network topology diagrams. This achieves automatic generation of layout information and hierarchical mapping tables, providing a complete set of rules for the subsequent automatic generation of topology diagrams that conform to the actual network architecture of branch offices. Unlike parsing only a single topology image, which only yields topology structure information, this embodiment generates two types of rules through dual inputs, making the source of layout information and hierarchical mapping tables clearer and improving the automation and efficiency of topology construction.

[0082] For example, to aid in understanding the embodiments of this application, please refer to Figure 3 , Figure 3 This is a schematic diagram of the overall process of the intelligent construction method for branch network topology in this application, specifically: First, obtain the network equipment architecture diagram and network topology diagram of the target organization. The network equipment architecture diagram can refer to a drawing depicting the physical connections of network equipment and the partitioning structure of the data center in the branch office; the network topology diagram can refer to a screenshot of the existing topology diagram.

[0083] Next, the network device architecture diagram is used for data center node identification, identifying areas containing data center identifiers as data center nodes; the network device architecture diagram is also used for partition node identification, identifying areas containing partition identifiers as partition nodes; based on the data center nodes, partition nodes, the arrangement relationships between data center nodes, and the partition arrangement relationships within the data center, network topology layout information is generated. This network topology layout information represents the arrangement relationships between data center nodes and the partition arrangement relationships within the data center.

[0084] Subsequently, the network topology diagram is parsed to extract device types, device role information, and vertical layout characteristics within partitions, generating a device hierarchy mapping table. This mapping table can contain the correspondence between device types and levels; for example, firewalls correspond to the first level, routers to the second level, and switches to the third level.

[0085] Next, the network topology layout information, device hierarchy mapping table, and physical space attributes of the data center of the target organization are obtained. Based on the physical space attributes of the data center, the devices are aggregated to generate data center nodes and edge relationships. Based on the data center nodes and edge relationships, a data center-level topology layout is performed according to the network topology layout information. Specifically, the device list of the target organization can be obtained; the devices in the device list are aggregated according to the physical space attributes of the data center to generate a set of data center nodes and edge relationships between data center nodes; and a data center-level topology layout is performed on the data center nodes and edge relationships represented in the network topology layout information.

[0086] Based on this, and using the data center-level topology layout results, network partitions within each data center are determined according to the network topology layout information. Devices within each network partition are then arranged hierarchically to obtain a partition-level topology layout result containing multiple network partitions. Specifically, network partitions within each data center are determined based on the partition arrangement relationships represented in the network topology layout information. For each network partition, device connection relationships are obtained, and the ingress and egress devices within the network partition are analyzed based on these relationships. The hierarchical relationships between devices within the network partition are determined based on the ingress and egress devices. Finally, based on these hierarchical relationships, the devices within each network partition are arranged hierarchically to obtain a partition-level topology layout result containing multiple network partitions.

[0087] Next, it is determined whether there are any layout anomalies in the partition-level topology layout results. If layout anomalies are detected in the partition-level topology layout results, the type of layout anomaly is determined. The layout anomaly type includes at least one of the following: no entry device in the network partition, isolated devices with missing device connections in the network partition, and all devices in the network partition are located at the same level.

[0088] If a layout anomaly exists, the device nodes corresponding to the layout anomaly are reassigned hierarchically based on the device hierarchy mapping table to obtain the target network topology layout. Specifically, when the layout anomaly type is that there is no entry device in the network partition, all device nodes in the network partition are reassigned to the corresponding level based on the device hierarchy mapping table; when the layout anomaly type is that there are isolated devices with missing device connections in the network partition, the isolated devices are added to the corresponding level of the current layout based on the device hierarchy mapping table; when the layout anomaly type is that all devices in the network partition are located at the same level, all device nodes in the network partition are reassigned to the corresponding level based on the device hierarchy mapping table.

[0089] Otherwise, if there are no layout anomalies in the partition-level topology layout result, the partition-level topology layout result will be directly used as the target network topology layout.

[0090] Through the above process, this embodiment achieves the automatic generation of a complete and accurate topology layout that conforms to the actual network architecture hierarchy of the branch office.

[0091] It should be noted that the above examples are only for understanding this application and do not constitute a limitation on the intelligent construction method of branch network topology of this application. Any simple modifications based on this technical concept are within the protection scope of this application.

[0092] This application also provides a branch network topology intelligent construction device, please refer to... Figure 4 The branch network topology intelligent construction device includes: The information acquisition module 10 is used to acquire the network topology layout information, device hierarchy mapping table and physical space attributes of the target organization. The network topology layout information represents the arrangement relationship between nodes in the computer room and the partition arrangement relationship within the computer room. The data center-level layout module 20 is used to aggregate devices to generate data center nodes and edge relationships based on the physical space attributes of the data center, and to perform data center-level topology layout based on the data center nodes and edge relationships and the network topology layout information. The partition-level layout module 30 is used to determine the network partitions in each computer room based on the data center-level topology layout results and the network topology layout information, and to perform hierarchical layout of the devices in each network partition to obtain a partition-level topology layout result containing multiple network partitions. The abnormal reassignment module 40 is used to perform hierarchical reassignment of the device nodes corresponding to the abnormal layout based on the device hierarchical mapping table when an abnormal layout is detected in the partition-level topology layout result, so as to obtain the target network topology layout.

[0093] In one embodiment, the abnormal reassignment module 40 is further configured to determine the layout abnormality type, which includes at least one of the following: no entry device in the network partition, isolated device with missing device connection relationship in the network partition, and devices in the network partition being located at the same level. Based on the layout anomaly type, the device nodes corresponding to the layout anomaly are hierarchically reassigned according to the device hierarchy mapping table to obtain the target network topology layout.

[0094] In one embodiment, the abnormal reassignment module 40 is further configured to, when the layout abnormality type is that there is no entry device in the network partition, reallocate all device nodes in the network partition to the corresponding level based on the device level mapping table; When the layout anomaly type is an isolated device with missing device connection relationships within a network partition, the isolated device is added to the corresponding level of the current layout based on the device hierarchy mapping table; When the layout anomaly type is that all devices in the network partition are at the same level, all device nodes in the network partition are reallocated to the corresponding level based on the device level mapping table.

[0095] In one embodiment, the information acquisition module 10 is further configured to acquire the network device architecture diagram and network topology diagram of the target organization; The network device architecture diagram is used to identify data center nodes, and the areas containing data center identifiers are identified as data center nodes; The network device architecture diagram is partitioned and the regions containing partition identifiers are identified as partition nodes. Based on the arrangement relationships between the data center nodes, the partition nodes, the data center nodes, and the partition arrangement relationships within the data center, network topology layout information is generated. The network topology is parsed to extract device types, device role information, and vertical layout characteristics within partitions, and a device hierarchy mapping table is generated.

[0096] In one embodiment, the information acquisition module 10 is further configured to perform a confidence assessment on the results of the identification of the data center node and the results of the identification of the partition node; The confidence level of the network topology graph parsing results is evaluated. If the confidence level of the data center node identification, the partition node identification, or the network topology map resolution is lower than a set threshold, the data center node identification, the partition node identification, or the network topology map resolution shall be re-executed.

[0097] In one embodiment, the data center layout module 20 is further configured to obtain the equipment list of the target organization; The equipment in the equipment list is aggregated according to the physical space attributes of the computer room to generate a set of computer room nodes and the edge relationships between the computer room nodes; Based on the arrangement relationship between data center nodes represented in the network topology layout information, a data center-level topology layout is performed on the data center nodes and edge relationships.

[0098] In one embodiment, the partition-level layout module 30 is further configured to determine the network partitions in each computer room based on the computer room-level topology layout results and according to the partition arrangement relationship in the computer room represented by the network topology layout information. For each network partition, obtain the device connection relationship, and analyze the ingress and egress devices within the network partition based on the device connection relationship; The hierarchical relationship between devices within the network partition is determined based on the ingress device and the egress device. Based on the hierarchical relationship, the devices within each network partition are arranged in a hierarchical manner to obtain a partition-level topology layout result containing multiple network partitions.

[0099] The branch network topology intelligent construction device provided in this application, employing the branch network topology intelligent construction method in the above embodiments, can solve the technical problem of how to automatically generate a complete and accurate topology layout that conforms to the actual network architecture hierarchy of the branch. Compared with the prior art, the beneficial effects of the branch network topology intelligent construction device provided in this application are the same as those of the branch network topology intelligent construction method provided in the above embodiments, and other technical features in the branch network topology intelligent construction device are the same as those disclosed in the methods of the above embodiments, and will not be repeated here.

[0100] This application provides a branch network topology intelligent construction device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the branch network topology intelligent construction method in the above embodiment 1.

[0101] The following is for reference. Figure 5 The diagram illustrates a structural schematic suitable for implementing the branch network topology intelligent construction device of the embodiments of this application. The branch network topology intelligent construction device in the embodiments of this application may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (Personal Digital Assistants), tablets, PMPs (Portable Media Players), vehicle terminals (e.g., vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 5 The branch network topology intelligent construction device shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0102] like Figure 5As shown, the branch network topology intelligent construction device may include a processing unit 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage device 1003 into a random access memory (RAM) 1004. The RAM 1004 also stores various programs and data required for the operation of the branch network topology intelligent construction device. The processing unit 1001, ROM 1002, and RAM 1004 are interconnected via a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to I / O interface 1006: input devices 1007 including, for example, touchscreens, touchpads, keyboards, mice, image sensors, microphones, accelerometers, gyroscopes, etc.; output devices 1008 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 1003 including, for example, magnetic tapes, hard disks, etc.; and communication devices 1009. Communication device 1009 allows the branch office network topology intelligent building device to communicate wirelessly or wiredly with other devices to exchange data. Although the branch office network topology intelligent building device with various systems is shown in the figure, it should be understood that it is not required to implement or possess all the systems shown. More or fewer systems can be implemented alternatively.

[0103] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device, or installed from storage device 1003, or installed from ROM 1002. When the computer program is executed by processing device 1001, it performs the functions defined in the methods of the embodiments disclosed in this application.

[0104] The branch network topology intelligent construction device provided in this application, employing the branch network topology intelligent construction method in the above embodiments, can solve the technical problem of how to automatically generate a complete and accurate topology layout that conforms to the actual network architecture hierarchy of the branch. Compared with the prior art, the beneficial effects of the branch network topology intelligent construction device provided in this application are the same as those of the branch network topology intelligent construction method provided in the above embodiments, and other technical features in this branch network topology intelligent construction device are the same as those disclosed in the previous embodiment method, and will not be repeated here.

[0105] It should be understood that the various parts disclosed in this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any suitable manner in one or more embodiments or examples.

[0106] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0107] This application provides a computer-readable storage medium having computer-readable program instructions (i.e., a computer program) stored thereon, which are used to execute the branch network topology intelligent construction method in the above embodiments.

[0108] The computer-readable storage medium provided in this application may be, for example, a USB flash drive, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, system, or device. The program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination thereof.

[0109] The aforementioned computer-readable storage medium may be included in the branch network topology intelligent construction device; or it may exist independently and not be assembled into the branch network topology intelligent construction device.

[0110] The aforementioned computer-readable storage medium carries one or more programs. When these programs are executed by the branch office network topology intelligent construction device, the branch office network topology intelligent construction device: acquires the target organization's network topology layout information, device hierarchy mapping table, and physical space attributes of the computer room, wherein the network topology layout information characterizes the arrangement relationship between computer room nodes and the partition arrangement relationship within the computer room; aggregates devices to generate computer room nodes and edge relationships based on the physical space attributes of the computer room, and performs a computer room-level topology layout based on the computer room nodes and edge relationships and the network topology layout information; determines network partitions within each computer room based on the computer room-level topology layout result and performs hierarchical layout of devices within each network partition, obtaining a partition-level topology layout result containing multiple network partitions; and, if a layout anomaly is detected in the partition-level topology layout result, performs hierarchical reallocation of the device nodes corresponding to the layout anomaly based on the device hierarchy mapping table to obtain the target network topology layout.

[0111] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a Local Area Network (LAN) or a Wide Area Network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0112] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0113] The modules described in the embodiments of this application can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the unit itself.

[0114] The readable storage medium provided in this application is a computer-readable storage medium that stores computer-readable program instructions (i.e., a computer program) for executing the above-described intelligent branch network topology construction method. This solves the technical problem of how to automatically generate a complete and accurate topology layout that conforms to the actual network architecture of a branch. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as those of the intelligent branch network topology construction method provided in the above embodiments, and will not be elaborated upon here.

[0115] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the branch network topology intelligent construction method described above.

[0116] The computer program product provided in this application can solve the technical problem of how to automatically generate a complete and accurate topology layout that conforms to the actual network architecture hierarchy of a branch office. Compared with the prior art, the beneficial effects of the computer program product provided in this application are the same as those of the intelligent branch office network topology construction method provided in the above embodiments, and will not be repeated here.

[0117] The above description is only a part of the embodiments of this application and does not limit the patent scope of this application. All equivalent structural transformations made under the technical concept of this application and using the contents of the specification and drawings of this application, or direct / indirect applications in other related technical fields, are included in the patent protection scope of this application.

Claims

1. A method for intelligently constructing branch network topology, characterized in that, The method includes: Obtain the network topology layout information, device hierarchy mapping table, and physical space attributes of the computer room of the target organization. The network topology layout information represents the arrangement relationship between computer room nodes and the partition arrangement relationship within the computer room. Based on the physical space attributes of the data center, the devices are aggregated to generate data center nodes and edge relationships, and based on the data center nodes and edge relationships, a data center-level topology layout is performed according to the network topology layout information; Based on the data center-level topology layout results, network partitions within each data center are determined according to the network topology layout information, and devices within each network partition are arranged in a hierarchical manner to obtain a partition-level topology layout result containing multiple network partitions. If an anomaly is detected in the partition-level topology layout result, the device nodes corresponding to the anomaly are hierarchically reassigned based on the device hierarchy mapping table to obtain the target network topology layout.

2. The method as described in claim 1, characterized in that, The step of performing hierarchical reallocation of device nodes corresponding to layout anomalies based on the device hierarchy mapping table to obtain the target network topology layout includes: Determine the layout anomaly type, which includes at least one of the following: no entry device in the network partition, isolated device with missing device connection relationship in the network partition, and all devices in the network partition are located at the same level. Based on the layout anomaly type, the device nodes corresponding to the layout anomaly are hierarchically reassigned according to the device hierarchy mapping table to obtain the target network topology layout.

3. The method as described in claim 2, characterized in that, The step of reallocating the device nodes corresponding to the layout anomaly based on the device hierarchy mapping table includes: When the layout anomaly type is that there is no entry device in the network partition, all device nodes in the network partition are reallocated to the corresponding level based on the device level mapping table; When the layout anomaly type is an isolated device with missing device connection relationships within a network partition, the isolated device is added to the corresponding level of the current layout based on the device hierarchy mapping table; When the layout anomaly type is that all devices in the network partition are at the same level, all device nodes in the network partition are reallocated to the corresponding level based on the device level mapping table.

4. The method as described in claim 1, characterized in that, Before obtaining the network topology layout information, device hierarchy mapping table, and physical space attributes of the computer room of the target organization, the following steps are also included: Obtain the network device architecture diagram and network topology diagram of the target organization; The network device architecture diagram is used to identify data center nodes, and the areas containing data center identifiers are identified as data center nodes; The network device architecture diagram is partitioned and the regions containing partition identifiers are identified as partition nodes. Based on the arrangement relationships between the data center nodes, the partition nodes, the data center nodes, and the partition arrangement relationships within the data center, network topology layout information is generated. The network topology is parsed to extract device types, device role information, and vertical layout characteristics within partitions, and a device hierarchy mapping table is generated.

5. The method as described in claim 4, characterized in that, The method further includes: A confidence level assessment is performed on the results of the data center node identification and the results of the partition node identification; The confidence level of the network topology graph parsing results is evaluated. If the confidence level of the data center node identification, the partition node identification, or the network topology map resolution is lower than a set threshold, the data center node identification, the partition node identification, or the network topology map resolution shall be re-executed.

6. The method as described in claim 1, characterized in that, The step of aggregating devices to generate data center nodes and edge relationships based on the physical space attributes of the data center, and performing data center-level topology layout based on the network topology layout information according to the data center nodes and edge relationships, includes: Obtain the equipment list of the target organization; The equipment in the equipment list is aggregated according to the physical space attributes of the computer room to generate a set of computer room nodes and the edge relationships between the computer room nodes; Based on the arrangement relationship between data center nodes represented in the network topology layout information, a data center-level topology layout is performed on the data center nodes and edge relationships.

7. The method as described in claim 1, characterized in that, The method based on the data center-level topology layout results determines network partitions within each data center according to the network topology layout information, and performs hierarchical layout of devices within each network partition to obtain a partition-level topology layout result containing multiple network partitions, including: Based on the data center-level topology layout results, the network partitions within each data center are determined according to the partition arrangement relationship within the data center represented in the network topology layout information. For each network partition, obtain the device connection relationship, and analyze the ingress and egress devices within the network partition based on the device connection relationship; The hierarchical relationship between devices within the network partition is determined based on the ingress device and the egress device. Based on the hierarchical relationship, the devices in each network partition are arranged in a hierarchical manner to obtain a partition-level topology layout result containing multiple network partitions.

8. A branch network topology intelligent construction device, characterized in that, The device includes: The information acquisition module is used to acquire the network topology layout information, device hierarchy mapping table and physical space attributes of the target organization. The network topology layout information represents the arrangement relationship between nodes in the computer room and the partition arrangement relationship within the computer room. The data center-level layout module is used to aggregate devices to generate data center nodes and edge relationships based on the physical space attributes of the data center, and to perform data center-level topology layout based on the data center nodes and edge relationships and the network topology layout information. The partition-level layout module is used to determine the network partitions in each data center based on the data center-level topology layout results and the network topology layout information, and to perform hierarchical layout of the devices in each network partition to obtain a partition-level topology layout result containing multiple network partitions. The abnormal reassignment module is used to perform hierarchical reassignment of the device nodes corresponding to the abnormal layout based on the device hierarchical mapping table when an abnormal layout is detected in the partition-level topology layout result, so as to obtain the target network topology layout.

9. A branch network topology intelligent construction device, characterized in that, The device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the branch network topology intelligent construction method as described in any one of claims 1 to 7.

10. A storage medium, characterized in that, The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, it implements the steps of the branch network topology intelligent construction method as described in any one of claims 1 to 7.