Method, device, system, apparatus and storage medium for network topology data analysis

Abstract

The application discloses a network topology data analysis method, device, system, equipment and storage medium, and belongs to the data analysis field. The embodiment constructs a topology graph according to physical device data and an association relationship between the physical device data by acquiring the physical device data in a physical network, a node represents the physical device data, the physical device data includes device identification and associated data of the physical device, and a connection between the nodes represents a relationship between the physical device data; a request of a user for an analysis event is received, a target associated data is selected from nodes related to the analysis event, a connection of the nodes and corresponding physical device data of the nodes in the topology graph; an analysis result is obtained by comparing the target associated data with preset data; and the target node, the connection between the target nodes, the corresponding physical device data of the target nodes and the analysis result are displayed according to a topology attribute of the physical device data in the network topology graph, so that flexible and effective data analysis can be realized through the network topology.

Description

Technical Field

[0001] This application belongs to the field of data analysis, and in particular relates to a method, apparatus, device, computer-readable storage medium, and computer program product for network topology data analysis. Background Technology

[0002] With the rapid development of communication technology and the increasing diversity of user needs, the business scenarios that provide services to users and the network architecture used to support these scenarios are becoming increasingly complex. Consequently, it is becoming more and more important to accurately and effectively grasp the network architecture to provide good services to users.

[0003] In existing technologies, network topology diagrams are commonly used to present and analyze physical networks. However, these diagrams are merely simple representations of device-level data. The topology and data are tightly coupled, which cannot accurately describe the physical network. Furthermore, the application of topology diagrams is very limited, resulting in a lack of flexibility and effectiveness in data analysis through network topology. Summary of the Invention

[0004] This application provides a method, apparatus, device, computer-readable storage medium, and computer program product for network topology data analysis, which can flexibly and effectively perform data analysis through network topology.

[0005] In a first aspect, embodiments of this application provide a method for network topology data analysis, the method comprising:

[0006] Acquire data from physical devices in a physical network;

[0007] Based on the physical device data and the relationships between them, a network topology diagram is constructed. The network topology diagram includes multiple nodes and the connections between the nodes. Nodes represent physical device data, which includes the device identifier of the physical device and the associated data of the physical device. The associated data includes the data associated with the physical device itself and the data associated with the physical device with other physical devices. The connections between nodes represent the relationships between physical device data.

[0008] Receive data analysis requests from users, which include information about the events to be analyzed.

[0009] Select the target node set for the event to be analyzed from the network topology diagram, and the connections between the child nodes of the target node set;

[0010] In the network topology diagram, select the target node set for analyzing the event and the target associated data from the physical device data corresponding to the connections between the child nodes of the target node set;

[0011] By comparing the target-related data with preset data, the analysis results of the analyzed event are obtained;

[0012] The network topology diagram displays the target node set, the connections between the child nodes of the target node set, and the target physical device data corresponding to the connections between the target node set and its child nodes, as well as the analysis results, according to the target topology attributes. The target topology attributes are the topology attributes of the target physical device data.

[0013] In one feasible implementation, the associated data of the physical device includes device attribute data, static configuration data, device performance data, capacity data, and alarm / complaint data;

[0014] Based on the physical device data and the relationships between them, construct a network topology diagram, including:

[0015] A network topology diagram is constructed based on the relationships between device attribute data, static configuration data, device performance data, capacity data, alarm and complaint data, and physical device data.

[0016] In one feasible implementation, the relationships between physical device data include relationships between devices, matching relationships between device types and indicator data and database tables, data aggregation relationships, and relationships between ports and the service flows they carry.

[0017] Based on the physical device data and the relationships between them, construct a network topology diagram, including:

[0018] Based on the physical device data and the relationships between devices, the matching relationships between device types and indicator data and database tables, the data aggregation relationships, and the relationships between ports and the carried service flows, a network topology diagram is constructed.

[0019] In one feasible implementation, the target-related data includes target attribute data, target indicator data, and target aggregation and distribution data;

[0020] By comparing the target-related data with preset data, the analysis results of the analyzed event are obtained, including:

[0021] By comparing target attribute data, target indicator data, target aggregated data, and corresponding preset data, the analysis results of the analyzed events are obtained.

[0022] In one feasible implementation, topology attributes include topology rendering identifier, topology rendering font, and topology rendering position;

[0023] The network topology diagram displays the target node set, the connections between the child nodes of the target node set, and the target physical device data corresponding to the connections between the target node set and its child nodes, according to the target topology attributes. The analysis results also include:

[0024] The network topology diagram displays the target node set, the connections between the child nodes of the target node set, and the target physical device data corresponding to the connections between the target node set and its child nodes, as well as the analysis results, according to the target topology presentation identifier, target topology presentation font, and target topology presentation position.

[0025] In one feasible implementation, before displaying the target node set, the connections between the child nodes of the target node set, and the target physical device data corresponding to the connections between the target node set and its child nodes in the network topology diagram according to the target topology attributes, and before displaying the analysis results, the method further includes:

[0026] Receive user modification information regarding the topological attributes of the target associated data;

[0027] Modify the topological attributes of the target associated data based on the modified information.

[0028] In one feasible implementation, the method further includes:

[0029] Receive user updates to physical device data;

[0030] Based on the updated data, the topology map is updated according to the physical device data and the relationships between them.

[0031] In one feasible implementation, after receiving a user's data analysis request, the method further includes:

[0032] The analysis component is invoked to select the target node set and the connections between the child nodes of the target node set from the network topology diagram; target associated data is selected from the physical device data corresponding to the target node set and the connections between the child nodes of the target node set in the network topology diagram; and the analysis results of the analysis event are obtained by comparing the target associated data with the preset data.

[0033] In one feasible implementation, the method further includes:

[0034] Receives new component data from users in the component library, which is used to store and analyze components;

[0035] Based on the newly added data of the components, an analysis component corresponding to the newly added data of the components is added to the component library. Secondly, embodiments of this application provide an apparatus for network topology data analysis, the apparatus comprising:

[0036] The acquisition module is used to acquire data from physical devices in the physical network.

[0037] The construction module is used to build a network topology diagram based on physical device data and the relationships between physical device data. The network topology diagram includes multiple nodes and the connections between multiple nodes. Nodes represent physical device data, and physical device data includes the device identifier of the physical device and the associated data of the physical device. The associated data includes the data associated with the physical device itself and the data associated with the physical device with other physical devices. The connections between nodes represent the relationships between physical device data.

[0038] The receiving module is used to receive data analysis requests from users, which include information about the analysis events.

[0039] The selection module is used to select the target node set for analyzing events from the network topology diagram, as well as the connections between the child nodes of the target node set;

[0040] The selection module is also used to select the target node set for analyzing events in the network topology diagram and to select target associated data from the physical device data corresponding to the connections between the child nodes of the target node set;

[0041] The comparison module is used to obtain the analysis results of the analyzed event by comparing the target related data with preset data;

[0042] The display module is used to display the target node set, the connections between the child nodes of the target node set, the target physical device data corresponding to the connections between the target node set and the child nodes of the target node set, and the analysis results in the network topology diagram according to the target topology attributes. The target topology attributes are the topology attributes of the target physical device data.

[0043] Thirdly, embodiments of this application provide an electronic device, the device including: a processor, and a memory storing computer program instructions; the processor reads and executes the computer program instructions to implement a method for network topology data analysis as described in any embodiment of the first aspect.

