Method, device and equipment for determining optimal emergency path of 5G network

Abstract

The embodiment of the invention provides a 5G network optimal emergency path determination method, device and equipment, and the method comprises the steps: obtaining network topology and network element operation management and control data related to a network replanning event in response to the detection of a network communication fault, and generating a directed topological graph; determining a target fault type corresponding to the network replanning event according to the directed topological graph and a fault content judgment template corresponding to each fault type; according to at least one first emergency path associated with a target fault node in the directed topological graph and the target fault type, determining overhead information of the at least one first emergency path; and according to the overhead information of all the to-be-selected paths, determining a target emergency path, and configuring network parameters for the target emergency path so as to establish network communication of the target fault node based on the reconfigured network parameters. And the optimal emergency path is automatically planned. Therefore, the fault judgment and repair efficiency is improved, and quick recovery of network transmission faults is guaranteed.

Description

Technical Field

[0001] This invention relates to the field of network maintenance technology, and in particular to a method, apparatus and equipment for determining the optimal emergency path for a 5G network. Background Technology

[0002] In the field of 5G transmission networks, infrastructure such as optical cables, pipelines and power may be affected by the natural environment, leading to optical cable interruptions and / or equipment power outages, which in turn cause multiple network outages.

[0003] In existing methods, emergency network recovery for multi-point network outages relies on manual experience for maintenance and communication reconstruction. This approach requires technicians to analyze the fault on-site, plan emergency routes, and configure services, resulting in low deployment efficiency, long processing times, and disruption of data transmission continuity. Summary of the Invention

[0004] This invention provides a method, apparatus, and device for determining the optimal emergency path in a 5G network, enabling automated generation of the optimal emergency path with short processing time, and ensuring rapid recovery from network transmission failures.

[0005] In a first aspect, embodiments of the present invention provide a method for determining the optimal emergency path in a 5G network, comprising:

[0006] In response to a network replanning event that detects a network communication failure, network topology and network element operation and control data associated with the network replanning event are acquired, and a directed topology graph is generated based on the network topology and network element operation and control data; wherein, the directed topology graph includes network core devices corresponding to the root node and user edge devices corresponding to the leaf nodes, and the faulty link is displayed in the directed topology graph in a first form;

[0007] Based on the directed topology graph and the fault content judgment template corresponding to each fault type in the pre-configured configuration, the target fault type corresponding to the network replanning event is determined;

[0008] Based on at least one first emergency path associated with the target fault node in the directed topology graph and the target fault type, determine the cost information of the at least one first emergency path;

[0009] Based on the cost information of all candidate paths, a target emergency path is determined, and network parameters are configured for the target emergency path to establish network communication for the target fault node based on the reconfigured network parameters.

[0010] Secondly, embodiments of the present invention also provide a 5G network optimal emergency path determination device, comprising:

[0011] A directed topology graph generation module is used to respond to a network replanning event that detects a network communication failure, acquire network topology and network element operation and control data associated with the network replanning event, and generate a directed topology graph based on the network topology and network element operation and control data; wherein, the directed topology graph includes network core devices corresponding to the root node and user edge devices corresponding to the leaf nodes, and the faulty link is displayed in the directed topology graph in a first form;

[0012] The target fault type determination module is used to determine the target fault type corresponding to the network replanning event based on the directed topology graph and the fault content judgment template corresponding to each fault type in the pre-configured configuration.

[0013] The overhead information determination module is used to determine the overhead information of the at least one first emergency path based on the target fault node associated with the target fault node in the directed topology graph and the target fault type.

[0014] The network communication establishment module is used to determine the target emergency path based on the cost information of all candidate paths, and configure network parameters for the target emergency path to establish network communication for the target fault node based on the reconfigured network parameters.

[0015] Thirdly, embodiments of the present invention also provide an electronic device, comprising:

[0016] At least one processor; and

[0017] A memory that is communicatively connected to at least one processor; wherein,

[0018] The memory stores a computer program that can be executed by at least one processor, such that the at least one processor can perform a method for determining the optimal emergency path for a 5G network as provided in any embodiment of the present invention.

[0019] Fourthly, embodiments of the present invention also provide a computer-readable storage medium storing computer instructions for causing a processor to execute a method for determining the optimal emergency path for a 5G network as provided in any embodiment of the present invention.

[0020] Fifthly, embodiments of the present invention also provide a computer program product, including a computer program that, when executed by a processor, implements the 5G network optimal emergency path determination method as described in any of the embodiments of this disclosure.

[0021] The technical solution provided in this invention, in response to a network replanning event detecting a network communication failure, firstly acquires network topology and network element operation and management data associated with the network replanning event, and generates a directed topology graph based on the network topology and network element operation and management data. The network and network element operation and management data are transformed into a directed topology graph for subsequent automated path planning. Further, a pre-configured fault content judgment template is acquired, and the target fault type corresponding to the network replanning event is determined based on the directed topology graph and the fault content judgment template corresponding to each fault type. By automatically configuring the fault content judgment template, the system can quickly and accurately determine the target fault type. Further, based on at least one first emergency path associated with the target fault node in the directed topology graph and the target fault type, the cost information of at least one first emergency path is determined. Based on the cost information of all candidate paths, a target emergency path is determined, and network parameters are configured for the target emergency path. Network communication with the target fault node is established based on the reconfigured network parameters. Based on the cost information of all candidate paths, automatic planning and selection of the optimal emergency path are achieved. This improves fault diagnosis and repair efficiency, shortens communication reconstruction time, and ensures rapid recovery from network transmission failures.

[0022] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0023] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0024] Figure 1 A flowchart illustrating a method for determining the optimal emergency path in a 5G network, as provided in this embodiment of the invention;

[0025] Figure 2 This is a schematic diagram of a directed topological graph provided in an embodiment of the present invention;

[0026] Figure 3 This is a schematic diagram illustrating different fault types provided in an embodiment of the present invention;

[0027] Figure 4 A flowchart illustrating a method for determining the optimal emergency path in a 5G network, as provided in this embodiment of the invention;

[0028] Figure 5This is an overall framework diagram of a method for determining the optimal emergency path in a 5G network, provided by an embodiment of the present invention.

[0029] Figure 6 This is a schematic diagram illustrating the determination of a target fault type according to an embodiment of the present invention;

[0030] Figure 7 This is a schematic diagram of the structure of a 5G network optimal emergency path determination device provided in an embodiment of the present invention;

[0031] Figure 8 A schematic diagram of the structure of an electronic device 10 that can be used to implement an embodiment of the present invention is shown. Detailed Implementation

