Automatic recovery method and system after network equipment loss, medium and electronic equipment

Abstract

The invention discloses an automatic recovery method and system after network equipment is lost, a medium and electronic equipment, and relates to the technical field of network management, and the method comprises the steps: obtaining a network topological graph corresponding to a target area, enabling nodes of the network topological graph to correspond to equipment of the target area, and enabling edges of the network topological graph to correspond to the connection relation of the equipment; if it is determined that the lost nodes exist in the network topological graph, a scheduling instruction is applied according to the lost nodes, and the lost nodes are repaired; wherein the scheduling instruction is used for isolating target data currently transmitted by the disconnected node, and scheduling the target data to be transmitted to a backup node in the network topology. By implementing the technical scheme provided by the invention, problems can be quickly positioned and corresponding measures can be taken under the condition of handling a large-scale network or simultaneous disconnection of multiple devices, so that the fault response speed is improved.

Description

Technical Field

[0001] The present application relates to the field of network management technology, and in particular to a method, system, medium and electronic device for automatically recovering a network device after it loses connection. Background Art

[0002] As networks continue to expand and become more complex, the stability and reliability of network devices have become key issues in network management. In large network environments, device disconnection is a common failure that may lead to network service interruption, data transmission delay or loss, etc. Therefore, quickly discovering and restoring disconnected devices is crucial to maintaining the normal operation of the network.

[0003] At present, the common method of handling network device disconnection mainly relies on manual intervention. After the network administrator discovers the device is disconnected through the monitoring system, he needs to manually analyze the cause of the failure, formulate a recovery strategy, and perform corresponding operations remotely or on-site. This method may be able to cope with the loss of connection of a single device, but in the case of large-scale networks or multiple devices losing connection at the same time, the response speed is often slow and inefficient. Summary of the invention

[0004] The present application provides a method, system, medium and electronic device for automatic recovery after a network device loses connection. When dealing with a large-scale network or multiple devices losing connection at the same time, the problem can be quickly located and corresponding measures can be taken to improve the fault response speed.

[0005] In a first aspect of the present application, the present application provides a method for automatically recovering a network device after it loses connection, comprising:

[0006] Acquire a network topology map corresponding to the target area, wherein the nodes of the network topology map correspond to the devices in the target area, and the edges of the network topology map correspond to the connection relationships between the devices;

[0007] If it is determined that there is a disconnected node in the network topology diagram, a scheduling instruction is applied according to the disconnected node, and the disconnected node is repaired;

[0008] The scheduling instruction is used to isolate the target data currently transmitted by the lost node, and to schedule the target node to transmit the target data to a backup node in the network topology.

[0009] In a second aspect of the present application, a system for automatically recovering a network device after it loses connection is provided, comprising:

[0010] A network topology map acquisition module, used to acquire a network topology map corresponding to a target area, wherein nodes of the network topology map correspond to devices in the target area, and edges of the network topology map correspond to connection relationships between devices;

[0011] A scheduling instruction application module is used to apply scheduling instructions according to the lost nodes and repair the lost nodes if it is determined that there are lost nodes in the network topology diagram; wherein the scheduling instructions are used to isolate the target data currently transmitted by the lost nodes, and schedule the target nodes to transmit the target data to the backup nodes in the network topology.

[0012] In a third aspect of the present application, a computer storage medium is provided, wherein the computer storage medium stores a plurality of instructions, wherein the instructions are suitable for being loaded by a processor and executing the above method steps.

[0013] In a fourth aspect of the present application, an electronic device is provided, comprising: a processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the above-mentioned method steps.

[0014] In summary, one or more technical solutions provided in the embodiments of the present application have at least the following technical effects or advantages:

[0015] By obtaining the network topology map corresponding to the target area, the connection relationship and working status of the network equipment can be fully understood. When a disconnected node is detected in the topology map, the system will automatically apply the scheduling instructions and repair it without manual intervention. This method significantly improves the fault response speed, especially when dealing with large-scale networks or multiple devices that are disconnected at the same time, it can quickly locate the problem and take corresponding measures. The application of scheduling instructions realizes the automatic isolation of disconnected nodes and the intelligent scheduling of data transmission, effectively preventing the spread of faults and ensuring the continuity of network services. By transmitting the target data to the backup node, this method ensures the integrity and availability of the data and minimizes the risk of data loss due to device disconnection.

[0016] Compared with the existing methods that rely on manual intervention, the automatic recovery mechanism of the present invention greatly improves the efficiency of network management, reduces human errors, and also reduces maintenance costs. In addition, the automation characteristics of the method enable it to quickly respond to the situation where multiple devices lose connection at the same time in a complex network environment, overcoming the shortcomings of the traditional method of slow response and low efficiency in such scenarios. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 It is a flowchart of a method for automatically recovering a network device after it loses connection provided by an embodiment of the present application;

[0018] Figure 2 It is a structural diagram of an automatic recovery system after a network device loses connection provided by an embodiment of the present application;

[0019] Figure 3 It is a structural schematic diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0020] In order to enable technicians in this field to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below in conjunction with the drawings in the embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this application, not all of the embodiments.

[0021] In the description of the embodiments of the present application, words such as "for example" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described as "for example" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "for example" or "for example" is intended to present related concepts in a specific way.

[0022] In the description of the embodiments of the present application, the meaning of the term "multiple" refers to two or more. For example, multiple systems refer to two or more systems, and multiple screen terminals refer to two or more screen terminals. In addition, the terms "first" and "second" are used for descriptive purposes only and cannot be understood as indicating or implying relative importance or implicitly indicating the indicated technical features. Thus, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features. The terms "include", "comprise", "have" and their variations all mean "including but not limited to", unless otherwise specifically emphasized.

[0023] Please refer to Figure 1 , Figure 1 This is a flowchart of a method for automatically recovering a network device after it loses connection, provided by an embodiment of the present invention. The method can be implemented by a computer program, can be implemented by a single-chip microcomputer, or can be run on an automatic recovery system for network devices after they lose connection based on the von Neumann system. The computer program can be integrated into an application or run as an independent tool application. Specifically, the method can include the following steps:

[0024] Step 101: Obtain a network topology map corresponding to a target area, wherein nodes of the network topology map correspond to devices in the target area, and edges of the network topology map correspond to connection relationships between devices.

[0025] Among them, the target area refers to a specific network range that requires automatic recovery management of network equipment loss. It can be understood as a logically or physically relatively independent network subsystem, which includes a group of interrelated network devices and connections. This area may be divided based on geographical location, for example, a network in a city or region; or it may be divided based on function or business type, for example, an enterprise's core business network or a dedicated network for a specific service. In an embodiment of the present application, the target area may include various types of network devices, such as routers, switches, servers, etc., as well as various communication links connecting these devices. It also includes a network management center responsible for managing and controlling these devices. These devices and links together constitute a relatively complete network subsystem that can independently perform specific network functions or support specific business needs.

[0026] Correspondingly, a network topology diagram refers to a mathematical model and graphical representation used to describe the structure and relationship of network devices and their interconnections in the target area. It can be understood as a complex graph composed of nodes and edges, where nodes represent various devices in the network and edges represent the physical or logical connections between these devices. In an embodiment of the present application, the network topology diagram is not just a static network structure diagram, but a dynamic, information-rich data model. It contains detailed attribute information of each device, such as device type, function, importance, current status, etc. For example, network devices may be divided into a management control plane and a service forwarding plane, and the network management center is responsible for transmitting control instructions and service data to these devices. In addition, the edges in the topology diagram also contain key information such as connection properties, such as bandwidth, delay, and connection type.