[0044] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer program instructions, which, when executed by a processor, implement a network topology data analysis method as described in any embodiment of the first aspect.

[0045] Fifthly, embodiments of this application provide a computer program product in which instructions, when executed by a processor of an electronic device, cause the electronic device to perform a network topology data analysis method as described in any embodiment of the first aspect.

[0046] This application discloses a method, apparatus, device, computer-readable storage medium, and computer program product for network topology data analysis. This embodiment acquires physical device data in a physical network and constructs a network topology diagram based on the physical device data and the relationships between them. The network topology diagram includes multiple nodes and connections between these nodes. Nodes represent physical device data, which includes the device identifier and associated data of the physical device. The associated data includes data associated with the physical device itself and data associated with other physical devices. Connections between nodes represent the relationships between physical device data. By constructing a network topology diagram based on physical device data and their relationships, an operational platform is provided for topology operations. This separates data acquisition and processing from data topology analysis, increasing the freedom of topology operations and providing a more intuitive representation of physical network data. The system then receives a user's data analysis request, which includes information about the analysis event. Finally, it selects a target node set for the analysis event from the network topology diagram, along with the connections between the child nodes of the target node set. In the network topology diagram, target node set for the analysis event and the physical device data corresponding to the connections between the child nodes of the target node set are selected. Based on the data analysis request, the target node set for the analysis event, the connections between its child nodes, and the corresponding associated data are selected on the network topology diagram. Complex and diverse topology operations can be performed on the network topology diagram without considering the underlying physical network data relationships, improving the flexibility of data analysis using network topology. Finally, by comparing the target associated data with preset data, the analysis results of the analysis event are obtained. The target node set, the connections between the child nodes of the target node set, and the target physical device data corresponding to the connections between the target node set and its child nodes are displayed on the network topology diagram according to the target topology attributes, along with the analysis results. The target topology attributes are the topology attributes of the target physical device data. Adding topology presentation attributes to the physical device data allows for real-time synchronous display of all data, including the analysis process and results, expanding the application of network topology diagrams and enabling flexible and effective data analysis through network topology. Attached Figure Description

[0047] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0048] Figure 1 This is a flowchart illustrating a method for network topology data analysis provided in one embodiment of this application;

[0049] Figure 2 This is a schematic diagram of the processing flow of a newly added device provided in one embodiment of this application;

[0050] Figure 3 This is a schematic diagram of the processing flow of newly added indicator data provided in one embodiment of this application;

[0051] Figure 4 This is a schematic diagram of the processing flow of a newly added analysis component provided in one embodiment of this application;

[0052] Figure 5 This is a flowchart illustrating a method for analyzing network speed according to an embodiment of this application;

[0053] Figure 6 This is a structural block diagram of a network topology data analysis apparatus provided in one embodiment of this application;

[0054] Figure 7 This is an architecture diagram of network topology data analysis provided in one embodiment of this application;

[0055] Figure 8 This is a schematic diagram of the hardware structure of an electronic device provided in one embodiment of this application. Detailed Implementation

[0056] The features and exemplary embodiments of various aspects of this application will be described in detail below. To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain this application and not to limit it. For those skilled in the art, this application can be implemented without some of these specific details. The following description of the embodiments is merely to provide a better understanding of this application by illustrating examples.

[0057] It should be noted that, in this document, relational terms such as "first" and "second" are used merely 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 apparatus 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 apparatus. Without further limitations, an element defined by the phrase "comprising..." does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes said element.

[0058] It should be understood that the term "and / or" used in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0059] With the rapid development of communication technology and the increasing diversity of user needs, the business scenarios that provide services to users and the network architecture used to support these scenarios are becoming increasingly complex. Consequently, it is becoming more and more important to accurately and effectively grasp the network architecture to provide good services to users.

[0060] In existing technologies, network topology diagrams are commonly used to present and analyze physical networks. However, these diagrams are merely simple representations of device-level data. The topology and data are tightly coupled, which cannot accurately describe the physical network. Furthermore, the application of topology diagrams is very limited, resulting in a lack of flexibility and effectiveness in data analysis through network topology.

[0061] To address the problems of the prior art, embodiments of this application provide a method, apparatus, device, computer storage medium, and computer program product for network topology data analysis. The method for network topology data analysis provided in this application embodiment will be described first below.

[0062] Figure 1 A flowchart illustrating a method for network topology data analysis according to an embodiment of this application is shown. Figure 1 As shown, the network topology data analysis method provided in this application includes steps S110 to S160.

[0063] S110: Obtain data on physical devices in the physical network.

[0064] Data is collected from physical devices within the physical network, and this data can also be directly extracted from the data sharing platform. The physical network is a network formed by various physical devices and media connected together; it is the lowest layer of the network carrying the Internet. Physical devices can include hosts, routers, and switches, while media can include fiber optic cables, electrical cables, and twisted-pair cables. Physical device data describes information such as the status, performance, configuration, and connectivity of physical devices. This data is crucial for network management and optimization because it provides real-time information about network health, performance bottlenecks, and security risks.

[0065] S120: Construct a network topology diagram based on the physical device data and the relationships between physical device data. The network topology diagram includes multiple nodes and the connections between multiple nodes. Nodes represent physical device data. Physical device data includes the device identifier of the physical device and the associated data of the physical device. The associated data includes the data associated with the physical device itself and the data associated with the physical device with other physical devices. The connections between nodes represent the relationships between physical device data.

[0066] A network topology diagram is constructed based on physical device data and the relationships between them. These relationships can include connections between network devices, device types and performance metrics, data aggregation methods, and the association between ports and service flows. These relationships can be represented and stored in a mapping table. The network topology diagram represents the mapping between the network topology and the physical network. The network topology diagram includes multiple nodes and connections between them. Nodes represent physical device data, which includes the device identifier and associated data. Specifically, the physical device data represented by a node can be physical devices such as computers, routers, and switches, along with their identification information and associated data. The associated data includes data related to the physical device itself, such as its current operating status, IP address, and number of network sessions. It can also include data related to other physical devices, such as connection status and dependency relationships. Connections between nodes represent the relationships between physical device data, which can be physical or logical relationships such as data links, spatial locations, and dependency categories between physical devices. The network topology diagram allows you to query the corresponding underlying physical network data.

[0067] S130: Receive a user's data analysis request, which includes information about the analysis event.

[0068] The system receives a data analysis request from a user, which includes information related to an event for which the user wants to perform data analysis. For example, the analysis event could be a network speed analysis event requested by the user to query the cause of slow internet browsing and video buffering when using APN1.

[0069] S140: Select the target node set for the analysis event from the network topology diagram, and the connections between the child nodes of the target node set.

[0070] In response to user-inputted data analysis requests, topology operations select nodes related to the analyzed event and the connections between their child nodes on the network topology graph. This involves selecting physical devices related to the analyzed event and their connections, essentially choosing the business path for the business data flow related to the analyzed event. Several associated node operations, such as business path identifiers, can be predefined. By selecting source and destination nodes on the topology, continuous nodes / connections between them are associated to form a business path. Topology operations can select single or multiple nodes and / or business paths composed of multiple nodes and their connections on the network topology graph. Nodes can be logical nodes, including nodes of the same device type, displayed as a single node. Through the network topology graph, i.e., the mapping between the topology structure and the physical network, the underlying physical network data corresponding to the topology operation can be queried.