[0032] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0033] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0034] Before introducing the technical solutions provided in the embodiments of this invention, an exemplary application scenario can be given first. In 5G bearer networks, Segment Routing Traffic Engineering (SRTP) tunneling technology is mainly used to carry critical backhaul services from base stations to the core network. When network infrastructure failures, such as optical cables, pipelines, and power supply failures, cause multiple network outages, the SRTP tunnels relying on the original paths become invalid, leading to base station service interruptions. Therefore, to ensure timely service recovery, when the original path cannot be repaired in time, an alternative service path needs to be rebuilt. That is, after a failure occurs, an alternative channel is physically established from the User-facing Provider Edge (UPE) to the Service Provider Edge (SPE), and then to the Network Provider Edge (NPE). Once the physical link is ready, through the interaction of the Interior Gateway Protocol (IGP), devices such as the user side, aggregation point, and core landing node learn the reachable routes via the new path. Furthermore, the IGP routes are refreshed to the centralized cloud network management system. Finally, the cloud-based network management controller recalculates the SRTP tunnel and sends the result to the devices to restore service.

[0035] Figure 1 This is a flowchart illustrating a method for determining the optimal emergency path in a 5G network, provided by an embodiment of the present invention. This embodiment is applicable to situations where a network communication failure is detected, and the optimal emergency path is determined. The method is executed by a 5G network optimal emergency path determination device, which can be implemented in hardware and / or software. This 5G network optimal emergency path determination device can be configured in a computing device. Figure 1 As shown, the method includes:

[0036] S110. In response to a network replanning event that detects a network communication failure, obtain network topology and network element operation and control data associated with the network replanning event, and generate a directed topology graph based on the network topology and network element operation and control data.

[0037] The directed topology graph includes the network core device corresponding to the root node and the user edge device corresponding to the leaf node. Faulty links are displayed in the first form in the directed topology graph.

[0038] In this embodiment, network communication failures can be physical layer failures, i.e., the loss of physical connection between devices. For example, physical layer failures can be fiber optic cable breaks, device power outages, hardware failures, or port failures. When a network communication failure is detected, network replanning is required. A network replanning event can be understood as initiating a calculation and configuration process to re-establish usable transmission paths for services affected by the failure. Network topology and network element operation management data can be understood as the structure of devices in the network, the physical or logical connections between devices, and information such as the operating status, performance indicators, and configuration parameters of individual devices. Devices can be routers, switches, and servers, etc. Network topology and network element operation management data can be data reflecting the actual network connection status obtained from the network management system, as well as relevant parameters of each device.

[0039] A directed topology graph can be a data model used to represent the relationships between nodes. In this embodiment, nodes in the directed topology graph can represent network devices, including but not limited to the network core device corresponding to the root node and the user edge device corresponding to the leaf nodes. The root node can be understood as the final source of traffic in the directed graph, and the network core device can be a device responsible for high-speed data exchange and connected to the core network as the final network exit. Leaf nodes are located at the edges of the directed topology graph, and user edge devices are devices located at the edges of the directed topology graph, acting as traffic terminals, usually the endpoints of service paths. Directed edges can represent the connection relationships between devices and indicate the direction of data flow. A faulty link can be a network connection that cannot carry data due to a physical terminal. The first form can be understood as a visual identifier used to represent faulty links in the generated directed topology graph, such as using an icon to represent that the path where the icon is located is a faulty link.

[0040] For example, Figure 2 This is a schematic diagram of a directed topology graph provided in an embodiment of the present invention. For example... Figure 2 As shown, the directed topology graph is generated from network topology and network element operation and management data. In the directed topology graph, the direction of backbone aggregation devices is the root direction, and the direction of user edge devices is the leaf direction. The physical links of network elements in the network topology and network element operation and management data are used as edges in the directed topology graph. The numbers marked on the links represent cost information. See also Figure 2 The cost between node N and node M is 20. Based on the network environment, faulty links are marked using fault network identifiers in the directed topology graph. For example, if the link between node J and node H is interrupted, it is a faulty link.

[0041] Specifically, when the system detects a network communication failure, network replanning is required. This involves acquiring network topology and network element operation and management data, and generating a directed topology graph. Network elements and their corresponding network connections are then extracted from the network topology and network element operation and management data. Core network devices are designated as root nodes, user edge devices as leaf nodes, and faulty links are marked at the points of failure in the directed topology graph.

[0042] Before generating a directed topology graph, network topology and network element operation and management data need to be obtained. The following section elaborates on the data contained in the network topology and network element operation and management data. Optionally, the network topology and network element operation and management data may include at least one or more of the following: internal gateway protocol process and overhead data to which physical links belong, physical link bandwidth utilization, and network element management plane information data.

[0043] The Interior Gateway Protocol (IGP) process can be an IGP instance running on a network device. This can be understood as network administrators dividing the network into multiple processes to manage a large network. The IGP process to which a physical link belongs can be the IGP instance carrying that physical link. The IGP can be a metric assigned to each physical link by the IGP, used to measure the cost of using that link. Overhead data includes, but is not limited to, bandwidth and latency. Physical link bandwidth utilization can be the percentage of currently used bandwidth on a physical link relative to the total available bandwidth. This parameter can characterize a real-time performance indicator of network congestion. Network element management plane information data can be data related to configuring, monitoring, maintaining, and diagnosing faults in network devices.

[0044] Specifically, the acquired network topology and network element operation and management data includes, but is not limited to, internal gateway protocol and cost data of physical links, physical link bandwidth utilization, and information data within network elements. Obtaining live network topology and network element operation and management data is convenient for determining the optimal path. This data is readily available, requires no secondary conversion, and is easy and reliable to collect.

[0045] S120. Based on the directed topology graph and the fault content judgment template corresponding to each fault type in the pre-configured settings, determine the target fault type corresponding to the network replanning event.

[0046] The fault type can be categorized based on its cause and characteristics. The fault content judgment template is a pre-set template. This template can be pre-defined for each fault type. The target fault type is determined by comparing the current fault condition with all pre-configured fault content judgment templates to identify the matching fault category. Specifically, the target fault type is one of the fault types included in the fault content judgment template.

[0047] Based on different fault types, generate fault content judgment templates. Optionally, the fault content judgment templates include, but are not limited to, unreachable fault types within the same access IGP domain, unreachable fault types across IGPs within the same backbone aggregation, unreachable fault types across SPEs in the backbone aggregation, and unreachable fault types between SPEs and NPEs in the core IGP domain.

[0048] Among them, see Figure 3 (a) The "unreachable within an access IGP domain" fault type can be that the fault occurs within an access IGP domain. An access IGP domain can be understood as an internal gateway protocol area in the network close to the user side or base station side. For example, an IGP domain can consist of user-side edge devices and backbone aggregation devices responsible for access aggregation, handling the access and initial aggregation of mid-range services. Backbone aggregation devices can be devices in the network responsible for aggregating lower-layer traffic and implementing forwarding policies; these devices can be relay nodes between the access layer and the core layer. See also... Figure 3 (b) Cross-IGP unreachability faults within the same backbone aggregation device can occur when the fault occurs on the same backbone aggregation device, causing routing interruptions between these multiple IGP domains because the device connects to multiple different IGP domains. See also Figure 3 (c) Cross-backbone aggregation SPE unreachable fault type can be a path device that crosses the backbone aggregation layer. For example, a link interruption connecting two different backbone aggregation devices, preventing services from reaching each other, is an example of a cross-backbone aggregation SPE unreachable fault type. See also Figure 3 (d) The unreachable fault type of the core IGP domain SPE / NPE can be a failure of the backbone aggregation equipment and / or network core equipment in the core domain, or a link interruption connecting the backbone aggregation equipment and / or network core equipment in the core domain.