[0027] Based on the above embodiment, as an optional embodiment, in step 101: the step of obtaining a network topology map corresponding to the target area may further include the following steps:

[0028] Step 201: Obtain the device type of the device in the target area and the connection relationship between each device, wherein the device type includes a network management center and network devices, the network devices include a management control plane and a service forwarding plane, the network management center transmits control instructions to the network devices through the management control plane, and transmits service data to the network devices through the service forwarding plane, wherein the connection relationship of the devices includes: at least one network device establishes a communication connection with the network management center, and at least one network device exchanges information through the network center.

[0029] The device type refers to the functional classification of each device in the network, which can be understood as a system for classifying and identifying network devices, used to distinguish the specific responsibilities and functions of different devices in the network. This classification not only includes the hardware attributes of the device, but more importantly, reflects the functional positioning and data processing capabilities of the device in the entire network architecture.

[0030] Furthermore, the types of devices in the embodiments of the present application are mainly divided into two categories: network management center and network equipment. The network management center is the control and management core of the entire network, responsible for the monitoring, configuration and decision-making of the entire network. Network equipment is a variety of equipment that constitutes the network infrastructure, such as routers, switches, firewalls, etc. More specifically, network equipment can be divided into two functional levels: management control plane and service forwarding plane. The management control plane is mainly responsible for receiving and executing control instructions from the network management center, processing network configuration, routing calculation and other tasks; while the service forwarding plane is responsible for actual data packet forwarding and processing, and executing specific network services.

[0031] By defining the device type, the system can adopt targeted strategies when performing fault diagnosis and recovery. When a device is detected to be disconnected, the system can quickly assess the scope and severity of the impact based on the type of the disconnected device. For example, if the network management center is disconnected, the backup system may need to be started immediately; if a problem occurs in the service forwarding plane of a network device, the system may try to reroute the data flow or enable the backup device.

[0032] In addition, device type information is also used to optimize network resource allocation and performance management. The system can dynamically adjust network configuration according to the characteristics and load conditions of different types of devices to achieve more balanced resource utilization and more efficient data processing.

[0033] The connection relationship refers to the physical and logical connection between various devices in the network, reflecting the flow path of data in the network and the dependency between devices. This connection relationship includes not only the direct physical connection between devices, but also the logical connection established through network protocols and virtualization technology.

[0034] Furthermore, the connection relationship in the embodiment of the present application is mainly reflected in two aspects. On the one hand, it is the connection between the network device and the network management center, and on the other hand, it is the information exchange between the network devices through the network management center. The network management center transmits control instructions to the network device through the management control plane, and transmits service data to the network device through the service forwarding plane. This dual connection mechanism ensures effective management of the network and efficient transmission of data.

[0035] The definition of connection relationships is mainly used to build an accurate network topology map. By understanding the connection between devices in detail, the system can generate a complete network structure model, which is crucial to understanding the overall architecture and operation mechanism of the network. For example, the system can clearly identify which devices are directly connected and which devices need to communicate through intermediate nodes.

[0036] Secondly, information about connection relationships is crucial for fault diagnosis and recovery. When a device loses connection, the system can quickly track other devices and services that may be affected based on the connection relationships. For example, if a critical network node loses connection, the system can immediately assess which downstream devices may be affected, thereby developing a more targeted recovery strategy.

[0037] Step 202: Determine nodes and edges respectively according to the device type and connection relationship of each device.

[0038] Among them, a node refers to a basic unit in a network topology diagram, representing various devices or functional entities in the network. In the embodiments of the present application, a node can be understood as a specific device in the network, such as a router, a switch, a server, and a more abstract functional unit, such as a network management center, a management control plane, and a service forwarding plane. Each node carries a wealth of attribute information, including but not limited to device type, functional role, processing power, current status, etc. These attributes enable the system to accurately assess the importance and potential impact of each node in the network.

[0039] Correspondingly, an edge refers to a line connecting nodes in a network topology diagram, representing various connection relationships between nodes. In the embodiments of the present application, an edge can be understood as a physical connection between devices, such as a network cable or optical fiber; or a logical connection, such as a virtual private network or a logical link in a software-defined network. Each edge also carries important attribute information, such as connection type, bandwidth capacity, current load, delay characteristics, etc. These attributes enable the system to accurately simulate the data flow and information exchange process in the network.

[0040] By determining the nodes and edges, an accurate network topology can be constructed. By abstracting the complex network structure into a combination of nodes and edges, the system is able to create a mathematically rigorous and intuitive network representation. This representation method makes the complex network structure easy to understand and analyze.

[0041] For example, when a node is disconnected or an edge is disconnected, the system can immediately evaluate the severity of the fault and the potential scope of impact by analyzing the properties of the relevant nodes and edges. For example, the loss of a highly connected node may have a greater impact on the entire network and therefore require more urgent processing.

[0042] Secondly, based on the analysis of node and edge properties, the system can quickly determine the optimal recovery path. For example, among multiple possible recovery paths, the system will give priority to those composed of high-bandwidth, low-latency edges to ensure the efficiency of the recovery process.

[0043] In addition, the definition of nodes and edges is also used for network optimization and resource management. By continuously monitoring the load status of nodes and the traffic conditions of edges, the system can dynamically adjust the network configuration, achieve load balancing, and improve the overall network performance.

[0044] Finally, when new devices are added or the network structure changes, the network topology diagram can be easily updated by simply adding new nodes or edges and defining the corresponding properties.

[0045] Step 203: Generate a network topology graph based on the nodes and edges.

[0046] Based on the above embodiment, as an optional embodiment, the embodiment of the present application also introduces the concept of node classification, which provides a more refined strategy basis for network management and fault recovery by distinguishing nodes into key nodes and ordinary nodes. Specifically, in step 202: determining nodes and edges according to the device type and connection relationship of each device, the step may also include the following steps:

[0047] Step 301: Determine key nodes and common nodes according to the device type and connection relationship of each device, where the importance of key nodes is greater than that of common nodes.

[0048] Among them, key nodes refer to devices or functional entities that play a core role in the network and have a significant impact on the overall function and performance of the network. In the embodiments of the present application, key nodes can be understood as network devices that meet one or more of the following conditions: undertake key network functions, such as network management centers, core routers, etc.; have high connectivity and are directly connected to a large number of other devices; are on the critical path of the network and are responsible for forwarding or processing a large amount of data; run important businesses or services and have a significant impact on the overall network performance. These nodes usually have a high comprehensive score, exceeding the preset importance threshold.

[0049] Correspondingly, ordinary nodes refer to devices or functional entities that play a secondary or auxiliary role in the network relative to key nodes. In the embodiments of the present application, ordinary nodes can be understood as those devices that are also necessary for the normal operation of the network but have a relatively small impact on the overall network, such as terminal access switches, ordinary workstations, etc. The comprehensive scores of these nodes are usually lower than the preset importance threshold.

[0050] Furthermore, the management of network devices by determining key nodes and common nodes has the following advantages:

[0051] (1) Optimize fault detection and recovery strategies. The system will implement more frequent and in-depth monitoring of key nodes and prioritize resource allocation for recovery when a fault occurs. This ensures that the core functions of the network can be maintained and restored as quickly as possible in the event of a fault.

[0052] (2) Realize intelligent resource allocation. The system can allocate more network resources to key nodes, such as higher bandwidth priority, stricter security measures, more frequent data backup, etc., thereby improving the performance and reliability of the overall network.

[0053] (3) Used for accurate fault impact assessment. When a node has a problem, the system can quickly assess the possible impact scope and severity based on whether it is a critical node or a common node, and formulate corresponding response strategies.