[0071] S150: Select the target associated data from the physical device data corresponding to the connection between the target node set and the child nodes of the target node set in the network topology diagram.

[0072] On the network topology map, select the nodes related to the analyzed event and the connections between their child nodes. That is, select the business path of the business data flow related to the analyzed event on the topology map. Then, select the associated data corresponding to the nodes and the connections between their child nodes. That is, select the target associated data on the associated data corresponding to the selected business path. The target associated data can be associated data corresponding to the topology operation related to the analyzed event. For example, the associated data can be channel-type indicator data including bandwidth utilization, TCP connection success rate, TCP connection latency, etc., as well as Ping success rate and Ping latency of business path connectivity tests.

[0073] S160: By comparing the target-related data with preset data, the analysis results of the analyzed event are obtained.

[0074] After obtaining the target association data corresponding to the topology operation related to the analysis event, this data is compared with the preset data corresponding to the analysis event. The preset data can be preset thresholds, preset conditions, preset events, etc. The analysis result of the analysis event is obtained by comparing the target association data corresponding to the topology operation related to the analysis event with the preset data. For example, if the value of the target association data corresponding to the topology operation related to the analysis event is greater than the preset threshold, the analysis result of the analysis event is abnormal, and the target association data corresponding to the topology operation related to the analysis event is abnormal data.

[0075] S170: Display the target node set, the connections between the child nodes of the target node set, and the target physical device data corresponding to the connections between the target node set and the child nodes of the target node set in the network topology diagram according to the target topology attributes, as well as the analysis results. The target topology attributes are the topology attributes of the target physical device data.

[0076] Physical device data includes topology attributes, which are used to represent the corresponding physical device data on the network topology diagram. The network topology diagram displays multiple nodes corresponding to the topology operation of the analysis event, as well as the connections between these nodes, i.e., the corresponding service path of the topology operation of the analysis event, according to the topology attributes of the relevant physical device data. It also displays the target physical device data corresponding to the connections between the target node set and its child nodes; that is, the physical device data between these nodes, between nodes and connections, and between connections. In other words, it displays all relevant physical device data on the service path corresponding to the topology operation of the analysis event according to the topology attributes. Finally, it displays the final analysis results, i.e., the abnormal data corresponding to the analysis results of the analysis event.

[0077] For example, based on the network speed analysis event input by the user, the network elements and service paths traversed by the corresponding internet number during the target time period are obtained on the network topology map. This is a topology operation. The service paths are obtained by querying the correlation between physical device data, which can be the correlation between network elements. Network speed-related metrics can be selected from the network elements and service paths, such as memory utilization, port utilization, and firewall concurrent sessions. Through the network topology map, i.e., the mapping relationship between the topology structure and the physical network, the underlying physical network data corresponding to the selected metrics can be queried. Based on the topology attributes of the physical device data corresponding to the above topology operation, the network elements and service paths traversed by the internet access process, as well as the physical device data of the related metrics, are displayed in real time on the network topology map. By comparing the metrics data with preset metric thresholds, it is determined whether the metrics data is abnormal. If the metrics data is abnormal, the corresponding analysis results are obtained, and combined with the topology attributes of the physical device data of the metrics data, the analysis results are displayed on the topology map.

[0078] This application discloses a method, apparatus, device, computer-readable storage medium, and computer program product for network topology data analysis. This embodiment acquires physical device data in a physical network and constructs a network topology diagram based on the relationships between the physical device data and the physical device data. The network topology diagram includes multiple nodes and connections between the nodes. Nodes represent physical device data, which includes the device identifier and associated data of the physical device. The associated data includes data associated with the physical device itself and data associated with other physical devices. The connections between nodes represent the relationships between physical device data. By constructing a network topology diagram based on the physical device data and their relationships in the physical network, an operational platform is provided for topology operations. This separates data acquisition and processing from data topology analysis, increasing the freedom of topology operations and providing a more intuitive representation of physical device data. Subsequently, a user's data analysis request is received, which includes information about the analysis event. The target node for the analysis event is selected from the network topology diagram. The network topology diagram is used to select target node sets and the connections between their child nodes. It selects target associated data from the physical device data corresponding to the connection between the target node set and its child nodes in the network topology diagram. Based on the data analysis request, it selects the target node set, its child nodes, and corresponding associated data on the network topology diagram. Complex and diverse topology operations can be performed on the network topology diagram without considering the underlying physical network data relationships, improving the flexibility of data analysis using network topology. Finally, by comparing the target associated data with preset data, the analysis results of the analysis event are obtained. The network topology diagram displays the target node set, the connections between its child nodes, and the target physical device data corresponding to the connection between the target node set and its child nodes, along with the analysis results, according to the target topology attributes. The target topology attributes are the topology attributes of the target physical device data. Adding topology presentation attributes to the physical device data allows for real-time synchronous display of all data, including the analysis process and results, expanding the application of network topology diagrams and enabling flexible and effective data analysis through network topology.

[0079] As another implementation of this application, the associated data of physical devices includes device attribute data, static configuration data, device performance data, capacity data, and alarm complaint data; Step S120: Construct a network topology diagram based on the association relationship between device attribute data, static configuration data, device performance data, capacity data, alarm complaint data, and physical device data.

[0080] The associated data for physical devices includes device attribute data, static configuration data, device performance data, capacity data, and alarm / complaint data.

[0081] The data includes: Device attribute data (such as device name, manufacturer, device type, and data center location), which can be displayed on the topology and supports clustering analysis of multiple devices within the same data center or manufacturer in topology analysis; Static configuration data (such as routing configuration, interface configuration, terminal address pool configuration, and tunnel configuration), which is used to generate the topology and map the relationship between physical ports and carried services, and can also support analysis functions such as service process failure delimitation and tunnel connectivity testing in topology analysis; Performance data (such as CPU load, memory utilization, registration success rate, session establishment success rate, and paging success rate), which displays the performance of network elements and service paths in the topology and supports complaint delimitation analysis in topology analysis; Capacity data (such as the number of registered users, online user capacity, concurrent sessions, and port bandwidth), which can be used to display device capacity utilization analysis and supports disaster recovery analysis in topology analysis; and Alarm and complaint data (such as alarm level, alarm content, complaint number, and complaint details), which displays the alarm status of devices / lines and the distribution of complaint numbers on devices, supporting alarm and complaint analysis in topology analysis. A network topology diagram is constructed based on the physical device data and the relationships between them. The network topology diagram can represent the mapping relationship between the topology and the physical network.

[0082] This embodiment integrates data such as device attributes, static configurations, performance, capacity, and alarms / complaints of the physical network, which can more intuitively and accurately display the network structure and status in the topology diagram, and provide data support for topology analysis, thereby improving the effectiveness and flexibility of network topology data analysis.

[0083] As another implementation of this application, the relationship between physical device data includes the relationship between devices, the matching relationship between device type and indicator data and database tables, the data aggregation relationship, and the relationship between ports and carried service flows; Step S120: Construct a network topology diagram based on physical device data and the relationship between physical device data, including: constructing a network topology diagram based on physical device data and the relationship between devices, the matching relationship between device type and indicator data and database tables, the data aggregation relationship, and the relationship between ports and carried service flows.

[0084] The relationships between physical device data include relationships between devices, matching relationships between device types and indicator data and database tables, data aggregation relationships, and relationships between ports and the services they carry. These relationships can be represented and stored in the form of mapping tables, and network topology diagrams can represent the mapping relationship between the network topology and the physical network.