[0049] Specifically, after a network replanning event is triggered, the system generates a directed topology graph reflecting the current fault status. It then calls a pre-configured fault content judgment template. The fault content present in the directed topology graph is matched with the fault content judgment template to determine the target fault type corresponding to the network replanning event.

[0050] S130. Based on at least one first emergency path associated with the target fault node in the directed topology graph and the target fault type, determine the cost information of at least one first emergency path.

[0051] The first emergency path is the transmission path planned by the system to restore services, which avoids the target faulty node. The target faulty node is the node identified in the directed topology graph, representing the location of the network replanning event. The cost information of the first emergency path is the transmission cost calculated for the first emergency path.

[0052] Specifically, the target fault node is identified in the directed topology graph, and the first emergency path associated with the target fault node is obtained. Based on a pre-configured fault content template, the corresponding target fault type is determined. Based on at least one first emergency path and its corresponding target fault type, the cost message for each first emergency path is calculated.

[0053] Furthermore, the calculation method for the cost information of the first emergency path associated with the target fault point based on the directed topology graph is described in detail. Optionally, based on at least one first emergency path associated with the target fault node in the directed topology graph and the target fault type, the cost information of at least one first emergency path is determined, including:

[0054] Based on the cumulative utilization rate of the link bandwidth corresponding to at least one first emergency path, determine the utilization rate weight; based on the target fault type, determine the fault type weight; based on the influence factor value of the link bandwidth utilization rate and the corresponding utilization rate weight, determine the first value; and based on the type influence value corresponding to the target fault type and the corresponding fault type weight, determine the second value; based on the first value and the second value of each first emergency path, determine the cost information of each first emergency path.

[0055] In this embodiment, the cumulative link bandwidth utilization rate can be a calculation parameter used in the calculation of the first emergency path overhead information, used to assess the expected percentage of total bandwidth utilization of the first emergency path. It can be noted that calculating the cumulative link bandwidth utilization rate requires obtaining the emergency link's occupied bandwidth, the maximum occupied bandwidth in the fault set links before the failure, and the maximum port bandwidth of the emergency link. The calculation process for the cumulative link bandwidth utilization rate is: Cumulative Link Bandwidth Utilization Rate = (Emergency Link Occupied Bandwidth + Maximum Occupied Bandwidth in the Fault Set Links Before the Failure) / Maximum Port Bandwidth of the Emergency Link. Wherein, the emergency link's occupied bandwidth can be the bandwidth currently occupied by the existing service traffic on the first emergency path. The maximum occupied bandwidth in the fault set links before the failure can be the bandwidth occupied by the final segment of the link from the failed service path. The maximum port bandwidth of the emergency link can be the total bandwidth capacity of the physical ports of the first emergency path.

[0056] In this embodiment, the utilization weight can be a weight coefficient dynamically set based on the cumulative utilization rate of the link bandwidth corresponding to the first emergency path. The larger the cumulative utilization rate of the link bandwidth, the greater the percentage of total bandwidth usage expected to be achieved by the link, and the greater the utilization weight of the link.

[0057] For example, the baseline value of the utilization weight corresponding to the cumulative link bandwidth utilization rate is 1, and different utilization weights corresponding to different cumulative link bandwidth utilization rates are preset. Table 1 is a utilization weight table corresponding to the cumulative link bandwidth utilization rate provided in the embodiments of the present invention:

[0058]

[0059] In this embodiment, the fault type weight can be a coefficient that is dynamically set according to the target fault type, and the fault type weights are different for different target fault types.

[0060] For example, taking the four typical fault scenarios in the fault content judgment template as examples, when the fault type is judged as "unreachable fault type within the same access IGP domain", it is judged that the fault is located within a single access domain and the scope of impact is limited; when the fault type is judged as "unreachable fault type across IGPs in the same backbone aggregation", the fault occurs in the backbone aggregation device, causing service interruption between multiple access IGP domains under the backbone aggregation device, so the weight of this scenario can be greater than the weight of unreachable fault type within the same access IGP domain; when the fault type is judged as "unreachable fault type across backbone aggregation SPE", it represents the interruption of the association between the backbone aggregation layers, and the scope of impact spans multiple aggregation areas; when the fault type is judged as "unreachable fault type of core IGP domain SPE / NPE", it represents the failure of the network core link. Therefore, the fault type weights for the four fault scenarios—unreachable fault type in the same access IGP domain, unreachable fault type across IGP in the same backbone aggregation, unreachable fault type across SPE in the backbone aggregation, and unreachable fault type in the core IGP domain SPE / NPE—are 1, 1.2, 1.4, and 1.6, respectively.

[0061] In this embodiment, the first value can be calculated from the utilization weight using the influence factor value of link bandwidth utilization. This represents the performance risk cost of selecting the first emergency path; the higher the value, the greater the risk. The influence factor of link bandwidth utilization represents the degree of influence of link bandwidth utilization in the cost information calculation process. The second value can be calculated from the type influence value corresponding to the target fault type and the fault type weight. This represents the cost required to deal with this type of fault. The higher the second value, the higher the required cost. The type influence value corresponding to the target fault type can be the degree of influence of the fault type in the cost information calculation process. It can be noted that the influence factor value of link bandwidth utilization and the type influence value corresponding to the target fault type can be preset. For example, the influence factor value of link bandwidth utilization can be set to 0.8, and the type influence value corresponding to the target fault type can be set to 0.2.

[0062] In this embodiment, the cost information of each first emergency path can be determined by a first value and a second value for each emergency path. The first emergency cost information is obtained by multiplying the link adjustment weight by the actual link cost. It can be noted that the actual link cost can be a pre-set first emergency link cost, such as uniformly setting the actual link cost to 8000. The link adjustment weight is obtained based on the first value and the second value of each emergency path.

[0063]

[0064] Where W is the link adjustment weight corresponding to the emergency path, and n is 2 in this embodiment. As the impact factor, This refers to the sub-weights of each influencing factor. It can be explained that... middle As a factor affecting link bandwidth utilization, The type impact value corresponding to the target fault type. middle As a utilization rate weight, The weights are for different fault types.