[0054] (4) It provides important guidance for network optimization and upgrading. When performing network transformation or capacity expansion, the system can give priority to enhancing the performance of key nodes or improving their redundancy, thereby more effectively improving the quality of the entire network.

[0055] Based on the above embodiments, in the automatic recovery process after the network device loses connection, accurately evaluating the importance of each device is the key to formulating an effective recovery strategy. To this end, the embodiment of the present application introduces a method for calculating the importance of a device based on a first preset formula. Specifically, step 301 may also include the following steps:

[0056] Step 401: Based on a first preset formula, the importance of each device is calculated through the device type and connection relationship of each device.

[0057] Among them, the first preset formula is:

[0058]

[0059] In the formula, R i Indicates the importance of device i, T i The device type coefficient of device i, n i Indicates the number of devices directly connected to device i, m i Indicates the number of devices indirectly connected to device i, K ij The connection type coefficient indicating that device i is directly connected to device j, K ik The connection type coefficient of device i indirectly connected to device k, C j Indicates the number of devices directly connected to device j, I k represents the number of devices indirectly connected to device k, λ and μ represent the corresponding weight coefficients, where the number of hops of the indirectly connected device is less than or equal to 3.

[0060] Specifically, in actual networks, the functions and roles of devices vary greatly. In order to reflect the inherent importance of different types of devices in the network, it is necessary to distinguish their basic importance through device type coefficients. For example, as the control core of the entire network, the network management center undertakes key tasks such as network configuration, monitoring and management, and its device type coefficient may be set to 2 or higher. In contrast, ordinary network devices such as switches or routers, although also important, play a relatively minor role in the overall network management, so the device type coefficient may be set to 1.

[0061] Furthermore, the main part of the formula takes into account the connection relationship of the devices, which is divided into two main items: direct connection impact and indirect connection impact. Directly connected devices usually have closer functional associations and more direct impacts, while indirect connections represent the potential influence of devices in a larger range.

[0062] In the direct connection impact section, the formula takes into account all other devices that are directly connected to the device. For each directly connected device, the formula calculates the product of the importance of its connection type and the number of connections to the device, and then adds these products together for all direct connections. The importance of the connection type is reflected by the connection type coefficient. For example, a connection that carries critical control instructions may be given a higher connection type coefficient (such as 1.5), while a connection for ordinary data transmission may have a lower coefficient (such as 1.0). This distinction allows the system to more accurately assess the contribution of each connection to the importance of the device.

[0063] Correspondingly, the structure of the indirect connection impact section is similar to the direct connection impact section, but it considers the indirect connection through other devices. For each indirectly connected device, the formula also calculates the product of the importance of its connection type and the number of connections of the device, and then adds these products for all indirect connections. The introduction of this part allows the formula to evaluate the influence of the device in a wider network range.

[0064] Furthermore, the setting that the number of hops of the indirectly connected device is less than or equal to 3 is made based on the actual needs of network management and performance optimization. For a large network topology, if all possible indirect connections are considered, not only will the computational complexity increase dramatically, but the number of indirectly connected devices of most nodes may also be similar, making it difficult to effectively distinguish the importance of the nodes. Therefore, this embodiment adopts a more sophisticated and practical method, that is, only considering indirect connections with hops of 1, 2, and 3.

[0065] This approach first focuses on directly connected devices (hop count 1), which typically have the most direct impact on the performance and functionality of a node. It then considers devices with one-hop indirect connections (hop count 2), which are not directly connected but are still within the node's immediate neighborhood and have an important impact on the local characteristics of the network. Finally, it expands the scope to devices with two-hop indirect connections (hop count 3), which are relatively far away but still within a reasonable range of influence and can reflect the node's position and importance in the larger network structure.

[0066] Through the above-mentioned step-by-step consideration method, the system can obtain sufficiently detailed network topology information while maintaining computational efficiency. This balance enables the system to quickly evaluate the importance of nodes, identify the potential scope of fault impact, and perform effective load transfer or backup node selection when necessary. For example, when it is necessary to select a backup for a critical node, the system will give priority to devices that are directly connected to it or only one node away, because these devices are usually able to take over the functions of the lost node more quickly and efficiently. At the same time, considering devices with a hop count of 3 also provides the system with a broader perspective, which helps to identify potential alternative paths or resources in large-scale networks.

[0067] In order to balance the contribution of direct and indirect connections to the importance of devices, direct connection weights and indirect connection weights are introduced into the formula. Usually, the direct connection weight is greater than the indirect connection weight. For example, the direct connection weight may be set to 1.5, while the indirect connection weight is set to 1.0. This setting reflects a common understanding that direct connections usually have a greater impact on the importance of devices than indirect connections. However, these weights can be adjusted according to the characteristics and management needs of specific networks. For example, in a highly distributed network, it may be necessary to increase the indirect connection weight to emphasize the importance of indirect connections.

[0068] In addition, in network management, different types of connections have different degrees of impact on the operation and stability of the network. The first preset formula quantifies this difference by introducing the connection type coefficient, and especially emphasizes the two key connection functions between the network management center and network devices: control command transmission and business data transmission. This distinction is crucial for accurately evaluating the importance of equipment and optimizing fault recovery strategies.

[0069] Control command transmission connections are mainly used for the network management center to send management commands, configuration updates, and monitoring requests to network devices. This type of connection is directly related to the overall management and control capabilities of the network. For example, through this connection, the network management center can adjust the routing strategy of network devices, update security policies, or perform key operations such as software upgrades in real time. Since these operations have a direct impact on the stability and security of the network, control command transmission connections are usually given a higher importance.

[0070] In contrast, business data transmission connections are mainly used to carry regular data traffic in the network, such as users' web browsing, file transfers, or video streaming. Although these connections are equally important for the daily operation of the network, in most cases, short interruptions or delays will not immediately threaten the overall operation of the network.

[0071] Based on the above, the system can assign a higher connection type coefficient value, such as 1.5, to the control instruction transmission connection. This higher value reflects the key role of the control connection in maintaining the normal operation of the network. Correspondingly, the business data transmission connection may be assigned a relatively low value, such as 1.0. This differentiated assignment reflects that in network management, maintaining effective control of the network is more urgent and important than maintaining specific business data flows.

[0072] Through the above technical solution, the equipment importance value calculated based on the first preset formula provides many practical application values ​​for network operation and maintenance.

[0073] In terms of fault recovery priority setting, the system will sort the lost devices according to the calculated importance values. When multiple devices are disconnected at the same time, the system will prioritize the allocation of resources to restore the devices with higher importance. For example, suppose three devices A, B, and C are disconnected at the same time, and their importance values ​​are 8.5, 6.2, and 7.8 respectively. The system will first mobilize resources to restore device A, followed by C and B. This recovery order based on quantitative indicators ensures that the core functions and key businesses of the network can be restored as quickly as possible, thereby minimizing the impact of network interruptions on the overall business.

[0074] Secondly, in terms of resource allocation strategy formulation, the network management system can dynamically adjust resource allocation based on the importance of the device. For devices with higher importance, the system will allocate more network bandwidth, more frequent monitoring checks, and higher levels of security protection measures. For example, if the importance of a router exceeds a preset threshold, the system may automatically increase its data backup frequency from once a day to once an hour, and allocate a dedicated backup power supply to it to ensure its continued stable operation.