[0085] The relationships between devices can include the core network mobility management device AMF01, whose device mapping table contains fields such as manufacturer, data center, left neighbor device, left neighbor port, right neighbor device 1, right neighbor port 1, right neighbor device 2, right neighbor port 2, backup device, and home POOL. This mapping relationship is the foundation for drawing topology and analyzing service paths, supporting upper-layer analyses such as device-to-manufacturer and data center disaster recovery. The matching relationship between device type, indicator data, and database tables can include indicators such as registration success rate, paging success rate, and CPU load for AMF-type devices; and indicators such as memory utilization and concurrent sessions for firewall devices. This mapping relationship supports upper-layer selection of indicators and allows querying specific data. Data aggregation relationships can include the cumulative relationship of registered user counts after multiple AMFs within a POOL are aggregated into the AMF pool, the cumulative relationship of registration success rate (numerator and denominator respectively), the maximum value for firewall primary / backup concurrent session load, and port bandwidth load. This mapping relationship supports the expansion / aggregation of primary / backup devices, devices within the same POOL, transmission line diagrams, and actual connection diagrams at the topology analysis layer, displaying corresponding data based on the topology status. The relationship between ports and carried service flows can include situations where, after the core network is service-oriented, service interfaces such as N4 / N8 / N10 appear as the same interface from a physical connection perspective. If logical protocol interfaces are not labeled on the topology, the carried services cannot be distinguished; therefore, a port-carrying service mapping relationship needs to be established. For example, physical port interface xgei-2 / 0 / 7 / 1, its sub-interface .1 carries interface N6, sub-interface .3 carries interface N3, etc. This mapping relationship supports topology analysis functions for upper-layer alarms and service flows.

[0086] This embodiment integrates physical device data relationships, such as relationships between devices, matching relationships between device types and indicator data and database tables, as well as data aggregation relationships, to construct a more detailed and accurate network topology diagram. This provides a more intuitive understanding of the network structure and its operational status, offers data support for topology analysis, and improves the effectiveness and flexibility of network topology data analysis.

[0087] As another implementation of this application, the target-related data includes target attribute data, target indicator data, and target aggregation and distribution data; Step S160: By comparing the target-related data with preset data, the analysis results of the analysis event are obtained, including: by comparing the target attribute data, target indicator data, target aggregation and distribution data, and corresponding preset data, the analysis results of the analysis event are obtained.

[0088] After analyzing the business data flow related to the event, the associated data corresponding to the nodes and the connections between these nodes' child nodes can include attribute data, indicator data, and aggregated / distributed data. Attribute data can include data centers, manufacturers, etc.; indicator data can include the number of users, success rate, ping latency, port utilization, etc.; aggregated / distributed data can include similar attribute or indicator data that can be aggregated or displayed separately, such as the number of concurrent sessions.

[0089] Topology analysis related to events can include single / multi-node analysis. For example, selecting attribute data such as data center and manufacturer for a single node, or analyzing metrics such as user count and success rate, or performing data analysis on multiple nodes within the same data center for a specific node, including user count, load, and success rate. Topology analysis related to events can also include data analysis of business paths. For example, clicking two nodes consecutively to select a continuous topology path, and then selecting metrics such as ping latency and port utilization on that path, or selecting the path of a specific user's internet access service for data analysis. Topology analysis related to events can also include node expansion / aggregation analysis. For example, double-clicking a logical node of a firewall expands it to show two actual firewall devices (primary and backup). If the logical node displays 1000 concurrent sessions, expanding it will display 550 and 450 concurrent sessions on the primary and backup devices respectively. Topology analysis related to events can also include calling analysis components on nodes. For example, calling other systems' dial-up testing tasks on a node, or starting the "Session Establishment Success Rate Degradation Location" analysis component on a node.

[0090] After obtaining the target related data such as attribute data, indicator data, or aggregated data corresponding to the topology operations related to the analysis event, these data are compared with the preset data corresponding to the analysis event. The preset data can be preset thresholds, preset conditions, and preset events. The analysis results of the analysis event are obtained by comparing the related data corresponding to the topology operations related to the analysis event with the preset data.

[0091] This embodiment performs topology operations on the network topology map and obtains corresponding related data for further comparative analysis with preset data. The physical device data corresponding to the topology operations includes attribute data, indicator data, and distribution data, providing a rich variety of in-depth topology operation methods and increasing the flexibility of network topology analysis.

[0092] As another implementation of this application, the topology attributes include topology presentation identifier, topology presentation font, and topology presentation position; Step S160: Display the target node set, the connections between the child nodes of the target node set, and the target physical device data corresponding to the connections between the target node set and the child nodes of the target node set in the network topology diagram according to the target topology attributes, as well as the analysis results, including: displaying the target node set, the connections between the child nodes of the target node set, and the target physical device data corresponding to the connections between the target node set and the child nodes of the target node set in the network topology diagram according to the target topology presentation identifier, target topology presentation font, and target topology presentation position, as well as the analysis results.

[0093] Data topology attributes can include topology display identifier, font, font color, and relative node / connection position. Different topology operations result in different topology attribute values ​​and display methods for the corresponding data. For example, for normal data display, `DataShowProp = (1, Msyh, black, 2)` means this data will be displayed on the topology with the font being Microsoft YaHei, the color being black, and the relative position being 2. For abnormal data display, `DataShowProp = (1, Msyh, red, 2)` means that when the indicator data is determined to be abnormal, this topology operation is called to display the data on the topology with the font being Microsoft YaHei, the color being red, and the relative position being 2. A topology operation that clears the current data display in one click is `AllClear()`, which sets all data with a topology display identifier of 1 in the data topology attributes to 0.

[0094] Topology operations involve associating nodes and the connections between them, such as identifying service paths. By selecting source and destination nodes on the topology, continuous nodes / connections between them are associated. Service path-related data includes channel-related metrics such as bandwidth utilization, TCP connection success rate, and TCP connection latency, as well as ping success rate and ping latency for service path connectivity tests. Selecting data to display on the service path also modifies the topology attributes of the aforementioned channel-related metrics, but the display position differs from that of a single node; it can be the middle of the long side above the smallest ellipse on the outer edge of the service path.

[0095] Topology operations involve analysis processes, and data within these processes is synchronously presented in the topology. Whether this presentation is enabled can be configured by adding topology attributes to the data. It's also necessary to identify whether the data is single-network metadata or associated network metadata to select appropriate location parameters within the data's topology attributes. The analysis process here is carried out by independent data analysis components, and the devices to which the input parameters of these components belong determine the device type associated with those components.

[0096] The network topology diagram displays multiple nodes corresponding to the topology operation of the analysis event according to the topology attributes of the relevant physical device data, as well as the connections between these nodes, i.e., the corresponding business path of the topology operation of the analysis event. It also displays the target physical device data corresponding to the connections between the target node set and the child nodes of the target node set, i.e., the physical device data between these nodes, between nodes and connections, and between connections. In other words, it displays all the relevant physical device data on the business path corresponding to the topology operation of the analysis event according to the topology attributes. Finally, it displays the final analysis results, i.e., the abnormal data corresponding to the analysis results of the analysis event.

[0097] This embodiment adds topology presentation attributes to the data to identify whether and how the data is presented in the topology, thereby rendering and displaying the data analysis process and results on the topology map, improving the effectiveness and flexibility of network topology data analysis.