[0065] Specifically, the cumulative utilization rate of link bandwidth corresponding to all first emergency paths is obtained, and the matching utilization rate weight is determined based on the cumulative utilization rate. The target fault type is obtained, and the corresponding fault type weight is matched. Further, the pre-set influence factor values ​​of link bandwidth utilization and the type influence values ​​corresponding to the target fault type are obtained. A first value is calculated based on the influence factor values ​​and utilization rate weights of the link bandwidth utilization. A second value is calculated based on the type influence values ​​and fault type weights corresponding to the target fault type. The link adjustment weight is calculated based on the first and second values. The cost information of the first emergency path is finally determined based on the link adjustment weights and the actual link cost. By introducing a multi-factor weighted algorithm to calculate the cost information of each first emergency path, the fault type and the cumulative utilization rate of link bandwidth for each emergency path are obtained. This is used to determine the optimal emergency path, optimize resource scheduling, improve the accuracy of the system's emergency path determination, and ensure the long-term operational stability of the network after recovery.

[0066] S140. Based on the cost information of all candidate paths, determine the target emergency path and configure network parameters for the target emergency path to establish network communication for the target fault node based on the reconfigured network parameters.

[0067] The cost information of the candidate paths can be a quantified value calculated for each candidate first emergency path through multi-factor weighting, representing the total cost of each candidate path, and used to determine the target emergency path. The target emergency path can be the optimal emergency path selected from all candidate paths based on the cost information. Optionally, the candidate path with the lowest cost information can be selected as the target emergency path.

[0068] Network parameters can be a series of control commands and configuration changes issued to relevant network devices to enable data forwarding along the target emergency path. Establishing network communication for the target faulty node can be achieved by deploying the target emergency path and applying reconfigured network parameters to restore services interrupted by the target faulty node.

[0069] Specifically, the cost information of all candidate paths calculated by the algorithm is obtained. Based on preset principles, a target emergency path for restoring communication is determined. According to the selected target emergency path, the network parameters to be sent are determined. The network parameters are sent to the devices to complete the reconfiguration of the network parameters. Finally, new network communication is established based on the reconfigured network parameters.

[0070] Next, the specific configuration process of network parameters will be described in detail. First, both ends of the selected target emergency path automatically obtain IP addresses from the emergency recovery Internet Protocol (IP) resource pool. This ensures that the emergency link obtains an IP address. Multiprotocol Label Switching (MPLS) is automatically enabled on the ports at both ends of the target emergency path to build the data forwarding foundation for all subsequent high-layer tunnels and provide label switching capabilities. The ports at both ends of the selected target emergency path are automatically added to the IGP process, enabling the control plane to be aware of the new link and incorporate it into the routing calculation topology. A virtual interface LB_I is automatically generated on the backbone aggregation node in the selected emergency path, automatically obtains an IP address from the emergency recovery IP resource pool, and is automatically added to the IGP process. A virtual interface LB_J is automatically generated on the node where the target failure occurs, added to the IGP process, and matched with LB_I to form a logically direct link across the failure area. Furthermore, pseudowires of the bearer protocol of the selected target emergency path are deployed, and the IGP protocol of the LB_I and LB_J virtual interfaces is carried through PW to complete the integrity refresh of the IGP process routing on the backbone aggregation device. Finally, the access tunnel from the backbone aggregation device to the target fault node of the IGP process automatically completes the cross-domain bypass of network elements and completes the service continuity.

[0071] The emergency recovery IP resource pool can be a set of IP addresses pre-planned by the network administrator and dedicated to emergency fault scenarios, used to isolate it from the daily business network. Multiprotocol Label Switching (MPLS) is a technology that uses labels to guide high-speed datagram forwarding in a communication network. It establishes a forwarding path by pushing labels onto data packets at the network ingress, switching them at intermediate nodes based on the labels, and popping the labels at the egress. A virtual interface can be a logical interface created at the software level of a network device. A pseudowire is a tunneling technology that simulates various Layer 2 or Layer 3 services end-to-end on a packet-switched network.

[0072] The technical solution provided in this invention, in response to a network replanning event detecting a network communication failure, firstly acquires network topology and network element operation and management data associated with the network replanning event, and generates a directed topology graph based on the network topology and network element operation and management data. The network and network element operation and management data are transformed into a directed topology graph for subsequent automated path planning. Further, a pre-configured fault content judgment template is acquired, and the target fault type corresponding to the network replanning event is determined based on the directed topology graph and the fault content judgment template corresponding to each fault type. By automatically configuring the fault content judgment template, the system can quickly and accurately determine the target fault type. Further, based on at least one first emergency path associated with the target fault node in the directed topology graph and the target fault type, the cost information of at least one first emergency path is determined. Based on the cost information of all candidate paths, a target emergency path is determined, and network parameters are configured for the target emergency path. Network communication with the target fault node is established based on the reconfigured network parameters. Based on the cost information of all candidate paths, automatic planning and selection of the optimal emergency path are achieved. This improves fault diagnosis and repair efficiency, shortens communication reconstruction time, and ensures rapid recovery from network transmission failures.

[0073] Figure 4 This is a flowchart illustrating a method for determining the optimal emergency path in a 5G network, provided by an embodiment of the present invention. This embodiment, based on the aforementioned embodiments, elaborates in detail on the method for determining the target fault type. For example... Figure 4 As shown, the method includes:

[0074] S210. Determine the initial fault dataset based on the target fault node and at least one IGP domain type in the directed topology graph.

[0075] The target fault node includes a fault network identifier and the IGP domain to which the target fault node belongs. The initial fault dataset includes at least one set of first data, which includes the IGP domain, the faulty network element, the second path, and the SPE / NPE pair. The faulty network element is related to the target fault node.

[0076] In this embodiment, the internal gateway protocol domain type can be a classification of internal gateway protocol areas, including but not limited to access IGP domains, aggregation IGP domains, and core IGP domains. Specifically, an access IGP domain can be an edge area close to a user or base station; an aggregation IGP domain can be an intermediate area aggregating inbound traffic; and a core IGP domain can be a network central switching area. The initial fault dataset can be a set of raw fault information collected from the IGP domains to which the target fault node belongs and related to it. The initial fault dataset is determined by the target fault node and at least one internal gateway protocol domain type in the directed topology graph. The target fault node includes a fault network identifier and the internal gateway protocol domain to which the target fault node belongs. The fault network identifier can be an identifier that uniquely identifies the faulty object in the directed topology graph. The internal gateway protocol domain to which the target fault node belongs can be the IGP domain to which the target fault node belongs. The initial fault dataset includes at least one set of first data. The first data can be understood as data related to the target fault node in the initial fault dataset, representing the path from the target fault node to the network core.

[0077] It can be noted that the first data includes an IGP domain, a faulty network element, a second path, and an SPE / NPE pair. The IGP domain can be the IGP domain to which the target faulty node belongs, and the faulty network element can be a network device associated with the target faulty node obtained from the initial fault dataset. The second path can be an alternative route from the faulty network element to the network core, and the SPE / NPE pair can be a pair of aggregation devices and core devices with an association in the directed topology graph.