[0075] In terms of network optimization, the importance value provides a clear optimization direction. The system can regularly analyze the distribution of importance values ​​of all devices in the network and identify areas where importance is too concentrated or dispersed. For example, if it is found that there are multiple devices in a certain area with high importance values ​​(such as all exceeding 8.5), this may indicate that there is a risk of single point failure in this area. The system can add redundant devices or redesign the network topology in this area to disperse the risk and improve the overall reliability of the network.

[0076] Step 402: Determine devices whose importance is greater than or equal to a threshold as key nodes, and determine devices whose importance is less than the threshold as ordinary nodes.

[0077] Step 302: Determine the backup node based on the key nodes and the common nodes.

[0078] Among them, the backup node refers to a device or functional entity that can take over the functions of the key node when necessary in the network topology. In the embodiment of the present application, the backup node can be understood as an ordinary node that has been evaluated and selected by the system, has sufficient processing power and network connection, and can quickly take over the functions of the key node when it fails.

[0079] Specifically, backup nodes can serve as the core component of network redundancy. When a key node fails or loses connection, it can quickly take over its functions to maintain the basic operation of the network and the continuity of key businesses. Secondly, backup nodes also play a load balancing role in daily network operations. They can share part of the network traffic when needed to avoid overloading of key nodes.

[0080] In a feasible implementation, the selection and configuration of backup nodes is a dynamic process. The system will continuously adjust and optimize the settings of backup nodes according to changes in network topology, evolution of business needs, and real-time status of each node's performance. This dynamism enables the network to always maintain the optimal redundancy strategy, ensuring high reliability while avoiding excessive waste of resources.

[0081] Step 303: The key node, the common node and the backup node are taken as nodes, and the connection relationship is taken as an edge.

[0082] Based on the above embodiment, as an optional embodiment, in step 302: determining the backup node according to the key node and the common node may further include the following steps:

[0083] Step 501: Obtain the propagation path of the key node.

[0084] Among them, the propagation path refers to the main channel and direction for the flow and diffusion of data, control instructions and network status information in the network. In the embodiment of the present application, the propagation path can be understood as a set of routes and connections starting from the key node, passing through a series of intermediate nodes and links, and finally reaching the edge of the network or a specific target node. These paths not only include network connections at the physical level, but also cover the data flow and control information transmission process at the logical level.

[0085] Specifically, the system first extracts all nodes directly connected to the key nodes from the network topology, which constitutes the first layer of the propagation path. Then, the system expands outward layer by layer, analyzing the connection relationship between these directly connected nodes and other nodes until it reaches the edge of the network or reaches the preset hop limit. In this process, the system not only considers physical connections, but also analyzes logical connections, such as logical links in virtual private networks (VPNs) or software-defined networks (SDNs).

[0086] At the same time, the system will also combine real-time network traffic data to analyze the main data flows from key nodes. This includes the transmission path of control instructions, the flow of business data, and the interaction paths of various network protocols. For example, for a core router, the system will pay special attention to the propagation path of its routing table updates because it directly affects the routing decisions of the entire network.

[0087] In addition, the system also considers the redundancy design and load balancing mechanism in the network. For example, if there are multiple parallel data transmission paths, the system will analyze the usage frequency and load of these paths to determine which are the main transmission paths and which are the backup paths. This analysis helps to identify critical links and potential bottlenecks in the network.

[0088] After obtaining the propagation path of the key node, the system can more accurately evaluate the impact range that may be caused by the failure of the key node. This provides an important basis for the subsequent selection of backup nodes. For example, if it is found that the propagation path of a key node covers most of the network, then when selecting its backup node, it is necessary to consider candidate nodes that can cover the same range.

[0089] Step 502: Take an ordinary node that can replace a key node in the propagation path as a target node.

[0090] Specifically, the system will first analyze the characteristics of each propagation path based on the previously acquired key node propagation path information, including path length, bandwidth capacity, delay characteristics, etc. Then, the system will look for common nodes in the network topology that can cover the same or similar propagation paths. This process involves complex path comparison and matching algorithms.

[0091] In a feasible implementation, the system may use a shortest path algorithm or a multi-constrained path algorithm to find common nodes that can replace key nodes at the lowest cost.

[0092] Exemplarily, the system can apply a shortest path algorithm, such as the Dijkstra algorithm or the Bellman-Ford algorithm, to calculate the shortest paths from the key node to all other nodes in the network. These paths constitute the propagation path set of the key node. The system will record the characteristics of these paths, including path length, total delay, minimum bandwidth, etc.

[0093] Then, the system will traverse all common nodes in the network, repeat the above process for each common node, and calculate the shortest path from that node to all other nodes in the network. The system will compare these paths with the propagation path set of key nodes and evaluate their similarity. The calculation of similarity may consider the node overlap covered by the path, the difference in path length, the matching degree of key performance indicators, etc.

[0094] In some cases, a single shortest path may not fully reflect the complexity of the network. In this case, the system will turn to a multi-constraint routing algorithm. Such algorithms, such as SAMCRA (Self-Adaptive Multiple Constraints Routing Algorithm) or TAMCRA (Tunable Accuracy Multiple Constraints Routing Algorithm), can simultaneously consider multiple network constraints, such as delay, bandwidth, number of hops, reliability, etc. Using these algorithms, the system can find common nodes that are close to critical nodes in multiple performance indicators.

[0095] Specifically, the multi-constrained path algorithm defines a multi-dimensional cost function. For example, a three-dimensional vector (delay, bandwidth, reliability) can be used to represent the path cost. The algorithm searches for non-dominated solutions in this multi-dimensional space, that is, those paths that are better than other solutions in at least one dimension. This can find the common nodes that are closest to the performance characteristics of the key nodes after considering multiple factors.

[0096] In addition, the system considers not only the physical topology but also the logical topology. For example, in a software-defined network (SDN) environment, the system analyzes the logical connections of the control plane to ensure that the selected target node can not only replace the key node in data forwarding, but also play a corresponding role in network control and management. At the same time, the system also considers factors such as the hardware capabilities and software version compatibility of the node to ensure that the target node can meet the requirements of replacing the key node in terms of technical specifications.

[0097] In addition, the system will evaluate the impact of each potential target node on network performance. This includes analyzing the changes that may be caused to network latency, throughput, load balancing, etc. if the node is used as a backup. The system will give priority to selecting ordinary nodes as target nodes that can maintain the original performance characteristics of the network to the greatest extent after replacing key nodes.

[0098] In actual operation, the system may select multiple target nodes for each key node to form a candidate pool. These target nodes are sorted according to the matching degree of their replacement capabilities to provide flexibility for the final determination of subsequent backup nodes. For example, if the most matching target node cannot be used as a backup node for some reason, the system can quickly select the next target node in the candidate pool.

[0099] Step 503: Obtain the redundancy of the target node.

[0100] Specifically, after determining the target nodes that can replace the key node propagation path, the system can further obtain the redundancy of these target nodes. Redundancy reflects the remaining resources of the node in terms of processing power, storage space, network bandwidth, etc., and is a key indicator for selecting suitable backup nodes.

[0101] Specifically, the system will conduct a comprehensive resource evaluation for each target node. This evaluation process involves multiple dimensions, including but not limited to CPU usage, memory usage, storage space utilization, network interface bandwidth utilization, etc. The system will collect the above data in real time and analyze it in combination with historical data to obtain more accurate and stable redundancy evaluation results. For example, for CPU usage, the system will not only consider the current instantaneous value, but also analyze the average and peak values ​​over a period of time to ensure that the selected backup node can run stably under various load conditions.