[0098] As another implementation of this application, before step S170: displaying the target node set, the connections between the child nodes of the target node set, and the target physical device data corresponding to the connections between the target node set and the child nodes of the target node set in the network topology diagram according to the target topology attributes, and the analysis results, the method further includes: receiving user modification information on the topology attributes of the target associated data target; modifying the topology attributes of the target associated data based on the modification information.

[0099] After obtaining the analysis results of the analysis event, the system receives further modification information from the user regarding the topology attributes of the target associated data of the physical device data related to the analysis results. The system then modifies the topology attributes of the target associated data of the physical device data related to the analysis results so that the data can be displayed synchronously on the topology in real time.

[0100] This embodiment achieves real-time synchronization between data analysis and topology rendering by adjusting data topology attributes in a timely manner during the data analysis process, thereby improving the effectiveness and flexibility of network topology data analysis.

[0101] As another implementation of this application, the method further includes: receiving updated data from the user regarding physical device data; and updating the topology map based on the updated data and according to the association between the physical device data and the physical device data.

[0102] In real-world communication networks, as networks and services evolve, network equipment will be added or removed accordingly. Similarly, performance metrics will also change. To adapt to changes in the existing network, we have designed several change mechanisms to address these changes in equipment and performance metrics. Figure 2 This application illustrates a schematic diagram of the processing flow for adding a new device according to an embodiment of the present application, as shown below. Figure 2As shown, the process for adding new equipment includes steps S210 to S240.

[0103] Step S210: Receive device update data.

[0104] Receive user updates to physical device data; these updates may include device update data.

[0105] Step S220: Determine if the device type exists.

[0106] Determine whether the device type of the newly added device in the device update data already exists in the existing mapping relationship.

[0107] Step S230: Update the device mapping table and port mapping table.

[0108] If the device type of the newly added device already exists, update the device mapping table and port mapping table. Specifically, automatically add a row to the device mapping table, with each field automatically obtained by reading the primary / standby and POOL configurations. Also automatically add a row to the port mapping table, with each field obtained by reading the port configuration of the newly added device.

[0109] Step S240: Update the device mapping table, port mapping table, and device type and indicator data.

[0110] If the device type for a newly added device does not exist, updates are made to the device mapping table, port mapping table, and device type and metric data. Specifically, a new row is automatically added to the device mapping table, with each field automatically retrieved by reading the primary / standby and POOL configurations. A new row is automatically added to the port mapping table, with each field retrieved by reading the port configuration of the newly added device. A new row is automatically added to the device type and metric data, with each field retrieved by reading the header of the data sharing table for the newly added device.

[0111] In response to increases or decreases in equipment and indicator data, Figure 3 This illustration shows a schematic diagram of the processing flow for newly added indicator data provided in one embodiment of this application, such as... Figure 3 As shown, the processing flow for newly added indicator data includes steps S310 to S330.

[0112] Step S310: Receive indicator data update data.

[0113] Receive user updates to physical device data; these updates may include target data updates.

[0114] Step S320: Locate the device and device type where the newly added indicator data is located.

[0115] Locate the device and device type where the newly added indicator data is located, and determine the corresponding device type and indicator data mapping table.

[0116] Step S330: Update the mapping table between equipment type and indicator data.

[0117] Update the mapping table between equipment type and indicator data. Automatically add a row to the equipment type and indicator data, with each field derived from the newly added data and its equipment type.

[0118] Receive device update data and / or indicator data from users regarding physical device data; based on the updated data, update the mapping table that stores the relationships between physical device data according to the relationships between physical device data, and update the topology graph based on the updated mapping table.

[0119] This embodiment receives user updates to physical device data and dynamically adjusts the topology map based on these updates, ensuring that the network topology map always reflects the latest network status and improving the accuracy of data analysis.

[0120] As another implementation of this application, the method further includes: after receiving the user's data analysis request in step S130, the method further includes: calling the analysis component to select the target node set of the analysis event from the network topology diagram, and the connection between the child nodes of the target node set; selecting target associated data from the physical device data corresponding to the target node set of the analysis event and the connection between the child nodes of the target node set in the network topology diagram; and obtaining the analysis result of the analysis event by comparing the target associated data with preset data.

[0121] By invoking a pre-defined analysis component corresponding to the analysis event, the system selects nodes related to the analysis event and the connections between their child nodes on the network topology map. This involves selecting physical devices related to the analysis event and their connections, or the business paths of the business data flows related to the analysis event. The system then selects target associated data corresponding to the nodes and their child nodes, i.e., the associated data corresponding to the selected business paths. This data is compared with pre-defined data corresponding to the analysis event. The pre-defined data can be preset thresholds, conditions, or events. The analysis results are obtained by comparing the target associated data corresponding to the topology operations related to the analysis event with the preset data. For example, the analysis component can be a rate analysis component, which includes queries for user subscription rates, current effective rates of user plane device UPFs, and rate limiting policies of billing and policy devices (PCFs), and compares and analyzes the results. Data querying, data mapping, and data management functions are performed within the analysis component.

[0122] This embodiment improves the efficiency and accuracy of network topology data analysis by calling the business path of the business data flow related to the analysis event in the network topology diagram and selecting the target associated data from the associated data of the business path. By comparing the target associated data with preset data, the analysis results of the analysis event are obtained.

[0123] As another implementation of this application, the method further includes: receiving new component data from the user in the component library, the component library being used to store analysis components; and adding an analysis component corresponding to the new component data in the component library based on the new component data.

[0124] In topology data analysis, besides basic data selection and presentation, another crucial analytical capability is the real-time synchronization of analysis components with the topology presentation. Naturally, the number of analysis components to perform specific analytical tasks, such as fault and complaint delineation, is gradually increased to meet the needs of data analysis. Therefore, to ensure real-time synchronization with the network topology data after the addition of analysis components, the system has added a component registration process to complete the review and registration of new components. For example, newly added analysis components can include downtime status analysis components, contract status analysis components, whitelist analysis components, segmented ping test components, and data center disaster recovery analysis components.

[0125] Figure 4 This illustration shows a schematic diagram of the processing flow of a newly added analysis component provided in one embodiment of this application, as follows: Figure 4 As shown, the processing flow for adding a new analysis component includes steps S410 to S470.

[0126] S410: Data analysis component registration.

[0127] S420: View all devices running the design for all components.

[0128] S430: Look up the device mapping table associated with the component in the mapping table.

[0129] S430: View the first device involved in the component's operation, and the topology node to which the component is associated.

[0130] S450: Check if the data in the component is labeled with topology rendering parameters.

[0131] S460: Add to the component library and associated device call list.

[0132] The data in the component has been labeled with topology rendering parameters and added to the component library and associated device call list.

[0133] S470: Prompt to improve component topology rendering configuration.

[0134] The data in the component does not have topology rendering parameters labeled. You are advised to improve the component's topology rendering configuration.

[0135] This embodiment receives new component data from users in the component library and adds the corresponding analysis component to the library. This improves the efficiency and accuracy of network topology data analysis.

[0136] In one embodiment, Figure 5 A flowchart illustrating a method for analyzing network rates according to an embodiment of this application is shown, as follows: Figure 5 As shown, the method includes steps S510 to S540.

[0137] S510: Obtain and display the business path.

[0138] Based on the user's input complaint card number, the system queries the network element devices that the number passes through in the network topology diagram; by querying the mapping relationship between data types and data tables, it returns the name of the user's service path table that needs to be queried; by querying the user's service path table, it obtains the network element device where the user is currently located, and completes the service path display on the topology.