[0078] Specifically, the system obtains the target faulty node and at least one Interior Gateway Protocol (IGP) domain type from the directed topology graph. Based on the target faulty node and the directed topology graph, it obtains the IGP domain, faulty network element, second path, and SPE / NPE pair, using this data as at least one set of first data in the initial fault dataset. Simultaneously, it obtains the faulty network identifier in the target faulty node and the IGP domain to which the target faulty node belongs.

[0079] S220. Read at least two faulty network elements in the initial fault dataset that are closest to the root node; where the distance is determined based on the path length from the faulty network element to the core domain root node.

[0080] In this embodiment, the root node can be a core device defined as the starting point for path calculation in a directed topology graph. The distance can be the path length from a faulty network element to the root node. For example, if the number of network hops required to travel from the faulty network element to the root node is 2, then the distance to the root node is 2.

[0081] Specifically, the system calculates the distance of each faulty network element in the initial fault dataset from the root node, sorts them by distance from smallest to largest, and selects at least two faulty network elements with the highest ranking.

[0082] S230. Search for at least one neighboring network element along the direction of the root node with at least two faulty network elements, and select the neighboring network element with the lowest cost to reach at least one neighboring network element as the preferred network element.

[0083] In this context, adjacent network elements can be the next device that has a physical connection with at least two selected faulty network elements, used to determine candidate emergency paths. The preferred network element can be the adjacent network element with the lowest cost among all adjacent network elements of the faulty network element after cost comparison. Cost can be the expense data for traveling from a faulty network element to an adjacent network element, which can be obtained from network topology and network element operation and management data.

[0084] Specifically, at least two neighboring network elements along the direction of the root node are identified from the faulty network element. Simultaneously, the cost of reaching at least one neighboring network element from the faulty network element is determined. The neighboring network element with the lowest cost to reach at least one neighboring network element is selected as the preferred network element.

[0085] S240. Using the preferred network element as the source network element, search towards the leaf nodes to determine the target fault type.

[0086] In this context, the source network element can be understood as the starting point of the path, meaning the search proceeds along the leaf nodes from the source network element. Searching along the leaf nodes can be understood as performing a directed traversal algorithm in the directed topology graph, starting from the source network element and searching towards the network edge.

[0087] Specifically, the preferred network element is obtained, and the preferred network element is used as the source network element to search towards the leaf nodes, thereby determining the target fault type.

[0088] Next, based on the process of searching towards the leaf nodes, the method for determining the target fault type is described in detail. Optionally, the preferred network element is used as the source network element for searching towards the leaf nodes, including:

[0089] If the source network element is located in an access domain, all SPE pairs in the access domain are recorded, and all IGP domain network elements along the leaf nodes of the source network element are traversed to generate a path data list. If the source network element is located in a core domain or backbone aggregation domain, all network elements in the IGP domain are traversed along the leaf nodes with the source network element as the starting node to generate a path data list. The path data list includes the source network element and the leaf network elements.

[0090] The access domain can be the network edge, directly connecting to users or base stations. The domain of the source network element can be the internal gateway protocol area type to which the preferred network element belongs. The SPE pair data can be the pairing information of backbone aggregation devices with related relationships. The path data list can be the path information from the source network element to the network elements belonging to each leaf node.

[0091] Specifically, the first step is to determine the domain of the source network element. If the source network element is in an access domain, all SPE pairs in the access domain are retrieved. Further, all IGP domain network elements along the leaf nodes of the source network element are traversed to generate a path data list including both the source and leaf network elements. If the source network element is in a core domain or backbone aggregation domain, all network elements within the IGP domain are traversed along the leaf nodes starting from the source network element, generating a path data list including both the source and leaf network elements. Determining the domain of the source network element provides accurate input for fault template matching, and the lists generated through different strategies improve the accuracy of matching different fault types.

[0092] After obtaining the path data list, the target fault type is further determined based on the data in the path data list. Optionally, the method also includes:

[0093] Based on the initial fault dataset and path data list, determine whether a shared network element identifier exists. If it exists, send the reachability identifier, the SPE / NPE pair associated with the leaf network element, and the IGP domain number to the scenario classification judgment module to determine the target fault type. If it does not exist, send the unreachability identifier and the current IGP domain type to the domain type verification module to determine whether only the core domain exists, and determine the target fault type based on the judgment result.

[0094] The shared network element identifier can be the unique identifier of the network device that appears in both the initial fault dataset and the path data list. The shared network element identifier indicates that a network element associated with the fault exists in the path data list. The reachability identifier can be a judgment flag sent to the downstream judgment module, indicating that a fault-associated network element has been found and the service path is clearly interrupted. The SPE / NPE pair associated with the leaf network element can be the SPE / NPE pair to which the network element closer to the leaf direction belongs under normal communication conditions in the path data list. Obtaining the SPE / NPE pair associated with the leaf network element is used to distinguish whether it is a cross-domain fault scenario.

[0095] The scenario classification and judgment module can be used to determine the specific fault type. This module sets a fault content judgment template and uses it to determine the fault type when the fault is physically reachable. The domain type verification module can be used to determine the specific fault type when the fault is physically unreachable.

[0096] Specifically, the initial fault dataset and path data list are obtained. The initial fault dataset and path data list are compared to determine if a shared network element identifier exists between them. If a shared network element identifier exists, it indicates that the faulty network element in the initial fault dataset exists in the path data list, meaning it is physically reachable. Further, the reachability identifier, the SPE / NPE pair associated with the leaf network element, and the IGP domain number are sent to the scenario classification judgment module for further judgment. If no shared network element identifier exists, it indicates that the faulty network element in the initial fault dataset does not have a shared network element identifier, meaning it is physically unreachable. Further, the unreachability identifier and the current IGP domain type are sent to the domain type verification module to determine if only the core domain exists. If it is not only the core domain, adjacent network elements are re-determined, and a search is initiated towards the leaf nodes. If only the core domain exists, a "No Path" identifier is displayed, indicating that no feasible path meeting the conditions was found. By comparing shared network element identifiers, the fault type determination process becomes a multi-dimensional data verification process, improving the accuracy of fault type determination.

[0097] After determining that physical reachability exists, the reachability identifier, the SPE / NPE pair associated with the leaf network element, and the IGP domain number are sent to the scenario classification and judgment module. Next, the process by which the scenario classification and judgment module determines the target fault type is described. Optionally, based on the scenario classification and judgment module, the target fault type is determined, including:

[0098] Determine whether only the core domain exists; if so, determine the target fault type as the core IGP domain SPE / NPE unreachable fault type; if not, compare the SPE pairs associated with the leaf network elements with the SPE pairs in the initial fault dataset, so that if the comparison results are inconsistent, the target fault type is determined as the cross-backbone aggregation SPE unreachable fault type.