[0102] During the evaluation process, the system sets a weight for each resource indicator, and then calculates a comprehensive redundancy score through weighted calculation. This score reflects the overall backup capability of the node. For example, for key nodes that need to process a large amount of data, the system may give higher weights to CPU and memory usage; while for nodes that are mainly responsible for data forwarding, network bandwidth utilization may be given a higher weight.

[0103] In addition, the system also considers the location and connection characteristics of the target node. For example, a node with high redundancy but poor network location may not be as suitable as a backup as a node with slightly lower redundancy but better location. Therefore, the system combines the topological location information of the node with its resource redundancy to form a more comprehensive evaluation metric.

[0104] It should be noted that the process of obtaining the redundancy of the target node is dynamic and continuous. The system will regularly update this data to adapt to changes in network load and fluctuations in device status. This dynamic evaluation mechanism ensures that when it is necessary to select a backup node, the system can always make decisions based on the latest and most accurate information.

[0105] Step 504: If there is a target node whose redundancy is greater than the threshold, the target node whose redundancy is greater than the threshold is determined as a backup node.

[0106] Among them, the target nodes with redundancy greater than the threshold refer to those nodes that have sufficient margin in resource utilization and performance reserve and can bear additional network load without affecting their normal functions. In the embodiment of the present application, the target nodes with redundancy greater than the threshold can be understood as those network devices or functional entities whose comprehensive resource utilization is lower than the preset safety upper limit after system evaluation and whose remaining capacity exceeds the specified threshold, including but not limited to: CPU usage, memory occupancy, storage space, network bandwidth utilization, etc.

[0107] Step 505: If there is no target node with redundancy greater than the threshold, load transfer is performed on the key node and the target node so that the redundancy of the target node is greater than the threshold.

[0108] Specifically, in order to solve the problem of unbalanced allocation of network resources and ensure that a suitable backup node can be found under any circumstances, during the automatic recovery process after the network device loses connection, when the system determines that there is no target node with redundancy greater than a threshold, the load is transferred to the key node and the target node so that the redundancy of the target node is greater than the threshold.

[0109] Specifically, when the system finds that all potential target nodes do not meet the redundancy threshold requirements, a dynamic load transfer process will be initiated. This process will first conduct a comprehensive analysis of the current network load distribution and identify which key nodes and target nodes can be redistributed. The system will consider multiple factors, including but not limited to the processing power of each node, the current load level, the network topology, and business priorities.

[0110] The system may try to transfer some non-critical services from high-load target nodes to nodes with lighter loads, or disperse the auxiliary functions of some key nodes to other nodes to reduce the pressure on key nodes. During the load transfer process, the system will strictly control the impact on network performance. It will set a series of constraints, such as ensuring that the service quality of key services is not affected, controlling the increase in network latency, and maintaining load balancing. The system will perform multiple rounds of iterations, fine-tuning the load distribution each time, and evaluating the adjusted network status in real time until a solution is found that meets all constraints and enables the target node redundancy to exceed the threshold. In addition, load transfer also needs to consider the dynamic characteristics of the network. The system will predict the load change trend in the short term to ensure that the load distribution after the transfer can remain stable for a certain period of time.

[0111] Based on the above embodiments, the means of determining that the device is disconnected mainly depends on the status monitoring of the management control plane and the service forwarding plane of the network device. Specifically, it may include one or more of the following methods:

[0112] (1) Management control plane detection:

[0113] No response to control instructions: The network management center issues control instructions (such as service configuration, alarm query, software upgrade, etc.) to network devices through the management control plane. If the management control plane of the network device fails, these instructions issued by the network management center will not be responded to. At this time, the management connection between the device and the network management center is lost, indicating that the device is disconnected.

[0114] Disconnected state: When the network management center cannot communicate with the device through the control plane, the device is considered to be in the "disconnected" state, that is, lost connection.

[0115] (2) Service forwarding plane detection

[0116] The service forwarding plane is normal but the control plane is invalid: Even if the control plane is disconnected, if the service forwarding plane of the device can still work normally, the network management center can send specific maintenance commands (such as restart instructions) through the service forwarding plane. If the service forwarding plane can accept and process these commands, it means that the forwarding plane of the device is still normal, and the reason for the disconnection is mainly concentrated in the control plane.

[0117] Service connection validity test: By testing the service connection status between the network management center and the device, confirm whether the service forwarding plane can work normally. If the service connection is normal but the control command does not respond, the device is considered to be partially disconnected (the control plane is disconnected).

[0118] (3) Periodic polling mechanism

[0119] Physical port status check: Network devices periodically poll the working status of all physical ports. If the working status of the physical port is normal, but the routing protocol status of the control plane and the OAM protocol status of the forwarding plane are both invalid, it can be inferred that the control plane or forwarding plane of the device may have failed.

[0120] Protocol status check: By checking the routing protocol status of the control plane and the protocol status of the forwarding plane, you can further confirm whether the device is in a disconnected state. If the protocol status is invalid for multiple consecutive times, the system believes that the control plane and forwarding plane of the device may have failed at the same time.

[0121] (4) Automatic loss of connection determination

[0122] Multiple no-response determination: The system will automatically determine that the device has lost connection if it detects that the device is unresponsive multiple times through continuous polling and command sending mechanisms.

[0123] Restart mechanism: Once the device is confirmed to be disconnected, the system will trigger an automatic recovery mechanism to try to restore the normal operation of the device by restarting the control plane and / or forwarding plane of the device.

[0124] (5) Network Failure Impact Assessment Based on Graph Theory

[0125] Topology analysis: In more complex scenarios, the system uses graph theory to model the topology of the entire network device. By analyzing the connection relationship between devices, the system can evaluate which devices may be indirectly affected by the lost device and predict the propagation path of the fault, thereby quickly identifying the lost device.

[0126] Step 102: If it is determined that there is a lost node in the network topology diagram, a scheduling instruction is applied according to the lost node, and the lost node is repaired, wherein the scheduling instruction is used to isolate the target data currently transmitted by the lost node, and to schedule the target data to be transmitted to a backup node in the network topology.

[0127] Specifically, the system will apply corresponding scheduling instructions according to the characteristics of the lost node. The main purpose of the scheduling instruction is to isolate the target data currently being transmitted by the lost node and reroute this data to a predetermined backup node.

[0128] On the one hand, the scheduling instructions mainly prevent data loss or interruption caused by node disconnection to ensure business continuity; on the other hand, by isolating the disconnected nodes, it can prevent potential network failures from spreading further and maintain the stability of the entire network. The system will first identify all data streams currently being processed by the disconnected nodes, and then formulate detailed scheduling strategies based on the priorities and characteristics of these data streams. For high-priority or time-sensitive data, the system will immediately redirect it to the most suitable backup node; for some non-critical data that can tolerate short delays, the system may temporarily cache it and wait for better network conditions before transmitting it.

[0129] During the scheduling process, the system will make full use of the previously constructed network topology map and node classification information. For example, for a lost device identified as a critical node, the system will prioritize backup nodes with redundancy above the threshold as the target of data redirection. These backup nodes, due to their sufficient resource reserves and similar network locations to the critical nodes, can quickly take over the functions of the lost nodes and minimize service interruptions. At the same time, the system will also consider the overall load balancing of the network to avoid overloading certain nodes during the redirection process.

[0130] The execution of scheduling instructions is a dynamic and continuous process. The system monitors the effect of data redirection in real time, including performance indicators such as the delay and packet loss rate of the new path. If it is found that a backup node cannot effectively handle the redirected data flow, the system will quickly adjust the strategy and select the next most suitable backup node. This dynamic adjustment mechanism ensures that the efficiency and reliability of data transmission can be maintained even in complex and changing network environments.