[0139] S520: Key performance indicator analysis of business paths.

[0140] In the network topology diagram, select metrics that may affect data transmission performance within the complaint period, such as memory utilization, port utilization, and firewall concurrent sessions. Based on the selected metrics, query the data of related nodes. Using the data type and data table mapping relationship, return the name of the performance data table to be queried. Then, read the data from the corresponding performance data table, modify the topology attribute values ​​of these data, and display the data along the business path on the network topology diagram. If a device's metrics are abnormal at this time, the problem is initially identified as occurring on that device, and further analysis of other data for that device is then conducted.

[0141] S530: Invoke the user rate analysis component.

[0142] At user nodes along the service path in the network topology diagram, the user rate analysis component is activated. This component includes queries for the user's subscribed rate, the current effective rate of the user plane device (UPF), and the rate-limiting policy of the billing and policy device (PCF), comparing and analyzing the output results. The analysis component performs three layers of functionality: data management, data mapping, and data querying. The data returned by the analysis component is displayed on the network topology diagram along with the analysis conclusions. If the user's subscribed rate and the currently effective policy are similar, it indicates that the user's subscribed rate is too low; if the user has an effective rate-limiting policy, the reason for triggering that policy is the cause of the user's slow internet speed.

[0143] S540: Segmented Ping Test of Business Path.

[0144] A segmented Ping test component is triggered on the service paths in the network topology diagram. This component includes ping tests on multiple service paths, such as UPF to base station, UPF to customer, and UPF to core network egress firewall. Real-time data collection is performed within the component; unlike other historical data analyses, this involves initiating ping tests and data collection in real-time by calling device commands. Based on the returned data, such as latency and packet loss rate, the data mapping relationship between the ping source and destination devices and the data management layer functions are queried. Finally, the data is returned to the network topology diagram, displaying segmented topology data, such as latency and packet loss rate for each segment. Based on the segmented latency and packet loss rate, the problematic segment can be identified, allowing for further analysis of the devices involved in that segment. Following the designed delimitation approach and analysis process, each analysis component can be called sequentially, similar to step 530.

[0145] Based on the same concept, embodiments of this application provide a device for network topology data analysis, which is described below in conjunction with... Figure 6 The apparatus for network topology data analysis provided in the embodiments of this application will be described in detail.

[0146] Figure 6 This is a structural block diagram of a network topology data analysis apparatus as shown in an embodiment of this application. Figure 6 As shown, the apparatus for network topology data analysis may include:

[0147] Module 610 is used to acquire data of physical devices in the physical network;

[0148] The construction module 620 is used to construct a network topology diagram based on physical device data and the relationships between physical device data. The network topology diagram includes multiple nodes and the connections between multiple nodes. Nodes represent physical device data, and physical device data includes the device identifier of the physical device and the associated data of the physical device. The associated data includes the data associated with the physical device itself and the data associated with the physical device with other physical devices. The connections between nodes represent the relationships between physical device data.

[0149] The receiving module 630 is used to receive data analysis requests from users, which include information about the analysis events.

[0150] The selection module 640 is used to select the target node set for analyzing events from the network topology diagram, as well as the connections between the child nodes of the target node set;

[0151] The selection module 640 is also used to select the target node set of the analysis event in the network topology diagram and to select the target associated data from the physical device data corresponding to the connection between the child nodes of the target node set;

[0152] The comparison module 650 is used to obtain the analysis results of the analysis event by comparing the target related data with preset data;

[0153] Display module 660 is used to display the target node set, the connections between the child nodes of the target node set, the target physical device data corresponding to the connections between the target node set and the child nodes of the target node set, and the analysis results in the network topology diagram according to the target topology attributes. The target topology attributes are the topology attributes of the target physical device data.

[0154] In one embodiment, the associated data of physical devices includes device attribute data, static configuration data, device performance data, capacity data, and alarm / complaint data; the construction module 620 is specifically used to construct a network topology map based on the association between device attribute data, static configuration data, device performance data, capacity data, alarm / complaint data, and physical device data.

[0155] In one embodiment, the relationships between physical device data include the relationships between devices, the matching relationships between device types and indicator data and database tables, the data aggregation relationships, and the relationships between ports and carried service flows; the construction module 620 is specifically used to construct a network topology diagram based on the physical device data and the relationships between devices, the matching relationships between device types and indicator data and database tables, the data aggregation relationships, and the relationships between ports and carried service flows.

[0156] In one embodiment, the target-related data includes target attribute data, target indicator data, and target aggregation data; the comparison module 650 is specifically used to obtain the analysis results of the analysis event by comparing the target attribute data, target indicator data, target aggregation data, and corresponding preset data.

[0157] In one embodiment, the topology attributes include a topology presentation identifier, a topology presentation font, and a topology presentation position; the display module 660 is specifically used to display, in the network topology diagram, a set of target nodes, the connections between the child nodes of the set of target nodes, and the target physical device data corresponding to the connections between the set of target nodes and the child nodes of the set of target nodes, as well as the analysis results, according to the target topology presentation identifier, the target topology presentation font, and the target topology presentation position.

[0158] In one embodiment, before displaying the target node set, the connections between the child nodes of the target node set, and the target physical device data corresponding to the connections between the target node set and the child nodes of the target node set in the network topology diagram according to the target topology attributes, and before displaying the analysis results, the display module 660 is specifically used to receive user modification information on the topology attributes of the target associated data; and modify the topology attributes of the target associated data based on the modification information.

[0159] In one embodiment, the construction module 620 is further configured to receive user-updated data on physical device data; and based on the updated data, update the topology map according to the correlation between physical device data and physical device data.

[0160] In one embodiment, after receiving a user's data analysis request, the selection module 640 is further configured to call the analysis component to select the target node set of the analysis event from the network topology diagram, as well as the connections between the child nodes of the target node set; select target associated data from the physical device data corresponding to the target node set of the analysis event and the connections between the child nodes of the target node set in the network topology diagram; and obtain the analysis result of the analysis event by comparing the target associated data with preset data.

[0161] In one embodiment, the construction module 620 is further configured to receive new component data from the user in the component library, which is used to store analysis components; and to add analysis components corresponding to the new component data in the component library based on the new component data.

[0162] Figure 6 Each module in the illustrated device has the ability to implement Figure 1 and Figure 5 The functions of each step in the process and their corresponding technical effects are described briefly and will not be elaborated here.

[0163] This application provides an architecture for network topology data analysis. The following is in conjunction with... Figure 7 The architecture for network topology data analysis provided in the embodiments of this application will be described in detail. Figure 7 This is an architecture diagram illustrating network topology data analysis according to an embodiment of this application. For example... Figure 7 As shown, the network topology data analysis architecture is divided into four layers: data sharing layer, data mapping layer, data management layer, and topology analysis layer.

[0164] The data sharing layer primarily handles data acquisition and processing within the physical network, without considering how the data is used. This layer can be designed independently or shared with an enterprise-level data sharing platform. Commonly used data in topology analysis includes the following categories:

[0165] 1. Equipment attribute data: such as equipment name, manufacturer, equipment type, and data center location. This data can be displayed on the topology and can also support clustering analysis of multiple devices in the same data center or manufacturer in topology analysis.