[0099] The question of whether only the core domain exists can be understood as determining whether the scope of the fault's impact is limited to the core IGP domain. The comparison can be understood as whether the SPE pairs associated with leaf network elements are consistent with the SPE pairs in the initial fault dataset.

[0100] Specifically, in the scenario classification and judgment module, based on the SPE / NPE pairs associated with leaf network elements, IGP domain numbers, and the initial fault dataset, it is determined whether only the core domain exists. If only the core domain exists, indicating that the fault is limited to the core domain, the target fault type is directly determined as the core IGP domain SPE / NPE unreachable fault type. If it does not exist only in the core domain, the SPE pairs associated with leaf network elements are further compared with the SPE pairs in the initial fault dataset. If the comparison is inconsistent, it indicates that the transmission equipment between SPE pairs in different IGP domains is interrupted, and the target fault type is determined as the cross-backbone aggregation SPE unreachable fault type. The scenario classification and judgment module determines whether only the core domain exists. When it does not exist only in the core domain, a comparison is introduced between the SPE pairs associated with leaf network elements and the SPE pairs in the initial fault dataset to further determine the target fault type. Considering the comparison and judgment of the core domain and SPE pairs improves the accuracy of the target fault type determination.

[0101] Furthermore, the SPE pairs associated with the leaf elements are compared with the SPE pairs in the initial fault dataset. When the comparison results are the same, the method may also include:

[0102] If the comparison results of the SPE pair associated with the leaf network element and the SPE pair in the initial fault dataset are the same, compare the IGP domain number where the leaf network element is located with the IGP domain number in the initial fault dataset; if the comparison results are inconsistent, determine the target fault type as the cross-IGP unreachable fault type of the same backbone aggregation; if the comparison results are consistent, determine the target fault type as the unreachable fault type of the same access IGP domain.

[0103] The IGP domain number can be the identifier of the internal gateway protocol zone to which the leaf element belongs in the path data list.

[0104] Specifically, when the comparison result of the SPE pair associated with the leaf network element and the SPE pair in the initial fault dataset is the same, the IGP domain number of the leaf network element and the IGP domain number in the initial fault dataset are obtained. These two IGP domain numbers are compared. If the comparison result is inconsistent, it indicates that the fault occurred on the same backbone aggregation device, and routing was interrupted between multiple IGP domains connected to the backbone aggregation device. The target fault type is then determined to be a cross-IGP unreachable fault type within the same backbone aggregation device. When the comparison result is the same, it indicates that the fault occurred within an access IGP domain. The target fault type is then determined to be an unreachable fault type within the same access IGP domain. By introducing the comparison of the IGP domain number of the leaf network element with the IGP domain number in the initial fault dataset, the judgment of whether it is within the same access IGP domain is added. This achieves range delimitation of the fault type and ensures accurate judgment of the target fault type.

[0105] The technical solution provided in this invention obtains the target fault node and a directed topology graph. Based on the target fault node and the internal gateway protocol domain, faulty network element, second path, and backbone aggregation device / network core device pairs in the directed topology graph, an initial fault dataset is generated. At least two faulty network elements closest to the root node are read from the initial fault dataset. At least one neighboring network element is searched along the direction of the root node using these two faulty network elements, and the cost of at least one neighboring network element is determined. The neighboring network element with the lowest cost to reach at least one neighboring network element is selected as the preferred network element. Further, the preferred network element is used as the source network element to search towards the leaf nodes, and fault type judgment is performed sequentially to finally determine the target fault type. By determining the target fault type hierarchically, accurate matching of fault types is achieved, improving the accuracy of optimal path determination and increasing fault recovery speed.

[0106] Figure 5 This is an overall framework diagram of a 5G network optimal emergency path determination method provided by an embodiment of the present invention, combined with... Figure 5 Understand the technical solutions of the embodiments of the present invention.

[0107] like Figure 5 As shown, the embodiments of the present invention explain the overall implementation of the scheme based on the above optional implementation methods. Specifically, it includes:

[0108] Users can perform optimal emergency path planning for the 5G network via an app on their mobile phones and / or computers. First, the application-layer emergency recovery app extracts faulty network data from the cloud-based network management system and receives manually input data on faults or potential hazards, as well as link information (IGP) routing data. Based on this data, data annotation is performed to generate network topology and network element operation and management data. Finally, a topology map (directed topology graph) is reconstructed based on the network topology and network element operation and management data.

[0109] Furthermore, fault type analysis is performed based on pre-configured fault content judgment templates to determine the target fault type. Figure 6 This is a schematic diagram illustrating the determination of a target fault type according to an embodiment of the present invention. Figure 6As shown, a fault set (initial fault dataset) FSet_IGP2 is determined based on the target fault node (fault point) and the directed topology graph. At least two faulty network elements closest to the root node are obtained. Using these two closest faulty network elements, a search is performed towards the root direction, with a search step size of one network element. The optimal network element with the minimum cost is determined. Using the newly found optimal network element as the source, a search is performed towards the leaves. After finding multiple paths in the first search, they are divided into different sets according to the IGP domain, generating a path data list. The path data list is compared with the initial fault dataset. If no physical reach is found in the first search, an incremental search is required in the second search. If physical reachability exists, it is determined whether the faulty network element belongs to the core domain. If the faulty network element is deployed in the core domain, the search ends when a SPE pair belonging to the same IGP domain as the faulty network element is found. The access domain records the SPE pairs, and the set of network elements in the IGP domains in the leaf direction is traversed. It is determined whether the IGP set and the fault set in the leaf direction are physically reachable. If no physical reachability exists, it is determined whether only the core domain exists. If the core domain exists, the search continues towards the leaf domains. If only the core domain exists, the analysis ends. If the IGP set (path data list) in the leaf domain direction is physically reachable from the fault set (initial fault dataset), further determine if only the core domain exists. If so, determine the target fault type as a core IGP domain SPE / NPE unreachable scenario (core IGP domain SPE / NPE unreachable fault type). If it is not only the core domain, determine if the SPE pair associated with the fault is consistent. If not, determine the target fault type as a cross-backbone aggregation SPE unreachable scenario (cross-backbone aggregation SPE unreachable fault type). If it is consistent with the SPE pair in the fault set, determine if it is consistent with the fault set IGP number (IGP domain number). If not, determine the target fault type as a same-backbone aggregation IGP unreachable scenario (same-backbone aggregation IGP unreachable fault type). If consistent, determine the target fault type as a same-access IGP domain unreachable scenario (same-access IGP domain unreachable fault type). After determining the target fault type, store the directed graph list of physical paths. Once the completion conditions are met, i.e., the target fault type is determined, the analysis ends.

[0110] After obtaining the target fault type, the cost information of the path is calculated based on the target fault type, network topology, and network element operation and management data using a multi-factor weighted algorithm. Finally, based on the path cost information, the target emergency path is determined, and the configured emergency path information is transmitted to the cloud-based network management system and the municipal / prefecture-level Slicing Packet Network (SPN). The emergency path is then established through the cloud-based network management system and the municipal / prefecture-level SPN.