[0131] At the same time, the system will start the procedure to repair the lost node. The specific strategy of the repair process depends on the reason for the loss of connection and the type of node. For loss of connection due to software failure, the system may try to restart the management control plane of the device and send a specific maintenance command through the service forwarding plane to trigger the restart. If the loss of connection is caused by hardware problems, the system may start the remote diagnosis program, collect detailed fault information, and make automatic repair attempts according to the preset repair process. In some cases, if the automatic repair cannot solve the problem, the system will generate a detailed fault report and notify the network administrator for manual intervention.

[0132] During the repair process, the system will continuously evaluate the progress and effect of the repair. If a repair strategy is found to be ineffective, it will quickly switch to an alternative plan. For example, if restarting the management control plane fails to solve the problem, the system may try to update the device firmware or reset to the last stable configuration version. This flexible repair strategy ensures that the system can cope with various complex failure situations.

[0133] Based on the above embodiment, as an optional embodiment, if the lost node is not a critical node, and there are at least two backup nodes corresponding to the lost node, the closeness of each backup node is calculated based on at least two of the path length, bandwidth and link load between each backup node and the lost node, and the backup node with the greatest closeness is used as the target backup node.

[0134] Specifically, in the process of automatic recovery of network equipment loss of connection, when the system detects that the lost node is not a key node and there are multiple optional backup nodes, an efficient method is needed to select the most suitable backup node. To this end, the embodiment of the present application introduces a backup node selection method based on compactness. This method comprehensively considers key factors such as path length, bandwidth, and link load, and quantifies the suitability of the backup node by calculating the compactness, thereby achieving the selection of the optimal backup node.

[0135] Specifically, the system first identifies all backup nodes corresponding to the lost nodes. These backup nodes are pre-determined in the previous network planning and have the basic ability to take over the functions of the lost nodes. Then, the system collects network status data between these backup nodes and the lost nodes, including path length, bandwidth, and link load. After collecting this data, the system applies the preset closeness calculation formula:

[0136]

[0137] Where C represents the closeness, L represents the path length between the target node and the lost node, B represents the bandwidth of the path between the target node and the lost node, U represents the link load of the path between the target node and the lost node, and w1, w2, and w3 represent the corresponding weight coefficients.

[0138] Among them, the path length between the backup node and the lost node refers to the number of hops or physical distance on the shortest path required from the backup node to the lost node in the network topology. In the embodiment of the present application, it can be understood as the number of intermediate devices or the actual physical distance that the data packet needs to pass through from the backup node to the lost node location. The path length is used to evaluate the network distance between the backup node and the lost node, reflecting the potential delay and complexity of data transmission. A shorter path length usually means faster data transmission speed and lower network overhead, which is conducive to quickly restoring network functions.

[0139] Among them, the bandwidth between the backup node and the lost node refers to the maximum data transmission capacity available on the network path connecting the two nodes. In the embodiment of the present application, it can be understood as the minimum bandwidth value among all links on the path from the backup node to the lost node, usually expressed in bits per second. Bandwidth is used to measure the data processing capability when the backup node takes over the function of the lost node, reflecting the throughput potential of the network path. A higher bandwidth value means that the backup node can handle the data traffic of the lost node more efficiently, which helps to maintain network performance and service quality.

[0140] Among them, the link load between the backup node and the lost node refers to the current resource occupancy on the network path connecting the two nodes. In an embodiment of the present application, it can be understood as the average utilization rate or maximum utilization rate of all links on the path from the backup node to the lost node, usually expressed as a percentage. The link load is used to evaluate the risk of network congestion that the backup node may face when taking over the function of the lost node, reflecting the busyness of the current network path. A lower link load value indicates that the path has more available resources and is more suitable for data migration and service switching, which is conducive to balancing the network load and improving recovery efficiency.

[0141] Furthermore, the system applies this formula to each backup node to calculate their respective closeness. After the calculation is completed, the system compares the closeness values ​​of all backup nodes and selects the node with the highest closeness as the target backup node. This selection process ensures that the selected backup node is closest to the ideal state in terms of network location, transmission capacity, and current load.

[0142] This method of selecting backup nodes improves the accuracy of the backup solution. By comprehensively considering multiple network factors, the system can more accurately evaluate the suitability of each backup node, avoiding the one-sidedness that may be caused by a single indicator. Secondly, this method enhances the efficiency of network recovery. Selecting the node with the highest degree of closeness as a backup means that data migration and service switching can be completed in the shortest time, thereby minimizing network interruption time. In addition, this method also helps to optimize the use of network resources. By considering link load, the system can avoid adding additional burden to the already highly loaded path, thereby maintaining the overall balance of the network.

[0143] It is worth noting that the effectiveness of this method depends largely on the reasonable setting of the weight coefficients. Network administrators can adjust the values ​​of w1, w2, and w3 according to the specific network environment and business needs. For example, in application scenarios that are sensitive to latency, the weight of w1 can be increased; while in networks that mainly transmit large data, a higher w2 value may be required. This flexibility allows this method to adapt to a variety of different network environments and operational needs.

[0144] Based on the above embodiment, as an optional embodiment, if the disconnected node is a key node, a minimum cut algorithm is used to determine a backup node.

[0145] Specifically, during the automatic recovery process after a network device loses connection, when the system determines that the lost node is a critical node, the minimum cut algorithm will be used to determine the backup node. The minimum cut algorithm is an algorithm for network flow graphs, and its purpose is to find a set of edges in the network so that after cutting off these edges, the source node and the sink node are no longer connected. The goal of the minimum cut is to find the set of edges with the smallest total capacity, thereby achieving effective "division". In the recovery scenario after a network device loses connection, the minimum cut algorithm can help determine which nodes or links can serve as backup nodes so that the network connectivity can continue to be maintained when the lost critical node fails.

[0146] In specific implementation, the system obtains the latest network topology and identifies the key nodes that are disconnected. Assume that key node A is disconnected. The system converts the network topology into a traffic model. In the traffic model, the key node A that is disconnected is set as the source node, and other nodes in the network, such as B, C, D, etc., are regarded as potential target nodes or sinks. This abstraction enables the system to better analyze the distribution of network traffic and potential bottlenecks.

[0147] After the conversion is completed, the system will apply the minimum cut algorithm, such as the Edmonds-Karp algorithm, to this traffic model. The core idea of ​​the algorithm is to find the minimum cut from the source node A to the rest of the network by repeatedly calculating the maximum flow. The minimum cut represents a set of edges in the network that will have the least impact on network traffic if these connections are cut off. The nodes on both sides of this set of edges become potential backup node candidates. The execution of the algorithm may require multiple iterations, and each iteration will update the network's traffic state until the optimal cut set is found.

[0148] Through the calculation of the minimum cut algorithm, the system may find that nodes B and C are the most suitable devices as backup nodes. This result means that B and C not only have sufficient resources and capabilities to take over the functions of A, but also maintain good connectivity in the network topology, minimizing the impact of network reconstruction. In the process of selecting B and C as backup nodes, the system also considers their redundancy to ensure that they have enough bandwidth and computing power to bear the additional load.

[0149] After the backup node is determined, the system will immediately perform data redirection operations. All data streams originally transmitted through the lost node A will be rerouted to B and C. The above process requires sophisticated traffic scheduling to ensure the continuity of data transmission and the balance of network load. The system will allocate different data streams to B and C based on the results of the minimum cut, simulating the original function of A as much as possible. At the same time, the system will also start the process of repairing the lost key node A, which may include remote diagnosis, software restart, or notifying technicians for on-site maintenance.