[0166] 2. Static configuration data: routing configuration, interface configuration, terminal address pool configuration, tunnel configuration, etc. This data is used to generate topology and map the relationship between physical ports and carried services. It can also be used to support analysis functions such as business process failure delimitation and tunnel connectivity testing in topology analysis.

[0167] 3. Performance data: CPU load, memory utilization, registration success rate, session establishment success rate, paging success rate, etc. These data are used to display the performance of network element devices and service paths in the topology, and support complaint delimitation analysis in topology analysis.

[0168] 4. Capacity data: number of registered users, number of online users, number of concurrent sessions, port bandwidth, etc.; this data can be used to display device capacity utilization analysis and support disaster recovery analysis in topology analysis;

[0169] 5. Alarm and Complaint Data: Alarm level, alarm content, complaint number, complaint details, etc. This data displays the alarm status of the device / line and the distribution of complaint numbers on the device, supporting alarm and complaint analysis in topology analysis.

[0170] II. The data mapping layer primarily maintains the mapping relationship between the topology and the physical network. There are mainly four types of mapping relationships:

[0171] 1. Relationships between devices: For example, the core network mobility management device AMF01 has a device mapping table containing fields such as manufacturer, data center, left neighbor device, left neighbor port, right neighbor device 1, right neighbor port 1, right neighbor device 2, right neighbor port 2, backup device, home POOL, etc. This table is the foundation for drawing topology and analyzing service paths, and supports upper-layer analysis such as device manufacturers, data center disaster recovery, etc.

[0172] 2. Matching relationship between device type, indicator data, and database tables: For example, AMF-type devices correspond to indicators such as registration success rate, paging success rate, and CPU load; firewall devices correspond to indicators such as memory utilization and concurrent sessions. This mapping relationship can support the selection of indicators by the upper layer and allows querying specific data.

[0173] 3. Data aggregation relationship: For example, after multiple AMFs in a POOL are aggregated into the AMF pool, the number of registered users is cumulative, the registration success rate is the sum of the numerator and denominator respectively, the firewall primary and backup concurrent session load, port bandwidth load is the maximum, etc.; This data mapping relationship supports the expansion / aggregation of primary and backup devices, devices in the same POOL, transmission line diagrams and actual connection diagrams in the topology analysis layer, and displays the corresponding data according to the topology status.

[0174] 4. Relationship between ports and carried service flows: After the core network is service-oriented, service interfaces such as N4 / N8 / N10 appear as the same interface from a physical connection perspective. If logical protocol interfaces are not labeled in the topology, it's impossible to distinguish the carried services. Therefore, a mapping relationship between ports and carried services needs to be established. For example, physical port interface xgei-2 / 0 / 7 / 1, its sub-interface .1 carries interface N6, sub-interface .3 carries interface N3, and so on. This mapping relationship supports topology analysis functions for upper-layer alarms and service flows.

[0175] The third section, the data management layer, mainly manages the topological attributes of static data associated with devices or intermediate data in the analysis process, in order to support various operations of topology analysis. Three basic management scenarios are defined here.

[0176] 1. Data topology attribute management: Define topology attribute values ​​for several data points, including at least four attributes: topology presentation identifier, font, font color, and relative node / connection position. Define several topology operations for data presentation, such as: Normal data presentation: `DataShowProp = (1, Msyh, black, 2)`, meaning this data will be presented on the topology with the font Microsoft YaHei, the color black, and the relative position 2. Abnormal data presentation: `DataShowProp = (1, Msyh, red, 2)`, meaning when the indicator data is determined to be abnormal, this topology operation is called to present the data on the topology with the font Microsoft YaHei, the color red, and the relative position 2. A one-click operation to clear the currently displayed data can also be defined, such as `AllClear()`, which sets all data with a topology presentation identifier of 1 in the topology attributes to 0.

[0177] 2. Data Management of Associated Nodes: To manage data for related nodes / connections, several associated node operations are defined, such as business path identification. By selecting source and destination nodes on the topology, continuous nodes / connections between them are associated. Business path-related data includes channel-related metrics such as bandwidth utilization, TCP connection success rate, and TCP connection latency, as well as ping success rate and ping latency for business path connectivity tests. Selecting data display on the business path involves modifying the topology attributes of the aforementioned channel-related metrics, but the display position differs from that of a single node; it can be the middle of the long side above the smallest ellipse on the outer edge of the business path.

[0178] 3. Data management in the analysis process is the core function of the topology analysis in this proposal. During data analysis, the presentation of data can be determined by adding topology attributes. It's also necessary to identify whether the data is single-network metadata or associated network metadata to select appropriate location parameters within the data topology attributes. The analysis process carrier here is an independent data analysis component, and the device to which the input parameters of the analysis component belong is the device type associated with the analysis component.

[0179] IV. Topology Analysis Layer: Based on conventional topology operations, this layer defines several corresponding topology operations for user data analysis scenarios to meet user analysis needs.

[0180] First, there's single / multi-node data analysis. This includes selecting attribute data for a single node, such as the data center or manufacturer, or metrics like user count and success rate. It also allows analysis of user count, load, and success rate across multiple nodes in the same data center. Second, there's business path data analysis. This involves clicking two nodes consecutively, selecting a continuous topology path, and then choosing metrics like ping latency and port utilization. Alternatively, you can select the path of a specific user's internet access service and analyze the business path data. Third, there's node expansion / aggregation analysis. For example, double-clicking a logical node on a firewall expands it into two actual firewall devices (primary and backup). If the logical node displays 1000 concurrent sessions, expanding it will display 550 and 450 concurrent sessions on the primary and backup devices, respectively. Fourth, there's node-invoking analysis components. This includes calling testing tasks from other systems on a node, and launching the "Session Establishment Success Rate Degradation Location" analysis component on the node.

[0181] Figure 8 A schematic diagram of the hardware structure of an electronic device provided in one embodiment of this application is shown.

[0182] The electronic device may include a processor 810 and a memory 820 storing computer program instructions.

[0183] Specifically, the processor 810 may include a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of this application.

[0184] Memory 820 may include mass storage for data or instructions. For example, and not limitingly, memory 820 may include a hard disk drive (HDD), floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or Universal Serial Bus (USB) drive, or a combination of two or more of these. Where appropriate, memory 820 may include removable or non-removable (or fixed) media. Where appropriate, memory 820 may be internal or external to the integrated gateway disaster recovery device. In a particular embodiment, memory 820 is non-volatile solid-state memory.

[0185] Memory may include read-only memory (ROM), random access memory (RAM), disk storage media devices, optical storage media devices, flash memory devices, and electrical, optical, or other physical / tangible memory storage devices. Therefore, typically, memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the method according to the first aspect of this disclosure.

[0186] The processor 810 reads and executes computer program instructions stored in the memory 820 to implement any of the network topology data analysis methods in the above embodiments.

[0187] In one example, the electronic device may also include a communication interface 830 and a bus 840. For example, Figure 8 As shown, the processor 810, memory 820, and communication interface 830 are connected through bus 840 and complete communication with each other.

[0188] The communication interface 830 is mainly used to realize communication between various modules, devices, units and / or equipment in the embodiments of this application.

[0189] Bus 840 includes hardware, software, or both, that couples components of an online data traffic metering device together. For example, and not limitingly, the bus may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), HyperTransport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Low Pin Count (LPC) bus, a memory bus, a Microchannel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local (VLB) bus, or other suitable buses, or combinations of two or more of these. Where appropriate, bus 840 may include one or more buses. Although specific buses are described and illustrated in embodiments of this application, any suitable bus or interconnect is contemplated herein.