[0111] The technical solution provided in this invention, in response to a network replanning event detecting a network communication failure, firstly acquires network topology and network element operation and management data associated with the network replanning event, and generates a directed topology graph based on the network topology and network element operation and management data. The network and network element operation and management data are transformed into a directed topology graph for subsequent automated path planning. Further, a pre-configured fault content judgment template is acquired, and the target fault type corresponding to the network replanning event is determined based on the directed topology graph and the fault content judgment template corresponding to each fault type. By automatically configuring the fault content judgment template, the system can quickly and accurately determine the target fault type. Further, based on at least one first emergency path associated with the target fault node in the directed topology graph and the target fault type, the cost information of at least one first emergency path is determined. Based on the cost information of all candidate paths, a target emergency path is determined, and network parameters are configured for the target emergency path. Network communication with the target fault node is established based on the reconfigured network parameters. Based on the cost information of all candidate paths, automatic planning and selection of the optimal emergency path are achieved. This improves fault diagnosis and repair efficiency, shortens communication reconstruction time, and ensures rapid recovery from network transmission failures.

[0112] Figure 7 This is a schematic diagram of a 5G network optimal emergency path determination device provided in an embodiment of the present invention, as shown below. Figure 7 As shown, the device includes: a directed topology graph generation module 310, a target fault type determination module 320, an overhead information determination module 330, and a network communication establishment module 340.

[0113] The system includes a directed topology graph generation module 310, which, in response to a network replanning event that detects a network communication failure, acquires network topology and network element operation and control data associated with the network replanning event, and generates a directed topology graph based on the network topology and network element operation and control data. The directed topology graph includes network core devices corresponding to root nodes and user edge devices corresponding to leaf nodes, and the faulty link is displayed in a first form in the directed topology graph. A target fault type determination module 320 is used to determine the target fault type corresponding to the network replanning event based on the directed topology graph and a pre-configured fault content judgment template corresponding to each fault type. An overhead information determination module 330 is used to determine the overhead information of at least one first emergency path associated with the target fault node in the directed topology graph and the target fault type. A network communication establishment module 340 is used to determine the target emergency path based on the overhead information of all candidate paths, and configure network parameters for the target emergency path to establish network communication for the target fault node based on the reconfigured network parameters.

[0114] The technical solution provided in this invention, in response to a network replanning event detecting a network communication failure, firstly acquires network topology and network element operation and management data associated with the network replanning event, and generates a directed topology graph based on the network topology and network element operation and management data. The network and network element operation and management data are transformed into a directed topology graph for subsequent automated path planning. Further, a pre-configured fault content judgment template is acquired, and the target fault type corresponding to the network replanning event is determined based on the directed topology graph and the fault content judgment template corresponding to each fault type. By automatically configuring the fault content judgment template, the system can quickly and accurately determine the target fault type. Further, based on at least one first emergency path associated with the target fault node in the directed topology graph and the target fault type, the cost information of at least one first emergency path is determined. Based on the cost information of all candidate paths, a target emergency path is determined, and network parameters are configured for the target emergency path. Network communication with the target fault node is established based on the reconfigured network parameters. Based on the cost information of all candidate paths, automatic planning and selection of the optimal emergency path are achieved. This improves fault diagnosis and repair efficiency, shortens communication reconstruction time, and ensures rapid recovery from network transmission failures.

[0115] Based on the above technical solutions, network topology and network element operation and control data shall include at least one or more of the following: internal gateway protocol process and overhead data to which physical links belong, physical link bandwidth utilization rate, and network element management plane information data.

[0116] Based on the above technical solutions, the target fault type determination module includes:

[0117] An initial fault dataset determination unit is used to determine an initial fault dataset based on the target fault node and at least one IGP domain type in the directed topology graph; wherein, the target fault node includes a fault network identifier and the IGP domain to which the target fault node belongs, and the initial fault dataset includes at least one set of first data, the first data including an IGP domain, a faulty network element, a second path, and an SPE / NPE pair, wherein the faulty network element is related to the target fault node;

[0118] The fault network element reading unit is used to read at least two fault network elements in the initial fault dataset that are closest to the root node; wherein, the distance is determined based on the path length from the fault network element to the core domain root node;

[0119] The preferred network element determination unit is used to search for at least one neighboring network element along the direction of the root node with the at least two faulty network elements, and to take the neighboring network element with the lowest cost to reach the at least one neighboring network element as the preferred network element;

[0120] The target fault type determination unit is used to search the leaf nodes by taking the preferred network element as the source network element in order to determine the target fault type.

[0121] Based on the above technical solutions, the target fault type determination unit includes:

[0122] The path data list generation subunit is used to record all SPE pair data in the access domain if the domain where the source network element is located is an access domain, and traverse all IGP domain network elements along the leaf nodes of the source network element to generate a path data list; it is also used to traverse all network elements in the IGP domain along the leaf nodes with the source network element as the starting node if the domain where the source network element is located is a core domain or a backbone aggregation domain to generate a path data list; wherein, the path data list includes source network elements and leaf network elements.

[0123] Based on the above technical solutions, the device further includes:

[0124] The shared network element identifier determination unit is used to determine whether a shared network element identifier exists based on the initial fault dataset and the path data list;

[0125] The target fault type determination unit is used to send the reachability identifier, the SPE / NPE pair associated with the leaf-direction network element, and the IGP domain number to the scenario classification judgment module if the fault exists, so as to determine the target fault type based on the scenario classification judgment module; and is also used to send the unreachability identifier and the current IGP domain type to the domain type verification module if the fault does not exist, so as to determine whether only the core domain exists, and determine the target fault type based on the judgment result.

[0126] Based on the above technical solutions, the target fault type determination unit includes:

[0127] The core domain determination subunit is used to determine whether only a core domain exists;

[0128] The fault type determination subunit is used to determine the target fault type as a core IGP domain SPE / NPE unreachable fault type if the fault type is true; and to compare the leaf-oriented network element SPE pair with the SPE pair in the initial fault data set if the fault type is false, so that if the comparison results are inconsistent, the target fault type is determined as a cross-backbone convergence SPE unreachable fault type.

[0129] Based on the above technical solutions, the device further includes: if the comparison results of the leaf-oriented network element SPE pair and the SPE pair in the initial fault dataset are the same, comparing the IGP domain number where the leaf-oriented network element is located with the IGP domain number in the initial fault dataset; if the comparison results are inconsistent, determining that the target fault type is an unreachable fault type of the same backbone aggregation IGP; if the comparison results are consistent, determining that the target fault type is an unreachable fault type of the same access IGP domain.

[0130] Based on the above technical solutions, the overhead information determination module includes:

[0131] The utilization weight determination unit is used to determine the utilization weight based on the cumulative utilization rate of the link bandwidth corresponding to the at least one emergency path;