[0150] However, in some cases, B and C may not be able to fully carry the entire load of A. This may be due to their limited processing capabilities, or the limitations of the network topology that prevent some data flows from being effectively redirected. In this case, the system will start the load transfer mechanism. It will analyze other nodes in the network, such as D, E, etc., and assign some non-critical data flows to these nodes for processing. This dynamic load balancing strategy ensures that B and C can focus on processing the most critical business data while also making full use of other resources in the network.

[0151] During the entire process, the system will continuously monitor the performance indicators of the network, such as processing power, latency, packet loss rate, etc., to ensure the effectiveness of the backup solution. If performance degradation is found, the system will adjust the load distribution strategy in real time or consider enabling other backup nodes. This dynamic adjustment mechanism ensures that the efficiency and reliability of data transmission can be maintained even in a complex and changing network environment.

[0152] Through the above technical solution, the minimum cut algorithm is used to determine the backup node, which improves the accuracy and efficiency of network recovery, and can select the most suitable backup node more quickly and accurately, thereby minimizing the network interruption time.

[0153] In summary, in the process of automatic recovery of network equipment loss, the system adopts different processing strategies for key nodes and non-key nodes, which is due to the differences in their importance and potential impact in the network.

[0154] For key nodes, the system uses a minimum cut algorithm to determine backup nodes. This is because key nodes usually play a core role in the network, and their loss of connection may have a significant impact on the connectivity and performance of the entire network. The minimum cut algorithm can find a set of edges with minimum capacity in the network flow graph, and the network can be effectively segmented after cutting off these edges. In this embodiment, this method is used to identify a set of backup nodes that are most suitable for taking over the functions of lost key nodes. The minimum cut algorithm takes into account the overall topological structure and traffic distribution of the network, and can find the optimal solution in maintaining network connectivity and minimizing performance impact. This method is particularly suitable for dealing with situations where key nodes are lost, because it can comprehensively evaluate the network structure and find the best backup strategy to ensure that the core functions and overall performance of the network are minimally affected.

[0155] In contrast, because the loss of connection of non-critical nodes usually does not have a serious impact on the entire network, more attention can be paid to local network characteristics and performance indicators. Therefore, the system adopts a method based on closeness calculation to select backup nodes. This method comprehensively considers factors such as path length, bandwidth, and link load, and quantifies the suitability of each potential backup node by calculating closeness. The calculation of closeness allows the system to evaluate the suitability of backup nodes in multiple dimensions, taking into account both network topology and performance factors. The above method is more flexible, and the weights of various factors can be adjusted according to the specific network environment and business needs to find the most suitable backup node.

[0156] The use of the two different methods above reflects the system's intelligent and differentiated strategies when dealing with network device disconnection. Using the minimum cut algorithm for key nodes ensures that the optimal solution can be found from a global perspective when dealing with situations that may have a significant impact on the entire network. Using a closeness-based method for non-key nodes provides a more flexible and efficient solution that can quickly find the local optimal backup node while avoiding unnecessary computational complexity.

[0157] Reference Figure 2 The present application also provides an automatic recovery system after a network device loses connection, including:

[0158] A network topology map acquisition module, used to acquire a network topology map corresponding to a target area, wherein nodes of the network topology map correspond to devices in the target area, and edges of the network topology map correspond to connection relationships between devices;

[0159] A scheduling instruction application module is used to apply scheduling instructions according to the lost nodes and repair the lost nodes if it is determined that there are lost nodes in the network topology diagram; wherein the scheduling instructions are used to isolate the target data currently transmitted by the lost nodes, and schedule the transmission of the target data to the backup nodes in the network topology.

[0160] On the basis of the above embodiments, as an optional embodiment, the network topology map acquisition module is also used to obtain the device type of the equipment in the target area, and the connection relationship between each of the devices; determine the nodes and edges respectively according to the device type and the connection relationship of each of the devices; generate a network topology map according to the nodes and edges; wherein the device types include a network management center and network devices, the network devices include a management control plane and a service forwarding plane, the network management center transmits control instructions to the network devices through the management control plane, and transmits service data to the network devices through the service forwarding plane; wherein the connection relationship of the devices includes: at least one of the network devices establishes a communication connection with the network management center, and at least one of the network devices exchanges information through the network center.

[0161] On the basis of the above embodiments, as an optional embodiment, the network topology map acquisition module is also used to determine the key nodes and ordinary nodes according to the device type and connection relationship of each of the devices, and the importance of the key nodes is greater than that of the ordinary nodes; determine the backup nodes according to the key nodes and the ordinary nodes; take the key nodes, the ordinary nodes and the backup nodes as nodes, and take the connection relationship as an edge.

[0162] Based on the above embodiment, as an optional embodiment, the network topology map acquisition module is further used to calculate the importance of each device based on the first preset formula through the device type and connection relationship of each device; determine the device whose importance is greater than or equal to the threshold as a key node, and determine the device whose importance is less than the threshold as a common node;

[0163] Among them, the first preset formula is:

[0164]

[0165] In the formula, R i Indicates the importance of device i, T i The device type coefficient of device i, n i Indicates the number of devices directly connected to device i, m i Indicates the number of devices indirectly connected to device i, K ij The connection type coefficient indicating that device i is directly connected to device j, K ikThe connection type coefficient of device i indirectly connected to device k, C j Indicates the number of devices directly connected to device j, I k represents the number of devices indirectly connected to device k, λ and μ represent the corresponding weight coefficients, where the number of hops of the indirectly connected device is less than or equal to 3.

[0166] On the basis of the above embodiments, as an optional embodiment, the network topology map acquisition module is also used to obtain the propagation path of the key node; use an ordinary node that can replace the key node in the propagation path as a target node; obtain the redundancy of the target node; if there is a target node with redundancy greater than a threshold, the target node with redundancy greater than the threshold is determined as a backup node; if there is no target node with redundancy greater than the threshold, load transfer is performed on the key node and the target node to make the redundancy of the target node greater than the threshold.

[0167] On the basis of the above embodiment, as an optional embodiment, the scheduling instruction application module is also used to calculate the closeness of each backup node according to at least two of the path length, bandwidth and link load between each backup node and the lost node if the lost node is not a critical node and there are at least two backup nodes corresponding to the lost node, and use the backup node with the greatest closeness as the target backup node.

[0168] Based on the above embodiment, as an optional embodiment, the scheduling instruction application module is further used to determine the backup node by using the minimum cut algorithm if the lost node is a key node.

[0169] It should be noted that: when the device provided in the above embodiment realizes its function, only the division of the above functional modules is used as an example. In actual application, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the device and method embodiments provided in the above embodiment belong to the same concept, and the specific implementation process is detailed in the method embodiment, which will not be repeated here.

[0170] An embodiment of the present application also provides a computer storage medium, which can store multiple instructions. The instructions are suitable for being loaded by a processor and executed as in the automatic recovery method after the network device loses connection in the above embodiment. The specific execution process can refer to the specific description of the embodiment shown, which will not be repeated here.

[0171] The present application also discloses an electronic device. Figure 3 , Figure 3The electronic device 300 may include: at least one processor 301 , at least one network interface 304 , a user interface 303 , a memory 305 , and at least one communication bus 302 .

[0172] The communication bus 302 is used to realize the connection and communication between these components.

[0173] The user interface 303 may include a display interface and a camera interface. The optional user interface 303 may also include a standard wired interface and a wireless interface.

[0174] The network interface 304 may optionally include a standard wired interface or a wireless interface (such as a WI-FI interface).