[0190] The electronic device can perform the network topology data analysis method described in the embodiments of this application, thereby achieving a combination of Figure 1 and Figure 6 The method described is for analyzing network topology data.

[0191] Furthermore, in conjunction with the network topology data analysis method in the above embodiments, this application embodiment can provide a computer-readable storage medium for implementation. This computer-readable storage medium stores computer program instructions; when executed by a processor, these computer program instructions implement any of the network topology data analysis methods in the above embodiments.

[0192] This application also provides a computer program product, including a computer program that, when executed, implements any of the network topology data analysis methods described in the above embodiments.

[0193] It should be clarified that this application is not limited to the specific configurations and processes described above and shown in the figures. For the sake of brevity, detailed descriptions of known methods are omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of this application is not limited to the specific steps described and shown. Those skilled in the art can make various changes, modifications, and additions, or change the order of steps, after understanding the spirit of this application.

[0194] The functional blocks shown in the above-described structural diagram can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application-specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of this application are programs or code segments used to perform the required tasks. Programs or code segments can be stored on a machine-readable medium or transmitted over a transmission medium or communication link via data signals carried on a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio frequency (RF) links, etc. Code segments can be downloaded via computer networks such as the Internet, intranets, etc.

[0195] It should also be noted that the exemplary embodiments mentioned in this application describe methods or systems based on a series of steps or apparatus. However, this application is not limited to the order of the above steps; that is, the steps can be performed in the order mentioned in the embodiments, or in a different order, or several steps can be performed simultaneously.

[0196] The aspects of this application have been described above with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It should be understood that each block in 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 general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that these instructions, executable via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It is also understood that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can also be implemented by dedicated hardware performing the specified functions or actions, or can be implemented by a combination of dedicated hardware and computer instructions.

[0197] The above description is merely a specific implementation of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, modules, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. It should be understood that the protection scope of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the protection scope of this application.

Claims

1. A method of network topology data analysis, characterized by, The method comprises: acquiring physical device data in a physical network; constructing a network topology graph according to the physical device data and the association relationship between the physical device data, the network topology graph comprising a plurality of nodes and a plurality of connections between the nodes, the nodes representing the physical device data, the physical device data comprising device identification of the physical device and association data of the physical device, the association data comprising data associated with the physical device itself and data associated with the physical device and other physical devices, the connections between the nodes representing the relationship between the physical device data and the physical device data; receiving a data analysis request of a user, the data analysis request comprising information of an analysis event; selecting a target node set of the analysis event and connections between child nodes of the target node set from the network topology graph; selecting target association data from the physical device data corresponding to the target node set of the analysis event and the connections between the child nodes of the target node set in the network topology graph; obtaining an analysis result of the analysis event by comparing the target association data with preset data; displaying the target node set, the connections between the child nodes of the target node set, the target physical device data corresponding to the target node set and the connections between the child nodes of the target node set, and the analysis result according to a target topology attribute in the network topology graph, the target topology attribute being a topology attribute of the target physical device data.

2. The method of claim 1, wherein, The association data of the physical device comprises device attribute data, static configuration data, device performance data, capacity data and alarm complaint data; The method comprises: constructing the network topology graph according to the association relationship between the device attribute data, the static configuration data, the device performance data, the capacity data and the alarm complaint data and the physical device data.

3. The method of claim 1, wherein, The association relationship between the physical device data comprises a relationship between devices, a matching relationship between device types and index data and database tables, a data aggregation relationship and a relationship between ports and carried service flows; The method comprises: constructing the network topology graph according to the association relationship between the physical device data and the relationship between devices, the matching relationship between device types and index data and database tables, the data aggregation relationship and the relationship between ports and carried service flows.

4. The method of claim 1, wherein, The target association data comprises target attribute data, target index data and target aggregation data; The method comprises: obtaining the analysis result of the analysis event by comparing the target attribute data, the target index data and the target aggregation data with corresponding preset data.

5. The method of claim 1, wherein, The topology attribute comprises a topology presentation identifier, a topology presentation font and a topology presentation position; displaying the target node set, the connection between the child nodes of the target node set, and the target physical device data corresponding to the target node set and the connection between the child nodes of the target node set in the network topology graph according to target topology attributes, and the analysis result, comprising: displaying the target node set, the connection between the child nodes of the target node set, and the target physical device data corresponding to the target node set and the connection between the child nodes of the target node set in the network topology graph according to target topology presentation identification, target topology presentation font, and target topology presentation position, and the analysis result.

6. The method of claim 1, wherein, Before displaying the target node set, the connection between the child nodes of the target node set, and the target physical device data corresponding to the target node set and the connection between the child nodes of the target node set in the network topology graph according to target topology attributes, and the analysis result, the method further comprises: receiving modification information of the user on the topology attributes of the target association data; modifying the topology attributes of the target association data based on the modification information.

7. The method of claim 1, wherein, The method further comprises: receiving update data of the user on the physical device data; updating the topology graph according to the physical device data and the association relationship between the physical device data based on the update data.

8. The method of claim 1, wherein, After receiving the data analysis request of the user, the method further comprises: calling an analysis component to select the target node set of the analysis event and the connection between the child nodes of the target node set from the network topology graph, selecting target association data from the physical device data corresponding to the target node set and the connection between the child nodes of the target node set of the analysis event in the network topology graph, and obtaining the analysis result of the analysis event by comparing the target association data with preset data.

9. The method of claim 1, wherein, The method further comprises: receiving component addition data of the user on a component library, the component library being used to store analysis components; based on the component addition data, adding an analysis component corresponding to the component addition data in the component library.

10. An apparatus for network topology data analysis, the apparatus comprising: The device comprises: an acquisition module configured to acquire physical device data in a physical network; a construction module configured to construct a network topology graph according to the physical device data and the association relationship between the physical device data, the network topology graph comprising a plurality of nodes and a plurality of connections between the nodes, the nodes representing physical device data, the physical device data comprising device identification of a physical device and association data of the physical device, the association data comprising data associated with the physical device itself and data associated with other physical devices, and the connections between the nodes representing the relationship between the physical device data and the physical device data; a receiving module configured to receive a data analysis request of a user, the data analysis request comprising information of an analysis event; a selection module configured to select a target node set of the analysis event and the connection between the child nodes of the target node set from the network topology graph; The selecting module is further configured to select target associated data from the physical device data corresponding to the target node set and the connection between the child nodes of the target node set in the network topology graph; The comparing module is configured to obtain an analysis result of the analysis event by comparing the target associated data with preset data; The display module is configured to display the target node set, the connection between the child nodes of the target node set, the target physical device data corresponding to the target node set and the connection between the child nodes of the target node set, and the analysis result according to a target topology attribute in the network topology graph, the target topology attribute being a topology attribute of the target physical device data.

11. An electronic device, comprising: The device comprises a processor and a memory storing computer program instructions; The processor executes the computer program instructions to implement the method for analyzing network topology data according to any one of claims 1-9.

12. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer program instructions, and the computer program instructions are executed by the processor to implement the method for analyzing network topology data according to any one of claims 1-9.

13. A computer program product, characterised in that, The instructions in the computer program product are executed by the processor of the electronic device, so that the electronic device executes the method for analyzing network topology data according to any one of claims 1-9.

Images