[0132] The fault type weight determination unit is used to determine the fault type weight based on the target fault type.

[0133] The numerical determination unit is used to determine a first value based on the influence factor value of the link bandwidth utilization and the corresponding utilization weight, and to determine a second value based on the type influence value and the corresponding fault type weight of the target fault type.

[0134] The cost information determination unit is used to determine the cost information of each first emergency path based on the first value and the second value of each first emergency path.

[0135] The 5G network optimal emergency path determination device provided in this embodiment of the invention can execute the 5G network optimal emergency path determination method provided in any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the method.

[0136] Figure 8 A schematic diagram of an electronic device 10, which can be used to implement embodiments of the present invention, is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0137] like Figure 8As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded from storage unit 18 into the RAM 13. The RAM 13 can also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0138] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0139] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as a method for determining the optimal emergency path in a 5G network.

[0140] In some embodiments, a method for determining an optimal emergency path for a 5G network can be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program can be loaded and / or installed on electronic device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the method for determining an optimal emergency path for a 5G network described above can be performed. Alternatively, in other embodiments, processor 11 can be configured to perform a method for determining an optimal emergency path for a 5G network by any other suitable means (e.g., by means of firmware).

[0141] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0142] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0143] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0144] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0145] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or middleware components (e.g., application servers), or frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0146] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0147] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0148] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A method for determining the optimal emergency path in a 5G network, characterized in that, include: In response to a network replanning event that detects a network communication failure, network topology and network element operation and control data associated with the network replanning event are acquired, and a directed topology graph is generated based on the network topology and network element operation and control data; wherein, the directed topology graph includes network core devices corresponding to the root node and user edge devices corresponding to the leaf nodes, and the faulty link is displayed in the directed topology graph in a first form; Based on the directed topology graph and the fault content judgment template corresponding to each fault type in the pre-configured configuration, the target fault type corresponding to the network replanning event is determined; Based on at least one first emergency path associated with the target fault node in the directed topology graph and the target fault type, determine the cost information of the at least one first emergency path; Based on the cost information of all candidate paths, a target emergency path is determined, and network parameters are configured for the target emergency path to establish network communication for the target fault node based on the reconfigured network parameters.

2. The method according to claim 1, characterized in that, The network topology and network element operation and control data shall include at least one or more of the following: internal gateway protocol process and overhead data to which physical links belong, physical link bandwidth utilization, and network element management plane information data.

3. The method according to claim 1, characterized in that, The step of determining the target fault type corresponding to the network replanning event based on the directed topology graph and the fault content judgment template corresponding to each fault type in the pre-configured configuration includes: An initial fault dataset is determined based on the target fault node and at least one IGP domain type in the directed topology graph; wherein, the target fault node includes a fault network identifier and the IGP domain to which the target fault node belongs, and the initial fault dataset includes at least one set of first data, the first data including an IGP domain, a faulty network element, a second path, and an SPE / NPE pair, wherein the faulty network element is related to the target fault node; Read at least two faulty network elements in the initial fault dataset that are closest to the root node; wherein the distance is determined based on the path length from the faulty network element to the core domain root node; Search for at least one neighboring network element along the direction of the root node using the at least two faulty network elements, and select the neighboring network element with the lowest cost to reach the at least one neighboring network element as the preferred network element; The preferred network element is used as the source network element to search the leaf nodes in order to determine the target fault type.

4. The method according to claim 3, characterized in that, The step of using the preferred network element as the source network element to search for the leaf node includes: If the domain where the source network element is located is an access domain, then all SPE pair data in the access domain are recorded, and all IGP domain network elements along the leaf nodes of the source network element are traversed to generate a path data list. If the domain where the source network element is located is a core domain or a backbone aggregation domain, then all network elements in the IGP domain are traversed along the leaf nodes with the source network element as the starting node to generate a path data list. The path data list includes source network elements and leaf network elements.

5. The method according to claim 4, characterized in that, The method further includes: Based on the initial fault dataset and path data list, determine whether there is a shared network element identifier; If it exists, the reachability identifier, the SPE / NPE pair associated with the leaf network element, and the IGP domain number are sent to the scenario classification judgment module to determine the target fault type based on the scenario classification judgment module. If it does not exist, the unreachable flag and the current IGP domain type are sent to the domain type verification module to determine whether only the core domain exists, and the target fault type is determined based on the judgment result.

6. The method according to claim 5, characterized in that, The scenario-based classification and judgment module determines the target fault type, including: Determine if only the core domain exists; If so, then the target fault type is determined to be the core IGP domain SPE / NPE unreachable fault type; If not, compare the SPE pairs associated with the leaf network element with the SPE pairs in the initial fault dataset, so that if the comparison results are inconsistent, the target fault type is determined to be the cross-backbone convergence SPE unreachable fault type.

7. The method according to claim 6, characterized in that, The method further includes: If the comparison result of the SPE pair associated with the leaf element is the same as that of the SPE pair in the initial fault dataset, compare the IGP domain number of the leaf element with the IGP domain number in the initial fault dataset. When the comparison results are inconsistent, the target fault type is determined to be the same backbone convergence cross-IGP unreachable fault type; If the comparison results are consistent, the target fault type is determined to be an unreachable fault type within the same access IGP domain.

8. The method according to claim 1, characterized in that, The step of determining the cost information of the at least one first emergency path based on the target fault node associated with the target fault node in the directed topology graph and the target fault type includes: The utilization weight is determined based on the cumulative utilization rate of the link bandwidth corresponding to at least one first emergency path; Determine the fault type weight based on the target fault type; Based on the influence factor value of the link bandwidth utilization and the corresponding utilization weight, a first value is determined, and based on the type influence value and the corresponding fault type weight of the target fault type, a second value is determined. The cost information for each first emergency path is determined based on the first and second values ​​of each first emergency path.

9. A device for determining the optimal emergency path in a 5G network, characterized in that, include: A directed topology graph generation module is used to respond to a network replanning event that detects a network communication failure, acquire network topology and network element operation and control data associated with the network replanning event, and generate a directed topology graph based on the network topology and network element operation and control data; wherein, the directed topology graph includes network core devices corresponding to the root node and user edge devices corresponding to the leaf nodes, and the faulty link is displayed in the directed topology graph in a first form; The target fault type determination module is used to determine the target fault type corresponding to the network replanning event based on the directed topology graph and the fault content judgment template corresponding to each fault type in the pre-configured configuration. The overhead information determination module is used to determine the overhead information of the at least one first emergency path based on the target fault node associated with the target fault node in the directed topology graph and the target fault type. The network communication establishment module is used to determine the target emergency path based on the cost information of all candidate paths, and configure network parameters for the target emergency path to establish network communication for the target fault node based on the reconfigured network parameters.

10. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform a 5G network optimal emergency path determination method according to any one of claims 1-8.

Images