[0175] Among them, the processor 301 may include one or more processing cores. The processor 301 uses various interfaces and lines to connect various parts in the entire server, and executes various functions of the server and processes data by running or executing instructions, programs, code sets or instruction sets stored in the memory 305, and calling data stored in the memory 305. Optionally, the processor 301 can be implemented in at least one hardware form of digital signal processing (Digital Signal Processing, DSP), field programmable gate array (Field-Programmable Gate Array, FPGA), and programmable logic array (Programmable Logic Array, PLA). The processor 301 can integrate one or a combination of a central processing unit (Central Processing Unit, CPU), a graphics processing unit (Graphics Processing Unit, GPU) and a modem. Among them, the CPU mainly processes the operating system, user interface diagrams and applications, etc.; the GPU is responsible for rendering and drawing the content to be displayed on the display screen; the modem is used to process wireless communications. It can be understood that the above-mentioned modem may not be integrated into the processor 301, and it can be implemented separately through a chip.

[0176] Among them, the memory 305 may include a random access memory (Random Access Memory, RAM) and may also include a read-only memory (Read-Only Memory). Optionally, the memory 305 includes a non-transitory computer-readable storage medium. The memory 305 can be used to store instructions, programs, codes, code sets or instruction sets. The memory 305 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the above-mentioned various method embodiments, etc.; the data storage area may store data involved in the above-mentioned various method embodiments, etc. The memory 305 may optionally be at least one storage device located away from the aforementioned processor 301. Refer to Figure 3 , the memory 305 as a computer storage medium may include an operating system, a network communication module, a user interface module and an application program of an automatic recovery method after a network device loses connection.

[0177] exist Figure 3 In the electronic device 300 shown, the user interface 303 is mainly used to provide an input interface for the user and obtain the data input by the user; and the processor 301 can be used to call the application program stored in the memory 305 for an automatic recovery method after the network device loses connection. When executed by one or more processors 301, the electronic device 300 executes one or more of the methods described in the above embodiments. It should be noted that for the aforementioned method embodiments, for the sake of simple description, they are all expressed as a series of action combinations, but those skilled in the art should know that the present application is not limited by the described order of actions, because according to the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required for the present application.

[0178] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0179] In the several embodiments provided in this application, it should be understood that the disclosed devices can be implemented in other ways. For example, the device embodiments described above are only schematic, such as the division of units, which is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some service interfaces, and the indirect coupling or communication connection of devices or units can be electrical or other forms.

[0180] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0181] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

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

[0183] The above is only an exemplary embodiment of the present disclosure and cannot be used to limit the scope of the present disclosure. That is, any equivalent changes and modifications made according to the teachings of the present disclosure are still within the scope of the present disclosure. After considering the disclosure of the specification and practice, those skilled in the art will easily think of other embodiments of the present disclosure.

[0184] This application is intended to cover any variation, use or adaptation of the present disclosure, which follows the general principles of the present disclosure and includes common knowledge or customary technical means in the art not described in the present disclosure. The description and examples are to be regarded as exemplary only, and the scope and spirit of the present disclosure are defined by the claims.

Claims

1. A method for automatically recovering a network device after it loses connection, characterized in that: include: Acquire a network topology map corresponding to the target area, wherein the nodes of the network topology map correspond to the devices in the target area, and the edges of the network topology map correspond to the connection relationships between the devices; If it is determined that there is a disconnected node in the network topology diagram, a scheduling instruction is applied according to the disconnected node, and the disconnected node is repaired; The scheduling instruction is used to isolate the target data currently transmitted by the lost node, and to schedule the target data to be transmitted to a backup node in the network topology.

2. The automatic recovery method after network device loss of connection according to claim 1, characterized in that: The obtaining of a network topology map corresponding to the target area includes: Acquire device types of devices in the target area and connection relationships between the devices; Determine nodes and edges respectively according to device types and connection relationships of the devices; Generate a network topology graph based on the nodes and edges; The device types include a network management center and a network device, the network device includes a management control plane and a service forwarding plane, the network management center transmits control instructions to the network device through the management control plane, and transmits service data to the network device through the service forwarding plane; The connection relationship of the devices includes: at least one of the network devices establishes a communication connection with the network management center, and at least one of the network devices exchanges information through the network center.

3. The automatic recovery method after network device loss of connection according to claim 2 is characterized in that: Determining nodes and edges according to device types and connection relationships of the devices includes: Determine key nodes and common nodes according to device types and connection relationships of the devices, wherein the importance of the key nodes is greater than that of the common nodes; Determine a backup node according to the key node and the common node; The key nodes, the common nodes and the backup nodes are taken as nodes, and the connection relationships are taken as edges.

4. The automatic recovery method after network device disconnection according to claim 3 is characterized in that: Determining key nodes and common nodes, and common nodes and common edges according to the device type and connection relationship of each of the devices includes: Based on a first preset formula, calculating the importance of each of the devices through the device type and connection relationship of each of the devices; Determine the devices whose importance is greater than or equal to the threshold as key nodes, and determine the devices whose importance is less than the threshold as ordinary nodes; Among them, the first preset formula is: In the formula, R i Indicates the importance of device i, T i The device type coefficient of device i, n i Indicates the number of devices directly connected to device i, m i Indicates the number of devices indirectly connected to device i, K ij The connection type coefficient indicating that device i is directly connected to device j, K ik The connection type coefficient of device i indirectly connected to device k, C j Indicates the number of devices directly connected to device j, I k represents the number of devices indirectly connected to device k, λ and μ represent the corresponding weight coefficients, where the number of hops of the indirectly connected device is less than or equal to 3.

5. The automatic recovery method after network device loss of connection according to claim 3 is characterized in that: The step of determining a backup node according to the key node and the common node includes: Obtaining a propagation path of the key node; Taking a common node that can replace a key node in the propagation path as a target node; Obtaining the redundancy of the target node; If there is a target node whose redundancy is greater than the threshold, the target node whose redundancy is greater than the threshold is determined as a backup node; If there is no target node whose redundancy is greater than the threshold, load transfer is performed on the key node and the target node so that the redundancy of the target node is greater than the threshold.

6. The automatic recovery method after network device disconnection according to claim 1, characterized in that: The method further comprises: If the lost node is not a critical node, and there are at least two backup nodes corresponding to the lost node, the closeness of each backup node is calculated based on at least two of the path length, bandwidth and link load between each backup node and the lost node, and the backup node with the greatest closeness is used as the target backup node.

7. The automatic recovery method after network device loss of connection according to claim 1, characterized in that: The method further comprises: If the disconnected node is a key node, a minimum cut algorithm is used to determine a backup node.

8. An automatic recovery system after network equipment is disconnected, characterized in that: include: A network topology map acquisition module, used to acquire a network topology map corresponding to a target area, wherein nodes of the network topology map correspond to devices in the target area, and edges of the network topology map correspond to connection relationships between devices; A scheduling instruction application module is used to apply scheduling instructions according to the lost nodes and repair the lost nodes if it is determined that there are lost nodes in the network topology diagram; wherein the scheduling instructions are used to isolate the target data currently transmitted by the lost nodes, and schedule the target nodes to transmit the target data to the backup nodes in the network topology.

9. An electronic device, characterized in that: It includes a processor, a memory, a user interface and a network interface, the memory is used to store instructions, the user interface and the network interface are used to communicate with other devices, and the processor is used to execute the instructions stored in the memory so that the electronic device executes the method as described in any one of claims 1-7.

10. A computer storage medium, characterized in that: The computer storage medium stores instructions, and when the instructions are executed, the method according to any one of claims 1 to 7 is executed.

Images